diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml index 2150ebe0f3fdd5bc7ea71212282eb806857b717e..936278e133e946ea105a73c09635afb027fcfaef 100644 --- a/tools/metrics/histograms/histograms.xml +++ b/tools/metrics/histograms/histograms.xml @@ -5,217902 +5,14 @@ found in the LICENSE file. --> - - - - - - - - - - - - - - - - - Removed 11/2018 because a need was discovered for a non-boolean value. - Superseded by Accessibility.Android.AnimationsEnabled2. - - dmazzoni@chromium.org - smcgruer@chromium.org - - Tracks whether animations are enabled on Android (e.g. if the animator - duration scale is non-zero.) The purpose is to inform the design of the - prefers-reduced-motion media feature; see http://crbug.com/722548. This is - logged once, 45 seconds after startup. - - - - - dmazzoni@chromium.org - smcgruer@chromium.org - chrome-a11y-core@google.com - - Tracks whether animations are enabled on Android (e.g. if the animator - duration scale is non-zero.) The purpose is to inform the design of the - prefers-reduced-motion media feature; see http://crbug.com/722548. This is - logged once, 45 seconds after startup. - - This replaced Accessibility.Android.AnimationsEnabled because the older - histogram did not capture the default (e.g. no flag) case. - - - - - - - aleventhal@chromium.org - chrome-a11y-core@google.com - - Tracks whether a screen reader is enabled on Android (e.g. Talkback). This - is checked once, 45 seconds after startup. Note: prefer - Accessibility.Android.ScreenReader.EveryReport when querying for unique - users, as it is logged more frequently. - - - - - twellington@chromium.org - tedchoc@chromium.org - - Tracks whether the accessibility tab switcher is enabled when an - accessibility service (e.g. TalkBack or Switch Access) is enabled that would - typically cause the accessibility tab switcher to be used. Recorded when the - activity is resumed or accessibility services are turned on. - - - - - twellington@chromium.org - skym@chromium.org - - Records the current user font size pref when exiting accessibility settings - if the preference was changed. The font size ranges from 50% to 200% and can - be set in increments of 5%; the default is 100%. - - - - - twellington@chromium.org - skym@chromium.org - - Records the current user font size pref during deferred startup for - ChromeActivity. The font size ranges from 50% to 200% and can be set in - increments of 5%; the default is 100%. - - - - - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Tracks flags and capabilities of enabled accessibility services. Recorded - every time an Android web content view first creates a virtual view - hierarchy, indicating that some accessibility service is running. The number - of emits of this histogram won't be as useful as the unique user counts. The - primary purpose of this is to guide optimization by determining what - capabilities of accessibility services are widespread and which ones are - relatively rare. - - - - - dmazzoni@chromium.org - jkim@igalia.com - chrome-a11y-core@google.com - - Tracks usage of ATK APIs on Linux Desktop. Recorded when ATK APIs that were - supposed to trigger AX mode enabled is called. The feature to turn on AX - mode through ATK APIs is disabled for now; see http://crbug.com/1086506. - - - - - evliu@google.com - media-dev@chromium.org - - Whether custom caption settings were loaded from the user preferences. - Recorded when WebKit preferences are overridden. - - - - - evliu@google.com - media-dev@chromium.org - - Whether custom caption settings were loaded from the system preferences. - Recorded when WebKit preferences are overridden. - - - - - dtseng@chromium.org - chrome-a11y-core@google.com - - A user can control ChromeVox via a variety of gestures on the touch screen. - For example, swiping right with one finger causes ChromeVox to navigate to - the next object. Track all possible gestures here. - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS Accessibility Menu is set to be shown regardless of - the state of a11y features.(logged once 45 secs after startup). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - dtseng@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS Autoclick feature is on (logged once 45 secs after - startup). - - - - - katie@chromium.org - dtseng@chromium.org - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Recorded when a user has picked a new autoclick action type from the bubble - menu. - - - - - - Removed 06/2020 as it is no longer needed for analysis. - - dmazzoni@chromium.org - kenjibaheux@google.com - katie@chromium.org - chrome-a11y-core@google.com - - If the user has enabled Autoclick, this is the delay set by the user for - autoclicks to occur, in milliseconds, at startup and when changed. - - - - - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS caret highlighting is on (logged once 45 secs after - startup). - - - - - - Removed M85 when no longer needed, as there is no longer a restriction on - having both features enabled. - - anastasi@google.com - dtseng@chromium.org - chrome-a11y-core@google.com - - When ChromeVox is enabled, true if Switch Access was previously enabled. - - - - - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Set when a Chrome OS user has spoken feedback enabled, recorded once each - time ChromeVox starts up. True if the user has enabled "ChromeVox - Next", a new ChromeVox experience that became the default in Chrome 56 - (but can be toggled on or off by the user), false otherwise. - - - - - dmazzoni@chromium.org - katie@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS feature to colorize the cursor is enabled (logged once - 45 secs after startup). - - - - - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS cursor highlighting is on (logged once 45 secs after - startup). - - - - - anastasi@google.com - dtseng@chromium.org - chrome-a11y-core@google.com - - Whether the ChromeOS dictation feature is enabled (logged once 45 secs after - startup). - - - - - anastasi@google.com - dtseng@chromium.org - chrome-a11y-core@google.com - Records how users invoke Dictation. - - - - dmazzoni@chromium.org - katie@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS Docked Magnifier feature is on (logged once 45 secs - after startup). - - - - - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS focus highlighting is on (logged once 45 secs after - startup). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS High Contrast mode feature is on (logged once 45 secs - after startup). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS Large Cursor feature is on (logged once 45 secs after - startup). - - - - - yawano@chromium.org - lpalmaro@chromium.org - chrome-a11y-core@google.com - - Cursor size of the Chrome OS Large Cursor (logged once 45 secs after - startup). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS Screen Magnifier feature is on (logged once 45 secs - after startup). - - - - - dmazzoni@chromium.org - katie@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS select-to-speak is on (logged once 45 secs after - startup). - - - - - katie@chromium.org - chrome-a11y-core@google.com - - Whether Select-to-Speak had background shading enabled when activated. - - - - - - Removed 7/2018 in Issue 866550 in favor of using global Text-to-Speech - settings for speech pitch. - - katie@chromium.org - - The speech pitch setting when Select-to-Speak was activated. It is stored as - a sparse histogram with values (100 * speech_pitch). For example, a speech - pitch of 1.0 (default) will be seen as 100. - - - - - - Removed 7/2018 in Issue 866550 in favor of using global Text-to-Speech - settings for speech rate. - - katie@chromium.org - - The speech rate setting when Select-to-Speak was activated. It is stored as - a sparse histogram with values (100 * speech_rate). For example, a speech - rate of 1.0 (default) will be seen as 100. - - - - - katie@chromium.org - chrome-a11y-core@google.com - - A user may activate Select-to-Speak by holding down 'search' and clicking or - dragging a region with the mouse, or by highlighting an area and using - search + s to read just the highlighted area. Track the methods here. - - - - - katie@chromium.org - chrome-a11y-core@google.com - - A user has tapped a button in the tray to change Select-to-Speak's state. - The tap was interpreted by Select-to-Speak as a request to start selection, - to cancel speech, or to cancel selection, depending on Select-to-Speak's - internal state when the tap occured. This tracks when the button was tapped - and the event that it generated. - - - - - - Removed 06/2020 as it is no longer needed for analysis. - - katie@chromium.org - - Whether Select-to-Speak had per-word highlighting enabled when activated. - - - - - gzadina@google.com - tbarzic@chromium.org - - The value for shelf navigation buttons setting set by the user during OOBE. - The metric will be reported after the setting has been stable for 10 - seconds, or the OOBE screen in which the value can be set is closed (if the - setting changes multiple times in quick succession, only the final value - will be reported). - - - - - gzadina@google.com - tbarzic@chromium.org - - The value for shelf navigation buttons setting set by the user in Chrome OS - Settings page. The metric will be reported after the setting change has been - stable for 10 seconds, or the settings window in which the value is set gets - closed (if the setting changes multiple times in quick succession, only the - final value will be reported). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS Spoken Feedback feature is on (logged once 45 secs - after startup). Note: prefer Accessibility.CrosSpokenFeedback.EveryReport - when querying for unique users, as it is logged more frequently. - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - tengs@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome OS Sticky Keys feature is on (logged once 45 secs after - startup). - - - - - dmazzoni@chromium.org - anastasi@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS switch access is on (logged once 45 secs after - startup). - - - - - - Removed M85 when no longer needed, as there is no longer a restriction on - having both features enabled. - - anastasi@google.com - dtseng@chromium.org - - When Switch Access is enabled, true if ChromeVox was previously enabled. - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether the Chrome OS Virtual Keyboard feature is on (logged once 45 secs - after startup). - - - - - katie@chromium.org - dmazzoni@chromium.org - chrome-a11y-core@google.com - - Whether the Chrome accessibility image label setting is on (logged once 45 - secs after startup). - - - - - - Removed 06/2020 because we don't need to keep tracking this. - - katie@chromium.org - dmazzoni@chromium.org - - When a user selects the Chrome accessibility image labels option in the - context menu, whether they are trying to enable or disable the feature, or - enable it for a single use. Recorded when the user selects the option from - the context menu. The feature may not have been enabled if they do not - confirm on the modal dialog that appears after. - - - - - - Removed 06/2020 because we don't need to keep tracking this. - - katie@chromium.org - dmazzoni@chromium.org - - When a user selects the Chrome accessibility image labels option in - chrome://settings, whether they are trying to enable or disable the feature. - Recorded when the user activates the toggle from the settings page. The - feature may not have been enabled if they do not confirm on the modal dialog - that appears after. - - - - - katie@chromium.org - dmazzoni@chromium.org - - Whether a user accepts or does not accept a modal dialog enabling the image - labels option. If the user does not accept it this does not track whether - they closed it with the negative button, the close button, or keyboard - escape. - - - - - katie@chromium.org - dmazzoni@chromium.org - chrome-a11y-core@google.com - - The language of a web page where image labels were requested, as detected by - Chrome (not necessarily what language the page claims to be in). - - - - - katie@chromium.org - dmazzoni@chromium.org - chrome-a11y-core@google.com - - The language that was requested for image descriptions, based on the page - language, the user's accept languages and top languages, and the server - languages. - - - - - - Removed 03/2020 in favor of Accessibility.WinHighContrastTheme. - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether Windows system settings show that high-contrast mode is enabled and - the user has selected a light-on-dark color scheme (logged once 45 secs - after startup). This causes Chrome to prompt the user with a bubble to - optionally install a High Contrast extension and theme. - - - - - gambard@chromium.org - rkgibson@google.com - - This metric is related to the Preferred Content Size chosen by the user. It - is only recorded once per session. This is hit if the chosen category is not - listed in the map defined in - /ios/chrome/browser/ui/util/dynamic_type_util.mm. In that case, we should - update the code by adding an entry for the new category in that map. This is - logged when the helper to returning the multiplier associated with the - current preferred content size is called. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - The number of nodes on this page for which language detection was attempted. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - The number of nodes on this page for which a detected language was - successfully assigned. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - The number of unique languages which were detected to be the most probable - language for at least one node on the page, regardless of whether a detected - language was assigned for that node. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - Of the nodes which had a detected language assigned, the percentage for - which the assigned language was the language detected as having the highest - probability. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - Of the nodes for which language detection was attempted, the percentage for - which a language was successfully assigned. - - - - - chrishall@chromium.org - aboxhall@chromium.org - dmazzoni@chromium.org - - Of the nodes for which a detected language was successfully assigned, the - percentage where the assigned language differs from the author-provided - language. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Whether the Live Caption feature is enabled. This is logged once, 45 seconds - after startup. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Whether the sample rate or channel count of a Live Caption audio stream - changed midstream. This is logged once per audio stream on the destruction - of the Cloud speech recognition client. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Whether the Live Caption feature flag is enabled. This is logged once at the - time of component registration. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Logged when there's a change in the lifetime of a Live Caption audio stream: - When a session started and captions began arriving from the service, when a - session ended because the audio stream finished, or when the session ended - because a user clicked the close button on the caption bubble. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Records when a user enables or disables the Live Caption feature from - chrome://settings. - - - - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Whether the Live Caption feature is blocked because the website is on the - captioning blocklist. This is logged once per stream when the speech - recognition client is created. - - - - - - Removed 08/2020. Replaced by Accessibility.LiveCaption. - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Whether the Live Caption feature is enabled. This is logged once, 45 seconds - after startup. - - - - - - Removed 08/2020. Replaced by Accessibility.LiveCaption.Session. - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Logged when there's a change in the lifetime of a Live Caption audio stream: - When a session started and captions began arriving from the service, when a - session ended because the audio stream finished, or when the session ended - because a user clicked the close button on the caption bubble. - - - - - - Removed 08/2020. Replaced by Accessibility.LiveCaption.ToggleEnabled. - - katie@chromium.org - abigailbklein@google.com - evliu@google.com - chrome-a11y-core@google.com - - Records when a user enables or disables the Live Caption feature from - chrome://settings. - - - - - - Removed 2020-09: Data no longer needed or gathered. - - ellyjones@chromium.org - chrome-a11y-core@google.com - - Whether the "differentiate without color" Mac system setting is - enabled. This is logged once, 45 seconds after startup. - - - - - - Removed 2020-09: Data no longer needed or gathered. - - ellyjones@chromium.org - chrome-a11y-core@google.com - - Whether the "full keyboard access" Mac system setting is enabled. - This is logged once, 45 seconds after startup. - - - - - - Removed 2020-09: Data no longer needed or gathered. - - ellyjones@chromium.org - chrome-a11y-core@google.com - - Whether the "increase contrast" Mac system setting is enabled. - This is logged once, 45 seconds after startup. - - - - - dmazzoni@chromium.org - smcgruer@chromium.org - chrome-a11y-core@google.com - - Tracks whether the accessibilityDisplayShouldReduceMotion system property is - enabled. The purpose is to inform the design of the prefers-reduced-motion - media feature; see http://crbug.com/722548. This is logged once, 45 seconds - after startup. - - - - - ellyjones@chromium.org - chrome-a11y-core@google.com - - Whether the "reduce transparency" Mac system setting is enabled. - This is logged once, 45 seconds after startup. - - - - - - - aleventhal@chromium.org - chrome-a11y-core@google.com - - Tracks whether a screen reader is enabled on Mac (e.g. VoiceOver). This is - logged once, 45 seconds after startup. Note: prefer - Accessibility.Mac.ScreenReader.EveryReport when querying for unique users, - as it is logged more frequently. - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether Chrome has enabled accessibility support because the user passed the - --force-renderer-accessibility flag on the command-line (logged once 45 secs - after startup). - - - - - dmazzoni@chromium.org - aboxhall@chromium.org - chrome-a11y-core@google.com - - Whether individual accessibility mode flags are set. Tracked when each mode - flag is flipped from false to true. These flags are flipped automatically - when software communicates with Chrome via accessibility APIs. Flags can - only be flipped off by advanced users or for debugging using - chrome://accessibility/ - and that isn't tracked in this histogram. - - - - - - - lpalmaro@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - alemate@chromium.org - cros-oac@google.com - - Delay between login_prompt_visible and Chrome OS OOBE startup sound - playback. Depends on sound subsystem initialization time. - - - - - dmazzoni@chromium.org - janewman@microsoft.com - chrome-a11y-core@google.com - - Tracks time taken to execute the public Windows API that {API}. This is - recorded for all Windows users that call into our public APIs. - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 06/2020 as this is stable and doesn't need to be tracked closely. - - - - katie@chromium.org - dmazzoni@chromium.org - - For every image on a page with screen reader accessibility mode enabled, - this histogram will be used to understand minimum dimension of the image, - i.e. either the width or height in px. - - - - - - Removed 06/2020 as this is stable and doesn't need to be tracked closely. - - - - katie@chromium.org - dmazzoni@chromium.org - - For every image on a page with screen reader accessibility mode enabled, - this histogram will be used to understand the size ratio of the image. This - is the smaller dimension divided by the larger dimension. - - - - - amraboelkher@chromium.org - poromov@chromium.org - - Whether the Chrome OS Docked Magnifier shortcut is enabled. It's being - emitted when the Docked Magnifier shortcut is triggered. - - - - - amraboelkher@chromium.org - poromov@chromium.org - - Whether the Chrome OS High Contrast mode shortcut is enabled. It's being - emitted when the High Contrast shortcut is triggered. - - - - - amraboelkher@chromium.org - poromov@chromium.org - - Whether the Chrome OS Full-screen Magnifier mode shortcut is enabled. It's - being emitted when the Full-screen Magnifier shortcut is triggered. - - - - - amraboelkher@chromium.org - poromov@chromium.org - - Whether the Chrome OS Spoken Feedback shortcut is enabled. It's being - emitted when the Spoken Feedback shortcut is triggered. - - - - - - Removed 12/2016 in Issue 672205 with the addition of Accessibility.ModeFlag. - - dmazzoni@chromium.org - kenjibaheux@google.com - - Whether Chrome has enabled accessibility support because it detects - supported assistive technology running, or due to being manually enabled via - a command-line flag (logged once 45 secs after startup). - - - - - evliu@google.com - media-dev@chromium.org - - Whether a VTT file contains an embedded style block. Recorded when a VTT - file is parsed. - - - - - dmazzoni@chromium.org - smcgruer@chromium.org - chrome-a11y-core@google.com - - Tracks whether the SPI_GETCLIENTAREAANIMATION system property is enabled. - The purpose is to inform the design of the prefers-reduced-motion media - feature; see http://crbug.com/722548. This is logged once, 45 seconds after - startup. - - - - - dmazzoni@chromium.org - nektar@chromium.org - chrome-a11y-core@google.com - Tracks usage of all public Windows accessibility APIs. - - - - dmazzoni@chromium.org - nektar@chromium.org - kbabbitt@microsoft.com - chrome-a11y-core@google.com - - Tracks properties requested via UI Automation GetPropertyValue(). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - chrome-a11y-core@google.com - - Whether Windows system settings show that audio descriptions are enabled - (logged once 45 secs after startup). - - - - - dmazzoni@chromium.org - almaher@microsoft.com - weblayoutdev@microsoft.com - - Tracks which Windows high contrast theme is set in system settings (logged - once 45 secs after startup). AccessibilityHighContrastColorScheme::None - indicates that high contrast mode is not enabled. - - - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@chromium.org - chrome-a11y-core@google.com - - Whether the third-party JAWS screen reader is running (logged once 45 secs - after startup). Note: prefer Accessibility.WinJAWS.EveryReport when querying - for unique users, as it is logged more frequently. - - - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@chromium.org - chrome-a11y-core@google.com - - Whether the third-party NVDA screen reader is running (logged once 45 secs - after startup). Note: prefer Accessibility.WinNVDA.EveryReport when querying - for unique users, as it is logged more frequently. - - - - - - System Access To Go is a discontinued product. - - dmazzoni@chromium.org - kenjibaheux@google.com - - Whether the third-party System Access To Go screen reader is running (logged - once 45 secs after startup). - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - - Whether Windows system settings show that a screen reader is running (logged - once 45 secs after startup). Note that this does not necessarily mean that - Chrome has detected a supported screen reader and has enabled its - accessibility mode. - - - - - - - aleventhal@chromium.org - - Whether the accessibility mode flag shows that a screen reader is running - (logged once 45 secs after startup). In this case, Chrome has detected - accessibility calls that would normally only occur from a screen reader. See - also the more specific metrics such as Accessibility.WinJAWS/WinNVDA. Note: - prefer Accessibility.WinScreenReader2.EveryReport when querying for unique - users, as it is logged more frequently. - - - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@chromium.org - chrome-a11y-core@google.com - - Whether Windows system settings show that Sticky Keys are enabled. - - - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@chromium.org - chrome-a11y-core@google.com - - Whether the third-party Supernova screen reader is running (logged once 45 - secs after startup). Note: prefer Accessibility.Supernova.EveryReport when - querying for unique users, as it is logged more frequently. - - - - - - - dmazzoni@chromium.org - kenjibaheux@google.com - aleventhal@chromium.org - chrome-a11y-core@google.com - - Whether the third-party ZoomText screen magnifier is running. Note: prefer - Accessibility.WinZoomText.EveryReport when querying for unique users, as it - is logged more frequently. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Records the source of in-session account addition (or re-authentication) - triggers on Chrome OS. This is recorded whenever an in-session account - addition (or re-authentication) is triggered - either explicitely by the - user, or automatically by Gaia (for accounts requiring immediate - re-authentication). - - - - - sinhak@chromium.org - anastasiian@chromium.org - - The result of creating a Reauth Proof Token (RAPT) for the parent in - secondary EDU account addition flow. Recorded after parent enters their - password and child access token is fetched. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - The result of fetching an access token for the child with |accounts.reauth| - scope in secondary EDU account addition flow. Recorded after parent enters - their password. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - The result of fetching a list of parents in secondary EDU account addition - flow. Recorded when user opens 'Add EDU account' flow. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Records the last completed step in the EDU account addition flow. Allows to - track the drop rate by screen. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Measures the time taken to fully initialize Chrome OS Account Manager. This - is recorded once per user session, at login time. - - - - - - Removed in M84 as part of https://crrev.com/c/2131912 The legacy code path - and API being checked by this UMA stat no longer exist. - - sinhak@chromium.org - - Tracks the usage of the legacy Primary Account setting flow vs the new flow - through Account Manager. This is recorded only once per session, at login - time. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Tracks the service type received with the mirror response header. - - - - - sinhak@chromium.org - - Tracks the final result of migrating accounts to Chrome OS Account Manager. - This is recorded only once per session, at login time. - - - - - - - sinhak@chromium.org - - Tracks the result of individual migration steps of migrating accounts to - Chrome OS Account Manager. This is recorded only once per session, at login - time. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Whether user has received a Mirror re-authentication request for account - with invalid cookies. Recorded when we open a re-authentication dialog for - the invalid account. See https://crbug.com/1012649 for details. - - - - - sinhak@chromium.org - - Tracks the number of accounts stored in Chrome OS Account Manager by a given - user. This is recorded only once per session, at login time. - - - - - sinhak@chromium.org - anastasiian@chromium.org - - Tracks the status of token loads from disk by Chrome OS Account Manager, for - a given user. This is recorded only once per session, at login time. - - - - - siggi@chromium.org - - The analyzer creation error code. Logged each time analyzer creation fails, - at most once per processed stability debug file. - - - - - siggi@chromium.org - - Status of the initialization to collect stability debug files. Logged once, - during the initialization of the stability debug file collection. - - - - - siggi@chromium.org - - Number of files found during stability file collection. Logged each time the - stability file collection proceeds (at most once per launch). - - - - - siggi@chromium.org - - Status for the collection of a stability debug file. Logged each time a - debug file collection attempt is made. - - - - - siggi@chromium.org - - Status for the analysis of the system session state. Logged each time a - debug file is collected. - - - - - siggi@chromium.org - - Time spent collecting stability debug information. Logged each time a - collection is performed. - - - - - - Removed 05/2017 in favor of ActivityTracker.Collect.Status. - - manzagop@chromium.org - - Number of unclean shutdowns, as derived from the stability instrumentation. - Logged each time stability file collection is performed. - - - - - - Removed 05/2017 in favor of ActivityTracker.Collect.Status. - - manzagop@chromium.org - - Number of unclean shutdowns that can potentially be attributed to system - instability. This should be smaller or equal to UncleanShutdownCount. Logged - each time stability file collection is performed. - - - - - siggi@chromium.org - - Status of the minidump writing. Logged each time a writing a minidump is - attempted. - - - - - siggi@chromium.org - - Events that occur during crash collection of the debug file. Logged each - time an event of interest occurs during crash debug file collection. - - - - - - Removed 05/2017 in favor of ActivityTracker.CollectCrash.Event. - - manzagop@chromium.org - - Success of the attempt to open the debug file for deletion. Logged each time - a debug file is opened for deletion during collection from the crash - handler. - - - - - siggi@chromium.org - - Status for the collection of a stability debug file. Logged each time a - debug file collection attempt is made from the crash handler. - - - - - siggi@chromium.org - - Events pertaining to recording to the debug file. Logged each time an event - of interest occurs wrt debug file recording. - - - - - - Removed 05/2017 in favor of ActivityTracker.Record.Event. - - manzagop@chromium.org - - Status of internal activity tracking initialization. Logged once, during the - activity tracking initialization. - - - - - - Setup time is <=10ms for 90% with 0.1% taking >500ms. Removed 2019/06. - - siggi@chromium.org - - Time spent setting up the stability debugging instrumentation. Logged once, - during setup of the stability debugging instrumentation. - - - - - - Gaussian distribution around 22 with 0.1% being >=100. Removed 2019/06. - - bcwhite@chromium.org - - The number of threads being tracked for activities such as waiting for a - lock/event, a thread to join, or a task to run. Analysis of this data can - reveal why a thread will not exit. This value is updated every time a new - thread gets an activity tracked for the first time so will show one count - for every permanent thread but multiple counts for a thread than exits and - is replaced. - - - - - - Never occurred. Removed 2019/06. - - bcwhite@chromium.org - - The limit on the number of thread trackers that could be allocated from the - persistent memory segment. Trackers beyond this number were allocated from - the heap and thus were not available for analysis. This value is updated on - every "memory full" failure. - - - - - tobyhuang@chromium.org - michaelpg@chromium.org - danan@chromium.org - - Records the number of users who go through the Add Supervision process to - convert regular accounts to Geller accounts. Initiated count is incremented - when Add Supervision dialog is opened. Completed count is incremented when - supervision is successfully enrolled. Signed out count is incremented when - the user clicks "Sign out" after enrollment at the end of the - process in the dialog. Closed count is incremented when the Add Supervision - dialog is closed prior to enrollment, excluding sign out. Switched accounts - count is incremented when the user clicks "Sign out" within the - dialog to swich accounts before enrollment completion. - - - - - tobyhuang@chromium.org - michaelpg@chromium.org - danan@chromium.org - - Measures the amount of time in milliseconds for users to successfully enroll - in supervision. - - - - - tobyhuang@chromium.org - michaelpg@chromium.org - danan@chromium.org - - Measures the amount of time in milliseconds for users to exit the Add - Supervision dialog without enrollment. This can happen if the user closes - the Add Supervision dialog or signs out to switch accounts. - - - - - tobyhuang@chromium.org - michaelpg@chromium.org - danan@chromium.org - - Measures the amount of time in milliseconds for users to sign out after - enrolling in supervision. Elapsed time is measured starting from when the - Add Supervision dialog was first opened. - - - - - - Removed April 2019 - - csharrison@chromium.org - jkarlin@chromium.org - - For a given ad request, logs information related to whether it is isolated - from the top-level context. Logged per ad subresource request. - - - - - - Removed April 2019 - - csharrison@chromium.org - jkarlin@chromium.org - - For a given request, logs information related to whether it is marked as an - ad, and whether it is secure (e.g. https). Logged per subresource request. - - - - - - Removed 10/2019 in issue 1000058; no longer needed. - - johnidel@chromium.org - - Total number of bytes buffered over the lifetime of a WebMediaPlayer inside - of an adframe. Suffixed by type of playback. - - - - - johnidel@chromium.org - dalecurtis@chromium.org - - Duration in milliseconds of HTML5 media (when known). Only recorded for - media within ad subframes. This is recorded every time the duration changes - for a video, and can be recorded multiple times for a single video (the - overall duration may not be known when loading starts). Because the duration - will generally increase as more video gets buffered, this histogram may skew - low. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Load type of HTML5 media in ad subframes such as URL, MediaSource and - MediaStream. - - - - - - Removed 07/2019 in favor of Ads.ResourceUsage.Size.Cache2. - - johnidel@chromium.org - jkarlin@chromium.org - - For a given resource fetched from the disk cache, logs the encoded body - length of the resource, even if the resource request was canceled or - incomplete. Recorded when the resource request is complete, or when the page - is destroyed/navigated for incomplete resources. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - For a given resource fetched from the disk cache or blink memory cache, logs - the encoded body length of the resource, even if the resource request was - canceled or incomplete. Recorded when the resource request is complete, or - when the page is destroyed/navigated for incomplete resources. The sum of - samples across a page load may differ substatially from the true sum due to - per-sample rounding. These are not intended to be compared to page level - histograms. - - - - - - Removed 10/2018. Replaced with - Ads.ResourceUsage.Size.Network.Mainframe.AdResource and - Ads.ResourceUsage.Size.Cache.Mainframe.AdResource. - - jkarlin@chromium.org - johnidel@chromium.org - - For a given ad resource in the main frame, logs the network bytes received - for the resource, even if the resource request was canceled or incomplete. - - - - - - Removed 10/2018. Replaced with - Ads.ResourceUsage.Size.Network.Mainframe.VanillaResource and - Ads.ResourceUsage.Size.Cache.Mainframe.VanillaResource. - - jkarlin@chromium.org - johnidel@chromium.org - - For a given non-ad resource in the main frame, logs the network bytes - received for the resource, even if the resource request was canceled or - incomplete. - - - - - - Removed 10/2018. Replaced with Ads.ResourceUsage.Size.Cache.Mime and - Ads.ResourceUsage.Size.Network.Mime. - - johnidel@chromium.org - jkarlin@chromium.org - - Size of resources tagged as ads, identified by the response header mime - type. This includes resources that did not complete loading. Recorded when - the resource request is completed. For incomplete requests, recorded when - the page is destroyed/navigated. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - For a given resource fetched from the network, logs the network bytes used - to load the resource (including headers), even if the resource request was - canceled or incomplete. Recorded when the resource request is complete, or - when the page is destroyed/navigated for incomplete resources. The sum of - samples across a page load may differ substatially from the true sum due to - per-sample rounding. These are not intended to be compared to page level - histograms. - - - - - - Removed 10/2018. Replaced with - Ads.ResourceUsage.Size.Network.Subframe.AdResource and - Ads.ResourceUsage.Size.Cache.Subframe.AdResource. - - jkarlin@chromium.org - johnidel@chromium.org - - For a given ad resource in a subframe, logs the network bytes received for - the resource, even if the resource request was canceled or incomplete. - - - - - - Removed 10/2018. Replaced with - Ads.ResourceUsage.Size.Network.Subframe.VanillaResource and - Ads.ResourceUsage.Size.Cache.Subframe.VanillaResource. - - jkarlin@chromium.org - johnidel@chromium.org - - For a given non-ad resource in a subframe, logs the network bytes received - for the resource, even if the resource request was canceled or incomplete. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The rank of the clicked anchor element in terms of area. This histogram is - recorded when the anchor element is clicked. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The interval between consecutive clicks of anchor elements. This histogram - is recorded when an anchor element is clicked except the first click in the - current document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The duration between page load and the first click of an anchor element. If - the first click happens before page load, then the sample is recorded in - bucket 0. This histogram is recorded when an anchor element is clicked for - the first time in the current document. - - - - - - Removed 07/2018. Replaced with - AnchorElementMetrics.Clicked.HrefEngagementScore2. - - chelu@chromium.org - tbansal@chromium.org - - The target link (href) engagement score of an anchor element. The score is - retrieved from the site engagement service. Currently all scores reported - are set to 0. This will soon change. This histogram is recorded when the - anchor element is clicked. - - - - - - Obsoleted in M79. - - chelu@chromium.org - tbansal@chromium.org - - The site engagement score of the target link (href) of an anchor element. - The score is retrieved from the site engagement service. This histogram is - recorded when the anchor element is clicked, and the score is larger than 0. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The calculated navigation score of the target link (href) of an anchor - element. The score is retrieved from the site engagement service. This - histogram is recorded when the anchor element is clicked and the score has - already been calculated when the document is loaded. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The rank of the navigation score of the target link (href) of an anchor - element. This histogram is recorded when the anchor element is clicked and - the score has already been calculated when the document is loaded. - - - - - tbansal@chromium.org - - True if the target link of the anchor element has the same host as the root - document. Recorded only on default search engine pages. - - - - - tbansal@chromium.org - ryansturm@chromium.org - src/chrome/browser/navigation_predictor/OWNERS - - True if the target link of the anchor element has the same host as the root - document. Recorded only on pages whose URL do not match the default search - engine. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements that contains - images and the total number of anchor elements. This histogram is recorded - when the anchor element is clicked and it contains images. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements that contains - images and the total number of anchor elements. This histogram is recorded - when the anchor element is clicked and it does not contain images. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements that is inside an - iframe and the total number of anchor elements. This histogram is recorded - when the anchor element is clicked and it is inside an iframe. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements that is inside an - iframe and the total number of anchor elements. This histogram is recorded - when the anchor element is clicked and it is not inside an iframe. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio between the height of the root document and the height of the - viewport times 100. This histogram is recorded when the anchor element is - clicked. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements whose href have - the same host as the document and the total number of anchor elements. This - histogram is recorded when the anchor element is clicked and href of the - anchor element has a different host than the document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements whose href have - the same host as the document and the total number of anchor elements. This - histogram is recorded when the anchor element is clicked and href of the - anchor element has the same host as the document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements whose href is - incremented by one from the url of the document and the total number of - anchor elements. This histogram is recorded when the anchor element is - clicked and its href is not incremented by one from the url of the document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the number of anchor elements whose href is - incremented by one from the url of the document and the total number of - anchor elements. This histogram is recorded when the anchor element is - clicked and its href is incremented by one from the url of the document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - True if the anchor element contains an image element, false if it is not. - - - - - - Obsoleted in M79. - - chelu@chromium.org - tbansal@chromium.org - - The site engagement score of the document URL. The score is retrieved from - the site engagement service. - - - - - - Obsoleted in M79. - - chelu@chromium.org - tbansal@chromium.org - - The site engagement score of the target link (href) of an anchor element. - The score is retrieved from the site engagement service. - - - - - - Obsoleted in M79. - - chelu@chromium.org - tbansal@chromium.org - - The site engagement score of the target link (href) of an anchor element. - The score is retrieved from the site engagement service. This histogram is - recorded when href is an external link. - - - - - - Removed 05/2020. - - tbansal@chromium.org - - True if the anchor element was inside an iframe tagged as an ad iframe. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - True if the anchor element is within an iframe, false if it is not. - - - - - chelu@chromium.org - tbansal@chromium.org - - True if the target link of the anchor element has the same host as the root - document. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - True if the target URL of the anchor element and the URL of the root - document only differ by one number, and the number in the target URL equals - the number in the the URL of the root document plus one. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the clickable region area of an anchor element, - and the viewport area. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the distance from the center of the clickable - region of an anchor element to the top edge of the visible region, and the - viewport height. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the distance from the bottom of the clickable - region of an anchor element to the bottom edge of the root frame, and the - viewport height. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the distance from the top of the clickable - region of an anchor element to the top edge of the root frame, and the - viewport height. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the distance from the top of the clickable - region of an anchor element to the top edge of the visible region, and the - viewport height. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The ratio times 100 between the visible clickable region area of an anchor - element, and the viewport area. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The highest navigation score of the anchor elements sent to the browser - process on a page load. This histogram is recorded when the webpage is - loaded. Normalized to a value between 0.0 and 100.0. - - - - - - Removed 05/2020. - - chelu@chromium.org - tbansal@chromium.org - - The number of anchor element metrics sent to the browser process on a page - load. This histogram is recorded when the webpage is loaded. - - - - - chelu@chromium.org - tbansal@chromium.org - - The number of anchor element metrics sent to the browser process on a page - load. Anchor elements having the same href are merged and counted as 1. This - histogram is recorded when the webpage is loaded. - - - - - - Removed 2020-01 - - twellington@chromium.org - - What caused ChromeTabbedActivity#onStop() to be called, which indicates that - Chrome is sent to the background. - - - - - - Removed 2020-01 - - twellington@chromium.org - - What happened when the user hit the system back button in - ChromeTabbedActivity. - - - - - peter@chromium.org - - Records whether notifications are enabled for Chrome, as the Android app, - every time metrics are logged. - - - - - - Removed 2019-01: New releases of Chrome+Android+ARM rely on NEON support. - - fdegans@chromium.org - - Reports the FPU capabilities of the Android ARM device. This is recorded - once per browser session during startup. - - - - - mcarlen@chromium.org - - Reports the drop out reason of an Autofill Assistant script. It is recorded - when Autofill Assistant is shut down or terminated. The AA_START value is - used as a baseline and counts the number of attempted starts of Autofill - Assistant flows. The sum of all drop out reasons should be the same as the - number of attempted starts (i.e. AA_START). - - - - - mcarlen@chromium.org - autofill_assistant+watch@google.com - - Reports the installation status of the DFM, e.g. installation deferred, - foreground installation succeeded etc. The metric cannot currently - distinguish whether the deferred installation succeeded or not. - - - - - lsuder@chromium.org - mcarlen@chromium.org - - Reports the basic user interactions that can happen in regard on boarding. - It is recorded on Autofill Assistant startup and during the on boarding. - - - - - arbesser@google.com - mcarlen@chromium.org - - Reports whether autofill information was changed during an autofill - assistant payment request, or not. This is recorded every time the user sees - the autofill assistant payment request. - - - - - arbesser@google.com - mcarlen@chromium.org - - Reports whether the user selected a profile which does not contain separate - first and last name. This is recorded when the user confirms the payment - request screen in autofill assistant provided that 'name' was one of the - requested fields. - - - - - arbesser@google.com - mcarlen@chromium.org - - Reports on whether a billing postal code was required and whether the user - ultimately succeeded or not. Also reports if the user had to change their - profile or if the default profile already contained a billing postal code. - This histogram is reported either when the user taps the 'continue' button - of the autofill assistant payment request (and thus succeeds) or when - autofill assistant closes during the action (i.e., the user aborted). - - - - - arbesser@google.com - mcarlen@chromium.org - - Reports whether the autofill assistant payment request was successfully - completed (i.e., the continue button was tapped) or not, and whether the - payment request was initially pre-filled completely or not. This is recorded - every time the user sees the autofill assistant payment request. - - - - - ioanastefan@chromium.org - nator@chromium.org - knollr@chromium.org - - Records that an exact task has been created. Recorded when the task is - scheduled. - - - - - ioanastefan@chromium.org - nator@chromium.org - knollr@chromium.org - - Records the stored tasks migrated to the Protocol Buffer data format. The - metric is recorded when the migration to the new format is being done. The - migration is done at a restart / OS upgrade, if tasks stored in the old - format are found. - - - - - fgorski@chromium.org - nyquist@chromium.org - Records that a specific background task has been canceled. - - - - ioanastefan@chromium.org - nator@chromium.org - knollr@chromium.org - - Records that a specific task has been created with an expiration deadline. - Recorded when the task is scheduled. - - - - - ioanastefan@chromium.org - nator@chromium.org - knollr@chromium.org - - Records that a specific task has been created without the expiration feature - activated. Recorded when the task is scheduled. - - - - - ioanastefan@chromium.org - nator@chromium.org - knollr@chromium.org - - Records that a specific background task has expired. Recorded before the - task is to be started. - - - - - fgorski@chromium.org - nyquist@chromium.org - Records that a specific background task has loaded native. - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific background task has loaded native in Full Browser - Mode. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific background task has loaded native in Reduced Mode. - - - - - fgorski@chromium.org - nyquist@chromium.org - - Records that a specific background task has failed to be scheduled. - - - - - fgorski@chromium.org - nyquist@chromium.org - - Records that a specific background task has been successfully scheduled. - - - - - fgorski@chromium.org - nyquist@chromium.org - Records that a specific background task has been started. - - - - fgorski@chromium.org - nyquist@chromium.org - - Records that a specific background task has been stopped by Background Task - Scheduler before it was able to complete itself. - - - - - - Removed 08/2017. Made decision in issue 736066 with already acquired data. - So this is no longer needed. - - boliu@chromium.org - - Measure time from bindService call to onServiceConnected. This is part of - launching child services on Android that's under Android's control. Recorded - in the first onServiceConnected of a connection. - - - - - - Removed 08/2017. Made decision in issue 736066 with already acquired data. - So this is no longer needed. - - boliu@chromium.org - - Boolean histogram that records whether bindServiced timed out. Timeout is - recorded in a delayed task, and success is recorded in onServiceConnected - callback. - - - - - boliu@chromium.org - src/base/android/OWNERS - - When ChildProcessConnection fallback is enabled (Android 10+ for sandboxed - services), this is recorded after the timeout (10s) of every - ChildProcessConnection launch. Record whether fallback operation is - performed. - - - - - cduvall@chromium.org - boliu@chromium.org - - Measures time from {type} child process starts to right before main. Only - recorded on Android N+. - - - - - - - - - - - - peconn@chromium.org - src/base/metrics/OWNERS - - Recorded at the same time as "CustomTabs.Visible", this metric - should eventually replace that one. This additionally distinguishes between - Trusted Web Activities, WebAPKs and Webapps. - - As of M87, this histogram is logged on a log start, rather than log end to - tag more logs. - - - - - yfriedman@chromium.org - - Android: Count of requests to Chrome browser which are granted to other apps - to read/write user's bookmarks and history. Only records cases when the app - has permission according to Android's permission manager. - - - - - yfriedman@chromium.org - - Android: Count of requests to Chrome browser which are granted to other apps - to read/write user's bookmarks and history. Only records cases where the app - is a system app or signed by Google. - - - - - - Unused as of 7/2019 - - mdjones@chromium.org - twellington@chromium.org - The duration the Chrome Home bottom sheet was open. - - - - - Unused as of 7/2019 - - mdjones@chromium.org - twellington@chromium.org - The reason the bottom sheet was opened. - - - - - Removed 03/2018. Chrome Home is being deprecated. - - mdjones@chromium.org - twellington@chromium.org - - Records the reciprocal of the velocity of a swipe that did not result in the - bottom sheet opening. This value is recorded in microseconds per dp traveled - and is only recorded if the "chrome-home-swipe-logic" experiment - is set to "velocity". - - - - - - Removed 03/2018. Chrome Home is being deprecated. - - mdjones@chromium.org - twellington@chromium.org - - Records the reciprocal of the velocity of a swipe that resulted in the - bottom sheet opening and the user navigating to a URL or a different sheet - content. This value is recorded in microseconds per dp traveled. - - - - - - Removed 03/2018. Chrome Home is being deprecated. - - mdjones@chromium.org - twellington@chromium.org - - Records the reciprocal of the velocity of a swipe that resulted in the - bottom sheet opening but the user taking no action (i.e. the next action is - the sheet closing). This value is recorded in microseconds per dp traveled. - - - - - - Removed 03/2018. Chrome Home is being deprecated. - - mdjones@chromium.org - twellington@chromium.org - - Records the reciprocal velocity of a swipe that resulted in the bottom sheet - opening. This value is recorded in microseconds per dp traveled and is only - recorded if the "chrome-home-swipe-logic" experiment is set to - "velocity". - - - - - - Removed 01/2018 with the removal of the first version of Chrome Home. - - mdjones@chromium.org - twellington@chromium.org - - The result of showing the Chrome Home promo when launched from the overflow - menu. This action can only be performed if Chrome Home is enabled. - - - - - - Removed 01/2018 with the removal of the first version of Chrome Home. - - mdjones@chromium.org - twellington@chromium.org - - The result of showing the Chrome Home promo when launched from the NTP. This - action can only be performed if Chrome Home is disabled. - - - - - - Removed 01/2018 with the removal of the first version of Chrome Home. - - mdjones@chromium.org - twellington@chromium.org - - The result of showing the Chrome Home promo when launched from startup. This - action can only be performed if Chrome Home is disabled. - - - - - - Removed 01/2018 with the removal of the first version of Chrome Home. - - mdjones@chromium.org - twellington@chromium.org - The reason the Chrome Home promo was shown. - - - - - Removed 04/2018. Replaced with Android.Survey.DownloadResponseCode. - - danielpark@chromium.org - The response code of the completed survey download request. - - - - - Removed 04/2018. Replaced with Android.Survey.InfoBarClosingState. - - danielpark@chromium.org - - If the infobar was visible when it was closed and if it was closed directly - or not. - - - - - - Removed 04/2018. Replaced with Android.Survey.ShowSurvey. - - danielpark@chromium.org - - Whether or not the survey was successfully shown after its download. - - - - - - Removed 04/2018. Replaced with Android.Survey.SurveyFilteringResults. - - danielpark@chromium.org - - The result of the survey filtering process. Each enum represents a different - filter that caught the user. This is recorded on cold starts when we check - if a user qualifies for a survey. - - - - - - Unused as of 7/2019 - - mdjones@chromium.org - twellington@chromium.org - - The time between the last time the Chrome Home bottom sheet was closed and - the next time it was opened. - - - - - - Unused as of 7/2019 - - mdjones@chromium.org - twellington@chromium.org - - The time between app creation and the first open of the Chrome Home bottom - sheet for this run of Chrome. - - - - - - Unused as of 7/2019 - - mdjones@chromium.org - twellington@chromium.org - - Records whether or not the user preference for Chrome Home is set to - enabled. This is recorded whenever the browser is restarted and the state of - Chrome Home is first checked. This metric is only recorded if the user's - preference is set. - - - - - estevenson@chromium.org - agrieve@chromium.org - - The amount of time Chrome spends blocked on resource extraction. Generally, - extraction is completed in the background but in certain cases a main-thread - getResources() call may block on resource extraction. - - - - - estevenson@chromium.org - agrieve@chromium.org - - Describes the result of Android resource extraction, and is recorded once - per browser start as part of deferred startup (not at time of extraction). - - - - - estevenson@chromium.org - agrieve@chromium.org - - The amount of time spent on resource extraction, whether or not extraction - was performed in the background or foreground. - - - - - finnur@chromium.org - rayankans@chromium.org - - Measures whether the address selected from the contacts picker has derived - fields. Derived fields refer to the individual attributes of a full address, - such as city, country, region, or postcode. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the total number of contacts shown in the contacts picker. Measured - once when the Contacts Picker dialog is dismissed. - - - - - finnur@chromium.org - twellington@chromium.org - - Records which action the user takes in the ContactsPickerDialog. Measured - once when the Contacts Picker dialog is dismissed. - - - - - finnur@chromium.org - twellington@chromium.org - - The contact properties requested by the website (names, emails, telephone - numbers). Measured once when the Contacts Picker dialog is dismissed. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the total number of contacts selected in the contacts picker. - Measured once when the Contacts Picker dialog is dismissed. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the percentage of contacts selected in the contacts picker. - Measured once when the Contacts Picker dialog is dismissed. - - - - - - Removed 12/2018. CustomFeedback never shipped to 100% and is no longer - planned for launch. - - jwanda@chromium.org - - Recorded when the user selects a category button when in the Custom Feedback - UI. - - - - - - Removed 12/2018. CustomFeedback never shipped to 100% and is no longer - planned for launch. - - jwanda@chromium.org - - Recorded when a user selects an option related to their problem within the - Custom Feedback UI. - - - - - wylieb@chromium.org - twellington@chromium.org - chrome-android-app@chromium.org - - Records if Chrome altered a google homepage/search request to include the - dark theme. Recorded only when navigating to google or google search. - Histogram total count will be the total number of requests to the google - hompage or google search. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Records the reason why dark theme is enabled when dark theme is visible to - user. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Records whether dark theme is enabled or not on cold start and when the - enabled state changes. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Records user theme preference of system default, light or dark theme on cold - start and when the theme preference changes. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - Records the current default browser state when the primer dialog prompting - users to change their default browser is shown. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - Records the current default browser state if the activity receives an intent - through the disambiguation sheet that is displayed in response to the - default browser promo. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - The final default browser state (outcome) after the user has been prompted - to set Chrome as the default when no browser is set as the default - initially. Recorded when the system UI prompting the user to change their - default is dismissed. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - The final default browser state (outcome) after the user has been prompted - to set Chrome as the default when another browser is set as the default - initially. Recorded when the system UI prompting the user to change their - default is dismissed. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - Records the default browser state when the Android Q+ role manager dialog is - shown. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - Records which button click led to the default browser promo dialog being - dismissed for dialogs shown when there is currently no default browser set. - - - - - lazzzis@google.com - twellington@chromium.org - pavely@chromium.org - - Records which button click led to the default browser promo dialog being - dismissed for dialogs shown when another browser is set as the default. - - - - - twellington@chromium.org - tedchoc@chromium.org - chrome-android-app@chromium.org - - Records the largest display dimension in dp during deferred startup. The - display size is not affected by Android N multi-window mode. Clamped at - 200dp to 1200dp. - - - - - twellington@chromium.org - tedchoc@chromium.org - chrome-android-app@chromium.org - - Records the smallest display dimension in dp during deferred startup. The - display size is not affected by Android N multi-window mode. Clamped at 0 to - 1000dp. - - - - - szermatt@chromium.org - autofill_assistant@google.com - - Counts calls to Activity.onPerformDirectAction made by the system on behalf - of the assist app and which action was performed, if any. Available starting - with Android Q. - - - - - shaktisahu@chromium.org - - Records the state of the download infobar when the user taps on the - infobar's close button. - - - - - shaktisahu@chromium.org - - Records various types of messages representing the state of the downloads as - they are shown on the download infobar. - - - - - hesen@chromium.org - clank-downloads@google.com - - Records various actions taken by the user on the rename dialog in download - home. - - - - - hesen@chromium.org - clank-downloads@google.com - - Records various error codes when users try to rename a download in a - download home, recorded when backend rename callback is compeleted. - - - - - shaktisahu@chromium.org - clank-downloads@google.com - Recorded when a download is cancelled from Java. - - - - - Removed Jan 2020. - - shaktisahu@chromium.org - clank-downloads@google.com - - Records the number of chips being shown on download home. Recorded during - initialization and also during any list change. - - - - - dtrainor@chromium.org - clank-downloads@google.com - - Recorded when the user selects a filter from the Chrome download manager - navigation drawer. - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records instances where the foreground undergoes a lifecycle change (when - the foreground starts, changes pinned notification, or stops). - - - - - dtrainor@chromium.org - clank-downloads@google.com - - The number of non-incognito download items displayed when the download UI is - initialized. - - - - - dtrainor@chromium.org - clank-downloads@google.com - - The number of non-incognito download items displayed that are already viewed - by the user at any time, recorded when the download UI is initialized. - - - - - dtrainor@chromium.org - clank-downloads@google.com - Recorded when a download fails to open. - - - - dtrainor@chromium.org - clank-downloads@google.com - Recorded when a download is opened. - - - - - Removed October 2019. The feature was dropped during implementation review. - - dtrainor@chromium.org - shaktisahu@chromium.org - clank-downloads@google.com - Recorded when a menu action is taken on the images section. - - - - dtrainor@chromium.org - clank-downloads@google.com - The count of Download Home list entry actions taken. - - - - dtrainor@chromium.org - clank-downloads@google.com - The count of Download Home top level menu actions taken. - - - - dtrainor@chromium.org - clank-downloads@google.com - - The number of items selected when performing a multi-delete action. - - - - - dtrainor@chromium.org - clank-downloads@google.com - - The number of items selected when performing a multi-share action. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records instances where a user interacts with a download notification (ie. - clicks on, pauses, resumes, cancels). - - - - - - Removed July 2019. The relaunch rarely happens. - - xingliu@chromium.org - clank-downloads@google.com - - Records instances when a notification is being launched for the first time - or relaunched due to the need to dissociate the notification from the - foreground (only on API less than 24). - - - - - - Removed July 2019. - - xingliu@chromium.org - clank-downloads@google.com - - Records the number of notifications that are already existing (presumably - displayed) when a new notification is being launched to help understand the - frequency of multiple downloads with downloads as a foreground service - disabled. - - - - - - Removed July 2019. - - xingliu@chromium.org - clank-downloads@google.com - - Records the number of notifications that are already existing (presumably - displayed) when a new notification is being launched to help understand the - frequency of multiple downloads with downloads as a foreground service - enabled. - - - - - xingliu@chromium.org - clank-downloads@google.com - Records how users open audio download files on Android. - - - - xingliu@chromium.org - clank-downloads@google.com - - Records the entry point for users opening downloaded files on Android, that - are not audio nor video. - - - - - xingliu@chromium.org - clank-downloads@google.com - Records how users open video download files on Android. - - - - - Deprecated Jan 2020. - - twellington@chromium.org - clank-downloads@google.com - - The extension type for non-incognito download items that match the - "other" filter type. Recorded when the download UI is initialized. - - - - - - Deprecated Jan 2020. - - twellington@chromium.org - clank-downloads@google.com - - The extension type for downloads that match the "other" filter - type. Recorded when a download fails to open. - - - - - - Deprecated Jan 2020. - - twellington@chromium.org - clank-downloads@google.com - - The extension type for downloads that match the "other" filter - type. Recorded when a download is opened. - - - - - - Deprecated Jan 2020. - - twellington@chromium.org - clank-downloads@google.com - - The extension type for downloads that match the "other" filter - type. Recorded when downloads are shared through the download manager. - - - - - xingliu@chromium.org - clank-downloads@google.com - - - - Records instances of DownloadForegroundService stops. The number of expected - stops (stopped) and unexpected stops (task removed, low memory, etc) can be - compared to get a sense of how often the service crashes to see how it - handles restarts. For example, the number of times the service is stopped - because of low memory can be compared to the number of times the service has - been destroyed to see how frequently it occurs. Or, the number of start - sticky's will indicate how often the service is able to restart due to an - unexpected stop. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records instances of DownloadNotificationService stops. The number of - expected stops (stopped) and unexpected stops (task removed, low memory, - etc) can be compared to get a sense of how often the service crashes to see - how it handles restarts. For example, the number of times the service is - stopped because of low memory can be compared to the number of times the - service has been destroyed to see how frequently it occurs. Or, the number - of start sticky's will indicate how often the service is able to restart due - to an unexpected stop. - - - - - twellington@chromium.org - ianwen@chromium.org - clank-downloads@google.com - The number of downloads shared at the same time. - - - - twellington@chromium.org - ianwen@chromium.org - clank-downloads@google.com - - Recorded when downloads are shared through the download manager. A recorded - value of "All" indicates that multiple types of downloads were - shared. - - - - - - Removed 06/2016 with code removal of download home V1 to follow. - - shaktisahu@chromium.org - clank-downloads@google.com - - Recorded when the user clicks the info button on download home to toggle the - storage info. The state recorded is after the visibility is toggled. - - - - - twellington@chromium.org - ianwen@chromium.org - clank-downloads@google.com - The percentage of total storage downloads consume. - - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Records the required stretch of the smaller dimension before displaying an - image on download home. Measured in percentage. - - - - - - Removed on Jan 2020. - - xingliu@chromium.org - clank-downloads@google.com - - The duration between when an audio file is downloaded and when the file is - opened, only recorded when the user opens the file in download home UI. - - - - - - Removed on Jan 2020. - - xingliu@chromium.org - clank-downloads@google.com - - The duration between when a video file is downloaded and when the file is - opened, only recorded when the user opens the file in download home UI. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records the entry point for users opening the download page on Android. - - - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Availability status for each dynamic feature module. Reported once per - Chrome start. This metric's purpose is to measure a feature module's install - penetration over time. - - - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Duration of successful installs for each dynamic feature module. Only - contains install durations for modules first requested *before* Chrome - started last and may therefore be installed from cache. Omits deep sleep - time. - - - - - - Removed 2019-09 in favour of - Android.FeatureModules.CachedAwakeInstallDuration. - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Duration of successful installs for each dynamic feature module. Only - contains install durations for modules first requested *before* Chrome - started last and may therefore be installed from cache. - - - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Install status counter for each dynamic feature module. Recorded during - on-demand and deferred installs. - - - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Install status for each dynamic feature module. Recorded after the - installation has finished. - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Length of time during startup used by module framework code. This is our - metric to improve and used to guard against regressions. - - - - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Duration of successful installs for each dynamic feature module. Only - contains install durations of modules first requested *after* Chrome started - last and are therefore unlikely to be installed from cache. Omits deep sleep - time. - - - - - - Removed 2019-09 in favour of - Android.FeatureModules.UncachedAwakeInstallDuration. - - - - agrieve@chromium.org - fredmello@chromium.org - tiborg@chromium.org - wnwen@chromium.org - - Duration of successful installs for each dynamic feature module. Only - contains install durations of modules first requested *after* Chrome started - last and are therefore unlikely to be installed from cache. - - - - - drott@chromium.org - layout-dev@chromium.org - - Records the latency of looking up a local font from Android downloadable - fonts at the time of instantiating the font in the fonts backend in the - renderer. Includes time for error checking and attempting to create the font - from the retrieved blob, if there is one. Only records timings for - situations in which a font could not be instantiated. - - - - - drott@chromium.org - layout-dev@chromium.org - - Records the latency of looking up a local font from Android downloadable - fonts at the time of instantiating the font in the fonts backend in the - renderer. Includes time for error checking and attempting to create the font - from the retrieved blob, if there is one. Only records timings for - situations in which a font was successfully instantiated and returned. - - - - - chouinard@chromium.org - twellington@chromium.org - - Records the result of font fetch requests made to the GMS Core Android - downloadable font provider. The result may be success, or failure with a - reason. In the case of multiple failures, only the first one encountered is - reported. See implementation at AndroidFontLookupImpl. - - - - - chouinard@chromium.org - twellington@chromium.org - - Records the time taken to make a fetchFonts font request to GMS Core via the - Android downloadable font provider API. This metric may be used to determine - whether it's reasonable to execute this task on the IO thread rather than - posting to a background thread. - - - - - chouinard@chromium.org - twellington@chromium.org - - Records the time taken to respond to a request from the renderer to fetch a - specific font file from the GMS Core Android downloadable font provider. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - - The number of selected items the user opened in new tabs from the native - Android history page. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - - The number of selected items the user removed from the native Android - history page. - - - - - - Not being recorded as of 2017. - - mariakhomenko@chromium.org - - Measures the amount of time spent in the getInstantAppIntent() API call. - - - - - sbirch@google.com - - Measures the amount of time spent in the getInstantAppIntent() API call when - the API was able to find an Instant App for the URL. This is recorded for - external intents coming into Chrome only and measures the delay before we - dispatch the intent to Instant Apps. - - - - - sbirch@google.com - tedchoc@chromium.org - - Measures the amount of time spent in the getInstantAppIntent() API call when - the API was not able to find an Instant App for the URL. This is recorded - for external intents coming into Chrome that get checked for their Instant - Apps eligibility, but end up being loaded in Chrome. It's critical to keep - this latency low for our startup performance. - - - - - sbirch@google.com - tedchoc@chromium.org - - For intents to load a web page in browser from Instant Apps, records where - the request to load came from. - - - - - sbirch@google.com - - Records events that occur when a user clicks on an intent:// URL that is - dispatched to instant apps. The intent:// URLs to the Instant Apps are - explicitly disabled unless they are launched from Google SERP, but we record - other attempts as well. - - - - - sbirch@google.com - tedchoc@chromium.org - - Records whether any given successful page load (for http and https schemes - only) could have been handled by an Instant App. - - - - - sbirch@google.com - tedchoc@chromium.org - - Measures the time from when we first received an eligible intent for Instant - Apps to the time we processed it in the case where the Instant Apps activity - had to invoke a fallback intent. This happens only on Android N and older. - - - - - sbirch@google.com - - Measures the amount of time spent triaging an incoming event to decide - whether it needs to be routed to Instant Apps. This is time from - ChromeLauncherActivity.onCreate() call to the time either startActivity() is - called or the request proceeds. This is a superset of - Android.InstantApps.ApiCallDurationWith[out]App. - - - - - sbirch@google.com - tedchoc@chromium.org - - Logs the reasons the banner is shown or hidden on an instant apps eligible - pages. Triggered every time asynchronous Instant Apps API indicates the - currently loaded page is instant apps eligible. Does not include Instant - Apps eligible pages loaded directly through the omnibox. - - - - - tedchoc@chromium.org - thildebr@chromium.org - - When an external application was launched as a result of a form submit, this - tracks whether there was a user gesture associated with the submit. - - - - - mthiesse@chromium.org - yfriedman@chromium.org - - When a site navigates to a URL that can be parsed as an Intent, record the - action of that Intent. - - - - - - Removed in M86. No longer tracked. - - peconn@chromium.org - - Records the usage of the Browser.EXTRA_HEADERS field for Intents that Chrome - receives, breaking down by type of header and by whether the launching app - was first or third party. - - - - - - Removed in M86. No longer tracked. - - jochen@chromium.org - peconn@chromium.org - - Records hashes of header names used in the Browser.EXTRA_HEADERS fields for - Intents that Chrome receives that aren't on the CORS header safelist. This - can be used to match against known types of headers to measure their - frequencies. - - - - - tedchoc@chromium.org - clank-team@google.com - - Signifies whether the last shared app information is retrieved successfully - or not. This is logged when configuring the direct sharing menu item. - - - - - rsesek@chromium.org - - Reports the kernel major and minor version from the utsname.release field. - The low 16 bits of each version are combined into a 32-bit integer. The - range is from [0x00020006,0x0004000a] to track kernel versions 2.6 through - 4.10. - - - - - perrier@chromium.org - megjablon@chromium.org - chrome-language@google.com - - Reports whether the Chrome UI language is the same as the Android system - lanaguage. Recorded once per top-level ChromeActivty start. - - - - - tiborg@chromium.org - heamy@chromium.org - chrome-language@google.com - - Reports whether Chrome was started in a language other than the system - language but we support the system language. That can happen if the user - changes the system language and the required language split cannot be - installed in time. - - - - - wnwen@chromium.org - - Whether VIEW intent sent explicitly to .Main activity was dispatched by - onCreate(). - - - - - wnwen@chromium.org - - Whether VIEW intent sent explicitly to .Main activity was dispatched by - onNewIntent(). - - - - - wnwen@chromium.org - - Sources (ExternalAppId) of undispatched VIEW intents sent explicitly to - .Main activity alias. - - - - - dmurph@chromium.org - - Recorded when the user presses a button in the 'Manage Space' screen for - Chrome. Note: the 'Clear App Data' option is likely incorrect, as the result - of that button disables UMA recording (as we factory reset the app). - - - - - dmurph@chromium.org - - Records the time it takes to delete all unimportant sites when the user - initiates the 'Clear Unimportant Sites' action in the 'Manage Space' screen - for Chrome. - - - - - dmurph@chromium.org - - Recorded when the user opens the 'Manage Space' screen for Chrome, after the - disk usage is calculated. The disk usage value represents the accumulated - disk usage by websites. - - - - - dmurph@chromium.org - - Recorded when the user opens the 'Manage Space' screen for Chrome, after the - disk usage is calculated. The disk usage value represents the accumulated - disk usage by websites that are not considered 'important'. - - - - - ssid@chromium.org - - The duration of each failed ActivityManager.getMyMemoryState() call made by - MemoryPressureMonitor. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ssid@chromium.org - - The duration of each successful ActivityManager.getMyMemoryState() call made - by MemoryPressureMonitor. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ssid@chromium.org - - Memory pressure notifications sent by Android through ComponentCallbacks2. - This metric was added 04/2018; for prior data for the browser process see - MemoryAndroid.NotificationBackground and - MemoryAndroid.NotificationForeground. - - - - - pavely@chromium.org - chrome-android-app@chromium.org - - Records the action taken on a security sensitive touch event in modal - dialog. As of M84 it is used for site premission dialogs. - - - - - tedchoc@chromium.org - clank-team@google.com - - The number of moderate bindings which were kept while Chrome process is in - the foreground. This is logged right before Chrome process goes into the - background. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Renaming the old tab metadata file failed during multi-instance migration. - Only true is recorded. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - The new tab metadata file already existed when multi-instance migration was - attempted. Only true is recorded. - - - - - - - twellington@chromium.org - tedchoc@chromium.org - chrome-android-app@chromium.org - - Records on every metrics upload whether the activity is running in Android N - multi-window mode or not. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Records whether the screen width is below 600dp when the activity is in - Android N multi-window mode. True if the screen width is less than 600dp and - false if is greater than or equal to 600dp. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Records the screen height in dp when the activity is in Android N - multi-window mode. Clamped at 200dp to 1200dp. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Records the screen width in dp when the activity is in Android N - multi-window mode. Clamped at 200dp to 1200dp. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Records the screen width in dp when the activity is in Android N - multi-window mode and the width is below 600dp. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - yfriedman@chromium.org - - Records that a specific background task has finished cleanly (i.e. no - unexpected exits because of chrome crash or OOM). This includes tasks that - have been stopped due to timeout. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific native background task started in Full Browser Mode - has finished cleanly. See Android.NativeBackgroundTask.TaskFinished for more - details. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific native background task started in Reduced Mode has - finished cleanly. It is possible that Full Browser has launched while the - task was running. See Android.NativeBackgroundTask.TaskFinished for more - details. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - yfriedman@chromium.org - - Records that a specific native background task has been started. This does - not consider tasks that are marked as DONE or RESCHEDULED before a call to - start native is made (regardless of whether native is already loaded). - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific native background task has been started in Full - Browser Mode. See Android.NativeBackgroundTask.TaskStarted for more details. - - - - - mheikal@chromium.org - hanxi@chromium.org - hnakashima@chromium.org - - Records that a specific native background task has been started in Reduced - Mode. See Android.NativeBackgroundTask.TaskStarted for more details. - - - - - - Removed in July 2019. See https://crbug.com/975556. - - michaelbai@chromium.org - - The return value of NativeLibraryPreloader.loadLibrary() in browser process, - is recorded once per browser process start. - - - - - - Removed in July 2019. See https://crbug.com/975556. - - michaelbai@chromium.org - - The return value of NativeLibraryPreloader.loadLibrary() in renderer - process, is recorded once per renderer process start. - - - - - mheikal@chromium.org - hnakashima@chromium.org - hanxi@chromium.org - - The number of times full-browser mode is requested to be loaded from native - code (running in reduced mode). - - - - - finkm@chromium.org - - Counts impressions of the NTP on Android. It also counts potential - impressions. A potential impression is a place where it would make sense to - open the NTP instead of the current view. E.g. the no-tab view is counted as - a potential impression since this view could be replaced with the NTP. For - better comparison regular impressions are also counted. The no-tab view - counting happens right after the user closed the last tab and the regular - impression counting happens at construction time of the NTP (=whenever a new - tab is opened). - - - - - chili@chromium.org - - State of a download or offline page request at user-initiated cancel. - - - - - ender@chromium.org - tedchoc@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Recorded every time AutocompleteController.java interacts with - autocomplete_controller_android.cc via an index reference to an item. - Indicates how often the match referenced by Java is different from the match - referenced by C++ at that position. - - - - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records time spent on positioning all suggestions on screen. This histogram - is recorded every time a new suggestion list is received. - - Values recorded here should generally aim to be small, likely below 2ms - range. Higher values are an indicator of a performance problem. - - Layout operation should take place just once when suggestion view is shown - for the first time. - - This metric is reported for all users and uses 100microsecond granularity. - - When comparing Durations measured here, also compare Total Counts for a - correct indication of how frequently views are laid out and how the overall - time spent performing layout operation changed. - - This histogram is related to Android.Omnibox.SuggestionView.Reused, - Android.Omnibox.SuggestionList.MeasureTime, - Android.Omnibox.SuggestionView.CreateTime. - - - - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records time spent on measuring all suggestions ahead of positioning them on - screen. This histogram is recorded every time a new suggestion list is - received. - - Values recorded here should generally aim to be small, likely below 2ms - range. Higher values are an indicator of a performance problem. - - Measure operation should take place just once when suggestion view is shown - for the first time. - - This metric is reported for all users and uses 100microsecond granularity. - - When comparing Durations measured here, also compare Total Counts for a - correct indication of how frequently views are measured and how the overall - time spent measuring views changed. - - This histogram is related to Android.Omnibox.SuggestionView.Reused, - Android.Omnibox.SuggestionList.LayoutTime, - Android.Omnibox.SuggestionView.CreateTime. - - - - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records time spent creating a single suggestion. - - Values recorded here should generally aim to be small, below 1ms range. - Higher values may be an indicator of a performance problem. - - This metric is reported for all users and uses 100microsecond granularity. - - When comparing Durations measured here, also compare Total Counts for a - correct indication of how frequently views are created and how the overall - time spent creating views changed. - - This histogram is related to Android.Omnibox.SuggestionList.LayoutTime, - Android.Omnibox.SuggestionList.MeasureTime, - Android.Omnibox.SuggestionView.Reused. - - - - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records number of times a suggestion was successfully reused. - - Values recorded here tell how efficiently View reuse algorithms operate and - how frequently these algorithms have managed to prevent unnecessary view - creation. Higher Reuse counts indicate better performance. - - When analysing this metric, consider checking also the Total Counts of - Android.Omnibox.SuggestionView.CreateTime metric for a better information - regarding how view creations and re-uses have changed: - - * If this metric increased while the Total Count of the CreateTime - decreased, the change has positive effect. - - * If this metric increased (or decreased) and there is a similar change in - Total Counts of CreateTime, then the effect is neutral. - - * If this metric decreased, while the Total Count increased, then the change - has a negative effect (fewer reuses, more time spent creating views) - - This histogram is related to Android.Omnibox.SuggestionList.LayoutTime, - Android.Omnibox.SuggestionList.MeasureTime, - Android.Omnibox.SuggestionView.CreateTime. - - - - - mdjones@chromium.org - twellington@chromium.org - amaralp@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - Records how the omnibox was focused. - - - - nyquist@chromium.org - yfriedman@chromium.org - - Records the size of the user's cache at startup on Android O and above. - - - - - nyquist@chromium.org - yfriedman@chromium.org - - At startup, records the space on disk taken by Chrome application including - APK resources, compiled libraries, and extracted native code. Only recorded - for Android O and above. - - - - - nyquist@chromium.org - yfriedman@chromium.org - - Records the size of the user's data directory at startup on Android O and - above. Does not include cache size. - - - - - - Removed from the code in July 2019. See https://crbug.com/975701. - - jeffreycohen@chromium.org - ewald@chromium.org - - At startup, records whether the Chrome application has been granted the read - storage permission on Android. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time the BitmapScaler spent scaling a bitmap. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the total number of images served from the high-res cache during - the lifetime of the dialog. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the total number of images sent for decoding during the lifetime of - the dialog. - - - - - finnur@chromium.org - twellington@chromium.org - - The percentage of out-of-memory decoding failures, per batch of photos (not - videos) decoded. Intended to help identify if there are devices where - decoding fails 100% of the time. Be wary at looking at other numbers in the - histogram, as a value emitted at, say, 50% may represent one failure in a - two-item decoding or 50 failures in a hundred-item decoding. These are - qualitatively different experiences for a user. - - - - - finnur@chromium.org - twellington@chromium.org - - The percentage of file error decoding failures, per batch of videos (not - photos) decoded. Intended to help identify if there are devices where - decoding fails 100% of the time. Be wary at looking at other numbers in the - histogram, as a value emitted at, say, 50% may represent one failure in a - two-item decoding or 50 failures in a hundred-item decoding. These are - qualitatively different experiences for a user. - - - - - finnur@chromium.org - twellington@chromium.org - - The percentage of IO error decoding failures, per batch of videos (not - photos) decoded. Intended to help identify if there are devices where - decoding fails 100% of the time. Be wary at looking at other numbers in the - histogram, as a value emitted at, say, 50% may represent one failure in a - two-item decoding or 50 failures in a hundred-item decoding. These are - qualitatively different experiences for a user. - - - - - finnur@chromium.org - twellington@chromium.org - - The percentage of runtime error decoding failures, per batch of videos (not - photos) decoded. Intended to help identify if there are devices where - decoding fails 100% of the time. Be wary at looking at other numbers in the - histogram, as a value emitted at, say, 50% may represent one failure in a - two-item decoding or 50 failures in a hundred-item decoding. These are - qualitatively different experiences for a user. - - - - - finnur@chromium.org - twellington@chromium.org - - The percentage of unknown decoding error failures, per batch of videos (not - photos) decoded. Intended to help identify if there are devices where - decoding fails 100% of the time. Be wary at looking at other numbers in the - histogram, as a value emitted at, say, 50% may represent one failure in a - two-item decoding or 50 failures in a hundred-item decoding. These are - qualitatively different experiences for a user. - - - - - finnur@chromium.org - twellington@chromium.org - - Records which action the user takes in the PhotoPickerDialog. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the total number of files returned from the enumeration operation. - Measured once at the end of the enumeration operation. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the enumeration rate (files per tenths of a second). Measured once - at the end of the enumeration operation. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time the BitmapScaler spent enumerating files on - disk. Measured once at the end of the enumeration operation. - - - - - finnur@chromium.org - twellington@chromium.org - - Records whether the EXIF orientation directive is present and what it is set - to. Collected once per decoded image, but only on Android N and above (and - when no IO error occurs). - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the byte count of a decoded image. Only recorded on successful - decodes. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes the decoder to decode one image. Only - recorded on successful decodes. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes to process one image decode request - (not video) end to end (RPC and actual decoding of the bits by utility - process). Recorded whether or not the RPC/decode request was successful. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes to decode all the frames needed to show - the animation -- end to end (RPC and actual decoding of the bits by utility - process). Recorded whether or not the RPC/decode request was successful. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes to process one video frame request end - to end (RPC and actual decoding of the bits by utility process). Recorded - whether or not the RPC/decode request was successful. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes to upscale a bitmap from the low-res - cache. Recorded only when there a cache miss from the high-res bitmap but a - cache hit from the low-res (placeholder) bitmap. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the byte count of the first video thumbnail. Only recorded on - successful decodes. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes the decoder to decode all the frames - needed to display an animated thumbnail. Only recorded on successful - decodes. - - - - - finnur@chromium.org - twellington@chromium.org - - Measures the amount of time it takes the decoder to decode the first frame - of a video. Only recorded on successful decodes. - - - - - twellington@chromium.org - tedchoc@chromium.org - - Whether Google Play Services is installed on the device. Recorded during - deferred startup. - - - - - twellington@chromium.org - tedchoc@chromium.org - - The version code for Google Play Services if it is installed on the device, - or 0 if it is not. Recorded during deferred startup. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Measures the amount of time spent querying for whether a WebAPK is already - installed. - - - - - - Removed in July, 2020 - - twellington@chromium.org - chrome-android-app@chromium.org - - Records the number of other devices listed in recent tabs page when recent - tabs page is loaded. - - - - - - Removed in July, 2020 - - twellington@chromium.org - chrome-android-app@chromium.org - - Records the number of recently-closed tabs shown in recent tabs page when - recent tabs page is loaded. - - - - - - Removed in July, 2020 - - twellington@chromium.org - chrome-android-app@chromium.org - - Records the total number of tabs listed in recent tabs page (sum of all tab - from other devices plus recently-closed tabs) when recent tabs page is - loaded. - - - - - aberent@chromium.org - - Whether Chrome tried to restore its settings from a previous device or - installation, and what happened when it did. Only recorded on first run. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The type of the search engine chosen by the user in Search Engine Choice - flow. - - - - - wylieb@chromium.org - fgorski@chromium.org - - Counts occurences of various events related to Search Engine Choice feature. - - - - - wylieb@chromium.org - pavely@chromium.org - fgorski@chromium.org - - Counts occurences of various events related to Search Engine Choice V2 - feature. - - - - - wylieb@chromium.org - fgorski@chromium.org - - The type of the search engine used before Search Engine Choice flow was - presented. - - - - - peter@chromium.org - rsesek@chromium.org - - Reports the status of the seccomp-bpf sandbox in photo picker decoding - processes. Anything other than "Sandbox Engaged" indicates the - sandbox is not turned on. See https://crbug.com/477049. - - - - - - Removed from the code in July 2019. See https://crbug.com/975749. - - rsesek@chromium.org - - Reports the level of kernel support for the seccomp-bpf sandbox using - prctl(PR_SET_SECCOMP). - - - - - rsesek@chromium.org - - Reports the status of the seccomp-bpf sandbox in renderer processes. - Anything other than "Sandbox Engaged" indicates the sandbox is not - turned on. See https://crbug.com/477049. - - - - - rsesek@chromium.org - - Reports the level of kernel support for the seccomp-bpf sandbox using the - seccomp system call. - - - - - finnur@chromium.org - peter@chromium.org - - Records the number of images selected in either the new Photo Picker or the - standard Android file picker. Note: Only recorded in situations determined - to warrant the new Photo Picker (not, for example, if mixed content, like - images and text files, was requested). - - - - - peter@chromium.org - finnur@chromium.org - - Records the scope of accepted content for a select file dialog when shown by - a Web developer. - - - - - - Removed from code June 2019. See https://crbug.com/577190 for context. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from checking for - whether play services is available. - - - - - - Removed July 2019 (http://crbug.com/984291). - - estevenson@chromium.org - wnwen@chromium.org - - Measures the amount of time due to a StrictMode violation from checking for - whether a package is Google signed. - - - - - - Removed 05/2016 in Issue 582539 with the removal of document mode. - - hartmanng@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from fetching the - DocumentMode shared preferences file. - - - - - - Removed 05/2016 in Issue 582539 with the removal of document mode. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from document mode - loading its prioritized tab's state. - - - - - - Removed from code June 2019. See https://crbug.com/508615 for context. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from fetching and - possibly creating the downloads directory. - - - - - - Removed from code June 2019. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from custom - notification builder through date formatting. - - - - - yfriedman@chromium.org - wnwen@chromium.org - - Measures the amount of time due to a StrictMode violation from calling out - to Android activity manager. - - - - - - Removed from code June 2019. - - wnwen@chromium.org - - Measures the amount of time due to a StrictMode violation from snippet UI - through date formatting. - - - - - wnwen@chromium.org - yfriedman@chromium.org - - Measures time spent during StrictMode-whitelisted code in - TabPersistentStore. - - - - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from fetching for - the thumbnail cache directory. - - - - - - Removed from code June 2019. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from looking up a - webapp's MAC on startup. - - - - - - Removed from code June 2019. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from fetching for - creating the webapp directory. - - - - - - Removed from code June 2019. - - wnwen@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from reading and - saving webapp state. - - - - - - Removed from code July 2019. - - hartmanng@chromium.org - yfriedman@chromium.org - - Measures the amount of time due to a StrictMode violation from fetching the - Webapp shared preferences file. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Recorded when a survey download is requested. If the client already has - successfully downloaded a survey, 'not requested' is recorded. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - The response code of the completed survey download request. - - - - twellington@chromium.org - chrome-android-app@chromium.org - - If the infobar was visible when it was closed and if it was closed directly - or not. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Whether or not the survey was successfully shown after its download. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - The result of the survey filtering process. Each enum represents a different - filter that caught the user. This is recorded on cold starts when we check - if a user qualifies for a survey. - - - - - ssid@chromium.org - - Measures whether Chrome low-end detection logic based on RAM size matches - the Android system utility value for isLowRamDevice(). This is recorded once - per browser start and may be recorded in the renderer if isLowEndDevice() - bit is checked. - - - - - - Removed 2020-04. - - tedchoc@chromium.org - - The distribution of results when running ExternalNavigationHandler, this - shows how often we send intents to be handled by other applications. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - - The number of bytes read for the other tab state's metadata file when - merging tab states in Android N+. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - - The number of normal and incognito tabs merged (for Android N+ - multi-instance). This will be logged for both cold-start and non-cold-start - merging assuming that the native library is loaded. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - - Measures the amount of time it takes to restore state for each merged tab - (for Android N+ multi-instance). This will only be logged for non-cold-start - merging, because restoring merged tabs is not distingushed from restoring - regular tabs on cold start. - - - - - wnwen@chromium.org - twellington@chromium.org - The number of bytes written for the tab metadata file. - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Records the status of a thumbnail query from the thumbnail disk storage. - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Measures the size of the thumbnail disk storage used. Recorded during - initialization. - - - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Measures the size of the bitmap cache used. Recorded whenever a bitmap is - added to the cache. - - - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Records the status of a thumbnail query from the thumbnail provider - in-memory cache. - - - - - hazems@chromium.org - src/android_webview/OWNERS - - Track if looking up Android app resource id using - android.content.res.Resources#getIdentifier succeeds in - AndroidProtocolHandler or if it falls back to reflection look up. - - - - - laisminchillo@chromium.org - src/android_webview/OWNERS - - Records calls to WebView APIs from AndroidX. Some AndroidX-originating calls - will plumb through the framework, for example, if methods that are available - in the framework are called from the equivalent method in AndroidX. - - - - - michaelbai@chromium.org - boliu@chromium.org - - Records if WebView was attached to a Android window in 30s since WebView was - created. Nothing will be recorded if WebView has already been destroyed. - - - - - michaelbai@chromium.org - boliu@chromium.org - - Records if WebView was attached to a Android window in 3m since WebView was - created. Nothing will be recorded if WebView has already been destroyed. - - - - - michaelbai@chromium.org - boliu@chromium.org - - Records if WebView was attached to a Android window in 5s since WebView was - created. Nothing will be recorded if WebView has already been destroyed. - - - - - michaelbai@chromium.org - boliu@chromium.org - - Records how long it took for WebView to be attached to a Android window - since WebView was created. If WebView is never attached to a window, nothing - will be recorded. - - - - - timvolodine@chromium.org - ntfschr@chromium.org - Records the invocation count of WebView callbacks. - - - - laisminchillo@chromium.org - src/android_webview/OWNERS - Records ClearProxyOverride calls. - - - - chlily@chromium.org - torne@chromium.org - - The value of the cookie's SameSite attribute, if any. This is logged once - per creation of a cookie via the CookieManager API. These cookies are double - counted (once from CookieManager, logged in this histogram, and once from - CanonicalCookie::Create, logged in Cookie.SameSiteAttributeValue). - - - - - chlily@chromium.org - torne@chromium.org - - If a cookie was SameSite=None, this records whether or not it was Secure. - Logged once per attempt to set a SameSite=None cookie via CookieManager API. - These cookies are double counted (once from CookieManager, logged in this - histogram, and once from CookieMonster::SetCanonicalCookie, logged in - Cookie.SameSiteNoneIsSecure). - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the number of times the developer UI app was launched. This only - ever logs the value "true" because we only care about the total - count. This is logged in the developer UI app during Activity#onCreate. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the state of crash collection, as seen by the developer UI. This is - recorded when launching the crash UI, but only if the UI is not already - showing an error message for another problem (ex. WebView package error). - This only logs the first state we detect: ex. if the user has enabled crash - reporting by opting in and also with the flag UI, this only logs the flag UI - case. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the user's interaction with crashes in the developer UI's crash - list. Specifically, this tracks how the user interacts with the "hide - crash", "upload this crash report" or the "file bug - report" buttons and possible subsequent dialogs. Since the latter two - buttons are connected (the user must upload a crash before they can file a - bug report), we track interaction with both in the same histogram. This is - recorded for each button press in the crash list and is not recorded if the - user does not interact with any crashes. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the number of crashes shown in the developer UI. This is logged each - time the crash UI is launched and each time its list is refreshed. The UI - currently limits the number of crashes at 20, so clients logging the maximum - may have more logs sitting on disk. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the time spent blocking WebView startup to check for developer mode - (see "Android.WebView.DevUi.DeveloperModeEnabled"). This is - recorded once during WebView startup, regardless of whether developer mode - is enabled. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records whether or not WebView is starting up in "developer mode." - This is a mode where the user has enabled debugging features through the - WebView developer UI. This is recorded once during startup. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the time spent blocking WebView startup to load flags from the - developer UI. This is recorded only once during WebView startup, and only if - we've already detected developer mode is enabled (see - "Android.WebView.DevUi.DeveloperModeEnabled"). - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - This is recorded each time a user toggles a flag in the developer UI - (changing a flag's state), and logs whether the user found this flag with - the search bar ("true" means there was a non-empty search query). - This is only recorded when the user toggles an individual flag through the - Spinner dialog, not when they press the "reset all flags" button. - - - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the user's navigation to a Fragment. "FromIntent" tracks - navigations triggered by an Intent (ex. navigating to HomeFragment on - launch) and "NavBar" tracks user interaction with the bottom - navigation bar. "AnyMethod" should be the sum of the other two. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the user's selection in the developer UI overflow menu or action - bar, recorded after each selection. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records how the developer UI launcher icon for Monochrome was toggled: was - it enabled or disabled? This can be recorded either from WebView's - non-embedded processes or Chrome's browser process whenever either changes - the icon state (nothing is logged if we don't need to change the icon - state). This is only recorded in Monochrome (Android Nougat, Oreo, and Pie), - since this logic is only relevant in that case. - - - - - - Removed May 2020 because this only captures sessions up to 10 seconds long. - Use Android.WebView.DevUi.SessionDuration2 instead, which captures sessions - up to an hour. - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the time spent using a specific tool, from creation to destruction. - - - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the time spent using a specific tool, from creation to destruction. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the number of flags we will toggle for this run of WebView. This is - recorded only once during WebView startup, and only if we've already - detected developer mode is enabled (see - "Android.WebView.DevUi.DeveloperModeEnabled"). If developer mode - is disabled, we will not toggle any flags through this mechanism. - - - - - michaelbai@chromium.org - boliu@chromium.org - - Records if WebView was ever attached to a window when WebView is destroyed. - If WebView is killed by platform, nothing will be recorded. - - - - - - Replaced by Android.WebView.ExtraHeadersRedirect 2020-07 - - torne@chromium.org - src/android_webview/OWNERS - - Record when extra headers are added to requests by AwURLLoaderThrottle and - whether they were kept or removed during redirects. - - - - - torne@chromium.org - src/android_webview/OWNERS - - Recorded when an app passes extra headers to - WebView.loadUrl(url,extra_headers). We check if the header names and values - are valid. - - - - - torne@chromium.org - src/android_webview/OWNERS - - Records the redirect type each time that a request is redirected, if that - request contains extra headers added by the - WebView.loadUrl(url,extra_headers) API. - - - - - - Removed in M79. Obtained required data from M78. - - boliu@chromium.org - ericrk@chromium.org - - Record in a functor draw whether stencil test is enabled by Android HWUI. - This is recorded every frame. Note some OS versions never use stencil so - worth checking result split by OS version. - - - - - vasilyt@chromium.org - boliu@chromium.org - - Tracks invalidate and frame submission status for WebView hardware draw. - Result is enum that represent three flags: did we called invalidate this - frame, did renderer submitted compositor frame and whether DrawParams from - Android HWUI changed. This is logged once per WebView draw functor call. - - - - - ntfschr@chromium.org - torne@chromium.org - src/android_webview/OWNERS - - Records the scheme for the baseUrl parameter to loadDataWithBaseURL. This - also records if this value is "empty", as determined by - TextUtils.isEmpty(). - - - - - jamwalla@chromium.org - - Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/ - null, the same as the baseUrl parameter, or different from baseUrl. - - - - - - Removed 2019/10/11. This histogram was never well understood and the - underlying feature has been shipped for some time anyway. - - smcgruer@chromium.org - - Records if a data url passed to loadUrl had a '#' character. This is to be - used in the effort to deprecate the incorrect treatment of '#' characters in - data URIs; see http://crbug.com/823666#c30. - - - - - ntfschr@chromium.org - torne@chromium.org - src/android_webview/OWNERS - - Records the scheme for the URL loaded by a browser-initiated navigation. - Specifically, this is the scheme of the URL passed to loadUrl() (and its - overloads), postUrl(), and loadData (this is implicitly "data:"). - also records if this value is "empty", which means either null or - "about:blank". This intentionally excludes loadDataWithBaseURL(). - - - - - - Removed in April 2020. The backfill logic is deemed no longer necessary to - keep around. - - ntfschr@chromium.org - src/android_webview/OWNERS - - Records whether WebView needed to backfill the install date pref with - Android frameworks APIs. Recorded once during startup (metrics service - initializtion). - - - - - - Removed in April 2020. Network Service has launched, and we don't intend to - follow up on this metric. - - ntfschr@chromium.org - timvolodine@chromium.org - - Records information about the specified MIME types for app-provided content - loaded in Android WebView. At the moment, this focuses on - shouldInterceptRequest, ContentProvider-supplied content, and app - assets/resources (where we expect the app to use proper file extensions to - indicate MIME type), and is recorded as part of the process of loading each - resource. This may apply to any type of resource (frame HTML, subresource, - etc.). - - - - - hazems@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - Records the time interval between when a histogram is recorded in a - non-embedded WebView process and when it's actually sent to the UMA API in - an embedded WebView. This is recorded during WebView startup for each - histogram retrieved and replayed successfully from WebView non-embedded - metrics service. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records the number of histograms received from WebView's non-embedded - histogram service. This is recorded once during WebView startup, after - retrieving histograms from the service (if the proto can be parsed). - - - - - hazems@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - Records whether metrics parsing from file in non-embedded histogram service - was successful. It's recorded during service startup by adding it to records - list. It captures the most recent file parsing result for the last service - launch before the client connects to the service. - - - - - hazems@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - Recorded by the non-embedded histogram service if it's unable to return - histograms. This is always recorded when a client connects to retrieve - histograms. - - - - - ntfschr@chromium.org - hazems@chromium.org - src/android_webview/OWNERS - - Records whether metrics transmission from the non-embedded histogram service - was successful. This is recorded once during WebView startup, after - retrieving histograms from the service. - - - - - timvolodine@chromium.org - tobiasjs@chromium.org - ntfschr@chromium.org - - The WebViewClient error code as returned by the onReceivedError callback - This is recorded regardless of whether the network service is enabled or - disabled. - - - - - timvolodine@chromium.org - tobiasjs@chromium.org - ntfschr@chromium.org - - The WebViewClient http resonse status code as returned by the - onReceivedHttpError callback This is recorded regardless of whether the - network service is enabled or disabled. - - - - - - Removed 09/2020. These are no longer being tracked. - - laisminchillo@chromium.org - timvolodine@chromium.org - - The WebViewClient SSL error code as received by onReceivedSslError. - - - - - - Removed 04/2020. These metrics are tracked generally for SafeBrowsing, and - WebView no longer needs specializations. - - laisminchillo@chromium.org - timvolodine@chromium.org - - Records the WebViewClient safe browsing threat type as returned by - onSafeBrowsingHit callback. - - - - - rmcelrath@chromium.org - src/android_webview/OWNERS - - Records how long WebView blocks startup to load prefs from disk. This is - recorded once per browser process startup. - - - - - ntfschr@chromium.org - timvolodine@chromium.org - - Records the action WebView took (if any) to "fix up" secure - cookies for backwards compatibility. - - - - - laisminchillo@chromium.org - src/android_webview/OWNERS - - Records whether bypass rules were present in SetProxyOverride calls. - - - - - laisminchillo@chromium.org - src/android_webview/OWNERS - - Records the type of scheme filter in SetProxyOverride calls. - - - - - laisminchillo@chromium.org - src/android_webview/OWNERS - Records the type of url in SetProxyOverride calls. - - - - timvolodine@chromium.org - ntfschr@chromium.org - - Whether the request was intercepted by the embedder of Android WebView, and - if so which url scheme was used. Intercepted request are requests for which - the shouldInterceptRequest() callback returned a non-null response. - - - - - timvolodine@chromium.org - tobiasjs@chromium.org - ntfschr@chromium.org - - Records the custom response status code for the intercepted requests where - input stream is null. In case status code is invalid (or has not been - specified by the app) a zero status code is recorded. This UMA is needed in - order to track specific usages of request interception where the behavior - with network service enabled is different from the old code path (for more - details see go/wv-ns-behavior-differences). This data is recorded regardless - of whether the network service is enabled or disabled. - - - - - - Removed in M73. Bundles have shipped. - - tiborg@chromium.org - yfriedman@chromium.org - - Result of applying a workaround to fix a crash on Android O if the WebView - provider is a split APK (see crbug.com/889954 for more details). - - - - - changwan@chromium.org - src/android_webview/OWNERS - - How long it takes to initialize a WebViewChromiumFactoryProvider. This is - the first major phase of the WebViewChromium construction. - - - - - changwan@chromium.org - src/android_webview/OWNERS - - How long it takes to initialize a WebViewProvider, the first time that one - is initialized. WebViewProvider initialization is the second major phase of - WebViewChromium construction. The first initialization is recorded - separately because it is usually much slower than subsequent ones. - - - - - changwan@chromium.org - src/android_webview/OWNERS - - How long it takes to initialize a WebViewProvider, the first time that one - is initialized. WebViewProvider initialization is the second major phase of - WebViewChromium construction. When it is not the first time, it is faster - and thus recorded separately. - - - - - torne@chromium.org - src/android_webview/OWNERS - - How many attempts it took to acquire the WebView data directory lock. A - value of 0 indicates that we reached the max retry count and failed to - acquire the lock successfully at all. - - - - - torne@chromium.org - src/android_webview/OWNERS - - Records whether we already tried to initialize WebView in the current - process previously, upon entry to the initialization function. This should - never be true under normal circumstances and may indicate an application - catching an exception thrown by initialization and discarding it. - - - - - laisminchillo@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - Records whether the WebViewClient provided by the app is an instance of - WebViewClientCompat (and therefore exposes AndroidX callbacks). This is - recorded each time the app sets a new WebViewClient via - WebView#setWebViewClient(). - - - - - changwan@chromium.org - src/android_webview/OWNERS - - The version of the target SDK of the app WebView is running in. This is - recorded at WebView creation. - - - - - torne@chromium.org - src/android_webview/OWNERS - - Recorded when an app passes a custom user agent to - WebSettings.setUserAgentString. We check if the UA is valid, and if not we - try to interpret it in several ways and record which (if any) made sense. - - - - - - Removed from code July 2018. Variations in WebView has launched. - - changwan@chromium.org - - Indicates whether variations is enabled. We want to know how enabling - variations affects metrics, but we can't enable variations as a variations - study, since variations can't enable/disable itself. Instead, WebView - hard-codes a random variable for enabling variations, and reports the result - in this histogram. - - - - - idries@google.com - src/android_webview/OWNERS - - Records the global visibility state of WebView in seconds. The Visible - bucket counts total seconds that any WebView was visible (the view itself - was visible, and was attached to the view hierarchy of a visible window). - The NotVisble bucket counts time since WebView initialization for which no - WebView was considered visible, or no WebView existed. The total of these - two buckets reflects the amount of time covered by metrics collection. - - - - - idries@google.com - src/android_webview/OWNERS - - Records per-WebView visibility duration in seconds. The Visible bucket - counts the total time in seconds that each WebView was considered visible - (the view itself was visible, and was attached to the view hierarchy of a - visible window). If more than one WebView is considered visible, then each - WebView contributes independently. The NotVisible bucket counts the duration - that each WebView exists but not in a visible state. As with the Visible - bucket, each WebView contributes independently, and thus this bucket is not - incremented when no WebViews exist. - - - - - idries@google.com - src/android_webview/OWNERS - - Identical to Android.WebView.Visibility.Global except that the - OpenWebContentVisible bucket only records time that any WebView is visible - and displaying contents which originate from the 'Open Web' (in this context - that is taken to mean having an HTTP or HTTPS scheme). The - OpenWebContentNotVisible bucket records time when the WebView was not - visible or not displaying contents which originate from an HTTP or HTTPS - scheme. - - - - - idries@google.com - src/android_webview/OWNERS - - Identical to Android.WebView.Visibility.PerWebView except that the - OpenWebContentVisible bucket only records time that each WebView is visible - and displaying contents which originate from the 'Open Web' (in this context - that is taken to mean having an HTTP or HTTPS scheme). The - OpenWebContentNotVisible bucket records time when each WebView was not - visible or not displaying contents which originate from an HTTP or HTTPS - scheme. - - - - - wylieb@chromium.org - lzbylut@chromium.org - - Counts occurences of various events related to the Search Engine Logo - feature. When enabled, the feature will show the logo of the default search - engine in the omnibox. These events record the performance of fetching - non-Google logos. - - - - - azeemarshad@chromium.org - jonmann@chromium.org - better-together-dev@google.com - - Records effective final success/failure when trying to install Android - Messages for Web PWA. This is recorded once when any one of the installation - attempts succeed or when all attempts fails, irrespective of number of - retries. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Records message types for which all retry attempts failed when dispatching - to Android Messages for Web Service-Worker. This is recorded when using FCM - web push for background notificaitons. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Records message types for which a retry was attempted when dispatching to - Android Messages for Web Service-Worker. This is recorded when using FCM web - push for background notificaitons. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Records message types for which dispatching to Android Messages for Web - Service-Worker succeeded. This is recorded when using FCM web push for - background notificaitons. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Indicates the feature state of the Messages feature. This metric is emitted - to at the creation of the user session (when the user logs in), and when - feature state updates occur. - - - - - azeemarshad@chromium.org - jonmann@chromium.org - better-together-dev@google.com - - Records the number of installations attempted for Android Messages for Web - PWA before succeeding. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Records installation result code for every installation attempt for Android - Messages for Web PWA initiated through Multidevice setup or settings. This - metric also includes installation result for every failed retry. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Records success/failure for when Android Messages for Web PWA is - uninstalled. The PWA is uninstalled when the messages URL changes, resulting - in the PWA being uninstalled at the old URL and reinstalled at the new URL. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Tracks the duration of time for which the Android Messages for Web Service- - Worker is handling background connection. - - - - - azeemarshad@chromium.org - better-together-dev@google.com - - Tracks dispatch success/failure status of the start streaming message sent - to the Android Messages for Web Service-Worker. - - - - - - Removed as of 06/2020. Mostly tracked with Snackbar.Shown. - - dtrainor@chromium.org - - When a user closes a tab an undo toast will popup on certain devices giving - the user the chance to undo closing that tab. This stat tracks how the user - interacts with that UI and what actions they take. A cold start means that - the undo bar wasn't showing when it was triggered to show again. A warm - start means that it was. Warm starts can happen when the user closes - multiple tabs close together. When the undo bar is dismissed, all closes - that were queued up to be undone are committed. This can happen either by a - timeout or by an action by the user to move to another part of the UI. - - - - - khushalsagar@chromium.org - - If the frame rate for the image animation can not be reached, frames in the - animation are skipped to catch up to the desired frame. This metric tracks - the number of frames skipped during catch up, and can be used to assess the - smoothness of these animations. It records the number of frames skipped each - time the animation is ticked forward to draw the next frame. In the ideal - case, where the animation can be drawn at the desired rate, 0 frames should - be skipped. Note that skipping of frames can also be triggered if the - animation was intentionally paused (on becoming off-screen, or the tab being - hidden). - - - - - majidvp@chromium.org - animations-dev@chromium.org - - The time it takes the WorkletMutatorDispatcher to complete an asynchronous - mutation request of animation worklet. The measured time is the total - elapsed time from when a request is queued until the results are received. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - majidvp@chromium.org - animations-dev@chromium.org - - The time it takes the WorkletMutatorDispatcher to dispatch to and mutate all - animation worklet mutators synchronously. This includes the time that it - takes each AnimationWorkletGlobalScope to produce its output (which includes - V8 script execution) and also any queuing cost associated with posting - mutation tasks and receiving responses. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed as of 01/2019. Replaced with - Animation.AnimationWorklet.MutateDuration. - - majidvp@chromium.org - animations-dev@chromium.org - - The time it takes for AnimationWorkletGlobalScope to produce a mutation - update. This includes all V8 script execution cost. - - - - - majidvp@chromium.org - kevers@chromium.org - animations-dev@chromium.org - - The time it takes for an AnimationWorklet to produce a mutation update. This - includes all V8 script execution cost. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - mkwst@chromium.org - brandm@microsoft.com - - Records if various requests to access storage are allowed or not and if the - Storage Access API unblocked the request or not. Recorded whenever a - decision to access storage like getting/setting cookies or opening an - indexeddb connection is made in CookieSettings. - - - - - mkwst@chromium.org - brandm@microsoft.com - - Records if a generated grant was implicit or explicit at the time it was - created. - - - - - mkwst@chromium.org - brandm@microsoft.com - - Records requests to use document.requestStorageAccess and reasons the - request may be approved or rejected. - - - - - dominickn@chromium.org - pjmclachlan@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks - usage of the BeforeInstallPromptEvent, which allows developers to control - when an app banner appears. The events in this histogram are not mutually - exclusive - for example, preventDefault() must be called if prompt() is - called. - - - - - pjmclachlan@google.com - pcovell@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks the - different ways that an app banner left the screen, e.g. through an automatic - dismissal after navigation or an explicit user action. - - - - - pjmclachlan@google.com - pcovell@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks - when an app banner was requested and how the request was handled, e.g. the - user blocked its appearance or the banner was ultimately created. - - - - - dominickn@chromium.org - pjmclachlan@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks the - status code logged by the app banner system as it processes a site's - eligibility for an app banner. Every request for a banner will be logged in - a bucket of this histogram. - - - - - pjmclachlan@google.com - pcovell@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks - when a user triggers an install dialog for the app promoted by the banner, - as well as whether or not the user ultimately decided to install the app. - - - - - dominickn@chromium.org - pjmclachlan@google.com - - App banners promote an application related to the current website, and are - requested specifically through the current page's HTML. This stat tracks the - number of minutes between the first recorded visit to an origin and the time - when the banner is actually shown. - - - - - dominickn@chromium.org - pjmclachlan@google.com - - This stat tracks the user reponse when the add-to-homescreen dialog is shown - either: (A) Via the website's JavaScript (B) Via the user tapping the app - banner which promotes the application related to the current site. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - AppCache check response result code. - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - Time elapsed between a completion task being queued and run. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - The amount of time taken to run a completion task on the IO thread. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - Tracks the number of times corruption is detected in the sql database. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - AppCache initialization result code. - - - - - Removed 2018-03-20. No longer tracked. - - mek@chromium.org - - How long URLRequests to be retrieved from the appcache are delayed. - - - - - - Removed 2018-03-20. No longer tracked. - - mek@chromium.org - - How long URLRequests that result in a synthesized error are delayed. - - - - - - Removed 2018-03-20. No longer tracked. - - mek@chromium.org - - How long URLRequests to be retrieved over the network are delayed. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - Counts the number of appcached page loads for secure vs insecure origins. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - Tracks the success rate of retrieving a main resource from the appcache. - - - - - pwnall@chromium.org - mek@chromium.org - - The proportion of manifests that use the Chrome-specific header. Only tracks - manifests that were successfully parsed. - - - - - pwnall@chromium.org - mek@chromium.org - - The proportion of manifests parsed with dangerous features enabled. Only - tracks manifests that were successfully parsed. - - - - - - Removed 01/2020. Feature has been removed. - - pwnall@chromium.org - mek@chromium.org - - The proportion of manifests that use patterns in valid FALLBACK: entries. - Only tracks manifests that were successfully parsed. - - - - - pwnall@chromium.org - mek@chromium.org - - Usage of CHROMIUM-INTERCEPT entries in AppCache manifests. Only tracks - manifests that were successfully parsed. - - - - - - Removed 01/2020. Feature has been removed. - - pwnall@chromium.org - mek@chromium.org - - The proportion of manifests that use patterns in valid NETWORK: entries. - Only tracks manifests that were successfully parsed. - - - - - - Removed 01/2020. Feature has been removed. - - pwnall@chromium.org - mek@chromium.org - - The proportion of manifests that use patterns in any valid entries. Only - tracks manifests that were successfully parsed. - - - - - - Removed as of 5/2019. No longer needed. - - cmp@chromium.org - pwnall@chromium.org - - The proportion of ParseManifest calls that are triggered using a valid vs an - invalid manifest URL. - - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - Identifies where a missing manifest was detected occured. - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - - Logged on each occurrence of there being no record for the manifest file in - the entries table. - - - - - mek@chromium.org - - Tracks the number of times the appcache reinit process occurs. The boolean - value indicates whether it was a repeated attempt to reinitialize during a - browsing session. - - - - - - Removed on 2019-06-17. No longer tracked. - - mek@chromium.org - - Tracks the success rate of retrieving a sub resource from the appcache. - - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - - Time elapsed between a background task being queued and run. - - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - The amount of time taken to run a background task. - - - - cmp@chromium.org - pwnall@chromium.org - Tracks whether the update job was canceled. - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times we encountered corruption and fixed it while - handling a 304 response. We only attempt to recover corruption during 304 - response handling, so for any corrupt caches that exist and don't trigger a - conditional request, these cases can't result in the possibility of fixing - corruption through this path. - - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times we plan to check whether we can reuse existing - resources. - - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times we encounter a corrupt resource while checking if - we can reuse an existing resource. This is only called when we find a - corrupt resource, so any resources that are corrupt but aren't tested won't - be included in this count. If all resources are non-corrupt, then the - default value (0) will be sent for metrics collection. - - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times we encountered a corrupt resource and chose to - recover the corruption by refetching the resource in a non-conditional - request. This metric is always emitted upon AppCacheUpdateJob destruction - and is only incremented when the corruption recovery feature is enabled and - a corrupt resource is detected. If either corruption recovery is disabled or - no corrupt resources are recovered, then this will not be emitted. - - This metric was enabled in M81 (Dec 19, 2019), disabled in M82 (Feb 18, - 2020), and re-enabled in M86 (Aug 2020). In M86 this includes 0 values (no - corruption recovered), but in M87 and later it does not. - - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times we encounter a non-corrupt resource while - checking if we can reuse an existing resource. This is only called when we - find a non-corrupt resource, so any resources that aren't corrupt but aren't - tested won't be included in this count. If all resources are corrupt, then - the default value (0) will be sent for metrics collection. - - - - - cmp@chromium.org - enne@chromium.org - - Tracks the number of times we encounter a corrupt resource while checking if - we can reuse an existing resource. This is only called when we find a - corrupt resource, so any resources that are corrupt but aren't tested won't - be included in this count. - - Unlike ExistingResourceCorrupt this is only emitted when there are any - corrupt resources found. - - - - - cmp@chromium.org - enne@chromium.org - - Tracks the number of times we encounter a non-corrupt resource while - checking if we can reuse an existing resource. This is only called when we - find a non-corrupt resource, so any resources that aren't corrupt but aren't - tested won't be included in this count. - - Unlike ExistingResourceNotCorrupt this is only emitted when there are any - non-corrupt resources found. - - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times while checking existing resources that we - determined we can reuse that resource. - - - - - - Removed on 2020-08-20. No longer tracked. - - cmp@chromium.org - pwnall@chromium.org - - Tracks the number of times while handling a 304 response a cached response - has a Vary header while the incoming 304 response doesn't. - - - - - cmp@chromium.org - pwnall@chromium.org - Tracks the final internal state for the update job. - - - - cmp@chromium.org - pwnall@chromium.org - - Tracks the resource freshness we cached in a response as we consider whether - we can reuse an existing resource. This metric is in days and typically - reflects the Cache-Control: max-age=X server response header. It may - indicate the Expires: header in some cases at the time of the response if a - max-age header was not provided. Note that max-age is in seconds and we're - generally interested in a range of 0 days to ~1 year. - - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - AppCache update job result code. - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - Percent completion at point of failure of an update job. - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - - Whether the resource causing the failure was from a different origin. - - - - - - Removed 2019-06-17. No longer tracked. - - mek@chromium.org - - Whether any progresss had been made in the 5 minutes preceeding failure. - - - - - spqchan@chromium.org - The number of times an AppleScript event gets called. - - - - - - jshikaram@chromium.org - dominickn@chromium.org - - The actions taken by the user when they are viewing the app details of an - app in App Management (chrome://os-settings/app-management). - - - - - jshikaram@chromium.org - dominickn@chromium.org - The ways the user opens up the App Management interface. - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of creating shortcuts for an Extension, specifically from - the user clicking on "Create Shortcut" on the chrome://apps page, - in the right click menu of the respective Extension icon. - - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of creating shortcuts for a WebApp, specifically from the - user clicking on "Create Shortcut" on the chrome://apps page, in - the right click menu of the respective WebApp icon. - - - - - sashab@chromium.org - - The number of times the app info dialog is launched. This is gathered each - time the app info dialog is opened, from each of the places the dialog can - be opened from. - - - - - sashab@chromium.org - - The location of the app that the dialog was opened for. This is gathered - each time the app info dialog is opened. - - - - - sashab@chromium.org - - The type of the app that the dialog was opened for. This is gathered each - time the app info dialog is opened. - - - - - tapted@chromium.org - benwells@chromium.org - - The number of times v2 packaged apps are launched grouped by - extension_misc::AppLaunchBuckets. See also Extensions.AppLaunch. - - - - - - Removed 11/2017 in issue 600915 with the removal of app list on platforms - other than Chrome OS. - - mad@chromium.org - Interactions with the App Launcher promo dialog. - - - - pdyson@chromium.org - - The number of apps the were not able to be ranked by the Aggregated ML app - ranker (Top Cat). - - - - - pdyson@chromium.org - - The number of apps successfully ranked by the Aggregated ML app ranker (Top - Cat). - - - - - thanhdng@chromium.org - jiameng@chromium.org - - The type of errors that occur during the inference of Search Ranking - aggregated model. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending an answer card request and receiving the - notification that answer card has finished loading. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending an answer card request and receiving the - notification navigation has been finished with a valid answer card. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending a non-empty query to AppSearchProvider and - receiving results back. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending an empty query to AppSearchProvider and receiving - Zero State recommendation results back. - - - - - anasalazar@chromium.org - newcomer@chromium.org - - The different ways to add page in app list's apps grid. Logged when the page - is created. - - - - - - - anasalazar@chromium.org - tbarzic@chromium.org - - Relative smoothness of animations of entering or exiting the cardified state - in the apps grid. 100% represents ideally smooth 60 frames per second. 50% - represents only 30 frames per second is achieved during the animations. 0% - should not happen. This metric is recorded one time per apps grid page each - time we enter or exit cardified state in the apps grid. - - - - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - The number of results returned from a call to the Drive QuickAccess API. - Only reported if the API call did not error. - - - - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - Whether or not the results cache is empty. An empty cache means either poor - network conditions, the user opening zero-state very quickly, or an API - error. - - - - - tby@chromium.org - jiameng@chromium.org - - Whether or not the cache of Drive file results has already been warmed with - a request to ItemSuggest. Emitted each time we decide whether to warm the - cache, ie. each time Drive FS is mounted. - - - - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - Whether or not DriveFS is mounted on a call to - DriveQuickAccessProvider::Start or ::GetQuickAccessItems. - - - - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - The error code returned from a call to the Drive QuickAccess API. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The time between when GetQuickAccessItems was last called, and receiving - Drive QuickAccess results back. Only reported if the API call did not error. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The time between sending a zero state query and receiving file - recommendations back from the DriveQuickAccessProvider. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The time between when GetQuickAccessItems was last called, and the user - entering zero state search. - - - - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - Counts how many results from one call to the QuickAccess API exist in the - DriveFS mount and are OK for display. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending a non-empty query and receiving results back from - the extension which performs the file search. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending an non-empty query and receiving search results - back from OmniboxProvider which queries chrome AutocompelteController's - search providers to get the results. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The time between sending an empty query and receiving zero state - recommendations back from OmniboxProvider which queries chrome - ZeroStateProvider and gets recent queries back from Google Autocomplete - server. - - - - - jiameng@chromium.org - tby@chromium.org - - Various error states of the provider for OS settings in the cros launcher. - Emitted only in the case of an unexpected error, the bucket proportion is - not meaningful. - - - - - jiameng@chromium.org - tby@chromium.org - - The latency of a search in the OsSettingsProvider. Recorded each time a - search is completed, even if it returns no results. Not recorded if the - query is too short to perform a search at all. Chrome OS only. - - - - - thanhdng@chromium.org - jiameng@chromium.org - - The length of the query that resulted in an app launch from search box. This - metric only records non-empty queries. - - - - - thanhdng@chromium.org - jiameng@chromium.org - - The number of app launches from the search box with non-empty queries. - - - - - wrong@chromium.org - jiameng@chromium.org - - Whether or not the user has enabled Suggested Content in the launcher. This - is logged once per UMA upload, and only for any user that has the Suggested - Content toggle feature flag enabled. - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted when a suggestion chip is launched. Currently only 'true' is used, - but we may emit 'false' in future to track abandonment. - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted when a suggestion chip is launched, records the index (position in - the bar) of that chip. The left-most chip is index 0 and the maximum index - is 4. - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted when a suggestion chip is launched, records the type of that chip. - - - - - tby@chromium.org - jiameng@chromium.org - - Records error when processing user events into Apps.AppList.UserEvent.* - metrics. These are expected to be rare and bucket proportion is not - meaningful. - - - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted on a usage of the launcher, and records overall impressions, - launches, and abandons for a launcher UI view. The bucket proportion is not - meaningful for this metric, because impressions are a superset of launches - and abandons. Instead, the ratio between buckets can be used to calculate - accurate overall CTR. - - - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted after an impression, if the user then closes the launcher or moves - to a different view without launching any search result. This is emitted - once per abandon, per displayed result. Records the displayed result's type. - See Apps.AppList.UserEvent.TypeImpression for more details. - - This metric is completed by a histogram suffix describing which UI surface - the results are recorded from. - - - - - - - tby@chromium.org - jiameng@chromium.org - - When a set of results is displayed for 2 seconds and the user has probably - seen it, or the user interacted with the results and has definitely seen it, - we consider it an impression. - - Emitted once per impression for each displayed result. Records the type of - the displayed result, eg. native app or omnibox bookmark. - - The Apps.AppList.UserEvent.Type* metrics are directly comparable - per-result-type. So, for example, (launches / impressions) for a result type - gives an accurate CTR. - - This metric is completed by a histogram suffix describing which UI surface - the results are recorded from. - - - - - - - tby@chromium.org - jiameng@chromium.org - - Emitted after an impression, if the user launches a result. Records the type - of the launched result. See Apps.AppList.UserEvent.TypeImpression for more - details. - - This metric is completed by a histogram suffix describing which UI surface - the results are recorded from. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The time between sending a zero state query and receiving file - recommendations back from the ZeroStateFileProvider. - - - - - tby@chromium.org - edimitriadis@chromium.org - - Emitted when the ZeroStateFileProvider is created, records whether the - FileTasksNotifier creation succeeded for the given profile. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The type of item that was launched from a zero state launcher search result. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - Logs the result score received from the Drive Quick Access provider. The - original float score is scaled to range from 0 to 100 and its floor is - recorded. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - Logs the result score received from the Omnibox search provider. The - original float score is scaled to range from 0 to 100 and its floor is - recorded. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - Logs the result score received from the zero state file provider. The - original float score is scaled to range from 0 to 100 and its floor is - recorded. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - Whether an item was clicked from zero state search results, or if results - were displayed for some amount time but not clicked. These clicks and - impressions are used for calculating CTR metrics. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - Whether a set of search result impressions contains any Drive QuickAccess - file results. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The number of zero state impressions that contained at least one result of - the specified file type. - - - - - - Removed October 2019, replaced by - Apps.AppList.ZeroStateResultsList.LaunchedItemPositionV2, which uses - different bucketing. - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The position index of an item launched from zero state search results. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The position index of an item launched from zero state search results. - - - - - - Removed October 2019, replaced by - Apps.AppList.ZeroStateResultsList.NumImpressionTypesV2, which uses different - bucketing. - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The number of item types included in each zero state impression set. - - - - - wrong@chromium.org - tby@chromium.org - jiameng@chromium.org - - The number of item types included in each zero state impression set. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The decision of the user whether to remove a zero state search result. This - is gathered per click of a remove or cancel button of a search result - removal confirmation dialog. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The type of the action user performed on zero state search result. This is - gathered per click of a remove or append button of a search result. - - - - - - Removed June 2019, replaced by - Apps.AppList.ZeroStateSearchResultRemovalDecision. - - jennyz@chromium.org - newcomer@chromium.org - - The decision of the user whether to remove a zero state search result. This - is gathered per click of a remove or cancel button of a search result - removal confirmation dialog. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The type of the app list suggestion that was opened by user in zero state. - - - - - - Removed as of 04/2019 in favor Apps.AppListAppLaunchedV2. - - newcomer@chromium.org - - The number of apps launched from the launcher. This is logged each time an - app is launched. The bucket denotes whether the app is suggested. - - - - - - Removed as of 04/2019 in favor Apps.AppListAppLaunchedV2. - - newcomer@chromium.org - - The number of apps launched from the fullscreen launcher. This is logged - each time an app is launched. The bucket denotes whether the app is - suggested. - - - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The number of apps launched from the launcher and shelf for each launcher - state. This is incremented each time an app is launched. Each bucket - represents where in the launcher or shelf the app was launched from. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The different ways to move an app in app list's apps grid. Logged when the - app moving succeeds. - - - - - charleszhao@chromium.org - pdyson@chromium.org - - The type of app clicked in the launcher on ChromeOS, recorded after the icon - is clicked, before it is launched. - - - - - newcomer@chromium.org - - Number of apps (including ones in folders) with Chrome badge, across all - Launcher pages. This is gathered per open-launcher event. - - - - - calamity@chromium.org - - The amount of time it takes to build the app list UI. This is logged each - time the app list is built from scratch. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The type of the default result opened by user by pressing ENTER key. - Launcher UI shows suggested apps, recent queries, etc when user activates - the search box, or shows matched apps (installed apps, play store app - results, etc.) and other results (query suggestions, web site, bookmark, - files, etc) when user types a query. It will set the focus on the first - result as the default. User can open the default result by simply pressing - ENTER key. This metrics logs the type of the default result (installed app, - play store result, query suggestion, etc) opened by user pressing ENTER key. - - - - - - App list doesn't support doodles anymore. - - calamity@chromium.org - - The number of user interactions with the app list doodle. This is logged - once per action. - - - - - - Removed January 2020, this was a debugging metric that was too expensive to - keep in the code. - - Results on beta were: 60% present and shown, 5% present and not shown, and - 35% absent. - - tby@chromium.org - wrong@chromium.org - jiameng@chromium.org - - Emitted when the launcher updates the displayed zero-state search results. - Records whether a) a Drive QuickAccess result was displayed, b) a DQA result - was present in the candidate results list but wasn't one of the top 5 so was - not displayed, or c) no DQA results were in the results list. - - - - - wutao@chromium.org - - Relative smoothness of animations of showing and hiding app list folder. - 100% represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user starts the folder - animation in the launcher. - - - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The folder name length in characters when an app list folder gets renamed. - Logged when the folder name is changed and the texfield is no longer in - focus. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The number of times folders are opened in the app list. This is logged when - the folder is clicked. - - - - - newcomer@chromium.org - mmourgos@chromium.org - - Elapsed time from the input event to hide the launcher UI. This is logged - each time the launcher is dismissed by pressing search key, clicking shelf - button, or focusing out side of the launcher. - - - - - - Removed 03/2018 with Mash AppList refactoring. - - tapted@chromium.org - - The trigger that caused the app list to be enabled. Recorded when the user - first shows the app list. If not shown after one hour, will be recorded - then. If Chrome was not running at the one-hour mark, will be recorded - during the next Chrome startup. - - - - - wutao@chromium.org - - The internal app in apps grid was opened by the user. This is gathered per - click of an internal app. - - - - - wrong@chromium.org - jiameng@chromium.org - - Logs the length of user typed queries that result in launcher clicks. - Emitted each time the user opens a launcher search result after typing a - query. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The UMA histogram that logs the length of user typed queries app list - launcher issues to the search providers. - - - - - - Removed January 2020, the app list launch recorded has been removed. - - tby@chromium.org - charleszhao@chromium.org - - Reports error states of the app list launch recorder system. - - - - - calamity@chromium.org - src/ash/app_list/OWNERS - - The page that the app list goes to. This is gathered every time the user - initiates a transition to another page in the launcher. - - - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The source used to switch pages in the app list's app grid. Logged when the - page switch succeeds. - - - - - newcomer@chromium.org - - Replaced with Apps.AppListPeekingToFullscreenSource on 9/2017. - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The source which transitions the app list from Peeking to Fullscreen. This - is logged when the transition method is used. - - - - - jennyz@chromium.org - newcomer@chromium.org - - The index of the app within all play store apps displayed when it is - launched. - - - - - hejq@chromium.org - The state of a Play Store app search request. - - - - jennyz@chromium.org - newcomer@chromium.org - - The number of the play store apps displayed to user for a query. - - - - - napper@chromium.org - robsc@chromium.org - - When a user opens an app recommendation result, this is the number of times - we showed the result before opening. Number of times shown is reset to 0 - every 30 days, and is held on device. - - - - - napper@chromium.org - robsc@chromium.org - - Response when parsing the recommended app list from Play Store for candidate - app list, recorded every time a response from the play store is parsed in - client. - - - - - napper@chromium.org - robsc@chromium.org - - Number of responses from server in Apps.AppListRecommendedResponse.count - when fetching appListRecommendded GetAppReinstallCandidates. - - - - - napper@chromium.org - robsc@chromium.org - - Milliseconds elapsed to fetch appListRecommended GetAppReinstallCandidates. - - - - - tby@chromium.org - jiameng@chromium.org - - The index of a clicked result in the search result box and the length of the - search query. The index is relative to the SearchResultListView, not the - overall position in the suggestion window. - - - - - thanhdng@chromium.org - jiameng@chromium.org - - This boolean records if the query that introduces a launch in the results - list is empty or not. This will be recorded every time the user clicks an - item in the launcher results list. - - - - - jennyz@chromium.org - jiameng@chromium.org - - The length of the query when the user abandons results of a queried search - or recommendations of zero state (zero length query) in launcher UI. - - - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The number of times the applist searchbox has been activated. This is split - by keystroke, mouse press, and gesture tap activations. This is gathered - each time the searchbox goes from inactive to active, not necessarily empty - to non-empty. - - - - - tapted@chromium.org - - The number of searches that are started in the app list. This is gathered - each time the app list search box transitions from empty to non-empty. - - - - - jennyz@chromium.org - newcomer@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - The type of app list search omnibox result that was opened by the user. This - is gathered per OmniboxResult opened in the app list's launcher suggestion - window. - - - - - - - calamity@chromium.org - - The length of the app list search query when a result is opened. This is - gathered per click of a search result. - - - - - - Removed 2020-05. Not needed any longer. - - calamity@chromium.org - - The minimum number of arrow keys a user would need to press to navigate to - the opened search result. This is gathered per click of a search result. - - - - - wutao@chromium.org - - The app list search result of an internal app that was opened by the user. - This is gathered per click of a search result. - - - - - wutao@chromium.org - - The app list search result of an internal app that was shown to the user. - This is gathered per creation of a search result. Note: Typing a word with - multiple letters could trigger multiple creations of the search result. - - - - - calamity@chromium.org - src/ash/app_list/OWNERS - - The display type of the app list search result that was opened by the user. - This is gathered per click of a search result. - - - - - newcomer@chromium.org - The state of the app list when a search result was opened. - - - - - Removed March 2019. Replaced with Apps.AppListSearchResultOpenTypeV2. - - tapted@chromium.org - - The type of app list search result that was opened by the user. This is - gathered per SearchResult opened. Only recorded for search results shown in - the search result page of the launcher, except for M-62 where suggestion - chips were recorded as search results (https://crbug.com/919550). M-62 - should be filtered out when viewing this histogram to ignore the metrics - caused by the above mentioned bug. - - - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The type of app list search result that was opened by the user. This is - gathered per SearchResult opened. Only recorded for search results shown in - the search result page of the launcher (suggestion chips are not recorded). - - - - - newcomer@chromium.org - mmourgos@chromium.org - - Elapsed time from the input event to show the launcher UI. This is logged - each time the app list is shown by pressing search key, clicking shelf - button, or swiping from shelf. - - - - - newcomer@chromium.org - - The number of times the different sources for showing the app list are used. - This is logged when the app list is shown. Does not count the app list shown - when the last window is closed in tablet mode. This is not the total number - of times the app list is shown to the user; for that consult the user action - AppList_WindowFocused. - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The number of transitions from the different AppListStates. This is gathered - each time the launcher transitions from various states in - AppListView::SetState (Peeking, Half, Fullscreen All Apps, Fullscreen - Search, and Closed). Not all state transitions are collected because they - are not meaningful in measuring user activity. - - - - - newcomer@chromium.org - charleszhao@chromium.org - - The number of times suggested chips are launched at each suggested-apps - tile. An index i, ranged from 0 to kNumStartPageTiles - 1, is logged each - time a suggested chip is launched from i-th tile. - - - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The type of app list suggestion chip that was opened by the user. This is - gathered per SuggestionChip opened. - - - - - - Removed 04/2020. The related app ranking experiments have finished. - - tby@chromium.org - jiameng@chromium.org - - The index of a clicked result in the search result app tiles and the length - of the search query. The index is relative to the SearchTileItemListView, - not the overall position in the suggestion window. - - - - - - Removed 2018-03. - - tapted@chromium.org - - Time between enabling the app list, and a user explicitly choosing to show - it. If the app list is not shown after one hour, an entry in the last bucket - is recorded. If the user installs a second packaged app within one hour, or - if the app list was not enabled by installing a packaged app from the Web - Store, no time value is recorded - only Apps.AppListHowEnabled. - - - - - - Removed 07/2016 in Issue 600915 with the removal of the app list on Windows. - - tapted@chromium.org - - The amount of time spent in warmup (in WarmupForProfile call). This will - tell us how long warmup blocks the UI. - - - - - jackhou@chromium.org - - Counts which major milestone versions of app_mode_loader are sending - --app-shim-error. --app-shim-error is sent as a command line argument to - Chrome when app_mode_loader was unable to dyload the Chrome Framework and - call ChromeAppModeMain. For example, when Chrome updates from 32-bit to - 64-bit, an older shim will find the new framework version but fail to dyload - it. - - - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The total number of apps in folders ignoring OEM folders. This is logged - each time the app list is initialized. The - "FullscreenAppListDisabled" suffix has been deprecated. - - - - - ajlinker@chromium.org - dominickn@chromium.org - nancylingwang@chromium.org - - Records whether an application has bounced (been uninstalled in less than - seven days). Recorded when an application is uninstalled. - - - - - - - newcomer@chromium.org - mmourgos@chromium.org - - The number of times a certain command was executed by a context menu, split - by whether the context menu came from an app, or another part of the system - UI. - - - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The show source (touch, mouse, keyboard, etc) for a context menu. Split by - the component from which the context menu originated. - - - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The user journey time for a ContextMenu, defined as the time between - launching a context menu and the context menu's close callback being - activated. Not recorded whenever the context menu is not for an app icon on - the shelf. - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of creating shortcut image for web app on Linux. - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of creating shortcut for web app on Linux. - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of creating shortcut for web app on MacOS. - - - - - - - dominickn@chromium.org - nancylingwang@chromium.org - nigeltao@chromium.org - - Records when a user attempts to launch a particular Chrome OS app. - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of re-creating shortcut during file handler registration - process for PWA on Linux - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of file handler registration for PWA on Linux - - - - - - Removed 08/2020. File handler registration is done through shortcuts - creation, replaced by WebApp.Shortcuts.Creation.Result. - - phillis@chromium.org - cmumford@chromium.org - - Records the result of file handler registration for PWA on MacOS - - - - - phillis@chromium.org - cmumford@chromium.org - - Records the result of file handler registration for PWA on Windows - - - - - - - andrewxu@chromium.org - newcomer@chromium.org - - Relative smoothness of animations of launcher transitions in tablet mode. - 100% represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user triggers launcher - animation in tablet mode. - - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of installing an app on the chrome://apps page. This - happens when a user drags a link to this page. - - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of locally installed an app on the chrome://apps page, - which involves hooking up Os integration. Specifically, this records if the - shortcuts were created successfully. This happens whena user right-clicks on - a greyed out webapp icon in the chrome://apps page and clicks - "Install". - - - - - wrong@chromium.org - jiameng@chromium.org - - Whether or not the most recent Launcher search query differs from the - previous query in length by more than one character. Search queries are - issued incrementally as the user types, so this will approximately - differentiate between incremental and non-incremental search queries. - Emitted on each change to the launcher search query. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time needed to create a lock screen apps profile. This metric - is recorded only if the profile creation was successful. The lock screen - apps profile is created if the user has an app enabled on Chrome OS lock - screen, and is used as the context in which the app is launched on top of - the lock screen. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Boolean indicating whether the lock screen apps profile creation succeeded. - The lock screen apps profile is created if the user has an app enabled on - Chrome OS lock screen, and is used as the context in which the app is - launched on top of the lock screen. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The size of a data item stored in the lock screen data item storage using - chrome.lockScreen.data API as sent from the app - the item will be encrypted - before getting stored in the storage. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The size of an encrypted data item stored in the lock screen data item - storage using chrome.lockScreen.data API. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time it took to complete a lock screen data item storage - operation. Reported only on the operation failure. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time it took to complete a lock screen data item storage - operation. Reported only on the operation success. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The result of a lock screen data item storage operation returned through - chrome.lockScreen.data extension API. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The number of data items saved in the lock screen data item storage per app. - This is recorded on startup, when the app attempts to use the - chrome.lockScreen.data API. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Reported when a user attempts to launch a note taking app on the lock - screen. It reports the note taking app state in the lock screen apps profile - at the launch attempt time - for example, whether the app was enabled, or - whether the app had been terminated and an app reload was attempted. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time a lock screen enabled app window spent in a certain state - during the app window activity. The state to which the histogram refers to - is defined by the suffix. The metric is logged upon leaving the associated - state. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The note taking action availability state on the lock screen, recorded when - the user session is locked. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The state in which lock screen enabled note taking app was when the note - taking session ended. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount time a lock screen app had been launching when the app launch was - canceled. Logged if the lock screen app session ends before the lock screen - app window is shown. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Ordinal number of a note taking app launch request from a lock screen within - a lock screen session. If a note taking app is launched n times during a - single lock screen session, this histogram will be reported with values 1 - through n. The launch counter is reset on screen unlock. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The user action that launched note taking from the lock screen. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Reported when a note taking app is unloaded from the lock screen apps - profile while lock screen note taking is available. Reports the unload - reason type, which can be used to deduce whether the app can be reloaded in - the profile. The app unload event is not reported if the app is unloaded due - to lock screen note taking becoming unavailble (e.g. when the user unlocks - the screen). - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Amount of time needed to install a copy of a lock screen note taking app - into lock screen apps profile. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The reason the note taking on lock screen was ended (and lock screen app - window was closed). - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - Reported when a note taking app is terminated in the lock screen apps - profile. It reports the number of times the app was reloaded in the lock - screen apps profile during the current lock screen session (prior to the - termination). - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time needed to load a note taking app window contents on the - lock screen - i.e. the time passed from the user requesting an app launch to - the app window contents being loaded. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The amount of time needed to launch a note taking app window from the lock - screen - i.e. the time passed from the user requesting an app launch to the - app window appearing on the screen. - - - - - - Obsolete - tracks actions in UI that did not launch. - - tbarzic@chromium.org - tbuckley@chromium.org - - The action the user took on the lock screen UI shown when lock screen app - window is in background, shown under the lock screen. - - - - - jiameng@chromium.org - thanhdng@chromium.org - tby@chromium.org - - Records number of clicks on search result for different display types in - zero-state. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The result of attempting to launch a default note-taking app on Chrome OS. - Only reported if the preferred app was unspecified or failed to launch. - - - - - dstockwell@chromium.org - tbuckley@chromium.org - - The result of attempting to launch the user-specified preferred note-taking - app, if any, on Chrome OS. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The number of folders that users have in their Launcher. Includes the OEM - folder. This metric is recorded every time the launcher is shown. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The number of pages that users have in the top level apps grid of their - Launcher. This metric is recorded every time the launcher is shown. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - The number of pages that are not full in the top level apps grid of - Launcher. This metric is recorded every time the launcher is shown. - - - - - - - newcomer@chromium.org - wutao@chromium.org - - Base name is deprecated as of 3/2019 in favor of - Apps.PaginationTransition.AnimationSmoothness.ClamshellMode and - Apps.PaginationTransition.AnimationSmoothness.TabletMode - - Relative smoothness of animations of launcher pagination transitions. 100% - represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user starts the pagination - transition animation of the launcher. - - - - - - - omrilio@chromium.org - newcomer@chromium.org - - Presentation time for the apps grid scrolling operation. This starts when - drag starts by gesture and ends before the patination animation starts. The - smoothness of the pagination animation is recorded in - Apps.PaginationTransition.AnimationSmoothness.{TabletMode|ClamshellMode}. - - - - - - - omrilio@chromium.org - newcomer@chromium.org - - Maximum latecy reported during one drag to scroll operation on apps grid. - - - - - dominickn@chromium.org - mxcai@chromium.org - - Recorded at the time a read/write operation happens for preferred app to - indicate whether the I/O succeeded or not. - - - - - dominickn@chromium.org - mxcai@chromium.org - - Recorded at the time a update operation happens for preferred apps to - indicate the type of update action. - - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Relative smoothness of animations of the scrollable shelf when scrolling. - 100% represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user scrolls over the - scrollable shelf. - - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Presentation time of the drag scroll in the scrollable shelf in - milliseconds. - - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Maximum latency of the presentation time of the drag scroll in the - scrollable shelf. - - - - - cmumford@chromium.org - rahsin@microsoft.com - - Records the result of shortcuts menu registration for PWA on Windows - - - - - cmumford@chromium.org - rahsin@microsoft.com - - Records the result of shortcuts menu unregistration for PWA on Windows - - - - - - - newcomer@chromium.org - - Relative smoothness of animations of peeking launcher state transitions. - 100% represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user switches states of the - launcher. - - - - - - - omrilio@chromium.org - newcomer@chromium.org - - Presentation time of the app launcher drag operation in milliseconds. - - - - - - - omrilio@chromium.org - newcomer@chromium.org - - Maximum latency of the presentation time of the app laucnher drag operation. - - - - - - There was only one valid value starting in M69 and code to record the values - was removed in M85. - - stevenjb@chromium.org - - The type of app window opened (through the chrome.app.window API). - - - - - hirokisato@chromium.org - sarakato@chromium.org - - Whether the ARC window is opened with TalkBack enabled or not. Counted when - a user opens a window or toggles the feature. Checked only when the spoken - feedback is enabled in Chrome OS. - - - - - dominickn@chromium.org - lgcheng@google.com - nancylingwang@chromium.org - - The adaptive Arc app icons are loaded from ArcAppIcon. Recorded whether the - icon is the adaptive icon when the icon is loaded. - - - - - dominickn@chromium.org - lgcheng@google.com - nancylingwang@chromium.org - - The adaptive Arc app icons are loaded from ArcAppIcon for default Arc apps. - Recorded whether the icon is the adaptive icon when the icon is loaded. - - - - - dominickn@chromium.org - lgcheng@google.com - nancylingwang@chromium.org - - The adaptive Arc app icons are loaded from Non ArcAppIcon. Recorded whether - the icon is the adaptive icon when the icon is loaded. - - - - - victorhsieh@chromium.org - tbuckley@chromium.org - - Record user's choice or error during ADB sideloading opt-in UI after reboot. - - - - - elijahtaylor@google.com - shihuis@google.com - The time elapsed for booting up the ARC instance. - - - - elijahtaylor@google.com - shihuis@google.com - - The number of ARC apps open at any given time. Collected every 5 minutes. - This indicates both how many users are engaging with apps and, when they do - engage, how many apps they are engaging with at a time. - - - - - robsc@chromium.org - napper@chromium.org - - Record a reason when an arc application completes installation successfully, - including policy based applications, default applications and user prompted - installations. - - - - - robsc@chromium.org - napper@chromium.org - - Record a count of an impression of FAR result. This is a count _any_ time - it's shown, even for a millisecond. - - - - - robsc@chromium.org - napper@chromium.org - - Record a count of an impression of FAR result. This is a count of heuristic - real impressions: a new showing after a while, a longer showing, etc. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - Record the time to build ARC app shortcut items on menu model. We get the - needed metadata from Android and decode icons in the utility process. It is - an asynchronous procedure so we need to know the longest waiting time. - - - - - elijahtaylor@google.com - shihuis@google.com - - Total number of ARC apps installed on a device measured at startup. Note: - This includes launchable apps that are installed by default, such as Play - Store and Settings, as well as any vendor specific apps. - - - - - robsc@chromium.org - napper@chromium.org - - Record a reason why an application was uninstalled when uninstall is - completed. - - - - - - - mhasank@google.com - arc-core@google.com - The status of account check before GMS Sign-in. - - - - - - mhasank@google.com - arc-core@google.com - - Elapsed time waiting for the account status check to be completed. This is - not recorded in case of account status check failure. - - - - - - - mhasank@google.com - arc-core@google.com - - Number of attempts done while waiting for the check-in task to be completed. - 0 means that device was already checked-in. This is recorded in case - check-in task is completed successfully. - - - - - - - mhasank@google.com - arc-core@google.com - - Elapsed time waiting for the check-in task to be completed. This is recorded - in case check-in task is completed successfully. - - - - - mhasank@google.com - arc-core@google.com - Contains the status of main account resolution. - - - - - - mhasank@google.com - arc-core@google.com - - Elapsed time waiting for network connection before starting other - authorization operations. - - - - - - - mhasank@google.com - arc-core@google.com - Elapsed time waiting for GMS sign-in to complete. - - - - elijahtaylor@google.com - shihuis@google.com - - The relative time of a boot progress event since the ARC starts. - - - - - elijahtaylor@google.com - xzhou@google.com - Code installation result for ARC boot continue. - - - - elijahtaylor@google.com - xzhou@google.com - - Total time needed to check the integrity of host generated code. If - signature checking fails, it also includes the time to regenerate and sign - the code. - - - - - elijahtaylor@google.com - xzhou@google.com - Host code relocation result. - - - - elijahtaylor@google.com - xzhou@google.com - Time needed to relocate boot*.art files. - - - - elijahtaylor@google.com - xzhou@google.com - Time needed to sign boot*.art files. - - - - elijahtaylor@google.com - xzhou@google.com - - Code verification result for host generated code for boot for login screen. - - - - - elijahtaylor@google.com - xzhou@google.com - Time needed to verify host generated code. - - - - sstan@google.com - bartfab@chromium.org - giovax@google.com - - Records the number of times ChromeOS Companion Library API called. Counter - adding when its Stub library receive the call from applications. - - - - - alexchau@google.com - emaxx@google.com - - Elapsed time from the policy update notification sent to ARC to the - corresponding successfully obtained compliance report from CloudDPS. - - - - - elijahtaylor@google.com - yusukes@google.com - - The number of ARC container lifetime events. One START event and up to one - non-START event are recorded per ARC session, which ends when the user opts - out from ARC or signs out. - - - - - elijahtaylor@google.com - yusukes@google.com - - The number of times ARC container crashes and automatically restarts in one - ARC session, which ends when the user opts out from ARC or signs out. - - - - - wvk@google.com - khmel@google.com - - Records the time that throttling was disabled due to a particular throttle - observer. The duration begins when a new throttle observer becomes active, - and measures until it becomes inactive or another throttle observer becomes - effective. - - - - - elijahtaylor@google.com - shihuis@google.com - - ARC use time. The use time is incremented in regular intervals while android - container is active. Reported at most once a day, at which point accumulated - time is reset (which means that sum of reported times for a OS version would - give an estimate of ARC usage time per OS version). - - - - - skau@chromium.org - vkuzkokov@google.com - - The number of pages sent to a native printer by ARC. Reported for every - print job originating in ARC container and sent to a CUPS printer. - - - - - hashimoto@google.com - shihuis@google.com - - Reason why a custom tab session ended. Recorded when a session ends. - - - - - - Removed 06/2019. Replaced by Arc.CustomTabs.SessionLifetime2.All to extend - the max value. - - hashimoto@google.com - shihuis@google.com - Lifetime of each session. Recorded when a session ends. - - - - - Removed 06/2019. Replaced by Arc.CustomTabs.SessionLifetime2.Closed to - extend the max value. - - hashimoto@google.com - shihuis@google.com - - Lifetime of each session. Recorded when a session is closed. - - - - - - Removed 06/2019. Replaced by - Arc.CustomTabs.SessionLifetime2.ForwardedToNormalTab to extend the max - value. - - hashimoto@google.com - shihuis@google.com - - Lifetime of each session. Recorded when a session ends because the tab was - forwarded to a normal tab. - - - - - hashimoto@google.com - Lifetime of each session. Recorded when a session ends. - - - - hashimoto@google.com - - Lifetime of each session. Recorded when a session is closed. - - - - - hashimoto@google.com - - Lifetime of each session. Recorded when a session ends because the tab was - forwarded to a normal tab. - - - - - maajid@google.com - shaochuan@google.com - shihuis@google.com - - Total of Arc.EngagementTime.Background and Arc.EngagementTime.Foreground. - Note that this differs from Arc.EngagementTime.Total in that this is the - ARC++ engagement time, while Arc.EngagementTime.Total is the CrOS total - engagement time on devices with ARC++ enabled. See Arc.EngagementTime.Total - for definition of engagement and further details. - - - - - maajid@google.com - shaochuan@google.com - shihuis@google.com - - Times when user is engaged and ARC++ apps are running in the background, but - the user isn't focusing on an ARC++ app window. See Arc.EngagementTime.Total - for definition of engagement and details. - - - - - maajid@google.com - shaochuan@google.com - shihuis@google.com - - Times when user is engaged and focuses on an ARC++ app window. See - Arc.EngagementTime.Total for definition of engagement and details. - - - - - maajid@google.com - shaochuan@google.com - shihuis@google.com - - Total CrOS user session time (from login to logout) excluding times when - user "disengages": screen is locked or dims down due to user idle. - Engagement time metrics, along with foreground and background time, are only - collected on users with ARC++ enabled. All four metrics are accumulated and - recorded to UMA once a day. For Total ARC++ engagement time, please see - Arc.EngagementTime.ArcTotal. - - - - - fukino@chromium.org - yusukes@chromium.org - - When a removable media is mounted, whether Android apps have full access to - the media. Users can allow full access in Settings. Changing the preference - in Settings is tracked by Arc.ExternalStorage.SetVisible. - - - - - fukino@chromium.org - yusukes@chromium.org - - When a user clicks a toggle switch in "External storage - preferences" screen, where the new value is ENABLED or not. - - - - - yusukes@google.com - khmel@google.com - - How long the user sees the spinning icon waiting for ARC container boot. - Zero when the container has already been up and running when the user - launches the ARC app. - - - - - yusukes@google.com - khmel@google.com - - Elapsed time from the when UI is shown after login to when the user - activates first ARC app. - - - - - alexchau@google.com - emaxx@google.com - - Elapsed time from the signing in process start to a successfully obtained - compliance report from CloudDPS. - - - - - alexchau@google.com - emaxx@google.com - - Elapsed time from ARC startup to a successfully obtained compliance report - from CloudDPS. This value is not reported during the first startup when - signing in happens. - - - - - khmel@google.com - lgcheng@google.com - - Elapsed time of first 5 compressed app icons is loaded from file system. - Recorded when the app icon loading completes. - - - - - khmel@google.com - lgcheng@google.com - - Elapsed time of other compressed app icons is loaded from file system. - Recorded when the app icon loading completes. - - - - - khmel@google.com - lgcheng@google.com - - Elapsed time of first 5 uncompressed app icons is loaded from file system. - Recorded when the app icon loading completes. - - - - - khmel@google.com - lgcheng@google.com - - Elapsed time of other uncompressed app icons is loaded from file system. - Recorded when the app icon loading completes. - - - - - yhanada@chromium.org - tetsui@chromium.org - - The number of IME apps installed. Collected at startup and when an IME app - is installed or uninstalled. - - - - - - Removed April 2018 and replaced by ChromeOS.Apps.IntentPickerAction. - - elijahtaylor@google.com - shihuis@google.com - ARC intent handler action taken by user. - - - - - Removed April 2018 and replaced by - ChromeOS.Apps.IntentPickerDestinationPlatform. - - elijahtaylor@google.com - shihuis@google.com - - ARC intent handler destination platform. The destination may be specified - due to the user explicit selection or a previously stored preference. - - - - - hashimoto@google.com - shihuis@google.com - - Types of things opened via ARC IntentHelperHost interface. Recorded when one - of the "open" methods of the interface is called. - - - - - elijahtaylor@google.com - shihuis@google.com - Cumulative count of low memory kills in one user session. - - - - cywang@google.com - elijahtaylor@google.com - shihuis@google.com - - When Chrome OS is in low memory state, TabManager kills some victims to free - memory. This value is the elapsed time between TabManager receiving the low - memory notification and the first kill. - - - - - elijahtaylor@google.com - shihuis@google.com - The memory size freed by each low memory kill event. - - - - elijahtaylor@google.com - shihuis@google.com - The elapsed time to last low memory kill event. - - - - elijahtaylor@google.com - levarum@google.com - - Native bridge used for ARC. Can be unknown and none. This is collected along - with Arc.State during every metrics recording interval, so it is in every - record uploaded to the server (despite crbug.com/929583 which was fixed in - M73). This is required because this value is used to categorize all other - data in the dashboard as collected with specific native bridge in use. Since - M74 this is also included in initial stability logs. - - - - - elijahtaylor@google.com - shihuis@google.com - Cumulative count of OOM kills in one user session. - - - - - Removed 09/2020 for Issue 1124182. - - elijahtaylor@google.com - shihuis@google.com - - The oom_badness score of a OOM killed process as reported by kernel. - - - - - - Removed 09/2020 for Issue 1124182. - - elijahtaylor@google.com - shihuis@google.com - The elapsed time since last OOM kill event. - - - - elijahtaylor@google.com - shihuis@google.com - Arc OptIn action taken by user. - - - - elijahtaylor@google.com - shihuis@google.com - Arc OptIn cancelation reason. - - - - elijahtaylor@google.com - khmel@google.com - Arc OptIn flow result. - - - - elijahtaylor@google.com - - Arc Silent Auth Code status. This status is set during the ARC OptIn flow. - - - - - khmel@google.com - - Arc Silent Auth Code status. This status is set during the ARC - Device/Primary Account reauthorization flow. - - - - - khmel@google.com - - Arc Silent Auth Code status. This status is set during the minting of an - auth code for a Secondary Account. It can be set for Secondary Account - signin or reauthorization. - - - - - - - jhorwich@google.com - khmel@google.com - State of PlayAutoInstall flow after the request. - - - - - - jhorwich@google.com - khmel@google.com - - Elapsed time from the when the PlayAutoInstall request was issued and - completed. - - - - - khmel@google.com - yusukes@google.com - - Elapsed time from the when the user launches the Play Store app and to when - the Play Store window is shown to the user. - - - - - jennyz@chromium.org - newcomer@chromium.org - - Time between a default play store result being activated by user pressing - ENTER key and being displayed. - - - - - hejq@chromium.org - - Time between sending an Play Store app discovery request and the storing - returned results. - - - - - jennyz@chromium.org - newcomer@chromium.org - - Time between a play store result being clicked and being displayed. - - - - - hejq@chromium.org - - The total number of returned apps of a Play Store app discovery query. - - - - - hejq@chromium.org - - The number of returned instant apps of a Play Store app discovery query. - - - - - hejq@chromium.org - - The number of returned uninstalled apps of a Play Store app discovery query. - - - - - - - yusukes@google.com - khmel@google.com - - Elapsed time from the when the user agrees ToS to when the Play Store window - is shown to the user. - - - - - bmgordon@chromium.org - jschettler@chromium.org - - Print preview events for ARC. Recorded when specific print preview events - occur (print preview requested, preview document created, etc.). - - - - - bmgordon@chromium.org - jschettler@chromium.org - - Time taken for ARC to render and generate a PDF for print preview. Includes - time to reflow the page back to normal, but not the time to reflow the page - to prepare for printing. - - - - - bmgordon@chromium.org - jschettler@chromium.org - - Time taken for ARC to render and generate a PDF for print preview divided by - the number of pages. Includes time to reflow the page back to normal, but - not the time to reflow the page to prepare for printing. - - - - - bmgordon@chromium.org - jschettler@chromium.org - - Count how frequently a set of pre-defined print preview errors occur for - ARC. - - - - - bmgordon@chromium.org - jschettler@chromium.org - Time taken for ARC to render a PDF for print preview. - - - - - - mhasank@google.com - arc-core@google.com - - The result (success or the reason of failure) of Cloud DPC provisioning. - Recorded when ARC++ provisioning flow completes. - - - - - - - alexchau@google.com - phweiss@google.com - - The result (success or the type of failure) of ARC provisioning. The base - value has been deprecated on 2016-09-15 in favour of per user type values. - - - - - - - alexchau@google.com - phweiss@google.com - - Elapsed time from the signing in process start to call to onSignInFailed. - - - - - - - alexchau@google.com - phweiss@google.com - - Elapsed time from the signing in process start to successful call to - onSignInComplete. - - - - - - - khmel@google.com - - The result (success or the type of failure) of ARC reauthorization. - - - - - - - khmel@google.com - skuhne@google.com - Standard deviation for commit time delta from ideal time. - - - - - - khmel@google.com - skuhne@google.com - Render frames per second. - - - - - - khmel@google.com - skuhne@google.com - Render quality with maximum 100%. - - - - niwa@google.com - yusukes@google.com - - The types of ARC SDK version upgrade. (e.g. Upgrade from N to P) Reported - when SDK version upgrade is detected during ARC boot. - - - - - sinhak@google.com - jhorwich@google.com - khmel@google.com - - The result (success or the type of failure) of ARC Secondary Account signin/ - reauthorization. - - - - - - - shaochuan@google.com - khmel@google.com - mmatena@google.com - - This is updated when the mojo connections to processes in detailing in - ArcMojoConnectionType are closed for reasons other than the ARC container - shutting down or crashing. - - - - - - - shaochuan@google.com - khmel@google.com - mmatena@google.com - - This is updated in case ARC++ stops for the reasons detailed in - ArcStopReason. For example, this is recorded in case of a graceful ARC++ - shutdown or if ARC++ crashes. - - - - - weifangsun@google.com - djacobo@google.com - - Exit code coming from ARC's share files feature. Used to observe stability - for the feature. - - - - - elijahtaylor@google.com - - The time it takes for ARC to shut down. This value is recorded on ARC - shutdown as the time is takes for the init process to exit after setting - 'sys.powerctl shutdown'. It is reported on the next ARC startup to avoid - sending data during shutdown. - - - - - elijahtaylor@google.com - ttylenda@google.com - - Whether ARC is enabled or not. Before M56 this was collected only on login - and when ARC was enabled or disabled. From M56 forward this is collected - during every metrics recording interval, so it is in every record uploaded - to the server (despite crbug.com/929583 which was fixed in M73). This is - required because this value is used to categorize all other data in the - dashboard as collected with ARC enabled or not. This is true even for users - who are running on ecryptfs and skipped Ext4 migration; even though ARC Apps - do not run until migration is complete on N or later systems. Since M74 this - is also included in initial stability logs. - - - - - - - elijahtaylor@google.com - shihuis@google.com - khmel@google.com - - Similar to "Arc.State" metric but has separation by user type. - - - - - giovax@chromium.org - arc-commercial@google.com - - The result (success or the type of failure) of ARC supervision transition - events. - - - - - giovax@chromium.org - arc-commercial@google.com - - Elapsed time for a successful supervision transition, during which the - supervision transition screen was displayed. - - - - - giovax@chromium.org - arc-commercial@google.com - - Whether supervision transition screen exited due to a successful transition. - - - - - elijahtaylor@google.com - khmel@google.com - Action of ARC++ Graphics Tracing tool. - - - - - - khmel@google.com - yusukes@google.com - - Elapsed time from the when ARC++ is started in already provisioned state to - when the ARC is available for the user. - - - - - - - khmel@google.com - yusukes@google.com - - Elapsed time from the when ARC++ is opted in from the user's session to when - the ARC is available for the user. - - - - - - - khmel@google.com - yusukes@google.com - - Elapsed time from the when ARC++ is opted in from OOBE to when the ARC is - available for the user. - - - - - jhorwich@chromium.org - elijahtaylor@chromium.org - shihuis@google.com - maajid@chromium.org - - Counts user interactions with ARC by type, such as ARC app launches via the - shelf or launcher. - - - - - - - mhasank@google.com - arc-core@google.com - - Elapsed time waiting for the check-in task to be completed. This is recorded - in case check-in task is completed successfully. - - - - - - - mhasank@google.com - arc-core@google.com - Elapsed time waiting for GMS sign-in to complete. - - - - - Renamed to Arc.LowMemoryKiller.FreedSize on 2016/03/24. - - elijahtaylor@google.com - The memory size freed by each low memory kill event. - - - - - Renamed to Arc.LowMemoryKiller.TimeDelta on 2016/03/24. - - elijahtaylor@google.com - The elapsed time to last low memory kill event. - - - - - Removed Jan 2020 for R82. - - zentaro@chromium.org - cros-peripherals@chromium.org - - The lock screen action has two accelerators: - Ctrl+Shift+L which is - deprecated. - Search+L which is new. This histogram shows the number of - times each accelerator (deprecated and new) is used. - - - - - - Removed 01/2017 for Issue 672905. - - afakhry@chromium.org - - The switch to the next IME action has two accelerators: - Shift+Alt which is - deprecated. - Ctrl+Shift+Space which is new. This histogram shows the number - of times each accelerator (deprecated and new) is used. - - - - - afakhry@chromium.org - - Showing the IME menu bubble has two accelerators: - Alt+Shift+K which is - deprecated. - Search+Shift+K which is new. This histogram shows the number - of times each accelerator (deprecated and new) is used. - - - - - zentaro@chromium.org - cros-peripherals@chromium.org - - Opening the task manager has two accelerators: - Shift+Esc which is - deprecated. - Search+Esc which is new. This histogram shows the number of - times each accelerator (deprecated and new) is used. - - - - - afakhry@chromium.org - - Toggling the high contrast display mode has two accelerators: - - Search+Shift+H which is deprecated. - Ctrl+Search+H which is new. This - histogram shows the number of times each accelerator (deprecated and new) is - used. - - - - - baileyberro@chromium.org - - Captures the result of a user using the rotation accelerator - - Ctrl+Shift+Refresh. This histogram shows how frequently users accidentally - hit the key combination. - - - - - amusbach@chromium.org - xdai@chromium.org - Captures usage of Alt+[ and Alt+]. - - - - - Removed 02/2017 due to lack of usage. - - kuscher@google.com - rbyers@chromium.org - - Number of active touch-points when a new touch-point is added. - - - - - kuscher@google.com - - The show type of the active window tracked over time by logging on a regular - basis (30 minutes). - - - - - cowmoo@google.com - xiaohuic@chromium.org - - Recorded whenever Ambient mode is entered from {TabletOrClamshell}. - AmbientUiMode indicates whether the user entered Ambient mode from the lock - screen or from screen idle. - - - - - - - - - wutao@chromium.org - xiaohuic@chromium.org - - Emitted when the ambient mode photo transition animation completes to report - the smoothness of this animation. 100% represents ideally smooth 60 frames - per second. - - - - - cowmoo@google.com - xiaohuic@chromium.org - - Among eligible users, whether the user has Ambient mode enabled. Recorded - once for every UMA upload. The set of eligible users includes all users with - profiles that can allow Ambient mode to be enabled. This is limited by - profile type, whether the user is primary, if the user has a supported - email, etc. - - - - - cowmoo@google.com - xiaohuic@chromium.org - - Among eligible users with ambient mode enabled, records the length of each - session. The metric is uploaded when ambient mode is ended. - - - - - - - - - cowmoo@google.com - xiaohuic@chromium.org - - Among eligible users with ambient mode enabled, records the source of - ambient mode photos. Recorded once for every UMA upload. - - - - - - Removed 10/2016 for Issue 616581. - - tbuckley@chromium.org - - The amount of time between selecting an item from the Ash app list. Not - recorded on the first time an item is selected from the app list after - startup. - - - - - - - cowmoo@chromium.org - xiaohuic@chromium.org - - Relative smoothness of assistant related animations. 100% represents ideally - smooth 60 frames per second. - - - - - minch@chromium.org - tclaiborne@chromium.org - - End scenario type while swiping back from the left side of the window in - tablet mode. - - - - - minch@chromium.org - tclaiborne@chromium.org - - Start scenario type while swiping back from the left side of the window in - tablet mode. - - - - - minch@chromium.org - tclaiborne@chromium.org - - Underneath window type while swiping back from the left side of the window - in tablet mode. - - - - - - Removed from code as of 04/2020. - - - - yulunwu@chromium.org - tbarzic@chromium.org - - Tracks usage of the contextual nudge for the user gesture education. - - - - - - - yulunwu@chromium.org - tbarzic@chromium.org - - Tracks the reason contextual nudges for user gesture education are - dismissed. - - - - - - - yulunwu@chromium.org - tbarzic@chromium.org - - Tracks time between showing contextual nudge and gesture being performed. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - mukai@chromium.org - - Emitted when the virtual desks activation animation completes to report the - smoothness of this animation when running on the display on which the active - window resides (if any) or the display of the primary root window. 100% - represents ideally smooth 60 frames per second. - - - - - afakhry@chromium.org - sammiequon@chromium.org - tclaiborne@chromium.org - - When a four finger touchpad swipe has ended, an animation to the nearest - desk will occur. This histogram is emitted when that animation finishes. - 100% represents ideally smooth 60 frames per second. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - mukai@chromium.org - - Emitted when the virtual desks removal animation completes to report the - smoothness of this animation when running on the display on which the active - window resides (if any) or the display of the primary root window. 100% - represents ideally smooth 60 frames per second. - - - - - - Removed 03/2020, and replaced by Ash.Desks.DesksCount2. This was broken as - it did report desks count during the creation of the first-ever created desk - after boot. - - afakhry@chromium.org - - Emitted when there's a change in the virtual desks count whether due to desk - creation or removal. Specifies the number of available desks. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when there's a change in the virtual desks count whether due to desk - creation or removal. Specifies the number of available desks. It is not - emitted for the first-ever created default desk. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when the active desk is changed to specify the source of this - action, i.e. whether due to new-desk shortcut, desk removed, window - activated, switch-desk shortcut, or a press on the desk mini_view. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when a window is moved from the current active desk to another desk. - Specifies the source of this action, i.e. whether to window drag-and-drop, - or keyboard shortcut. - - - - - - Removed 03/2020, and replaced by Ash.Desks.NewDesk2. This was broken as it - did report the creation of the first-ever created default desk after boot as - being created by the new-desk button. - - afakhry@chromium.org - - Emitted when a virtual desk is created to specify the source of this action, - i.e. whether from the new-desk button, keyboard shortcut. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when a virtual desk is created to specify the source of this action, - i.e. whether from the new-desk button, keyboard shortcut, or due to desks - restore. It is not emitted for the first-ever created default desk. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The number of windows on the first desk. Emitted when a desk is removed, or - a window is moved to another desk. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The number of windows on the second desk. Emitted when a desk is removed, or - a window is moved to another desk. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The number of windows on the third desk. Emitted when a desk is removed, or - a window is moved to another desk. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The number of windows on the fourth desk. Emitted when a desk is removed, or - a window is moved to another desk. - - - - - afakhry@chromium.org - sammiequon@chromium.org - tclaiborne@chromium.org - - Presentation time in ms when a four finger swipe is being used to change - desks. One full swipe results in multiple emissions of this metric; once - everytime the fingers change location on the trackpad. Presentation time is - the time it takes from when the software recognizes the touchpad swipe to - when the next frame is displayed on the screen. - - - - - afakhry@chromium.org - sammiequon@chromium.org - tclaiborne@chromium.org - - The largest presentation time value in ms for a single four finger swipe to - change desks. One full swipe results in one emission of this metric; its the - largest value of Ash.Desks.PresentationTime.UpdateGesture which is emitted - multiple times during a single full swipe. Presentation time is the time it - takes from when the software recognizes the touchpad swipe to when the next - frame is displayed on the frame. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when a virtual desk is removed to specify the source of this remove - operation, i.e. whether from the close-desk button, or keyboard shortcut. - - - - - tbuckley@chromium.org - tclaiborne@chromium.org - - The number of seconds between task window activations triggered by users - clicking or tapping on a window, as recorded by the Desktop_SwitchTask user - action. Recorded on Chrome OS only. Task switches from other sources are - ignored and do not affect this metric. In other words, if a user performs - the following steps (1) click on task window 'A' (2) Alt+Tab to task 'Z'(3) - click on task window 'B', then this will result in a sample recorded for the - time delta between activating task window 'A'and 'B'. - - - - - jamescook@chromium.org - jessejames@chromium.org - cros-system-services@google.com - - The display zoom setting for the primary display, recorded on startup. - - - - - zentaro@chromium.org - cros-peripherals@google.com - - Emitted when the user chooses an option on the Display Change Dialog that is - shown when a user changes the resolution of an external display. - - - - - mcasas@chromium.org - dcastagna@chromium.org - - Whether a display has a "CTM" matrix properties that can be used - to set a color transform matrix. Recorded every time there is a display - configuration update. - - - - - mcasas@chromium.org - dcastagna@chromium.org - - This boolean keeps track if an ICC file was downloaded correctly (if true) - or a local file was reused instead. - - - - - - Removed 10/2017, replaced by Ash.DisplayColorManager.IccFileDownloaded - - mcasas@chromium.org - dcastagna@chromium.org - - This boolean keeps track if a request for an ICC for a specific product id - has been successful or not. - - - - - mcasas@chromium.org - dcastagna@chromium.org - - This boolean keeps track if a Display update (i.e. when connecting a new - one) carried valid ColorSpace information. - - - - - mcasas@chromium.org - dcastagna@chromium.org - - Whether we could parse a valid product id from a display EDID. Recorded - every time there is a display configuration update. - - - - - kuscher@google.com - wutao@chromium.org - - User-initiated action taken that affects docked windows such as docking, - undocking, minimizing, restoring, closing or just dragging a docked window. - - - - - kuscher@google.com - wutao@chromium.org - - Source (mouse, touch, keyboard or unknown) of the user-initiated action for - docked windows. - - - - - kuscher@google.com - wutao@chromium.org - - Number of all docked windows or panels including hidden or minimized. - Recorded on every user action that interacts with docked windows. - - - - - kuscher@google.com - wutao@chromium.org - - Number of large (wider than dock maximum width) windows that had to be - shrunk to get docked among the visible docked windows. Recorded on every - user action that interacts with docked windows. - - - - - kuscher@google.com - wutao@chromium.org - - Number of docked visible panels. Recorded on every user action that - interacts with docked windows. - - - - - kuscher@google.com - wutao@chromium.org - - Number of visible docked windows or panels. Recorded on every user action - that interacts with docked windows. - - - - - kuscher@google.com - wutao@chromium.org - - Time elapsed between instances of docking, undocking or any other action - affecting docked state of a window. - - - - - kuscher@google.com - wutao@chromium.org - - Width of the docked area in pixels. Recorded every time it changes after a - user window resize operation is completed. - - - - - tbarzic@chromium.org - xdai@chromium.org - - Presentation time in ms when a window is dragged from the bottom of the - shelf. Recorded when the drag action is in progress. - - - - - tbarzic@chromium.org - xdai@chromium.org - - Maximum latency of the presentation time in ms when a window is dragged from - the bottom of the shelf. Recorded when the drag action is finished. - - - - - - Removed 08/2014 in Issue 352654, and replaced by Event.GestureCreated. - - kuscher@google.com - rbyers@chromium.org - - The gesture-events recognized and dispatched by the browser gesture - recognizer. - - - - - - Removed on 01/2020, no longer useful. - - kuscher@google.com - rbyers@chromium.org - - The gesture-events recognized and dispatched for UI components owned by Ash. - For browser gestures, see Event.Touch.GestureType. - - - - - sammiequon@chromium.org - tbarzic@chromium.org - - Relative smoothness of animations when performing tablet mode homescreen - animations, recorded when the animation completes. 100% represents ideally - smooth 60 frames per second. - - - - - andrewxu@chromium.org - tbarzic@chromium.org - Gestures supported by the in-app hotseat. - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Tracks the animation smoothness for the ShelfWidget's animating background - during transitions of the hotseat to shown, extended, and hidden hotseat - states. Check Ash.HotseatWidgetAnimation.AnimationSmoothness for smoothness - of the HotseatWidget. - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Presentation time in ms of the hotseat when it changes between the hidden - and the extended state as a result of a drag action. Recorded when the drag - action is in progress. - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Maximum latency of the presentation time in ms of the hotseat when it - changes between the hidden and the extended state as a result of a drag - action. Recorded when the drag action is finished. - - - - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Tracks the animation smoothness for the bounds animation of the hotseat - widget's elements during transitions of the hotseat to shown, extended, and - hidden hotseat states. Check Ash.HotseatTransition.AnimationSmoothness for - smoothness of the shelf's animating background. - - - - - kuscher@google.com - - The type of the window which is put into immersive fullscreen. Immersive - fullscreen is entered via the F4 key. - - - - - oshima@chromium.org - mukai@chromium.org - - Time between when the size of a window changes during an interactive window - resize and the results are drawn (presented) on screen. This is recorded for - each movement of the mouse/pointer that results in a resize. - - - - - oshima@chromium.org - mukai@chromium.org - - Maximum time between when the size of a window changes during an interactive - window resize and the results are drawn (presented) on screen. This is - recorded for each movement of the mouse/pointer that results in a resize. - - - - - rsorokin@chromium.org - cros-oac@google.com - - The count of auth method switching actions in ChromeOS lock screen. - - - - - rsorokin@chromium.org - cros-oac@google.com - - The usage of different auth methods (PIN / Password / Smartlock / - Fingerprint) in ChromeOS lock screen clamshell mode. - - - - - rsorokin@chromium.org - cros-oac@google.com - - The usage of different auth methods (PIN / Password / Smartlock / - Fingerprint) in ChromeOS lock screen tablet mode. - - - - - tellier@google.com - cros-oac@google.com - - The number of incorrect passwords entered in Chrome OS login/lock screen - until the user gives up (user signs out the current session or shuts down - the device). - - - - - tellier@google.com - cros-oac@google.com - - The number of incorrect passwords entered in Chrome OS login/lock screen - until a successful attempt. - - - - - - Removed 27/05/2020, the histogram has been revised as we do not count pod - switching anymore and the metric was not recorded on shutdown. New - histogram: Ash.Login.Lock.NbPasswordAttempts.UntilFailure - - kerrnel@google.com - - The number of incorrect password entered in ChromeOS login/lock screen until - the user gives up (switch pods or user sign out the current session or - shutdown the device). - - - - - - Removed 27/05/2020, the histogram has been revised as we did not count - successful authentification on login screen and successful authentification - on lock screen wasn't recorded due to a bug. New histogram: - Ash.Login.Lock.NbPasswordAttempts.UntilSuccess - - kerrnel@google.com - - The number of incorrect password entered in ChromeOS login/lock screen until - a successful attempt. - - - - - rsorokin@chromium.org - cros-oac@google.com - - The numbers of times that users click on the shelf buttons, trays and lock - screen note on the ChromeOS lock screen. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Whether the cryptohome migration banner was shown on the Chrome OS login - screen. - - - - - rsorokin@chromium.org - cros-oac@google.com - - The numbers of times that users click on the shelf buttons and trays on the - ChromeOS login screen. - - - - - raleksandrov@google.com - cros-oac@google.com - What shelf buttons or trays are clicked in the OOBE. - - - - rrsilva@google.com - cros-oac@google.com - - The result of the PIN auto submit 'Backfill' operation. Users updating to - M86 with an existing PIN will have their preference regarding auto submit - 'backfilled' to either enabled or disabled. - - - - - - - - - anasalazar@chromium.org - newcomer@chromium.org - - Relative smoothness of animations of the navigation widget's elements, which - are the widget itself and its child views. 100% represents ideally smooth 60 - frames per second. 50% represents only 30 frames per second is achieved - during the animations. Recorded every time an animation is triggered in the - Navigation Widget. We record this metric for each element separately. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - Emitted when the Auto Night Light notification is shown. - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when the user interacts with the Auto Night Light notification to - report the state of the notification as a result of this interaction. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The type of CRTC color transorm matrix support for the currently connected - displays. Emitted when cursor compositing status is refreshed, but only when - Night Light is on. The cursor compositing status is refreshed whenever there - is a change in Night Light status or color temperature. - - - - - afakhry@chromium.org - - The selected Night Light schedule type. Emitted when the user changes the - Night Light schedule type from the Display System Settings. - - - - - afakhry@chromium.org - - The ranges in which the selected values of the Night Light color temperature - reside. Emitted when the user drags the Night Light color temperature slider - to change its value from the Display System Settings. - - - - - jamescook@chromium.org - - An upper bound on the number of windows visible to the user on the primary - display. Determined by processing the windows in increasing z-order and - counting all non-minimized windows until a maximized or fullscreen window is - processed. This metric is logged periodically every 30 minutes. - - - - - - - omrilio@chromium.org - oshima@chromium.org - - Relative smoothness of animations when closing a window, recorded when the - animation completes. 100% represents ideally smooth 60 frames per second. - - - - - - - omrilio@chromium.org - oshima@chromium.org - - Relative smoothness of animations when entering overview mode, recorded when - the animation completes. 100% represents ideally smooth 60 frames per - second. - - - - - - - omrilio@chromium.org - oshima@chromium.org - - Relative smoothness of animations when exiting overview mode, recorded when - the animation completes. 100% represents ideally smooth 60 frames per - second. - - - - - sammiequon@chromium.org - tclaiborne@chromium.org - - Maximum latency of the presentation time for scrolling the overview grid in - overview mode for a scrolling session. - - - - - sammiequon@chromium.org - tclaiborne@chromium.org - - Presentation time for scrolling the overview grid in overview mode. Each - time the grid is updated by a scroll, the time it takes to update the new - visuals onto the screen is updated. - - - - - - - omrilio@chromium.org - oshima@chromium.org - Presentation time for dragging a window in overview mode. - - - - - - omrilio@chromium.org - oshima@chromium.org - - Maximum latency of the presentation time for dragging a window in overview - mode. - - - - - amusbach@chromium.org - xdai@chromium.org - - Recorded when a drag from overview (not from the top or shelf) is completed, - and when an overview item is closed by vertically swiping or flinging (even - if you fling without dragging). - - - - - zentaro@chromium.org - baileyberro@chromium.org - - The number of windows restored in multi-display scenario, such as due to - disconnecting and reconnecting display, enabling and disabling mirror mode, - entering and leaving dock mode. Zero is not recorded. - - - - - takise@chromium.org - linben@chromium.org - How long Android PIP was used for, upon ending the session. - - - - takise@chromium.org - linben@chromium.org - - Various individiual Picture-in-picture related events. See AshPipEvents. - - - - - takise@chromium.org - linben@chromium.org - - Area of a Picture-in-picture window when ending a free-resize, as a - percentage of the area it takes up on the display it is on. - - - - - takise@chromium.org - linben@chromium.org - - Initial area of a Picture-in-picture window when beginning a free-resize, as - a percentage of the area it takes up on the display it is on. - - - - - takise@chromium.org - linben@chromium.org - - The position that a Picture-in-picture window was moved to by a user drag. - - - - - zentaro@chromium.org - baileyberro@chromium.org - - Record the delay when power button and volume down key are both pressed, - which indicates user might want to use accelerator to take screenshot. This - will help us determine the best chord delay among metrics. - - - - - - Removed 05/2019; no longer need to track this. - - sky@chromium.org - - The delta between when chrome main starts to when the Chrome OS system UI - (ash) is visible to the user (specifically the first time pixels are lit up - on the primary display showing the Chrome OS system UI). - - - - - oshima@chromium.org - wutao@chromium.org - - Relative smoothness of animations when rotating screen. 100% represents - ideally smooth 60 frames per second. 50% represents only 30 frames per - second is achieved during the animations. 0% should not happen. This metric - is recorded exactly once when the user rotates the screen. - - - - - anasalazar@google.com - mmourgos@google.com - - Tracks the number of menu items that are enabled in a shelf item's secondary - menu. This metric is only recorded when a menu item is selected. - - - - - anasalazar@google.com - mmourgos@google.com - - Tracks the index of the selected menu item in a shelf item's secondary menu. - This metric is only recorded when a menu item is selected. - - - - - tbarzic@chromium.org - gzadina@google.com - - The reason shelf navigation buttons are shown in tablet mode. The buttons - are shown when the device is in tablet mode only if certain accessibility - settings are enabled. This histogram records which accessibility setting - caused the buttons to be shown. Shown when navigation buttons visibility - changes in tablet mode, and only if HideShelfControlsInTabletMode feature is - enabled. - - - - - anasalazar@google.com - mmourgos@google.com - - The number of icons in the shelf, not including the App Launcher icon. This - metric is recorded every 30 minutes. - - - - - anasalazar@google.com - mmourgos@google.com - - The number of pinned icons in the shelf, not including the App Launcher - icon. This metric is recorded every 30 minutes. - - - - - anasalazar@google.com - mmourgos@google.com - - The number of unpinned icons in the shelf. This metric is recorded every 30 - minutes. - - - - - tengs@chromium.org - gzadina@chromium.org - - The percentage of the screen area circled by the Assistant pen. Recorded - when the "closed shape" gesture is recognized. - - - - - tengs@chromium.org - gzadina@chromium.org - - The duration of an Assistant pen gesture. Recorded at the end of every - gesture. - - - - - tengs@chromium.org - gzadina@chromium.org - - The interval between subsequent Assistant pen gestures within a session. - Session is defined as the period while the Assistant tool is enabled. - Recorded at the end of each gesture except for the first one in the session. - The interval is computed excluding the gesture duration. - - - - - tengs@chromium.org - gzadina@chromium.org - - The number of Assistant pen gestures per session. Session is defined as the - period while the Assistant tool is enabled. Recorded at the end of the - session. - - - - - tengs@chromium.org - gzadina@chromium.org - - The number of recognized Assistant pen gestures per session. Session is - defined as the period while the Assistant tool is enabled. Recorded at the - end of the session. - - - - - tengs@chromium.org - gzadina@chromium.org - - The type of the Assistant pen gesture. Recorded at the end of each gesture. - - - - - tengs@chromium.org - gzadina@chromium.org - - The length of a recognized "horizontal stroke" Assistant pen - gesture. Recorded at the and of the gesture. - - - - - tengs@chromium.org - gzadina@chromium.org - - The amount of time spent in Palette Assistant mode. Recorded when the - Assistant mode is exited. - - - - - tengs@chromium.org - gzadina@chromium.org - - The amount of time spend in Palette Laser pointer mode. Recorded when the - Laser pointer mode is exited. - - - - - tengs@chromium.org - gzadina@chromium.org - - The amount of time spend in Palette Magnify mode. Recorded when the Magnify - mode is exited. - - - - - tengs@chromium.org - gzadina@chromium.org - - Tracks the number of times a palette mode is explicitly cancelled or - switched out of. - - - - - tengs@chromium.org - gzadina@chromium.org - - Recorded every time that the palette option has been selected from the - palette that has been opened manually (not via a stylus eject event). - - - - - tengs@chromium.org - gzadina@chromium.org - - Recorded every time that the palette option has been selected from the - palette that has been opened automatically (by a stylus eject event). - - - - - tengs@chromium.org - gzadina@chromium.org - - Recorded every time that the palette option has been selected by means other - that the palette menu (e.g. stylus barrel button or a keyboard accelerator). - - - - - tbuckley@chromium.org - - The number of seconds between contiguous task switch user actions triggered - by the Shelf buttons where the user activates a different user-predictable - task. Task switches from other sources are ignored and do not affect this - metric. In other words, if a user performs the following steps (1) launch - task 'A' from the Shelf (2) Alt+Tab to task 'Z' (3) launch task 'B' from the - Shelf, then this will result in a sample recorded for the time delta between - launching tasks 'A' and 'B'. - - - - - tbuckley@chromium.org - - Tracks the amount of time between a window being minimized by the shelf and - subsequently activated. In other words this metric is only recorded if a - shelf button pressed action causes a window to be minimized and the very - next shelf button pressed action causes the same window to be activated. - - - - - wrong@chromium.org - jiameng@chromium.org - - Whether or not the user had set up a night light schedule at the time of - night light event logging. - - - - - wrong@chromium.org - jiameng@chromium.org - - The number of Bluetooth devices available at the time of Bluetooth event - logging. - - - - - kuscher@google.com - - The current state of the shelf (alignment) tracked over time by logging on a - regular basis (30 minutes), this is used instead of log in or shelf usage to - track users that do not lock/unlock or log in frequently and use a small - number of browser instances or otherwise infrequently interact with the - shelf launcher. - - - - - - - kuscher@google.com - tbarzic@chromium.org - - The current state of the shelf (alignment) when the shelf launcher is used - to launch an app/window/etc, this is used instead of log in to give data on - users that do not lock/unlock or log in frequently. - - - - - andrewxu@chromium.org - newcomer@chromium.org - - Relative smoothness of animations of the shelf icons. 100% represents - ideally smooth 60 frames per second. Recorded when shelf icon animations are - completed, including icon move, icon fade-in and icon fade-out. - - - - - amusbach@chromium.org - xdai@chromium.org - - The amount of time that the user spent in multi-display split view mode, - meaning that split view is active on more than one display. The time is - measured from when the number of displays in split view becomes more than - one to when it drops back down to one. - - - - - xdai@chromium.org - - The amount of time that the user spent in split view mode. The time is - measured from the moment a window is snapped to one side of the screen to - when split view mode is ended. - - - - - sammiequon@chromium.org - xdai@chromium.org - - Relative smoothness of animation when releasing the split view divider, - recorded when the animation completes. 100% represents ideally smooth 60 - frames per second. - - - - - - - amusbach@chromium.org - xdai@chromium.org - omrilio@chromium.org - oshima@chromium.org - - Presentation time while resizing one or two split view windows. - - - - - - - amusbach@chromium.org - xdai@chromium.org - omrilio@chromium.org - oshima@chromium.org - - Maximum latency of the presentation time while resizing one or two split - view windows. - - - - - - Removed 02/2017 due to lack of usage. - - kuscher@google.com - rbyers@chromium.org - The duration of mostly stationary long-duration touches. - - - - omrilio@chromium.org - - Maximum latency of the presentation timestamp while dragging a tab in tablet - mode. - - - - - omrilio@chromium.org - Presentation time while dragging a tab in tablet mode. - - - - omrilio@chromium.org - - Maximum latency of the presentation timestamp while dragging maximized - window in tablet mode. - - - - - omrilio@chromium.org - - Presentation time while dragging maximized window in tablet mode. - - - - - andrewxu@chromium.org - tbarzic@chromium.org - - Boolean indicating whether a swipe from hotseat on home screen resulted in a - transition to overview. - - - - - tengs@chromium.org - gzadina@chromium.org - - The visible rows displayed in the system menu's default view. Recorded each - time the menu is opened. - - - - - tengs@chromium.org - gzadina@chromium.org - - The height of the system menu divided by the height of the Ash desktop work - area; a value over 100% indicates that a portion of the system menu is not - visible to the user. Recorded each time the menu is opened. - - - - - tengs@chromium.org - gzadina@chromium.org - - The number of user-visible rows in the system menu's default view. Recorded - each time the menu is opened. - - - - - - Removed 10/2016 for Issue 616581. - - tbuckley@chromium.org - - The number of seconds between tab switches triggered by a user gesture (e.g. - Ctrl+T, Ctrl+1, tapping or clicking the tab strip, etc). - - - - - oshima@chromium.org - sammiequon@chromium.org - - Relative smoothness of animations when entering tablet mode, recorded when - the animation completes. 100% represents ideally smooth 60 frames per - second. - - - - - oshima@chromium.org - sammiequon@chromium.org - - Relative smoothness of animations when exiting tablet mode, recorded when - the animation completes. 100% represents ideally smooth 60 frames per - second. - - - - - tbuckley@google.com - - The number of seconds between contiguous task switch user actions triggered - by any of the other task switch actions that are tracked. (e.g., - Ash.Shelf.TimeBetweenNavigateToTaskSwitches, - Ash.Tab.TimeBetweenSwitchToExistingTabUserActions, - Ash.WindowCycleController.TimeBetweenTaskSwitches, - Ash.AppList.TimeBetweenTaskSwitches, - Ash.WindowSelector.TimeBetweenActiveWindowChanges, etc). Note the - Ash.AppList.TimeBetweenTaskSwitches and - Ash.Tab.TimeBetweenSwitchToExistingTabUserActions histograms were deprecated - and removed in 10/2016. - - - - - - Removed 12/2013 in r239809, and replaced by Ash.TouchDuration2. - - kuscher@google.com - The duration of a touch-sequence. - - - - - Removed 08/2014 in Issue 352654, and replaced by Event.TouchDuration. - - kuscher@google.com - rbyers@chromium.org - The duration of a touch-sequence. - - - - - Removed 08/2014 in Issue 352654, and replaced by Event.TouchMaxDistance. - - kuscher@google.com - rbyers@chromium.org - - The maximum euclidean distance in dips which a touch point has travelled - away from its starting point. Only measured for single finger gestures. - - - - - - Removed 02/2017 due to lack of usage. - - kuscher@google.com - rbyers@chromium.org - The interval between touch-move events. - - - - kuscher@google.com - rbyers@chromium.org - The distance between touch-move events. - - - - - Removed 07/2018 due to lack of usage. - - kuscher@google.com - The position of the touch-events along the X axis. - - - - - Removed 07/2018 due to lack of usage. - - kuscher@google.com - The position of the touch-events along the Y axis. - - - - - Removed 07/2018 due to lack of usage. - - kuscher@google.com - The radius of a touch event. - - - - kuscher@google.com - - The interval between the end of a touch-sequence and the start of the next - touch-sequence. - - - - - - Removed 02/2017 due to lack of usage. - - kuscher@google.com - rbyers@chromium.org - - The number of rapid touch-starts that happened within a short interval. - Logged once for each such burst group. - - - - - oshima@chromium.org - - Chrome OS only. The computed angle between the lid and the keyboard panel. - These values are imprecise and may be tens of degrees off from reality. - Reported once per hour that the system is awake, and not reported if the - system doesn't have two accelerometers. - - - - - girard@chromium.org - - The length of time that TouchView is active, for each activation. - - - - - girard@chromium.org - The proportion of time spent in TouchView during a session. - - - - girard@chromium.org - The total time that TouchView is active during a session. - - - - girard@chromium.org - The length of time between TouchView activations. - - - - girard@chromium.org - - The total time that TouchView is not active during a session. - - - - - - Removed as of 2/2018. Currently there is only one type of Wallpaper App. - - xdai@chromium.org - - The Wallpaper App that the user is using right now on Chrome OS. It's the - app that is used when the user right clicks on desktop and selects "Set - wallpaper" or when the user selects "Set wallpaper" from - chrome://settings page. This is recorded at user login. - - - - - - Removed as of 8/2018. - - tbuckley@chromium.org - - The time taken to extract colors from wallpapers. Recorded each time the - wallpaper image changes. It may contain multiple colors extracted. - - - - - - Removed as of 8/2018. - - tbuckley@chromium.org - - The time taken to extract colors from 'expensive' wallpapers. Recorded each - time the wallpaper image changes and the color extraction is expected to be - expensive, e.g. image size > 100 pixels. This includes time spent - switching threads. It may contain multiple colors extracted. - - - - - - Removed as of 6/2017. - - tbuckley@chromium.org - - Tracks the success rate for wallpaper color extraction. Recorded each time - the wallpaper image changes. - - - - - newcomer@chromium.org - tbuckley@chromium.org - - Tracks the success rate for wallpaper color extraction. Recorded each time - the wallpaper image changes for each extracted wallpaper prominent color. - - - - - xdai@chromium.org - - The custom wallpaper layout type. Recorded when the user sets a new custom - wallpaper or changes the existing custom wallpaper's layout. - - - - - - Removed as of 11/2012. Use of indices has been removed. - - kuscher@google.com - - The wallpaper index if one of the default wallpapers has been selected. - Recorded at user login. Currently only for the old wallpaper picker UI. - - - - - xdai@chromium.org - - Recorded when a new wallpaper is set, either by the built-in Wallpaper - Picker App, or by a third party App. Note the wallpaper change triggered by - Sync file system event doesn't count. - - - - - - Removed as of 04/2017 in favor of Ash.Wallpaper.ColorExtraction.Durations - and Ash.Wallpaper.ColorExtraction.UserDelay. - - tbuckley@chromium.org - - The time taken to extract colors from wallpapers. Recorded each time the - wallpaper image changes. NOTE, this measure also included the time spent - jumping between threads, thus it was deprecated in favor of - Ash.Wallpaper.ColorExtraction.Durations. - - - - - - Removed as of 8/2018. - - tbuckley@chromium.org - - The time taken to resize wallpapers. Recorded once each time the wallpaper - changes (e.g. initial wallpaper loading at boot, switching user avatar at - login screen, switching between logged in users, user selects new wallpaper, - etc). - - - - - kuscher@google.com - The wallpaper type. Recorded at user login. - - - - wutao@chromium.org - - Relative smoothness of cross fade animation when setting window bounds. 100% - represents ideally smooth 60 frames per second. 50% represents when only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when SetBoundsDirectCrossFade is - called, such as when window is maximized. - - - - - sammiequon@chromium.org - xdai@chromium.org - - When dragging a maximized window, the window will shrink to restore bounds. - Dragging the window back to the top of the screen will expand the window. - This histogram will be recorded to measure the smoothenss of the expand - animation. 100% represents ideally smooth 60 frames per second. 50% - represents when only 30 frames per second is achieved during the animations. - 0% should not happen. - - - - - sammiequon@chromium.org - xdai@chromium.org - - When dragging a maximized window, the window will shrink to restore bounds. - This histogram will be recorded to measure the smoothness of the shrink - animation. 100% represents ideally smooth 60 frames per second. 50% - represents when only 30 frames per second is achieved during the animations. - 0% should not happen. - - - - - sammiequon@chromium.org - tclaiborne@chromium.org - - Relative smoothness of hiding window animation. 100% represents ideally - smooth 60 frames per second. 50% represents when only 30 frames per second - is achieved during the animations. 0% should not happen. This metric is - recorded exactly once when AnimateHideWindowCommon is called, such as when - window is closed. - - - - - oshima@chromium.org - sammiequon@chromium.org - - Relative smoothness of snapping window animation. 100% represents ideally - smooth 60 frames per second. 50% represents when only 30 frames per second - is achieved during the animations. 0% should not happen. This metric is - recorded exactly once when a window is snapped to the left or right in - clamshell mode using the alt + [ or ] accelerator, but only if the size of - the window's bounds change. - - - - - - Removed as of 07/2019. - - wutao@chromium.org - tbuckley@google.com - - The amount of time the Alt key is held after pressing Alt+Tab to begin - cycling through windows. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - Emitted when the user ends window cycling via Alt-Tab, if and only if user - had 2 or more desks and a new window was activated, to report the distance - between the active desks before and after window cycling. A distance of 0 - means no desks switch occurred. - - - - - sammiequon@chromium.org - tclaiborne@chromium.org - xdai@chromium.org - - The number of windows in the Alt+Tab selector. Only recorded once when - cycling starts, not every time when Tab is pressed without releasing Alt. - - - - - - Removed as of 07/2019. - - wutao@chromium.org - tbuckley@google.com - - When a window is selected after pressing Alt+Tab, records that window's - position in the global MRU ordering. 1 represents the most-recently used - window, 2 represents the next most-recently used window, and so on. Recorded - when Alt+Tab cycling stops, i.e., when Alt key is released. - - - - - sammiequon@chromium.org - tclaiborne@chromium.org - xdai@chromium.org - - The number of seconds between task switches triggered by the next window and - previous window accelerator keys (ie Alt+Tab, Alt+Shift+Tab). - - - - - yjliu@chromium.org - chromeos-wmp@google.com - - Relative smoothness of showing window animation when the window cycle view - moves the next window into position when alt + tab is pressed. 100% - represents ideally smooth 60 frames per second. 50% represents when only 30 - frames per second is achieved during the animations. 0% should not happen. - - - - - - Removed 01/2020 in Issue 989794 since we are now using focus rings instead - of a highlight. The focus rings have no animations. - - yjliu@chromium.org - chromeos-wmp@google.com - - Relative smoothness of showing window animation when the highlight moves to - the next window in the window cycle view when alt + tab is pressed. 100% - represents ideally smooth 60 frames per second. 50% represents when only 30 - frames per second is achieved during the animations. 0% should not happen. - - - - - yjliu@chromium.org - chromeos-wmp@google.com - - Relative smoothness of showing window animation when the window cycle view - starts. 100% represents ideally smooth 60 frames per second. 50% represents - when only 30 frames per second is achieved during the animations. 0% should - not happen. - - - - - andrewxu@chromium.org - tbarzic@chromium.org - - The final state after window drag gesture that started from the system shelf - in tablet mode. - - - - - jdufault@chromium.org - - How long it took for the screen lock process to complete. This does not - include timeouts. - - - - - jdufault@chromium.org - - How long it took for the screen lock process to complete, for timeouts only. - - - - - - Removed 03/2019 in favor of Ash.Overview.AnimationSmoothness.Close.Clamshell - and Ash.Overview.AnimationSmoothness.Close.Tablet - - estade@chromium.org - - Relative smoothness of animations when closing a window in overview mode. - 100% represents ideally smooth 60 frames per second. - - - - - - Removed 03/2019 in favor of Ash.Overview.AnimationSmoothness.Enter.Clamshell - and Ash.Overview.AnimationSmoothness.Enter.Tablet - - estade@chromium.org - - Relative smoothness of animations when entering overview mode. 100% - represents ideally smooth 60 frames per second. - - - - - - Removed 03/2019 in favor of - Ash.Overview.AnimationSmoothness.Exit.ClamshellMode and - Ash.Overview.AnimationSmoothness.Exit.TabletMode - - estade@chromium.org - - Relative smoothness of animations when exiting overview mode. 100% - represents ideally smooth 60 frames per second. - - - - - flackr@chromium.org - - The number of times the arrow keys are pressed in overview mode per session, - i.e. between bringing up overview mode and ending it. This is only measured - for the sessions that end by selecting a window with the enter key. - - - - - - Removed as of 06/2014. No longer relevant since alt-tab switching was - separated from WindowSelector. - - flackr@chromium.org - kuscher@google.com - - The amount of time the Alt key is held after pressing Alt+Tab to begin - cycling through windows. - - - - - flackr@chromium.org - kuscher@google.com - - The number of items (single windows or groups of windows such as panels) in - the overview mode, present at the start of each session. - - - - - flackr@chromium.org - - The number of items showing in overview mode at the moment when an item is - selected or when selection is canceled. Only recorded if the text filtering - textfield contains a non-empty string. - - - - - flackr@chromium.org - - The ratio between the arrow key presses and the number of overview items, - expressed as a percentage for a single session. - - - - - flackr@chromium.org - - The number of items closed from the window overview for a single session. - - - - - estade@chromium.org - tbuckley@chromium.org - - When a window is selected in overview mode, records that window's position - in the global MRU ordering. 1 represents the most-recently used window, 2 - represents the next most-recently used window, and so on. - - - - - flackr@chromium.org - - The length of the string entered into the text filtering textfield at the - moment when an item is selected or when selection is canceled. - - - - - flackr@chromium.org - - The number of times the text filtering textfield has had all of its text - removed within a single overview mode session. Measured from the time - overview mode is invoked to when an item is selected or when selection is - canceled. - - - - - tbuckley@chromium.org - - The amount of time between endings of overview mode sessions which were - caused by the user selecting a window which was not previously active. Only - recorded on the second and later times after startup that the user selected - a window which was not previously active. - - - - - flackr@chromium.org - kuscher@google.com - - The amount of time between uses of overview mode, recorded when overview - mode is entered. Only recorded on the second and later times after startup - that the user entered overview mode. - - - - - flackr@chromium.org - kuscher@google.com - - The amount of time spent in overview mode. Overview mode is engaged by - pressing the overview button. The time is measured from the moment the - windows begin animating to a thumbnail size preview to when a window is - selected or selection is canceled. - - - - - flackr@chromium.org - - The amount of time spent in overview mode when text filtering is used. The - time is measured from the moment the windows begin animating to a thumbnail - size preview to when a window is selected or selection is canceled. Only - recorded if the text filtering textfield contains a non-empty string. - - - - - yichenz@chromium.org - chromeos-wmp@google.com - - Presentation time in ms when a tab is dragged in clamshell mode. Each time - the tab is dragged within a display, the time it takes to present the new - frame on screen is recorded. - - - - - yichenz@chromium.org - chromeos-wmp@google.com - - Maximum presentation time recorded during the tab dragging session. - - - - - xiaohuic@chromium.org - croissant-eng@chromium.org - - The number of times Assistant better onboarding buttons are clicked. - - - - - xiaohuic@chromium.org - croissant-eng@chromium.org - - The number of times Assistant better onboarding UI is shown. The UI has a - few different modes recorded in the enum. - - - - - xiaohuic@chromium.org - meilinw@chromium.org - - The number of times buttons on Assistant UI (e.g., minimize) are clicked. - - - - - - Removed as of 01/2020. - - wutao@chromium.org - - Relative animation smoothness of resizing assistant container window. 100% - represents ideally smooth 60 frames per second. 50% represents when only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded when the container window resizing is finished. - - - - - updowndota@chromium.org - xiaohuic@chromium.org - - Among eligible users, whether the user has the Assistant context (related - info) enabled. Recorded once for every UMA upload. The set of eligible users - includes all users with profiles that can allow Assistant service to be - enabled (AssistantAllowedState is limited by locale, policy, etc). - - - - - meilinw@chromium.org - xiaohuic@chromium.org - - Counts the number of times Dsp hotword gets detected in each status, to help - capture the hotword false acceptance rate. - - - - - xiaohuic@chromium.org - meilinw@chromium.org - - Record the Assistant entry point where Assistant UI becomes visible. - - - - - xiaohuic@chromium.org - meilinw@chromium.org - - Record the Assistant exit point where Assistant UI becomes invisible. - - - - - updowndota@chromium.org - croissant-eng@chromium.org - - Counts the number of times user click the hotword enable notification to - open Assistant settings. - - - - - xiaohuic@chromium.org - croissant-eng@chromium.org - - Record the Assistant interaction resolution code. It indicates how the - Assistant server interpreted a particular query and decision on the state, - e.g. if the conversation is normal or timed out or ended with other errors. - - - - - updowndota@chromium.org - croissant-eng@chromium.org - - Amount of time between get settings request and response. The request will - be sent for each time the Assistant OptIn Flow is triggered to get string - texts from the server. - - - - - updowndota@chromium.org - croissant-eng@chromium.org - - Number of times that the loading timeout triggers. The loading timeout is - set by the Assistant OptIn Flow loading screen, which shows up during the - server string texts and webviews are pending. - - - - - updowndota@chromium.org - croissant-eng@chromium.org - Record the status of the Assistant opt-in flow. - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a click on a proactive suggestions card by the user. This histogram - is recorded for every click event while derivative metrics are recorded for - splicing by category, index, and veId only when those respective attributes - are known. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for a proactive suggestions card that was clicked - by the user. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records the index for a proactive suggestions card within its list that was - clicked by the user. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records the VE ID for a proactive suggestions card that was clicked by the - user. - - - - - - Removed 11/2018 because a need was discovered for a non-boolean value. - Superseded by Accessibility.Android.AnimationsEnabled2. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records an attempt to show a proactive suggestion to the user for the first - time. - - - - - - Associated with an experimental feature which was removed in M85. - - - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for an attempt to show a proactive suggestion to - the user for the first time. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a result of having shown a proactive suggestion to the user for the - first time. - - - - - - Associated with an experimental feature which was removed in M85. - - - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user for the first time. - - - - - - Removed 11/2018 because a need was discovered for a non-boolean value. - Superseded by Accessibility.Android.AnimationsEnabled2. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a result for a proactive suggestions server request. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for a proactive suggestions server request that - resulted in error. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for a proactive suggestions server request that - resulted in a successful response containing content. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for a proactive suggestions server request that - resulted in a successful response that did not contain content. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records an attempt to reshow a proactive suggestion to the user that has - already been seen. - - - - - - Associated with an experimental feature which was removed in M85. - - - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for an attempt to reshow a proactive suggestion - to the user that has already been seen. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a result of having reshown a proactive suggestion to the user that - has already been seen. - - - - - - Associated with an experimental feature which was removed in M85. - - - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having reshown a proactive suggestion to the - user that has already been seen. - - - - - - Replaced in M80 by Assistant.ProactiveSuggestions.FirstShowAttempt and - Assistant.ProactiveSuggestions.ReshowAttempt. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records an attempt to show a proactive suggestion to the user. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowAttempt.AbortedByDuplicateSuppression.ByCategory - and - Assistant.ProactiveSuggestions.ReshowAttempt.AbortedByDuplicateSupression.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for an attempt to show a proactive suggestion to - the user that was aborted due to duplicate suppression. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowAttempt.Success.ByCategory and - Assistant.ProactiveSuggestions.ReshowAttempt.Success.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for an attempt to show a proactive suggestion to - the user that was successful. - - - - - - Replaced in M80 by Assistant.ProactiveSuggestions.FirstShowResult and - Assistant.ProactiveSuggestions.ReshowResult. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a result of having shown a proactive suggestion to the user. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowResult.Click.ByCategory and - Assistant.ProactiveSuggestions.ReshowResult.Click.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user that resulted in a click. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowResult.CloseByContextChange.ByCategory. - and - Assistant.ProactiveSuggestions.ReshowResult.CloseByContextChange.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user that resulted in being closed due to a change in context. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowResult.CloseByTimeout.ByCategory and - Assistant.ProactiveSuggestions.ReshowResult.CloseByTimeout.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user that resulted in being closed due to timeout. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowResult.CloseByUser.ByCategory and - Assistant.ProactiveSuggestions.ReshowResult.CloseByUser.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user that resulted in being closed by the user. - - - - - - Replaced in M80 by - Assistant.ProactiveSuggestions.FirstShowResult.Teleport.ByCategory and - Assistant.ProactiveSuggestions.ReshowResult.Teleport.ByCategory. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for having shown a proactive suggestion to the - user that resulted in teleportation directly to a single result. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records an impression of a proactive suggestions view seen by the user. This - histogram is recorded for every impression event while derivative metrics - are recorded for splicing by category and veId only when those respective - attributes are known. Note that this histogram is primarily used with - Assistant.ProactiveSuggestions.CardClick to give an idea of CTR. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records a content category for a proactive suggestions view that was seen by - the user. Note that this histogram is primarily used with - Assistant.ProactiveSuggestions.CardClick.ByCategory to give an idea of CTR. - - - - - - Associated with an experimental feature which was removed in M85. - - xiaohuic@chromium.org - dmblack@google.com - croissant-eng@chromium.org - - Records the VE ID for a proactive suggestions view that was seen by the - user. Note that this histogram is primarily used with - Assistant.ProactiveSuggestions.CardClick.ByVeId to give an idea of CTR. - - - - - xiaohuic@chromium.org - meilinw@chromium.org - Number of queries fired for each entry point. - - - - xiaohuic@chromium.org - meilinw@chromium.org - The Assistant query response type. - - - - xiaohuic@chromium.org - meilinw@chromium.org - - The source of Assistant query (e.g. dialog plate text field, voice input). - Recorded when the query is committed. - - - - - xiaohuic@chromium.org - meilinw@chromium.org - - Among eligible users, whether the user has the Assistant service enabled. - Recorded once for every UMA upload. The set of eligible users includes all - users with profiles that can allow Assistant service to be enabled - (AssistantAllowedState is limited by locale, policy, etc). - - - - - xiaohuic@chromium.org - jeroendh@google.com - - Amount of time between when the Assistant service is launched, and when the - Assistant back-end signals it is ready to process queries. - - - - - updowndota@chromium.org - Amount of time spent in starting Assistant service. - - - - meilinw@chromium.org - xiaohuic@chromium.org - - For each attempt to set the hotword locale for a DSP device, counts whether - the attempt succeeded. - - - - - wylieb@chromium.org - fgorski@chromium.org - - (Android only) Reports user eligibility for the feature, but ignores if the - feature is enabled. The criteria includes: locale, agsa version and - available memory. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of DnsAttempts before DnsTransaction completes with failure. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of DnsAttempts before DnsTransaction completes successfully. - - - - - pauljensen@chromium.org - mef@chromium.org - - Whether DnsConfigService::OnConfigChange actually corresponded to a change - in DnsConfig. - - - - - pauljensen@chromium.org - mef@chromium.org - - Duration of time between calls to DnsConfigService::InvalidateConfig. - - - - - pauljensen@chromium.org - mef@chromium.org - Duration of time spent parsing DnsConfig. - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of results of parsing DnsConfig in DnsConfigServicePosix. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - Whether DnsConfig was parsed successfully. - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of results of parsing DnsConfig in DnsConfigServiceWin. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - Whether the first valid DnsConfig included a rogue nameserver. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Counts of specific error codes returned by DnsTask if a subsequent ProcTask - succeeded, at the end of a streak of failures after which the DnsClient was - disabled. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - TRUE counts the events when a valid DnsConfig is received and used to enable - DnsClient, while FALSE counts the events when DnsClient is disabled after a - series of successful fallbacks from DnsTask to ProcTask. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time spent by ProcTask in failing fallback resolutions. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time spent by ProcTask in successful fallback resolutions. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Whether there was a valid DNS configuration at the start of a job which - eventually completed successfully. - - - - - pauljensen@chromium.org - mef@chromium.org - Whether DnsHosts were parsed successfully. - - - - pauljensen@chromium.org - mef@chromium.org - - Whether DnsConfigService::OnHostsChange actually corresponded to a change in - DnsHosts. - - - - - pauljensen@chromium.org - mef@chromium.org - - Duration of time between calls to DnsConfigService::InvalidateHosts. - - - - - pauljensen@chromium.org - mef@chromium.org - Duration of time spent parsing DnsHosts. - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of results of parsing DnsHosts in DnsConfigServiceWin. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - The size of the HOSTS file observed before each attempt to parse it. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). Includes only Jobs which had - priority HIGHEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). Includes only Jobs which had - priority IDLE when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). Includes only Jobs which had - priority LOW when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). Includes only Jobs which had - priority LOWEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (using DnsClient). Includes only Jobs which had - priority MEDIUM when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). Includes only Jobs which had priority HIGHEST - when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). Includes only Jobs which had priority IDLE when - started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). Includes only Jobs which had priority LOW when - started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). Includes only Jobs which had priority LOWEST when - started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (using DnsClient). Includes only Jobs which had priority MEDIUM when - started. - - - - - - Removed as of 4/2016. - - mgersh@chromium.org - - Type of nameservers in the DNS config, recorded each time the config is read - by the DNSConfigService. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Counts of results of parsing addresses out of DNS responses in successful - DnsTransactions. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The source of the async DNS preference's default. Logged at startup, when - the IO thread is created. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The source of the async DNS preference's value. Logged at startup, when the - IO thread is created. - - - - - - Removed as of 12/2018. - - robpercival@chromium.org - - The DNS response rcode - (https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6). - Logged when a DnsTransaction finishes an attempt at a DNS record lookup. It - may make multiple attempts - the rcode of each attempt will be logged. No - logging will occur for attempts that do not obtain a response from a DNS - server. - - Only DNS record lookups performed by the internal DNS resolver - ("AsyncDNS") will have their rcode logged. Lookups performed by - the system resolver will not have their rcode logged. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskError. - - mgersh@chromium.org - - Counts of specific error codes returned by DnsTask if a subsequent ProcTask - succeeded. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskFail. - - mgersh@chromium.org - - Duration of time taken by DnsTask in resolutions that failed. Excludes time - spent in the subsequent fallback. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - Counts of the overall results of using asynchronous DNS in HostResolverImpl. - This only includes jobs started with valid DNS configuration and excludes - synchronous resolutions (as IP literals, from cache, and from HOSTS). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. - - mgersh@chromium.org - - Duration of time taken by DnsTask in resolutions that succeeded. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. - - mgersh@chromium.org - - Same as AsyncDNS.ResolveSuccess, but limited to pure IPv4 lookups. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. - - mgersh@chromium.org - - Same as AsyncDNS.ResolveSuccess, but limited to pure IPv6 lookups. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. - - mgersh@chromium.org - - Same as AsyncDNS.ResolveSuccess, but limited to IPv4/IPv6 lookups. - - - - - pauljensen@chromium.org - mef@chromium.org - - Count of servers in DnsConfig. Recorded on every new DnsSession, which is - created on DNS change. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Index in DnsConfig of the failing server, recorded at the time of failure. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of server failures after network change before first success in the - DnsSession. Recorded at the time of first success. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of server failures after success until the end of the session. Server - has reported success at some point during the session. Recorded at the end - of the DnsSession. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of server failures before success. This is NOT the first success in - the DnsSession. Recorded at the time of success. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Count of server failures without success until the end of the session. - Server has never reported success during the DnsSession. Recorded at the end - of the DnsSession. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The current server is "good" and does not have to be skipped. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in failing calls to AddressSorter in dual-stack - resolutions using DnsTask. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in successful calls to AddressSorter in dual-stack - resolutions using DnsTask. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - The number of names from the search name list consumed during a successful - transaction (QTYPE A only). - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - The number of names left on the search name list at the end of a successful - transaction (QTYPE A only). - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - The number of names on the search name list at the start of a transaction - (QTYPE A only). - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by DnsTCPAttempt in failed attempts. Excludes - timeouts. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by DnsTCPAttempt in successful attempts. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Difference between RTT and timeout calculated using Histogram algorithm. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Difference between timeout calculated using Histogram algorithm and RTT. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Difference between RTT and timeout calculated using Jacobson algorithm. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Difference between timeout calculated using Jacobson algorithm and RTT. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time that would be spent waiting for lost request using - Histogram algorithm. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time that would be spent waiting for lost request using Jacobson - algorithm. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.TotalTime. - - mgersh@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Excludes speculative requests. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.TotalTime_speculative. - - mgersh@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Speculative requests only. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in failing DnsTransactions. This includes server - failures, timeouts and NXDOMAIN results. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in successful DnsTransactions. This includes all - NOERROR answers, even if they indicate the name has no addresses or they - cannot be parsed. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Same as AsyncDNS.TransactionSuccess but limited to A query type. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Same as AsyncDNS.TransactionSuccess but limited to AAAA query type. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - TTL of the resolved addresses, as in the response received from the server. - For results served from local cache, the TTL is from the original response. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by DnsUDPAttempt in failed attempts. Excludes - timeouts. - - - - - - Removed as of 12/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by DnsUDPAttempt in successful attempts. Includes - responses arriving after timeout, if multiple attempts are allowed. - - - - - pauljensen@chromium.org - mef@chromium.org - - Duration of time since the last empty config result to the time a non-change - OnConfigChange is received. - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of time since the last empty config result to the time a non-change - OnHostsChange is received. - - - - - ericorth@chromium.org - src/net/OWNERS - - The result of DnsConfigService watch. Counts STARTED on every initialization - and FAILED_* on any failure. - - - - - jbauman@chromium.org - - Whether the browser compositor uses GPU or the software renderer. - - - - - alemate@chromium.org - oshima@chromium.org - - The amount of time spent painting a WebContents frame when a window switches - from occluded to visible state. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to authenticate a user to an Active Directory domain. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - Result from automatic background machine password renewal. - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from automatic background ticket-granting-ticket renewal. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result of an attempt to get an Active Directory user's Kerberos - ticket-granting-ticket and configuration data. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result of an attempt to get the status of an Active Directory user's - Kerberos ticket, password and account. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to join a machine to an Active Directory domain. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to fetch device policy from an Active Directory - domain and store it on disk. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to fetch user policy from an Active Directory domain - and store it on disk. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of times 'kinit' failed until the next try succeeded or the method - gave up because a maximum number of tries was exceeded. 'kinit' is run for - Active Directory enrolled devices during user authentication and device - policy fetch. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of times 'smbclient' failed until it the next try succeeded or the - method gave up because a maximum number of tries was exceeded. 'smbclient' - is run for Active Directory enrolled devices during policy fetch. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - The Kerberos encryption types used while succesfully authenticating an user. - This value comes from the DeviceKerberosEncryptionTypes policy. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - The Kerberos encryption types used while succesfully joining an Active - Directory domain. This value comes from the advanced settings of the - domainjoin screen. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of group policy objects attached to a specific user or machine on an - Active Directory domain. This value is recorded when user or device policy - is fetched from an Active Directory server. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to authenticate a user to an Active Directory domain. - The value is recorded no matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to get the Kerberos ticket-granting-ticket and - configuration data of an Active Directory user. The value is recorded no - matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to get status information of an Active Directory user. - The value is recorded no matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to join a machine to an Active Directory domain. Domain - join is part of the Active Directory enrollment process. The value is - recorded no matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to fetch device policy from an Active Directory domain - and store it on disk. The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to fetch user policy from an Active Directory domain - and store it on disk. The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'kinit' (request Kerberos ticket-granting- - ticket). TGTs are requested regularly for accessing services on Active - Directory domains. The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'klist' (print Kerberos ticket-granting-ticket - information). The command reveals a TGT's lifetime, which is used to - determine TGT status in GetUserStatus() called periodically by Chrome. The - value is recorded no matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'kpasswd' (change Active Directory password). - The command is used to change the machine account password. By default, it - is run every 30 days by the AuthPolicy daemon. The value is recorded no - matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'net ads gpo list' (list Active Directory group - policy objects). The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'net ads info' (query Active Directory - information). The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'net ads join' (join machine to an Active - Directory domain). The value is recorded no matter if the operation was - successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'net ads search' (query information about an - Active Directory account). The value is recorded no matter if the operation - was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'net ads workgroup' (query Active Directory - workgroup). The value is recorded no matter if the operation was successful - or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to call 'smbclient' (download policy from an Active - Directory domain). The value is recorded no matter if the operation was - successful or not. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the frequency of user interactions with the Autocheckout bubble, - which prompts users to invoke Autocheckout on supported websites. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the frequency of final states reached in Autocheckout buy flow. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - The state of the Autocheckout dialog when it was dismissed. - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user submitted the Autocheckout - dialog and when the Autocheckout flow, or filling process, concluded. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user submitted the Autocheckout - dialog and when the Autocheckout flow concluded, in cases where the flow - failed. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user submitted the Autocheckout - dialog and when the Autocheckout flow concluded, in cases where the flow - succeeded. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - The initial state of a user that's interacting with a freshly shown - Autocheckout dialog. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - User interactions with the Autofill popup shown while filling an - Autocheckout dialog. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the frequency of security warnings and errors in the Autocheckout - dialog. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the duration for which an Autocheckout dialog was shown. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the duration for which an Autocheckout dialog was shown, in cases - where the user ended up canceling out of the dialog. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the duration for which an Autocheckout dialog was shown, in cases - where the user ended up accepting the dialog. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures how users are interacting with the Autocheckout dialog UI. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the duration of time it takes for the Autocheckout UI to be - actionable by the user after it is shown. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the frequency of errors in communicating with the Google Online - Wallet server. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the frequency of required user actions returned by the Google - Online Wallet server. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures time taken to download the Autocheckout whitelist file. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures time taken to download the Autocheckout whitelist file in case the - download was failed. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Measures time taken to download the Autocheckout whitelist file in case the - download was succeeded. - - - - - seblalancette@chromium.org - - Logged when the Autocomplete Retention Policy cleaned up expired entries. - Expired entries are entries that haven't been used in the last 14 months. - - - - - seblalancette@chromium.org - - Logged when users select Autocomplete entries in the dropdown, this - histogram captures the number of days that have passed since the selected - autocomplete entry was last used. I.e., the distribution of time between - uses of an "active" autocomplete entry. - - - - - seblalancette@chromium.org - - Autocomplete events recorded when the user interacts with suggestions served - from Autocomplete. - - - - - tbansal@chromium.org - ryansturm@chromium.org - chrome-omnibox-team@google.com - jdonnelly@chromium.org - - Type of AutocompleteMatch. Recorded every time the autocomplete action - predictor in omnibox triggers a preresolve, or a preconnect. - - - - - tbansal@chromium.org - - Every time we calculate the confidence for a URL to determine if it should - be prerendered, we track the URL and confidence calculated. When an Omnibox - navigation happens, if we calculated a confidence for that URL, a count is - incremented for the confidence that was calculated. This histogram is then a - histogram of counts that relates the number of correctly predicted URLs to a - confidence value. By comparing that number to the - AutocompleteActionPredictor.NavigationCount and - Prerender.OmniboxNavigationsUsedPrerenderCount histograms, it's possible to - determine the effect of changing the confidence threshold on the accuracy of - prerendering prediction. - - - - - tbansal@chromium.org - - The distribution of network actions recommended by the - AutocompleteActionPredictor. A network action can be one of the enumerated - AutocompleteActionPredictor::Action values: PRERENDER, PRECONNECT, or NONE. - The AutocompleteActionPredictor recommends one of these based on a - confidence score for a given URL and user-entered text pair. - - - - - tbansal@chromium.org - - The distribution of confidence ratings. The AutocompleteActionPredictor uses - a heuristic to calculate a confidence score given a URL and user-entered - text pair. It is in the range [0,1] and is mapped on to a recommended - action, one of the enumerated AutocompleteActionPredictor::Action values: - PRERENDER, PRECONNECT or NONE. This is the distribution of those scores - multiplied by 100. - - - - - tbansal@chromium.org - chrome-omnibox-team@google.com - jdonnelly@chromium.org - - Trackes the number of times something is added, removed, or deleted from the - AutocompleteActionPredictor backing database. - - - - - tbansal@chromium.org - - The distribution of row counts for the AutocompleteActionPredictorDatabase. - Each row contains information regarding the user's Omnibox use history. - - - - - tbansal@chromium.org - chrome-omnibox-team@google.com - jdonnelly@chromium.org - - A boolean that indicates if the autocomplete suggestion under consideration - by the AutocompleteActionPredictor was found in the database. This gives an - upper bound on the fraction of suggestions it is possible to calculate a - confidence for, and thus an upper bound on the fraction of suggestions that - can be prerendered. - - - - - tbansal@chromium.org - - The number of navigations triggered by the Omnibox and seen by the - AutocompleteActionPredictor. This triggers when the Omnibox is showing - Autocomplete results to the user and they select one with the mouse or by - pressing enter. - - - - - - Removed as of 2/2016. - - jinsukkim@chromium.org - - Whether the text encoding auto detection logic was attempted for a web page. - The logic is triggered when the parser fails to find the encoding method - from other signals such as http header, meta tag, BOM, etc. - - If the logic successfully detects a new encoding method which is different - from the default one, the result is reported through - AutodetectEncoding.Detected with the encoding method (see below). Otherwise - - i.e. detection logic somehow fails to work for the page or the detected - one is same as the default - no result is reported. - - - - - - Removed as of 2/2016. - - jinsukkim@chromium.org - - The number of web pages whose encoding method is found by the auto detection - logic. Grouped by the encoding methods defined in EncodingMethod. - - - - - jsaul@google.com - chrome-autofill@google.com - - Tracks whether Profile (Address) Autofill is enabled on page load for a page - containing forms. - - - - - jsaul@google.com - chrome-autofill@google.com - - Tracks whether Profile (Address) Autofill is enabled when Chrome launches. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - Whether an attempt to access the Mac AddressBook was skipped because doing - so would incorrectly cause the appearance of the permissions dialog. This - happens when Chrome auto-update changes the binary on disk before the first - AddressBook access attempt. - - - - - - Removed as of 8/2015. - - isherman@chromium.org - - Whether the Mac AddressBook was available on an attempt to read data from - it. - - - - - - Removed as of 8/2015. - - isherman@chromium.org - - Whether the Mac AddressBook was available on the *first* attempt to read - data from it. This is only recorded once per Chrome profile. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of unverified autofill addresses deleted because they have not - been used for a long time, and are not used as billing addresses of valid - credit cards. Note the deletion only happens once per major version upgrade. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of address suggestions not shown in the Autofill popup because - they have not been used recently enough. Note that suppression only applies - when the user has not typed any text into the field. If any text is in the - field, all matching addresses are displayed, regardless of how recently they - have been used. - - - - - koerber@google.com - battre@chromium.org - - Each country can require different fields (ZIP code, state, city) to exist - for an address to be valid. This histogram logs which mandatory fields were - missing in a submitted address form. - - - - - koerber@google.com - battre@chromium.org - - Logs whether the individual requirements for importing an address profile - are met at form submission time. - - - - - koerber@google.com - battre@chromium.org - - Logs the overall status of a profile import attempt on form submission time. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of address suggestions shown in the Autofill popup. - - - - - schwering@google.com - chrome-autofill@google.com - - Records at submission time for each autofilled field with autocomplete != - off whether the user edited the autofilled field value or not. - - - - - schwering@google.com - chrome-autofill@google.com - - Records for each submitted form whether the user accepted the suggestion to - fill values and the triggering field has autocomplete != off. This is - counted as 'yes' if the user accepted such a suggestion at any time, - regardless whether other suggestions were ignored or whether the accepted - suggestion was reverted afterwards. - - - - - schwering@google.com - chrome-autofill@google.com - - Records at submission time for each autofilled field with autocomplete = off - whether the user edited the autofilled field value or not. - - - - - schwering@google.com - chrome-autofill@google.com - - Records for each submitted form whether the user accepted the suggestion to - fill values and the triggering field has autocomplete = off. This is counted - as 'yes' if the user accepted such a suggestion at any time, regardless - whether other suggestions were ignored or whether the accepted suggestion - was reverted afterwards. - - - - - michaelbai@chromium.org - Whether autocomplete is enabled. - - - - michaelbai@chromium.org - Whether an autocomplete query is created for a field. - - - - michaelbai@chromium.org - Whether there is any suggestions for an autocomplete query. - - - - - Removed as of 6/2015, replaced by Autofill.ProfileActionOnFormSubmitted. - - sebsg@chromium.org - - Whether a new Autofill profile was created automatically. In the - "false" case, an existing profile was used (and possibly updated). - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - Tracks the time it takes to fetch the full PAN of a credit card once user - successfully authenticates using WebAuthn. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - Tracks the number of times Chrome made a GetDetailsForGetRealPan call. A - preflight call is only made when card suggestions are shown, and can only - happen when the user has server cards and is eligible for WebAuthn. - - As a percentage of the number of times card suggestions are shown, which is - tracked under Autofill.FormEvents.CreditCard, this metric provides an - estimate for the potential reach for the Autofill Better Auth project. - Moreover, this acts as a baseline value for other metrics in this project. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - Tracking the latency of a GetDetailsForGetRealPan call to Payments servers. - This duration should be comparable to that of Autofill.UnmaskPrompt.Duration - and should ideally stay under 500 ms in order for the user to autofill their - credit card without experiencing much friction. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - If the user is definitely opted-in to the new auth flow, Payments sends a - list of instrument IDs in the GDFGRP call, and Chrome makes the final call - on whether CVC or WebAuthn should be shown. Tracks which authentication - method was prompted. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - Tracks when a user completes each step in a card unmasking flow per - authentication type. This will provide a relative conversion rate for each - authentication type. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - Tracks when users opt-in either from the settings page or from a checkout - flow, making an UpdateAutofillUserPreference call. For each call to - payments, logs if the call was made in order to verify an existing - credential, to create a new credential, or to fetch a challenge. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - Logs the number of times the opt-in promo to use FIDO authentication for - card unmasking has been shown. Only applicable on Desktop. - - This is useful when compared to Autofill.BetterAuth.OptInPromoUserDecision, - to see what percentage of users are interacting with the dialog. Also, when - an opted-out user receives the preflight call before selecting a card (which - is recorded by the first bucket in - Autofill.BetterAuth.UserPerceivedLatencyOnCardSelection.OptedOut), then the - promo should eventually show if the user selects a masked card and - successfully authenticates through CVC. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - Tracks the user response to the opt-in promo for using FIDO authentication - for card unmasking. The user can either accept the promo and proceed to - perform user-verification, can decline the promo immediately, or first - accept the promo but then decline while the challenge is being fetched. Only - applicable on Desktop. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - Tracks the number of times UpdateAutofillUserPreference has been called with - the intention of opting out from FIDO authentication using the toggle switch - on the payments section on the settings page. - - This will be useful when compared to values in - Autofill.BetterAuth.OptInCalled to give an idea of what percentage of users - decide to opt-out. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - The GetDetailsForGetRealPan call is made when card suggestions are shown. - This metric tracks whether the response is received before or after a card - is chosen by the user. For an opted-in user, a late response would imply - perceived latency. For an opted-out user, a late response would imply that - opt-in may not have been offered. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - The GetDetailsForGetRealPan call is made when card suggestions are shown. - This metric logs the duration of the perceived latency when the response for - this call is received after a card is chosen by an opted-in user. After - waiting a set number of seconds without receiving a response, Chrome will - fall back to CVC authentication. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - The GetDetailsForGetRealPan call is made when card suggestions are shown. If - an opted-in user selects a card before the response is returned, latency is - perceived. Given that the user perceives latency, this metric logs whether - the request timed out and fell back to CVC or if the request was completed - and continued to WebAuthn. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - Tracks how long it takes to check that the user is verifiable through - WebAuthn's IsUserVerifiablePlatformAuthenticatorAvailable() call. This check - is done before deciding to make a GetDetailsForGetRealPan call to Payments. - - - - - jsaul@google.com - manasverma@google.com - autofill-auth-team@google.com - - - - This metric tracks the result of the WebAuthn prompt when the user attempts - to either opt-in for FIDO authentication or unmask a card using FIDO - authentication. - - - - - - Removed after M78. - - jsaul@google.com - siyua@chromium.org - payments-autofill-team@google.com - - Tracks whether UKM logging is enabled for the page in the Autofill. - - - - - jsaul@google.com - siyua@chromium.org - payments-autofill-team@google.com - - Events tracking the usage of the cardholder name fix flow prompt. This - prompt is triggered whenever cardholder name must be explicitly requested - from the user in order to upload the card to Google Payments. - - - - - jsaul@google.com - siyua@chromium.org - payments-autofill-team@google.com - - - - Records the length of CVCs sent to Payments when making card unmask calls, - to help determine if blank or invalid length CVCs are being sent. - - - - - - Removed as of 2/2016, replaced by Autofill.CardUploadDecisionMetric. - - jdonnelly@chromium.org - - Whether upload was offered upon detecting a form submission with credit card - data and a reason if it wasn't. - - - - - - Removed as of 5/2017, replaced by Autofill.CardUploadDecisionMetric. - - jdonnelly@chromium.org - - Whether upload was offered upon detecting a form submission with credit card - data and a detailed reason if it wasn't. - - - - - jsaul@google.com - siyua@chromium.org - payments-autofill-team@google.com - - Whether upload was offered upon detecting a form submission with credit card - data, a detailed reason if upload was offered even with some missing fields - and detailed reasons if it wasn't. - - - - - aneeshali@google.com - jsaul@google.com - - Detailed reasons why (or why not) card upload was enabled. When a user - submits a form, this check is triggered to decide whether to ask the user if - she wants to upload the card. - - - - - - Removed as of 3/2011, replaced by Autofill.CreditCardInfoBar. - - Please list the metric's owners. Add more owner tags as needed. - The Autofill credit card info bar was accepted. - - - - - Removed as of 3/2011, replaced by Autofill.CreditCardInfoBar. - - Please list the metric's owners. Add more owner tags as needed. - The Autofill credit card info bar was denied. - - - - jsaul@google.com - chrome-autofill@google.com - - Tracks whether Credit Card Autofill is enabled on page load for a page - containing forms. - - - - - jsaul@google.com - chrome-autofill@google.com - - Tracks whether Credit Card Autofill is enabled when Chrome launches. - - - - - battre@chromium.org - chrome-autofill@google.com - - The relative frequency with which users accept, deny, or ignore the Autofill - credit card assisted filling infobar prompt. - - - - - battre@chromium.org - jsaul@google.com - chrome-autofill@google.com - - The relative frequency with which users accept, deny, or ignore the Autofill - credit card info bar prompt. - - - - - battre@chromium.org - jsaul@google.com - chrome-autofill@google.com - - The number of credit card deleted during a major version upgrade because - they have not been used recently enough and are expired. - - - - - battre@chromium.org - jsaul@google.com - chrome-autofill@google.com - - The number of credit card suggestions not shown in the Autofill popup - because they have not been used recently enough and are expired. Note that - suppression only applies when the user has not typed any text into the - field. If any text is in the field, all matching cards are displayed, - regardless of how recently they have been used and their expiration status. - - - - - - Was replaced by the AutofillDoNotUploadSaveUnsupportedCards feature in M75. - Removed 2019/07. - - jsaul@google.com - - When a credit card is not allowed to be offered upload save due to its - network, logs what the card network was. - - - - - siyua@chromium.org - jsaul@google.com - - Records when credit card upload provides feedback on its status to the user. - - - - - battre@chromium.org - chrome-autofill@google.com - - Logs the number of days that have passed since the credit card was last - used. - - - - - battre@chromium.org - chrome-autofill@google.com - - Logged at the time of autofill address use, this histogram captures the - number of days that have passed since the address was last used. I.e., the - distribution of time between uses of an "active" autofill address. - - - - - battre@chromium.org - chrome-autofill@google.com - - - - Logs the number of days that have passed since each credit card belonging to - a given Chrome Profile was last used. This is logged for each Autofill - credit card once per Chrome User Profile load. - - - - - battre@chromium.org - chrome-autofill@google.com - - This histogram captures the number of days that have passed since each - stored address profile belonging to a given Chrome Profile was last used. - This is logged for each Autofill address profile once per Chrome User - Profile load. - - - - - - Removed as of 06/2019. - - jsaul@google.com - sebsg@chromium.org - - Logs the number of days between most recent use without modification and the - penultimate use of the profile when submitting a credit card form. - - - - - battre@chromium.org - chrome-autofill@google.com - - Measures the adoption of the HTML autocomplete type hint specification (see - http://is.gd/whatwg_autocomplete for more details). For each fillable form - detected, logs whether that form includes author-specified type hints. - - - - - koerber@google.com - battre@google.com - - Total number of fields at submission time that were autofilled and have or - have not been editing by the user afterwards. - - - - - koerber@google.com - battre@google.com - - Total number of fields at submission time of a specific type that were - autofilled and have or have not been editing by the user afterwards. - - - - - siashah@google.com - jsaul@google.com - payments-autofill-team@google.com - - Events tracking the usage of the expiration date fix flow prompt. This - prompt is triggered whenever expiration date must be explicitly requested - from the user in order to upload the card to Google Payments. - - - - - siashah@google.com - jsaul@google.com - payments-autofill-team@google.com - - The number of times the expiration date fix flow prompt is shown. - - - - - kolos@chromium.org - battre@chromium.org - chrome-autofill@google.com - Number of fields in a form that Autofill encounters. - - - - - - battre@chromium.org - chrome-autofill@google.com - - Predicted and actual form field type. This is a computed sparse histogram - where the value is ((predicted << 16)| actual). Predicted and actual - are taken from the autofill::ServerFieldType enumeration. - - - - - - - battre@chromium.org - chrome-autofill@google.com - - Aggregate Autofill field-type prediction outcomes. See - https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the - values. - - - - - - - battre@chromium.org - chrome-autofill@google.com - - Autofill field-type prediction outcomes, broken down by field type. See - https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the - values. - - - - - battre@chromium.org - chrome-autofill@google.com - - Time elapsed between the user's first interaction with a form and the form's - submission, for an autofilled form. - - - - - battre@chromium.org - chrome-autofill@google.com - - Time elapsed between the user's first interaction with a form and the form's - submission, for a non-autofilled form. - - - - - battre@chromium.org - chrome-autofill@google.com - - Time elapsed between form load and form submission, for an autofilled form. - - - - - battre@chromium.org - chrome-autofill@google.com - - Time elapsed between form load and form submission, for a non-autofilled - form. - - - - - - Removed 06/2020 after sufficient data was collected, to cleanup the code - base. - - schwering@google.com - chrome-autofill@google.com - - Records how forms change dynamically: whether the form signature changed, a - field's signature changed, or a field was newly created. The reference - period starts when Autofill parses the form for the first time, and ends - when a navigation is committed or the frame is destructed. - -
- Every form is observed for dynamic changes from the time it was first parsed - by Autofill until either a navigation has been committed or the frame is - destructed or the form's observation had to be flushed prematurely (the form - observations are managed in an LRU cache of maximum size 32, with least - recently parsed forms being discarded first). At the end of the lifetime, a - three-bit number is sent: the lowest bit is 1 iff a field was changed during - the form's lifetime (its signature changed); the second bit is 1 iff a field - was added (its renderer ID is new to the form); the highest bit is 1 iff the - form was changed (its signature changed). -
- - - - battre@chromium.org - jsaul@google.com - - Autofill form events for address forms. These are recorded when the user - interacts with a form requesting an address. - -
- Important caveat about submission metrics: - Submission using autofill data - is determined by simply evaluating if there was a fill operation in this - page. So, if the user filled with local data, completed erased or modified - the data after and then submitted, we would only emit one "Submitted - with server suggestion filled (once)"; - The submission segmentation - works by checking what kind of data was last filled for this type of form in - the page load. So, if a user initially filled with local data and after that - filled with server, we will only emit "Submitted with server suggestion - filled (once)". -
- - - - jsaul@google.com - battre@chromium.org - - Autofill form events for credit card forms. These are recorded when the user - interacts with a form requesting a credit card. - -
- Important caveat about submission metrics: - Submission using autofill data - is determined by simply evaluating if there was a fill operation in this - page. So, if the user filled with local data, completed erased or modified - the data after and then submitted, we would only emit one "Submitted - with server suggestion filled (once)"; - The submission segmentation - works by checking what kind of data was last filled for this type of form in - the page load. So, if a user initially filled with local data and after that - filled with server, we will only emit "Submitted with server suggestion - filled (once)". -
- - - - - Removed as of 02/2020. - - jsaul@google.com - siyua@chromium.org - - Autofill form events for credit card forms. These are recorded when the user - interacts with a form requesting a credit card, a dropdown of suggestions is - shown and at least one of the suggestions has a bank name. Form events are - logged at most once per page load. - -
- These metrics are used to measure the impact of the bank name experiment. - They are used to calculate the CTR of the autofill UI with bank names - available. Not all credit cards will have bank names even if we launch the - experiment. With these metrics we can run the experiment on 2 groups. For - one group, we will show bank names if available. For the other, we won't - shown. -
- - - - estark@chromium.org - - Autofill form events for credit card forms on nonsecure pages. These are - recorded when the user interacts with a form requesting a credit card. - -
- Important caveat about submission metrics: - Submission using autofill data - is determined by simply evaluating if there was a fill operation in this - page. So, if the user filled with local data, completed erased or modified - the data after and then submitted, we would only emit one "Submitted - with server suggestion filled (once)"; - The submission segmentation - works by checking what kind of data was last filled for this type of form in - the page load. So, if a user initially filled with local data and after that - filled with server, we will only emit "Submitted with server suggestion - filled (once)". -
- - - - sujiezhu@google.com - jsaul@google.com - - Autofill form events for credit card forms. These are recorded when the user - interacts with a form requesting a credit card, a dropdown of suggestions is - shown and at least one of the suggestions has a server nickname available. - -
- These metrics are used to measure the impact of the server card nickname - experiment. They are used to calculate the suggestion selection rate with - server nickname available. We will run the experiment on the same group of - user who has server cards with nicknames to compare the selection rate. For - enabled user, we will show nickname and log. For the other, we won't show - nickname in suggestion but we still log to this histogram. -
- - - - sujiezhu@google.com - jsaul@google.com - - Time elapsed between when the first Autofill suggestion is shown and user - first chooses a card, for a credit card form, where the user has at least - one card with a server nickname available. Log only once per form. We will - run the experiment on the same group of user who have server cards with - nicknames to compare the selection duration. For enabled user, we will show - nickname and log. For the other, we won't show nickname in suggestion but we - still log to this histogram. - - - - - battre@chromium.org - chrome-autofill@google.com - The autofill state related to a submitted form. - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts whether users accepted any autofill suggestion that was shown to them - for a given form. - - This metric is only recorded if a suggestion for the given form type (see - histogram name) was shown at least once. This is recorded once per form. If - the user accepts one suggestion, this is reported as "User chose to - fill" once. It does not matter if the user clears the filled values nor - if the user accepts a different suggestion later. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts whether users interacted with a form of a certain type. - - Focusing a field is sufficient to consider a form as being interacted with. - The user does not need to type anything. Note that some forms may get - focused on page load. - - This metric is recorded once per form observed by Autofill, but only for - forms that Autofill classifies to be of the type indicated by the histogram - name. If a form changes dynamically, Autofill interprets the forms before - and after the change as two different forms and records two values. If a - form did not have features that classify it as a form of a certain type - (e.g. an address form or payment form), then nothing is recorded. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts whether a form was parsed/interpreted to be of the type indicated in - the histogram name. - - This metric is recorded once for each form observed by Autofill. If a form - changes dynamically, then Autofill treats the different versions of the form - as different forms. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts whether users submitted a form that was filled via autofill. - - This metric is recorded once for each form observed by Autofill but only for - forms that the user filled via Autofill. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts whether users were shown suggestions to fill the form, given that - they have already interacted with the form. - - This metric is recorded only for forms that users interacted with. It is - recorded only once per form, meaning that it does not matter how often the - user sees suggestions. If a form changes dynamically, then Autofill treats - the different versions of the form as different forms. - - - - - jsaul@google.com - battre@chromium.org - - Whether the user had opted-in to seeing their server cards in Wallet Sync - Transport mode. Recorded when showing the autofill dropdown for credit - cards. - - - - - - Removed as of 06/2019. - - jsaul@google.com - sebsg@chromium.org - - Whether user modified an address profile shortly before submitting a credit - card form. - - - - - battre@chromium.org - chrome-autofill@google.com - - Logs when a hidden or presentational field is autofilled. The hidden or - presentational fields are only autofilled for 'select' fields to support - synthetic fields. - - - - - - Removed after M77. - - mathp@chromium.org - - Tracks whether Autofill was able to create the ICU collator successfully. - - - - - battre@chromium.org - chrome-autofill@google.com - - Tracks whether or not autofill suppressed sending votes or calculating - quality metrics because the profile data was marked as invalid. Logged - during field-type validation if/when a field marked as invalid is found to - match the submitted data. - - - - - battre@chromium.org - chrome-autofill@google.com - - Tracks whether or not autofill suppressed offering an autofill suggestion - because the profile data was marked as invalid. Logged during autofill - suggestion generation when a suggestion is about to generated based on a - field marked as invalid. - - - - - jsaul@google.com - battre@chromium.org - chrome-autofill@google.com - - This includes Autofill.Address.IsEnabled.PageLoad and - Autofill.CreditCard.IsEnabled.PageLoad, and tracks whether either profile - Autofill or payment Autofill is enabled on page load for a page containing - forms. It helps deduce the overlap by showing what percentage of users have - one type of Autofill enabled but not the other. - - - - - jsaul@google.com - battre@chromium.org - chrome-autofill@google.com - - This includes Autofill.Address.IsEnabled.Startup and - Autofill.CreditCard.IsEnabled.Startup, and tracks whether either profile - Autofill or payment Autofill is enabled when Chrome launches. It helps - deduce the overlap by showing what percentage of users have one type of - Autofill enabled but not the other. - - - - - - Obsolete after M77. - - mahmadi@chromium.org - - [iOS] Measures the frequency of button presses on the iOS Autofill keyboard - accessory view when VoiceOver is off. - - - - - - Obsolete after M85. - - mahmadi@chromium.org - - [iOS] Measures the frequency of button presses on the iOS Autofill keyboard - accessory view when VoiceOver is on. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for submitted forms whether users accepted the suggestion to fill - values. This is counted as 'yes' if the user accepted such a suggestion at - any time, regardless whether other suggestions were ignored or whether the - accepted suggestion was reverted afterwards. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for submitted forms whether the user filled any fields via Autofill. - - If the user reverts the filling, the form is still counted as filled. - - This metric is different from Autofill.KeyMetrics.FillingAcceptance in the - sense that the latter is only recorded if the user has actually seen a - prompt to fill data. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for submitted and autofilled forms whether users edited at least one - filled value before submitting the form. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for submitted forms whether Chromium had any address or payments data - to fill. - - It does not matter whether the user actually requested to fill the data. It - does not matter either whether the data available for filling corresponded - to the submitted data. - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for filled (by Autofill) forms whether users submitted those forms. - - This is only recorded for forms that the user filled via Autofill. It does - not matter if the user reverted the filling afterwards. - - This is recorded once Autofill stops tracking the form (e.g. due to a - navigation or due to removal from the DOM). - - - - - battre@chromium.org - kolos@chromium.org - nepper@chromium.org - - Counts for not filled (by Autofill) forms whether users submitted those - forms. - - This is only recorded for forms into which the user typed anything but did - not fill anything. It does not matter if the user reverted what they typed. - - This is recorded once Autofill stops tracking the form (e.g. due to a - navigation or due to removal from the DOM). - - - - - siyua@chromium.org - jsaul@google.com - - Record events related to bubble showing. Logged when bubble is requested or - is actually shown to users. - - - - - siyua@chromium.org - jsaul@google.com - - Records whether and how the local card migration bubble was accepted or - closed. - - - - - siyua@chromium.org - jsaul@google.com - Record how bubble is closed by different user interactions. - - - - sujiezhu@google.com - siyua@chromium.org - jsaul@google.com - - Record the decisions made when determining if local card migration should be - offered. - - - - - siyua@chromium.org - jsaul@google.com - - Record duration of the local card migration dialog being visible to users. - - - - - siyua@chromium.org - jsaul@google.com - - Record events related to showing the local card migration dialog. - - - - - siyua@chromium.org - jsaul@google.com - - Record user interactions related to local card migration dialog. - - - - - siyua@chromium.org - jsaul@google.com - - Record the percentage of cards selected by the user in the migration dialog. - - - - - siyua@chromium.org - jsaul@google.com - - Records when local card migration prompts are shown and/or accepted. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - When Chrome tries to access the user's Address Book, OSX presents a blocking - dialog which disrupts the user experience. A new Chrome feature has been - introduced wherein Chrome only shows this blocking dialog if the user - explicitly asked Chrome to access the user's Address Book. If a form's field - looks like it might support Autofill suggestions from the user's Address - Book and there are no other suggestions, Chrome shows an Autofill entry that - prompts the user to give Chrome access to the user's Address Book. This - histogram tracks the frequency that this Autofill entry is presented, and - the frequency that this Autofill entry is selected. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - This metric is emitted each time the user accepts an Autofill suggestion. It - records whether the result is from the Address Book. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - The amount of time spent accessing the OSX Address Book the first time after - Chrome was launched. If this time is larger than ~100ms, this it is likely - that the user was shown a blocking, modal dialog. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - After a Chrome is given access to the Mac Address Book, whether the Address - Book contained a Me card. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - When Chrome is given access to the Me Card of the Address Book, whether the - card has an address that contained a street number and either a city or zip - code. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - When Chrome is given access to the Me Card of the Address Book, whether the - card has an email. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - When Chrome is given access to the Me Card of the Address Book, whether the - card has a name. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - When Chrome is given access to the Me Card of the Address Book, whether the - card has a phone number. - - - - - - Removed as of 8/2015. - - erikchen@chromium.org - - The number of times that the access Address Book prompt has been shown when - the user selects the prompt. - - - - - manasverma@google.com - jsaul@google.com - - The frequency of user interactions with the Manage Cards prompt. - - - - - - Removed as of 12/2019. The comparison found that Chrome and Payments - correctly matched 99.9% of the time. - - jsaul@google.com - payments-autofill-team@google.com - - This metric is recorded when two credit cards are compared using - CreditCard::HasSameNumberAs and one of the cards in the comparison is - masked. The metric measures whether there is a match between a masked card's - network and the network of the card with which the masked card is being - compared. - - - - - msarda@google.com - payments-autofill-team@google.com - - This metric is recorded when the bit that indicates the user is opted in to - wallet sync transport is migrated (part of the migration from using email to - using Gaia ID as the account identifier). - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of autofilled fields that were subsequently edited prior to the - form being submitted. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of Autofill profiles that have been considered for deduplication. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of Autofill profiles that have been removed during deduplication. - - - - - battre@chromium.org - chrome-autofill@google.com - - Records whether the number of fillable form elements matches the number of - fields in the form's description. Instances where this is recorded as False, - denote cases where autofill failed to preview/fill an autofill suggestion. - This can happen when a fields is filtered out of a formless form. - - - - - siyua@chromium.org - payments-autofill-team@google.com - - Tracks the number of autofill offers data a user has stored, measured at - Chrome profile launch time. - - - - - siyua@chromium.org - payments-autofill-team@google.com - - Tracks the number of the credit cards an autofill card linked offer data is - related to, measured at Chrome profile launch time. - - - - - siyua@chromium.org - payments-autofill-team@google.com - - Tracks the number of the merchants an autofill offer data is related to, - measured at Chrome profile launch time. - - - - - siyua@chromium.org - payments-autofill-team@google.com - - Tracks whether the offer data is valid or not, measured whenever offer data - is synced down via Sync. - - - - - marsin@google.com - koerber@google.com - - Tracks whether the visible page language was translated or not upon form - submission. - - - - - - Removed 10/2015. - - dvadym@chromium.org - gcasto@chromium.org - - Tracks the increased load on the Autofill server if the restriction on - querying for password forms with fewer than 3 fields were omitted. - - - - - - Removed as of 1/2016, autofill payload compression was removed. - - mathp@chromium.org - - Compression ratio of the query and upload payload that are sent to the - Autofill server. The payload is compressed using gzip. - - - - - - Removed as of 9/2018, replaced by - Autofill.PaymentsCustomerDataBillingIdStatus. - - mathp@chromium.org - - When PaymentsCustomerData is used to send a request to Google Payments, we - log the validity state of the billing customer ID. - - - - - - Removed as of August 2019. - - mathp@chromium.org - - When PaymentsCustomerData is used to send a request to Google Payments, we - log the validity state of the billing customer ID. - - - - - battre@chromium.org - chrome-autofill@google.com - - The profile action that took place when a form was submitted. - - - - - - Removed as of 3/2011, replaced by Autofill.StoredProfileCount. - - Please list the metric's owners. Add more owner tags as needed. - The number of Autofill address profiles a user has. - - - - battre@chromium.org - src/components/autofill/OWNERS - - This metric is recorded when the autofill-use-improved-label-disambiguation - experiment is enabled and profile suggestions are available. This metric - measures how often suggestions were created with and without a formatter. - - - - - - Removed as of 3/2011, replaced by Autofill.Quality. - - Please list the metric's owners. Add more owner tags as needed. - The quality of the AutoFill implementation. - - - - - Removed as of 2/2014 (M35), replaced by Autofill.UserHappiness. - - isherman@chromium.org - The quality of the Autofill implementation. - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.Aggregate.Heuristic. - - isherman@chromium.org - The quality of Autofill's heuristic field type detection. - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.ByFieldType.Heuristic. - - isherman@chromium.org - - The quality of Autofill's heuristic field type detection, broken down by the - specific field type. Fields with multiple possible types (based on the - stored Autofill data) are logged as having ambiguous type. - - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.Aggregate.Overall. - - isherman@chromium.org - The overall quality of the Autofill field type predictions. - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.ByFieldType.Overall. - - isherman@chromium.org - - The overall quality of the Autofill field type predictions, broken down by - the specific field type. Fields with multiple possible types (based on the - stored Autofill data) are logged as having ambiguous type. - - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.Aggregate.Server. - - isherman@chromium.org - The quality of the Autofill server's field type detection. - - - - - Removed as of 6/2017, replaced by - Autofill.FieldPredictionQuality.ByFieldType.Server. - - isherman@chromium.org - - The quality of the Autofill server's field type detection, broken down by - the specific field type. Fields with multiple possible types (based on the - stored Autofill data) are logged as having ambiguous type. - - - - - battre@chromium.org - chrome-autofill@google.com - - For credit card forms that are queried for Autofill, a ratio of how many are - within secure contexts (which includes mixed passive content). - - - - - battre@chromium.org - chrome-autofill@google.com - - The delay of a network request for a query due to exponential backoff. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of bytes that were sent in a query that subsequently failed. This - is to help determine the appropriate threshold at which autofill queries - should switch from GET to POST, and if there are certain sizes of queries - which are prone to failure. - - - - - - Removed as of 8/2018, replaced by Autofill.Query.HttpResponseOrErrorCode. - - rogerm@chromium.org - The HTTP response code returned on a query. - - - - battre@chromium.org - chrome-autofill@google.com - - The http response code or net error code returned on a query. - - - - - battre@chromium.org - chrome-autofill@google.com - The HTTP method used to query the autofill server. - - - - battre@chromium.org - chrome-autofill@google.com - The duration of a network request for a query. - - - - battre@chromium.org - chrome-autofill@google.com - - Was the autofill query response retrieved from the HTTP cache. - - - - - battre@chromium.org - chrome-autofill@google.com - - The quality of fields rationalization, putting rationalization result into - good/ok/bad categories. - - - - - - Were added as part of Issue 851295; no longer necessary. Removed 2019/07. - - sebsg@chromium.org - The number of full server cards that were reset. - - - - - Removed as of 10/2018 (M72). - - sebsg@chromium.org - The number of full server cards that would have been reset. - - - - - Were added as part of Issue 851295; no longer necessary. Removed 2019/07. - - sebsg@chromium.org - - Records whether a sync service in a not active state is passed to Autofill - OnSyncServiceInitialized. - - - - - - Were added as part of Issue 851295; no longer necessary. Removed 2019/07. - - sebsg@chromium.org - - Records whether a null sync service is passed to Autofill - OnSyncServiceInitialized. - - - - - - Removed as of 04/2019 (M76). No longer necessary since we don't mask data - for USS Autofill Wallet anymore. - - sebsg@chromium.org - - Records the sync service state when OnStateChanged is called. - - - - - jsaul@google.com - payments-autofill-team@google.com - - If the cardholder name fix flow is shown when credit card upload is offered, - records if the cardholder name textfield was prefilled with the name from - the user's Google Account. - - - - - jsaul@google.com - payments-autofill-team@google.com - - If the cardholder name fix flow is shown during credit card upload and the - user accepts upload, logs whether the final cardholder name was changed from - its prefilled value or not. - - - - - - Removed as of 05/2019. Was a temporary metric to gauge the impact of - http://crbug.com/892299. - - jsaul@google.com - sebsg@chromium.org - mahmadi@chromium.org - - - - Records if the PersonalDataManager was notified to attempt saving of a card. - - - - - jsaul@google.com - payments-autofill-team@google.com - - Records the reason expiration date was explicitly requested from the user - during credit card save. - - - - - - Deprecated after M85. - - battre@chromium.org - - - - Records if a card was saved from a form that had split name fields. - - - - - - Deprecated after M85. - - battre@chromium.org - - - - Records if a card was offered to be saved from a form that had split name - fields. - - - - - jsaul@google.com - siyua@chromium.org - - The relative frequency with which users accept or deny the Autofill save - credit card prompt. - - - - - jsaul@google.com - siyua@chromium.org - - The relative frequency with which the Autofill save credit card prompt is - shown or not. Logged when the flow is triggered and the prompt should be - shown. - - - - - jsaul@google.com - siyua@chromium.org - - The relative frequency with which users accept or deny the Autofill save - credit card prompt. Logged when users interacted with the prompt. - - - - - battre@chromium.org - chrome-autofill@google.com - Whether a credit card scan was completed or cancelled. - - - - battre@chromium.org - chrome-autofill@google.com - How long a credit card took to scan. - - - - battre@chromium.org - jsaul@chromium.org - chrome-autofill@google.com - Usage of the "Scan card" control item. - - - - jsaul@google.com - battre@chromium.org - chrome-autofill@google.com - - Logged when the user clicks on the server credit card link in the settings - page. - - - - - - Removed as of 6/2011, replaced by Autofill.ServerExperimentId.Query. - - isherman@chromium.org - - The experiment ID received in response to an Autofill server query. - - - - - - Removed as of 2/2014 (M35). - - isherman@chromium.org - - The experiment ID received in response to an Autofill server query. - - - - - - Removed as of 2/2014 (M35). - - isherman@chromium.org - - The experiment ID received at the time of an Autofill upload. - - - - - - Removed as of 3/2011, replaced by Autofill.ServerQueryResponse. - - Please list the metric's owners. Add more owner tags as needed. - The usefulness of AutoFill server information. - - - - battre@chromium.org - chrome-autofill@google.com - The usefulness of Autofill server information. - - - - battre@chromium.org - chrome-autofill@google.com - - Tracks whether Autofill server had at least some prediction data for a given - form at query response time. - - - - - battre@chromium.org - chrome-autofill@google.com - - - - The number of credit cards a user has stored, measured at Chrome profile - launch time. - - - - - battre@chromium.org - chrome-autofill@google.com - - - - The number of disused credit cards a user has stored, measured at Chrome - profile launch time. This is only reported for users who have at least one - stored credit card. - - - - - - Removed in favor of Autofill.StoredCreditCardCount.Local. - - mathp@chromium.org - - The number of local credit cards a user has stored, measured at Chrome - profile launch time. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of Autofill addresses a user has stored, measured at launch time. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of Autofill addresses a user has stored, measured when an - autofillable form is submitted. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of stored Autofill address profiles which have not been used in a - sufficiently long time for autofill to consider them disused. Measured once - per Chrome user profile launch. - - - - - - Removed in favor of Autofill.StoredCreditCardCount.Server. - - mathp@chromium.org - - The number of server credit cards a user has stored, measured at Chrome - profile launch time. - - - - - jsaul@google.com - annelim@google.com - - Records when credit card save is not offered (either at all on mobile or by - simply not showing the bubble on desktop) due to the candidate card having - too many strikes. - - - - - jsaul@google.com - annelim@google.com - - Records when local card migration is not offered due to the candidate's - LocalCardMigration strike count reaching maximum strikes. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" a given card has, when a user - dismisses a prompt to save a new credit card. The strike count is - incremented each time the user dismisses the prompt. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" a user has, when a prompt for - local card migration is dismissed. The strike count is incremented each time - the user dismisses the prompt. - - - - - jsaul@google.com - annelim@google.com - - When a StrikeDatabase fails to initialize, records the number of consecutive - failed initialization attempts. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" a user has when local card - migration is accepted. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" a given card had when a user opted - to save the card to Chrome. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" a given card had when a user - successfully uploaded the card to Google Payments. - - - - - jsaul@google.com - annelim@google.com - - Records the number of "strikes" present in a StrikeDatabase entry - when a strike expires. - - - - - jsaul@google.com - payments-autofill-team@google.com - - Metric to measure credit card state when form is submitted, specifically if - it had a valid card number and/or expiration date. - - - - - jsaul@google.com - payments-autofill-team@google.com - - Metric to measure if a submitted card's expiration date matches the same - server card's expiration date (unmasked or not). Cards are considered to be - the same if they have the same card number (if unmasked) or if they have the - same network and last four digits (if masked). - - - - - kolos@chromium.org - jsaul@google.com - - Metric to measure if a submitted form contains any recognizable value - patterns (e.g., Unified Payment Interface Virtual Payment address (UPI - VPA)). Reported for every submitted non-empty visible field observed by - Autofill. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Records acceptance of autofill suggestions in regular and off-the-record - modes. - - - - - battre@chromium.org - chrome-autofill@google.com - - The index of the accepted Autofill suggestion in the popup. Due to - crbug.com/966411, the iOS data is incorrect. - - - - - battre@chromium.org - chrome-autofill@google.com - - The index of the accepted Autocomplete suggestion in the popup. Due to - crbug.com/966411, the iOS data is incorrect. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Records showing of autofill suggestions in regular and off-the-record modes. - - - - - kenjitoyama@chromium.org - battre@chromium.org - chrome-autofill@google.com - - Number of milliseconds passed between the start and end of - FormStructure::DetermineHeuristicTypes(). - - - - - kenjitoyama@chromium.org - battre@chromium.org - chrome-autofill@google.com - - Number of milliseconds passed between the start and end of parsing a single - form. - - - - - marsin@google.com - koerber@google.com - - The visible page language (best guess of the original or the translated - language, if translation was used) upon form submission. This is a sparse - histogram where the integer value represents the language code as described - by the ISO 639 standard. - - - - - - Removed as of 01/2019, as it never occurs. - - rogerm@chromium.org - - The delay of a network request for which the download manager seems to have - lost the request type due to exponential backoff. This should never be - logged. - - - - - - Removed as of 01/2019, as it never occurs. - - rogerm@chromium.org - - The number of bytes that were sent in a request for which the download - manager seems to have lost the request type. This should never be logged. - - - - - - Removed as of 8/2018, replaced by Autofill.Unknown.HttpResponseOrErrorCode. - - rogerm@chromium.org - - The HTTP response code returned on a request for which the download manager - seems to have lost the request type. This should never be logged. - - - - - - Removed as of 01/2019, as it never occurs. - - rogerm@chromium.org - - The http response code or net error code returned on a request for which the - download manager seems to have lost the request type. This should never be - logged. - - - - - - Removed as of 01/2019, as it never occurs. - - rogerm@chromium.org - - The duration of a network request for which the download manager seems to - have lost the request type. This should never be logged. - - - - - jsaul@google.com - siyua@chromium.org - - Duration of the interaction with the UnmaskPrompt since it was shown until - it was closed. This prompt is triggered when a user selects a masked card in - an autofill dropdown. - - - - - jsaul@google.com - siyua@chromium.org - - Events tracking the usage of the unmasking prompt. This prompt is triggered - when a user selects a masked card in a autofill dropdown. - - - - - jsaul@google.com - siyua@chromium.org - - Duration of the GetRealPan API call. This API call is triggered by the - unmasking prompt when the user types information to verify their ownership - of the card being fetched. - - - - - jsaul@google.com - siyua@chromium.org - - Tracks the result of the GetRealPan API call. This API call is triggered by - the unmasking prompt when the user types information to verify their - ownership of the card being fetched. - - - - - jsaul@google.com - siyua@chromium.org - - Time the user waited before abandoning an unmasking operation. In such a - scenario, the user is cancelling a pending unmasking operation (possibly - because it is taking too long). The time measured here corresponds to the - time between the user clicking the "Verify" button and then - clicking "Cancel". - - - - - jsaul@google.com - siyua@chromium.org - - Duration between the user clicking the Verify button within the unmasking - prompt until we get a response back from the server. This prompt is - triggered when a user selects a masked card in an autofill dropdown. - - - - - battre@chromium.org - chrome-autofill@google.com - - Records incidents where an implicit (formless) form has elements filtered - out of it. This happens to unowned fields (directly embedded in the page - with no enclosing <form> tag) without autocomplete attributes if - formless forms are restricted to "checkout" pages. Logged when - parsing forms/fields. - - - - - - - battre@chromium.org - chrome-autofill@google.com - - The delay of a network request for an upload due to exponential backoff. - - - - - battre@chromium.org - chrome-autofill@google.com - - The number of bytes that were sent in an upload that subsequently failed. - This is to help determine if there are certain upload sizes which are prone - to failure. - - - - - - Removed as of 8/2018, replaced by Autofill.Upload.HttpResponseOrErrorCode. - - rogerm@chromium.org - The HTTP response code returned on an upload. - - - - - - battre@chromium.org - chrome-autofill@google.com - - The http response code or net error code returned on an upload. - - - - - battre@chromium.org - chrome-autofill@google.com - - Tracks whether or not the configuration fo metadata upload encoding is valid - or invalid. Note that if the configuration is invalid, the client will fall - back to a default configuration that sends 4 bits per byte (i.e., either the - even or odd bits encoding). - - - - - battre@chromium.org - chrome-autofill@google.com - - The metadata encoding scheme used by the client to encode rich uploads. - - - - - - - battre@chromium.org - chrome-autofill@google.com - The duration of a network request for an upload. - - - - - - jsaul@google.com - - Measures if a card for which upload was accepted is already stored as a - local card on the device or if it has not yet been seen. - - - - - - - battre@chromium.org - chrome-autofill@google.com - - Whether or not an upload was sent after having been triggered by a form - submission or proxy-form-submission. - - - - - - - jsaul@google.com - - Measures if a card for which upload was offered is already stored as a local - on the device or if it has not yet been seen. - - - - - jsaul@google.com - annelim@google.com - - Records the number of times that the cache for unmasked server cards has - been accessed for a given card. For example, if the cache is being accessed - and it has already been accessed for the card twice before, then - "3" is recorded. - - - - - battre@chromium.org - chrome-autofill@google.com - - Measures the frequency of various events in the Autofill user interaction - flow. By comparing frequencies, we can compute several interesting - "user happiness" metrics. - - - - - battre@chromium.org - chrome-autofill@google.com - - Tracks how the different wallet addresses are converted to local autofill - profiles. - - - - - - Removed as of 12/2018, replaced by Autofill.WalletAddresses2. - - - - sebsg@chromium.org - jkrcal@chromium.org - - The number of Wallet addresses that were added to Chrome or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. Recorded only if both the user had previously non-empty - data set locally and the new data set is also non-empty (to rule out initial - sync and wiping out data). This metric has a flaw that the Directory - implementation (unlike the USS implementation) records the metric also on - every startup and the resulting histograms are hard to compare. - - - - - - Removed as of 05/2019. - - - - sebsg@chromium.org - jkrcal@chromium.org - - The number of Wallet addresses that were added to Chrome or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. Recorded only if both the user had previously non-empty - data set locally and the new data set is also non-empty (to rule out initial - sync and wiping out data). - - - - - - Removed as of 11/2018, replaced by Autofill.WalletAddresses.Added. - - sebsg@chromium.org - treib@chromium.org - - The number of Wallet addresses that were added to Chrome via Sync. Recorded - when receiving an AUTOFILL_WALLET_DATA update from the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 11/2018, replaced by Autofill.WalletAddresses.AddedOrRemoved. - - sebsg@chromium.org - treib@chromium.org - - The total number of Wallet addresses that were added to or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 11/2018, replaced by Autofill.WalletAddresses.Removed. - - sebsg@chromium.org - treib@chromium.org - - The number of Wallet addresses that were removed from Chrome via Sync. - Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 12/2018, replaced by Autofill.WalletCards2. - - - - sebsg@chromium.org - jkrcal@chromium.org - - The number of Wallet credit cards that were added to Chrome or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. Recorded only if both the user had previously non-empty - data set locally and the new data set is also non-empty (to rule out initial - sync and wiping out data). This metric has a flaw that the Directory - implementation (unlike the USS implementation) records the metric also on - every startup and the resulting histograms are hard to compare. - - - - - - Removed as of 05/2019. - - - - sebsg@chromium.org - jkrcal@chromium.org - - The number of Wallet credit cards that were added to Chrome or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. Recorded only if both the user had previously non-empty - data set locally and the new data set is also non-empty (to rule out initial - sync and wiping out data). - - - - - - Removed as of 11/2018, replaced by Autofill.WalletCards.Added. - - sebsg@chromium.org - treib@chromium.org - - The number of Wallet credit cards that were added to Chrome via Sync. - Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 11/2018, replaced by Autofill.WalletCards.AddedOrRemoved. - - sebsg@chromium.org - treib@chromium.org - - The total number of Wallet credit cards that were added to or removed from - Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from - the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 11/2018, replaced by Autofill.WalletCards.Removed. - - sebsg@chromium.org - treib@chromium.org - - The number of Wallet credit cards that were removed from Chrome via Sync. - Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. - -
- Can probably be removed around Q1 2019, after project Dice has rolled out. -
- - - - - Removed as of 04/2019 because most measurements were in the last bucket, - replaced by Autofill.WalletUseDateInMinutes.Address. - - jkrcal@chromium.org - treib@chromium.org - - The time since last use date of a wallet address, as known by sync. Recorded - for each wallet address on startup. - - - - - - Removed as of 04/2019 because most measurements were in the last bucket, - replaced by Autofill.WalletUseDateInMinutes.Card. - - jkrcal@chromium.org - treib@chromium.org - - The time since last use date of a wallet card, as known by sync. Recorded - for each wallet card on startup. - - - - - - Removed as of 2019-08. - - jkrcal@chromium.org - treib@chromium.org - - The time since last use date of a wallet address, as known by sync. Recorded - for each wallet address on startup. - - - - - - Removed as of 2019-08. - - jkrcal@chromium.org - treib@chromium.org - - The time since last use date of a wallet card, as known by sync. Recorded - for each wallet card on startup. - - - - - yigu@chromium.org - battre@chromium.org - web-identity@google.com - - Records whether a frame has ever used autocomplete="one-time-code" - during its lifecycle. i.e. it's only recorded once per frame. In addition, - we only record it if the frame has parsed forms. - - - - - yigu@chromium.org - battre@chromium.org - web-identity@google.com - - Records whether a frame collects phone number based on the field - classification. It records once per frame only if it has parsed forms. - - Note that the field types may not be calculated if there are less than 3 - fields in the form unless an autocomplete attribute is provided. e.g. if the - form has only a single field regarding phone number without specifiying - autocomplete="phone", a sample with "false" will be - reported. - - - - - yigu@chromium.org - madjivp@chromium.org - web-identity@google.com - - Records whether a document collected phone number, and/or used WebOTP, - and/or used OneTimeCode (OTC) during its lifecycle. i.e. it's recorded in - the browser process when a document is destroyed. - - - - - michaelbai@chromium.org - src/android_webview/OWNERS - Records the state of an autofill session. - - - - michaelbai@chromium.org - src/android_webview/OWNERS - Whether the autofill is created by activity context. - - - - michaelbai@chromium.org - src/android_webview/OWNERS - - Whether the autofill service is enabled in Android platform. - - - - - michaelbai@chromium.org - src/android_webview/OWNERS - Records the source of form submission. - - - - michaelbai@chromium.org - src/android_webview/OWNERS - The time taken to display suggestion. - - - - michaelbai@chromium.org - src/android_webview/OWNERS - Whether the user changed autofilled field. - - - - - Removed 12/2019. No longer tracked. - - gayane@chromium.org - - Time that it takes to calculate all the theme properties for autogenerated - themes in ms. - - - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. We also log the als-delta from the - previous log-lux (when brightness was last changed) to the current log-lux, - which includes both the sign of the als-delta and its absolute value. Chrome - OS only. - - - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. We also log the als-stddev in its - averaging period. We log it separately for the case when the associated - als-delta is positive and negative. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. This enum states the reason why the - model also thinks brightness should be changed. Chrome OS only. - - - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. We also log the number of model - iterations if we've set to use personal curve only. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. This enum states the reason why the - model doesn't think brightness should be changed. Chrome OS only. - - - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, we will ask the model whether it also - thinks brightness should be changed. We also log the als-stddev in its - averaging period. This metric records the als-stddev when the associated - als-delta is unknown. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether the ALS is enabled or the error otherwise. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - Reason for the model to change brightness. Chrome OS only. - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - The time between two consecutive auto brightness changes. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of model iterations when brightness is changed by a personal curve. - Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether the brightness monitor is enabled or the error otherwise. Chrome OS - only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on an Atlas - device with an ambient sensor that is supported by the auto screen - brightness model. Reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on an Eve device - with an ambient sensor that is supported by the auto screen brightness - model. Reported daily. The count is accumulated through the day, spanning - reboots, and sent once the system clock indicates that a full day or more - has passed since the last report. If the system is suspended or off for more - than a day, the current count will be reported immediately the next time the - system boots, but the skipped days will not be reported. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on a Kohaku - device with an ambient sensor that is supported by the auto screen - brightness model. Reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on a device - without an ambient sensor. Reported daily. The count is accumulated through - the day, spanning reboots, and sent once the system clock indicates that a - full day or more has passed since the last report. If the system is - suspended or off for more than a day, the current count will be reported - immediately the next time the system boots, but the skipped days will not be - reported. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on a Nocturne - device with an ambient sensor that is supported by the auto screen - brightness model. Reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on a device with - an ambient sensor that is supported by the auto screen brightness model. - Reported daily. The count is accumulated through the day, spanning reboots, - and sent once the system clock indicates that a full day or more has passed - since the last report. If the system is suspended or off for more than a - day, the current count will be reported immediately the next time the system - boots, but the skipped days will not be reported. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Number of times that a user has made brightness adjustments on a device with - an ambient sensor that is not supported by the auto screen brightness model. - Reported daily. The count is accumulated through the day, spanning reboots, - and sent once the system clock indicates that a full day or more has passed - since the last report. If the system is suspended or off for more than a - day, the current count will be reported immediately the next time the system - boots, but the skipped days will not be reported. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Type of error seen when handling data related to automatic screen brightness - adjustments. Only reported on Chrome OS. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - The elapsed time from a model brightness adjustment to the next user manual - brightness change. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - Whether the global curve is reset at initialization. - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - A monotone cubic spline curve may be invalid from input that used to - generate it. This metric records why it's invalid. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether there was no recorded ALS reading when brightness was changed. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Under the current implementation of brightness monitor, user brightness - request should be received before brightness change signal. Adapter operates - under this assumption. This metric logs an error if a brightness change - signal is received without a prior brightness request signal. Chrome OS - only. - - - - - jiameng@chromium.org - napper@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Personal model iteration count when modeller is initialized. Chrome OS only. - - - - - jiameng@chromium.org - napper@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - Status of the model loading from disk. Chrome OS only. - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether a new brightness exceeds the preset bound that defines reasonble - range of change. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether a training data is an outlier and should be discarded by the model - during training. Chrome OS only. - - - - - jiameng@chromium.org - napper@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When training data comes in, the model may or may not be updated. We measure - the error of the model as compared with the target value from training data. - This metric measures the error when model is not updated. Chrome OS only. - - - - - jiameng@chromium.org - napper@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When training data comes in, the model may or may not be updated. We measure - the error of the model as compared with the target value from training data. - This metric measures the error when model is updated. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether user brightness change is consistent with the model so that model is - not updated. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - The time elapsed between training start and a new curve saved to disk. Only - reported if a new curve was created and saved successfully to disk. Chrome - OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether a new curve was successfully saved to disk. Only reported if a new - curve was created during the training process. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, if the previous change was caused by - the model, then we log bucketized absolute brightness changes of the two - adjustments. This metric records changes if they are in the opposite - directions. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When there is an error in the automatic screen brightness parameters, this - records which kind of parameter is invalid. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - Whether the user's personal brightness curve is valid. Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - When user changes brightness manually, if the previous change was caused by - the model, then we log bucketized absolute brightness changes of the two - adjustments. This metric records changes if they are in the same direction. - Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - The time elapsed to complete training after which a new curve was generated. - Chrome OS only. - - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - The time elapsed to complete training after which no new curve was - generated. Chrome OS only. - - - - - - Removed as of 11/2018. It has been replaced by DailyUserAdjustment. - - jiameng@chromium.org - Type of user manual screen brightness adjustment. - - - - jiameng@chromium.org - wrong@chromium.org - tby@chromium.org - thanhdng@chromium.org - - How user manual screen brightness adjustment changes the model. Chrome OS - only. - - - - - robertogden@chromium.org - tbansal@chromium.org - - How old a cached probe result was when it was used, in hours. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the completion status of a probe when it completes each attempt. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the completion status of a probe retry after an externally reported - failure. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the end state of a probe just before it goes inactive. This happens - when the prober succeeds, fails and has no more retries, or the delegate - stops probing. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the net error of a completed or timed out probe. Note that if a HTTP - response does not occur within the probe's TTL, when a sample will also be - added to the ERR_TIMED_OUT bucket. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the number of attempts that are made to achieve a successful probe - result. Only recorded on success. This metric is 1-based so if a probe - succeeds the first time, a sample of 1 will be recorded. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the HTTP response code of a completed probe, when a HTTP response is - received. - - - - - - Replaced by Availability.Prober.TimeUntilFailure2. - - robertogden@chromium.org - tbansal@chromium.org - - Records the amount of time spent working on a single probe attempt to get to - a failed state. Recorded every time a probe fails. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the amount of time spent working on a single probe attempt to get to - a failed state. Recorded every time a probe fails. - - - - - - Replaced by Availability.Prober.TimeUntilSuccess2. - - robertogden@chromium.org - tbansal@chromium.org - - Records the amount of time spent working on a single probe attempt to get to - a successful state. Recorded every time a probe succeeds. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Records the amount of time spent working on a single probe attempt to get to - a successful state. Recorded every time a probe succeeds. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Records the reason why the page is evicted from the back-forward cache but - after the document is restored. This happens when there is a race between - eviction and restoring. This also records when the page is restored to - calculate how often this eviction happens. - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, this records whether - the page was restored from the BackForwardCache or not. - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, this records what - blocklisted features were used when the page was loaded and prevented this - page from being stored in the back-forward cache. Multiple blocklisted - features can be recorded for the same page. - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history and the - BackForwardCache wasn't used because of the related browsing instances, this - records the reason why the browsing instance wasn't swapped. - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - carlscab@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - For history navigations, records the reasons passed to - BackForwardCache::DisableForRenderFrameHost calls. These reasons are - specified as strings, so this histograms contains their hashes computed as - base::HashMetricName. - - The metric is recorded when a history navigation commits and emits a sample - for each reason. Compare this with - BackForwardCache.HistoryNavigationOutcome, which contains the total number - of navigations which where not cached - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, record why it wasn't - restored from the cache. The page might not have entered the back-forward in - the first place based on the features used, or it might have been evicted - while being in the cache. - - This is recorded for all websites regardless whether back-forward cache is - enabled or not. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Records the reason why the page is evicted from the back-forward cache but - after the document is restored. This happens when there is a race between - eviction and restoring. This also records when the page is restored to - calculate how often this eviction happens. - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Records the time duration between the last time when the entry goes to the - back-forward cache and the time when the process is killed. - - - - - hbolaria@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Track number of times an unexpected IPC message is posted to frames in the - renderer process while they are frozen in the back-forward cache. IPC tasks - are denoted by md5 hash of the mojo bindings method name or message hash for - legacy IPCs. - - Recorded when an IPC task is posted to frames that have already been stored - in the back-forward cache, after a 15 second delay to account for completion - of all freezing-related operations. - - - - - hbolaria@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Duration between start of page being stored in the back-forward cache and - when the unexpected IPC call is received by a frame while in the cache. - - Recorded when an IPC task is posted to frames that have already been stored - in the back-forward cache, after a 15 second delay to account for completion - of all freezing-related operations. - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, this records whether - the page was restored from the BackForwardCache or not. - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, this records what - blocklisted features were used when the page was loaded and prevented this - page from being stored in the back-forward cache. Multiple blocklisted - features can be recorded for the same page. - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history and the - BackForwardCache wasn't used because of the related browsing instances, this - records the reason why the browsing instance wasn't swapped. - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - carlscab@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - For history navigations, records the reasons passed to - BackForwardCache::DisableForRenderFrameHost calls. These reasons are - specified as strings, so this histograms contains their hashes computed as - base::HashMetricName. - - The metric is recorded when a history navigation commits and emits a sample - for each reason. Compare this with - BackForwardCache.HistoryNavigationOutcome, which contains the total number - of navigations which where not cached - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - When navigating back to a page in the session history, record why it wasn't - restored from the cache. The page might not have entered the back-forward in - the first place based on the features used, or it might have been evicted - while being in the cache. - - This is recorded when back-forward cache is enabled for this navigation - (back-forward cache feature is enabled and the domain is in the scope of the - experiment). - - - - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Records whether a page restored from the back-forward cache has pageshow - handlers installed in its main frame. Recorded when the renderer resumes - page when restoring it from the back-forward cache. - - - - - rakina@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records whether a page where we did a same-site proactive BrowsingInstance - swap on (with the intention on storing it in the back-forward cache later) - is still eligible for back-forward cache when swapping out the old page - during navigation commit. Recorded when we have just finished committing the - new page on the renderer side, and during the commit of the new page in the - browser side. - - - - - rakina@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records whether we did a same-site proactive BrowsingInstance swap or not - for a same-site cross-document navigation. Recorded when we are committing - the navigation. - - - - - rakina@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records whether a page where we did a same-site proactive BrowsingInstance - swap on (with the intention on storing it in the back-forward cache later) - is no longer eligible for back-forward cache after the navigation committed - and the page has unload handlers that will run after commit, which is a - web-observable behavior change for same-site navigations. Recorded when we - have just finished committing the new page on the renderer side, and during - the commit of the new page in the browser side. - - - - - sreejakshetty@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records the number of reloads after a history navigation both for the cases - when page is served and not served from back-forward cache. - - This is recorded when navigation is committed, only for the domains which - are in the scope of back-forward cache experiment and they are of same - NavigationEntry (e.g. back and reload in different tab do not count). - - - - - sreejakshetty@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records the total number of history navigations along with the number of - reloads if the previous navigation was a history one. - - This is recorded when navigation is committed, only for the domains which - are in the scope of back-forward cache experiment. - - - - - sreejakshetty@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Duration between start of navigation restoring a document from back-forward - cache and the first paint. - - This is recorded when a history navigation is served from back-forward cache - but in a foreground tab. - - - - - - Deprecated 09/2020 in favor of ActionAfterPagehide2 which excludes actions - taken when the unload event is in progress. - - rakina@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records occurences of certain actions triggered by script running on a page - after the pagehide event gets dispatched in the page, which might be - possible if we dispatch the pagehide event without unloading/freezing the - page (only happens when we're doing a same-site navigation and we did a - proactive BrowsingInstance swap but we're reusing the old page's process). - Note: we will only track actions that might affect the user after we've - navigated away from the old page, such as modifications to storage, - navigations, or sending/receiving postMessage. - - - - - rakina@chromium.org - altimin@chromium.org - bfcache-dev@chromium.org - - Records occurences of certain actions triggered by script running on a page - after the pagehide event gets dispatched in the page, which might be - possible if we dispatch the pagehide event without unloading/freezing the - page (only happens when we're doing a same-site navigation and we did a - proactive BrowsingInstance swap but we're reusing the old page's process). - - Note: We will only track actions that might affect the user after we've - navigated away from the old page, such as modifications to storage, - navigations, or sending/receiving postMessage. - - Note 2: We will not track actions taken when the unload event is currently - in progress, which means the page is not actually stored in the back-forward - cache and the actions are expected to happen after pagehide. - - - - - carlscab@google.com - bfcache-dev@chromium.org - - Hash (base::HashMetricName) of a mojo interface name. - - A sample is recorded for every message the browser receives from a renderer - for a page that is in the back-forward cache. Logging can be disabled via - the back-forward cache feature parameter - "message_handling_when_cached". - - Renderers should not be sending messages back to the browser for pages that - are in the back-forward cache. Eventually we will be killing such renderers - (as we could assume that it is misbehaving because it got compromised). But - first we must make sure that we are not sending messages by mistake (i.e. - bugs in the renderer). - - - - - - - peter@chromium.org - rayankans@chromium.org - - Records the Service Worker status code that caused a Background Fetch API - event to fail dispatching whilst trying to dispatch an event on the active - Service Worker. - - - - - - - peter@chromium.org - rayankans@chromium.org - - Records the Service Worker status code that caused a Background Fetch API - event to fail dispatching whilst trying to find the Service Worker. - - - - - - - peter@chromium.org - rayankans@chromium.org - - Records the Service Worker status code that caused a Background Fetch API - event to fail dispatching whilst trying to start the active Service Worker. - - - - - - - peter@chromium.org - rayankans@chromium.org - - Records the result of dispatching one of the Background Fetch API events to - the Service Worker associated with the event. - - - - - peter@chromium.org - rayankans@chromium.org - - Records whether the fetch requests contains any duplicate URLs. This is - called after the provided requests are verified, but before the fetch is - started. - - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether the background fetch contains any requests with a body. - Called before the fetch is started. - - - - - rayankans@chromium.org - peter@chromium.org - - Records the number of Background Fetch registrations found on browser - start-up. This is called after the initialization database task runs - successfully. - - - - - - - rayankans@chromium.org - peter@chromium.org - - Records the duration of the mojo call for the exposed BackgroundFetchManager - APIs. - - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether match() or matchAll() was called from Document Scope. Called - when match() or matchAll() is invoked in the renderer process. - - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether match() or matchAll() was called when the background fetch - was incomplete. Called when match() or matchAll() is invoked in the renderer - process. - - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records the percent of requests for which updates are received in the - renderer process from the browser process. Called when the completion event - for a background fetch has finished processing. - - - - - - Removed 10/2018 since DB tasks record this more accurately. - - peter@chromium.org - rayankans@chromium.org - - Records the error after the Background Fetch Data Manager creates a - registration. - - - - - - Removed 10/2018 since DB tasks record this more accurately. - - peter@chromium.org - rayankans@chromium.org - - Records the error after the Background Fetch Data Manager deletes a - registration. - - - - - - Removed 10/2018 since DB tasks record this more accurately. - - peter@chromium.org - rayankans@chromium.org - - Records the error after the Background Fetch Data Manager marks a - registration for deletion. This is called when the Scheduler Controller is - finished. - - - - - - - rayankans@chromium.org - peter@chromium.org - Records the storage error when running a database task. - - - - atwilson@chromium.org - mvanouwerkerk@chromium.org - - The number of background applications (extensions) for a profile that were - loaded after the profile was registered with the BackgroundModeManager. - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - Logged if BackgroundModeManager is running and listening for pref changes, - and the pref does indeed change. The new value is logged. - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - Logged when an item in the system tray icon menu is clicked. - - - - - gab@chromium.org - mvanouwerkerk@chromium.org - - Logged during BackgroundModeManager's initialization. Indicates the - AutoLaunchState the current browser process was launched in. - - - - - gab@chromium.org - mvanouwerkerk@chromium.org - - Logged during BackgroundModeManager's initialization. Indicates the state of - the kBackgroundModeEnabled pref on startup. - - - - - peter@chromium.org - mvanouwerkerk@chromium.org - - The duration of a session before the browser got restarted in the background - by the BackgroundOptimizer to purge the memory. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the number of `sync` events which were fired in a batch. A batch is - defined as the set of `sync` events dispatched at the same time by the - BackgroundSyncManager. One-shots usually run individually (a batch of one), - unless the device was offline and multiple are waiting for the device to go - back online. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether the fired `sync` events upon completion orginated from a - background wakeup task or the foreground. - - - - - - As of 10/2015 this has been replaced by - BackgroundSync.Event.OneShotResultPattern. - - iclelland@chromium.org - Records whether a one-shot sync event succeeded or failed. - - - - nator@chromium.org - rayankans@chromium.org - - Records whether a `sync` event succeeded or failed and whether the sync - event finished in the foreground or background. - -
- A `sync` event finished in the foreground if the associated Service Worker - Registration has a client at the time that the event finished. -
- - - - nator@chromium.org - rayankans@chromium.org - - Records whether a one-shot sync started firing in the foreground or - background. Called shortly before the event is fired. - - - - - - As of 10/2015 this has been replaced by - BackgroundSync.Event.PeriodicResultPattern. - - iclelland@chromium.org - Records whether a periodic sync event succeeded or failed. - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether a periodic sync event succeeded or failed and whether the - sync event finished in the foreground or background. - -
- A sync event finished in the foreground if the associated Service Worker - Registration has a client at the time that the event finished. -
- - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether a periodic sync event started firing in the foreground or - background. Called shortly before the event is fired. - - - - - nator@chromium.org - rayankans@chromium.org - - Time taken to execute a batch of one-shot sync events. A batch is defined as - the set of sync events dispatched at the same time by the - BackgroundSyncManager. One-shots usually run individually (a batch of one), - unless the device was offline and multiple are waiting for the device to go - back online. - - - - - - Removed as of 09/2019. - - nator@chromium.org - rayankans@chromium.org - - Records the result of attempting to cancel a future browser launch using the - GCM Network Manager on Android. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether Google Play Services is available to the Background Sync - system on Android, for scheduling future sync events when the browser is not - running. This will be logged at most once per run. - - - - - - Removed as of 09/2019. - - nator@chromium.org - rayankans@chromium.org - - Records the result of attempting to schedule a future browser launch using - the GCM Network Manager on Android. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether the browser has sufficient permissions to create a - BackgroundSyncNetworkObserver object on Android, at the point when it tries - to create it. This should never be false, but is being tracked in order to - help resolve crbug.com/545473. - - - - - - Removed as of 03/2019. - - rayankans@chromium.org - - Whether the Background Sync dispatch conditions changed between scheduling - the operation and dispatching the event. This is collected right before the - event is dispatched. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - Records time elapsed since the soonest expected wake-up time. Recorded - whenever a periodic Background Sync Chrome wake-up task is called after - loading the native parts of the browser. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the result of attempting to register a one-shot sync. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the result of attempting to register a one-shot sync in a situation - where the sync could fire immediately. - - - - - nator@chromium.org - rayankans@chromium.org - peter@chromium.org - - Records whether the dispatched sync event succeeded at the completion of the - one-shot Background Sync registration. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether a one-shot sync registration exactly duplicates an existing - registered sync. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the number of times a sync event was dispatched for a one-shot - Background Sync registration before it succeeded. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the result of attempting to register a periodic sync. This is called - at each successful registration. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether a periodic sync registration duplicates the tag of an - existing registered sync. Recorded upon each successful periodic Background - Sync registration. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the minInterval requested, in seconds, when a periodic sync is - successfully registered. - - - - - - Stopped recording as of 2/2016. - - iclelland@chromium.org - - Records the result of attempting to unregister a one-shot sync. - - - - - nator@chromium.org - platform-capabilities@chromium.org - - Records the result of attempting to unregister a periodic sync. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - If BackgroundSync uses BackgroundTaskScheduler to wake up Chrome, this - records the time elapsed since the soonest expected wake-up time. Recorded - whenever a BackgroundSync background task is called after loading the native - parts of the browser. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - If Chrome is woken up by the one shot Background Sync Background task, this - records whether any sync events were fired as a result. Recorded whenever - Chrome is woken up to process one-shot Background Sync registrations on - Android. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - If Chrome is woken up by the periodic Background Sync Background task,this - records whether any periodicsync events were fired as a result. Recorded - whenever Chrome is woken up to process periodic Background Sync - registrations on Android. - - - - - ssid@chromium.org - Records the reason for unwind failues in sampling profiler. - - - - phillis@chromium.org - cmumford@chromium.org - The result from updating the app badge on macOS. - - - - - Removed 6/3/2020. No longer needed. - - phillis@chromium.org - cmumford@chromium.org - The result from updating the app badge on Windows. - - - - timvolodine@chromium.org - device-dev@chromium.org - - Number of batteries reported by the UPower service on Linux at the start of - the Battery Status API. - - - - - timvolodine@chromium.org - - Number of internal batteries reported by MacOS at the start of the Battery - Status API. - - - - - timvolodine@chromium.org - - Number of batteries reported by Windows at the start of the Battery Status - API. - - - - - timvolodine@chromium.org - - Whether the Battery Status API was successfully started up on Android. - - - - - - The blacklist is deprecated in favor of third-party DLL blocking. - - csharp@chromium.org - - Records the name hashes of all the dlls that are blocked from the browser - process. - - - - - - Removed at 2015 July. - - csharp@chromium.org - - Counts the number of times a renderer process is started with the browser - blacklist patch. This should never be hit. - - - - - - Replaced by ChromeElf.Beacon.RetryAttemptsBeforeSuccess after the old - blacklist was deprecated. - - csharp@chromium.org - proberge@google.com - - Records the number of attempts needed before the blacklist is properly set - up. This is logged immediately after a successful setup. - - - - - - Replaced by ChromeElf.Beacon.SetupStatus after the old blacklist was - deprecated. - - csharp@chromium.org - - Records the successes and failures when running the browser blacklist setup - code. Used to determine if the blacklist is working as intended during - startup (since the blacklist runs before crash reporting is set up). This - only occurs on Windows. - - - - - shaktisahu@chromium.org - - Records the size of the uncompressed commit messages received by Blimp - compositor. - - - - - shaktisahu@chromium.org - - Records whether connection attempt to the Blimp engine was successful. - - - - - shaktisahu@chromium.org - Records whether Blimp is supported. - - - - shaktisahu@chromium.org - Records whenever a Blimp tab toggles visibility. - - - - - Obsolete as of 05/2019. - - ulan@chromium.org - - Records how a bloated renderer was handled in the browser process. - - - - - - Obsolete as of 05/2019. - - ulan@chromium.org - - Records how a bloated renderer was handled in the resource coordinator - service. - - - - - - Obsolete as of 05/2019. - - ulan@chromium.org - - Records how a bloated V8 heap was handled in the renderer process. It is - emitted the first time V8 heap reaches the heap limit and invokes the - NearHeapLimitCallback. Subsequent invocations of the callback are ignored. - Thus it is emitted once per renderer process run. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Disconnected GATT connection status codes. Used to better understand errors - seen in Android. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Failed GATT connection error codes. Used to better understand errors seen in - Android. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Successful GATT connection result codes. Used to better understand Android - results. - - - - - - Removed as of 04/2019, and replaced by Bluetooth.Availability.v2. This - metric was double-reporting on an error condition. - - kenrb@chromium.org - kpaulhamus@chromium.org - - Determines the availability and capabilities of the Bluetooth driver. This - metric is logged on startup. - - - - - kenrb@chromium.org - kpaulhamus@chromium.org - - Determines the availability and capabilities of the Bluetooth driver. This - metric is logged on startup. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Records how long it takes for the user to select a device either after they - open the UI and Bluetooth is on, or after Bluetooth turns on while the UI is - open. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Records how long it takes for a failed pairing attempt, initiated from - Bluetooth Settings or System Tray, to finish. If the user needed to go - through an auth process during pairing, the time the user took to confirm - that is not included. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Records how long it takes for a successful pairing attempt, initiated from - Bluetooth Settings or System Tray, to finish. If the user needed to go - through an auth process during pairing, the time the user took to confirm - that is not included. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Records success or failure of a pairing attempt (initiated in the UI) to a - peripheral after the user taps that device in the list of discovered - peripherals in Bluetooth Settings or System Tray. - - Suffixed by Bluetooth transport type. View the base histogram to see results - for all transport types aggregated together, and suffixed histograms for the - results of just that particular transport type. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Breaks down why a pairing attempt to a peripheral failed (see - 'Bluetooth.ChromeOS.Pairing.Result'). - - Suffixed by Bluetooth transport type. View the base histogram to see results - for all transport types aggregated together, and suffixed histograms for the - results of just that particular transport type. - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - An enumerated histogram which captures the transport type of devices which - are paired with. Reports of transport types other than classic, BLE, or dual - should be considered concerning and investigated. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Records success or failure of a reconnection attempt to an already paired - peripheral after the user taps that device in the list of peripherals in - Bluetooth Settings or System Tray. Explicitly excludes automatic - reconnection attempts initiated by Chrome OS. - - Suffixed by Bluetooth UI surface. View the base histogram to see results for - all UI surfaces aggregated together, and suffixed histograms for the results - of just that particular UI surfaces. - - - - - - - hansberry@chromium.org - cros-system-services-networking@google.com - - Breaks down why a user-initiated reconnection attempt to a peripheral failed - (see 'Bluetooth.ChromeOS.UserInitiatedReconnectionAttempt.Result'). - - Suffixed by Bluetooth UI surface. View the base histogram to see results for - all UI surfaces aggregated together, and suffixed histograms for the results - of just that particular UI surfaces. - - - - - adlr@chromium.org - - Counts the number of simulataneously connected Bluetooth devices. Used to - direct testing efforts, and by our UI team to determine appropriate UI - sizes. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of calls to BluetoothAdapter::StartDiscoverySession. - Used to prioritize efforts to fix failures of this function. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of calls to BluetoothDiscoverySession::Stop. Used to - prioritize efforts to fix failures of this function. - - - - - - As of 08/2015 this has been replaced by - Bluetooth.Web.Characteristic.ReadValue and - Bluetooth.Web.Characteristic.WriteValue. - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many times each GATT Error has occured. The results will be used - to determine how common this errors are and if we need to provide better - error messages to the users. - - - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many times each macOS GATT error has occured. The results will - be used to determine how commun this errors are and if we need to provide - better error messages to the users. - - - - - adlr@chromium.org - - Records the method used to pair each Bluetooth Device. Used to direct our - testing efforts. - - - - - adlr@chromium.org - - Records the result of pairing each Bluetooth Device. Used to understand - whether we are having significant problems with Bluetooth pairing and seeing - errors more commonly than we should. - - - - - - Removed 08/2015 and replaced by Bluetooth.Web.RequestDevice.Outcome. - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of a navigator.bluetooth.requestDevice() call. Used to - understand what errors developers are getting so we can target efforts - toward the most common ones. Multiple outcomes may result for a given - RequestDevice, such as rescan multiple times and then select a device. - - - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - 'status' values returned by Android GATT event. - - - - - Removed as of 11/2016, replaced by - Bluetooth.Web.Blocklist.ParsedNonEmptyString. - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of BluetoothBlacklist::Add parsing a non-empty string. - These strings will be updated dynamically by a server, and this histogram - provides feedback that parsing is functioning correctly on clients. - - False values are BAD, a blacklist is failing to be applied correctly. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of BluetoothBlocklist::Add parsing a non-empty string. - These strings will be updated dynamically by a server, and this histogram - provides feedback that parsing is functioning correctly on clients. - - False values are BAD, a blocklist is failing to be applied correctly. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to characteristic.readValue(). Used to know - what types of errors users are seeing. The results will be used to determine - how common these errors are and if we need to provide better error messages - to the users. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to characteristic.startNofications(). Used to - know what types of errors users are seeing. The results will be used to - determine how common these errors are and if we need to provide better error - messages to the users. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to characteristic.writeValue(). Used to know - what types of errors users are seeing. The results will be used to determine - how common these errors are and if we need to provide better error messages - to the users. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Counts how many times users interact with a regular chooser vs. an invalid - chooser. (A chooser is invalid when it's event handler becomes null.) - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of a device.gatt.connect() call. Used to understand what - errors developers are getting so we can target efforts toward the most - common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how long it takes for a connection attempt to fail. Use to let - developers know how to better wait for and handle connection errors. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how long it takes for a device to successfully connect. Use to let - developers know how long it should take to connect to a BLE device. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to descriptor.readValue(). Used to know what - types of errors users are seeing. The results will be used to determine how - common these errors are and if we need to provide better error messages to - the users. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to descriptor.writeValue(). Used to know what - types of errors users are seeing. The results will be used to determine how - common these errors are and if we need to provide better error messages to - the users. - - - - - - Removed as of 3/2017. Replaced by using blink IDL annotation MeasureAs which - appear in Blink.UseCounter.Features. - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Counts the number of times each call to a WebBluetooth function is done. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the UUIDs used when getting a characteristic. The recorded value is - a 31-bit hash of the UUID. Used to know what types of characteristics to - target when building libraries that use the Web Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to getCharacteristic(). Used to understand - what errors developers are getting so we can target efforts toward the most - common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the UUIDs used when getting characteristics. The recorded value is a - 31-bit hash of the UUID. Used to know what types of characteristics to - target when building libraries that use the Web Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to getCharacteristics(). Used to understand - what errors developers are getting so we can target efforts toward the most - common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the UUIDs used when getting a descriptor. The recorded value is a - 31-bit hash of the UUID. Used to know what types of descriptors to target - when building libraries that use the Web Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to getDescriptor(). Used to understand what - errors developers are getting so we can target efforts toward the most - common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the UUIDs used when getting descriptors. The recorded value is a - 31-bit hash of the UUID. Used to know what types of descriptors to target - when building libraries that use the Web Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the outcome of a call to getDescriptors(). Used to understand what - errors developers are getting so we can target efforts toward the most - common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of a GATTServer.getPrimaryService() call. Used to - understand what errors developers are getting so we can target efforts - toward the most common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records what GATT Services are used when connected. The record value is a - 31-bit hash of the Service UUID. This will help us know if we should build - an API for specific services rather than a general Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of a GATTServer.getPrimaryServices() call. Used to - understand what errors developers are getting so we can target efforts - toward the most common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records what GATT Services are used when connected. The record value is a - 31-bit hash of the Service UUID. This will help us know if we should build - an API for specific services rather than a general Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many filters are used when scanning. These results will help us - better understand the uses of the API and make changes according to - developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records a 31-bit hash of the GATT Service UUIDs used when scanning. This - will help us know if we should build an API for specific services rather - than a general Bluetooth API. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many services are used in a filter. These results will help us - better understand the uses of the API and make changes according to - developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - juncai@chromium.org - - In the case of not accepting all devices, records the number of devices that - are in the chooser when a device is paired. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many optional services are used when scanning. These results - will help us better understand the uses of the API and make changes - according to developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records what optional services are used. The recorded value is a 31-bit hash - of the Service UUID. These results will help us better understand the uses - of the API and make changes according to developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the value of 'acceptAllDevices' in RequestDeviceOptions. These - results will help us better understand the uses of the API and make changes - according to developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records the result of a navigator.bluetooth.requestDevice() call. Used to - understand what errors developers are getting so we can target efforts - toward the most common ones. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - juncai@chromium.org - - Raw RSSI values provided to chooser, before processing them for display in - the Web Bluetooth chooser. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - juncai@chromium.org - - Displayed RSSI levels, after processing and as displayed to users in the Web - Bluetooth chooser. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - juncai@chromium.org - - Records the duration scanning for devices is run, terminated by events such - as the chooser being closed with a selected device, cancelled, or the scan - duration timing out. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records how many services are used when scanning. This results will help us - better understand the uses of the API and make changes according to - developers' behavior. - - - - - odejesush@chromium.org - ortuno@chromium.org - reillyg@chromium.org - - Records what services are used from either required or optional sets. The - recorded value is a 31-bit hash of the Service UUID. These results will help - us better understand the uses of the API and make changes according to - developers' behavior. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records a duration of a Bluetooth adapter - being lost. This helps us better understand the Bluetooth controller drop - issue in the field. - - - - - - Replaced 08/2018 by BlueZ.ChipLost2 for more suspend/resume filtering even - when the Bluetooth adapter is turned off. - - sonnysasaka@chromium.org - - This is specific to Chrome OS. Records a duration of a Bluetooth adapter - being lost caused by hardware disconnection. This helps us better understand - the Bluetooth controller drop issue in the field. - - - - - sonnysasaka@chromium.org - - This is specific to Chrome OS. Records a duration of a Bluetooth adapter - being lost caused by hardware disconnection. This helps us better understand - the Bluetooth controller drop issue in the field. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the number of existing advertisements - when registering for a new advertisement. This helps us better understand - the common amount of advertisments used and the registration failures due to - the limited number of advertisement slots. - - - - - - - mmandlik@google.com - chromeos-bt-platform-sw-core@google.com - - Records the outcome of bluetooth profile connection request to a remote - device. This helps to understand the percentage of successful profile - connections against failures and the causes of failures. - - - - - - - mmandlik@google.com - chromeos-bt-platform-sw-core@google.com - - Records the outcome of bluetooth profile probing while pairing with a remote - device. This helps to understand the percentage of successful profile - probing against failures and the causes of failures. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the reason of Bluetooth disconnection - between the local device and the remote Bluetooth device. This helps us - better understand the initiator of disconnection request. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the outcomes of advertisement - registration. This helps us better understand the persentage of successful - advertisements against failures and the causes of failures. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the outcomes of connection requests - to remote devices. This helps us better understand the persentage of - successful connections against failures and the causes of failures. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the outcomes of pairing with remote - devices. This helps us better understand the persentage of successful - pairing against failures and the causes of failures. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the duration when the local device is - performing Bluetooth advertisment and discoverable as a Bluetooth Low Energy - device by other devices. This helps us better understand the amount of - successful advertisment sessions and the duration. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the duration when the local device is - discoverable by other devices as a Bluetooth classic device. This helps us - better understand the amount of requests to expose the local device as a - Bluetooth classic device and the duration. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the duration for the local device to - perform device discovery. This helps us better understand the amount of - device discovery request and the duration for users to find the target - device. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the duration taken to finish a - successful pairing between the local device and a remote Bluetooth device. - This helps us better understand the latency of completing Bluetooth pairing. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the duration taken to finish a - successful connection between the local device and a remote Bluetooth - device. This helps us better understand the latency of connecting to a - Bluetooth device. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the types of device discovery - performed by the local device. This helps us better understand the most - common type of device discovery performed. - - - - - mcchou@chromium.org - - This is specific to Chrome OS. Records the types of discovered devices in - terms of Bluetooth classic, Bluetooth low energy and Dual-mode supports. - This helps us better understand the persentage of Bluetooth devices in terms - of type. - - - - - - - calamity@chromium.org - chrome-analysis-team@google.com - - Logs when a user action triggers a command in the bookmark manager. Commands - can be triggered by keyboard shortcuts, menu items or other buttons in the - UI. - - Revised in M-76 when the "Open (double click/enter)" bucket was - split into two separate buckets, one for bookmarks and one for folders. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - Removed as of May 2020. - - calamity@chromium.org - johntlee@chromium.org - - Logs when a keyboard shortcut triggers a command in the bookmark manager. - - Revised in M-76 when the "Open (double click/enter)" bucket was - split into two separate buckets, one for bookmarks and one for folders. - - - - - calamity@chromium.org - - Logs where the menu was opened from when a user action opens the command - menu in the bookmark manager. - - - - - calamity@chromium.org - - Logs the number of bookmarks that were dragged simultaneously by a user. - - - - - - Removed as of July 2020. - - jhimawan@google.com - twellington@google.com - - Logs the number of drag actions that are performed in one session (defined - as the time between a user's opening a folder and closing said folder). - - - - - - Removed as of July 2020. - - jhimawan@google.com - twellington@google.com - - Logs the number of uses of the Move Up / Down buttons in one session - (defined as the time between a user's opening a folder and closing said - folder). - - - - - calamity@chromium.org - dbeam@chromium.org - - Records the time taken to load the bookmarks Web UI and render. This is - roughly equivalent to 'time to first meaningful paint' for the bookmark - manager. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records when a bookmark is added sliced on profile type. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records the count of tabs when a user bookmarks all open - tabs, in incognito mode. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records the count of tabs when a user bookmarks all open - tabs, in regular mode. - - - - - calamity@chromium.org - - Logs the number of bookmark items inside a folder every time a folder is - opened inside the bookmark manager. - - - - - supertri@chromium.org - isherman@chromium.org - aidanday@google.com - mamir@chromium.org - - The total number of bookmarks a user has saved. Recorded when a profile is - opened - precisely, when bookmarks are loaded into storage from disk. The - count includes all bookmarks both in the "Bookmarks Bar" and also - under "Other Bookmarks". - - - - - mamir@chromium.org - mastiz@chromium.org - - The number of bookmarks a user has saved with a URL that is also present in - at least one other bookmark. This excludes folders (which don't have a URL). - Recorded when bookmarks are loaded into storage from disk if there is at - least one duplicate. - - - - - - Removed as of 05/2020. - - mamir@chromium.org - mastiz@chromium.org - - The number of bookmarks a user has saved with an empty title (strictly - speaking, i.e. does not count whitespace-only titles), including folders and - excluding the root. Recorded when bookmarks are loaded into storage from - disk if there is at least one node with an empty title. - - - - - twellington@google.com - chrome-android-app@chromium.org - - Records the number of bookmarks which are opened using the "Open in - incognito tab" button from selection mode in the Android bookmark - manager. - - - - - twellington@google.com - chrome-android-app@chromium.org - - Records the number of bookmarks which are opened using the "Open in new - tab" button from selection mode in the Android bookmark manager. - - - - - mastiz@chromium.org - sky@chromium.org - - Time taken to build the bookmark index. Logged upon profile load when the - bookmarks JSON file is read. - - - - - mastiz@chromium.org - sky@chromium.org - - Time taken to decode the bookmarks JSON file. Logged upon profile load when - the bookmarks JSON file is read. - - - - - mamir@chromium.org - mastiz@chromium.org - - Time to compute values to be logged for UMA metrics - Bookmarks.Count.OnProfileLoad.*. - - - - - ianwen@chromium.org - How users add a new bookmark. - - - - - Removed as of 05/2020. - - mamir@chromium.org - - The size of the file used to persist bookmarks. It's recorded every time the - file is loaded in memory. - - - - - - Removed as of 6/2019. This histogram is no longer necessary. - - yfriedman@chromium.org - - Logs the depth of the bookmark in the bookmark tree hierarchy every time a - bookmark is launched. Depth indicates how many levels below a permanent - bookmark folder the bookmark was found in (e.g. a bookmark immediately in - the bookmark bar has depth 1). - - - - - ianwen@chromium.org - Logs a UI location from which a bookmark is launched. - - - - pkotwicz@chromium.org - - Logs how frequently BookmarkModel::OnFaviconsChanged() is called with a - non-empty |icon_url| to determine whether BookmarkNodes should be cached - based on their favicon URLs (e.g. http://www.google.com/favicon.ico) in - addition to their page URLs (e.g. http://www.google.com). OnFaviconChanged() - is expected to be called less than 10 times per user per day with a - non-empty |icon_url|. - - - - - - Removed as of 1/2016. - - kkimlabs@chromium.org - - Logs how user is opening a bookmark on Android. For example, user can long - press and select "Open in a new tab" or "Open in incognito - tab". - - - - - wychen@chromium.org - - Logs whether the bookmark entry is a user bookmark or a partner bookmark - when it is opened. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - The number of times bookmarks are used in each profile type. Recorded when a - bookmark is clicked. - - - - - - Replaced 08/2016 by BootTime.Total2 with larger range and more buckets. - - bccheng@chromium.org - semenzato@chromium.org - Time from power on to login panel ready (Chrome OS). - - - - bccheng@chromium.org - semenzato@chromium.org - Time from power on to login panel ready (Chrome OS). - - - - eustas@chromium.org - Compressed/Decompressed size ratio. - - - - eustas@chromium.org - More detailed failure reason. - - - - - Removed in M76. - - eustas@chromium.org - Indicates whether the gzip-like header was detected. - - - - eustas@chromium.org - The final state of BrotliFilter. - - - - eustas@chromium.org - Maximal amount of memory allocated by decoder. - - - - manukh@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - The time elapsed decoding an image using BitmapFetcher. - - - - manukh@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - The time elapsed fetching an image from a URL using BitmapFetcher. - - - - - lgrey@chromium.org - robliao@chromium.org - - Whether the user's system is in dark mode, light mode, or if this choice is - unavailable due to lack of system support. Updated every UMA upload. - - - - - - Removed 05/2020. Was not substantially different from results in the GPU - process. - - ccameron@chromium.org - graphics-dev@chromium.org - - Compiling a MTLLibrary will sometimes hang forever. When initializing the - browser process, a test shader is compiled to see if the MTLCompilerService - is responding or not. This records the time that it took for the compile to - succeeded, up to 1 minute. After 1 minute, a timeout sentinel value of 3 - minutes is reported. - - - - - - Removed 05/2020. Did not reveal interesting results. - - ccameron@chromium.org - graphics-dev@chromium.org - - Compiling a MTLLibrary will sometimes hang forever. When initializing the - browser process, a test shader is compiled to see if the MTLCompilerService - is responding or not. This records the time that it took for the compile - method to finish (not including the time for the compile itself to finish), - up to 1 minute. After 1 minute, a timeout sentinel value of 3 minutes is - reported. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the size of a compressed on-disk capture for the paint preview after - a proto is written to disk if compressed. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the number of frames captured by a paint preview if it succeeded. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records a boolean indicating whether a capture attempt was successful. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the total time spent capturing a paint preview of a page. This - includes capture and serialization of all frames and IPC time. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the size of an uncompressed on-disk capture for the paint preview - after a proto is written to disk if not compressed. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the compressed on-disk size of the capture if it succeeded for the - capture experiment. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the ratio of success to failure for the Paint Preview capture - experiment. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records if the paint preview compositor process started correctly. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the time it took to start the paint preview compositor process. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - Records when a link is clicked in the paint preview player. - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the time taken to from the request to start the compositor process - to the first bitmap being loaded. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the the reason for exiting the compositor process for the - TabbedPaintPreviewPlayer. Recorded when the compositor returns an error or - disconnects. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the the reason for exiting TabbedPaintPreviewPlayer. Recorded when - paint preview is removed. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records whether paint preview was drawn before the tab finished loading. - Recorded when tab has finished loading. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records whether a paint preview exists. Recorded when attempting to show a - preview on startup. This in conjuction with CompositorFailureReason gives - the total number of failures to show a paint preview. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the number of times that the upgrade snackbar was shown in a session - of TabbedPaintPreviewPlayer. Recorded when paint preview is removed. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the time taken to from actvity creation to the first bitmap being - shown. Recorded on first paint preview paint event. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the length of the time that a session of TabbedPaintPreviewPlayer - lasts. Recorded when paint preview is removed. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the total disk usage by the Paint Preview Tab Service at startup of - the profile keyed service. - - - - - gab@chromium.org - olivierli@chromium.org - - Similar to Browser.Responsiveness.IOJankyIntervalsPerMinute but sums janky - events across all foreground threads over the monitored minute rather than - considering each interval a boolean. This aims to cover a blind spot of - IOJankyIntervalsPerMinute as it cannot see an improvement where we unblock - 19/20 threads performing I/O. Not reported across system sleep. More details - @ https://bit.ly/chrome-io-jank-metric - - - - - gab@chromium.org - olivierli@chromium.org - - This metric is emitted every minute. It reports a number between 0 and 60 - which corresponds to the number of 1 second intervals during the monitored - minute to which a stalled foreground thread - ScopedBlockingCall(BlockingType::MAY_BLOCK) was attributed. A stalled call - is first attributed to the interval in which it began, and is attributed to - a number of intervals equal to the length of the call, rounded to the - nearest second. (Before http://crrev.com/c/2314873, the length was truncated - rather than rounded.) This aims to capture moments where the main thread is - responsive but the application is not (because things aren't loading). Not - reported across system sleep. More details @ - https://bit.ly/chrome-io-jank-metric - - - - - - - erikchen@chromium.org - tdresser@chromium.org - chrome-analysis-team@google.com - - This metric is emitted every 30 seconds [when there is user activity]. Each - 30 second duration is divided into 100ms intervals. This metric counts the - number of these intervals that were "janky". See - https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit - for more details. - - On desktop platforms, this metric measures native events, as well as tasks - posted to the UI and IO threads of the browser process. On Android, this - metric only measures tasks posted to the UI and IO threads. - - Update (October 27th 2019): The responsiveness::Watcher emitting this metric - previously started observation before the main message loop was running, - this resulted in the 99th percentile being mostly comprised of slow startups - (before the message loop gets to run). This was fixed and a fake-improvement - in the high percentiles is expected when the fix goes live. - - Update (M82 March 2020): Stopped recording background intervals on Android. - - Due to a bug, this metric does not measure long queueing time as jankiness. - It only measures jankiness as individual tasks taking a long time to run. - Given that it's a long-standing bug, this metric will not be modified. We - are testing a new metric - Browser.Responsiveness.JankyIntervalsPerThirtySeconds2 that correctly - accounts for queueing time. See - https://groups.google.com/a/google.com/forum/#!topic/chrome-scheduler/X32gKl6fW2A - for more details. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - erikchen@chromium.org - tdresser@chromium.org - fdoray@chromium.org - chrome-analysis-team@google.com - - This metric is emitted every 30 seconds after main message loop start, when - there is user activity. Each 30 second duration is divided into 100ms - intervals. This metric counts the number of these intervals that were - "janky". An interval is janky if during it the UI or IO thread - executes an "important" task that was queued more than 100 ms ago, - or a non-important task or a native event handler that started executing - more than 100 ms ago. See - https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit - for more details. - - Update (M82 March 2020): Stopped recording background intervals on Android. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - ejoe@google.com - jonross@chromium.org - - The time between input event timestamp for tab switch and when the - TabStripModel begins processing the switch. - - - - - sadrul@chromium.org - sky@chromium.org - - The time it takes for the browser to request a tab to be visible. Note that - this only measures the time from the browser deciding to make the tab - visible (after a click, or keyboard-shortcut to switch tabs), until the tab - is requested to become visible. The time it takes to actually make the tab - visible and show on screen is measured in a separate metric, in - RWH_TabSwitchPaintDuration. - - - - - - - fdoray@chromium.org - Whether a frame was presented after a tab switch event. - - - - - - fdoray@chromium.org - jonross@chromium.org - - The time between a tab switch input event timestamp and when the tab is - hidden, if no frame is presented in the meantime. - - - - - - - ejoe@google.com - jonross@chromium.org - - The time between the input event timestamp and the frame presentation time - on a tab switch. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Number of open guest windows at the same time. Recorded when a new guest - window is created. Please note that this metric double counts the lower - numbers, meaning that if user opens three windows (without closing any in - between), then buckets 1, 2, and 3 will all be incremented in turn. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Number of open incognito windows at the same time. Recorded when a new - incognito window is created. Please note that this metric double counts the - lower numbers, meaning that if user opens three windows (without closing any - in between), then buckets 1, 2, and 3 will all be incremented in turn. - - - - - - Removed in M77 with the removal of Browser Actions. - - peconn@chromium.org - - The number of tabs currently opened when users tap "Open in new Chrome - tab" from Browser Actions context menu. This includes the new tab - created from the tap. - - - - - - Removed in M77 with the removal of Browser Actions. - - peconn@chromium.org - - The option that the user selected from a Browser Actions context menu. - - - - - dominickn@chromium.org - meacer@chromium.org - - Whether or not the user checked the option in the external protocol dialog - to remember their choice of opening or not opening the specified app. - Recorded each time the user interacts with the External Protocol Dialog, - when making a decision. - - - - - - Removed 09/2017. This histogram has been replaced with - ExternalProtocol.HandleState. - - dominickn@chromium.org - - Whether or not the user checked the option in the external protocol dialog - to remember their choice of opening or not opening the specified app. - Recorded each time the user interacts with the External Protocol Dialog - (either accepting or cancelling/dismissing). - - - - - ericrobinson@chromium.org - johnidel@chromium.org - - Record the time spent in the background after RenderProcessHost - initialization of the process. Recorded when the RenderProcessHost for the - process is destroyed. - - - - - - - wfh@chromium.org - - Count of renderer process terminations due to a code integrity failure, - grouped by type. This is only reported on Windows. - - - - - wfh@chromium.org - Count of renderer process crashes grouped by type. - - - - wfh@chromium.org - Count of renderer process kills grouped by type. - - - - oshima@chromium.org - - Out of BrowserRenderProcessHost.ChildKills, numer of kills due to SIGKILL, - which is a strong signal of out of memory on Chrome OS, grouped by renderer - type. - - - - - - - wfh@chromium.org - - The launch error codes for failed renderer process launches. - - - - - - - wfh@chromium.org - Count of renderer process launch failures grouped by type. - - - - - - wfh@chromium.org - - Count of renderer process crashes that we miscounted because we took the - exit code too early. Grouped by type. - - - - - ericrobinson@chromium.org - csharrison@chromium.org - - Determines what combination of low and normal priority frames were attached - to a render process during its lifetime. Recorded when the host for the - render process is destroyed. - - - - - boliu@chromium.org - alexmos@chromium.org - - Recorded at most once per renderer process when it first becomes invisible - and has media stream. Record the frame depth of the process. Note this - metric is only meaningful when some form of OOPIF is enabled; otherwise - frame depth is always 0. - - - - - - Removed June 2019. - - horo@chromium.org - - How long a render process is kept alive by additional customers such as - shared workers and service workers. - - - - - - Removed June 2019. - - panicker@chromium.org - - How long fetch is alive which in turn keeps the render process alive. - TODO(panicker): Remove after investigation of crbug/823482, likely in M68. - - - - - - Removed June 2019. - - panicker@chromium.org - - How long service worker is alive which in turn keeps the render process - alive. TODO(panicker): Remove after investigation of crbug/823482, likely in - M68. - - - - - - Removed June 2019. - - panicker@chromium.org - - How long shared worker is alive which in turn keeps the render process - alive. TODO(panicker): Remove after investigation of crbug/823482, likely in - M68. - - - - - - Removed June 2019. - - alexmos@chromium.org - panicker@chromium.org - - How long the renderer process is kept alive by a subframe unload handler. - TODO(panicker): Remove after investigation of crbug/823482. - - - - - - Removed Feb 2020. - - wfh@chromium.org - - Number of times BrowserRenderProcessHost::OnChannelError was called. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Records what happens when an attempt is made to use a spare - RenderProcessHost - logs that either the attempt succeeded or why it failed. - - - - - ericrobinson@chromium.org - johnidel@chromium.org - - Record the lifetime of the RenderProcessHost after initialization of the - process. Recorded when the RenderProcessHost for the process is destroyed. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when we check whether a Trusted Web Activity client app can handle - Browsable Intents. It measures how long consulting the Android - PackageManager takes. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when any Android app is uninstalled or has its data cleared. This - measures how long it takes to read data from Preferences to determine - whether we need to act. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when an Android background service attempts to create a Tab. We - time how long the Android package manager queryIntentActivities call takes. - - - - - - Retired in M77 in favour of BrowserServices.TwaOpenTime.V2 which uses a more - appropriate timescale. - - peconn@chromium.org - peter@chromium.org - - Triggered when a TrustedWebActivity is paused, recording the time since it - had been resumed. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when a TrustedWebActivity is paused, recording the time since it - had been resumed. - - - - - peconn@chromium.org - peter@chromium.org - - The result of Digital Asset Link verification performed when starting a - Trusted Web Activity. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when Trusted Web Activity verification completes. Records how long - it takes the device to realise it is offline and fall back to the cached - result. - - - - - peconn@chromium.org - peter@chromium.org - - Triggered when Trusted Web Activity verification completes. Records how long - verification took when online. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records which browser the Legacy Browser Support feature is configured to - open (which defaults to IE). Recorded on browser startup, and when the value - changes. Only measured when Legacy Browser Support is enabled via the - BrowserSwitcher* policies. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records whether the "AppData/Local/Google/BrowserSwitcher" - directory was successfully created. Windows only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records whether a temp file in - "AppData/Local/Google/BrowserSwitcher" the directory was - successfully created. Windows only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records whether the temp file in - "AppData/Local/Google/BrowserSwitcher" directory was successfully - moved to its final destination ("cache.dat") after writing its - contents. Windows only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - On navigation and redirect, whether to switch browsers or not. Only measured - when Legacy Browser Support is enabled via the BrowserSwitcher* policies. - When this is true, Chrome attempts to launch an alternative browser - (typically IE) with the navigation URL. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - On navigation and redirect, records how long it took to compute a decision - (stay in Chrome/open in IE). Only measured when Legacy Browser Support is - enabled via the BrowserSwitcher* policies. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Number of rules that come from an external greylist XML file. Measured when - the sitelist is loaded during browser startup. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Number of rules that come from an external sitelist XML file. Measured when - the sitelist is loaded during browser startup. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Number of rules in the BrowserSwitcherUrlGreylist policy. Measured when the - policy is loaded. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Whether there is a wildcard ("*") rule in the - BrowserSwitcherUrlGreylist policy. Measured when the - BrowserSwitcherUrlGreylist policy gets updated. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Number of rules that come from Internet Explorer Enterprise Mode's sitelist. - Measured when the sitelist is loaded during browser startup. Windows only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records whether an attempt to launch an alternate browser failed or - succeeded. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Records how long it took to launch an alternate browser (regardless of - whether it failed or succeeded). Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Number of rules in the BrowserSwitcherUrlList policy. Measured when the - policy gets updated. Desktop Chrome only. - - - - - nicolaso@chromium.org - pastarmovj@chromium.org - - Whether there is a wildcard ("*") rule in the - BrowserSwitcherUrlList policy. Measured when the BrowserSwitcherUrlList - policy gets updated. Desktop Chrome only. - - - - - - Obsolete since 01/2020: mus+ash project was canceled, and these metrics are - no longer useful. - - sadrul@chromium.org - mustash-team@google.com - - Duration of an interactive resize from start to end. Measured only on - Windows. - - - - - - Obsolete since 01/2020: mus+ash project was canceled, and these metrics are - no longer useful. - - sadrul@chromium.org - - Size changed between two consecutive steps during browser-window resize. - Measured only on Windows. - - - - - - Obsolete since 01/2020: mus+ash project was canceled, and these metrics are - no longer useful. - - sadrul@chromium.org - - Number of intermediate resize-steps taken to complete the resize from start - to end. Measured only on Windows. - - - - - - Obsolete since 01/2020: mus+ash project was canceled, and these metrics are - no longer useful. - - sadrul@chromium.org - - Time-interval between two consecutive steps during browser-window resize. An - interactive resize can have many number of small steps. This measures the - interval between two steps. 'Duration' measures the interval between the - first and last steps. Measured only on Windows. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was closed because the user accepted it. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - - An open bubble was closed because the user didn't accept it. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was closed because of a focus change. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was forced to close. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was dismissed because a frame was destroyed. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - - An open bubble was dismissed because fullscreen was toggled. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - - An open bubble was dismissed because the page was navigated. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was closed because a tab was detached. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - An open bubble was closed because a tab was switched. - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - - An open bubble was dismissed by the user without making a decission. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - - Log the amount of time any bubble was visible. Only bubbles that are shown - will have a visible time. - - - - - - No longer used; generating code removed in M81. - - hcarmona@chromium.org - A bubble was given to the bubble manager but not shown. - - - - - Renamed to ImageFetcher.Events on 04/2019. - - fgorski@chromium.org - wylieb@chromium.org - - Events that track the lifecycle and performance of the cached_image_fetcher. - The events reported include: success/failure conditions, various recoverable - errors and a couple of dead-end errors. - - - - - - Renamed to ImageFetcher.ImageLoadFromCacheTime on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the cache - in native. - - - - - - Renamed to ImageFetcher.ImageLoadFromCacheTimeJava on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the cache - in Java. - - - - - - Renamed to ImageFetcher.ImageLoadFromNativeTimeJava on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from native - code. Only recorded on successful loads. - - - - - - Renamed to ImageFetcher.ImageLoadFromNetworkAfterCacheHit on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the network - after a cache hit. - - - - - - Renamed to ImageFetcher.ImageLoadFromNetworkTime on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the - network. - - - - - - Renamed to ImageFetcher.LoadImageMetadata on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes to load an image's metadata from the metadata store. - - - - - - Renamed to ImageFetcher.TimeSinceLastCacheLRUEviction on 06/2019. - - fgorski@chromium.org - wylieb@chromium.org - - The time since the last LRU eviction from the image cache. Recorded when two - LRU evictions occur within closure proximity to one another. Will be used to - determine if LRU eviction is happening too frequently. - - - - - - Replaced with Blink.Canvas.ContextType in 10/2018. - - fserb@chromium.org - kbr@chromium.org - - Records the context type names used to create canvas rendering contexts. - - - - - - Replaced with Blink.Canvas.CreateImageBitmapSource in 10/2018. - - fserb@chromium.org - zakerinasab@chromium.org - - The source from which an ImageBitmap is created by a createImageBitmap call. - - - - - - Removed 11/2017 with removal of Display List Canvas 2D mode. - - fserb@chromium.org - - The reasons why a canvas initially set to display list mode had to fall back - to direct rasterization mode. - - - - - - Replaced with Blink.Canvas.GPUAccelerated2DCanvasDisableDeferralReason in - 10/2018. - - fserb@chromium.org - - The reasons why a GPU accelerated canvas stopped deferring its rendering - operations. - - - - - - Replaced with Blink.Canvas.HibernationEvents in 10/2018. - - fserb@chromium.org - aaronhk@chromium.org - - Records the occurrence of events related to 2D canvas GPU resource - hibernation. - - - - - - Removed 10/2018 with Blink.OffscreenCanvas histograms - - xidachen@chromium.org - fserb@chromium.org - - The type of code path that OffscreenCanvas's commit API goes through. - - - - - - The experiment finishes and removed in 03/2020 - - yiyix@chromium.org - fserb@chromium.org - - measure the percentage of Canvas is dirty before each repaint by using - cc::Rect. Note that we record this metrics for all canvas that has an area - of more than 65k pixel^2 (256x256). - - - - - - The experiment finishes and removed in 03/2020 - - yiyix@chromium.org - fserb@chromium.org - - measure the percentage of Canvas is dirty before each repaint by using - cc::Region. Note that we record this metrics for all canvas that has an area - of more than 65k pixel^2 (256x256). - - - - - - Replaced with Blink.Canvas.RequestedImageMimeTypes in 10/2018. - - aaronhk@chromium.org - - Records the occurence of image file formats passed into toDataURL and toBlob - functions in canvas. - - - - - - Removed 2019/08, this metrics doesn't reflect the measurement speed because - it is dependent on the length of text. - - yiyix@chromium.org - fserb@chromium.org - - Time spent in microseconds to perform calls to measure TextMetrics for - Canvas2d. It's measured each time TextMetrics is called. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - yiyix@chromium.org - fserb@chromium.org - - Time spent in microseconds to perform calls to SetFont in Canvas for - Canvas2d. It's measured each time SetFont is called. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 08/2016 with removal of Chrome Crash Service component. - - scottmg@chromium.org - - Tracks the component updater steps for the Chrome Crash Service. - - - - - mmourgos@chromium.org - newcomer@chromium.org - - Within one minute of the default network reporting a portal network, if we - see an offline detection result, it is likely the client got blacklisted. - Record the boolean rate that Chrome observes offline vs non-offline - detection results. See go/bad-portal for client blacklisting problem. - - - - - meacer@chromium.org - Records the result of a captive portal probe. - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - Count of displayed and not displayed due to errors notifications about - captive portal. - - - - - - Retired in M85. - - pmarko@chromium.org - cros-networking@google.com - cros-oac@google.com - - Count of clicked, closed and ignored captive portal notifications. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - Duration of the captive portal detection process for a particular network at - OOBE. Detection duration is recorded each time portal detection is completed - for an active network. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - The result of captive portal detection attempts performed at OOBE. Detection - result is recorded when portal detection is completed for an active network - and when it differs from the previous result for the same network. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - The result of captive portal detection attempts at OOBE if it diverges from - network manager results. Detection result is recorded each time portal - detection is completed for an active network. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - Number of milliseconds passed between consecutive reports for the same - network about portal and online states. - - - - - ericorth@chromium.org - doh-core@google.com - cros-networking@google.com - - Reason for attempting a captive portal probe. This is logged only when a - probe HTTP request is made. If there are multiple reasons that triggered - this probe, only the first is logged. - - - - - - Retired in M85. - - pmarko@chromium.org - cros-networking@google.com - cros-oac@google.com - - Number of milliseconds between start of request to gstatic.com/generate_204 - and receipt of response with redirect to captive portal login page. - - - - - - Retired in M85. - - pmarko@chromium.org - cros-networking@google.com - - Duration of the captive portal detection process for a particular network in - user session. Detection duration is recorded each time portal detection is - completed for an active network. - - - - - - Retired in M85. - - pmarko@chromium.org - michaeldo@chromium.org - cros-networking@google.com - cros-oac@google.com - - The result of captive portal detection attempts performed in user session. - Detection result is recorded when portal detection is completed for an - active network and when it differs from the previous result for the same - network. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - The result of captive portal detection attempts in session if it diverges - from network manager results. Detection result is recorded each time portal - detection is completed for an active network. - - - - - - Retired in M85. - - rsorokin@chromium.org - cros-networking@google.com - cros-oac@google.com - - Number of milliseconds passed between consecutive reports for the same - network about portal and online states. - - - - - - Retired in M86. - - michaeldo@chromium.org - cros-networking@google.com - - The result of captive portal detection attempts performed in user session. - Detection result is recorded when portal detection is completed for a failed - secure connection. - - - - - - Retired in M86. - - michaeldo@chromium.org - cros-networking@google.com - - The result of captive portal detection attempts performed in user session. - Detection result is recorded when portal detection is completed for a - request which timed out or hadn't yet replied within eight seconds. - - - - - - - ryanchung@google.com - - Records the result of the Cast certificate verification on the Cast sender. - - - - - - - ryanchung@google.com - - Records whether the correct nonce challenge was in the Cast receiver's - response. - - - - - - - ryanchung@google.com - - Records whether the signature returned by the Cast receiver is verifiable - with the challenge and device certificate. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Records the time the network has been down on a Cast device. Recorded when - network goes up. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Records the time the network has been up on a Cast device. Recorded when - network goes down. - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - Records the number of times the cast button was shown to the user. The value - will be true if the button is enabled, and false if the button is disabled. - Note that depending on the current UX, it's possible that we hide the button - entirely if it's disabled, so it's possible for the false values to be 0. - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - Records the number of times the cast button was shown to the user when the - video is fullscreened. The value will only be recorded on entering - fullscreen. The value will be true if the button is enabled, and false if - the button is disabled. Note that depending on the current UX,it's possible - that we hide the button entirely if it's disabled, so it's possible for the - false values to be 0. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - Records the media type of every video being cast. - - - - maybelle@chromium.org - miguelg@chromium.org - - Records the result of a request to play remotely on a per player app basis - within Chrome for Android. - - - - - - Removed 04/2014, and replaced by Cast.Sender.CastPlayerResult. - - maybelle@chromium.org - miguelg@chromium.org - - Records the result of a request to play remotely. The value will be true if - the playback succeeded, and false if there was an error. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Records the percentage of the video left at the time the remote playback is - stopped. This will be recorded when the playback is stopped by the user, or - when it's stopped by the cast device. - - - - - tguilbert@google.com - media-dev@chromium.org - - Records the type of the remote playback device selected by the user. This - will be recorded when the user has chosen the device from the media route - chooser dialog. - - - - - tguilbert@google.com - media-dev@chromium.org - - Record each interaction with the fullscreen remote playback controls in - cases when the corresponding media element on the page was present. - - - - - tguilbert@google.com - media-dev@chromium.org - - Record each interaction with the fullscreen remote playback controls in - cases when the corresponding media element on the page was not present. - - - - - tguilbert@google.com - media-dev@chromium.org - - Indicates whether the corresponding media element on the page was present - when the fullscreen remote playback controls were shown. - - - - - - Removed July 2017 in favor of Media.Controls.CTR.CastOverlayButton. - - mlamouri@chromium.org - media-dev@chromium.org - - Records events and user interactions related to the Cast overlay shown on - video elements. - - - - - tguilbert@google.com - media-dev@chromium.org - - Records the ratio of the time the media element was detached from the remote - playback session to the total duration of the session (as from when the - element has been attached till when the session stopped or disconnected), in - percents. - - - - - tguilbert@google.com - media-dev@chromium.org - - Records the result of resolving the video URL for cast, including checking - its CORS header. - - - - - posciak@chromium.org - - Indicates whether initialization of a video encode accelerator for Cast - sender was successful. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - The latency between when a Cast V2 connection is established and the first - message is received on that connection. "Unknown" is the peer - type, which is not known at this point in the CastV2 connection - establishment. Naming conforms to the CastV2 sender-side histogram naming - convention "CastV2.[action].[name].[peer_type]". - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - On accepting a Cast V2 transport socket connection, if an error is - encountered, the error code is logged here. "Unknown" is the peer - type, which is not known at this point in the CastV2 connection - establishment. "SslHandshake.Error" is the name of the action. - Naming conforms to the CastV2 sender-side histogram naming convention - "CastV2.[action].[name].[peer_type]". - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - The time taken to do the handshake during Cast V2 transport socket creation. - "Unknown" is the peer type, which is not known at this point in - the CastV2 connection establishment. Naming conforms to the CastV2 - sender-side histogram naming convention - "CastV2.[action].[name].[peer_type]". - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The count of cellular device activation failures (Chrome OS). - - - - - - Removed 07/2020 because the histogram is neither logged nor owned. - - Please list the metric's owners. Add more owner tags as needed. - The count of cellular device activation tries (Chrome OS). - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The count of cellular reconnect failures during activation (Chrome OS). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The count of cellular device reconnect tries during activation (Chrome OS). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The count of successful cellular plan established (Chrome OS). - - - - - - Removed 07/2020 because it is unowned and did not appear to be needed. - - Please list the metric's owners. Add more owner tags as needed. - - The count of initiated cellular device setup starts (Chrome OS). - - - - - - Removed logging on 07/2020; the histogram is unowned and has been marked as - obsolete since 04/2016. - - Please list the metric's owners. Add more owner tags as needed. - The count of failed cellular plan setup tries (Chrome OS). - - - - - Removed logging on 07/2020; the histogram is unowned and has been marked as - obsolete since 04/2016. - - Please list the metric's owners. Add more owner tags as needed. - The count of failed cellular plan purchases (Chrome OS). - - - - - Removed logging on 07/2020; the histogram is unowned and has been marked as - obsolete since 04/2016. - - Please list the metric's owners. Add more owner tags as needed. - - The count of successfully completed cellular plan purchases (Chrome OS). - - - - - - Removed as of 8/2013. This histogram only considered the leaf certificate - expiry date as a proxy for whether a certificate was in-scope for the BRs, - but did not consider the issuance date. As some CAs have issued long-lived - certs prior to the BRs, this disproportionately reported those certs as - being subject to the BRs, but non-compliant, when in reality they're not - subject. - - Please list the metric's owners. Add more owner tags as needed. - - Information about the certificate algorithms and sizes in use on the web, to - examine compliance with the CA/Browser Forum requirements and security best - practice. - - - - - - - - - rsleevi@chromium.org - - Information about the certificate algorithms and sizes in use on the web, to - examine compliance with the CA/Browser Forum requirements and security best - practice. This histogram considers the notBefore as the issuance date, for - purposes of what requirements apply. - - - - - sinhak@chromium.org - escordeiro@chromium.org - - Number of forced logouts for child accounts on an account reconciliation - error. Check |ChromeOSChildAccountReconcilorDelegate|. - - - - - jam@chromium.org - - Count of child processes killed because they sent an IPC that couldn't be - deserialized. - - - - - - Removed 3/2013. Renamed to ChildProcess.Crashed2. - - Please list the metric's owners. Add more owner tags as needed. - Count of child process crashes grouped by process type. - - - - - - wfh@chromium.org - chrome-stability-core@google.com - - Recorded when a crash occurs in a Utility process. On crash, the exit code - will indicate the exception code of the crash. - - - - - wfh@chromium.org - chrome-stability-core@google.com - - Count of child utility process crashes, bucketed by the hash of their - process name. The process name is typically the service name of the mojo - service. - - - - - - - wfh@chromium.org - chrome-stability-core@google.com - Count of child process crashes grouped by process type. - - - - - Removed as of 10/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process crashes that we miscounted because we took the exit - code too early. Grouped by process type. - - - - - - Removed 10/2011. Renamed to ChildProcess.Crashed. - - Please list the metric's owners. Add more owner tags as needed. - Count of child process crashes grouped by process type. - - - - - Removed 10/2011. Renamed to ChildProcess.CrashedWasAlive. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process crashes that we miscounted because we took the exit - code too early. Grouped by process type. - - - - - - Removed as of 10/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process crashes for which we were not able to understand the - exit code, grouped by process type. - - - - - - Removed 3/2013. Renamed to ChildProcess.Disconnected2. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process abnormal channel disconnects grouped by process type. - - - - - wfh@chromium.org - - Count of child process abnormal channel disconnects grouped by process type. - - - - - - Removed 3/2013. Renamed to ChildProcess.DisconnectedAlive2. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process abnormal channel disconnects that are not classified - and reported because we took the exit code too early. Grouped by process - type. - - - - - - - wfh@chromium.org - - Count of child process abnormal channel disconnects that are not classified - and reported because we took the exit code too early. Grouped by process - type. - - - - - asvitkine@chromium.org - - Whether creating field trials from shared memory succeeded. Recorded by each - child process on process startup. - - - - - asvitkine@chromium.org - - Whether creating field trials from --force-fieldtrials switch succeeded. - Recorded by each child process on process startup. - - - - - - Removed 3/2017. - - clamy@chromium.org - - What the browser was waiting for from the renderer when it was reported as - hung. - - - - - cduvall@chromium.org - cmumford@chromium.org - - The amount of avaiable memory when a renderer hangs. Recorded for every - renderer hang. - - - - - - Removed 4/2019. - - cmumford@chromium.org - - What the browser was waiting for from the renderer when it was reported as - hung. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Whether a renderer hang happened in the foreground or background. Recorded - for every renderer hang on Android. - - - - - - Removed 6/2019. - - wfh@chromium.org - - Whether the browser command line had the switch --no-startup-window when a - child process crashed due to invalid sandbox state. Recorded when a child - process crashes if the exit code from the child process is - RESULT_CODE_INVALID_SANDBOX_STATE. - - - - - - Removed 3/2013. Renamed to ChildProcess.Killed2. - - Please list the metric's owners. Add more owner tags as needed. - Count of child process kills grouped by process type. - - - - - - wfh@chromium.org - chrome-stability-core@google.com - Count of child process kills grouped by process type. - - - - oshima@chromium.org - - Out of ChildProcess.Killled, number of kills due to SIGKILL, which is a - strong signal of out of memory on Chrome OS, grouped by process type. - - - - - nasko@chromium.org - - Count of child processes killed by the extension API (processes.terminate). - - - - - - Removed as of 10/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process kills that we miscounted because we took the exit - code too early. Grouped by process type. - - - - - - Removed 10/2011. Renamed to ChildProcess.Killed. - - Please list the metric's owners. Add more owner tags as needed. - Count of child process kills grouped by process type. - - - - - Removed 10/2011. Renamed to ChildProcess.KilledWasAlive. - - Please list the metric's owners. Add more owner tags as needed. - - Count of child process kills that we miscounted because we took the exit - code too early. Grouped by process type. - - - - - wfh@chromium.org - - Count of child utility process launches, bucketed by the hash of their - process name. The process name is typically the service name of the mojo - service. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates how many times each particular type of Activity was in the - foreground when a UMA session was terminated abnormally. UMA sessions last - as long as Chrome remains in the foreground. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates how many times each particular type of Activity was brought to the - foreground when a UMA session was active (i.e. launched at some point). UMA - sessions last as long as Chrome remains in the foreground. - - - - - - Removed 12/2019. - - manzagop@chromium.org - - Indicates the execution phase the browser was in when the browser crashed. - - - - - - Removed as of 11/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates the execution phase the browser was in when browser didn't exit - cleanly. - - - - - - Removed as of 04/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The total number of times the browser process has attempted to generate a - crash dump. This should be the sum of Chrome.BrowserDumpsWithCrash and - Chrome.BrowserDumpsWithNoCrash. - - - - - - Removed as of 04/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times the browser process has attempted to generate a crash - dump because of an actual browser crash. - - - - - - Removed as of 04/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times the browser process has attempted to generate a crash - dump in a non-crashing (i.e., reporting only) context. - - - - - - Removed in 07/2020 because the histogram is unused. - - isherman@chromium.org - src/base/metrics/OWNERS - - The number of command line switches that were present at the start of a - chrome session. - - - - - - Removed in 07/2020 because the histogram is unused. - - isherman@chromium.org - src/base/metrics/OWNERS - - The number of command line switches that were present at the start of a - chrome session, excluding App Mode and User Data Directory switches. - - - - - fdoray@chromium.org - gab@chromium.org - - Track set of Windows errors inside the meessage loop/pump system, where - system calls fail, and we try to gracefully recover. These errors should - really never happen, so we should be sure to look closer if they do. - - - - - gab@chromium.org - - The result of every rendez-vous reported once per browser process launch. - - - - - - Removed as of 12/2017. - - gab@chromium.org - aseren@yandex-team.ru - - The error code of remote process termination on Windows in case when remote - process hung. This histogram has been replaced by - Chrome.ProcessSingleton.TerminateProcessErrorCode.Windows histogram. - - - - - gab@chromium.org - aseren@yandex-team.ru - The reason of remote hang processes termination. - - - - gab@chromium.org - aseren@yandex-team.ru - - Used to send the result of interaction with remote process as histograms in - case when remote process influences on start. - - - - - gab@chromium.org - aseren@yandex-team.ru - - The error code of remote process termination on Posix in case when remote - process hung. - - - - - gab@chromium.org - aseren@yandex-team.ru - - The error code of remote process termination on Windows in case when remote - process hung. - - - - - gab@chromium.org - aseren@yandex-team.ru - - Time it takes from TerminateProcess call to the moment when we stop waiting - for remote process switches to signal state. - - - - - gab@chromium.org - aseren@yandex-team.ru - - The error code of wating for remote process termination on Windows. - - - - - gab@chromium.org - - Time it takes to grab the process singleton. Reported once per successful - attempt at obtaining the singleton. - - - - - gab@chromium.org - - Time it takes to return an error from the process singleton algorithm (nor - succeeding in obtaining it, nor in generating a rendez-vous). This does not - include time spent in the fast notification path (chrome_exe_main_win.cc). - - - - - gab@chromium.org - - Time it takes to find the process singleton owner and notify it. Reported - once per successful rendez-vous. This does not include time spent in the - fast notification path (chrome_exe_main_win.cc). - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user not in the search engine dialog - experiment. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user in the search engine dialog - experiment. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user in slot 1 of a randomized - search engine dialog. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user in slot 2 of a randomized - search engine dialog. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user in slot 3 of a randomized - search engine dialog. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - The default search engine selected by a user in slot 4 of a randomized - search engine dialog. - - - - - yichenz@chromium.org - chromeos-wmp@google.com - - Tracks the animation smoothness for the fade-in animation of tab hover card. - - - - - yichenz@chromium.org - chromeos-wmp@google.com - - Tracks the animation smoothness for the fade-out animation of tab hover - card. - - - - - yichenz@chromium.org - chromeos-wmp@google.com - - Tracks the animation smoothness of tab loading animation. A tracker starts - when the first tab loading animation starts and stops after the last one - stops for each browser window. The metric is emitted when the tracker stops. - - - - - - Removed 6/2017. No longer tracked. - - asvitkine@chromium.org - - Records when a page load happens, based on the same logic as the PageLoad - user action. - - - - - - Removed 12/2019. No longer tracked. - - gayane@chromium.org - yyushkina@chromium.org - - Records applied color id every time its applied from Colors menu. - - - - - - Removed 12/2019. No longer tracked. - - gayane@chromium.org - yyushkina@chromium.org - - Records whether color/theme changes were confirmed or reverted by - ChromeColorsService. - - - - - gayane@chromium.org - yyushkina@chromium.org - - Records installed color id every time theme service is initialized from - prefs. Happens once per profile load. - - - - - - Removed 12/2019. No longer tracked. - - gayane@chromium.org - yyushkina@chromium.org - - Records the reason color/theme changes were reverted by ChromeColorsService. - - - - - chrisha@chromium.org - pmonette@chromium.org - - Records the NTSTATUS result that was returned when attempting to hook - NtMapViewOfSection during chrome_elf.dll initialization. Emitted - asynchronously shortly after startup. - - - - - chrisha@chromium.org - pmonette@chromium.org - - Records the number of attempts needed before third-party DLL blocking was - properly set up. This is logged immediately after a successful setup. Only - recorded on Windows. - - - - - chrisha@chromium.org - pmonette@chromium.org - - Records the successes and failures when running the third-party DLL blocking - setup code, taking into account the safety beacon. Used to determine how - often the third-party DLL blocking is disabled because it failed to - initialize properly twice in a row. Only recorded on Windows. - - - - - chrisha@chromium.org - pmonette@chromium.org - - Records the different status codes that are emitted by chrome_elf.dll while - initializing the NtMapViewOfSection hook used to blocked third-party DLLs. - Multiple status codes can be emitted per initialization since some of those - status codes represent non-fatal failures. E.g. Failure to clear the - previous failure codes. This also means that duplicates are possible. This - is recorded shortly after Chrome launches, since chrome_elf.dll doesn't have - access to the //base API. - - - - - - Removed 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*. - - lizeb@chromium.org - - Time between the intent arrival in a Chrome generated custom tab and the - first navigation commit, if the navigation is successful. Similar in - principle to Startup.FirstCommitNavigationTime. - - - - - - Removed 2017-08 in favor of - ChromeGeneratedCustomTab.IntentToFirstNavigationStartTime. - - lizeb@chromium.org - - In "Herb" mode shows the time between the intent arrival in a - Chrome generated custom tab and the first navigation start (note: not the - navigation commit, as the name suggests). Recorded when the page has - finished loading. - - - - - lizeb@chromium.org - - For Custom Tabs generated by Chrome itself instead of external apps, this - shows the time between the intent arrival in the CCT and the first - navigation start. Recorded when the page has finished loading. - - - - - lizeb@chromium.org - - For Custom Tabs generated by Chrome itself instead of external apps, this - shows time between the intent arrival in the CCT and the first "page - loaded" event, if the navigation is successful. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Measures the model evaluation latency in the Chrome ML Service. This will be - recorded whenever a model evaluation call is invoked on a valid model, - regardless of whether the evaluation result is valid or not. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the model loading result status from the Chrome ML Service. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the decision model prediction result from the Chrome ML Service. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Measures the duration in which the Chrome ML Service is alive. This is - monitored by a service observer in the browser process, and should be - recorded correctly when the service exits either gracefully or unexpectedly. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - Records if the Chrome ML Service crashed. - - - - mcrouse@chromium.org - sophiechang@chromium.org - Records if the Chrome ML Service launched successfully. - - - - mcrouse@chromium.org - sophiechang@chromium.org - Records if the Chrome ML Service terminated normally. - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Whether the ML Service is already running when it is requested. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Measures the model validation latency in the Chrome ML Service. This is - recorded when the ML service receives a model and evaluates it, regardless - of whether the model turns out to be valid or not. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The actions to enable or disable services sending synced notifications. - Synced Notification Sending services can be individually disabled by the - user in the Chrome Notification center settings dialog. - - - - - dominickn@chromium.org - melzhang@chromium.org - mxcai@chromium.org - - Records the response when the intent picker is shown to the user on Chrome - OS to allow them to open an external protocol in an app. - - - - - dominickn@chromium.org - melzhang@chromium.org - mxcai@chromium.org - - Records the response when users that are shown the intent picker accept - opening an external protocol in an app as well as whether the app is - persisted. - - - - - dominickn@chromium.org - melzhang@chromium.org - mxcai@chromium.org - - Records the response when users that are shown the intent picker reject - opening an external protocol in an app. - - - - - elijahtaylor@google.com - dominickn@chromium.org - shihuis@google.com - - Records the response when the intent picker is shown to the user on Chrome - OS to allow them to open a URL in an app. - - - - - elijahtaylor@google.com - dominickn@chromium.org - shihuis@google.com - - Records the app platform chosen (or Chrome if the user did not choose an - app) when the intent picker is shown to the user on Chrome OS. The - destination may be specified due to the user explicit selection or a - previously stored preference. - - - - - dominickn@chromium.org - nancylingwang@chromium.org - - Records whether a notification matches multiple apps, when there is one or - multiple web apps matching a web page nonpersistent notification. - - - - - ajlinker@chromium.org - dominickn@chromium.org - mxcai@chromium.org - - Records the type of app sending a link to the browser to be opened. - - - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the resolution of output stream that is configured by Chrome OS - camera service. - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the process time of ConfigureStreams() method in Chrome OS camera - service. - - This metric is reported for all users and will not cause abnormal - distribution since the metric is Chrome OS specified. - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the type of the error which triggers the Notify() method in Chrome - OS camera service. - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the camera facing of the camera session in Chrome OS camera service. - - - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the process time of the JDA (Jpeg Decode Accelerator) or JEA (Jpeg - Encode Accelerator) run on Chrome OS camera service. There are suffixes that - record the runner method (hardware/software), the runner type - (decode/encode). - - This metric is reported for all users and will not cause abnormal - distribution since the metric is Chrome OS specified. - - - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the resolution of the image that JDA/JEA process by Chrome OS camera - service. The resolution represents by the total pixels contained in the - image. There are suffixes that record the runner method (hardware/software), - the runner type (decode/encode). - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - - Records the process time of OpenDevice() method in Chrome OS camera service. - - This metric is reported for all users and will not cause abnormal - distribution since the metric is Chrome OS specified. - - - - - wtlee@chromium.org - chromeos-camera-eng@google.com - Records the session duration in Chrome OS camera service. - - - - miersh@google.com - pmarko@chromium.org - - The amount of time it took to sign one CSR by certificate provisioning - worker. - - - - - miersh@google.com - pmarko@chromium.org - - Number of times each event is reached during certificate provisioning flow. - - - - - miersh@google.com - pmarko@chromium.org - - The amount of time it took to generate one key pair by certificate - provisioning worker. - - - - - miersh@google.com - pmarko@chromium.org - - For final states (see the list in cert_provisioning::IsFinalState): number - of times certificate provisioning worker finished on every state. For other - states: number of times the worker failed on every state. - - - - - miersh@google.com - pmarko@chromium.org - - The amount of time it took to build one Verified Access response by - certificate provisioning worker. - - - - - - Removed 01/2020 in Issue 1036859 with the removal of the heap collection - code. - - aalexand@google.com - gmx@chromium.org - - A count of successes and various failure modes related to the collection and - processing of Chrome heap sample profiles on Chrome OS. - - - - - aalexand@google.com - gmx@chromium.org - - A count of successes and various failure modes related to collecting and - processing profile data obtained via "perf events" on Chrome OS. - - - - - aalexand@google.com - cwp-team@google.com - - Record the collection status (success or failure) when the Chrome process - and thread types are collected as part of the ChromeOS perf profile - collection. - - - - - cywang@chromium.org - chinglinyu@chromium.org - - Records the status of collection attempts triggered by jankiness on Chrome - OS. - - - - - gmx@chromium.org - cwp-team@google.com - - A count of successes and various failure modes related to the parsing of - logical CPU frequencies on Chrome OS. Recorded when the browser process - starts. - - - - - - Removed 01/2020 in Issue 1036859 with the removal of the heap collection - code. - - aalexand@google.com - gmx@chromium.org - - Records the number of "heap" reports included in an UMA upload on - Chrome OS. - - - - - aalexand@google.com - gmx@chromium.org - - Records the number of "perf events" reports included in an UMA - upload on Chrome OS. - - - - - - Removed 10/2017 and replaced by Platform.DetachableBase.PairResult. - - kitching@google.com - Result of a Chrome OS detachable base pair operation. - - - - - Removed 10/2017 and replaced by Platform.DetachableBase.ROUpdateMetric. - - kitching@google.com - Result of a Chrome OS detachable base RO firmware update. - - - - - Removed 10/2017 and replaced by Platform.DetachableBase.RWUpdateMetric. - - kitching@google.com - Result of a Chrome OS detachable base RW firmware update. - - - - - Removed 8/2017. - - xiaowenx@chromium.org - mukai@chromium.org - - The name of the current color calibration of the display on Chrome OS. This - value is sent when the color calibration is changed by the user. - - - - - tobyhuang@chromium.org - cros-families-eng@google.com - - Categorizes the current user for the Family Experiences team's metrics. A - Supervised User has a supervised primary account and no secondary accounts. - A Supervised Student has a supervised primary account and one or more K-12 - EDU secondary accounts, which is the only available option for a secondary - account in that scenario. A Student at Home has a K-12 EDU primary account - on an unmanaged ChromeOS device, regardless of the secondary account. Other - is for all other users that do not fall into any of the above categories. - - - - - wjmaclean@chromium.org - - Whether the GAIA Authenticator unexpectedly encountered a null contentWindow - value while handling WebView's onContentLoad event. This metric is only - enabled for AuthMode = DEFAULT, which indicates ChromeOS online login. This - is the only mode where the issue has been observed. Other modes not captured - here are OFFLINE (offline ChromeOS login) and DESKTOP (for online GAIA login - on desktop Chrome). - - - - - - Removed in 2020/06 as the histogram is no longer in use. The instrumentation - code is long gone. The iframe flow is not used since 2015. - - achuith@chromium.org - - Whether a user signed in using the new WebView-based GAIA flow. This value - is sent after the GAIA screen has completed user authentication. - - - - - - - itspeter@chromium.org - stimim@chromium.org - chromeos-hw-checker@google.com - - Qualification status of each component types. This entry is generated by - hardware_verifier.conf at boot time. - - - - - itspeter@chromium.org - stimim@chromium.org - chromeos-hw-checker@google.com - Aggregated result of hardware verifier check. - - - - itspeter@chromium.org - stimim@chromium.org - chromeos-hw-checker@google.com - - The amount of time it takes to finish one hardware verification run. - - - - - itspeter@chromium.org - stimim@chromium.org - chromeos-hw-checker@google.com - The amount of time it takes to probe hardware components. - - - - - - jamescook@chromium.org - lacros-team@google.com - - Recorded as part of the metrics session data to identify the lacros-chrome - browser binary. - - - - - zeuthen@chromium.org - - The number of seconds of uptime since the last time the Chrome OS machine-id - was regenerated. This is reported every time the machine-id is regenerated - except for the first time since reboot. - - - - - zeuthen@chromium.org - - The reason why the Chrome OS machine-id was regenerated. This is reported - when the machine-id is re-generated. - - - - - xdai@chromium.org - - The memory pressure level in Chrome OS, which is recorded periodically (once - per second). This is used to show the relative frequency of the system being - in a critical vs relaxed memory pressure state. - - - - - yoshiki@chromium.org - omrilio@chromium.org - - The cause of the scroll event by the user on the message center. Only the - first event after the message center opens is recorded. For example, the - user opens the message center and scrolls by mouse then by key, only the - mouse event is recorded. If the user closes and reopens the message center - before the second event, both events are recorded. - - - - - omorsi@google.com - mgawad@google.com - - Tracks the final result of performing {Operation} operation on an {KeyType} - key in PlatformKeysService. - - - - - - - - - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - Whether platform verification subsystem features are available at the time a - platform verification request is made for content protection on Chrome OS. - - - - - - Removed in 2019/08 as the histogram is no longer in use. (crbug/975047) - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The result of a certificate expiry check during a platform verification - attempt for content protection on Chrome OS. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The result of a platform verification attempt for content protection on - Chrome OS. - - - - - tengs@chromium.org - gzadina@google.com - - Record when the user toggles the integrated privacy screen on/off. See the - PrivacyScreenToggleUISurface enum for all UI surfaces for toggling the - feature. - - - - - mslus@chromium.org - emaxx@chromium.org - - Records every online login authenticated purely with GAIA or with SAML. - - - - - - Removed as of 10/2019. Replaced with ChromeOS.SAML.APILogin that correctly - records various login flows. - - bartfab@chromium.org - - Whether a Chrome OS login via SAML used the principals API. This is recorded - during login on Chrome OS if SAML is being used for authentication. - - - - - mslus@chromium.org - rsorokin@chromium.org - - Records how often users are guided through the SAML in-session password - change flow, and how often it is completed succesfully. - - - - - mslus@chromium.org - mohammedabdon@chromium.org - Records SAML provider when SAML login flow is used. - - - - miersh@google.com - pmarko@chromium.org - - Tracks results of calculating response for a challenge from Verified Access - server for remove attestation during SAML authentication. - - - - - - Removed as of 10/2019. Replaced with ChromeOS.SAML.Scraping.PasswordCountAll - that fixes the main case of a single scraped password. - - bartfab@chromium.org - - The number of passwords that were scraped during a Chrome OS login via SAML. - This is set only when the principals API is not used. - - - - - mslus@chromium.org - emaxx@chromium.org - - The number of passwords that were scraped during a Chrome OS login via SAML. - This is set only when the Chrome Credentials Passing API is not used. - - - - - bartfab@chromium.org - - Whether one of the scraped passwords was successfully verified as the user's - password. This is set only when the Chrome Credentials Passing API is not - used. - - - - - khorimoto@chromium.org - cros-customization@google.com - - The amount of time between when the settings window becomes blurred and when - the user focuses it again. - - - - - - Removed as of 05/2020 (crbug/1072514). - - jamescook@chromium.org - cros-system-services@google.com - - Records whether the "try your Chrome browser settings" banner was - shown when the user opened a new Chrome OS settings window and also records - interactions with the banner. - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users interact with an element in the Chrome OS's Languages - browser settings page. - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users check/uncheck "Offer to translate pages in this - language" checkbox. - - - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users interact with a toggle in the Chrome OS's Languages - browser settings page. - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users interact with different element in the Chrome OS's - Languages OS settings page. - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users check/uncheck "Offer to translate pages in this - language" checkbox in OS Settings - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users visit a language settings support page for Chrome OS. - - - - - - - myy@chromium.org - essential-inputs-team@google.com - - Records when users interact with a toggle in the Chrome OS's Languages OS - settings page. - - - - - jamescook@chromium.org - cros-system-services@google.com - - The amount of time between the render frame host StartProvisionalLoad event - and the render frame DocumentOnLoadCompleted event for the Chrome OS - settings page. - - - - - jamescook@chromium.org - cros-system-services@google.com - - The amount of time between the render frame host StartProvisionalLoad and - DidFinishDocumentLoad events for the Chrome OS settings page. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The number of characters for queries used to fetch results from the Settings - Search Mojo API. - - - - - - - khorimoto@chromium.org - cros-customization@google.com - The number of clicks before changing a setting. - - - - - - khorimoto@chromium.org - cros-customization@google.com - The number of navigations before changing a setting. - - - - - - khorimoto@chromium.org - cros-customization@google.com - The number of searches before changing a setting. - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The number of search results fetched each time a successful search request - is made to the Settings Search Mojo API. - - - - - jamescook@chromium.org - cros-system-services@google.com - - Records whether the "try your Chrome OS settings" banner was shown - when the user opened a new Chrome browser settings tab and also records - interactions with the banner. - - - - - khorimoto@chromium.org - cros-customization@google.com - - Paths visited within chrome://os-settings. For evaluating popularity and - priorities for OS Settings UI. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The time fetching search results from the Settings Search Mojo API. Recorded - when getSearchHandler().search() completes. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The number of search requests made to the Settings Search Mojo API. For - search requests that succeeded with a response, the number of search - requests that had results which were discarded, and the number of search - requests that were shown to the user. Recorded when - getSearchHandler().search() completes. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The number of search requests made to the Settings Search Mojo API in one - session of the settings app. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - Section search results clicked by user in the OS settings search box. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - Setting search results clicked by user in the OS settings search box. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - Subpage search results clicked by user in the OS settings search box. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - Type of search results clicked by user in the OS settings search box. - - - - - - - khorimoto@chromium.org - cros-customization@google.com - - The time spent on the settings page before changing a setting. - - - - - khorimoto@chromium.org - hsuregan@chromium.org - cros-customization@google.com - - The user action taken when search results exist and are displayed. - - - - - khorimoto@chromium.org - cros-customization@google.com - - The amount of time between when a Chrome OS settings window is opened and - when it is closed. - - - - - dominickn@chromium.org - melzhang@chromium.org - - Records number of apps found for a given intent in the Sharesheet. - - - - - dominickn@chromium.org - melzhang@chromium.org - Records user action on sharesheet invocations. - - - - jamescook@chromium.org - cros-customization@google.com - - Tracks whether browser sync preferences were migrated to the new OS sync - feature (project SplitSettingsSync). Recorded once per session during login. - - - - - - - amehfooz@chromium.org - tengs@chromium.org - - Tracks the animation smoothness for the collapse / expand animation of the - system tray. - - - - - tengs@chromium.org - gzadina@google.com - - Tracks the number of blocked notifiers in the system tray after the user - blocks one or multiple notifiers. Note that this metric records the number - of blocked notifiers *after* the update. - - - - - tengs@chromium.org - gzadina@google.com - - Tracks the number of blocked notifiers in the system tray when it is opened. - - - - - tengs@chromium.org - amehfooz@chromium.org - - The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.) - in the system tray quick settings when it is opened, including pods that - overflow to other pages. See - ChromeOS.SystemTray.Tablet.FeaturePodCountOnOpen for the corresponding - histogram logged in tablet mode. - - - - - tengs@chromium.org - gzadina@google.com - - Records the first interaction the user has with the system tray, which can - be a click/tap on the quick settings or message center bubble. Note that - this interaction could be at any time after the user opens the tray (e.g. 30 - seconds later before the first click). - - - - - tengs@chromium.org - gzadina@google.com - - An enum value how system tray bubble is interacted e.g. by tap (touch - screen), or click (mouse, trackpad, etc.) Reported every time the region - inside system tray bubble is tapped or clicked. - - - - - tengs@chromium.org - gzadina@google.com - - If the value is true, SystemTray is expanded when it's opened. Otherwise, - it's closed when it's opened. - - - - - tengs@chromium.org - gzadina@google.com - - Records the number of notifications that are removed in a single clear all - action by the user. - - - - - yamaguchi@chromium.org - - Type of the support page which user opened by clicking the indicator of - managed device type in the unified system tray bubble. - - - - - tengs@chromium.org - gzadina@google.com - - The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in - the shelf status area whenever a pod appears/disappears. This histogram is - only logged when the device is not in tablet mode, otherwise - ChromeOS.SystemTray.Tablet.ShelfPodCount is logged. - - - - - tengs@chromium.org - amehfooz@chromium.org - - The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.) - in the system tray quick settings when it is opened, including pods that - overflow to other pages. This histogram is only logged when the device is in - tablet mode, otherwise ChromeOS.SystemTray.FeaturePodCountOnOpen is logged. - - - - - tengs@chromium.org - gzadina@google.com - - The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in - the shelf status area whenever a pod appears/disappears. This histogram is - only logged when the device is in tablet mode, otherwise - ChromeOS.SystemTray.ShelfPodCount is logged. - - - - - tengs@chromium.org - gzadina@google.com - - The amount of time a user took from clicking on the button in status area, - to clicking on an item in the system tray bubble. - - - - - tengs@chromium.org - gzadina@google.com - - An enum value how system tray bubble is expanded or collapsed. It can be - toggled by the button and touch gesture. - - - - - jorgelo@chromium.org - tnagel@chromium.org - - The number of files with URL extended attributes found in the users' home - directories. This is emitted once per boot. See crbug.com/919486 and - crbug.com/939386 for more details. - - - - - allenwebb@chromium.org - jorgelo@chromium.org - mnissler@chromium.org - Timing and number of USB devices attached. - - - - rsorokin@chromium.org - tellier@google.com - cros-oac@google.com - - The time spent before the web UI vesion of the multiprofile account picker - is ready. - - - - - tellier@google.com - rsorokin@chromium.org - cros-oac@google.com - - The time spent before the views-based version of the multiprofile account - picker is ready. - - - - - rsesek@chromium.org - - The amount of time it took to load the native libraries in the browser - process. - - - - - - Removed as of 06/2019. - - digit@chromium.org - pasko@chromium.org - lizeb@chromium.org - - Whether relro sharing was attempted for the browser process, and if - attempted, whether it succeeded. - - - - - - Removed 10/2014 in Issue 419010, and replaced by - ChromiumAndroidLinker.BrowserStates. - - simonb@chromium.org - Is low memory device. - - - - - Removed as of 06/2019. - - petrcermak@chromium.org - - Whether the device supports loading a library directly from the APK file. - The functionality is checked and reported during every Chromium browser - process start up. - - - - - - Removed 10/2014 in Issue 419010, and replaced by - ChromiumAndroidLinker.RendererStates. - - simonb@chromium.org - Load at fixed address failed. - - - - - Removed 2020-02 as part of crbug.com/1021156. - - lizeb@chromium.org - pasko@chromium.org - - Status of each attempt to load the native library with a custom linker. - Recorded after each attempt to load. Not recorded when all attempts fail in - a process. - - - - - - Removed 2019-07 in crbug.com/981599. - - agrieve@chromium.org - yfriedman@chromium.org - - The total number of times Chrome uses relinker fallback to extract and load - native libraries. - - - - - rsesek@chromium.org - - The amount of time it took to load the native libraries in the renderer - process. - - - - - - Removed as of 06/2019. - - simonb@chromium.org - - Whether relro sharing was attempted for a renderer process, and if - attempted, whether it succeeded. - - - - - jamiewalch@chromium.org - - Recorded every time a Chromoting connection enters a new state. - - - - - jamiewalch@chromium.org - - The duration of sessions that were closed, normally by a user-initiated - action. - - - - - jamiewalch@chromium.org - The duration of sessions that failed to connect. - - - - jamiewalch@chromium.org - - The time taken to authenticate as part of a Chromoting connection request. - - - - - jamiewalch@chromium.org - - The time taken to connect to a remote-host, after a request has been - authenticated. - - - - - joedow@chromium.org - lambroslambrou@chromium.org - - Input event delivery latency from the browser to the plugin. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - jamiewalch@chromium.org - - The bandwidth of non-empty packets in Chromoting remote sessions, updated - every time a video packet is processed and logged every 1s. - - - - - jamiewalch@chromium.org - - The time to capture a video frame on the host, returned as part of a video - packet. - - - - - jamiewalch@chromium.org - - Amount of time wasted on IPC and threading overhead when capturing a video - frame. - - - - - joedow@chromium.org - lambroslambrou@chromium.org - - The time from when an input event is received to when the next frame is - captured. - - - - - jamiewalch@chromium.org - The time to decode a video packet on the client. - - - - joedow@chromium.org - lambroslambrou@chromium.org - - The time to encode a video packet on the host, returned as part of a video - packet. - - - - - jamiewalch@chromium.org - - Delay before a newly captured frame is passed to the encoder. - - - - - joedow@chromium.org - lambroslambrou@chromium.org - - The frame-rate of non-empty packets in Chromoting remote sessions, updated - every time a video packet is processed and logged every 1s. - - - - - jamiewalch@chromium.org - - Estimated network roundtrip latency calculated by subtracting total - processing time on host and client from the total roundtrip time. - - - - - jamiewalch@chromium.org - - The packets/sec, including empty packets, in Chromoting remote sessions, - updated every time a video packet is processed and logged every 1s. - - - - - jamiewalch@chromium.org - The time to paint a decoded video packet on the client. - - - - jamiewalch@chromium.org - - The time from an input being sent from the client to a response being - received by the client after it is processed by the host. - - - - - jamiewalch@chromium.org - - Delay before an encoded video packet is written to the send buffer. - - - - - - Removed 07/2020 because this unowned histogram is no longer being used and - has expired. - - Please list the metric's owners. Add more owner tags as needed. - - The length of time between a dangerous download appearing on the downloads - shelf, and the "Discard" button being clicked. - - - - - - Removed 07/2020 because this unowned histogram is no longer being used and - has expired. - - Please list the metric's owners. Add more owner tags as needed. - - The length of time between a dangerous download appearing on the downloads - shelf, and the "Dismiss" button being clicked. Deprecated since - M54. - - - - - - Removed 07/2020 because this unowned histogram is no longer being used and - has expired. - - Please list the metric's owners. Add more owner tags as needed. - - The length of time between the external protocol dialog being shown and the - "Launch Application" button being clicked. - - - - - - Removed 07/2020 because this unowned histogram is no longer being used and - has expired. - - Please list the metric's owners. Add more owner tags as needed. - - The length of time between a download appearing on the download shelf, and - the user opening it by clicking the item or pressing return. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Time between "Report and Discard" button being shown and it being - clicked. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The length of time between a dangerous download appearing on the download - shelf, and the "Keep" button being clicked. - - - - - - Removed M86 since what it's measuring no longer happens. - - yoavweiss@chromium.org - tbansal@chromium.org - mkwst@chromium.org - - Count of client hints that were received by the render process. Recorded - approximately at the time of the renderer startup. - - - - - yoavweiss@chromium.org - tbansal@chromium.org - mkwst@chromium.org - - Duration for which the origin requested the client hints to be persisted. - Collected on the renderer side. - - - - - yoavweiss@chromium.org - tbansal@chromium.org - mkwst@chromium.org - - Count of events when the client hints needs to be persisted to the disk by - the browser. - - - - - yoavweiss@chromium.org - tbansal@chromium.org - mkwst@chromium.org - - Count of client hints that need to be persisted to the disk. Recorded by the - renderer. - - - - - - Launched briefly in M-59 dev, then refactoring made obsolete. - - mpearson@chromium.org - - Whether Android's Clipboard.java successfully constructed a hasher to hash - clipboard entries. Recorded on construction of the class, which happens only - on startup. - - - - - - Removed as of 4/2013, experiment confirmed correctness of our patch. - - Please list the metric's owners. Add more owner tags as needed. - - Counts how often the user writes or reads from the clipboard and whether the - write was from an incognito window or not. - - - - - huangdarwin@chromium.org - src/ui/base/clipboard/OWNERS - - Counts how often each Clipboard format is read by the platform clipboard. - These reads generally imply that an application requested this format after - checking that the format is available, but there are some cases where Chrome - reads a format to check for existence (outside the - ui::Clipboard::ReadAvailableTypes() function). Please prefer interpreting - these numbers as relative use changes, as opposed to absolute user usage. - - - - - huangdarwin@chromium.org - src/ui/base/clipboard/OWNERS - - Counts how often the Windows clipboard fails to register a format. Recorded - when RegisterClipbaordFormat fails (returns 0). Failure rates will inform - whether we implement error handling. https://crbug.com/1000919 - - - - - huangdarwin@chromium.org - src/ui/base/clipboard/OWNERS - - Counts how often each Clipboard format is written by the platform clipboard. - These writes all imply that an application had this format available, and - therefore wrote this format. - - - - - dcheng@chromium.org - pkotwicz@chromium.org - - The length of time that it takes to transfer ownership of Chrome's CLIPBOARD - selection to the clipboard manager when Chrome exits. - - - - - thestig@chromium.org - Event counts in CloudPrintAuth. - - - - thestig@chromium.org - The number of printers available for registration. - - - - thestig@chromium.org - - The number of printers available for registration in Windows Service. - - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - The amount of time between capabilities updates. - - - - thestig@chromium.org - Event counts in PrinterJobHandler. - - - - thestig@chromium.org - The number of jobs successfully completed per hour. - - - - thestig@chromium.org - The number of jobs started per hour. - - - - thestig@chromium.org - Then number of job completion statuses. - - - - thestig@chromium.org - Event counts in PrintSystem. - - - - thestig@chromium.org - The amount of time needed to prepare job for spooling. - - - - thestig@chromium.org - The number of printers user has blacklisted. - - - - thestig@chromium.org - The number of printers user has whitelisted. - - - - thestig@chromium.org - The amount of time needed to finish print job. - - - - thestig@chromium.org - Event counts in ServiceProcessControl. - - - - - Removed 12/2015. http://crbug.com/466644 - - thestig@chromium.org - - Temporarily histogram with size of IPC sockets in default location. - - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - - The amount of time used to fail to collect printer capabilities. - - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - The amount of time used to collect printer capabilities. - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - - The amount of time the utility process runs before disconnect. - - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - The amount of time used to fail to generate metafile. - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - The amount of time used to generate metafile. - - - - thestig@chromium.org - Event counts in ServiceUtilityProcessHost. - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - - The amount of time used to fail to collect printer capabilities. - - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - The amount of time used to collect printer capabilities. - - - - thestig@chromium.org - The amount of time needed to spool print job. - - - - thestig@chromium.org - The number of printers to unregister. - - - - thestig@chromium.org - The amount of data downloaded on cloud print request. - - - - thestig@chromium.org - The amount of time needed for cloud print request. - - - - thestig@chromium.org - Request counts to cloud print service. - - - - thestig@chromium.org - The number of retries used to complete cloud print request. - - - - thestig@chromium.org - The amount of data uploaded with cloud print request. - - - - thestig@chromium.org - Number of tries before successful ping. 99 means giving up. - - - - - Removed 02/2017. http://crbug.com/643570 - - thestig@chromium.org - Xmpp timeout option value provided by server. - - - - sorin@chromium.org - - The number of times the component updater called UpdateClient::Install or - UpdateClient::Update. These correspond to the number of manual component - update checks performed as a result of a user action, and the number of - automated component update checks. - - - - - xiaochu@chromium.org - - Chrome OS only. Installation error code in CrosComponentManager. - - - - - xiaochu@chromium.org - Chrome OS only. Time it takes to mount a component image. - - - - sorin@chromium.org - The result of an install or an update check. - - - - sorin@chromium.org - The result of an install or an update check. - - - - sorin@chromium.org - - Time to complete an Install or an Update component update call. - - - - - - Removed in July 2019 - - weili@chromium.org - - Tracks the status of PDF document composition and generation conducted in - PDF compositor service. - - - - - - Removed in July 2019 - - weili@chromium.org - - Tracks the status of PDF page composition and generation conducted in PDF - compositor service. - - - - - - Removed 05/2019 because it no longer reports. To be superseded by a - measurement related to percentage of cache/discardable memory used by image - caching. - - vmpstr@chromium.org - - The maximum number of images that were cached in the browser over the - lifetime of the image decode cache. This is recorded at the image cache - destruction. It is further split up by Software and Gpu rasterization. - - - - - - Removed 06/2019 because the research it was used for is complete. - - ccameron@chromium.org - - The total number of quads in all render passes in a CompositorFrame. This is - logged as the CompositorFrame is submitted to its surface. - - - - - - Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when display list recording source is updated (in a - browser process). - - - - - - Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a display list, in microseconds. - Recorded when display list is updated (in a browser process). - - - - - - Removed 10/2018. This metric didn't end up being useful. - - kylechar@chromium.org - - How often the layer compositor successfully submitted content to the display - compositor, or what caused an abort. This is reported fairly late in the - pipeline, during the final stages of submitting content. - - - - - - Removed September, 2020. Memory.GPU.PeakMemoryUsage.PageLoad can be used to - track overall GPU memory usage. - - pdr@chromium.org - paint-dev@chromium.org - - The GPU memory allocated for tilings (in a browser process), summed over all - picture layers. Emitted once per drawing. Nothing is recorded if there are - no picture layers. - - Tilings are used for decomposition of the layer's entire contents at a - picture screenspace resolution to do threaded rasterization. - - - - - flackr@chromium.org - animations-dev@chromium.org - - Time spent finding the closest matching layer to a given point whenever we - do hit testing on LayerTreeImpl (in a browser process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - schenney@chromium.org - animations-dev@chromium.org - - Time spent updating layers, in microseconds. Recorded when layers are - updated (in a browser process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Time spent updating layer draw properties, in microseconds. Recorded when a - LayerTreeImpl's draw properties are updated (in a browser process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of layers in the active tree for each compositor frame. This is - logged once per frame, before the frame is drawn (in a browser process). - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of PictureLayers in the active tree for each compositor frame. - This is logged once per frame, before the frame is drawn (in a browser - process). - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of render surfaces in the render surface layer list. Recorded - each time the render surface layer list is constructed (in a browser - process). - - - - - - Has not produced data for over a year prior to removal in 03/2020. - - paint-dev@chromium.org - - Total estimated memory used by SkPictures in the layer tree, in kilobytes. - Recorded once per frame, before the frame is drawn (in a browser process). - - - - - - Obsolete since 2015. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when picture pile is updated (in a browser process). - - - - - - Obsolete since 2015. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a picture pile, in microseconds. - Recorded when picture pile is updated (in a browser process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 11/2016. Increased the max tracking range to accomendate GPU raster, - and will require new baskets. - - paint-dev@chromium.org - - Rasterized area, in pixels, divided by rasterization time, in milliseconds, - of a compositor rasterization task. Recorded after the task finishes (in a - browser process). - - - - - - Removed 04/2019. Was unused. - - paint-dev@chromium.org - - Rasterized area, in pixels, divided by rasterization time, in milliseconds, - of a compositor rasterization task. Recorded after the task finishes (in a - browser process). - - - - - - Removed 04/2019. Was unused. - - paint-dev@chromium.org - - Time spent completing a compositor rasterization task, in microseconds. - Recorded after the task finishes (in a browser process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 02/2016. We'd learned as much as we could from this metric and it - made no sense to keep it around. - - vollick@chromium.org - - Tracks the number of missing tiles that had some image content in the - browser process. - - - - - - Removed 02/2016. We'd learned as much as we could from this metric and it - made no sense to keep it around. - - vollick@chromium.org - - Tracks the number of missing tiles that did not have any image content in - the browser process. - - - - - kylechar@chromium.org - sadrul@chromium.org - - Recorded for each OnBeginFrame() message that could potentially be sent to a - CompositorFrameSinkClient. The value indicates if the message was sent to - the client and why it was/wasn't sent. - - - - - - Expired 2020-03-01. - - kylechar@chromium.org - - The result of submitting a CompositorFrame to a CompositorFrameSink. - ACCEPTED means the frame was accepted by the CompositorFrameSink. - COPY_OUTPUT_REQUESTS_NOT_ALLOWED means an unprivileged client attempted to - readback a texture. SURFACE_INVARIANTS_VIOLATION means size or device scale - factor changed but a new viz::LocalSurfaceId was not allocated. - - - - - wychen@chromium.org - - The turn around time taken for the async readback of pixels is measured - here. This should be marked as obsolete once some tests no longer rely on - this histogram. See crbug/1110961 for more details. - - - - - - Made obsolete 04/2016. Logging removed 08/2020. - - Please list the metric's owners. Add more owner tags as needed. - - The time taken for the sync readback of pixels is measured here. - - - - - weiliangc@chromium.org - - Time spent drawing of composited layers by GLRenderer, in microseconds. This - is logged once per frame, when a frame should be drawn. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vasilyt@chromium.org - backer@chromium.org - - The area of the display damage that was added to current frame damage after - all adjustments, including FrameBufferDamage from buffer queue and render - pass filters. - - This metric is reported once per frame only on platforms/devices that - support partial swap and does not include "empty swap" (no frame - damage) case. - - - - - vasilyt@chromium.org - backer@chromium.org - - The area of the display that was damaged since previous draw to this frame - buffer. - - This metric is reported once per frame only on platforms/devices that - support partial swap and does not include "empty swap" (no frame - damage) case. - - - - - vasilyt@chromium.org - backer@chromium.org - - The area of the display that was damaged in current frame. - - This metric is reported only on platforms/devices that support partial swap - and does not include "empty swap" (no frame damage) case. - - - - - vasilyt@chromium.org - backer@chromium.org - - The total area of the display that will be redrawn this frame. - - This metric is reported only on platforms/devices that support partial swap - and does not include "empty swap" (no frame damage) case. - - - - - weiliangc@chromium.org - - Time spent drawing of composited layers by SoftwareRenderer, in - microseconds. This is logged once per frame, when a frame should be drawn. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - penghuang@chromium.org - backer@chromium.org - - Time spent drawing of composited layers by SkiaRenderer with Vulkan backend, - in microseconds. This is logged once per frame, when a frame should be - drawn. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - yiyix@chromium.org - chromeos-gfx@chromium.org - - Time spent to remove invisible quads from the quad_list in CompositorFrame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 02/2018, replaced by similar metric - Compositing.Display.Draw.Occlusion.Drawing.Area.Saved2. - - yiyix@chromium.org - - It records the total drawing area skipped to show on screen as a result of - applying draw occlusion. This is logged once per frame, when the frame is - drawn. - - - - - yiyix@chromium.org - - It records the total drawing area skipped to show on screen as a result of - applying draw occlusion. This is logged once per frame, when the frame is - drawn. - - - - - yiyix@chromium.org - - It records the percentage of total area drawing skipped by draw occlusion of - the total area of damage rects in a compositor frame. This is logged once - per frame, when the frame is drawn. - - - - - - Removed 06/2019 because the research it was used for is complete. - - ccameron@chromium.org - - This is logged once per frame, when the frame is drawn. The total number of - quads in all render passes in the CompositorFrame that is produced by - surface aggregation. - - - - - - Removed 03/2018. We'd learned enough from this metric and it made no sense - to keep it around. - - yiyix@chromium.org - - This is logged once per frame, when the frame is drawn. Captures area of all - draw quads that need to go through no scale and no translation transforms. - - - - - backer@chromium.org - rjkroege@chromium.org - - This is logged once per frame, if the output surface provides timing - information. It measures the time from the display compositor starting a - draw on the Viz Compositor thread to issuing all related draw calls to the - driver on the Gpu Main thread. Only reported for platforms supporting high - resolution clocks. - - - - - samans@chromium.org - rjkroege@chromium.org - - Indicates whether DrmOverlayManager was able to find the overlay - configuration in its cache. Recorded when DrmOverlayManager is asked to - verify an overlay configuration. - - - - - samans@chromium.org - rjkroege@chromium.org - - The amount of memory allocated for the purpose of performing a pageflip - test. Recorded every time DRM thread is asked to validate an overlay - configuration. - - - - - backer@chromium.org - rjkroege@chromium.org - - This is logged once per frame. It is the number of renderer passes after - flattening all possible render passes. If the value is more than one, then - an intermediate rendering target must be used during the rendering of the - frame for each render pass greater than one. - - - - - samans@chromium.org - rjkroege@chromium.org - - Indicates whether the OverlayCandidate passed to - OverlayCandidateValidatorOzone is backed by a SharedImage (as opposed to a - legacy mailbox). Recorded for every candidate in every overlay configuration - passed to OverlayProcessorOzone. - - - - - samans@chromium.org - rjkroege@chromium.org - - Indicates whether the SharedImage corresponding to the OverlayCandidate was - found. Reported for every OverlayCandidate that is backed by a SharedImage. - - - - - vasilyt@chromium.org - backer@chromium.org - - This is logged once per frame, if the output surface provides timing - information. It measures delta between the time when display compositor - scheduled first draw task for the current frame on Viz Compositor thread and - the time when Gpu Thread started processing it. Only reported for platforms - supporting high resolution clocks. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when display list recording source is updated. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a display list, in microseconds. - Recorded when display list is updated. - - - - - - Removed 05/2017 in Issue 710306. Histogram was used temporarily for tracking - a potential performance regression. - - paint-dev@chromium.org - - Time spent finding the closest matching layer to a given point, in - microseconds. Recorded each time we do hit testing on LayerTreeImpl. - - - - - - Expired M81 - - kylechar@chromium.org - - The amount of time it took for a main frame with unresolved dependencies to - activate. Note that some activations may be triggered due to a deadline - hitting. - - - - - - Removed 04/2016, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - dneto@chromium.org - - The number of layers in the active tree for each compositor frame. This is - logged once per frame, before the frame is drawn. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Total estimated memory used by SkPictures in the layer tree, in kilobytes. - Recorded once per frame, before the frame is drawn. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when picture pile is updated. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a picture pile, in microseconds. - Recorded when picture pile is updated. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Rasterized area, in pixels, divided by rasterization time, in milliseconds, - of a compositor rasterization task. Recorded after the task finishes. - - - - - - Removed 09/2015, replaced by similar metrics under Compositing.Renderer and - Compositing.Browser, depending on which process it occurs in. - - paint-dev@chromium.org - - Time spent completing a compositor rasterization task, in microseconds. - Recorded after the task finishes. - - - - - - Removed 05/2019 because it no longer reports. To be superseded by a - measurement related to percentage of cache/discardable memory used by image - caching. - - vmpstr@chromium.org - - The maximum number of images that were cached in the renderer over the - lifetime of the image decode cache. This is recorded at the image cache - destruction. It is further split up by Software and Gpu rasterization. - - - - - ccameron@chromium.org - - The outcome of attempting to replace all renderer tiles with CALayers. - Either success, or the first reason why a DrawQuad couldn't be replaced by a - CALayer. - - - - - - Removed 01/2020. - - khushalsagar@chromium.org - - The outcome for whether an image could be sucessfully deferred for - asynchronous decode in the renderer compositor. If not, the reason for using - a synchronous decode. An image which is decoded asynchronously will be - checkerboarded on the rasterized tiles until the decode is finished, as - opposed to synchronous decodes where the tile rasterization is blocked on - the image decode completing. - - - - - - Removed 06/2019 because the research it was used for is complete. - - ccameron@chromium.org - - The total number of quads in all render passes in a CompositorFrame. This is - logged as the CompositorFrame is submitted to its surface. - - - - - - Removed September 2020 because the research it was used for is complete. - - pdr@chromium.org - dlibby@microsoft.com - paint-dev@chromium.org - - Records instances of directly composited images that did not need to - recalculate raster scale in response to scale changes. The boolean value - indicates whether will-change:transform is set or a scale transforms is - animating. This metric will be used to determine the impact on raster CPU - usage if we were to scope the directly composited images feature. - - - - - - Removed September 2020 because the research it was used for is complete. - - pdr@chromium.org - dlibby@microsoft.com - paint-dev@chromium.org - - Records whether or not a PictureLayerImpl that has a single drawImage paint - operation is able to apply directly composited image optimization. See - PictureLayerImpl::ShouldDirectlyCompositeImage for more details. - - - - - - Removed September 2020 because the research it was used for is complete. - - pdr@chromium.org - dlibby@microsoft.com - paint-dev@chromium.org - - Records the number of tile pixels added when directly composited image is - applied to a layer. If the raster scale is greater than it otherwise would - be, the difference in pixels used for tiling the layer is logged in this - histogram. - - - - - - Removed September 2020 because the research it was used for is complete. - - pdr@chromium.org - dlibby@microsoft.com - paint-dev@chromium.org - - Records whether or not the chosen raster scale for a directly composited - image matches the ideal raster scale. In cases where the scale does not - match (i.e. false values for this histogram), either TileAreaAdded or - TileAreaSaved will be logged to provide an indication on the effects on - memory usage. - - - - - - Removed September 2020 because the research it was used for is complete. - - pdr@chromium.org - dlibby@microsoft.com - paint-dev@chromium.org - - Records the number of tile pixels saved when directly composited image is - applied to a layer. If the raster scale is lower than it otherwise would be, - the difference in pixels used for tiling the layer is logged in this - histogram. - - - - - - Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when display list recording source is updated (in a - renderer process). - - - - - - Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a display list, in microseconds. - Recorded when display list is updated (in a renderer process). - - - - - - Removed 10/2018. This metric didn't end up being useful. - - kylechar@chromium.org - - How often the layer compositor successfully submitted content to the display - compositor, or what caused an abort. This is reported fairly late in the - pipeline, during the final stages of submitting content. - - - - - pdr@chromium.org - paint-dev@chromium.org - - The GPU memory allocated for tilings (in a renderer process), summed over - all picture layers. Emitted once per drawing. Nothing is recorded if there - are no picture layers. - - Tilings are used for decomposition of the layer's entire contents at a - picture screenspace resolution to do threaded rasterization. - - - - - flackr@chromium.org - animations-dev@chromium.org - - Time spent finding the closest matching layer to a given point whenever we - do hit testing on LayerTreeImpl (in a renderer process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - chrishtr@chromium.org - paint-dev@chromium.org - - Records whether layer draw properties updates were skipped due to the layer - being back-facing and not being double-sided, but were otherwise going to be - updated. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Time spent updating layers, in microseconds. Recorded when layers are - updated (in a renderer process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Time spent updating layer draw properties, in microseconds. Recorded when a - LayerTreeImpl's draw properties are updated (in a renderer process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - chrishtr@chromium.org - paint-dev@chromium.org - - Records whether a layer update was skipped due to the layer being - back-facing and not being double-sided, but was otherwise going to be - updated. - - - - - wangxianzhu@chromium.org - paint-dev@chromium.org - - Records the approximate kilo-pixels covered by text drawing operations by - LCD-text disallowed reasons. Hence the histogram value for each reason is - the approximate number of non-LCD kilo-pixels resulting from that reason. - Recorded when the renderer is idle, at minimum interval of the longer of 1 - minute and 500 begin frames for each local frame tree. - - - - - wangxianzhu@chromium.org - paint-dev@chromium.org - - Records the number of layers containing text by LCD-text disallowed reasons. - Recorded along with Compositing.Renderer.LCDTextDisallowedReasonKPixels. - - - - - - Replaced by Compositing.Renderer.LCDTextDisallowedReason* on 2020-05-08. - - wangxianzhu@chromium.org - paint-dev@chromium.org - - Records the percentage of approximate number of pixels covered by text - drawing operations that are LCD-text eligible, in that of all text drawing - operations. This is recorded when the renderer is idle, at minimum interval - of the longer of 1 minute and 500 begin frames for each local frame tree. - Note that LCD-text eligible text may rasterize in non-LCD-text mode when - e.g. LCD-text is not supported by the font or LCD-text doesn't appreciably - improve quality. - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of layers in the active tree for each compositor frame. This is - logged once per frame, before the frame is drawn (in a renderer process). - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of PictureLayers in the active tree for each compositor frame. - This is logged once per frame, before the frame is drawn (in a renderer - process). - - - - - schenney@chromium.org - paint-dev@chromium.org - - The number of render surfaces in the render surface layer list. Recorded - each time the render surface layer list is constructed (in a renderer - process). - - - - - - Removed in 03/2020 because changes in the data are difficult to reason about - as the number of layers also tends to change at the same time. - - - - paint-dev@chromium.org - - The number of PictureLayers in the active tree for each compositor frame - that have both text drawing operations and do not permit lcd text. This is - logged once per frame, before the frame is drawn (in a renderer process). - Suffixed with the count of number of picture layers with text. - - - - - - Removal in 03/2020 because it is not very useful. - - paint-dev@chromium.org - - Total estimated memory used by SkPictures in the layer tree, in kilobytes. - Recorded once per frame, before the frame is drawn (in a renderer process). - - - - - - Obsolete since 2015. - - paint-dev@chromium.org - - Area of invalidated content, in pixels, divided by update (i.e. record), in - milliseconds. Recorded when picture pile is updated (in a renderer process). - - - - - - Obsolete since 2015. - - paint-dev@chromium.org - - Time spent updating (i.e. recording) a picture pile, in microseconds. - Recorded when picture pile is updated (in a renderer process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 11/2016. Increased the max tracking range to accomendate GPU raster, - and will require new baskets. - - paint-dev@chromium.org - - Rasterized area, in pixels, divided by rasterization time, in milliseconds, - of a compositor rasterization task. Recorded after the task finishes (in a - renderer process). - - - - - - Removed 04/2019. Was unused. - - paint-dev@chromium.org - - Rasterized area, in pixels, divided by rasterization time, in milliseconds, - of a compositor rasterization task. Recorded after the task finishes (in a - renderer process). - - - - - - Removed 04/2019. Was unused. - - paint-dev@chromium.org - - Time spent completing a compositor rasterization task, in microseconds. - Recorded after the task finishes (in a renderer process). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 02/2016. We'd learned as much as we could from this metric and it - made no sense to keep it around. - - vollick@chromium.org - - Tracks the number of missing tiles that had some image content in the - renderer process. - - - - - - Removed 02/2016. We'd learned as much as we could from this metric and it - made no sense to keep it around. - - vollick@chromium.org - - Tracks the number of missing tiles that did not have any image content in - the renderer process. - - - - - weiliangc@chromium.org - - Checkerboarded area, in number of pixels, that has recording but does not - have time to finish rastering yet. A sample is recorded everytime a frame is - drawn while a scroll is in progress. Tracking bug 535732. - - - - - weiliangc@chromium.org - - Checkerboarded area, in number of pixels, that has no recording to raster - from. A sample is recorded everytime a frame is drawn while a scroll is in - progress. Tracking bug 535732. - - - - - - Removed as being no longer useful to track. - - enne@chromium.org - chrishtr@chromium.org - - Percent of layers drawn that frame that are mask layers. A sample is - recorded on the first draw per commit. - - - - - weiliangc@chromium.org - - Keeps track of number of incomplete tiles in a drawn compositor frame while - scrolling. This is a rough measurement of ugliness during user interaction. - Incomplete tiles are non ideal scaled. A sample is recorded everytime a - frame is drawn while a scroll is in progress. Tracking bug 381695. - - - - - weiliangc@chromium.org - - Keeps track of number of missing tiles in a drawn compositor frame while - scrolling. This is a rough measurement of ugliness during user interaction. - Incomplete tiles are checkerboard or solid color. A sample is recorded - everytime a frame is drawn while a scroll is in progress. Tracking bug - 381695. - - - - - - Removed as being no longer useful to track. - - enne@chromium.org - chrishtr@chromium.org - - Total visible area of layers drawn that frame that are mask layers and also - are simple rounded corner masks. A sample is recorded on the first draw per - commit. - - - - - - Removed as being no longer useful to track. - - enne@chromium.org - chrishtr@chromium.org - - Percent of visible area of layers drawn that frame that are mask layers and - also are simple rounded corner masks. A sample is recorded on the first draw - per commit. - - - - - - Removed as being no longer useful to track. - - enne@chromium.org - chrishtr@chromium.org - - Percent of layers drawn that frame that are mask layers and also are simple - rounded corner masks. A sample is recorded on the first draw per commit. - - - - - sunnyps@chromium.org - graphics-dev@chromium.org - - Size of the in-use portion of the ResourcePool for CC layer tree. Recorded - each time resources are reclaimed after tile work completes. - - - - - weiliangc@chromium.org - - Time spent aggregating compositor frames from different surfaces in - microseconds. This is logged once per frame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vikassoni@chromium.org - khushalsagar@chromium.org - - Whether an aggregated frame contains video or not. This metric will be used - to analyze the percentage of displayed frame with video. This metric will be - extended in future to specify whether the video is inline or fullscreen. - - - - - - Removed 10/2018. This metric didn't end up being useful. - - akaba@chromium.org - kylechar@chromium.org - - The distance between the latest inflight surface and the primary surface. - This is logged for each call to HandleSurfaceQuad(). - - - - - - Removed 07/2018 in issue 865597 in order to avoid spurious error messages on - Viz process crash. - - kylechar@chromium.org - - The number of SurfaceDrawQuads where the surface doesn't exist. This is - logged for each call to Aggregate(). - - - - - - Removed 07/2018 in issue 865597 in order to avoid spurious error messages on - Viz process crash. - - kylechar@chromium.org - - The number of SurfaceDrawQuads where the surface exists but doesn't have an - active CompositorFrame. This is logged for each call to Aggregate(). - - - - - - Removed 10/2018. This metric didn't end up being useful. - - kylechar@chromium.org - - The number of SurfaceDrawQuads where the primary SurfaceId does not have a - corresponding active CompositorFrame and so the fallback surface is used - instead. This is logged for each call to Aggregate(). - - - - - - Removed 10/2018. This metric didn't end up being useful. - - kylechar@chromium.org - - The number of SurfaceDrawQuads where the surface exists and has an active - CompositorFrame. This is logged for each call to Aggregate(). - - - - - - Removed as of 10/2018. This metric didn't end up being useful. - - kylechar@chromium.org - - Tracks whether an activation of a surface was due to due to a deadline or - the resolution of dependencies. - - - - - jonross@chromium.org - kylechar@chromium.org - - The amount of time it took for a Surface with unresolved dependencies to - activate. Note that some activations may be triggered due to a deadline - hitting. That is tracked in the DeadlineHit histogram. - - - - - - Removed as of 2018/09/10 in favor of - Compositing.CompositorFrameSinkSupport.SubmitResult. - - kylechar@chromium.org - - The number of times a renderer in this browser session has violated a - surface synchronization invariant. This manifests as a skipped frame. - Ideally this metric should always report 0, but realistically there are - races in the system and this tracks the frequency that we hit these races. - - - - - jonross@chromium.org - kylechar@chromium.org - - Tracks the number of alive surfaces after each garbage collection operation. - - - - - - Removed 2018/01/24. - - kylechar@chromium.org - - The number of temporary references that have existed for at least 10 seconds - and are most likely orphaned. This is logged every 10 seconds. - - - - - - Expired M81. - - kylechar@chromium.org - Tracks the reason for removing a temporary reference. - - - - - Expired M81. - - kylechar@chromium.org - - Tracks the number of temporary references after each garbage collection - operation. - - - - - - Obsolete after 03/2019. For temporary debugging of CompositorImpl hangs. - - ericrk@chromium.org - - Tracks the amount of time it takes to synchronously tear down the display - when the CompositorImpl becomes invisible or is destroyed. Recorded after - display teardown completes in CompositorImpl:: - TearDownDisplayAndUnregisterRootFrameSink. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages in the pipeline as a single frame goes - through the various stages in the compositor. This is reported for frames - that went through all the compositor stages in chromium, and was presented - to the user. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages in the pipeline as a single frame goes - through the various stages in the compositor in the cases that there is no - damage from main thread. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - behdadb@chromium.org - sadrul@chromium.org - - For the compositor pipeline, measures how far the presentation time of a - compositor frame is from the frame deadline (i.e. vsync time). - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages in the pipeline as a single frame goes - through the various stages in the compositor. This is reported for frames - that the user did not see: this includes frames that are dropped in various - stages inside chromium, or even frames that went through all stages in - chromium, but ultimately was not presented to the user. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages in the pipeline as a single frame goes - through the various stages in the compositor. This is reported for frames - that went through all the compositor stages in chromium, and was presented - to the user, but were delayed and missed their deadline. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages in the pipeline as a single frame goes - through the various stages in the compositor. This is reported for frames - that the user did not see: this includes frames that are dropped in various - stages inside chromium, or even frames that went through all stages in - chromium, but ultimately was not presented to the user. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed on 9/2019. Did not provide enough information about latency. - - sadrul@chromium.org - graphics-dev@chromium.org - - The latency increase of an abnormally long activation stage on the - multithread thread compositor pipeline when the frame is missed. - - These latency increases are determined by comparing the stage duration to - the times from past non-missed frames. These times are also reported to - "CompositorLatency.MissedFrame.<StageName>" - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Whether frame is dropped or presented meeting or missing the deadline or is - a compositor only frame. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Modeset attempt result of an external display. Every time an external - display is connected/disconnected, or when the display mode of the external - screen is changed by the user, Chrome attempts to modeset the display. This - metric tracks the result of those attempts. Resolution and RefreshRate - metrics will be recorded for each attempt. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Modeset attempt result of an internal display. This is recorded after Chrome - attempted all the available modes and finally modeset the display. All the - previously attempted modes and refreshes, including the successful one will - be recorded. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Refresh rate of the mode for the display we're about to modeset. This is - recorded every time an external display is connected/disconnected, or when - the display mode of the external screen is about to change. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - DisplayResolution of the mode for the external display we're about to - modeset. 0 means the display was powered off. This is recorded every time an - external display is connected/disconnected, or when the display mode of the - external screen is about to change. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Modeset attempt result of an internal display. Chrome might try additional - modes after a failed attempt. Every time an external display is - connected/disconnected, or when the display mode of the external screen is - changed by the user, Chrome attempts to modeset the display. This metric - tracks the result of those attempts. Resolution and RefreshRate metrics will - be recorded for each attempt. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Modeset attempt result of an internal display. This is recorded after Chrome - attempted all the available modes and finally modeset the display. All the - previously attempted modes and refreshes, including the successful one will - be recorded. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - Refresh rate of the mode for the display we're about to modeset. This is - recorded every time the internal display is powered on/off, or when an - external monitor is plugged in. - - - - - dcastagna@chromium.org - marcheu@chromium.org - chromeos-gfx@chromium.org - - DisplayResolution of the mode for the internal display we're about to - modeset. 0 means the display was powered off. This is recorded every time - the internal display is powered on/off, or when an external monitor is - plugged in. - - - - - chrisha@chromium.org - - The number of confirmed bad modules found during module enumeration. - - - - - chrisha@chromium.org - - The length of time it takes to enumerate the loaded modules in the browser - process. - - - - - chrisha@chromium.org - - The length of time it takes to enumerate the shell extensions. - - - - - chrisha@chromium.org - - The length of time it takes to enumerate the Winsock LSP modules. - - - - - chrisha@chromium.org - - The cumulative length of time it takes to inspect all modules on disk, - extracting their certificates and version information. This work is actually - spread out over a much longer period of time so as not to impact the user. - - - - - chrisha@chromium.org - - The cumulative length of time it takes to enumerate and inspect all modules. - This work is actually spread out over a much longer period of time so as not - to impact the user. - - - - - chrisha@chromium.org - - The number of suspected bad modules found during module enumeration. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Whether or not the network connectivity info, i.e. validated, is provided by - the system. We will use it if it is available from the system. Otherwise, we - will do our own http probes to find it out. This UMA will not be recorded if - a flag in about:flags is set to bypass this logic to always favor the check - by http probes. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - The HTTP response code returned from a HTTP probe for the purpose of - checking network connectivity. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - The result from a HTTP probe for the purpose of checking network - connectivity. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - The total duration measuring all the HTTP probes and backoff time taken when - the network connectivity is successfully validated. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Records type of url, default or fallback URL, resulting in successful - connectivity validation. - - - - - ebeach@google.com - - Connectivity Diagnostics App: WiFi signal strength recorded during - NIC_SIGNAL_STRENGTH test. - -
- The "Strength" property of a WiFi signal is a partially-reversible - function that linearly maps the RSSI range -120dBm to -20dBm to Strength - values from 0 to 100. -
- - - - - Removed 04/2020. No longer used. - - ebeach@google.com - HTTP latency seen by the Connectivity Diagnostics. -
- HTTP latency is computed using the chrome.socket API to make an HTTP GET - request to the /generate_204 page of three randomly generated Google - hostnames (*-ccd-testing-v4.metric.gstatic.com). The time taken from issuing - the HTTP request to receiving a response is clocked in JavaScript and the - arithmetic mean of the three times is used as the HTTP latency. -
- - - - ebeach@google.com - Resolution latency seen by the Connectivity Diagnostics. -
- Resolver latency is computed by using the chrome.dns API to query three - randomly generated Google hostnames (*-ccd-testing-v4.metric.gstatic.com). - The random hostnames guarantees that there will be no caching of DNS - hostnames. The time taken from issuing the DNS request to receiving a - response is clocked in JavaScript and the arithmetic mean of the three times - is used as the resolver latency. -
- - - - - Removed 04/2020. No longer used. - - ebeach@google.com - - Connectivity Diagnostics App: Outcome of the connectivity tests. - - - - - - Removed 04/2020. No longer used. - - ebeach@google.com - - Connectivity Diagnostics App: Amount of time taken to run each of the - connectivity tests. - - - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - - The time between a change in content and when the new capture is sent to the - browser process. - -
- A specific content change is hard to track. This is roughly calculated as - the interval from the first content change after a prior capturing content - to the first content being sent after the next capture of content. -
- - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - - The time taken to capture the on-screen content. - - Note that this metrics is only recorded on clients on which a - high-resolution clock is available. - - - - - - Expired - - michaelbai@chromium.org - The estimated time taken to capture one on-screen content. - - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - - The time taken to get the bounding box of the batch of captured content. - - Note that this metrics is only recorded on clients on which a - high-resolution clock is available. - - - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - - The time taken to send the content to the browser process in batch. - - Note that this metrics is only recorded on clients on which a - high-resolution clock is available. - - - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - The total number of content captures sent for a document. - - - - michaelbai@chromium.org - src/third_party/blink/renderer/core/content_capture/OWNERS - - The time taken for the task to start after it's scheduled. - - Note: The time of task that was scheduled for the retry wasn't measured - because it is always 500ms. - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - Records the category of the content when registered. - - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - - Records the status of dispatching the `contentdelete` event in every phase - of dispatch. - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - Records the category of the entry clicked on by a user. - - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - Records the result of the database operation. - - - - rayankans@chromium.org - platform-capabilities@chromium.org - - Records how many entries were found when loaded by the browser. - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - - Records the category of an attempted registration that was blocked. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default autoplay setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default cookies setting at profile open. - - - - - Removed 07/2014 since it is not referenced anywhere in the code. - - toyoshim@chromium.org - The default handler setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - The default permission setting for idle detection at profile open. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default image setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default JavaScript setting at profile open. - - - - - Support for keygen was removed. - - svaldez@chromium.org - - The default setting for using key generation in forms at profile open. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default location setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default camera setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default microphone setting at profile open. - - - - - This setting was deprecated in r322364 and replaced with separate settings - for camera and microphone. See - ContentSettings.DefaultMediaStreamCameraSetting and - ContentSettings.DefaultMediaStreamMicSetting. - - toyoshim@chromium.org - msramek@chromium.org - The default MediaStream setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - The default MIDI permission setting on sysex (system exclusive) messages at - profile open. - - - - - - Removed on 2020-07-07. This histogram is no longer recorded. - - toyoshim@chromium.org - The default mouse cursor setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default notification setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default plugins setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default popups setting at profile open. - - - - - Removed on 2020-07-07. This histogram is no longer recorded. - - miguelg@chromium.org - - The default permission setting for push messages at profile open. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default sound setting at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default subresource filter setting at profile open - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - The default permission setting for WebUSB at profile open. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - The default permission setting for Web Bluetooth at profile open. - - - - - engedy@chromium.org - - Records the number of times Flash permission is granted for a host. - - - - - - - lshang@chromium.org - dullweber@chromium.org - engedy@chromium.org - - The number of user defined content setting exceptions at browser start. - Suffixed with the name of content setting types. - - - - - alexmos@chromium.org - engedy@chromium.org - - Records the schemes of content setting exceptions at browser start. Each - exception provides one sample. - - - - - alexmos@chromium.org - engedy@chromium.org - - Records how often a content settings exception for the file: scheme has a - non-empty path. Recorded once per exception at browser start. - - - - - alexmos@chromium.org - engedy@chromium.org - - Count of how often a specific content type has a content settings exception - defined for a file: scheme with no path (i.e., wildcard path). Recorded once - per exception at browser start. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - alexmos@chromium.org - engedy@chromium.org - - Count of how often a specific content type has a content settings exception - defined for a file: scheme with a valid, non-empty path. Recorded once per - exception at browser start. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - raymes@chromium.org - - Count of how often a specific content setting is set for an embedded URL by - an extension. Only counts settings when the secondary pattern is different - to the primary pattern. Exactly one of this or - ContentSettings.ExtensionNonEmbeddedSettingSet will be emitted per call to - contentSettings.set(), if the arguments to the call are valid. - - - - - raymes@chromium.org - - Count of how often a specific content setting is set when only a single - pattern is specified. Exactly one of this or - ContentSettings.ExtensionEmbeddedSettingSet will be emitted per call to - contentSettings.set(), if the arguments to the call are valid. - - - - - calamity@chromium.org - src/chrome/browser/ui/page_action/OWNERS - - Counts which content setting buttons are pressed by the user. - - - - - - Removed 2015-10-05 in Issue 433475. Histogram was used temorarily for - diagnosing crash causes. - - scheib@chromium.org - - Numer of results of parsing WebsiteSettingsHandler::last_setting_ success or - failure in WebsiteSettingsHandler methods. - - - - - - Removed 2020-01-06. Histogram had already expired and metrics are no longer - required after the mixed content shield removal. - - estark@chromium.org - - Tracks whether the mixed content shield was shown, and how the user - interacted with it. - - - - - - Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.Allow - - battre@chromium.org - - The number of user defined cookies setting exceptions for allowing cookies - at browser start. - - - - - - Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.Block - - battre@chromium.org - - The number of user defined cookies setting exceptions for blocking cookies - at browser start. - - - - - battre@chromium.org - - The number of user defined hostname patterns for content settings at browser - start. - - - - - - Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.SessionOnly - - battre@chromium.org - - The number of user defined cookies setting exceptions for 'clearing cookies - on browser exit' at browser start. - - - - - - Removed 11/2015 in favor of Permissions.Action.* - - miguelg@chromium.org - - Tracks whether a permission was granted, rejected, etc. The suffix of the - histogram indicates which particular permission. - - - - - - Removed 11/2015 in favor of Permissions.Action.InsecureOrigin.* - - miguelg@chromium.org - - Tracks whether a permission was granted, rejected, etc on an insecure - origin. The suffix of the histogram indicates which particular permission. - - - - - - Removed 11/2015 in favor of Permissions.Action.SecureOrigin.* - - miguelg@chromium.org - - Tracks whether a permission was granted, rejected, etc on a secure origin. - The suffix of the histogram indicates which particular permission. - - - - - dominickn@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Number of times a given permission was requested by a website and the user - has the permission set to prompt (i.e. not blocked or allowed). - - Note this is probably not the metric you want - it does not correspond to - the total number of times websites request a permission. Also, because - specific permissions have code that can automatically block or grant - permissions based on things like incognito, installed extensions etc., this - does also not correspond to the number of times users are prompted to allow - permissions. - - For a better metric to track how often users are prompted, either use - ContentSettings.PermissionsActions*, or Permissions.Prompt.*. - - See https://crbug.com/638076 for more details. - - - - - dominickn@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Number of times a given permission was requested by an insecure origin and - the user has the permission set to prompt (i.e. not blocked or allowed). - - Note this is probably not the metric you want - it does not correspond to - the total number of times websites request a permission. Also, because - specific permissions have code that can automatically block or grant - permissions based on things like incognito, installed extensions etc., this - does also not correspond to the number of times users are prompted to allow - permissions. - - For a better metric to track how often users are prompted, use - ContentSettings.PermissionsActions*. - - See https://crbug.com/638076 for more details. - - - - - dominickn@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Number of times a given permission was requested by a secure origin and the - user has the permission set to prompt (i.e. not blocked or allowed). - - Note this is probably not the metric you want - it does not correspond to - the total number of times websites request a permission. Also, because - specific permissions have code that can automatically block or grant - permissions based on things like incognito, installed extensions etc., this - does also not correspond to the number of times users are prompted to allow - permissions. - - For a better metric to track how often users are prompted, use - ContentSettings.PermissionsActions*. - - See https://crbug.com/638076 for more details. - - - - - tommycli@chromium.org - - Tracks whether the plugin content blocked puzzle piece was shown in the - Omnibox, and how the user interacted with it. - - - - - charleszhao@chromium.org - - Tracks whether the popup content blocked puzzle piece was shown in the - Omnibox, and how the user interacted with it. - - - - - csharrison@chromium.org - - Counts of various events related to the popup blocker. Including blocked - popups and overridden (clicked through) popups. This is similar to the - ContentSettings.Popups but is at the per-popup layer rather than at the UI - layer. - - - - - csharrison@chromium.org - - The blocked popup list contains a list of links that Chrome has blocked via - the popup blocker. If a user clicks on the link, the popup is opened. This - metric records the position of the popup in the list that a user clicks - through. Currently it should only be recorded on desktop platforms, because - the mobile UI for popup blocking does not currently allow for specific - exceptions. - - - - - csharrison@chromium.org - - Measures the total duration a popup WebContents is visible / foregrounded, - until it is closed. - - - - - csharrison@chromium.org - - Measures the total duration a popup WebContents is visible / foregrounded, - until it is closed via some user gesture (like Ctrl-W). - - - - - - Removed in favor of ContentSettings.Popups.FirstDocumentEngagementTime2. - - csharrison@chromium.org - - Measures the total duration a popup WebContents is visible / foregrounded - for the duration of its first document load. This time is measured from the - first navigation commit to the time either the WebContents is destroyed or - when a new navigation commits. - - - - - csharrison@chromium.org - - Measures the total duration a popup WebContents is visible / foregrounded - for the duration of its first document load. This time is measured from the - first navigation commit to the time either the WebContents is destroyed or - when a new navigation commits. - - - - - csharrison@chromium.org - - The total number of popups blocked by the strong blocker for a given page - load. Logged when the page is navigated away from, or the tab is closed. - Only logged for pages which are triggered for strong popup blocking, aka - abusive experience enforcement. - - - - - csharrison@chromium.org - - Counts of various events related to the strong popup blocker (aka abusive - experience enforcement), that is triggered via safe browsing. - - - - - - Removed in favor of - SubresourceFilter.PageLoad.Activation.RedirectPosition2.Enforcement - - csharrison@chromium.org - ericrobinson@chromium.org - - For pages that trigger Safe Browsing triggered popup blocker (in warn or - enforce modes), records the position in the redirect chain for the page the - activation was triggered by. If SubresourceFilterConsiderRedirects is - disabled, then always returns "Only navigation". - - - - - rogerm@chromium.org - feed@chromium.org - - Whether the feed was fetched with activity logging enabled. This is logged - on every feed fetch. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: count of app lifecycle events reported to the Feed library. - Recorded as these events occur; e.g. when Chrome is foregrounded, - backgrounded, or the user clears cached browsing data. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: number of rows present in a history deletion that's causing all - current suggestions to be deleted. Each row should correspond to a url that - is beign removed from history. Is not emitted when entire history is being - cleared. - - - - - - Removed in favor of ContentSuggestions.Feed.AppLifecycle.Events. - - pnoland@chromium.org - fgorski@chromium.org - - Android: count of app lifecycle events reported to the Feed library. - Recorded as these events occur; e.g. when Chrome is foregrounded, - backgrounded, or the user clears cached browsing data. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - When an article on the NTP is opened by the user, records whether it is - available offline. When an article is available offline, it will have an - offline badge in the UI on the NTP. Opening the article occurs when the user - navigates from the NTP to the article itself, which can be either in the - current tab or a new tab. Note that this is independent of whether the - article is actually opened as an offline page or not. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Records whether an article on the NTP that is shown to the user was also - available offline. When an article is available offline, it will have an - offline badge in the UI. The initial offline status of the article is used - for this metric. While it is possible for the offline status to change while - the article is on screen, this metric will not be re-emitted. The criteria - for an article to be "shown" is for 2/3 of its vertical height to - be on screen for any amount of time. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Tracks the number of operations in a Feed mutation when database receive the - commit request. - - - - - - - vincb@google.com - feed@chromium.org - src/chrome/browser/android/feed/OWNERS - Actions related to the feed controls. - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Tracks the number of entries for the Feed storage after database perform get - all keys request. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The display status of the content suggestions when users open NTPs. - Whether content suggestions are disabled by policy (e.g. enterprise or - supervised users), enabled but collapsed, or enabled and expanded when a new - NTP is created. - - - - - petewil@chromium.org - harringtond@chromium.org - feed@chromium.org - - Tracks each instance of user engagement with the feed, by scrolling or - interacting with a card (opening the URL or using the menu). Note that each - event type reports samples very differently and buckets can't be directly - compared. We're mostly interested in unique user counts. We track every - interaction, and we report ENGAGED and ENGAGED_SIMPLE once per user visit. A - user visit is when the user scrolls or interacts with the NTP more than 5 - minutes after the previous visit. The SCROLLED engagement type represents a - single instance of the user scrolling, and is reported once per Feed visit. - The INTERACTED engagement type represents one instance of using the menu or - opening a feed article into its own tab. SCROLLED and INTERACTED are - reported for every occurrence, thus we could end up with more scrolled and - interected than ENGAGED or ENGAGED_SIMPLE samples. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The type of spinner when the content suggestion shows the loading - spinner. This is tracked based on if the spinner is shown, not how long it - is visible. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: How long the content suggestion loading spinner is shown when a - loading spinner finishes showing. This is tracked based on when the spinner - is enabled in the UI, not how long it is actually visible on screen. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: How long the content suggestion loading spinner is shown when a - spinner is destroyed without completing. This is tracked based on when the - spinner is enabled in the UI, not how long it is actually visible on screen. - - - - - - Removed in favor of CachedImageFetcher.Events. - - wylieb@chromium.org - - Android: Represents success/failure of Feed image loading. Recorded upon - each individual image retrieved from the feed_image_cache. Feed v1 only. - - - - - - Removed in favor of CachedImageFetcher.Events. - - wylieb@chromium.org - - Android: The time it takes for Feed to load an image from the cache. - - - - - - Removed in favor of CachedImageFetcher.Events. - - wylieb@chromium.org - - Android: The time it takes for Feed to load an image from the network. - - - - - harringtond@chromium.org - feed@chromium.org - - Android: Status of image fetches for the feed. Recorded for each image - fetch. Fetches happen when loading the feed or scrolling the feed. Fetched - images are cached, so subsequent loads may not fetch again. Feed v2 only. - - - - - - Removed 4/2019 in favor of ProtoDB.InitStatus.*. - - gangwu@chromium.org - fgorski@chromium.org - - Tracks the Feed storage success rate during initial storage. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The position of an interest header on the NTP that the user has indicated - they aren't interested in the story's source. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The position of an interest header on the NTP that the user has indicated - they aren't interested in the story's topic. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - The Feed library encountered an error at any time. - - - - - Removed 4/2019 in favor of ProtoDB.LoadKeysSuccess.*. - - gangwu@chromium.org - fgorski@chromium.org - Tracks the Feed storage success rate during load keys. - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The time it takes for the Feed to load all keys from the storage. - - - - - harringtond@chromium.org - feed@chromium.org - - Latencies for individual steps taken to load the feed. This is reported at - most once per Chrome execution, and only reported for a Feed load operation - that ends with the Feed showing up on the UI. All steps added together tally - to the total time taken. - - Feed v2 only. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Status of loading new feed data in the background. Feed v2 only. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Status of loading the initial Feed stream, which happens when a feed surface - is shown. Feed v2 only. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - This is the store-specific status for the initial load of the Feed stream. - This is provided along with ContentSuggestions.Feed.LoadStreamStatus.Initial - because store errors can be shadowed by fallback to network fetch. Feed v2 - only. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Status of loading additional Feed content onto the bottom of the stream. - Feed v2 only. - - - - - - Removed 4/2019 in favor of ProtoDB.LoadEntriesSuccess.*. - - gangwu@chromium.org - fgorski@chromium.org - Tracks the Feed storage success rate during load entries. - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The time it takes for the Feed to load entries from the storage. - - - - - - This implementation is incorrect and we are now using - NewTabPage.ActionAndroid2 instead. Marked obsolete in 01-2020 - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - The position of a card in the feed from which the user has opened the Manage - Interests page. Recorded when the Manage Interest item is clicked in the - card menu. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The amount of time fetching articles takes, regardless of success. This - includes the time it takes to get an auth token for signed in users. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: the size in kb of gzip-compressed requests sent by the Feed's - networking host. Recorded when a request is sent. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The integer status code of network requests made by the feed - library's networking host. This code includes both protocol(1xx-5xx) and - non-protocol(-xxx) errors. Recorded when a request completes. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: the uncompressed size in KB of responses received by the Feed's - networking host. Recorded when a successful response is received. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The HTTP response status for a network request made by the Feed component. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The amount of time it takes to get an access token for signed in users. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: failure reason when attempting to fetch an OAuth token for the - feed. Recorded when a token fetch completes. - - - - - - Removed in favor of ContentSuggestions.Feed.Network.RequestStatusCode. - - pnoland@chromium.org - - Android: The integer status code of network requests made by the feed - library's networking host. This code includes both protocol(1xx-5xx) and - non-protocol(-xxx) errors. Recorded when a request completes. - - - - - frechette@chromium.org - feed@chromium.org - - Android: Whether the notice card for feed action reporting has been - fulfilled. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The number of urls that have offline status requested per call. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The number of milliseconds to round trip offline status for a set of URLs - from Offline Pages component. - - - - - - Removed 4/2019 in favor of ProtoDB.UpdateSuccess.*. - - gangwu@chromium.org - fgorski@chromium.org - - Tracks the Feed storage success rate during commit operations. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The time it takes for the Feed to commit operations from the storage. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The number of milliseconds it takes for Feed content to be visible in the - UI. If content is not immediately available, this is conceptually the amount - of time a loading spinner is shown to the user. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The integer error code when Piet wants to report events that - occurred during Frame rendering. - - - - - - Removed in favor of - ContentSuggestions.Feed.Network.RequestSizeKB.Compressed. - - pnoland@chromium.org - - Android: the size in kb of gzip-compressed requests sent by the Feed's - networking host. Recorded when a request is sent. - - - - - - Removed in favor of ContentSuggestions.Feed.Network.ResponseSizeKB. - - pnoland@chromium.org - - Android: the uncompressed size in KB of responses received by the Feed's - networking host. Recorded when a successful response is received. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Difference in age of content between feed and host. Recorded when the Feed - asks the scheduler how to behave when a NTP is opened. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The match status between Feed and the host when the scheduler's - ShouldSessionRequestData method is called. This occurs whenever the NTP is - opened, and tries to track if the Feed and host state agrees or disagrees. - If the device already has content, new requests are not necessarily required - for a reasonable user experience. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The match status between Feed and the host when the scheduler's - ShouldSessionRequestData method is called. This occurs whenever the NTP is - opened, and tries to track if the Feed and host state agrees or disagrees. - The type of request that could be outstanding is to fetch new or more news - articles, and when requests are outstanding new requests should not be - started. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The scheduler watches for various triggers, which cause it to decide if a - refresh is currently warranted or not. This histogram is emitted when a - trigger causes a refresh. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - When NTP is opened, the scheduler host tells the Feed library how to act, if - the existing content should be shown, immediately or with timeout, and if a - refresh request should be started. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - When the Feed scheduler receives a refresh request, the scheduler will - decide to refresh or not depending on the scheduler status. Recorded when - the Feed scheduler receives the request. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - When the previous last fetch attempt time is cleared, log the time since the - last fetch attempt. This typically occurs when suggestions are cleared. A - client that has never made a successful fetch (at least since it was last - cleared) will report the time since epoch. - - - - - carlosk@chromium.org - petewil@chromium.org - feed@chromium.org - Number of each type of feedback sent about the feed. - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - The reason for a server request from the Feed's prespective, when the - request is started. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How long it took from enqueuing the task to when it was run. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How long it took from the task starting to when it finished executing. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How long a user used the Feed in one day (local time midnight to midnight). - Reported at most once per day. Usage reported is typically from the previous - day, but could be from several days ago if the user is not active. Time is - calculated starting with the first Feed interaction, until the Feed surface - is closed, or the user is idle (no scrolling or other actions) for 30 - seconds. - - - - - - Removed in favor of ContentSuggestions.Feed.TokenCompleted.ContentCount2. - Removed 03/2019. http://crbug.com/943838 - - skym@chromium.org - gangwu@chromium.org - - How many top level features were in the continuation response, typically - clusters. Recorded when the fetch completes successfully. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How many top level features were in the continuation response, typically - clusters. Recorded when the fetch completes successfully. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How many tokens were in the continuation response, typically ways to fetch - more articles. Recorded when the fetch completes successfully. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - When a token fails to complete, how many failures this token has seen. - Record when the fetch fails. - - - - - - Removed in favor of ContentSuggestions.Feed.Network.TokenFetchStatus. - - pnoland@chromium.org - - Android: failure reason when attempting to fetch an OAuth token for the - feed. Recorded when an artcile fetch completes. - - - - - iwells@chromium.org - harringtond@chromium.org - feed@chromium.org - - Result of attempting to upload a batch of one or more actions. - - - - - iwells@chromium.org - harringtond@chromium.org - feed@chromium.org - - Result of an UploadActionsTask run in which zero or more batches of user - actions are uploaded. See ContentSuggestions.Feed.UploadActionsBatchStatus - for the status of a particular batch upload. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Counts of user actions within the feed surface (Feed v2 only). - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Time between the UI requesting additional stream content and failure by - either a 15 second timeout or a surface closure. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Time between the UI requesting additional stream content and the content - being provided within 15 seconds. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - Reported when a user taps on a Feed card unless the page is not loaded - successfully within 20 seconds. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - The time between a user tapping on a Feed card and the page finishes loading - successfully. Only reported when loading takes less than 20 seconds. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - The time between a Feed surface opening and failing to provide the user - content. This is reported when either the surface is closed or a timeout of - 15 seconds expires. - - - - - harringtond@chromium.org - carlosk@chromium.org - feed@chromium.org - - The time between a Feed surface opening and the user viewing the first - content. If this takes more than 15 seconds, - ContentSuggestions.Feed.UserJourney.OpenFeed.FailureDuration is reported - instead. - - - - - harringtond@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: Time spent reading the page linked by an opened suggestion card. - This is a lower-bound time. Does not include time after Chrome is closed and - re-opened. Does not include time after the visited tab no longer has focus, - or after the tab is navigated. For the 'open in new tab' action, time starts - when the user switches to the new tab. If the user returns by tapping the - suggestion again, it will be recorded as another entry in this histogram. - - Feed v2 only. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The position of a clicked element in the stream not accounting for - header views. The top being 0. Position does not change after initial - layout. Specifically the position does not update if dismisses/removes are - performed. This is similar to NewTabPage.ContentSuggestions.Opened, but - records the specific elementType that was clicked. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The time since the content was made available on the device. This - could be the time for when this content was retrieved from the server or the - time the data was pushed to the device. Recorded when the user clicks the - element. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The position of a viewed element in the stream not accounting for - header views. The top being 0. Position does not change after initial - layout. Specifically the position does not update if dismisses/removes are - performed. This is similar to NewTabPage.ContentSuggestions.Shown, but - records the view after it has been on the screen for 500 milliseconds of - time instead of on predraw. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - Android: The time since the content was made available on the device. This - could be the time for when this content was retrieved from the server or the - time the data was pushed to the device. Recorded when the element has been - on the screen for 500 milliseconds. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How many top level features were in an initial article fetch, typically - clusters. Recorded when an article fetch completes and were previously in - zero state. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - - How many tokens were in an initial article fetch, typically ways to fetch - more articles. Recorded when an article fetch completes and were previously - in zero state. - - - - - carlosk@chromium.org - harringtond@chromium.org - feed@chromium.org - The reason the zero state (no articles) is shown to a user. - - - - - Removed in favor of ContentSuggestions.FetchPendingSpinner.VisibleDuration. - - dgn@chromium.org - ntp-dev+metrics@chromium.org - - Android: How long the content suggestion placeholder is shown. This is - tracked based on when the placeholder is enabled in the UI, not how long it - is actually visible on screen. Depending on the screen size, the used value - could be bigger. - - - - - - Removed in favor of - ContentSuggestions.Feed.FetchPendingSpinner.VisibleDuration. - - dgn@chromium.org - ntp-dev+metrics@chromium.org - - Android: How long the content suggestion loading spinner is shown. This is - tracked based on when the spinner is enabled in the UI, not how long it is - actually visible on screen. Depending on the screen size, the used value - could be bigger. - - - - - michaeldo@chromium.org - src/ios/web/web_state/ui/OWNERS - - Logs true when the system touches are cancelled in order to show the Context - Menu instead of performing a default system action. Only logged on iOS. - - - - - michaeldo@chromium.org - src/ios/web/web_state/ui/OWNERS - - Logged when DOM element details are not yet available when the user - completes a long press. Also logs if the context menu was shown once the - element details became available or if the display was cancelled. This - ensures that all context menu gestures are eventually processed. Only logged - on iOS. - - - - - - Removed 06/2019. iFrame Context Menu feature shipped. - - michaeldo@chromium.org - - How long it takes to fetch the details of the DOM element the user is - selecting for the context menu. On iOS, JavaScript must be run in order to - get the details of the DOM element. If the element is not inside the main - frame, latency could be added due to the communication between frames. Only - logged on iOS. - - - - - michaeldo@chromium.org - src/ios/web/web_state/ui/OWNERS - - Logged when the Context Menu will be displayed. Also logs if the element for - the last touch was found in the main frame or a iframe. Only logged on iOS. - - - - - mrsuyi@chromium.org - gambard@chromium.org - - Logged when the copying image from context menu is invoked and relevant - events happen during the copying image procedure. - - - - - mrsuyi@chromium.org - gambard@chromium.org - - Result of getting image data by JavaScript for CopyImage, SaveImage and - SearchByImage from iOS context menu. Recorded when the JavaScript returns, - or fails for timeout. - - - - - benwgold@google.com - lens-chrome@google.com - - Whether the user supports the Lens intent and if not, the reason why. - Recorded only if the feature is enabled when the long-press context menu is - shown for an image. - - - - - qinmin@chromium.org - - Type of the url when user saves the content through the save link context - menu. - - - - - - Removed from code as of 5/2019. WARNING: The code emitting this histogram - was broken on desktop, and logged many items that should not have been - logged at all into bucket 0. The values for bucket 0 are wrong and should - not be relied upon. The replacements are ContextMenu.SelectedOptionDesktop, - ContextMenu.SelectedOptionAndroid, and ContextMenu.SelectedOptionIOS. - - lzbylut@google.com - - The option that the user selected from a context menu. This mis-logged and - thus was removed. - - - - - - - avi@chromium.org - mpearson@chromium.org - chrome-analysis-team@google.com - - The option that the user selected from a context menu on Android. This is - logged on Android only; check out ContextMenu.SelectedOptionIOS for iOS, and - ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is - invoked on mixed content, only one of the submetrics receives the log; read - the code to determine which one. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - avi@chromium.org - mpearson@chromium.org - - The option that the user selected from a context menu on desktop. This is - logged on desktop only; check out ContextMenu.SelectedOptionIOS for iOS, and - ContextMenu.SelectedOptionAndroid for Android. Note that if a menu is - invoked on mixed content, only one of the submetrics receives the log; read - the code to determine which one. - - - - - - - avi@chromium.org - mpearson@chromium.org - chrome-analysis-team@google.com - - The option that the user selected from a context menu on iOS. This is logged - on iOS only; check out ContextMenu.SelectedOptionAndroid for Android, and - ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is - invoked on mixed content, only one of the submetrics receives the log; read - the code to determine which one. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - mpearson@chromium.org - - Recorded when a context menu is shown, sliced by whether a web contents was - present. (It generally should be; indeed, this code path should not be - followed when it is absent. For instance, invoking a context menu from the - new tab page or from the sad tab page will not cause an emission to this - histogram.) Note that this refers to link context menus, not the - cut-copy-paste context menus that can appear during long presses on text on - a web page or long presses in the omnibox. This is an Android-only metric; - compare with RenderViewContextMenu.Shown and RenderViewContextMenu.Used on - desktop. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - Logged when the callback to fetch the thumbnail returns a result: Success - (bitmap data received) or Failure (null bitmap). Android only. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - The time it takes for the user to abandon the context menu after it's shown - by pressing back or touching outside the menu. This is only logged if the - menu is abandoned. See ContextMenu.TimeToTakeAction.SelectedItem for the - cases where it is closed as a result of user interaction with the menu. - Android only. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - - The time it takes for the user to select an item. This is only logged if the - menu is closed as a result of the user clicking a menu item or a DirectShare - button. See ContextMenu.TimeToTakeAction.Abandoned for the cases where it is - abandoned by the user. Android only. - - - - - - Removed 06/2019. iFrame Context Menu feature shipped. - - michaeldo@chromium.org - - Logged when an unexpected FindElementResultHandler message was received by - the application. An unexpected message may be sent by a malicious frame. - Only logged on iOS. - - - - - twellington@chromium.org - chrome-android-app@chromium.org - Logged when the URL is clicked. Android only. - - - - ramyan@chromium.org - yyushkina@chromium.org - - Number of times the emoji item in the views text services context menu is - used. - - - - - michaeldo@chromium.org - src/ios/web/web_state/ui/OWNERS - - Logs true when the context menu gesture recognizer fully recognizes a long - press, but is still waiting on the DOM element details before the context - menu can be shown. Only logged on iOS. - - - - - - This feature was deprecated in M74 - - twellington@chromium.org - - Android: Whether contextual suggestions are enabled. Recorded when the - enabled state changes. Note that this may be recorded multiple times per - session. - - - - - - This feature was deprecated in M74 - - donnd@chromium.org - fgorski@chromium.org - twellington@chromium.org - - Records each event handled by the Contextual Suggestions backend. Recorded - when the event is sent to the backend, typically when a UI or network action - is registered. Implemented for Android. - - - - - - This feature was deprecated in M74 - - pnoland@chromium.org - - Android: The net::Error status code of contextual suggestion fetches. - Recorded when a fetch completes. - - - - - - This feature was deprecated in M74 - - pnoland@chromium.org - fgorski@chromium.org - - Android: the amount of time taken elapsed between a contextual suggestion - fetch starting and ending. Recorded when a fetch is completed. - - - - - - This feature was deprecated in M74 - - pnoland@chromium.org - - Android: The size of the serialized and base64-encoded proto sent to the - server when fetching contextual suggestions. Recorded when a fetch is - - - - - - This feature was deprecated in M74 - - pnoland@chromium.org - - Android: The http status code of contextual suggestion fetches. Recorded - when a fetch completes. - - - - - - This feature was deprecated in M75 - - pnoland@chromium.org - - Android: The number of bytes in the response received when a contextual - suggestions fetch completes. Recorded when the response is received. - - - - - - This feature was deprecated in M74 - - pnoland@chromium.org - - Android: The size of the response body received when a contextual - suggestions fetch completes. Recorded when the response is received. - - - - - - This feature was deprecated in M74 - - fgorski@chromium.org - wylieb@chromium.org - - Android: The length of a visit on a page. Reported for HTTP and HTTPS pages - provided there was something visible printed to the screen. Selecting a tab - or loading a new URL in current tab starts timing a visit. Switching to a - different tab, closing the tab or loading a new URL finishes timing and - reports the time if the page did a visually non-empty paint or finished - loading. Bucketed by short/medium/long. - - - - - - This feature was deprecated in M74 - - fgorski@chromium.org - wylieb@chromium.org - - Android: The length of a visit on a page. Reported for HTTP and HTTPS pages - provided there was something visible printed to the screen. Selecting a tab - or loading a new URL in current tab starts timing a visit. Switching to a - different tab, closing the tab or loading a new URL finishes timing and - reports the time if the page did a visually non-empty paint or finished - loading. - - - - - - This feature was deprecated in M74 - - twellington@chromium.org - - Android: Whether the user preference for contextual suggestions is enabled. - Recorded on cold start and when the user has changed the preference state. - Note that this may be recorded multiple times per session. - - - - - - Removed 01/2019, no longer needed - - twellington@chromium.org - - Android: Whether the contextual suggestions results are returned to the - UI-layer while the user is in overview mode. - - - - - - This feature was deprecated in M74 - - twellington@chromium.org - - Android: The position of the clicked contextual suggestion card within its - cluster. - - - - - - This feature was deprecated in M74 - - twellington@chromium.org - - Android: The position of the clicked contextual suggestion card within the - entire list of suggestions. - - - - - johnidel@chromium.org - csharrison@chromium.org - - Records the time it takes to clear conversion data. Logged any time site - data is cleared in Chrome. - - - - - johnidel@chromium.org - csharrison@chromium.org - - Records the "extra" non-scheduled time it took to send a - particular conversion report. This is primarily due to a report's scheduled - report time taking place while the browser is closed. Recorded when a - conversion report is sent. - - - - - johnidel@chromium.org - csharrison@chromium.org - - Records the number of registered conversions - (https://github.com/WICG/conversion-measurement-api) on a given top level - page load. Recorded when the page navigates away or is otherwise closed. - Only recorded for non-off-the-record profiles (OTR profiles have the feature - disabled). - - - - - johnidel@chromium.org - csharrison@chromium.org - - Records the high level request status of a conversion report. Recorded for - every conversion report sent. - - - - - morlovich@chromium.org - - Whether or not updates to the backing store succeeded or failed, recorded - every update. - - - - - - Removed 2015-08-17 as part of cookie histogram cleanup - (https://crbug.com/521135). - - Please list the metric's owners. Add more owner tags as needed. - Intervals between access time updates for each cookie. - - - - morlovich@chromium.org - - Recorded when a problem occurs trying to commit changes to the cookie store - back to disk, in the SQLite store. - - - - - - Removed 2019-10-23 as part of cookie histogram cleanup - (https://crbug.com/993120). - - mkwst@chromium.org - - Record when at attempt is made to delete an equivalent cookie on a set - cookie operation and when such a cookie is found and deleted. Also measure - when strict secure cookie rules affect this outcome and prevent a cookie - from being deleted. - - - - - - Removed 2017-07-14 as it demonstrated that making cookie parsing rules - stricter was not feasible. See https://crbug.com/638117. - - ricea@chromium.org - - Indicates whether a cookie initialised from a Set-Cookie header value was - valid or not. This is only logged after cookies containing control - characters have already been rejected, so "Invalid" here means - that the cookie contains quotes, commas, backslashes or top-bit-set - characters. - - - - - estark@chromium.org - - Number of times a cookie was set with a name prefixed by - "__Secure-" or "__Host-" (prefixes reserved by - https://tools.ietf.org/html/draft-west-cookie-prefixes). - - - - - estark@chromium.org - - Number of times a cookie was set with a name prefixed by - "__Secure-" or "__Host-" that violate cookie prefix - rules. That is, a __Secure- cookie must be set over a secure connection with - the Secure attribute, and a __Host- cookie must be set over a secure - connection, with the Secure attribute, with no Domain attribute, and with a - Path attribute of "/". (As defined in - https://tools.ietf.org/html/draft-west-cookie-prefixes.) - - - - - bingler@chromium.org - chlily@chromium.org - - The scheme a cookie was set by and the scheme of the request that the cookie - was sent to. This is recorded once per cookie each time a URL request has - its headers set. - - - - - estark@chromium.org - - For each cookie added to the store, record whether its source URL has a - cryptographic scheme, broken down by Secure and not Secure. - - - - - chlily@chromium.org - tnagel@chromium.org - - Records the detection of a corrupted meta table. See http://crbug.com/111376 - . - - - - - chlily@chromium.org - morlovich@chromium.org - - Records a failure to recover a corrupted meta table. See - http://crbug.com/111376 . - - - - - battre@chromium.org - - Number of cookies in the store (recorded every 10 minutes of active browsing - time) - - - - - - Removed as of March 9, 2020. - - dmikurube@chromium.org - - The size, on disk, of the cookie database as it is being loaded. - - - - - - Removed Jul 2017 for lack of use. - - nharper@chromium.org - - For each cookie removed from the store, the reason it was removed. - - - - - - Removed 2015-08-17 as part of cookie histogram cleanup - (https://crbug.com/521135). - - Please list the metric's owners. Add more owner tags as needed. - - For each domain, number of cookies in that domain (recorded every 10 minutes - of active browsing time). - - - - - - Removed 2015-08-17 as part of cookie histogram cleanup - (https://crbug.com/521135). - - Please list the metric's owners. Add more owner tags as needed. - - For every top level domain, number of subdomains in that top level domain - (recorded every 10 minutes of active browsing time). - - - - - - Removed 2015-08-17 as part of cookie histogram cleanup - (https://crbug.com/521135). - - Please list the metric's owners. Add more owner tags as needed. - - For every top level domain, number of cookies in that domain (recorded every - 10 minutes of active browsing time). - - - - - - Removed Jul 2017 for lack of use. - - nharper@chromium.org - - For each evicted (not expired) cookie, the amount of time since it was last - used - - - - - battre@chromium.org - Number of minutes until cookie expires when set. - - - - - Removed Feb 2019 as further data collection is no longer necessary. - - rockot@google.com - - The length of time between when the network stack receives a request for a - cookie list and when it actually responds to the request or abandons it (for - e.g. a closed renderer). - - - - - mkwst@chromium.org - - The size of each outgoing request's 'Cookie' header field's value, in bytes. - - - - - bingler@chromium.org - chlily@chromium.org - - The value of the effective samesite for cookies that will be included in a - request. Logged once per successful inclusion. - - - - - bingler@chromium.org - chlily@chromium.org - - The value of the effective samesite for cookies that will be accepted from a - response. Logged once per successful inclusion. - - - - - morlovich@chromium.org - chlily@chromium.org - - Whether killing the database because it was corrupted beyond repair - succeeded. - - - - - - Removed June 2020. No longer needed because results are expected to be - stable. - - chlily@chromium.org - morlovich@chromium.org - - The age in milliseconds of a cookie that activates the Lax-allow-unsafe - intervention. Emitted whenever a cookie is included in a request with an - unsafe HTTP method, where the cookie has an unspecified SameSite attribute - and is only included because it is new enough to fall under the age - threshold for allowing Lax-allow-unsafe. - - - - - morlovich@chromium.org - - Recorded when a problem is recorded when loading the persistent cookie - store. - - - - - - Removed 2019-10-31 as part of cookie histogram cleanup - (https://crbug.com/993120). - - tnagel@chromium.org - - Degree of protection against cookie theft. Recorded for each cookie when - setting the `Cookie` header for a request. - - - - - - Removed 2019-07-03. Cookie.Count measures similar things with different - timing. - - morlovich@chromium.org - - This histogram records the total number of cookies loaded from disk, - including any cookies that are discarded during loading (for whatever - reason). - - - - - chlily@chromium.org - kaustubhag@chromium.org - - Records the number of distinct keys (eTLD+1's) that have experienced - eviction of a non-expired cookie due to reaching the max number of cookies - per key. This is not persisted across network service restarts, so it - represents the number of such eTLD+1's that have relatively recently added - new cookies that went over the limit (since the last browser restart, crash, - etc). Recorded every 10 minutes of active browsing time. - - - - - chlily@chromium.org - kaustubhag@chromium.org - - Records the number of distinct keys (eTLD+1's) that have any stored cookies - (which may or may not be expired). Recorded every 10 minutes of active - browsing time. - - - - - - Removed as of 9/2013. Experiment to measure control characters in cookies is - finished. - - Please list the metric's owners. Add more owner tags as needed. - - When parsing a cookie, indicates if control characters were present in any - of the cookie values and if any of the cookie values were invalid. - Specifically, checks that all of the parsed values are valid according to - the valid token definition in Section 2.2 of RFC2616 which specifies a token - must have no separators (i.e. no characters from the following string, - ignoring the starting and ending single quote: '()<>@,;:\"/[]?={} - \t') and no control characters. - - - - - pwnall@chromium.org - - This histogram records the total duration of time during which at least one - web request was blocked waiting for the cookie store to load. If no requests - were affected, the value is 0. If two requests are simultaneously blocked - for 1 second, the value is 1 second. If two requests are consecutively - blocked for 1 second each, the value is two seconds. - - - - - pwnall@chromium.org - - The number of distinct Effective Top-Level Domains Plus One (ETLD+1, i.e., - google.com, bbc.co.uk) for which a priority cookie load occurred. - - - - - - Removed as of 8/2015. - - huangs@chromium.org - - The duration in seconds between a cookie getting evicted (due to the number - of cookies exceeding a domain limit), and subsequently reinstated. - - - - - chlily@chromium.org - morlovich@chromium.org - - The same-site context of a request, i.e. the relationship between the - request and the navigational environment. Logged on every request to access - a cookie. - - - - - chlily@chromium.org - bingler@chromium.org - - The value of the cookie's SameSite attribute, if any. This is logged once - per created cookie, upon parsing of the SameSite attribute from a string. - - - - - bingler@chromium.org - kaustubhag@chromium.org - - The type of breaking same-site context downgrade a cookie is experiencing - along with the secureness of the origin that we're attempting to send the - cookie to. Logged once per included cookie or if the cookie was excluded - only due to insufficient same-site context. - - For more information on breaking context downgrades please see the comment - block above - net::CanonicalCookie::CookieInclusionStatus::WARN_STRICT_LAX_DOWNGRADE_STRICT_SAMESITE. - - - - - bingler@chromium.org - kaustubhag@chromium.org - - The type of breaking same-site context downgrade a cookie is experiencing - along with the secureness of the origin that is attempting to set the - cookie. Logged once per included cookie or if the cookie was excluded only - due to insufficient same-site context. - - For more information on breaking context downgrades please see the comment - block above - net::CanonicalCookie::CookieInclusionStatus::WARN_STRICT_LAX_DOWNGRADE_STRICT_SAMESITE. - - - - - - Removed Apr 2020 as this metric doesn't capture the correct information. - https://crbug.com/1066231 - - bingler@chromium.org - kaustubhag@chromium.org - - The value of the SameSiteCookieContext if a Lax or Strict cookie is being - sent http-to-https or https-to-http for the site-for-cookies to the request. - Logged once per cookie sent with the above conditions. - - - - - - Removed Apr 2020 as this metric doesn't capture the correct information. - https://crbug.com/1066231 - - bingler@chromium.org - kaustubhag@chromium.org - - The value of the SameSiteCookieContext if a Lax or Strict cookie is being - set http-to-https or https-to-http for the site-for-cookies from the - response. Logged once per cookie sent with the above conditions. - - - - - chlily@chromium.org - morlovich@chromium.org - - If a cookie was SameSite=None, this records whether or not it was Secure. - Logged once per attempt to set a SameSite=None cookie. - - - - - chlily@chromium.org - morlovich@chromium.org - - If a cookie had an unspecified SameSite attribute, this records what mode it - was treated as, i.e. what the effective SameSite mode is. Logged once per - attempt to determine SameSite inclusion/exclusion for an - unspecified-SameSite cookie. - - - - - - Removed June 2020. No longer needed because results are expected to be - stable. - - chlily@chromium.org - morlovich@chromium.org - - The age in milliseconds of a cookie that would have activated the - Lax-allow-unsafe intervention except for the fact that it is too old. - Emitted whenever a cookie is excluded from being sent on a request with an - unsafe method, where the cookie has an unspecified SameSite attribute and is - too old to fall under the age threshold to allow Lax-allow-unsafe. - - - - - - Removed as of 9/2013. Experiment to measure control characters in cookies is - finished. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates whether a cookie attribute pair was set with both a valid key and - a valid attribute value or not. For the key, this implies that it was a - valid token as defined in Section 2.2 of RFC2616 which specifies a token - must have no separators (i.e. no characters from the following string, - ignoring the starting and ending single quote: '()<>@,;:\"/[]?={} - \t') and no control characters. For the value, this implies that it - contained no control characters and no semicolon. - - - - - - Removed as of 9/2013. Experiment to measure control characters in cookies is - finished. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates whether a cookie name was set with a valid token. A valid token is - defined in Section 2.2 of RFC2616 which specifies a token must have no - separators (i.e. no characters from the following string, ignoring the - starting and ending single quote: '()<>@,;:\"/[]?={} \t') and no - control characters. - - - - - - Removed as of 9/2013. Experiment to measure control characters in cookies is - finished. - - Please list the metric's owners. Add more owner tags as needed. - - Indicates whether a cookie value was valid or invalid when there was an - attempt to set it, where a valid value is defined in RFC 6265 as ASCII - characters excluding controls, whitspace, comma, semicolon, and backslash. - - - - - - Removed as of 9/2015. The associated experiment was flawed. - - erikchen@chromium.org - - The number of session cookies deleted on shutdown. This metric is emitted - even if no cookies are deleted. - - - - - - Removed as of 9/2015. The associated experiment was flawed. - - erikchen@chromium.org - - The amount of time required to delete session cookies on shutdown. This - metric is emitted even if no cookies are deleted. - - - - - erikchen@chromium.org - - The number of session cookies deleted on startup. This metric is emitted - even if no cookies are deleted. This metric is not emitted if session - cookies are restored, rather than deleted on startup. - - - - - erikchen@chromium.org - - The amount of time required to delete session cookies on startup. This - metric is emitted even if no cookies are deleted. This metric is not emitted - if session cookies are restored, rather than deleted on startup. - - - - - nharper@chromium.org - - The amount of time (ms) between the cookie store load starting and - completing. - - - - - pwnall@chromium.org - - The amount of time (ms) to migrate a v9 cookie database to v10. - - - - - chlily@chromium.org - morlovich@chromium.org - - The amount of time (ms) to migrate a v10 cookie database to v11. Migration - occurs upon first startup of a browser version with v11 database code. - - - - - chlily@chromium.org - morlovich@chromium.org - - The amount of time (ms) to migrate a v11 cookie database to v12. Migration - occurs upon first startup of a browser version with v12 database code. - - - - - - Removed as of 04/2015. The migration has finished for most users. - - The amount of time (ms) to migrate a v4 database to v5. - - - - - Removed as of 04/2015. The migration has finished for most users. - - The amount of time (ms) to migrate a v5 database to v6. - - - - - Removed as of 04/2015. The migration has finished for most users. - - The amount of time (ms) to migrate a v6 database to v7. - - - - - Removed as of 04/2015. The migration has finished for most users. - - The amount of time (ms) to migrate a v7 database to v8. - - - - erikchen@chromium.org - The amount of time (ms) to migrate a v8 database to v9. - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time (ms) to get cookies for each URL request. - - - - - nyquist@chromium.org - The amount of time (ms) to initialize the cookies database. - - - - - Removed as part of histogram expiry. See discussion in crbug.com/975202. - - nyquist@chromium.org - - The amount of time (ms) to read and parse the domain map from the cookies - database. - - - - - pwnall@chromium.org - - This histogram records the wall-clock delay between a priority load task - being posted to the DB-thread and its execution. - - - - - erikchen@chromium.org - - This histogram records the the total amount of time spent fetching the - cookies associated with an eTLD+1 from disk, including time spent waiting in - task queues. - - - - - pwnall@chromium.org - - This histogram records the sum of the durations of all initial tasks loading - cookies from the database. - - - - - erikchen@chromium.org - - This histogram records the wall-clock delay between the Load task being - posted to the DB-thread and its execution. - - - - - - Removed as part of histogram expiry. See discussion in crbug.com/975202. - - nyquist@chromium.org - - The amount of time (ms) to read the domain map from the cookies database. - - - - - - Removed as part of histogram expiry. See discussion in crbug.com/975202. - - nyquist@chromium.org - - The amount of time (ms) to parse the domains already loaded from the cookies - database and put them in the domain map. - - - - - mkwst@chromium.org - For each cookie added to the store, record it's type(s). - - - - - Removed 2019-10-31 as part of cookie histogram cleanup - (https://crbug.com/993120). - - mkwst@chromium.org - tnagel@chromium.org - - Records the age (in days) of {Age} cookie delivered along with a request. - Recorded when setting the `Cookie` header for a given request. - {CookieConnectionType} {CookieSiteAffinity} - - - - - - - - - - - - - - - - - wychen@chromium.org - - The cache hit status of metadata extraction for AppIndexing. - - - - - wychen@chromium.org - - The time spent on scanning the document in the main frame to extract the - metadata. The metadata would be used to feed Icing for CopylessPaste feature - on Android. This only counts pages with failed or empty JSON extraction. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - wychen@chromium.org - The error status of metadata extraction for AppIndexing. - - - - wychen@chromium.org - - The time spent on scanning the document in the main frame to extract the - metadata. The metadata would be used to feed Icing for CopylessPaste feature - on Android. This only counts pages with successful JSON extraction. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - For each audio thread running state, records the number of busyloops. - Busyloop means the audio thread doen't sleep during more than two loops, - which may make the system busy. Depending on the time of running state, the - records is seperated into three logs: ShortPeriod(shorter than 10 minutes), - MediumPeriod(between 10 and 60 minutes), LongPeriod (longer than 60 - minutes). - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - When each busyloop stops, records the length of it. The lengths exceeding - 1000 are recorded as 1000. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - It is used for logging input device usage of ChromeOS users. The count - indicates the number of each input device has been used and is recorded when - a device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - It is used for logging output device usage of ChromeOS users. The count - indicates the number of each input device has been used and is recorded when - a device is closed. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The volume of a device, which is recorded when closing a device. - - - - - enshuo@chromium.org - chromeos-audio@google.com - - For each HFP audio device record whether it supports battery indicator. - - - - - enshuo@chromium.org - chromeos-audio@google.com - - For each HFP battery level change event record if it comes from the command - defined by Apple's Spec or BT HFP spec. The count indicates how frequent - user might see this event and can help us decide which data source we prefer - to show if the headset supports both. - - - - - enshuo@chromium.org - chromeos-audio@google.com - - For each SCO connection record the returned event. The event indicates if - the setup of the connection is successful or not. - - - - - enshuo@chromium.org - chromeos-audio@google.com - - For each HFP audio device supporting WBS record how many packets are lost - per 1000 packets when the device is closed. This is for tracking how bad the - packet loss can be for WBS in real world. - - - - - hychao@chromium.org - chromeos-audio@google.com - - For each single connection of bluetooth HFP audio device record whether it - supports wideband-speech feature or not. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The highest hardware delay of input device in CRAS(ChromeOS audio server). - It is calculated by 1000 * highest_hw_level / largest_cb_level. The - highest_hw_level is the highest remaining frames in the device. The - largest_cb_level is the largest callback threshold of streams which have - attached to this device. The value is recorded when the device is removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The highest hardware delay of output device in CRAS(ChromeOS audio server). - It is calculated by 1000 * highest_hw_level / largest_cb_level. The - highest_hw_level is the highest remaining frames in the device. The - largest_cb_level is the largest callback threshold of streams which have - attached to this device. The value is recorded when the device is removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The highest hardware level of input device in CRAS(Chrome OS audio server). - The hardware level is the remaining frames in the device. For input device, - it can show the latency between capturing and actual reading. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The highest hardware level of output device in CRAS(Chrome OS audio server). - The hardware level is the remaining frames in the device. For output device, - it can show the latency between writing and actual playout. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device A2DP in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of fallback device in the abnormal situation. The runtime is the - duration between opening and closing a device. The value is recorded when - the device is closed. - - - - - hychao@chromium.org - chromeos-audio@google.com - - The runtime of input device Bluetooth narrowband in CRAS(ChromeOS audio - server). The runtime is the duration between opening and closing a device. - The value is recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of Bluetooth input device that doesn't fall to any other - category we defined. i.e HSP, narrowband or wideband. The runtime is the - duration between opening and closing a device. The value is recorded when - the device is closed. - - - - - hychao@chromium.org - chromeos-audio@google.com - - The runtime of input device Bluetooth wideband in CRAS(ChromeOS audio - server). The runtime is the duration between opening and closing a device. - The value is recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device InternalMic in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device HFP in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device Hotword in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device HSP in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device InternalMic in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device InternalMic in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device Mic in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of fallback device in the normal situation. The runtime is the - duration between opening and closing a device. The value is recorded when - the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device PostDspLoopback in CRAS(ChromeOS audio server). - The runtime is the duration between opening and closing a device. The value - is recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device PostMixLoopback in CRAS(ChromeOS audio server). - The runtime is the duration between opening and closing a device. The value - is recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device InternalMic in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of silent hotword device in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device Unknown in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input device USB in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of input stream in CRAS(ChromeOS audio server). The runtime is - the duration between creating and destroying a stream. The value is recorded - when the stream is destroyed. - - - - - hychao@chromium.org - chromeos-audio@google.com - - For each single connection of bluetooth HFP record the result of codec - negotiation, if supported. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The first time missed callbacks happened on input streams in CRAS (Chrome OS - audio server). In normal situation, audio thread should follow the callback - schedule to send frames to clients. However, sometimes it may miss schedule - because of some reasons. When the first time that audio thread misses - callback schedule, record how many seconds have passed since stream started - running. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The first time missed callbacks happened on output streams in CRAS (Chrome - OS audio server). In normal situation, audio thread should follow the - callback schedule to fetch frames from clients. However, sometimes it may - miss schedule because of some reasons. When the first time that audio thread - misses callback schedule, record how many seconds have passed since stream - started running. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The number of missed callbacks of input streams in a day after rescheduling. - It is calculated by number of the missed callbacks / runtime of the stream - after rescheduling. This value is recorded when the stream is removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The number of missed callbacks of output streams in a day after - rescheduling. It is calculated by number of the missed callbacks / runtime - of the stream after rescheduling. This value is recorded when the stream is - removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The number of missed callbacks of input streams in a day. It is calculated - by number of the missed callbacks / runtime of the stream. This value is - recorded when the stream is removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The number of missed callbacks of output streams in a day. It is calculated - by number of the missed callbacks / runtime of the stream. This value is - recorded when the stream is removed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The second time missed callbacks happened on input streams in CRAS (Chrome - OS audio server). When the second time audio thread misses callback - schedule, record how many seconds have passed since the first time. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The second time missed callbacks happened on output streams in CRAS (Chrome - OS audio server). When the second time audio thread misses callback - schedule, record how many seconds have passed since the first time. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device A2DP in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of fallback device in the abnormal situation. The runtime is the - duration between opening and closing a device. The value is recorded when - the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of Bluetooth output device in CRAS(ChromeOS audio server) that - doesn't belong to any category we defined. i.e A2DP, HFP or HSP. The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device Haptic in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device HDMI in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device Headphone in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device HFP in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device HSP in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device InternalSpeaker in CRAS(ChromeOS audio server). - The runtime is the duration between opening and closing a device. The value - is recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device Lineout in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of fallback device in the normal situation. The runtime is the - duration between opening and closing a device. The value is recorded when - the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device Unknown in CRAS(ChromeOS audio server). The - runtime is the duration between opening and closing a device. The value is - recorded when the device is closed. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output device USB in CRAS(ChromeOS audio server). The runtime - is the duration between opening and closing a device. The value is recorded - when the device is closed. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The runtime of output stream in CRAS(ChromeOS audio server). The runtime is - the duration between creating and destroying a stream. The value is recorded - when the stream is destroyed. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The callback threshold of stream in CRAS(Chrome OS audio server). It is the - number of frames when to request more from the client. This value is - recorded when the stream is created. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The client type of input stream in CRAS(Chrome OS audio server). This value - is recorded when the stream is created. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The client type of output stream in CRAS(Chrome OS audio server). This value - is recorded when the stream is created. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The bit map of effects to be enabled on this stream. This value is recorded - when the stream is created. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The flags of stream in CRAS(Chrome OS audio server). It is the special - handling for stream. This value is recorded when the stream is created. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The sampling format of stream in CRAS(Chrome OS audio server). This value is - recorded when the stream is created. - - - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The sampling rate of stream in CRAS(Chrome OS audio server). This value is - recorded when the stream is created. - - - - - hychao@chromium.org - chromeos-audio@google.com - - The longest additional time CRAS(Chrome OS audio server) ever waits for a - stream exceeding the timeout threshold. This value is recorded per stream - when it gets removed and used to investigate the audio glitch/skip problem - on Chrome OS. - - - - - yuhsuan@chromium.org - chromeos-audio@google.com - - The number of underruns happened on one audio device. Underrun here means - there are no samples in device buffer while device is playing. It is - recorded when device is closed by CRAS(Chrome OS audio server). - - - - - - - wfh@chromium.org - chrome-stability-core@google.com - - The exit codes for crashed extension processes. Note: Due to - https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. - - - - - - - wfh@chromium.org - chrome-stability-core@google.com - - The exit codes for crashed renderer processes. Note: Due to - https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. - - - - - jperaza@chromium.org - crashpad-dev@chromium.org - - The reason that a crash report entered the upload pending state. - - - - - jperaza@chromium.org - crashpad-dev@chromium.org - The size of a crash report minidump on disk when captured. - - - - jperaza@chromium.org - crashpad-dev@chromium.org - Logs whether a crash uploaded succeeded or failed. - - - - jperaza@chromium.org - crashpad-dev@chromium.org - The reason that a crash report upload was skipped. - - - - jperaza@chromium.org - crashpad-dev@chromium.org - The outcome of execution of the Crashpad exception handler. - - - - mark@chromium.org - crashpad-dev@chromium.org - The exception code encountered in a crash on Mac OS X. - - - - jperaza@chromium.org - crashpad-dev@chromium.org - The exception code encountered in a crash on Windows. - - - - jperaza@chromium.org - crashpad-dev@chromium.org - - A count of the number of exceptions handled by Crashpad with two buckets for - starting and finishing. - - - - - mark@chromium.org - crashpad-dev@chromium.org - - The exception code encountered for a crash of the crash handler process on - Mac OS X. - - - - - jperaza@chromium.org - crashpad-dev@chromium.org - - The exception code encountered for a crash of the crash handler process on - Windows. - - - - - jperaza@chromium.org - crashpad-dev@chromium.org - Handler start/crash/exit events. - - - - - Removed as of 04/2016 as CrashPad does not implement this. - - siggi@chromium.org - - Reports the result of an attempt to report a crash dump via Breakpad. - Success indicates only that the out-of-process crash reporter succesfully - generated a dump. The success or failure of the eventual upload is not - measured. This stability metric is logged from the first Chrome launch - post-dump. - - - - - - Removed as of 04/2016 as CrashPad does not implement this. - - siggi@chromium.org - - Reports the result of an attempt to report a dump via Breakpad without - crashing. Success indicates only that the out-of-process crash reporter - succesfully generated a dump. The success or failure of the eventual upload - is not measured. This stability metric is logged from the first Chrome - launch post-dump. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - Reports the Foundation error code of an attempt to upload a breakpad crash - report. "NSNoError" if the upload was successful. - - - - - - Removed as of 03/2018 when Chrome for iOS stopped uploading crash dumps in - the background. - - olivierrobin@chromium.org - pkl@chromium.org - - Time delta between when the crash took place and when the crash was uploaded - by the app as a background task. Only logged on iOS. - - - - - - 07/2020: Investigation complete. - - iby@chromium.org - cros-telemetry@google.com - - Which crash handler (Breakpad or Crashpad) is handling - ProducerClient::InitSharedMemoryIfNeeded()'s attempt to do a - DumpWithoutCrashing. Investigating why Breakpad never seems to generate - InitSharedMemoryIfNeeded reports on some ChromeOS devices. - - - - - - 06/2020: Removed in favor of - CrashReport.DumpWithoutCrashingResult.FromInitSharedMemoryIfNeeded2. - - iby@chromium.org - cros-telemetry@google.com - - Did the attempt to dump without crashing in - ProducerClient::InitSharedMemoryIfNeeded() succeed or fail? Investigating - why Breakpad never seems to generate InitSharedMemoryIfNeeded reports on - some ChromeOS devices. - - - - - - 07/2020: Investigation complete. - - iby@chromium.org - cros-telemetry@google.com - - Did the attempt to dump without crashing in - ProducerClient::InitSharedMemoryIfNeeded() succeed or fail? Investigating - why Breakpad never seems to generate InitSharedMemoryIfNeeded reports on - some ChromeOS devices. - - - - - - Removed as of 03/2018 when Chrome for iOS stopped uploading crash dumps in - the background. - - olivierrobin@chromium.org - pkl@chromium.org - - The number of crash reports present when the app wakes up as a background - task to upload crash reports. Only logged on iOS. - - - - - - Removed 01/2017 in Issue 680162 with the removal of Kasko. - - siggi@chromium.org - - Counts crash reports that the Kasko crash reporter fails to upload and hands - off to Chrome. Kasko stores the failed reports in a location specified by - Chrome. Chrome records this metric when it detects new minidump files in - that location. Currently the reports are discarded, but they could - eventually be uploaded via the Chrome network stack. - - - - - mutexlox@chromium.org - iby@chromium.org - cros-telemetry@google.com - - The amount of time crash_sender takes to run when invoked directly on Chrome - OS, without counting time spent sleeping (e.g. for hold_off_time). Used to - make an informed decision about a timeout. - - - - - mutexlox@chromium.org - iby@chromium.org - cros-telemetry@google.com - - The amount of time crash_sender takes to run when invoked directly on Chrome - OS. Used to make an informed decision about a timeout. - - - - - - Removed as of 12/2013. Default pinned apps trial is finished. - - Please list the metric's owners. Add more owner tags as needed. - Chrome OS shelf clicks. - - - - charleszhao@chromium.org - tby@chromium.org - - This histogram is emitted each time when CrOSAction is recorded by the - CrOSActionRecorder. For each CrOSAction multiple values can be emitted, - corresponding to different events happened during the action processing by - CrOSActionRecorder. - - - - - fdegros@chromium.org - chromeos-files-app@google.com - - The type of archive file that Chrome OS cros-disks daemon is requested to - mount. - - - - - fdegros@chromium.org - chromeos-files-app@google.com - - The media type of removable device that Chrome OS cros-disks daemon is - requested to mount. - - - - - fdegros@chromium.org - chromeos-files-app@google.com - - The type of file system that Chrome OS cros-disks daemon is requested to - mount. - - - - - fdegros@chromium.org - chromeos-files-app@google.com - - The error code returned by ZIP mounting program fuse-zip, which is called - every time a user opens a ZIP archive in ChromeOS Files App. - - - - - fdegros@chromium.org - chromeos-files-app@google.com - - The error code returned by RAR mounting program rar2fs, which is called - every time a user opens a RAR archive in ChromeOS Files App. - - - - - austinct@chromium.org - - The error code of disk format signals received from the Chrome OS cros-disks - daemon. - - - - - austinct@chromium.org - - Time taken for the Chrome OS cros-disks daemon to perform a format - operation. - - - - - amistry@chromium.org - - The error code of disk mount signals received from the Chrome OS cros-disks - daemon. - - - - - amistry@chromium.org - - The {mount type}x{mount error code} received from the Chrome OS cros-disks - daemon. - - - - - amistry@chromium.org - - Time taken by the Chrome OS cros-disks daemon to perform a Mount operation. - - - - - amistry@chromium.org - - The error code of disk unmount operations returned from the Chrome OS - cros-disks daemon. - - - - - amistry@chromium.org - - Time taken by the Chrome OS cros-disks daemon to perform an Unmount - operation. - - - - - alemate@chromium.org - cros-oac@google.com - - Records the number of times when first-run dialog was shown. - - - - - alemate@chromium.org - cros-oac@google.com - - Index of furthest step that was reached during tutorial. Since order of - steps could change eventially and new steps could apear we use index here - instead of step name. - - - - - alemate@chromium.org - cros-oac@google.com - The total time that user spent on first-run tutorial. - - - - alemate@chromium.org - cros-oac@google.com - The time that user spent on some step of tutorial. - - - - alemate@chromium.org - cros-oac@google.com - Tracks the way how user left tutorial. - - - - alemate@chromium.org - cros-oac@google.com - - Records the number of times when first-run tutorial has been launched. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time a Crostini app is launched, recording whether the app is - the built in terminal, a registered app, or an unknown app. - - - - - clumptini@google.com - tbuckley@chromium.org - - The result of attempting to launch a Crostini app (including Terminal). - - - - - clumptini@google.com - tbuckley@chromium.org - - Records the number of Crostini apps that surface in the launcher at login - time (not including the Terminal). This only logs if Crostini is enabled for - the current user. - - - - - clumptini@google.com - tbuckley@chromium.org - - The available disk space at the start of the crostini install flow, recorded - when installation was canceled. This is recorded any time the user cancels - the install before it finishes. This includes cases where e.g. they - previously tried installing and got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - - The available disk space at the start of the crostini install flow, recorded - when installation returned an error. This is recorded any time the user - tries to install install crostini and gets an error. This includes cases - where e.g. they previously tried installing and got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - - The available disk space at the start of the crostini install flow, recorded - when installation succeeded. This is recorded any time the user successfully - installs crostini. This includes cases where e.g. they previously tried - installing and got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - Result of crostini backup. - - - - clumptini@google.com - tbuckley@chromium.org - - log base 2 of compressed container backup size in bytes, rounded to the - nearest integer. Value is between 0 and 50, to give good granularity for - common sizes, while maintaining a range that can support very large sizes. - - - - - clumptini@google.com - tbuckley@chromium.org - - log base 2 of uncompressed container image size in bytes, rounded to the - nearest integer. Value is between 0 and 50, to give good granularity for - common sizes, while maintaining a range that can support very large sizes. - - - - - clumptini@google.com - tbuckley@chromium.org - - 100 * compressed size / container size. The conventional compression ratio - of input / output has not been used as the resulting value is unbounded. - - - - - clumptini@google.com - tbuckley@chromium.org - Time taken for failed backup. - - - - clumptini@google.com - tbuckley@chromium.org - Time taken for successful backup. - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time a Crostini container is launched, recording the OS - version running inside the container. - - - - - clumptini@google.com - tbuckley@chromium.org - - The percentage of the system CPU that crosvm processes used during the - 10-minute measuring period. This is recorded once every 10 minutes when - crosvm is running. - - - - - clumptini@google.com - tbuckley@chromium.org - - The number of crosvm processes that are running at the end of the 10-minute - interval. This is recorded once every 10 minutes when crosvm is running. - - - - - clumptini@google.com - tbuckley@chromium.org - - The percentage of the system memory that crosvm processes used at the end of - the 10-minute measuring period. This is recorded once every 10 minutes when - crosvm is running. - - - - - - Removed 10/2019 because it was never used. - - sidereal@google.com - nverne@chromium.org - - The maximum space allowed for a VM disk image, as set at install time. This - is recorded each time a disk image is successfully created. - - - - - clumptini@google.com - davidmunro@google.com - - Records the result (e.g. succeeded) whenever an attempt to resize a Crostini - disk finishes. - - - - - clumptini@google.com - davidmunro@google.com - - Recorded each time a user tries resizing a Crostini disk to infer attempts - that started but never finished (e.g. code bug missing a timeout). This - won't exactly line up with the total of Crostini.DiskResizeResult due to how - metrics work (e.g. start one day and result the next) but should be close. - - - - - clumptini@google.com - davidmunro@google.com - - Records the type (e.g. sparse qcow2) of the user's disk. Emitted often, you - probably want to look at the unique user numbers of this metric. Certain - disk types are vulnerable to disk corruption in certain scenarios so this - metric tracks our progress in moving people off them and tells us if we need - to do additional work to migrate users off. - - - - - clumptini@google.com - tbuckley@chromium.org - - Filesystem corruption events in the crostini VM, recorded every time - corruption is observed to affect the state of the system. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the CrostiniRecoveryView is show, on detecting that a VM - is still running after a Chrome crash. - - - - - clumptini@google.com - tbuckley@chromium.org - - Emitted whenever a run of CrostiniRestarter is triggered except during the - initial install. - - - - - clumptini@google.com - tbuckley@chromium.org - - The result of a single run of CrostiniRestarter. This is recorded any time - the crostini restart flow is triggered, except during the initial install. - - - - - clumptini@google.com - tbuckley@chromium.org - Result of crostini restore. - - - - clumptini@google.com - tbuckley@chromium.org - Time taken for failed restore. - - - - clumptini@google.com - tbuckley@chromium.org - Time taken for successful restore. - - - - clumptini@google.com - tbuckley@chromium.org - victorhsieh@chromium.org - Record user's choice in Crostini Settings - - - - clumptini@google.com - tbuckley@chromium.org - - Emitted whenever a run of CrostiniRestarter is triggered during the initial - install. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user completes the Crostini setup UI, recording the - result of the setup. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user initiates the Crostini setup UI, recording the - UI surface that invoked the setup. - - - - - clumptini@google.com - tbuckley@chromium.org - - A record of post-startup failures in crostini components. Buckets are - recorded to whenever we become aware that the corresponding component has - failed. - - - - - joelhockey@chromium.org - tbuckley@chromium.org - - Record which settings in terminal are changed by users. This is captured - each time terminal is launched and fetches the current settings, and not - just when settings are changed, in order to give the best information about - the current state of active users. - - - - - clumptini@google.com - tbuckley@chromium.org - - The time from a user setting up their device, to the user enabling Crostini. - - - - - clumptini@google.com - tbuckley@chromium.org - - The time taken for the crostini installer to be canceled by the user. This - is recorded any time the user cancels the install before it finishes. This - includes cases where e.g. they previously tried installing and got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - - The time taken for the crostini installer to fail due to an error. This is - recorded any time the user tries to install install crostini and gets an - error. This includes cases where e.g. they previously tried installing and - got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - - The time taken for the crostini installer to finish successfully. This is - recorded any time the user successfully installs crostini. This includes - cases where e.g. they previously tried installing and got an error. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user completes the Crostini uninstall UI, recording - the result of the uninstall. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user initiates the Crostini uninstall UI, recording - the UI surface that initiated the uninstall. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time we display (or would display, see suffixes) a - notification that the user is trying to do something Crostini doesn't - support. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user sees the Crostini upgrade Notifiation, recording - the action that closded the notification. - - - - - clumptini@google.com - tbuckley@chromium.org - - A collection of events that can occur while upgrading the crostini - container, recorded as they occur. - - - - - clumptini@google.com - tbuckley@chromium.org - - Recorded each time the user sees the Crostini upgrade UI, recording the UI - surface that initiated the upgrade. - - - - - clumptini@google.com - tbuckley@chromium.org - - Records the reason why the "Cros USB device detected" notification - was dismissed. Recorded on notificiation close, after usb attached. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether or not the device manufacturer name returned in the - hardware info is empty. Recored during the construction of a - ClientAppMetadata proto. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether or not the device model name returned in the hardware info - is empty. Recored during the construction of a ClientAppMetadata proto. - - - - - khorimoto@chromium.org - better-together-dev@google.com - - Indicates the result of fetching an InstanceId token during the construction - of a ClientAppMetadata proto messages. - - - - - khorimoto@chromium.org - nohle@chromium.org - better-together-dev@google.com - - Counts the number of times the InstanceId token fetch got retried because it - did not match with the expected InstanceId. Logged during the construction - of a ClientAppMetadata proto message. - - - - - hansberry@chromium.org - better-together-dev@google.com - Indicates success of performing a DeviceSync. - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval performed during - initialization of the DeviceSync service. Recorded when the async callback - is invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval - performed during initialization of the DeviceSync service. Recorded when the - async callback is invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of GCM registration performed during - initialization of the DeviceSync service. Recorded when the async callback - is invoked. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of GCM registration performed during initialization of - the DeviceSync service. Recorded when the async callback is invoked. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the DeviceSync service initialization. - Recorded each time the DeviceSync service starts up, after initialization - succeeds. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Indicates that there was no issue retrieving supported and enabled software - features, or that there were enabled features which were not in the - supported feature set. See the histogram - "CryptAuth.DeviceSyncSoftwareFeaturesResult.Failures" for a - breakdown of failures by feature type. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Breaks down by feature type - "CryptAuth.DeviceSyncSoftwareFeaturesResult"'s count of enabled - features which were not in the supported feature set. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async GetDevicesActivityStatus API call to - CryptAuth during multi-device setup. Recorded when the async callback is - invoked or when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval needed for the - device activity getter. Recorded when the async callback is invoked or when - the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval needed - for the device activity getter. Recorded when the async callback is invoked - or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async GetDevicesActivityStatus API call - during multi-device setup. Recorded when the async callback is invoked or - when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the ClientAppMetadataFetch during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async BatchNotifyGroupDevices API call to - CryptAuth. Recorded when the async callback is invoked or when the call - times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval for the - CryptAuth device notifier. Recorded when the async callback is invoked or - when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval for the - CryptAuth device notifier. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async BatchNotifyGroupDevices API call to - CryptAuth. Recorded when the async callback is invoked or when the call - times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async device metadata decryption during the - CryptAuth v2 DeviceSync flow. Records a success if the operation did not - timeout; a separate metric, - CryptAuth.DeviceSyncV2.DeviceSyncer.MetadataDecryptionSuccess, tracks - individual encryption failures.Recorded when the async callback is invoked - or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async group private key decryption during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async device metadata decryption during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async group private key decryption during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - - Removed 2020-01-02 because metric was never used. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ShareGroupPrivateKey API call during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the group private key sent by CryptAuth matches the - existing group private key when they are expected to agree. Emitted during a - CryptAuth v2 DeviceSync if the group private key is not being rotated. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the local device metadata agrees with that sent by - CryptAuth in the SyncMetadata response. Emitted during the CryptAuth v2 - DeviceSync flow, after device metadata is decrypted. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not device metadata sent by CryptAuth in the SyncMetadata - response was able to be decrypted. Emitted during the CryptAuth v2 - DeviceSync flow for each device metadata packet. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not device metadata sent by CryptAuth in the SyncMetadata - response was able to be parsed from a decrypted serialized byte string into - a proto. Emitted during the CryptAuth v2 DeviceSync flow for each device - metadata packet. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async BatchGetFeatureStatuses API call during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the expected number of devices were sent in the - BatchGetFeatureStatuses response. Emitted when a BatchGetFeatureStatuses - response is received from the CryptAuth server. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async BatchGetFeatureStatuses API call - during the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not a device ID in the BatchGetFeatureStatuses response - has been seen already in the same response. Emitted for each device in the - BatchGetFeatureStatuses response. Emitted when a BatchGetFeatureStatuses - response is received from the CryptAuth server. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the feature type strings returned in the - BatchGetFeatureStatuses response are known feature types. Emitted for each - feature type for each device in the BatchGetFeatureStatuses response. - Emitted when a BatchGetFeatureStatuses response is received from the - CryptAuth server. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not a feature is marked as enabled even though it is - listed as unsupported. This should never happen. Emitted for all feature - types, for each device in the BatchGetFeatureStatuses response. Emitted when - a BatchGetFeatureStatuses response is received from the CryptAuth server. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not a device in the BatchGetFeatureStatuses response was - included in the BatchGetFeatureStatuses request. Emitted for each device in - the BatchGetFeatureStatuses response. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async BatchSetFeatureStatuses API call to - CryptAuth. Recorded when the async callback is invoked or when the call - times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval for the - CryptAuth feature status setter. Recorded when the async callback is invoked - or when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval for the - CryptAuth feature status setter. Recorded when the async callback is invoked - or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async BatchSetFeatureStatuses API call to - CryptAuth. Recorded when the async callback is invoked or when the call - times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ShareGroupPrivateKey API call during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async group private key encryption during the - CryptAuth v2 DeviceSync flow. Records a success if the operation did not - timeout; a separate metric, - CryptAuth.DeviceSyncV2.GroupPrivateKeySharer.EncryptionSuccess, tracks - individual encryption failures. Recorded when the async callback is invoked - or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the group private key was able to be encrypted using - a device's encrypting key. Recorded during the ShareGroupPrivateKey phase of - the CryptAuth v2 DeviceSync flow. Recorded for each device with whom we - intend to share the group private key. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async group private key encryption during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ShareGroupPrivateKey API call during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not a device's key used to encrypt the group private key - is empty. If the key is empty, the group private key cannot be encrypted and - shared with the device. Recorded during the ShareGroupPrivateKey phase of - the CryptAuth v2 DeviceSync flow. Recorded for each device with whom we - intend to share the group private key. - - - - - nohle@chromium.org - better-together-dev@google.com - - The clients' reasons for making CryptAuth v2 DeviceSync requests. Recorded - when a DeviceSync is requested. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the first async SyncMetadata API call during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the second async SyncMetadata API call during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async group key creation during the CryptAuth v2 - DeviceSync flow. Recorded when the async callback is invoked or when the - call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async local device metadata encryption during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the first async SyncMetadata API call during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async group key creation during the - CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async local device metadata encryption - during the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the second async SyncMetadata API call during - the CryptAuth v2 DeviceSync flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the device metadata packets sent by CryptAuth have - all of the necessary fields populated. Emitted for each device metadata - packet during the SyncMetadata phase of the CryptAuth v2 DeviceSync flow. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the device ID from a device metadata packet sent by - CryptAuth in the SyncMetadata response has the same ID as a packet from the - same response. Emitted for each device metadata packet during the - SyncMetadata phase of the CryptAuth v2 DeviceSync flow. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the number of devices returned by a v1 DeviceSync. Only recorded - when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and - v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices - are merged together, which occurs after either a v1 or v2 DeviceSync. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the number of devices returned by a v2 DeviceSync. Only recorded - when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and - v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices - are merged together, which occurs after either a v1 or v2 DeviceSync. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the percentage of devices returned by a v2 DeviceSync that replace - their v1 counterparts. This will only occur if the v2 device has a decrypted - public key that matches a v1 device. Only recorded when v1 and v2 DeviceSync - are running in parallel. Only recorded if a v1 and v2 DeviceSync has ever - previously occurred. Emitted when v1 and v2 devices are merged together, - which occurs after either a v1 or v2 DeviceSync. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the percentage of devices returned by a v2 DeviceSync that have a - decrypted user public key. Only recorded when v1 and v2 DeviceSync are - running in parallel. Only recorded if a v1 and v2 DeviceSync has ever - previously occurred. Emitted when v1 and v2 devices are merged together, - which occurs after either a v1 or v2 DeviceSync. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the ratio of the number of devices returned by a v2 DeviceSync to - the number returned by a v1 DeviceSync. Devices returned by a v2 DeviceSync - should be a subset of the devices returned by a v1 DeviceSync, barring any - race conditions. This ratio should be greater than or equal to - PercentageOfV1DevicesReplacedByV2Devices because a v2 device can only - replace its v1 counterpart if it has a decrypted public key. Only recorded - when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and - v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices - are merged together, which occurs after either a v1 or v2 DeviceSync. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether or not any device data in the device registry changed as a - result of the CryptAuth v2 DeviceSync attempt. Recorded when a DeviceSync - attempt finishes. - - - - - nohle@chromium.org - better-together-dev@google.com - - The CryptAuth v2 DeviceSync attempt results broken down by result code. - Recorded when a DeviceSync attempt finishes. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether the CryptAuth v2 DeviceSync attempt succeeded, failed, or - finished with non-fatal errors. Recorded when a DeviceSync attempt finishes. - - - - - nohle@chromium.org - better-together-dev@google.com - - The top-level result of the CryptAuth device enrollment process. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async EnrollKeys API call to CryptAuth during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async SyncKeys API call to CryptAuth during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or - when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async ClientAppMetadata retrieval during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or - when the call times out. - - - - - - Removed 2019-12-11 in favor of - CryptAuth.EnrollmentV2.GcmRegistration.Success because the timeout was - removed. - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async GCM registration call during the CryptAuth - v2 Enrollment flow. Recorded when the async callback is invoked or when the - call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the result of the async key creation call during the CryptAuth v2 - Enrollment flow. Recorded when the async callback is invoked or when the - call times out. - - - - - - Removed 2019-09-12 in favor of - CryptAuth.EnrollmentV2.ExecutionTime.ClientAppMetadataFetch2 because too - many results were reaching the max time limit. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval during - the CryptAuth v2 Enrollment flow. Recorded when the async callback is - invoked or when the call times out. - - - - - - Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async ClientAppMetadata retrieval during - the CryptAuth v2 Enrollment flow. Recorded when the async callback is - invoked or when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async EnrollKeys API call to CryptAuth - during the CryptAuth v2 Enrollment flow. Recorded when the async callback is - invoked or when the call times out. - - - - - - Removed 2019-12-11 in favor of - CryptAuth.EnrollmentV2.GcmRegistration.AttemptTime because too many results - were reaching the max time limit. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async GCM registration call during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async key creation call during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or - when the call times out. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async SyncKeys API call to CryptAuth - during the CryptAuth v2 Enrollment flow. Recorded when the async callback is - invoked or when the call times out. - - - - - - Removed 2020-07-29. GCM registration now occurs in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the execution time of the async GCM registration call during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked. - - - - - - Removed 2020-07-29. GCM registration now occurs in DeviceSync service. - - nohle@chromium.org - better-together-dev@google.com - - Records the success or failure of the async GCM registration call during the - CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked. - - - - - nohle@chromium.org - better-together-dev@google.com - - The clients' reasons for making CryptAuth v2 Enrollment requests. Recorded - when an enrollment is requested. - - - - - nohle@chromium.org - better-together-dev@google.com - - The CryptAuth v2 Enrollment attempt results broken down by result code. - Recorded when an enrollment attempt finishes. - - - - - nohle@chromium.org - better-together-dev@google.com - - The success or failure of CryptAuth v2 Enrollment requests. Recorded when an - enrollment attempt finishes. - - - - - nohle@chromium.org - better-together-dev@google.com - - The state--at system start time--of persisted user key pairs, generated - during CryptAuth v1 and/or v2 Enrollment: whether they exist and if they - agree. Recorded on CryptAuth v2 Enrollment manager construction. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records the multi-device feature type sent in a GCM message from CryptAuth - v2. Emitted when a GCM message with a feature type key/value pair is - received from CryptAuth. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the DeviceSync group name sent in a GCM message from - CryptAuth is valid. Currently the only valid group name is - "DeviceSync:BetterTogether". Emitted when a GCM message with a - DeviceSync group name key/value pair is received from CryptAuth. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the multi-device feature type sent in a GCM message - from CryptAuth v2 is recognized by the Chrome OS client. Emitted when a GCM - message with a feature type key/value pair is received from CryptAuth. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records whether or not the CryptAuth TargetService was specified in a GCM - message by both the CryptAuth v1 registration tickle type key/value pair as - well as the CryptAuth v2 target service key/value pair. Both key/value pairs - should not exist in same GCM message. Emitted when a GCM message is received - from CryptAuth. - - - - - nohle@chromium.org - better-together-dev@google.com - - The CryptAuth TargetService--Enrollment or DeviceSync--indicated by the - registration tickle type key/value pair of an incoming GCM message. The - registration tickle type is used in GCM messages sent by CryptAuth v1. - Emitted when a GCM message from CryptAuth is received. - - - - - nohle@chromium.org - better-together-dev@google.com - - The CryptAuth TargetService--Enrollment or DeviceSync--indicated by the - target service key/value pair of an incoming GCM message. This key/value - pair is used in GCM messages sent by CryptAuth v2. Emitted when a GCM - message from CryptAuth is received. - - - - - nohle@chromium.org - better-together-dev@google.com - - The time it takes the GCM driver to return the result of a GCM registration - request made by the CryptAuth GCM manager. CryptAuth registration with GCM - is only performed once, if successful, for a given user on a device as the - first step in CryptAuth v1 or v2 Enrollment. Recorded when the CryptAuth GCM - manager is notified by the GCM driver that the registration attempt - finished, successfully or not. The GCM driver might quietly retry failures - before notifying the CryptAuth GCM manager. The time recorded here - encompasses the possible retry attempts and delays from the GCM driver. - - - - - nohle@chromium.org - better-together-dev@google.com - - The result code from a GCM registration request made by the CryptAuth GCM - manager. CryptAuth registration with GCM is only performed once, if - successful, for a given user on a device as the first step in CryptAuth v1 - or v2 Enrollment. Recorded when the CryptAuth GCM manager is notified by the - GCM driver that the registration attempt finished, successfully or not. The - GCM driver might quietly retry failures before notifying the CryptAuth GCM - manager. This metric will not include results codes that were quietly - retried by the GCM driver. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether or not the Instance ID used by the CryptAuth client - differs from the previously retrieved ID. Recorded while fetching client app - metadata if a previous ID has been set. - - - - - nohle@chromium.org - better-together-dev@google.com - - Indicates whether or not the Instance ID token used by the CryptAuth client - differs from the previously retrieved token. Recorded while fetching client - app metadata if a previous token has been set. - - - - - zuan@chromium.org - cros-hwsec+uma@chromium.org - - Records the total running time of every async dbus calls of Cryptohome at - server side. - - - - - zuan@chromium.org - cros-hwsec+uma@chromium.org - - Records the total inqueue time of every async dbus calls of Cryptohome at - server side. Recorded when the first stage of this requests is served. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - Checksum status of critical persistent data used by Cryptohome. This status - is recorded every time the cryptohomed daemon reads a file. - - - - - slangley@chromium.org - wiefangsun@chromium.org - - In low disk space scenarios, Cryptohome erases whole user profiles. This is - a number of user profiles deleted during cleanup. Only reported when - non-zero. - - - - - apronin@chromium.org - louiscollard@chromium.org - zuan@chromium.org - cros-hwsec+uma@chromium.org - - Records when a deprecated API function in cryptohome is called, so we know - which exposed DBus API can be removed without side effect. - - - - - dspaid@chromium.org - - The status of the user home directory migration from ecryptfs to - ext4-crypto. This is logged once at the end of each migration. - - - - - kinaba@chromium.org - - The error code of file operation by which the user home directory migration - from ecryptfs to ext4-crypto has failed. This is logged once the migration - encounters a file I/O error. - - - - - kinaba@chromium.org - - The type of file operation at which the user home directory migration from - ecryptfs to ext4-crypto has failed. This is logged once the migration - encounters a file I/O error. - - - - - kinaba@chromium.org - - The category of the path where the user home directory migration from - ecryptfs to ext4-crypto has failed. This is logged once the migration - encounters a file I/O error. - - - - - dspaid@chromium.org - - The total amount of free disk space on the system when the user started the - migration from ecryptfs to ext4-crypto. This is only logged when the user - encounters an insufficient space error. - - - - - dspaid@chromium.org - - The total amount of free disk space on the system when the user received an - insufficient space error during the migration from ecryptfs to ext4-crypto. - This is only logged when the user encounters an insufficient space error. - - - - - dspaid@chromium.org - - The total number of bytes of xattr data that we are trying to store on a - file when we receive an insufficient space error. This includes both xattr - data already present on the file as well as the new xattr we are trying to - set. This is only logged during ecryptfs to ext4-crypto migration if we - receive an insufficient space error when setting a new extended attribute. - - - - - dspaid@chromium.org - - The status of the user home directory migration from ecryptfs to - ext4-crypto. This is logged once at the start of each migration. - - - - - hashimoto@chromium.org - - The total byte count (MB) of the data in a user's home directory which is - being migrated from ecryptfs to ext4-crypto. This is logged once when a new - migration starts. - - - - - hashimoto@chromium.org - - The total file count in a user's home directory which is being migrated from - ecryptfs to ext4-crypto. This is logged once when a new migration starts. - - - - - dspaid@chromium.org - pmarko@chromium.org - - The status of the user home directory minimal migration from ecryptfs to - ext4-crypto. This is logged once at the end of each minimal migration. - - - - - dspaid@chromium.org - pmarko@chromium.org - - The status of the user home directory minimal migration from ecryptfs to - ext4-crypto. This is logged once at the start of each minimal migration. - - - - - slangley@chromium.org - weifangsun@chromium.org - - In low disk space scenarios, Cryptohome erases caches while target amount of - free disk space is not reached. It starts from low priority categories. This - histogram reports which topmost priority was reached to fulfill a cleanup - request. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - Cryptohome errors. - - - - enlightened@chromium.org - tnagel@chromium.org - - Indicates whether Encrypted Vault Keyset Key (EVKK) is TPM wrapped. This is - reported when the Derive function inside scrypt auth block or TPM auth block - is called, which happends during cryptohome mount phase. - - - - - - Removed 05/2018 in favor of Cryptohome.GCache.FreedDiskSpaceInMb. Reports - zero in 99% of hits. - - oka@chromium.org - - The amount of drive cache (MB) which was evicted by cryptohome due to - shortage of remaining disk space. - - - - - vsavu@chromium.org - weifangsun@chromium.org - - In low disk space scenarios, Cryptohome performs a lot of disk space - operations to erase data. This is the amount of space that was released by - the automatic cleanup. - - - - - - Replaced by Cryptohome.FreeDiskSpaceTotalTime2 in M81. - - slangley@chromium.org - weifangsun@chromium.org - - Being replaced by Cryptohome.FreeDiskSpaceTotalTime2 - - In low disk space scenarios, Cryptohome performs a lot of disk space - operations to erase data. This is a number of milliseconds taken to perform - a cleanup. Reported only if longer than 5 ms. - - - - - slangley@chromium.org - weifangsun@chromium.org - - In low disk space scenarios, Cryptohome performs a lot of disk space - operations to erase data. This is a number of milliseconds taken to perform - a cleanup. Reported only if longer than 5 ms. Increased maximum and number - of buckets compared to FreeDiskSpaceTotalTime. - - - - - slangley@chromium.org - weifangsun@chromium.org - - This is an amount of Google Drive cache (MB) which was evicted by cryptohome - due to shortage of remaining disk space. Reported only if something was - deleted (greater than zero). - - - - - dspaid@chromium.org - - The encryption type used for a user's cryptohome directory. This is logged - each time the cryptohome is mounted. - - - - - - Retired in M81. - - vsavu@google.com - igorcov@chromium.org - - Records the result of using the install_attributes.pb cache. This is logged - at each device boot. - - - - - - Retired in M81. - - vsavu@google.com - igorcov@chromium.org - - Records the result of validating install_attributes.pb. This is logged at - each device boot. - - - - - - - pmalani@chromium.org - apronin@chromium.org - mnissler@chromium.org - allenwebb@chromium.org - cros-hwsec+uma@chromium.org - - Events related to Low Entropy (LE) credential management. These are logged - every time an operation involving a LE credential is performed. - - - - - alemate@chromium.org - rsorokin@chromium.org - cros-oac@google.com - - This is the status of cryptohome migration to GaiaId. Every time user logs - in current migration status is recorded. - - - - - fukino@chromium.org - - The amount of consumed battery level during cryptohome encryption migration. - This is logged when the battery level decreases during migration, and the - data is used to check if the minimum battery level required to start - migration is appropriate. - - - - - fukino@chromium.org - - The first screen in the encryption migration UI, which is shown when a user - attempts to log in to the system and old encryption (eCryptfs) is detected. - - - - - fukino@chromium.org - - The result of encryption migration from eCryptfs to Ext4 dircrypto. The - recorded result is what the migration UI in Chrome side is notified from - cryptohomed. - - - - - fukino@chromium.org - - The result of the removal of user's cryptohome. When the migration UI is - notified that the migration failed, the UI tries to remove the user's - cryptohome to make sure that the user can create clean crytohome directory - in the next sign-in. - - - - - fukino@chromium.org - - User's choice when the system is ready to migrate encryption. The user can - start migration or skip it. It is used to know how many users have skipped - migration. - - - - - fukino@chromium.org - - How many times each screen in migration UI is shown to the user. A screen is - recorded as a visible screen when the screen is kept displayed at least for - a second. - - - - - betuls@chromium.org - jorgelo@chromium.org - - The result of a cryptohome out-of-process mount cleanup. Recorded once per - logout. - - - - - betuls@chromium.org - jorgelo@chromium.org - - The result of a cryptohome out-of-process mount operation. Recorded once per - login attempt. - - - - - zuan@chromium.org - cros-hwsec+uma@chromium.org - - How many tasks runs in parallel typically in the mount thread of cryptohome. - Recorded when a requests comes in. Counts of 1 will not reported. - - - - - vsavu@chromium.org - slangley@chromium.org - weifangsun@chromium.org - - The amount of time (s) between disk cleanup runs. If there is sufficient - disk space, nothing is reported. The first cleanup run after boot is not - reported. - - - - - kerrnel@chromium.org - mnissler@chromium.org - - The amount of time (ms) for Chrome OS cryptohome daemon to verify the user's - password during an unlock operation. - - - - - dspaid@chromium.org - - The amount of time (ms) for the user's home directory to be migrated from - ecryptfs to ext4-crypto. If the migration is interrupted and subsequently - resumed (such as due to power loss) then no value is recorded for either - attempt. - - - - - dspaid@chromium.org - - The amount of time (ms) for the user's home directory to be migrated from - ecryptfs to ext4-crypto if the minimal migration method was used. If the - minimal migration is interrupted and subsequently resumed (such as due to - power loss) then no value is recorded for either attempt. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome daemon to initialize the - PKCS#11. Initializations under 1 second represent checks on a previously - initialized PKCS#11, and should be discarded for analysis. - - - - - - Removed 07/2019 as it is not used since crrev.com/c/1393048 - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home - directory asynchronously. - - - - - jorgelo@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time for Chrome OS cryptohome to mount the encrypted home - directory. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome to mount the encrypted - guest home directory asynchronously. - - - - - jorgelo@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time for Chrome OS cryptohome to mount the encrypted guest - home directory. - - - - - - Removed 06/2020 as it is not used since crrev.com/c/1183895 (8/2018). - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome to mount the encrypted - guest home directory synchronously. - - - - - - Removed 06/2020 as it hasn't been reported since around crrev.com/185598 - (~2014) and has been completely removed in crrev.com/c/1183895 (6/2020). - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home - directory synchronously. - - - - - jorgelo@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time cryptohome spends actively performing mounts when - creating an ephemeral user data directory. Does not include any process or - async dispatch overhead. - - - - - betuls@chromium.org - jorgelo@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time cryptohome spends performing the mounts for the user's - encrypted home directory. Does not include any process or async dispatch - overhead. - - - - - jorgelo@chromium.org - betuls@chromium.org - - The amount of time (ms) cryptohome spends terminating and reaping the - out-of-process mounter, which includes the time spent by the mounter itself - tearing down the user home directory. - - - - - jorgelo@chromium.org - betuls@chromium.org - - The amount of time (ms) cryptohome spends running the out-of-process - mounter, until the user home directory is finalized. - - - - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - The amount of time (ms) for Chrome OS cryptohome daemon to take ownership of - the TPM. - - - - - afakhry@chromium.org - - The errors resulting from interacting with the Trusted Platform Module (TPM) - device. - - - - - zuan@chromium.org - cros-hwsec+uma@chromium.org - - Records the time duration of every dbus outgoing calls issued from the - client of Crypthome in Chrome side. - - - - - ranj@chromium.org - yfriedman@chromium.org - - - - Records the time duration in CustomTab Activity from onStart/onResume to - onStop/onPause, if that activity is opened by Webapp/WebApk/Trusted Web - Activity. - - - - - yusufo@chromium.org - - Android: AppId declared by the launching application in EXTRA_APPLICATION_ID - in a custom tab. This histogram is used as a means to count the total - instances of custom tabs created meanwhile binning them across launching - apps that have identified themselves. Starting with M84 this is is also - recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - peconn@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/browserservices/OWNERS - - - Records whether the CustomTab/TrustedWebActivity "navigate to landing - page" algorithm for child tabs - e.g. tabs opened via window.open() - - produces the same behaviour (closes the current tab) as the webapp - "close current tab" algorithm. Recorded when the user clicks the - CustomTab/TrustedWebActivity close button on a child tab. Starting with M84 - this is is also recorded for webapps/WebAPKs. Filter the platform for just - CCT/TWA data. - - - - - peconn@chromium.org - peter@chromium.org - - Android: Recorded whenever user closes the custom tab by hitting the close - button or back to return to the caller app. Keeps track of the connection - status and whether the app was using a KeepAlive connection. Recorded only - for AGSA. Starting with M84 this is is also recorded for webapps/WebAPKs. - Filter the platform for just CCT/TWA data. - - - - - peconn@chromium.org - peter@chromium.org - - Android: Recorded whenever user closes the custom tab by hitting the close - button or back to return to the caller app. Keeps track of the connection - status and whether the app was using a KeepAlive connection. Recorded for - all apps other than AGSA. Starting with M84 this is is also recorded for - webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - lizeb@chromium.org - cct-team@google.com - - Time between the start of a detached resource request and its completion - (failure or success). Android only. Starting with M84 this is is also - recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - lizeb@chromium.org - cct-team@google.com - - Reports the final status of the detached request, including success. - Recorded once per detached resource request. Android only. Starting with M84 - this is is also recorded for webapps/WebAPKs. Filter the platform for just - CCT/TWA data. - - - - - lizeb@chromium.org - cct-team@google.com - - Number of redirects followed by a detached resource request until success or - failure. Android only. Starting with M84 this is is also recorded for - webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Time to create an activity delegate for a custom tabs dynamic module. - Android only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Time to create the package context for a custom tabs dynamic module. Android - only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Possible reasons for destroying a custom tabs dynamic module. Android only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - amalova@chromium.org - - Time to initialize the entry point class for a custom tabs dynamic module. - Android only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Time to load the entry point class for a custom tabs dynamic module. Android - only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Time to instantiate the entry point class for a custom tabs dynamic module. - Android only. - - - - - - Removed in February 2020 - - mvanouwerkerk@chromium.org - - Possible results when loading a custom tabs dynamic module. Android only. - - - - - - Removed in October 2019 - - msalama@google.com - lizeb@chromium.org - mvanouwerkerk@chromium.org - - The proportional set size (PSS) of code pages occupied by a custom tabs - dynamic module. Recorded before the module destruction. Android only. - - - - - - Removed in October 2019 - - msalama@google.com - lizeb@chromium.org - mvanouwerkerk@chromium.org - - The proportional set size (PSS) of code pages occupied by a custom tabs - dynamic module. Recorded when a module is loaded. Android only. - - - - - - Removed in October 2019 - - msalama@google.com - lizeb@chromium.org - mvanouwerkerk@chromium.org - - The resident set size (RSS) of code pages occupied by a custom tabs dynamic - module. Recorded before the module destruction. Android only. - - - - - - Removed in October 2019 - - msalama@google.com - lizeb@chromium.org - mvanouwerkerk@chromium.org - - The resident set size (RSS) of code pages occupied by a custom tabs dynamic - module. Recorded when a module is loaded. Android only. - - - - - - Finished experiment and replaced by CustomTabs.Visible in September 2020 - - asvitkine@chromium.org - src/base/metrics/OWNERS - - Experimental version of CustomTabs.Visible that is logged on a log start, - rather than log end, to check if this results in more logs being tagged. - Starting with M84 this is is also recorded for webapps/WebAPKs. Filter the - platform for just CCT/TWA data. - - - - - - Removed 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*. - - lizeb@chromium.org - - Time between the intent arrival in Chrome and the first navigation commit, - if the navigation is successful. Similar in principle to - Startup.FirstCommitNavigationTime. - - - - - - Removed 2017-08 in favor of CustomTabs.IntentToFirstNavigationStartTime. - - lizeb@chromium.org - - Time between the intent arrival to a Custom Tab and the navigation start - (note: not the navigation commit, as the name suggests). Recorded when the - page has finished loading. Non-"Herb" mode. - - - - - lizeb@chromium.org - - Time between the intent arrival to a Custom Tab and the first navigation - commit. Recorded for every custom tabs intent when the page has finished - loading. - - - - - lizeb@chromium.org - - Time between the intent arrival to a Custom Tab and the navigation start. - Recorded when the page has finished loading. Non-"Herb" mode. - - - - - lizeb@chromium.org - - Time between the intent arrival in Chrome and the first "page - loaded" event, if the navigation is successful. Non-"Herb" - mode. - - - - - lizeb@chromium.org - - Android only. Which flavors of mayLaunchUrl() were used before a tab launch. - Can be low and/or high confidence. Recorded at the same time as - CustomTabs.WarmupStateOnLaunch for the buckets "Session, No Warmup, - Warmup called from another UID", "Session, No Warmup" and - "Session, Warmup". - - - - - - Removed 4/2018 when prerender was removed from Custom Tabs. - - lizeb@chromium.org - - Android: When there is a prerender for a session with non-default - parameters, whether the prerender was matched when navigating. - - - - - lizeb@chromium.org - cct-team@google.com - - Recorded only on Android. Whether a parallel request was requested by the - calling application, and if so its initial status. Recorded once per handled - intent, when the request is initiated. Starting with M84 this is is also - recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - lizeb@chromium.org - - For Custom Tabs, records whether mayLaunchUrl() has been called, and if so, - whether the call was later matched by a URL launch. - - - - - lizeb@chromium.org - - When a URL prediction succeeds, time in ms between the prediction and the - actual launch. - - - - - - Removed 4/2018 when prerender was removed from Custom Tabs. - - lizeb@chromium.org - - Android: When prerendering a URL for Custom Tabs, whether the client session - uses the default parameters. - - - - - alexilin@chromium.org - - Time between the start of a detached resource request for resource prefetch - and its completion (failure or success). Android only. - - - - - alexilin@chromium.org - - Reports the final status of the detached request for resource prefetch, - including success. Recorded once per resource prefetch request. Android - only. - - - - - - Replaced by CustomTabs.SpareWebContents.Status2 as of 03/2019. - - lizeb@chromium.org - - Android: When a spare WebContents is created from Custom Tabs, record - creation, and whether it was used, killed or destroyed. Creation is recorded - to get the "abandoned" case, that is when Chrome is killed before - the renderer. - - - - - lizeb@chromium.org - mthiesse@chromium.org - - Android: When a spare WebContents is created from Custom Tabs, record - creation, and whether it was used by CCT, stolen by another Chrome Activity, - killed or destroyed. Creation is recorded to get the "abandoned" - case, that is when Chrome is killed before the renderer. Starting with M84 - this is is also recorded for webapps/WebAPKs. Filter the platform for just - CCT/TWA data. - - - - - lizeb@chromium.org - - Android: When a spare WebContents is created from Custom Tabs, record how - long is took before the render process was killed. Starting with M84 this is - is also recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA - data. - - - - - lizeb@chromium.org - - Recorded only for Android. How a speculation was started or why it was - disallowed. This is recorded when a speculation of any kind is requested, - with either a "Speculation allowed" value, or a reason why it was - not allowed. If the speculation is allowed and is attempted to be started, - the status on start will be counted in addition: one of - "Prefetch", "Prerender", "Background Tab" or - "Prerender not started". The last case is when a prerender is - abandoned during start. Starting with M84 this is is also recorded for - webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - lizeb@chromium.org - - Recorded only for Android. Recorded when a speculation is requesting to swap - into a visible tab. Starting with M84 this is is also recorded for - webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - - - yusufo@chromium.org - src/base/metrics/OWNERS - - Recorded only for Android. Records on every metrics upload whether the - currently visible tab is a custom tab. The custom tab is launched by a - client app with customized UI. Some metrics like page load time will behave - differently for these tabs since it will be possible to warm up the browser - process and prepare resources for specific urls ahead of time via a service - connection. This histogram can be used to cluster these metric differently. - - As of M87, this histogram is logged on a log start, rather than log end to - tag more logs. - - - - - lizeb@chromium.org - - Recorded only on Android. Reports whether warmup() has been called when a - Custom Tabs Intent is received from an application, and if so, whether the - call could be matched with a session. Starting with M84 this is is also - recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. - - - - - lizeb@chromium.org - - Android: When a CustomTabActivity creates its Tab, whether we use a - prerendered WebContents, a spare renderer or create a new WebContents. - - - - - grt@chromium.org - sky@chromium.org - Errors when trying to load DataPack files. - - - - - Replaced by DataReductionProxy.LoFi.Accuracy. - - bengr@chromium.org - tbansal@chromium.org - - Counts the accuracy of estimated network quality when using Lo-Fi. Counters - are incremented when a main frame URL request is handled by Data Reduction - Proxy and session was in Auto Lo-Fi enabled field trial. - - - - - - Removed as of 8/2017, per server-directed preview decision. - - tbansal@chromium.org - - Counts the changes in the state of Lo-Fi request header (q=low) being added - to the Chrome proxy request header. Counters are incremented when a main - frame URL request is handled by Data Reduction Proxy and session was in Auto - Lo-Fi enabled field trial. - - - - - - Obsoleted April 2020. - - bengr@chromium.org - marq@chromium.org - tbansal@chromium.org - - Counts various events that trigger Chrome to block the fallback - configuration of the data reduction proxy. - - - - - - Obsoleted April 2020. - - bengr@chromium.org - marq@chromium.org - tbansal@chromium.org - - Counts various events that trigger Chrome to block the primary configuration - of the data reduction proxy. - - - - - bengr@chromium.org - tbansal@chromium.org - - Counts the response bytes that did not go through the data reduction proxy - as the result of a bypass event. - - - - - bengr@chromium.org - tbansal@chromium.org - - Counts the response bytes that went through the data reduction proxy and - were not bypassed. - - - - - - Removed as of 6/2014, replaced by DataReductionProxy.BypassTypeFallback. - - bengr@chromium.org - marq@chromium.org - - Counts various events that trigger Chrome to bypass the fallback - configuration of the data reduction proxy. - - - - - - Removed as of 6/2014, replaced by DataReductionProxy.BypassTypePrimary. - - bengr@chromium.org - marq@chromium.org - - Counts various events that trigger Chrome to bypass the primary - configuration of the data reduction proxy. - - - - - - Removed as of March 2020. - - bengr@chromium.org - - Positive net error code that caused the fallback data reduction proxy to be - bypassed and put on the proxy retry list. Called after a failure to connect - or resolve a host name. - - - - - - Removed as of March 2020. - - bengr@chromium.org - - Positive net error code that caused the primary data reduction proxy to be - bypassed and put on the proxy retry list. Called after a failure to connect - or resolve a host name. - - - - - - Obsoleted April 2020. - - bengr@chromium.org - marq@chromium.org - tbansal@chromium.org - - Counts various events that trigger Chrome to bypass the fallback - configuration of the data reduction proxy. - - - - - - Obsoleted April 2020. - - bengr@chromium.org - marq@chromium.org - tbansal@chromium.org - - Counts various events that trigger Chrome to bypass the primary - configuration of the data reduction proxy. - - - - - - Removed 2018/04. - - tbansal@chromium.org - bengr@chromium.org - - Records if the platform detected that a captive portal is present on the - current network. Recorded at the time of Chrome startup and on IP change - event. Recorded only for users that have data saver enabled. - - - - - - Removed in Feb. 2016 - - bengr@chromium.org - - Size of the response body. This is the actual number of bytes received, - which usually agrees with but is not necessarily the same as the size - specified by the Content-Length header. Only recorded if the request is sent - while a simulated Data Reduction Proxy configuration fetch is taking place. - - - - - - Removed in Feb. 2016 - - bengr@chromium.org - - The difference between the size specified in the X-Original-Content-Length - header and the size of the response body. Only recorded if the request is - sent while a simulated Data Reduction Proxy configuration fetch is taking - place. Only positive values are logged, so if X-Original-Content-Length is - not specified or if it equals or exceeds the content length, it is not - logged. - - - - - - Removed in Feb. 2016 - - bengr@chromium.org - - Size specified in the X-Original-Content-Length header. If this header is - not present in the response, the size of the response body is used. Only - recorded if the request is sent while a simulated Data Reduction Proxy - configuration fetch is taking place. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Total number of authentication required responses received from the Data - Reduction Proxy. - - An "Unexpired" value is recorded every time a new client config is - fetched and parsed successfully. An "Expired" value is recorded - every time Chrome receives an authentication failure from the data saver - proxy. - - - - - - Obsoleted March 2020. - - robertogden@chromium.org - tbansal@chromium.org - - On receiving an authentication failure from the data reduction proxy, - records whether the session key used in the request matches the current - session key. - - Recorded every time Chrome receives an authentication failure from the data - saver proxy. - - - - - - Obsoleted March 2020. - - robertogden@chromium.org - tbansal@chromium.org - - Time from when the request starts to the time when the auth failure is - received from the data saver proxy. - - Recorded every time an auth failure is received from the data saver proxy. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The time delta between connectStart and connectEnd of the client config - request. This is recorded only on successful requests when connectStart and - connectEnd were non-null. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The number of failed attempts when retrieving the configuration from the - Data Reduction Proxy API before a successful attempt took place. - - Recorded every time a new client config is fetched and parsed successfully. - If the device has a valid connection type but no Internet connectivity, this - count will keep increasing. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Time from when the Data Reduction Proxy configuration request starts until - it completes. - - Recorded every time a new client config is fetched and parsed successfully. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Count per HttpResponseCode when attempting to retrieve the Data Reduction - Proxy configuration from the Data Reduction Proxy API. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The time delta between requestStart and requestEnd of the client config - request. This is recorded only on successful requests. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Upper bound on the count of HTTP requests that did or did not go through the - data saver proxy. - - An HTTP request may not go through data saver proxy if the config was - unavailable, due to local bypass rules, or due to server side bypasses. If - data saver is turned on, this metric is recorded every time proxy is - resolved for an HTTP request. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Upper bound on the count of main frame requests that did or did not go - through the data saver proxy. - - A main frame request may not go through data saver proxy if the config was - unavailable, due to local bypass rules, or due to server side bypasses. If - data saver is turned on, this metric is recorded every time proxy is - resolved for an HTTP request. - - - - - - Removed 2018/04. - - tbansal@chromium.org - bengr@chromium.org - - Records whether the persisted client config for data saver proxies read from - the disk at the time of Chrome startup was expired or not. Recorded once at - the time of Chrome startup. - - - - - - Removed in October 2018 - - robertogden@chromium.org - - Records whether the client config client sent variation headers in the - config request. - - - - - rajendrant@chromium.org - tbansal@chromium.org - - Records the number of days since data reduction proxy was last enabled by - the user. Recorded only if the data reduction proxy was last enabled since - this metric was added to Chromium (M-56). Recorded at Chrome startup if data - reduction proxy is already enabled, and when the user enables the data - reduction proxy. - - - - - - Obsoleted in M-79. - - tbansal@chromium.org - bengr@chromium.org - - Records the number of days since the data reduction savings were cleared - because the system clock moved back by more than 1 day. Recorded at Chrome - startup if data reduction proxy is enabled, and if the data reduction proxy - savings were cleared in some previous Chrome session. - - - - - robertogden@chromium.org - bengr@chromium.org - - When the data savings are cleared because the user deletes their browsing - history, record how many buckets were deleted. See also - DataReductionProxy.SavingsCleared.Reason/User action - cleared browsing - history. - - - - - rajendrant@chromium.org - tbansal@chromium.org - - Samples of user interactions with the Data Saver settings menu across all - platforms (android, IOS, desktop extension). Data is collected whenever user - toggles the ON/OFF switch in the settings menu for reducing data usage. - - For desktop, Off-to-On/On-to-Off histogram count will increment when the - data saver extension is installed/uninstalled respectively as well. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - For each carrier, the total number of HTTP responses that have been checked - for tampering. This assumes the data reduction proxy injected fingerprints - have not been tampered with. Only the data reduction proxy responses with - 200 OK response code are checked. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - For each carrier, the total number of HTTPS responses that have been checked - for tampering. This assumes the data reduction proxy injected fingerprints - have not been tampered with. Only the data reduction proxy responses with - 200 OK response code are checked. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - For each carrier, the total number of HTTP responses that passed the tamper - detection. This assumes the data reduction proxy injected fingerprints have - not been tampered with. Only the data reduction proxy responses with 200 OK - response code are checked. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - For each carrier, the total number of HTTPs responses that passed the tamper - detection. This assumes the data reduction proxy injected fingerprints have - not been tampered with. Only the data reduction proxy responses with 200 OK - response code are checked. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - The total number of HTTP responses that some part (specified by suffix name) - have been tampered with. This assumes the data reduction proxy injected - fingerprints have not been tampered with. Only the data reduction proxy - responses with 200 OK response code are checked. - - - - - - Removed in June 2017 - - xingx@chromium.org - bolian@chromium.org - bengr@chromium.org - - The total number of HTTPS responses that some part (specified by suffix - name) have been tampered with. This assumes the data reduction proxy - injected fingerprints have not been tampered with. Only the data reduction - proxy responses with 200 OK response code are checked. - - - - - kundaji@chromium.org - - Time taken to load historical data usage from Level DB into memory. This UMA - is reported each time the method to load historical data usage is called, - which happens when user views data usage history. - - - - - - Obsoleted March 2020. - - tbansal@chromium.org - - Net error codes observed when invalid response headers were received from - data reduction proxy. - - - - - rajendrant@chromium.org - bengr@chromium.org - - Records the aggregate data use of services for the last week. Different - conditions are added as suffixes to this histogram. Recorded when Chrome is - started, so this does not include the current session. The aggregation - happens when requests complete. The current week calculation is based on - week starting from the Epoch day(Thursday, January 1, 1970), and every 7 - days is treated as a week. - - - - - rajendrant@chromium.org - bengr@chromium.org - - Records the aggregate data use for the last week. This is the downstream - data use of all user-initiated traffic. Recorded when Chrome is started, so - this does not include the current session. The aggregation happens when - requests complete. The current week calculation is based on week starting - from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated - as a week. - - - - - kundaji@chromium.org - Status of calling Open() on Data Reduction Proxy LevelDB. - - - - kundaji@chromium.org - Size of Data Reduction Proxy LevelDB measured at startup. - - - - - Removed as of 8/2017, per server-directed preview decision. - - bengr@chromium.org - tbansal@chromium.org - - Records the accuracy of estimated network quality when using Lo-Fi. Network - quality predicted at the time of navigation start is compared with the - network quality observed during the specified time interval following the - start of the navigation. This metric is recorded only when the session is in - Lo-Fi enabled field trial. - - - - - - Obsolete as of October 2017. - - bengr@chromium.org - megjablon@chromium.org - - Counts of Lo-Fi implicit opt out actions. If the user chooses to "Load - image" for k pages in a session, LoFi is disabled for the remainder of - that session. If Lo-Fi is disabled for j consecutive sessions, Lo-Fi is - disabled for that user until the next implicit opt out epoch, which may be - in a later session, or never. k and j default to 3 and are assigned via the - DataReductionProxyLoFi field trial. - - - - - - Removed as of October 2017 per transition to blacklist. - - bengr@chromium.org - megjablon@chromium.org - - Tracks Lo-Fi usage at the granularity of browser sessions. Counts for each - session if Lo-Fi was used or not. In the case where Lo-Fi was not used, - records if it was because the network quality was always good or because the - user had implicitly opted out. The session where a user permanently opts out - is counted in the Lo-Fi used bucket. - - - - - - Functionality removed in M77. - - bengr@chromium.org - tbansal@chromium.org - - Counts of pageloads that received or requested, but did not receive, various - Lo-Fi lite page transformations. Recorded when a lite page is requested or - received through Data compression proxy. - - - - - - Removed as of 9/2016, replaced by Previews.ContextMenuAction.LoFi. - - bengr@chromium.org - megjablon@chromium.org - - User interactions with the Lo-Fi snackbar and context menu option. These - include: - - Displays and clicks on the "Load images" snackbar. Displays and - clicks on the "Load image" and "Load images"context menu - options. Count of pages where the user has clicked "Load image" at - least once. - - - - - - Removed 2018/04. - - bengr@chromium.org - sclittle@chromium.org - - Counts the response bytes of responses that Chrome expected to come through - a data reduction proxy and have the data reduction proxy via header, but - where the data reduction proxy via header was missing. Note that this does - not include responses that were bypassed. - - - - - - Obsoleted March 2020. - - bengr@chromium.org - sclittle@chromium.org - - Counts the different HTTP response codes of responses that Chrome expected - to come through a data reduction proxy and have the data reduction proxy via - header, but where the data reduction proxy via header was missing. - - - - - - Obsoleted in March 2020. - - bengr@chromium.org - tbansal@chromium.org - - Counts the number of times various events occur when the data reduction - proxy is enabled and the IP address of the client changes. - - - - - - Obsoleted in April 2020 - - tbansal@chromium.org - - Records if the network properties of a network were found in the cache or - not. Recorded every time there is a change in the connection type. - - - - - - Removed in M79. - - ryansturm@chromium.org - - Counts the number of times that pageload metrics were queued to be attempted - or not queued based on the reporting fraction. Recorded once per pageload. - - - - - - Removed in M79. - - ryansturm@chromium.org - - Counts various actions related to crash detection in the pingback client. - This is recorded only when a renderer crash occurs on a Data Reduction Proxy - page load. - - - - - - Removed in M79. - - ryansturm@chromium.org - - Counts the number of times that a batched pingback request succeeded or - failed at being sent to the server. Recorded everytime a pingback request is - attempted. - - - - - - Obsoleted in March 2020. - - bengr@chromium.org - marq@chromium.org - - Counts various outcomes of requesting the data reduction proxy's probe URL. - - - - - - Obsoleted in March 2020. - - bengr@chromium.org - tbansal@chromium.org - - Reports the type of network error when the data reduction proxy probe fails - due to a network error. - - - - - - Removed as of 3/2015, replaced by DataReductionProxy.UIAction. - - bengr@chromium.org - marq@chromium.org - - Samples which method was used by the user to dismiss the proxy promo. This - is sampled when the promo leaves view, with the sampled value depending on - which of four possible controls the user used. - - - - - - Obsolete as of 10/2018. - - dougarnett@chromium.org - - Records the sending of accepted transform headers to the data reduction - proxy and also receiving transforms and policies from the data reduction - proxy. Recorded on a per page request basis and also on a per image resource - request basis for empty-image transforms. Headers for both types of requests - (pages and resources) are recorded here for convenience in viewing in a - single histogram. In general, the separate groups of request/receive buckets - for either page or resource types can be compared. - - - - - - Obsolete as of 10/2018. - - dougarnett@chromium.org - - Records the reason that a page request is not accepting proxy server - transforms. Recorded on a per page request basis. - - - - - sclittle@chromium.org - src/components/data_reduction_proxy/OWNERS - - Records the result of migrating the Data Reduction Proxy away from being - configured via a proxy preference, including cases when no migration action - was taken. - - - - - - Obsoleted March 2020. - - tbansal@chromium.org - bengr@chromium.org - - Records the scheme of the data reduction proxy server. Recorded for every - request that is fetched successfully through a data reduction proxy server. - - - - - - Removed in 5/2017, since the experiment to use default QUIC alternative - proxy was deprecated. - - tbansal@chromium.org - bengr@chromium.org - - Status of the availability of valid alternative data reduction proxy - servers. This metric is recorded only when data reduction proxy delegate is - queried for the value of the supported alternative proxy server. - - - - - - As of M66 this has been superceded by Net.AlternativeProxyFailed. - - tbansal@chromium.org - - Number of times an alternative QUIC proxy was marked as broken. - - - - - - Obsoleted March 2020. - - tbansal@chromium.org - - Records the result of the attempt to use a data reduction proxy that - supports QUIC. The metric is logged for every request for which the resolved - proxy is a data reduction HTTPS proxy. - - - - - rajendrant@chromium.org - tbansal@chromium.org - - Whether the save-data savings JSON retrieved from field trial was parsed as - a dictionary. Recorded on startup. - - - - - - Removed in 2/2016, since it didn't get recorded for many kinds of error - codes when it should have been recorded, and - Net.HttpRequestCompletionErrorCodes is a good enough replacement when - filtering for clients with the Data Reduction Proxy enabled. - - sclittle@chromium.org - bengr@chromium.org - - Reports the different network errors that requests that try to use the data - reduction proxy are completing with, including OK and ABORTED. - - - - - - Removed in 2/2016, since it didn't get recorded for many kinds of error - codes when it should have been recorded, and - Net.HttpRequestCompletionErrorCodes is a good enough replacement when - filtering for clients with the Data Reduction Proxy enabled. - - sclittle@chromium.org - bengr@chromium.org - - Reports the different network errors that main frame resource requests that - try to use the data reduction proxy are completing with, including OK and - ABORTED. - - - - - - Removed 2018/04. - - tbansal@chromium.org - bengr@chromium.org - - Content type of the resource determined by data reduction proxy. Used for - determining the data reduction proxy that should be used for fetching the - resource. Logged once per resource for only the resources that are eligible - for fetching by data reduction proxies. - - - - - - Obsoleted March 2020. - - sclittle@chromium.org - bengr@chromium.org - - Reports the state of the proxy server field in the response seen by the Data - Reduction Proxy bypass logic. - - - - - - Replaced by DataReductionProxy.SavingsCleared.Reason in M68. - - tbansal@chromium.org - bengr@chromium.org - - Records if the data reduction savings were cleared because the system clock - moved back by more than 1 day. Recorded at Chrome startup if the data - reduction proxy is enabled. - - - - - robertogden@chromium.org - bengr@chromium.org - - Records why the data reduction savings were cleared. See also - DataReductionProxy.DeleteBrowsingHistory.NumBuckets. - - - - - - Obsoleted in March 2020. - - bengr@chromium.org - - Time from when the Data Reduction Proxy secure proxy check starts until it - completes. - - - - - - Removed as of 3/2015, replaced by DataReductionProxy.UIAction. - - bengr@chromium.org - marq@chromium.org - - Samples of user interactions with the ON/OFF switch in the settings menu for - reducing data usage. Only the setting changes between entering the reducing - data usage setting menu and leaving the menu will be sampled. So if a user - enters the menu with OFF and leaves it with OFF, it is counted as one OFF to - OFF conversion regardless of how many times they toggle the ON/OFF switch. - - - - - bengr@chromium.org - tbansal@chromium.org - - Logs the data savings in MB of the data reduction proxy snackbar promo that - was shown. The snackbar promo shows the user the amount of data Chrome has - saved them using Data Saver. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the negative data savings percentage at Chrome startup for data - saver enabled users who have browsed a reasonable amount (at least 10MB - since data saver was enabled). - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the data savings percentage at Chrome startup for data saver enabled - users who have browsed a reasonable amount (at least 10MB since data saver - was enabled). Negative savings are not recorded. - - - - - rajendrant@chromium.org - tbansal@chromium.org - - Samples of the state of the data reduction proxy on Chrome startup. The - proxy will either be unavailable (the feature hasn't been rolled out to this - user yet), not enabled (the feature is available but the user doesn't have - it turned on), or enabled (the feature is enabled and turned on). - - - - - - Obsoleted March 2020. - - tbansal@chromium.org - bengr@chromium.org - - Count of the number of requests that were successfully fetched via data - reduction proxy. The bucket represents the index of the data reduction proxy - in the data reduction proxy list. - - - - - - Obsoleted March 2020. - - tbansal@chromium.org - bengr@chromium.org - - Count of the number of main frame requests that were successfully fetched - via data reduction proxy. The bucket represents the index of the data - reduction proxy in the data reduction proxy list. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the aggregate data use of services for the current week. Different - conditions are added as suffixes to this histogram. Recorded when Chrome is - started, so this does not include the current session. The aggregation - happens when requests complete. The current week calculation is based on - week starting from the Epoch day(Thursday, January 1, 1970), and every 7 - days is treated as a week. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the aggregate data use for the current week. This is the downstream - data use of all user-initiated traffic. Recorded when Chrome is started, so - this does not include the current session. The aggregation happens when - requests complete. The current week calculation is based on week starting - from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated - as a week. - - - - - - Removed 2018/04. - - tbansal@chromium.org - bengr@chromium.org - - Records the time duration between the data saver initialization and the - first HTTP request that is resolved through the data saver proxy. On IP - address changes, time duration between the IP address change event and the - next subsequent HTTP request that resolves through the data saver proxy is - recorded. - - - - - bengr@chromium.org - mcrouse@chromium.org - - Samples of user interactions with the Data Reduction Proxy promos, First Run - Experience, main menu footer, and settings menu. All samples are mutually - exclusive. These samples include: - - The user interactions with the First Run Experience. On Android when the - user sees the FRE card, the Data Reduction Proxy defaults to ON. The user - can disable the proxy via a switch on the card. The state of the proxy is - sampled when the First Run Experience is completed and only reported if the - Data Reduction Proxy card was shown. - - The user interactions with the second run promo. On Android, there are two - actions that dismiss this promo (enable or dismiss). This is sampled when - the promo leaves view. - - The user interactions with the Infobar promo. On Android, there are two - actions that dismiss the promo (enable, dismiss). This is sampled when the - promo leaves view. - - The user interactions with the Snackbar promo. The user can either ignore - the promo or click the action to the settings menu. From the settings menu, - the user may enable or disable the proxy. - - The user interactions with the main menu footer. The user can click the - footer to enter the settings menu. From the settings menu, the user may - enable or disable the proxy. - - Any other user interaction with the ON/OFF switch in the settings menu for - reducing data usage. Only the setting changes between entering the reducing - data usage setting menu and leaving the menu will be sampled regardless of - how many times they toggle the ON/OFF switch. Other samples that report - ON/OFF settings menu changes are not also reported here. - - The views of and user interactions with the site breakdown in the settings - menu. The site breakdown can be sorted by data saved descending or data used - descending, and expanded to view more sites. The Data Reduction statistics - can also be reset. - - - - - rajendrant@chromium.org - robertogden@chromium.org - src/components/data_reduction_proxy/OWNERS - - The total original content size displayed to the user. Computed over the - last 30 days. Recorded when the user views the data savings in the UI. - - - - - rajendrant@chromium.org - robertogden@chromium.org - src/components/data_reduction_proxy/OWNERS - - The difference between the total data savings as displayed to the user and - the sum of the data savings for all hosts in the data use breakdown. - Calculated as a percentage of `abs(summedSavingsTotal - - displayedSavingsTotal) / (summedSavingsTotal + displayedSavingsTotal)`. - Recorded when the user views the data savings in the UI. - - - - - - Removed March 2018. Percent no longer displayed. - - tbansal@chromium.org - - The percentage of data savings displayed to users. Computed over the last 30 - days. Recorded when the user views the data savings in the UI. - - - - - rajendrant@chromium.org - robertogden@chromium.org - src/components/data_reduction_proxy/OWNERS - - The total data saved displayed to the user. Computed over the last 30 days. - Recorded when the user views the data savings in the UI. - - - - - rajendrant@chromium.org - robertogden@chromium.org - src/components/data_reduction_proxy/OWNERS - - The difference between the total data usage as displayed to the user and the - sum of the data usage for all hosts in the data use breakdown. Calculated as - a percentage of `abs(summedUsageTotal - displayedUsageTotal) / - (summedUsageTotal + displayedUsageTotal)`. Recorded when the user views the - data savings in the UI. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - Records the result of an attempt to fetch the warmup URL. - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Records the total number of warmup URL (i.e., the probe URL) fetch attempts - that were made before the warmup URL was successfully fetched. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Number of times the data reduction proxy warm up URL was fetched. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - Whether the warm up URL was fetched succesfully. - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Whether the response headers of the warm up URL had Chrome Proxy via header. - Recorded only when non-null response headers were available when the fetch - of warm up URL concludes. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - HTTP response code of the warm up URL. Set to 1 when HTTP response headers - were unavailable. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Net error codes observed when the fetch of the warm up URL concludes. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Proxy scheme of the proxy server via which the warm up URL was fetched. - Recorded only when non-null response headers were available when the fetch - of warm up URL concludes. - - - - - - Obsoleted in March 2020. - - tbansal@chromium.org - - Whether the warmup (or probe) URL was successfully fetched over a data saver - proxy. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The number of invalid matching rules fetched from the platform external data - use observer. A sample is recorded everytime fetch done callback is called. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The number of valid matching rules fetched from the platform external data - use observer. A sample is recorded everytime fetch done callback is called. - - - - - - Removed 2018/07. - - rajendrant@chromium.org - bengr@chromium.org - - Records the sequence number of the page load within a data usage tracking - session. Logged for each navigation in the tracking session. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The time taken in milliseconds to fetch the matching rules for the first - time from the platform external data use observer. This measures the - duration from the start time of Chromium to the time the rules are returned - asynchronously. A sample is recorded when the first fetch done callback is - called. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The time taken in milliseconds to submit the data use reports to the - platform external data use observer. This measures the duration from the - time of report submission to the time report submission done asynchronous - callback is received. A sample is recorded everytime report submission done - callback is received. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The time taken in milliseconds for a regular expression to parse an URL. A - sample is recorded evertime regular expression parsing is done for an URL. - - - - - - Removed 2018/07. - - bengr@chromium.org - tbansal@chromium.org - - Count of bytes in the data use reports that were intended to be submitted to - the platform external data use observer. - - - - - - Removed 2018/07. - - bengr@chromium.org - tbansal@chromium.org - Result of data usage report submission. - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The duration from the start time of a tab entry's latest data usage tracking - session, till when the entry is expired and removed from the tab model. This - is for tab entries that are still actively tracking data usage for a - Chromium tab. - - Tab model maintains the tab entries, each pertaining to tracking sessions of - a single Chromium tab. These entries are considered expired after some - duration and can be removed from the tab model after that. The sample is - taken when an expired tab entry still tracking data usage is removed from - the tab model. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The duration from the end time of a tab entry's latest data usage tracking - session, till when the entry is expired and removed from the tab model. This - is for tab entries that are not actively tracking data usage for a Chromium - tab. - - Tab model maintains the tab entries, each pertaining to tracking sessions of - a single Chromium tab. These entries are considered expired after some - duration and can be removed from the tab model after that. The sample is - taken when an expired inactive tab entry is removed from the tab model. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The duration from the end time of a data usage tracking session, till when - the tracking session is removed from the tab model. This is for old tracking - sessions that are not actively tracking data usage. - - Tab model maintains a limited number of tracking sessions per Chromium tab. - When this limit is reached oldest inactive tracking sessions are removed. - The sample is taken when an old inactive tracking session of a tab is - removed from the tab model. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The lifetime of a data usage tracking session of a Chromium tab, maintained - by the tab model. This is the duration between the time tracking started due - to an entry event and ended with an exit event. The sample is taken when the - data usage tracking session ends. - - - - - - Removed 2018/07. - - bengr@chromium.org - rajendrant@chromium.org - - The duration from the end time (start time, if still active) of a tab - entry's latest data usage tracking session, till when the entry is removed - from the tab model. This is for tab entries that are not expired yet, and - removed from the tab model. - - Tab model maintains a limited number of entries, each pertaining to tracking - sessions of a single Chromium tab. When this limit is reached even after - removing expired tab entries, then oldest unexpired tab entries are removed. - The sample is taken when an unexpired tab entry is removed from the tab - model. - - - - - - Removed 2018/07. - - rajendrant@chromium.org - bengr@chromium.org - - The reason for ending the data usage tracking session. Logged when the - tracking session ends. - - - - - - Removed 2018/07. - - rajendrant@chromium.org - bengr@chromium.org - - The reason for starting the data usage tracking session. Logged when the - tracking session was started. - - - - - - Removed 2018/07. - - bengr@chromium.org - megjablon@chromium.org - - Samples of user interactions with the Data Use snackbar and dialog. These - samples include: - - Displays of the snackbar that indicates the start of data use tracking and - clicks on its "More" button. Displays of snackbar that indicates - the end of data use tracking and clicks on its "More" button. - Displays of the dialog that indicates the end of data use tracking and the - user interactions with it, which include: clicking "Continue", - clicking "Cancel", clicking "Learn more", and opting out - of seeing the dialog. If the user opts out of seeing the dialog, they will - see the snackbar that indicates the end of data use tracking from then on. - - - - - - Replaced by KB version in October, 2017. - - rajendrant@chromium.org - bengr@chromium.org - - The total background data use of Chrome's services broken down by service - name. It is logged only in Android when the URLRequest of a service - completes. - - - - - - Replaced by DataUse.AllServicesKB.* version in June, 2018. - - rajendrant@chromium.org - bengr@chromium.org - - The total background data use of Chrome's services broken down by service - name. It is logged only in Android when the URLRequest of a service - completes. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - The request and response size of the messages exchanged by all the services. - Whenever a URLRequest of a service is completed, the number of exchanged - bytes is logged in this histogram. The buckets in this histogram are - services recorded by the corresponding network traffic annotation tag - hashes, so it makes it possible to compare the use of different services in - different conditions. Different conditions are added as suffixes to this - histogram. If the OS is not Android all the requests are considered - foreground. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the data use of Chrome user traffic by the foregound vs. background - state of the app and tab. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - The time since Chrome is in background when background data use happens. - Recorded for each byte of background data use. The source of traffic whether - from user browsing or chrome services is added as suffix to this histogram. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - The time since Chrome is in background when first background data use - happens. Recorded when first background downstream data use after Chrome is - in background. The source of traffic whether from user browsing or chrome - services is added as suffix to this histogram. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Count of total bytes received by the Chrome on the network. With network - servicification this is recorded when requests complete. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Count of total bytes sent by the Chrome on the network. With network - servicification this is recorded when requests complete. - - - - - - Removed 2018/05. Bytes are logged to DataUse.ContentType.ServicesKB. - - rajendrant@chromium.org - bengr@chromium.org - - Data use of Chrome services traffic by different content types. Recorded - when network bytes are received by Chrome. - - - - - - Removed since not needed. - - rajendrant@chromium.org - bengr@chromium.org - - Data use of Chrome services traffic by different content types. Recorded in - KB when network bytes are received by Chrome. - - - - - - Removed 2017/04. Bytes are logged to DataUse.ContentType.UserTrafficKB. - - rajendrant@chromium.org - bengr@chromium.org - - Data use of user traffic by different content types. Recorded when network - bytes are received by Chrome. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Data use of user traffic by different content types. Recorded in KB when - network bytes are received by Chrome. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the downstream network data use of favicon requests. Logged when the - request is completed or redirected. Zero bytes are recorded when the request - is served from cache. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the downstream network data use of favicon requests with non 200 - response code. Logged when the request is completed or redirected. - - - - - - Removed 10/2017. - - bengr@chromium.org - - The request and response size of the messages exchanged by a service. It is - logged when the URLRequest of a service is completed. The service name is - added as a suffix to this histogram name. - - - - - - Replaced by DataUse.AllServicesKB.* version in June, 2018. - - bengr@chromium.org - - The request and response size of the messages exchanged by all the services. - Whenever a URLRequest of a service is completed, the number of exchanged - bytes is logged in this histogram. The buckets in this histogram are - services, so it makes it possible to compare the use of different services - in different conditions. Different conditions are added as suffixes to this - histogram. If the OS is not Android all the requests are considered - foreground. - - - - - - Removed 2018/05. Bytes are logged to DataUse.PageTransition.UserTrafficKB. - - rajendrant@chromium.org - bengr@chromium.org - - Data use of user traffic by different core page transition types. Recorded - when the URL request finishes. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Data use of user traffic by different core page transition types. Recorded - in KB when the URL request finishes. - - - - - - Removed 10/2017. - - bengr@chromium.org - - Number of downloaded bytes of different data types in Sync service for - received updates. It is updated when an update message is received from sync - server. - - - - - - Removed 10/2017. - - bengr@chromium.org - - Number of downloaded entities of different data types in Sync service for - received updates. It is updated when an update message is received from sync - server. - - - - - - Removed 10/2017. - - bengr@chromium.org - - Number of downloaded bytes of ProgressMarker of different data types in Sync - service for received updates. It is updated when an update message is - received from sync server. - - - - - - Removed 10/2017. - - bengr@chromium.org - - Number of uploaded bytes of different data types in Sync service for sent - commits. Updated when a commit message is sent to sync server. - - - - - - Removed 10/2017. - - bengr@chromium.org - - Number of uploaded entities of different data types in Sync service for sent - commits. Updated when a commit message is sent to sync server. - - - - - - Removed in M74 and replaced by DataUse.AllServicesKB. - - bengr@chromium.org - - The total data use of Chrome's services. There is no ResourceRequestInfo - attached to these requests. If the OS is not Android all the requests are - considered foreground. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - The total amount of data use of Chrome for user traffic. This traffic has - content::ResourceRequestInfo attached to its request. If the OS is not - Android all the requests are considered foreground. - - - - - satorux@chromium.org - Whether an asynchronous D-Bus method call is successful. - - - - satorux@chromium.org - The time spent for an asynchronous D-Bus method call. - - - - satorux@chromium.org - - Whether a call to a D-Bus exported method is handled successfully. - - - - - satorux@chromium.org - - The time spent for handling a call to a D-Bus exported method. - - - - - satorux@chromium.org - The time spent for handling a D-Bus signal. - - - - satorux@chromium.org - The time spent for sending a D-Bus signal. - - - - satorux@chromium.org - Whether a synchronous D-Bus method call is successful. - - - - satorux@chromium.org - The time spent for a synchronous D-Bus method call. - - - - pmonette@chromium.org - grt@chromium.org - - The HRESULT from ActivateApplication when opening the Win10+ settings page - fails. - - - - - - Removed 2015/11. Renamed to DefaultBrowser.SetDefaultAsyncDuration. - - pmonette@chromium.org - - How long it took to set Chrome as the default browser asynchronously in - Windows 10+. The duration is recorded only on Success, Failure, Abandoned - and Retry result codes. - - - - - - Removed 2015/11. Renamed to DefaultBrowser.SetDefaultResult. - - pmonette@chromium.org - - The count of how many times users were successfully able to set Chrome as - the default browser asynchronously in Windows 10+. - - - - - pmonette@chromium.org - - Possible user interactions with the default browser info bar. - - - - - gab@chromium.org - - Results of interaction with set-as-default dialog in Win8+ first run flow. - - - - - - Removed 2016/03. The async set-as-default experiments are finished. - - pmonette@chromium.org - - How long it took to set Chrome as the default browser asynchronously in - Windows 10+. The duration is recorded only on Success, Failure, Abandoned, - Retry and NoErrorsNotDefault result codes. - - - - - - Removed 2016/03. - - pmonette@chromium.org - - The outcome of an attempt to set Chrome as the user's default browser. - - - - - pmonette@chromium.org - - The outcome of an attempt to set Chrome as the user's default browser. - - - - - pmonette@chromium.org - - The reason why the default browser settings interaction concluded on Windows - 10. - - - - - pmonette@chromium.org - - The registry keys for the default browser protocols (http/https) are - monitored to know when the user finished interacting with the system - settings. This is how long it took for the last registry watcher to get - signaled. - - - - - - - gab@chromium.org - pmonette@chromium.org - - Whether Chrome was the default browser when it started up. - - Only logged correctly on Windows, Mac, and Linux. Logged incorrectly on - other platforms. - - For ChromeOS, no histogram is necessary because Chrome is always the default - browser. - - For Android, see Mobile.DefaultBrowser.State. - - For iOS, in the future Chrome will be allowed to be the default browser. How - that will be logged is to be decided at the time of writing this - description. - - - - - pmonette@chromium.org - - When changing the default browser on Windows 10, records whether the browser - chooser is successfully invoked when opening the settings page. This - histogram is only recorded when the Win10AcceleratedDefaultBrowserFlow - experiment is enabled. - - - - - - Removed 2015/11. The same information is available as the value Failure in - DefaultBrowser.SetDefaultResult. - - gab@chromium.org - - In the make-default infobar, the user explicitly declined to set Chrome as - default. Or, on OSes requiring the SetAsDefaultUI, the user explicitly chose - another browser as default from the interactive UI. TODO(gab): Split the - interactive signal into a separate histogram. - - - - - - Removed 2015/11. Renamed to DefaultBrowser.InfoBar.UserInteraction. - - gab@chromium.org - - The user ignored the make-default infobar (it was eventually dismissed along - with its associated web content without the user interacting with it). - - - - - - Removed 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There is - no longer a distinction between interactive or not. - - gab@chromium.org - - In the make-default infobar, the user clicked a button making Chrome the - default. - - - - - - Removed 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There is - no longer a distinction between interactive or not. - - gab@chromium.org - - Same as SetAsDefault, but in Win8+ (resulting in interactive UI instead of - automatic takeover). Successes == these reports minus reports for - DefaultBrowserWarning.SetAsDefaultUIFailed and some - DefaultBrowserWarning.DontSetAsDefault. TODO(gab): Improve reporting here. - - - - - - Removed 2015/11. The same information is available as the value Failure in - DefaultBrowser.SetDefaultResult. - - gab@chromium.org - - The user dismissed the interactive SetAsDefaultUI without making an explicit - choice (or the UI failed to come up for another reason). - - - - - - Removed 2016/03. - - pmonette@chromium.org - - The outcome of an attempt to set Chrome as the user's default client for a - protocol. - - - - - pmonette@chromium.org - - The outcome of an attempt to set Chrome as the user's default client for a - protocol. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The actual delay added to main frame navigations by DelayNavigationThrottle. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The absolute delta between the specified and actual delays added to main - frame navigations by DelayNavigationThrottle. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The specified delay added to main frame navigations by - DelayNavigationThrottle. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - The currently active app or window. Sampled during demo sessions and - reported while the user remains active. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Records apps that have been launched by a user using the device during Demo - mode. The sample is recorded when each app is launched. For any given app - id, the metric is recorded only once per Demo Session. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - The source of app launches in demo mode, either the shelf, the app list, or - the highlights app. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - The duration the user spent interacting with the demo session, measured from - the first user activity to the last user activity. This metric rounds the - duration to the nearest second and uses exponential bucketing capped at 1 - hour. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Tracks whether the idle logout warning was canceled or proceeded to logout. - Note: the count of "shown" includes both cases, so the count of - "shown and proceeded" is equal to "shown" minus - "canceled". - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Tracks the reason for removal of pre-install demo resources. To support - offline demo mode, factory Chrome OS devices will have a set of offline - enabled demo mode apps pre-installed. These resources are removed once they - are not needed anymore. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Tracks the result of requests to remove pre-installed demo resources. To - support offline demo mode, factory Chrome OS devices will have a set of - offline enabled demo mode apps pre-installed. These resources are removed - once they are not needed anymore. This will record only requests that - attempted deleting pre-installed resources from disk. Requests that fail - early will be ignored. For example, a request will fail early if the device - is in demo mode, or the resources have already been removed. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - A demo session starts when a user signs in using the policy-configured - public account. It stops when the user signs out, either manually or after - an idle timeout. Session length is the duration between the start and stop - events. It is recorded during signing out and reported on the next chrome - run. This metric tracks the recorded session length rounded down to the - nearest minute and is capped at 2 hours. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - This records the time taken to download the demo mode resources when demo - mode is setup for the first time. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - This records the time taken to enterprise-enroll the device when demo mode - is setup for the first time. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - When demo mode is setup for the first time, it must download the demo mode - resources and enterprise-enroll the device. This records the time taken for - these two steps to complete. (See DemoMode.Setup.DownloadDuration and - DemoMode.Setup.EnrollDuration) - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Records the number of times an operator has encountered an error during the - loading screen and been required to retry setup. This is only recorded after - setup completes successfully. - - - - - drcrash@chromium.org - cros-demo-mode-eng@google.com - - Records how many unique apps have been launched by a user using the device - during Demo mode. The sample is recorded when the DemoMode session closes. - - - - - melandory@chromium.org - - DeprecatedInvlalidatorRegistrar is crashing on the browser shut down. The - reason for the crash is that not all invalidation handlers de-registister - themselves. Histogram records the type of the handler which hasn't - unregistered itself. Analyzing the histogram will allow us to understand, - which handlers are causing the crash. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - The dimissal reason of the desktop to iOS promotion entry point. - DismissalReason will be prefixed by the entry point promotion name that the - user interacted with. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - The type of the desktop to iOS promotion that was shown to the user. This - will be logged every time the user sees the desktop to iOS promotion. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - [IOS] For users who sign-in on Chrome for iOS, log the type of the desktop - iOS promotions that was shown to the user. Only recorded if the user has - seen at least one desktop iOS promotion in the last 7 days and is signing - into chrome on iOS. The last promotion entry point that sent an SMS (if any) - is logged as DesktopIOSPromotion.SMSSent.IOSSigninReason; all other - promotions that the user has seen are logged as - DesktopIOSPromotion.NoSMS.IOSSigninReason. - - - - - - Removed 11/2018 in issue 894963. - - justincohen@chromium.org - - Whether getting the OAuth token was successful for a desktop to iOS - promotion query. - - - - - - Removed 11/2018 in issue 894963. - - justincohen@chromium.org - - HTTP Response code returned by the server when trying to fetch the OAuth - token for a desktop ios promotion query. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - Whether the SMS service api called from the desktop to iOS promotion - returned a phone number or failed. This phone number is presented to the - user so they know that Chrome will send the SMS to this number. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - Whether the SMS service api initiated SMS sending successfully from the - desktop to iOS promotion. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - [IOS] The difference between the client time of triggering the SMS action on - a specific entry point promotion on desktop and client time of signing in - Chrome iOS app. This will only be logged if at least one promotion was shown - to the user on the last 7 days and if at least one SMS was sent. If multiple - SMSs were sent (at any time), it uses the time from the most recently sent - one. If the is negative due to bad clock on one of the clients it will be - logged as 0. SMSToSigninTime will be prefixed by the entry point promotion - name that was responsible for the SMS sending. - - - - - - Removed 11/2018 in issue 894963. - - mrefaat@chromium.org - - [IOS] For users who sign-in on Chrome for iOS, log which variation of the - desktop iOS promotions was shown to the user. The variation number is a - unique identifier that is set for each group on the DesktopIOSPromotion - study, and will be only recorded if the user has seen at least one desktop - iOS promotion in the last 7 days and is signing into Chrome on iOS. The last - variation that sent an SMS (if any) is logged as - DesktopIOSPromotion.SMSSent.VariationSigninReason. If no SMS was sent, then - the last variation the user has seen is logged as - DesktopIOSPromotion.NoSMS.VariationSigninReason. - - - - - alph@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - Specified DevTools action has been taken. - - - - yangguo@chromium.org - rayankans@chromium.org - bmeurer@chromium.org - - The result of clearing all stored events for a Background Service feature. - This is called if a developer clicks on a delete button in a Background - Service DevTools panel. - - - - - rayankans@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - - The result of loading all stored events for a Background Service feature. - This is called when the a Bakground Service DevTools panel is opened. - - - - - rayankans@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - - The result of logging a Background Service event. An event is logged if - `Recording` mode is on and a relevant Background Service event is taking - place. - - - - - yangguo@chromium.org - bmeurer@chromium.org - rayankans@chromium.org - - Records the Background Service for which `Recording` mode was enabled. This - is called if the developer toggles the record button in the relevant - Bakground Service DevTools panel. - - - - - yangguo@chromium.org - mathias@chromium.org - alexrudenko@chromium.org - - Records which color contrast threshold was fixed by the user in the Color - Picker. - - - - - changhaohan@chromium.org - yangguo@chromium.org - mathias@chromium.org - - Records state changes for DevTools computed style grouping toggled from the - Computed pane. - - - - - - Removed 08/2020 because the set of settings has changed. Superseded by - DevTools.CSSGridSettings2. - - yangguo@chromium.org - brgoddar@microsoft.com - leo.lee@microsoft.com - - DevTools settings for CSS grid recorded on launch of the DevTools. - - - - - yangguo@chromium.org - brgoddar@microsoft.com - leo.lee@microsoft.com - - DevTools settings for CSS grid recorded on launch of the DevTools. - - - - - yangguo@chromium.org - soxia@microsoft.com - leo.lee@microsoft.com - - Records the usage of dual screen device emulation: a dual screen or fold - device is selected for emulation; the span button is hit; or the platform - support of dual screen is utilized. - - - - - yangguo@chromium.org - brgoddar@microsoft.com - shanejc@microsoft.com - - Fired when a devtools experiment is disabled from the experiments tab. - - - - - yangguo@chromium.org - brgoddar@microsoft.com - shanejc@microsoft.com - - Fired when a devtools experiment is enabled from the experiments tab. - - - - - yangguo@chromium.org - brgoddar@microsoft.com - shanejc@microsoft.com - - Fires for each experiment that is enabled at the time of Devtools Launch. - - - - - changhaohan@chromium.org - yangguo@chromium.org - mathias@chromium.org - - Records which UI element is being used to open Grid overlays. - - - - - - Removed in July 2020, M86. This histogram was fired multiple times per - setting change and is unusable. Replaced with DevTools.CSSGridSettings. - - yangguo@chromium.org - brgoddar@microsoft.com - leo.lee@microsoft.com - - Recorded when a DevTools CSS Grid overlay display setting is changed. - Actually fires once for each overlay target active when the setting is - changed. - - - - - yangguo@chromium.org - patrick.brosset@microsoft.com - leo.lee@microsoft.com - - Number of simultaneous persistent CSS grid overlays in DevTools, recorded - after each change. - - - - - alph@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - - Time to load Developer Tools when user clicks Inspect Element in the context - menu. - - - - - yangguo@chromium.org - jegarc@microsoft.com - - Records which type of issue is expanded in the issues panel. - - - - - yangguo@chromium.org - bmeurer@chromium.org - - Records which UI element is being used to open the Issues Panel. - - - - - yangguo@chromium.org - jegarc@microsoft.com - - Records which resource from what issue category is opened in the issue - panel. - - - - - yangguo@chromium.org - jalyn@microsoft.com - leo.lee@microsoft.com - - Recorded when the user changes which keyboard shortcut presets they are - using in the DevTools. - - - - - yangguo@chromium.org - jalyn@microsoft.com - leo.lee@microsoft.com - - Recorded when a DevTools keyboard shortcut has been processed and - successfully executed its action. - - - - - - - yangguo@chromium.org - bmeurer@chromium.org - - Measures the time until a given tool is interactive during a cold start of - the DevTools. - - - - - yangguo@chromium.org - joselea@microsoft.com - shanejc@microsoft.com - Specified DevTools panel was closed. - - - - alph@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - Specified DevTools panel was shown. - - - - alph@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - Specified DevTools setting was changed. - - - - changhaohan@chromium.org - yangguo@chromium.org - bmeurer@chromium.org - Specified DevTools sidebar pane was shown. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the DiskSpace recovery step that runs - on recovery startups. The recovery step attempts to guarantee the DiskSpace - test, which checks that the disk space in the volume where the user data - directory normally lives is not dangerously low, would pass on the next - startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the JSONBookmarks recovery step that - runs on recovery startups. The recovery step attempts to guarantee the - JSONBookmarks test, which makes sure that the JSON-encoded Bookmarks file is - properly formed, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the JSONLocalState recovery step that - runs on recovery startups. The recovery step attempts to guarantee the - JSONLocalState test, which makes sure that the JSON-encoded Local State file - is properly formed, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the JSONPreferences recovery step - that runs on recovery startups. The recovery step attempts to guarantee the - JSONPreferences test, which makes sure that the JSON-encoded Preferences - file is properly formed, would pass on the next startup. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the PathDictionaries recovery step - that runs on recovery startups. The recovery step attempts to guarantee the - PathDictionaries test, which makes sure that the path to the Dictionaries - directory exists and has the right permissions, would pass on the next - startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the PathLocalState recovery step that - runs on recovery startups. The recovery step attempts to guarantee the - PathLocalState test, which makes sure that the path to the Local State file - exists and has the right permissions, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the PathResources recovery step that - runs on recovery startups. The recovery step attempts to guarantee the - PathResources test, which makes sure that the path to the Resources - directory exists and has the right permissions, would pass on the next - startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the PathUserData recovery step that - runs on recovery startups. The recovery step attempts to guarantee the - PathUserData test, which makes sure that the path to the User Data directory - exists and has the right permissions, would pass on the next startup. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityAppCache recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityAppCache test, which checks the integrity of the App - Cache database, would pass on the next startup. - - - - - - Removed as of Jun 2014: we no longer have an archived database. - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityArchivedHistory - recovery step that runs on recovery startups. The recovery step attempts to - guarantee the SQLiteIntegrityArchivedHistory test, which checks the - integrity of the Archived History database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityCookie recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityCookie test, which checks the integrity of the Cookie - database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker - recovery step that runs on recovery startups. The recovery step attempts to - guarantee the SQLiteIntegrityDatabaseTracker test, which checks the - integrity of the Database Tracker database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityFavicons recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityFavicons test, which checks the integrity of the Favicons - database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityHistory recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityHistory test, which checks the integrity of the History - database, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityNSSCert recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityNSSCert test, which checks the integrity of the NSS - Certificate database, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityNSSKey recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityNSSKey test, which checks the integrity of the NSS Key - database, would pass on the next startup. - - - - - - Removed 05/2016 in Issue 617226; has not been valid for many years. - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityThumbnails - recovery step that runs on recovery startups. The recovery step attempts to - guarantee the SQLiteIntegrityThumbnails test, which checks the integrity of - the Thumbnails database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityTopSites recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityTopSites test, which checks the integrity of the TopSites - database, would pass on the next startup. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityWebData recovery - step that runs on recovery startups. The recovery step attempts to guarantee - the SQLiteIntegrityWebData test, which checks the integrity of the Web Data - database, would pass on the next startup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Count of the number of times diagnostics recovery is invoked or not, and how - it was invoked. A sample is added to this histogram once for each startup of - Chrome. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the DiskSpace test - that runs on recovery startups. The DiskSpace test checks that the disk - space in the volume where the user data directory normally lives is not - dangerously low. - - - - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the JSONBookmarks - test that runs on recovery startups. The JSONBookmarks test checks to make - sure that the JSON encoded bookmarks file is properly formed. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the JSONLocalState - test that runs on recovery startups. The JSONLocalState test checks to make - sure that the JSON encoded Local State file is properly formed. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the JSONPreferences - test that runs on recovery startups. The JSONPreferences test checks to make - sure that the Preferences file is properly formed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the PathDictionaries - test that runs on recovery startups. The PathDictionaries test checks makes - sure that the path to the Dictionaries folder exists and has the right - permissions. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the PathLocalState - test that runs on recovery startups. The PathLocalState test checks makes - sure that the path to the Local State folder exists and has the right - permissions. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the PathResources - test that runs on recovery startups. The PathResources test checks makes - sure that the path to the Resources folder exists and has the right - permissions. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of diagnostics for the PathUserData test - that runs on recovery startups. The PathUserData test checks makes sure that - the path to the User Data folder exists and has the right permissions. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityAppCache test that - runs on recovery startups. The test checks the integrity of the App Cache - database. - - - - - - Removed as of Jun 2014: we no longer have an archived database. - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityArchivedHistory - test that runs on recovery startups. The test checks the integrity of the - Archived History database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityCookie test that - runs on recovery startups. The test checks the integrity of the Cookie - database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker - test that runs on recovery startups. The test checks the integrity of the - Database Tracker database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityFavicons test that - runs on recovery startups. The test checks the integrity of the Favicons - database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityHistory test that - runs on recovery startups. The test checks the integrity of the History - database. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityNSSCert test that - runs on recovery startups. The test checks the integrity of the NSS - Certificate database. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Shows the success and failure rates of the SQLiteIntegrityNSSKey test that - runs on recovery startups. The test checks the integrity of the NSS Key - database. - - - - - - Removed 05/2016 in Issue 617226; has not been valid for many years. - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityThumbnails test - that runs on recovery startups. The test checks the integrity of the - Thumbnails database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityTopSites test that - runs on recovery startups. The test checks the integrity of the TopSites - database. - - - - - shess@chromium.org - - Shows the success and failure rates of the SQLiteIntegrityWebData test that - runs on recovery startups. The test checks the integrity of the Web Data - database. - - - - - Please list the metric's owners. Add more owner tags as needed. - - TBD - Not run automatically yet, so this is just a placeholder for future - metrics collection. Any samples collected here represent users running - diagnostics manually. - - - - - shess@chromium.org - - Histogram comparing the various types of diagnostic test failures when - diagnostic tests are run. Note that some types of test failures cause the - rest of the tests to be skipped. - - - - - pdyson@chromium.org - - Counts the number times dialog boxes are created using a particular parent - class. - - - - - pdyson@chromium.org - - Counts the number times various types of dialog boxes are created. - - - - - - Removed, use Dialog.DialogDelegate.Create. - - pdyson@chromium.org - - Counts the number times dialog boxes are created using DialogDelegate. - - - - - pdyson@chromium.org - - How long dialog boxes are open, for dialog boxes created using the parent - class DialogDelegate. This will include bubbles that use - BubbleDialogDelegateView as a parent class, and dialogs that use - DialogDelegateView as a parent class. This is logged on delegate - destruction. - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - - Reports size of font cache file. This is reported every time we rebuild font - cache. - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - layout-dev@chromium.org - - Reports the total number of fonts that will be ignored while building static - font cache due to size limitation. During cache building phase if our logic - suggests that we need to put more than 70% of font file contents into cache - file then we don't cache that particular font file. These ignored font files - are directly picked up from system fonts folder during Direct Write cache - building process. Our end goal is to minimize costly open and close - operations on font files in system folder. - - - - - drott@chromium.org - etienneb@chromium.org - - The number of iterations that was required to initialize Direct Write. This - metric is taken by the browser process at startup. The value -1 is reported - when the initialization failed. The fallback path using GDI is used instead - of DWrite. - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - - Reports the total number of fonts that will be ignored while loading a - custom font collection. With current criteria fonts that are not in - system-font location will be ignored. - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - - Reports the total number of fonts to be loaded through a custom font - collection. This actually reports total font entries from registry excluding - font entries that point to non-system location. - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - - Measures the total time spent in loading a custom font collection in - non-cache-file mode. We load system fonts as a custom font collection to - avoid any interaction with windows font cache service from sandboxed - renderer process. Please note that windows font cache services is different - from our cache file approach (later referred here as cache-file mode). - - - - - - Removed 04/2016, as the code path containing this metric was deprecated in - favor of DWriteFontProxyImpl. - - drott@chromium.org - - Measures the total time spent in loading a custom font collection in - cache-file mode. We load system fonts as a custom font collection to avoid - any interaction with windows font cache service from sandboxed renderer - process. Please note that windows font cache services is different from our - cache file approach (later referred here as cache-file mode) - - - - - drott@chromium.org - layout-dev@chromium.org - Records the error returned from CreateFontFace. - - - - drott@chromium.org - layout-dev@chromium.org - - When scanning fonts for meta data as part of local matching, record the - ratio of empty per-family results to all per-family results as percentage. - Recorded in DWriteFontTableBuilder at the time of finishing scanning the - font files for their name meta information. A value of 100% means, all - per-family scan tasks came back empty. A value of 0% means, all per-family - tasks yielded at least one font file. Used for diagnosing - https://crbug.com/1009402. - - - - - drott@chromium.org - layout-dev@chromium.org - Records how many font families are in the fallback cache. - - - - drott@chromium.org - layout-dev@chromium.org - - Measures the effectiveness of the font fallback proxy. This tracks if we - were able to find a suitable font to render the character, and whether an - IPC was necessary. - - - - - drott@chromium.org - - The number of font families as seen by the font proxy in the renderer. - - - - - drott@chromium.org - layout-dev@chromium.org - - Number of font families on the system as retrieved from DWrite API (usually - less than to number of font files reported in - DirectWrite.Fonts.Proxy.NumFontFiles as a family can contain multiple font - files). Recorded in DWriteFontTableBuilder at the time of starting scanning - the font files for their name meta information. Used for diagnosing - https://crbug.com/1009402. - - - - - drott@chromium.org - layout-dev@chromium.org - - The errors encountered by the DirectWrite font proxy while loading fonts. - - - - - drott@chromium.org - layout-dev@chromium.org - Records the error returned from GetSystemFontCollection. - - - - drott@chromium.org - layout-dev@chromium.org - - Indexing speed in font files per second while building the local font unique - name lookup table. Recorded after building the lookup table in - DWriteFontLookupTableBuilder. - - - - - drott@chromium.org - layout-dev@chromium.org - - The number of last resort fallback fonts found on the system as seen by the - browser. - - - - - drott@chromium.org - layout-dev@chromium.org - - The number of font files found for a last resort fallback font. - - - - - drott@chromium.org - layout-dev@chromium.org - - The codepath that was used to load a font family. This is logged in the - browser every time a renderer attempts to load a font family, once per font - file. - - - - - drott@chromium.org - layout-dev@chromium.org - - The outcome of attempting to load a font family in the renderer (success vs - failure and number of families). This is logged in the renderer once per - family that is loaded. - - - - - drott@chromium.org - layout-dev@chromium.org - - The time taken to load a font family, excluding glyph data. This is logged - in the renderer once per family that is loaded. - - - - - drott@chromium.org - layout-dev@chromium.org - - Time it takes to build the font unique name lookup table. Recorded at the - initial build of this table, after which it is kept for the lifetime of the - browser process. The start time is recorded when the actual task of starting - to scan fonts has started. - - - - - drott@chromium.org - layout-dev@chromium.org - - Measures whether the font table lookup structure was loaded from disk cache - or had to be rebuilt due to changes in installed fonts, DWrite version or - Chrome version. Recorded when DWriteFontLookupTableBuilder starts to prepare - the lookup table. - - - - - drott@chromium.org - layout-dev@chromium.org - - Measures whether the font table lookup structure was successfully persisted - to disk after having been constructed. Recorded when - DWriteFontLookupTableBuilder finalizes the lookup table. - - - - - drott@chromium.org - layout-dev@chromium.org - - Time it takes from scheduling the preparation of the font lookup table until - it is ready, independent of whether it is read from cache or built by - scanning fonts. Start time is recorded when the call is made to prepare the - table. Duration and this histogram's value is recorded either when it is - done reading from cache or when the table construction is ready. This metric - includes a scheduling delay from when the task to read from cache or build - is scheduled, untils its execution, while - DirectWrite.Fonts.Proxy.LookupTableBuildTime does not include this - scheduling delay and measures only from when the first font scanning task is - started. - - - - - drott@chromium.org - layout-dev@chromium.org - - Size of the font unique name lookup table in kilobytes. Recorded at the - initial build of this table, after which it is kept for the lifetime of the - browser process. - - - - - drott@chromium.org - layout-dev@chromium.org - - Errors, if any, encountered by the DirectWrite font proxy message filter. - - - - - drott@chromium.org - layout-dev@chromium.org - - When scanning fonts for meta data as part of local matching, record the most - frequent failure of why no meta data was gathered for a font family. - Recorded in DWriteFontTableBuilder at the time of finishing scanning the - font files for their name meta information. Values are Windows HRESULT error - codes, including custom values for implementation specific failure cases. - Used for diagnosing https://crbug.com/1009402. - - - - - drott@chromium.org - layout-dev@chromium.org - - Number of font files which were encountered during scanning for locally - installed font and building the unique font name lookup table. Recorded in - DWriteFontTableBuilder while after the building the lookup table. Kept for - the lifetime of the browser process after that. - - - - - drott@chromium.org - layout-dev@chromium.org - - Shows whether the font lookup table construction timed out. Recorded when - DWriteFontLookupTableBuilder finalizes the lookup table. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Whether an extension has been wiped out. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How many external extensions get wiped out as a result of the Sideload - Wipeout one-time initiative. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Whether any extension got wiped out as a result of the Sideload Wipeout - one-time initiative. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The user selection in the Sideload Wipeout bubble, grouped by the - UmaWipeoutHistogramOptions enum. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The number of tabs discard candidates. This is recorded each time Chrome - needs to urgently discard a tab. - - - - - - - fdoray@chromium.org - - Number of tabs discarded in each interval of 10 minutes, per discard reason. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The number of tab discard attempts during a high-PMF session. Recorded at - the end of each high PMF session, or when the number of discard attempts - within the same high-PMF session reaches 100 (at which point the counter - will reset, e.g. 102 discards attempts would be recorded in two pieces as - "100" and "2"). - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Indicates if a tab has been successfully discarded during a high-PMF - session. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The memory pressure level when the High-PMF policy decides to discard a tab. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The amount of memory that has been reclaimed after discarding a tab during a - high-PMF session. In the case of a memory increase the value will be - reported as 0 and will go in the underflow bucket. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The number of successful tab discards during a high-PMF session. Recorded at - the end of each high PMF session, or when the number of successful discards - within the same high-PMF session reaches 100 (at which point the counter - will reset, e.g. 102 successful discards would be recorded in two pieces as - "100" and "2"). - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The largest tab's resident set among all the urgent discarding candidates. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - The resident set of the oldest urgent discarding candidate. - - - - sebmarchand@chromium.org - catan-team@chromium.org - - An estimate of the total resident set of Chrome when receiving a critical - memory pressure event, in megabytes. Note that the estimate is based on the - most recent data collected by Performance Manager, which are refreshed at a - low frequency (up to 2 minutes). - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - An estimate of the total resident set of Chrome when receiving a critical - memory pressure event, in percentage of the total amount of RAM. Note that - the estimate is based on the most recent data collected by Performance - Manager, which are refreshed at a low frequency (up to 2 minutes). - - - - - - - fdoray@chromium.org - - Whether the machine was online when a discarded tab was reloaded. - - - - - - - fdoray@chromium.org - - Number of discarded tabs reloaded in each interval of 10 minutes, grouped by - their discard reason. - - - - - - Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs - are discarded too often. - - fdoray@chromium.org - - Number of tabs that are not pending load or discarded when an urgent discard - request is received. - - - - - - Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs - are discarded too often. - - fdoray@chromium.org - - Time between two consecutive urgent discard requests. Urgent discards are - undesirable; it is better to reduce memory usage before the system is in a - bad state. - - - - - - Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs - are discarded too often. - - fdoray@chromium.org - - Time between Chrome startup and the first urgent discard request. Urgent - discards are undesirable; it is better to reduce memory usage before the - system is in a bad state. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The amount of physical memory available when receiving a low memory - notification, in megabytes. Windows 8.1+ only. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The time it takes to receive a high memory notification from the OS after - receiving a low memory notification. Windows 8.1+ only. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The memory pressure level when receiving a low memory notification from the - OS. Windows 8.1+ only. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Records information about DiskBasedCertCache operations with respect to - certificate chain positions. Zero indicates that a certificate is root, one - indicates that it is the first intermediate certificate, etc. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Records the outcome of requests to retrieve certificates from the disk - cache. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Whether or not the leaf certificate of a certificate chain was successfuly - read from the disk cache. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Whether or not the leaf certificate of a certificate chain was successfully - written to the disk cache. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Measures the wall clock time spent reading a certificate chain. The starting - time is when the read command is issued, and the ending time is when all of - the certificates in the chain have been read into memory. - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - brandonsalmon@chromium.org - - Measures the wall clock time spent writing a certificate chain to disk. The - starting time is when the write command is issued, and the ending time is - when all the certificates in the chain have been written to disk. - - - - - rvargas@chromium.org - - The time for an async IO operation to complete. This covers content Writes - and Reads, measured from the cache thread. - - - - - rvargas@chromium.org - The synchronous portion of an async read. - - - - rvargas@chromium.org - The synchronous portion of an async write. - - - - rvargas@chromium.org - - The average number of open disk cache entries at any given time. - - - - - rvargas@chromium.org - The total size of all the internal buffers. - - - - rvargas@chromium.org - - The number of KB accessed from the cache in a 30 seconds interval. - - - - - rvargas@chromium.org - The time spent creating a new entry on the cache. - - - - rvargas@chromium.org - The age of the last entry on the queue of deleted entries. - - - - rvargas@chromium.org - - The size of the data portion of a given entry by the time it is deleted. - - - - - rvargas@chromium.org - The percentage of the deleted entries. - - - - rvargas@chromium.org - Number of external files that we were unable to delete. - - - - rvargas@chromium.org - - The size of the HTML headers of a given entry by the time it is deleted. - - - - - rvargas@chromium.org - The number of entries currently stored on the cache. - - - - rvargas@chromium.org - - The number of entries currently stored on the cache, after it is full. - - - - - rvargas@chromium.org - - The number of entries accessed by the cache in a 30 seconds interval. - - - - - rvargas@chromium.org - - The average size of an entry. It is only measured after the cache is full, - so evictions are taking place. - - - - - rvargas@chromium.org - Critical error ids. - - - - - Removed 2019-07-05 - - morlovich@chromium.org - The age of the cache's files (wall time). - - - - rvargas@chromium.org - - The age of the cache (in hours) by the time we reach the size limit. - - - - - rvargas@chromium.org - - The number of hours required to fill up the cache, as measured by the cache - being running. - - - - - rvargas@chromium.org - - The average number of KB accessed from the cache in a 30 seconds interval, - by the time we reach the cache size limit. - - - - - rvargas@chromium.org - - The average number of entries accessed by the cache in a 30 seconds - interval, by the time we reach the cache size limit. - - - - - rvargas@chromium.org - - The average size of an entry by the time we reach the cache size limit. - - - - - rvargas@chromium.org - - The percentage of the entries that are highly reused, by the time we fill up - the cache. - - - - - rvargas@chromium.org - - The hit ratio by the time we fill up the cache. Of course, we started with - an empty cache. - - - - - rvargas@chromium.org - - The percentage of the cache used by entries of more than 512 KB, by the time - we reach the cache size limit. - - - - - rvargas@chromium.org - - The percentage of the entries that have been reused a few times, by the time - we fill up the cache. - - - - - rvargas@chromium.org - - The percentage of the entries that have never been reused, by the time we - fill up the cache. - - - - - rvargas@chromium.org - - The percentage of re-created deleted entries versus entries that we really - don't know about. - - - - - rvargas@chromium.org - The time spent reading the LRU-related portion of an entry. - - - - rvargas@chromium.org - - The age of the last entry on the queue of highly used entries. - - - - - rvargas@chromium.org - The percentage of the entries that are highly reused. - - - - rvargas@chromium.org - - The current hit ratio. It is only measured after the cache is full, so - evictions are taking place, and data from the fill-up period is not - considered. - - - - - rvargas@chromium.org - - The hit ratio for each size. To calculate the hit ratio of caches of a - certain size, take the ratio of a bin in this histogram to the same bin in - DiskCache.0.Size2. - - - - - rvargas@chromium.org - - The hit ratio for each total time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.0.TotalTime. - - - - - rvargas@chromium.org - - The hit ratio for each use time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.0.UseTime. - - - - - rvargas@chromium.org - - Percentage of the index table that is currently used (the cache is full). - - - - - rvargas@chromium.org - The size of each key. - - - - rvargas@chromium.org - - Percentage of the cache used by entries of more than 512 KB. It is only - measured after the cache is full, so evictions are taking place. - - - - - rvargas@chromium.org - - The time to load the main entry data from disk, with a "loaded" - system. - - - - - rvargas@chromium.org - - The age of the last entry on the queue of entries reused a few times. - - - - - rvargas@chromium.org - - The percentage of the entries that have been reused a few times. - - - - - rvargas@chromium.org - - The maximum number of simultaneously open disk cache entries. - - - - - - Removed. See MaxSize2. - - rvargas@chromium.org - The maximum size of the cache. - - - - rvargas@chromium.org - The maximum size of the cache. - - - - rvargas@chromium.org - - The age of the next entry to be evicted that has never been reused. - - - - - rvargas@chromium.org - The percentage of the entries that have never been reused. - - - - rvargas@chromium.org - The number of open entry references at any given moment. -
- Closely related to AverageOpenEntries, but this one is not the average per - client but instead a direct histogram updated every 30 secs. -
- - - - rvargas@chromium.org - - The time spent opening an entry already on the cache (cache hit). - - - - - rvargas@chromium.org - The number of pending IO operations (Async IO). - - - - rvargas@chromium.org - The time spent reading from an entry. - - - - rvargas@chromium.org - - The percentage of re-created deleted entries versus entries that we really - don't know about. - - - - - rvargas@chromium.org - The reason for not sending a full report. - - - - - Removed. See Size2 - - rvargas@chromium.org - The current size of the cache. - - - - rvargas@chromium.org - The current size of the cache. - - - - rvargas@chromium.org - The time spent reading from an sparse entry. - - - - rvargas@chromium.org - The time spent writing to an sparse entry. - - - - rvargas@chromium.org - The time spent deleting the cache. (Clear browsing data). - - - - rvargas@chromium.org - The time spent deleting the cache. (Clear browsing data). - - - - rvargas@chromium.org - - The number of times that this cache has been deleted by the user. - - - - - rvargas@chromium.org - - The number of times that the user has deleted new entries from this cache. - - - - - rvargas@chromium.org - The number of times that ga.js was evicted. - - - - rvargas@chromium.org - - The number of fatal errors detected for this cache (so we delete - everything). - - - - - rvargas@chromium.org - - The total time it takes to perform a payload IO operation (AKA, directed to - an entry). This is measured from the IO thread. - - - - - rvargas@chromium.org - Number of hours that the cache has been used. - - - - rvargas@chromium.org - - The number of hours that the cache has been in use, for users that still - have available space. - - - - - rvargas@chromium.org - The time spent removing deleted entries from the cache. - - - - rvargas@chromium.org - The time spent removing old entries from the cache. - - - - rvargas@chromium.org - The time spent removing old entries from the cache. - - - - rvargas@chromium.org - - The time spent evicting entries from the cache (moving them to the deleted - list). - - - - - rvargas@chromium.org - - The time that an entry lives in the cache without being accessed until it is - finally purged. - - - - - rvargas@chromium.org - - The number of entries that are deleted on a single iteration. - - - - - rvargas@chromium.org - - The number of entries that are evicted on a single iteration. - - - - - rvargas@chromium.org - - The number of entries that are evicted (moved to the deleted list) on a - single iteration. - - - - - rvargas@chromium.org - The number of entries that are evicted per hour of use. - - - - rvargas@chromium.org - - The time spent moving an entry to the front of the LRU list. - - - - - rvargas@chromium.org - - The percentage of the allowed disk space that we are currently using. - - - - - rvargas@chromium.org - - Number of hours that the cache has been used since last week. - - - - - rvargas@chromium.org - The time spent writing to an entry. - - - - rvargas@chromium.org - - The time for an async IO operation to complete. This covers content Writes - and Reads, measured from the cache thread. Media-specific cache. - - - - - rvargas@chromium.org - - The synchronous portion of an async read. Media-specific cache. - - - - - rvargas@chromium.org - - The synchronous portion of an async write. Media-specific cache. - - - - - rvargas@chromium.org - - The average number of open disk cache entries at any given time. - Media-specific cache. - - - - - rvargas@chromium.org - - The total size of all the internal buffers. Media-specific cache. - - - - - rvargas@chromium.org - - The number of KB accessed from the cache in a 30 seconds interval. - Media-specific cache. - - - - - rvargas@chromium.org - - The time spent creating a new entry on the cache. Media-specific cache. - - - - - rvargas@chromium.org - - The size of the data portion of a given entry by the time it is deleted. - Media-specific cache. - - - - - rvargas@chromium.org - - Number of external files that we were unable to delete. Media-specific - cache. - - - - - rvargas@chromium.org - - The size of the HTML headers of a given entry by the time it is deleted. - Media-specific cache. - - - - - rvargas@chromium.org - - The number of entries currently stored on the cache. Media-specific cache. - - - - - rvargas@chromium.org - - The number of entries currently stored on the cache, after it is full. - Media-specific cache. - - - - - rvargas@chromium.org - - The number of entries accessed by the cache in a 30 seconds interval. - Media-specific cache. - - - - - rvargas@chromium.org - - The average size of an entry. It is only measured after the cache is full, - so evictions are taking place. Media-specific cache. - - - - - rvargas@chromium.org - Critical error ids. Media-specific cache. - - - - - Removed 2019-07-05 - - morlovich@chromium.org - - The age of the cache's files (wall time). Media-specific cache. - - - - - rvargas@chromium.org - - The age of the cache (in hours) by the time we reach the size limit. - Media-specific cache. - - - - - rvargas@chromium.org - - The number of hours required to fill up the cache, as measured by the cache - being running. Media-specific cache. - - - - - rvargas@chromium.org - - The average number of KB accessed from the cache in a 30 seconds interval, - by the time we reach the cache size limit. Media-specific cache. - - - - - rvargas@chromium.org - - The average number of entries accessed by the cache in a 30 seconds - interval, by the time we reach the cache size limit. Media-specific cache. - - - - - rvargas@chromium.org - - The average size of an entry by the time we reach the cache size limit. - Media-specific cache. - - - - - rvargas@chromium.org - - The hit ratio by the time we fill up the cache. Of course, we started with - an empty cache. Media-specific cache. - - - - - rvargas@chromium.org - - The percentage of the cache used by entries of more than 512 KB, by the time - we reach the cache size limit. Media-specific cache. - - - - - rvargas@chromium.org - - The time spent reading the LRU-related portion of an entry. Media-specific - cache. - - - - - rvargas@chromium.org - - The current hit ratio. It is only measured after the cache is full, so - evictions are taking place, and data from the fill-up period is not - considered. Media-specific cache. - - - - - rvargas@chromium.org - - The hit ratio for each size. To calculate the hit ratio of caches of a - certain size, take the ratio of a bin in this histogram to the same bin in - DiskCache.2.Size2. Media-specific cache. - - - - - rvargas@chromium.org - - The hit ratio for each total time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.2.TotalTime. Media-specific cache. - - - - - rvargas@chromium.org - - The hit ratio for each use time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.2.UseTime. Media-specific cache. - - - - - rvargas@chromium.org - - Percentage of the index table that is currently used (the cache is full). - Media-specific cache. - - - - - rvargas@chromium.org - The size of each key. Media-specific cache. - - - - rvargas@chromium.org - - Percentage of the cache used by entries of more than 512 KB. It is only - measured after the cache is full, so evictions are taking place. - Media-specific cache. - - - - - rvargas@chromium.org - - The time to load the main entry data from disk, with a "loaded" - system. Media-specific cache. - - - - - rvargas@chromium.org - - The maximum number of simultaneously open disk cache entries. Media-specific - cache. - - - - - - Removed. See MaxSize2. - - rvargas@chromium.org - The maximum size of the cache. Media-specific cache. - - - - rvargas@chromium.org - The maximum size of the cache. Media-specific cache. - - - - rvargas@chromium.org - - The number of open entry references at any given moment. Closely related to - AverageOpenEntries, but this one is not the average per client but instead a - direct histogram updated every 30 secs. Media-specific cache. - - - - - rvargas@chromium.org - - The time spent opening an entry already on the cache (cache hit). - Media-specific cache. - - - - - rvargas@chromium.org - - The number of pending IO operations (Async IO). Media-specific cache. - - - - - rvargas@chromium.org - The time spent reading from an entry. Media-specific cache. - - - - rvargas@chromium.org - - The percentage of re-created deleted entries versus entries that we really - don't know about. Media-specific cache. - - - - - rvargas@chromium.org - - The reason for not sending a full report. Media-specific cache. - - - - - - Removed. See Size2. - - rvargas@chromium.org - The current size of the cache. Media-specific cache. - - - - rvargas@chromium.org - The current size of the cache. Media-specific cache. - - - - rvargas@chromium.org - - The time spent deleting the cache. (Clear browsing data). Media-specific - cache. - - - - - rvargas@chromium.org - - The time spent deleting the cache. (Clear browsing data). Media-specific - cache. - - - - - rvargas@chromium.org - - The total time it takes to perform a payload IO operation (AKA, directed to - an entry). This is measured from the IO thread. Media-specific cache. - - - - - rvargas@chromium.org - - Number of hours that the cache has been used. Media-specific cache. - - - - - rvargas@chromium.org - - The time spent removing deleted entries from the cache. Media-specific - cache. - - - - - rvargas@chromium.org - - The time spent removing old entries from the cache. Media-specific cache. - - - - - rvargas@chromium.org - - The time spent removing old entries from the cache. Media-specific cache. - - - - - rvargas@chromium.org - - The time spent evicting entries from the cache (moving them to the deleted - list). Media-specific cache. - - - - - rvargas@chromium.org - - The time that an entry lives in the cache without being accessed until it is - finally purged. Media-specific cache. - - - - - rvargas@chromium.org - - The number of entries that are deleted on a single iteration. Media-specific - cache. - - - - - rvargas@chromium.org - - The number of entries that are evicted on a single iteration. Media-specific - cache. - - - - - rvargas@chromium.org - - The number of entries that are evicted (moved to the deleted list) on a - single iteration. Media-specific cache. - - - - - rvargas@chromium.org - - The number of entries that are evicted per hour of use. Media-specific - cache. - - - - - rvargas@chromium.org - - The time spent moving an entry to the front of the LRU list. Media-specific - cache. - - - - - rvargas@chromium.org - - The percentage of the allowed disk space that we are currently using. - Media-specific cache. - - - - - rvargas@chromium.org - - Number of hours that the cache has been used since last week. Media-specific - cache. - - - - - rvargas@chromium.org - The time spent writing to an entry. Media-specific cache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time for an async IO operation to complete. This covers content Writes - and Reads, measured from the cache thread. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The synchronous portion of an async read. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The synchronous portion of an async write. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of open disk cache entries at any given time. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The total size of all the internal buffers. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of KB accessed from the cache in a 30 seconds interval. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The time spent creating a new entry on the cache. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The size of the data portion of a given entry by the time it is deleted. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of external files that we were unable to delete. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries currently stored on the cache. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries currently stored on the cache, after it is full. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries accessed by the cache in a 30 seconds interval. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average size of an entry. It is only measured after the cache is full, - so evictions are taking place. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - Critical error ids. AppCache. - - - - - Removed 2019-07-05 - - morlovich@chromium.org - The age of the cache's files (wall time). AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The age of the cache (in hours) by the time we reach the size limit. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of hours required to fill up the cache, as measured by the cache - being running. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of KB accessed from the cache in a 30 seconds interval, - by the time we reach the cache size limit. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of entries accessed by the cache in a 30 seconds - interval, by the time we reach the cache size limit. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average size of an entry by the time we reach the cache size limit. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio by the time we fill up the cache. Of course, we started with - an empty cache. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of the cache used by entries of more than 512 KB, by the time - we reach the cache size limit. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent reading the LRU-related portion of an entry. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The current hit ratio. It is only measured after the cache is full, so - evictions are taking place, and data from the fill-up period is not - considered. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each size. To calculate the hit ratio of caches of a - certain size, take the ratio of a bin in this histogram to the same bin in - DiskCache.3.Size2. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each total time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.3.TotalTime. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each use time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.3.UseTime. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Percentage of the index table that is currently used (the cache is full). - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The size of each key. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - Percentage of the cache used by entries of more than 512 KB. It is only - measured after the cache is full, so evictions are taking place. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time to load the main entry data from disk, with a "loaded" - system. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The maximum number of simultaneously open disk cache entries. AppCache. - - - - - - Removed. See MaxSize2. - - Please list the metric's owners. Add more owner tags as needed. - The maximum size of the cache. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The maximum size of the cache. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent opening an entry already on the cache (cache hit). AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The number of pending IO operations (Async IO). AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The time spent reading from an entry. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of re-created deleted entries versus entries that we really - don't know about. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The reason for not sending a full report. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The current size of the cache. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The total time it takes to perform a payload IO operation (AKA, directed to - an entry). This is measured from the IO thread. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - Number of hours that the cache has been used. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent removing deleted entries from the cache. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent removing old entries from the cache. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent evicting entries from the cache (moving them to the deleted - list). AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time that an entry lives in the cache without being accessed until it is - finally purged. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are deleted on a single iteration. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are evicted on a single iteration. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are evicted (moved to the deleted list) on a - single iteration. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are evicted per hour of use. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent moving an entry to the front of the LRU list. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of the allowed disk space that we are currently using. - AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of hours that the cache has been used since last week. AppCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The time spent writing to an entry. AppCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time for an async IO operation to complete. This covers content Writes - and Reads, measured from the cache thread. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The synchronous portion of an async read. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The synchronous portion of an async write. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of open disk cache entries at any given time. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The total size of all the internal buffers. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of KB accessed from the cache in a 30 seconds interval. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent creating a new entry on the cache. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The size of the data portion of a given entry by the time it is deleted. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of external files that we were unable to delete. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The size of the HTML headers of a given entry by the time it is deleted. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries currently stored on the cache. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries currently stored on the cache, after it is full. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries accessed by the cache in a 30 seconds interval. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average size of an entry. It is only measured after the cache is full, - so evictions are taking place. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - Critical error ids. ShaderCache. - - - - - Removed 2019-07-05 - - morlovich@chromium.org - The age of the cache's files (wall time). ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The age of the cache (in hours) by the time we reach the size limit. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of hours required to fill up the cache, as measured by the cache - being running. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of KB accessed from the cache in a 30 seconds interval, - by the time we reach the cache size limit. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average number of entries accessed by the cache in a 30 seconds - interval, by the time we reach the cache size limit. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The average size of an entry by the time we reach the cache size limit. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio by the time we fill up the cache. Of course, we started with - an empty cache. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of the cache used by entries of more than 512 KB, by the time - we reach the cache size limit. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent reading the LRU-related portion of an entry. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The current hit ratio. It is only measured after the cache is full, so - evictions are taking place, and data from the fill-up period is not - considered. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each size. To calculate the hit ratio of caches of a - certain size, take the ratio of a bin in this histogram to the same bin in - DiskCache.4.Size2. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each total time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.4.TotalTime. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The hit ratio for each use time. To calculate the hit ratio of caches of a - certain age, take the ratio of a bin in this histogram to the same bin in - DiskCache.4.UseTime. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Percentage of the index table that is currently used (the cache is full). - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The size of each key. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - Percentage of the cache used by entries of more than 512 KB. It is only - measured after the cache is full, so evictions are taking place. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time to load the main entry data from disk, with a "loaded" - system. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The maximum number of simultaneously open disk cache entries. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The maximum size of the cache. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent opening an entry already on the cache (cache hit). - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of pending IO operations (Async IO). ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The time spent reading from an entry. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The reason for not sending a full report. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The current size of the cache. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The total time it takes to perform a payload IO operation (AKA, directed to - an entry). This is measured from the IO thread. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - Number of hours that the cache has been used. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent removing old entries from the cache. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time that an entry lives in the cache without being accessed until it is - finally purged. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are evicted on a single iteration. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of entries that are evicted per hour of use. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time spent moving an entry to the front of the LRU list. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of the allowed disk space that we are currently using. - ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of hours that the cache has been used since last week. ShaderCache. - - - - - Please list the metric's owners. Add more owner tags as needed. - The time spent writing to an entry. ShaderCache. - - - - Please list the metric's owners. Add more owner tags as needed. - The percentage of use for blocks of type 0 (links). - - - - Please list the metric's owners. Add more owner tags as needed. - The percentage of use for blocks of type 1 (256 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - The percentage of use for blocks of type 2 (1024 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - The percentage of use for blocks of type 3 (4096 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - The number of used blocks of type 0 (links). - - - - Please list the metric's owners. Add more owner tags as needed. - The number of used blocks of type 1 (256 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - The number of used blocks of type 2 (1024 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - The number of used blocks of type 3 (4096 bytes). - - - - Please list the metric's owners. Add more owner tags as needed. - Number of block-files that we were unable to delete. - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - The number of entries currently stored on the cache. - - - - Please list the metric's owners. Add more owner tags as needed. - The experiment group for this user. - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - - The current hit ratio. It is only measured after the cache is full, so - evictions are taking place, and data from the fill-up period is not - considered. - - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - - Percentage of the cache used by entries of more than 512 KB. It is only - measured after the cache is full, so evictions are taking place. - - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - The maximum size of the cache. - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - The current size of the cache. - - - - dmikurube@chromium.org - The size distribution of data stored on the cache. - - - - - Removed 2019-07-05 - - morlovich@chromium.org - The size distribution of data stored in the HTTP cache. - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - - The total time it takes to perform a payload IO operation, for the regular - disk cache. - - - - - - Removed. - - Please list the metric's owners. Add more owner tags as needed. - - The time that an entry lives in the cache without being accessed until it is - finally purged. - - - - - sashamcintosh@chromium.org - chromeos-gfx@google.com - - Type of failure that occurs during EDID parsing. Typically the failure is - caused by a mismatch between the EDID size and the expected offset of the - data component. - - - - - malaykeshav@chromium.org - - The zoom percentage that the user has set on the internal display and is - actively using. This is emitted when the zoom factor has been updated in - display manager and has not been changed for a while. - - - - - zentaro@chromium.org - baileyberro@chromium.org - - The number of displays connected to the device that are in software or - hardware mirror mode. This is emitted once when the normal or mixed mirror - mode is enabled through API call, or the display configuration changes (e.g. - adding or removing a display) when mirror mode is on. - - - - - zentaro@chromium.org - baileyberro@chromium.org - - The types of mirror mode in which the displays connected to the device are - in. This is emitted once when the normal or mixed mirror mode is enabled - through API call, or the display configuration changes ( e.g. adding or - removing a display) when mirror mode is on. - - - - - zentaro@chromium.org - cros-peripherals@google.com - - The mode in which the connected displays to the device are in. This is - emitted once when displays are added or removed, or when the user changes - the mode by e.g. enabling mirror or unified modes. - - - - - zentaro@chromium.org - cros-peripherals@google.com - - The number of displays connected to the device when Unified Desktop mode is - on. This is emitted when Unified Desktop mode is turned on, or the displays - are added or removed while in Unified Mode. - - - - - zentaro@chromium.org - nohle@chromium.org - - Records the execution time to update the display configuration. Emitted when - the update-display-configuration task finishes, successfully or not. - - - - - zentaro@chromium.org - nohle@chromium.org - - Records whether or not the display configuration was successfully updated. - Emitted when the update-display-configuration task finishes, successfully or - not. - - - - - - Removed after M72 since no longer needed. - - - - sadrul@chromium.org - sunnyps@chromium.org - - The reason for the DisplayScheduler to abort a draw operation. - - - - - - Removed as of 6/2018. - - mgersh@chromium.org - - The attempt which completed after the job was already cancelled. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - The attempt which completed after the job was already cancelled OR the - attempt that has finished after host resolution was already completed by an - earlier attempt. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in OS resolutions for actual navigations. These - attempts which completed after the job was already canceled OR after the job - was already completed by an earlier attempt. Note that cached resolutions - may provide low (0ms?) resolution times. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - The attempt that has not resolved the host successfully. - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - The attempt that resolved the host first and the resolution was not - successful. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - The attempt that resolved the host first and the resolution was successful. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - The attempt that has resolved the host successfully. - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken in OS resolutions that succeeded and were requested - for actual navigations. These attempts which completed after the job was - already canceled OR after the job was already completed by an earlier - attempt. Note that cached resolutions may provide low (0ms?) resolution - times. - - - - - - Removed as of 6/2018. - - mgersh@chromium.org - - This histogram shows the time saved by having spawned an extra attempt, when - the first attempt didn't finish before retry attempt. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The time left to expiration of an entry when it is removed while compacting - the HostCache. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The time since expiration of an entry when it is removed while compacting - the HostCache. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The time since expiration of an entry when it is removed on lookup. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - Error status when an empty address list was found in OnLookupComplete(). - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - The reason for erasing a DNS entry from the host cache. - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When erasing a stale (expired or old-network) DNS entry from the host cache, - how long past the expiration time it is. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When erasing a stale (expired or old-network) DNS entry from the host cache - how many network changes happened between setting and erasing it. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When erasing a stale (expired or old-network) DNS entry from the host cache - how many hits it received while stale. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When erasing a valid DNS entry from the host cache, for how much longer it - would have remained valid. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - The outcome of looking up a DNS entry in the host cache. - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When looking up a stale DNS entry in the host cache, how long past the - expiration time it is. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When looking up a stale DNS entry in the host cache, how many network - changes happened between setting it and looking it up. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - Number of HostCache entries persisted to disk, measured at restore time. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - Whether the persisted HostCache entries were restored successfully. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - The outcome of setting a DNS entry in the host cache. - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When updating a stale (expired or old-network) DNS entry in the host cache, - and both results are successful, how the address list differs between the - old and new entries. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When updating a stale (expired or old-network) DNS entry in the host cache, - how long past the expiration time the old entry was. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - When updating a stale (expired or old-nework) DNS entry in the host cache, - how many network changes happened between setting the old entry and setting - the new entry. - - - - - - Removed as of 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - The number of hits received to an updated stale DNS entry in the host cache - while it was stale. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - When either a pre-resolution was not done recently enough to provide - benefit, or the corresponding pre-resolution is still pending, this - histogram shows the duration of time used to resolve a hostname as not - existing during a failed attempt to navigate to (GET) a URL. In newer - versions, if the hostname has never been found as a link during a page scan, - and it has a referring URL, then it is added to referrer list data structure - (hoping we'll do better next time). - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - When either a pre-resolution was not done recently enough to provide - benefit, or the corresponding pre-resolution is still pending, this - histogram shows the duration of the duration of time used to resolve a - hostname to navigate to (GET) a URL. In newer versions, if the hostname has - never been found as a link during a page scan, and it has a referring URL, - then it is added to referrer list data structure (hoping we'll do better - next time). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). Includes only Jobs which had priority HIGHEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). Includes only Jobs which had priority IDLE when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). Includes only Jobs which had priority LOW when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). Includes only Jobs which had priority LOWEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. - - mgersh@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started (a getaddrinfo call was dispatched to the thread - pool). Includes only Jobs which had priority MEDIUM when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). Includes - only Jobs which had priority HIGHEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). Includes - only Jobs which had priority IDLE when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). Includes - only Jobs which had priority LOW when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). Includes - only Jobs which had priority LOWEST when started. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. - - mgersh@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started (a getaddrinfo call was dispatched to the thread pool). Includes - only Jobs which had priority MEDIUM when started. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time used (most recently) to pre-resolve a hostname, when - the prefetched resolution was apparently evicted from the cache. The - included samples only list pre-resolution times when the later - navigations/fetches took in excess of 15ms. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time used (most recently) to pre-resolve a hostname, when - the prefetched resolution was apparently evicted from the cache. The - included samples only list pre-resolution times when the later - navigations/fetches took in excess of 15ms. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - Replaced by DNS.PrefetchFoundNameL. - - - - - Removed 2/2010, and replaced by DNS.PrefetchResolution - - mgersh@chromium.org - - The duration of time used by the DNS pre-resolving threads to resolve a host - name via the network. Any resolutions that are faster than 15ms are - considered to be local cache hits, not requiring network access, and are not - included in this histogram. This histogram is most useful for estimating the - typical cost of a name resolution, but it also estimates the total number of - network-based resolutions induced by this feature. Not all these resolutions - prove helpful (i.e., the user does not always actually visit the resolved - hostnames). - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - Replaced by DNS.PrefetchNegativeHitL. - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time saved due to DNS pre-resolving in the "name not - found" case. Time "savings" shown in the histogram are - defined to be the difference between the DNS pre-resolution duration, and - the DNS resolution duration seen during a navigation. These cache hits only - list events where the DNS pre-resolve duration for a host was in excess of - 15ms (i.e., the network was consulted), and the actual DNS resolution (when - a user attempted to navigate to a link with the same host name) took less - than 15ms (i.e., the network was not consulted), which means the gain was a - result of a "cache hit" in the OS cache. For some users with LANs, - all negative results (even when the DNS cache might otherwise help) take - about 2.5 seconds (due to timeouts for netbios broadcasts), and hence no - savings are possible (or shown) for such users in this category. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - Replaced by DNS.PrefetchPositiveHitL. - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time saved due to DNS pre-resolving in the "name was - found" case, and induced by either a page scan for a link or an omnibox - entry by the user. Time "savings" shown in the histogram are - defined to be the difference between the DNS pre-resolution duration, and - the DNS resolution duration seen during a navigation. These cache hits only - list events where the DNS pre-resolve duration for a host was in excess of - 15ms (i.e., the network was consulted), and the actual DNS resolution (when - a user attempted to navigate to a link with the same host name) took less - than 15ms (i.e., the network was not consulted), which means the gain was a - result of a "cache hit" in the OS cache. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time spent by a proposed resolution waiting in the queue to - be resolved. This number is in addition to any DNS resolution time that may - come later. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - The duration of time saved due to DNS pre-resolving in the "name was - found" case, and induced by predicting (using referrer lists) that a - resolution was needed. Time "savings" shown in the histogram are - defined to be the difference between the DNS pre-resolution duration, and - the DNS resolution duration seen during a navigation. These cache hits only - list events where the DNS pre-resolve duration for a host was in excess of - 15ms (i.e., the network was consulted), and the actual DNS resolution (when - a user attempted to navigate to a link with the same host name) took less - than 15ms (i.e., the network was not consulted), which means the gain was a - result of a "cache hit" in the OS cache. - - - - - mgersh@chromium.org - - The duration of time used by the DNS pre-resolving threads to resolve a host - name via the network. Any resolutions that are faster than 15ms are - considered to be local cache hits, not requiring network access, and are not - included in this histogram. This histogram is most useful for estimating the - typical cost of a name resolution, but it also estimates the total number of - network-based resolutions induced by this feature. Not all these resolutions - prove helpful (i.e., the user does not always actually visit the resolved - hostnames). - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - When, due to congestion avoidance, a queued pre-resolution is abandoned - (recycled) without actually being resolved, this histograms records the age - in the queue of that entry. Only times over 2 seconds are recorded in this - histogram. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - When, due to congestion avoidance, a queued pre-resolution is abandoned - (recycled) without actually being resolved, this histograms records the age - in the queue of that entry. Only times less than or equal to 2 seconds are - recorded in this histogram. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ResolveCategory. - - mgersh@chromium.org - - Counts of successes and failures of OS resolutions in various categories. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. - - mgersh@chromium.org - - Duration of time taken in OS resolutions for actual navigations. Note that - cached OS resolutions may provide low (0ms?) resolution times. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. - - mgersh@chromium.org - Same as DNS.ResolveFail, but limited to pure IPv4 lookups. - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. - - mgersh@chromium.org - Same as DNS.ResolveFail, but limited to pure IPv6 lookups. - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. - - mgersh@chromium.org - Same as DNS.ResolveFail, but limited to IPv4/IPv6 lookups. - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. - - mgersh@chromium.org - - Duration of time taken in speculative OS resolutions. Note that cached OS - resolutions may provide low (0ms?) resolution times. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. - - mgersh@chromium.org - - Duration of time taken in speculative OS resolution that succeeded. Note - that cached resolutions may provide low (0ms?) resolution times. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. - - mgersh@chromium.org - - Duration of time taken in OS resolutions that succeeded and were requested - for actual navigations. Note that cached resolutions may provide low (0ms?) - resolution times. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. - - mgersh@chromium.org - - Same as DNS.ResolveSuccess, but limited to pure IPv4 lookups. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. - - mgersh@chromium.org - - Same as DNS.ResolveSuccess, but limited to pure IPv6 lookups. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. - - mgersh@chromium.org - - Same as DNS.ResolveSuccess, but limited to IPv4/IPv6 lookups. - - - - - - Removed as of 5/2013. - - mgersh@chromium.org - - Counts of hits and misses in the DNS cache and DNS jobs pool of wasted - HostResolverImpl::Jobs that could be avoided by always resolving using - AF_UNSPEC. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver returns, a stale cached - result was available, and the network responded before or exactly at the - stale delay, how much earlier it responded. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver returns, a stale cached - result was available, and the network responded after the stale delay, how - much later it responded. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver returns or is canceled, - the outcome of the request. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver has no stale cached result - available, the number of host cache entries that were restored from prefs. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver has no stale cached result - available, the number of entries in the host cache. - - - - - - Removed 2020-06 - - pauljensen@chromium.org - mef@chromium.org - - When a DNS request made through StaleHostResolver had a stale cached result - and both the stale and network results were successful, the difference - between the old and new address lists. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.TotalTime. - - mgersh@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Excludes speculative requests. - - - - - - Removed as of 9/2017. Replaced by Net.DNS.TotalTime_speculative. - - mgersh@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Speculative requests only. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - In some cases, such as when content arrives with embedded references to - other servers, the prefetch system can't (or doesn't) attempt to pre-resolve - the hostnames. As an example, a visit to www.cnn.com will fetch content with - references to about 12 additional hostnames, none of which are currently - anticipated. Such resolutions are termed "Unexpected Resolutions," - and the durations associated with those DNS resolutions are shown below. - Future features may attempt to learn (from prior experience locally, or from - server provided hints), what secondary hostname resolutions should be done - when a primary resolution (or navigation) takes place. This histogram shows - what the potential savings are that "remain on the table" until we - employ some of these more advanced features. - - - - - - Removed as of 9/2017. - - mgersh@chromium.org - - In some cases, such as when content arrives with embedded references to - other servers, or when a page (such as one in SSL) preclude scanning and - prefetching, the prefetch system can't (or doesn't) attempt to pre-resolve - the hostnames. As an example, a visit to www.cnn.com will fetch content with - references to about 12 additional hostnames, none of which might be - anticipated. Similarly, clicking on a link in an SSL page won't be - anticipated (since scanning in not allowed by default). Such resolutions are - termed "Unexpected Resolutions," and the durations associated with - those navigation induced DNS resolutions are shown below. If a referring URL - is available for the navigation, the relationship to the referring URL was - recorded, and future navigations to the referring hostname would have - induced a pre-resolution of hostname that caused an entry below. Such any - entry may facilitate future listing in the ReferredPositiveHit histogram. - - - - - ericorth@chromium.org - src/net/OWNERS - - Status of DNS diagnostic probe updates sent to a Chrome net error page. - - - - - - Renamed 7/2013 to DnsProbe.ProbeDuration. - - mgersh@chromium.org - Time between starting and finishing DNS probe. - - - - - Removed 7/2013. - - mgersh@chromium.org - - Time between starting and finishing DNS probe when NCN says we're offline. - - - - - - Removed 7/2013. - - mgersh@chromium.org - - Result of DNS probes sent by the probe service when NCN says we're offline. - - - - - - Removed 7/2013. - - mgersh@chromium.org - - Time between starting and finishing DNS probe when NCN says we're online. - - - - - - Removed 7/2013. - - mgersh@chromium.org - - Result of DNS probes sent by the probe service when NCN says we're online. - - - - - - Renamed 7/2013 to DnsProbe.ProbeResult. (Also switched to the full - DnsProbe.ProbeStatus enum.) - - mgersh@chromium.org - Result of DNS probes sent by the probe service. - - - - - Removed 7/2013. - - mgersh@chromium.org - Elapsed time of DNS probes that return PROBE_BAD_CONFIG. - - - - - Removed 7/2013. - - mgersh@chromium.org - - Whether the only nameserver in the system DNS config was 127.0.0.1 when the - probe result was BAD_CONFIG. - - - - - - Removed 7/2013. - - mgersh@chromium.org - - The result of the system probe job when the overall probe result was - BAD_CONFIG. - - - - - - Removed 7/2013. - - mgersh@chromium.org - - The number of nameservers in the system DNS config when the probe result was - BAD_CONFIG. - - - - - - Removed 7/2013. - - mgersh@chromium.org - Elapsed time of DNS probes that return PROBE_NO_INTERNET. - - - - - Removed 7/2013. - - mgersh@chromium.org - Elapsed time of DNS probes that return PROBE_NXDOMAIN. - - - - - Removed 7/2013. - - mgersh@chromium.org - Elapsed time of DNS probes that return PROBE_UNKNOWN. - - - - - Replaced 2/2019 with DnsProbe.ProbeDuration2, which uses TimeTicks instead - of Time. - - pauljensen@chromium.org - mef@chromium.org - Wall time between starting and finishing DNS probe. - - - - ericorth@chromium.org - src/net/OWNERS - - Time ticks between starting and finishing a DNS diagnostics probe. - - - - - ericorth@chromium.org - src/net/OWNERS - Result of DNS diagnostics probes sent by the probe service. - - - - panicker@chromium.org - - Records result of invoking beforeunload handler, that determines whether to - show the dialog. - - - - - hajimehoshi@chromium.org - keishi@chromium.org - - Records the GC count between the time when the document is shut down and and - the time when the document is actually destroyed. This only counts documents - that are destroyed before the process dies. - - - - - hajimehoshi@chromium.org - keishi@chromium.org - - Records documents that survives some GCs after the document is shut down. - - - - - - Removed 9/2016. - - mariakhomenko@chromium.org - - Recorded only for Android. Records on every metrics upload whether document - mode is enabled. - - - - - sullivan@chromium.org - - Milliseconds spent in beforeunload dialog. Does not include time to process - beforeunload event in JavaScript (see - DocumentEventTiming.BeforeUnloadDuration). Recorded immediately after - closing dialog, upon user confirmation to navigate away from the page. - - - - - panicker@chromium.org - - Microseconds spent in beforeunload. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - panicker@chromium.org - - Microseconds spent in onfreeze. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - panicker@chromium.org - - Microseconds spent in pagehide. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - panicker@chromium.org - - Microseconds spent in vibilitychange (hidden). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - panicker@chromium.org - - Microseconds spent in onresume. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - panicker@chromium.org - - Microseconds spent in unload. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed May 2020. - - pstew@chromium.org - - Chrome OS document scan metric that tracks whether a document scan call to - the image conversion process succeeded. - - - - - fletcherw@chromium.org - bmgordon@chromium.org - project-bolton@google.com - - Chrome OS document scan metric that tracks which SANE backend (effectively a - scanner driver) was used when a scan failed. - - - - - fletcherw@chromium.org - bmgordon@chromium.org - project-bolton@google.com - - Chrome OS document scan metric that tracks which SANE backend (effectively a - scanner driver) that a user requested to use for a scan. - - - - - - Removed July 2020. - - fletcherw@chromium.org - bmgordon@chromium.org - - Chrome OS document scan metric that tracks whether an attempt to scan - succeeded. - - - - - fletcherw@chromium.org - bmgordon@chromium.org - project-bolton@google.com - - Chrome OS document scan metric that tracks which SANE backend (effectively a - scanner driver) was used when a scan succeeded. - - - - - - Removed July 2019. - - nharper@chromium.org - - Tracks whether the "Origin Bound Certs" file exists in a profile. - Logged each time the network context params are created for a profile, which - should happen approximately once per session for a profile. - - - - - - Removed January 2018. - - mattm@chromium.org - Number of certs loaded from domain bound cert database. - - - - - Feature was removed (crbug.com/875053). - - nharper@chromium.org - - The status of loading the Channel ID database from disk. This histogram - records why the database failed to load, or that it loaded successfully. - - - - - - Removed January 2018. - - mattm@chromium.org - Time spent loading domain bound cert database. - - - - - Removed 4/2017. - - mattm@chromium.org - - The size, on disk, of the domain bound cert database as it is being loaded. - - - - - - Feature was removed (crbug.com/875053). - - nharper@chromium.org - - The version number of the Channel ID database (before any migrations are - run). - - - - - - Removed 4/2017. - - mattm@chromium.org - Time spent generating a domain bound cert. - - - - - Removed 4/2017. - - mattm@chromium.org - - Combined time for GetDomainBoundCert retrieval (both synchronous and - asynchronous). - - - - - - Removed 4/2017. - - mattm@chromium.org - - Time for asynchronous retrieval (from the GetDomainBoundCert call until - completion callback is called). - - - - - - Removed 4/2017. - - mattm@chromium.org - Time for synchronous GetDomainBoundCert cert retrieval. - - - - - Removed January 2018. - - mattm@chromium.org - Result of GetDomainBoundCert function. - - - - - Feature was removed (crbug.com/875053). - - mattm@chromium.org - - Whether the domain-bound certs sqlite database was killed succesfully when - an unrecoverable error was detected. - - - - - - Removed January 2018. - - mattm@chromium.org - - Counts of SSL client sockets broken down by support for Domain Bound - Certificates TLS extension. Counts only connections with full handshakes, - resumed sessions are not counted. - - - - - - Removed 4/2017. - - mattm@chromium.org - - Longest time spent by requests waiting for load of domain bound cert - database. - - - - - - Removed 4/2017. - - mattm@chromium.org - - Number of requests that waited for load of domain bound cert database. - - - - - qfiard@google.com - - The distribution over daily active users of Google Search of the ratio of - Google searches in the past day that were issued by the user on a Google - domain that is not the primary one used by the user over the same time - period. - - - - - qfiard@google.com - - The distribution over daily active users of Google Search of the ratio of - Google searches in the past 30 days that were issued by the user on a Google - domain that is not the primary one used by the user over the same time - period. - - - - - qfiard@google.com - - The distribution over daily active users of Google Search of the ratio of - Google searches in the past week that were issued by the user on a Google - domain that is not the primary one used by the user over the same time - period. - - - - - qfiard@google.com - - The distribution over daily active users of Google Search of the ratio of - Google searches in the past two weeks that were issued by the user on a - Google domain that is not the primary one used by the user over the same - time period. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The time between successive Domain Reliability beacons being queued in the - same context. (Can be arbitrarily long if no beacons are queued in a while.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The time between successive Domain Reliability beacons being queued across - all contexts. (Can be arbitrarily long if no beacons are queued in a while.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - Whether a beacon added to a Domain Reliability context was saved to be - uploaded to the collector. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - Whether adding a beacon to a Domain Reliability context caused it to evict - an older beacon to stay within memory limits. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The Chrome error code included in a beacon saved to be uploaded to the - collector. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The Chrome error code included in a beacon with a non-empty server_ip field - saved to be uploaded to the collector. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The upload depth included in a beacon saved to be uploaded to the collector. - (Zero means the beacon was not about a report upload; n+1 means the beacon - was about a report with upload depth n.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - When Domain Reliability receives a valid NEL configuration header for an - origin with Domain Reliability active, whether or not it needed to recreate - the origin's context to apply a changed config. - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The index of the collector that a Domain Reliability upload was sent to. - (Later collectors are only used when earlier collectors have failed.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - After an upload to a collector finishes (successfully or not), the delay - before the scheduler can send another upload to that collector. (If recent - uploads were successful, this will be 0; if not, it will be based on the - BackoffEntry and any Retry-After header received.) - - - - - - Removed 11/2019 for cleanup. https://crbug.com/807144 - - juliatuttle@chromium.org - - The elapsed time between starting and finishing a Domain Reliability upload. - - - - - - Removed 11/2014; see UploadCollectorIndex - - juliatuttle@chromium.org - - Whether a Domain Reliability upload was sent to a collector other than the - first one listed in the config. (This only happens when an upload to the - first collector fails.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The time between successive Domain Reliability uploads being started in the - same context. (Can be arbitrarily long if no beacons are reported in a - while.) - - - - - - Removed November 2017. - - juliatuttle@chromium.org - - The time between successive Domain Reliability uploads being started across - all contexts. (Can be arbitrarily long if no beacons are reported in a - while.) - - - - - - Removed 11/2019 for cleanup. https://crbug.com/807144 - - juliatuttle@chromium.org - - The time from the first beacon in a Domain Reliability upload being recorded - and that upload completing successfully. (Note that if some beacons are - never uploaded successfully, they will not feature in this histogram at - all.) - - - - - - Removed 11/2019 for cleanup. https://crbug.com/807144 - - juliatuttle@chromium.org - - The network error code (or OK if none) returned by the URLFetcher when a - Domain Reliability report is uploaded. - - - - - - Removed 11/2019 for cleanup. https://crbug.com/807144 - - juliatuttle@chromium.org - - The HTTP response code returned by the Domain Reliability collector when a - report is uploaded. - - - - - - Removed 11/2019 for cleanup. https://crbug.com/807144 - - juliatuttle@chromium.org - Whether a Domain Reliability upload succeeded. - - - - - UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. - - mdjones@chromium.org - - Records if the close button was used before or after opening and viewing - Reader Mode content. - - - - - wychen@chromium.org - - The reason to reject distillability at PageDistillableAfterParsing time. - - - - - wychen@chromium.org - - Score of distillability from AdaBoost model, non-mobile-friendly only. The - score shown here is multiplied by 100. - - - - - wychen@chromium.org - - Score of distillability from AdaBoost model, non-mobile-friendly only. The - score shown here is multiplied by 100. - - - - - - Removed 04/2020 because the code to collect this metric has not been called - in months. - - nyquist@chromium.org - - Whether the perceived quality of the distillation of a web page was good. - - - - - mdjones@chromium.org - - "Used" is recorded when the user clicks the infobar to enter - Reader Mode. "Not Used" is recorded when the user clicks the close - button. If there's no user action, nothing is recorded. - - - - - wychen@chromium.org - - Score of long article from AdaBoost model, distillable and - non-mobile-friendly only. The score shown here is multiplied by 100. - - - - - wychen@chromium.org - - Score of long article from AdaBoost model, distillable and - non-mobile-friendly only. The score shown here is multiplied by 100. - - - - - - PageDistillableAfterLoading and PageDistillableAfterParsing provide more - details since 02/2016. - - cjhopman@chromium.org - - Records the "Distillable Type" (not distillable, mobile-friendly - distillable, non-mobile-friendly distillable, etc) for each analyzed page. - - - - - wychen@chromium.org - - Records the "Distillable Type" (mobile-friendly not distillable, - mobile-friendly distillable, non-mobile-friendly not distillable, - non-mobile-friendly distillable) for each analyzed page after loading. - - - - - wychen@chromium.org - - Records the "Distillable Type" (mobile-friendly not distillable, - mobile-friendly distillable, non-mobile-friendly not distillable, - non-mobile-friendly distillable) for each analyzed page after parsing. - - - - - - Not collected anymore. - - cjhopman@chromium.org - - Records the "Distillable Type" (not distillable, mobile-friendly - distillable, non-mobile-friendly distillable, etc) for each distilled page. - - - - - kuan@chromium.org - Records whether a page has distilled data. - - - - katie@chromium.org - gilmanmh@google.com - chrome-a11y-core@google.com - The method a user used to enter reader mode on an article. - - - - katie@chromium.org - gilmanmh@google.com - chrome-a11y-core@google.com - - The method a user used to exit reader mode and return to the original - article. - - - - - mdjones@chromium.org - - Records if the panel became visible at any point after a page was navigated. - - - - - mdjones@chromium.org - - Records the number of words in a distilled page. This only records the first - page of a multi-page article. - - - - - nyquist@chromium.org - - Records the number of words in a distilled page. For articles with multiple - pages, each page is counted separately. - - - - - katie@chromium.org - chrome-a11y-core@chromium.org - - Records the amount of active time a user spent on a distillable page before - switching that page to Reader Mode. Active time is time that the article was - visible, not total time the page was open: the timer is paused when the page - is not visible. This is not recorded when the user opens a distillable page - but does not switch to Reader Mode from that page (via the omnibox icon or - menu option). - - - - - katie@chromium.org - chrome-a11y-core@chromium.org - - Records the amount of active time a user spent on a Reader Mode page. Active - time is the time the Reader Mode page was visible, not the total time the - page was open: the timer is paused when the page is not visible. This is - recorded regardless of how a user enters the page: e.g. using the - forward/back buttons, entering the URL directly, or coming from a - distillable page all start the timer equally. - - - - - yfriedman@chromium.org - - Time spent in DomDistiller's identification of text content. - - - - - yfriedman@chromium.org - Complete time spent in DomDistiller's processing of a page. - - - - wychen@chromium.org - - Time spent in DistillPageImpl(), mostly ExecuteJavaScript(), including - compilation and execution. - - - - - yfriedman@chromium.org - - Time spent in creating DomDistiller's internal representation of the HTML - document. - - - - - yfriedman@chromium.org - - Time spent in DomDistiller's final processing of article content/formatting. - - - - - yfriedman@chromium.org - - Time spent in DomDistiller's processing of article metadata. - - - - - wychen@chromium.org - - Time spent in ExecuteJavaScript() in DomDistiller. It includes JavaScript - code transmission through IPC, parsing, compilation, execution, and - returning the JSON back through IPC. - - - - - - UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. - - wychen@chromium.org - - Records the time from a swipe-up gesture on ReaderModePanel to the first - paint of the empty template. - - - - - wychen@chromium.org - - Records the time from the Reader Mode panel opening to the viewer loaded. - - - - - mdjones@chromium.org - - Records the amount of time a user spent on a Reader Mode Page. - - - - - - UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. - - mdjones@chromium.org - - Records the amount of time between the Reader Mode panel opening and it - closing or returning to the peeking state. - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.clear() or sessionStorage.clear(). - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.getItem() or sessionStorage.getItem(). - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.key() or sessionStorage.key(). - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.length() or sessionStorage.length(). - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.removeItem() or - sessionStorage.removeItem(). - - - - - - Removed 2012. - - michaeln@chromium.org - - Duration to execute localStorage.setItem() or sessionStorage.setItem(). - - - - - - Removed from code 2017-08. - - treib@chromium.org - Outcome of downloading the Doodle config. - - - - - Removed from code 2017-08. - - treib@chromium.org - - The time it took to download the Doodle config. Recorded only if the - download succeeded and the received data was parsed without errors. - - - - - grt@chromium.org - - The number of items within the Cache directory that could not be moved aside - following a downgrade. 0 indicates that the target directory could not be - created. - - - - - grt@chromium.org - - Indicates whether or not moving a user's cache dir following a downgrade - succeeded or failed. - - - - - grt@chromium.org - ydago@chromium.org - - The number of items within from an invalid snapshot directory that could not - be moved. 0 indicates that the target directory could not be created. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not moving an invalid snapshot directory succeeded or - failed. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not cleaning up after a snapshot restoration failure - succeeded or failed. - - - - - grt@chromium.org - ydago@chromium.org - - The number of items within from a snapshot directory that could not be - restored following a downgrade. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not restoring a snapshot of the user data dir succeeded - or failed. - - - - - grt@chromium.org - ydago@chromium.org - - The number of items within the user data directory that could not be - snapshotted following an upgrade. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates the id of an item that failed to be copied when taking a user data - snapshot. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not moving a user data snapshot dir before replacing it - with a newer snapshot succeeded or failed. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not creating a profile directory while creating a user - data snapshot succeeded or failed. - - - - - grt@chromium.org - ydago@chromium.org - - Indicates whether or not creating a snapshot of the user data dir succeeded - or failed. - - - - - grt@chromium.org - - The type of User Data downgrade detected, if any. The "none" - bucket is not reported. - - - - - grt@chromium.org - - The number of items within User Data that could not be moved aside following - a downgrade. - - - - - grt@chromium.org - - Indicates whether or not moving a user's User Data dir following a downgrade - succeeded or failed. - - - - - - Removed in 08/2018. - - dtrainor@chromium.org - The length of downloads for serves that accept byte ranges. - - - - - Removed in 08/2018. - - dtrainor@chromium.org - - The length of downloads for serves that do not specify whether the accept - ranges, or have invalid ranges specified. - - - - - - Removed in 08/2018. - - dtrainor@chromium.org - - The length of downloads for serves that do not accept ranges. - - - - - - Removed January 2017. - - dtrainor@chromium.org - The actual bandwidth (per read) of a download. - - - - dtrainor@chromium.org - Downloads extension API function calls. - - - - dtrainor@chromium.org - - Time taken to invoke IAttachmentExecute::Save() excluding the time taken to - instantiate CLSID_AttachmentServices. - - - - - - Removed in 08/2018. - - dtrainor@chromium.org - - Result of invoking (or attempting to invoke) Windows Attachment Services API - via IAttachmentExecute::Save(). - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Disk bandwidth (defined as total bytes divided by the amount of time blocked - on write or close on the file descriptor) seen for a single download. - - - - - dtrainor@chromium.org - - Overall bandwidth seen for the download. Note that this is measured at the - point at which the file is written, and so will not take into account the - time costs of activities that occur after file write is completed (e.g. safe - browsing scanning). - - - - - - Removed January 2017. - - dtrainor@chromium.org - - The percentage of the potential bandwidth actually used (per read) of a - download. An entry of 100% implies that Chrome was the limiting factor in - download speed. - - - - - - Removed April 2017. - - qinmin@chromium.org - - For parallel downloading, average disk bandwidth seen when only 1 stream is - actively downloading the content. Other streams may have already finished, - or have not been created yet. If a download was ever paused, this is not - recorded. - - - - - - Removed April 2017. - - qinmin@chromium.org - - For parallel downloading, average disk bandwidth seen when parallel streams - are downloading the content. If a download was ever paused, this is not - recorded. - - - - - - Removed 02/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Records the number of cancelled download that are cleaned up from the - history, after loading all the downloads from the history DB on startup. - - - - - xingliu@chromium.org - clank-downloads@google.com - Records why the download is canceled. - - - - - Removed 1/2017. - - dtrainor@chromium.org - - The number of downloads in history at the time it is cleared. - - - - - - Deprecated 04/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Network connection information about the download, recorded after the - network response is received. - - - - - - Deprecated 02/2020. - - dtrainor@chromium.org - - Content-Disposition header features. The presence of a Content-Disposition - header, use of 'filename' and 'filename*' parameters, and string encoding - schemes are counted for each unthrottled download. The total number - downloads is Download.Counts[5] (Initiated and Unthrottled). - - - - - - Deprecated 02/2020. - - qinmin@chromium.org - - File size calculated from the content-length header of successfully - completed Parallelizable downloads. - - - - - - Removed 03/2017, and replaced by Download.Start.ContentType. - - dtrainor@chromium.org - Content types that are downloaded. - - - - xingliu@chromium.org - Types of audio files that are downloaded. - - - - - - dtrainor@chromium.org - Types of images that are downloaded. - - - - xingliu@chromium.org - Types of text files that are downloaded. - - - - - - xingliu@chromium.org - Types of video files that are downloaded. - - - - - - xingliu@chromium.org - - Various individual counts in the download system; see DownloadCountType for - details. - - - - - dtrainor@chromium.org - - Various individual counts in the download system, for example the number of - downloads blocked by throttling from the DownloadRequestLimiter. - - - - - - Removed in 01/2020. - - dtrainor@chromium.org - felt@chromium.org - - User chose to save a download which was marked dangerous. Grouped by the - type of danger. - - - - - - Removed in 01/2020. - - dtrainor@chromium.org - felt@chromium.org - - User chose to save a download which was marked DANGEROUS_FILE. Grouped by - the type of file. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - felt@chromium.org - - A download which was marked DANGEROUS_FILE was discarded without the user - directly choosing, because the browser was closed. Grouped by the file - extension. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@chromium.org - - User chose to save a download which was marked DANGEROUS_FILE. Grouped by - the type of file. - - - - - - Removed in M77 since the data was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates why a download is marked as DANGEROUS_FILE. Grouped by reason, - such as Safe Browsing (SB) service is not available, and SB returns UNKOWN - or SAFE verdict. The sum of all reasons should roughly equal to the - DANGEROUS_FILE bucket count in Download.DownloadWarningShown. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - felt@chromium.org - - User chose to discard a download which was marked DANGEROUS_FILE. Grouped by - the file extension. - - - - - - Removed in 08/2018. - - asanka@chromium.org - Time taken to create a single download in the history DB. - - - - xingliu@chromium.org - - Records whether the download database is available when database startup - completes, before starting any pending downloads. If the database is - available, it will provide the next download id. Or no download history will - be persisted. - - - - - - Removed in 08/2018. - - asanka@chromium.org - Time taken to query all downloads from history DB. - - - - - Removed in 08/2018. - - asanka@chromium.org - Time taken to update a single download in the history DB. - - - - - Removed in 07/2019. - - qinmin@chromium.org - - Whether a download can be found for a download slice in the DB. This - histogram is recorded for each download slice row every time the database is - loaded. - - - - - - Removed in 08/2018. - - asanka@chromium.org - Reason for dropping a record read in from the DB. - - - - - Removed in 08/2018. - - asanka@chromium.org - Number of downloads removed from the history at once. - - - - - Removed 2/2017 - - dtrainor@chromium.org - - How long it took to delete a batch of downloads from history. - - - - - - Removed 2/2017 - - dtrainor@chromium.org - - How long it took to delete some downloads from history, per download. - - - - - xingliu@chromium.org - - How long users keep downloaded audio files on disk. Recorded when the - downloaded file is deleted. - - - - - xingliu@chromium.org - - How long users keep downloaded video files on disk. Recorded when the - downloaded file is deleted. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - felt@chromium.org - - A download which was marked dangerous was discarded without the user - directly choosing, because the browser was closed. Grouped by the type of - danger. - - - - - - Removed 1/2017. - - dtrainor@chromium.org - - The percentage of the available disk bandwidth that was used by the - download. 100% indicates that the disk bandwidth was the limiting factor for - the download. - - - - - dtrainor@chromium.org - User actions in chrome://downloads - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records when user is shown the download danger prompt while attempting to - recover a blocked download from chrome://downloads, grouped by the type of - file. - - - - - qinmin@chromium.org - dtrainor@chromium.org - - Records the delay of creating non-incognito download manager after the - download system is initialized. - - - - - qinmin@chromium.org - dtrainor@chromium.org - - Records the approximate memory usage from non-incognito download manager, - after all downloads are loaded. - - - - - - - dtrainor@chromium.org - The size of successfully completed downloads. - - - - - Replaced 03/2020 by Download.ShowedDownloadWarning due to this one expiring. - - dtrainor@chromium.org - - A download warning was shown in the shelf. Note that some downloads may not - be shown on the shelf, e.g., if chrome://downloads is already open when the - download completes, or if an extension is using the downloads API. Grouped - by the type of danger. - - - - - qinmin@chromium.org - dtrainor@chromium.org - - The total number of download IDs that are duplicate in the in-progress - downloads DB, capped at 10. - - - - - - Removed in 09/2020. - - qinmin@chromium.org - - Estimated time saved on a download when parallel downloading is enabled. To - estimate this, the time spent on a download is classified into two - categories. The fist category has only one stream active, while other - streams are either finished, not started, or failed. And the second category - has multiple streams active. By calculating the average bandwidth during the - first category, a rough estimation on the time it will save is obtained by - assuming all the bytes downloaded during the second category are downloaded - by only one stream. If a download is ever paused, this is not recorded. - - - - - - Removed in 07/2019. - - qinmin@chromium.org - - Similar to Download.EstimatedTimeSavedWithParallelDownload, but this - estimates the time wasted on a download when parallel downloading is - enabled. - - - - - - Removed in 06/2020. - - dtrainor@chromium.org - - Whether the user enables dangerous download feedback reporting after viewing - the opt-in dialog. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - How the user interacts with the file chooser when doing a "Save - As" for non-full-page saves. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The amount of time in milliseconds the file thread blocks for each set of - buffers drained from the incoming pipe (ms). - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The number of buffers in a call to DownloadManager::UpdateDownload. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The time between a download completing and the file being opened for the - first time. - - - - - - Removed 11/2018. - - yaoxia@chromium.org - - The type of frame in which a download occurs and whether the download - involves a transient user gesture. It is only recorded for downloads - originated from navigations or from HTML anchor download attributes. - - - - - - Removed in 04/2020. - - dtrainor@chromium.org - - The number of items in the History database, at the time a new download is - recorded. - - - - - - Removed in 04/2020. - - dtrainor@chromium.org - - The number of items in the History database, at the time a new download is - recorded. Higher maximum, more buckets than Download.HistorySize. - - - - - - - xingliu@chromium.org - The count of HTTP Response codes for download requests. - - - - meacer@chromium.org - jdeblasio@chromium.org - - Records the type of the window.opener origin when a download is initiated in - a tab by that tab's opener (crbug.com/121259). - - - - - qinmin@chromium.org - - Various individual counts related to in-progress download DB. - - - - - jdeblasio@chromium.org - estark@chromium.org - cthomp@chromium.org - - Records file extension of download to support analysis for mixed content - file download blocking. - - - - - jdeblasio@chromium.org - estark@chromium.org - cthomp@chromium.org - - Records security state of downloads to support analysis for mixed content - file download blocking. - - - - - jdeblasio@chromium.org - estark@chromium.org - cthomp@chromium.org - - Records mime-type of download to support analysis for mixed content file - download blocking. This is a temporary metric for investigating differences - in metrics. - - - - - - Checked on 06/2020 and no longer logged. - - dtrainor@chromium.org - - Positive net error code that caused a download to be interrupted at the - *end* of a download (when the number of bytes is known). This is only - triggered when the total content size is known before any bytes are - transferred, such as when a Content-Length header is supplied. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - - The reason that a download was interrupted at the *end* of a download (when - the number of bytes is known). This is only triggered when the total content - size is known before any bytes are transferred, such as when a - Content-Length header is supplied. - - - - - - Removed in 02/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Records the number of interrupted download that are cleaned up from the - history, after loading all the downloads from the history DB on startup. - - - - - - Checked on 06/2020 and no longer logged. - - dtrainor@chromium.org - - Positive net error code that caused a download to be interrupted. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - - The total number of bytes minus the received number of bytes at the time - that a download is interrupted. This is only triggered when the total - content size is known before any bytes are transferred, such as when a - Content-Length header is supplied. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - The reason that a download was interrupted. - - - - - Removed in 07/2019. - - dtrainor@chromium.org - - The number of kilobytes received for a download at the time it is - interrupted. - - - - - - Deprecated 02/2020. - - dtrainor@chromium.org - - The reported total size in kilobytes for a download at the time it is - interrupted. This is essentially the size reported by the Content-Length - header. If no size is specified up-front, it is not recorded in the - histogram. For example, a download transferred with chunked encoding will - not be recorded. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - - The excessive number of bytes which have been received at the time that a - download is interrupted. This is only triggered when the total content size - is known before any bytes are transferred, such as when a Content-Length - header is supplied. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - True if the size of an interrupted download is unknown, false if it is - known. - - - - - mahmadi@chromium.org - - Logged at different stages of downloading a USDZ MIME type AR model on iOS. - - - - - eugenebut@chromium.org - - The action that a user takes on a file after it has been successfully - downloaded on iOS. - - - - - eugenebut@chromium.org - mrefaat@chromium.org - - Positive net error codes that happens in the case of download content fetch - failure. - - - - - eugenebut@chromium.org - stkhapugin@chromium.org - - HTTP status code returned when file download completes on iOS. - - - - - eugenebut@chromium.org - - Logged when the download is completed (successfully or not) or in-progress - download was cancelled because of the app termination. This histogram - includes information whether the download was successful and whether or not - the download task was running while the app was active. - - - - - eugenebut@chromium.org - Result when a user attempts to download a file on iOS. - - - - ewannpv@chromium.org - eugenebut@chromium.org - - Result when a user attempts to present the download UI on iOS. Looged when - download is created. - - - - - ewannpv@chromium.org - eugenebut@chromium.org - - Result when the download UI is prexsented on iOS. Values indicate if Google - Drive is installed and whether or not Install Google Drive promo was shown. - Logged when download is updated. - - - - - - Removed in 12/2019 replaced by IOSDownloadFileUIGoogleDrive's histogram. - - eugenebut@chromium.org - pkl@chromium.org - - Logged when the download was successfully completed. Bool value indicates - whether or not Install Google Drive promo was shown to the user. - - - - - eugenebut@chromium.org - - MIME type of a download response. Logged when the download UI was offered by - the browser to the user. - - - - - eugenebut@chromium.org - - Result when a user attempts to download a PassKit file on iOS. - - - - - eugenebut@chromium.org - sdefresne@chromium.org - - The user discarded in-progress download and replaced with the new one. Only - recorded after the user interacts with a dialog offering the choice between - replacing an in-progress download versus downloading separately to a new - filename. - - - - - eugenebut@chromium.org - sdefresne@chromium.org - Result of an attempt to present Add Passes dialog on iOS. - - - - mahmadi@chromium.org - - Result of an attempt to present a USDZ MIME type AR model on iOS. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records events for download later feature in download core code. - - - - - xingliu@chromium.org - clank-downloads@google.com - - The size of downloads when the user tries to download at a scheduled time. - Recorded when the positive button in download later dialog is clicked. - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The user selection in the download later dialog. Recorded when the user - starts a download, or clicking the change button on download infobar and - download home UI. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records events for download later feature in download Android UI. - - - - - - Removed as of 01/2019. - - yaoxia@chromium.org - - Whether the main frame download involves a transient user gesture. It is - only recorded for downloads originated from navigations or from HTML anchor - download attributes. - - - - - - Removed as of 03/2019. - - yaoxia@chromium.org - - For a download that occurs in top frame, record whether the frame is - sandboxed and whether the download involves a transient user gesture. It is - only recorded for downloads originated from navigations or from HTML anchor - download attributes. - - - - - - Removed as of 08/2019. - - dtrainor@chromium.org - felt@chromium.org - - A download has been marked as malicious. Grouped by the type of danger. Each - download can only be recorded once; it will be labeled with the first type - of danger spotted. - - - - - - Removed in 04/2019 after network service is enabled by default. Use - Download.MapErrorNetworkFailed.NetworkService instead. - - dtrainor@chromium.org - - Network error that produced a DOWNLOAD_INTERRUPT_REASON_NETWORK_FAILED - result in DownloadResourceHandler::OnResponseCompleted(). - - - - - - Removed as of 08/2020. - - dtrainor@chromium.org - qinmin@chromium.org - - Network error that produced a DOWNLOAD_INTERRUPT_REASON_NETWORK_FAILED - result in DownloadResourceHandler::OnResponseCompleted(). Recorded when - running with the network service enabled. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Windows error that produced a DOWNLOAD_INTERRUPT_REASON_ACCESS_DENIED result - in MapShFileOperationCodes(). - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_FAILED result - in MapShFileOperationCodes(). - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_TRANSIENT_ERROR - result in MapShFileOperationCodes(). - - - - - - - dtrainor@chromium.org - qinmin@chromium.org - xingliu@chromium.org - Records events for local media metadata parsing. - - - - - Removed July 2019. - - xingliu@chromium.org - - Records the duration to successfully complete the media file parsing. - - - - - - - dtrainor@chromium.org - qinmin@chromium.org - xingliu@chromium.org - - Records events when using media parser to analyze local media files. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - Network connection type when a download is completed. - - - - - - dtrainor@chromium.org - xingliu@chromium.org - Network connection type when starting a new download. - - - - - Removed in 08/2018. - - asanka@chromium.org - - Percentage of DownloadItem::Observer::OnDownloadUpdated events that - signified a change in the extension API representation of the download. - - - - - - - dtrainor@chromium.org - chrome-analysis-team@google.com - - Invocation count for methods of opening a download. For some file types, - Chrome defaults to opening the file in the browser instead of invoking the - system handler. The user has the option of overriding this behavior. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - dtrainor@chromium.org - The number of unopened downloads, when one is opened. - - - - - Deprecated 02/2020. - - dtrainor@chromium.org - - The time between a download completing and the file being opened. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Changes observed when a response is received for a full download resumption - request. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Changes observed when a response is received for a partial (byte-range) - download resumption request. - - - - - - Removed 08/2020 - - dtrainor@chromium.org - - The core page transition type for navigation initiated downloads. Not - recorded for programmatic downloads. This metric is recorded when the - response headers were received and processed for a download. The number of - samples here should correspond to Download.Counts[8] (Started) - - (programmatic downloads that don't have a page transition type). - - - - - - Removed August 2018. - - xingliu@chromium.org - - Records the ratio of parallel streams bandwidth to single stream bandwidth - in parallel download. - - - - - xingliu@chromium.org - - When parallel downloading feature is enabled, a download may be created as - parallel download or fall back to normal download based on various factors. - Records the total number of parallel and non-parallel downloads created when - parallel downloading feature is enabled. Also records the reason why a - parallel download falls back to normal download. The reasons are not - mutually exclusive. - - - - - qinmin@chromium.org - xingliu@chromium.org - - Records the received failure reason after sending a parallel download - request. - - - - - - Removed in 07/2019. - - qinmin@chromium.org - - Records the remaining download time when building parallel requests. - - - - - - Removed August 2018. - - xingliu@chromium.org - - Records the ratio of the actual total time of the download to the total time - without parallel streams. The total time without parallel streams is - calculated as the size of the file divided by the single stream bandwidth. - - - - - xingliu@chromium.org - - Records if the byte stream reader of a subsequent request is successfully - added to the download sink. - - - - - xingliu@chromium.org - - The total number of requests sent for a parallel download, including the - initial request. - - - - - xingliu@chromium.org - clank-downloads@google.com - The download time for a parallelizable download. - - - - xingliu@chromium.org - clank-downloads@google.com - The download size of a parallelizable download. - - - - qinmin@chromium.org - - For parallelizable download, average disk bandwidth seen for different - settings. If a download was ever paused, this is not recorded. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The download path generation behavior which happens before download path - validation in download target determination process. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The download path validation result before the final download target is - determined. - - - - - - Removed January 2017. - - dtrainor@chromium.org - - The maximum bandwidth (per read) that Chrome could have provided for the - download. If the actual bandwidth equals the potential bandwidth, that means - that Chrome was the limiting factor for download bandwidth. - - - - - pmonette@chromium.org - alewoolf@microsoft.com - - Whether a connection error has happened for the QuarantineService. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The percentage of the lifetime of the DownloadResourceHandler for which it - was blocked by downstream flow control. 0% indicates that the network - bandwidth was the limiting factor for the download. - - - - - calamity@chromium.org - dbeam@chromium.org - - Records the time taken to load the downloads Web UI and render (at least) a - screen full of items. This is roughly equivalent to 'time to first - meaningful paint' for the downloads page. - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Records whenever max auto-resumption limit was reached for a download. - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Records the last interrupt reason for this download when the download - reaches auto-resumption limit. - - - - - shaktisahu@chromium.org - clank-downloads@google.com - Records the last interrupt reason for this download. - - - - shaktisahu@chromium.org - clank-downloads@google.com - Records whether a resumption was due to user. - - - - - Removed in 08/2019. - - qinmin@chromium.org - xingliu@chromium.org - - Records the interrupt reason after download is resumed after a content - length mismatch error. - - - - - - Removed in 04/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Records whether strong validators are present when download completes. - - - - - - Removed in 09/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Records counts related to download restarting from the beginning during - resumption. - - - - - qinmin@chromium.org - xingliu@chromium.org - - Records the interrupt reason when download is restarting from the beginning - during resumption. - - - - - - Removed in 04/2020. - - qinmin@chromium.org - xingliu@chromium.org - - Records whether strong validators are present when download is resumed. - - - - - dtrainor@chromium.org - - Events (e.g. Started, Cancelled, Finished, Write to Completed file, Write to - Failed file) occuring within the state machine of a SavePackage operation. - - - - - - Deprecated 05/2020. - - - - dtrainor@chromium.org - mheikal@chromium.org - hanxi@chromium.org - - The number of times full browser mode is requested to be loaded by a - DeferredClientWrapper. This is recorded when a DeferredClientWrapper needs - to inflate the underlying client while the browser is running in reduced - mode. DeferredClientWrapper inflates the underlying client for any - non-trivial method call on DeferredClientWrapper. - - - - - - - xingliu@chromium.org - clank-downloads@google.com - Records a failed database operation. - - - - - - xingliu@chromium.org - clank-downloads@google.com - Records a successful database operation. - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The total number of database records used by download service, and the - number of records in each entry state. - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The interrupt reason for failed downloads in download service. - - - - - dtrainor@chromium.org - xingliu@chromium.org - An action the download service took on an active download. - - - - - Deprecated 02/2020. - - dtrainor@chromium.org - - Records how many resumptions have taken place at the time of resumption for - a download in the Download Service. This differs from - Download.Service.Entry.RetryCount, which records restarts. - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records how many attempts have taken place at the time of a retry for a - download in the Download Service. This differs from - Download.Service.Entry.ResumptionCount, which records resumptions not - complete restarts. - - - - - - Removed as of 01/2020. - - shaktisahu@chromium.org - - The number of times download service tried to delete the download file - before successfully deleting it. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The number of files that have been deleted by external application or the - user, when performing clean up tasks in download service. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The number of failed file deletion attempts, when performing clean up tasks - in download service. - - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The number of files successfully deleted, when performing clean up tasks in - download service. - - - - - - - xingliu@chromium.org - - The error code when failed to create the download directory. - - - - - - Removed 08/2020 - - xingliu@chromium.org - - The percentage of disk space used by download service files. Recorded during - initialization of the file monitor. - - - - - xingliu@chromium.org - - The percentage of free disk space to total disk space. Recorded during - initialization of the file monitor. - - - - - - - xingliu@chromium.org - - The lifestime of a download file, which begins from the download completion - to the file being deleted by the clean up task. - - - - - - Removed 08/2020 - - - - xingliu@chromium.org - - Records if the final file path has been renamed by low level download - library after the download is successfully completed. - - - - - - Removed as of 08/2019. - - - - xingliu@chromium.org - - The file size of completed download, including failed downloads. - - - - - - Removed in 09/2019. - - dtrainor@chromium.org - xingliu@chromium.org - - Records if a completed download service entry was sent to a client with a - hash or not. - - - - - - - xingliu@chromium.org - The time to complete the download in download service. - - - - xingliu@chromium.org - The completion type for downloads in download service. - - - - - - shaktisahu@chromium.org - - The reason for suspending a download right after the upload data is received - from the client. Every pause will result in two entries in the histogram: - ANY and a more specific reason. - - - - - - - shaktisahu@chromium.org - - The reason for pausing an in-progress download. Every pause will result in - two entries in the histogram: ANY and a more specific reason. - - - - - - Removed 08/2020 - - xingliu@chromium.org - - The state that the entry transitions to when recovery operation happens. - - - - - - Removed in 06/2019 in Issue 975678. - - xingliu@chromium.org - The battery requirement of the download request. - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - Records the API calls on download service. - - - - - Removed in 06/2019 in Issue 975678. - - xingliu@chromium.org - The network requirement of the download request. - - - - - Removed in 06/2019 in Issue 975678. - - xingliu@chromium.org - The priority of the download request. - - - - - Removed 08/2020 - - - - xingliu@chromium.org - The start response of download attempts. - - - - - Download client api no longer expects a repsponse from the client when a - download is started. - - - - xingliu@chromium.org - The start result of download attempts. - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - The start up result of the download service. - - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The platform background tasks used by download service will invoke native - functions after being scheduled. The tasks may be aborted or canceled. This - metric records the status of background tasks when native functions are - invoked. - - - - - shaktisahu@chromium.org - - Records if the entry has been deleted for some reason while we are waiting - for the client to respond with the upload data. - - - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - The download service uses a single code path for both downloading and - uploading data. This metric records whether a given request includes upload - data. It is recorded upon starting a download or upload, immediately after - the client indicates whether the request includes upload data. - - - - - sdy@chromium.org - - Events related to dragging a completed download from the shelf, which - represents dragging a reference to the downloaded file. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The number of download items in progress on the shelf when it closes - automatically. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The number of download items in progress on the shelf when the user closes - it. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The number of download items on the shelf when it closes automatically. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - The number of download items on the shelf when the user closes it. - - - - - dtrainor@chromium.org - - User saw the confirm prompt to save a download which was marked dangerous. - Grouped by the type of danger. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@chromium.org - - A download warning was shown in the shelf. Note that some downloads may not - be shown on the shelf, e.g., if chrome://downloads is already open when the - download completes, or if an extension is using the downloads API. Grouped - by the type of danger. - - - - - - Removed 1/2018, integrated into Download.Counts.DOWNLOAD_TRIGGERED_COUNT - - xingliu@chromium.org - - The initiation source (if initiated within the content layer of chrome) for - a download. - - - - - - - xingliu@chromium.org - clank-downloads@google.com - - The initiation source (if initiated within the above-content layer of - chrome) for a download. - - - - - shaktisahu@chromium.org - Content types of the downloads. - - - - - Removed in 04/2020. Superseded by mixed download metrics under - Download.InsecureBlocking. - - cthomp@chromium.org - estark@chromium.org - - The content type of a download, for downloads where the final resolved URL - or any redirect before the final URL are insecure. To normalize these - numbers, divide the counts by the counts of Download.Start.ContentType (to - measure the proportion for each content type downloaded insecurely) or by - the sum of Download.Start.ContentType (to measure the proportion of a - particular insecure download content type over all downloads). - - - - - shaktisahu@chromium.org - clank-downloads@google.com - - Content types of the downloads that are started in non-incognito profile. - - - - - - Removed in 04/2020. Superseded by mixed download metrics under - Download.InsecureBlocking. - - cthomp@chromium.org - estark@chromium.org - - The content type of a download, for downloads where the final resolved URL - and all redirects before the final URL are secure. To normalize these - numbers, divide the counts by the counts of Download.Start.ContentType (to - measure the proportion for each content type downloaded securely) or by the - sum of Download.Start.ContentType (to measure the proportion of a particular - secure download content type over all downloads). - - - - - - Removed as of 03/2019. - - yaoxia@chromium.org - - For a download that occurs in subframe, record whether the frame is - sandboxed, whether the origin is same to the top frame, whether it's an ad - subframe, and whether the download involves a transient user gesture. It is - only recorded for downloads originated from navigations or from HTML anchor - download attributes. - - - - - - Removed in M77 since the data was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The connection security state of a download, indicating whether its final - resolved url and the redirects before final url are secure. - - - - - - Removed in 08/2018. - - asanka@chromium.org - Time between the start of a download and its completion. - - - - - Removed in 08/2018. - - asanka@chromium.org - - Time elapsed until a retried download file rename operation failed for the - last time after the initial rename failed. - - - - - - Removed in 08/2018. - - asanka@chromium.org - - Time elapsed until a retried download file rename operation succeeded after - the initial rename failed. - - - - - - Removed in 07/2019. - - dtrainor@chromium.org - felt@chromium.org - - User chose to discard a download which was marked dangerous. Grouped by the - type of danger. - - - - - drubery@chromium.org - chrome-safebrowsing-team@chromium.org - - User chose to save a download which was marked dangerous. Grouped by the - type of danger. - - - - - - - dtrainor@chromium.org - qinmin@chromium.org - xingliu@chromium.org - Records events for local video thumbnail retrieval. - - - - dtrainor@chromium.org - qinmin@chromium.org - Records the OS error code when moving a file on windows. - - - - - Removed 1/2017 - - dtrainor@chromium.org - - The number of iterations for the write loop in BaseFile::AppendDataTofile(). - - - - - - Removed 1/2017 - - dtrainor@chromium.org - The write size for calls to BaseFile::AppendDataTofile(). - - - - - Removed 2/2018 - - digit@chromium.org - - The time to succesfully download and install the DownloadableStrings - component on Android. - - - - - - Removed 2/2018 - - digit@chromium.org - - The mobile country code (MCC) of the device's SIM card, if available (in the - [200..999] range), or 0 for "undetermined". This is collected on - Chrome startup. For devices with several SIM cards, this only reports the - code of the SIM card in use during startup. - - - - - - Removed 2/2018 - - digit@chromium.org - - The status code returned after trying to install and update the - DownloadableStrings component. - - - - - - Removed 2/2018 - - digit@chromium.org - - The timeout reported by the component updater when trying to install the - DownloadableStrings component fails with a specific error. - - - - - - Obsolete 07/2019 as DriveFS implementation obsoletes this metric. - - hirono@chromium.org - Respose code of batch upload request. - - - - - Removed 8/2013. - - joshwoodward@google.com - Status of drive cache metadata database open. - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Time spent to load the delta change list information from the server. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Time spent to load the list of files in a single directory from Google Drive - server. - - - - - - This was a temporary histogram for bug http://crbug.com/229650 that has been - closed. - - mtomasz@chromium.org - - Sizes of files being downloaded from Drive. Temporary histogram for - gathering data for http://crbug.com/229650. - - - - - - Removed 12/2013 due to the UMA stat bucket layout change. We'll use - Drive.FullFeedLoadTime instead. - - joshwoodward@google.com - - Time spent to load the entire file system information from the server - - - - - - Removed 10/2012. - - joshwoodward@google.com - - Provides breakdown of specific formats for hosted documents. Recorded when - feed is loaded from the server. - - - - - - Removed 10/2012. - - joshwoodward@google.com - - Provides breakdown of specific file formats for regular files. Recorded when - feed is loaded from the server. - - - - - - Obsolete 02/2019 as DriveFS implementation obsoletes this metric. - - mtomasz@chromium.org - - Error codes returned by the Drive API for files list requests executed via - the FilesListRequestRunner class. - - - - - - Obsolete 02/2019 as DriveFS implementation obsoletes this metric. - - mtomasz@chromium.org - - Maximum number of results for each files list request using the Drive API. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Time spent to load the entire file system information from the server - - - - - - Deperecated 12/2013 since it did not record meaningful information. - Drive.DirectoryFeedLoadTime should be checked for measuring the time until - the user sees the first response of file lists. - - joshwoodward@google.com - - Time spent to load the initial part of the file system information from the - server - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - Result of drive resource metadata database initialization. - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Result of attempt to open existing drive resource metadata database. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Reason of drive resource metadata database validity check failure. Recorded - when the validity check fails during Drive metadata initialization triggered - by profile initialization. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Version number of drive resource metadata DB found on the disk before - checking whether it should be upgraded. Recorded during Drive metadata - initialization triggered by profile initialization. - - - - - - Obsolete 08/2019. Most migrations are complete, we no longer need this. - - dats@chromium.org - sammc@chromium.org - - Records the number of dirty (unsynced) files migrated from legacy Drive to - DriveFs. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Number of files recovered from Drive cache directory. Recorded when file - recovery takes place after metadata DB corruption is found during metadata - DB initialization. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive - is first accessed. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Number of regualr files on Drive. Logged when Drive is first accessed. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Number of total files (regualr files + hosted documents) on Drive. Logged - when Drive is first accessed. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Tracks whether the push notification is initially enabled for Drive. - Recorded when the first notification is processed. Notification is emulated - by polling if the push notication is disabled. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Tracks whether the push notification request is registered correctly for - Drive. Recorded when the push notification manager is initialized. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Time spent to perform an incremental search for auto completion of files on - Drive. This time is collected for every partial query the user types for - auto completion. For instance, if the user types "faq", - incremental searches are performed for "f", "fa", and - "faq" respectively. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - Total file count contained in a drive batch upload request. - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - Total file size contained in a drive batch upload request. - - - - - This was a temporary histogram for bug http://crbug.com/229650 that has been - closed. - - mtomasz@chromium.org - - Number of jobs which have to be completed before a newly added download or - download from or to Drive is requested. Temporary histogram for gathering - data for http://crbug.com/229650. - - - - - - Obsolete 04/2019 as DriveFS implementation obsoletes this metric. - - slangley@chromium.org - weifangsun@chromium.org - - Upload protocol for each file. e.g. Batch upload including 5 files triggers - the metric 5 times. - - - - - - This was a temporary histogram for bug http://crbug.com/229650 that has been - closed. - - mtomasz@chromium.org - - Sizes of files being uploaded to Drive. Temporary histogram for gathering - data for http://crbug.com/229650. - - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to launch Google Drive for the first time. - - - - - dats@chromium.org - sammc@chromium.org - Records outcomes of attempts to mount Google Drive. - - - - dats@chromium.org - sammc@chromium.org - How long did it take to mount Google Drive. - - - - dats@chromium.org - sammc@chromium.org - Records outcomes of attempts to unmount Google Drive. - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to perform a lookup of pinned files in local Google - Drive cache. - - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to perform a search of shared files in local Google - Drive cache. - - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to search a title in local Google Drive cache. - - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to perform a search of shared files in online Google - Drive. - - - - - dats@chromium.org - sammc@chromium.org - - How long did it take to perform a search in online Google Drive. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Outcome of enabling Google Drive offline mode automatically when a user - first logs into a Chrome OS device. This process involves opening a hidden - web page in the context of the Google Drive hosted app to perform the - initialization of offline mode. - - - - - andrescj@chromium.org - mcasas@chromium.org - chromeos-gfx@google.com - - Number of bits per channel described by a parsed EDID blob. This UMA is - recorded whenever the color space is extracted from an EDID blob. - - - - - - Converted to DCHECK in 08/2020. If EDID property is unset, blob is always - NULL. - - andrescj@chromium.org - mcasas@chromium.org - chromeos-gfx@google.com - - True when an EDID blob is detected and is empty. This UMA is recorded - whenever we attempt to parse the EDID from a display. - - - - - andrescj@chromium.org - mcasas@chromium.org - chromeos-gfx@google.com - - Whether an EDID blob was detected. This UMA is recorded whenever we attempt - to parse the EDID from a display. - - - - - andrescj@chromium.org - mcasas@chromium.org - chromeos-gfx@google.com - - Whether a EDID blob contained an HDR transfer function (e.g. SMPT SE2084 or - HLG). This UMA is recorded whenever the color space is extracted from an - EDID blob. - - - - - andrescj@chromium.org - mcasas@chromium.org - chromeos-gfx@google.com - - When attempting to get the color space from an EDID blob, whether the sanity - checks passed (and if not, which check failed). This UMA is recorded - whenever the color space is extracted from an EDID blob. - - - - - - Removed as of 03/2018. - - joshwoodward@google.com - isherman@chromium.org - - When Easy Unlock attempts to authenticate the secure connection between a - Chromebook (or other Chrome device) and an Android phone, whether the - authentication succeeded. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Upon a successful Smart Lock unlock or signin, records whether the user's - phone was locked during any point while the lock screen was up. This can be - used to get a sense for whether users are using Smart Lock for Chromebook - without something like Smart Lock for Android to keep their phones unlocked. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Measures the use of Smart Lock on the sign-in screen: records whether a - Smart Lock login succeeded or failed; or if a password fallback was used, - the reason why. Recorded upon a login attempt for users who have the Smart - Lock feature enabled. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Measures the time elapsed between the user focusing their user pod and - signing in using Smart Lock. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Measures the use of Smart Lock on the lock screen: records whether a Smart - Lock unlock attempt succeeded or failed; or if a password fallback was used, - the reason why. Recorded upon an unlock attempt for users who have the Smart - Lock feature enabled. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Measures the time elapsed between the lock screen being shown and the user - unlocking the device using Smart Lock. The lock screen is typically shown - when the user opens their Chromebook's lid (or otherwise wakes the - computer), but can also be shown when the user manually locks the device. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The hash of the phone model used to successfully sign in or unlock using - Smart Lock. - -
- This hash is calculated by taking the first 4 bytes of the MD5 hash of the - device model. -
- - - - hansberry@chromium.org - better-together-dev@google.com - - Measures the exponentially weighted rolling average of the received signal - strength indicator (RSSI) of the phone when the user successfully unlocks or - signs in using Smart Lock. - -
- The exponentially weighted averaging formula is: - - rollingRssi = (1 - weight) * rollingRssi + weight * currentRssi; - - RSSI readings are inherently noisy, so this averaging gives a smoothed RSSI - value to work with as a heuristic for proximity. - - If no RSSI was read, then a sentinel value of 127 will be recorded. -
- - - - - Removed as of 11/2018. - - tengs@chromium.org - hansberry@chromium.org - - Measures the time delta in milliseconds since the last zero RSSI value was - read to when the user successfully unlocks or signs in using Smart Lock. - -
- A zero RSSI value is special because both Bluetooth devices in a connection - attempt to maintain by adjusting their transmit power levels. This time - delta can be used as a possible heuristic to determine that the phone is - close to the local device. - - If no RSSI was read, then an overflow value will be recorded. -
- - - - - Removed as of 11/2018. - - tengs@chromium.org - hansberry@chromium.org - - Measures the difference between the current transmit power and the maximum - transmit power of the local device when the user successfully unlocks or - signs in using Smart Lock. - -
- Devices connected using classic Bluetooth adjust their transmit power - dynamically to optimize power and signal strength. The difference between - the current transmit power and maximum transmit power can be used as a - heurstic to determine if the phone is close to the local device. - - According to the Bluetooth specs, there are three classes of devices, with a - maximum transmit power of 20, 4, and 0 dBm respectively. - - If no transmit power was read, then a sentinel value of 127 will be - recorded. -
- - - - - Removed as of 02/2017. - - bcwhite@chromium.org - - Reports the type of Bluetooth adapter present in the device. - -
- Statistics about what Bluetooth capabilities are available will determine - how the EasyUnlock feature gets developed and deployed across platforms. - - This value is logged only once during the lifetime of the Chrome process, - shortly after it starts up. If a Bluetooth USB adapter is inserted after - that point, the change will not be registered until Chrome restarts. -
- - - - - Removed as of 01/2020. - - hansberry@chromium.org - Button clicked in EasyUnlock app during setup process. - - - - - Removed 02/2015. Replaced by EasyUnlock.Setup.PromoNotificationEvent. - - joshwoodward@google.com - tbarzic@chromium.org - - Tracks events related to notifications used by EasyUnlock feature. For - example a specific EasyUnlock notification being shown or clicked. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Whether a lock screen and a trust agent are enabled on the remote device - (Android phone) for Easy Unlock. Recorded once per status update message - from the remote device. A status update message is expected to be sent once - when the secure channel between the local and the remote device is - established, and also each time the user-presence status changes on the - remote side. - - - - - - Removed as of 01/2020. - - hansberry@chromium.org - - The number of eligible devices that the CryptAuth server returns during the - Smart Lock setup flow. - -
- Note that a single user might report multiple values, for example if they - try to complete the setup flow with a device in airplane mode, and then try - again taking the device out of airplane mode. -
- - - - - Removed as of 01/2020. - - hansberry@chromium.org - - The number of ineligible devices that the CryptAuth server returns during - the Smart Lock setup flow. - -
- Note that a single user might report multiple values, for example if they - try to complete the setup flow with a device in airplane mode, and then try - again taking the device out of airplane mode. -
- - - - - Removed as of 01/2020. - - hansberry@chromium.org - - Whether the user's phone has a secure screen lock installed. Recorded during - Smart Lock setup, when the user's phone first connects to the Chromebook. - - - - - - Removed as of 01/2020. - - hansberry@chromium.org - - Whether the user's phone has a trust agent -- e.g. Smart Lock for Android -- - enabled. Recorded during Smart Lock (for Chrome) setup, when the user's - phone first connects to the Chromebook. - -
- Note that this histogram tracks whether the setting under Settings ~> - Security ~> Trust agents ~> Smart Lock (Google) (or any other trust - agent) is enabled. The Smart Lock trust agent is enabled by default for - users who have ascure lock screen. This metric does _not_ measure whether - users have any Smart Lock trustlets enabled. -
- - - - - Removed as of 01/2020. - - hansberry@chromium.org - - Records the most actionable reason why none of a user's devices were - eligible as unlock keys for Smart Lock. This is recorded during the Smart - Lock setup flow, only if the CryptAuth server returns no eligible devices - for the user. - -
- To be precise, this metric tracks the _least_ actionable _reason_ why the - _most_ actionable _device_ is not eligible as an unlock key. For example, - suppose that the user has 10 ineligible devices returned. This metric tries - to identify the most likely candidate device for use as a Smart Lock key, - and then records the most confounding reason why that device is still not - eligible to be used as an unlock key. -
- - - - - Removed as of 03/2018. - - hansberry@chromium.org - jhawkins@chromium.org - - Records events at each step of the Setup process, when the Setup flow is - initiated without the promotion notification. - - - - - - Removed as of 03/2018. - - hansberry@chromium.org - jhawkins@chromium.org - - Records events at each step of the Setup process, when the Setup flow is - initiated via the promotion notification. - - - - - - Removed as of 01/2020. - - hansberry@chromium.org - - Measures user interactions with the Smart Lock promo notification. - -
- Due to technical limitations of the implementation, it is hard to track - precisely which users opened the setup app as a result of interacting with - the promo notification. This metric measures setup app interactions from all - users who click on the promo notification, and subsequently launch the setup - app. -
- - - - - Removed as of 03/2018. - - joshwoodward@google.com - tbarzic@chromium.org - - The state of EasyUnlock setup when the app window was closed by user. - - - - - - Removed 02/2015; replaced by EasyUnlock.AuthEvent.SignIn. - - hansberry@chromium.org - - Measures the use of Easy sign-in: records whether an Easy sign-in login - succeeded or failed; or if a password fallback was used, the reason why. - Recorded upon a login attempt for users who have the Easy sign-in feature - enabled. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The time it takes after resuming from a suspended state (ie. opening the - Chromebook lid) to when a remote device is connected and a request is made. - Note that it is possible for the remote device not to be present when - resuming from suspend, and the device may be connected at a later time. - Therefore, large values for this metric may not be too meaningful due to - meddling users. - - - - - - Removed as of 01/2020. - - hansberry@chromium.org - - Records when the Easy Unlock trial run is launched, and when the user - attempts to click on the lock icon during the trial run. - -
- If a user clicks on the lock icon more than once, then the "clicked - lock icon" event counter will be incremented more than once as well. - Hence, the "user count" data shows how many users ever clicked on - the lock icon during the trial run. From the raw (non-"user - count") data, we can also see whether users click on the icon multiple - times. -
- - - - - Removed 02/2015; replaced by EasyUnlock.AuthEvent.Unlock. - - joshwoodward@google.com - tbarzic@chromium.org - Screen unlock events detected while EasyUnlock was enabled. - - - - - Removed 03/2016; replaced by - EmbeddedWorkerInstance.Start.SendStartWorker_ExistingProcess and - EmbeddedWorkerInstance.Start.TimeToURLJob_ExistingProcess. - - ksakamoto@chromium.org - - The time taken to allocate a process to start the EmbeddedWorkerInstance. - Recorded when an existing process was used. - - - - - - Removed 03/2016; replaced by - EmbeddedWorkerInstance.Start.SendStartWorker_NewProcess and - EmbeddedWorkerInstance.Start.TimeToURLJob_NewProcess. - - ksakamoto@chromium.org - - The time taken to allocate a process to start the EmbeddedWorkerInstance. - Recorded when a new process was created. - - - - - - Removed as of 05/2015. Replaced by - EmbeddedWorkerInstance.NewProcessAllocation and - EmbeddedWorkerInstance.ExistingProcessAllocation. - - horo@chromium.org - - The time taken to allocate a process to start the EmbeddedWorkerInstance. - - - - - - Removed as of June 2020. If you find it's useful and add the metric again, - please consider using an enum of StartSituation instead of a boolean. - - falken@chromium.org - chrome-worker@google.com - - Whether a new renderer process was created for the EmbeddedWorkerInstance or - existing one was used. Only recorded for installed workers. - - - - - - Removed as of 03/2016. Replaced by - EmbeddedWorkerInstance.Start.TimeToEvaluateScript. - - horo@chromium.org - - The time taken to evaluate the script to start the EmbeddedWorkerInstance. - - - - - - Removed as of 03/2016. Replaced by - EmbeddedWorkerInstance.Start.TimeToLoad_Network. - - horo@chromium.org - - The time taken to load the script file for the EmbeddedWorkerInstance with - network access. - - - - - - Removed as of 03/2016. Replaced by - EmbeddedWorkerInstance.Start.TimeToLoad_HttpCache and - EmbeddedWorkerInstance.Start.TimeToLoad_InstalledScript. - - horo@chromium.org - - The time taken to load the script file for the EmbeddedWorkerInstance - without network access. - - - - - - Removed June 2018 (M69). Replaced with - ServiceWorker.StartTiming.SentStartWorkerToReceivedStartWorker. - - falken@chromium.org - - The time between the browser sending a "start a service worker" - message to the renderer, and the renderer receiving it. This may include - renderer startup time. Only recorded if the high-resolution system clock was - used and deemed consistent across proceses, and the time was non-negative - (see EmbeddedWorkerInstance.Start.StartMessageLatency.Type). Only recorded - for installed workers. Recorded upon successful startup. - - - - - - Removed June 2018 (M69). Replaced with - ServiceWorker.StartTiming.ClockConsistency. - - falken@chromium.org - - See EmbeddedWorkerInstance.Start.StartMessageLatency. Describes the outcome - of taking the measurement and whether StartMessageLatency was recorded. - - - - - - Removed July 2018 (M69). Replaced with - ServiceWorker.StartTiming.ScriptEvaluationStartToScriptEvaluationEnd. - - falken@chromium.org - - The time taken for initial evaluation of the service worker script. - Specifically, the time between ACK from the renderer that the thread started - and ACK that the script evaluation finished. Only recorded for installed - workers. - - - - - - Removed June 2018 (M69). This depended on the URLRequestJob code path, which - won't be taken with S13nServiceWorker/NetworkService. If we want this again, - it can be logged from ServiceWorkerScriptLoader or in Blink directly using - Resource Timing. - - falken@chromium.org - - The time taken to load a new (not installed) service worker, when it came - from the HTTP cache. - - - - - - Removed June 2018 (M69). This path is no longer taken since service worker - installed script manager is used for installed scripts. - - falken@chromium.org - The time taken to load an installed service worker. - - - - - Removed June 2018 (M69), see note in - EmbeddedWorkerInstance.Start.TimeToLoad.HttpCache. - - falken@chromium.org - - The time taken to load a new (not installed) service worker, when it came - from the network. - - - - - - Removed July 2018 (M69). Replaced with - ServiceWorker.StartTiming.StartToSentStartWorker. - - falken@chromium.org - - The time taken between deciding to start a worker and sending the start - worker IPC. Only recorded for installed workers. - - - - - - Removed July 2018 (M69). Replaced with - ServiceWorker.StartTiming.ReceivedStartWorkerToScriptEvaluationStart. - - falken@chromium.org - - The time taken to start the service worker thread. Specifically, the time - between ACK from the renderer that load finished and ACK that the thread - started. Does not include script evaluation time. Only recorded for - installed workers. - - - - - - Removed June 2018 (M69). This path is no longer taken since service worker - installed script manager is used for installed scripts. - - falken@chromium.org - - The round-trip time between asking the renderer process to start a worker - and receiving the corresponding resource request. Only recorded for - installed workers. - - - - - - Removed June 2018 (M69). - - falken@chromium.org - - Indicates if Blink was not initialized by the time the browser sent a - "start a service worker" message to the renderer. If this is true, - receiving the message had to wait until after Blink initialization finished. - Blink initialization is considered the time RenderThreadImpl::Init sets up - the Mojo interface for receiving the "start a service worker" - message. Only recorded for installed workers. Recorded upon successful - startup. - - - - - - Removed June 2018 (M69). - - falken@chromium.org - - Recorded when EmbeddedWorkerInstance.Start.WaitedForRendererSetup is true. - The time between when the "start a service worker" was sent by the - browser, and Blink initialization finishing. The start time is recorded by - the browser process, and the end time by the renderer process, so process - clock skew could possibly affect the result. - - - - - - Removed 4/2016 after we no longer show "all bookamrks" in bookmark - manager. - - ianwen@chromium.org - Number of bookmarks the user has. Android only. - - - - - Removed 3/2015 along with the enhanced bookmarks sync experiment. - - noyau@chromium.org - yefim@chromium.org - - Captures the state the enhanced bookmark experiment is in. Recorded on - startup. To be removed once the enhanced bookmark experiment is finished. - see crbug/323423. - - - - - - Removed 9/2015 after list view became the only view mode. - - ianwen@chromium.org - - Record which Enhanced Bookmark UI mode users are in. This will be recorded - everytime the user opens the bookmark manager UI. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - The way device is joined to the Active Directory domain. This will be - recorded during successful enterprise enrollment and domain join. - - - - - - Code removed in M46. - - aberent@chromium.org - - Android Only - Time to load the App Restrictions from the O.S.. - - - - - twellington@google.com - tedchcoc@chromium.org - - Records the time it takes to retrieve applicaton restrictions from the - system. Android only. - - - - - twellington@google.com - tedchcoc@chromium.org - - Records the time it takes to retrieve applicaton restrictions from the - system when the retrieved Bundle is empty. Android only. - - - - - twellington@google.com - tedchcoc@chromium.org - - Records the time it takes to retrieve applicaton restrictions from the - system when the retrieved Bundle is not empty. Android only. - - - - - - Code removed in M46. - - aberent@chromium.org - - Android Only - Whether Chrome was able to read and decode the - AppRestrictions policy cache on startup. - - - - - - - igorcov@chromium.org - vsavu@chromium.org - - Consistency between TPM lock state and absence/presence of install - attributes at boot. - - - - - - - pmarko@chromium.org - igorcov@chromium.org - - Duration of the bucket download part of the auto-enrollment protocol. - - - - - - - pmarko@chromium.org - igorcov@chromium.org - - Time since the user logged in until the auto-enrollment protocol completed. - 0 is sampled when the protocol is done by the time the user logs in. - - - - - - - amraboelkher@google.com - mpolzer@google.com - - Duration of the hash dance to determine enrollment state of the device. Only - recorded if the hash dance finished successfully. - - - - - amraboelkher@google.com - mpolzer@google.com - - Comparison of hash dance and private set membership results used to - determine the initial enrollment state of the device. - - - - - amraboelkher@google.com - mpolzer@google.com - - The status of a private set membership request. This request is used to - determine the initial enrollment state of the device. - - - - - amraboelkher@google.com - mpolzer@google.com - - Duration of the private set membership request to determine enrollment state - of the device. Only recorded if it finished successfully. - - - - - - - pmarko@chromium.org - igorcov@chromium.org - Total duration time of the auto-enrollment protocol. - - - - - - pmarko@chromium.org - igorcov@chromium.org - - Network error code (if applicable) for auto-enrollment requests. - - - - - - - pmarko@chromium.org - igorcov@chromium.org - URL fetcher status for auto-enrollment requests. - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting CBCM policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events measuring effectiveness of refreshing CBCM policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - - - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting status of executed CBCM remote commands. The metric - includes only signed CBCM remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting status of executed CBCM remote commands. The metric - includes only unsigned CBCM remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting received CBCM remote commands. The metric includes - signed CBCM remote commands, both valid and invalid. Valid remote command is - counted by its type. Invalid remote command is counted by a reason why it is - considered invalid (e.g. unknown type or duplication). - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting received CBCM remote commands. The metric includes - unsigned CBCM remote commands, both valid and invalid. Valid remote command - is counted by its type. Invalid remote command is counted by a reason why it - is considered invalid (e.g. unknown type or duplication). - - - - - anthonyvd@google.com - cbe-eng@google.com - - Events for counting CBCM remote commands invalidations received with and - without payloads. Invalidations indicate that there is a remote command to - execute. Payloads provide context about the remote commands update, but may - be absent if dropped by the invalidation service. - - - - - zmin@chromium.org - src/chrome/browser/enterprise/reporting/OWNERS - - Recorded when cloud extension request pending list is updated. Note that - when multiple requests are added or removed together, there will be only one - event recorded. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - The proto size of the basic Chrome browser cloud management reporting - request. When a report is separated into multiple requests, all of them - contain the basic request. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - The number of request for one Chrome browser cloud management report. A - report is separated into multiple requests when it's too large. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - The proto size of each Chrome browser cloud management reporting request. It - includes the requests which are more than 5MB and discarded. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - The upload result for each cloud reporting request. Note that there may be - multiple requests per report. Also, one request may creates multiple data - point due to retry. - - - - - - Removed 06/2020 because enough data had been gathered. - - zmin@chromium.org - pastarmovj@chromium.org - - The number of profiles that miss at least one report and may not be able to - catch the next round due to browser shutdown. The metric is recorded during - browser shutdown process. - - - - - - - grt@chromium.org - src/chrome/browser/enterprise/reporting/OWNERS - - The trigger detected by the ReportScheduler responsible that led to an - attempt to upload an enterprise report. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device local account policy invalidations received with - and without payloads. Invalidations indicate that a policy has been updated - and should be refreshed. Payloads provide context about the policy update, - but may be absent if dropped by the invalidation service. - - As opposed to current histogram, Enterprise.DevicePolicyInvalidations2 - counts only events of device policy invalidations. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing device local account policy - when invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. - - As opposed to current histogram, Enterprise.DevicePolicyRefresh3 counts only - events of refreshing device policies. - - - - - - - emaxx@chromium.org - poromov@chromium.org - - Result of the device ID validation in the device policy blob. - - - - - - Removed 03/2020 in order to separate device and device local account. - Superseded by Enterprise.DevicePolicyInvalidations2 and - Enterprise.DeviceLocalAccountPolicyInvalidations2. - - asumaneev@google.com - managed-platforms@google.com - - Events for counting both device and device local account policies - invalidations received with and without payloads. Invalidations indicate - that a policy has been updated and should be refreshed. Payloads provide - context about the policy update, but may be absent if dropped by the - invalidation service. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. - - As opposed to current histogram, - Enterprise.DeviceLocalAccountPolicyInvalidations2 counts only events of - device local account policy invalidations. - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.DevicePolicyRefresh2. - - bartfab@chromium.org - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. - - - - - - Removed 03/2020 in order to separate device and device local account. - Superseded by Enterprise.DevicePolicyRefresh3 and - Enterprise.DeviceLocalAccountPolicyRefresh3. - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing both device and device local - account policies when invalidations are received from a service. For each - refresh, indicates whether the policy changed, and whether the policy was - invalidated at the time of the refresh. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. - - As opposed to current histogram, Enterprise.DeviceLocalAccountPolicyRefresh3 - counts only events of refreshing device local account policies. - - - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting status of executed device remote commands. The metric - includes only signed device remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting status of executed device remote commands. The metric - includes only unsigned device remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting received device remote commands. The metric includes - signed device remote commands, both valid and invalid. Valid remote command - is counted by its type. Invalid remote command is counted by a reason why it - is considered invalid (e.g. unknown type or duplication). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting received device remote commands. The metric includes - unsigned device remote commands, both valid and invalid. Valid remote - command is counted by its type. Invalid remote command is counted by a - reason why it is considered invalid (e.g. unknown type or duplication). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device remote commands invalidations received with and - without payloads. Invalidations indicate that there is a remote command to - execute. Payloads provide context about the remote commands update, but may - be absent if dropped by the invalidation service. - - Metric is similar to Enterprise.DevicePolicyInvalidations2. Device local - account scope does not exist for remote commands so there is no metric for - remote commands similar to - Enterprise.DeviceLocalAccountPolicyInvalidations2. - - - - - poromov@chromium.org - managed-devices@google.com - - Recorded every time policy file is missing or corrupted on Chrome OS. Should - be compared to Enterprise.DeviceSettings.UpdatedStatus as happens only if - status is STORE_NO_POLICY and device being not managed. - - - - - poromov@chromium.org - managed-devices@google.com - - Recorded every time as DeviceSettingsProvider updates its current state. - Used to compare rate of Enterprise.DeviceSettings.MissingPolicyMitigated - event. - - - - - poromov@chromium.org - managed-devices@google.com - - Number of retries the client did to execute a DeviceManagementServer - request. It's recorded after the request has been completed, either - successfully after 0 or more retries, with a failure (too many retries or - non-retriable error) or with a server error. - - - - - - Removed 03/2019, since no code reports it anymore. - - mnissler@chromium.org - - Events related to fetching, saving and loading DM server tokens. These are - used to retrieve cloud policies. - - - - - - Removed 03/2019, since the issues has been long fixed. - - atwilson@chromium.org - - Temporary metric tracking which regex caused an icu::RegexMatcher - initialization failure, to help figure out the cause of - http://crbug.com/365351 which we can't repro locally. - - - - - - Removed 03/2019, since the issues has been long fixed. - - atwilson@chromium.org - - Temporary metric tracking the type of an icu::RegexMatcher initialization - failure, to help figure out the cause of http://crbug.com/365351 which we - can't repro locally. - - - - - - Removed 03/2019, since the issues has been long fixed. - - atwilson@chromium.org - - Temporary metric tracking the success of icu::RegexMatcher IcuMatcher - initialization, to help figure out the cause of http://crbug.com/365351. - - - - - - - igorcov@chromium.org - vsavu@chromium.org - - Whether loading of device policy from file on an enterprise-enrolled - (checked against install_attributes.pb) Chrome OS device yields an - enterprise policy with a DM token. Filled once during session startup, after - first successful device policy read. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to device enrollment on new installs of Chrome OS devices. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to attestation-based enrollment (Zero-Touch) of Chrome OS - devices. - - - - - antrim@chromium.org - raleksandrov@google.com - cros-oac@google.com - - Events related to Chrome OS enterprise enrollment automated by OOBE - configuration. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to forced re-enrollment (FRE) of Chrome OS devices. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to attestation-based re-enrollment (Auto RE) of Chrome OS - devices. - - - - - raleksandrov@google.com - pmarko@chromium.org - cros-oac@google.com - - Events related to forced initial enrollment of Chrome OS devices during the - first startup of a device. - - - - - raleksandrov@google.com - pmarko@chromium.org - cros-oac@google.com - - Events related to attestation-based initial enrollment (Zero-Touch) of - Chrome OS devices during the first startup of a device. - - - - - raleksandrov@google.com - pmarko@chromium.org - cros-oac@google.com - - Events related to manual fallback from attestation-based initial enrollment - (Zero-Touch) of Chrome OS devices during the first startup of a device. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to manual fallback from attestation-based re-enrollment (Auto - RE) of Chrome OS devices. - - - - - raleksandrov@google.com - cros-oac@google.com - - Events related to Chrome OS enterprise enrollment recovery. Note that this - only covers cases in which prior to recovery, the "private owner" - of the device had UMA stats enabled. - - - - - raleksandrov@google.com - cros-oac@google.com - - Elapsed time from *after* GAIA login until enrollment was cancelled. - - - - - raleksandrov@google.com - cros-oac@google.com - - Elapsed time from *after* GAIA login until enrollment failed. - - - - - raleksandrov@google.com - cros-oac@google.com - - Elapsed time from *after* GAIA login until enrollment succeeded. - - - - - emaxx@chromium.org - poromov@chromium.org - rsorokin@chromium.org - - Chrome OS only. Whether the successful locking of install attributes reused - the previously existing locked attributes, or a fresh lock has being held. - - - - - anthonyvd@google.com - chrome-enterprise-team-core@google.com - - Events for counting CBCM policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. Subset of - "Enterprise.CBCMPolicyInvalidations". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - anthonyvd@google.com - chrome-enterprise-team-core@google.com - - Events measuring effectiveness of refreshing CBCM policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - Subset of "Enterprise.CBCMPolicyRefresh". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device local account policy invalidations received with - and without payloads. Invalidations indicate that a policy has been updated - and should be refreshed. Payloads provide context about the policy update, - but may be absent if dropped by the invalidation service. Subset of - "Enterprise.DeviceLocalAccountPolicyInvalidations2". Gets recorded - only when FCMInvalidationService is used as InvalidationService. - - As opposed to current histogram, - Enterprise.FCMInvalidationService.DevicePolicyInvalidations2 counts only - events of device policy invalidations. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing device local account policy - when invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. Subset of - "Enterprise.DeviceLocalAccountPolicyRefresh3". Gets recorded only - when FCMInvalidationService is used as InvalidationService. - - As opposed to current histogram, - Enterprise.FCMInvalidationService.DevicePolicyRefresh3 counts only events of - refreshing device policies. - - - - - - Removed 03/2020 in order to separate device and device local account. - Superseded by Enterprise.FCMInvalidationService.DevicePolicyInvalidations2 - and - Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyInvalidations2. - - asumaneev@google.com - managed-platforms@google.com - - Events for counting both device and device local account policies - invalidations received with and without payloads. Invalidations indicate - that a policy has been updated and should be refreshed. Payloads provide - context about the policy update, but may be absent if dropped by the - invalidation service. Subset of - "Enterprise.DevicePolicyInvalidations". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. Subset of - "Enterprise.DevicePolicyInvalidations2". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - As opposed to current histogram, - Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyInvalidations2 - counts only events of device local account policy invalidations. - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.FCMInvalidationService.DevicePolicyRefresh2. - - askaraitzhan@google.com - isandrk@chromium.org - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. Subset of "Enterprise.DevicePolicyRefresh". - Gets recorded only when FCMInvalidationService is used as - InvalidationService. - - - - - - Removed 03/2020 in order to separate device and device local account. - Superseded by Enterprise.FCMInvalidationService.DevicePolicyRefresh3 and - Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyRefresh3. - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing both device and device local - account policies when invalidations are received from a service. For each - refresh, indicates whether the policy changed, and whether the policy was - invalidated at the time of the refresh. Subset of - "Enterprise.DevicePolicyRefresh2". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. Subset of "Enterprise.DevicePolicyRefresh3". - Gets recorded only when FCMInvalidationService is used as - InvalidationService. - - As opposed to current histogram, - Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyRefresh3 counts - only events of refreshing device local account policies. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting user policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. Subset of - "Enterprise.PolicyInvalidations". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Tracks the result of registration for policy invalidations. It will fail - when duplicate invalidation names are used for different policies due to - http://b/119860379. Subset of - "Enterprise.PolicyInvalidationsRegistrationResult". Gets recorded - only when FCMInvalidationService is used as InvalidationService. - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.FCMInvalidationService.PolicyRefresh2. - - askaraitzhan@google.com - isandrk@chromium.org - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - Subset of "Enterprise.PolicyRefresh". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - Subset of "Enterprise.PolicyRefresh2". Gets recorded only when - FCMInvalidationService is used as InvalidationService. - - - - - wenyufu@chromium.org - twellington@chromium.org - - Records the time it takes to retrieve applicaton restrictions from the - system using an AsyncTask. Recording during first run experience on Android - only. - - - - - skym@chromium.org - twellington@chromium.org - wenyufu@chromium.org - - Records the time it takes to retrieve applicaton restrictions from the - system using an AsyncTask. Recording during first run experience on Android - only. Has a bigger range (0-3 minutes) than the non-Medium version. - - - - - igorcov@chromium.org - poromov@chromium.org - - Result of a single attempt to signal a device heartbeat, which is used for - monitoring the device connectivity. By default heartbeats per a single - device are sent every 2 minutes. - - - - - pmarko@chromium.org - igorcov@chromium.org - - Chrome OS only. Encodes if initial enrollment should be done, and if not, - why. This histogram is recorded when the Auto Enrollment Check screen is - reached in the Chrome OS Out Of The Box Experience (OOBE) sequence and the - device has not been enrolled or in consumer mode before, i.e. when the - 'check_enrollment' and 'ActivateDate' VPD keys are not present. - - - - - - Removed 10/2019, since no code reports it anymore. Superseded by - Enterprise.InvalidDevicePolicyFilesStatus. - - emaxx@chromium.org - igorcov@chromium.org - - Chrome OS only. Number of policy files that turned out to be invalid when - reading the device policy data. In success scenario the latest policy file - read is successful and has valid data submitting zero for this statistic. - - - - - emaxx@chromium.org - igorcov@chromium.org - vsavu@chromium.org - - Chrome OS only. Result of checking if device policy files are valid when - reading the device policy data. - - - - - mnissler@chromium.org - - Number of policies loaded at startup on iOS, and when a change is detected - at runtime. - - - - - emaxx@chromium.org - igorcov@chromium.org - - Chrome OS only. The result of D-Bus call to lock device to single user. - Estimated that till version M86 we should get enough stats to understand if - there are big problems with the D-Bus call. - - - - - - Remove in M82. Because we decide not to handle user level enrollment - separately. - - zmin@chromium.org - - Records whether the Chrome install is system level or user level when trying - to enroll into the machine level user cloud policy on Windows. This is - intended to count the number of enrollments for each install type. - - - - - rogerta@chromium.org - zmin@chromium.org - - Time since the enrollment request was made until an error is returned from - the server. - - - - - rogerta@chromium.org - zmin@chromium.org - - Time since the enrollment request was made until a successful enrollment - response is returned from the server. - - - - - rogerta@chromium.org - zmin@chromium.org - The result of machine level user cloud policy enrollment. - - - - rogerta@chromium.org - zmin@chromium.org - - Records whether the machine level user cloud policy enrollment dialog is - shown to the user and the action they took. - - - - - rogerta@chromium.org - zmin@chromium.org - - The length of time the machine level user cloud policy enrollment dialog was - visible to the user. - - - - - domfc@chromium.org - zmin@chromium.org - - Records whether a browser unenrollment was completed succcessfully by - writing an invalid DM token to storage or not. - - - - - domfc@chromium.org - webprotect-team@google.com - - Records the size (in bytes) of data that might have been scanned by the - OnBulkDataEntry Enterprise Connector. Is is logged once per user action that - would trigger this Connector. - - - - - mnissler@chromium.org - Result of the OpenNetworkConfiguration policy validation. - - - - mnissler@chromium.org - - A set of enterprise policy rules that are in use. This is recorded every 24 - hours and at startup, if the last recording was earlier than a day before. - - - - - ydago@chromium.org - - A set of enterprise policy rules that are ignored because they do not share - the highest priority from their policy atomic group. This is recorded at - startup, then every 24 hours. If chrome is not running at the 24 hours mark, - this will be recorded at the next startup. - - - - - ydago@chromium.org - - A set of policy atomic groups that have at least one policy disabled because - of its source. This is recorded at startup, then every 24 hours. If chrome - is not running at the 24 hours mark, this will be recorded at the next - startup. - - - - - - Removed 03/2019, since no code reports it anymore. - - mnissler@chromium.org - - Events related to fetching, saving and loading user policies, and also - device policies on Chrome OS. - - - - - atwilson@chromium.org - - Boolean tracking whether there is a valid policy signing key on disk. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting user policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. - - - - - asumaneev@google.com - managed-platforms@google.com - - Tracks the result of registration for policy invalidations. It will fail - when duplicate invalidation names are used for different policies due to - http://b/119860379. - - - - - mnissler@chromium.org - - Time since startup of the cloud policy code until the policy invalidation - service first reported its online status. - - - - - atwilson@chromium.org - Tracking the results of policy key verification. - - - - mnissler@chromium.org - - Load status from the policy loaders which pull policy settings from the - underlying platform, such as Windows Group Policy. - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.PolicyRefresh2. - - mnissler@chromium.org - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - - - - - rbock@google.com - igorcov@chromium.org - Time since last device policy fetch. - - - - zmin@chromium.org - pastarmovj@chromium.org - Time since last machine level user policy fetch. - - - - rbock@google.com - igorcov@chromium.org - Time since last user policy fetch. - - - - poromov@chromium.org - Tracking the results of policy user verification. - - - - isandrk@chromium.org - sduraisamy@chromium.org - - Extensions (and apps) are quite restricted in public sessions for security - and privacy concerns - some permissions are blocked which means the - extension itself is blocked (prevented from loading). This histogram counts - requested permissions on extension installation in public sessions (both - installed and blocked extensions). - - - - - marcgrimme@chromium.org - managed-devices@google.com - - A public session starts when a user signs in using the policy configured - public account. It stops when the user signs out. Session length is the - duration between the start and stop events. It is recorded during signing - out and reported on the next chrome run. This metric tracks the recorded - session length rounded down to the nearest 10-minute bucket and capped at 24 - hours. - - - - - rogerta@chromium.org - - Number of retries the client did to execute a real-time reporting upload - request. It's recorded after the request has been completed, either - successfully after 0 or more retries, with a failure (too many retries or - non-retriable error) or with a server error. - - - - - marcgrimme@chromium.org - managed-devices@google.com - - A regular user session starts when a user signs in using his/her user - account. It stops when the user signs out. Session length is the duration - between the start and stop events. It is recorded during signing out and - reported on the next chrome run. This metric tracks the recorded session - length on an enrolled device rouned down to the nearest 10-minute bucket and - capped at 24 hours. - - - - - antrim@chromium.org - - When an enterprise admin attempts to establish a remote session to a device - running in kiosk mode, the command will fail if device is not considered - idle. This histogram is emitted when that happens. - - - - - antrim@chromium.org - - When an enterprise admin attempts to establish a remote session to a device - running in kiosk mode, it is possible to override usual idleness check and - connect anyway. - - - - - asumaneev@google.com - managed-platforms@google.com - - Tracks whether remote commands invalidator registered for corresponding - invalidations. In case of success the invalidator is able to receive - incoming invalidations. - - Metric is similar to Enterprise.PolicyInvalidationsRegistrationResult. - - - - - - Removed 01/2020 since the histogram indicators were stable. - - nikitapodguzov@chromium.org - The time to perform operations on the ResourceCache object. - - - - - - emaxx@chromium.org - igorcov@chromium.org - - On Chrome OS, the response obtained to retrieve policy request. - - - - - - Removed 01/2020 because SCHEMA_ALLOW_INVALID strategy was removed. - - poromov@chromium.org - hendrich@chromium.org - - Signals whether mismatched value was ignored while validating while using - SCHEMA_ALLOW_INVALID strategy. The strategy is used only for - ManagedBookmarks policy and is considered for deprecation. Recorded when - policy is validated using SCHEMA_ALLOW_INVALID strategy. - - - - - ayaelattar@chromium.org - poromov@chromium.org - - Shows which system features are set to be disabled by - SystemFeaturesDisableList policy. Recorded when the policy preference is - updated with a new system feature. No-op updates aren't counted. - - - - - - Removed and removed from code as of 01/2016. - - pbond@chromium.org - - Events for counting sensitive data occurrences in system logs to upload. - (Email addresses, IP addresses, SSIDs, URLs). The lines with this data will - be removed before upload. - - - - - poromov@chromium.org - Result of a single attempt to upload system logs. - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting device policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. Subset of - "Enterprise.DevicePolicyInvalidations". Gets recorded only when - TiclInvalidationService is used as InvalidationService; - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.TiclInvalidationService.DevicePolicyRefresh2. - - askaraitzhan@google.com - isandrk@chromium.org - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. Subset of "Enterprise.DevicePolicyRefresh". - Gets recorded only when TiclInvalidationService is used as - InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing device policy when - invalidations are received from a service. For each refresh, indicates - whether the policy changed, and whether the policy was invalidated at the - time of the refresh. Subset of "Enterprise.DevicePolicyRefresh2". - Gets recorded only when TiclInvalidationService is used as - InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting user policy invalidations received with and without - payloads. Invalidations indicate that a policy has been updated and should - be refreshed. Payloads provide context about the policy update, but may be - absent if dropped by the invalidation service. Subset of - "Enterprise.PolicyInvalidations". Recorded only when - TiclInvalidationService was used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Tracks the result of registration for policy invalidations. It will fail - when duplicate invalidation names are used for different policies due to - http://b/119860379. Subset of - "Enterprise.PolicyInvalidationsRegistrationResult". Gets recorded - only when TiclInvalidationService is used as InvalidationService. - - - - - - Removed 10/2019 because was recorded incorrectly. Superseded by - Enterprise.TiclInvalidationService.PolicyRefresh2. - - askaraitzhan@google.com - isandrk@chromium.org - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - Subset of "Enterprise.PolicyRefresh". Recorded only when - TiclInvalidationService was used as InvalidationService. - - - - - asumaneev@google.com - managed-platforms@google.com - - Events measuring effectiveness of refreshing user policy when invalidations - are received from a service. For each refresh, indicates whether the policy - changed, and whether the policy was invalidated at the time of the refresh. - Subset of "Enterprise.PolicyRefresh2". Recorded only when - TiclInvalidationService was used as InvalidationService. - - - - - bmalcolm@chromium.org - managed-devices@google.com - - Number of retries the client did to execute an UploadJob. It's recorded - after the request has been completed, either successfully after 0 or more - retries, with a failure because of too many retries or if the UploadJob is - interrupted (destroyed before it could succeed or fail). - - - - - atwilson@chromium.org - - Result of the attempted policy load during profile initialization. - - - - - atwilson@chromium.org - - Result of validating the policy that has just been loaded from disk. - - - - - atwilson@chromium.org - - Result of validating the policy sent down from the server, before writing to - disk. - - - - - agawronska@chromium.org - michaelpg@chromium.org - Failure reason for OAuth token fetch for child user. - - - - mnissler@chromium.org - Initialization delay due to loading the user policy cache. - - - - mnissler@chromium.org - Policy client error during initial policy fetch. - - - - mnissler@chromium.org - Delay for registering the client with the policy server. - - - - mnissler@chromium.org - Delay for minting an OAuth2 acccess token. - - - - mnissler@chromium.org - Delay for fetching policy from the policy server. - - - - mnissler@chromium.org - Total delay for the initial policy fetch. - - - - igorcov@chromium.org - asumaneev@google.com - Service error during OAuth2 access token fetch. - - - - mnissler@chromium.org - Network error during OAuth2 access token fetch. - - - - hendrich@chromium.org - managed-devices@google.com - Re-registration results after failed policy fetch. - - - - emaxx@chromium.org - - Session abort due to a fatal error of Chrome OS user policy initialization. - - - - - mnissler@chromium.org - Source of policy validation errors on Chrome OS. - - - - mnissler@chromium.org - - Validation result when loading user policy from the policy store. - - - - - mnissler@chromium.org - - Validation result when writing user policy to the policy store. - - - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting status of executed user remote commands. The metric - includes only signed user remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting status of executed user remote commands. The metric - includes only unsigned user remote commands. Reports a final status of - finished remote command (e.g. success, failure or termination). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting received user remote commands. The metric includes - signed user remote commands, both valid and invalid. Valid remote command is - counted by its type. Invalid remote command is counted by a reason why it is - considered invalid (e.g. unknown type or duplication). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting received user remote commands. The metric includes - unsigned user remote commands, both valid and invalid. Valid remote command - is counted by its type. Invalid remote command is counted by a reason why it - is considered invalid (e.g. unknown type or duplication). - - - - - asumaneev@google.com - managed-platforms@google.com - - Events for counting user remote commands invalidations received with and - without payloads. Invalidations indicate that there is a remote command to - execute. Payloads provide context about the remote commands update, but may - be absent if dropped by the invalidation service. - - Metric is similar to Enterprise.PolicyInvalidations. - - - - - xiyuan@chromium.org - sduraisamy@chromium.org - Tracks the sign-in events on an enrolled device. - - - - atwilson@chromium.org - - Choice the user made when presented with enterprise signin dialog. - - - - - igorcov@chromium.org - tnagel@chromium.org - - The status code (exit code or signal) from sanity check of RW_VPD read and - matching the contents with data from dump_vpd_log (Chrome OS). - - - - - igorcov@chromium.org - tnagel@chromium.org - - The status code (exit code or signal) from VPD update operation (Chrome OS). - - - - - mnissler@chromium.org - - Delay incurred by the token fetching step of the wildcard login check. - - - - - mnissler@chromium.org - Total delay incurred by the wildcard login check. - - - - mnissler@chromium.org - - Delay incurred by the user info fetching step of the wildcard login check. - - - - - - Removed 07/2016 in Issue 621270. - - mnissler@chromium.org - pastarmovj@chromium.org - - Whether we were able to contact the AD Domain Controller. This check is - performed once at start-up on Windows. - - - - - - Removed 07/2016 in Issue 621270. - - mnissler@chromium.org - pastarmovj@chromium.org - - Enum of possible things that can fail while checking for enterprise env. - This check is performed once at start-up on Windows. - - - - - pastarmovj@chromium.org - rogerta@chromium.org - - Whether the machine is part of an AD domain. This check is performed once at - start-up on Windows. - - - - - olsen@chromium.org - - A set of policy rules that failed validation due to unparsable JSON, or JSON - that did not match the schema. This validation happens on start-up and when - the policy has changed. - - - - - pastarmovj@chromium.org - - A set of policy rules that were ignored due to integrity violations while - parsing the policy data which happens on start-up and when the policy has - changed. - - - - - pastarmovj@chromium.org - zmin@chomium.org - - The number of disabled policy entries on Windows due to integrity violations - while parsing the policy data which happens on start-up and when the policy - has changed. - - - - - mad@chromium.org - - Whether the machine is joined to an AD domain. This check is performed once - at start-up on Windows. - - - - - rogerta@chromium.org - - Whether the machine is considered an enterprise user. An enterprise user is - either in a domain or is managed via MDM. This check is performed once at - start-up on Windows. - - - - - - Removed M85, obsoleted by IsFullyManaged2 because recording frequency - changed from once per session to once per app start. Note that the summary - of this histogram incorrectly stated otherwise. - - twellington@google.com - tedchcoc@chromium.org - - On Android (OS version M+): Whether the device has a "device - owner" app installed. This check is performed once at start-up. - - - - - twellington@google.com - tedchcoc@chromium.org - - On Android (OS version Lollipop+): Whether the device has a "device - owner" app installed. This check is performed once on application - start-up. - - - - - mad@chromium.org - - Whether the full machine name is the same as the short one, identifying a - local machine. This check is performed once at start-up on Windows. - - - - - mad@chromium.org - - Whether the currently logged in user is a local user or not, based on its - SAM compatible user name and machine name. This check is performed once at - start-up on Windows. - - - - - - Removed M85, obsoleted by IsManaged2 because recording frequency changed on - Android from once per session to once per app start. - - rogerta@chromium.org - pastarmovj@chromium.org - - On Windows: Whether the machine is managed via MDM. On macOS: Whether Chrome - found a file of managed policies to follow. On Android (up to M84: OS - version M+, M85+: OS version Lollipop+): Whether the device has a profile - owner app. This check is performed once at start-up. Note that this data is - bogus before M81 on the Mac. - - - - - rogerta@chromium.org - pastarmovj@chromium.org - - On Windows: Whether the machine is managed via MDM. On macOS: Whether Chrome - found a file of managed policies to follow. On Android (OS version - Lollipop+): Whether the device has a profile owner app. This check is - performed once on application start-up. - - - - - twellington@google.com - tedchcoc@chromium.org - - Records the time it takes to calculate whether there is a profile owner app - on the device. Android only. - - - - - avi@chromium.org - pastarmovj@chromium.org - - On the Mac: Whether the current user has an enterprise identity in Open - Directory. This check is performed once at start-up. - - - - - avi@chromium.org - pastarmovj@chromium.org - - On the Mac: Whether the machine is joined to a domain. This check is - performed once at start-up. - - - - - avi@chromium.org - pastarmovj@chromium.org - - On the Mac: Whether the machine is managed via MDM, with data obtained via a - new method (profiles) that is only available in 10.13.4 or later. This check - is performed once at start-up. - - - - - avi@chromium.org - pastarmovj@chromium.org - - On the Mac: Whether the machine is managed via MDM, with data obtained via - an old method (system_profiler). This check is performed once at start-up. - - - - - rogerta@chromium.org - - Whether we could obtain the address of the NetGetJoinInformation function. - This check is performed once at start-up on Windows. - - - - - pastarmovj@chromium.org - rogerta@chomium.org - - The rough Windows suite we are running on. This check is performed once at - start-up on Windows. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records the reason that the BottomSheet-based Ephemeral Tab panel was - closed. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records the reason that the Ephemeral Tab panel was closed. Recorded when - the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records whether the user fully opened the Ephemeral Tab panel when it was - shown. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records whether the user opened the Ephemeral Tab panel beyond peeking - state. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records the duration in milliseconds that the Ephemeral Tab was left open. - Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - jinsukkim@chromium.org - - Records the duration in milliseconds that the Ephemeral Tab was peeking. - Recorded when the UX is hidden. Implemented for Android. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - On non-mobile sites, gesture taps are delayed to prevent double taps from - sending a click event. This stat tracks the user's first action within 5 - seconds after a double tap gesture when the gesture tap delay is disabled. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - On non-mobile sites, gesture taps are delayed to prevent double taps from - sending a click event. This stat tracks the user's first action within 5 - seconds after a double tap gesture when gesture tap events are delayed. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - - Time between initiation of any input event and the renderer receiving and - starting to process it. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - - mustaq@chromium.org - nzolghadr@chromium.org - - Tracks the number of Android MotionEvents with ACTION_DOWN or - ACTION_POINTER_DOWN or ACTION_BUTTON_PRESS for each ToolType (unknown, - finger, mouse or stylus). - - Team: input-dev@chromium.org. - - - - - yigu@chromium.org - event-targeting@chromium.org - - Tracks how many clients were queried (asynchronously) to determine the - target for an input event. - - - - - yigu@chromium.org - - Tracks how long it takes for a client to respond to an asynchronous request - to find a target for an input event. - - Team: event-targeting@chromium.org. - - - - - - Removed as of 01/2020. The feature has been launched. - - yigu@chromium.org - - Tracks how long an event has to wait in the queue while a previous event is - being targeted asynchronously. - - Team: event-targeting@chromium.org. - - - - - nzolghadr@chromium.org - - Whether click target was affected by DOM manipulation or not. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Whether click target was affected by interactive element being in the - ancestor path. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - input-dev@chromium.org - Number of Mouse events coalesced. - - - - - Removed in 06/2020. - - tdresser@chromium.org - input-dev@chromium.org - Number of Touch events coalesced. - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between the first and last events in a coalesced mouse events group. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between the first and last events in a coalesced touch events group. - - Team: input-dev@chromium.org. - - - - - - Removed 01/2019 due to lack of usage. - - eirage@chromium.org - - Number of continuous gesture events (GestureScrollUpdate, - GesturePinchUpdate) coalesced inside the compositor thread event queue per - event. This field is recorded just before the event is processed on the - compositor thread. - - Team: input-dev@chromium.org. - - - - - - Removed 01/2019 due to lack of usage. - - eirage@chromium.org - - Time between the first event in a coalesced continuous gesture events group - (GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the - compositor thread. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 01/2019 due to lack of usage. - - eirage@chromium.org - - Time between the last event in a coalesced continuous gesture events group - (GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the - compositor thread. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 01/2019 due to lack of usage. - - eirage@chromium.org - - Time between when a non-continuous gesture event (GestureScrollStart/End, - GesturePinchStart/End) was placed into the queue and when it was processed - on the compositor thread. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 01/2018 in favor of - Event.DownEventCount.PerInputFormFactorDestinationCombination. - - xiaoyinh@chromium.org - tbuckley@chromium.org - - The number of down events received per destination. Every down event that is - targeted to each destination will be counted, including those that don't - have an effect. For example: Tapping on a disabled button inside the browser - frame will be treated as down events on browser window. - - - - - - Removed 01/2018 in favor of - Event.DownEventCount.PerInputFormFactorDestinationCombination. - - xiaoyinh@chromium.org - tbuckley@chromium.org - - Counts the number of down events generated by clamshell/touchview. - - - - - - Removed 01/2018 in favor of - Event.DownEventCount.PerInputFormFactorDestinationCombination. - - xiaoyinh@chromium.org - tbuckley@chromium.org - - Counts the number of down events generated by Mouse/Touch/Stylus. - - - - - - Removed 02/2019 in favor of - Event.DownEventCount.PerInputFormFactorDestinationCombination2. - - tbuckley@chromium.org - - The number of down events received per input, form factor, and destination - combination. - - Input is down events generated by mouse/touch/stylus. Form factor is down - events generated by clamshell/touchviewLandscape/touchviewPortrait. - Destination: Every down event that is targeted to each destination will be - counted including those that don't have an effect. For example: Tapping on a - disabled button inside the browser frame will be treated as down events on - browser window. - - - - - tbuckley@chromium.org - - The number of down events received per destination, input and form factor - combination. - - Input is down events generated by mouse/touch/stylus. Form factor is down - events generated by clamshell/touchviewLandscape/touchviewPortrait. - Destination: Every down event that is targeted to each destination will be - counted including those that don't have an effect. For example: Tapping on a - disabled button inside the browser frame will be treated as down events on - browser window. - - - - - - Removed 06/2020 as being expired. - - dcheng@chromium.org - sadrul@chromium.org - - Reports whether chrome accepts or rejects a drag and drop operation. - - During a drag and drop operation, there are many 'drag update' events that - happen for each mouse-move event. For each such drag-update event, chrome - reports whether it is able to accept the drop event or not. - - - - - - Removed 06/2020 as being expired. - - nzolghadr@chromium.org - - Counts the number of times the user cancelled a drag and drop operation. - - - - - - Removed 06/2020 as being expired. - - nzolghadr@chromium.org - - Counts the number of times the user completed a drag and drop operation. - - - - - - Removed 06/2020 as being expired. - - nzolghadr@chromium.org - - Counts the number of times a drag and drop operation originating outside of - a Chrome window successfuly drops. - - - - - - Removed 06/2020 as being expired. - - nzolghadr@chromium.org - - Counts the number of times the user started a drag and drop operation. - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - For each 10 second window, reports the fraction of the time there was no - user input. We consider there to be no user input if we haven't received any - events for > 50ms. - - - - - wjmaclean@chromium.org - - Record whether we unexpectedly encounter an empty gesture queue while - routing gesture events to frames' renderers: true => empty queue, false - => non-empty queue. - - - - - wjmaclean@chromium.org - kenrb@chromium.org - - The size of the TouchEventAckQueue, recorded each time we process an event - ack (the queue usually, but not always, decreases in size during ack - processing). Ideally this queue will operate at length close to zero, - depending on how long it takes for events to travel to a renderer and be - processed and an ack sent back. As the size increases it indicates decreased - responsiveness of renderers with respect to touch events. One purpose of - this metric is to develop a sense of normal queue sizes for different - platforms. Initially we expect queue length to be less than 20 most of the - time, but this is a guess. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Emitted after a renderer process main-thread fling curve animation - terminates, for any reason, reporting the average animation frequency - (animations/second) of the fling instance over its lifetime. This is - computed as the number of fling animation ticks divided by the fling - animation duration. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Emitted after a renderer process impl-thread fling curve animation - terminates, for any reason, reporting the average animation frequency - (animations/second) of the fling instance over its lifetime. This is - computed as the number of fling animation ticks divided by the fling - animation duration. - - Team: input-dev@chromium.org. - - - - - kuscher@google.com - - The gesture-events recognized and dispatched by the browser gesture - recognizer. This replaces Ash.GestureCreated, which did not record events on - Android and Windows. - - Team: input-dev@chromium.org. - - - - - dtapuska@chromium.org - - For each hit test, records whether it was a hit or miss, and why. - - Team: input-dev@chromium.org. - - - - - dtapuska@chromium.org - - For hit tests that are validated, records whether it was correct or not, and - why. - - Team: input-dev@chromium.org. - - - - - dtapuska@chromium.org - - For hit tests that are invalid, records the score (a series of bits - indicating what was matched and what wasn't). - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019. - - - - eirage@chromium.org - - Records the euclidean distance from a mouse event's position to the - predicted position at the event time when prediction is available. - Prediction is available after the predictor selected by feature flag gets a - few continuous mouse events. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019. - - - - eirage@chromium.org - - Records the euclidean distance from a ScrollUpdate event's absolute scroll - position (count by accumulated delta) to the predicted scrolling position at - the event time when prediction is available. Prediction is available after - the predictor selected by feature flag gets a few continuous - GestureScrollUpdate events. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019. Replaced by - Event.InputEventPrediction.Scroll.OverPrediction. - - - - eirage@chromium.org - - Records y direction distance from a ScrollUpdate event's absolute scroll - position (count by accumulated delta) to the predicted scrolling position at - the event time when prediction is available and also the predicted result is - 'OverPredict'. Over predict means the absolute value of predicted scroll - delta is larger than the real delta in the same time period. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019. Replaced by - Event.InputEventPrediction.Scroll.UnderPrediction. - - - - eirage@chromium.org - - Records y direction distance from a ScrollUpdate event's absolute scroll - position (count by accumulated delta) to the predicted scrolling position at - the event time when prediction is available and also the predicted result is - 'UnderPredict'. Under predict means the absolute value of predicted scroll - delta is smaller than the real delta in the same time period. - GestureScrollUpdate events. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019. - - - - eirage@chromium.org - - Records the euclidean distance from a touch event's position to the - predicted position at the event time when prediction is available. - Prediction is available after the predictor selected by feature flag gets a - few continuous touches with same ids. - - Team: input-dev@chromium.org. - - - - - eirage@chromium.org - axantoine@google.com - - Overshoot distance in pixels between a predicted scroll position and the - corresponding interpolated real scroll position that occurred at the - prediction time. - - Team: input-dev@chromium.org. - - - - - eirage@chromium.org - axantoine@google.com - - Euclidean distance in pixels between two successive variations of touch - scroll deltas which are the difference between a predicted scroll position - and its corresponding interpolated real position that occurred at prediction - time. - - Team: input-dev@chromium.org. - - - - - eirage@chromium.org - axantoine@google.com - - Undershoot distance in pixels between a predicted scroll position and the - corresponding interpolated real scroll position that occurred at the - prediction time. - - Team: input-dev@chromium.org. - - - - - eirage@chromium.org - axantoine@google.com - - Euclidean distance in pixels between two successive variations of touch - scroll deltas which are the difference between a predicted scroll position - and the interpolated real position that occurred at frame time. - - Team: input-dev@chromium.org. - - - - - eirage@chromium.org - axantoine@google.com - - Boolean that indicates whether the prediction is in the same direction as - the real trajectory at the same prediction time. True means the direction is - not the same (wrong direction). - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - input-dev@chromium.org - - Time between the renderer main thread receiving a keyboard event and acking - it, for events which were not preventDefaulted. Only recorded for key - presses. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - input-dev@chromium.org - - Time between the renderer main thread receiving a keyboard event and acking - it, for events which were preventDefaulted. Only recorded for key presses. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchend event and acking - it, for events which were not preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchend event and acking - it, for events which were preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchmove event and acking - it, for events which were not preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchmove event and acking - it, for events which were preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchstart event and - acking it, for events which were not preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between the renderer main thread receiving a touchstart event and - acking it, for events which were preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of all input events and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of input event and browser processing. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between key events sent from RWH to renderer and acked by renderer. - Only monitors key presses. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between key events received by Chrome and sent from RWH to renderer. - Only monitors key presses. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between touch events sent from RWH to renderer and acked by renderer. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between touch events received by Chrome and sent from RWH to renderer. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - ccameron@chromium.org - - Time between wheel events sent from RWH to renderer and acked by renderer. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - ccameron@chromium.org - - Time between wheel events received by Chrome and sent from RWH to renderer. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the OS receiving a keyboard event and the resulting GPU frame - swap. If no swap was induced by the event, no recording is made. Only - recorded for key presses. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between the OS receiving a mouse event and the resulting GPU frame - swap. If no swap was induced by the event, no recording is made. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between the OS receiving a touchpad pinch event and the resulting GPU - frame swap. If no swap was induced by the event, no recording is made. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between the OS receiving a touchpad pinch event and the resulting GPU - frame swap. If no swap was induced by the event, no recording is made. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between the OS receiving a touchpad pinch event and RenderWidgetHost - sending event to render. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Duration of a non-resurive hitTest operation. The hit test is non-recursive - when the AllowChildFrameContent flag is clear. See also - Event.Latency.HitTestRecusrive. - - Team: paint-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Duration of a recursive hitTest operation. The hit test is recursive when - the AllowChildFrameContent flag is set. See also Event.Latency.HitTest. - - Team: paint-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between input event received by OS and sent to Chrome. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram never has negative values, so it was removed 06/2020. - - sullivan@chromium.org - input-dev@chromium.org - - For Mac, a version of Event.Latency.OS that has the negative values it would - contain if ValidateEventTimeClock() were not called on the timestamps. - - This metric is intended to debug http://crbug.com/1039833, where very high - numbers are seen for PageLoad.InputDelay3. The units of this metric are the - same as PageLoad.InputDelay3 for consistency while debugging. - - - - - sullivan@chromium.org - input-dev@chromium.org - - For Mac, a version of Event.Latency.OS that has the positive values it would - contain if ValidateEventTimeClock() were not called on the timestamps. - - This metric is intended to debug http://crbug.com/1039833, where very high - numbers are seen for PageLoad.InputDelay3. The units of this metric are the - same as PageLoad.InputDelay3 for consistency while debugging. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - input-dev@chromium.org - - Time between sending a keyboard event to the renderer main thread and when - the renderer begins to process that event, for events which were not - preventDefaulted. Only recorded for key presses. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a keyboard event to the renderer main thread and when - the renderer begins to process that event, for events which were - preventDefaulted. Only recorded for key presses. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchend event to the renderer main thread and when - the renderer begins to process that event, for events which were not - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchend event to the renderer main thread and when - the renderer begins to process that event, for events which were - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchmove event to the renderer main thread and when - the renderer begins to process that event, for events which were not - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchmove event to the renderer main thread and when - the renderer begins to process that event, for events which were - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchstart event to the renderer main thread and when - the renderer begins to process that event, for events which were not - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed in 06/2020. - - tdresser@chromium.org - - Time between sending a touchstart event to the renderer main thread and when - the renderer begins to process that event, for events which were - preventDefaulted. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between initiation of all input events and renderer processing. This is - soon to be replaced by Event.Latency.Renderer2.* - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between input event creation and the renderer receiving and starting to - process the event. For touch events on Windows, we measure from when the - event reaches Chrome, whereas on other platforms we use the timestamp from - the kernel. On Windows, this metric is only reported when |IsHighResolution| - is true, which will introduce some sampling bias. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between input event creation and the renderer impl thread receiving and - starting to process the event. For touch events on Windows, we measure from - when the event reaches Chrome, whereas on other platforms we use the - timestamp from the kernel. On Windows, this metric is only reported when - |IsHighResolution| is true, which will introduce some sampling bias. - - Team: input-dev@chromium.org. - - - - - - Removed 12/2013 and replaced by Event.Latency.RendererImpl.GestureScroll2 - - rbyers@chromium.org - - Time between initial creation of touch event and when the resulting - ScrollGesture reaches Impl thread. Maximum is 200ms. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between touch event creation and when the resulting GestureScroll - reaches the Impl thread. Maximum is 1000ms. On Windows, we measure from when - the touch event reaches Chrome, whereas on other platforms we use the - timestamp from the kernel. On Windows, this metric is only reported when - |IsHighResolution| is true, which will introduce some sampling bias. This - supersedes the Event.Latency.RendererImpl.GestureScroll metric. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between initial creation of a wheel event and the generated - ScrollUpdate gesture event is handled on main/impl thread (specified by - suffix). If no swap was induced by the ScrollUpdate gesture event, no - recording is made. Unlike Event.Latency.ScrollUpdate.Wheel.TimeToHandled2 - this metric includes the first GSU of every scrolling sequence as well. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between initial creation of a wheel event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. Unlike - Event.Latency.ScrollUpdate.Wheel.TimeToScrollUpdateSwapBegin2 this metric - includes the first GSU of every scrolling sequence as well. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the display compositor receives the notification of the first - ScrollUpdate gesture event in a given scroll gesture event sequence with - scrollbar source induced renderer swap and GPU starts to swap. The name - contains BrowserNotified for consistency with the existing - ScrollBegin/ScrollUpdate metrics - historically the display compositor lived - in the browser process. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between gpu starts to swap the first ScrollUpdate gesture event in a - given scroll gesture event sequence with scrollbar source induced frame and - the swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the first ScrollUpdate gesture event in a given scroll gesture - event sequence with scrollbar source, is handled on main/impl thread - (specified by suffix) and before renderer starts to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the renderer starts to swap a frame (generates compositor - frame) induced by the first ScrollUpdate gesture event in a given scroll - gesture event sequence with scrollbar source, and display compositor - receives the submitted compositor frame. The name contains BrowserNotified - for consistency with the existing ScrollBegin/ScrollUpdate metrics - - historically the display compositor lived in the browser process. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between initial creation of a scrollbar event and the first generated - ScrollUpdate gesture event in a given scroll gesture event sequence is - handled on main/impl thread (specified by suffix). If no swap was induced by - the ScrollUpdate gesture event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - speed-metrics-dev@chromium.org - - Time between initial creation of an input event that resulted in a scrollbar - scroll and the start of the frame swap on the GPU service caused by the - generated ScrollUpdate gesture event if that ScrollUpdate is the first such - event in a given scroll gesture event sequence. If no swap was induced by - the event, no recording is made. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68. - - nzolghadr@chromium.org - - Time between initial creation of a wheel/touch event and start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. If no - swap was induced by the event, no recording is made. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Time between initial creation of a wheel/touch event and start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. If no - swap was induced by the event, no recording is made. - - Team: input-dev@chromium.org. - - - - - sadrul@chromium.org - chrome-gpu-metrics@google.com - - Records whether the browser top-controls (i.e. omnibox, toolbar) moved - because of the scroll-begin event (i.e. the first scroll-update event of - that sequence). - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures an average distance that represents how the page sticks to the - finger when user scrolls. Only reports touch scrolling. See - https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ - - This is the lag caused by the Gesture Scroll Begin Event. In each touch - interaction there is a GSB followed by multiple Gesture Scroll Updates, - which are separately logged by Event.Latency.ScrollUpdate.Touch.AverageLag. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.org - input-dev@chromium.org - - Measures an average distance that represents how the page sticks to the - finger when user scrolls. Only reports touch scrolling. See - https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ - - This is the lag caused by the Gesture Scroll Begin Event. In each touch - interaction there is a GSB followed by multiple Gesture Scroll Updates, - which are separately logged by - Event.Latency.ScrollUpdate.Touch.AverageLagPresentation. - - The difference between AverageLag and AverageLagPresentation is that the - former uses the Gpu Swap Begin Time as an approximation for the time the - frame is visible on the screen, while the latter uses the Presentation Time. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - - Time between the browser receives the notification of the first ScrollUpdate - gesture event in a given scroll gesture event sequence with touch source - induced renderer swap and GPU starts to swap. - - Team: input-dev@chromium.org. - - - - - - Removed 04/2020 due to lack of usage. - - eirage@chromium.org - axantoine@google.com - - Time between the initiation of the last ScrollBegin event received and its - handling in a frame by the scroll predictor (i.e. rAF time). - - Team: input-dev@chromium.org. - - Warning: Only recorded in a touch context. - - - - - tdresser@chromium.org - - Time between gpu starts to swap the first ScrollUpdate gesture event in a - given scroll gesture event sequence with touch source induced frame and the - swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the first ScrollBegin gesture event in a given scroll gesture - event sequence with touch source, is handled on main/impl thread (specified - by suffix) and before renderer starts to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 10/2019 due to lack of usage. - - eirage@chromium.org - axantoine@google.com - - Time between the handling of the last ScrollBegin event received in the - frame (i.e. rAF time) and the end of the swap of that frame on the gpu. - - Team: input-dev@chromium.org. - - Warning: Only recorded in a touch context. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the renderer starts to swap a frame induced by the first - ScrollUpdate gesture event in a given scroll gesture event sequence with - touch source, and browser receives the swap notification. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between initial creation of a touch event and the first generated - ScrollBegin gesture event in a given scroll gesture event sequence is - handled on main/impl thread (specified by suffix). If no swap was induced by - the ScrollUpdate gesture event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. This is - going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a - rebucketing change made this metric lose its usefulness in Chirp - infrastructure. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input-dev@chromium.org - speed-metrics-dev@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between the browser receives the notification of the first ScrollUpdate - gesture event in a given scroll gesture event sequence with wheel source - induced renderer swap and GPU starts to swap. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between gpu starts to swap the first ScrollUpdate gesture event in a - given scroll gesture event sequence with wheel source induced frame and the - swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the first ScrollUpdate gesture event in a given scroll gesture - event sequence with wheel source, is handled on main/impl thread (specified - by suffix) and before renderer starts to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the renderer starts to swap a frame induced by the first - ScrollUpdate gesture event in a given scroll gesture event sequence with - wheel source, and browser receives the swap notification. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between initial creation of a wheel event and the first generated - ScrollUpdate gesture event in a given scroll gesture event sequence is - handled on main/impl thread (specified by suffix). If no swap was induced by - the ScrollBegin gesture event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a wheel event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. This is - going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a - rebucketing change made this metric lose its usefulness in Chirp - infrastructure. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a wheel event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between initial creation of a wheel event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghad@chromium.org - - Time between the browser receives the notification of a ScrollUpdate gesture - generated from a touchscreen fling induced renderer swap and GPU starts to - swap. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between gpu starts to swap a ScrollUpdate gesture event generated from - a touchscreen fling induced frame and the swap finishes. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Time between a ScrollUpdate gesture event generated from a touchscreen - fling, is handled on main/impl thread (specified by suffix) and before - renderer starts to swap. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - input-dev@chromium.org - - Time between the renderer starts to swap a frame induced by a ScrollUpdate - gesture event generated from a touchscreen fling, and browser receives the - swap notification. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Time between initial creation of a ScrollUpdate gesture event generated from - a touchscreen fling is handled on main/impl thread (specified by suffix). If - no swap was induced by the ScrollUpdate gesture event, no recording is made. - - Team: input-dev@chromium.org. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - sahel@chromium.org - - Time between initial creation of a ScrollUpdate gesture event generated from - a touchscreen fling and the start of the frame swap on the GPU service - caused by the generated ScrollUpdate gesture event. If no swap was induced - by the event, no recording is made. This is going to be replaced by - *.TimeToScrollUpdateSwapBegin3 version since a rebucketing change made this - metric lose its usefulness in Chirp infrastructure. - - Team: input-dev@chromium.org. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - sahel@chromium.org - - Time between initial creation of a ScrollUpdate gesture event generated from - a touchscreen fling and the start of the frame swap on the GPU service - caused by the generated ScrollUpdate gesture event. If no swap was induced - by the event, no recording is made. - - Team: input-dev@chromium.org. - - - - - nozlghadr@chromium.org - - Time between initial creation of a ScrollUpdate gesture event generated from - a touchscreen fling and the start of the frame swap on the GPU service - caused by the generated ScrollUpdate gesture event. If no swap was induced - by the event, no recording is made. - - Team: input-dev@chromium.org. - - - - - - To be replaced by - Event.Latency.ScrollUpdate.Touch.BrowserNotifiedToBeforeGpuSwap2, - Event.Latency.ScrollUpdate.Wheel.BrowserNotifiedToBeforeGpuSwap2 in M56. - https://crbug.com/649754 - - rbyers@chromium.org - - Time between the browser receives the notification of a ScrollUpdate gesture - event induced renderer swap and GPU starts to swap. - - - - - - To be replaced by Event.Latency.ScrollUpdate.Touch.GpuSwap2, - Event.Latency.ScrollUpdate.wheel.GpuSwap2 in M56. https://crbug.com/649754 - - rbyers@chromium.org - - Time between gpu starts to swap a ScrollUpdate gesture event induced frame - and the swap finishes. - - - - - - To be replaced by Event.Latency.ScrollUpdate.Touch.HandledToRendererSwap2, - Event.Latency.ScrollUpdate.Wheel.HandledToRendererSwap2 in M56. - https://crbug.com/649754 - - rbyers@chromium.org - - Time between the ScrollUpdate gesture event is handled on main/impl thread - (specified by suffix) and before renderer starts to swap. - - - - - - To be replaced by - Event.Latency.ScrollUpdate.Touch.RendererSwapToBrowserNotified2, - Event.Latency.ScrollUpdate.Wheel.RendererSwapToBrowserNotified2 in M56. - https://crbug.com/649754 - - rbyers@chromium.org - - Time between the renderer starts to swap a frame induced by ScrollUpdate - gesture event and browser receives the swap notification. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the display compositor receives the notification of the first - ScrollUpdate gesture event in a given scroll gesture event sequence with - scrollbar source induced renderer swap and GPU starts to swap. The name - contains BrowserNotified for consistency with the existing - ScrollBegin/ScrollUpdate metrics - historically the display compositor lived - in the browser process. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between gpu starts to swap a ScrollUpdate gesture event with scrollbar - source induced frame and the swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the ScrollUpdate gesture event with scrollbar source, is - handled on main/impl thread (specified by suffix) and before renderer starts - to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between the renderer starts to swap a frame (generates compositor - frame) induced by the first ScrollUpdate gesture event in a given scroll - gesture event sequence with scrollbar source, and display compositor - receives the submitted compositor frame. The name contains BrowserNotified - for consistency with the existing ScrollBegin/ScrollUpdate metrics - - historically the display compositor lived in the browser process. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - - Time between initial creation of an input event that results in a scrollbar - scroll and the generated ScrollUpdate gesture event is handled on main/impl - thread (specified by suffix). If no swap was induced by the ScrollUpdate - gesture event, no recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - nzolghadr@chromium.org - dlibby@microsoft.com - input-dev@chromium.org - speed-metrics-dev@chromium.org - - Time between initial creation of a scrollbar event and start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event. - If no swap was induced by the event, no recording is made. The first GSU of - every scrolling sequence is excluded from this metric. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68. - - nzolghadr@chromium.org - - Time between initial creation of a wheel/touch event and start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event. - If no swap was induced by the event, no recording is made. The first GSU of - every scrolling sequence is excluded from this metric. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Time between initial creation of a wheel/touch event and start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event. - If no swap was induced by the event, no recording is made. The first GSU of - every scrolling sequence is excluded from this metric. - - Team: input-dev@chromium.org. - - - - - sadrul@chromium.org - chrome-gpu-metrics@google.com - - Records whether the browser top-controls (i.e. omnibox, toolbar) moved - because of the scroll-update event (other than the first update event in the - sequence). - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures an average distance that represents how the page sticks to the - finger when user scrolls. Only reports touch scrolling. See - https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ - - This is the lag caused by the Gesture Scroll Updates occourring in the - lifetime of a scroll interaction. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures the negative impact on the AverageLag metric that is attributable - to scroll prediction. This value has the same units as - Event.Latency.ScrollUpdate.Touch.AverageLag but is a difference between that - value and what it would have been if prediction was disabled. - - PredictionNegative is logged when prediction caused an increase in perceived - lag (i.e. the rendered position was on average further from the actual - location of the finger) for a given interaction/interval. The duration of - the interaction/interval is either 1s, or the time from when the user starts - scrolling to lifting the finger, whichever is smaller. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures the positive impact on the AverageLag metric that is attributable - to scroll prediction. This value has the same units as - Event.Latency.ScrollUpdate.Touch.AverageLag but is a difference between that - value and what it would have been if prediction was disabled. - - PredictionPostive is logged when prediction caused a decrease in perceived - lag (i.e. the rendered position was on average closer to the actual location - of the finger) for a given interaction/interval. The duration of the - interaction/interval is either 1s, or the time from when the user starts - scrolling to lifting the finger, whichever is smaller. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures an average distance that represents how the page sticks to the - finger when user scrolls. Only reports touch scrolling. See - https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ - - This is the lag caused by the Gesture Scroll Updates occurring in the - lifetime of a scroll interaction. - - The difference between AverageLag and AverageLagPresentation is that the - former uses the Gpu Swap Begin Time as an approximation for the time the - frame is visible on the screen, while the latter uses the Presentation Time. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures the negative impact on the AverageLagPresentation metric that is - attributable to scroll prediction. This value has the same units as - Event.Latency.ScrollUpdate.Touch.AverageLagPresentation but is a difference - between that value and what it would have been if prediction was disabled. - - PredictionNegative is logged when prediction caused an increase in perceived - lag (i.e. the rendered position was on average further from the actual - location of the finger) for a given interaction/interval. The duration of - the interaction/interval is either 1s, or the time from when the user starts - scrolling to lifting the finger, whichever is smaller. - - The difference between AverageLag and AverageLagPresentation is that the - former uses the Gpu Swap Begin Time as an approximation for the time the - frame is visible on the screen, while the latter uses the Presentation Time. - - Team: input-dev@chromium.org. - - - - - flackr@chromium.org - joalmei@microsoft.com - input-dev@chromium.org - - Measures the positive impact on the AverageLagPresentation metric that is - attributable to scroll prediction. This value has the same units as - Event.Latency.ScrollUpdate.Touch.AverageLagPresentation but is a difference - between that value and what it would have been if prediction was disabled. - - PredictionPostive is logged when prediction caused a decrease in perceived - lag (i.e. the rendered position was on average closer to the actual location - of the finger) for a given interaction/interval. The duration of the - interaction/interval is either 1s, or the time from when the user starts - scrolling to lifting the finger, whichever is smaller. - - The difference between AverageLag and AverageLagPresentation is that the - former uses the Gpu Swap Begin Time as an approximation for the time the - frame is visible on the screen, while the latter uses the Presentation Time. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - - Time between the browser receives the notification of a ScrollUpdate gesture - event with touch source induced renderer swap and GPU starts to swap. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2019 due to lack of usage. - - eirage@chromium.org - axantoine@google.com - - Time between the initiation of the last ScrollUpdate event received and its - handling in a frame by the scroll predictor (i.e. rAF time). - - Team: input-dev@chromium.org. - - Warning: Only recorded in a touch context. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between gpu starts to swap a ScrollUpdate gesture event with touch - source induced frame and the swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between the ScrollUpdate gesture event with touch source, is handled on - main/impl thread (specified by suffix) and before renderer starts to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 04/2020 due to lack of usage. - - eirage@chromium.org - axantoine@google.com - - Time between the handling of the last ScrollUpdate event received in the - frame (i.e. rAF time) and the end of the swap of that frame on the gpu. - - Team: input-dev@chromium.org. - - Warning: Only recorded in a touch context. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between the renderer starts to swap a frame induced by ScrollUpdate - gesture event with touch source, and browser receives the swap notification. - - Team: input-dev@chromium.org. - - - - - - Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - To be replaced by - Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2 in M57. - https://crbug.com/669618 - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - - Time between initial creation of a touch event and the generated - ScrollUpdate gesture event is handled on main/impl thread (specified by - suffix). If no swap was induced by the ScrollUpdate gesture event, no - recording is made. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a touch event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. This is going to be - replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing - change made this metric lose its usefulness in Chirp infrastructure. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a touch event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - - tdresser@chromium.org - input-dev@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - Time between initial creation of a touch event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - To be replaced by Event.Latency.ScrollUpdate.Touch.TimeToHandled2 in M56. - https://crbug.com/649754 - - rbyers@chromium.org - - Time between initial creation of a touch event and the generated - ScrollUpdate gesture event is handled on main/impl thread (specified by - suffix). If no swap was induced by the ScrollUpdate gesture event, no - recording is made. - - - - - tdresser@chromium.org - - Time between the browser receives the notification of a ScrollUpdate gesture - event with wheel source induced renderer swap and GPU starts to swap. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Time between gpu starts to swap a ScrollUpdate gesture event with wheel - source induced frame and the swap finishes. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between the ScrollUpdate gesture event with wheel source, is handled on - main/impl thread (specified by suffix) and before renderer starts to swap. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - input@chromium.org - - Time between the renderer starts to swap a frame induced by ScrollUpdate - gesture event with wheel source, and browser receives the swap notification. - - Team: input-dev@chromium.org. - - - - - - Replaced by Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a wheel event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - To be replaced by - Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2 in M57. - https://crbug.com/669618 - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - - Time between initial creation of a wheel event and the generated - ScrollUpdate gesture event is handled on main/impl thread (specified by - suffix). If no swap was induced by the ScrollUpdate gesture event, no - recording is made. The first GSU of every scrolling sequence is excluded - from this metric. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a wheel event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. This is going to be - replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing - change made this metric lose its usefulness in Chirp infrastructure. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. - - tdresser@chromium.org - - Time between initial creation of a wheel event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - tdresser@chromium.org - - Time between initial creation of a wheel event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. The first GSU of every - scrolling sequence is excluded from this metric. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by - Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - - - - - Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a touch event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. - - - - - - Replaced by Event.Latency.TouchToFirstScrollUpdateSwapBegin. - crbug.com/478845 - - rbyers@chromium.org - - Time between initial creation of a touch event and the frame swap caused by - by the generated ScrollUpdate gesture event if that ScrollUpdate is the - first such in a given scroll gesture event sequence. If no swap was induced - by the event, no recording is made. - - - - - - Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a touch event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - To be replaced by - Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2 in M56. - https://crbug.com/649754 - - Team: input-dev@chromium.org. - - - - - - Replaced by Event.Latency.TouchToScrollUpdateSwapBegin. crbug.com/478845 - - tdresser@chromium.org - - Time between initial creation of a touch event and the frame swap caused by - by the generated ScrollUpdate gesture event. If no swap was induced by the - event, no recording is made. - - - - - - Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a touch event and start of the frame swap - on the GPU service caused by the generated ScrollUpdate gesture event. If no - swap was induced by the event, no recording is made. - - To be replaced by - Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2 in M56. - https://crbug.com/649754 - - Team: input-dev@chromium.org. - - - - - - Replaced by - Event.Latency.ScrollUpdate.Wheel.TimeToFirstScrollUpdateSwapBegin2. - - tdresser@chromium.org - - Time between initial creation of a wheel event and the start of the frame - swap on the GPU service caused by the generated ScrollUpdate gesture event - if that ScrollUpdate is the first such event in a given scroll gesture event - sequence. If no swap was induced by the event, no recording is made. - - - - - - Removed 08/2016, and replaced by Linux.X11.ServerRTT. - - thomasanderson@chromium.org - Time to request a timestamp from the X server. - - - - tommckee@chromium.org - speed-metrics-dev@chromium.org - - When tracking input event latency, we expect to associate some number of - latency records (instances of ui::LatencyInfo) with a CompositorFrame. Each - record is associated to a particular navigation through its ukm::SourceId - property. This histogram tracks how often the records of an individual frame - have varying or invalid source ids. See crbug.com/1062764. - - - - - - Removed 03/2018 due to lack of usage. - - dtapuska@chromium.org - - Number of continuous events (touchmove, mousemove, mousewheel) coalesced - inside the main thread event queue per event. This field is recorded just - before the event is processed on the main thread. - - Team: input-dev@chromium.org. - - - - - - Removed 01/2018 due to lack of usage. - - dtapuska@chromium.org - - Time between when a continuous event (touchmove, mousemove, mousewheel) was - placed into the queue (or coalesced with another event) and when it was - processed on the main thread. - - Team: input-dev@chromium.org. - - - - - - Removed 01/2018 due to lack of usage. - - dtapuska@chromium.org - - Time between when a continuous event (touchmove, mousemove, mousewheel) was - placed into the queue and when it was processed on the main thread. - - Team: input-dev@chromium.org. - - - - - - Expired 2019-07. - - dtapuska@chromium.org - - Whether the Begin Main Frame was not received and the queue generated a - flush queue after a given timeout. - - Team: input-dev@chromium.org. - - - - - - Removed 01/2018 due to lack of usage. - - dtapuska@chromium.org - - Time between when a non-continuous event (not touchmove, mousemove, - mousewheel) was placed into the queue and when it was processed on the main - thread. - - Team: input-dev@chromium.org. - - - - - - Expired 2019-07. - - dtapuska@chromium.org - - Counts the number of event listener invocations that were forced to be - passive due to interventions and whether the invocation of the listener - called prevent default or not. - - Team: input-dev@chromium.org. - - - - - dtapuska@chromium.org - - The result of handling of MouseWheel, TouchStart, TouchMove, TouchEnd events - in the renderer. - - Team: input-dev@chromium.org. - - - - - - Removed 08/2016 in Issue 595327, and replaced by - Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling. - - dtapuska@chromium.org - - Time between when a forced non-blocking event was generated and the event - processed. This histogram tracks the benefit of forcing non-blocking events - listeners. - - - - - - Expired 2019-07. - - dtapuska@chromium.org - - Time between when a touchstart or first touchmove event per scroll was - generated and the event processed, for events which were forced non-blocking - since they occurred during fling. This histogram tracks the benefit of - forcing events non-blocking during fling. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 04/2018 due to cancellation of experiment. - - tdresser@chromium.org - - Time between when a touchstart or first touchmove event per scroll was - generated and the event processed, for events which were forced non-blocking - since they occurred while the main thread was unresponsive. This histogram - tracks the benefit of forcing events non-blocking when the main thread is - unresponsive. - - Team: input-dev@chromium.org. - - - - - - Removed as of M80 due to the lack of usage. - - dtapuska@chromium.org - - Time between when a cancelable event was generated and the event processed - yet no action was executed for the event. This histogram tracks the - potential benefit of using passive events listeners. - - Team: input-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 10/2019 due to the completion of the experiment. - - nzolghadr@chromium.org - sarsha@microsoft.com - - On Windows, reports negative time delta between pointer input timestamps - based on TimeNow and the timestamp reported via - PointerInfo.PerformanceCount. This negative time delta is w.r.t to - PerformanceCount. See also - Pen.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Positive. - - - - - - Removed 10/2019 due to the completion of the experiment. - - nzolghadr@chromium.org - sarsha@microsoft.com - - On Windows, reports positive time delta between pointer input timestamps - based on TimeNow and the timestamp reported via - PointerInfo.PerformanceCount. This positive time delta is w.r.t to - PerformanceCount. See also - Pen.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Negative. - - - - - - Removed 06/2017 due to lack of usage. - - dtapuska@chromium.org - - Whether the input IPC messages were discarded before being fully processed - in RenderView's IPC message handler. - - Team: input-dev@chromium.org. - - - - - - Removed 10/2017 due to the completion of the experiment. - - yigu@chromium.org - - Record the area of a scroller upon page load. This is intended to help us - measure the distribution of scrollers with different sizes. Combined with - the other two metrics which measure the size of scrollers on scroll, we may - have a better idea of not compositing small scrollers. - - Team: input-dev@chromium.org, animations-dev@chromium.org. - - - - - - Removed 10/2017 due to the completion of the experiment. - - yigu@chromium.org - - Record the area of a scroller upon ScrollBegin. This is intended to help us - measure the frequencies of different sizes of scrollers getting scrolled. - For those small scrollers that users may rarely scroll, there is no need to - composite them even if we are able to do so. - - Team: input-dev@chromium.org, animations-dev@chromium.org. - - - - - - Removed as of 10/2019 due to no further need of data. - - nzolghadr@chromium.org - dlibby@microsoft.com - - Time (ms) between the pointer down event and when a subsequent pointer move - is recognized as a scroll. - - Team: input-dev@chromium.org - - - - - tdresser@chromium.org - - On non-mobile sites, gesture taps are delayed to prevent double taps from - sending a click event. This stat counts the number of taps that are delayed - by the double-tap delay versus those that are sent immediately on mobile - sites. - - Team: input-dev@chromium.org. - - - - - - Removed as of 1/2018 in issue 650338 (http://crbug.com/650338). Using a - DCHECK instead. - - majidvp@chromium.org - caseq@chromium.org - - Whether the timestamps on input events produced by the windowing system - appear to be sharing the same time base as TimeTicks, modulo possible - roll-over. - - Team: input-dev@chromium.org. - - - - - charliea@chromium.org - nzolghadr@chromium.org - - Whether a given touch event is filtered by the passthrough touch event queue - or not. If the event was filtered, a reason is given. Potential reasons for - filtering include the page not having any registered touch handlers and the - renderer process not responding to previous touch events. - - Team: input-dev@chromium.org - - - - - kuscher@google.com - rbyers@chromium.org - - The gesture-events recognized and dispatched for UI components owned by the - browser. This histogram was created as part of separating gesture events - between the browser and Ash (crbug.com/826476). The enums are extracted from - Ash.GestureTarget. - - - - - - Removed 10/2019 due to the completion of the experiment. - - nzolghadr@chromium.org - sarsha@microsoft.com - - On Windows, reports negative time delta between pointer input timestamps - based on TimeNow and the timestamp reported via - PointerInfo.PerformanceCount. This negative time delta is w.r.t to - PerformanceCount. See also - Touch.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Positive. - - - - - - Removed 10/2019 due to the completion of the experiment. - - nzolghadr@chromium.org - sarsha@microsoft.com - - On Windows, reports positive time delta between pointer input timestamps - based on TimeNow and the timestamp reported via - PointerInfo.PerformanceCount. This positive time delta is w.r.t to - PerformanceCount. See also - Touch.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Negative. - - - - - - Removed 05/2016, and replaced by Event.Touch.TargetAndDispatchResult2. - - dtapuska@chromium.org - - An enumeration identifying 3 properties: 1) a classification of the event - target whether it is a root scroll listener (window, document, body) or not; - 2) the result of the dispatch; 3) whether the document was scrollable or - not. - - - - - - Expired 2019-07 - - dtapuska@chromium.org - - An enumeration identifying 4 properties: 1) a classification of the current - target whether it is a root scroll listener (window, document, body) or not; - 2) the result of the dispatch or whether it was previously canceled 3) - whether the document was scrollable or not 4) what phase the listener was - encountered at. This metric is logged during the dispatch of the touch - events. It will only be reported for main frame events that block scrolling, - have only one touch point and current targets that fired an event listener - at that phase. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - On non-mobile-optimized (desktop) sites, whether the ack response from the - renderer for any event in a contiguous touch sequence exceeds the - desktop-specific timeout threshold. - - Team: input-dev@chromium.org. - - - - - tdresser@chromium.org - input-dev@chromium.org - - On mobile-optimized sites, whether the ack response from the renderer for - any event in a contiguous touch sequence exceeds the mobile-specific timeout - threshold. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2019 due to no longer needed. - - eirage@chromium.org - - Records the euclidean distance in dips from a gesture event's original tap - center to its adjusted touch point. 0 if not adjusted. This only records - GestureTap events and GestureLongPress events. - - Team: input-dev@chromium.org. - - - - - - Removed 03/2018 due to no longer needed. - - eirage@chromium.org - - Records if doing touch adjustment on touchstart have same hit test node as - doing touch adjustment on GestureTap. If not, record if one is descendant of - the other. Others means neither of the nodes are descendant of the other. - This only records GestureTap events. - - Team: input-dev@chromium.org. - - - - - - Removed 02/2018 and replaced by Event.Touch.TouchAdjustment.AdjustedNode. - - eirage@chromium.org - - Records if doing touch adjustment on touchstart have same hit test node as - doing touch adjustment on GestureTap. True for same node, false for - different node. This only records GestureTap events. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart events and - the first touchmove events per scroll. Only recorded after the page is fully - loaded. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart events and - the first touchmove events per scroll. Only recorded before the page is - fully loaded. - - Team: input-dev@chromium.org. - - - - - - Removed 08/2016 in Issue 595327, and replaced by - Event.Touch.TouchDispositionsDuringFling2. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart events. Only - recorded while there is an active fling animation. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart and first - touchmove events per scroll. Only recorded while there is an active fling - animation. - - Team: input-dev@chromium.org. - - - - - - Removed 08/2016 in Issue 595327, and replaced by - Event.Touch.TouchDispositionsOutsideFling2. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart events. Only - recorded while there is no active fling animation. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Records the disposition (handled or not handled) of touchstart and first - touchmove events per scroll events. Only recorded while there is no active - fling animation. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between when a touch event was generated and the event was processed. - Recorded only for touchstart events and the first touchmove events per - scroll that occur after the page is fully loaded. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between when a touch event was generated and the event was processed. - Recorded only for touchstart events and the first touchmove events per - scroll that occur before the page is fully loaded. This histogram tracks the - benefit of forcing passive event listeners before the page is fully loaded. - - Team: input-dev@chromium.org. - - - - - - Removed 06/2017 due to lack of usage. - - tdresser@chromium.org - - Time between when a touch event was generated and the event was processed. - Recorded only for touchstart events and the first touchmove events per - scroll when there was no active fling animation. - - Team: input-dev@chromium.org. - - - - - - Removed 08/2016 in Issue 595327, and replaced by - Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling. - - tdresser@chromium.org - - Time between when a touchstart event was generated and the event was - processed. Recorded only when there was an active fling animation. This - histogram tracks the benefit of forcing passive event listeners during - fling. - - - - - - Removed 08/2016 in Issue 595327, and replaced by - Event.Touch.TouchLatencyOutsideFling. - - tdresser@chromium.org - - Time between when a touchstart event was generated and the event was - processed. Recorded only when there was no active fling animation. - - - - - kuscher@google.com - tdresser@chromium.org - - The duration of a touch-sequence. Only measured for single finger gestures. - This replaces Ash.TouchDuration2, which did not record events on Android and - Windows. - - Team: input-dev@chromium.org. - - - - - kuscher@google.com - tdresser@chromium.org - - The maximum euclidean distance in dips (device independent pixel) which a - touch point has travelled away from its starting point. Only measured for - single finger gestures. This replaces Ash.TouchMaxDistance, which did not - record events on Android and Windows. - - Team: input-dev@chromium.org. - - - - - nzolghadr@chromium.org - - Duration of touch selection sequence which finished with the user selecting - one of the text manipulation actions, such as copy, cut, or paste. The - duration is measured from the moment the text selection handles are shown, - and until the action is executed. - - - - - nzolghadr@chromium.org - - Whether the touch selection sequence ended with the user selecting one of - the text manipulation actions, such as copy, cut, or paste. after startup). - Sequences ending with such action are considered successful. - - - - - nzolghadr@chromium.org - - Duration of touch selection sequence which involved dragging a text - selection handle. The duration is measured from the moment the text - selection handles are shown, and until they are dismissed. - - - - - amaralp@chromium.org - - Percentage of touch handle height that would be clipped by the viewport in - the best case of flipping or not flipping. - - - - - amaralp@chromium.org - - Percentage of touch handle height that would be clipped by the viewport if - the handle was not vertically flipped. - - - - - amaralp@chromium.org - - The difference between the metrics |BottomHandleClippingPercentage| and - |BestVerticalClippingPercentage|. Measures how useful vertical flipping is. - - - - - amaralp@chromium.org - - Percentage of left touch handle width that would be clipped by the viewport - without flipping. - - - - - amaralp@chromium.org - - Percentage of right touch handle width that would be clipped by the viewport - without flipping. - - - - - amaralp@chromium.org - - Whether flipping the handle vertically would result in less clipping. - - - - - - Removed as of 07/2018. Replaced with Event.VizHitTest.AggregateTimeUs. - - riajiang@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestAggregator to aggregate hit-test data - received from all clients. - - - - - - Removed as of 01/2020. The feature has been launched. - - yigu@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestAggregator to aggregate hit-test data - received from all clients, in microseconds. - - - - - yigu@chromium.org - - Tracks the reasons why sychronous hit testing could not be done for each hit - test requests processd by HitTestQuery. - - Team: event-targeting@chromium.org. - - - - - zandershah@google.com - event-targeting@chromium.org - - Tracks the result of AsyncLayerTreeFrameSink calls to - HitTestRegionList::IsEqual. - - - - - - Removed as of 01/2020. The feature has been launched. - - yigu@chromium.org - event-targeting@chromium.org - - Total number of hit-test regions Viz received from all clients. - - - - - - Removed as of 07/2018. Replaced with Event.VizHitTest.TargetTimeUs. - - riajiang@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestQuery to find a target on a given - location. - - - - - - Removed as of 01/2020. The feature has been launched. - - yigu@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestQuery to find a target on a given - location, in microseconds. - - - - - - Removed as of 07/2018. Replaced with Event.VizHitTest.TransformTimeUs. - - riajiang@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestQuery to transform a location to a given - target's coordinate space. - - - - - - Removed as of 01/2020. The feature has been launched. - - yigu@chromium.org - event-targeting@chromium.org - - Tracks how long it takes for HitTestQuery to transform a location to a given - target's coordinate space, in microseconds. - - - - - - Removed as of 11/2019. The verification path is removed. - - yigu@chromium.org - - This tracks how often the cc layer based hit testing fast path result - matches or doesn't match the asynchronous blink hit test result. - - Team: event-targeting@chromium.org. - - - - - mohsen@chromium.org - graphics-dev@chromium.org - - Tracks the duration of various stages an event goes through from when it is - generated on the browser side until it ends up generating a frame that is - eventually presented to the user. If the frame is dropped, nothing is - reported. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - mgiuca@chromium.org - - The number of times the fullscreen bubble was re-shown due to inactivity - during a session of fullscreen mode (not including mouse or keyboard lock). - If the mouse or keyboard is also locked while a re-show occurs, both this - and BubbleReshowsPerSession.MouseLock and/or - BubbleReshowsPerSession.KeyboardLock are incremented. Includes all types of - fullscreen (user-triggered, extension-triggered and page-triggered). - Recorded at the end of the session if the simplified-fullscreen-ui flag is - enabled. - - - - - joedow@chromium.org - - The number of times the keyboard lock exit bubble was re-shown during a - session of keyboard lock mode. This occurs when the ExclusiveAccessMode - inactivity timer fires (roughly every 15 minutes). If also in fullscreen - while a re-show occurs both this and BubbleReshowsPerSession.Fullscreen are - incremented in that scenario. Recorded at the end of the session if the - simplified-fullscreen-ui flag is enabled. - - - - - joedow@chromium.org - - The number of times the keyboard lock exit bubble was re-shown during a - session of keyboard lock mode due to the user pressing the escape key - repeatedly. This metric does not count reshows due to inactivity. Recorded - at the end of the session if the simplified-fullscreen-ui flag is enabled. - - - - - mgiuca@chromium.org - - The number of times the mouse lock bubble was re-shown due to inactivity - during a session of mouse lock mode. If also in fullscreen while a re-show - occurs, both this and BubbleReshowsPerSession.Fullscreen are incremented. - Recorded at the end of the session if the simplified-fullscreen-ui flag is - enabled. - - - - - dewittj@chromium.org - petewil@chromium.org - - If we find a bad catalog from the network, report which problems it had. - - - - - dewittj@chromium.org - petewil@chromium.org - Results of the Explore Sites network request for a catalog. - - - - dewittj@chromium.org - petewil@chromium.org - - The Explore Sites catalog can be requested in several code paths. This - identifies which code path was used for the request. - - - - - - - dewittj@chromium.org - petewil@chromium.org - chrome-analysis-team@google.com - - The number of times the user clicked on a site in a category with the - selected type on the Explore Sites page. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - dimich@chromium.org - - 0-based index of a category tile on NTP which was clicked by the user. - Indices are assigned by counting category tiles left-to-right, top-to-bottom - as they appear on NTP. Recorded on click. - - - - - dewittj@chromium.org - Counts when the explore sites store is opened or closed. - - - - dimich@chromium.org - - Http response code from ExploreSitesFetcher. Recorded every time the fetcher - is finishing without network error and actually has HTTP response code. 2XX - codes also included. - - - - - dimich@chromium.org - - Net error results from ExploreSitesFetcher. Recorded every time the fetcher - is finishing. OK and ABORTED are included. - - - - - freedjm@chromium.org - chrome-explore-team@google.com - Tracks the result of image decoding for the favicons. - - - - dimich@chromium.org - - Number of unique hosts visited by the user during the last 30 days. Reported - at most once a week for all users on Android only, with a 5 second delay - after startup. This is different from History.MonthlyHostCount which is - reported for a percentage of startups, to avoid bias toward more active - users. - - - - - chili@chromium.org - dewittj@chromium.org - - Recorded every time a user navigates out of the explore sites page and comes - back to it within 30 seconds on the same tab. This is used to measure - accidental clicks, where we expect users who navigate to the wrong page will - navigate back to the ExploreSites page immediately afterward. - - - - - dimich@chromium.org - - Recorded every time NTP is opened while ExploreSites feature is enabled. - Indicates whether or not the local cached version of ExploreSites catalog - was available or a network request was initiated to load one. - - - - - dimich@chromium.org - freedjm@chromium.org - - Reported each time from the result callback of the ExploreSitesFetcher. - Values include Success and several failure codes. - - - - - - Removed with M77 and replaced by ExploreSites.SiteTilesClickIndex2. - - dewittj@chromium.org - petewil@chromium.org - - The total index of the selected tile on the ExploreSites page. This measures - how far down from the top it is, counting all the other tiles in cards above - it. This assumes 8 tiles per category, and might skip some valid indices if - fewer tiles are displayed in a category. - - - - - dewittj@chromium.org - petewil@chromium.org - - The total index of the selected tile on the ExploreSites page. This measures - how far down from the top it is, counting all the other tiles in cards above - it. This assumes 10 tiles per category, which is set to the maximum of the - tile counts of all existing variations of the ExploreSites page. - - - - - - Removed with M46. - - felt@chromium.org - rdevlin.cronin@chromium.org - - For each pageload, the number of extensions that inject at least one new ad. - - - - - - Removed with M46. - - felt@chromium.org - rdevlin.cronin@chromium.org - - For each pageload, the number of extensions that performed an action that - heuristically looks like injecting an ad, but could not be confirmed. - - - - - - Removed with M46. - - felt@chromium.org - rdevlin.cronin@chromium.org - - For each pageload, the number of extensions that performed an action that - heuristically looks like replacing an ad, but could not be confirmed. - - - - - - Removed with M46. - - felt@chromium.org - rdevlin.cronin@chromium.org - - For each pageload, the number of extensions that remove at least one ad. - - - - - - Removed with M46. - - felt@chromium.org - rdevlin.cronin@chromium.org - - For each pageload, the number of extensions that replace at least one ad. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that inject a content script. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create divs to add to the - page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create 'embed' elements to - add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create iframes to add to - the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create inputs to add to the - page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create links to add to the - page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create 'object' elements to - add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that create script tags to add - to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that use document.write. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that inject a - content script. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create divs - to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create - 'embed' elements to add to the page. - - - - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create - iframes to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create - inputs to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create links - to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create - 'object' elements to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that create - script tags to add to the page. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that use - document.write. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that set - innerHTML. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that invoke DOM - methods. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that set the - value of DOM properties via assignments. - - - - - - Removed with M46. - - felt@chromium.org - - For each www.google.com pageload, the number of extensions that read from - the DOM. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that set innerHTML. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that invoke DOM methods. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that set the value of DOM - properties via assignments. - - - - - - Removed with M46. - - felt@chromium.org - - For each pageload, the number of extensions that read from the DOM. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that were blacklisted when already installed, - grouped by Extension::Location. Logged when ExtensionService blackists and - unloads an installed extension. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that have been blocked from installing grouped by - Extension::Location. Logged when ExtensionService refuses to install a - blacklisted extension. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that have been silently installed in a blacklisted - state, grouped by Extension::Location. Logged when ExtensionService installs - a blacklisted extension without blocking it (ExtensionBlacklist.BlockCRX - would be logged otherwise). Typically this will be when a user has a - blacklisted extension synced. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that were unblacklisted when installed, grouped by - Extension::Location. Logged when ExtensionService unblacklists and loads a - blacklisted extension. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken by the user when seeing the bubble, logged right after the - action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The total number of extensions found to be loaded under Developer Mode, - logged when the devmode bubble is shown (once per startup per profile, if - any devmode extension is found). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The total number of extensions found to be wiped by SideloadWipeout, logged - when the wipeout bubble is shown, which is once per startup per profile. - - - - - - Stopped recording in 2019-07. Data was no longer required. - - finnur@chromium.org - - The action taken by the user when seeing the bubble, logged right after the - action is taken. - - - - - - - lazyboy@chromium.org - extensions-core@chromium.org - - The time taken to create the computed_hashes.json file for an extension. - This happens once for each extension after we get signed values of the - expected root node of a tree hashes for each file from the webstore; we then - compute the individual block level hashes of the actual files and cache them - in computed_hashes.json (assuming we don't detect any mismatches). - - - - - lazyboy@chromium.org - extensions-core@chromium.org - - The time taken to initialize the ContentHashReader for an extension resource - load. (The work done is to read in the verified contents and computed hashes - data, and compare them to make sure they agree.) - - - - - lazyboy@chromium.org - - The time taken in computation (hashing actual bytes read and comparing - against expected computed hashes values) during an extension resource load. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced with ExtensionInstalledLoader.ForceDisabled2. - - Please list the metric's owners. Add more owner tags as needed. - - Counts whether we force-disabled an installed extension at startup because a - policy provider indicated it must remain disabled. - - - - - - Expired 2018-08-30 - - rdevlin.cronin@chromium.org - - Counts whether we force-disabled an installed extension at startup because - it failed ManagementPolicy::MustRemainDisabled check. This checks both - UserMayLoad and MustRemainDisabled methods on a policy provider. - - - - - - Code removed 2020-04. - - N/A. Never properly tracked. - - - - - Code removed 2020-04. - - N/A. Never properly tracked. - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - This is a count of the number of ids that we asked to be signed which the - server response indicated were not in the webstore. - - - - - - Code removed 2020-04. - - N/A. Never properly tracked. - - - - - Code removed 2020-04. - - N/A. Never properly tracked. - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - A count of the number of server requests since Chrome started running, - recorded each time we do a request. NOTE: when interpreting these values, - keep in mind that a user who did 5 server requests during one run of Chrome - will log this histogram 5 times with values 1, 2, 3, 4, and 5. - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether the server result received by the extensions install signer was - valid or invalid. - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - This records the number of seconds since the last time we've done a request - to the server (only during this run of the browser). - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Records how many seconds the browser has been running at the time a request - to the server is made to get a new install signature. - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Logged during InstallVerifier::Init, to indicate the actual enforcement - status used (usually determined by the ExtensionInstallVerifier field trial - experiment, but possibly modified by command line flags). - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Logged during InstallVerifier::Init to indicate the enforcement status as - determined by the ExtensionInstallVerifier field trial experiment. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - The result of the verifier trying to get a new signature. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The result of initialization for the extension install verifier. - - - - - - Code removed 2020-04. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The outcome for each call to InstallVerifier::MustRemainDisabled. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken by the user when seeing the bubble, notifing them of an - extension overriding their new tab page. Logged right after the action is - taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken by the user when seeing the bubble, notifing them of an - extension overriding their homepage. Logged right after the action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken by the user when seeing the bubble, notifing them of an - extension overriding their search engine. Logged right after the action is - taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken by the user when seeing the bubble, notifing them of an - extension overriding their startup page. Logged right after the action is - taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The cause for the failure in the setIcon() extension API function. This is - temporary logging to help track down the cause of a crash. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions on a page that wanted to execute a script, required - explicit user consent, and were denied permission. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions on a page that wanted to execute a script, required - explicit user consent, and were granted permission. - - - - - - Code removed 2015-10. - - rdevlin.cronin@chromium.org - - The number of extensions per page that injected an ad and could have been - stopped if the user had declined script injection. This is related to the - ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or - navigation. Only recorded if there was at least one ad injection detected. - - - - - - Removed 2/2014. - - rdevlin.cronin@chromium.org - - The number of extensions which would display an Active Script Running - indiciation to the user. Recorded at page close. - - - - - - Code removed 2015-10. - - rdevlin.cronin@chromium.org - - The number of extensions per page that injected an ad and that could not - have been stopped through script injection permission. This is related to - the ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or - navigation. Only recorded if there was at least one ad injection detected. - - - - - - Code removed 2015-08. - - felt@chromium.org - rdevlin.cronin@chromium.org - The type of ad that was injected. - - - - - Code removed long ago. - - felt@chromium.org - rdevlin.cronin@chromium.org - - The install location of an ad-injecting extension. Recorded upon page close - for any extension that injected ads on that page. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time it takes to generate the JavaScript API bindings for a - particular extension API. This includes the time from when a JavaScript - context tries to access the API, triggering the lazy initializion, to the - time when the API object is returned. This is only recorded if the binding - is successfully generated. See also Extensions.DidCreateScriptContext_*. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time it takes to create the JavaScript binding object using - the binding.js module. This is a strict subset of - Extensions.ApiBindingGenerationTime, which includes this work and more. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - dbertoni@chromium.org - - Reports whether a tab was updated to a javascript:-scheme URL from the - extensions tabs.update API. Reported once per call to tabs.update(). - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - tjudkins@chromium.org - extensions-core@chromium.org - - Reports whether a URL navigated to by an extension through the extensions - API has the devtools scheme. Reported once per call to tabs.update(), - tabs.create() or browser.openTab(). Also reported from windows.create() and - will be reported once for each url passed to that function. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Captures the results of URL resolution when relative urls are used in the - tabs/windows api. - - - - - benwells@chromium.org - dominickn@chromium.org - tapted@chromium.org - - The number of times v1 apps are launched grouped by - extension_misc::AppLaunchBuckets. See also Apps.AppLaunch for v2 apps. - - - - - - Removed as of 12/2014, replaced by Apps.HostedAppLaunchContainer. - - benwells@chromium.org - tapted@chromium.org - - The number of times apps are launched grouped by - extensions::LaunchContainer. - - - - - benwells@chromium.org - cylee@chromium.org - - The number of times apps are launched grouped by - extensions::AppLaunchSource. - - - - - lazyboy@chromium.org - - A platform app ended up in a regular tab either by the app page or its - background page. Note that this happens unexpectedly right now and we wish - to track its usage before removing the supporting code. - - - - - benwells@chromium.org - tapted@chromium.org - - The number of apps loaded at startup time grouped by Extension::Location. - - - - - benwells@chromium.org - tapted@chromium.org - - The actions taken in the NTP apps promo grouped by - extension_misc::AppsPromoBuckets. - - - - - benwells@chromium.org - tapted@chromium.org - - The number of apps launched grouped by extensions::LaunchType. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The extension install location of an extension that Chrome attempted to add, - but failed because it would downgrade the version. Tracking for - https://crbug.com/810799. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The extension item type of an extension that Chrome attempted to add, but - failed because it would downgrade the version. Tracking for - https://crbug.com/810799. - - - - - - Expired - - rdevlin.cronin@chromium.org - - Time taken to load BackgroundContents for apps at startup when the extension - system notifies that it is ready. - - - - - - Replaced by Extensions.BackgroundPageLoadTime2. - - rdevlin.cronin@chromium.org - The time for an extension's background page to load. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time taken for an extension's persistent background page to load its - initial URL. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The type (if any) of background page the extension has. Recorded for - installed extensions on startup. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of times each Extension function call sends a bad message, - killing the renderer. This may indicate a bug in that API's implementation - on the renderer. Note a similar, aggregate metric is BadMessageTerminate_EFD - which counts the number of bad messages that are sent overall. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The reason a valid ExtensionSyncData could not be parsed from a SyncData - received from sync. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The elapsed time to create a new full instance of an extension API's - bindings using native bindings. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The elapsed time to update the bindings for a new or existing v8::Context. - The suffix indicates which type of context the bindings are for. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M73 after collecting the data necessary. - - ortuno@chromium.org - reillyg@chromium.org - - Records the UUID of the service to which a Chrome App opens a socket - connection. The recorded value is a 31-bit hash of the UUID. These results - will help us better understand the uses of the API and make changes - according to developers' behavior. - - - - - - Removed in M73 after collecting the data necessary. - - ortuno@chromium.org - reillyg@chromium.org - - Records the UUID of a service created by a Chrome App listening for L2CAP - connections. The recorded value is a 31-bit hash of the UUID. These results - will help us better understand the uses of the API and make changes - according to developers' behavior. - - - - - - Removed in M73 after collecting the data necessary. - - ortuno@chromium.org - reillyg@chromium.org - - Records the UUID of a service created by a Chrome App listening for RFCOMM - connections. The recorded value is a 31-bit hash of the UUID. These results - will help us better understand the uses of the API and make changes - according to developers' behavior. - - - - - - Removed 2019/05 as PWA link capturing has been removed. - - mgiuca@chromium.org - ortuno@chromium.org - - Time it takes to retrieve the app for the current URL during a navigation. - - - - - - Removed 2019/05 as PWA link capturing has been removed. - - mgiuca@chromium.org - ortuno@chromium.org - - Time it takes to retrieve the app associated with the window during a - navigation. - - - - - - Removed 2019/05 as PWA link capturing has been removed. - - mgiuca@chromium.org - ortuno@chromium.org - - Time it takes to retrieve the app for the target url during a navigation. - - - - - - Removed 2018/11 in favor of WebApp.Icon.HttpStatusCodeClassOnCreate. - - alancutter@chromium.org - mgiuca@chromium.org - - The HTTP status code class returned for each icon loaded during a - BookmarkApp's creation. - - - - - - Removed 2019/05 in favor of WebApp.Icon.HttpStatusCodeClassOnSync. - - alancutter@chromium.org - mgiuca@chromium.org - - The HTTP status code class returned for each icon loaded when syncing a - BookmarkApp. - - - - - - Removed 2019/05 as PWA link capturing has been removed. - - mgiuca@chromium.org - ortuno@chromium.org - - Number of times navigations into and out of Bookmark Apps are processed, - grouped by their result. - - - - - - Removed 2019/05 as PWA link capturing has been removed. - - mgiuca@chromium.org - ortuno@chromium.org - - The time between the last navigation in the context and us opening a new app - window in response to a new navigation. If it is very small, the context - probably redirected immediately, which is a bad user experience. - - - - - benwells@chromium.org - dominickn@chromium.org - Records the container used for a bookmark app launch. - - - - benwells@chromium.org - dominickn@chromium.org - mgiuca@chromium.org - ortuno@chromium.org - - The number of times Bookmark Apps are launched, grouped by - extensions::AppLaunchSource. The equivalent histogram on Android is called - Launch.HomeScreenSource. - - - - - - Logging code has been removed in M77. Some historical data may be found at - (Google-internal, sorry) - https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY - - lukasza@chromium.org - - When an extension violates browsing instance boundaries, this metric records - the extension type. - - This is a temporary metric - probably okay to remove it in M66, after we've - gathered sufficient UMA data in M65. See also https://crbug.com/786411. - - - - - - Logging code has been removed in M77. Some historical data may be found at - (Google-internal, sorry) - https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY - - lukasza@chromium.org - - When an extension violates browsing instance boundaries, this metric records - whether either the source or the target frame was of the extension view type - of VIEW_TYPE_BACKGROUND_CONTENTS. - - This is a temporary metric - probably okay to remove it in M66, after we've - gathered sufficient UMA data in M65. See also https://crbug.com/786411. - - - - - - Logging code has been removed in M77. Some historical data may be found at - (Google-internal, sorry) - https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY - - lukasza@chromium.org - - When an extension violates browsing instance boundaries, this metric records - the extension view type of the source frame. - - This is a temporary metric - probably okay to remove it in M66, after we've - gathered sufficient UMA data in M65. See also https://crbug.com/786411. - - - - - - Logging code has been removed in M77. Some historical data may be found at - (Google-internal, sorry) - https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY - - lukasza@chromium.org - - When an extension violates browsing instance boundaries, this metric records - the extension view type of the found frame. - - This metric should help confirm or deny the theory that violating browsing - instance boundaries is only needed for looking up background contents / - pages (of VIEW_TYPE_BACKGROUND_CONTENTS type). - - This is a temporary metric - probably okay to remove it in M66, after we've - gathered sufficient UMA data in M65. See also https://crbug.com/786411. - - - - - rkaplow@chromium.org - - The amount of time that elapsed during - ExtensionService::CheckForExternalUpdates. - - - - - archanasimha@chromium.org - extensions-core@chromium.org - - Records every time the user clicks on the extensions checkup middle slot - promo link. The user is served the promo if they are part of the - ExtensionsCheckup experiment and have at least one non default installed - extension. The promo should appear every time the user opens the NTP. The - enum value represents the focus of the message displayed in the promo, which - is determined by the experiment group the user is in. This metric should be - compared with Extensions.Checkup.NtpPromoShown. - - - - - archanasimha@chromium.org - extensions-core@chromium.org - - Records every time the user is served the extensions checkup middle slot - promo on the NTP. The user is served the promo if they are part of the - ExtensionsCheckup experiment and have at least one non default installed - extension. The promo should appear every time the user opens the NTP. The - enum value represents the focus of the message displayed in the promo, which - is determined by the experiment group the user is in. This metric should be - compared with Extensions.Checkup.NtpPromoClicked. - - - - - archanasimha@chromium.org - extensions-core@chromium.org - - The amount of time passed from when the chrome://extensions page has - finished loading till it is closed. We record the time elapsed once the - WebUI has been destroyed. - - - - - - Replaced by Extensions.ChromeExtensionsClientInitTime2. - - dbertoni@chromium.org - extensions-core@chromium.org - - The amount of elapsed time taken to initialize the ChromeExtensionsClient. - Recorded once per client initialization, which happens once per instance of - Chrome. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - The amount of elapsed time taken to initialize the ChromeExtensionsClient. - Recorded once per client initialization, which happens once per instance of - Chrome. This is a new stat that has microsecond resolution. - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - How long a successful initialization of computed_hashes.json file takes. - Recorded when content verification needs to retrieve block hashes. - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether or not computed_hashes.json file read and parse succeeded. Recorded - when content verification needs to retrieve block hashes. - - - - - burunduk@chromium.org - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether or not computed_hashes.json file was successfully generated and - written during extension installation. Recorded during installation of an - extension if hashes computing was requested for this specifix extension. - Hashes computing on installation is used for off-store policy-based - extensions since we need them to be checked against corruption and cannot - use Chrome Web Store for source of hashes. - - - - - burunduk@chromium.org - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time taken to successfully create the computed_hashes.json file for an - extension upon installation. The histogram is collected with - &Extensions.ContentVerification.ComputeHashesOnInstallResult& (in - case of success). - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether or not fetching verified_contents.json succeeded. Recorded when the - file wasn't available locally and we needed to fetch it from network. - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - - Time spent by ContentVerifier for a request to create a ContentHash - instance. Recorded during an extension load completion or during an on - demand content verification that was triggered by ContentVerifyJob. - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether or not initializing verified_contents.json succeeded. Recorded - during an extension load completion or during an on demand content - verification that was triggered by ContentVerifyJob. - - - - - lazyboy@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - How long a successful initialization of verified_contents.json file takes. - Recorded if Extensions.ContentVerification.VerifiedContentsInitResult = true - was recorded. - - - - - - - rdevlin.cronin@chromium.org - karandeepb@chromium.org - - Records the action taken by the user from the extension icon context menu. - - - - - lazyboy@chromium.org - extensions-core@chromium.org - - Fired each time an extension was detected to be corrupted (contents not - matching an expected content hash from the webstore) and was disabled. - - - - - lazyboy@chromium.org - rockot@chromium.org - extensions-core@chromium.org - - The reason why an extension was detected to be corrupted. Recorded each time - an extension is disabled due to corruption detection. - - - - - - - lazyboy@chromium.org - extensions-core@chromium.org - - Logged once at startup, this is the value of a counter that is incremented - anytime we disable a corrupted extension because its content didn't match an - expected content hash. - - - - - lazyboy@chromium.org - extensions-core@chromium.org - - Simiar to Extensions.CorruptExtensionBecameDisabled, but fires when we're in - a bootstrapping mode and would have disabled an extension. - - - - - - Removed 11/2018. Renamed to Extensions.CorruptPolicyExtensionDetected2. - - asargent@chromium.org - - Fires when we detect corruption in an enterprise policy forced install - extension and begin the process of reinstalling it. Compare to - CorruptPolicyExtensionResolved to judge success rate. - - - - - - Removed 01/2020. Replaced by Extensions.CorruptPolicyExtensionDetected3. - - burunduk@chromium.org - lazyboy@chromium.org - poromov@chromium.org - extensions-core@chromium.org - - Fires when we detect corruption in an enterprise policy forced install - extension and begin the process of reinstalling it. Compare to - CorruptPolicyExtensionResolved to judge success rate. - - - - - burunduk@chromium.org - lazyboy@chromium.org - poromov@chromium.org - extensions-core@chromium.org - - Fires when we suspect corruption in an enterprise policy forced install - extension and begin the process of reinstalling it, saving reason of such - suspection. Compare to CorruptPolicyExtensionResolved to judge success rate. - Note that if extension was not reinstalled in the session when corruption - was found, it will be detected again (possible several times, every session - start will trigger a detection until the extension will be fixed), but as - CORRUPTION_DETECTED_IN_PRIOR_SESSION. - - - - - burunduk@chromium.org - lazyboy@chromium.org - extensions-core@chromium.org - managed-devices@google.com - - Fires when we've successfully resinstalled a corrupt enterprise policy - force-installed extension, with a value indicating how long it took - end-to-end to complete the reinstall (including download time). - - - - - - Removed 9/2016 by fix for Issue 447040. - - asargent@chromium.org - - Fires when we detect corruption in an enterprise policy forced install - extension. See http://crbug.com/447040 for more background on why we don't - yet disable these. A useful comparison can be made between this value and - the number of policy forced extensions loaded at startup, which is logged in - the EXTERNAL_POLICY_DOWNLOAD bucket of the Extensions.ExtensionLocation - histogram. - - - - - - Removed as of 06/2020. - - waffles@chromium.org - extensions-core@chromium.org - Net error results from URLFetcher. - - - - - Expired. - - waffles@chromium.org - extensions-core@chromium.org - - Number of times chrome retried to download an extension with a url on a - google.com domain, before eventually giving up. - - - - - - Expired. - - waffles@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Number of times chrome retried to download an extension with a url on a non - google.com domain, before eventually giving up. - - - - - - Removed 2020-02. - - waffles@chromium.org - extensions-core@chromium.org - - Number of times chrome retried to download an extension with a url on a - google.com domain, before eventually succeeding. - - - - - - Removed 2020-02. - - waffles@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Number of times chrome retried to download an extension with a url on a non - google.com domain, before eventually succeeding. - - - - - - Removed 2020-02. - - waffles@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Length of the path to the directory under which an extension is installed. - This directory is in the user's profile. - - - - - cmumford@chromium.org - - The result of an attempt to recover from an attempt to open a database that - failed as a result of corruption. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - The result of an open attempt to an Extensions database. - - - - - Shipped only in M48. Superceded by Extensions.Database.Database.Restore and - Extensions.Database.Value.Restore. - - cmumford@chromium.org - - The result of an attempt to recover from an attempt to open a database that - failed as a result of corruption. - - - - - cmumford@chromium.org - - The result of an attempt to delete a corrupted value from a database. - - - - - - - karandeepb@chromium.org - - Number of calls to the declarative API extension functions. This includes - the declarativeContent and declarativeWebRequest APIs. Emitted when the - extension function is called. - - - - - kelvinjiang@chromium.org - extensions-core@chromium.org - - Number of times a declarative content action is created within an extension. - Emitted when a new declarative content action is created. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Measures the time taken to load a single indexed ruleset in the browser - process for an extension. This includes reading the indexed ruleset file and - verifying it. Emitted whenever a single extension ruleset is loaded. - - - - - - Removed Jan 2020 to increase resolution to microseconds. Replaced with - Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension2. - - karandeepb@chromium.org - extensions-core@chromium.org - - Time taken to evaluate the before-request action for a network request for a - single extension ruleset. Emitted for each network request that is visible - to the extension. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Time taken to evaluate the before-request action for a network request for a - single extension ruleset. Emitted for each network request that is visible - to the extension. This is only emitted for users with high resolution - clocks. - - - - - - Removed Dec 2018. Replaced with - Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions2. - - karandeepb@chromium.org - - Time taken to evaluate whether a network request should be blocked or - redirected as per the Declarative Net Request API. This includes the time - taken to evaluate all the extension rulesets. Emitted for non-sensitive - network requests seen by the Extension System. - - - - - - Removed Jan 2020 to increase resolution to microseconds. Replaced with - Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions3. - - karandeepb@chromium.org - extensions-core@chromium.org - - Time taken to evaluate whether a network request should be blocked or - redirected as per the Declarative Net Request API. This includes the time - taken to evaluate all the extension rulesets. Emitted for non-sensitive - network requests seen by the Extension System when there is at least one - active extension ruleset. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Time taken to evaluate the action to take for the network request as per the - Declarative Net Request API. This includes the time taken to evaluate all - the extension rulesets. Emitted for non-sensitive network requests seen by - the Extension System when there is at least one active extension ruleset. - This is only emitted for users with high resolution clocks. - - - - - karandeepb@chromium.org - lazyboy@chromium.org - - Time taken to index and persist to disk, the deserialized json rules - provided by an extension manifest for the Declarative Net Request API. This - is emitted whenever a packaged extension with a declarative ruleset is - installed or updated. - - - - - - Removed March 2019. - - karandeepb@chromium.org - - Time taken to index the deserialized json rules provided by an extension - manifest for the Declarative Net Request API. This is emitted whenever an - extension's json ruleset is successfully indexed. This may happen when a - packed extension is installed, an unpacked extension is loaded, an - extension's ruleset is re-indexed due to corruption, etc. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Logs whether a regex rule wasn't indexed since it exceeded the per-rule - memory limit. Emitted for every regex rule an extension adds. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Records the result of loading an extension ruleset for the Declarative Net - Request API. Emitted whenever a single extension ruleset is loaded. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - The number of enabled indexed declarative rules provided by an extension - manifest for the Declarative Net Request API. This is emitted whenever a - packaged extension with a declarative ruleset is installed or updated. - - - - - - Removed April 2020. Replaced with - Extensions.DeclarativeNetRequest.ManifestRulesCount2. - - karandeepb@chromium.org - lazyboy@chromium.org - - The number of indexed declarative rules provided by an extension manifest - for the Declarative Net Request API. This is emitted whenever a packaged - extension with a declarative ruleset is installed or updated. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - The number of indexed declarative rules provided by an extension manifest - for the Declarative Net Request API. This also includes rules from disabled - rulesets. This is emitted whenever a packaged extension with a declarative - ruleset is installed or updated. - - - - - - Removed Jan 2020. The addAllowedPages API was removed. - - karandeepb@chromium.org - lazyboy@chromium.org - - Describes the different cases pertaining to initiator checks used by the - Declarative Net Request Page Whitelisting API. Emitted whenever an extension - ruleset is evaluated for a main frame sub-resource request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Indicates the result of reading the dynamic JSON rules for an extension from - the disk. Logged whenever an extension calls the getDynamicRules extension - function or when it updates the dynamic rules through a call to - addDynamicRules or removeDynamicRules. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the request header added by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnBeforeSendHeaders stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the request header modified by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnBeforeSendHeaders stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the request header removed by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnBeforeSendHeaders stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the response header added by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnHeadersReceived stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the response header modified by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnHeadersReceived stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - Records the response header removed by extensions using the - DeclarativeNetRequest API. Recorded for each network request during the - OnHeadersReceived stage. Multiple samples can be recorded per request. - - - - - karandeepb@chromium.org - lazyboy@chromium.org - - Indicates whether reindexing of a Declarative Net Request ruleset was - successful. Called whenever a JSON ruleset for an extension is reindexed, - e.g. on ruleset corruption. Note: this is emitted for both static and - dynamic rulesets. - - - - - - Removed May 2018. Replaced with - Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions - - karandeepb@chromium.org - - Time taken to evaluate whether a network request should be blocked as per - the Declarative Net Request API. This includes the time taken to evaluate - all the extension rulesets. Emitted whenever a non-sensitive network request - is seen by the Extension System. - - - - - - Removed December 2019. Replaced with - Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension - - karandeepb@chromium.org - - Time taken to evaluate whether a network request should be blocked for a - single extension ruleset. Emitted for each network request that is visible - to the extension. - - - - - - Removed December 2019. Replaced with - Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension - - karandeepb@chromium.org - - Time taken to evaluate whether a network request should be redirected for a - single extension ruleset. Emitted for network requests visible to the - extension. - - - - - - Removed May 2018. Replaced with - Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions - - karandeepb@chromium.org - - Time taken to evaluate whether a network request should be redirected as per - the Declarative Net Request API. This includes the time taken to evaluate - all the extension rulesets. Emitted for non-sensitive network requests seen - by the Extension System. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Indicates the result of an extension function call to add or remove dynamic - rules. Logged every time an extension calls the addDynamicRules or - removeDynamicRules extension function. - - - - - Please list the metric's owners. Add more owner tags as needed. - Time spent until rules storage delegate gets ready. - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether an icon specified in the declarativeContent.SetIcon API is - considered visible by our icon analysis code. This stat is emitted when we - create the underlying object that sets the icon when the declarative rule is - applied. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether an icon specified in the declarativeContent.SetIcon API is - considered visible by our icon analysis code. This stat is emitted when we - create the underlying object that sets the icon when the declarative rule is - applied. - - This replaces the previous stat, DeclarativeSetIconWasVisibleRendered, due - to a change to our analysis algorithm. The new algorithm renders the icon - against the toolbar background color and determines how visible the - resulting pixels are. - - - - - - Removed 09/2020. - - karandeepb@chromium.org - mmenke@chromium.org - - The type of each WebRequestConditionAttribute created as part of the - declarativeWebRequest API. - - - - - - Removed July 2019. - - karandeepb@chromium.org - - Whether a network request from a guest webview has any declarative web - request rules that need to be evaluated. Emitted whenever a network request - from a guest webview is received at the network layer. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Number of extensions referenced in the depricated external extensions source - at path chrome::DIR_DEPRICATED_EXTERNAL_EXTENSIONS. - - - - - - There is no such thing as an extension dialog. - - Please list the metric's owners. Add more owner tags as needed. - The time for a dialog-hosted extension to load. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per blessed - extension context (chrome-extension://... origins within Extension - processes, like background pages, options pages, popups). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per blessed web page - context (hosted apps). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per content script - context. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per content script - context. This histogram measures the time to install Extension Javascript - bindings in a context for a platform app enabled on the Chrome OS lock - screen. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per unblessed - extension context (chrome-extension://... origins hosted in iframes). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings in an unknown type - of context (this should never happen other than in bizarre circumstances). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per web page context - (just the chrome.app, chrome.webstore, and possibly chrome.runtime APIs). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records - the time taken to install Extension JavaScript bindings per WebUI context - (chrome://extensions and so forth). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Records the time taken to install Extension JavaScript bindings per service - worker context. - - - - - - Expired 2018-08 - - rdevlin.cronin@chromium.org - - Records the Chrome channel when JavaScript exceptions are not gracefully - dealt with, and suppressed by C++ instead. These are exceptions generated - (or simply not caught and gracefully recovered) in our own internal - JavaScript, not from JavaScript code written by developers (that which is - typically hosted in CRX files). This should be 0 for unstable channels like - canary and dev, because we try *not* to suppress errors and instead kill the - renderer and generate a crash report. However, at times we need to suppress - even those. Note that this histogram is intended to be tracked over time, - per channel, to observe crash rates. Comparisons between - stable/beta/dev/canary are unlikely to be meaningful. - - - - - - - rdevlin.cronin@chromium.org - - The number of extensions that are disabled at browser startup. - - - - - - - rdevlin.cronin@chromium.org - - The number of extensions that are disabled at browser startup due to - permissions increases. - - - - - - Removed 03/2017 because miscounting IGNORE histogram entry. This error is - fixed with DisabledUIUserResponse2. - - rdevlin.cronin@chromium.org - - User response to the dialog shown when an extension is disabled due to an - update requiring more permissions. - - - - - catmullings@chromium.org - - User response to the dialog shown when an extension is disabled due to an - update requiring more permissions. A count is recorded when the user takes - an action on the dialog (re-enable or remove the extension) or ignores the - dialog. - - - - - - Removed 03/2017 because miscounting IGNORE histogram entry. This error is - fixed with DisabledUIUserResponseRemoteInstall2. - - mek@chromium.org - - User response to the dialog shown when an extension is disabled due to it - having been installed remotely. - - - - - catmullings@chromium.org - - User response to the dialog shown when an extension is disabled due to it - having been installed remotely. A count is recorded when the user takes an - action on the dialog (re-enable or remove the extension) or ignores the - dialog. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The count of disabled extensions at startup grouped by disble reason from - disable_reason::DisableReason. When an extension is disabled, it can be for - one or more reasons (although typically just one), so the sum of these may - be greater than 'Extensions.Disabled' which is a count of the number of - unique extensions that are disabled. - - - - - - Removed 2019-06. - - rdevlin.cronin@chromium.org - - The state of the toolbar icon for the docs offline extension (visible in the - toolbar, overflowed in the menu, or the extension is disabled). Recorded - once per startup per (non-incognito) profile. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether a call to set a dynamic icon in the toolbar passed an icon - considered visible by our icon analysis code. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether a call to set a dynamic icon in the toolbar passed an icon - considered visible by our icon analysis code. - - This replaces the previous stat, DynamicExtensionActionIconWasVisible, due - to a change to our analysis algorithm. The new algorithm renders the icon - against the toolbar background color and determines how visible the - resulting pixels are. - - - - - - Obsolete since the enhanced bookmarks manager is no longer using an event - page. - - wittman@chromium.org - - The number of event listeners the Enhanced Bookmarks Manager has, measured - at profile startup. A value of 0 implies that Chrome has a general bug with - event page management, since the bookmarks manager should always have at - least one event listener - but a bug with event page management that affects - the bookmarks manager is particularly dire. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - If opening the CRX file for unpacking fails, this integer is the error code - given by the OS. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions with event pages that have no registered event - listeners at profile startup. (This may indicate something has gone wrong; - such event pages will never get started.) - - - - - - Replaced by Extensions.EventPageActiveTime2. - - rdevlin.cronin@chromium.org - The time an extension's event page has spent loaded. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time between an extension's event page loading its first URL and the - event page later shutting down. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - The time an extension's event page has spent unloaded. - - - - - Replaced by Extensions.EventPageLoadTime2. - - rdevlin.cronin@chromium.org - The time for an extension's event page to load. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time taken for an extension's event page to load its initial URL. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Recorded every time an event is dispatched to an extension. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded every time an event is dispatched to a *component* extension. - Otherwise identical to Extensions.Events.Dispatched. - - - - - - Removed 21-Jan-2020. - - mfoltz@chromium.org - - Recorded every time an event is dispatched to a *component* extension with a - suspended event page. Otherwise identical to - Extensions.Events.DispatchWithSuspendedEventPage. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded every time an event is dispatched to an extension with a persistent - background page. The event may or may not have been dispatched to the - background page itself, for example it may have been dispatched to its - popup. When this metric is recorded, Extensions.Events.Dispatch will also be - recorded. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded every time an event is dispatched to an extension with an event - page that was already running (i.e. at some point had been woken from its - suspended state, see Extensions.Events.DispatchWithSuspendedEventPage). The - event may or may not have been dispatched to the event page itself, for - example it may have been dispatched to its popup. When this metric is - recorded, Extensions.Events.Dispatch will also be recorded. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded every time an event is dispatched to an extension with an event - page that was suspended. This implies that firing this event woke up the - event page. The event may or may not have been dispatched to the event page - itself, for example it may have been dispatched to its popup, but regardless - it will wake the event page. When this metric is recorded, - Extensions.Events.Dispatch will also be recorded. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Recorded when an extension is already disabled and a new disable reason is - added to the extension. The new disable reason is retrieved from the update - service data key reasons during an update check for extensions. - - - - - burunduk@chromium.org - snijhara@google.com - managed-devices@google.com - - Number of cached extensions on disk. Reported on Chrome OS during user - session start. - - - - - burunduk@chromium.org - snijhara@google.com - managed-devices@google.com - - Total size of .crx files in cache on disk. Reported on Chrome OS during user - session start. - - - - - - Removed 2019-05. - - rdevlin.cronin@chromium.org - - The amount of time taken to create a single extension object. This includes - parsing all the different extension manifest keys and initializating the - associated manifest data. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - The update service data key reasons that the update service encounters - during an update check session using update client when disabling an - extension. - - - - - - Removed in M77. - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - True if the cache of the extension frame map was hit during access on the IO - thread. - - - - - - Removed in M77. - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - True if the lookup for a frame in the extension frame map succeeded after a - cache miss. - - - - - - Removed 2019-11 - - rdevlin.cronin@chromium.org - - The maximum number of ExtensionHosts (primarily background/event pages) that - were actively loading at any one time, within the first minute of Chrome - startup. Emitted exactly one minute after startup. - - - - - - Removed 2019-11 - - rdevlin.cronin@chromium.org - - The maximum number of ExtensionHosts (primarily background/event pages) in - the queue awaiting being loaded (via an ExtensionHostQueue), within the - first minute of Chrome startup. Emitted exactly one minute after startup. - - - - - - Removed 2019-11 - - rdevlin.cronin@chromium.org - - The total number of ExtensionHosts that completed loading in the first - minute of Chrome startup. Emitted exactly one minute after startup. - - - - - - Removed 2019-11 - - rdevlin.cronin@chromium.org - - The total number of ExtensionHosts (primarily background/event pages) that - were added to a queue to start loading, within the first minute of Chrome - startup. These may or may not end up starting, let alone finishing, - depending on the queue behavior. Emitted exactly one minute after startup. - - - - - - - rdevlin.cronin@chromium.org - - Emitted when an extension is downloaded by the user (including webstore - installs). - - - - - - - rdevlin.cronin@chromium.org - - The install location for a given extension. Recorded once per enabled - extension on profile initialization. - - - - - - Removed 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during ExtensionManagement::Refresh. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Recorded when an extension that was previously only disabled remotely is - re-enabled remotely during an update service session. - - - - - - Removed 4/2016. ExtensionRendererState was replaced with ExtensionFrameMap. - - rdevlin.cronin@chromium.org - - True if the cache for the ExtensionRendererState was hit during a lookup. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Length of the Extensions dir path inside the profile directory. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken for the ExtensionService to initialize, including the time it - takes to load the extensions for the service's profile and parse their - manifests. This happens during startup and also any time a new profile is - loaded. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken for the ExtensionService to notify all ready listeners that the - extension system is now ready. This happens as part of the total - initialization time of ExtensionService, measured in - Extensions.ExtensionServiceInitTime. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - An extension has been uninstalled. - - - - - Expired. - - waffles@chromium.org - - Records the error codes of the extension updater update check errors. These - events are triggered only when the extension updater gets an error for the - first time (before any retry) in the update check phase for a google.com - domain. - - - - - - Expired. - - waffles@chromium.org - - Records the error codes of the extension updater update check errors. These - events are triggered only when the extension updater gets an error for the - first time (before any retry) in the update check phase for a non google.com - domain. - - - - - - Expired. - - waffles@chromium.org - - The number of extensions that are checked for update. This number is emitted - right before the extensions are split between the current extension updater - and the unified extension updater (if used). - - - - - - Expired. - - waffles@chromium.org - - The number of extensions that are passed over to the extension updater for - update check. Triggered when the extension updater starts doing update - check. - - - - - - Expired. - - waffles@chromium.org - - The number of extensions that have updates in an update check session. - Triggered when the extension updater found an update for an extension. - - - - - - Removed 2020-02. - - waffles@chromium.org - - Records the update results of extensions in an extension updater session, - grouped by ExtensionUpdaterUpdateResult. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Records what happens to extensions that are sideloaded, grouped by the - ExternalExtensionEvent enum. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of sideloaded apps/extensions loaded on startup grouped by - enabled/disabled state. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of extensions referenced in the external extensions source at path - chrome::DIR_EXTERNAL_EXTENSIONS. - - - - - - Expired 2018-08. - - rdevlin.cronin@chromium.org - - Whether or not the uninstallation of an external extension succeeded. - Triggered when the external install warning is shown to the user and the - user selects to remove the extension. - - - - - archanasimha@chromium.org - extensions-core@chromium.org - - Records when an extension with the chrome://favicon host permission makes a - network level request for a favicon resource. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time that elapsed during extensions::FeatureProvider::Static. - Only measured while in the browser process. - - - - - rdevlin.cronin@chromium.org - - The number of extensions (and friends) that could have been given access to - the file:// scheme, and were, for users that have at least one extension - that could have been given access. This excludes anything that doesn't show - up in chrome://extensions (platform apps, hosted apps, component - extensions), policy-installed extensions, and unpacked extensions. See also - Extensions.FileAccessNotAllowed. - - - - - rdevlin.cronin@chromium.org - - The number of extensions (and friends) that could have been given access to - the file:// scheme, but weren't, for users that have at least one extension - that could have been given access. This excludes anything that doesn't show - up in chrome://extensions (platform apps, hosted apps, component - extensions), policy-installed extensions, and unpacked extensions. See also - Extensions.FileAccessAllowed. - - - - - - Expired after M77. - - xiaohuic@chromium.org - - Record the time taken to physically move the extention files from temporary - location to the final installation directory. It includes the time to flush - the file system if ExtensionUseSafeInstallation field trial is enabled. This - is recorded once per extension install/update. - - - - - - Removed 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the FontSettingsEventRouter - construction. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - Number of enterprise policy forced extensions that are blacklisted and thus - not loaded after 5 minutes if at least one of policy forced extensions is - not yet enabled. - - - - - swapnilgupta@google.com - burunduk@chromium.org - poromov@chromium.org - - Status of cache entry about enterprise policy forced extension. Recorded for - each forced extension. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The last known intermediate stage of extension when the extension - installation stage if CREATED if failure reason was not recorded - (installation of an extension was neither yet finished nor failed). Recorded - for each forced extension that failed to install after 5 minutes. Recorded - together with "Extensions.ForceInstalledTimedOutCount" histogram, - but for every extension not installed at the moment. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The last known downloading stage of extension downloading process if failure - reason was not recorded and installing stage is DOWNLOADING, so it's - specification of Extensions.ForceInstalledStage. Recorded for each forced - extension that failed to install after 5 minutes. Recorded together with - "Extensions.ForceInstalledTimedOutCount" histogram, but for every - extension not installed at the moment. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Status of cache entry about enterprise policy forced extension which failed - to install. Recorded for each forced extension that failed to install after - 5 minutes. Recorded together with - "Extensions.ForceInstalledTimedOutCount" histogram, but for every - extension not installed at the moment. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Detailed reason why CRX installation failed for enterprise policy forced - extensions. Recorded for each forced extension that failed to install after - 5 minutes with Extensions.{OffStore,Webstore}_ForceInstalledFailureReason3 - equal to CRX_INSTALL_ERROR_*. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The detailed reason why enterprise policy forced extensions had failed to - install because fetched update manifest was invalid due to app status error. - Recorded for each forced extension that failed to install after 5 minutes - with Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID and - Extensions.ForceInstalledFailureManifestInvalidErrorDetail2 equal to - BAD_APP_STATUS. - - - - - - Removed 07/2020, replaced by - Extensions.ForceInstalledFailureManifestInvalidErrorDetail2. - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The detailed reason why enterprise policy forced extensions had failed to - install because fetched update manifest was invalid. Recorded for each - forced extension that failed to install after 5 minutes with - Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The detailed reason why enterprise policy forced extensions had failed to - install because fetched update manifest was invalid. Recorded for each - forced extension that failed to install after 5 minutes with - Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID. - - Replaced Extensions.ForceInstalledFailureManifestInvalidErrorDetail due to - addition of new error BAD_APP_STATUS, and some of the errors that were - MISSING_UPDATE_CHECK_TAG would now be reported as BAD_APP_STATUS. - - - - - snijhara@google.com - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The info field in the update manifest fetched from the server for enterprise - policy forced extensions. Recorded for each forced extension for which the - server responds with no updates and an empty CRX fetch url. Recorded for - each forced extension that failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - CRX_FETCH_URL_EMPTY. - - - - - - Removed 12/2019, replaced by Extensions.ForceInstalledFailureReason3. - - askaraitzhan@google.com - burunduk@chromium.org - poromov@chromium.org - rdevlin.cronin@chromium.org - - The reason why enterprise policy forced extensions were not installed. - Recorded for each forced extension that failed to install after 5 minutes. - Recorded together with "Extensions.ForceInstalledTimedOutCount" - histogram, but for every extension not installed at the moment. - - - - - - Removed 04/2020, replaced by Extensions.ForceInstalledFailureReason3. - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The reason why enterprise policy forced extensions were not installed. - Recorded for each forced extension that failed to install after 5 minutes. - Recorded together with "Extensions.ForceInstalledTimedOutCount" - histogram, but for every extension not installed at the moment. - - Replaced Extensions.ForceInstalledFailureReason because of splitting - CRX_FETCH_FAILED options into three dirrerent failures. - - - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The reason why enterprise policy forced extensions were not installed. - Recorded for each forced extension that failed to install after 5 minutes. - Recorded together with "Extensions.ForceInstalledTimedOutCount" - histogram, but for every extension not installed at the moment. - - Replaced Extensions.ForceInstalledFailureReason2 because of reporting - MANIFEST_INVALID instead of MANIFEST_FETCH_FAILED in case parsing update - manifest failed with different reasons for the extensions. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The reason why enterprise policy forced extensions had failed to unpack. - Recorded for each forced extension that failed to install after 5 minutes - with Extensions.ForceInstalledFailureReason3 equal to - CRX_INSTALL_ERROR_SANDBOXED_UNPACKER_FAILURE. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The type of session in case enterprise policy forced extensions were not - installed. Recorded for each force installed extension which failed to - install after 5 minutes. Supported only on ChromeOS and recorded only if - there is an active user. - - - - - - Removed 2020-08-28 because it is verified from the collected statistics that - we always receive "no update" status in case of - CRX_FETCH_URL_EMPTY. - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The update check status details for enterprise policy forced extensions when - update manifest is fetched from server. Recorded for each forced extension - that failed to install after 5 minutes. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Number of fetch retries made when CRX fetch failed for enterprise policy - forced extensions. Recorded for each forced extension that failed to install - after 5 minutes with - Extensions.{OffStore,Webstore}_ForceInstalledFailureReason3 equal to - CRX_FETCH_FAILED. - - - - - - Removed 2020-08-28, replaced by Extensions.ForceInstalledHttpErrorCode2. - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - HTTP error code for the last retry attempt when CRX fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - CRX_FETCH_FAILED and a HTTP response code was received. HTTP response code - is received only if there was no network error. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - HTTP error code for the last retry attempt when CRX fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - CRX_FETCH_FAILED and a HTTP response code was received. HTTP response code - is received only if there was no network error. Replaced - Extensions.ForceInstalledHttpErrorCode because error codes are now reported - only when network error code is HTTP_RESPONSE_CODE_FAILURE. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The amount of time elapsed during installation of enterprise policy forced - extensions. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Number of fetch retries made when Manifest fetch failed for enterprise - policy forced extensions. Recorded for each forced extension that failed to - install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - MANIFEST_FETCH_FAILED. - - - - - - Removed 2020-08-28, replaced by - Extensions.ForceInstalledManifestFetchFailedHttpErrorCode2. - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - HTTP error code for the last retry attempt when Manifest fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - MANIFEST_FETCH_FAILED and a HTTP response code was received. HTTP response - code is received only if there was no network error. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - HTTP error code for the last retry attempt when Manifest fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - MANIFEST_FETCH_FAILED and a HTTP response code was received. HTTP response - code is received only if there was no network error. Replaced - Extensions.ForceInstalledManifestFetchFailedHttpErrorCode because error - codes are now reported only when network error code is - HTTP_RESPONSE_CODE_FAILURE. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Network error code for the last retry attempt when Manifest fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - MANIFEST_FETCH_FAILED. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Network error code for the last retry attempt when CRX fetch failed for - enterprise policy forced extensions. Recorded for each forced extension that - failed to install after 5 minutes with - Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to - CRX_FETCH_FAILED. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - Records the disable reason for the enterpise policy forced extensions. - Recorded for each forced extension that installed but failed to load after 5 - minutes. If the extension is not disabled, it records - DisableReason::DISABLE_NONE. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Records whether there was a possible non-misconfiguration failure for the - enterprise policy forced extensions. Records true if in a session at least - one forced extension failed to install after 5 minutes with a - non-misconfiguration failure and false when all the forced extensions which - failed to install after 5 minutes failed due to some misconfiguration. - Recorded together with "Extensions.ForceInstalledTimedOutCount" - histogram. - - - - - - Removed 09/2020, replaced by Extensions.ForceInstalledStage2. - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The last known stage of extension installation process if failure reason was - not recorded (installation of an extension was neither yet finished nor - failed). Recorded for each forced extension that failed to install after 5 - minutes. Recorded together with - "Extensions.ForceInstalledTimedOutCount" histogram, but for every - extension not installed at the moment. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - The last known stage of extension installation process if failure reason was - not recorded (installation of an extension was neither yet finished nor - failed). Recorded for each forced extension that failed to install after 5 - minutes. Recorded together with - "Extensions.ForceInstalledTimedOutCount" histogram, but for every - extension not installed at the moment. - - Replaced Extensions.ForceInstalledStage because the stages that were used - for used for investigation of CREATED stage are moved to a new enum. - - - - - swapnilgupta@google.com - burunduk@chromium.org - managed-devices@google.com - - The amount of time elapsed during different stage of the installation - process for the enterprise policy forced extensions. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Number of enterprise policy forced extensions that are not installed after 5 - minutes if at least one of policy forced extensions is not yet enabled. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Number of enterprise policy forced extensions that are not loaded after 5 - minutes timeout, while might be already installed. - - - - - burunduk@chromium.org - swapnilgupta@google.com - managed-devices@google.com - - Total amount of extensions in force installed list. Gets recorded on profile - open (which happens on every startup and when user logs in) and tries to - load extensions. Number of records should correspond to the sum of records - in "Extensions.ForceInstalledLoadTime" and records in - "Extensions.ForceInstalledTimedOutAndNotInstalledCount". - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of apps/extensions loaded on startup with an inconsistent "from - webstore" state. This means an item that is flagged as from_webstore, - but with either a non-webstore update_url or an external install location. - - - - - - Replaced by Extensions.Functions.ComponentExtensionCalls, - Extensions.Functions.ExtensionCalls, and Extensions.Functions.WebUICalls - 2019-05. - - rdevlin.cronin@chromium.org - Number of calls to extension functions. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when a component extension calls an extension API. Recorded once - per function call. See also Extensions.Functions.WebUICalls and - Extensions.Functions.ExtensionCalls. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when a non-component extension calls an extension API. Recorded - once per function call. See also Extensions.Functions.WebUICalls and - Extensions.Functions.ComponentExtensionCalls. - - - - - lazyboy@chromium.org - dbertoni@chromium.org - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when an extension service worker calls an extension API. Note that - the function would also be included in either - Extensions.Functions.ExtensionCalls or - Extensions.Functions.ComponentExtensionCalls histogram. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when an extension function call fails and finishes execution. The - suffix indicates the exact bucket the function is in. See also - Extensions.Functions.FailedTotalExecutionTime. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The total amount of time it took to execute an extension function that - failed from the time the extension function is called to the time the - function responds. Note that since some extension functions are inherently - slow (anything that requires user interaction, for instance), this is not a - definitive source for function performance. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time it takes to handle a response for an extension API - request. Recorded on the renderer side once we receive the response IPC from - the browser and have deserialized the arguments and passed them to the JS - context. Only recorded if the response is successfully handled. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time it takes to start an extension API request. Recorded on - the renderer side after we perform JS pre-processing, but includes all - serialization and dispatching. Only recorded if the request is successfully - dispatched. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when an extension function call succeeds and finishes execution. - The suffix indicates the exact bucket the function is in. See also - Extensions.Functions.SucceededTotalExecutionTime. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The total amount of time it took to execute an extension function that - succeeded from the time the extension function is called to the time the - function responds. Note that since some extension functions are inherently - slow (anything that requires user interaction, for instance), this is not a - definitive source for function performance. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The synchronous amount of time an extension function takes. Note that many - extension functions run asynchronously; see also - Extensions.Functions.[Succeeded|Failed]TotalExecutionTime. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Recorded when a WebUI context calls an extension API. Recorded once per - function call. See also Extensions.Functions.ComponentExtensionCalls and - Extensions.Functions.ExtensionCalls. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - What happens when the extensions system tries to get a temp dir to unpack - in? - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records requests to use resources from Google Docs Offline - extension, along with whether the extension has been available or not and - the request has been done from incognito mode or not. Note that this request - is double counted for the imports. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it is - automatically disabled due to a permission increase (e.g., after an - extension upgrade). To find places where this histogram may be emitted, look - for calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument AutoDisable. For Sync users, this may be reported for each device, - depending on whether the Sync update or the extension auto-update happen - first. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it was - installed. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument Install. For Sync users, this is reported for each device. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when installation - was aborted (e.g. because the parent window of the confirmation dialog went - away), not including installation errors and user cancels. To find places - where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - InstallAbort. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when installation - was canceled. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument InstallCancel. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it was - loaded (which happens at profile open or extension install). To find places - where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument Load. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it was - re-enabled from a confirmation prompt. To find places where this histogram - may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - ReEnable. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when the - re-enable prompt was aborted (e.g. because the parent window of the - confirmation dialog went away), not including installation errors and manual - user cancels. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument ReEnableAbort. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when the - re-enable was canceled from the confirmation prompt. To find places where - this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - ReEnableCancel. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it was - uninstalled. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument Uninstall. For Sync users, this is reported for each device. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when it was - installed through the web store. To find places where this histogram may be - emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - WebStoreInstall. Contrary to the more-general HasPermissions_Install3 - histogram, this one is NOT reported for each device. - - - - - - Code removed 2020-06. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when installation - from the web store was aborted (e.g. because the parent window of the - confirmation dialog went away), not including installation errors and user - cancels. To find places where this histogram may be emitted, look for calls - to ExtensionService::RecordPermissionMessagesHistogram with the argument - WebStoreInstallAbort. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Whether there were any permissions present in an extension when installation - from the web store was canceled. To find places where this histogram may be - emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - WebStoreInstallCancel. - - - - - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - The number of enabled extensions with a homepage override specified in their - manifest. Recorded once per profile at profile initialization. - - - - - benwells@chromium.org - dominickn@chromium.org - - Records the container used for a hosted app launch. The definition of - 'launch' for the purposes of this histogram is different to that used for - the launch type histograms. This definition is less inclusive, for example - it does not include navigations to the hosted app due to normal browsing, - which the other definition does include. This definition could be thought of - more as explicit launches via a launch surface such as the app launcher, - chrome://apps, or a shortcut. - - - - - - Expired 2018-08 - - rdevlin.cronin@chromium.org - - The usage (in kilobytes) of persistent storage in a hosted app with the - unlimitedStorage permission. This is logged each time the storage is used*, - so this also serves as a cap of the number of calls that would fail if the - app did not have the unlimited storage permission. *Capped at once per 30 - seconds so as to not impact performance. - - - - - - Expired 2018-08 - - rdevlin.cronin@chromium.org - - The percentage of "normal" (that is, not unlimited) quota that a - hosted app with unlimited storage is currently using. This is logged each - time the storage is used*, so the number of times the app would use greater - than 100% of the default storage can serve as a cap for the number of calls - that would fail if the app did not have the unlimitedStorage permission. - *Capped at once per 30 seconds so as to not impact performance. - - - - - - Expired 2018-08-30 - - rdevlin.cronin@chromium.org - - The usage (in kilobytes) of a hosted app with the unlimitedStorage api - permission, recorded once per run per app the first time we load storage for - the hosted app. This is separate from the other metrics on hosted app - unlimited storage usage because it is logged once per extension per run. - - - - - - - rdevlin.cronin@chromium.org - - The number of extensions (and friends) that could have been allowed in - incognito, and were, for users that have at least one extension that could - have been allowed. This excludes anything that doesn't show up in - chrome://extensions (platform apps, hosted apps, component extensions), - policy-installed extensions, and unpacked extensions. See also - Extensions.IncognitoNotAllowed. - - - - - rdevlin.cronin@chromium.org - - The number of extensions (and friends) that could have been allowed in - incognito, but weren't, for users that have at least one extension that - could have been allowed. This excludes anything that doesn't show up in - chrome://extensions (platform apps, hosted apps, component extensions), - policy-installed extensions, and unpacked extensions. See also - Extensions.IncognitoAllowed. - - - - - - Removed 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during - ExtensionPrefs::InitExtensionControlledPrefs. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time that elapsed during the GetExtensions call within - ExtensionPrefs::InitPrefStore. - - - - - - Removed 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during ExtensionPrefs::InitPrefStore. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The amount of time for a CSS file to be injected into a page. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken to execute all scripts for one location within an extension. - Recorded every time content scripts injected by extensions are executed. - Unlike Extensions.InjectScriptTime, this includes execution time of - asynchronously injected scripts. - - - - - - - rdevlin.cronin@chromium.org - - Number of blocking scripts injected at document end by extensions. - - - - - - - rdevlin.cronin@chromium.org - Number of scripts injected at document end by extensions. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken to inject all scripts at document end by extensions. Not reported - if scripts are executed asynchronously. - - - - - - - rdevlin.cronin@chromium.org - - Number of blocking scripts injected at document idle by extensions. - - - - - - - rdevlin.cronin@chromium.org - Number of scripts injected at document idle by extensions. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken to inject all scripts at document idle by extensions. Not - reported if scripts are executed asynchronously. - - - - - - Removed 03/2017 in favor of Extensions.InjectedScriptExecutionTime. - - rdevlin.cronin@chromium.org - Time taken to inject all scripts by extensions. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Number of blocking scripts injected at document start by extensions. - - - - - - - rdevlin.cronin@chromium.org - Number of css files injected by extensions. - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Number of scripts injected at document start by extensions. - - - - - - rdevlin.cronin@chromium.org - - Time taken to inject css/scripts at document start by extensions. Not - reported if scripts are executed asynchronously. - - - - - - Obsolete as of 2019-05 as it can be derived by comparing the aggregate - counts of Extensions.InstallPrompt.TimeToInstall and - Extensions.InstallPrompt.TimeToInstall. - - meacer@chromium.org - - Whether the user accepted or aborted an extension installation. - - - - - kelvinjiang@chromium.org - extensions-core@chromium.org - - Time from first display of the extension installation prompt until the user - aborts the installation through clicking the cancel button or dismissing the - dialog. - - - - - kelvinjiang@chromium.org - extensions-core@chromium.org - - Time from first display of the extension installation prompt until the user - accepts the installation. Will always be greater than 500ms as the install - option is enabled after that time has elapsed. - - - - - - Stopped recording 2019-07. The previous enum was garbled. - - meacer@chromium.org - - Type of the extension install prompt displayed when an extension - installation is triggered. - - - - - meacer@chromium.org - rdevlin.cronin@chromium.org - - Type of the extension install prompt displayed when an extension - installation is triggered. Replaced Extensions.InstallPrompt.Type 2019-07. - - - - - meacer@chromium.org - - Actions on the show details link grouped by action type when the install - prompt trial is running. - - - - - meacer@chromium.org - - Actions on the show permissions link grouped by action type when the install - prompt trial is running. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Installs grouped by the location property in prefs. - - - - - - rdevlin.cronin@chromium.org - Installs grouped by Extension::HistogramType. - - - - peter@chromium.org - - The number of options provided to the GetToken request. Recorded when the - extension has made a call to chrome.instanceID.getToken(). - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - The amount of elapsed time taken to render an icon against a specified - background color and determine whether it would be visible to the user. - Recorded every time the analysis code is called. - - - - - - - rdevlin.cronin@chromium.org - The number of extensions and themes loaded at profile open. - - - - - - rdevlin.cronin@chromium.org - - Time taken to load all component extensions at profile open. This happens as - part of the total initialization time of ExtensionService, measured in - Extensions.ExtensionServiceInitTime. - - - - - - Removed as of 2019-11. Replaced by Extensions.LoadAllTime2. - - rdevlin.cronin@chromium.org - - Time taken to load all non-component extensions at profile open. This - happens as part of the total initialization time of ExtensionService, - measured in Extensions.ExtensionServiceInitTime. - - - - - - - rdevlin.cronin@chromium.org - - Time taken to load all non-component extensions at profile open and record - metrics. This happens as part of the total initialization time of - ExtensionService, measured in Extensions.ExtensionServiceInitTime. - - - - - - - rdevlin.cronin@chromium.org - The number of apps loaded by each user at profile open. - - - - - - rdevlin.cronin@chromium.org - - The number of externally managed apps loaded by each user at profile open. - - - - - - - rdevlin.cronin@chromium.org - - The number of user-installed apps loaded by each user at profile open. - - - - - - - rdevlin.cronin@chromium.org - - The number of browser action extensions loaded at profile open. - - - - - - Removed as of 4/2015. Replaced by ManagedUsers.Whitelist.Count. - - asargent@chromium.org - - The number of content-pack extensions loaded at profile open. - - - - - calamity@chromium.org - - The creation flags of all extensions loaded at profile open grouped by - Extension::InitFromValueFlags. - - - - - - - rdevlin.cronin@chromium.org - The number of extensions loaded at profile open. - - - - - - rdevlin.cronin@chromium.org - - The number of externally managed extensions loaded at profile open. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of user-installed extensions loaded at profile open. - - - - - - - rdevlin.cronin@chromium.org - - The number of externally managed extensions and apps loaded at profile open. - - - - - - - rdevlin.cronin@chromium.org - - The number of hosted apps loaded by each user at profile open. - - - - - - - rdevlin.cronin@chromium.org - - The number of extensions that had neither a page nor browser action - specified in their manifest. Recorded at profile open. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of enabled extensions or apps the user has installed that do not - update from the Chrome Web Store. Recorded during profile initialization. - - - - - - - rdevlin.cronin@chromium.org - - The number of legacy packaged apps loaded by each user at profile open. - - - - - - - rdevlin.cronin@chromium.org - The number of platform apps loaded at profile open. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - The number of themes loaded at profile open. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions loaded at profile open grouped by - Extension::HistogramType. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of converted user scripts loaded at profile open. - - - - - isandrk@chromium.org - jhastings@chromium.org - - Records requests to enter or exit locked fullscreen mode through extension - APIs. Used only on Chrome OS. - - - - - - Removed June 2019. - - ksakamoto@chromium.org - - The amount of time taken to inject content scripts. If multiple scripts are - injected within a single task, this records the time taken to execute all - the scripts. - - This metric only logs tasks longer than 50 milliseconds. This threshold - aligns with the definition of "long task" in Long Tasks API - (https://w3c.github.io/longtasks/). - - Note that this histogram itself doesn't tell you what percentage of content - scripts are greater than 50 ms. See Extensions.Inject{Start,End,Idle}_Time - and Extensions.InjectedScriptExecutionTime.* for the overall distribution. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of times chrome retried to download an extension update manifest with - a url on a google.com domain, before eventually giving up. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of times chrome retried to download an extension update manifest with - a url on a non google.com domain, before eventually giving up. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of times chrome retried to download an extension update manifest with - a url on a google.com domain, before eventually succeeding. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of times chrome retried to download an extension update manifest with - a url on a non google.com domain, before eventually succeeding. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether an icon that's specified in the manifest is considered - visible by our icon analysis code. This stat is only for packed extensions, - which we check dynamically when the icon is requested. The stat is emitted - the first time the default icon is requested, since we cache the icon that's - selected. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether an icon that's specified in the manifest is considered - visible by our icon analysis code. This stat is only for packed extensions, - which we check dynamically when the icon is requested. The stat is emitted - the first time the default icon is requested, since we cache the icon that's - selected. - - This replaces the previous stat, ManifestIconSetIconWasVisibleForPacked, due - to a change to our analysis algorithm. The new algorithm renders the icon - against the toolbar background color and determines how visible the - resulting pixels are. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether loading an icon declarated in the extension's manifest icon - set is considered visible by our icon analysis code. This stat is only for - unpacked extensions, which we check at load time. - - - - - dbertoni@chromium.org - extensions-core@chromium.org - - Reports whether loading an icon declarated in the extension's manifest icon - set is considered visible by our icon analysis code. This stat is only for - unpacked extensions, which we check at load time. - - This replaces the previous stat, ManifestIconSetIconWasVisibleForUnpacked, - due to a change to our analysis algorithm. The new algorithm renders the - icon against the toolbar background color and determines how visible the - resulting pixels are. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of extension loads on startup where it is necessary to reload the - mainfest because the locale has changed. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of extension loads on startup where it is not necessary to reload the - extension's manifest. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of extension loads on startup where it is necessary to reload the - manifest because the extension is unpacked. - - - - - - - rdevlin.cronin@chromium.org - The manifest version of each loaded extension. - - - - rdevlin.cronin@chromium.org - - The number of ports created in a given script context at a specific time. - Recorded once at the destruction of the script context (when no more ports - could be created) if and only if at least one port was created in the - context. Only includes ports to extension contexts (i.e., not ports created - to tabs or native apps). - - - - - rdevlin.cronin@chromium.org - - The total amount of time between when an extension opens a new channel and - when it receives the global port id from the browser and can begin sending - messages. - - - - - rdevlin.cronin@chromium.org - - The amount of synchronous time taken for the renderer to request an - extension message port id from the browser when a new channel is first - opened by an extension. - - - - - - Removed January 2020. - - rdevlin.cronin@chromium.org - nharper@chromium.org - - The behavior for including the TLS channel ID in the information sent with - extension messaging. Recorded once per opened channel. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The size, in bytes, of a message sent from an extension using one of the - messaging APIs (e.g. chrome.runtime.sendMessage). All message sizes are - logged, but messages over 64 MB in size aren't sent. - - - - - rdevlin.cronin@chromium.org - - The amount of time for the renderer to inform the browser process of a new - port being created with a certain id. This replaces the flow for - Extensions.Messaging.GetPortId[A]SyncTime. - - - - - ekaramad@chromium.org - wjmaclean@chromium.org - - Reports the creation of MimeHandlerViews and usage of postMessage for cross - and same origin resources. - - - - - battre@chromium.org - karandeepb@chromium.org - extensions-core@chromium.org - Time that network requests were blocked due to extensions. - - - - battre@chromium.org - karandeepb@chromium.org - extensions-core@chromium.org - - Percentage of total lifetime a network request was blocked due to an - extension. - - - - - - Removed June 2019. - - battre@chromium.org - - Time that network requests were blocked due to relevant rule registries - loading. - - - - - - Never used. Added to source 06/2012. Removed from source and added here - 09/2016. - - - Delay of network requests due to waiting for extension declarativeWebRequest - rules to be loaded from disk at startup. - - - - - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - The number of enabled extensions with a New Tab Page override specified in - their manifest. Recorded once per profile at profile initialization. - - - - - - - rdevlin.cronin@chromium.org - - The number of apps/extensions with a non-webstore update_url loaded at - startup time grouped by Extension::Location. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Number of non-WebStore extensions on startup that override the new tab page. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_AutoDisable2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it is automatically disabled - due to a permission increase (e.g., after an extension upgrade). - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_AutoDisable3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it is automatically disabled - due to a permission increase (e.g., after an extension upgrade). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it is automatically disabled - due to a permission increase (e.g., after an extension upgrade). To find - places where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - AutoDisable. For Sync users, this may be reported for each device, depending - on whether the Sync update or the extension auto-update happen first. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_Install2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was installed. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_Install3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was installed. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it was installed. To find - places where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - Install. For Sync users, this is reported for each device. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_InstallAbort2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation was aborted, not - including installation errors and user cancels. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_InstallAbort3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation was aborted, not - including installation errors and user cancels. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when installation was aborted (e.g. - because the parent window of the confirmation dialog went away), not - including installation errors and user cancels. To find places where this - histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - InstallAbort. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_InstallCancel2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation was canceled. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_InstallCancel3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation was canceled. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when installation was canceled. To - find places where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - InstallCancel. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_Load2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - The permissions present in an extension when it was loaded. - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_Load3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - The permissions present in an extension when it was loaded. - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it was loaded (which happens at - profile open or extension install). To find places where this histogram may - be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument Load. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_ReEnable2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was re-enabled from a - confirmation prompt. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_ReEnable3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was re-enabled from a - confirmation prompt. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it was re-enabled from a - confirmation prompt. To find places where this histogram may be emitted, - look for calls to ExtensionService::RecordPermissionMessagesHistogram with - the argument ReEnable. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_ReEnableAbort2. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when the re-enable prompt was - aborted, not including installation errors and manual user cancels. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_ReEnableAbort3. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when the re-enable prompt was - aborted, not including installation errors and manual user cancels. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when the re-enable prompt was - aborted (e.g. because the parent window of the confirmation dialog went - away), not including installation errors and manual user cancels. To find - places where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - ReEnableAbort. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_ReEnableCancel2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when the re-enable was canceled from - the confirmation prompt. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_ReEnableCancel3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when the re-enable was canceled from - the confirmation prompt. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when the re-enable was canceled from - the confirmation prompt. To find places where this histogram may be emitted, - look for calls to ExtensionService::RecordPermissionMessagesHistogram with - the argument ReEnableCancel. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_Uninstall2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was uninstalled. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_Uninstall3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was uninstalled. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it was uninstalled. To find - places where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - Uninstall. For Sync users, this is reported for each device. - - - - - - Removed as of 5/2014, replaced by Extensions.Permissions_WebStoreInstall2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was installed through the - web store. - - - - - - Removed as of 6/2015, replaced by Extensions.Permissions_WebStoreInstall3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when it was installed through the - web store. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when it was installed through the - web store. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument WebStoreInstall. Contrary to the more-general Permissions_Install3 - histogram, this one is NOT reported for each device. - - - - - - Removed as of 5/2014, replaced by - Extensions.Permissions_WebStoreInstallAbort2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation from the web store - was aborted, not including installation errors and user cancels. - - - - - - Removed as of 6/2015, replaced by - Extensions.Permissions_WebStoreInstallAbort3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation from the web store - was aborted, not including installation errors and user cancels. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when installation from the web store - was aborted (e.g. because the parent window of the confirmation dialog went - away), not including installation errors and user cancels. To find places - where this histogram may be emitted, look for calls to - ExtensionService::RecordPermissionMessagesHistogram with the argument - WebStoreInstallAbort. - - - - - - Removed as of 5/2014, replaced by - Extensions.Permissions_WebStoreInstallCancel2. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation from the web store - was canceled. - - - - - - Removed as of 6/2015, replaced by - Extensions.Permissions_WebStoreInstallCancel3. - - rdevlin.cronin@chromium.org - rpaquay@chromium.org - - The permissions present in an extension when installation from the web store - was canceled. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The permissions present in an extension when installation from the web store - was canceled. To find places where this histogram may be emitted, look for - calls to ExtensionService::RecordPermissionMessagesHistogram with the - argument WebStoreInstallCancel. - - - - - rdevlin.cronin@chromium.org - - The time taken between a user clicking on a button to open a popup, and the - popup finishing loading its initial URL. This is a good way to measure the - UI responsiveness of extension popups. It will be strictly larger than - Extensions.PopupLoadTime2, which only measures the time it takes to load - - there may be a delay between clicking and starting to load, for example, if - the popup's host got caught in a queue. - - - - - - Replaced by Extensions.PopupLoadTime2. - - rdevlin.cronin@chromium.org - The time for an Extension's popup to load. - - - - rdevlin.cronin@chromium.org - - The time taken for an extension popup to load its initial URL. This may not - include the time taken for an extension process to start, if the extension - already has a background page running. It does not necessarily correlate - with the amount of time since the popup was *clicked* either, since there - may be a delay between the user clicking and the loading started. - Extensions.PopupCreateTime measures this instead. - - - - - tnagel@chromium.org - chrome-privacy-core@chromium.org - - The number of extensions reported in chrome://management ui with powerful - permissions. This number is recorded every time the user opens - chrome://management ui. - - - - - - Replaced by Extensions.ProcessManagerStartupHostsTime2 - 12/2019 - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time taken to start up persistent background pages for extensions in - ExtensionProcessManager when the extension system notifies that it is ready. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The time taken to start up persistent background pages for extensions in - ExtensionProcessManager when the extension system notifies that it is ready. - This version of the histogram does not include cases where the background - page startup is deferred, which would have been logged as ~0ms startup in - Extensions.ProcessManagerStartupHostsTime. - - - - - rdevlin.cronin@chromium.org - treib@chromium.org - - Whether the DISABLE_PERMISSIONS_INCREASE disable reason was removed from an - extension while checking for a permissions increase. Recorded during startup - and on reload and update, for each extension that has the - DISABLE_PERMISSIONS_INCREASE reason. - - - - - - Stopped recording 2019-07. Data no longer needed. - - extensions-core@chromium.org - - The initialization latency (in milliseconds) introduced to each extension - resource request by querying the directory timestamp. - - - - - lazyboy@chromium.org - - The difference in seconds between an extension resource's last modification - time and its extension base directory's creation time. Recorded on each - extension resource request if the difference is non-negative (i.e., the - resource's last modification time is more recent than the directory's - creation time.) For cases where the directory creation date is more recent, - see Extensions.ResourceLastModifiedNegativeDelta instead. - - - - - lazyboy@chromium.org - - The absolute difference in seconds between an extension resource's last - modification time and extension base directory's creation time. Recorded on - each extension resource request if the difference is negative (i.e., the - directory's creation time is more recent than the resource's last - modification time.) For cases where the resource modification time is more - recent, see Extensions.ResourceLastModifiedDelta instead. - - - - - - - rdevlin.cronin@chromium.org - karandeepb@chromium.org - - Whether an extension had host permissions withheld as a result of the - RuntimeHostPermissions feature. Recorded once per extension at profile - initialization if and only if the RuntimeHostPermissions feature is enabled - and the extension requests any host permissions (i.e., could be affected by - the feature). - - - - - - - rdevlin.cronin@chromium.org - karandeepb@chromium.org - - The number of hosts an extension has been granted explicit access to that it - also requested (note that if the user granted unrequested hosts, those will - not be included in this count). Recorded once per extension at profile - initialization if and only if the RuntimeHostPermissions feature is enabled - and the extension has had host permissions withheld. See also - Extensions.RuntimeHostPermissions.ExtensionHasWithheldHosts. - - - - - - Can be inferred from SandboxUnpackFailureReason. - - extensions-core@chromium.org - - Count the number of times a sandboxed extension unpack fails. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The reason an extension failed to unpack, recorded when a failure occurs. - - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Time taken to unpack an extension, when the unpack fails. - - - - achuith@chromium.org - - Whether a CRX file hash sum was the same as in an updater manifest. - - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Length of the initial path to the CRX to be unpacked. - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Length of the normalized (link/junction free) path to the temporary copy of - a CRX made during unpacking. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which a CRX file is unpacked in Kilobytes per second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files 1MB to 2MB are unpacked in Kilobytes per second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files 2MB to 5MB are unpacked in Kilobytes per second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files 50kB to 1MB are unpacked in Kilobytes per second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files 5MB to 10 MB are unpacked in Kilobytes per second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files larger than 10MB are unpacked in Kilobytes per - second. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - - Rate at which CRX files under 50 KB are unpacked in Kilobytes per second. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Count the number of times a sandboxed CRX unpack succeeds. - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Count the number of times a sandboxed CRX unpack succeeds, but we can't get - the file size. - - - - - - Code removed 2020-04. - - extensions-core@chromium.org - Size of the .crx file, in KB, when the unpack succeeds. - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Time taken to unpack an extension, when the unpack succeeds. - - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - Length of the path of the temporary copy of a CRX made during unpacking. - - - - - - Code removed 2020-04. No longer being monitored. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Length of the path under which a CRX is unpacked. - - - - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - The number of enabled extensions with a search engine override specified in - their manifest. Recorded once per profile at profile initialization. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken on the settings overridden dialog that was shown to alert - the user of an extension overriding the New Tab Page, when the dialog shown - is the version that asks the user if they want to go back to Google's New - Tab Page. Recorded once per instance of the dialog being shown, after the - action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken on the settings overridden dialog that was shown to alert - the user of an extension overriding the default search provider, when the - dialog shown is the version that asks the user if they want to go back to - Google search. Recorded once per instance of the dialog being shown, after - the action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken on the settings overridden dialog that was shown to alert - the user of an extension overriding the default search provider, when the - dialog shown is the version that asks the user if they want to go back to a - previous search engine that isn't Google. Recorded once per instance of the - dialog being shown, after the action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken on the settings overridden dialog that was shown to alert - the user of an extension overriding the New Tab Page, when the dialog shown - is the generic version. Recorded once per instance of the dialog being - shown, after the action is taken. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action taken on the settings overridden dialog that was shown to alert - the user of an extension overriding the default search provider, when the - dialog shown is the generic version. Recorded once per instance of the - dialog being shown, after the action is taken. - - - - - - Removed in September, 2016 - - - Emitted when QuotaExceededError was called due to an extension using too - many bytes for a given setting. The number has no natural numerator - (normalizing factor) and thus is not particularly useful. - - - - - - Removed in September, 2016 - - - Emitted when QuotaExceededError was called due to an extension using too - many keys. The number has no natural numerator (normalizing factor) and thus - is not particularly useful. - - - - - - Removed in September, 2016 - - - Emitted when QuotaExceededError was called due to an extension using too - many bytes. The number has no natural numerator (normalizing factor) and - thus is not particularly useful. - - - - - - Removed in July 2019. - - alexmos@chromium.org - - When the web-accessible resource check in - ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this - records the reason for the failure. This check is performed on navigations - that utilize the OpenURL path as well as on transfers. - - - - - - Removed in July 2019. - - alexmos@chromium.org - - When the web-accessible resource check in - ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this - records the scheme of the SiteInstance that initiated the blocked load. This - check is performed on navigations that utilize the OpenURL path as well as - on transfers. - - - - - - This has not been recorded since at least mid-2013. - - asargent@chromium.org - The time one extension delays network requests at startup. - - - - - This has not been recorded since at least mid-2013. - - rdevlin.cronin@chromium.org - - The total time extensions delay network requests at startup. - - - - - rdevlin.cronin@chromium.org - kelvinjiang@chromium.org - - The number of enabled extensions with startup page overrides specified in - their manifest. Recorded once per profile at profile initialization. - - - - - - Removed 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during StorageFrontend::Init. - - - - - rdevlin.cronin@chromium.org - - The amount of synchronous time spent retrieving an extension's message - bundle (the collection of its i18n resources) from the browser. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The duration by which a network request was delayed while waiting for - extension user script load. Recorded once per request that is delayed, at - the time the resource resumes loading. - - - - - - Expired 2018-08. - - rdevlin.cronin@chromium.org - - The total number of network requests that were delayed by extension user - script load. Recorded once each time network requests may have been delayed - by user script load (i.e., once at the end of each batch of script loads). - - - - - - Removed June 2019. - - ksakamoto@chromium.org - - Time elapsed between two asynchronously-injected content script runs. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The source that triggered an extension action. Recorded once per invocation - of an extension action. - - - - - - Replaced by Extensions.Toolbar.PinnedExtensionCount2 in 2020/05. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that the user has pinned on the toolbar. Recorded - once per profile during initialization. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of extensions that the user has pinned on the toolbar. Recorded - once per profile during initialization if the user has at least one - extension with an action in the toolbar. - - - - - - Replaced by Extensions.Toolbar.PinnedExtensionPercentage2 in 2020/05. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The percentage of extensions that the user has pinned to the toolbar (i.e., - this will be 100 if the user has every extension pinned). Recorded once per - profile during initialization. - - - - - - Replaced by Extensions.Toolbar.PinnedExtensionPercentage3 in 2020/05. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The percentage of extensions that the user has pinned to the toolbar (i.e., - this will be 100 if the user has every extension pinned). Recorded once per - profile during initialization if the user has at least one extension with an - action in the toolbar. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The percentage of extensions that the user has pinned to the toolbar (i.e., - this will be 100 if the user has every extension pinned). Recorded once per - profile during initialization if the user has at least one extension with an - action in the toolbar. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Time taken to load a toolstrip. - - - - - Removed 2020-02. - - waffles@chromium.org - - Records the error codes of the unified extension updater download errors. - These events are triggered when the extension updater fails to download the - extension update package of an extension, which can happen only after the - updater has successfuly determined that there is an update for the - extension. - - - - - - Expired. - - waffles@chromium.org - - The number of extensions that are passed over to the unified extension - updater for update check. Triggered when the new extension updater starts - doing update check. - - - - - - Removed 2020-02. - - waffles@chromium.org - - Records the error codes of the unified extension updater update check - errors. These events are triggered only when the new extension updater gets - an error in the update check phase. - - - - - - Removed 2020-02. - - waffles@chromium.org - - Records the update results of extensions in an unified extension updater - session, grouped by ExtensionUpdaterUpdateResult. - - - - - - Removed 2020-02. - - waffles@chromium.org - - The update service errors that the update service encouters during an update - check session using update client. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The action that was taken from an extension uninstall dialog. Recorded once - per dialog shown. Only recorded if all possible actions (including report - abuse) were available on the dialog. - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The source for the extension uninstall. This is only recorded if an - uninstall dialog is shown to the user (i.e., it is not recorded for internal - "cleanups"). - - - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - Uninstalls grouped by Extension::HistogramType. - - - - - Stopped recording 2019-07. - - extensions-core@chromium.org - - Count failing CRX installs, grouped by the way an extension can be - installed. - - - - - - Code removed 2020-06. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The install source of an extension that failed to unpack correctly. Emitted - each time an extension fails to unpack from the CrxInstaller. - - - - - - Stopped recording 2019-07. - - extensions-core@chromium.org - - Count successful CRX installs, grouped by the cause of the install. - - - - - - Code removed 2020-06. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The install source of an extension that succeeded in unpacking correctly. - Emitted each time an extension successfully unpacks from the CrxInstaller. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of legacy packaged apps and hosted apps that were checked during - an update check. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of extensions that were checked during an update check. - - - - - - Removed 2019-01. - - waffles@chromium.org - Time in minutes between update checks. - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of crx's with a Google-hosted update URL that were checked during - an update check. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of crx's with no update URL checked during an update check. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of crx's with a non-Google update URL that were checked during an - update check. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of packaged apps that were checked during an update check. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of themes that were checked during an update check. - - - - - - Removed 3/2018 in https://crbug.com/357781 with the removal of the - extensions-update-frequency command line flag. - - catmullings@chromium.org - - Logs whether or not the extensions-update-frequency command line flag is - used. Recorded at profile creation if extensions autoupdate is enabled. - - - - - - Expired. - - waffles@chromium.org - - Counts the number of entries with the same extension ID found in the update - manifest of an update check request. When the update manifest does not - contain any update entry for an extension ID in the update check request, - the count will be 0. - - - - - - Expired. - - waffles@chromium.org - - The number of prodversionmin attributes appearing in an update manifest of - an update check request. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of extensions that were updated at browser startup. - - - - - - Removed 10/2013. - - Please list the metric's owners. Add more owner tags as needed. - - What happened when the extension updater tried to write a file? - - - - - Please list the metric's owners. Add more owner tags as needed. - Updates grouped by the location property in prefs. - - - - Please list the metric's owners. Add more owner tags as needed. - Updates grouped by Extension::HistogramType. - - - - apotapchuk@chromium.org - anqing@chromium.org - - Tracks the usage of different MIME type handlers used to view files. It is - recorded when the browser intercepts navigation with one of the type - handlers. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records any flags that were registered in the extraInfoSpec of a webRequest - listener, as well as the total number of listeners registered. Recorded each - time a new listener is registered. - - - - - - Removed November 2018. Replaced with Extensions.WebRequest.InitiatorAccess2. - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Describes the different cases pertaining to host permissions check for the - initiator URL of a network request. This is emitted whenever an extension is - found to have access to a request url, when checked by the WebRequest API. - - - - - - Removed April 2019. - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Describes the different cases pertaining to host permissions check for the - initiator URL of a network request. This is emitted whenever an extension is - found to have access to a request url for the WebRequest or Declarative Net - Request API. - - - - - yhirano@chromium.org - kinuko@chromium.org - - Whether and how keepalive requests are blocked. There is a similar histgoram - Net.KeepaliveRequest.BlockStatus. See there for the difference between the - two histograms. - - - - - - Removed 11/2018 as this is no longer needed. - - rockot@chromium.org - - Tracks whether any interesting response header modifications were made for - each request seen by the Web Request API. Logged for every network request - as long as one or more enabled extensions is using a declarative or blocking - filter to process onHeadersReceived events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M69. - - - - - rockot@chromium.org - - For every network request visible to the Web Request API, this indicates - whether any registered declarative rules or event listeners observed the - onBeforeSendHeaders event. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M69. - - - - - rockot@chromium.org - - For every network request visible to the Web Request API, this indicates - whether any registered declarative rules or event listeners observed the - onHeadersReceived event. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M69. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the request header added by extensions using the WebRequest API. - Recorded for each network request during the OnBeforeSendHeaders stage. - Multiple samples can be recorded per request. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the request header modified by extensions using the WebRequest API. - Recorded for each network request during the OnBeforeSendHeaders stage. - Multiple samples can be recorded per request. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the request header removed by extensions using the WebRequest API. - Recorded for each network request during the OnBeforeSendHeaders stage. - Multiple samples can be recorded per request. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the response header added by extensions using the WebRequest API. - This is logged for the cumulative delta across all the web request - extensions. Recorded for each network request during the OnHeadersReceived - stage. Multiple samples can be recorded per request. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the response header modified by extensions using the WebRequest API. - This is logged for the cumulative delta across all the web request - extensions. Recorded for each network request during the OnHeadersReceived - stage. Multiple samples can be recorded per request. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Records the response header removed by extensions using the WebRequest API. - This is logged for the cumulative delta across all the web request - extensions. Recorded for each network request during the OnHeadersReceived - stage. Multiple samples can be recorded per request. - - - - - - Removed May 2019. - - cduvall@chromium.org - karandeepb@chromium.org - - Whether the set-cookie response header was changed by an extension using the - Web Request API. Logged for every network request as long as one or more - enabled extensions is using a declarative or blocking filter to process - onHeadersReceived events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M73. - - - - - - Removed May 2019. - - cduvall@chromium.org - karandeepb@chromium.org - - Whether the set-cookie response header was removed by an extension using the - Web Request API. Logged for every network request as long as one or more - enabled extensions is using a declarative or blocking filter to process - onHeadersReceived events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M73. - - - - - - Removed 11/2018 as this is no longer needed. - - rockot@chromium.org - - Whether either or both of the special Accept-Language or User-Agent request - headers were removed by an extension using the Web Request API. Logged for - every network request as long as one or more enabled extensions is using a - declarative or blocking filter to process onBeforeSendHeaders events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M69. - - - - - - Removed April 2019. - - cduvall@chromium.org - karandeepb@chromium.org - - Whether Accept-Language, Accept-Encoding, User-Agent, Cookie, Referer, or - mulitple of these request headers were changed by an extension using the Web - Request API. Logged for every network request as long as one or more enabled - extensions is using a declarative or blocking filter to process - onBeforeSendHeaders events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M73. - - - - - - Removed April 2019. - - cduvall@chromium.org - karandeepb@chromium.org - - Whether Accept-Language, Accept-Encoding, User-Agent, Cookie, Referer, or - mulitple of these request headers were removed by an extension using the Web - Request API. Logged for every network request as long as one or more enabled - extensions is using a declarative or blocking filter to process - onBeforeSendHeaders events. - - This histogram is temporary, for investigating https://crbug.com/827582. It - can probably be removed by M73. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - The total time a network request took when at least one Web Request listener - was registered at the start of the request, and a listener was blocked on - the request. Measures from onBeforeRequest to onCompleted/onErrorOccurred, - and does not include canceled or redirected requests. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - The total time a network request took when at least one Web Request listener - with 'extraHeaders' in the extraInfoSpec was registered at the start of the - request. Measures from onBeforeRequest to onCompleted/onErrorOccurred, and - does not include canceled or redirected requests. - - - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - The total time a network request took when at least one Web Request listener - was registered at the start of the request. Measures from onBeforeRequest to - onCompleted/onErrorOccurred, and does not include canceled or redirected - requests. - - - - - - Removed as of Jan 2019. - - yhirano@chromium.org - - Whether cookies on a websocket connection are modified in - OnBeforeSendHeaders. - - This histogram is temporary, for investigating https://crbug.com/827582. - - - - - - Removed as of Jan 2019. - - yhirano@chromium.org - - Whether cookies on a websocket connection are modified in OnHeadersReceived. - - This histogram is temporary, for investigating https://crbug.com/827582. - - - - - - Removed as of Jan 2019. - - yhirano@chromium.org - ricea@chromium.org - - Whether certain headers are modified in OnBeforeSendHeaders. - - - - - - Removed as of Jan 2019. - - yhirano@chromium.org - - Tracks request headers modifications on a websocket connection in - OnBeforeSendHeaders. - - This histogram is temporary, for investigating https://crbug.com/827582. - - - - - - Removed as of Jan 2019. - - yhirano@chromium.org - - Whether response headers on a websocket connection are modified in - OnHeadersReceived. - - This histogram is temporary, for investigating https://crbug.com/827582. - - - - - - - karandeepb@chromium.org - - Counts the number of times an action is requested by extensions as part of - the Web Request API. For a given web request stage, multiple actions may be - logged. - - - - - karandeepb@chromium.org - extensions-core@chromium.org - - Number of enabled extensions which have requested the - "webRequestBlocking" permission. Includes all kinds of extensions, - including component and unpacked extensions. Recorded during profile - initialization. - - - - - karandeepb@chromium.org - rdevlin.cronin@chromium.org - - Number of enabled extensions which have requested the "webRequest" - permission. Includes all kinds of extensions, including component and - unpacked extensions. Recorded during profile initialization. - - - - - - Removed as of 11/2017. No longer relevant after refactoring. - - rdevlin.cronin@chromium.org - - Whether or not the render frame lookup for a given webRequest event - succeeded. - - - - - - Expired after M77. - - xiaohuic@chromium.org - - The time spent to download the crx file from the webstore to local disk. - This is recorded once per successful download. - - - - - Please list the metric's owners. Add more owner tags as needed. - The reason a webstore download was interrupted. - - - - Please list the metric's owners. Add more owner tags as needed. - - The number of KBytes received for a webstore download before it was - interrupted. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The total expected size in KBytes of an interrupted webstore download. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Tracks whether the total size of an interrupted webstore download was known. - - - - - dpapad@chromium.org - dbeam@chromium.org - - The amount of time between starting the provisional load and fully loading - the document in the main frame of the chrome://extensions page. This - corresponds to the WebContentsObserver::DocumentLoadedInFrame method. - - - - - dpapad@chromium.org - dbeam@chromium.org - - The amount of time between starting the provisional load and having - completed the onload handler in the main frame of the chrome://extensions - page. This corresponds to the - WebContentsObserver::DocumentOnLoadCompletedInMainFrame method. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Records whether adding a new/updated extension to the install verifier - succeeded. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The outcome of a call to ExtensionService::VerifyAllExtensions, whether it - was called for bootstrapping or another reason (extension - installed/uninstalled, etc.). - - - - - - Removed as of 09/2018, with the removal of the "Zip Unpacker" - component extension. - - yamaguchi@google.com - - Records the reason why the ZIP unpacker extension was disabled when the - service attempted to re-enable the extension upon startup. Each entry - indicates that the extension was disabled unintentionally and a fix was - attempted. - - - - - Please list the metric's owners. Add more owner tags as needed. - - When loading the chrome://extensions page, this records whether we decided - to do a verification check against the server (because the user had one or - more extensions disabled due to verification failure). - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of icons the Browser Actions Container knows about (visible or in - the overflow bucket). Does not count icons that have been permanently hidden - by the user. Measured once per startup per (non-incognito) profile. - - - - - - Stopped recording 2019-07. - - finnur@chromium.org - - The number of Browser Action icons the user has elected to permanently hide - (as opposed to putting them in the overflow bucket). Measured once per - startup per (non-incognito) profile. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of visible icons in the Browser Actions Container (visible as in - number of icons not in the overflow bucket). 0 means all icons are in the - overflow bucket. MAX_INT means the toolbar is always showing all icons. - Measured once per startup per (non-incognito) profile but only for those - profiles that have one or more browser actions showing in the toolbar. - - - - - lazyboy@chromium.org - The time taken to complete an extension url request. - - - - - Removed at 07/2019 because refactored DataPipeProducer does not provide the - net::Error code any more, and it reaches the planned expiry milestone. - - extensions-core@chromium.org - - The error code for failures of incremental reads of a file stream for a - chrome-extension:// URL. (See also ExtensionUrlRequest.OnReadCompleteResult - for the success case). - - - - - - Removed at 07/2019 because refactored DataPipeProducer does not provide the - reported value, and this metric was already broken, reporting always 0. - - lazyboy@chromium.org - extensions-core@chromium.org - - The result of an incremental read of a file stream for a chrome-extension:// - URL, representing a byte count. Logged in success cases (see also - ExtensionUrlRequest.OnReadCompleteError). - - - - - lazyboy@chromium.org - - When fetching a chrome-extension:// URL, this indicates the first byte - position we read from. This will be greater than 0 in cases such as XHR's - with a Range header, but will normally be 0 in the typical case of reading - the entire file. This helps identify how frequently partial file reads are - taking place. - - - - - lazyboy@chromium.org - - The total number of bytes read for a chrome-extension:// URL, logged when - the job is finished (either successfully or not). - - - - - pmarko@chromium.org - rogerta@chromium.org - - Record the validity of |rlz_embargo_end_date| in RW_VPD. This is recorded - when the VPD value is accessed, which may be multiple times in the same - chrome invocation. This is not recorded when the VPD value is missing. - - - - - agawronska@chromium.org - tobyhuang@chromium.org - xiqiruan@chromium.org - cros-families-eng@google.com - - Records the Chrome OS user session duration in milliseconds. Reports current - daily duration at the first session start on next day. This is only logged - for active usage time of device, determined by UsageTimeState::ACTIVE. - - - - - agawronska@chromium.org - tobyhuang@chromium.org - xiqiruan@chromium.org - cros-families-eng@google.com - - Records the Chrome OS user engagement hour within the current day (0-23), - total of weekday and weekend. Logged on - UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report the - same hour multiple times. - - - - - agawronska@chromium.org - tobyhuang@chromium.org - xiqiruan@chromium.org - cros-families-eng@google.com - - Records the Chrome OS user engagement hour of day (0-23) on weekday. Logged - on UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report - the same hour multiple times. - - - - - agawronska@chromium.org - tobyhuang@chromium.org - xiqiruan@chromium.org - cros-families-eng@google.com - - Records the Chrome OS user engagement hour of day (0-23) on weekend. Logged - on UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report - the same hour multiple times. - - - - - brucedawson@chromium.org - - Records several bits of information about whether the Windows - FaultTolerantHeap might be enabled. This is logged (from a delayed task) - when the browser process starts up. - - - - - victorvianna@google.com - jkrcal@chromium.org - - Records whether an icon already existed in the thumbnail DB when downloading - an on-demand one. On-demand icons are the ones added to local cache without - the user visiting the corresponding page. - - - - - - Removed as of 12/2017. - - fhorschig@chromium.org - - Records the number of favicon link tags on a page once the page has finished - loading. The count includes the automatically added favicon.ico entry. - - - - - - Removed as of 12/2017. - - fhorschig@chromium.org - - Records the number of favicon link tags with a non empty sizes attribute - once the page has finished loading. - - - - - - Removed as of 12/2017. - - fhorschig@chromium.org - - Records the number of apple-touch-icon and apple-touch-icon-precomposed link - tags once the page has finished loading. - - - - - - Removed as of 12/2017. - - fhorschig@chromium.org - - Records the number of icons requested until the best-fitting candidate was - found or there were no candidates left to check. More than 15 attempts are - unlikely and will be stored in overflow bucket 16. Less than 1 attempt means - an error happened; these cases are in bucket 0. - - - - - - Removed as of 12/2017. - - fhorschig@chromium.org - - Records whether a download succeeded, failed or was skipped because it has - failed previously. - - - - - mastiz@chromium.org - - Records the number of large icons that were fetched from the local cache - (e.g. during NTP impression), where the URL (of the page or the icon) - matches a hardcoded blacklist. Suspicious mismatches are reported as errors. - - - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Records the size (concretely the width) in pixel of the favicon downloaded - from Google favicon server (size 0 denotes that download has failed). - - - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Records the size (concretely the width) in pixel of the favicon that is used - to generate a fallback style in the case when large enough favicon is not - available (size 0 denotes that no favicon is available at all). - - - - - - - melandory@chromium.org - Net error codes for failed subscription requests. - - - - - Removed 2020-02. - - treib@chromium.org - melandory@chromium.org - - Recorded whenever the GCM client announces that some FCM messages were - deleted. Note that this does not record the number of deleted messages. - - - - - - - - - melandory@chromium.org - treib@chromium.org - - Status of the message from the FCM channel. Recorded upon receiving response - from the FCM channel. - - - - - - - melandory@chromium.org - treib@chromium.org - - Status of the initial attempt to retrieve the instance id token. - - - - - tschumann@chromium.org - treib@chromium.org - - Status of resetting the client instance ID, which includes unregistering - from FCM servers. - - - - - - - melandory@chromium.org - treib@chromium.org - - Status of subscription request to the Per User Topic server. Recorded upon - receiving response from server. - - - - - - - melandory@chromium.org - treib@chromium.org - - For each subcription request to the FCM Per-User-Topic server, log the - response received from the server. - - - - - - - melandory@chromium.org - treib@chromium.org - - For each subcription request to the FCM Per-User-Topic server, log the - response received from the server per topic. Note: This is only recorded - with a data type suffix. The base version is never recorded. - - - - - - Replaced in 2019-12 by FCMInvalidations.TokenStateOnRegistrationRequest2. - This first version did not record the "Token was cleared" bucket. - - melandory@chromium.org - treib@chromium.org - - Records the outcome of instance ID token requests (i.e. whether the token - changed). Such requests are made when invalidations are first enabled (e.g. - on sign-in), and then periodically every 24 hours. - - - - - - - melandory@chromium.org - treib@chromium.org - - Records the outcome of instance ID token requests (i.e. whether the token - changed). Such requests are made when invalidations are first enabled (e.g. - on sign-in), and then periodically every 24 hours. - - - - - - - melandory@chromium.org - treib@chromium.org - - Status of unsubscription request to the Per User Topic server. Recorded upon - receiving response from server. - - - - - - Removed in favor of ContentSuggestions.Feed.Offline.GetStatusCount. - - skym@chromium.org - - The number of urls that have offline status requested per call. - - - - - - Removed in favor of ContentSuggestions.Feed.Offline.GetStatusDuration. - - skym@chromium.org - - The number of milliseconds to round trip offline status for a set of URLs - from Offline Pages component. - - - - - - Removed in favor of ContentSuggestions.Feed.Scheduler.RefreshTrigger. - - skym@chromium.org - - The scheduler watches for various triggers, which cause it to decide if a - refresh is currently warranted or not. This histogram is emitted when a - trigger causes a refresh. - - - - - - Removed in favor of ContentSuggestions.Feed.Scheduler.RequestBehavior. - - skym@chromium.org - - When NTP is opened, the scheduler host tells the Feed library how to act, if - the existing content should be shown, immediately or with timeout, and if a - refresh request should be started. - - - - - weili@chromium.org - robliao@chromium.org - - Records how user interacts with Happiness Tracking Surveys (HaTS) bubble - prompt which is shown for a subset of users. Each time when the bubble is - shown, there should be one and only one enum type is recorded. - - - - - - Depcreated as of 08/2019. Replaced by - Feedback.HappinessTrackingSurvey.BubbleUsage. - - jeffreycohen@chromium.org - cyflee@chromium.org - - Reports on the responses to showing Happiness Tracking Surveys (HaTS) to a - subset of users. Records each time HaTS is shown. - - - - - sauski@google.com - msramek@chromium.org - - Records the first reason why the Happiness Tracking Surveys (HaTS) bubble - was or was not shown. While the request to show may not meet multiple - criteria, the first criterion is reported here. - - - - - afakhry@chromium.org - cros-telemetry@google.com - Records the source that requested showing the feedback app. - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: Counts the number of directory-changed events, - bucketed by the RootType of the directory newly displayed. - - - - - - Was removed from the code at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser - Specific actions taken by user such initiating - cloud import, canceling import, selecting a directory, or opting-in to - Drive>Photos sync. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: number of Computers a user has available in the - Files app. Computed every time the File Browser is opened (including file - picker dialogs). NOTE: This data is biased towards users that use the Files - App more often. - - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS File Browser opening mode. - - - - - Removed 2020-09. - - joelhockey@chromium.org - tbuckley@chromium.org - Dialog shown when using crostini app to open a file. - - - - - Removed 2020-09. - - joelhockey@chromium.org - tbuckley@chromium.org - - The depth from volume root of the path being shared. This is equivalent to - how many '/' are in the path. E.g. 'Downloads' or 'My Drive' has depth 0. - 'Downloads/foo/bar' has depth 2. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: time to scan a directory. Measured on every File - Browser directory change. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Tracks whether download destination is set to a Google Drive folder when the - download destination is changed by the user in the settings page. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Tracks whether download destination is set to a Google Drive folder on - startup. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The size of the space consumed by a users files in "My Files" - folder and it's children, calculated as a percentage of the total disk - space. Caluclated on user login. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The total size of all of the users files stored in the "My Files" - folder and it's children. Caluclated on user login. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: number of files and directories in the Downloads - directory (not including the contents of nested directories). Computed every - time the File Browser current directory changes to Downloads. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The time taken to calculate the hash of a file, only recorded if the time - exceeds a local threshold that is currenty 5 seconds. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The time taken to search for a file using it's hash value, only recorded if - the time exceeds a local threshold that is currently 1 second. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The type of file system provider that has been mounted. This metric is - emmitted on mounting of the filesystem. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: this is recorded when the user adds a folder - shortcut. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: number of saved folder shorcuts. This is recorded - when the Files app is launched. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: this is recorded when the user clicks or selects a - folder shortcut and is navigated to the target folder. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: this is recorded when the user removes a folder - shortcut. - - - - - austinct@chromium.org - - Chrome OS File Browser: this records the filesystem selected when formatting - an external drive. - - - - - - The bug which the UMA was investigating got fixed. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: time from the SuspendDone event to the DiskRemoved - event. The UMA is added temporarily for crbug.com/433734. - - - - - - The bug which the UMA was investigating got fixed. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: time from the DiskRemoved event to the Suspend - event. The UMA is added temporarily for crbug.com/433734. - - - - - slangley@chromium.org - - Chrome OS Files App: Whether an external media device was removed during the - upload process. - - - - - slangley@chromium.org - - Chrome OS Files App: Whether the media import process was cancelled. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The time taken to execute launcher search for drive files. Recorded when the - complete result set is returned from drive. - - - - - slangley@chromium.org - weifangsun@chromium.org - - The time taken to execute launcher search for local files. Recorded when the - complete result set has been calculated for files on the local disk. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser is an built-in extension without a background page. - Its main.html file is loaded every time the user opens a File Browser tab or - a file chooser dialog. The file is fairly large and the initialization is - pretty expensive. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: The locations (root types) of non-top-level entries - when they are expanded or collapsed (expand icon clicked) in the directory - tree. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: The locations (root types) of top-level entries (root - entries) when they are expanded or collapsed (expand icon clicked) in the - directory tree. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: The locations (root types) of non-top-level entries - when they are clicked in the directory tree. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: The locations (root types) of top-level entries (root - entries) when they are clicked in the directory tree. - - - - - slangley@chromium.org - - Chrome OS Files App: Whether the media import (Photos/Video) from external - media was cancelled. - - - - - slangley@chromium.org - - Chrome OS Files App: Count of duplicate media (Photos/Videos) files that - were skipped during a single upload session. - - - - - slangley@chromium.org - - Chrome OS Files App: Number of errors that occured during an upload session. - - - - - slangley@chromium.org - - Chrome OS Files App: Count of individual media (Photos/Videos) uploaded from - a single upload session. - - - - - slangley@chromium.org - - Chrome OS Files App: Size of the media (Photos/Videos) uploaded from a - single upload session. - - - - - slangley@chromium.org - - Chrome OS Files App: Whether the media import (Photos/Video) from external - media was started. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: The commands selected in the menu by the files app. - - - - - - Removed 2020-09. - - joelhockey@chromium.org - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: time to start and mount the crostini container in - order to show Linux Files. - - - - - fukino@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: Notification types what were shown to the user. - - - - - fukino@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: User actions responding to a notification. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The locations (root types) of files which are opened - by the file picker. - - - - - - Removed 4/2013, and replaced by FileBrowser.ViewingFileType. - - slangley@chromium.org - weifangsun@chromium.org - File types that were tried to be opened through browser. - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Editor: time to display an image. Measured from the moment - the user selected the image till the moment it is displayed (not counting - the low resolution preview). - - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS Photo Editor: the type of the file opened. - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS Photo Editor: the way the image has been loaded. - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS Photo Editor: time to load an image from a file. - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Editor: the result of a file save operation. - - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS Photo Editor: time to save an image to a file. - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Editor: size of an image file in megabytes. Measured on - every image load. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Editor: size of an image in megapixels. Measured on every - image load. - - - - - slangley@chromium.org - weifangsun@chromium.org - Chrome OS Photo Editor: the button which the user clicked. - - - - - Code seems to have been removed at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Import flow: action chosen in the Action Choice dialog for - the external device. - - - - - - Code seems to have been removed at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Import flow: the number of photos imported. Measured on - every successfull import operation. - - - - - - Code seems to have been removed at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Import flow: the percent of photos imported among all the - photos on the device. Measured on every successfull import operation. - - - - - - Code seems to have been removed at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Import flow: time to load the action dialog. Measured - between the moment window appears and the moment user see all available - actions for the device. - - - - - - Code seems to have been removed at an unknown time. - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Photo Import flow: time to scan the external device. - - - - - slangley@chromium.org - weifangsun@chromium.org - - File dialog type (e.g. Full page, Save as file) when quick view is launched. - - - - - slangley@chromium.org - weifangsun@chromium.org - File types that were tried to be opened with quick view. - - - - slangley@chromium.org - weifangsun@chromium.org - File types that were selected when quick view is launched. - - - - slangley@chromium.org - weifangsun@chromium.org - The volume type where quick view is opened. - - - - slangley@chromium.org - weifangsun@chromium.org - How quick view was opened. - - - - slangley@chromium.org - weifangsun@chromium.org - - Time to load a recently modified file list from Media Views. It is triggered - when the user opens or reloads Recent view in the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Time to load a recently modified file list from Crostini. It is triggered - when the user opens or reloads Recent view in the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Time to load a recently modified file list from Downloads. It is triggered - when the user opens or reloads Recent view in the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Time to load a recently modified file list from Drive. It is triggered when - the user opens or reloads Recent view in the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Time to load a recently modified file list from all sources. It is triggered - when the user opens or reloads Recent view in the Files app. - - - - - lucmult@chromium.org - majewski@chromium.org - Chrome OS File Browser: the source of file sharing action. - - - - - - lucmult@chromium.org - majewski@chromium.org - - Chrome OS File Browser: The number of files shared via a single Share - action. - - - - - lucmult@chromium.org - majewski@chromium.org - - Chrome OS File Browser: The type of the file shared via Share action. - Recorded for each file being shared by a share action - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: the reason why the suggest apps dialog was closed. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: whether the Webstore item user selected was - successfully installed or not. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: whether the initialization of the dialog succeeded - or not. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: time to load the suggest apps dialog. Measured - between the moment window appears and the moment all the contents in the - dialog including the Chrome Webstore widget are ready. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: number of Team Drives a user has available in the - Files app. Computed every time the File Browser is opened (including file - picker dialogs). NOTE: This data is biased towards users that use the Files - App more often. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS Files App: Recorded when the Grid View/List View toggle menu icon - is selected. - - - - - slangley@chromium.org - weifangsun@chromium.org - - File types that were tried to be viewed through browser. This is recorded - when the user tries to view a file from the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - File types that were tried to be viewed through browser while the user is - offline. This is recorded when the user tries to view a file from the Files - app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - File types that were tried to be viewed through browser while the user is - online. This is recorded when the user tries to view a file from the Files - app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The locations (root types) of files which are opened - in stand-alone mode. This does not include files opened in file picker mode. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The locations (root types) of files which are opened - in stand-alone mode while the user is offline. This does not include files - opened in file picker mode. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The locations (root types) of files which are opened - in stand-alone mode while the user is online. This does not include files - opened in file picker mode. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The type of the handler to be used to open files. - This is recorded when the user tries to view a file from the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The type of the handler to be used to open files - when the user is offline. This is recorded when the user tries to view a - file from the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: The type of the handler to be used to open files - when the user is online. This is recorded when the user tries to view a file - from the Files app. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: counts the number of times volumes are mounted for - each volume type. - - - - - slangley@chromium.org - weifangsun@chromium.org - - Chrome OS File Browser: counts the number of times ZIP file was opened or - created, categorized by component extensions and its operation types. - - - - - mek@chromium.org - - For each FileReaderSync instance records the type of the web worker that - created the instance. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - The result of FileSystemDirectoryDatabase initialization. - - - - tzik@chromium.org - The result of FileSystemDirectoryDatabase repair. - - - - tzik@chromium.org - - The success or the cause of failure for each call to OpenFileSystem(). - - - - - tzik@chromium.org - The result of opening a filesystem. - - - - tzik@chromium.org - The result of opening a non-throttled filesystem. - - - - - - dmurph@chromium.org - pwnall@chromium.org - The result of FileSystemOriginDatabase initialization. - - - - - Removed July 2019. - - alexmos@chromium.org - - Logged when we fail the permission validation of the filesystem URL origin, - from ChildProcessSecurityPolicy::HasPermissionsForFileSystemFile. This is - not expected to happen in normal operation. - - - - - tzik@chromium.org - - Number of origins that have persistent filesystem. Measured when the Quota - system queries the filesystem subsystem about its entire usage, which - usually happens when one of the storage subsystem methods is called for the - first time. - - - - - tzik@chromium.org - - Number of origins that have temporary filesystem. Measured when the Quota - system queries the filesystem subsystem about its entire usage, which - usually happens when one of the storage subsystem methods is called for the - first time. - - - - - ghendel@chromium.org - pkl@chromium.org - Track whether Firebase is enabled or not at app startup. - - - - jlebel@chromium.org - olivierrobin@chromium.org - - Counts the number of times First Run experience was triggered by another - application launching Chrome. This metric measures the effectiveness of - Smart App Banner promotions on installation of Chrome. - - - - - - Removed from code March 2019. - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the email interstitial of the onboarding - process. We record that the page was seen and what action the user took. - - - - - - Removed from code April 2019. - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the Email Providers new user experience. - We record the number of times the page is seen, how they interacted with the - page (i.e. interacting with presented options and button clicks), and - through what method they leave the page (i.e. confirm, cancel, neither). The - new user experience should only be shown once to new profiles. Hence, the - leaving method should be recorded at most once. - - - - - - Removed from code April 2019. - - hcarmona@chromium.org - scottchen@chromium.org - - Records what email provider was selected as part of the Email Providers New - User Experience. Histogram is only recorded when a user confirms adding an - email provider. - - - - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the Google Apps new user experience. We - record both accept and reject but are not recording when a user ignored the - prompt completely. Users can ignore this prompt by closing the tab or - navigating away, we record when the prompt is shown. - - - - - hcarmona@chromium.org - scottchen@chromium.org - - Records what Google apps were selected as part of the Google Apps New User - Experience. Histogram is only recorded when a user accepts the prompt to add - Google Apps. - - - - - - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the landing page of the onboarding - process. We record that the page was seen and what action the user took. - - - - - hcarmona@chromium.org - johntlee@chromium.org - - Records when a user interacts with the NTP Backgrounds new user experience. - We record the number of times the page is seen, how they interacted with the - page (i.e. interacted with the options and buttons), and through what method - they leave the page (i.e, confirm, cancel, neither). The new user experience - should only be shown once to new profiles. - - - - - hcarmona@chromium.org - johntlee@chromium.org - - Records the time taken to load a NTP background image for preview. This is - recorded when a user clicks on a background to preview and the full-size - version of the background finishes loading. - - - - - - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the set default page of the onboarding - process. We record that the page was seen and what action the user took. - - - - - hcarmona@chromium.org - scottchen@chromium.org - - Records when a user interacted with the sign in interstitial of the - onboarding process. We record that the page was seen and what action the - user took. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - Result of sentinel file has been written. - - - - jlebel@chromium.org - chrome-signin-team@google.com - File error when the sentinel file was not written. - - - - - - fernandex@chromium.org - jlebel@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - Result of the sign in flow during first run on iOS. - - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - WARNING: The list of actions used to identify new tasks hasn't been - attentively updated for several years (as of 2017). Some actions that should - likely be considered new tasks are probably missing. Take this histogram - with a grain of salt. Was expired for M85, M86. - - The amount of time (in seconds) that the app was in the background before - the user started it - - - - - - Removed 2020-04. - - tedchoc@chromium.org - - The amount of time (in minutes) that the app was in the background before - the user started it (via an ACTION_MAIN intent) and performed a user action - that describes the intent of resuming the app. Only recorded if the action - took place within the first 10 seconds of starting Chrome. The actions are - further described in the FirstUserActionTypes suffix. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - WARNING: The list of actions used to identify new tasks hasn't been - attentively updated for several years (as of 2017). Some actions that should - likely be considered new tasks are probably missing. Take this histogram - with a grain of salt. Was expired for M77-M86. - - On handsets, the type of the first user action performed after the app was - started or unbackgrounded. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - WARNING: The list of actions used to identify new tasks hasn't been - attentively updated for several years (as of 2017). Some actions that should - likely be considered new tasks are probably missing. Take this histogram - with a grain of salt. Was expired for M82-M86. - - On tablets, the type of the first user action performed after the app was - started or unbackgrounded. - - - - - drott@chromium.org - etienneb@chromium.org - - Time to retrieve the fallback fonts on the system when not found in cache. - - - - - drott@chromium.org - etienneb@chromium.org - The amount of font returned for a given font family. - - - - drott@chromium.org - etienneb@chromium.org - Time to retrieve the fallback fonts on the system. - - - - oyiptong@chromium.org - storage-dev@chromium.org - - Records the number of font families observed by the font enumeration cache - as part of the Font Access API. - - - - - oyiptong@chromium.org - storage-dev@chromium.org - - Records errors returned when obtaining the list of system fonts from - DirectWrite's GetSystemFontCollection. - - - - - oyiptong@chromium.org - storage-dev@chromium.org - - Records the most frequent failure to obtain metadata for a font family when - enumerating fonts as part of the Font Access API. Recorded in - FontEnumerationCacheWin when all fonts have been enumerated. Values are - Windows HRESULT error codes, and also includes custom values specific to - this implementation. - - - - - oyiptong@chromium.org - storage-dev@chromium.org - The number of duplicate fonts returned by fontconfig. - - - - oyiptong@chromium.org - storage-dev@chromium.org - The number of fonts returned by fontconfig. - - - - oyiptong@chromium.org - storage-dev@chromium.org - - The number of fonts whose name table entries could not be read. - - - - - oyiptong@chromium.org - storage-dev@chromium.org - Time spent enumerating fonts. - - - - msalama@chromium.org - msarda@chromium.org - - Tracks revoke actions taken by the account reconcilior to force Dice - migration. To enforce consistency, the reconcilior may invalidate the - primary account or revoke one or more secondary account tokens, if no - equivalent valid gaia cookie exist for those accounts. - - - - - - - droger@chromium.org - msarda@chromium.org - - Reports the network error code for requests to the ListAccounts Gaia - endpoint. - - - - - - Removed 2019-09. Enough data has been collected for investigation of - https://crbug.com/876306 - - droger@chromium.org - msarda@chromium.org - - - - Reports the network error code for requests to the ListAccounts Gaia - endpoint. There are suffixes for individual tries (0 is the initial request, - and 1-8 are retries). - - - - - - Removed 2019-09. Enough data has been collected for investigation of - https://crbug.com/876306 - - droger@chromium.org - msarda@chromium.org - - Reported when a request to the ListAccounts Gaia endpoint fails to complete - for network reasons (i.e. when the error is not OK). This histogram can be - used in conjunction with - "Gaia.AuthFetcher.ListAccounts.ProcessUptime.Success" in order to - compute the failure rate of ListAccounts depending on the process uptime - (measured as a base::TimeDelta between the start of the process and the - start of the request). - - - - - - Removed 2019-09. Enough data has been collected for investigation of - https://crbug.com/876306 - - droger@chromium.org - msarda@chromium.org - - Reported when a request to the ListAccounts Gaia endpoint completes without - network error (i.e. when the network error is OK). This histogram can be - used in conjunction with - "Gaia.AuthFetcher.ListAccounts.ProcessUptime.Error" in order to - compute the failure rate of ListAccounts depending on the process uptime - (measured as a base::TimeDelta between the start of the process and the - start of the request). - - - - - - Removed 2019-09. Enough data has been collected for investigation of - https://crbug.com/876306 - - droger@chromium.org - msarda@chromium.org - - Reported when a request to the ListAccounts Gaia endpoint fails to complete - for network reasons (i.e. when the network error is not OK). This histogram - can be used in conjunction with - "Gaia.AuthFetcher.ListAccounts.SystemUptime.Success" in order to - compute the failure rate of ListAccounts depending on the system uptime - (measured as a base::TimeDelta between the start of the system and the start - of the request). - - - - - - Removed 2019-09. Enough data has been collected for investigation of - https://crbug.com/876306 - - droger@chromium.org - msarda@chromium.org - - Reported when a request to the ListAccounts Gaia endpoint completes without - network error (i.e. when the network error is OK). This histogram can be - used in conjunction with - "Gaia.AuthFetcher.ListAccounts.SystemUptime.Error" in order to - compute the failure rate of ListAccounts depending on the system uptime - (measured as a base::TimeDelta between the start of the system and the start - of the request). - - - - - - - msarda@chromium.org - droger@chromium.org - chrome-signin-team@google.com - - Detailed error type in bad requests for OAuth2 access tokens. Recorded when - a HTTP 400 is received in response to a access token request. - - - - - - - msarda@chromium.org - droger@chromium.org - chrome-signin-team@google.com - - URLFetcher response codes for OAuth2AccessToken. Positive values are HTTP - status codes, negative values are network error codes. Recorded on responses - to OAuth access token requests. - - - - - - No longer recorded as of M86. - - msarda@chromium.org - droger@chromium.org - chrome-signin-team@google.com - - Number of successful requests preceding a bad request for an OAuth2 refresh - token. - - - - - - Removed as of 01/2018. Use Gamepad.KnownGamepadConnectedWithId instead. - - mattreynolds@chromium.org - - Records an enumeration value that can be used to identify the connected - device from a list of known gamepads. Reported when a device with a vendor - and product ID matching a known gaming input device is detected during - Gamepad API enumeration. - - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - Records an integer value that can be used to identify a connected gamepad - device. The value is constructed from the 16-bit vendor ID in the high-order - bytes and the 16-bit product ID in the low-order bytes, then cast to a - 32-bit signed integer. The GamepadVendorProduct enum lists IDs for several - popular gamepads but is incomplete. To identify a device not included in the - enum, convert back to the vendor/product IDs and look up the human-friendly - product name in go/gamepad-ids. This histogram records a new entry when a - device with a vendor and product ID matching a known gaming input device is - detected during Gamepad API enumeration. - - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - Records an enumeration value identifying the active data fetcher when a - fetcher enumerates a device that is not on the list of known gamepads, but - is recognized as a gamepad by the fetcher. - - - - - peter@chromium.org - knollr@chromium.org - - Records that a message has been received from a delivery channel powered by - the GCM account mappings. - - - - - - Removed as of 01/2016. The error has been fixed by GCM. (crbug/580367) - - khushalsagar@chromium.org - Result of a message received by the GcmReceiver on Android. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of times when gcm.unregister API is called. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Length of time taken to complete a GCM checkin request successfully. If the - checkin is retried multiple times, the length of time is counted for the - last successful retry. - - - - - peter@chromium.org - zea@chromium.org - Status code of the outcome of a GCM checkin request. - - - - peter@chromium.org - knollr@chromium.org - - Network error code for a GCM checkin request that failed because of a - network error. - - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of retries before a GCM checkin succeeds. - - - - - Removed as of 03/2018 (M67). - - zea@chromium.org - Whether the GCM connection was made via a proxy or not. - - - - zea@chromium.org - URL response and error codes from GCM disconnect events. - - - - zea@chromium.org - Number of connections made to each specific MCS endpoint. - - - - zea@chromium.org - URL response and error codes from GCM connection attempts. - - - - peter@chromium.org - zea@chromium.org - - The time between the initiation of a connection and the successful - completion of it. - - - - - zea@chromium.org - Reasons for GCM connection resets. - - - - zea@chromium.org - - GCM connection success rate. Does not take into account login success. See - GCM.ConnectionFailureErrorCode for a breakdown of connection failure - reasons. - - - - - zea@chromium.org - - Time (from login until reset) that a GCM connection was active. - - - - - peter@chromium.org - zea@chromium.org - - Success rate of writing new keying material to the GCM key store. - - - - - - - peter@chromium.org - zea@chromium.org - - Result of decryption on a received GCM message, which includes unencrypted - messages, successfully decrypted messages and decryption failures. - - - - - peter@chromium.org - alexchau@chromium.org - - Result of encryption of outgoing GCM message, which includes successfully - encrypted messages and encryption failures. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - Result of upgrading GCM Key Store Database from deprecated format to current - format. We upgrade the GCM Key store when it first initialized, if it - contains any EncryptionData object with a KeyPair in it, and then record - whether the upgrade was successful in this metric. - - - - - peter@chromium.org - zea@chromium.org - - Success rate of reading keying material from the GCM key store. - - - - - peter@chromium.org - zea@chromium.org - - Success rate of initializing the LevelDB back-end of the GCM key store. - - - - - peter@chromium.org - zea@chromium.org - - Success rate of loading existing keying material in the GCM key store. - - - - - peter@chromium.org - zea@chromium.org - - Success rate of removing keying material from the GCM key store. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - peter@chromium.org - The result of a database open attempt by the GCM store. - - - - - Removed in September 2020 as the data was no longer being used. - - peter@chromium.org - - Interval between two successive received data message bursts. - - - - - peter@chromium.org - zea@chromium.org - - Number of DATA_MESSAGE messages received from Google Cloud Messaging for - which a matching registration exists. Recorded when processing the received - message. Prior to M56 this also counted received DELETED_MESSAGES messages - (whether or not a registration existed). - - - - - peter@chromium.org - - Records whether a non-empty collapse_key token is set for each received - DATA_MESSAGE message from Google Cloud Messaging for which a matching - registration exists. Recorded while processing the received message. - - - - - - No longer used starting with Chrome 61 as the check was removed. - - peter@chromium.org - - Records whether a matching registration was found for each received - DATA_MESSAGE message from Google Cloud Messaging. Recorded while processing - the received message. Prior to M56 this also counted received - DELETED_MESSAGES messages. - - - - - peter@chromium.org - - For every DELETED_MESSAGES message received from Google Cloud Messaging - (whether or not a matching registration exists), this records the provided - count of how many messages were simultaneously deleted, or zero if the count - is unknown. - - - - - peter@chromium.org - mamir@chromium.org - - Whether a received GCM message could be delivered to an app handler. - Recorded for each received GCM message that didn't have encryption issues. - - - - - - Removed in June 2019. - - peter@chromium.org - - The time between the successful completion of the connection and the arrival - of the first data message. - - - - - - Removed in April 2020. - - tschumann@chromium.org - treib@chromium.org - - Reports the client-started state when the GCM driver requested a read of the - instance id although the client was not ready. If != Success, the client is - likely leaking a registration. - - - - - zea@chromium.org - - If a heartbeat was missed, the time delta by which it was missed (in system - time, not ticks). - - - - - - Removed in 2020-06. - - - - tschumann@chromium.org - treib@chromium.org - - Result of the outcome of persisting a change in the GCMStore. This histogram - is to meausure the frequency of such events and assess their severity. For - example, failing to write when calling AddInstanceIDData() likely results in - leaked FCM registrations. - - - - - peter@chromium.org - - Number of SEND_ERROR messages received from Google Cloud Messaging. Recorded - when processing the received message. - - - - - jianli@chromium.org - Status code of loading from the persistent GCM store. - - - - - Removed as of 2/2015. - - zea@chromium.org - - Success indicates successfully loading an initialized persistent GCM store - at startup time. Failure indicates a failure loading the store. - - - - - zea@chromium.org - - Number of applications hitting GCM per-app outstanding message limits at - startup time. - - - - - - Removed as of 3/2014. - - zea@chromium.org - - Number of GCM users associated with this client at startup time. - - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Category of TTL specified in the outgoing message: 0, less than or equal to - 1 minute, less than or equal to 1 hour and etc. - - - - - peter@chromium.org - - Number of connection events which have not been sent to GCM. This is - recorded only at the time of shutdown to capture the events which are being - lost due to shutdown. Because this is recorded at shutdown, this is not - guaranteed to be complete and should be treated as a best effort record. - - - - - - Removed in September 2020 as the data was no longer being used. - - peter@chromium.org - Number of messages in a received GCM data message burst. - - - - - Removed in June 2019. - - peter@chromium.org - - Interval between messages within a received GCM data message burst. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - Reports the status of cached GCM registration. This is recorded when a new - registration request is considered on the GCM client. - - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Length of time taken to complete a GCM registration request successfully. If - the registration is retried multiple times, the length of time is counted - for the last successful retry. - - - - - peter@chromium.org - - Number of registration requests sent to Google Cloud Messaging. Recorded - immediately after the request has started. - - - - - peter@chromium.org - platform-capabilities@chromium.org - - Net error code from a GCM registration attempt. Recorded when URL loading - completes. - - - - - peter@chromium.org - - Status code of the outcome of a GCM registration request. The Unknown error - case was split up in M56 (merged mid-beta to M55) to separate out the - Response parsing failed, Internal server error, Quota exceeded, and Device - has too many registrations cases. - - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of retries before a GCM registration succeeds. - - - - jianli@chromium.org - Number of sender IDs specified in a registration request. - - - - msarda@chromium.org - chrome-signin-team@google.com - - Number of times that account mapping entries are deleted from or kept in the - GCM store database while loading them in memory. Used during the account ID - migration from email to Gaia ID. - - - - - - Removed in M56 in favor of GCM.ResetStoreError - - jianli@chromium.org - - Reports the problem encountered when resetting the GCM store. - - - - - zea@chromium.org - - Reports the problem encountered when resetting the GCM store. - - - - - zea@chromium.org - - Number of unacknowledged incoming messages restored from the persistent - store at startup. - - - - - zea@chromium.org - - Number of pending outgoing messages restored from the persistent store at - startup. - - - - - peter@chromium.org - - Number of registrations restored from the persistent store at startup. - - - - - peter@chromium.org - - Result of sending an upstream message through Google Cloud Messaging. - Recorded when the message has either been queued, sent, or has been dropped - because it expired or an error happened. - - - - - - Removed Sep 2020. No longer used. - - alexchau@chromium.org - peter@chromium.org - - Categorized response body when 403: Forbidden is received from sending web - push messages. Recorded when received response after message has been sent. - All platforms. - - - - - alexchau@chromium.org - peter@chromium.org - - Size of web push messages payload. Recorded right before the message is - sent. - - - - - alexchau@chromium.org - peter@chromium.org - - Result of sending web push messages. Recorded when the message has either - been sent, or has been dropped because an error happened. - - - - - alexchau@chromium.org - peter@chromium.org - - Result code from sending web push messages. Logs net::Error if it's not - net::OK. Logs net::OK if response header is not present. Otherwise, logs - HTTP status code returned. Recorded when received response after message has - been sent. - - - - - zea@chromium.org - - Success indicates successfully destroying the GCM persistent store. Failure - indicates a failure destroying the persistence store. GCM store will be - destroyed when the profile has been signed out. - - - - - zea@chromium.org - Size of the GCM persistent store in kilobytes at startup. - - - - zea@chromium.org - - Success indicates successfully updating the GCM persistent store on message - update. Failure indicates a failure updating the persistence store. - - - - - zea@chromium.org - Time elapsed from machine suspend until resume. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Length of time taken to complete a GCM unregistration request successfully. - If the unregistration is retried multiple times, the length of time is - counted for the last successful retry. - - - - - - Removed 7/2019. No longer used. - - peter@chromium.org - - Number of unregistration requests sent to Google Cloud Messaging. Recorded - immediately after the request has started. - - - - - peter@chromium.org - zea@chromium.org - Status code of the outcome of a GCM unregistration request. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of retries before a GCM unregistration succeeds. - - - - jianli@chromium.org - - Indicates whether the user was signed in when GCM started up. - - - - - knollr@chromium.org - peter@chromium.org - - Device state when receiving a web push message. Indicates if the message was - sent with a high priority and if the device was in idle mode. Recorded when - a web push message got received. - - - - - - Removed 2020-02. - - pavely@chromium.org - - Status of parsing incoming invalidations message from GCM channel. - - - - - - Removed 2020-02. - - pavely@chromium.org - - Status of sending outgoing invalidations message through GCM. - - - - - Please list the metric's owners. Add more owner tags as needed. - Result of the authentication for Drive. - - - - - Removed 9/2012, and replaced by Drive.EntireFeedLoadTime - - Please list the metric's owners. Add more owner tags as needed. - - Time spent to load the entire file system information from the server - - - - - - Removed 9/2012, and replaced by Drive.EntryKind - - Please list the metric's owners. Add more owner tags as needed. - - Provides breakdown of specific formats for hosted documents. Recorded when - feed is loaded from the server. - - - - - - Removed 9/2012, and replaced by Drive.InitialFeedLoadTime - - Please list the metric's owners. Add more owner tags as needed. - - Time spent to load the initial part of the file system information from the - server - - - - - - Removed 9/2012, and replaced by Drive.NumberOfHostedDocuments - - Please list the metric's owners. Add more owner tags as needed. - - Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive - is first accessed. - - - - - - Removed 9/2012, and replaced by Drive.NumberOfRegularFiles - - Please list the metric's owners. Add more owner tags as needed. - - Number of regualr files on Drive. Logged when Drive is first accessed. - - - - - - Removed 9/2012, and replaced by Drive.NumberOfTotalFiles - - Please list the metric's owners. Add more owner tags as needed. - - Number of total files (regualr files + hosted documents) on Drive. Logged - when Drive is first accessed. - - - - - mattreynolds@chromium.org - device-dev@chromium.org - - Records the action performed by an existing user when prompted to authorize - the use of location by Chrome. - - - - - mattreynolds@chromium.org - device-dev@chromium.org - - Records the action performed by a new user when prompted to authorize the - use of location by Chrome. - - - - - - Removed 01/2020 because the metric is not needed anymore. See - https://crbug.com/1036861 for discussion on this metric. - - mattreynolds@chromium.org - device-dev@chromium.org - - Whether high accuracy geolocation information was requested. - - - - - kcarattini@chromium.org - dominickn@chromium.org - - For Geolocation requests from the omnibox on Android, the time since the - location was most recently acquired. If no location has been acquired, the - maximum bucket is incremented. - - - - - kcarattini@chromium.org - dominickn@chromium.org - - Counts Geolocation requests for omnibox searches sliced by various - permission combinations. The location mode abbreviations indicate one of: - High Accuracy, Battery Saving, GPS On or Location Mode Off. - - - - - kcarattini@chromium.org - dominickn@chromium.org - - For Geolocation requests from the omnibox on Android, the time since the - location was first acquired. If no location has been acquired, the minimum - bucket is incremented. - - - - - kiyun@google.com - mvanouwerkerk@chromium.org - newt@chromium.org - - Reason why the X-Geo header was or was not included in a Google search from - the omnibox. - - - - - - Removed 9/2014, and replaced by - ContentSettings.PermissionActions_Geolocation. - - mvanouwerkerk@chromium.org - Events in GeolocationInfoBarDelegate. - - - - - Removed 9/2014, and replaced by - ContentSettings.PermissionActions_Geolocation. - - mvanouwerkerk@chromium.org - Events in GeolocationInfoBarDelegateAndroid. - - - - mattreynolds@chromium.org - device-dev@chromium.org - Error code for the geoposition sent to the renderers. - - - - mattreynolds@chromium.org - device-dev@chromium.org - - The number of WiFi access points used to determine geolocation. - - - - - mattreynolds@chromium.org - device-dev@chromium.org - Events in NetworkLocationRequest. - - - - mattreynolds@chromium.org - device-dev@chromium.org - Http response codes in NetworkLocationRequest. - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - For each query into the position cache used by the network location - provider, records whether a position was returned from the cache. - - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - For each query into the position cache used by the network location - provider, records the number of items in the cache. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the backoff level when the Location Settings Dialog is accepted by - the user. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the backoff level when the Location Settings Dialog is rejected by - the user. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the backoff level when the Location Settings Dialog is shown to the - user. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the backoff level when the Location Settings Dialog is suppressed - due to backoff. - - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - Counts Geolocation request timeout values, bucketing by timeout duration. - This is recorded for all requests upon creation, see - Geolocation.TimeoutExpired for timeouts that actually expired. - - - - - mattreynolds@chromium.org - deviceapi-team@google.com - - Counts Geolocation request timeout expirations, bucketing by timeout - duration. This means no position was received within the allowed time from - the browser process due to e.g. a slow network or an unresponsive system - location provider. - - - - - benwells@chromium.org - - Records the action the user took after the geolocation disclosure has been - displayed. - - - - - benwells@chromium.org - - Records how long the search geolocation disclosure infobar was visible for. - - - - - - Removed 2017/11. Use PostDisclosureDSESetting instead. - - benwells@chromium.org - - Records the geolocation content setting for the default search engine's - origin after the search geolocation disclosure has been shown and won't be - shown again. This metric is only recorded once per client. - - - - - benwells@chromium.org - - Records the geolocation default search engine setting after the search - geolocation disclosure has been shown and won't be shown again. This metric - is only recorded once per client. - - - - - - Removed 2017/01. Replaced by PostDisclosureContentSetting. - - benwells@chromium.org - - Records the geolocation permission for the default search engine's origin - after the search geolocation disclosure has been shown and won't be shown - again. This metric is only recorded once per client. - - - - - - Removed 2017/11. Use PreDisclosureDSESetting instead. - - benwells@chromium.org - - Records the geolocation content setting for the default search engine's - origin immediately before the search geolocation disclosure has been shown. - This metric is only recorded once per client. - - - - - benwells@chromium.org - - Records the geolocation default search engine setting immediately before the - search geolocation disclosure has been shown. This metric is only recorded - once per client. - - - - - - Removed 2017/01. Replaced by PreDisclosureContentSetting. - - benwells@chromium.org - - Records the geolocation permission for the default search engine's origin - immediately before the search geolocation disclosure has been shown. This - metric is only recorded once per client. - - - - - - Removed 2020/02. Replaced by Cancelled. - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gestures that were abandoned before they were completed. - Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gesture was made beyond a threshold big enough to regard it as a - valid gesture navigation i.e. at least 1/3 of the arrow puck is visible. - Similar to 'Triggered' but is used in pair with 'Cancelled' on M81 forward - to measure cancellation rate. Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gestures that were cancelled before they were completed. Similar - to 'Abandoned' but is used in pair with 'Activated' on M81 forward to - measure cancellation rate. Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Navigations that were triggered due to completed overscroll gesture. - Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gesture was made to trigger navigation, but within 3 seconds user - used overscroll gesture to navigate back to the page. Implemented for - Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gesture was made to trigger navigation bottom sheet to peeked - state. Peek state can be entered and exited more than once in a sequence of - overscroll gesture (until user lifts his finger). They are recorded as just - one event per sequence. Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Index of the entries in the navigation bottom sheet that user tapped. - Negative means navigating backward, positive forward. Zero index means that - the user chose "Show full history". - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - User tapped one of the entries in the expanded navigation bottom sheet to - navigate to other page. Implemented for Android. - - - - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gesture was made to trigger navigation bottom sheet to expanded - state where the whole list of history items are presented. - - - - - - Removed 2020/02. - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gesture was made beyond a threshold that, upon release, would - trigger navigation. Users can swipe back below the threshold but this event - will still be logged. Implemented for Android. - - - - - - Removed 2020/02. Replaced by Activated. - - jinsukkim@chromium.org - chrome-android-app@chromium.org - - Overscroll gestures initiated by the user. Note that not all overscroll - gestures triggered are completed (e.g. the overscroll gesture is aborted if - user swipes back to the edge before releasing the finger). Implemented for - Android. - - - - - - Removed in r454917 03/2017. - - robliao@chromium.org - skare@chromium.org - Types of cards which received an index 0 button click. - - - - - Removed in r454917 03/2017. - - robliao@chromium.org - skare@chromium.org - Types of cards which received an index 1 button click. - - - - - Removed in r454917 03/2017. - - robliao@chromium.org - skare@chromium.org - Types of cards which received a notification click. - - - - - Removed in r454917 03/2017. - - robliao@chromium.org - skare@chromium.org - Events in Google Now component extension. - - - - - Removed in r455117 03/2017. - - robliao@chromium.org - skare@chromium.org - - Count of the number of Google Now notifications visible when the message - center/notification center is shown. - - - - - - Removed from code June 2019. See https://crbug.com/490710 for context. - - wnwen@chromium.org - - ConnectionResult error codes resulting from attempts to check whether or not - Google Play Services is available. Most of these checks are done lazily, - when a user accesses a feature that uses Google Play Services. Added for - http://crbug.com/490710. - - - - - - Removed from code June 2019. See https://crbug.com/490710 for context. - - wnwen@chromium.org - - Types of action taken in response to Google Play Services user-recoverable - errors. Added for http://crbug.com/490710. - - - - - - Removed 2015/08. - - kmadhusu@chromium.org - - Counts number of Google searches from various access points in the browser. - WARNING: Do not use this histogram as it currently fails to classify a large - percentage of Omnibox searches correctly - http://crbug.com/421631. - - - - - - Removed 09/2018; see https://crbug.com/871490. - - gab@chromium.org - - The effective update policy for Chrome on Windows. Recorded once per startup - (following a 45 seconds delay). - - - - - grt@chromium.org - The HRESULT for a failed on-demand update check. - - - - - Removed 12/2015 in Issue 566085. - - yfriedman@chromium.org - dfalcantara@chromium.org - - (Android-only) Records what action the user took (if any) on the InfoBar - indicating that a new version of Chrome is available. - - - - - shaktisahu@chromium.org - - (Android-only) The amount of internal memory storage that is free on the - file system and available to the applications when the InfoBar or update - menu item is shown. - - - - - - Removed 6/2020. - - yfriedman@chromium.org - dfalcantara@chromium.org - khushalsagar@chromium.org - - (Android-only) The amount of internal memory storage available on the user's - device when the InfoBar or update menu item is shown. Deprecating soon in - M64. - - - - - - Removed 12/2015 in Issue 566085. - - yfriedman@chromium.org - dfalcantara@chromium.org - - (Android-only) The amount of time which the InfoBar indicating a new version - is available is visible. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Records the instances where Play update API returned the - current install status of inline updates. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Records the instances where Play update API returned the - current availability of inline updates. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Records the instances where Play update API calls failed. - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Records the instances where Play update API notified us of an - install error during an update. This is keyed on the specific state so we - can tell which states are seeing which errors. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) The UI component that triggered an inline update to finish - and install. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) The UI component that triggered an inline update to retry. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) The UI component that triggered an inline update to start. - - - - - nikunjb@chromium.org - chrome-metrics-team@google.com - - Store the hash of update cohort name as reported by Chrome Updater on - Windows. Recorded at the start of metrics service. - - - - - grt@chromium.org - - The exit code from Chrome's installer following a failed on-demand update - check. All values reported for this histogram fall in the - GOOGLE_UPDATE_ERROR_UPDATING bucket of the GoogleUpdate.UpdateErrorCode - histogram and the GOOPDATEINSTALL_E_INSTALLER_FAILED bucket of the - GoogleUpdate.ErrorHresult histogram. - - - - - twellington@chromium.org - - (Android-only) Records whether Chrome was updated after the update menu item - was clicked. - - - - - twellington@chromium.org - - (Android-only) Records whether the update menu item was clicked when the app - menu was opened. - - - - - - Removed 08/2020 - - xingliu@chromium.org - - (Android-only) Records events when try to launch the update work flow via an - update notification. - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Whether or not an update was successful when looking at the - Chrome version on the next session where there is no update in progress. - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Whether or not an update was successful within a specific - server-configured window of time (e.g. an update may not occur right after - the user attempts to start it, but if they update sometime in the next X - days, we can possibly attribute it to the update flow we started). An - example window value could be on the order of days (e.g. 2 days since an - update started). - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) Whether or not an update was being tracked as 'in progress' - when another update was started. - - - - - dtrainor@chromium.org - nyquist@chromium.org - - (Android-only) The state of any in-progress updates when the process first - starts and queries for it. - - - - - grt@chromium.org - - An unrecognized CurrentState value received from Google Update while polling - for the status of an on-demand update check. - - - - - grt@chromium.org - The error code for a failed on-demand update check. - - - - - Removed 09/2018; see https://crbug.com/871490. - - grt@chromium.org - - True if the effective update policy for Chrome on Windows is the result of - an app-specific override; false if it is the default for all apps. Recorded - once per startup (following a 45 seconds delay). - - - - - grt@chromium.org - The result of an on-demand update check. - - - - vmiura@chromium.org - - Refresh rate of the display in Hz. This is recorded every time we present a - frame. - - - - - cwallez@chromium.org - - The sum of the size of the CPU-side memory allocations of Buffer11's copies - (vs. GPU memory allocations). These allocations are used when modifying the - buffer data on the CPU or when transfering to GPU memory via DMA. - - - - - jmadill@chromium.org - - An extended Windows error code returned from D3D11CreateDevice on error. Can - be almost any valid HRESULT or DXGI error code, which are listed at - https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx. - - - - - - Removed sometime around M77. - - jmadill@chromium.org - - The time that elapses for the initial call to D3D11CreateDevice on D3D11 - ANGLE. A pure system call, with no ANGLE or Chromium code, called once every - GPU process startup. - - - - - jmadill@chromium.org - - The maxmium supported (or currently requested) Direct3D feature level in - D3D11 ANGLE. We support as low as 9.3, and as high as 11.1, though Chrome - should only use 10.0+ for D3D11. Gives an indication of how new a user's - video card is, what features it supports, and it's general speed tier. - - - - - jonahr@google.com - angle-team@google.com - - The result from initializing a D3D11 device in ANGLE. Can be success, or one - of several error codes which indicate different reasons for failing. - - - - - jmadill@chromium.org - - The result from initializing a D3D9 device in ANGLE. Can be success, or one - of several error codes which indicate different reasons for failing. - - - - - jonahr@google.com - angle-team@google.com - - The time ANGLE spends calling the D3D shader compiler. Tracks total time we - spend compiling shaders on startup and during Chrome's lifetime. - - - - - jonahr@google.com - angle-team@google.com - - Time ANGLE spends in eglInitialize, where it spins up a Renderer. This can - gives us insight into how much time we're spending initializing the GPU. - - - - - jmadill@chromium.org - - The time to load a gpu program from the program cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - jmadill@chromium.org - - The time to link a gpu program. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - jmadill@chromium.org - - If a successfully linked program was found in the GPU program cache during a - program link call, and if the hit was originally loaded from disk. - - - - - jonahr@google.com - angle-team@google.com - - Records if the call to load a cached binary was successful. This can - legitimately fail if the driver wants chrome to re-link and re-cache the gpu - program. - - - - - jmadill@chromium.org - - The size of program binaries loaded into the gpu program cache. - - - - - - Removed sometime around M77. - - jmadill@chromium.org - - Time ANGLE spends initializing various shaders and internal classes. This is - time that isn't purely loading system DLLs and calling OS methods. It might - be work we can optimize or defer until later. - - - - - - Removed sometime around M77. - - jmadill@chromium.org - - Time ANGLE spends loading system DLLs, such as the D3D compiler DLL, and the - D3D11 and DXGI DLLs. Probably unavoidable startup costs, though very useful - to keep track of. - - - - - jmadill@chromium.org - - Windows computers running Windows 8+, or running Windows 7 with a platform - update, support the newer version of DXGI. This update also indicates the - computer is capable of running Direct3D 11.1 if the hardware supports it. - - - - - forshaw@chromium.org - wfh@chromium.org - - On Windows 10 version RS1 and above the GPU can be sandboxed using an - AppContainer. This is recorded every time the GPU sandbox is initialized and - enabling the AppContainer is requested, such as through a command line - option. The recorded value can indicate that the AppContainer was disabled - due to an incompatible configuration or the GPU process had previously - crashed resulting in the AppContainer being forcefully disabled. - - - - - forshaw@chromium.org - wfh@chromium.org - - On Windows 10 version RS1 and above the GPU can be sandboxed using an - AppContainer. This indicates the status when initializing the sandbox - profile during process creation. - - - - - - Removed sometime around M55. - - vmiura@chromium.org - - The amount of GPU memory that was currently allocated as of just before the - GPU process' exit. - - - - - - Removed sometime around M55. - - vmiura@chromium.org - - The maximum amount of GPU memory that had ever been allocated during the GPU - process' lifetime, as of just before the GPU process' exit. - - - - - - Removed sometime around M55. - - vmiura@chromium.org - - The GPU memory manager's limit on the amount of GPU memory that can be - allocated as of just before the GPU process' exit. - - - - - vmiura@chromium.org - - The number of surfaces that the GPU process was rendering to right before - exiting. This should be equal to the number of tabs (both visible and - hidden) rendering via the compositor. - - - - - - Removed sometime around M55. - - vmiura@chromium.org - - The number of windows that the GPU memory manager believed to exist as of - just before the GPU process' exit. - - - - - vmiura@chromium.org - - Counts number of browser invocations for which a GPU feature is - allowed/blacklisted/disabled. - - - - - - Replaced by GPU.BlacklistFeatureTestResultsWindows2 in M67. - - vmiura@chromium.org - - Counts number of browser invocations for which a GPU feature is - allowed/blacklisted/disabled in various Windows sub-versions. - - - - - vmiura@chromium.org - - Counts number of browser invocations for which a GPU feature is - allowed/blacklisted/disabled in various Windows sub-versions. - - - - - vmiura@chromium.org - - Counts number of browser invocations for which a disabled blacklist entry is - matched. - - - - - vmiura@chromium.org - - Counts number of browser invocations for which the GPU process is blocked - due to a blacklist entry match. - - - - - - Removed in M77. - - kbr@chromium.org - - Indicates whether WebGL / Pepper3D were blocked, and if so, for all domains, - or only a single one. This statistic is gathered every time an attempt is - made to create a 3D context. - - - - - - Removed 01/2017. - - ericrk@chromium.org - - The amount of time spent in GLES2DecoderImpl::CheckFramebufferValid. - - - - - vmiura@chromium.org - - The time that the GPU process spends collecting driver information during - startup. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - kylechar@chromium.org - - Records what compositing mode (software, GL, etc.) Chrome is using every - five minutes. This is the default compositing mode that most windows will - use. There are some window types (eg. menus on some platforms) that always - use software compositing and ignore the default. - - - - - sievers@chromium.org - - The reason a GPU command buffer context of a given type was lost. - - - - - ericrk@chromium.org - The amount of memory used by a GL Context. - - - - - Removed 07/2018: not useful anymore. - - vmiura@chromium.org - - The time that the browser process takes to create the compositor from its - point of view. One of these is created for each top-level window (browser - frame, menus, etc.). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vmiura@chromium.org - Whether D3D11 supports B8G8R8A8 format for render targets. - - - - vmiura@chromium.org - Whether D3D11 supports B8G8R8A8 format for 2D textures. - - - - - As of 02/26/2020 this has been superceded by GPU.D3D11FeatureLevel. - - vmiura@chromium.org - The highest D3D11 feature level available. - - - - sadrul@chromium.org - zmo@chromium.org - - Records the highest D3D_FEATURE_LEVEL available, collected in the info - collection GPU process, once per UMA ping. This is Windows platform only. - - - - - vmiura@chromium.org - magchen@chromium.org - - The maximum D3D12 feature level supported in the gpu drivers. It is recorded - 15 seconds after the browser launch. - - - - - jmadill@chromium.org - - ANGLE's currently active D3D shader model version. Logged once every startup - of the GPU process, on Windows only. Note that Shader Models 2 and 3 map to - D3D9 with ANGLE, and 4+ map to D3D11 ANGLE. - - - - - - Removed 11/2016. - - ericrk@chromium.org - - The amount of time spent destroying programs during ProgramManager::Destroy. - - - - - - Removed 11/2016. - - ericrk@chromium.org - - The number of progams destroyed during ProgramManager::Destroy. - - - - - - Removed 11/2016. - - ericrk@chromium.org - - The number of programs destroyed per millisecond during - ProgramManager::Destroy. Only logged if both the number of programs and the - elapsed time are greater than zero. - - - - - sunnyps@chromium.org - zmo@chromium.org - - If the system approves a swap chain's custom present duration request, this - is the approved custom present duration. If the swap chain's custom present - duration request is not approved, this is zero. - - - - - sunnyps@chromium.org - zmo@chromium.org - - How the Desktop Window Manager presented Chrome's DirectComposition layers - to the screen. - - - - - zmo@chromium.org - graphics-dev@chromium.org - - How the Desktop Window Manager presented Chrome's main DirectComposition - layer to the screen. - - - - - zmo@chromium.org - rafael.cintron@microsoft.com - - HRESULT return value of IDXGIFactory2::CreateSwapChainForComposition. - - - - - magchen@chromium.org - zmo@chromium.org - - HRESULT return value of ID3D11VideoDevice::CreateVideoProcessorEnumerator in - Direct Composition InitializeVideoProcessor. - - - - - - Removed 11/2018. Replaced by GPU.DirectComposition.DCLayerResult2.Clear. - - jbauman@chromium.org - - Recorded for each quad (on overlay processing) the reason it was or wasn't - put in an overlay. - - - - - sunnyps@chromium.org - zmo@chromium.org - - Recorded for each texture quad (on overlay processing) the reason it was or - wasn't put in an overlay. - - - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded for each quad (on overlay processing) with protected video type the - reason it was or wasn't put in an overlay. - - - - - - Removed 08/2019. Replaced by GPU.DirectComposition.DCLayerResult.Video - - - - magchen@chromium.org - zmo@chromium.org - - Recorded for each quad (on overlay processing) with protected video type the - reason it was or wasn't put in an overlay. - - - - - magchen@chromium.org - zmo@chromium.org - - HRESULT return value of IDCompositionDevice2::CreateSurface. - - - - - sunnyps@chromium.org - zmo@chromium.org - - Result of calling CreateDecodeSwapChainForCompositionSurfaceHandle. Recorded - when decode swap chain is created. - - - - - sunnyps@chromium.org - zmo@chromium.org - - The reason decode swap chain wasn't used to present a video frame. Recorded - on each present. See also GPU.DirectComposition.VideoPresentationMode. - - - - - - Removed 3/2019. This either succeeds or fails with DXGI_STATUS_OCCLUDED - infrequently which we also handle. - - sunnyps@chromium.org - zmo@chromium.org - - Result of calling Present on decode swap chain. Recorded on each present. - - - - - - Removed 3/2019. Creating the surface never fails. - - sunnyps@chromium.org - zmo@chromium.org - - Result of calling CreateSurfaceFromHandle. Recorded when decode swap chain - is created. - - - - - - Removed 4/2019. Replaced by GPU.DirectComposition.VideoPresentationMode. - - sunnyps@chromium.org - zmo@chromium.org - - Whether zero copy decode swap chain was used to present video frame instead - of video processor blit with flip swap chain. Recorded on each present. - - - - - - No longer needed. Data has been collected. - - magchen@chromium.org - zmo@chromium.org - - Recorded for each overlay frame during the video playback whether the - workaround that reduces the swap chain size to fit the screen is active. - - - - - sunnyps@chromium.org - zmo@chromium.org - - How many frames since the last time the layer color format was changed. - - - - - - Removed 4/2019. Replaced by GPU.DirectComposition.OverlayFullScreenTypes. - - magchen@chromium.org - zmo@chromium.org - - Recorded for each overlay/underlay quad during the video playback whether - the video is played in full screen mode - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded for each video quad during the video playback whether it is an - underlay or an overlay - - - - - sunnyps@chromium.org - zmo@chromium.org - - Number of presented frames for which presentation queries haven't completed. - Recorded on each vblank. - - - - - - Removed 10/2018. Replaced by GPU.DirectComposition.OverlayFormatUsed2. - - sunnyps@chromium.org - Which overlay format was chosen for YUV overlays. - - - - - Removed 5/2019. Replaced by GPU.DirectComposition.OverlayFormatUsed3. - - sunnyps@chromium.org - zmo@chromium.org - - Which overlay format was chosen for YUV overlays. Recorded once per GPU - process launch only if hardware overlays are supported. - - - - - sunnyps@chromium.org - zmo@chromium.org - - Which overlay format was chosen for YUV overlays. Recorded once per GPU - process launch only if hardware overlays are supported. - - - - - - Removed 03/2020. Data has been collected. - - magchen@chromium.org - zmo@chromium.org - - The overlay size types in comparison to the full screen size. Recorded for - each overlay quad during the video playback. - - - - - - Removed 04/2019. Rec 709 is almost always supported. - - magchen@chromium.org - sunnyps@chromium.org - zmo@chromium.org - - Whether or not Rec709 color space is supported on NV12 supported machines. - Recorded during the GPU process initialization. - - - - - sunnyps@chromium.org - zmo@chromium.org - True if Chrome will try to use DirectComposition overlays. - - - - - Replaced by format specific histograms under OverlaySupportFlags2. - - sunnyps@chromium.org - - These are the flags explaining how well overlays are supported on the - current display. The is recorded for every connected display when creating a - DirectComposition view context. - - - - - - Removed 04/2019. BGRA is never supported, NV12 always supports scaling, and - YUY2 supports scaling in 75% cases. - - - - sunnyps@chromium.org - zmo@chromium.org - - Flags that indicate if overlays are supported, and if additional features - such as scaling are supported for some common pixel formats. - - - - - sunnyps@chromium.org - zmo@chromium.org - Whether or not a frame displays an overlay. - - - - - Removed 08/2018. Replaced by SwapBuffersResult which is emitted on both - success and failure. - - sunnyps@chromium.org - Emitted on direct composition surface swap buffers failure. - - - - - Removed 05/2018. GetLastError returns error for last successful or failed - win32 call so this doesn't work as expected. - - sunnyps@chromium.org - Last error when presentation using DirectComposition fails. - - - - - Removed 04/2019. SwapBuffers rarely fails. - - sunnyps@chromium.org - zmo@chromium.org - Whether or not swap buffers succeeded. - - - - - Removed 04/2019 because of using histogram macros instead of functions. - Replaced by SwapChainCreationResult2. - - - - sunnyps@chromium.org - zmo@chromium.org - - Whether creating swap chain for overlay format succeeded. Recorded once per - swap chain creation. - - - - - - - sunnyps@chromium.org - zmo@chromium.org - - Whether creating swap chain for overlay format succeeded. Recorded once per - swap chain creation. - - - - - - - magchen@chromium.org - zmo@chromium.org - - Whether creating swap chain for protected video succeeded. Recorded once per - swap chain creation. - - - - - - Removed 10/2018. Replaced by GPU.DirectComposition.SwapChainFormatUsed. - - jbauman@chromium.org - What type of swapchain was actually created for an overlay. - - - - - Removed 5/2019. Replaced by GPU.DirectComposition.SwapChainFormatUsed3. - - sunnyps@chromium.org - zmo@chromium.org - - What format was used for each overlay swap chain on each swap buffers. - - - - - sunnyps@chromium.org - zmo@chromium.org - - What format was used for each overlay swap chain on each swap buffers. - - - - - - Removed 04/2019. ResizeBuffers rarely fails. - - sunnyps@chromium.org - zmo@chromium.org - - Result of ResizeBuffers call. Recorded once per swap chain resize. - - - - - magchen@chromium.org - zmo@chromium.org - - HRESULT return value of ID3D11Device::CreateTexture2D in Direct Composition - UploadVideoImages for creating a copy texture. - - - - - magchen@chromium.org - zmo@chromium.org - - HRESULT return value of ID3D11Device::CreateTexture2D in Direct Composition - UploadVideoImages for creating a staging texture. - - - - - magchen@chromium.org - zmo@chromium.org - - HRESULT return value of ID3D11VideoDevice::CreateVideoProcessor in Direct - Composition InitializeVideoProcessor. - - - - - sunnyps@chromium.org - zmo@chromium.org - - What code path was used to present a video frame. Recorded on each present. - - - - - - Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.DisplayCompositor. - - mohsen@chromium.org - - Counts of the number of gpu process crashes when it only has display - compositor (no hardware acceleration and software compositing). - - - - - - Removed 2/2017. The values hadn't been updated since it was created, and the - code gathering the installation status has been removed in Chrome CL - 2679773002. - - vmiura@chromium.org - - Whether a version of DisplayLink is installed that crashes the GPU process. - This information is collected at statup. It applies only to Windows. See - http://crbug.com/177611. - - - - - jonahr@google.com - angle-team@google.com - - The time we spend in GLES2DecoderImpl::DoLinkProgram. Related to how much - time we spend compiling shaders during startup. - - - - - - - vmiura@chromium.org - kbr@chromium.org - zmo@chromium.org - - For every entry in the gpu driver bug list that is hit on a machine, this - records the id. Entry 0 is the total number of times that data is recorded. - It should be recorded whenever new GPU information is received: on startup, - whenever a GPU process launches, and whenever the active GPU changes. - - - - - jbauman@chromium.org - The display type used to ask for an EGLDisplay. - - - - zmo@chromium.org - vmiura@chromium.org - The error states generated by OpenGL calls. - - - - - Expired in M75. - - kylechar@chromium.org - - The duration from when a request to establish a GPU channel arrives in - viz::GpuClient and to when the response for the request is sent. - - - - - reveman@chromium.org - - Whether GLFence support is available. Recorded each time a new context group - is initialized and extensions are detected. - - - - - ccameron@chromium.org - graphics-dev@chromium.org - - The time that elapsed between a call to glCreateProgram and the call to - query GL_LINK_STATUS via glGetProgramiv in Skia's GrGLInterface. This - encompasses the creation of the vertex, fragment, and geometry shaders, - their compilation, and their linking. This is called for every program - created by Skia via the GrGLInterface. - - - - - magchen@chromium.org - zmo@chromium.org - - Records the OpenGL implementation mode. Recorded during GPU process - initilization. - - - - - - Removed November 27, 2019. See GPU.GpuBlockedBetweenSwapsUs2. - - vasilyt@chromium.org - backer@chromium.org - - This is logged once per frame if the output surface provides timing - information. It measures the time Gpu Main thread was blocked (difference - between wall time and cpu time) during tasks execution for currect frame. - Only reported when there is single surface swap in the same vsync interval. - Only reported for platforms supporting high resolution clocks. - - - - - vasilyt@chromium.org - backer@chromium.org - - This metric recorded only with --enable-gpu-blocked-time flag. This is - logged once per frame if the output surface provides timing information. It - measures the time Gpu Main thread was blocked (difference between wall time - and cpu time) during tasks execution for currect frame. Only reported when - there is single surface swap in the same vsync interval. Only reported for - platforms supporting high resolution clocks. - - - - - - Removed 10/2019. Moved to GPU.GPUChannelHostWaitTime.Max120Seconds. - - magchen@chromium.org - zmo@chromium.org - - The wait time between the IPC message sent from the GPU channel host and the - event sync from the GPU process. If the wait time takes longer than 60 - seconds, 60 seconds will be recoreded. - - - - - - Removed 01/2020. - - kylechar@chromium.org - - Records how long the browser UI thread spent blocked for a sync IPC sent - using GpuChannelHost to see if it's contributing to jank. - - - - - magchen@chromium.org - zmo@chromium.org - - The wait time between the IPC message sent from the GPU channel host and the - event sync from the GPU process. If the wait time takes longer than 120 - seconds, 120 seconds will be recoreded. - - - - - - Renamed to GPU.IntelGpuSeriesType 03/2020 - - sunnyps@chromium.org - zmo@chromium.org - - Records user device's GPU generation. Only recorded on Windows platform at - GPU process launch time. Currently only meaningful with Intel GPUs. - - - - - - Removed 01/2020. Moved to GPU.GPUInitializationTime.V2. - - magchen@chromium.org - zmo@chromium.org - - The time between the GPU process starts and the GPU Info is collected in Viz - GPU service. If GPU initilization takes longer than 60 seconds, 60 seconds - will be recoreded. - - - - - magchen@chromium.org - zmo@chromium.org - - The time between the GPU process starts and the GPU Info is collected at GPU - process startup and recorded in browser process when this piece info is sent - back to browser process. The range is between 200ms and 5s. - - - - - wnwen@chromium.org - - Breakdown of exit status for gpu processes. Only recorded on Android. - - - - - jbauman@chromium.org - - Counts for the exit codes returned by the GPU process when it terminated. - - - - - vmiura@chromium.org - - Whether the GPU process successfully initialized or failed and then exitted - normally. - - - - - - Removed 08/2016. - - vmiura@chromium.org - - Counts enumerating the initial cause for the GPU Process to be launched. - - - - - vmiura@chromium.org - - Startup time of the GPU process as measured by the GPU process host. - - - - - - Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.HardwareAccelerated. - - vmiura@chromium.org - - Counts of the number of process launches and crashes (when running on h/w). - - - - - - This histogram is no longer recorded. Use GPU.GLImplementation == - kGLImplementationSwiftShaderGL to check if the gpu process is launched with - software rendering. - - vmiura@chromium.org - - A boolean indicating whether the gpu process that was launched uses software - or hardware 3d rendering. - - - - - rjkroege@chromium.org - msisov@igalia.com - - The reason a GPU process is terminated. It works only when - TERMINATION_STATUS_PROCESS_WAS_KILLED TerminationStatus is set. The goal of - this histogram is to get spikes of the above mentioned case when - Ozone/Wayland terminates the GPU process due to invalid data it received if - any. - - - - - - Removed April 2018. Replaced by GPU.GPUProcessTerminationStatus2. - - vmiura@chromium.org - - Counts for each time the GPU Process Host detects the process dies. - - - - - vmiura@chromium.org - - Counts for each time the GPU Process Host detects the process dies. - - - - - - Removed August 2020. Replaced by Memory.GPU.PeakMemoryAllocationSource. - - enne@chromium.org - khushalsagar@chromium.org - - Kilobytes of memory used by Skia in the gpu process. This is recorded after - every block of commands in the raster decoder. - - - - - sadrul@chromium.org - zmo@chromium.org - - Records whether the system has a discrete GPU, collected in the info - collection GPU process, once per UMA ping. This is Windows platform only. - - - - - - Removed 10/2013. - - vmiura@chromium.org - - Records whether a client was selected for the force compositing mode field - trial or not. - - - - - jonahr@google.com - angle-team@google.com - - The time that the GPU process spends in initializing the GL surface, and - collecting graphics information. Records times up to three minutes. - - - - - - Removed 4/2015. - - vmiura@chromium.org - - The time that the GPU process spends in initializing the GL surface, and - collecting graphics information. - - - - - sadrul@chromium.org - zmo@chromium.org - - Records the highest Intel GPU generation of the system using the GPU info - collected at GPU process startup time, once per UMA ping. - - - - - sunnyps@chromium.org - zmo@chromium.org - - Records user device's GPU series type. Only recorded on Windows platform at - GPU process launch time. Only meaningful with Intel GPUs. - - - - - ccameron@chromium.org - - The time that it took to update the CALayer tree and commit the transaction. - This is often affected by IOSurface paging. - - - - - ccameron@chromium.org - - The time that it took for a call to IOSurfaceCreate to complete. - - - - - ccameron@chromium.org - - The time that it took for a call to glFlush to complete. This is often - affected by IOSurface paging. - - - - - ccameron@chromium.org - - The time that it took for a call to CGLTexImageIOSurface2D to complete. - - - - - ccameron@chromium.org - khushalsagar@chromium.org - - The time that the GPU's main CPU thread spends waiting for previous frames' - GPU work to complete. Recorded at every frame. - - - - - senorblanco@chromium.org - - The maximum number of multisampled anti-aliasing (MSAA) samples per pixel - that the user's GPU can render. - - - - - - It is not planned to use this approach to determine if Metal is to be used. - - ccameron@chromium.org - graphics-dev@chromium.org - - Compiling a MTLLibrary will sometimes hang forever. When initializing Metal, - a test shader is compiled to see if the MTLCompilerService is responding or - not. This records the success or failure of this test compile, once at - initialization. - - - - - ccameron@chromium.org - graphics-dev@chromium.org - - Compiling a MTLLibrary will sometimes hang forever. When initializing the - gpu process, a test shader is compiled to see if the MTLCompilerService is - responding or not. This records the time that it took for the compile to - succeeded, up to 1 minute. After 1 minute, a timeout sentinel value of 3 - minutes is reported. - - - - - ccameron@chromium.org - graphics-dev@chromium.org - - Linking a MTLRenderPipelineState will sometimes hang forever. When - initializing the GPU process, a test shader is compiled to see if the - MTLCompilerService is responding or not. This records the time that it took - for the compile to succeeded, up to 1 minute. After 1 minute, a timeout - sentinel value of 3 minutes is reported. - - - - - - Removed 05/2020. Did not reveal interesting results. - - ccameron@chromium.org - graphics-dev@chromium.org - - Compiling a MTLLibrary will sometimes hang forever. When initializing the - gpu process, a test shader is compiled to see if the MTLCompilerService is - is responding or not. This records the time that it took for the compile - method to finish (not including the time for the compile itself to finish), - up to 1 minute. After 1 minute, a timeout sentinel value of 3 minutes is - reported. - - - - - - This did not substantially improve the situation and was removed. - - ccameron@chromium.org - graphics-dev@chromium.org - - Creating a new MTLLibrary will automatically retry if its callback is not - invoked within a short timeframe. This records the attempt number whose - callback was executed first. Recorded after every call to -[MTLDeviceProxy - newLibraryWithSource:] completes. - - - - - ccameron@chromium.org - graphics-dev@chromium.org - - The time that it takes to create a new MTLLibrary, including all retries. - Recorded after every call to -[MTLDeviceProxy newLibraryWithSource:] - completes. - - - - - - This did not substantially improve the situation and was removed. - - ccameron@chromium.org - graphics-dev@chromium.org - - Creating a new MTLRenderPipelineState will automatically retry if its - callback is not invoked within a short timeframe. This records the attempt - number whose callback was executed first. Recorded after every call to - -[MTLDeviceProxy newRenderPipelineStateWithDescriptor:] completes. - - - - - ccameron@chromium.org - graphics-dev@chromium.org - - The time that it takes to create a new MTLRenderPipelineState, including all - retries. Recorded after every call to -[MTLDeviceProxy - newRenderPipelineStateWithDescriptor:] completes. - - - - - khushalsagar@chromium.org - - During OutOfProcess(Oop) raster, the renderer generates and sends the - requisite glyph data for rasterizing a tile with the serialized paint - commands. If the data for any glyph is missing, the GPU process attempts to - use a fallback glyph from the cache. This records each time we encounter a - cache miss on the GPU and whether we could use a fallback. - - - - - - Removed 06/2019. - - khushalsagar@chromium.org - - This records the number of bytes required to serialize a paint op for OOP - rasterization. The metric is recorded each time an op is serialized with a - size > 512k bytes. - - - - - hubbe@chromium.org - media-dev@chromium.org - - Records the output color space of the monitor as reported by Windows. - Recorded once for each monitor when the gpu process starts. If monitor - enumeration fails, this metric will not be provided. - - - - - hubbe@chromium.org - media-dev@chromium.org - - Records if any connected monitor is HDR capable. Recorded when the gpu - process starts. Only recorded on Windows as of M-61. If monitor enumeration - fails, this metric will not be provided. - - - - - - Removed 07/2020. No longer used. - - hubbe@chromium.org - media-dev@chromium.org - - Records the display maximum lumens as reported by Windows. Recorded once for - each monitor when the gpu process starts. If monitor enumeration fails, this - metric will not be provided. - - - - - jonahr@google.com - angle-team@google.com - - The time we spend in GLES2DecoderPassthroughImpl::DoLinkProgram. Related to - how much time we spend compiling shaders during startup. - - - - - vmiura@chromium.org - - Recorded once for every GPU process launch and crash when GPU process is - started for the display compositor with software compositing. Crash buckets - are based on crash count for disabling features. No hardware acceleration - and no SwiftShader WebGL will be run. - - - - - vmiura@chromium.org - - Recorded once for every GPU process launch and crash when GPU process is - started for hardware accelerated GPU compositing and/or WebGL. Crash buckets - are based on crash count for disabling features. With OOP-D enabled the - display compositor also runs in the GPU process. - - - - - vmiura@chromium.org - - Recorded once for every GPU process launch and crash when GPU process is - started for SwiftShader WebGL. Crash buckets are based on crash count for - disabling features. With OOP-D enabled the display compositor with software - compositing will also run as part of the GPU process. - - - - - vmiura@chromium.org - - The time to load a gpu program from the program cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vmiura@chromium.org - - The time to link a gpu program. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - jonahr@google.com - angle-team@google.com - - If a successfully linked program was found in the GPU program cache during a - program link call. - - - - - vmiura@chromium.org - - The time to check the program cache that we've already compiled the shader. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vmiura@chromium.org - - The time to compile a shader. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ericrk@chromium.org - - Whether we succeeded in compressing program data. Expected to always be - true. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ericrk@chromium.org - - The time to compress a program's binary data during insertion into the - program cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ericrk@chromium.org - - The percentage of raw size that a program binary takes after compression. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ericrk@chromium.org - - Whether we succeeded in decompressing program data. Failure indicates disk - or memory corruption. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ericrk@chromium.org - - The time to decompress a program's binary data during retrieval from the - program cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - vmiura@chromium.org - - Records if the call to glProgramBinary was successful. This can legitimately - fail if the driver wants chrome to re-link and re-cache the gpu program. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - ssid@chromium.org - - Amount of memory released from the program cache on memory pressure. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - vmiura@chromium.org - - Records the total in-memory cache size, before a program is cached. Can be - used with GPU.ProgramCache.MemorySizeBeforeKb to find the maximum cache size - distribution. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - vmiura@chromium.org - - Records the total in-memory cache size, after a program is cached. Can be - used with GPU.ProgramCache.MemorySizeAfterKb to find the maximum cache size - distribution. - - - - - - Not used after M77. ProgramCache not actively being tuned. - - vmiura@chromium.org - - The size of program binaries loaded into the gpu program cache. - - - - - zmo@chromium.org - graphics-dev@chromium.org - - Whether or not a {FORMAT_TYPE} fbo is complete and renderable. - - - - - - - - - - - - - - - - vmiura@chromium.org - wfh@chromium.org - - Whether or not the GPU sandbox properly initialized. Failures are typically - platform- and driver-specific (e.g. driver creating threads on Linux). - - - - - kylechar@chromium.org - chrome-gpu-metrics@google.com - - Records the wall time taken for each GPU scheduler task to run. The time - delta starts when the GPU scheduler pops the task off the task queue and - finishes when the task has completed. Only recorded for clients with high - resolution clocks. - - - - - vmiura@chromium.org - - Counts activation and deactivation of accelerated compositing. - - - - - ericrk@chromium.org - - Whether or not the shader prefix loaded from disk matched the expected - prefix for the data and system configuration. False indicates either disk - corruption or a system configuration change, and should be rare. - - - - - penghuang@chromium.org - backer@chromium.org - - Whether or not the content of a SharedImage is consumed. False indicates the - content of a SharedImage is never used due to destroying the SharedImage or - writing new content to it before using it. - - - - - samans@chromium.org - viz-team-wat@google.com - - Time it took to acquire the lock in SharedImageManager. Recorded only when - the manager is thread-safe. Ignores clients with no high-resolution clock. - - - - - - Never used. - - vmiura@chromium.org - - Counts of the number of gpu process crashes when the software rasterizer is - enabled. - - - - - sadrul@chromium.org - zmo@chromium.org - - Collects whether Chrome uses software renderer or hardware GPU 20 seconds - after Chrome starts, and records this value once per UMA ping. This value is - not re-collected at each recording time because GPU process could crash for - various reasons and fall back to software rendering. This value is intended - to reflect device capabilities rather than the current state. - - - - - vmiura@chromium.org - - Records whether a client was selected for the Stage3D on XP field trial or - not. - - - - - vmiura@chromium.org - magchen@chromium.org - - This metric shows whether the GPU supports D3D12. It is recorded 120 seconds - after the browser launch. - - - - - - Removed 06/2020. Data has been collected on Windows. - - vmiura@chromium.org - magchen@chromium.org - - This metric shows whether the GPU supports Vulkan. It is recorded 15 seconds - after the browser launch. - - - - - - Removed 12/2012. Moved to GPU.AtExitSurfaceCount. - - vmiura@chromium.org - - The number of surfaces that the GPU process was rendering to right before - exiting. This should be equal to the number of tabs (both visible and - hidden) rendering via the compositor. - - - - - vikassoni@chromium.org - - Counts the error code which is returned when AImageReader api call - acquireLatestImageAsync fails. - - - - - vasilyt@chromium.org - backer@chromium.org - - This is logged once per frame if the output surface provides timing - information. It measures the time of SwapBuffers call. Only reported when - there is single surface swap in the same vsync interval. Only reported for - platforms supporting high resolution clocks. - - - - - - Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.SwiftShader. - - capn@chromium.org - - Counts of the number of process launches and crashes (when running on s/w). - - - - - - Removed 06/2020. Both LUMINANCE_F16 and R16_EXT must be supported for now. - - hubbe@chromium.org - rijubrata.bhaumik@intel.com - media-dev@chromium.org - - Whether LUMINANCE_F16 and/or R16_EXT texture support is available. Recorded - each time a new context group is initialized and extensions are detected. - - - - - reveman@chromium.org - - Whether RG texture support is available. Recorded each time a new context - group is initialized and extensions are detected. - - - - - - Removed 04/2018. Infobar has been removed. - - vmiura@chromium.org - Counts user actions when a 3D API info bar is raised. - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - - The amount of time required to create an external VkSemaphore. Only reported - for platforms supporting high resolution clocks. - - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - - The amount of time required to get a file handle from a VkSemaphore. Only - reported for platforms supporting high resolution clocks. - - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - The number of semaphores imported into GL per frame. - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - - The amount of time required to import a VkSemaphore from a file handle. Only - reported for platforms supporting high resolution clocks. - - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - - The amount of time required to import a VkSemaphore into GL. Only reported - for platforms supporting high resolution clocks. - - - - - backer@chromium.org - penghuang@chromium.org - vasilyt@chromium.org - - The number of vkQueueSubmit() calls per SwapBuffers. It is recorded when - SwapBuffers() call is completed or skipped. - - - - - - Removed 06/2020. Data has been collected on Windows. - - vmiura@chromium.org - magchen@chromium.org - - Whether the Vulkan extension VK_KHR_external_memory_win32 is supported in - the GPU drivers. It is recorded 15 seconds after the browser launch. - - - - - - Removed 06/2020. Data has been collected on Windows. - - vmiura@chromium.org - magchen@chromium.org - - Whether the Vulkan extension VK_KHR_external_semaphore_win32 is supported in - the GPU drivers. It is recorded 15 seconds after the browser launch. - - - - - - Removed 06/2020. Data has been collected on Windows. - - vmiura@chromium.org - magchen@chromium.org - - Whether the Vulkan extension VK_KHR_win32_keyed_mutex is supported in the - GPU drivers. It is recorded 15 seconds after the browser launch. - - - - - - Removed 06/2020. Data has been collected on Windows. - - vmiura@chromium.org - magchen@chromium.org - - The maximum Vulkan API version supported in the gpu drivers. It is recorded - 15 seconds after the browser launch. - - - - - stanisc@chromium.org - - Whether WaitForVBlank operation has been successful or failed with one of - the errors prompting a backup delay based v-sync mechanism. Recorded each - time a new GPU v-sync signal is generated. - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded for each time the GPU watchdog thread starts, crashes and ends. - This includes data from both watchdog V1 and V2. - - - - - - No longer used after GPU watchdog V2 is enabled by default in M82. It's the - same as the default histogram GPU.WatchdogThread.Event. - - magchen@chromium.org - zmo@chromium.org - - Recorded for each time the GPU watchdog V2 thread starts, crashes and ends. - - - - - - - magchen@chromium.org - zmo@chromium.org - - The number of extra timeouts the GPU main thread needs to make any progress - after the first watchdog timeout. - - - - - magchen@chromium.org - zmo@chromium.org - - Records the number of the watchdog timeout functions being entered at each - timeout after allowing the GPU to finish the current job with extra thread - time. If the user decides to quite Chrome, the recorded count would decrease - at the next timeout. - - - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded timeout events when the GPU watchdog V2 enters OnWatchdogTimeout. - - - - - - GPU watchdog V1 is disabled in M82. Please see - GPU.WatchdogThread.ExtraThreadTime for the result of V2. - - magchen@chromium.org - zmo@chromium.org - - The time the GPU main thread needs to make any progress after the first - watchdog timeout. - - - - - - GPU watchdog V1 is disabled in M82. Please see GPU.WatchdogThread.Timeout - for the result of V2. - - magchen@chromium.org - zmo@chromium.org - - Recorded timeout events when the GPU watchdog V2 enters OnWatchdogTimeout. - - - - - - GPU watchdog V1 is disabled in M82. Please see GPU.WatchdogThread.WaitTime - for the result of V2. - - magchen@chromium.org - zmo@chromium.org - - Record the wait time in OnWatchdogTimeout() for the GPU main thread to make - any progress. - - - - - - - magchen@chromium.org - zmo@chromium.org - - Record the wait time in OnWatchdogTimeout() for the GPU main thread to make - any progress. - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded every second in a 60-second loop that the watchdog was still - running after allowing the GPU to complete the current job within 60 - seconds. If any of the users decided to quit Chrome, the recorded count - would decrease at the next second. - - - - - magchen@chromium.org - zmo@chromium.org - - Recorded the time the GPU main thread makes any progress after allowing the - GPU to complete the current job within 60 seconds. - - - - - vmiura@chromium.org - - Counts of context initialization that succeed or fail based on combinations - of attributes requiring canRecoverFromContextLoss and devices that report - can_lose_context. Failing Init is desired when a device can not guarantee it - won't fail for a user that can not handle failures, e.g. DX9 on WinXP used - by Canvas2D' - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) gaming graphics score. It is in - the range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 - represents a failure to get the score. This is collected each time Chrome is - launched. - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) gaming graphics score, scaled by - 10x. It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 - represents a failure to get the score. This is collected each time Chrome is - launched. - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) graphics score. It is in the - range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a - failure to get the score. This is collected each time Chrome is launched. - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) graphics score, scaled by 10x. - It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 - represents a failure to get the score. This is collected each time Chrome is - launched. - - - - - vmiura@chromium.org - - A boolean representing whether or not we succeeded in getting the system's - WinSAT scores. This is collected each time Chrome is launched. - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) overall system score. This is - the minimum of all the individual subscores. It is in the range 1.0-5.9 on - Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a failure to get - the score. This is collected each time Chrome is launched. - - - - - vmiura@chromium.org - - The WinSAT (Windows System Assessment Tool) overall system score, scaled by - 10x. This is the minimum of all the individual subscores. It is in the range - 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 represents a failure to - get the score. This is collected each time Chrome is launched. - - - - - vmiura@chromium.org - - The amount of time it takes to read the WinSAT results. This is collected - each time Chrome is launched. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Presentation timestamp comes from the driver when showing a display frame on - screen. These timestamps could be invalid, and be earlier than the swap - time. This metric records how much time before the swap-time such invalid - timestamps are. If the presentation timestamp is after the swap-time, then - this metric is not recorded. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Presentation timestamp comes from the driver when showing a display frame on - screen. These timestamps can sometimes be in the future. This metric records - how far in the future these timestamps can be. If the timestamp is not in - the future, then this metric is not recorded. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Measures very large (more than 3 minutes) delay in presenting display - frames. Presentation timestamp comes from the driver when showing a display - frame on screen. There are times when the presentation can be delayed a long - time. This metric reports how often this can happen. This is reported only - if the presentation takes 3 minutes or more. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of frames that were shown with checkerboards during a - particular sequence of frames (e.g. during scroll, animation, etc.). Note - that this is only recorded for sequences of length > 4. - - Checkerboarding is measured by tracking the number of times checkerboard - frames are displayed (as opposed to the number of checkerboard frames - produced), since the same checkerboard frame can be displayed more than - once. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Counts the number of frames expected during a particular sequence of frames - (e.g. during scroll, animation, etc.). - - - - - sadrul@chromium.org - mjzhang@chromium.org - graphics-dev@chromium.org - - Tracks the percent of janks for a particular sequence of frames (e.g. during - scroll, animation, etc.). This is reported in various sub-metrics with - suffixes describing the type of the sequence (e.g. TouchScroll etc.). - - Jank is measured by tracking the number of abrupt increases in frame - presentation interval, divided by the total number of frames expected to be - produced and displayed. The lower this number is, the less the smoothness - varies over time. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of dropped frames for a particular sequence of frames - (e.g. during scroll, animation, etc.). This is reported in various - sub-metrics with suffixes describing the type of the sequence (e.g. - TouchScroll etc.). - - PercentDroppedFrames is measured by tracking the number of frames which were - not displayed on screen out of the total number of frames expected to be - produced and displayed. In other words, the lower this number is, the - smoother experience. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - ericrk@chromium.org - - Tracks the percent of dropped frames for a particular sequence of frames for - all animations. This metric is reported for all animations (e.g. - comositor-driven animations, main-thread driven animations, and raf-driven - animations). - - PercentDroppedFrames is measured by tracking the number of frames which were - not displayed on screen out of the total number of frames expected to be - produced and displayed. In other words, the lower this number is, the - smoother experience. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - ericrk@chromium.org - - Tracks the percent of dropped frames for a particular sequence of frames - where a user-input (e.g. scroll, pinch) is active. This metric is reported - for all sources of user-input (i.e. both touchscreen and - touchpad/mouse-wheel). - - PercentDroppedFrames is measured by tracking the number of frames which were - not displayed on screen out of the total number of frames expected to be - produced and displayed. In other words, the lower this number is, the - smoother experience. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - ericrk@chromium.org - - Tracks the percent of dropped frames for a particular sequence of frames. - This metric is reported for all animations and all interactions. - - PercentDroppedFrames is measured by tracking the number of frames which were - not displayed on screen out of the total number of frames expected to be - produced and displayed. In other words, the lower this number is, the - smoother experience. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of frames that missed the deadline for a particular - sequence of frames (e.g. during scroll, animation, etc.). This is reported - in various sub-metrics with suffixes describing the type of the sequence - (e.g. TouchScroll etc.). - - PercentMissedDeadlineFrames is measured by tracking the number of frames - which were displayed on screen but missed the vsync interval. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of frames that missed the deadline for a particular - sequence of frames for all animations. This metric is reported for all - animations (e.g. comositor-driven animations, main-thread driven animations, - and raf-driven animations). - - PercentMissedDeadlineFrames is measured by tracking the number of frames - which were displayed on screen but missed the vsync interval. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of frames that missed the deadline for a particular - sequence of frames where a user-input (e.g. scroll, pinch) is active. This - metric is reported for all sources of user-input (i.e. both touchscreen and - touchpad/mouse-wheel). - - PercentMissedDeadlineFrames is measured by tracking the number of frames - which were displayed on screen but missed the vsync interval. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the percent of frames that missed the deadline for a particular - sequence of frames. This metric is reported for all animations and all - interactions. - - PercentMissedDeadlineFrames is measured by tracking the number of frames - which were displayed on screen but missed the vsync interval. - - Note that this metric is reported only when there are sufficient number of - frames (>= 100). If there are sequences with fewer frames, then these are - aggregated until there are enough frames to produce the metric. - - - - - - As of 2020-02-12, this is deprecated in favor of - Graphics.Smoothness.PercentDroppedFrames. - - sadrul@chromium.org - graphics-dev@chromium.org - - - - - As of 2020-02-12, this is deprecated in favor of - Graphics.Smoothness.PercentDroppedFrames.AllAnimations. - - sadrul@chromium.org - ericrk@chromium.org - - - - - As of 2020-02-12, this is deprecated in favor of - Graphics.Smoothness.PercentDroppedFrames.AllInteractions. - - sadrul@chromium.org - ericrk@chromium.org - - As of 2020-02-12, this is deprecated in favor of - Graphics.Smoothness.PercentDroppedFrames.AllInteractions. - - - - - - As of 2020-02-12, this is deprecated in favor of - Graphics.Smoothness.PercentDroppedFrames.AllSequence. - - sadrul@chromium.org - ericrk@chromium.org - - - - yiyix@chromium.org - chrome-gpu-metrics@google.com - - The amount of time it takes for the BeginFrame to travel to the Client from - the DisplayCompositor. - - Note that this metrics is only recorded on clients on which a - high-resolution clock is available - - - - - yiyix@chromium.org - chrome-gpu-metrics@google.com - - How long the client takes to prepare a compositor frame after receiving a - BeginFrameArgs. - - Note that this is only recorded on clients on which a high-resolution clock - is available. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the dirty span of the transition animation between - Tab and Grid Tab Switcher. The dirty span is the duration from the start of - the animation to the last View invalidation. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the frame rate of the transition animation between - Tab and Grid Tab Switcher. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the maximum interval between rendered frames during - the transition animation between Tab and Grid Tab Switcher. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the result of thumbnail fetching in the Grid Tab - Switcher. - - - - - - Removed 07/2020; currently unowned, and histogram gathering was causing - crashes. - - vtsyrklevich@chromium.org - dynamic-tools@google.com - - Reports how many allocations it took for malloc GWP-ASan to OOM. Reported - the first time the allocator fails to consecutively allocate - GuardedPageAllocator::kOutOfMemoryCount allocations in a row. - - - - - - Removed 07/2020; currently unowned, and histogram gathering was causing - crashes. - - vtsyrklevich@chromium.org - dynamic-tools@google.com - - Reports how many allocations it took for PartitionAlloc GWP-ASan to OOM. - Reported the first time the allocator fails to consecutively allocate - GuardedPageAllocator::kOutOfMemoryCount allocations in a row. - - - - - vtsyrklevich@chromium.org - dynamic-tools@google.com - - Reports the GWP-ASan crash analysis result. That can either be a - determination that the crash was related to GWP-ASan, not related to - GWP-ASan, or an error making that determination. Recorded with every crash. - - Deprecated in favor of GwpAsan.CrashAnalysisResult.Malloc and - GwpAsan.CrashAnalysisResult.PartitionAlloc in M76 - - - - - sadrul@chromium.org - zmo@chromium.org - - Records the system hardware concurrency collected in the info collection GPU - process, once per UMA ping. For most systems, it is equivalent to the number - of CPU cores. - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - - The number of displays present right after the user has attached or detached - a new display. Excludes mirrored displays, but includes sleeping displays. - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - - The number of displays present at start up. Excludes mirrored displays, but - includes sleeping displays. - - - - - - Removed 1/2020 - but the data exists in system_profile under - hardware.app_drive and hardware.user_data_app_drive - - dbeam@chromium.org - - Whether a drive has a seek penalty (i.e. is a spinning disk). Emitted 0-2 - times shortly after startup when constructing the initial UMA log. - - - - - - Removed 1/2020 - but the data exists in system_profile under - hardware.app_drive and hardware.user_data_app_drive - - dbeam@chromium.org - - Whether it was possible to determine if a drive has a seek penalty. This can - fail for various reasons (device drivers don't offer this information, the - drive is still mounting, lack of access, etc.). Emitted twice shortly after - startup when constructing the initial UMA log. - - Seek penalty detection is disabled on XP/Vista as of 9/24/2015 because it - crashes too much. http://crbug.com/514822 - - - - - - Removed 1/2020 - but the data exists in system_profile under - hardware.app_drive and hardware.user_data_app_drive - - dbeam@chromium.org - - The amount of time it takes to determine whether a drive has a seek penalty. - Emitted twice shortly after startup when constructing the initial UMA log. - - - - - - Removed in M83 after all code for the old enumeration method had been - removed. - - charliea@chromium.org - - On Windows and Mac, we're implementing new methods to enumerate serial - devices that provide us more information about the actual devices. This - metric measures the difference between the number of devices that the new - and old enumeration methods find. Once this metric gives us confidence that - the new and old methods are at parity, we can cut out the old method - altogether. - - - - - sadrul@chromium.org - zmo@chromium.org - - Records a rough estimation of the system total disk space collected in the - info collection GPU process, once per UMA ping. - - - - - erikchen@chromium.org - chrome-memory@google.com - - One metric is emitted every 24-hours after Chrome is launched for every - process that is being profiled. The timer is reset if Chrome exits. - - - - - erikchen@chromium.org - chrome-memory@google.com - - One metric is emitted every 24-hours after Chrome is launched for every - Chrome instance that is using out of process heap profiling. The timer is - reset if Chrome exits. - - - - - erikchen@chromium.org - chrome-memory@google.com - - The metric is emitted each time Chrome attempts to record a memory-infra - trace to upload an out-of-process heap-profiling memory dump. - - - - - erikchen@chromium.org - chrome-memory@google.com - - The metric is emitted each time Chrome uploads a trace. It reflects the - uncompressed size of the trace. - - - - - erikchen@chromium.org - chrome-memory@google.com - - The metric is emitted each time Chrome uploads a trace. It reflects whether - the upload was successful. - - - - - - Removed 3/2019. - - ryansturm@chromium.org - bengr@chromium.org - - Records that the capping heavy pages InfoBar was allowed or the specific - reason that the feature was blacklisted from heavy page capping. Recorded - when the triggering threshold is met for users with capping heavy pages - enabled. Reasons are ordered in the same order they are checked. - - - - - - Removed 3/2019. - - ryansturm@chromium.org - bengr@chromium.org - - Records the details of user interaction with the heavy page capping InfoBar. - - - - - - Removed 3/2019. - - ryansturm@chromium.org - - Records the data savings due to heavy page capping. This is recorded when - the page is being terminated. This is not recorded when the tab is - backgrounded, so android fast shutdown may result in this metric not being - recorded. This is only recorded for page loads that were still paused when - the page was terminated. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Which HID were detected when user pressed Continue on OOBE dialog. This - metric is specific to Chrome OS. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Whether HID detection dialog was shown on OOBE. Logged on screen show or on - screen skip respectively. This metric is specific to Chrome OS. - - - - - rsorokin@chromium.org - alemate@chromium.org - cros-oac@google.com - - Records number of times the dialog was shown by the time OOBE is completed. - This metric is specific to Chrome OS. - - - - - asvitkine@chromium.org - bcwhite@chromium.org - - The hash codes of histograms that were found to have bad construction - arguments. These would be DCHECK exceptions in debug builds but have simply - been logged and corrected as best as possible rather than crash. - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a browser for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. Each type of inconsistency is a bit, and all bits found - in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency MAY appear time and - again as the same corrupt histogram is examined for each potenital UMA - upload. - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a browser for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. Each type of inconsistency is a bit, and all bits found - in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency will only appear at - most one time for each histogram in a single process (i.e., duplicate - corruption in a single histogram is not noted in this chart.) - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a child process for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. Each type of inconsistency is a bit, and all bits found - in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency MAY appear time and - again as the same corrupt histogram is examined for each potenital UMA - upload. - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a child process for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. Each type of inconsistency is a bit, and all bits found - in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency will only appear at - most one time for each histogram in a single process (i.e., duplicate - corruption in a single histogram is not noted in this chart.) - - - - - - Removed 7/2012. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a renderer for transmission to the browser. Inconsistent data is NOT - transmitted to the browser. Each type of inconsistency is a bit, and all - bits found in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency MAY appear time and - again as the same corrupt histogram is examined for each potenital UMA - upload. - - - - - - Removed 7/2012. - - asvitkine@chromium.org - - The number of inconsistency events found when examining a single histogram's - data in a renderer for transmission to the browser. Inconsistent data is NOT - transmitted to the browser. Each type of inconsistency is a bit, and all - bits found in one histogram examination are added together to summarize the - inconsistent event. Note that the same inconsistency will only appear at - most one time for each histogram in a single renderer process (i.e., - duplicate corruption in a single histogram is not noted in this chart.) - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of extra samples counted in the redundant_count in a histogram - that were not found by summing the samples in the buckets. - - - - - - Removed 7/2017. - - asvitkine@chromium.org - - The number of missing samples in the redundant_count in a histogram that - were found by summing the samples in the buckets. - - - - - asvitkine@chromium.org - - The amount of discrepancy found when examining a single histogram's data in - the browser process for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. - - - - - asvitkine@chromium.org - - The amount of discrepancy found when examining a single histogram's data in - a child process for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. - - - - - - Removed 7/2012. - - asvitkine@chromium.org - - The amount of discrepancy found when examining a single histogram's data in - a renderer process for transmission via UMA. Inconsistent data is NOT - transmitted via UMA. - - - - - asvitkine@chromium.org - bcwhite@chromium.org - - The hash codes of histograms that were found to have construction arguments - different from a previous instantiation of the same name. Entries here have - conflicting definitions and should be investigated. Data collected for the - secondary definitions will be silently dropped. - - - - - Please list the metric's owners. Add more owner tags as needed. - - When metrics services (UMA) ran an update, the number of child processes - that did not respond, providing histogram updates, before the timeout. - - - - - asvitkine@chromium.org - bcwhite@chromium.org - - The hash codes of histograms of which the external name storage was altered - after the histogram was created. - - - - - Please list the metric's owners. Add more owner tags as needed. - - When metrics services (UMA) ran an update, the number of times the process - groups (renderer processes and plugin/gpu processes) did not respond, - providing histogram updates, before the timeout. - - - - - asvitkine@chromium.org - bcwhite@chromium.org - - The hash codes of histograms that were found to request more than 1000 - buckets. These would be DCHECK exceptions in debug builds if the limit is - lowered so are being logged before that change. - - - - - sky@chromium.org - sdefresne@chromium.org - - Logged whenever history database initialization fails. The frequency of - logging will tell you the total failure rate. True indicate that we think - the database is non-recoverable and it will be deleted. It should be - re-created the next time Chrome is started. False indicates we think the - error is temporary (like out of disk space or file locked). Chrome will run - with no history database and nothing will be done to try to fix the error. - See History.InitializationFailureStep for which particular step of history - initialization failed. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - The time that passed while performing a browsing data deletion with an - origin filter. The deletion might be for all time or specific time range. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - The time that passed while performing a full browsing data deletion. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - The time that passed while performing a browsing data deletion for a set of - origins. - - - - - - Removed May 2020, replaced with more detailed histograms: - History.ClearBrowsingData.Duration.TimeRangeDeletion, - History.ClearBrowsingData.Duration.OriginDeletion, - History.ClearBrowsingData.Duration.FilteredDeletion. - - dullweber@chromium.org - msramek@chromium.org - - The time that passed while performing a browsing data deletion for a - restricted amount of time (e.g. "Last hour") or with an origin - filter. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - Record tasks from BrowsingDataRemoverImpl that took more than 180s to - finish. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - Record tasks from ChromeBrowsingDataRemoverDelegate that took more than 180s - to finish. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - Record tasks from StoragePartition that took more than 180s to finish. - - - - - - - dullweber@chromium.org - msramek@chromium.org - - The time that passed while performing a browsing data deletion for a - restricted amount of time (e.g. "Last hour") without an origin - filter. - - - - - dullweber@chromium.org - msramek@chromium.org - - Records tasks from ChromeBrowsingDataRemoverDelegate that did not complete - successfully, i.e. where some data that was supposed to be deleted was left - behind. - - - - - msramek@chromium.org - - Whether a notice about other forms of browsing history was shown in the - footer of the Clear Browsing Data dialog. This is recorded every time the - dialog is opened. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - Recorded when the user presses the 'clear' button when presented with the - list of important sites they might want to exclude from clearing browsing - data. We record the number of sites the user deselected, or protected, from - clearing. The default has all sites selected. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - Recorded when the user presses the 'clear' button when presented with the - list of important sites they might want to exclude from clearing browsing - data. We record the percent of sites the user deselected, or protected, from - clearing. The default has all sites selected, which is 0%. Note: To reduce - the number of empty buckets, the percent is divided by 5. - - - - - dmurph@chromium.org - - Recorded when the user presses the 'clear' button in the clear browsing - dialog. We record 'true' if the important sites dialog is shown. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Recorded when the user presses the 'clear' button when presented with the - list of installed apps they might want to exclude from clearing browsing - data. This histogram will be true if the user choose to exclude at least one - installed app from clearing. The default has all apps selected, in which - case this enum would be false. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Recorded when the user presses the 'clear' button when presented with the - list of installed apps they might want to exclude from clearing browsing - data. We record the number of apps the user deselected, or protected, from - clearing. The default has all apps selected. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Recorded when the user presses the 'clear' button when presented with the - list of installed apps they might want to exclude from clearing browsing - data. We record the percent of apps the user deselected, or protected, from - clearing. The default has all apps selected, which is 0%. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - Recorded when we successfuly fetched important sites in the clear browsing - data screen. This is the number of sites that we think are important to the - user. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Recorded when we successfuly fetched installed apps in the clear browsing - data screen. This is the number of apps that we think are important to the - user and allow the users to exclude from clearing browsing data. - - - - - msramek@chromium.org - - Recorded when the user deletes their passwords in the ClearBrowsingData - dialog. Counts how many other data types were selected for deletion. - - - - - msramek@chromium.org - - Whether a dialog with a notice about other forms of browsing history was - shown after the user deleted data from the Clear Browsing Data dialog. - - - - - - Removed 02/2020 since the histogram indicators were stable. - - dullweber@chromium.org - msramek@chromium.org - - Track whether the SpannableString is applied correctly in - ClearBrowsingDataCheckbox.java. (crbug.com/783866) - - - - - - - dullweber@chromium.org - msramek@chromium.org - - The number of tasks that are in the task queue when the BrowsingDataRemover - is destroyed. - - - - - dullweber@chromium.org - msramek@chromium.org - - Time spent in Clear Browsing Data dialog. From opening the dialog until data - is cleared. This does not record users who exit the dialog without clearing. - - - - - - - msramek@chromium.org - - Recorded when the user deletes their browsing data. Shows whether cookies - and/or cache were among the selected data types. - - - - - - - msramek@chromium.org - - Recorded when the user deletes their browsing data manually from the - ClearBrowsingData dialog. Shows whether cookies and/or cache were among the - selected data types. - - - - - dullweber@chromium.org - msramek@chromium.org - - Recorded when the user deletes their browsing data. Shows which tab was used - to perform the deletion. - - - - - shess@chromium.org - - Time spent on advanced History DB metrics calculation (weekly and monthly - URL, host, and category counts). Advanced metrics are logged on - initialization of the History DB on 0.3% of starts. - - - - - shess@chromium.org - - Time spent on basic History DB metrics calculation (file size and table - counts). Basic metrics are logged on initialization of the History DB on 1% - of starts. - - - - - shess@chromium.org - - Size of History DB file. Duplicate of Profile.HistorySize and - Sqlite.SizeKB.History. Logged on initialization of the History DB on 1% of - starts. - - - - - dimich@chromium.org - - Time spent on computing the monthly count of hosts visited. Reported every - time computation is performed, which in turn is done approximately weekly. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Count of "History Index *" databases deleted. These databases - stored the full-text-search data for history, which was removed at r213442, - this histogram tracks cleanup. - - - - - mpearson@chromium.org - mjzhang@chromium.org - chrome-analysis-team@google.com - - Number of unique domains visited by the user within a calendar day in user's - local timezone. For each profile, reported at profile open (which usually - happens at startup) for each unreported day (up to 7 days) prior to the - current date, and also reported once every 24 hours thereafter for the - latest unreported day, while the profile remains open. If no domains are - visited in a given day, a count of 0 will be reported for that day. - - Note: for users syncing between multiple devices, this count may include - some URLs/domains that weren't visited on this device. In other words, some - domains may be counted for multiple client_ids even though they were only - visited once, on one device. However, at this time (Feb 2020), only URLs - navigated to via the omnibox ("typed URLs") are synced, not all - visited URLs. There are no plans to change this behavior. As such, because - the mis-counting only occurs for users who are syncing across multiple - devices and only for a subset of visited URLs, the effect of double-counting - is likely to be small. - - - - - mpearson@chromium.org - mjzhang@chromium.org - chrome-analysis-team@google.com - - Number of unique domains visited by the user within a 28 calendar day period - in user's local timezone. For each profile, reported at profile open (which - usually happens at startup) for each unreported 28-day period (up to 7 - periods) ending on the current day, current day - 1, current day - 2, etc. - Also reported once every 24 hours thereafter for the latest unreported - period, while the profile remains open. If no domains are visited during a - 28-day period, a count of 0 will be reported for that period. - - Note: for users syncing between multiple devices, this count may include - some URLs/domains that weren't visited on this device. In other words, some - domains may be counted for multiple client_ids even though they were only - visited once, on one device. However, at this time (Feb 2020), only URLs - navigated to via the omnibox ("typed URLs") are synced, not all - visited URLs. There are no plans to change this behavior. As such, because - the mis-counting only occurs for users who are syncing across multiple - devices and only for a subset of visited URLs, the effect of double-counting - is likely to be small. - - - - - mpearson@chromium.org - mjzhang@chromium.org - chrome-analysis-team@google.com - - Number of unique domains visited by the user within a 7 calendar day period - in user's local timezone. For each profile, reported at profile open (which - usually happens at startup) for each unreported 7-day period (up to 7 - periods) ending on the current day, current day - 1, current day - 2, etc. - Also reported once every 24 hours thereafter for the latest unreported - period, while the profile remains open. If no domains are visited during a - 7-day period, a count 0 will be reported for that period. - - Note: for users syncing between multiple devices, this count may include - some URLs/domains that weren't visited on this device. In other words, some - domains may be counted for multiple client_ids even though they were only - visited once, on one device. However, at this time (Feb 2020), only URLs - navigated to via the omnibox ("typed URLs") are synced, not all - visited URLs. There are no plans to change this behavior. As such, because - the mis-counting only occurs for users who are syncing across multiple - devices and only for a subset of visited URLs, the effect of double-counting - is likely to be small. - - - - - mpearson@chromium.org - mjzhang@chromium.org - chrome-analysis-team@google.com - - Time spent on a scheduled computation task of domain visit counts. Each such - task computes a number of (at least 1 and up to 7) sets of domain counts, - where each set includes 3 results, for a 1-day, 7-day and 28-day period - respectively. Note that for each computation task, only one query time is - reported which covers the entire duration of the task. A task is scheduled - once at startup and every 24 hours thereafter while the browser remains - open. - - - - - calamity@chromium.org - - The percentage of time taken in ExpireHistoryBackend::ExpireVisits for - calculating the redirect parent. - - - - - calamity@chromium.org - - The time taken to expire a list of visits. This is not scaled to the number - of visits deleted, but gives an idea of how long a single request to - ExpireHistoryBackend::ExpireVisits takes. - - - - - rogerm@chromium.org - - The wall-clock time taken to gather favicon database metrics. Metrics are - logged on initialization of the Favicon DB on 1% of starts. - - - - - rogerm@chromium.org - - Size of the Favicons database in MB. This is calculated as the number of - pages consumed by the database multiplied by the page size. Logged on - initialization of the Favicon DB on 1% of starts. - - - - - - No longer tracked as of March 2017. - - rpop@google.com - - Size of the recovered Favicons database relative to the original corrupt - database. Recovery is VACUUM-like, so the resulting database should always - be smaller. Substantial 100% results would indicate empty databases being - recovered, substantial low% results would indicate very little data being - recovered. - - - - - - No longer tracked as of March 2017. - - rpop@google.com - - Rows recovered from [favicon_bitmaps] table in Favicons recovery. - - - - - - No longer tracked as of March 2017. - - rpop@google.com - Rows recovered from [favicons] table in Favicons recovery. - - - - - No longer tracked as of March 2017. - - rpop@google.com - - Rows recovered from [icon_mapping] table in Favicons recovery. - - - - - - No longer tracked as of March 2017. - - rpop@google.com - - Track results of SQLite database recovery code in thumbnail_database.cc. - - - - - yiyaoliu@chromium.org - - The count of differences between cached top sites and up-to-date top sites - when function TopSitesImpl::SetTopSites is firstly called at startup. - - - - - yiyaoliu@chromium.org - - The amount of time for function - history::TopSitesBackend::UpdateTopSitesOnDBThread to execute when this - function is called during startup. Excludes the case where local - TopSitesDatabase db_ is unavailable, i.e. where the update doesn't really - happen. - - - - - Please list the metric's owners. Add more owner tags as needed. - Time to check the thumbnail database for an url's favicon. - - - - calamity@chromium.org - src/chrome/browser/resources/history/OWNERS - - The page of the History page shown to the user. Logged each time the user - loads the History page or switches pages. - - - - - - Removed as of 02/2020. The vast majority of the time this is under 50ms. - - rkaplow@chromium.org - - The amount of time that elapsed during HistoryService::Init. - - - - - sky@chromium.org - sdefresne@chromium.org - - The phase of history initialization that failed. This histogram is only - logged on database initialization failure. - History.AttemptedToFixProfileError will tell how often initialization fails - overall. - - - - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - sky@chromium.org - mpearson@chromium.org - - The number of typed URLs in the history database that are read into the - "in memory" history database. This in memory copy of the typed - URLs is used for synchronous inline autocomplete on the UI thread, while the - larger slower service is run off of disk on a background thread. Recorded on - profile open. - - - - - sky@chromium.org - mpearson@chromium.org - - Number of items in in-memory keyword_search_terms table. Recorded on profile - open. - - - - - - Removed July 2020 as not deemed necessary. - - sky@chromium.org - mpearson@chromium.org - - Time to load in-memory keyword_search_terms table from disk. Recorded on - profile open. - - - - - sky@chromium.org - mpearson@chromium.org - - Number of items in in-memory urls table. Recorded on profile open. - - - - - - Removed July 2020 as not deemed necessary. - - sky@chromium.org - mpearson@chromium.org - - Time to load in-memory urls table from disk urls table. Recorded on profile - open. - - - - - sky@chromium.org - mpearson@chromium.org - - The time it takes to read the typed URLs from the main history database into - the "in memory" history database. This in memory copy of the typed - URLs is used for synchronous inline autocomplete on the UI thread, while the - larger slower service is run off of disk on a background thread. Recorded on - profile open. - - - - - - No longer needed. Removed Aug 2019 as part of crbug.com/969934 cleanup. - - gab@chromium.org - - The sum of the visit_count fields for all URLs in the "in memory" - history database. This corresponds to the number of times the user has - visited the typed URLs in the last 30 days (excluding page reloads, since - the history database does not increment the visit_count in that case). - Recorded on profile open. - - - - - - Removed August 2020. - - mpearson@chromium.org - - Size of on-disk cache for in-memory url index. Recorded on profile open when - restoring from a cache file. - - - - - - Removed August 2020. - - mpearson@chromium.org - - Number of items in the in-memory url index char_word_map_. Recorded on - profile open when restoring from a cache file and again shortly after - profile open when rebuilding the in-memory url index from history. - - - - - mpearson@chromium.org - chrome-omnibox-team@google.com - - Number of history items in the in-memory url index. Recorded on profile open - when restoring from a cache file and again shortly after profile open when - rebuilding the in-memory url index from history. - - - - - mpearson@chromium.org - ssid@chromium.org - - Time to rebuild in-memory url index from main history database. Recorded - once shortly after profile open. - - - - - - Removed July 2020. - - mpearson@chromium.org - ssid@chromium.org - - Time to restore the in-memory url index from disk cache. Recorded on profile - open. - - - - - - Removed July 2020. - - mpearson@chromium.org - ssid@chromium.org - - Time to write in-memory url index to disk cache. Recorded once shortly after - profile open (after rebuilding the in-memory url index from history) and - again upon (clean) shutdown. - - - - - - Removed August 2020. - - mpearson@chromium.org - - Number of items in in-memory url index word_map_. Recorded on profile open - when restoring from a cache file and again shortly after profile open when - rebuilding the in-memory url index from history. - - - - - sky@chromium.org - sdefresne@chromium.org - - History database version from which history migration failed. If there are - higher than normal migration failures, this histogram will indicate which - migration step failed. - - - - - mpearson@chromium.org - sky@chromium.org - - Unique hostnames in History database urls table with last-visit times in the - last 30 days. Metrics are logged on initialization of the History DB on 0.3% - of starts. See also ExploreSites.MonthlyHostCount metric which is similar - but is reported on a elapsed time basis to help avoid bias toward more - active users. - - - - - mpearson@chromium.org - sky@chromium.org - - Unique URLs in History database urls table with last-visit times in the last - 30 days. Metrics are logged on initialization of the History DB on 0.3% of - starts. - - - - - mpearson@chromium.org - sky@chromium.org - - Number of rows in History visits table with visit times in the last 30 days. - Metrics are logged on initialization of the History DB on 1% of starts. - - - - - rogerm@chromium.org - - The total number of favicon bitmaps (of all sizes) cached in a user's - Favicon database. A given favicon URL may be associated with multiple - bitmaps (of different sizes). Logged on initialization of the Favicon DB on - 1% of starts. - - - - - rogerm@chromium.org - - The number of page URL (e.g., http://www.google.com) to favicon URL (e.g., - http://www.google.com/favicon.ico) mappings stored in a user's Favicon - database. Logged on initialization of the Favicon DB on 1% of starts. - - - - - rogerm@chromium.org - - The total number of favicon URLs (e.g. http://www.google.com/favicon.ico) - tracked in a user's Favicon database. This metric tracks knowledge of a - favicon URL not whether there are cached bitmaps for that favicon URL. See - History.NumFaviconBitmapsInDB for that. Logged on initialization of the - Favicon DB on 1% of starts. - - - - - rogerm@chromium.org - - The total number of large (>= 64 pixels wide) favicons being tracked in a - user's Favicon database. This is a subset of History.NumFaviconBitmapsInDB, - which includes all sizes in its count. Logged on initialization of the - Favicon DB on 1% of starts. - - - - - rogerm@chromium.org - - The total number of touch icons being tracked in a user's Favicon database. - This is a subset of History.NumFaviconsInDB, which includes all icon types - in its count. Logged on initialization of the Favicon DB on 1% of starts. - - - - - chengx@chromium.org - - The amount of time for function HistoryBackend::QueryMostVisitedURLs to - execute. Excludes the case where local HistoryDatabase db_ is unavailable, - i.e. where the query doesn't really happen. - - - - - calamity@chromium.org - dbeam@chromium.org - - Records the time taken to load the history Web UI and render (at least) a - screen full of items. This is roughly equivalent to 'time to first - meaningful paint' for the history page. - - - - - msramek@chromium.org - - Whether the notice about other forms of browsing history was shown in the - header of the History page when the header was displayed. The header is - refreshed with every history query. - - - - - - Removed as of 11/2018, not used in production since 2/2018. - - twifkak@chromium.org - bengr@chromium.org - - Page visits to each of a user's top 50 hosts. The bucket is the 1-based rank - of the host. Visits to all other hosts go into the 51st bucket. - Android-only. Only counts the last URL in a redirect chain and does not - include reloads. The list of top hosts is computed approximately nightly. - This means that a given day will likely include a recalculation of top - hosts, and therefore a given bucket may represent two different hosts at - different times of day. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Size of the recovered TopSites database relative to the original corrupt - database. Recovery is VACUUM-like, so the resulting database should always - be smaller. Substantial 100% results would indicate empty databases being - recovered, substantial low% results would indicate very little data being - recovered. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Rows recovered from [thumbnails] table in TopSites recovery. - - - - - Please list the metric's owners. Add more owner tags as needed. - - The TopSites recovery code is written conservatively, with successful - recovery committed and any failure leading to rollback. This tracks the - outcomes to determine which cases are high-frequency enough to warrant - adding additional code to handle them (versus simply deleting the data). - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Page visits to each of a user's top 50 sites. Visits to all other sites go - into the 51st bucket. Only count the page visit if it came from user - browsing and only count it once when cycling through a redirect chain. - - - - - - Removed because only the execution time at startup is of interest. See - histogram History.UpdateTopSitesOnDBThread_Startup_Time. - - yiyaoliu@chromium.org - - The amount of time for function - history::TopSitesBackend::UpdateTopSitesOnDBThread to execute. Excludes the - case where local TopSitesDatabase db_ is unavailable, i.e. where the update - doesn't really happen. - - - - - mpearson@chromium.org - sky@chromium.org - - Number of rows in urls table in History DB. Metrics are logged on - initialization of the History DB on 1% of starts. - - - - - mpearson@chromium.org - sky@chromium.org - - Number of rows in visits table in History DB. Metrics are logged on - initialization of the History DB on 1% of starts. - - - - - mpearson@chromium.org - sky@chromium.org - - Unique hostnames in History database urls table with last-visit times in the - last 7 days. Metrics are logged on initialization of the History DB on 0.3% - of starts. - - - - - mpearson@chromium.org - sky@chromium.org - - Unique URLs in History database urls table with last-visit times in the last - 7 days. Metrics are logged on initialization of the History DB on 0.3% of - starts. - - - - - mpearson@chromium.org - sky@chromium.org - - Number of rows in History visits table with visit times in the last 7 days. - Metrics are logged on initialization of the History DB on 1% of starts. - - - - - msramek@chromium.org - dullweber@chromium.org - - Recorded each time an entry on the history page is clicked. Measures the age - in days (defined as 24 hour periods, not using local time) of that entry. - Values are ROUNDED UP, i.e. "1" means at most one day old etc. - - - - - msramek@chromium.org - dullweber@chromium.org - - Subset of the HistoryPage.ClickAgeInDays histogram, with better bucket - resolution at lower numbers. - - - - - rpop@google.com - - Number of entries that the clicked entry is older than in History page. Last - bucket is any entry of that value or higher. - - - - - rpop@google.com - - Subset of the Click Position histogram. Contains only the first smaller - subset of entries on the page. Number of entries that the clicked entry is - older than in History page. Last bucket is entries of that value or higher. - - - - - - - rpop@google.com - chrome-analysis-team@google.com - - Histogram for usage of the section in the history page that allows the user - to access tabs from other devices. - - OtherSessionsActions.OPENED_LINK_VIA_CONTEXT_MENU was added for M-76. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - markchang@chromium.org - - The number of tabs created in each window when a user executes "Open - all" menu item from a session menu in the "Tabs from other - devices" section of the history page. - - - - - markchang@chromium.org - - Total number of tabs opened when a user executes "Open all" menu - item from a session menu in the "Tabs from other devices" section - of the history page. - - - - - markchang@chromium.org - - Total number of windows opened when a user executes "Open all" - menu item from a session menu in the "Tabs from other devices" - section of the history page. - - - - - rpop@google.com - - Number of entries that the deleted entry is older than in History page. Last - bucket is any entry of that value or higher. Confirmed removal is not - guaranteed, just an initiation of 'Remove selected items'. - - - - - rpop@google.com - - Subset of Remove Entry Position histogram. Contains only the first smaller - subset of entries on the page. Number of entries that the deleted entry is - older than in History page. Last bucket is any entry of that value or - higher. Confirmed removal is not guaranteed, just an initiation of 'Remove - selected items'. - - - - - calamity@chromium.org - src/chrome/browser/ui/page_action/OWNERS - - Counts which content setting buttons in the hosted app frame are pressed by - the user. - - - - - calamity@chromium.org - alancutter@chromium.org - - Number of times that each menu item is clicked from the hosted app window - menu button. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - rlp@chromium.org - - The state of the hotword audio logging preference. This value is emitted - each time the hotword availability is requested by the extension if the user - is also opted in to hotword voice search. This check typically happens each - time a hotword search is initiated. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - rlp@chromium.org - - The state of the hotword preference. This value is emitted during - HotwordService initialization which happens during Profile initialization. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - rlp@chromium.org - - Whether the external component hotword extension exists (i.e., not pending - download, disabled, etc.). This value is emitted each time the hotword - availability is requested by the extension which typically happens each time - a hotword search is initiated. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - rlp@chromium.org - - Errors reported by the hotword service when determining if hotwording is - available. Non-errors are also reported so that errors can be seen as a - percentage of total requests. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - amistry@chromium.org - rlp@chromium.org - somast@chromium.org - - Success or error when attempting to open a MediaStream for the microphone. - At most one success or error will be logged for an attempt to open a stream. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - amistry@chromium.org - rlp@chromium.org - somast@chromium.org - - Timeout occured while waiting for a message from the NaCl hotword detector - plugin. This value is the message that was expected to be received from the - plugin. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - amistry@chromium.org - rlp@chromium.org - somast@chromium.org - - Success or error when attempting to load the NaCl hotword detector plugin. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - amistry@chromium.org - rlp@chromium.org - somast@chromium.org - - Location of hotword trigger. Emitted every time the hotword is triggered by - the user saying 'Ok Google'. - - - - - - Removed as of 10/2017. Feature removed with crbug/761426. - - amistry@chromium.org - rlp@chromium.org - somast@chromium.org - - Language, switched to by the user, that triggered a hotword shared module - reinstall. - - - - - - Removed as of 02/2020. - - yhirano@chromium.org - lukasza@chromium.org - - Logs the type of requests made by HTML imports with wrong fetcher. - - - - - morlovich@chromium.org - - For every http cache transaction with a pattern (see HttpCache.Pattern), the - time from the first access to the disk cache until the transaction was done. - - - - - morlovich@chromium.org - - For http cache transactions in which a network request was sent, the time - elapsed between sending it over the network until the transaction was done. - - - - - - Removed as of 3/2015. - - ricea@chromium.org - - The time spent performing an asynchronous revalidation that was triggered by - a Cache-Control: stale-while-revalidate directive. This is recorded when the - asynchronous revalidation completes, either after the response was - completely read or an error occurred. One entry is recorded for each - asynchronous revalidation that is performed. - - - - - morlovich@chromium.org - - For http cache transactions in which a network request was sent, the time - elapsed between beginning the request and sending it over the network; this - is the time spent accessing the disk cache. - - - - - jkarlin@chromium.org - - For each request that results in an unconditionalizable network request, the - cause for the request. - - - - - morlovich@chromium.org - - For each request with HttpCache.CantConditionalizeCause == Zero Freshness, - this is true iff the zero freshness status was determined by looking at - in-memory hints in disk cache index, rather than by opening the entry and - looking at headers. - - - - - jkarlin@chromium.org - morlovich@chromium.org - - The time spent waiting for write lock on a disk cache entry. - - - - - - stale-while-revalidate implementation removed for now, see - https://crbug.com/700568. - - ricea@chromium.org - - Count of the number of external (ie. from Blink) conditionalized requests, - and whether or not those requests could have been served from the browser - cache. - - - - - ericrobinson@chromium.org - shivanisha@chromium.org - - Whether the HttpCache was forced to reset upon creation, effectively - clearing out its previous content. This is recorded when the cache is - created for the browsing session. - - - - - - Removed in favor of HttpCache.NetworkIsolationKeyPresent2. - - jkarlin@chromium.org - shivanisha@chromium.org - - Records whether a cache request has a network isolation key set or not, - which is used for double-keying. - - - - - jkarlin@chromium.org - shivanisha@chromium.org - - Records whether a cache request has a network isolation key set or not, - which is used for double-keying. - - - - - - Removed 4/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Result of a main page HttpCacheTransaction if offline mode had been enabled. - - - - - shivanisha@chromium.org - - Records whether a transaction either created a Writers object when one - didn't exist, or joined an existing Writers object, or why it failed to do - so (e.g., it's a range request, it's not a GET request, etc.). - - - - - morlovich@chromium.org - jkarlin@chromium.org - For each http cache transaction, the recorded pattern. - - - - - Removed 2019-07-03. - - morlovich@chromium.org - - For http cache transactions in which a network request was sent, the - percentage of total request time that elapsed before sending the request - over the network; this is the time spent accessing the disk cache. - - - - - morlovich@chromium.org - Net error results from non-restartable cache read errors. - - - - morlovich@chromium.org - Net error results from restartable cache read errors. - - - - - Removed in M77. One day Android results: 25.00% 1033 50.00% 4945 75.00% - 42023 95.00% Infinity - - jkarlin@chromium.org - - For each http cache transaction for which a cache entry exists but it cannot - be used because the entry's age is beyond its freshness: counts how many - freshness periods have elapsed since the entry was last used (x1000). - - - - - - Removed in M77. One day percentiles on Android: 25.00% 16146 50.00% 101342 - 75.00% 372632 95.00% Infinity - - jkarlin@chromium.org - - For each http cache transaction for which a validation attempt is made due - to a stale entry and is updated (e.g., 200), records the age of the entry in - seconds. - - - - - - Removed in M77. One day percentiles on Android: 25.00% 246.3 50.00% 1353 - 75.00% 9142 95.00% 147572 99.00% Infinity - - jkarlin@chromium.org - - For each http cache transaction for which a validation attempt is made due - to a stale entry and is updated (e.g., 200), records the age of the entry as - percentage of freshness period. - - - - - - Removed in M77. One day percentiles on Android: 25.00% 10791 50.00% 70285 - 75.00% 223571 95.00% Infinity - - jkarlin@chromium.org - - For each http cache transaction for which a validation attempt is made due - to a stale entry and is validated (304), records the age of the entry in - seconds. - - - - - - Removed in M77. One day percentiles on Android: 25.00% 169.5 50.00% 476.3 - 75.00% 2451 95.00% 43218 99.00% 474791 99.50% Infinity - - jkarlin@chromium.org - - For each http cache transaction for which a validation attempt is made due - to a stale entry and is validated (304), records the age of the entry as - percentage of freshness period. - - - - - - Removed 07/2019 and replaced by HttpCache.NetworkIsolationKeyPresent. - - jkarlin@chromium.org - shivanisha@chromium.org - - Records whether a cache request has a top frame origin set or not, which is - used for double-keying. - - - - - jkarlin@chromium.org - For each validation attempt, the cause for the validation. - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - The type of Vary header for a given GET response. - - - - - - garryxiao@chromium.org - cylai@chromium.org - cros-hwsec-userland-eng+uma@chromium.org - - The result of attestation-related operations on the Chrome OS side. - - - - - kojii@chromium.org - layout-dev@chromium.org - The time it takes to open a hyphenation dictionary. - - - - kojii@chromium.org - layout-dev@chromium.org - The time it takes to open a hyphenation dictionary file. - - - - ftang@chromium.org - intl-libs-team@google.com - - This metric logs the creation of key ICU objects. These object creation - called directly from Chrome code or indirectly from depending library such - as blink and v8. - - - - - ftang@chromium.org - intl-libs-team@google.com - - This metric logs the ICU built-in data file name opened and used by chrome. - These file open calls are perform internally inside ICU while Chrome - directly or indirectly call ICU to create object and cause ICU to load new - data files, such as loading codeset conversion table, create break iterator, - and open dictionary files for word break/line break iterator. It however - does not include the opening of resource bundle files. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Time it takes to do high-quality image resampling for images that are - resized. Non-resized images and ones our heuristic decides can be done - "badly" are not counted. - - - - - amoylan@chromium.org - martis@chromium.org - - For each image processed by the image annotation service, records whether or - not results for the image already existed in the client-side cache. A hit - means that image data was not transmitted to the image annotation server. - - - - - dmazzoni@chromium.org - amoylan@chromium.org - martis@chromium.org - - For each request made by a client feature to the image annotation service, - reports the final status of the service response. - - - - - - - amoylan@chromium.org - martis@chromium.org - - For each annotation of the given type returned by the image annotation - server, records the confidence (as a percentage) produced by the ML model - for the annotation. - - - - - amoylan@chromium.org - martis@chromium.org - - For each annotation backend run by the image annotation server, records the - gRPC status reported. - - - - - - - amoylan@chromium.org - martis@chromium.org - - For each annotation of the given type returned by the image annotation - server, records whether or not the text of the annotation was empty. This is - sometimes valid, e.g. for text extraction (OCR) on an image that does not - contain any text. - - - - - amoylan@chromium.org - martis@chromium.org - - For each image sent from a client feature to the image annotation service, - reports the image's final size (in kilobytes) after resizing and reencoding. - - - - - amoylan@chromium.org - martis@chromium.org - - For each annotation backend run by the image annotation server, records - whether or not the backend is recognised by this version of Chrome. - - - - - amoylan@chromium.org - martis@chromium.org - - For each image request sent to the image annotation server, records whether - or not the description backend is included among the requested backends. - - The description backend will not be included when the image is known to - violate the description model policy (i.e. be too small or have too-high an - aspect ratio). - - - - - dmazzoni@chromium.org - amoylan@chromium.org - martis@chromium.org - - For each non-empty response sent from the image annotation server, records - whether or not JSON data were successfully parsed from the response body. - - - - - amoylan@chromium.org - martis@chromium.org - - For each pixel fetch request sent from the image annotation service to a - client feature, records whether or not encoded pixel data were successfully - returned to the service. - - - - - amoylan@chromium.org - martis@chromium.org - - For each HTTP response from the image annotation server, reports the - associated HTTP code. - - - - - amoylan@chromium.org - martis@chromium.org - - For each HTTP response from the image annotation server, reports the time - elapsed (in milliseconds) since the corresponding request was sent. - - - - - amoylan@chromium.org - martis@chromium.org - - For each HTTP request sent to the image annotation server, reports the net - error (or OK status) of the request. - - - - - amoylan@chromium.org - martis@chromium.org - - For each HTTP request sent to the image annotation server, reports the size - of the request. Measured in kilobytes, since a request can contain the pixel - data of multiple images. - - - - - amoylan@chromium.org - martis@chromium.org - - For each HTTP response from the image annotation server, reports the - response size in bytes. - - - - - amoylan@chromium.org - martis@chromium.org - - For each image sent from a client feature to the image annotation service, - reports the image's original (i.e. pre-scaling) area in pixels. Images with - pixel count above a certain threshold will be resized prior to transmission. - - - - - - - amoylan@chromium.org - martis@chromium.org - - For each annotation backend run by the image annotation server, records the - gRPC status reported. - - - - - - - fgorski@chromium.org - wylieb@chromium.org - xingliu@chromium.org - - The total number of metadata entries in the image fetcher cache metadata - database for a given cache strategy. Recorded during cache eviction process. - - - - - - - fgorski@chromium.org - wylieb@chromium.org - xingliu@chromium.org - - The total size of the cache for a given cache strategy. Recorded during - cache eviction process. - - - - - fgorski@chromium.org - wylieb@chromium.org - - Events that track the lifecycle and performance of the cached_image_fetcher. - The events reported include: success/failure conditions, various recoverable - errors and a couple of dead-end errors. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the cache - in native. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the cache - in Java. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from native - code. Only recorded on successful loads. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the network - after a cache hit. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes for cached_image_fetcher to load an image from the - network. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time it takes to load an image's metadata from the metadata store. - - - - - fgorski@chromium.org - wylieb@chromium.org - - Android: The integer status code of network requests made by the image data - fetcher. This code includes both protocol(1xx-5xx) and non-protocol(-xxx) - errors. Recorded when a request completes. - - - - - fgorski@chromium.org - wylieb@chromium.org - - The time since the last LRU eviction from the image cache. Recorded when two - LRU evictions occur within closure proximity to one another. Will be used to - determine if LRU eviction is happening too frequently. - - - - - tapted@chromium.org - chromeos-files-app@google.com - - For each image load request that requested caching, records whether or not - it was found in the client-side cache. A hit means the request was not - forwarded to the ImageLoader extension. - - - - - tapted@chromium.org - chromeos-files-app@google.com - - Returns the percentage of the client-side cache that is used for loading - images, before they are sent to the ImageLoader extension. Expressed as a - percentage of ImageLoaderClient.CACHE_MEMORY_LIMIT (e.g. 20MB). - - - - - tapted@chromium.org - chromeos-files-app@google.com - - For each image load request records whether or not it requested caching. - - - - - gcomanici@chromium.org - - The size of the history on Auto Import from IE. This measure is only logged - on a succesfull Auto Import. - - - - - gab@chromium.org - The importer used on first run Auto Import. - - - - gab@chromium.org - The importer used on import from the bookmarks file API. - - - - gab@chromium.org - - The importer used on import from the chrome://settings/importData UI. - - - - - - Removed 06/19. - - vasilii@chromium.org - hurims@gmail.com - - Whether or not the password checkbox is checked when importing a profile of - Firefox. Note that canceled imports could be counted also. - - - - - - Removed 07/2020. - - vasilii@chromium.org - hurims@gmail.com - - The number of passwords that are imported from Firefox. This is recorded - when importing a profile of Firefox with the password checkbox checked. Note - that the reported number of password could be slightly bigger than the - actual number of imported passwords because some incomplete or blacklisted - passwords that are dropped while importing might be included in the reported - value. - - - - - - Removed and removed BookmarkBarView - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time from install time to time that user opens import dialog - from BookmarkBarView. - - - - - - Removed and removed BookmarkBarView - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time from install time to time that user opens import dialog - from NTP floating BookmarkBarView. - - - - - - Removed and replaced by Import.ShowDialog.FromBookmarkBarView - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time from install time to time that user opens import dialog - from BookmarkBarView. - - - - - - Removed and replaced by Import.ShowDialog.FromFloatingBookmarkBarView - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time from install time to time that user opens import dialog - from NTP floating BookmarkBarView. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - File error on Windows when ImportantFileWriter fails to mark the temporary - file for deletion upon closure. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - File error happened upon temporary file creation at ImportantFileWriter. - - - - - - Replaced by ImportantFile.FileDeleteNoRetryError, - ImportantFile.FileDeleteRetryExceededError, and - ImportantFile.FileDeleteRetrySuccessCount in M84. - - grt@chromium.org - xaerox@yandex-team.ru - - File error happened upon temporary file deletion at ImportantFileWriter. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - File error happened upon temporary file deletion at ImportantFileWriter when - it was not possible to retry in a delayed task. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - The final file error when all retries for deleting the temorary file fail. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - The number of retries needed to successfully delete the temporary file. Only - recorded when at least one retry (two attempts) is needed. - - - - - - Removed in M84. - - xaerox@yandex-team.ru - - File error happened upon opening temporary file at ImportantFileWriter. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - File error happened upon temporary file renaming at ImportantFileWriter. - - - - - grt@chromium.org - xaerox@yandex-team.ru - - File error happened upon writing data to temporary file at - ImportantFileWriter. - - - - - grt@chromium.org - lassey@google.com - - Count of various failures in ImportantFileWrite when manipulating a temp - file to write to before moving it into place (replacing another file). - - - - - - Removed in 2019-11. - - mamir@chromium.org - - Time used to atomically write string into a file using ImportantFileWriter. - - - - - robliao@chromium.org - - The thread used to initialize the Windows parental controls. - - - - - robliao@chromium.org - - The amount of time that elapsed during a run of - PlatformParentalControlsValue::IsParentalControlActivityLoggingOnImpl on - Windows 7 and above. - - - - - pmonette@chromium.org - - Records whether the user was automatically shown the - chrome://settings/incompatibleApplications page following a Chrome crash. - - - - - pmonette@chromium.org - - The number of incompatible applications detected by Chrome at the time the - chrome://settings/incompatibleApplications page was opened. - - - - - timvolodine@chromium.org - - Whether the Sensor.TYPE_LINEAR_ACCELERATION was available at the start of - Device Motion. - - - - - timvolodine@chromium.org - - Whether the Sensor.TYPE_ACCELEROMETER was available at the start of Device - Motion. - - - - - timvolodine@chromium.org - - Whether the SENSOR_TYPE_ACCELEROMETER_3D was available at the start of - Device Motion on the Windows platform. - - - - - timvolodine@chromium.org - - Provides a histogram of the base sensors (if any) that are used at the start - of the Device Orientation API. Currently Sensor.TYPE_GAME_ROTATION_VECTOR is - the default sensor for orientation, if it's not available fall-back options - are provided by using either Sensor.TYPE_ROTATION_VECTOR or a combination of - Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD. - - - - - timvolodine@chromium.org - - Whether the SENSOR_TYPE_GYROMETER_3D was available at the start of Device - Motion on the Windows platform. - - - - - timvolodine@chromium.org - - Whether the Sensor.TYPE_GYROSCOPE was available at the start of Device - Motion. - - - - - timvolodine@chromium.org - - Whether the SENSOR_TYPE_INCLINOMETER_3D was available at the start of Device - Orientation on the Windows platform. - - - - - timvolodine@chromium.org - - This histogram counts the number of Device Motion API invocations in the - default implementation (Linux and CrOS). The default implementation does not - provide any sensors so the result is always false. - - - - - timvolodine@chromium.org - - Whether the sudden motion sensor was available at the start of Device Motion - on the MacOS platform. - - - - - timvolodine@chromium.org - - This histogram counts the number of Device Orientation API invocations in - the default implementation (Linux and CrOS). The default implementation does - not provide any sensors so the result is always false. - - - - - timvolodine@chromium.org - - Whether the sudden motion sensor was available at the start of Device - Orientation on the MacOS platform. - - - - - - Removed 11/2014 (crbug.com/347507). Replaced by - InertialSensor.DeviceOrientationSensorAndroid. - - timvolodine@chromium.org - - Whether the Sensor.TYPE_ROTATION_VECTOR was available at the start of Device - Orientation. - - - - - - - rkaplow@chromium.org - src/components/infobars/OWNERS - - Records how many times a particular infobar was shown to the user. On - Android, the infobar may be partially hidden due to stacking. On desktop, a - tab with a visible infobar will increment this histogram every time the user - switches away from the tab and back to it with the infobar still visible. - - - - - - - mdjones@chromium.org - dominickn@chromium.org - - Records how many times a particular infobar was displayed in a hidden state - due to at least one other infobar existing. If there are no existing - infobars, but the user scrolls at the exact moment a new infobar is added, - the infobar may be hidden, but not recorded in this metric. Reliably - triggering and detecting this combination is tricky so it isn't done. Only - recorded on Android. - - - - - - - mdjones@chromium.org - dominickn@chromium.org - - Records how many times a particular infobar was visible and hiding a new - infobar behind it. Only recorded on Android. - - - - - - - mdjones@chromium.org - dominickn@chromium.org - - Records how many times a particular infobar was displayed in a visible state - due to no other infobars existing. If there are no existing infobars, but - the user scrolls at the exact moment a new infobar is added, the infobar may - be hidden, but recorded here as visible. Reliably triggering and detecting - this combination is tricky so it isn't done. Only recorded on Android. - - - - - nyquist@chromium.org - xingliu@chromium.org - - Records if in-product help configuration is parsed correctly, and the - failure reasons for parsing failures. - - - - - nyquist@chromium.org - xingliu@chromium.org - - - - Records if database initialization succeeds for in-product help. - - - - - nyquist@chromium.org - xingliu@chromium.org - - - - Records if database successfully loads the data for in-product help. - - - - - nyquist@chromium.org - xingliu@chromium.org - - Records the total number of event records in the database for in-product - help after the event model is loaded. - - - - - nyquist@chromium.org - xingliu@chromium.org - - - - Records if each database update succeeds for in-product help. - - - - - nyquist@chromium.org - xingliu@chromium.org - - - - Records if the model is ready when in-product help event happens. - - - - - collinbaker@chromium.org - - Last step of in-product help (IPH) for reopening tabs that user followed - before finishing the IPH flow or dismissing it early. Recorded when the IPH - flow is dismissed, which is at one of three possible times: when the promo - bubble times out, when the menu is closed after the user opens it for IPH, - or when the user opens the last closed tab. The last is considered a - success. - - - - - nyquist@chromium.org - xingliu@chromium.org - - - - Records if in-product help is shown to the user, and the failure reasons if - in-product help is not shown. Recorded on its own across all in-product help - features, in addition to being a base name for feature-specific histograms. - - - - - myy@chromium.org - essential-inputs-team@google.com - - The number of active input methods. Recorded when the user logs in to Chrome - OS or each cold start of Chrome on Android. The active input methods are - selected by user in the language settings page on Chrome OS and in system - language settings on Android. - - - - - myy@google.com - essential-inputs-team@google.com - - Tracks when assistive autocorrect is performed by a text input client. - Recorded when autocorrect is triggered by users with the feature enabled - using a text input client that's being tracked. - - - - - jopalmer@google.com - essential-inputs-team@google.com - - Tracks time between when autocorrect occurs and user clicks to undo the - autocorrect. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The number of times each assistive action is triggered. Recorded when - assistive actions are triggered. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The number of times each assistive action could be triggered according to - the surrounding text but was not triggered because the user turned off the - feature. Recorded when the surrounding text could trigger assistive actions - but the corresponding feature was disabled. - - - - - myy@google.com - essential-inputs-team@google.com - - The reason for emoji suggestions not being shown to users. Recorded when the - surrounding text could trigger emoji suggestions but the feature was - disabled. Only the first applicable reason in IMEAssistiveDisabledReason - enum is recorded per occurrence. - - - - - myy@google.com - essential-inputs-team@google.com - - The reason for personal information suggestions not being shown to users. - Recorded when the surrounding text could trigger personal information - suggestions but the feature was disabled. Only the first applicable reason - in IMEAssistiveDisabledReason enum is recorded per occurrence. - - - - - myy@google.com - essential-inputs-team@google.com - - The number of times an emoji suggest addition is accepted at a given index. - Recorded when an user accepts an emoji suggestion appeared after typing an - emoji-triggered word. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The number of times each assistive action could be triggered according to - the surrounding text. This includes cases in InputMethod.Assistive.Coverage, - and also includes cases when the feature is turned off or there is - insufficient data. Recorded when the surrounding text could trigger - assistive actions. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The number of times each assistive action is accepted. Recorded when - assistive actions are accepted by the users. - - - - - myy@google.com - essential-inputs-team@google.com - - The duration from when emoji suggestions show up to when users accept a - suggestion. Recorded when users accept the suggestion. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The duration from when personal info suggestions show up to when users - accept a suggestion. Recorded when users accept the suggestion. - - - - - myy@google.com - essential-inputs-team@google.com - - The duration from when emoji suggestions show up to when users dismiss a - suggestion. Recorded when users dismiss the suggestion. - - - - - jiwan@google.com - essential-inputs-team@google.com - - The duration from when personal info suggestions show up to when users - dismiss a suggestion. Recorded when users dismiss the suggestion. - - - - - myy@google.com - essential-inputs-team@google.com - - The user's preference for emoji suggestions. Recorded when - AssistiveSuggester is initialised. "Enabled" is logged as the - default value if the user didn't explicitly set it. - - - - - myy@google.com - essential-inputs-team@google.com - - The user's preference for personal information suggestions. Recorded when - AssistiveSuggester is initialised. "Enabled" is logged as the - default value if the user didn't explicitly set it. - - - - - shend@chromium.org - essential-inputs-team@google.com - The auto-correction level for suggestion engine. - - - - shend@chromium.org - essential-inputs-team@google.com - - The breakdown of input method usage by input method category. Recorded when - the system changes the current input method. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The suggestion index (1-based) of the suggestion list item which user - chooses to commit. - - - - - - Removed 03/2015, and replaced by InputMethod.Commit.Type2. - - shuchen@chromium.org - - The suggestion accuracy type which the user chooses to commit. - - - - - shuchen@chromium.org - - The suggestion accuracy type which the user chooses to commit. - - - - - shuchen@chromium.org - The number of characters committed with composition text. - - - - lanwei@chromium.org - siliu@microsoft.com - - Whether the composition is composed by IMM32-based input method processor - when TSF is disabled on Windows. Recorded when user starts new composition. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Types of actions performed by the user during handwriting, recorded when the - user performs a gesture action. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - The index of the selected suggestion from the handwriting alternative - suggestion menu. This metric is recorded when the handwriting text - highlighted is multiple words, and the selected suggestion is a single word. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - The index of the selected suggestion from the handwriting alternative - suggestion menu. The metric is recorded when the suggestion is selected. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - The index of the selected suggestion from the handwriting alternative - suggestion menu. This metric is recorded when the handwriting text - highlighted is a single word, and the selected suggestion is mutliple words. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Number of characters written in a 10 second interval, recorded every 10s - while the handwriting keyboard is active. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Number of characters written in a 5 second interval, recorded every 5s while - the handwriting keyboard is active. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Number of characters written in a 60 second interval, recorded every 60s - while the handwriting keyboard is active. - - - - - - This is deprecated since M46, InputMethod.ID2 is used since then. - - shuchen@chromium.org - - The breakdown of input method usage by input method IDs. Recorded when the - user presses keys on physical or on-screen keyboard. - - - - - shuchen@chromium.org - - The breakdown of input method usage by input method IDs. Recorded when the - user presses keys on physical or on-screen keyboard. - - - - - azurewei@chromium.org - shuchen@chromium.org - - Whether the opt-in IME menu in the shelf has been activated. - - - - - azurewei@chromium.org - shuchen@chromium.org - - The number of times users click emoji, handwriting or voice button in opt-in - IME menu. - - - - - shuchen@chromium.org - The trigger type of input method switches by user. - - - - shend@chromium.org - essential-inputs-team@google.com - Time taken by the engine to handle a key event. - - - - aurimas@chromium.org - - Whether the currently selected keyboard language matches the system - language. Recorded once with every cold start of Chrome for Android. - - - - - shend@chromium.org - essential-inputs-team@google.com - The result of the user pressing the mode change key. - - - - googleo@chromium.org - shuchen@chromium.org - - The time taken to activate a new IME via IME Mojo service in the IME - extension. It's from when the IME extension sends out an request to activate - a new IME until the new IME is resolved in the IME service and its Mojo - interface is bound to the IME extension. - - - - - shend@chromium.org - essential-inputs-team@google.com - The events of Mojo service in the IME Extension. - - - - shend@chromium.org - essential-inputs-team@google.com - - The time taken to process a rulebased request via the IME Mojo service - inside the IME extension. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The time taken to initialize the IME Mojo service in the IME extension. It's - from the IME extension starts loading a private Mojo bundle for making a - request to connect a IME service until the connection between the extension - and the IME Mojo service is built. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The suggestion index (1-based) of the suggestion list item which user - chooses to commit for physical keyboard autocorrect. - - - - - shuchen@chromium.org - - The suggestion accuracy type which the user chooses to commit for physical - keyboard autocorrect. - - - - - - Removed as of Jan 2020. - - changwan@chromium.org - The result of registering proxy view to InputMethodManager. - - - - shend@chromium.org - essential-inputs-team@google.com - - The number of times the backspace key was pressed on the virtual keyboard, - while the virtual keyboard was alive. Recorded when the virtual keyboard is - closed. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The layout type of the virtual keyboard, recorded when backspace is pressed. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that counts the number of times the cursor was moved to - the previous word by swiping backwards on the selection track. The count is - initialized when the user starts swiping from any side of the virtual - keyboard, incremented based on how far they swipe backwards on the selection - track, and recorded when they release their finger. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Counts the length of text typed by the virtual keyboard between each - backspace. This metric provides a rough approximation of an error rate for - the virtual keyboard. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The total number of characters committed. Recorded when the virtual keyboard - is closed. - - - - - keithlee@google.com - essential-inputs-team@google.com - - The character per minute ratio recoded during a typing session. - - - - - keithlee@google.com - essential-inputs-team@google.com - - The total number of characters committed during a typing session. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that counts the number of times each virtual keyboard - display mode is used. Recorded when the virtual keyboard is opened or a user - changes the keyboard mode from UI in the virtual keyboard. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that counts events from the decoder triggered by the - virtual keyboard. - - - - - shend@chromium.org - essential-inputs-team@google.com - How long the virtual keyboard was visible. - - - - shend@chromium.org - essential-inputs-team@google.com - How emojis were inserted. - - - - shend@chromium.org - essential-inputs-team@google.com - Errors from the virtual keyboard extension - - - - shend@chromium.org - essential-inputs-team@google.com - - Whether an input field was focused by a stylus or not. Recorded when an - input field is focused. - - - - - shend@chromium.org - essential-inputs-team@google.com - Text input events related to gesture typing. - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - What kind of commit method was used when text was committed to an input from - the handwriting input method in the virtual keyboard. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - What type of container was the virtual keyboard in when text was committed - from the handwriting input method. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - How wide was the keyboard container when text was committed from the - handwriting input method. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The on-screen keyboard initialization latency in milliseconds. - - - - - jopalmer@chromium.org - essential-inputs-team@google.com - - Time to show the on-screen keyboard in milliseconds. Similar to - InputMethod.VirtualKeyboard.KeyboardShown but with a larger maximum to - capture more of the distribution. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The layout of the on-screen keyboard. Logged when the specific layout is - shown. - - - - - dvallet@google.com - essential-inputs-team@google.com - - The count of layout switching actions while virtual keyboard is alive. - Recorded when the virtual keyboard window is hidden or destroyed. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that counts the number of times the cursor was moved to - the next word by swiping forward on the selection track. The count is - initialized when the user starts swiping from any side of the virtual - keyboard, incremented based on how far they swipe forwards on the selection - track, and recorded when they release their finger. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The layout of the virtual keyboard that is shown when the user focuses on an - input field with a stylus. Recorded when the layout is shown after a focus. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - The width of the virtual keyboard window, in pixels, when the floating - keyboard is initialized. This is recorded only once on startup, when the - virtual keyboard is initialized in floating mode. - - - - - curtismcmullan@chromium.org - essential-inputs-team@google.com - - The width of the virtual keyboard window, in pixels, after a user has - completed resizing the virtual keyboard. This is recorded when the user - lifts their finger at the end of a drag that initiates a resize. - - - - - keithlee@google.com - essential-inputs-team@google.com - The duration in seconds of a typing session. - - - - shend@chromium.org - essential-inputs-team@google.com - - The count of user actions to switch keyboard mode (floating, docked). - Recorded when the user clicks in the docked/floating keyboard menu option. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The number of times the virtual keyboard was tapped while the virtual - keyboard was alive. Recorded when the virtual keyboard is closed. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that tracks the total number of words that were deleted - by swiping forward on the deletion track. The count is initialized when the - user starts swiping on the backspace key, incremented based on how far they - swipe forwards on the deletion track, and recorded when they release their - finger. - - - - - shend@chromium.org - essential-inputs-team@google.com - - The number of words typed per minute. Recorded when the virtual keyboard is - closed. - - - - - shend@chromium.org - essential-inputs-team@google.com - - Chrome OS histogram that tracks the total number of words that were restored - by swiping backwards on the deletion track. The count is initialized when - the user starts swiping on the backspace key, incremented based on how far - they swipe backwards on the deletion track, and recorded when they release - their finger. - - - - - zeuthen@chromium.org - - The number of update attempts until the update has been applied. This is - reported every time the device has completed an update. - - - - - zeuthen@chromium.org - Errors from update_engine process when running in dev mode. - - - - zeuthen@chromium.org - - The overhead in downloading extra bytes due to errors/interruptions. - Expressed as a percentage of the bytes that are actually needed to be - downloaded for the update to be successful. - - - - - zeuthen@chromium.org - - The combinations of protocol and source server that were used to complete a - successful update. - - - - - zeuthen@chromium.org - - The number of update attempts with a full update payload until the update - has been applied. This is reported on every update attempt. - - - - - zeuthen@chromium.org - - The source used to provision the install-date-days value sent to Omaha with - every request. This is reported when OOBE completes (M34 or later) or when - upgrading to a version with install-date-days support. - - - - - zeuthen@chromium.org - - Errors from update_engine process when running in normal mode. - - - - - zeuthen@chromium.org - - The age of the OS, defined as the age of the /etc/lsb-release file. This is - reported on every update check but at most once a day. - - - - - zeuthen@chromium.org - - The number of update attempts until the update has been applied. This is - reported on every update attempt. - - - - - zeuthen@chromium.org - - The type of update payload used to update the device. The difference between - "Full" and "Forced Full" is that in the latter, the - request sent to Omaha included a directive saying that a delta payload - wasn't accepted. A "Full" payload is one where a delta payload was - accepted but Omaha provided a full payload. This is reported every time the - device has completed an update. - - - - - zeuthen@chromium.org - - The number of times a Chrome OS device has been powerwashed (factory reset) - without subsequently going through recovery and/or changing the dev mode - switch. Reported once after each powerwash. - - - - - zeuthen@chromium.org - - The number of consecutive times a device has failed to boot an update that - successfully applied. This metric is reported every time the firmware fails - to boot the slot with the update and fell back to the slot it originally - updated from. - - - - - - Superseded by Installer.Recovery.Reason in 8/2017. - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of times the device has been recovered. - - This is reported on reboot after a successful recovery. Cleared only when - switching to dev mode or on factory reset. - - This metric is specific to Chrome OS. - - - - - kimjae@chromium.org - chromeos-core-services@google.com - - The reason for entering recovery mode immediately prior to a recovery. - - This is reported on reboot after a successful recovery. - - This metric is specific to Chrome OS. - - - - - zeuthen@chromium.org - - Number of MBs downloaded from during an update that completed successfully. - - - - - zeuthen@chromium.org - - Wall-clock duration between when an update has successfully completed (and - the user is presented with the "reboot arrow") and when the system - has booted into the new update. This is reported every time the device is - rebooted after an update has been applied. - - - - - zeuthen@chromium.org - - Total number of MBs downloaded since the last successful update. This also - includes all the bytes downloaded during any prior failed attempts. - - - - - zeuthen@chromium.org - - Absolute wall-clock time duration it took for the update to complete from - the time an update first began. It includes not just the time the device was - up, but also includes the time the device spent sleeping. - - - - - zeuthen@chromium.org - - Uptime duration it took for the update to complete from the time an update - first began. It does not include the time the device spent sleeping, but it - does include the uptime spent in waiting for the hourly update checks to - happen. - - - - - zeuthen@chromium.org - - Number of times the device was rebooted by the user since an update began - and until it completed successfully. - - - - - zeuthen@chromium.org - - The number of update attempts that didn't complete because a newer update - was detected during the update operation. This is reported every time the - device has completed an update. - - - - - zeuthen@chromium.org - - The number of consecutive different abandoned update payloads since the last - successful update. This is reported every time an update payload is - abandoned because a newer update payload is available. - - - - - zeuthen@chromium.org - - The time in seconds it took to update a Chrome OS system -- from completing - an update check to reboot pending. - - - - - zeuthen@chromium.org - - Number of times the download URLs were switched due to failures. - - - - - - Removed 4/2015. It appears the code at some point changed to use the - histogram name 'ExtensionInstallSigner.InvalidCount' and we forgot to update - this histogram name. - - Please list the metric's owners. Add more owner tags as needed. - - This is a count of the number of ids that we asked to be signed which the - server response indicated were not in the webstore. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallSigner.ResultWasValid. - - Please list the metric's owners. Add more owner tags as needed. - - The extensions install signer got a well-formed result from the server but - the signature check on it failed. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.GetSignatureResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier tried to get a new signature and received a - response but it wasn't properly signed. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.GetSignatureResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier tried to get a new signature but was unable - to (network error contacting the server, response from server was malformed, - etc.). - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.GetSignatureResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier got a new signature from the server that was - valid. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.InitResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier found a valid signature at startup, and this - is a count of the number of signed ids it contained. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.InitResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier found a signature in the prefs at startup, - and it parsed properly, but it was invalid (some ids may have been - added/removed, could not verify it was signed with the correct private key, - etc.). - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.InitResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier did not find any signature in the prefs at - startup. - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.InitResult. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier found a signature in the prefs at startup, - but it wasn't parseable (missing/wrong format of required keys, etc.). - - - - - - Removed 1/2014 (crbug.com/333934). Replaced by - ExtensionInstallVerifier.MustRemainDisabled. - - Please list the metric's owners. Add more owner tags as needed. - - The extension install verifier would have disabled an extension but is not - in enforcement mode. - - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Length of time taken to complete the DeleteToken request successfully. If - the request is retried multiple times, the length of time is counted for the - last successful retry. - - - - - peter@chromium.org - Status code of the outcome of DeleteToken request. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of retries before DeleteToken succeeds. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - - Whether the Instance ID API is enabled. Checked when a chrome.instanceID - function is called. - - - - - - Removed in 2020-06. - - tschumann@chromium.org - treib@chromium.org - - Counts the events when the GCM integration generates and registers a new - instance ID with FCM. This histogram acts as a pure counter and only emits - 'true' values. The goal of the histogram is to detect potential instance ID - leaks. It's best interpreted in relation to the reported number of - syncing/sync-transport users. - - - - - jianli@chromium.org - - Length of time taken to complete the GetToken request successfully. If the - request is retried multiple times, the length of time is counted for the - last successful retry. - - - - - peter@chromium.org - platform-capabilities@chromium.org - - Net error code from an Instance ID GetToken attempt. Recorded when URL - loading completes. - - - - - peter@chromium.org - - The number of options provided to the GetToken request. Recorded when the - request has been received by the InstanceID instance. - - - - - peter@chromium.org - Status code of the outcome of GetToken request. - - - - - Removed 7/2019. No longer used. - - jianli@chromium.org - Number of retries before GetToken succeeds. - - - - peter@chromium.org - - Number of Instance IDs restored from the persistent store at startup. - - - - - peter@chromium.org - - Number of InstanceID tokens restored from the persistent store at startup. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Records various events of interest in the InstantController. E.g. When URLs - are blacklisted. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How often an Instant preview is committed onto a different tab than it was - created from. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time between the first Omnibox interaction and when the Instant preview - shows. If the instant preview was already showing when the user interacted - with the omnibox, this histogram is not recorded. - - - - - - Removed as of 07/2019, see crbug.com/975798. - - kmilka@chromium.org - ramyan@chromium.org - - Records a histogram for how often the Cacheable NTP fails to load. - - - - - - Depcreated as of 10/2013. No longer relevant since the HTML overlay was - abandoned. - - Please list the metric's owners. Add more owner tags as needed. - - Records the cause for falling back to a local overlay at the time of - fallback. - - - - - - Removed as of 10/2013. This histogram is no longer relevant since the HTML - overlay went away. - - Please list the metric's owners. Add more owner tags as needed. - - Records a histogram for instant extended (Local NTP and Online NTP) and - non-extended navigations. - - - - - - Removed as of 11/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Records, on startup, whether the user has chosen to opt-in to or opt-out of - InstantExtended via chrome://flags. - - - - - - Removed 2013-06. As of m30 use InstantExtended.NewOptInState. - - Please list the metric's owners. Add more owner tags as needed. - - Records, on startup, whether the user has chosen to opt-in to or opt-out of - InstantExtended via chrome://flags. - - - - - - Removed 2013-07. Please see InstantExtended.PercentageMatchV2_QuerytoQuery - instead. - - Please list the metric's owners. Add more owner tags as needed. - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a search query to another search query. - - - - - - Removed 2013-07. Please see InstantExtended.PercentageMatchV2_QuerytoURL - instead. - - Please list the metric's owners. Add more owner tags as needed. - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a search query to a url. Example: Accidental search for - google.con, then navigation to google.com. - - - - - - Removed 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoQuery - instead. - - Please list the metric's owners. Add more owner tags as needed. - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a url to a search query. - - - - - - Removed 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoURL - instead. - - Please list the metric's owners. Add more owner tags as needed. - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a url to another url. - - - - - - Removed in August 2016 with the removal of query in the omnibox code. - - mpearson@chromium.org - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a search query to another search query. - - - - - - Removed in August 2016 with the removal of query in the omnibox code. - - mpearson@chromium.org - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a search query to a url. Example: Accidental search for - google.con, then navigation to google.com. - - - - - - Removed in September 2016 because (i) this measurement was somewhat wrong, - (ii) it's difficult to understand the data, and (iii) there are better ways - to answer the same question. The measurement is somewhat wrong because - reloads, link drops, and pasting URLs and pressing enter are all incorrectly - logged to the URLtoQuery histogram, not the URLtoURL histogram. Futhermore, - this histogram is difficult to analyze because it's not broken up by input - length. Short URLs can by random chance have a sizable percentage match with - a query. Finally, there are better source for data like this; ask mpearson - for details. - - mpearson@chromium.org - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a url to a search query. - - - - - - Removed in September 2016 because (i) this measurement was somewhat wrong, - and (ii) there are better ways to answer the same question. The measurement - is somewhat wrong because reloads, link drops, and pasting URLs and pressing - enter are all incorrectly logged to the URLtoQuery histogram, not the - URLtoURL histogram. Furthermore, there are better source for data like this; - ask mpearson for details. - - mpearson@chromium.org - - Records the number of matching characters at the start of the user's text as - a percentage of average length between the old and new text when the user - navigates from a url to another url. - - - - - - Removed 2013-06. This preference has not been exposed or used for months, - and we do not plan to use it in the future. - - Please list the metric's owners. Add more owner tags as needed. - - Records, on startup, the value of the "Allow your search engine to - provide Instant result" preference setting for the first profile - loaded. - - - - - - Removed as of 7/2015. - - ksimbili@chromium.org - - Records the scroll state on the preview page when instant search clicks - feature is triggered. - - - - - - Removed as of 7/2015. - - ksimbili@chromium.org - - Records the reason that triggered the page swap when instant search clicks - feature is triggered. - - - - - - Removed as of 7/2015. - - ksimbili@chromium.org - - The time spent by the user in preview page before swapping to original or - navigating out of preview page. - - - - - - Removed as of 7/2015. - - ksimbili@chromium.org - - The time it took for swap to trigger for all swaps. The is the time between - preview page load start to preview page swap with the original page. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a breakdown of how many times each possible Bluetooth advertisement - registration result occurs. - - The bucket "Unknown result" indicates that the Bluetooth platform - returned an unknown error code; if it has any counts, the client code should - be changed to account for the new error code. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a breakdown of how many times each possible Bluetooth advertisement - unregistration result occurs. - - The bucket "Unknown result" indicates that the Bluetooth platform - returned an unknown error code; if it has any counts, the client code should - be changed to account for the new error code. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides the success rate of starting a Bluetooth discovery session. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides the success rate of stopping a Bluetooth discovery session. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a top-level breakdown of the times a connection to a host has - failed. - - An "unknown error" is caused by the host returning an - "unknown error" response code. Tethering timing out and client - connection error are both broken down further in - InstantTethering.ConnectionToHostResult.Failure.TetheringTimeout and - InstantTethering.ConnectionToHostResult.Failure.ClientConnection, - respectively. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Breaks down the reasons why the client failed to connect to the hotspot, and - the number of times they occurred. - - Note that a client connection can be canceled by a user either via pressing - the Disconnect button or beginning a connection attempt to another host. The - "internal error" case is a general bucket that captures client - errors we don't expect to be significant failure causes. - - This histogram breaks down the "client connection error" count of - InstantTethering.ConnectionToHostResult.Failure. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Captures the number of times of whether or not first-time setup was required - when tethering timed out. - - Starting tethering on the host works like so: if first-time setup is - required on the host, a first-time setup UI is shown on the host; once the - user interacts with it, the provisioning app is called. If first-time setup - is not required, then the provisioning app is directly called. To be clear: - the provisioning app is always run. - - There are two possible ways for tethering to time out: either the - provisioning app flaked (crashed or hung, and never called back to Instant - Tethering), or the user never interacted with the first-time setup UI flow - (assuming first-time setup was required). - - Because it's very unlikely for the provisioning app to flake, we can read - the "was first-time setup" count as almost always indicative of - the user not interacting with the first-time setup UI. We expect the - "was not first-time setup" count to be low (because, as mentioned, - it's very unlikely for the provisioning app to flake). - - This histogram breaks down the "tethering timed out" count of - InstantTethering.ConnectionToHostResult.Failure. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a breakdown of the times a connection to a host was either - unsuccessful due to provisioning failure (the carrier disallows tethering) - or "other" (this is captured under - InstantTethering.ConnectionToHostResult.SuccessRate.Background). - - This metric captures the rough percentage of connections which are - unsuccessful due to provisioning failure. It is separate from - InstantTethering.ConnectionToHostResult.SuccessRate.Background and the - metrics related to it because provisioning failure is neither truly a - success nor an error. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - Captures the count of successful and failed connection attempts. - - This metric counts the top-level user action from beginning to connect, all - the way through success or failure of the connection (excluding any - programmatic retries within the connection attempt). - - This metric provides an immediate understanding of the Instant Tethering - connection success rate. The counts of failure are broken down in - InstantTethering.ConnectionToHostResult.Failure. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Captures the count of successful and failed connection attempts. - - This metric counts the top-level user action from beginning to connect, all - the way through success or failure of the connection (excluding any - programmatic retries within the connection attempt). - - This metric provides an immediate understanding of the Instant Tethering - connection success rate. The counts of failure are broken down in - InstantTethering.ConnectionToHostResult.Failure. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Breaks down the state of Instant Tethering during user sessions. All states, - except for 'Enabled', indicate that the feature was not active. This - histogram is emitted to each time a condition affecting Instant Tethering's - state, e.g. the user enabling or disabling the feature, or Bluetooth - becoming enabled or disabled. - - Note: The "Screen locked" bucket is obsolete, and should not have - any reports. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - Captures the effective count of successful and failed GATT connection - attempts, including retries. This means that if a GATT connection attempt - fails but then succeeds on a future retry, this is counted as a single - success. In the context of this metric, a failure represents a GATT failure - in all retry attempts. - - An individual attempt is considered successful if a GATT connection was - created and authenticated successfully (i.e., the connection was ready for - Instant Tethering to exchange protocol messages). - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - Captures the effective count of successful and failed GATT connection - attempts, including retries. This means that if a GATT connection attempt - fails but then succeeds on a future retry, this is counted as a single - success. In the context of this metric, a failure represents a GATT failure - in all retry attempts. - - An individual attempt is considered successful if a GATT connection was - created and authenticated successfully (i.e., the connection was ready for - Instant Tethering to exchange protocol messages). - - This metric is the background advertisement analog of - InstantTethering.GattConnectionAttempt.EffectiveSuccessRateWithRetries. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - Captures the count of successful and failed GATT connection attempts. - - An attempt is considered successful if a GATT connection was created and - authenticated successfully (i.e., the connection was ready for Instant - Tethering to exchange protocol messages). - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - Captures the count of successful and failed GATT connection attempts. - - An attempt is considered successful if a GATT connection was created and - authenticated successfully (i.e., the connection was ready for Instant - Tethering to exchange protocol messages). - - This metric is the background advertisement analog of - InstantTethering.GattConnectionAttempt.SuccessRate. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of a batch of host scans. A batch is defined as a series of one - or host scans separated by no more than one minute. - - For example, if a scan occurs then stops and does not start back up again, - the metric logged would be the amount of time taken for that scan. However, - if a scan finishes and a new scan starts up again less than a minute after - the previous scan finished, the metric logged would be the time difference - between the start of the first scan and the finish of the second scan. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a breakdown of the results of each host scan. This metric is - recorded after each host scan. - - Comparing the number of times no hosts were found against the other buckets - can help determine how often a host scan is useful. - - The sum of the buckets capturing that a notification was shown can be used - as a baseline of comparison against - InstantTethering.ConnectionToHostResult.ProvisioningFailureRate to roughly - measure engagement with the notification. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between the start and end of a Tether connection. - Timing starts when the device connects to the Wi-Fi hotspot and ends when - the device becomes disconnected from the Wi-Fi hotspot. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Captures the count of successful and failed attempts to send a - 'KeepAliveTickle' message to the phone. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Indicates the feature state of the Instant Tethering feature. This metric is - emitted to at the creation of the user session (when the user logs in), and - when feature state updates occur. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Counts the number of interactions a user has with each of the Instant - Tethering notifications. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client begins to scan and advertise, and - connects to a host (before authentication). - - This histogram only considers the time from when the client *sends* an - advertisement, and not when the client *receives* an advertisement. See - InstantTethering.Performance.StartScanToReceiveAdvertisementDuration and - InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration for - histograms that consider when the client receives an advertisement. - - This histogram is the foreground advertisement analog of - InstantTethering.Performance.StartScanToConnectionDuration.Background. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client connects to a host, and - authenticates with that host. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client connects to a host, and - authenticates with that host. - - This histogram is the background advertisement analog of - InstantTethering.Performance.ConnectionToAuthenticationDuration. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when a client authenticates with a host, and - receives a ConnectTetheringResponse. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time it takes for the client to connect to the host, from - the moment the user taps 'Connect', until the client connects to the host's - hotspot. This does not include timeouts. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time it takes for the client to connect to the host, from - the moment the user taps 'Connect', until the client connects to the host's - hotspot. This does not include timeouts. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time it takes for the client to connect to the provided - hotspot after receiving a ConnectTetheringResponse. This does not include - timeouts. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time it takes for the client to send off a - DisconnectTetheringRequest. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when a client authenticates with a host, and - receives a KeepAliveTickleResponse. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client received a foreground - advertisement from a host, and connected to that host (before - authentication). - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client received a background - advertisement from a host, and connected to that host (before - authentication). - - This histogram is the background advertisement analog of - InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client begins to scan, and connects to a - host (before authentication). - - This histogram is the background advertisement analog of - InstantTethering.Performance.AdvertisementToConnectionDuration. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client begins to scan and advertise, and - receives a foreground advertisement from a host. - - - - - - Removed 2019/02 in favor of MultiDevice.* equivalent. - - hansberry@chromium.org - - The duration of time between when a client begins to scan, and receives a - background advertisement from a host. - - This histogram is the background advertisement analog of - InstantTethering.Performance.AdvertisementToConnectionDuration. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when a client authenticates with a host, and - receives a TetherAvailabilityResponse. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides a breakdown of how each Tether session ended. A session begins when - a device is first connected to a host's hotspot, and ends when the device is - no longer connected to the hotspot. This metric is recorded at the end of - each session. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides the count of the number of users who have the Instant Tethering - toggle enabled vs. disabled on startup. This metric is logged each time a - user logs into a Chromebook. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Provides the count of the number of times users have enabled or disabled the - user preference for Mobile data. This metric is logged each time the value - is toggled. - - - - - - Removed on 8/1/13. - - felt@chromium.org - - The time between the SSL interstitial display and the user decision, which - may be either accept or deny. This is only recorded for overridable SSL - warnings with a CERT_AUTHORITY_INVALID warning. Timing begins when user - first focuses on the page. - - - - - meacer@chromium.org - - User action when the user is shown a captive portal error page. - - - - - - Removed on 8/1/13. - - felt@chromium.org - - The time between the SSL interstitial display and the user decision, which - may be either accept or deny. This is only recorded for overridable SSL - warnings with a CERT_COMMON_NAME_INVALID warning. Timing begins when user - first focuses on the page. - - - - - - Removed on 8/1/13. - - felt@chromium.org - - The time between the SSL interstitial display and the user decision, which - may be either accept or deny. This is only recorded for overridable SSL - warnings with a CERT_DATE_INVALID warning. Timing begins when user first - focuses on the page. - - - - - estark@chromium.org - carlosil@chromium.org - - User decision when presented with a security interstitial. As of M44, - subresource interstitials were split into their own entries. As of M52, - social_engineering_ads* and social_engineering_landing* interstitial reasons - are split into their own entries from phishing*. - - - - - felt@chromium.org - carlosil@chromium.org - - User decision when presented with a security interstitial, on a site that - the user had previously visited. As of M44, subresource interstitials were - split into their own entries. As of M52, social_engineering_ads* and - social_engineering_landing* interstitial reasons are split into their own - entries from phishing*. - - - - - estark@chromium.org - carlosil@chromium.org - - User interactions with a security interstitial. As of M44, subresource - interstitials were split into their own entries. As of M52, - social_engineering_ads* and social_engineering_landing* interstitial reasons - are split into their own entries from phishing*. - - - - - - Replaced by interstitial.ssl_overridable.* and - interstitial.ssl_nonoverridable.* in Jan 2015 (M42). - - felt@chromium.org - - User action when the user is shown a SSL interstitial. SHOW_ALL and MORE - refer to the total number of SSL errors; all of the other numbers pertain to - the number of actions related to SSL errors that are overridable. The counts - do not sum to 100%; SHOW_ALL is a superset of SHOW_OVERRIDABLE, which in - turn will be a supserset of the PROCEED/DONT_PROCEED variables. - SHOW_UNDERSTAND is only being used by an experimental field trial. The - interstitials due to captive portals are now recorded in the - "SSLCaptivePortal". - - - - - meacer@chromium.org - - Record possible states of captive portals. This histogram is emitted - (possibly multiple times to different buckets) whenever a ssl interstitial - page is displayed and captive portal detection is enabled. The captive - portal technique forces a client on a network to see a special web page - (usually for authentication purposes) before using the internet normally. - - - - - estark@chromium.org - carlosil@chromium.org - - Possible non-attack causes of the non-overridable SSL interstitial. Many - errors are not reported in this histogram and new errors may be added over - time, therefore one should not look at the breakdown of this histogram (one - bucket divided by the sum) because that will be inaccurate. Instead, one - should look at each bucket count divided by the count of the ssl errors of - that type. E.g. WWW mismatch is recorded only when the ssl error is - CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW - mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the - histogram interstitial.ssl_error_type. - - - - - estark@chromium.org - carlosil@chromium.org - - Possible non-attack causes of the overridable SSL interstitial. Many errors - are not reported in this histogram and new errors may be added over time, - therefore one should not look at the breakdown of this histogram (one bucket - divided by the sum) because that will be inaccurate. Instead, one should - look at each bucket count divided by the count of the ssl errors of that - type. E.g. WWW mismatch is recorded only when the ssl error is - CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW - mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the - histogram interstitial.ssl_error_type. - - - - - mab@chromium.org - - State of the system clock, as inferred from the build timestamp, when an SSL - CERT_INVALID_DATE error is seen. - - - - - - Removed August 2016. Replaced with interstitial.ssl.clockstate.network2, - which records reasons why network time might be unavailable. - - mab@chromium.org - - State of the system clock, relative to network time, when an SSL - CERT_INVALID_DATE error is seen. - - - - - - Removed October 2016. Due to a bug, data in this histogram is mislabelled - and should be disregarded. Replaced with - interstitial.ssl.clockstate.network3. - - estark@chromium.org - mab@chromium.org - - State of the system clock, relative to network time, when an SSL - CERT_INVALID_DATE error is seen. - - - - - estark@chromium.org - mab@chromium.org - - State of the system clock, relative to network time, when an SSL - CERT_INVALID_DATE error is seen. - - - - - felt@chromium.org - carlosil@chromium.org - - The histogram shows the connection types associated with SSL warnings. E.g., - do more warnings occur on WiFi? - - - - - - Removed September 13 2017. - - jww@chromium.org - - Specifies when a user enters the page info menu whether or not the user - pressed the SSL decisions revoke button. This can only by done if the user - is in the "Remember Certificate Error Decisions" experiment. This - is logged when the page info UI is closed. Replaced by - .did_user_revoke_decisions2 to keep data separate after changing - functionality to only log when button was visible. - - - - - carlosil@chromium.org - - Specifies when a user enters the page info menu whether or not the user - pressed the SSL decisions revoke button. This is logged when the page info - UI is closed, only if the button was visible in the page info. - - - - - - Removed Dec 2017 (M65). - - jww@chromium.org - - Records when a user has made a decision to proceed on a nonoverridable SSL - interstitial. Also records whether a prior decision had been made but the - decision expired. - - - - - - Removed Dec 2017 (M65). - - jww@chromium.org - - Records when a user has made a decision to proceed on an overridable SSL - interstitial. Also records whether a prior decision had been made but the - decision expired. - - - - - - Removed Nov 2017 (M64). - - jww@chromium.org - - Emitted when a good certificate is seen, specifying whether the user already - gave an exception for a bad certificate for the same host. - - - - - - Removed December 2017 (M65). - - jam@chromium.org - - Whether the resource type for a request that succeeded with a good cert and - revoked a certificate exception is for a frame (as opposed to subresource). - - - - - - Removed Jan 2015 (M42). - - felt@chromium.org - - The likelihood of a |CERT_AUTHORITY_INVALID| error being an attack. - - - - - - Removed Jan 2015 (M42). - - felt@chromium.org - - The likelihood of a |CERT_COMMON_NAME_INVALID| error being an attack. - - - - - - Removed Jan 2015 (M42). - - felt@chromium.org - - The likelihood of a |CERT_DATE_INVALID| error being an attack. - - - - - carlosil@chromium.org - - Records when a user visits a site after clicking through a certificate - warning. - - - - - - Removed on 8/1/13. - - felt@chromium.org - - The time between the SSL interstitial display and the user decision, when - the user accepts the SSL warning. This is only recorded for overridable SSL - warnings. Timing begins when user first focuses on the page. - - - - - meacer@chromium.org - carlosil@chromium.org - estark@chromium.org - The type of action that the SSL error handler takes. - - - - estark@chromium.org - - When handling a certificate date error, Chrome (under certain Variations - Service experiments) will delay displaying the warning interstitial for up - to 3 seconds while querying a network time service. This histogram records - the amount of time for which the interstitial was delayed on this check. The - histogram is recorded even when a time query is not sent (for example, - because Chrome already had an up-to-date network timestamp that it could - use, or because the client is not in the experimental group that enables - network time queries). - - - - - - Removed 2018-11. - - estark@chromium.org - - When encountering a certificate error, Chrome looks for the well-known - Superfish certificate in the certificate chain and records this histogram as - true if the Superfish certificate is present and false otherwise. The - Superfish certificate is an indication that the user is vulnerable to - man-in-the-middle attacks because of software installed on their computer. - - - - - estark@chromium.org - carlosil@chromium.org - - The type of SSL error that the user encounters. This is recorded for all SSL - warnings, regardless of whether they are overridable. - - - - - estark@chromium.org - - Recorded when a non-overridable SSL interstitial is shown. The value is true - if the user has seen the same error multiple times (in which case a special - message is added to the interstitial). - - - - - estark@chromium.org - - Recorded when a non-overridable SSL interstitial is shown for a Certificate - Transparency error. The value is true if the user has seen the same error - multiple times (in which case a special message is added to the - interstitial). - - - - - estark@chromium.org - - Recorded when an overridable SSL interstitial is shown. The value is true if - the user has seen the same error multiple times (in which case a special - message is added to the interstitial). - - - - - estark@chromium.org - - Recorded when an overridable SSL interstitial is shown for a Certificate - Transparency error. The value is true if the user has seen the same error - multiple times (in which case a special message is added to the - interstitial). - - - - - estark@chromium.org - - Recorded whenever the user sees or proceeds through an SSL interstitial for - an error that the user has seen multiple times (in which case a special - message is added to the interstitial). - - - - - estark@chromium.org - - Recorded whenever the user sees or proceeds through an SSL interstitial for - a Certificate Transparency error that the user has seen multiple times (in - which case a special message is added to the interstitial). - - - - - - Removed on 8/1/13. - - felt@chromium.org - - The time between the SSL interstitial display and the user decision, when - the user rejects the SSL warning. This is only recorded for overridable SSL - warnings. Timing begins when user first focuses on the page. - - - - - nyquist@chromium.org - khushalsagar@chromium.org - melandory@chromium.org - - Status of sending outgoing invalidation message through GCM upsteam. - - - - - - Histogram for the deprecated implementation. - - pavely@chromium.org - melandory@chromium.org - Network channel used for invalidations. - - - - melandory@chromium.org - - Status of the invalidation component. The metric is recorded on startup - unless invalidations are disabled, plus when the state changes. - - - - - - Removed 2018-01. As of M65 use Mobile.CanonicalURLResult. - - gchatz@chromium.org - - The result of the operation to retrieve the page's canonical URL. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - When a navigation is committed, it should have a non-null NavigationContext. - This histogram counts the frequency of this invariant holding at the time - when a new navigation is committed. It is used to verify the effectiveness - of code fixes because this issue is not currently reproducible in testing - (http://crbug.com/864769). True means a non-null NavigationContext is - present. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - When a navigation is committed, the web view URL is expected to match that - of the current back-forward item. WKWebView seems to break this assumption - at times. This histogram counts the frequency of this invariant violation at - the time when a new navigation is committed. True means the URL matches the - current back-forward item. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The number of times the Content Extension was displayed since last Chrome - foregrounding. Reported when Chrome is put in foregrounded. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The index of the URL selected by the user in the Content Extension. - - - - - rkgibson@google.com - gambard@chromium.org - - When the content rule list provider updates its lists, this can succeed or - fail. Failure occurs when the rule lists are updated again before the first - update finishes. - - - - - mrefaat@chromium.org - bling-team@google.com - - Recorded to indicate whether the GetCookiesForURL call found cookies or not - when called on a specific system cookie store implementation. Most of the - cookies fetching on iOS Chromium is done by the WKWebView and doesn't - involve calling GetCookiesForURL. The method is only called when a request - is made by the UrlRequestFetcher for cases that are not handled by WKWebView - (eg. Downloads, Auto Suggestions and NTP tiles). - - - - - mrefaat@chromium.org - bling-team@google.com - - The system cookie store type used when GetCookiesForURL method is called. - Most of the cookies fetching on iOS Chromium is done by the WKWebView and - doesn't involve calling GetCookiesForURL. The method is only called when a - request is made by the UrlRequestFetcher for cases that are not handled by - WKWebView (eg. Downloads, Auto Suggestions and NTP tiles). - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user copied a Password since - last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user copied a URL since last - Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user copied a Username since - last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension was displayed since last Chrome - foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension password util failed to look up - for a password since last Chrome foregrounding. Reported when Chrome is put - in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension pasword util was queried with a - nil argument since last Chrome foregrounding. Reported when Chrome is put in - foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user selected for a Password - since last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension selected a Password without - user intervention since last Chrome foregrounding. Reported when Chrome is - put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension needed user reauthentication - since last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user searched for a Password - since last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - djean@chromium.org - - Recorded when a request to replace identities in ASCredentialIdentityStore - fails. - - - - - javierrobles@chromium.org - djean@chromium.org - - The number of times the Credential Extension user unobfuscated a Password - since last Chrome foregrounding. Reported when Chrome is put in foreground. - - - - - justincohen@chromium.org - eugenebut@chromium.org - - Recorded when app is running in the background and posted a background task. - This time is obtained by calling UIApplication.backgroundTimeRemaining. When - backgroundTimeRemaining reaches 0 and there is at least one running - background task, then iOS terminates the app instead of suspending it. The - lower recorded value is, the higher chances that posted task will keep - running when backgroundTimeRemaining reaches 0, causing the app termination. - When app is relaunched after termination the app starts cold which is slower - and does not fully restore the prior UI state, so terminations are worse - than suspensions. - - - - - justincohen@chromium.org - gambard@chromium.org - - Workaround for a WKWebView bug where WKNavigations can leak, leaving a - permanent pending URL, thus breaking the omnibox. While it is possible for - navigations to finish out-of-order, it's an edge case that should be handled - gracefully, as last committed will appear in the omnibox instead of the - pending URL. This metric records whether there are old navigations to clean - up each time a navigation finishes. See crbug.com/1010765 for details. - - - - - thegreenfrog@chromium.org - rohitrao@chromium.org - - The action taken by the user in response to the default browser promo. - - - - - kkhorimoto@chromium.org - michaeldo@chromium.org - Tracks the way JavaScript dialogs are closed on iOS. - - - - jif@chromium.org - - The type of content that the user is dragging into Chrome. Because a drag - can contain multiple types of objects, multiple DragContent values may be - recorded for a single drag event. - - - - - edchin@chromium.org - justincohen@chromium.org - - Tracks the result of snapshotting when the user enters the tab switcher. - Recorded whenever the user enters the tab switcher. - - - - - danyao@chromium.org - - When a navigation is finished, it should have a non-null NavigationContext. - This histogram counts the frequency of this invariant holding at the time - when a new navigation is finished. It is used to verify the effectiveness of - code fixes because this issue is not currently reproducible in testing - (http://crbug.com/864769). True means a non-null NavigationContext is - present. - - - - - danyao@chromium.org - - When a navigation is finished, it should have a non-null NavigationItem. - This histogram counts the frequency of this invariant holding at the time - when a new navigation is finished. It is used to verify the effectiveness of - code fixes because this issue is not currently reproducible in testing - (http://crbug.com/864769). True means a non-null NavigationItem is present. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - When a navigation is finished, the web view URL is expected to match that of - the current back-forward item. WKWebView seems to break this assumption at - times. This histogram counts the frequency of this invariant violation at - the time when a new navigation is finished. True means the URL matches the - current back-forward item. - - - - - javierrobles@chromium.org - eugenebut@chromium.org - - Reports exceptions when trying to send a form input accessory action to the - virtual keyboard. - - - - - erikchen@chromium.org - - This event is recorded each time a Handoff is received by Chrome on iOS. The - enumeration indicates the source of the Handoff. - - - - - - Removed 09/2020. - - eugenebut@chromium.org - michaeldo@chromium.org - - Recorded when the iOS JavaScript Console logging is manually enabled or - manually disabled. - - - - - pkl@chromium.org - - Tracks the reason for why the In Product Help bubble was dismissed. - - - - - thegreenfrog@chromium.org - rohitrao@chromium.org - - As of iOS14, users will be able to set a default browser other than Safari. - When Chrome is the default browser, it will receive all URL opens, which is - likely to change certain stability metrics. Thus, it will be good to filter - those metrics by default browser status. This metrics records whether the - user was deemed to have set Chrome as the device's default browser. This - metric will be logged with ever histogram upload. - - - - - rkgibson@google.com - gambard@chromium.org - - IOS Content Blocking uses special injected Javascript to block access to - things like cookies and local storage. Future changes to iOS/WebKit could - cause these blocks to break. This logs that occurrence. - - - - - - Removed 2018-12. - - pkl@chromium.org - - Counts the times when a mailto: URL is tapped by user and whether the URL - has been rewritten for an available native Mail client app or not. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The time during which main thread was not responding. 0 if application was - killed before recovering. Logged after an action posted on the main thread - is not executed immediately. The histogram is sent when the task is finally - executed or on next application startup. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The durations of time in which the app is too busy to handle user - interaction responsively. Logged when a MXMetricPayload is received (one per - day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The amount of time taken to resume the app from the background. Logged when - a MXMetricPayload is received (one per day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The average amount of memory in use by the app when it's suspended. Logged - when a MXMetricPayload is received (one per day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The reason for the application termination in background. Logged when a - MXMetricPayload is received (one per day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The total time the app is in the background. Logged when a MXMetricPayload - is received (one per day). Note: The date the data is reported is later than - the day it account for. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The reason for the application termination in background. Logged when a - MXMetricPayload is received (one per day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The total time the app is in the foreground. Logged when a MXMetricPayload - is received (one per day). Note: The date the data is reported is later than - the day it account for. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The largest amount of memory used by the app. Logged when a MXMetricPayload - is received (one per day). - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The amount of time taken to launch the app. Logged when a MXMetricPayload is - received (one per day). - - - - - marq@chromium.org - djean@chromium.org - - The source of "Open in new Window" user requests. Recorded when a - newly created window is added to a session. - - - - - javierrobles@chromium.org - eugenebut@chromium.org - - NSString API: stringByReplacingCharactersInRange:withString: was invoked - with a nil argument. - - - - - gambard@chromium.org - - The type of NTP impressions on iOS, split by type of suggestions shown - (local vs remote vs remote_collapsed). - - - - - mrefaat@chromium.org - bling-team@google.com - - The result of the download operation done when the user taps "open - in" button to open a file by a different application. - - - - - ewannpv@chromium.org - gambard@chromium.org - bling-team@google.com - - The MIME type of the previwed file when the "Open In" toolbar is - presented. - - - - - danyao@chromium.org - The number of navigation started events by navigation type. - - - - danyao@chromium.org - - The "true" value of this boolean histogram counts the number of - page loading started events. The "false" value will never be seen. - - - - - - Removed 2017-11. - - danyao@chromium.org - - Counts different types of navigation and loading events that are relevant to - counting page loads. - - - - - edchin@chromium.org - justincohen@chromium.org - - Tracks the result of snapshotting when the page has been loaded. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - Measures the time from the end of user input in the omnibox to when the page - is fully loaded. Only measures page loads initiated by user typing a URL or - selecting a suggested entry from the URL bar. - - - - - - Removed 2019-07. - - eugenebut@chromium.org - marq@chromium.org - - Recorded when the user quits the app. True if ChromeBrowserProvider is a - non-null pointer. Chrome for iOS has frequent crashes during shutdown caused - by dereferencing null or dangling ChromeBrowserProvider pointer - (crbug.com/983504). ChromeBrowserProvider can only be null if iOS did not - call application:didFinishLaunchingWithOptions: callback. This metric should - help to understand if ChromeBrowserProvider can even be null after app is - launched. - - - - - javierrobles@chromium.org - bling-team@google.com - - Tracks the results and attempts of reauthentication when using password - Autofill suggestions. - - - - - javierrobles@chromium.org - bling-team@google.com - - Tracks the results and attempts of reauthentication when using a password in - Manual Fallback. - - - - - mrefaat@chromium.org - bling-team@google.com - - The user reaction to the prompt that appears when a website tries to open an - external application repeatedly. - - - - - eugenebut@chromium.org - justincohen@chromium.org - - [iOS] The number of items Navigation Manager was requested to restore. 100 - is logged when the number of navigation items is greater than 100. This is - just a requested count and actual number of restored items can be smaller. - Restoration is triggered in the following cases (the list is not - exhaustive): app cold start, remote tab was open, cookie were cleared, - recently closed tab was restored. - - - - - eugenebut@chromium.org - justincohen@chromium.org - - [iOS] Time spent on restoring committed Navigation Manager's items. Recorded - once per restoration, as a cumulative time across all items. Restoration is - triggered in the following cases (the list is not exhaustive): app cold - start, remote tab was open, cookies were cleared, recently closed tab was - restored. This metric will be used for monitoring session restoration - performance which relies on system's WKWebView. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - The action selected by the user in the Search Extension. - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The number of times the Search Extension was displayed since last Chrome - foregrounding. Reported when Chrome is put in foreground. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The number of items received simultaneously in Chrome from the IOS share - extension. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - Type of the item received from the iOS share extension. - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The delay in milliseconds between the item creation in the extension and its - processing in Chrome. - - - - - javierrobles@chromium.org - olivierrobin@chromium.org - - The source application that sent the external command to Chrome. - - - - - pkl@chromium.org - - The latency in milliseconds between the start of the Share Page operation - and when the UI is ready to be presented. - - - - - - Removed 2019-01. - - edchin@chromium.org - - Tracks the result of snapshotting when the user enters the tab switcher. - Recorded whenever the user enters the tab switcher. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - The Spotlight Action pressed by the user. - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - Tracks the availability of the Spotlight indexation on the device. It is - logged once at each cold start. Note: Spotlight may be available on the - device but disabled by the user. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - Time spent in Spotlight initial indexation of bookmarks. - - - - eugenebut@chromium.org - olivierrobin@chromium.org - Number of bookmarks indexed during initial indexation. - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This event is recorded each time a Chrome Spotlight entry is selected by the - user. The enumeration indicates the nature of the Spotlight entry. - - - - - mrefaat@chromium.org - eugenebut@chromium.org - - The result of StoreKit handling for a specific iTunes URL. Not Handled will - be logged when the LinksHandler didn't handle a specific URL on purpose (not - supported), and Failure will be logged when a URL that should have been - handled wasn't handled. - - - - - mrefaat@chromium.org - bling-team@google.org - - Whether the StoreKit loaded the required iTunes product successfully or not. - - - - - - Removed 2019-04. - - edchin@chromium.org - marq@chromium.org - - WebStateList should be guaranteed to be non-nil during a - WebStateListObserver callback. This histogram counts the frequency of this - invariant holding when webStateList:DidDetachWebState: is invoked in - TabGridMediator. Violations of this invariant is the cause of real-world - crashes (https://crbug.com/877792), which were not currently reproducible in - testing. This histogram is used to retain visibility of the severity of this - issue, while preventing the crashes with a no-op. - - - - - - Removed 2019-04. - - edchin@chromium.org - marq@chromium.org - - WebStateList should be guaranteed to be non-nil during a - WebStateListObserver callback. This histogram counts the frequency of this - invariant holding when GetActiveTabID() is invoked in TabGridMediator. - Violations of this invariant is the cause of real-world crashes - (https://crbug.com/877792), which were not currently reproducible in - testing. This histogram is used to retain visibility of the severity of this - issue, while preventing the crashes with a no-op. - - - - - marq@chromium.org - - The UI interaction by which the user changed the visible page in the tab - switcher. - - - - - gambard@chromium.org - justincohen@chromium.org - - A boolean that is used to indicate that the URL property of the WKWebView - has changed to a nil or empty URL. Recorded on the KVO of the URL of the - WKWebView. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - Measures the number of main frame navigations in slim navigation manager - that are affected by a WKWebView bug that corrupts back/forward history - (http://crbug.com/887497). This is recorded during WKWebView's - decidePolicyForNavigationAction callback. True means the bug is triggered. - False means the bug is not triggered. - - - - - danyao@chromium.org - - WKWebView should notify navigation commit before navigation finish, but - exceptions have been observed. This histogram counts the frequency of this - invariant violation at the time when a new navigation is finished. True - means navigation finish callback happened before navigation commit. - - - - - kkhorimoto@chromium.org - pkl@chromium.org - - Records the user actions related to the WKWebView 3D touch link preview API. - - - - - - Removed 2020-03. - - mrsuyi@chromium.org - eugenebut@chromium.org - - On iOS9, didStartProvisionalNavigation may be called with empty URL. However - in didCommitNavigation the URL will be about:blank. This historgram checks - if this still happens in later iOS versions, and records it when it happens. - - - - - erikchen@chromium.org - - Errors that the privileged attachment broker encounters while trying to - broker attachments. - - - - - erikchen@chromium.org - - Errors that an unprivileged attachment broker encounters while trying to - broker attachments. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the amount of time that the navigation to a previously prefetched - page was delayed because cookies had to be copied from the isolated cookie - jar. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records whether a previously prefetched subresource from an Isolated - Prerender was served from cache when its page was later navigated to. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the response body length as cached in memory encountered when - isolated prefetching a mainframe HTML resource from the Google Search Result - Page. Recorded for non-network error prefetches only. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the time taken to establish a socket connection when isolated - prefetching a mainframe HTML resource from the Google Search Result Page. - Recorded for non-network error prefetches only. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the number of cookies that needed to be copied from the prefetch - navigation to the user's profile after a prefetched link is navigated to. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the Net Error encountered when isolated prefetching a mainframe HTML - resource from the Google Search Result Page. Recorded for every completed - prefetch. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the HTTP response code encountered isolated prefetching a mainframe - HTML resource from the Google Search Result Page. Recorded for non-network - error prefetches only. Redirects are not included here. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the total number of redirects encountered while doing all the - prefetches on an eligible Google Search Result page. Only recorded when at - least one prefetch was attempted. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the total time taken when isolated prefetching a mainframe HTML - resource from the Google Search Result Page. Recorded for successful - non-network error prefetches only. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the net error encountered when prefetching a single subresource - during Isolated Prerenders. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the number of subresources that were NoStatePrefetch'd during an - Isolated Prerender. Recorded once for each page that is NoStatePrefetch'd - during Isolated Prerenders. - - - - - robertogden@chromium.org - ryansturm@chromium.org - tbansal@chromium.org - - Records the HTTP response code encountered when prefetching a single - subresource during Isolated Prerenders. - - - - - - Removed 2020-01. - - avi@chromium.org - - The count of the number of characters in JavaScript dialog messages. - - - - - - Removed 2018-06. - - avi@chromium.org - - The count of the number of characters in JavaScript dialog messages that - were suppressed by the user. Compare with - JSDialogs.CountOfJSDialogMessageCharacters. - - - - - - Removed 2018-06. - - avi@chromium.org - - The count of the number of characters in JavaScript dialog messages. - - - - - - Removed 2018-06. - - avi@chromium.org - - The count of the number of newlines in JavaScript dialog messages. (This - does not count breaks inserted by the UI toolkit in wrapping the messages.) - - - - - - Removed 2016-02. - - avi@chromium.org - - The count of the number of characters in onbeforeunload messages. - - - - - - Removed 2016-02. - - avi@chromium.org - - The count of the number of newlines in onbeforeunload messages. (This does - not count breaks inserted by the UI toolkit in wrapping the messages.) - - - - - - Removed 2020-01. - - avi@chromium.org - The cause of dismissal of JavaScript dialogs. - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between closing a Javascript dialog and opening - another, to track very frequent dialogs. - - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between opening a Javascript dialog and opening - another, to track very frequent dialogs. - - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between opening a Javascript dialog and closing - it, to track very short-lived dialogs. - - - - - - Removed 2020-01. - - avi@chromium.org - - For dialogs, whether or not they were spawned by a tab that was foremost. - - - - - avi@chromium.org - - For onbeforeunload dialogs, the user's choice between staying on the page - and leaving it. - - - - - avi@chromium.org - carlosil@chromium.org - meacer@chromium.org - - For dialogs, the relationship of the origins of the main frame vs the - alerting frame. - - - - - avi@chromium.org - carlosil@chromium.org - meacer@chromium.org - The scheme of the URL showing a JavaScript dialog. - - - - - Removed 2017-10. - - avi@chromium.org - - The site engagement values of sites showing onbeforeunload dialogs. Logged - once per dialog, whether shown or suppressed. - - - - - - Removed 2016-10. Site engagement needed to be measured in small buckets - anyway so it was never high-resolution enough for use. - - avi@chromium.org - - The site engagement values of sites showing dialogs. Logged once per dialog, - whether shown or suppressed. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Time in milliseconds to acquire a Kerberos ticket. The value is recorded no - matter if the operation was successful or not. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Type of the Chrome OS login user (primary user) who requests Kerberos - tickets. Reported at most once a day by the Kerberos daemon when a Kebreros - ticket is acquired or Kerberos files are requested, which happens e.g. on - Chrome startup. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - The Kerberos encryption types used while succesfully creating or refreshing - a Kerberos TGT. This value is derived from the Kerberos configuration - 'enctypes' fields. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of managed Kerberos accounts owned by the current Chrome OS user. A - managed account is an account that got added via the KerberosAccounts - policy. Reported at most once a day similar to Kerberos.DailyActiveUsers. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of Kerberos accounts owned by the current Chrome OS user that use the - 'Remember password' feature, i.e. the account password is stored by the - Kerberos daemon. Reported at most once a day similar to - Kerberos.DailyActiveUsers. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Total number of Kerberos accounts owned by the current Chrome OS user. - Reported at most once a day similar to Kerberos.DailyActiveUsers. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of unmanaged Kerberos accounts owned by the current Chrome OS user. - An unmanaged account is an account that was added manually by the user. - Reported at most once a day similar to Kerberos.DailyActiveUsers. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Number of Kerberos accounts owned by the current Chrome OS user that use the - login password for authentication. These accounts were added via the - KerberosAccounts policy, using the '${PASSWORD}' placeholder as password. - Reported at most once a day similar to Kerberos.DailyActiveUsers. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to acquire a Kerberos ticket. This happens whenever a - new ticket is added or an existing ticket is reauthenticated. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to add a new Kerberos account, either through the - Kerberos Tickets settings page or via the KerberosAccounts policy. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to clear Kerberos accounts, usually through toggling - Kerberos related policies. For instance, disabling the KerberosEnabled - policy clears all accounts. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to retrieve a Kerberos ticket from the Kerberos - daemon. Systems using Kerberos (Chrome, SMB file shares) perform this action - during startup and when they get notified that the files changed. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to list Kerberos accounts, usually through opening - the Kerberos Tickets settings page or making changes to accounts. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to remove a new Kerberos account through the Kerberos - Tickets settings page. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to set Kerberos configuration. This happens right - before acquiring a Kerberos ticket. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Result from an attempt to validate Kerberos configuration. This happens when - the user tries to set configuration in the Advanced section of the dialog to - add new Kerberos tickets. - - - - - fsandrade@chromium.org - tomdobro@chromium.org - - Error code from an attempt validate Kerberos configuration. Contains more - specific information than KerberosErrorType about the result of the - validation. - - - - - - Removed 07/2016 in crbug.com/631204 with KeyboardUmaEventFilter removal. - - girard@chromium.org - - The time between keystrokes in Aura text fields. The only keystrokes that - are measured are ones that produce a printable character and are not over 5 - seconds apart. - - - - - - Removed 2019-07. Search key shortcut analysis is done. - - xiaohuic@chromium.org - zalcorn@chromium.org - - The time between a user pressing the Chrome OS "Search" key and - the second key being pressed down to active a shortcut. e.g. Search + L - would record the time between Search key down and L key down. If the user - pressed multiple keys after Search, we only record the first key down. - - - - - - Removed 2019-06. Shortcut viewer has been in production for many milestones - and its performance is adequate. - - jamescook@chromium.org - msw@chromium.org - wutao@chromium.org - - Time delay to make the visual update in response to a search-query. Note - that this does *not* include the initial delay to trigger the update after - the initial keystroke to change the search-query string. - - - - - - Removed 2019-06. Shortcut viewer has been in production for many milestones - and its performance is adequate. - - jamescook@chromium.org - msw@chromium.org - wutao@chromium.org - - Time delay for the visual update to be visible on screen in response to a - search-query. Note that this does *not* include the initial delay to trigger - the update after the initial keystroke to change the search-query string. - - - - - jamescook@chromium.org - msw@chromium.org - wutao@chromium.org - - Time delay between the user gesture that triggered the keyboard shortcut - viewer dialog (e.g. pressing Ctrl-Alt-/) and the dialog widget being shown, - including layout time for the views::Views. - - - - - fhorschig@chromium.org - - Android only. Records whenever users faces an action in the accessory bar or - one of its sheets. - - - - - fhorschig@chromium.org - - Android only. Records whenever users select an action in the accessory bar - or one of its sheets. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Android only. Records how often users encounter the keyboard accessory bar. - Its buckets show the contents when it came up. Every bucket may be logged up - to one time per impression. - - - - - fhorschig@chromium.org - - Android only. Records how many suggestions a user faced when opening a - sheet. The base histogram counts impressions across all sheets. - - - - - fhorschig@chromium.org - - Android only. Records which type of suggestion was selected from an open - sheet. - - - - - ioanap@chromium.org - fhorschig@chromium.org - - Android only. Records how often the user clicks on a certain toggle when - opening an accessory sheet together with the state the toggle was in before - clicking. - - - - - ioanap@chromium.org - fhorschig@chromium.org - - Android only. Records how often the user sees a certain toggle when opening - an accessory sheet together with the state the toggle was in. - - - - - fhorschig@chromium.org - - Android only. Records how often the bottom sheet was opened or closed by a - user and the overall count of closures. Closing buckets may be logged up to - one time per trigger. There are suffixes for each specific sheet type. - - - - - ioanap@chromium.org - fhorschig@chromium.org - - Android only. Records the number of times that the keyboard accessory was - shown on a form for which saving is disabled (with a crossed-out key icon). - Recorded when the user focuses the password field. - - Note: Only the "Shown" bucket should contain samples. - - - - - - Removed 2019-07 -- Replaced by - KeyboardAccessory.GeneratedPasswordDialogChoice*. - - ioanap@chromium.org - vasilii@chromium.org - - Android only. Records the interaction with the password generation dialog. - - - - - - - ioanap@chromium.org - vasilii@chromium.org - - Android only. Records the interactions with the password generation dialog - for automatic generation. - - - - - xiyuan@chromium.org - apotapchuk@chromium.org - Tracks cryptohome failure during kiosk launch. - - - - xiyuan@chromium.org - apotapchuk@chromium.org - Tracks kiosk launch errors. - - - - xiyuan@chromium.org - aghuie@chromium.org - - Records kiosk launches, whether it is an enterprise or consumer kiosk and - whether it is an auto launch or manual launch. - - - - - - Removed in 2019-07. - - brunoad@chromium.org - maroun@chromium.org - michaelpg@chromium.org - - Records usage of methods in KioskNextHome Mojo bridge. Recorded on every - method invocation. - - - - - - Removed in 2019-07. - - brunoad@chromium.org - maroun@chromium.org - michaelpg@chromium.org - - Records the result (success or failure) of every call from KioskNextHome - bridge to get the Android id. - - - - - - Removed in 2019-07. - - brunoad@chromium.org - maroun@chromium.org - michaelpg@chromium.org - - Records the result (success or error reason) of every call from - KioskNextHome bridge to launch an intent. - - - - - - Removed on 2019-07. - - - - agawronska@chromium.org - michaelpg@chromium.org - - Relative smoothness of animations of KioskNext Home state transitions. 100% - represents ideally smooth 60 frames per second. 50% represents only 30 - frames per second is achieved during the animations. 0% should not happen. - This metric is recorded exactly once when the user switches states of the - KioskNext Home. - - - - - - Removed in 2019-07. - - brunoad@chromium.org - maroun@chromium.org - michaelpg@chromium.org - Records when KioskNextShell becomes enabled or disabled. - - - - - Removed in 2019-07. - - brunoad@chromium.org - maroun@chromium.org - michaelpg@chromium.org - Records launches of KioskNextShell. Only true is recorded. - - - - googleo@chromium.org - chrome-language@google.com - - The actions taken on languages settings, recorded every time they happen. - This histogram will record every single event that happens separately. - - - - - googleo@chromium.org - chrome-language@google.com - The type of panes which language settings loads. - - - - anthonyvd@chromium.org - frechette@chromium.org - chrome-language@google.com - Accept languages. - - - - dvallet@chromium.org - chrome-language@google.com - The number of accepted languages in the user preferences. - - - - anthonyvd@chromium.org - frechette@chromium.org - chrome-language@google.com - Application languages used for UI. - - - - - - asvitkine@chromium.org - ntfschr@chromium.org - - Logs which Chrome flags from about:flags were active on start up. Android - WebView supports flags differently than most platforms, see - https://chromium.googlesource.com/chromium/src/+/HEAD/android_webview/docs/developer-ui.md - for details. - - - - - dominickn@chromium.org - hartmanng@chromium.org - peconn@chromium.org - - Records how Chrome handled a launch from an Android Home screen shortcut. - - - - - dominickn@chromium.org - hartmanng@chromium.org - peconn@chromium.org - - Records the source of an Android homescreen launch intent used to launch - Chrome. - - The Menu item bucket is deprecated as of M57, and will only contain records - for shortcuts added to the homescreen until M56. - - For M57+, the Menu item (standalone) bucket contains all launch intents - originating from the add to homescreen menu item that launch to standalone - mode and *are not* WebAPKs. These are sites which do not meet the PWA - eligibility criteria, but have an app manifest that specifies either - standalone or fullscreen display. This bucket also contains PWA *and* - non-PWA intents that were added to the homescreen *prior* to M57, as we - cannot distinguish between them after they are added. - - For M57+, the Menu item (shortcut) bucket contains all launch intents - originating from the add to homescreen menu item that launch to a browser - tab, regardless of when the intent was added. - - - - - dfalcantara@chromium.org - - Records flags (and combinations of flags) that were attached to the Intent - that started ChromeLauncherActivity. - - - - - - Removed 2016-06 -- hit rate is neglible. - - dfalcantara@chromium.org - - Records whether or not an invalid Android Intent was fired to launch Chrome. - (http://crbug.com/445136) - - - - - - Removed 2019-05 -- removed as part of removing mash code - - jamescook@chromium.org - - Records when a mojo ash UI service is started, for example the mojo app - version of the keyboard shortcut viewer. - - - - - - - calamity@chromium.org - grt@chromium.org - The different ways Chrome is launched. - - - - peter@chromium.org - yfriedman@chromium.org - - Records the display mode (as defined in the Web App Manifest spec) at the - launch of the Added to Home screen or installed Web App (including WebAPKs). - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, at least half of which were - complex text fragments, the average number of microseconds spent laying out - each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, at least half of which were - floats, the average number of microseconds spent laying out each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, the average number of - microseconds spent laying out each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, at least half of which were - fixed or absolute positioned, the average number of microseconds spent - laying out each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, at least half of which were - simple text fragments, the average number of microseconds spent laying out - each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - benjhayden@chromium.org - - For layouts that considered at least 100 nodes, at least half of which were - table cells, the average number of microseconds spent laying out each node. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - skobes@chromium.org - - Records the number of times ScrollAnchor adjusts the scroll offset. - - - - - pnoland@chromium.org - - Records the status of attempts to restore a serialized scroll anchor. - - - - - pnoland@chromium.org - - The number of characters in the selector computed for a serialized scroll - anchor. Recorded when a scroll anchor is serialized. - - - - - ymalik@chromium.org - - Records the number of times scroll anchoring is suppressed because of the - SANACLAP bit being set on an ancestor (see bit.ly/sanaclap). - - - - - pnoland@chromium.org - - The time it took to compute the selector of a serialized anchor element. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ymalik@chromium.org - - The time it took to find a suitable anchor element. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - pnoland@chromium.org - - The time it took to restore the scroll anchor using the serialized anchor - element. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 2018-09. No longer needed. - - chaopeng@chromium.org - input-dev@chromium.org - - We are considering allowing JS scrolling to prevent browser scroll position - restoration. This histogram measures the impact of that change, in terms of - how often restoration would be prevented by JS Scroll. Recorded after each - successful scroll restoration attempt. - - - - - - Replaced by LevelDB.ApproximateMemTableMemoryUse indefinitely. - - thildebr@chromium.org - - The approximate memory use of a LevelDB in bytes. Recorded right after - initializing an on-disk database. - - - - - nyquist@chromium.org - salg@google.com - - The approximate MemTable memory use of a LevelDB in bytes. Recorded right - after initializing an on-disk database. - - - - - - Removed in 2020-04. - - cmumford@chromium.org - chrome-owp-storage@google.com - The result of an open attempt of a leveldb. - - - - - Removed 2017-10. Superceded by LevelDB.SharedCache.KBUsed. - - cmumford@chromium.org - - The estimated size (in bytes) of the leveldb shared cache. Recorded once per - UMA ping. - - - - - - Removed 2020-04. - - cmumford@chromium.org - chrome-owp-storage@google.com - - The number of databases currently using the shared block cache. Recorded - once per UMA ping. - - - - - - No longer used. Removed in April, 2020. - - cmumford@chromium.org - - The estimated size (in kilobytes) of the leveldb shared cache. Recorded once - per UMA ping. - - - - - - Removed 2013-10. No thread-unsafety was found. - - dgrogan@chromium.org - - Linux and CrOS use unlocked_stdio(3). If it is used unsafely, record it - here. If there is no record of unsafety after chrome 29 has been in the - stable channel for a few weeks then revert this change. - - - - - cmumford@chromium.org - chrome-owp-storage@google.com - - Tracks the success rate of deleting an unused leveldb table backup file. - - - - - dmurph@chromium.org - pwnall@chromium.org - Methods where leveldb's Chromium environment has IO errors. - - - - - Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE. - - dgrogan@chromium.org - PlatformFileErrors encountered by a single leveldb method. - - - - - Removed 2020-04. - - dmurph@chromium.org - pwnall@chromium.org - - Errors (base::File::Error) encountered by a single leveldb method. - - - - - - Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewLogger. - - dgrogan@chromium.org - Errno of errors encountered in NewLogger. - - - - - Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewSequentialFile. - - dgrogan@chromium.org - Errno of errors encountered in NewSequentialFile. - - - - - Removed 2013-04. As of m28 use LevelDBEnv.IOError.NewRandomAccessFile. - - dgrogan@chromium.org - - File errors in leveldb ChromiumEnv's NewRandomAccessFile method. - - - - - - Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileAppend. - - dgrogan@chromium.org - Errno of errors encountered in WritableFileAppend. - - - - - Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileFlush. - - dgrogan@chromium.org - Errno of errors encountered in WritableFileFlush. - - - - - Removed 2019-06. - - dgrogan@chromium.org - - Number of directories missing when Non-IDB LevelDBEnv tries to create a Lock - file. - - - - - - Removed as of September 20, 2017. - - cmumford@chromium.org - - File descriptor limit recorded every time LevelDB calls NewRandomAccessFile - for clients other than IndexedDB. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Number of backup files found without corresponding ldb files. As measured by - GetChildren when used in LevelDB clients other than IndexedDB. - - - - - - Removed April, 2020. - - dmurph@chromium.org - pwnall@chromium.org - - When Non-IDB LevelDBEnv successfully retries an operation that had failed, - record the error from the most recent failed attempt. - - - - - - As of M54 no longer creating or using table backup files. - - dgrogan@chromium.org - - Success indicates a successful backup or restore operation for .ldb table - files when used by LevelDB clients other than IndexedDB. - - - - - - Removed 2013-04. As of m28 use LevelDBEnv.TimeUntilSuccessFor. - - dgrogan@chromium.org - - Time Non-IDB LevelDBEnv slept before successfully completing this operation. - 0 means success on the first try. - - - - - - Removed in 2020-04. - - dmurph@chromium.org - pwnall@chromium.org - - Time Non-IDB LevelDBEnv slept before successfully completing this operation. - 0 means success on the first try, as LevelDBEnv only sleeps when retries are - needed. - - - - - mek@chromium.org - - Delay between the browser process receiving changes and those changes being - written to the DB. - - - - - chengx@chromium.org - - This metric records the LoadLibraryExW and LoadLibraryW Windows API call - results, which are used in native_library_win.cc. - - - - - - Removed as of 11/2014, removed from code. - - feng@chromium.org - - A boolean that indicates whether the workaround of a Sony framework bug was - used. The metric is Android-specific, and is logged when the browser starts. - See more details at http://crbug.com/311644. - - - - - lizeb@chromium.org - - Percentage of the native library code pages resident in memory. Recorded - immediately before the library prefetching kicks in, only on Android. - - - - - - Removed 2019-10. The code has stabilized, the failure rate is 0.04% on - Stable. - - lizeb@chromium.org - pasko@chromium.org - - Detailed status of the library prefetch final status. This is an expanded - version of LibraryLoader.PrefetchStatus. Android only, recorded at most once - per browser startup. - - - - - - Removed 2019-10. No longer recorded. - - lizeb@chromium.org - pasko@chromium.org - - Indicates whether the forking of a child process to prefetch the native - library succeeded. Android only, recorded at most once per browser startup. - - - - - - Deprecated 2020-04 in favor of Linux.Distro2 because distro-specific version - metrics were added. - - thestig@chromium.org - thomasanderson@chromium.org - The Linux distro used. Logged on each start up. - - - - thestig@chromium.org - thomasanderson@chromium.org - - The Debian version number (eg. 8: Jessie, 9: Stretch). Logged once on - startup if Linux.Distro is Debian. - - - - - thestig@chromium.org - thomasanderson@chromium.org - - The Fedora version number (eg. 27, 28) Logged once on startup if - Linux.Distro is Fedora. - - - - - thestig@chromium.org - thomasanderson@chromium.org - - The openSUSE Leap version number, logged as 1000*major + minor (eg. 15001 = - 15.1). Logged once on startup if Linux.Distro is openSUSE Leap. - - - - - thestig@chromium.org - thomasanderson@chromium.org - - The Ubuntu version number, logged as 1000*year + month (eg. 16004 = 16.04 - Xenial). Logged once on startup if Linux.Distro is Ubuntu. - - - - - thestig@chromium.org - thomasanderson@chromium.org - The Linux distro used. Logged on each start up. - - - - thestig@chromium.org - - The version of glibc used. (Linux only) Logged on each start up. - - - - - mpdenton@google.com - src/sandbox/linux/OWNERS - - The Linux sandbox status. This describes what sandboxing features are - enabled (such as the suid/namespace sandboxes, various namespaces, seccomp - bpf, ...). Emitted once at startup. - - - - - pkotwicz@chromium.org - thomasanderson@chromium.org - - The window manager used. (Linux only) Logged on each start up. - - - - - thomasanderson@chromium.org - rjkroege@chromium.org - - The amount of time (ms) to construct the GbmSupportX11 singleton. - - - - - thomasanderson@chromium.org - - RTT between Chrome and the X11 server. Tracked in X11EventSource by - measuring the latency to receive a property event after changing a property. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - mcrouse@chromium.org - rajendrant@chromium.org - - Whether the LiteVideo hint cache contains hint for the host of the - navigation being considered for the LiteVideo optimization. Recorded for - every HTTP/HTTPS navigation. - - - - - mcrouse@chromium.org - rajendrant@chromium.org - - When determining whether the LiteVideo should be attempted on a navigation, - the host could be blocklisted for various reasons. This reports the reason - the host of the navigation was blocklisted, or was allowed. Recorded for - every HTTP/HTTPS navigation. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the total count of media responses that were currently being - throttled. Recorded whenever a new response gets throttled. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records whether the LiteVideo hint agent in the renderer process received - hints. - - - - - mcrouse@chromium.org - rajendrant@chromium.org - - Records the total number of LiteVideoHints, keyed by host, cached locally by - the LiteVideoDecider for use when queried by subframes. - - - - - mcrouse@chromium.org - rajendrant@chromium.org - - Records the number of entries in the map that records the number of rebuffer - events within each frame. Recorded once per navigation. - - - - - mcrouse@chromium.org - rajendrant@chromium.org - - Indicates whether the hints for configuring LiteVideo throttling provided - via Finch were successfully parsed and loaded for use. Android only, - recorded once per browser startup. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records how much a media response was throttled by LiteVideo. Recorded once - for each throttled response. - - - - - sophiechang@chromium.org - tbansal@chromium.org - - The status of when the optimization hints were received by the Loading - Predictor. This will be recorded on navigations for which predictions from - the Optimization Guide were received. - - - - - alexilin@chromium.org - - The number of origins that were preconnected for a page load. It includes - preconnect attempts that don't result in new opened connection. Logged after - the preconnect manager completes all jobs attached to the page load. - - - - - alexilin@chromium.org - - The percentage of origins that were preconnected and requested by a page - load to the total number of origins that were preconnected for a page load. - Logged after the preconnect manager completes all jobs attached to the page - load. - - - - - alexilin@chromium.org - tbansal@chromium.org - - When the loading predictor has origins in the local database for a given - navigation to preconnect and preresolve, the count of predicted origins. - - - - - alexilin@chromium.org - tbansal@chromium.org - - When the loading predictor has origins in the local database for a given - navigation to preconnect and preresolve, the precision of the predictions in - percentage. This is computed as 100 \times \frac{correct - predictions}{predictions}. - - - - - alexilin@chromium.org - tbansal@chromium.org - - When the loading predictor has origins in the local database for a given - navigation to preconnect and preresolve, the recall of the predictions, in - percentage. This is computed as 100 \times \frac{correct predictions}{all - prefetchable subresources}. - - - - - alexilin@chromium.org - tbansal@chromium.org - - When the prefetch predictor has origins in the local database for a given - navigation to preconnect and preresolve, records stats about whether - redirect was predicted correctly or incorrectly. - - - - - alexilin@chromium.org - - The number of hosts that were preresolved for a page load. It includes only - successful DNS lookups. Logged after the preconnect manager completes all - jobs attached to the page load. - - - - - alexilin@chromium.org - - The percentage of hosts that were preresolved and requested by a page load - to the total number of hosts that were preresolved for a page load. Logged - after the preconnect manager completes all jobs attached to the page load. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - Records the time measured before starting DNS lookup until after the - connection is complete for main frame subresources observed by the - LoadingPredictor. Only resources that required network connection and - happened before the first contentful paint are recorded. - - - - - - Removed July 2019. - - thestig@chromium.org - Records number of attempts to start local discovery. - - - - - Removed July 2019. - - thestig@chromium.org - Time between detector restarts. - - - - - Removed July 2019. - - thestig@chromium.org - Time before detector trigger notifications. - - - - - Removed July 2019. - - thestig@chromium.org - Records events related to devices page. - - - - - Removed July 2019. - - thestig@chromium.org - - Windows only histogram that reports request time spend accessing firewall - rules. It's logged once per browser process lifetime, when local discovery - is used first time. - - - - - - Removed July 2019. - - thestig@chromium.org - - Windows only histogram that reports, whether a firewall is set, so we can - bind inbound sockets. It's logged once per browser process lifetime, when - local discovery is used first time. - - - - - - Removed July 2019. - - thestig@chromium.org - Records events related to local discovery notifications. - - - - uthakore@chromium.org - invernizzi@chromium.org - - Number of requests made by a private page to resources besides itself. - - - - - uthakore@chromium.org - invernizzi@chromium.org - - Number of requests made by a public page to resources with reserved IP - addresses. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Type of backend requested from the Local Search Service. It is reported once - at the initialization of an Index. Chrome OS only. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Number of times the local search service has been requested to perform a - search on a device. Reported daily. The count is accumulated through the - day, spanning reboots, and sent once the system clock indicates that a full - day or more has passed since the last report. If the system is suspended or - off for more than a day, the current count will be reported the next time - the system boots, but the skipped days will not be reported. Chrome OS only. - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Reasons why local search daily metrics were reported. Chrome OS only. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Number of documents in the corpus. Recorded each time the index is updated - (documents added, updated or removed) and if the index is not empty. Chrome - OS only. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Number of results for each successful search. Chrome OS only. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Search request response status for Cros Settings. Chrome OS only. - - - - - - - jiameng@chromium.org - tby@chromium.org - thanhdng@chromium.org - wrong@chromium.org - - Time taken to find search results. Only recorded if search response status - is success, i.e. neither index nor query is empty. Chrome OS only. - - - - - ssid@chromium.org - - Total size of the HTML5 LocalStorage browser-side cache purged in KB when - memory pressure signal was triggered or cache size hit the limits. - - - - - ssid@chromium.org - - Total size of the HTML5 LocalStorage databases in KB in the browser-side - cache recorded each time a new database is opened in memory. - - - - - - No longer emitted after onion soup refactor. - - mek@chromium.org - dmurph@chromium.org - - Size of the HTML5 LocalStorage DB in KB in the browser-side cache. - - - - - - No longer emitted after onion soup refactor. - - mek@chromium.org - dmurph@chromium.org - - Time to load HTML5 LocalStorage into the browser-side cache. - {LocalStorageSizes} - - - - - - - No longer emitted after onion soup refactor. Replaced with - LevelDBWrapper.CommitDelay. - - mek@chromium.org - dmurph@chromium.org - - Delay between a page making changes and those changes being written to the - DB. - - - - - mek@chromium.org - dmurph@chromium.org - - Size of the HTML5 LocalStorage DB in KB in the renderer-side cache using - Mojo implementation. - - - - - mek@chromium.org - dmurph@chromium.org - - Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using - Mojo implementation. - - - - - mek@chromium.org - dmurph@chromium.org - - Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using - Mojo implementation, split by size. {LocalStorageSizes} - - - - - - ssid@chromium.org - - The renderer side cache hit rate metrics for new HTML5 LocalStorage DB - opened. - - - - - mek@chromium.org - dmurph@chromium.org - - Size of the HTML5 LocalStorage DB in KB in the renderer-side cache. - - - - - - No longer omitted after onion soup refactor. Replaced by - LocalStorage.MojoTimeToPrime. {LocalStorageSizes} - - mek@chromium.org - dmurph@chromium.org - - Time to load HTML5 LocalStorage into the renderer-side cache. - - - - - - - No longer omitted after onion soup refactor. Replaced by - LocalStorage.MojoTimeToPrime. - - mek@chromium.org - dmurph@chromium.org - - Time to load HTML5 LocalStorage into the renderer-side cache. Note that the - name is not 'Renderer' prefixed for continuity with the old naming. - - - - - mek@chromium.org - - Total size of the HTML5 LocalStorage browser-side cache purged in KB when - memory pressure signal was triggered or cache size hit the limits. - - - - - mek@chromium.org - - Total size of the HTML5 LocalStorage databases in KB in the browser-side - cache. Recorded each time a new database is opened in memory. - - - - - mek@chromium.org - - The result of an attempt to commit localstorage data to the database. - - - - - mek@chromium.org - - The result of a failed attempt to open a LevelDB database for LocalStorage. - - - - - mek@chromium.org - - The result of a failed attempt to open a LevelDB database for LocalStorage - on disk. - - - - - mek@chromium.org - - The result of a failed attempt to open a LevelDB database for LocalStorage - in memory. - - - - - mek@chromium.org - - The result of attempting to delete the LocalStorage database. - - - - - mek@chromium.org - - The reason opening a directory for the LevelDB database that backs - LocalStorage failed. - - - - - mek@chromium.org - - The reason loading an initial snapshot of the localstorage data for an - origin failed. - - - - - mek@chromium.org - - Whether or not any fixes needed to be made to localstorage data, as a result - of bugs in the migration code in M61/M62. Recorded every time the browser - loads an initial snapshot of the localstorage data for an origin. - - - - - mek@chromium.org - dullweber@chromium.org - - Recorded when the database connection is closed unexpectedly. - - - - - mek@chromium.org - - The reason opening the LevelDB database that backs LocalStorage failed. - - - - - - - mek@chromium.org - - The result of opening the LevelDB database that backs LocalStorage. - - - - - mek@chromium.org - - The reason reading the schema version of the LocalStorage database failed. - - - - - mhasank@google.com - arc-core@google.com - - Tracks the time to backup ARC bug report when starting ARC fails. - - - - - xiyuan@chromium.org - - Tracks the browser process shutdown time from when SIGTERM is sent to the - browser process to when the browser process group exits (or gets killed by - SIGABRT). - - - - - cmasone@chromium.org - sumit@chromium.org - - Chrome OS histogram tracking, per consumer sign-in, whether the device owner - is allowing arbitrary accounts to be used on the device, or only those on a - specific whitelist. - - - - - - - alemate@chromium.org - rsorokin@chromium.org - - A set of chrome flags that triggered browser restart on Chrome OS after user - sign in. Chrome needs to be restarted if the device owner set of flags is - different from the user flags. Which means that there is a flag difference - which led to this restart. This difference is reported by this metric. - - - - - - Removed 01/2020. It was added to decide if the SplitSettings project could - safely decouple browser page zoom from ARC++/OS zoom. We decided it was safe - and did the decoupling in M78. - - jamescook@chromium.org - jessejames@chromium.org - cros-system-services@google.com - The user's default page zoom setting, recorded on login. - - - - achuith@chromium.org - Chrome OS login failure reason. - - - - achuith@chromium.org - omrilio@chromium.org - - Chrome OS histogram that keeps track of the days since the least frequently - used account signed in. Reported on every boot and once a day after that. - - - - - betuls@chromium.org - jorgelo@chromium.org - chromeos-security-core@google.com - - Mount Namespace creation success status. Reported every time user signs in. - - - - - alemate@chromium.org - Records whether a new user's priority prefs sync timed out. - - - - alemate@chromium.org - - Time spent waiting for priority preferences to sync after new user sign in. - The operation will time out after 10s. - - - - - glevin@chromium.org - - On offline login failure, records whether it is for an existing user. - - - - - glevin@chromium.org - - On offline login success, records number of attempts, including success. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Tracks the reason why a user was sent through the GAIA re-auth flow which - caused the local password change. - - - - - xiyuan@chromium.org - omrilio@chromium.org - - Records the UI flow after a possible password change is detected. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Tracks the reason why a user was sent through the GAIA re-auth flow which - did not cause the local password change. - - - - - cmasone@chromium.org - The state of Chrome OS owner key and device policy files. - - - - rsorokin@chromium.org - achuith@chromium.org - cros-oac@google.com - - Time from first display of the login prompt until the user completes signing - in. - - - - - elijahtaylor@google.com - yusukes@chromium.org - rsorokin@chromium.org - cros-oac@google.com - - Time from first display of the login prompt until the existing user - completes signing in. - - - - - - Removed in M85. Splitted in two: Login.PasswordChanged.ReauthReason and - Login.PasswordNotChanged.ReauthReason. - - achuith@chromium.org - - Tracks the reason why a user was sent through the GAIA re-auth flow. - - - - - iby@chromium.org - - Tracks whether a ChromeOS user was logged out because Chrome repeatedly - crashed. - - - - - mnissler@chromium.org - Result of a state key generation operation. - - - - achuith@chromium.org - Chrome OS login success reason. - - - - glevin@chromium.org - - Time between sending a request to, and receiving a reply from, GAIA token - endpoint to validate TokenInfo. - - - - - raleksandrov@google.com - antrim@chromium.org - rsorokin@chromium.org - cros-oac@google.com - - Time between sending a request to, and receiving a reply from, GAIA token - endpoint to obtain TokenInfo. - - - - - alemate@chromium.org - achuith@chromium.org - - Chrome OS histogram that keeps track of number of users who have logged in - in the last 28 days. Reported on every boot and once a day after that. - - - - - alemate@chromium.org - achuith@chromium.org - - Chrome OS histogram that keeps track of number of users who have logged in - in the last day. Reported on every boot and once a day after that. - - - - - alemate@chromium.org - achuith@chromium.org - - Chrome OS histogram that keeps track of number of users who have logged in - in the last 7 days. Reported on every boot and once a day after that. - - - - - alemate@chromium.org - achuith@chromium.org - - Chrome OS histogram that keeps track of percentage of local users who have - logged in in the last 7 days. Reported on every boot and once a day after - that. - - - - - cmasone@chromium.org - - Chrome OS histogram that keeps track of the way a user logs in and whether - Chrome OS is running normal or developer mode. - - - - - tbansal@chromium.org - - Original Blink priority of the request that belongs to an iframe. Recorded - for every request fetched via Blink, but only when the experiment to lower - the priority of iframes is enabled. - - - - - tbansal@chromium.org - - Original Blink priority of the request that belongs to the main frame. - Recorded for every request fetched via Blink, but only when the experiment - to lower the priority of iframes is enabled. - - - - - - - amoylan@chromium.org - alanlxl@chromium.org - - CPU time (for one CPU core) of one Chrome OS ML Service request. Reported - for all users; users without high-resolution clocks will report 0 for short - requests. - - - - - alanlxl@chromium.org - amoylan@chromium.org - - Fraction of total CPU resources used by Chrome OS ML Service, sampled every - 5 minutes. - - - - - amoylan@chromium.org - alanlxl@chromium.org - - The result of CreateGraphExecutor, which can be OK or some specific error. - - - - - - Removed 2020-02-01 because elapsed time should be measured by clients, if - they need it. - - - - amoylan@chromium.org - alanlxl@chromium.org - Elapsed time of one Chrome OS ML Service request. - - - - amoylan@chromium.org - alanlxl@chromium.org - - The result of Execute, which can be OK or some specific error. - - - - - amoylan@chromium.org - alanlxl@chromium.org - charleszhao@chromium.org - - The result of load handwriting model, which can be OK or some specific - error. The error code could be logged in machine learning service in chrome - or in chromeos when handwriting model is not loaded successfully. - - - - - amoylan@chromium.org - alanlxl@chromium.org - charleszhao@chromium.org - - The result of handwriting recognition, which can be OK or some specific - error. - - - - - amoylan@chromium.org - alanlxl@chromium.org - - The error result of LoadModel in cases when the model name could not be - determined. See MachineLearningService.*.LoadModelResult.Event for the - result broken down by model name when the name is known. - - - - - amoylan@chromium.org - alanlxl@chromium.org - - The result of LoadModel, which can be OK or some specific error. - - - - - alanlxl@chromium.org - amoylan@chromium.org - - Events related to the connection and disconnection of the Mojo IPC channel - between Chrome and the Chrome OS ML Service. - - - - - - Removed 07/2019 because we change to record total (shared+unshared) memory - rather than only private memory. Replaced by - MachineLearningService.PeakTotalMemoryKb. - - alanlxl@chromium.org - amoylan@chromium.org - - Peak private (non-shared) memory used by Chrome OS ML Service over the last - 24 hours. Sampled every 5 minutes, so may miss short-lived spikes. - - - - - alanlxl@chromium.org - amoylan@chromium.org - honglinyu@chromium.org - - Peak total (shared and non-shared) memory used by Chrome OS ML Service over - the last 24 hours. Sampled every 5 minutes, so may miss short-lived spikes. - - - - - - Removed 07/2019 because we change to record total (shared+unshared) memory - rather than only private memory. Replaced by - MachineLearningService.TotalMemoryDeltaKb. - - - - amoylan@chromium.org - alanlxl@chromium.org - - Memory usage increase caused by one Chrome OS ML Service request. - - - - - - Removed 07/2019 because we change to record total (shared+unshared) memory - rather than only private memory. Replaced by - MachineLearningService.TotalMemoryKb. - - alanlxl@chromium.org - amoylan@chromium.org - - Private (non-shared) memory used by Chrome OS ML Service, sampled every 5 - minutes. - - - - - amoylan@chromium.org - alanlxl@chromium.org - honglinyu@chromium.org - - Memory usage increase caused by one Chrome OS ML Service request. - - - - - alanlxl@chromium.org - amoylan@chromium.org - honglinyu@chromium.org - - Total (shared and non-shared) memory used by Chrome OS ML Service, sampled - every 5 minutes. - - - - - - Removed in M86. - - yilkal@chromium.org - michaelpg@chromium.org - cros-families-eng@google.com - - The depth of blocked frame in the frame tree. The value is recorded when the - renderer frame hosting the blocking page finishes loading. - - - - - yilkal@chromium.org - michaelpg@chromium.org - cros-families-eng@google.com - - The number of blocked iframes per unblocked main frame load. The value is - recorded when the main frame finishes loading. - - - - - - Removed 07/2020 as it is no longer used. - - achuith@chromium.org - - Chrome OS histogram that keeps track of supervised user password change - result. - - - - - agawronska@chromium.org - cros-families@google.com - - The counts of results from supervised user URL filtering. Each entry - includes the outcome of the filter (i.e. allowed, blocked, or unknown) and - the page transition type (how the user got there, e.g. typed URL, clicked - link). - - - - - escordeiro@chromium.org - unichrome-eng@google.com - - The extra page load delays introduced by network requests due to the - supervised user url filtering feature, measured once per page load, for - failed requests. This is the delay to fetch the token and call the - ClassifyUrl rpc, when there is a cache miss. - - - - - escordeiro@chromium.org - unichrome-eng@google.com - - The extra page load delays introduced by network requests due to the - supervised user url filtering feature, measured once per page load. This is - the delay to fetch the token and call the ClassifyUrl rpc, when there is a - cache miss. Only recorded for successful requests. - - - - - escordeiro@chromium.org - unichrome-eng@google.com - - The counts of response status from supervised user - KidsManagementURLCheckerCLient. Each entry includes the outcome of a request - (i.e. success, net error, parsing error). - - - - - michaelpg@chromium.org - yilkal@chromium.org - cros-families-eng@google.com - - The counts of request for permission sent from main frame or sub-frame. - - - - - agawronska@chromium.org - cros-families@google.com - - The extra page load delays introduced by network requests due to the - supervised user SafeSites feature, measured once per page load. - - - - - treib@chromium.org - escordeiro@chromium.org - menegola@chromium.org - - The counts of results from the supervised user safety filter. Each entry - includes the outcome of the filter (i.e. allowed, blocked, or unknown) and - the page transition type (how the user got there, e.g. typed URL, clicked - link). This only includes URL requests that were handled by the SafeSites - filter (both online and the static blacklist). - - - - - agawronska@chromium.org - cros-families@google.com - - The number of whitelists installed for a supervised user. Recorded at every - profile startup. - - - - - - Removed in M85. - - treib@chromium.org - escordeiro@chromium.org - menegola@chromium.org - - The total amount of time taken to parse the JSON contents of a whitelist out - of process. - - - - - - Removed in M85. - - treib@chromium.org - escordeiro@chromium.org - menegola@chromium.org - - The amount of time taken to read a whitelist file from disk. - - - - - - Removed in M85. - - treib@chromium.org - escordeiro@chromium.org - menegola@chromium.org - - The total amount of time taken to load a whitelist from disk and parse it, - including jumps to the blocking thread. - - - - - mgiuca@chromium.org - mlamouri@chromium.org - - Tracks whether the Manifest fetch succeed and why it failed if it failed. - - - - - mgiuca@chromium.org - mlamouri@chromium.org - - Tracks which properties of a Manifest were present when it was parsed. If a - property can't be parsed, it will be recorded as not present. These - histograms will only be used if the Manifest was correctly fetched and - parsed and the parsed manifest is not empty. - - - - - - Removed as of 2019-10-21. - - mgiuca@chromium.org - mlamouri@chromium.org - Tracks whether the parsed Manifest is the empty Manifest. - - - - mgiuca@chromium.org - mlamouri@chromium.org - - Tracks the Manifest parsing result. A failure will be recorded if the - Manifest was incorrectly structured. This doesn't take into account parse - failures for each individual properties. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of credentials presented to the user in the "Use - other password..." view in Manual Fallback. This is logged everytime - the user opens this view. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of cards presented to the user in Manual Fallback. This is - logged everytime the user opens this view. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of credentials presented to the user in the Passwords - Manual Fallback view. This is logged everytime the user opens this view. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of profiles presented to the user in Manual Fallback. This - is logged everytime the user opens this view. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of autofill suggestions present when the user taps on the - credit card button in manual fallback. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of password suggestions present when the user taps on the - password button in manual fallback. - - - - - javierrobles@chromium.org - gambard@chromium.org - - Tracks the number of autofill suggestions present when the user taps on the - profiles (address) button in manual fallback. - - - - - - Removed as of July 21, 2014. - - Please list the metric's owners. Add more owner tags as needed. - - Whether accelerated compositing was used for HTML5 media rendering. - - - - - vikassoni@chromium.org - Error codes to handle AImage and AImageReader api calls. - - - - mlamouri@chromium.org - media-dev@chromium.org - - Android-specific metric. The time between the moment the backgrounded video - playback is started (meaning the user just resumed the backgrounded video - allowing playback) and the moment it stops being background playback by the - current playing video either going foreground or being paused by the user. - Note: on Android, videos are suspended when backgrounded. - - - - - - Removed as of 08/2017 - - qinmin@chromium.org - - Android: Records whether a regular media URL is HLS (HTTP Live Streaming) - media or not. - - - - - - Removed as of 08/2017 - - sandersd@chromium.org - - Android: Records which HLS prediction based on the original URL was best. - - - - - tguilbert@chromium.org - media-dev@chromium.org - Android: Whether MediaPlayer exited without errors. - - - - sandersd@chromium.org - media-dev@chromium.org - - Wall time of MediaPlayer playbacks. Each count represents one second of - media playback. Multiple MediaPlayer instances can together accumulate watch - time faster than real time. - - - - - - Removed as of 04/2017 - - qinmin@chromium.org - - Android: Number of consecutive media server crashes monitored before it is - reset to 0. Reset happens if there are no crashes in a minute, or if user - hits the "try again" button on the media throttle info bar. - - - - - - Removed as of 04/2017 - - qinmin@chromium.org - - Android: The distribution of responses to the media throttle infobar prompt. - - - - - - Removed as of June 12, 2017. Replaced by - Media.ChromeArcVideoDecodeAccelerator.InitializeResult. - - johnylin@chromium.org - - Counts of status values returned from calls to - ArcGpuVideoDecodeAccelerator::Initialize(). - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Records when an audible tab is closed and we now only have one audible tab - open. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records how long more than one tab is audible at the same time. The - concurrent tabs might change during this period. The time recorded starts - when the browser goes from one to two audbile tabs and stops when it is back - below two. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records how many tabs were audible when a new tab started to be audible. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records how many tabs are audible at the same time during the session. It is - recording the maximum audible tab count everytime it increases. In other - words, a session with N concurrent audible tabs will record entries from 1 - through N exactly once. - - - - - henrika@chromium.org - media-dev@chromium.org - - Size (in audio frames) of native I/O buffers that is set by the audio - manager when calling AUAudioInputStream::Open(). I.e., it is the actual - buffer size and it can differ from the one that the client requested. Only - sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - henrika@chromium.org - media-dev@chromium.org - - Stored in combination with Media.Audio.RenderFailsWhenBufferSizeChangesMac. - It is set to true if calls to AudioUnitRender has ever worked, i.e., we did - not start to see kAudioUnitErr_CannotDoInCurrentContext error messages - directly from start but there has been at least on successful call to - AudioUnitRender. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Indicates if the Automatic Gain Control (AGC) is enabled or not. Only - sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - mlamouri@chromium.org - media-dev@chromium.org - Records the autoplay source of audios. - - - - - Removed from code as of 07/2019. - - mlamouri@chromium.org - media-dev@chromium.org - - Records time from load starts until audio starts based on autoplay - attribute. - - - - - - Removed from code as of 07/2019. - - mlamouri@chromium.org - media-dev@chromium.org - - Records time from load starts until audio starts based on play method. - - - - - - Removed as of May 2019. - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Records whether the given bitstream audio output format is supported. - Recorded when the browser or audio process AudioManager is constructed. - - - - - - Removed as of 02/2017. - - tommi@chromium.org - - A boolean that reflects whether or not an error was reported during audio - capture. - - - - - guidou@chromium.org - olka@chromium.org - - Whether missing callbacks where detected during audio capture. Logged when - AudioInputDevice is stopped. - - - - - - Removed March 2019. - - grunell@chromium.org - - The audio input device latency. The time from when a frame was captured - until it reaches Chrome's platform audio implementation. Sampled for every - buffer received from the device, and reports the latency for the first frame - in the buffer. - - - - - guidou@chromium.org - armax@chromium.org - - The number of captured audio frames that is provided by the operating system - in each callback. Typically, Chrome will want to use a 10 ms buffer (e.g. - 480 frames for a sample rate of 48 kHz), but the OS may decide to capture - e.g. 256 frames of audio at a time. If the desired frame size is used, the - emitted value is special-cased to be 0. This histogram then shows how - frequent it is that the desired number of frames is used and if not, the - number of frames used in practice. The number of frames per callback is - normally constant or very rarely changed throughout the lifetime of the - audio stream. The first value that differs from the desired value is stored - and logged when an audio input stream is closed. Any further differences - during the lifetime will be ignored. - - - - - guidou@chromium.org - olka@chromium.org - - The number of glitches that were detected at the OS level while an audio - stream was active. A glitch is detected if the OS has to skip providing a - set of frames. This value is logged when an audio input stream is closed. - - - - - guidou@chromium.org - olka@chromium.org - - A boolean that reflects whether or not an error was reported during audio - capture for a high latency stream. - - - - - guidou@chromium.org - olka@chromium.org - - This histogram measures the duration of every input stream, as seen from the - renderer. It counts from when it has been successfully started, until it is - stopped. Streams that fail to start are not logged. - - - - - guidou@chromium.org - olka@chromium.org - - The length in milliseconds of the largest audio glitch that was detected at - the OS level. This value is logged when an audio input stream that has - suffered glitches is closed. - - - - - guidou@chromium.org - olka@chromium.org - - The combined length in milliseconds of audio glitches that was detected at - the OS level. This is useful to know in particular for audio processing such - as echo cancellation. This value is logged when an audio input stream that - has suffered glitches is closed. - - - - - guidou@chromium.org - olka@chromium.org - - A boolean that reflects whether or not an error was reported during audio - capture for a low latency stream. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The time from the first microphone access failure due to blocked system - permission before the last browser restart to startup after browser restart. - Logged once at browser startup if the system permission then is allowed. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The time from the last microphone access failure due to blocked system - permission before the last browser restart to startup after browser restart. - Logged once at browser startup if the system permission then is allowed. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for microphone. Logged once at browser - startup. For more information on the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for microphone. Logged once at browser - startup if there was a failure accessing the microphone due to blocked - system permission before the last browser restart. For more information on - the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for microphone at the time of a user media - request. Logged when the system permission is checked. If the permission is - "not determined" this is logged, permission is requested, and the - resulting permission (from the user response) is also logged. For more - information on the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - - Removed June 2020. - - maxmorin@chromium.org - olka@chromium.org - - Error codes from AudioInputStreamBroker::ObserverBindingLost. They describe - why an audio input stream ended. - - - - - - Replaced by Media.Audio.Capture.StreamCallbackError2 - - maxmorin@chromium.org - - When AudioInputDevice is stopped, this stat is recorded with whether an - error callback was ever received over IPC. - - - - - guidou@chromium.org - olka@chromium.org - - When AudioInputDevice is stopped, this stat is recorded with whether an - error callback was ever received over IPC, and in that case whether the - error occurred during or after stream creation. - - - - - maxmorin@chromium.org - - A boolean that reflects whether or not an error was reported during audio - capture for a virtual stream. - - - - - - Removed March 2019. - - grunell@chromium.org - - The number of times a glitch was detected by detecting skipped frames (as - with Media.Audio.Capture.Glitches) and disconinuity was flagged by the OS at - the same time (as with Media.Audio.Capture.Win.Discontinuities). Sometimes - these indications are not consistent with each other so this metric helps - understanding how often they aren't. This value is logged when an audio - input stream is closed. - - - - - - Removed March 2019. - - grunell@chromium.org - - The audio engine's period between processing passes. See - IAudioClient::GetDevicePeriod. This value is logged when an audio input - stream is opened. - - - - - - Removed March 2019. - - grunell@chromium.org - - The number of times the device position was less than expected during the - lifetime of an audio stream. This value is logged when an audio input stream - is closed. - - - - - - Removed March 2019. - - grunell@chromium.org - - The number of glitches that were detected at the OS level on Windows while - an audio stream was active, as reported by the OS via the discontinuity flag - (see IAudioCaptureClient::GetBuffer). This value is logged when an audio - input stream is closed. - - - - - - Removed March 2019. - - grunell@chromium.org - - The endpoint buffer size for input audio. This value is logged when an audio - input stream is opened. - - - - - tommi@chromium.org - guidou@chromium.org - olka@chromium.org - - Error codes from IAudioClient::Initialize() in - WASAPIAudioInputStream::InitializeAudioEngine on Windows. - - - - - guidou@chromium.org - olka@chromium.org - - Errors from IAudioClient::Initialize() in - WASAPIAudioInputStream::InitializeAudioEngine on Windows that are related to - the audio format. Each error is split by whether format conversion was used - or not. - - - - - gudiou@chromium.org - olka@chromium.org - - Success/error cases for opening an audio input stream on Windows. - - - - - - Removed March 2019. - - grunell@chromium.org - - The maximum stream latency as reported by the OS. See - IAudioClient::GetStreamLatency. This value is logged when an audio input - stream is opened. - - - - - guidou@chromium.org - armax@chromium.org - - Tracks support and initialization success/failure of the CoreAudio dispatch - override hotfix. Logged during initialization of AudioManagerMac. The fix is - not supported on macOS earlier than version 10.10. - - - - - guidou@chromium.org - armax@chromium.org - - Logged whenever the CoreAudio dispatch override hotfix needs to look up the - calling function using dladdr(). Once ResumeIO and PauseIO have been - identified, no more lookups should be performed during the session. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Indicates if the size of the audio unit's IO buffer was changed when - starting an input audio stream. Sampled each time an AUAudioInputStream - instance is closed, i.e., we know that input audio has started as it should - when this value is stored. Can be compared with - Media.Audio.InputBufferSizeWasChangedMac which is only added when input - audio fails to start. - - - - - henrika@chromium.org - - Indicates if the size of the audio unit's IO buffer was changed when - starting an input audio stream. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - Removed Feb 2018. Was put in place to debug missing callback issues that - have since been resolved. - - henrika@chromium.org - - Lists device properties that have been changed during an audio input stream - session. We update a map of different property changes during a session and - all these values are recorded when an AUAudioInputStream object is closed, - hence multiple enum values can be emitted when the histogram is stored. - - - - - - Removed Feb 2018. Was put in place to debug missing callback issues that - have since been resolved. - - henrika@chromium.org - - Lists device properties that have been changed during an audio input stream - session. Only sampled when Media.Audio.InputStartupSuccessMac reports - 'Failure' and multiple enum values can be emitted each time that happens. - - - - - - Removed May 2017. Restart mechanism is removed. - - henrika@chromium.org - - Counts the total number of times an attempt to restart input audio has been - done. The value is stored once when a stream is closed and updated when it - has been detected that input audio callbacks are not generated as expected. - - - - - henrika@chromium.org - webrtc-audio@google.com - - Indicates if audio capturing did start after stream startup was requested. - Sampled once, a few seconds after a stream has been asked to start. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Indicates if audio capturing started with a small delay or not. Sampled each - time an AUAudioInputStream instance is closed, i.e., we know that input - audio has started as it should when this value is stored. Can be compared - with Media.Audio.InputStartWasDeferredMac which is only added when input - audio fails to start. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Indicates if audio capturing started with a small delay or not. Only sampled - when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - henrika@chromium.org - media-dev@chromium.org - - Indicates if the volume level of the audio session is set to zero when the - input audio session starts. Sampled once when the stream starts but only on - Windows platforms. See http://crbug.com/1014443. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Indicates if the Mac OSX device is on battery power or not. Only sampled - when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - henrika@chromium.org - media-dev@chromium.org - - The number of logical processors/cores available on the Mac OSX device. Only - sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Number of created default input audio streams. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Number of created low-latency input audio streams. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Number of created output audio streams. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Time delta between the moment output device authorization request is - received by the browser and the moment its processessing is finished (and - reply is to be sent back to the renderer if IPC is not closed yet). - - - - - - Removed as of October 2019. - - armax@chromium.org - - When a mojo audio stream factory is destructed, the streams it created are - also destructed. This is a potential source of stat differences between the - new mojo code and the old Chrome IPC code, where streams could potentially - stick around until the destruction of the owning RenderProcessHost. This - histogram measures how many output streams are destructed each time a mojo - output stream factory is destructed. - - - - - henrika@chromium.org - webrtc-audio@google.com - - The number of physical processors/cores available on the Mac OSX device. - Only sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - armax@chromium.org - guidou@chromium.org - - The time, in milliseconds, between when a block of audio is read from the - soundcard and when it's presented to the audio processor. Used in - calculating the total system delay for the audio processor. - - - - - armax@chromium.org - guidou@chromium.org - - The variance of the capture delay in milliseconds (see - Media.Audio.Processing.CaptureDelayMs). Logged once every second and - calculated over the past second of data. - - - - - armax@chromium.org - guidou@chromium.org - - The time, in milliseconds, between when a block of audio is presented to the - audio processor and the time it's played out on the soundcard. Used in - calculating the total system delay for the audio processor. - - - - - armax@chromium.org - guidou@chromium.org - - The variance of the render delay in milliseconds (see - Media.Audio.Processing.RenderDelayMs). Logged once every second and - calculated over the past second of data. - - - - - armax@chromium.org - guidou@chromium.org - - The estimated total audio system delay presented to the audio processor. The - sum of the individual capture and render delays at similar points in time. - - - - - armax@chromium.org - guidou@chromium.org - - The variance of the total delay in milliseconds (see - Media.Audio.Processing.TotalDelayMs). Logged once every second and - calculated over the past second of data. - - - - - - Removed in June 2020. - - guidou@chromium.org - olka@chromium.org - - Number of simultaneous inputs coming to the AudioRendererMixer which renders - audio with user specified latency. The value is logged each time it reaches - a new maximum for the mixer. It is useful for evaluating how mixing audio in - renderer reduces the number of output audio streams going from the renderer - to the browser. - - - - - - Removed in June 2020. - - olka@chromium.org - - Number of simultaneous inputs coming to the AudioRendererMixer which renders - audio with interactive latency. The value is logged each time it reaches a - new maximum for the mixer. It is useful for evaluating how mixing audio in - renderer reduces the number of output audio streams going from the renderer - to the browser. - - - - - - Removed in June 2020. - - olka@chromium.org - - Number of simultaneous inputs coming to the AudioRendererMixer which renders - audio with playback latency. The value is logged each time it reaches a new - maximum for the mixer. It is useful for evaluating how mixing audio in - renderer reduces the number of output audio streams going from the renderer - to the browser. - - - - - - Removed in June 2020. - - olka@chromium.org - - Number of simultaneous inputs coming to the AudioRendererMixer which renders - audio with real time latency. The value is logged each time it reaches a new - maximum for the mixer. It is useful for evaluating how mixing audio in - renderer reduces the number of output audio streams going from the renderer - to the browser. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Subset of audio output latencies encountered by the renderer so far. Logged - each time an audio output with a new latency starts playing. The values are - bitsets where each bit represents corresponding latency according to - AudioLatency::LatencyType. Useful for understanding usecases for audio - output mixing in renderer. - - - - - - Removed June 2019. - - olka@chromium.org - - Reflects how regularly browser issues audio requests to renderer. Depends on - how well the system buffer size the browser side renders audio at and the - buffer size it requests from renderer are aligned. When zero, it means - renderer buffer size is a multiple of system buffer size, and render calls - from browser to renderer are issued evenly. When -1, it means the renderer - buffer size is larger than system buffer size, but is not an exact multiple - of it; in this case browser periodically skips a call to renderer. When - positive, floor(value/2) reflects the number of extra consecutive render - requests issued by browser to renderer each time to fulfill the system audio - render request; if (value/2) is not integer, then plus one more extra call - is issued periodically. The metric is recorded on the edge between browser - and renderer. On Mac the system buffer size may vary dynamically, the metric - does not capture that: only the buffer size mismatch introduced by audio - output device configuration is captured. - - - - - guidou@chromium.org - olka@chromium.org - - The number of frames audio is actually rendered at if the number is - different from the desired number of frames. If the desired frame size is - used, this value will be 0. Typically, Chrome will want to use a 10ms buffer - (e.g. 480 frames for a sample rate of 48kHz), but we might have to render - audio 256 frames at a time. This histogram gives us an indication as to how - frequent that is and what buffer sizes are used in practice. This value is - logged when an audio output stream is stopped. - - - - - guidou@chromium.org - armax@chromium.org - - The time spent to get audio data from the source. For WebRTC, it's the time - spent in WebRtcAudioRenderer::SourceCallback. Logged every function call, - which is every 10 ms. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - guidou@chromium.org - armax@chromium.org - - The maximum time spent to get audio data from the source during a session. - For WebRTC, it's the time spent in WebRtcAudioRenderer::SourceCallback. A - session is between Start() and Stop() of WebRtcAudioRenderer. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - guidou@chromium.org - olka@chromium.org - - The number of glitches that were detected at the OS level while an audio - stream was active. A glitch is detected if the OS has to skip rendering a - set of frames. This value is logged when an audio output stream is stopped. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The time delta from an AudioInputDevice sending a RecordStream message to it - getting its first data callback. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The time delta between the moment a MojoAudioInputIPC instance on the - renderer process requests a new stream from the browser to the moment it - receives a response. - - - - - guidou@chromium.org - olka@chromium.org - - The length in milliseconds of the largest glitch that was detected at the OS - level. This value is logged when an audio output stream that has suffered - glitches is stopped. - - - - - guidou@chromium.org - olka@chromium.org - - The combined length in milliseconds of audio glitches. This is useful to - know in particular for audio processing such as echo cancellation. This - value is logged when an audio output stream that has suffered glitches is - stopped. - - - - - maxmorin@chromium.org - - Similar to Media.Audio.OutputDeviceAuthorizationTime, this histogram - measures the time required for device authorization, but it is measured on - the renderer side when AudioOutputDevice calls RequestDeviceAuthorization on - the IO thread until it receives OnDeviceAuthorized, also on the IO thread. - Note that an authorization timeout will cause OnDeviceAuthorized to be - called, so for platforms that use a timeout, very few times will be above - the timeout value. - - - - - guidou@chromium.org - olka@chromium.org - - Whether audio output device timed out waiting for authorization reply from - the browser side. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The time delta from an AudioOutputDevice sending its first PlayStream - message to it getting its first data callback. - - - - - armax@chromium.org - dalecurtis@chromium.org - guidou@chromium.org - olka@chromium.org - - Device status received in response to device authorization request. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The time delta between the moment a MojoAudioOutputIPC instance on the - renderer process requests a new stream from the browser to the moment it - receives a response. - - - - - maxmorin@chromium.org - - This histogram measures the duration of every output stream, as seen from - the renderer. It counts from when it has been successfully started, until it - is stopped. Streams that fail to start are not logged. - - - - - guidou@chromium.org - olka@chromium.org - - Whether a cached sink was used to get audio output device information, or a - new sink was created for that. - - - - - guidou@chromium.org - olka@chromium.org - - When a new sink is created to get output device information, it is cached. - This metric shows if such a sink is later reused for audio output (can - happen no more than once) or deleted unused after timeout expires. Logged - when one of the abovementioned events takes place. - - - - - guidou@chromium.org - olka@chromium.org - - Whether a sink was created through the sink cache or directly. - - - - - - Removed 09/2018, and replaced by - Media.Audio.Render.StreamBrokerDisconnectReason2. - - jonasolsson@chromium.org - maxmorin@chromium.org - olka@chromium.org - - Error codes from AudioOutputStreamBroker::ObserverBindingLost. They describe - why an audio output stream ended. - - - - - - Removed on April 2020. - - guidou@chromium.org - olka@chromium.org - - Describes why and in which state an audio output stream ended. - - - - - - Removed as of March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - If the document was destroyed after the broker requested the output stream - from the audio service, but before it received the reply: how long ago the - stream was requested. - - - - - - Removed as of March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Time interval between the moment the broker requested the output stream from - the audio service, and the moment it received the reply. - - - - - - Replaced by Media.Audio.Render.StreamCallbackError2 - - maxmorin@chromium.org - - When AudioOutputDevice is stopped, this stat is recorded with whether an - error callback was ever received over IPC. - - - - - maxmorin@chromium.org - - When AudioOutputDevice is stopped, this stat is recorded with whether an - error callback was ever received over IPC, and in that case whether the - error occurred during or after stream creation. - - - - - henrika@chromium.org - media-dev@chromium.org - - True if a call to AudioUnitRender failed with an error code of - kAudioUnitErr_CannotDoInCurrentContext (-10863) and the call was preceded - with a change in the native I/O buffer size. This value is logged while - input audio is active but it should be a very rare event. - - - - - henrika@chromium.org - media-dev@chromium.org - - Size (in audio frames) the client has asked for when creating an - AUAudioInputStream object. It might not be able to fulfill this request. The - actual size is given by Media.Audio.ActualInputBufferFrameSizeMac. Only - sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Counts the number of times the system has resumed from power suspension. - Counting is reset each time Chrome restarts. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - - - - olka@chromium.org - maxmorin@chromium.org - - Device status received during TrackAudioRenderer initialization. This is a - specific case of Media.Audio.Render.OutputDeviceStatus histogram. - - - - - - - - - olka@chromium.org - maxmorin@chromium.org - - Device status received by TrackAudioRenderer when switching the output - device. This is a specific case of Media.Audio.Render.OutputDeviceStatus - histogram. - - - - - - Removed as of Aug 2018. - - henrika@chromium.org - - Reports the system uptime in hours for Mac OS X devices. Only sampled when - Media.Audio.InputStartupSuccessMac reports 'Failure'. - - - - - - - - - olka@chromium.org - maxmorin@chromium.org - - Device status received during WebRTCAudioRenderer initialization. This is a - specific case of Media.Audio.Render.OutputDeviceStatus histogram. - - - - - - - - - olka@chromium.org - maxmorin@chromium.org - - Device status received by WebRTCAudioRenderer when switching the output - device. This is a specific case of Media.Audio.Render.OutputDeviceStatus - histogram. - - - - - dalecurtis@chromium.org - Bits per channel of HTML5 audio sample data. - - - - guidou@chromium.org - olka@chromium.org - - Whether there is input audio glitches due to dropped input audio data or - not. Sampled when a low-latency input audio stream is destructed. - - - - - guidou@chromium.org - olka@chromium.org - - The percentage of input audio data that was dropped at the browser/renderer - boundary due to for example buffer overflow in the writer side buffer or in - the socket. Reported at the destruction of low-latency audio input stream. - - - - - gudou@chromium.org - olka@chromium.org - - The percentage of input audio data blocks that had to be buffered because - there was not room in the shared memory ring buffer on the browser/renderer - boundary. This happens if the reading side hasn't read data in time. - Reported at the destruction of low-latency audio input stream. - - - - - - Removed as of Jan 2018. - - minyue@chromium.org - - Captures bit-exact audio repetitions with pre-defined look back time. As - soon as a repetition is detected, its look back time is reported. Ideally, - no reports should be generated. - - - - - - Removed 06/2019 in issue 975301. - - dalecurtis@chromium.org - Audio channel layout in HTML5 media. - - - - - - dalecurtis@chromium.org - Audio codec used in HTML5 media. - - - - dalecurtis@chromium.org - media-dev@chromium.org - Audio codec profile used in HTML5 media for AAC playback. - - - - henrika@chromium.org - webrtc-audio@google.com - - Error codes that AudioUnitRender() returns in AUAudioInputStream on Mac. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - Measures the time taken for AudioInputController:: - - - - - Removed as of 02/2017. - - dalecurtis@chromium.org - - Whether capture started successfully after an input stream startup was - requested. - - - - - guidou@chromium.org - olka@chromium.org - - Every 15 seconds during the lifetime of an audio input stream, the sound - level is measured, see AudioInputController::CheckAudioPower(). If the level - is below a certain threshold, it's considered "silence". Otherwise - it's considered "audio". This metric shows whether there was only - silence, only audio, or both, during the lifetime of a stream. If logged - before the first measurement, i.e. if the lifetime is less than 15 seconds, - "no measurement" is reported. If there is no audio data provided - by the OS during the lifetime of the stream, for example because of a bug, - measurements will not be performed and "no measurement" is - reported. - - - - - - Removed 06/2020. No longer needed. - - dalecurtis@chromium.org - Measures the time taken for AudioInputDeviceManager:: - - - - - Removed 06/2020. No longer needed. - - dalecurtis@chromium.org - Measures the time taken for AudioOutputController:: - - - - guidou@chromium.org - olka@chromium.org - - A boolean that reflects whether or not an error was reported during audio - rendering, reported after a stream has stopped, if it was started. - - - - - - - - - olka@chromium.org - guidou@chromium.org - armax@chromium.org - - Time interval from the output stream controller construction to its - destruction. - - - - - guidou@chromium.org - olka@chromium.org - - Whether an AudioOutputController succeeded in creating and opening an output - stream proxy. Only logged for the initial creation, subsequent re-creations - due to device change events are logged in the - Media.AudioOutputController.ProxyStreamCreationResultForDeviceChange - histogram. - - - - - guidou@chromium.org - olka@chromium.org - - Whether an AudioOutputController succeeded in creating and opening an output - stream proxy after receiving a default device change event. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Time spent waiting in AudioOutputController::WaitTillDataReady() if the data - was not initially available. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Whether playback started successfully after stream startup was requested. - - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Whether a low latency stream to be rendered through the resampler was opened - successfully or which type of fallback stream was used instead. In case a - fake fallback stream is used it means audio rendered through the resampler - will be muted. In case fallback fails entirely, renderer callback error will - be signalled. - - - - - marinaciocea@chromium.org - - This histogram is the 3nd potential failure step in - CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram - is input for - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult - histogram. - - - - - marinaciocea@chromium.org - - This histogram is the 1st potential failure step in - CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram - is input for - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult - histogram. - - - - - marinaciocea@chromium.org - - This histogram is the 2nd potential failure step in - CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram - is input for - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult - histogram. - - - - - marinaciocea@chromium.org - - This histogram is the last potential failure step in - CoreAudioUtil::GetPreferredAudioParameters. - - - - - marinaciocea@chromium.org - - This histogram is the 4nd potential failure step in - CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram - is input for - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult - histogram. - - - - - olka@chromium.org - - Records format used by AudioManager to create audio output stream proxy. If - a fake stream is created it results in muted audio playback. - - On Windows, the failure reasons that can lead to fake stream creation are - tracked with the following histograms: - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceEnumeratorResult - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult - Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult - - - - - henrika@chromium.org - olka@chromium.org - - Captures if render-side audio glitches are detected or not. Sampled when a - low-latency output audio stream is destructed. - - - - - - Removed Mar 2016 in favor of a new PipelineStatus code. - - scherkus@chromium.org - Captures statistics for various AudioRendererImpl events. - - - - armax@chromium.org - dalecurtis@chromium.org - guidou@chromium.org - olka@chromium.org - - Status of audio sink used by AudioRendererImpl. If not OK, a NullAudioSink - will be used for audio output instead. This is logged for every call to - AudioRendererImpl::Initialize, which generally occurs once per active audio - session (i.e., between a play and pause). If audio track changes are ever - enabled, it may additionally be called for every audio track change. - - - - - - Removed 02/2017. No longer needed. - - grunell@chromium.org - - The maximum number of simultaneous audio render streams over IPC created in - AudioRendererHost for a render process. Logged at render process shutdown. - - - - - - Removed 02/2017. No longer needed. - - grunell@chromium.org - - The maximum number of simultaneous audio render streams over IPC created in - AudioRendererHost for all render processes. Logged at render process - shutdown. - - - - - dalecurtis@chromium.org - olka@chromium.org - - Percentage of AudioSyncReader::Read() calls where the renderer missed its - realtime deadline. - - - - - - Removed 06/2019 in issue 975301. - - dalecurtis@chromium.org - - Audio sample format in HTML5 media. Logged when Audio Decoder initializes. - - - - - - Removed 06/2019 in issue 975301. - - dalecurtis@chromium.org - Audio samples per second in HTML5 media. - - - - - Removed 06/2019 in issue 975301. - - dalecurtis@chromium.org - - Audio samples per second in HTML5 media (atypical values, in Hz). - - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - How long it take for the audio manager instance to be created by the audio - service, in case the audio service owns the audio manager. - - - - - marinaciocea@chromium.org - maxmorin@chromium.org - olka@chromium.org - - The time interval when the audio service has connections, computed from the - moment the first bind request is received to the moment when the last - connection is closed. - - - - - marinaciocea@chromium.org - maxmorin@chromium.org - olka@chromium.org - - The time interval when the audio service has no connections, computed from - the moment the last connection is closed until quit closure is called or a - new bind request is received. - - - - - - Removed 06/2018. Split into Media.AudioService.ObservedInitialDowntime and - Media.AudioService.ObservedDowntime2. - - marinaciocea@chromium.org - maxmorin@chromium.org - olka@chromium.org - - The audio service downtime, observed from the browser process. The downtime - interval is measured either from when the audio service listener is - initialized to the first audio service start, or from the audio service - shutdown to the next startup. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The audio service downtime, observed from the browser process. The downtime - interval is measured from the audio service shutdown to the next startup. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The audio service downtime, observed from the browser process. The downtime - interval is measured from when the audio service listener is initialized to - the first audio service start. - - - - - - Removed 10/2018. Covered by the more generic stats - ChildProcess.Crashed.UtilityProcessHash and - ChildProcess.Launched.UtilityProcessHash. - - marinaciocea@chromium.org - maxmorin@chromium.org - olka@chromium.org - - The termination status of the audio service process, observed from the - browser process. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The start result of the audio service, observed from the browser process. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The startup time of the audio service, observed from the browser process. - The startup time interval is measured from when a connect request results in - the audio service being created to the moment when the audio service is - started. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The uptime of the audio service, observed from the browser process. The - uptime interval is measured from when the audio service starts to when it is - shut down (either normally or through kill/crash). This metric includes - Media.AudioService.Uptime measurements, logged by the audio service on - normal shutdown. A difference between Media.AudioService.ObservedUptime and - Media.AudioService.Uptime indicates buggy audio service behavior. - - - - - - Removed on March 2020. - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The time interval between the moment when a client issues a system - information request to the audio service, and the moment it receives the - responce. Logged individually for each request type. - - - - - - Removed on March 2020. - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - The uptime of the audio service, observed from the audio service. The uptime - interval is measured from the audio service start to the audio service stop. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - State of the audio thread. A value of "started" is emitted once - the hang monitor has been initialized. If the thread is detected as hung - later, a value of "hung" is emitted. If the hung thread later - recovers a value of "recovered" is emitted. - - - - - - Removed July 2019. No longer needed. - - grunell@chromium.org - - State of the media stream audio track processing, sampled once during the - life time of a MediaStreamAudioProcessor. - - - - - - Removed January 2019. No longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - The result of autoplaying video elements in cross-origin iframes. - - - - - liberato@chromium.org - videostack-eng@chromium.org - - Record a count for each frame sent to the client by AVDA, separated by what - type of frame it is: Non Overlay, secure overlay, etc. - - - - - liberato@chromium.org - videostack-eng@chromium.org - - Record a count for each frame sent to the client by AVDA. True counts - indicate that the frame was an overlay (SurfaceView). False counts are for - Non Overlay frames. This will be deprecated in favor of - Media.AVDA.FrameInformation in M63. - - - - - - Removed 03/2016. No longer needed. - - watk@chromium.org - - The time that a bitstream buffer spends in AVDA's pending bitstream buffer - queue before it is fed to MediaCodec. - - - - - - Removed 10/2016. No longer needed. - - liberato@chromium.org - - Number of times that AVDA stopped decoding because MediaCodec failed to - provide a FORMAT_CHANGED message before sending decoded frames back. True - counts indicate instances where FORMAT_CHANGE was missed, while false - instances indicate any MediaCodec initialization by AVDA. - - - - - - Removed 10/2016. No longer needed. - - watk@chromium.org - - The number of concurrently running AndroidVideoDecodeAccelerators. Logged - during each AVDA initialization. - - - - - - Removed 10/2016. No longer needed. - - liberato@chromium.org - - Number of times that AVDA's deferred rendering encountered a virtual GL - context. True counts indicate virtual, false counts indicate not. - - - - - - Removed 06/2018. This has been renamed to - Media.CodecImage.SurfaceTextureGLOwner.WaitTimeForFrame and - Media.CodecImage.ImageReaderGLOwner.WaitTimeForFrame. - - liberato@chromium.org - - Time spent waiting for a frame to become available in a Non Overlay after - requesting that MediaCodec renders it. - - - - - - Removed 10/2019 in issue 1000058; no longer needed. - - hubbe@chromium.org - media-dev@chromium.org - Kb read by media demuxer from MultiBuffer cache. - - - - - Removed 10/2019 in issue 1000058; no longer needed. - - hubbe@chromium.org - media-dev@chromium.org - Kb read by from network into MultiBuffer cache. - - - - - Removed 10/2019 in issue 1000058; no longer needed. - - hubbe@chromium.org - dalecurtis@chromium.org - - Total number of bytes buffered over the lifetime of a WebMediaPlayer, - suffixed by type of playback. - - - - - - Removed 06/2019 in issue 975278. - - dalecurtis@chromium.org - - Whether a media response might be used to satisfy a future request. - - - - - chcunningham@chromium.org - mlamouri@google.com - media-dev@chromium.org - - Time spent between receiving a decodingInfo() call and resolving it. It only - record successful calls and ignores audio-only. - - - - - chcunningham@chromium.org - mlamouri@google.com - media-dev@chromium.org - - Time spent between receiving a decodingInfo() call and resolving it. It only - record successful calls and ignores audio-only. This is a subset of - Media.Capabilities.DecodingInfo.RequestTime.Video that only takes into - account clear content. - - - - - chcunningham@chromium.org - mlamouri@google.com - media-dev@chromium.org - - Time spent between receiving a decodingInfo() call and resolving it. It only - record successful calls and ignores audio-only. This is a subset of - Media.Capabilities.DecodingInfo.RequestTime.Video that only takes into - account encrypted content. - - - - - - Removed as of Dec 18, 2017. Replaced by - Media.GpuArcVideoDecodeAccelerator.InitializeResult. - - johnylin@chromium.org - - Counts of status values returned from calls to - ChromeArcVideoDecodeAccelerator::Initialize(). - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - The average number of delayed and dropped frames for the ChromeCast - application. Reported every 5 seconds. - - - - - - Removed 07/2015 in issue 508534. - - mfoltz@chromium.org - - The average number of displayed frames for the ChromeCast application. - Reported every 5 seconds. - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - Time needed to pre-buffer A/V data before the actual playback for the - ChromeCast application. - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - Time needed to buffer A/V data after an abort for the ChromeCast - application. - - - - - - Not collected as of M83. - - mfoltz@chromium.org - - Time needed to buffer A/V data after an underrun for the ChromeCast - application. - - - - - vikassoni@chromium.org - liberato@chromium.org - - Whether we exceeded the timeout in CodecBufferWaitCoordinator:: - WaitForFrameAvailable and will proceed without a frame ready. - - - - - vikassoni@chromium.org - liberato@chromium.org - - Time spent waiting for a frame to become available in a Non Overlay - (TextureOwner mode) so that MediaCodec can render it. This time is recorded - before the frame is rendered. - - - - - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut - - ericrk@chromium.org - liberato@chromium.org - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut - - - - - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame - - vikassoni@chromium.org - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame - - - - - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut - - ericrk@chromium.org - liberato@chromium.org - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut - - - - - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame - - liberato@chromium.org - - Removed 07/2019. This has been renamed to - Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame - - - - - cassew@google.com - media-dev@chromium.org - - Duration of decoder selection during config changes, measured from first - call to 'DecoderSelector::SelectDecoder' to - 'DecoderSelector::FinalizeSelection'. The HW/SW suffix indicates the type of - the decoder that was ultimately selected. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - Records events related to click through rate (CTR) calculation. - - The CTR can be calculated by computing "Interacted" / - "Displayed". "Interacted", for buttons, means that they - were clicked. For sliders, it will reflect any change in the internal state - and includes other events in addition to clicks. "Displayed" means - that the control element was meant to be displayed in the controls. It does - not mean that the user have seen the element so is not to be confused with - visibility. Furthermore, because the controls UI changes while loading, - "Displayed" is only computed when metadata are available unless - preloading was disabled on the element or the browser. - - - - - - Removed July 2017 in favor of Media.Controls.CTR.DownloadButton. - - mlamouri@chromium.org - nyquist@chromium.org - media-dev@chromium.org - - Records events and user interactions related to the download button shown on - media elements. - - - - - - Removed 07/2019 as no longer needed. - - beccahughes@chromium.org - media-dev@chromium.org - - Records the amount of time the overflow menu is displayed until the user - clicked on a menu item. The overflow menu is shown by clicking the three - dots on the media controls and is used to show more controls when there is - not enough space. This histogram will record up to 100 seconds with accuracy - to the second. - - - - - - Removed 07/2019 as no longer needed. - - beccahughes@chromium.org - media-dev@chromium.org - - Records the amount of time the overflow menu is displayed until the user - dismissed the menu without clicking on a menu item. The overflow menu is - shown by clicking the three dots on the media controls and is used to show - more controls when there is not enough space. This histogram will record up - to 100 seconds with accuracy to the second. - - - - - - Removed May 19 2016 in favor of Media.Controls.Show.{Audio,Video} - - mlamouri@chromium.org - - Record whether the default media controls were shown and why every time they - could be shown. - - - - - mlamouri@chromium.org - - Record whether the default media controls of an audio element were shown and - why every time they could be shown. Note that audio elements that were not - insterted to the DOM and do not have a controls attribute are not taken into - account. - - - - - mlamouri@chromium.org - - Record whether the default media controls of a video element were shown and - why every time they could be shown. - - - - - dalecurtis@chromium.org - - The state of the user selected virtual beamforming audio device on CrOS. - It's logged whenever the format of the audio input stream is queried, which - at least happens on stream startup, but could happen at other times as well. - - - - - liberato@chromium.org - tmathmeyer@chromium.org - - This enum allows us to count D3D11VideoDecoder specific crashes and - initialization failures. This is recorded whenever the decoder is - initialized or destroyed. - - - - - liberato@chromium.org - sandersd@chromium.org - tmathmeyer@chromium.org - - This enum measures whether or not d3d11 is supported and if not, what the - reason is. - - - - - - Removed Sep 15 2015 in favor of Media.DetectedAudioCodecHash - - jrummell@chromium.org - Audio codec used in HTML5 media. - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Audio codec used in HTML5 media. Reporting corrected in M51 to include all - detected audio codecs, not just those up to and including the first one - supported. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - Audio codec used in HTML5 media for a local file playback. - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Container used for HTML5 media. Views that include pre-M34 data will - categorize dash (38) and smooth streaming (39) in the "Other" - bucket. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - Container used for HTML5 media for a local file playback. - - - - - Removed 07/2019 in issue 975315. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected audio tracks in HTML5 media. Not all may be usable by the - player. - - - - - - Removed 07/2019 in issue 975315. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected text tracks in HTML5 media. Not all may be usable by the - player. - - - - - - Removed 07/2019 in issue 975315. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected video tracks in HTML5 media. Not all may be usable by the - player. - - - - - - Removed Sep 15 2015 in favor of Media.DetectedVideoCodecHash - - jrummell@chromium.org - Video codec used in HTML5 media. - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Video codec used in HTML5 media. Reporting corrected in M51 to include all - detected video codecs, not just those up to and including the first one - supported. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - Video codec used in HTML5 media for a local file playback. - - - - - Removed 10/2015 in favor of Permissions.Action. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the actions taken in the media infobar, which prompts the users for - device permission. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Count of dropped frames between pipeline start and stop. Media pipeline - starts/stops when an HTML5 video is loaded/unloaded respectively in the - browser. - - - - - - Removed 03/2017 in favor of Media.Duration2 with larger max bucket. - - scherkus@chromium.org - Duration in milliseconds of HTML5 media (when known). - - - - - Removed 06/2019. Not useful. - - dalecurtis@chromium.org - Duration in milliseconds of HTML5 media (when known). - - - - - Removed 12/2018 since we had enough data to make a decision. - - dalecurtis@chromium.org - media-dev@chromium.org - - Did IsResolutionSupportedForDevice() succeed or fail during - ID3D11VideoDevice::CreateVideoDecoder(). - - - - - - Removed 02/2020. Not useful. - - liberato@chromium.org - sandersd@chromium.org - - Whenever an error is logged from the DXVAVDA, this records the line in - dxva_video_decode_accelerator.cc where the failure occurred. - - - - - - Removed 12/2018 since we had enough data to make a decision. - - dalecurtis@chromium.org - media-dev@chromium.org - - Did IsResolutionSupportedForDevice() succeed or fail during - ID3D11VideoDevice::GetVideoDecoderConfig(). - - - - - - Removed 02/2020. Not useful. - - jbauman@chromium.org - sandersd@chromium.org - - Whenever an error is logged from the DXVAVDA picture buffer code, this - records the line in dxva_picture_buffer_win.cc where the failure occurred. - This histogram can only meaningfully be compared between different versions - of Chromium if no line numbers in that file changed between those versions. - - - - - liberato@chromium.org - sandersd@chromium.org - - This enum measures how often each of the various DXVAVDA PictureBuffer - display mechanisms are used. Each count represents the mechanism selected at - the end of DXVA::Initialize; i.e., there is one count per decoder. - - - - - liberato@chromium.org - tmathmeyer@chromium.org - sandersd@chromium.org - - Records how many times the DXVA VDA successfully initializes a D3D11 device - vs. D3D9 device. - - - - - sandersd@chromium.org - media-dev@chromium.org - Result of EME promises that were handled by Chromium code. - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - media-dev@chromium.org - addKey result - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - cancelKeyRequest result. - - - - xhwang@chromium.org - media-dev@chromium.org - - Size in KB of the last file successfully read by the CDM through CDM FileIO - before a specific error happens. This is reported only when the error - happens, which should be rare. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Size in KB of the first file successfully read by the CDM through CDM - FileIO. This is recorded once per CDM instance. - - - - - - Removed 08/2019, replaced with Media.EME.CdmFileIO.TimeTo.ReadFile. - - media-dev@chromium.org - The actual time spent by the CDM reading a file. - - - - jrummell@chromium.org - media-dev@chromium.org - - The actual time spent by the CDM accessing a file. This is only recorded for - successful operations. - - - - - - Removed 08/2019, replaced with Media.EME.CdmFileIO.TimeTo.WriteFile. - - media-dev@chromium.org - The actual time spent by the CDM writing a file. - - - - xhwang@chromium.org - media-dev@chromium.org - - The status of CDM host verification. This is reported per CDM load. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Chromium could support multiple versions of CDM interface. This metric - records the CDM interface version that the CDM created by Chromium uses. - This is recorded once per CDM instance. - - - - - xhwang@chromium.org - media-dev@chromium.org - - The error code of a library CDM load failure. Only reported on Windows. - - - - - xhwang@chromium.org - media-dev@chromium.org - The result from an attempt to load a library CDM. - - - - xhwang@chromium.org - media-dev@chromium.org - The time spent to load a library CDM. - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether the CDM instance is created successfully. Reported each time a CDM - instance creation is attempted, usually as a result of Javascript call of - createMediaKeys(). - - - - - xhwang@chromium.org - media-dev@chromium.org - The time it takes to create the CDM instance. - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether EME encrypted event has been fired. Every time a WebMediaPlayerImpl - object is created a "false" value is reported to provide a - baseline. Every time an encrypted event is fired, a "true" value - will be reported. Note that it is possible to have multiple encrypted events - during the lifetime of a WebMediaPlayerImpl object. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether encrypted media is enabled when requestMediaKeySystemAccess() is - called. User can enable and disable encrypted media in content settings. - Recorded when requestMediaKeySystemAccess() is called but will be reported - at most once per renderer process. - - - - - jrummell@chromium.org - media-dev@chromium.org - - The encryption scheme used by the audio stream in an HTML5 video. Reported - when metadata is available if the initial config is encrypted. - - - - - jrummell@chromium.org - media-dev@chromium.org - - The encryption scheme used by the video stream in an HTML5 video. Reported - when metadata is available if the initial config is encrypted. - - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - media-dev@chromium.org - generateKeyRequest result. - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether a given WebMediaPlayer instance, with a CDM attached, is played in - an incognito window or in Chrome OS guest mode. Players that never started - playback are excluded. Recorded once at time of player destruction. - - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - media-dev@chromium.org - KeyAdded event count. - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - media-dev@chromium.org - KeyError event count. - - - - xhwang@chromium.org - media-dev@chromium.org - System code count associated with key status. - - - - - Removed 02/2016 with removal of prefixed EME. - - xhwang@chromium.org - media-dev@chromium.org - - Key system support query status and result. Each enum value will be reported - at most once per renderer process. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether the CDM is available for the key system or not. In normal cases, - this is reported once per render process if the EME API is used. In rare - cases it could be reported more than once if the CDM is not available and - then is component updated. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Reported at most once during browser process shutdown the max number of - concurrent CDM processes at any time during the lifetime of that browser - process. Will NOT be reported if no CDM process has ever been created. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether MediaCrypto is available on a MediaDrm-based CDM. Reported once per - MediaDrmBridge creation. In normal cases it should always be available. - - - - - jrummell@chromium.org - media-dev@chromium.org - - The status of every attempt to obtain a pre-provisioned origin ID to be used - by MediaDrm. This will only be reported for applications that use - MediaDrmOriginIdManager. - - - - - jrummell@chromium.org - media-dev@chromium.org - - The number of pre-provisioned origin IDs available shortly after startup on - devices that do not support per-application provisioning. - - - - - jrummell@chromium.org - media-dev@chromium.org - - The number of pre-provisioned origin IDs available shortly after startup on - devices that support per-application provisioning. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether MediaDrmBridge supports the key system. Reported once per - MediaDrmBridge creation. In normal cases it should always be supported. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether connection error has happened for MojoCdm. Every time a MojoCdm - object is created a "false" value is reported to provide a - baseline. Every time a mojo connection error happened, a "true" - value will be reported, which typically means a remote CDM process crash. - - - - - - Renamed to Media.EME.EncryptedEvent in 10/2017. - - xhwang@chromium.org - media-dev@chromium.org - EME NeedKey event count. - - - - xhwang@chromium.org - media-dev@chromium.org - - Output protection query status and result. One query and one positive (no - unprotected external links) result (if any) are reported per CDM instance. - - - - - sandersd@chromium.org - media-dev@chromium.org - - Key system support query status and result, as reported by - RequestMediaKeySystemAccess. Each value will be reported at most once per - renderer process. - - - - - xhwang@chromium.org - media-dev@chromium.org - System code count in promise rejection. - - - - xhwang@chromium.org - media-dev@chromium.org - The time it takes to resolve a EME promise. - - - - jrummell@chromium.org - media-dev@chromium.org - - The net error or HTTP response code of provisioning requests made by - UrlProvisionFetcher on Android and Cast devices. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Whether the robustness level of any video capability in the supported - configuration passed into requestMediaKeySystemAccess() is empty. This is - specific to the Widevine key system. - - - - - - Removed 07/2019 as no longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - Records the reason why the Media Engagement data was cleared. Partial - changes and full wipeout will both be recorded as one event. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when the Media Engagement Preloaded List is checked whether a - string is present on that list. If the check was successful then the result - of the check is recorded in this histogram. If the check was not successful - then the reason for the check failing is recorded. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when data is loaded into the Media Engagement Preloaded List. If - the load is successful then "loaded" is recorded to this - histogram. If the load was not successful then the reason why is recorded to - this histogram. - - - - - - Removed 07/2019 as no longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - Time taken to load the Media Engagement Preloaded List. It should be - recorded once per load of the list which will be once per start up with - additional loads when the list is updated while running. - - - - - - Removed 07/2019 as no longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - Time taken to lookup an entry in the Media Engagement Preloaded List. This - is recorded for every lookup, regardless of its success. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The media engagement score recorded at the time of playback. It is converted - to a percentage so should be divided by 100 to get the actual score. It is - only recorded for playback that is either lacking an audio track or not - muted. - - - - - - Removed 11/2018 in Issue 900679 as we are no longer using this. - - beccahughes@chromium.org - media-dev@chromium.org - - Media engagement scores for each origin, recorded at Chrome startup. It is - converted to a percentage so should be divided by 100 to get the actual - score. - - - - - - Removed 07/2019 as no longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - Records creation and playback status of a Media Engagement Session. This is - recorded at the same time as the data is commited into the content settings - database. - - - - - - Removed 07/2019 as no longer needed. - - mlamouri@chromium.org - media-dev@chromium.org - - Records creation and playback status of a restored Media Engagement Session. - This is recorded at the same time as the data is commited into the content - settings database. Restored information are recorded in addition of regular - ones (Media.Engagement.Session). - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when the Media Engagement service doesn't determine a player to be - significant. If a player is not significant the reasons why will be - individually recorded to this histogram each time except for the first time - which is recorded to a different histogram. - - The significant state of a player is reevaluated any time the state of the - player changes (e.g. muted, playing/paused). If the player was not - considered signficiant and still is not then we will record the reasons why - in this histogram. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when the Media Engagement service doesn't determine a player to be - significant. If a player is not significant the reasons why will be - individually recorded to this histogram the first time only. - - The significant state of a player is reevaluated any time the state of the - player changes (e.g. muted, playing/paused). If the player was not - considered signficiant and still is not then we will record the reasons why - in this histogram. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when the Media Engagement service no longer determines a player to - be significant. If a player is no longer significant, the reasons why will - be individually recorded to this histogram. - - The significant state of a player is re-evaluted any time the state of the - player changes (e.g. muted, playing/paused). If the player was previously - considered significant and is no longer considered that we will record the - reasons why in this histogram. - - - - - - Removed 07/2019 as no longer needed. - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when the history is cleared and the media engagement data are - similarly cleared. It records the reduction in score for each affected - origin. The algorithm is made to reduce the score by 0.0 as much as possible - and if it fails, the score will actually become 0.0 so every reduction also - represent the value of the previous score. - - - - - - Removed May 2018; has been 32-bit for years now. - - dalecurtis@chromium.org - - Bits per channel of the hardware audio device which failed to open in low - latency mode and required high latency fallback. - - - - - - Removed 06/2019 in issue 975072. Not useful. - - dalecurtis@chromium.org - - Channel count of the hardware audio device which failed to open in low - latency mode and required high latency fallback. - - - - - - Removed 06/2019 in issue 975072. Not useful. - - dalecurtis@chromium.org - - Channel layout of the hardware audio device which failed to open in low - latency mode and required high latency fallback. - - - - - - Removed 06/2019 in issue 975072. Not useful. - - dalecurtis@chromium.org - - Samples per second of the hardware audio device which failed to open in low - latency mode and required high latency fallback. - - - - - - Removed 06/2019 in issue 975072. Not useful. - - dalecurtis@chromium.org - - Samples per second of the hardware audio device (atypical values, in Hz) - which failed to open in low latency mode and required high latency fallback. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Whether Chrome had to fallback to the high latency audio path or not. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when a Media Feed is loaded from the database. If there was an - error reading from the database then the result will include the reason. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when a Media Feed item is loaded from the database. If there was an - error reading from the database then the result will include the reason. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Records the size of the fetched feed when a Media Feed is periodically - fetched in the background. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when a Media Feed Item is checked against Safe Search. This happens - automatically when Chrome fetches the feed so long as the user has opted - into Safe Search checking. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average number of delayed and dropped frames for the Fling application. - Reported every 5 seconds. - - - - - - Removed 07/2015 in issue 508534. - - halliwell@chromium.org - - The average number of displayed frames for the Fling application. Reported - every 5 seconds. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to pre-buffer A/V data before the actual playback for the Fling - application. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to buffer A/V data after an abort for the Fling application. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to buffer A/V data after an underrun for the Fling application. - - - - - steimel@chromium.org - media-dev@chromium.org - - Records if the Global Media Controls device selector was available. Recorded - once per notification either when the device selector was shown or when the - notification disappears. - - - - - steimel@chromium.org - media-dev@chromium.org - - Records if the Global Media Controls device selector was opened. Recorded - once per notification either when the device selector was opened or when the - notification disappears. This histogram is only recorded if the device - selector was available. - - - - - steimel@chromium.org - media-dev@chromium.org - - Recorded each time a media session is dismissed or removed from the Global - Media Controls. Records the reason why it happened (e.g. user clicked the - dismiss button or playback stopped). - - - - - steimel@chromium.org - media-dev@chromium.org - - Recorded each time a paused media session is interacted with (e.g. playing - the media or clicking on the notification to go back to the tab). Records - the time passed since it was last interacted with (or since when it was - paused if this is the first post-pause interaction). - - - - - steimel@chromium.org - media-dev@chromium.org - - Recorded each time the Global Media Controls Device picker dialog is opened - and is populated with devices. Records the number of device options - displayed, possibly including the default fallback device. - - - - - steimel@chromium.org - media-dev@chromium.org - - Recorded each time the Global Media Controls dialog is opened. True if this - was repeat usage of the dialog (e.g. if it's not the first time the dialog - has been opened this session). - - - - - steimel@chromium.org - media-dev@chromium.org - - The focused state of the WebContents associated with the MediaSession that - the user is interacting with via the Global Media Controls. Recorded when - the user presses an action on the Global Media Controls dialog (e.g. play). - - - - - dcastagna@chromium.org - - Records when a context provider is acquired in media, and when it's released - because a context loss has been detected. - - - - - acourbot@chromium.org - chromeos-video-eng@google.com - - Counts of status values returned from calls to - GpuArcVideoDecodeAccelerator::Initialize(). - - - - - dcastagna@chromium.org - mcasas@chromium.org - - GpuMemoryBufferVideoFramePool is called with an unsupported VideoFrame pixel - format. Emitted on VideoFrame arrival. - - - - - - Removed in December 2019 because GpuVideoDecoderError is gone and - crbug.com/902968 is fixed. - - sandersd@chromium.org - Counts of video decode errors reported to GpuVideoDecoder. - - - - - Removed in December 2019 because GpuVideoDecoderError is gone and - crbug.com/902968 is fixed. - - posciak@chromium.org - Results of attempts to GpuVideoDecoder::Initialize(). - - - - vikassoni@chromium.org - liberato@chromium.org - - The error code returned when GetSharedContextState() fails or MakeCurrent() - on the SharedContextState fails. - - - - - - Removed May 2018; has been 32-bit for years now. - - dalecurtis@chromium.org - Bits per channel of the hardware audio device. - - - - - - dalecurtis@chromium.org - Channel count of the hardware audio device. - - - - - - dalecurtis@chromium.org - Channel layout of the hardware audio device. - - - - - - dalecurtis@chromium.org - Samples per second of the hardware audio device. - - - - - Removed 06/2019 in issue 975072. Not useful. - - dalecurtis@chromium.org - - Samples per second of the hardware audio device (atypical values, in Hz). - - - - - steimel@chromium.org - media-dev@chromium.org - - Records media key presses that are handled by the - HardwareKeyMediaController. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Whether a given WebMediaPlayer instance, after preload, started playback; - recorded once at time of player destruction. - - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Whether capture started successfully after a high-latency input stream - startup was requested. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The size of the Media History database. Recorded once on startup. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when Media History is initialized when the browser is started. This - is not recorded in incognito mode or if "save browsing history" is - disabled. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when Media History is recreated when the browser is started and the - Media History database has been corrupted to the point where we need to - delete it and start again. This is not recorded in incognito mode or if - "save browsing history" is disabled. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when Media History records a playback to the database. Playbacks - are recorded when the player is destroyed and are are recorded on a - per-player level and might be called multiple times on a single page. - Playbacks are not recorded in incognito mode or if "save browsing - history" is disabled. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded when Media History records a sessions to the database. Sessions are - recorded once per WebContents on navigation if there was playback on the - page. Playbacks are not recorded in incognito mode or if "save browsing - history" is disabled. - - - - - - Removed June 2017. Found that the MediaInfoLoader class (the only user of - this histogram) is no longer used by anyone. - - qinmin@chromium.org - - The time it takes to perform redirect tracking and a CORS access check while - preparing to play a media file. - - - - - cassew@google.com - media-dev@chromium.org - - Duration of initial decoder selection. Measured from first call to - 'DecoderSelector::SelectDecoder' to 'DecoderSelector::FinalizeSelection'. - The HW/SW suffix indicates the type of the decoder that was ultimately - selected. - - - - - - Removed 05/2015 in Issue 1141703002. FFmpeg is now statically linked. - - scherkus@chromium.org - - Errors returned by LoadLibraryEx on Windows while attempting to load - ffmpegsumo.dll. - - - - - tommi@chromium.org - webrtc-audio@google.com - - Error codes that we encounter while setting up an AUAudioInputStream on Mac. - - - - - - Removed and removed from code as of 02/2016. - - henrika@chromium.org - - Invalid input sample rate when calling AUAudioInputStream::Open on Mac. - - - - - henrika@chromium.org - webrtc-audio@google.com - - Duration in milliseconds of low-latency audio input streams. Sampled when - the stream is closed by the AudioInputController. - - - - - maxmorin@chromium.org - - Duration in milliseconds of low-latency audio input streams which never got - any callbacks. - - - - - - Removed from code on 05/2020. - - dalecurtis@chromium.org - sandersd@chromium.org - - Whether the WMPI data source is streaming (does not support range requests). - - - - - steimel@chromium.org - beccahughes@chromium.org - media-dev@chromium.org - - Recorded each time the Kaleidoscope First Run Experience is shown when - either the tab is closed or the FRE is completed. Records how far into the - FRE the user got before exiting (or completing). - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded each time the Kaleidoscope module is loaded on the New Tab Page - with whether the data was loaded from the server or whether it hit the - cache. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Recorded each time the Kaleidoscope module is loaded on the New Tab Page - with the time it takes to fetch the data from the server. - - - - - - - liberato@chromium.org - chcunningham@chromium.org - - Confusion matrix for UMA-reported regresssion tasks for media local learning - experiments. Each bucket is interpreted as follows: - - TrueNegative - prediction was negative, observation was negative. - FalseNegative - prediction was negative, observation was positive. - FalsePositive - prediction was positive, observation was negative. - TruePositive - prediction was positive, observation was positive. - - For those observations for which we could not make a prediction due to data - sparsity, the "no-prediction" buckets indicate whether the - observation was positive or negative. - - - - - - - liberato@chromium.org - chcunningham@chromium.org - - Confusion matrices, split out by the feature index used to train the model. - Each confusion matrix has 6 entries: - - TrueNegative - prediction was negative, observation was negative. - FalseNegative - prediction was negative, observation was positive. - FalsePositive - prediction was positive, observation was negative. - TruePositive - prediction was positive, observation was positive. - No-prediction Negative - no prediction made, observation was negative. - No-prediction Positive - no prediction made, observation was positive. - - The confusion matrix entry will also be labelled with a bucket number, which - for this histogram represents the index of the feature that was used. The - feature index matches |LearningTask::feature_descriptions| for the - appropriate task. - - - - - - - liberato@chromium.org - chcunningham@chromium.org - - Confusion matrices, split out by the total amount of training data used to - train the model. Each confusion matrix has 6 entries: - - TrueNegative - prediction was negative, observation was negative. - FalseNegative - prediction was negative, observation was positive. - FalsePositive - prediction was positive, observation was negative. - TruePositive - prediction was positive, observation was positive. - No-prediction Negative - no prediction made, observation was negative. - No-prediction Positive - no prediction made, observation was positive. - - The bucket number mentioned in the enum label indicates how much weight the - training set had. To convert from bucket number to an actual weight range, - one must know the particular settings in the corresponding LearningTask. - - Please see |LearningTask::max_reporting_weight| and - |LearningTask::num_reporting_weight_buckets| for the the appropriate task. - - - - - - Removed in favor of Media.Learning.BinaryThreshold.Aggregate.* - - - - liberato@chromium.org - chcunningham@chromium.org - - Confusion matrix for MediaCapabilities local learning experiment, using a - lookup table and the base MediaCapabilities features (resolution, frame - rate, video format). A positive outcome is smooth playback, while a negative - outcome is not smooth. For example, a False Negative indicates that we - predicted a negative result (not smooth playback), but we later observed - that the result was positive (smooth playback). - - For those observations for which we could not make a prediction due to data - sparsity, the "no-prediction" buckets indicate whether the - observation was positive or negative. - - This is very similar to the existing MediaCapabilities implementation, but - uses the same training set as other learners. - - The "BaseTable" variant uses a lookup table as the model, and uses - the original MediaCapabilities features (resolution, frame rate, video - format). - - The "BaseTree" variant uses ExtraTrees model and the same features - as the BaseTable variant. - - The "EnhancedTree" variant uses ExtraTrees, plus additional - features such as NetworkType. The exact set of features is still in flux, so - be sure to restrict reporting to a particular Chromium version. - - - - - dalecurtis@chromium.org - - Audio IO layer used by the Linux OS, sampled once at startup of the browser. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Load type of HTML5 media, such as URL, MediaSource and MediaStream. - - - - - Please list the metric's owners. Add more owner tags as needed. - - State of the WebRtc local renderer, sampled once during the lifetime of a - local renderer. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The reason why the lock screen media controls were hidden if they were - previously shown. Recorded when the controls are destroyed by the lock - screen (e.g. unlock, switch user, shutdown). - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Whether the lock screen media controls were shown and if they will not be - shown the reason why. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The action (e.g. pause) that a user clicked on the lock screen media - controls. - - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Whether capture started successfully after a low-latency input stream - startup was requested. - - - - - liberato@chromium.org - sandersd@chromium.org - tguilbert@chromium.org - - The time between MediaCodec::dequeueOutputBuffer() and the dispatch of the - corresponding VideoFrame from MediaCodecVideoDecoder. - - - - - dalecurtis@chromium.org - - The total watch time (see Media.WatchTime) of a given playback divided by - the number of rebuffering events that occured during that playback. - - - - - jrummell@chromium.org - media-dev@chromium.org - - Whether the content type provided to HTMLMediaElement would parse with - ParsedContentType or not. - - - - - - Removed and removed from code as of January 2019. - - ossu@chromium.org - grunell@chromium.org - - Whether or not the MediaElement is at a playback position of infinity when - checking if playback has ended. - - - - - mlamouri@google.com - media-dev@chromium.org - - Recorded when an HTMLMediaElement play() promise is rejected (handled or - not) with the type of rejection. - - - - - steimel@chromium.org - media-dev@chromium.org - - Whether or not the MediaKeysListener was able to successfully register a hot - key. Failure typically indicates that the hotkey was already registered by a - different application. - - - - - mcasas@chromium.org - wtlee@chromium.org - The errors HW video encode encounters in MediaRecorder. - - - - mcasas@chromium.org - wtlee@chromium.org - Whether HW video encode is used in MediaRecorder. - - - - henrika@chromium.org - webrtc-audio@google.com - - Heuristically detects if the user has muted the microphone or not. Measured - approximately four times per minute. - - - - - - Removed 08/2018. Histogram Eraser marked this histogram as unnecessary. See - https://crbug.com/871467 for details. - - henrika@chromium.org - - Level of the microphone volume measured in percent. This value can be larger - than 100% on Linux. Measured approximately four times per minute. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - midi-dev@chromium.org - Connected input port numbers on the initialization. - - - - - Removed 06/2019. - - toyoshim@chromium.org - midi-dev@chromium.org - Connected output port numbers on the initialization. - - - - - Removed 06/2019. - - toyoshim@chromium.org - midi-dev@chromium.org - - The final status of MidiManager on destruction. This can monitor unexpected - failures on initializing platform dependent MIDI stuff. - - - - - toyoshim@chromium.org - midi-dev@chromium.org - - Reports whether any data was sent or received by a MidiManager. Recorded - once per MidiManager instantiation, upon destruction. MidiManager is - instantiated when the first Web MIDI client starts a session, and destroyed - when the last client ends the session. - - - - - toyoshim@chromium.org - midi-dev@chromium.org - Reports sysex message size. - - - - toyoshim@chromium.org - midi-dev@chromium.org - - The MidiManager instance use count, but this is not intended to understand - the real API usage because this can be counted by feature scanning scripts - that are often used for footprinting. You may want to track SendReceiveUsage - to monitor only instances that actually send or receive MIDI messages. - - - - - sandersd@chromium.org - media-dev@chromium.org - - Records the number of active MojoVideoDecoderService instances that are - alive each time an instance becomes active. An instance is active if - Decode() has been called at least once. This provides an estimate of the - concurrent hardware resource requirements. - - - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - Delay between a DecodeBuffer (and encoded chunk) input and a decoded - VideoFrame being produced by the remote MojoVideoDecoder. Output once per - successful decode. - - - - - eugene@chromium.org - liberato@chromium.org - - Total number of instances of MojoVideoDecoder used by a page (i.e. render - frame) when an instance of MojoVideoDecoder encountered a decoding error or - a crash during the first 150 frames of a video stream. - - - - - eugene@chromium.org - liberato@chromium.org - - Total number of instances of MojoVideoDecoder used by a page (i.e. render - frame) when an instance of MojoVideoDecoder successfuly decode the first 150 - frames of a video stream. - - - - - - - wolenetz@chromium.org - media-dev@chromium.org - - Audio codec used in Media Source Extensions playback. Set when MediaSource - addSourceBuffer() is successfully called during playback. Also set twice - during a successful SourceBuffer changeType() operation. See issue 535738 - for reworking MSE codec histograms to record on each successfully parsed - initialization segment (possibly filtered to record only when actual new - codec configurations are parsed). - - - - - - Removed 05/2018. Splicing no longer performed on buffers with estimated - duration. See https://crbug.com/396634. - - chcunningham@chromium.org - - Categorizes MSE audio splicing by the type of duration used in the - overlapped buffer. - - - - - wolenetz@chromium.org - sandersd@chromium.org - media-dev@chromium.org - - Duration of config changes that include codec changes, measured from before - decoder flush until after the first output frame is returned. The HW/SW - suffix indicates the type of the decoder that was ultimately selected. - - - - - wolenetz@chromium.org - media-dev@chromium.org - - Amount of time taken to destroy one ChunkDemuxer object, not including - initial background task scheduling delay. - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Tracks if ShakaPackager metadata was detected in the MP4 'moov' atom during - MSE based media playback. Recorded for every 'moov' atom, which is expected - once per asset. Multiple assets may be played within the same MSE session. - - - - - - Removed 07/2019 in issue 975090. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected audio tracks in Media Source Extensions playback. Not all - may be usable by the player. - - - - - - Removed 07/2019 in issue 975090. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected text tracks in Media Source Extensions playback. Not all - may be usable by the player. This count includes only explicitly signalled - tracks in MSE initialization segments parsed from WebM or ISO BMFF - bytestreams. - - - - - - Removed 07/2019 in issue 975090. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of detected video tracks in Media Source Extensions playback. Not all - may be usable by the player. - - - - - wolenetz@chromium.org - media-dev@chromium.org - - For each MediaSource instance, records the type of thread that created the - instance. - - - - - - Deleted along with browser side MSE implementation. - - qinmin@chromium.org - timav@chromium.org - - Relative number of late audio frames wrt total number of audio frames in MSE - playback, multiplied by one million. The audio frame is considered late if - it might cause an underrun, i.e. comes from decoder when audio buffer is - already depleted. - - - - - - Deleted along with browser side MSE implementation. - - qinmin@chromium.org - timav@chromium.org - - Relative number of late video frames wrt total number of video frames in MSE - playback, multiplied by one million. The video frame is late if it missed - its presentation time as determined by PTS when it comes from decoder. The - rendering policy (i.e. render or skip) does not affect it. - - - - - wolenetz@chromium.org - sandersd@chromium.org - - Reports the number of consecutive empty samples in a sequence within a track - run. There can be zero or more such sequences in a track run, and each - sequence is reported separately. This metric is expected to inform a - heuristic to realistically bound the parsing complexity of track runs that - may contain empty samples. See https://crbug.com/907268. - - - - - wolenetz@chromium.org - sandersd@chromium.org - - Reports the number of empty samples within a track run. This metric is - expected to inform a heuristic to realistically bound the parsing complexity - of track runs that may contain empty samples. See https://crbug.com/907268. - - - - - wolenetz@chromium.org - sandersd@chromium.org - - Reports the size of each sample parsed. This metric is expected to inform a - heuristic to realistically bound the parsing complexity of track runs that - may contain empty or huge samples. See https://crbug.com/907268. - - - - - wolenetz@chromium.org - sandersd@chromium.org - - Reports the number of samples in each track run. This metric is expected to - inform a heuristic to realistically bound the parsing complexity of track - runs that may contain huge numbers of samples. See https://crbug.com/907268. - - - - - - Removed 07/2019 in issue 975898. - - wolenetz@chromium.org - media-dev@chromium.org - - Number of tracks specified to AddId() for Media Source Extensions playback. - May be called multiple times per element if playback is dynamically altered. - - - - - - Renamed to Media.LoadType. - - acolwell@chromium.org - - Whether Media Source Extensions is specified for playback of Media elements. - Sampled when media pipeline starts. - - - - - - Deleted along with browser side MSE implementation. - - qinmin@chromium.org - timav@chromium.org - - Duration of an uninterrupted MSE playback. This is the time interval between - the playback starts or resumes and the moment when user stops the playback - by pressing pause, initiating a seek etc. Measured in media time in - milliseconds. - - - - - - Deleted along with browser side MSE implementation. - - qinmin@chromium.org - timav@chromium.org - - Relative number of starvations wrt total number of frames in MSE playback, - multiplied by one million. Starvation happens when the player interrupts the - regular playback and asks for more data, conditions are player-specific. - - - - - - - wolenetz@chromium.org - media-dev@chromium.org - - Video codec used in Media Source Extensions playback. Set when MediaSource - addSourceBuffer() is successfully called during playback. Also set twice - during a successful SourceBuffer changeType() operation. See issue 535738 - for reworking MSE codec histograms to record on each successfully parsed - initialization segment (possibly filtered to record only when actual new - codec configurations are parsed). - - - - - - - wolenetz@chromium.org - media-dev@chromium.org - - Video codec used in Media Source Extensions playback if the media container - is MP4. Set when MediaSource addSourceBuffer() is successfully called during - playback. Also set twice during a successful SourceBuffer changeType() - operation. See issue 535738 for reworking MSE codec histograms to record on - each successfully parsed initialization segment (possibly filtered to record - only when actual new codec configurations are parsed). - - - - - - - wolenetz@chromium.org - media-dev@chromium.org - - Video codec used in Media Source Extensions playback if the media container - is WebM. Set when MediaSource addSourceBuffer() is successfully called - during playback. Also set twice during a successful SourceBuffer - changeType() operation. See issue 535738 for reworking MSE codec histograms - to record on each successfully parsed initialization segment (possibly - filtered to record only when actual new codec configurations are parsed). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The audio bit rate as reported by the Netflix application. May be reported - multiple times as network conditions change during playback. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of audio channels as reported by the Netflix application. May be - reported multiple times as network conditions change during playback. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average number of delayed and dropped frames for the Netflix - application. Reported every 5 seconds. - - - - - - Removed 07/2015 in issue 508534. - - halliwell@chromium.org - - The average number of displayed frames for the Netflix application. Reported - every 5 seconds. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Video bit rate as reported by the Netflix application. May be reported - multiple times as network conditions change during playback. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Video height as reported by the Netflix application. May be reported - multiple times as network conditions change during playback. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Whether the media notification (including ones for Cast sessions) is - displaying artwork. This is recorded when the artwork is updated by the - underlying media session. - - - - - takumif@chromium.org - openscreen-eng@google.com - media-dev@chromium.org - - Whether the Cast media notification is displaying artwork. This is recorded - a few seconds after a notification is shown for the first time, which is - different from when Media.Notification.ArtworkPresent is recorded. - - - - - takumif@chromium.org - openscreen-eng@google.com - media-dev@chromium.org - - The number of Cast media notifications that are currently being displayed. - This is recorded when a media notification starts being displayed. - - - - - takumif@chromium.org - openscreen-eng@google.com - media-dev@chromium.org - - Whether the Cast media notification is displaying certain types of metadata. - This is recorded a few seconds after a notification is shown for the first - time, which is different from when Media.Notification.MetadataPresent is - recorded. - - - - - takumif@chromium.org - openscreen-eng@google.com - media-dev@chromium.org - - The action (e.g. pause) that a user clicked on a Cast media notification - (including ones for Cast sessions). - - - - - mlamouri@chromium.org - media-dev@chromium.org - - The type of media notification the user clicked to go back to Chrome. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The number of media notifications that are currently being displayed - (including ones for Cast sessions). This is recorded when a media - notification starts being displayed. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - Whether the media notification (including ones for Cast sessions) is - displaying certain types of metadata. This is recorded when the metadata is - updated by the underlying media session. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The source of the underlying media session (e.g. ARC, web, Cast) that - displayed the media notification. This is recorded when a notification is - available to be shown. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The action (e.g. pause) that a user clicked on a media notification - (including ones for Cast sessions). - - - - - guidou@chromium.org - olka@chromium.org - - Duration of an audio output stream. Measured in AudioOutputController from - when a stream is started until it is stopped. A stream is stopped when it is - paused, closed (i.e. destructed), or when a device change event causes it to - be restarted. - - - - - mlamouri@google.com - media-dev@chromium.org - - Whether Pepper players have played sound through its lifetime. - - - - - ihf@chromium.org - posciak@chromium.org - Counts of video decode errors reported to plugin. - - - - sandersd@chromium.org - dalecurtis@chromium.org - - Counts every output picture emitted to a PPAPI client, categorized by size - and decoder type. Flash will only use platform decoders, but NaCl clients - can use either decoder type. - - - - - ihf@chromium.org - posciak@chromium.org - - Number of PictureBuffers/textures requested per hardware decoder creation. - This value varies by platform and video. A user visible video may trigger - multiple decoder creations (sometimes every 5 seconds) but would normally - not hold more than 2 sets of buffers at any given time in memory. - - - - - ihf@chromium.org - posciak@chromium.org - - Vertical video resolution rounded to the nearest bucket. (Corresponds - roughly to the number in 720p.) - - - - - prabhur@chromium.org - dalecurtis@chromium.org - - Status of the media pipeline at the end of its lifecycle suffixed by stream - and video decoder type. - - - - - xhwang@chromium.org - media-dev@chromium.org - - Status of the media pipeline starting process (including demuxer and - renderer initialization). If the media pipeline is destroyed during the - starting process nothing will be reported, but this should relatively rare. - - - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - Time for the platform-specific (set of) video decode acceleration command(s) - to be executed. Output once per decode request submit. - - - - - liberato@chromium.org - videostack-eng@chromium.org - - Total battery (0-100 percent) consumed by playback. When divided by - Media.PlaybackPower.ElapsedTime, this provides the average rate of battery - drain for that category of playback. Units are (total) percent. This is - recorded when an entire percent (or more) is consumed during playback. Since - devices have different battery sizes, methods of measuring battery, and - different power consumption rates, it's a good idea to filter by a specific - device type and OS version before trying to interpret these results. The - magnitude of these numbers, alone, is also likely hard to use, for this - reason. Instead, consider comparing A/B experiments to see if they get - larger or smaller. Playbacks under one msec are ignored. - - - - - liberato@chromium.org - videostack-eng@chromium.org - - Total time, in msec, elapsed while consuming the battery described by - Media.PlaybackPower.BatteryDelta. See that histogram for details. Recorded - when one or more percent of battery is consumed during playback. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average number of delayed and dropped frames for the PlayMovies - application. Reported every 5 seconds. - - - - - - Removed 07/2015 in issue 508534. - - halliwell@chromium.org - - The average number of displayed frames for the PlayMovies application. - Reported every 5 seconds. - - - - - - Removed 03/2020 in https://crbug.com/1053019. - - media-dev@chromium.org - - Indicates if a suspend initiated for preload=metadata was ideal. I.e. we did - not immediately resume after completing the suspend when signaling - ReadyState::HAVE_FUTURE_DATA. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Indicates the number of rebuffers a given watch time session had. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Tracks whether a web page allows content to be remoted. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Measured audio content transfer bitrate while remoting content. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Audio channel layout used while remoting content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Audio codec used while remoting content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Audio sampling rate while remoting audio content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Audio sampling rate while remoting audio content (atypical values, in Hz). - - - - - - Removed 11/2017 in issue 788940. - - miu@chromium.org - - The difference between the estimated transmission capacity and the media - bitrate when capacity is higher. - - - - - - Removed 11/2017 in issue 788940. - - miu@chromium.org - - The difference between the media bitrate and the estimated transmission - capacity when media bitrate is higher. - - - - - - Removed as no more poster image is being downloaded while remoting content. - - miu@chromium.org - - Measures the amount of time it took to ultimately fail to download a poster - image for an HTML5 video while remoting content. - - - - - - Removed as no more poster image is being downloaded while remoting content. - - miu@chromium.org - - Measures the amount of time it took to successfully download a poster image - for an HTML5 video while remoting content. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Measures the duration of each remoting session. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Tracks the trigger for starting a remoting session. - - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Tracks the trigger for stopping a remoting session. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Measures the duration of each remoting session shorter than 15 seconds. - - - - - - Removed 11/2017 in issue 788940. - - miu@chromium.org - - The estimated content bitrate (including both audio and video) when starting - a remoting session. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Measures how long, from the start of a remoting session, until content began - playing out on the remote device. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Measures how long, from the start of a remoting session, until a message was - received from the remote device indicating initialization succeeded. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Tracks whether audio or video or both are remoted. - - - - - Removed 11/2017 in issue 788940. - - miu@chromium.org - - The estimated transmission capacity when starting a remoting session. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Aspect ratio of video while remoting content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - - Measured video content transfer bitrate while remoting content. - - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Video codec used while remoting content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Video codec profile used while remoting content. - - - - miu@chromium.org - jophba@chromium.org - openscreen-eng@google.com - Video width while remoting content. - - - - posciak@chromium.org - Counts of video decode errors reported to RTCVideoDecoder. - - - - - Renamed to Media.RTCVideoDecoderInitDecodeSuccess. - - posciak@chromium.org - Results of attempts to RTCVideoDecoder::InitDecode(). - - - - - - mcasas@chromium.org - sprang@chromium.org - chromeos-gfx@chromium.org - - Indicates whether we were successful in initializing hardware video decoder - for use in the RTC pipeline. - - - - - kron@chromium.org - webrtc-video@google.com - - Initialization latency of the hardware video decoder that is used in the RTC - pipeline. - - - - - - - mcasas@chromium.org - sprang@chromium.org - chromeos-gfx@chromium.org - Video codec profile used in RTC video decoder. - - - - kron@chromium.org - webrtc-video@google.com - - Reinitialization latency of the hardware video decoder that is used in the - RTC pipeline. - - - - - - - mcasas@chromium.org - sprang@chromium.org - chromeos-gfx@chromium.org - - Indicates whether we were successful in initializing hardware video encoder - for use in the RTC pipeline. - - - - - - - mcasas@chromium.org - sprang@chromium.org - chromeos-gfx@chromium.org - Video codec profile used in RTC video encoder. - - - - emircan@chromium.org - - Indicates whether we were successful in preserving timestamps in hardware - video encoder session. It is tracked during the session and logged after it - ends. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - Time during which a media session has been active, in other words, the time - between an activation and deactivation, without counting time while it was - suspended. If a session is activated after being deactivated, there will be - two entries. For example, if a user plays a song but is interrupted by a - phone call, it will only account for the song playing time. - - - - - - Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. - - beccahughes@chromium.org - media-dev@chromium.org - - The number of times a media session abandon audio focus and where the - abandon audio focus call originated from. This is recorded every time a - media session abandons audio focus because it has stopped playing. - - - - - - Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. - - beccahughes@chromium.org - media-dev@chromium.org - - The number of times a media session requested audio focus and where that - focus request originated from. This is recorded every time a media session - requests audio focus because it wants to start playing. - - - - - - Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. - - beccahughes@chromium.org - media-dev@chromium.org - - The number of times a media session requested audio focus for a specific - audio focus type. This is recorded every time a media session requests a new - audio focus type. This may be because the session has started playing or the - type of media being played has changed. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - The number of times the user paused playback of a media session using other - means than the pause button on the page. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - The number of times the user started playback of a media session using other - means than the play button on the page. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - Indicate whether the native requestAudioFocus() call was successful. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - The number of times the user stopped a media session using other means than - the pause button on the page. - - - - - mlamouri@chromium.org - media-dev@chromium.org - - The number of times a media session is suspended and why it has been - suspended. - - - - - beccahughes@chromium.org - media-dev@chromium.org - - The number of times user interacts with MediaSession sorted by action type. - - - - - steimel@chromium.org - media-dev@chromium.org - - The focused state of the WebContents associated with the MediaSession that - the user is interacting with. Recorded when the user interacts with a - MediaSession (e.g. by pressing the play/pause key on their keyboard). - - - - - - Removed 07/2019 in issue 975367. - - media-dev@chromium.org - - Whether a SRC= playback had a poster set at load() when the effective - preload type is "auto". Note that this includes audio playbacks, - since we do not have track metadata at load(); audio elements never have - posters. - - - - - - Removed 07/2019 in issue 975367. - - media-dev@chromium.org - - Whether a SRC= playback had a poster set at load() when the effective - preload type is "metadata". Note that this includes audio - playbacks, since we do not have track metadata at load(); audio elements - never have posters. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Video codec used in plain src= (not MSE) HTML5 media if the media container - is MP4. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Video codec used in plain src= (not MSE) HTML5 media if the media container - is WebM. - - - - - - - mlamouri@google.com - media-dev@chromium.org - - The duration of the user gesture (how long their finger is down), recorded - at the end of each drag gesture. This histogram is split according to the - width of the slider track in CSS px - see histogram name suffix. - - - - - - - mlamouri@google.com - media-dev@chromium.org - - The net distance the media scrubber moved, recorded at the end of each drag - gesture, as a percentage of the width of the slider track. This histogram is - split according to the width of the slider track in CSS px - see histogram - name suffix. - - - - - - - mlamouri@google.com - media-dev@chromium.org - - The sum of absolute distances the media scrubber incrementally moved, - recorded at the end of each drag gesture, each measured as the change in - media current time. If the scrubber was dragged back and forth before being - released, this will be larger than the value recorded for - Media.Timeline.DragTimeDelta (and may even be larger than the media - duration), otherwise it will be the same as DragTimeDelta. This histogram is - split according to the width of the slider track in CSS px - see histogram - name suffix. - - - - - - - mlamouri@google.com - media-dev@chromium.org - - The net distance the media scrubber moved, recorded at the end of each drag - gesture, measured as the change in media current time. This histogram is - split according to the width of the slider track in CSS px - see histogram - name suffix. - - - - - - - mlamouri@google.com - media-dev@chromium.org - - The type of user gesture, recorded at the end of each input sequence. For - example holding down the right arrow key with the scrubber focused will only - be logged as a single event. This histogram is split according to the width - of the slider track in CSS px - see histogram name suffix. - - - - - - Removed from code as of 07/2019. - - - - mlamouri@google.com - media-dev@chromium.org - - The width of the media timeline track in CSS pixels, recorded the first time - a media element with controls starts playing (strictly speaking, it's the - width in CSS pixels ignoring CSS transforms, multiplied by pageZoomFactor, - but deliberately ignoring pinch zoom's pageScaleFactor). - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Time in milliseconds from when WebMediaPlayerImpl starts loading until the - first video frame has been shown. - - - - - - Removed from code 2018/11/29. - - hubbe@chromium.org - media-dev@chromium.org - - Time in milliseconds from when WebMediaPlayerImpl starts loading until the - first video frame has been shown IFF six or more videos are loading in - parallel. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Time in milliseconds from when WebMediaPlayerImpl starts loading until - metadata is known. - - - - - - Removed from code 2014/6/18. - - scherkus@chromium.org - - Time in milliseconds from HTML5 media pipeline creation to playing event. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Time in milliseconds from when WebMediaPlayer starts loading until it has - buffered enough to start playback. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - scherkus@chromium.org - Size of HTML5 media (when known), in MB. - - - - - Removed 06/2019 in issue 975278. - - dalecurtis@chromium.org - - Reasons a media response won't be used to satisfy a future request. - - - - - - Removed Feb 2017. Media.UnderflowDuration provides more useful counts. - - dalecurtis@chromium.org - - The number of times a src= playback has underflowed; i.e. ran out of data. - - - - - - Removed Aug 2017. Media.UnderflowDuration2.SRC removes zero-weighting so - that we only report actual underflows. - - dalecurtis@chromium.org - - The amount of time taken to leave the underflow state (i.e. resume playback) - for src= playbacks. - - - - - - Removed Aug 2017. Media.UnderflowDuration2.EME removes zero-weighting so - that we only report actual underflows. - - media-dev@chromium.org - - The amount of time taken to leave the underflow state (i.e. resume playback) - for Encrypted Media Extensions (EME) based playbacks. - - - - - - Removed Aug 2017. Media.UnderflowDuration2.MSE removes zero-weighting so - that we only report actual underflows. - - dalecurtis@chromium.org - - The amount of time taken to leave the underflow state (i.e. resume playback) - for Media Source Extensions (MSE) based playbacks. - - - - - - - - - dalecurtis@chromium.org - - The amount of time taken to leave the underflow state (i.e. resume playback) - for playbacks. This doesn't report initial zero samples, which was - previously used to compensate for playbacks that don't rebuffer. - - - - - - Replaced with Media.URLScheme2 which is only recorded for src=URL playbacks - instead of including MediaSource playbacks which are always blob. - - media-dev@chromium.org - - URL scheme used with HTML5 media. (each URL provides one sample) - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - URL scheme used with HTML5 media; only recorded for src=URL playbacks and - not for Media Source Extensions playbacks. Each URL provides one sample. - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - The codec-specific delegate in VaapiVideoDecoder has returned an error from - Decode(). This could be a parse error, or a VA error itself. - - - - - mcasas@chromium.org - chromeos-gfx-video@google.com - - Whether the creation of VaapiWrapper succeeded or not inside - VaapiVideoDecoder. - - - - - mcasas@chromium.org - chromeos-gfx-video@google.com - - Whether the call to VaapiWrapper's VADisplayState::Initialize() succeeded or - not. - - - - - - Removed as of 08/2020. - - hiroh@chromium.org - chromeos-gfx@chromium.org - - Count of VAAPI errors that occur inside the VaapiWrapper due to VPP - functionality needed by the VaapiImageProcessor. - - - - - - Replaced by Media.VaapiMjpegDecodeAccelerator.VAAPIError as of 08/2020. - - andrescj@chromium.org - chromeos-gfx@chromium.org - - Count of VAAPI errors that occur inside the VaapiWrapper due to decoding - functionality needed by the VaapiMjpegDecodeAccelerator. - - - - - andrescj@chromium.org - chromeos-gfx@chromium.org - - The response given to the client by VaapiJpegDecodeAccelerator for a decode - request. This is recorded when the decode succeeds or fails. The recorded - value corresponds to a MjpegDecodeAccelerator::Error. - - - - - - Replaced by Media.VaapiMjpegDecodeAccelerator.Vpp.VAAPIError as of 08/2020. - - kamesan@chromium.org - chromeos-gfx@chromium.org - - Count of VAAPI errors that occur inside the VaapiWrapper due to VPP - functionality needed by the VaapiMjpegDecodeAccelerator. - - - - - - Replaced by Media.VaapiImageDecodeAcceleratorWorker.VAAPIError as of - 08/2020. - - andrescj@chromium.org - chromeos-gfx@chromium.org - - Count of VAAPI errors that occur inside the VaapiWrapper due to - functionality needed by the VaapiJpegDecodeAcceleratorWorker. - - - - - wtlee@chromium.org - chromeos-gfx@chromium.org - - Result codes reported by jpeg encode using VA-API hardware jpeg encoder. - - - - - - Replaced by Media.VaapiJpegEncodeAccelerator.Vpp.VAAPIError as of 08/2020. - - wtlee@chromium.org - chromeos-gfx@chromium.org - - Count of VAAPI errors that occur inside the VaapiWrapper due to VPP - functionality needed by the VaapiJpegEncodeAccelerator. - - - - - - Replaced by Media.VaapiVideoDecodeAccelerator.VAAPIError as of 08/2020. - - mcasas@chromium.org - posciak@chromium.org - chromeos-gfx@chromium.org - - Error codes reported by video decode using VA-API hardware video decoder. - - - - - mcasas@chromium.org - chromeos-gfx-video@google.com - - Whether the creation of VaapiWrapper succeeded or not inside VaVDA. - - - - - - Removed as of 4/2015, partially replaced by Media.VAVDA.DecoderFailure. - - posciak@chromium.org - - Error codes reported by video decode using VA-API hardware video decoder. - - - - - - Replaced by Media.VaapiVideoEncodeAccelerator.VAAPIError as of 08/2020. - - posciak@chromium.org - - Error codes reported by video encode using VA-API hardware video encoder. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records the autoplay source of videos. This includes - Media.Video.Autoplay.Muted. - - - - - - Removed from code as of 07/2019. - - mlamouri@chromium.org - media-dev@chromium.org - - Records time from load starts until video starts based on autoplay - attribute. - - - - - mlamouri@google.com - media-dev@chromium.org - Records the autoplay source of muted videos. - - - - - Removed as autoplay muted video by attributed is paused when going offscreen - since https://crbug.com/683141. - - mlamouri@chromium.org - media-dev@chromium.org - - Records the offscreen playing duration of a muted video autoplaying from - autoplay attribute. - - - - - - Removed as of M80, autoplaying muted videos can no longer be blocked. - - mlamouri@chromium.org - media-dev@chromium.org - - Records the reason why autoplay of muted videos was blocked. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records muted video started playing with play() become visible at some - point. The UMA for false is not complete since it is recorded in a - destructor which is garbage-collected. Please subtract - Media.Video.Autoplay.Muted "play() method" count with the true - count of this histogram to obtain the real false count. - - - - - mlamouri@google.com - media-dev@chromium.org - - Records the offscreen playing duration of a muted video autoplaying from - play() method. - - - - - mlamouri@google.com - media-dev@chromium.org - - Status of the unmute action on a video that autoplayed because it was muted. - - - - - - Removed from code as of 07/2019. - - mlamouri@chromium.org - media-dev@chromium.org - - Records time from load starts until video starts based on play method. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The time from the first camera access failure due to blocked system - permission before the last browser restart to startup after browser restart. - Logged once at browser startup if the system permission then is allowed. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The time from the last camera access failure due to blocked system - permission before the last browser restart to startup after browser restart. - Logged once at browser startup if the system permission then is allowed. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for camera. Logged once at browser startup. - For more information on the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for camera. Logged once at browser startup - if there was a failure accessing the camera due to blocked system permission - before the last browser restart. For more information on the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - grunell@chromium.org - engedy@chromium.org - hkamila@chromium.org - - The Mac system permission state for camera at the time of a user media - request. Logged when the system permission is checked. If the permission is - "not determined" this is logged, permission is requested, and the - resulting permission (from the user response) is also logged. For more - information on the values, see - https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. - - - - - - Removed from code as of 02/2020. - - mlamouri@google.com - media-dev@chromium.org - - Whether auto rotation of screen orientation is enabled by the user (if so - the user has not locked the screen orientation at the OS level, though the - orientation may still be locked by apps). Recorded each time - MediaControlsOrientationLockDelegate locks the screen orientation in - response to a video going fullscreen (or loading metadata whilst - fullscreen). - - - - - - Removed from code as of 07/2019. - - mlamouri@chromium.org - - Result of the orientation lock attempt when a video enters fullscreen. - - - - - - Removed from code as of 06/2020. - - mlamouri@chromium.org - - Status of the metadata when attempting to lock the screen orientation for a - fullscreen video. - - - - - - Removed as of 11/2018 -- no longer used and expensive to monitor. - - dalecurtis@chromium.org - media-dev@chromium.org - - Records the time distance between consequent keyframes in a video. The new - value is recorded for each video key frame decoded. - - - - - eugene@chromium.org - videostack-eng@chromium.org - - Video playback roughness for a 100s interval. Suffixed by the framerate. - - - - - - Removed as of 01/18/2017 in issue 670150. Replaced by - Media.Video.TimeFromForegroundToFirstFrame.DisableTrack and - Media.Video.TimeFromForegroundToFirstFrame.Paused. - - dalecurtis@chromium.org - media-dev@chromium.org - - Records the time between the moment when the video element is brought to the - foreground and when the video frame compositor outputs the next frame. - - - - - - Removed as of 06/2019 -- no longer used after background track disable has - launched. - - dalecurtis@chromium.org - media-dev@chromium.org - - Records the time between the moment when the video element that had video - track disabled in the background is brought to the foreground and when the - video frame compositor outputs the next frame. Recorded even if disabling - video track in the background is turned off to collect data for the control - group. - - - - - - Removed as of 06/2019 -- no longer used after background track disable has - launched. - - dalecurtis@chromium.org - media-dev@chromium.org - - Records the time between the moment when the video element that was paused - in the background is brought to the foreground and when the video frame - compositor outputs the next frame. Recorded even if disabling pausing video - in the background is turned off to collect data for the control group. - - - - - mcasas@chromium.org - - Video Capture Device captured aspect ratio, as a rounded integer multiplied - by 100. The collection is made in the VideoCaptureController upon reception - of the first frame. - - - - - mcasas@chromium.org - - Counts appearances of Blacklisted Video Capture devices during enumeration. - This collection happens during first enumeration in the appropriate - platforms' VideoCaptureDeviceFactory. - - - - - guidou@chromium.org - armax@chromium.org - - Time it takes from the moment that a VideoCaptureController is requested to - start to the moment the first video frame arrives at - VideoCaptureController::OnFrameReadyInBuffer(). - - - - - mcasas@chromium.org - guidou@chromium.org - armax@chromium.org - - Breaks down the events counted in Media.VideoCaptureManager.Event bucket - "Stopping video capture due to error" by the origin of the error. - This allows narrowing down what is causing errors. An event for this - histogram is emitted once for each time a client disconnects from a video - capture session because the session has reported an error. - - - - - mcasas@chromium.org - guidou@chromium.org - armax@chromium.org - - An event for this histogram is emitted once for each time a video frame is - dropped on the way from a capture source, e.g. a webcam, to a corresponding - media::VideoCaptureController instance running in the Browser process. If - more than - |VideoCaptureController::max_consecutive_frame_drop_for_same_reason_count()| - frames are dropped consecutively for the same reason, no more events for the - same reason will be counted for that session until either a frame is - delivered successfully or the reason for the frame dropping changes. - - - - - mcasas@chromium.org - guidou@chromium.org - armax@chromium.org - - Video Capture Device frame rate requested by VideoCaptureManager on - AllocateAndStart(). The collection is made in the VideoCaptureController - upon reception of the first frame. - - - - - - Removed as of 10/2014 in issue 422822. Replaced by - Media.VideoCaptureManager.Event and the two new values 3 and 4 in the enum - VideoCaptureEvent. - - grunell@chromium.org - mcasas@chromium.org - - Whether any frames were received during a video capture session. This metric - is recorded when a video source is stopped. - - - - - mcasas@chromium.org - - Video Capture Device captured frame height in pixels. The collection is made - in the VideoCaptureController upon reception of the first frame. - - - - - chfremer@chromium.org - - Indicates how many times Chrome has asked AVFoundation to enumerate devices - since the process start when zero devices are returned. This event is only - emitted for the first time that zero devices are returned since the process - start. This is used in the context of investigating http://crbug.com/582931. - - - - - perkj@chromium.org - - MacBook hardware version used when Chrome cannot enumerate a video device. - This is used for tracking http://crbug.com/582931. - - - - - perkj@chromium.org - - Number of video capture devices detected by Chrome during device - enumeration. Zero devices indicate a problem since all MacBooks should have - a built-in camera. This is used for tracking http://crbug.com/582931. - - - - - chfremer@chromium.org - - Counts events that are emitted in the context of attempting to mitigate the - issue of no cameras being found on Macbooks by restarting the video capture - service and retrying to obtain device infos, see http://crbug.com/582931. - - - - - chfremer@chromium.org - - An event for this histogram is emitted when a video capture session drops - more than - |VideoCaptureController::max_consecutive_frame_drop_for_same_reason_count()| - consecutive video frames for the same reason. After this event is emitted - once, no additional events are emitted for consecutively dropped frames for - the same reason until the count is reset by either a frame being delivered - successfully or a frame being dropped for a different reason. See also - Media.VideoCapture.FrameDrop. - - - - - - Removed 10/2014 in Issue 660493002. - - mcasas@chromium.org - - Pixel format provided by a Video Capture Device. The collection is made in - the VideoCaptureController upon reception of the first frame. - - - - - mcasas@chromium.org - - Video Capture Device captured frame width in pixels. The collection is made - in the VideoCaptureController upon reception of the first frame. - - - - - chfremer@chromium.org - - Indicates which video capture backend is used on Windows. A count is - recorded each time a new VideoCaptureDeviceFactoryWin instance is created. - - - - - chfremer@chromium.org - - Counts number of times taking a still image on Windows fails/succeeds. - - - - - chfremer@chromium.org - - Counts how many retries are needed for calls to MediaFoundation function - GetAvailableDeviceMediaType before getting a result different from - MF_E_INVALIDREQUEST or giving up. - - - - - guidou@chromium.org - armax@chromium.org - - Counts how many retries are needed for calls to MediaFoundation function - GetDeviceStreamCategory before getting a result different from - MF_E_INVALIDREQUEST or giving up. - - - - - guidou@chromium.org - armax@chromium.org - - Counts how many retries are needed for calls to MediaFoundation function - GetDeviceStreamCount before getting a result different from - MF_E_INVALIDREQUEST or giving up. - - - - - - Removed July 30th. This is no longer used. - - mcasas@chromium.org - - Video Capture and device enumeration/monitoring API used for Mac OS Lion or - later. Collection is made only once when the flags are parsed and the - appropriate library selected and/or loaded, successfully or not. - - - - - henryhsu@chromium.org - - Indicates whether we were successful in initializing hardware jpeg decoder - for attempts to VideoCaptureGpuJpegDecoder::Initialize(). - - - - - mcasas@chromium.org - Measures the time taken for VideoCaptureManager:: - - - - chfremer@chromium.org - mcasas@chromium.org - - Counts video capture event, such as start and stop capture. Note that the - ideal case is 50% start events and 50% normal stop events. - - - - - - Removed 07/2017 in favor of the more differentiated durations. - - chfremer@chromium.org - - Measures the duration from the time the Browser connected to the video - capture service to the time it closed the connection. - - - - - chfremer@chromium.org - - Measures the duration from the time the Browser connected to the video - capture service to the time it closed the connection. Entries are only - logged if the service was used for creating an actual capture session as - opposed to enumerating devices only. - - - - - chfremer@chromium.org - - Measures the duration from the time the Browser connected to the video - capture service to the time it closed the connection. Entries are only - logged if the service was used for enumerating devices only, but not for - creating an actual capture session. - - - - - chfremer@chromium.org - - Measures the duration from the time the Browser connected to the video - capture service to the time the connection was lost. - - - - - - Removed 07/2017 in favor of the more differentiated durations. - - chfremer@chromium.org - - Measures the duration from the time the Browser last closed or lost - connection to the video capture service to the time it reconnects. - - - - - chfremer@chromium.org - - Measures the duration from the time the Browser last closed or lost - connection to the video capture service to the time it reconnects. This - duration only gets logged for reconnects after usage of the service for - capture (as opposed to enumeration-only usage). - - - - - chfremer@chromium.org - - Measures the duration from the time the Browser last closed or lost - connection to the video capture service to the time it reconnects. This - duration only gets logged for reconnects after enumeration-only usage of the - service. - - - - - chfremer@chromium.org - - Counts video capture service events, such as startup, shutdown, and - connection lost. - - - - - - - dalecurtis@chromium.org - Video codec used in HTML5 media. - - - - - Removed 03/2020 in https://crbug.com/1053030. We have this in UKM. - - dalecurtis@chromium.org - Video codec profile used in HTML5 media. - - - - - Removed 11/2016 in issue 2506533002. - - scherkus@chromium.org - Coded aspect ratio of HTML5 video. - - - - - Removed 11/2016 in issue 2506533002. - - scherkus@chromium.org - Coded width of HTML5 video. - - - - - Removed 03/2020 in https://crbug.com/1053030. - - dalecurtis@chromium.org - - Pixel format color range of HTML5 video. Emitted on video load. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Whether Chrome had to fall back to a secondary video decoder after the - primary decoder failed reinitialization. - - - - - - - - - chcunningham@chromium.org - media-dev@chromium.org - - Indicates whether we were successful performing some database operation. See - suffix VideoDecodeStatsDBOperations. - - - - - - - - - chcunningham@chromium.org - media-dev@chromium.org - - Indicates duration of time performing some database operation. - - - - - - Replaced by Media.VideoFramePixelFormat 05/2015. - - mcasas@chromium.org - Pixel format used in HTML5 video. Emitted on video load. - - - - - Removed 03/2020 in https://crbug.com/1053032. - - hubbe@chromium.org - media-dev@chromium.org - Video frame color space. Emitted for each video frame. - - - - - Replaced by Media.VideoPixelFormatUnion 08/2015. - - mcasas@chromium.org - watk@chromium.org - Pixel format used in HTML5 video. Emitted on video load. - - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - Delay between a VideoFrame being decoded and it being consumed by the OS - presentation API (on ChromeOS, this includes the display controller too). - - - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - Delay between a VideoFrame being decoded and it being handed over to the - CompositorFrameSink, essentially capturing the buffering in the Renderer. - This value is strictly included in Media.VideoFrameSubmitter - - - - - xhwang@chromium.org - media-dev@chromium.org - - The height of the first video frame in an HTML5 video. Reported when the - first video frame is available. - - - - - mlamouri@google.com - peconn@chromium.org - media-dev@chromium.org - - Every time a video persistence session could be triggered, it records the - result of the attempt. - - - - - mlamouri@google.com - media-dev@chromium.org - - Record the type of controls a persisted video is using. This is recorded - every time a video enters persistence mode - - - - - mlamouri@google.com - peconn@chromium.org - media-dev@chromium.org - - Records the length during which a video was in a persistent state. It is - recorded once per video persistence session. - - - - - mlamouri@google.com - peconn@chromium.org - media-dev@chromium.org - - Records the reason why a video persistence session has ended. - - - - - - Replaced by Media.VideoFormat 05/2015. - - scherkus@chromium.org - Pixel format used in HTML5 video. Emitted on video load. - - - - - Pixel format has been removed from demuxers. 06/2019 - - mcasas@chromium.org - emircan@chromium.org - - Pixel format used in capture and HTML5 video. Emitted on video load. - - - - - - - dalecurtis@chromium.org - media-dev@chromium.org - - Indicates how many cadence changes have occurred during playback, a zero - value is emitted at the beginning of playback. Subsequent values are emitted - during video rendering for each cadence change (up to a maximum of 10). - - - - - xhwang@chromium.org - media-dev@chromium.org - - Indicates whether video is rendering in low delay mode. It's recorded when a - video starts playing. - - - - - dalecurtis@chromium.org - Metadata rotation in mp4 videos. Emitted during demuxing. - - - - - Replaced by Media.VideoCapture.FramesReceived 09/2014. - - grunell@chromium.org - mcasas@chromium.org - - If any frames were received during a video capture session. It's recorded - when a video source is stopped. - - - - - - Removed 03/2020 in https://crbug.com/1053030. - - dalecurtis@chromium.org - Visible aspect ratio of HTML5 video. - - - - - Removed 03/2020 in https://crbug.com/1053030. - - dalecurtis@chromium.org - Visible width of HTML5 video. - - - - armax@chromium.org - guidou@chromium.org - olka@chromium.org - - Whether capture started successfully after a high-latency input stream - startup was requested. - - - - - - Removed 05/2016. - - dcastagna@chromium.org - Number of frame buffers used by Vpx decoder. - - - - - Removed 05/2016. - - dcastagna@chromium.org - - Number of frame buffers currently in use by both Vpx decoder and a - VideoFrame. - - - - - - Removed 11/2018 -- shows nothing interesting; it's been static for years. - - dalecurtis@chromium.org - Amount of time taken to decode one VP9 frame. - - - - sandersd@chromium.org - media-dev@chromium.org - - Whether a VTDecompressionSession is internally using hardware accelerated - decoding. - - - - - sandersd@chromium.org - media-dev@chromium.org - - Count of VideoToolbox initialization failure reasons. Successful - initializations are counted as a special failure type. The sum of successes - and failures gives a lower bound on the number of attempted initializations. - - - - - sandersd@chromium.org - media-dev@chromium.org - - Count of VTVDA session failure reasons. Successful initializations are - counted as a special failure type. Since only successfully initialized - session can fail, failures rates are computed as a simple ratio. - - - - - dalecurtis@chromium.org - - Watch time is defined as the amount of elapsed media time for audio+video - media aggregated per player instance. A minimum of 7 seconds of unmuted, - foreground media must be watched to start watch time monitoring. Watch time - is checked on a regular basis and reported to UMA upon one of the stop - events mentioned below or at player destruction if none occur prior. - - Any one of paused, hidden, or muted is sufficient to stop watch time metric - reports. Each of these has a hysteresis where if the state change is undone - within some time, the watch time will be counted as uninterrupted. - - Power events (on/off battery power) have a similar hysteresis, but unlike - the aforementioned properties, will not stop metric collection. - - Each seek event will result in a new watch time metric being started and the - old metric finalized as accurately as possible. - - - - - - Replaced by Media.AudioRendererImpl.SinkStatus in Nov 2018. - - olka@chromium.org - dalecurtis@chromium.org - - Status of audio sink provided to WebMediaPlayer. If not OK, null sink will - be used for audio output instead. - - - - - sandersd@chromium.org - tguilbert@chromium.org - - When an HLS manifest is found during loading (on Android only), and the - response is CORS cross-origin, this histogram records whether the response - included an Access-Control-Allow-Origin header. Such requests are likely to - be supported by fetch() if the mode is correctly configured. - - - - - sandersd@chromium.org - tguilbert@chromium.org - - When an HLS manifest is found during loading (on Android only), records - whether the request was CORS cross-origin. These are cases that could not be - implemented using fetch(). Note: subresources referenced by the manifest are - not considered; they may have different origins or CORS configurations. - - - - - sandersd@chromium.org - tguilbert@chromium.org - - When an HLS manifest is found during loading (on Android only), records - whether the request would be mixed content. These are cases that could not - be implemented using fetch(). Note: subresources referenced by the manifest - are not considered; they may have different origins. - - - - - - Removed because an overwhelming majority of pages do not set the crossorigin - attribute and as a result most HLS content is counted. Superseded by - Media.WebMediaPlayerImpl.HLS.HasAccessControl. - - sandersd@chromium.org - tguilbert@chromium.org - - When an HLS manifest is found during loading (on Android only), records - whether the request was CORS cross-origin or redirected between origins. - These are cases that may or may not be able to be implemented using fetch(), - depending on details of the redirection and the setting of the crossorigin - attribute. Note: subresources referenced by the manifest are not considered; - they may have different origins or CORS configurations. - - - - - - Removed in March 2020. - - wolenetz@chromium.org - - Amount of memory used by the WebMediaPlayerImpl and its components. - - - - - sandersd@chromium.org - media-dev@chromium.org - - Wall time of WebMediaPlayer playbacks. Each count represents one second of - media playback. Multiple WebMediaPlayer instances can together accumulate - watch time faster than real time. - - - - - - Removed 09/2018 since support for these containers has been deprecated. - - dalecurtis@chromium.org - - Media container extensions seen by WebView that are not supported by the - standard HTML5 playback path. This value is recorded every time a - WebMediaPlayer is created with one of the unsupported containers. - - - - - - Removed 01/2017 as Windows Core Audio is now the only audio input - implementation on Windows. - - henrika@chromium.org - - Whether Chrome is using Windows Core Audio for audio input or not. Updated - on Windows only when a low-latency audio input stream is created. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average number of delayed and dropped frames for the YouTube - application. Reported every 5 seconds. - - - - - - Removed 07/2015 in issue 508534. - - halliwell@chromium.org - - The average number of displayed frames for the YouTube application. Reported - every 5 seconds. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to pre-buffer A/V data before the actual playback for the - YouTube application. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to buffer A/V data after an abort for the YouTube application. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Time needed to buffer A/V data after an underrun for the YouTube - application. - - - - - mcasas@chromium.org - chromeos-gfx@chromium.org - - Error codes reported by libva (via VaapiWrapper) while being used from the - specified client name. {VaapiClientName} - - - - - - - - - - - - - - - - - vandebo@chromium.org - If a media scan was cancelled, the duration (in ms) it ran. - - - - vandebo@chromium.org - - The number of directories with media files found during a scan. - - - - - vandebo@chromium.org - - Duration in milliseconds taken to do a media scan that ran to completion. - - - - - vandebo@chromium.org - - The percentage of galleries accepted (not deselected) from the scan result - dialog. - - - - - vandebo@chromium.org - - The number of galleries added or updated in preferences after a scan. - - - - - vandebo@chromium.org - Various usage counts for media galleries. - - - - steimel@chromium.org - media-dev@chromium.org - - True if the MediaLauncherActivity was successfully able to open the file. - Recorded when the MediaLauncherActivity starts the CustomTabActivity. - - - - - steimel@chromium.org - media-dev@chromium.org - - The type of media that a user is opening via the MediaLauncherActivity. - - - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - Round trip time for a Cast app availability request. Can be suffixed with - Success or Failure. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Whether opening Cast channel succeeds or not. Recorded when all opening - channel attempts (including retry attempts) finish. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Errors encountered on a Cast channel. Recorded when a Cast channel fails to - open, or when an opened channel fails to respond to keepalive ping request - and times out. - - - - - btolsch@chromium.org - openscreen-eng@google.com - - The number of Cast devices available from the device cache at the time of a - new network connection. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - The number of connected Cast devices. Recorded when browser finishes - discovering Cast devices. Recording happens roughly once per hour. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - The number of known Cast devices. Recorded when browser finishes discovering - Cast devices. Recording happens roughly once per hour. - - - - - btolsch@chromium.org - openscreen-eng@google.com - The source of discovery for a newly-created Cast sink. - - - - muyaoxu@google.com - openscreen-eng@google.com - - The types of apps supported by the sender page. Recorded when requesting the - receiver to launch a new session. - - - - - muyaoxu@google.com - openscreen-eng@google.com - - The type of app that the receiver device choose to launch. Recorded when - receiving a receiver status response to the launch request. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken to fail to open a cast channel. Recorded when - one opening channel attempt fails. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken to successfully open a cast channel. Recorded - when one opening channel attempt succeeds. - - - - - takumif@chromium.org - muyaoxu@google.com - openscreen-eng@google.com - - Records whether audio is played on the receiver device. If not, then on the - sender side. Recorded when a new site-initiated mirroring session is - started. - - - - - takumif@chromium.org - openscreen-eng@google.com - Total time to launch a Cast Streaming mirror session. - - - - takumif@chromium.org - openscreen-eng@google.com - - Total length of a Cast Streaming mirror session of any type, including the - time spent in media remoting. - - - - - rwkeane@google.com - openscreen-eng@google.com - Total length of a Cast Streaming File mirror session. - - - - rwkeane@google.com - openscreen-eng@google.com - - Total length of a Cast Streaming Offscreen Tab mirror session. - - - - - rwkeane@google.com - openscreen-eng@google.com - Total length of a Cast Streaming Screen mirror session. - - - - rwkeane@google.com - openscreen-eng@google.com - - Total length of a Cast Streaming mirror session of type Tab and NOT of types - offscreen tab or local file. This includes the time spent in media remoting. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Whenever a Cast Streaming session fails to start, record the error - associated with the event. This is recorded only for the extension Cast MRP. - See MediaRouter.CastStreaming.Start.Failure.Native for the native MRP. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Whenever a Cast Streaming session fails to start, record the error - associated with the event. This is recorded only for the native Cast MRP. - See MediaRouter.CastStreaming.Start.Failure for the extension MRP. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Whenever a Cast Streaming session is successfully started, record if it was - for a Tab or Desktop mirroring session. - - - - - rwkeane@chromium.org - openscreen-eng@google.com - - Whenever a resource is loaded from the Media Router Component Extension, - this metric gets logged. The value for this metric is always true. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The pref value to enable the cloud services. Recorded whenever the Cast - dialog is opened. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The pref value to enable the cloud services. Recorded whenever the browser - is initialized for a regular (not incognito or guest) profile. - - - - - mfoltz@chromium.org - takumif@chromium.org - openscreen-eng@google.com - - The number of available DIAL devices. Recorded when browser finishes - discovering DIAL devices. Recording happens roughly once per hour. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The result of a DIAL CreateRoute request. Recorded when the user requests to - create a media route to a DIAL device. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The result of a DIAL app info request. Recorded when an app info request is - issued to a DIAL device. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The number of known DIAL devices. Recorded when browser finishes discovering - DIAL devices. Recording happens roughly once per hour. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The result of parsing a Cast SDK message in the DIAL media route provider. - Recorded when the DIAL media route prover finishes parsing a Cast SDK - message sent from a Cast-enabled webpage. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - Error encountered while parsing DIAL device description XML text. Recorded - when utility process returns an invalid DIAL device description object to - browser. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The result of a DIAL TerminateRoute request. Recorded the user requests to - terminate a DIAL media route. - - - - - takumif@chromium.org - openscreen-eng@google.com - Location the user clicked to open the Media Router dialog. - - - - takumif@chromium.org - openscreen-eng@google.com - - Records errors encountered by the Mirroring Service. If an error occurs - while media remoting, the service attempts to revert to mirroring. Otherwise - mirroring is terminated. - - - - - btolsch@chromium.org - openscreen-eng@google.com - - Network connection type reported by DiscoveryNetworkMonitor whenever it - detects a change in the set of networks connected to the host device which - may affect local discovery. - - - - - btolsch@chromium.org - openscreen-eng@google.com - - Time between network change events reported by DiscoveryNetworkMonitor. - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - The type of Presentation URL used in a PresentationRequest by a web page. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Logged when the Media Router starts a presentation according to the type of - presentation URL and the type of media sink. - - - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - Result of a request to a MediaRouteProvider to create a route. - CreateRoute.Result (without a suffix) is recorded for the extension or an - unknown MRP. - - - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - Result of a request to a MediaRouteProvider to join a route. - JoinRoute.Result (without a suffix) is recorded for the extension or an - unknown MRP. - - - - - - Removed in M77. Route controller is specific to the old WebUI Cast dialog, - and the new Views dialog does not have it. - - takumif@chromium.org - openscreen-eng@google.com - - Records whether the Media Route Provider succeeded or failed to create a - controller for a media route. - - - - - - - takumif@chromium.org - mfoltz@chromium.org - openscreen-eng@google.com - - Result of a request to a MediaRouteProvider to terminate a route. - TerminateRoute.Result (without a suffix) is recorded for the extension or an - unknown MRP. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Records how the major version of the Media Router component extension - compares to the major version of the browser. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Reason that the Media Router woke the Media Route Provider event page. - - - - - mfoltz@chromium.org - openscreen-eng@google.com - - Records the outcome of waking the Media Router component's event page. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The number of times a Media Router create route response succeeds or fails. - This breaks down the different failure types in to separate buckets. - - - - - - Removed in M77. Sink search is specific to the old WebUI Cast dialog, and - the new Views dialog does not have it. - - takumif@chromium.org - openscreen-eng@google.com - - The outcome of querying Media Route Providers for a sink by ID. - "Success" indicates that a sink was found. This is recorded when - the user attempts to cast to a sink with a manually entered ID. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The type of the Media Sink that media is being Cast to. Recorded each time - the user selects a Media Sink to start Casting. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The source of a Media Router session. This is recorded to keep track of what - kind of media is being streamed. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The file format of a local media Media Router session. This is recorded when - a casting session begins to keep track of what kind of media is being - streamed. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The file size of a local media Media Router session. This is recorded when a - casting session begins to keep track of what kind of media is being - streamed, specifically, whether it is a clip or a song, or a full length - film or podcast. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken from the user opening the Media Router dialog - to the user closing the dialog. This is only recorded if closing the dialog - is the first action the user takes. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken from the Media Router dialog showing the sink - list and being populated with at least one device to the user selecting a - device immediately after to create a new route. - - - - - takumif@chromium.org - openscreen-eng@google.com - The index of the sink that was selected in the sink list. - - - - takumif@chromium.org - openscreen-eng@google.com - - The number of times a session was successfully started versus failed. - - - - - takumif@chromium.org - openscreen-eng@google.com - The number of times a user stops different types of routes. - - - - takumif@chromium.org - openscreen-eng@google.com - - Counts the number of devices known and populated to the Media Router dialog - three seconds after the dialog loads. Always expected to be non-negative. - - - - - takumif@chromium.org - openscreen-eng@google.com - - This records how the Cast dialog was opened and what Cast mode was used - whenever a Cast session starts. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Whether the Cast toolbar icon is in its ephemeral state (shown only when the - feature is active), or is pinned to the toolbar by user pref / admin policy. - - - - - - Removed in M77. Route controller is specific to the old WebUI Cast dialog, - and the new Views dialog does not have it. - - takumif@chromium.org - openscreen-eng@google.com - - Duration in milliseconds it takes the WebUI route controls in the route - details view to be populated after the view is opened. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken from the user click to open the Media Router - dialog to initializing the dialog with data. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Duration in milliseconds taken from a user click to open the Media Router - dialog to the initial paint. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The first action taken by the user after opening the Media Router dialog. - - - - - takumif@chromium.org - openscreen-eng@google.com - - Whether the Cast toolbar icon is in its ephemeral state (shown only when the - feature is active), or is pinned to the toolbar by user pref / admin policy. - Recorded whenever the browser is initialized for a regular (not incognito or - guest) profile. - - - - - - Removed in M77. This histogram was for tracking whether the old WebUI Cast - dialog opened in sink list view or route details view. - - takumif@chromium.org - openscreen-eng@google.com - - The view that was shown when the Media Router dialog is initially opened. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The number of times the user selects a specific cast source type. - - - - - takumif@chromium.org - openscreen-eng@google.com - - The number of Media Sinks available for Casting a Presentation API URL to - local screens. Recorded at most once an hour, when the Wired Display Media - Route Provider reports an update on the sink count. - - - - - - Removed in M77. One day results for Android were 99.99% success, .01% - Exceeded Cache Size, and an even smaller fraction Exceeded Single Entry - Size. - - jkarlin@chromium.org - The outcome of Entry::WriteData in the memory cache. - - - - - - marinaciocea@chromium.org - maxmorin@chromium.org - olka@chromium.org - - A rough estimate of the private memory footprint of the audio service - process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - olka@chromium.org - guidou@chromium.org - - An amount of private memory of the audio service process placed in swap - (VmSwap). - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - fdoray@chromium.org - - The size of the resident memory in a audio service process. This is - influenced by factors we control (e.g. memory that is not accessed can be - swapped) and factors we don't control (e.g. an unrelated process using a lot - of memory can force memory in our process to be swapped). Recorded once on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - olka@chromium.org - guidou@chromium.org - - A rough estimate of the shared memory footprint of the audio service - process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - A rough estimate of the private memory footprint of the browser process - while an Android background task is running. Recorded once per background - task, with a random delay of 0s to 60s after it starts. Available only on - Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - An amount of private memory the browser process placed in swap (VmSwap) by - the browser process while an Android background task is running in Full - Browser Mode. Recorded once per background task, with a random delay of 0s - to 60s after it starts. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - The size of the resident memory in a browser process while an Android - background task is running. Recorded once per background task, with a random - delay of 0s to 60s after it starts. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - A rough estimate of the shared memory footprint of the browser process while - an Android background task is running. Recorded once per background task, - with a random delay of 0s to 60s after it starts. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - A rough estimate of the private memory footprint of the browser process - while the Android Offline Prefetch Android background task is running. - Recorded once per background task, with a random delay of 0s to 60s after it - starts. The same value is recorded into - Memory.BackgroundTask.Browser.PrivateMemoryFootprint, which aggregates all - task types. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - An amount of private memory the browser process placed in swap (VmSwap) by - the browser process while the Android Offline Prefetch Android background - task is running in Full Browser Mode. Recorded once per background task, - with a random delay of 0s to 60s after it starts. The same value is recorded - into Memory.BackgroundTask.Browser.PrivateSwapFootprint, which aggregates - all task types. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - The size of the resident memory in a browser process while the Android - Offline Prefetch Android background task is running. Recorded once per - background task, with a random delay of 0s to 60s after it starts. The same - value is recorded into Memory.BackgroundTask.Browser.ResidentSet, which - aggregates all task types. Available only on Android. - - - - - - - hanxi@chromium.org - hnakashima@chromium.org - - A rough estimate of the shared memory footprint of the browser process while - the Android Offline Prefetch background task is running. Recorded once per - background task, with a random delay of 0s to 60s after it starts. The same - value is recorded into Memory.BackgroundTask.Browser.SharedMemoryFootprint, - which aggregates all task types. Available only on Android. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - TBD. - - - - - Removed 06/2016 Replaced with Memory.Browser.Large2. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by the browser process. Recorded once per UMA - ping. Note the existence of Memory.Browser.Large, which doesn't have - overflow issues. TODO(rkaplow): This should be replaced with - Memory.Browser.Large2 in M54. - - - - - - Removed 03/2018. No direct replacement. - - bashi@chromium.org - kouhei@chromium.org - - The total committed memory used by the browser process. Recorded once per - UMA ping. - - - - - - Removed 07/2016 as it reports wrong numbers. crbug.com/629354. Replaced with - Memory.Browser.Large2 - - erikchen@chromium.org - - The private working set used by the browser process. Recorded once per UMA - ping. - - - - - - Removed 11/2017 Replaced with Memory.Browser.PrivateMemoryFootprint. - - bashi@chromium.org - kouhei@chromium.org - - The private working set used by the browser process. Recorded once per UMA - ping. - - - - - - - erikchen@chromium.org - chrome-analysis-team@google.com - - This metric is only recorded on iOS. This measures the sum of - PrivateMemoryFootprint and SharedMemoryFootprint, which is possible because - iOS is single-process. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint - but only recorded when UIApplication.sharedApplication.applicationState is - UIApplicationStateActive. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This metric is only recorded on iOS when - UIApplication.sharedApplication.applicationState is - UIApplicationStateActive. True if the sum of PrivateMemoryFootprint and - SharedMemoryFootprint is greater than 200MB. According to Apple, apps on - iPhone 6 and older devices get terminated by the OS if memory usage crosses - 200MB watermark, so it's important to keep the memory usage under 200MB. - "true" value may not show up on iPhone 6 and older devices if iOS - is strict about the advertised watermark. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint - but only recorded when UIApplication.sharedApplication.applicationState is - UIApplicationStateBackground. According to Apple, apps get terminated by the - OS if memory usage in background crosses 50MB watermark, so it's important - to keep the memory usage under 50MB. The timing of this metric will line up - so that it rarely occurs when the app is in the background. With a small - data set, the metrics might be biased in ways that we can't think of right - now. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint - but only recorded when UIApplication.sharedApplication.applicationState is - UIApplicationStateInactive. The timing of this metric will line up so that - it rarely occurs when the app is inactive. With a small data set, the - metrics might be biased in ways that we can't think of right now. - - - - - rkgibson@google.com - eugenebut@chromium.org - - Investigation into crbug.com/1102494 shows that OverscrollActionsController - is allocating thousands of objects in it's -initWithScrollView:. This is - likely because thousands of OverscrollActionsControllers are being - initialized. The theory is that there are users that have many many tabs, - causing many OverscrollActionsControllers to be allocated. This histogram - tests that theory by logging how many live OverscrollActionsControllers - there are. This is recorded every time histograms are uploaded. - - - - - rkgibson@google.com - eugenebut@chromium.org - - Investigation into crbug.com/1102494 shows that OverscrollActionsController - is allocating thousands of objects in it's -initWithScrollView:. This is - likely because thousands of OverscrollActionsControllers are being - initialized. The theory is that there are users that have many many tabs, - causing many OverscrollActionsControllers to be allocated. This histogram - tests that theory by logging how many open tabs there are. This is recorded - every time histograms are uploaded. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint - but recorded right after the app transitions into background. According to - Apple, apps get terminated by the OS if memory usage in background crosses - 50MiB watermark so it's important to keep the memory usage under 50MiB. - - - - - - - erikchen@chromium.org - chrome-analysis-team@google.com - - A rough estimate of the private memory footprint of the browser process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - erikchen@chromium.org - ssid@chromium.org - - An amount of private memory of the browser process placed in swap (VmSwap). - Available on Android, Linux and ChromeOS. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - fdoray@chromium.org - - The size of the resident memory in the browser process. This is influenced - by factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - erikchen@chromium.org - - A rough estimate of the shared memory footprint of the browser process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - TBD. - - - - - Removed 11/2017. No direct replacement, but - Memory.Renderer.PrivateMemoryFootprint is similar. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each chrome:// renderer process. Each - process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of active chrome:// renderer processes. Recorded once per UMA - ping. - - - - - - Removed as of Aug 2016. CompressibleString has been reverted once at - https://crrev.com/2227933002. - - hajimehoshi@chromium.org - - This records the frequency with which JavaScript source strings are - compressed and decompressed in foreground and background tabs. Compressing - runs 10 seconds after the tab goes background and decompressing runs when - JavaScript source string is required (e.g. V8 starts to compile). This - measurement is a preparation to introduce CompressibleString class for - JavaScript source strings to reduce Blink memory usage. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - - Available free memory until the system will be in a critical state. Critical - is as defined by the OS (swapping will occur, or physical memory will run - out, etc). - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - Time elapsed between the global state changes. - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - The global state of memory coordinator when a critical pressure notification - is received. - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - The global state of memory coordinator when a moderate pressure notification - is received. - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - The total private working set memory used by the browser and renderer - processes when the memory coordinator changes the global memory state. - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - Android: Records trim memory level when the global state is NORMAL. - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - Android: Records trim memory level when the global state is SUSPENDED. - - - - - - Obsolete as of 2/2017 - - bashi@chromium.org - - Android: Records trim memory level when the global state is THROTTLED. - - - - - thiabaud@google.com - lizeb@chromium.org - - Freelist size used by ClientDiscardableMemoryManager in the foreground only. - Recorded during |OnMemoryDump|. - - - - - thiabaud@google.com - lizeb@chromium.org - - Boolean metric which tracks whether or not discardable memory had already - been discarded when an attempt is made to lock it. - - - - - thiabaud@google.com - lizeb@chromium.org - - Effective memory used by ClientDiscardableMemoryManager in the foreground - only. Recorded during |OnMemoryDump|. - - - - - thiabaud@google.com - lizeb@chromium.org - - Virtual memory used by ClientDiscardableMemoryManager in the foreground - only. Recorded during |OnMemoryDump|. - - - - - reveman@chromium.org - thiabaud@google.com - - The discardable memory allocation size in KB. Recorded each time a new - discardable memory instance is created. - - - - - ericrk@chromium.org - - The size of the EGL_ANDROID_blob_cache cache file on disk. Recorded once per - Chrome launch, after the first page has loaded. - - - - - - Removed 12/2017. Replaced by Memory.Browser.PrivateMemoryFootprint. - - erikchen@chromium.org - - A rough estimate of the private memory footprint of the browser process. - - - - - - Removed 03/2018. - - bashi@chromium.org - - Amount of reclaimed memory (in terms of the private working set size) after - a purge request on the browser process. Recorded 2 seconds after the purge - request. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The browser process's memory usage reported by the memory instrumentation - service in MB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The browser process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The browser process's memory usage reported by the memory instrumentation - service in KB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The browser process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed June 2019. - - bashi@chromium.org - - The number of pages compressed per second. Recorded every 60 seconds. Only - recorded on macOS. - - - - - ssid@chromium.org - erikchen@chromium.org - - Records how many failed process dumps there were for a given global dump - completed by the memory instrumentation service - (resource_coordinator/memory_instrumentation/coordinator_impl.h). This is - recorded once each time a global dump request is completed. - - - - - ssid@chromium.org - erikchen@chromium.org - - Records how long it took the memory instrumentation service - (resource_coordinator/memory_instrumentation/coordinator_impl.h) from - starting working on a global memory dump request until complating that - request. This does not include queuing time (requests are handled serially). - This is recorded once each time a request is completed. - - - - - ssid@chromium.org - erikchen@chromium.org - - Number of global memory dump requests queued in by the memory - instrumentation service - (resource_coordinator/memory_instrumentation/coordinator_impl.h). This - includes the request currently being worked on if any. This is recorded once - each time a new request is queued. This happens at least once per UMA ping - to in order to compute Memory.Experimental.Renderer2, - Memory.Experimental.Browser2 etc. - - - - - - Removed June 2019. - - bashi@chromium.org - - The number of pages decompressed per second. Recorded every 60 seconds. Only - recorded on macOS. - - - - - - Removed 12/2017. Replaced by Memory.Extension.PrivateMemoryFootprint. - - erikchen@chromium.org - - A rough estimate of the private memory footprint of an extension process. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The extension process's memory usage reported by the memory instrumentation - service in MB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The extension process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The extension process's memory usage reported by the memory instrumentation - service in KB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The extension process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - erikchen@chromium.org - - The physical footprint of the GPU process on macOS. Other measurements fail - to correctly account for OpenGL memory usage. This metric also has flaws and - is not intended for permanent use. It's an emergency measure added to help - debug https://crbug.com/713854. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 12/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint. - - erikchen@chromium.org - - A rough estimate of the private memory footprint of the GPU process. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The gpu process's memory usage reported by the memory instrumentation - service in MB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The gpu process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The gpu process's memory usage reported by the memory instrumentation - service in KB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The gpu process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The time taken by the call to the various memory pressure handlers in - GpuChannelManager::HandleMemoryPressure. - - - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The network service process's memory usage reported by the memory - instrumentation service in MiB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The network service process's memory usage reported by the memory - instrumentation service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The network service process's memory usage reported by the memory - instrumentation service in KiB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The network service process's memory usage reported by the memory - instrumentation service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 12/2019. - - sebmarchand@chromium.org - catan-team@chromium.org - - The amount of time spent in the critical memory pressure state. Recorded - every time the level changes and at shutdown. - - - - - - Removed 12/2019. - - sebmarchand@chromium.org - catan-team@chromium.org - - The amount of time spent in the no memory pressure state. Recorded every - time the level changes and at shutdown. - - - - - - Removed 08/2018. Made a decision in issue 871507 that we no longer need this - data. - - ssid@chromium.org - - Records the status of OOM intervention if the feature is turned on, with - various reasons for failure, in the browser process. Recorded once at - browser startup. - - - - - - Removed 02/2020. - - bashi@chromium.org - - Records state of the intervention (accepted or declined) when the foreground - renderer is crashed after near-OOM intervention is triggered. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - - Records the time elapsed between a near-OOM detection and when a navigation - is started. - - - - - - Removed 02/2020. - - bashi@chromium.org - - Records the reason for stopping near-OOM detection. This isn't recorded when - a near-OOM situation was detected. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - - Records the time elapsed between a near-OOM detection and when an OOM - protected renderer was crashed. - - - - - - Replaced by ReducedBlinkUsageAfter10secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of blink usage after 10 seconds of intervention. This reports - negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of blink usage after 10 seconds of intervention. This reports - positive numbers when reduced. - - - - - - Replaced by ReducedBlinkUsageAfter20secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of blink usage after 20 seconds of intervention. This reports - negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of blink usage after 20 seconds of intervention. This reports - positive numbers when reduced. - - - - - - Replaced by ReducedBlinkUsageAfter30secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of blink usage after 30 seconds of intervention. This reports - negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of blink usage after 30 seconds of intervention. This reports - positive numbers when reduced. - - - - - - Replaced by ReducedRendererPMFAfter10secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of renderer pmf after 10 seconds of intervention. This - reports negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of renderer pmf after 10 seconds of intervention. This - reports positive numbers when reduced. - - - - - - Replaced by ReducedRendererPMFAfter20secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of renderer pmf after 20 seconds of intervention. This - reports negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of renderer pmf after 20 seconds of intervention. This - reports positive numbers when reduced. - - - - - - Replaced by ReducedRendererPMFAfter30secs2 in 03/2019. - - yuzus@chromium.org - - Reduced amount of renderer pmf after 30 seconds of intervention. This - reports negative numbers when reduced. - - - - - yuzus@chromium.org - keishi@chromium.org - - Reduced amount of renderer pmf after 30 seconds of intervention. This - reports positive numbers when reduced. - - - - - yuzus@chromium.org - - The renderer process's memory usage reported every second when OOM - intervention is enabled. - - - - - ssid@chromium.org - - The renderer process' Blink memory usage, as sum of V8, PartitionAlloc and - BlinkGC allocations, when a foreground OOM occurs. This was last recorded - metric by renderer a few seconds before getting killed. - - - - - - Removed 08/2018. Made a decision in issue 871507 that we no longer need this - data. - - ssid@chromium.org - - Records the status of OOM intervention in renderer process if the feature is - turned on, with various reasons for failure. Recorded at each navigation or - reload. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - - Records the time elapsed between a near-OOM detection and when a foreground - renderer process was gone. This histogram does not contain OOM protected - crashes. - - - - - yuzus@chromium.org - - The renderer process's PMF size reported every second when OOM intervention - is enabled. - - - - - ssid@chromium.org - bashi@chromium.org - - The renderer process' private memory footprint when a foreground OOM occurs. - This was last recorded metric by renderer a few seconds before getting - killed. - - - - - yuzus@chromium.org - - The renderer process's swap size reported every second when OOM intervention - is enabled. - - - - - ssid@chromium.org - bashi@chromium.org - - The renderer process' swap size when a foreground OOM occurs. This was last - recorded metric by renderer a few seconds before getting killed. - - - - - yuzus@chromium.org - keishi@chromium.org - - Records the time since last main frame navigation start on the renderer - process when high memory usage is detected. Record only when navigation - happened at least once. - - - - - - Removed 1/2019 because RendererTimeSinceLastNavigationAtDetection replaced - this metric by expanding coverage to include detection-only mode. - - yuzus@chromium.org - - Records the time since last main frame navigation start on the renderer - process when intervention is triggered. Record only when navigation happened - at least once. - - - - - ssid@chromium.org - haraken@chromium.org - - Records the time since last main frame navigation start on the renderer - process when it OOMs in foreground visible state. Record 0 if no navigation - was started. - - - - - yuzus@chromium.org - keishi@chromium.org - - Records the time since starting monitor on renderer when high memory usage - is detected. - - - - - yuzus@chromium.org - - The renderer process's virtual memory usage reported every second when OOM - intervention is enabled. - - - - - - Replaced by Memory.Experimental.OomIntervention.RendererVmSizeAtOOMLarge. - - ssid@chromium.org - - The renderer process' virtual memory usage, when a foreground OOM occurs. - This was last recorded metric by renderer a few seconds before getting - killed. - - - - - ssid@chromium.org - bashi@chromium.org - - The renderer process' virtual memory usage, when a foreground OOM occurs. - This was last recorded metric by renderer a few seconds before getting - killed. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - Records user decisions on near-OOM intervention. - - - - keishi@chromium.org - yuzus@chromium.org - V8 memory usage 10 seconds after intervention. - - - - keishi@chromium.org - yuzus@chromium.org - V8 memory usage 20 seconds after intervention. - - - - keishi@chromium.org - yuzus@chromium.org - V8 memory usage 30 seconds after intervention. - - - - keishi@chromium.org - yuzus@chromium.org - V8 memory usage right before intervention. - - - - - - keishi@chromium.org - - The renderer process's memory usage at the specific timing, i.e. after a - page load and 5/10/15minutes after backgrounded. - - - - - tasak@google.com - bartekn@google.com - - The highest private memory footprint of a renderer process in (X mins after - the first page navigation, Y mins after the first page navigation]. (X, Y] - is (0, 2], (2, 4], (4, 8], and (8, 16]. The metric is recorded at the Y's - timing. - - - - - keishi@chromium.org - - The number of loads in a main frame during the lifetime of a render process - (excludes extensions). Emitted when the processes quits. - - - - - - Removed 02/2020. - - pdr@chromium.org - paint-dev@chromium.org - - Recorded after every memory purge signal received by a foreground local - frame root with accelerated compositing enabled. Records whether or not the - signal was the first received by the local frame root. - - This metric has changed over time and it is important to consider these - changes when analyzing historical data. - - - - - tasak@google.com - bartekn@google.com - - The peak RSS size(VmHMW) of a render process when the highest private memory - footprint is observed after the first navigation start. - - - - - - Removed 12/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint. - - erikchen@chromium.org - - A rough estimate of the private memory footprint of a renderer process. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - - Amount of reclaimed memory (in terms of - Memory.Experimental.Renderer.TotalAllocated) after a purge request on a - renderer process. Recorded 2 seconds after the purge request. - - - - - keishi@chromium.org - - The uptime of a render process in time ticks (excludes extensions). Emitted - when the processes quits. - - - - - tasak@google.com - bartekn@google.com - - The number of webpages when the highest private memory footprint of renderer - process is observed after the first navigation start. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The renderer process's memory usage reported by the memory instrumentation - service in MB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The renderer process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The renderer process's memory usage reported by the memory instrumentation - service in KB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The renderer process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed June 2019. - - bashi@chromium.org - - The number of swap-ins per second. Recorded every 60 seconds. - - - - - - Removed June 2019. - - bashi@chromium.org - - The number of swap-outs per second. Recorded every 60 seconds. - - - - - sebmarchand@chromium.org - - The swap thrashing level, which is recorded periodically. This shows the - cumulative number of seconds that systems spend in each of the swap - thrashing states. Only available on Windows. - - - - - sebmarchand@chromium.org - - The number of swap-thrashing level state changes for each possible pairwise - state change. Only available on Windows. - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the private memory footprint of all processes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - keishi@chromium.org - tasak@chromium.org - - The renderer process' private memory footprint 10 seconds after a memory - pressure signal is generated. - - - - - keishi@chromium.org - tasak@chromium.org - - The renderer process' private memory footprint right before a memory - pressure signal is generated. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The utility process's memory usage reported by the memory instrumentation - service in MB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The utility process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - The utility process's memory usage reported by the memory instrumentation - service in KB. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The utility process's memory usage reported by the memory instrumentation - service in bytes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 03/2019. Replaced by - Memory.Experimental.WMIRefresher.Init.AddEnumDuration2. - - sebmarchand@chromium.org - - The time it takes for the call to |AddEnum| to complete during the - initialization of the WMI Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The time it takes for the call to |AddEnum| to complete during the - initialization of the WMI Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The time it takes for the call to |CoCreateInstance| to complete during the - initialization of the WMI Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The time it takes for the call to |CreateLocalWmiConnection| to complete - during the initialization of the WMI Refresher. - - - - - - Obsolete as of 09/2019 - - sebmarchand@chromium.org - - The result of configuring the WMIRefresher to read the disk idle time - values. - - - - - - Removed 03/2019. Replaced by - Memory.Experimental.WMIRefresher.InitializeDiskIdleTimeConfigDuration2. - - sebmarchand@chromium.org - - The time it takes to initialize the disk idle config in the WMI Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The time it takes to initialize the disk idle config in the WMI Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The time it takes to do a refresh of the disk idle time value in the WMI - Refresher. - - - - - - Obsolete as of 08/2019 - - sebmarchand@chromium.org - - The result of refreshing the disk idle time value in the WMIRefresher. - - - - - - Removed 11/2017. Replaced by Memory.Extension.PrivateMemoryFootprint. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each extension process. Each process - provides one sample. Recorded once per process per UMA ping. - - - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the private memory footprint of the extension process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - fdoray@chromium.org - - The size of the resident memory in an extension process. This is influenced - by factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of the extension process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 06/2020. No direct replacement. For similar histograms see - Memory.RenderProcessHost.Count.*, Memory.RendererProcessCount and - Memory.ProcessCount. Old data has been preserved at (Google-internal) - https://docs.google.com/document/d/1QleZ5KhAbFZkv0In61sw7e2rWCaJ05dUCdV9DncJZ2E - - creis@chromium.org - nasko@chromium.org - - The count of active extension processes. Recorded once per UMA ping. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The number of glyph pages present in the renderer when it commits a load. - Since this is per-sub-process, you can get the average number of glyph pages - in the system by multiplying this number with the average number of - renderers. Note that this typically won't count the glyph pages added as a - result of the load that just committed, since layout will happen after the - commit. There are 512 bytes per glyph page, but this number also very - closely approximates the number of glyph width map pages in the same - renderer. The only difference is that if you have font fallback, it will - make a new glyph page and no width page, but in most common cases there is - no fallback). Width pages are 1K each (256 floats), so you could think of - this value as being the number of "1.5K units related to glyphs per - renderer per page load". - - - - - - Removed 11/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint. - - hajimehoshi@chromium.org - jamescook@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by the GPU process. Recorded once per UMA ping. - - - - - - - - - - - jonross@chromium.org - graphics-dev@chromium.org - sadrul@chromium.org - - The maximum amount of memory of the GPU process allocated by a particular - source during a user interaction (e.g. tab-switch, page-load, scroll etc.). - See Memory.GPU.PeakMemoryUsage. - - - - - - - jonross@chromium.org - sadrul@chromium.org - graphics-dev@chromium.org - - The maximum amount of memory of the GPU process during a particular - interaction (e.g. tab-switch, page-load, scroll etc.). - - - - - - - erikchen@chromium.org - ssid@chromium.org - chrome-analysis-team@google.com - - A rough estimate of the private memory footprint of the gpu process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - erikchen@chromium.org - ssid@chromium.org - - An amount of private memory of the GPU process placed in swap (VmSwap). - Available on Android, Linux and ChromeOS. - - - - - - - fdoray@chromium.org - - The size of the resident memory in the GPU process. This is influenced by - factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of the gpu process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - hajimehoshi@chromium.org - erikchen@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - System-wide graphics driver memory consumption. Recorded on Chrome OS for - platforms where it is exposed by the kernel (for example, Intel i915 and - Exynos Mali). Recorded once per UMA ping. - - - - - alph@chromium.org - erikchen@chromium.org - - Browser process memory allocated with malloc when UMA heap profile is taken. - - - - - - Obsolete as of 11/2015 - - ssid@chromium.org - Size of messages received by IPC::ChannelReader. - - - - - Removed 7/2019. No longer recorded. - - lizeb@chromium.org - - Recorded each time a Movable String is (un)parked, with the context: - foreground/background. - - - - - - Removed 7/2019. No longer recorded. - - lizeb@chromium.org - - This records the number of movable Javascript source string resources in a - given renderer, at the time page is backgrounded. Recorded alongside - Memory.MovableStringsTotalSizeKb. - - - - - - Removed 7/2019. No longer recorded. - - lizeb@chromium.org - - This records the total size of movable Javascript source string resources in - a given renderer, at the time page is backgrounded. Recorded alongside - Memory.MovableStringsCount. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each Native Client loader process. Each - process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each Native Client broker process. Each - process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 03/2019. Replaced by - Memory.NativeLibrary.MappedAndResidentMemoryFootprint2 to add more precision - to buckets. - - msalama@google.com - lizeb@chromium.org - - The size of the resident memory for the native library code across all - processes. This metric is computed by parsing proc/self/pagemap and counting - native library pages that are mapped and present in RAM for at least one - Chrome process. Recorded once per UMA ping. Available only on Android. - - - - - msalama@google.com - lizeb@chromium.org - - The size of the resident memory for the native library code across all - processes. This metric is computed by parsing proc/self/pagemap and counting - native library pages that are mapped and present in RAM for at least one - Chrome process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - lizeb@chromium.org - pasko@chromium.org - - Result of an attempt to read /proc/self/pagemap when determining the amount - of resident memory mapped by the current process. Reading the file is - performed as part of computing the - Memory.NativeLibrary.MappedAndResidentMemoryFootprint2 histogram. Available - only on Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - lizeb@chromium.org - - The size of the native library code which was ordered, yet is not resident - in memory, across all processes. This metric is computed by parsing - proc/self/pagemap and counting native library pages that are mapped and - present in RAM for at least one Chrome process. Available only on Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - lizeb@chromium.org - - The size of the native library code which is outside the ordered section, - yet is resident in memory, across all processes. This metric is computed by - parsing proc/self/pagemap and counting native library pages that are mapped - and present in RAM for at least one Chrome process. Available only on - Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the private memory footprint of the network service - process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - An amount of private memory of the network service process placed in swap - (VmSwap). Available on Android, Linux and ChromeOS. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Note: Histogram data may be missing for mid-2020 due to expiry. - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - The size of the resident memory in a network service process. This is - influenced by factors we control (e.g. memory that is not accessed can be - swapped) and factors we don't control (e.g. an unrelated process using a lot - of memory can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - mmenke@chromium.org - morlovich@chromium.org - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of the network service - process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Note: Histogram data may be missing for mid-2020 due to expiry. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide memory allocation right after a renderer was killed by - oom-killer, roughly equivalent to the sum of memory allocated with malloc() - in userspace plus graphics driver memory. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide file-backed memory plus free memory right after a renderer was - killed by oom-killer, which should be smaller than or close to what the - kernel uses to trigger low-memory notifications for tab discards. If this is - higher than the kernel's threshold for tab discards, renderers may be killed - due to reasons other than out-of-memory. - - - - - oshima@chromium.org - alemate@chromium.org - - Graphics driver (GEM object) memory right after a renderer was killed by - oom-killer. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide shared memory right after a renderer was killed by oom-killer. - Used primarily for shared buffers in the graphics system. Tracked because - it's a historical source of leaks on Chrome OS. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide memory allocation right after a renderer was killed by - oom-killer, roughly equivalent to the sum of memory allocated with malloc() - in userspace plus graphics driver memory. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide file-backed memory plus free memory right after a renderer was - killed by oom-killer, which should be smaller than or close to what the - kernel uses to trigger low-memory notifications for tab discards. If this is - higher than the kernel's threshold for tab discards, renderers may be killed - due to reasons other than out-of-memory. - - - - - oshima@chromium.org - alemate@chromium.org - - Graphics driver (GEM object) memory right after a renderer was killed by - oom-killer. - - - - - oshima@chromium.org - alemate@chromium.org - - System-wide shared memory right after a renderer was killed by oom-killer. - Used primarily for shared buffers in the graphics system. Tracked because - it's a historical source of leaks on Chrome OS. - - - - - - - dcastagna@chromium.org - ssid@chromium.org - - The total number of open file descriptors opened per process. Recorded once - per UMA ping. - - - - - - - dcastagna@chromium.org - ssid@chromium.org - - The limit of open file descriptors that can be opened per process. Recorded - once per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of other various utility processes (nacl, gpu, sandbox, zygote, - utility). Recorded once per UMA ping. - - - - - lizeb@chromium.org - - Total size of compressed ParkableStrings, in KB. Recorded at the same time - as "Memory.ParkableString.TotalSizeKb". - - - - - lizeb@chromium.org - - Time to compress a ParkableString, in us. Note: This metric drops reports on - clients with low-resolution clocks, which means these reports will be biased - against a portion of the population on Windows. See - Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - lizeb@chromium.org - - Size of a compressed ParkableString, recorded at compression time. - - - - - lizeb@chromium.org - - Size of a compressed ParkableString, recorded at compression time. - - - - - - Removed 07/2019. No longer recorded. - - lizeb@chromium.org - - Average compression ratio, 100 * compressed_size / initial_size, for all - compressed ParkableStrings. Recorded at the same time as - "Memory.ParkableString.TotalSizeKb". - - - - - lizeb@chromium.org - pasko@chromium.org - - Average compression ratio, 100 * compressed_size / initial_size, for all - compressed ParkableStrings. Recorded at the same time as - "Memory.ParkableString.TotalSizeKb.5min". - - - - - lizeb@chromium.org - - Time to decompress a ParkableString, in us. Note: This metric drops reports - on clients with low-resolution clocks, which means these reports will be - biased against a portion of the population on Windows. See - Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - lizeb@chromium.org - - Original size of a compressed ParkableString, recorded at decompression - time. - - - - - lizeb@chromium.org - - Original size of a compressed ParkableString, recorded at decompression - time. - - - - - lizeb@chromium.org - pasko@chromium.org - - Whether the disk allocator is usable. Recorded at the same time as - "Memory.ParkableString.TotalSizeKb.5min". The disk may not be - usable for several reasons, including the profile being an Incognito one, - permssions error, or disk write error. - - - - - lizeb@chromium.org - pasko@chromium.org - - Total main thread time used by ParkableStrings for reading over the first 5 - minutes of a renderer lifetime. Starting time is from the first - ParkableString being added. - - - - - lizeb@chromium.org - pasko@chromium.org - - Total time used by ParkableStrings for writing to disk over the first 5 - minutes of a renderer lifetime. Starting time is from the first - ParkableString being added. - - - - - lizeb@chromium.org - pasko@chromium.org - - Total main thread time used by ParkableStrings over the first 5 minutes of a - renderer lifetime. Starting time is from the first ParkableString being - added. - - - - - lizeb@chromium.org - pasko@chromium.org - - Sum of memory saved by compression and disk discarding, in KB. Recorded at - the same time as "Memory.ParkableString.TotalSizeKb.5min", when - disk discarding is enabled. - - - - - lizeb@chromium.org - pasko@chromium.org - - Total disk footprint used by ParkableStrings including allocator waste, in - KB. Recorded once, 5 minutes after the first ParkableString is added to a - renderer, at the same time as - "Memory.ParkableString.MemorySavings.5min". - - - - - lizeb@chromium.org - pasko@chromium.org - - Total size of ParkableStrings discarded to disk, excluding allocator waste, - in KB. Recorded once, 5 minutes after the first ParkableString is added to a - renderer, at the same time as - "Memory.ParkableString.MemorySavings.5min". - - - - - lizeb@chromium.org - pasko@chromium.org - - Total thread time used by ParkableStrings for parking over the first 5 - minutes of a renderer lifetime. Starting time is from the first - ParkableString being added. - - - - - lizeb@chromium.org - pasko@chromium.org - - Time to read a ParkableString from disk, in us. Note: This metric drops - reports on clients with low-resolution clocks, which means these reports - will be biased against a portion of the population on Windows. See - Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - lizeb@chromium.org - pasko@chromium.org - Size read from disk for a ParkableString. - - - - lizeb@chromium.org - pasko@chromium.org - Read throughput from disk for a ParkableString. - - - - lizeb@chromium.org - pasko@chromium.org - - Sum of memory saved by compression, in KB. Recorded at the same time as - "Memory.ParkableString.TotalSizeKb". - - - - - lizeb@chromium.org - pasko@chromium.org - - Sum of memory saved by compression, in KB. Recorded at the same time as - "Memory.ParkableString.TotalSizeKb.5min". - - - - - - Removed 07/2019. No longer recorded. - - lizeb@chromium.org - - Total size of ParkableStrings assuming no compression, in KB. Recorded 30s - after compression was triggered, provided that the renderer stayed - backgrounded. - - - - - lizeb@chromium.org - pasko@chromium.org - - Total size of ParkableStrings assuming no compression, in KB. Recorded once, - 5 minutes after the first ParkableString is added to a renderer, at the same - time as "Memory.ParkableString.MainThreadTime.5min". - - - - - lizeb@chromium.org - pasko@chromium.org - - Time to write a ParkableString to disk, in us. Note: This metric drops - reports on clients with low-resolution clocks, which means these reports - will be biased against a portion of the population on Windows. See - Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - lizeb@chromium.org - pasko@chromium.org - Size of an on-disk ParkableString, recorded at write time. - - - - lizeb@chromium.org - pasko@chromium.org - Throughput of a ParkableString disk write. - - - - - Deprecated and removed from the code 06/2020. - - lizeb@chromium.org - pasko@chromium.org - - Total main thread time used by PartitionAlloc's decommit logic over the - first 5 minutes of a renderer lifetime. Starting time is renderer - initialization. - - - - - - Removed 11/2017. No direct replacement. - - thestig@chromium.org - - The private working set used by each Pepper Flash plugin process. Each - plugin process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each Pepper plugin process. Each plugin - process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each Pepper plugin broker process. Each - process provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of Pepper plugin broker processes, recorded once per metrics - services (UMA) update. See MetricsReportingScheduler for details. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of active Pepper plugin processes. Recorded once per UMA ping. - - - - - - Removed due to NPAPI removal. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each plugin process. Each plugin process - provides one sample. Recorded once per process per UMA ping. - - - - - - Removed due to NPAPI removal. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of active plugin processes. Recorded once per UMA ping. - - - - - chrisha@chromium.org - - The memory pressure level, which is recorded periodically. This shows the - cumulative number of seconds that systems spend in each of the memory - pressure states. - - - - - chrisha@chromium.org - - The number of pressure level state changes for each possible pairwise state - change. - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The time spent in each of the memory pressure state. Recorded when - transitioning from a memory pressure state to the other and when exiting - memory pressure. - - - - - creis@chromium.org - nasko@chromium.org - - The count of all active processes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - The current process limit. Recorded once per UMA ping. - - - - - Removed 06/2016 Replaced with Memory.Renderer.Large2. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each renderer process. Each renderer process - provides one sample. Recorded once per UMA ping. TODO(rkaplow): This should - be replaced with Memory.Renderer.Large2 in M54. - - - - - pasko@chromium.org - leszeks@chromium.org - - The state of CachedMetadata on every attempt to use it for a script - resource. Used for experiment in http://crbug.com/1045052. - - - - - - Removed 03/2018. No direct replacement. - - bashi@chromium.org - kouhei@chromium.org - - The total committed memory used by each renderer process. Each renderer - process provides one sample. Recorded once per process per UMA ping. - - - - - hajimehoshi@chromium.org - - The esitimated memory size which would be reduced when reusing disk cache is - implemented. If it is 100% sure that the encoded data is in disk cache, the - same data in memory can be dropped to reduce memory usage. This is rencorded - when an ImageResource is pruned. See crbug/664437. - - - - - - Removed 11/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint. - - bashi@chromium.org - kouhei@chromium.org - - The private working set used by each renderer process. Each renderer process - provides one sample. Recorded once per process per UMA ping. - - - - - - - erikchen@chromium.org - ssid@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - A rough estimate of the private memory footprint of the renderer process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - - - - - - fdoray@chromium.org - - The size of the resident memory in a renderer process. This is influenced by - factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of the renderer process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - Removed 11/2017. No direct replacement, although - Memory.Total.PrivateMemoryFootprint is similar. - - bashi@chromium.org - hajimehoshi@chromium.org - tasak@chromium.org - - The private working set used by each renderer process, including all - renderer types, i.e. this includes Chrome renderer, extensions renderer, as - well as regular renderer processes. Each renderer process provides one - sample. Recorded once per process per UMA ping. - - - - - - Removed 01/2018. No direct replacement, although - Memory.Total.PrivateMemoryFootprint is similar. - - bashi@chromium.org - hajimehoshi@chromium.org - tasak@chromium.org - - The total committed memory used by each renderer process, including all - renderer types, i.e. this includes Chrome renderer, extensions renderer, as - well as regular renderer processes. Each renderer process provides one - sample. Recorded once per process per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Growth speed of the private working set used by each renderer process per 30 - minutes. The usage and growth speed is recorded at most every 30 minutes, - not every exact 30 minutes. If the interval is longer than 30 minutes, it is - normalized to a speed KB per 30 minutes. Each renderer process provides one - sample. Recorded once per UMA log unless this is the first time the UMA log - is recorded after startup of the renderer, 30 minutes have not passed from - the last recording of the renderer or the usage goes down. If the usage goes - down, the amount of the shrink will be recorded in the - Memory.RendererShrinkIn30Min histogram. - - - - - creis@chromium.org - nasko@chromium.org - - The count of active renderer processes. Excludes renderers hosting - chrome-extension:// and/or chrome:// URLs. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Computed based on OS data. - - WARNINGS: Not reliable on Android, see https://crbug.com/875400. Ignores - processes that do not host a widget, see https://crbug.com/949977#c36. - Consider using Memory.RenderProcessHost.Count.* instead. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Shrink speed of the private working set used by each renderer process per 30 - minutes. The usage and shrink speed is recorded at most every 30 minutes, - not every exact 30 minutes. If the interval is longer than 30 minutes, it is - normalized to a speed KB per 30 minutes. Each renderer process provides one - sample. Recorded once per UMA log unless this is the first time the UMA log - is recorded after startup of the renderer, 30 minutes have not passed from - the last recording of the renderer or the usage goes up. If the usage goes - up, the amount of the growth will be recorded in the - Memory.RendererGrowthIn30Min histogram. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - nasko@chromium.org - - The count of all renderer processes. Covers all renderer processes, - including ones hosting web content (i.e. http(s):// and/or file://), - extensions (i.e. chrome-extension://) and WebUI (i.e. chrome://). - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Computed based on count of RenderProcessHost objects, even if 1) they have - not been launched yet (e.g. during session restore) or 2) they are dead - (e.g. killed by the browser process or the OS). - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - nasko@chromium.org - - The count of active renderer processes. Recorded once per UMA ping. Covers - all renderer processes, including ones hosting web content (i.e. http(s):// - and/or file://), extensions (i.e. chrome-extension://) and WebUI (i.e. - chrome://). - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Computed based on count of RenderProcessHost objects that are - IsInitializedAndNotDead (i.e. have been launched and not terminated yet). - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each sandbox helper process. Each sandbox - helper process provides one sample. Recorded once per process per UMA ping. - - - - - reveman@chromium.org - - The amount of free space in temporary directory for shared memory files. - Recorded each time a new discardable memory manager instance is created. - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.AvailPageFile2. - - georgesak@chromium.org - - Windows-only metric that represents the maximum amount of memory the current - process can commit. This value is equal to or smaller than the system-wide - available commit value. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the maximum amount of memory the current - process can commit. This value is equal to or smaller than the system-wide - available commit value. - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.AvailPhys2. - - georgesak@chromium.org - - Windows-only metric that represents the amount of physical memory currently - available. This is the amount of physical memory that can be immediately - reused without having to write its contents to disk first. It is the sum of - the size of the standby, free, and zero lists. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the amount of physical memory currently - available. This is the amount of physical memory that can be immediately - reused without having to write its contents to disk first. It is the sum of - the size of the standby, free, and zero lists. - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.AvailVirtual2. - - georgesak@chromium.org - - Windows-only metric that represents the amount of unreserved and uncommitted - memory currently in the user-mode portion of the virtual address space of - the calling process. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the amount of unreserved and uncommitted - memory currently in the user-mode portion of the virtual address space of - the calling process. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the approximate percentage of physical - memory that was in use (0 indicates no memory use and 100 indicates full - memory use). - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.TotalPageFile2. - - georgesak@chromium.org - - Windows-only metric that represents the current committed memory limit for - the system or the current process, whichever is smaller. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the current committed memory limit for - the system or the current process, whichever is smaller. - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.TotalPhys2. - - georgesak@chromium.org - - Windows-only metric that represents the amount of actual physical memory. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the amount of actual physical memory. - - - - - - Removed in 595320 and replaced with Memory.Stats.Win.TotalVirtual2. - - georgesak@chromium.org - - Windows-only metric that represents the size of the user-mode portion of the - virtual address space of the calling process. This value depends on the type - of process, the type of processor, and the configuration of the operating - system. For example, this value is approximately 2 GB for most 32-bit - processes on an x86 processor and approximately 3 GB for 32-bit processes - that are large address aware running on a system with 4-gigabyte tuning - enabled. - - - - - - Removed in 05/2019 - - georgesak@chromium.org - - Windows-only metric that represents the size of the user-mode portion of the - virtual address space of the calling process. This value depends on the type - of process, the type of processor, and the configuration of the operating - system. For example, this value is approximately 2 GB for most 32-bit - processes on an x86 processor and approximately 3 GB for 32-bit processes - that are large address aware running on a system with 4-gigabyte tuning - enabled. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by the browser process. Recorded once per UMA ping if the - system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each chrome:// renderer process. Each process provides one - sample. Recorded once per process per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The amount of memory that swap was compressed into. Recorded once per UMA - ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The ratio of swapped data original size to compressed size. Recorded once - per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each extension process. Each process provides one sample. - Recorded once per process per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by the GPU process. Recorded once per UMA ping if the system - has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Indicates that the system has swapped memory out at least once since boot. - Recorded once per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The amount of memory that is used by swap, including bookkeeping. Recorded - once per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each Native Client loader process. Each process provides - one sample. Recorded once per process per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each Native Client broker process. Each process provides - one sample. Recorded once per process per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The number of reads from swap. Recorded once per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The number of writes to swap. Recorded once per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The amount of memory that was swapped out. Recorded once per UMA ping if the - system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each Pepper plugin process. Each plugin process provides - one sample. Recorded once per process per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each Pepper plugin broker process. Each process provides - one sample. Recorded once per process per UMA ping if the system has - swapped. - - - - - - Removed due to NPAPI removal. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each plugin process. Each plugin process provides one - sample. Recorded once per process per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each renderer process. Each renderer process provides one - sample. Recorded once per process per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each sandbox helper process. Each sandbox helper process - provides one sample. Recorded once per process per UMA ping if the system - has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The sum of all processes' swap. Recorded once per UMA ping if the system has - swapped. See Memory.Swap.Total2 for the same metric with higher precision - bucketing. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - rkaplow@chromium.org - - The sum of all processes' swap. Recorded once per UMA ping if the system has - swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each utility process. Each utility process provides one - sample. Recorded once per process per UMA ping if the system has swapped. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by each worker process. Each worker process provides one - sample. Recorded once per process per UMA ping if the system has swapped. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The swap used by the zygote process. Recorded once per UMA ping if the - system has swapped. - - - - - - Removed 09/2016. Replaced by Memory.Total2. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The sum of all processes. This is not aware of shared memory so it is just a - rough estimate. Recorded once per UMA ping. See Memory.Total2 for the same - metric with higher precision bucketing. - - - - - - - erikchen@chromium.org - ssid@chromium.org - chrome-analysis-team@google.com - - A rough estimate of the private memory footprint of all processes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - tommckee@chromium.org - - A rough estimate of the private memory footprint of all renderer processes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - - - fdoray@chromium.org - - The size of the resident memory in all processes. This is influenced by - factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Note: This metric is a simple sum of the resident set of all processes and - this cause some double accounting for the shared portion of the working set. - As a result this metric doesn't give an exact representation of how much - physical memory is used by Chrome. - - - - - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of all processes. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - sadrul@chromium.org - zmo@chromium.org - - Records the system commit limit (number of total pages) x page size, - collected in the info collection GPU process, once per UMA ping. This is - Windows platform only. - - - - - - Removed 11/2017. Replaced by Memory.Total.PrivateMemoryFootprint. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - rkaplow@chromium.org - - The sum of all processes. This is not aware of shared memory so it is just a - rough estimate. Recorded once per UMA ping. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each utility process. Each utility process - provides one sample. Recorded once per process per UMA ping. - - - - - - - jam@chromium.org - - A rough estimate of the private memory footprint of the utility process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - jam@chromium.org - - An amount of private memory of the utility process placed in swap (VmSwap). - Available on Android, Linux and ChromeOS. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Note: Histogram data may be missing for mid-2020 due to expiry. - - - - - - - fdoray@chromium.org - - The size of the resident memory in a utility process. This is influenced by - factors we control (e.g. memory that is not accessed can be swapped) and - factors we don't control (e.g. an unrelated process using a lot of memory - can force memory in our process to be swapped). Recorded on - Windows/Linux/ChromeOS/Android. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - - - - jam@chromium.org - erikchen@chromium.org - ssid@chromium.org - - A rough estimate of the shared memory footprint of the utility process. - - Recorded at Poisson sampled time intervals with a mean of 5 minutes on - Android and 30 minutes on other platforms. - - Note: Histogram data may be missing between M77 to M87 due to expiry. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by each worker process. Each worker process - provides one sample. Recorded once per process per UMA ping. - - - - - - Removed 03/2018. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The count of active worker processes. Recorded once per UMA ping. - - - - - - Removed 11/2017. No direct replacement. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - The private working set used by the zygote process. Each zygote process - provides one sample. Recorded once per process per UMA ping. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Value of getMemoryClass() recorded once upon startup. This is an integer, - device-specific constant correlated with the amount of memory available on - Android device. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Reasons behind evictions of individual tabs, recorded upon each tab - eviction. - - - - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Number of loaded (memory-resident) tabs when LowMemory notification is - delivered. - - - - - - Removed 04/2018. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Time between two consecutive LowMemory notification in one foreground - session. - - - - - ssid@chromium.org - - Whether Chrome is running in low ram mode. This histogram is reported on - every upload by Android devices. A device is considered low-RAM if it has - 512MiB of RAM or lower (see SysUtils.detectLowEndDevice()). - - Note: The low-RAM determination has changed in M-49, it used to be given - directly by the Android OS. - - - - - - Removed 04/2018 in favor of Android.MemoryPressureNotification. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Memory notifications delivered through system callbacks to Chrome while in - the background. - - - - - - Removed 04/2018 in favor of Android.MemoryPressureNotification. - - hajimehoshi@chromium.org - kenjibaheux@google.com - kouhei@chromium.org - - Memory notifications delivered through system callbacks to Chrome while in - the foreground - we count LowMemory notification vs particular levels of - TrimMemory foreground notification. - - - - - - Obsolete as of 06/2020. - - bashi@chromium.org - The amount of reclaimed memory after a tab became inactive. - - - - - Removed as of 10/2016. - - - [iOS] When the OS sends a memory warning and the app evicts a tab, this - histogram records the time since the evicted tab was active. - - - - - marq@chromium.org - - The number of memory warnings during a given foreground session. - - - - - - Removed as of 10/2016. - - - [iOS] When the OS sends a memory warning and the app protects a tab, this - histogram records the time since the protected tab was active. - - - - - - Removed as of 07/2018. - - gab@chromium.org - - The size of the delayed task queue when the loop becomes idle. Diagnosis - metric for https://crbug.com/850450#c4. - - - - - - Removed as of 07/2018. - - gab@chromium.org - - Reports the delay of a delayed task posted to a MessageLoop. Reported once - per delayed task. Diagnosis metric for https://crbug.com/850450#c4. - - - - - - Removed as of 11/2018. - - gab@chromium.org - - The size of the delayed task queue when the loop becomes idle on a UI - thread. Diagnosis metric for https://crbug.com/850450#c4. Note: this metric - is a bit broken on Mac OSX as CFRunLoop doesn't deterministically invoke - MessageLoop::DoIdleWork(). - - - - - - Removed as of 07/2018. - - gab@chromium.org - - Reports the delay for which the MessageLoop successfully slept until an - upcoming delayed task. Reported each time a MessageLoop successfully sleeps - until the next delayed task. - - - - - - Removed as of 07/2018. - - gab@chromium.org - - Reports the delay for which the MessageLoop had planned to sleep (next - delayed task) before it was woken up early. Reported each time a MessageLoop - is woken up early. - - - - - akhouderchah@chromium.org - benchan@chromium.org - - The result (e.g. success or the type of failure) of a modem interface switch - operation performed by mist on Chrome OS. - - - - - - Removed as of 01/2020. - - carlosil@chromium.org - estark@chromium.org - - Whether a navigation opted out or not of Mixed Content autoupgrades. - Recorded every navigation. - - - - - carlosil@chromium.org - - The net error or HTTP response code of a mixed content resource request that - was autoupgraded to HTTPS - - - - - carlosil@chromium.org - - Whether or not an autoupgrade mixed content request was for a resource we - know to be an ad - - - - - carlosil@chromium.org - estark@chromium.org - - Logs the type of each resource request that is autoupgraded to HTTPS and - fails to load. - - - - - carlosil@chromium.org - estark@chromium.org - - Logs the type of each resource request that was autoupgraded to HTTPS and - resulted in a response. - - - - - carlosil@chromium.org - estark@chromium.org - - Logs the type of each resource request that is autoupgraded to HTTPS. This - is logged when the request is started. - - - - - carlosil@chromium.org - - The status of a mixed content resource request that was autoupgraded to - HTTPS - - - - - - Removed as of 01/2020. - - carlosil@chromium.org - - The status of a mixed content websocket that was autoupgraded to WSS. - - - - - gangwu@chromium.org - twellington@chromium.org - - The time it takes for the user to abandon the app menu after it's shown by - pressing back or touching outside the menu. This is only logged if the menu - is abandoned. See Mobile.AppMenu.TimeToTakeAction.SelectedItem for the cases - where it is closed as a result of user interaction with the menu. Android - only. - - - - - gangwu@chromium.org - twellington@chromium.org - - The time it takes for the user to select an item. This is only logged if the - menu is closed as a result of the user clicking a menu item. See - Mobile.AppMenu.TimeToTakeAction.Abandoned for the cases where it is - abandoned by the user. Android only. - - - - - pkl@chromium.org - tedchoc@chromium.org - - The result of the operation to retrieve the page's canonical URL. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Bookmark - entries. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Bookmark - folders. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which context menu was shown. To drill down into a specific context - menu's usage, take a look at its actions' histogram (the format for actions - histograms is Mobile.ContextMenu.*.Actions). Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for History - entries. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Most Visited - entries. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Reading List - entries. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Recent Tabs - entries. To view how often this context menu was shown, take a look at this - other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - gambard@chromium.org - - Tracks which action was selected in the context menu shown for Recent Tabs - headers/devices. To view how often this context menu was shown, take a look - at this other histogram: Mobile.ContextMenu.EntryPoints. Currently only on - iOS. - - - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - Android: The number of browsers installed on the device. Logged when a new - session is started. - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - Android: Whether or not the device has a default browser and whether or not - it is a system installed browser. Logged when a new session is started. - - - - - - - - - dtrainor@chromium.org - nyquist@chromium.org - - Android: The number of system installed browsers. Logged when a new session - is started. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the time between tapping the target and source language in a legacy - infobar. If only one of either is tapped, nothing is logged. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the time an unused legacy infobar persists on screen. This is logged - when the infobar is closed. - - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records the state of a badge when it was tapped. - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records the reason why a Banner was dismissed. - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records Infobar Banner events. - - - - sczs@chromium.org - thegreenfrog@google.com - - Records the time an Infobar (Messages) Banner is visible on screen. Used to - know how long it takes a user to act on the banner before it gets - auto-dismissed. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Tracks the number of multiple Infobars being presented at the same time. - This will be recorded everytime an Infobar is presented. - - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the time between the Infobar Delegate is created, and the user - accepts a Confirm Infobar action. - - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the events related to Confirm Infobars (e.g. Presented, Accepted, - Dismissed,etc.) - - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records generic Infobar Modal events. - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records a tap on an Infobar overflow menu row. - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records the reason why a Password Modal was dismissed. - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records Password specific Infobar Modal events. - - - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records the context when a Password Modal was presented. - - - - sczs@chromium.org - thegreenfrog@chromium.org - Records Save Card specific Infobar Modal events. - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the context when an iOS user taps on a Translate Banner Action - Button. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records when an iOS user initiates an Translate specific Infobar Modal - event. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records the context when an iOS user initiates a Translate Modal - presentation. - - - - - sczs@chromium.org - edchin@chromium.org - - Records the total number of tabs opened when Open all was selected from - other devices in Recent Tabs. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for a bookmark entry. To view how often this sharing scenario was triggered, - take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks which sharing entry point was triggered. To view the outcome of these - sharing scenarios, take a look at their actions' histogram (the format is - Mobile.Share.*.Actions). Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for a history entry. To view how often this sharing scenario was triggered, - take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for a most visited tile. To view how often this sharing scenario was - triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for the generated QR code image. To view how often this sharing scenario was - triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for a reading list entry. To view how often this sharing scenario was - triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - for a recent tab entry. To view how often this sharing scenario was - triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - seblalancette@chromium.org - chrome-sharing-core@google.com - - Tracks the sharing actions executed when the sharing scenario was initiated - from the tab's share button. To view how often this sharing scenario was - triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. - - - - - - Removed in 07/2020 because it is no longer needed for analysis. - - peconn@chromium.org - pkotwicz@chromium.org - - Records the cases when the splash screen is hidden when the activity is - finishing. Only "true" is recorded. The purpose is to help - determine cause of http://crbug.com/1096171 - - - - - - Removed in 06/2020 because it is no longer needed for analysis. - - peconn@chromium.org - peter@chromium.org - - Records the cases when removing a Trusted Web Activity's or WebAPK's - translucency via a reflective call fails. Only "true" is recorded. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records which Android notifications users interact with. Recorded when an - user taps the button in a notification, for any Chrome-generated - notification on Android that includes a button tap-target. - - - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records the duration in minutes from the time when the system notification - is shown to the time that the user clicked on an action button on the - Android notification. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Android: Represents the number of system notifications that were blocked and - could not be shown by type. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Android: Represents the type of notification that was last shown before the - user disabled notification permissions on Chrome. This is only logged the - first time we attempt to show a notification and fail. - - - - - - - peter@chromium.org - xingliu@chromium.org - - Android: Represents the number of system notifications by type that we - attempted to show but were blocked, due to their notification channel being - blocked. Only applies to devices on Android O and above. - - - - - - - xingliu@chromium.org - chrome-analysis-team@google.com - - Records the type of notification when the user clicks the body of Android - notification. This does not include clicks on notification action buttons. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records the duration in minutes from the time when the system notification - is shown to the time that the user clicked the notification on Android. - - - - - - Removed in 04/2020. - - xingliu@chromium.org - - Android: Represents the number of system notifications failed to be created - by the Android API. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records the type of notification when the user dismisses the Android - notification. - - - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records the duration in minutes from the time when the system notification - is shown to the time that the user dismissed the notification on Android. - - - - - knollr@chromium.org - xingliu@chromium.org - - Android: Represents the number of system notifications failed to be notified - by Android NotificationManager API. Recorded when the notification is shown - on Android. - - - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Android: Represents the number of system notifications that will be - successfully shown to the user by type. - - - - - sczs@chromium.org - thegreenfrog@chromium.org - - Records a histogram for an infobar (both legacy and Messages) that the user - did not interact with throughout its lifetime. - - - - - hnakashima@chromium.org - hanxi@chromium.org - yfriedman@chromium.org - - Android: Records events for downloads started from the background, that is, - while the browser process is not running. Used to measure completion rate of - these downloads. - - - - - qinmin@chromium.org - xingliu@chromium.org - - Android: Records the target determination result for downloads started in - the background, that is, while the browser process is not running. - - - - - - Removed 02/2020. - - qinmin@chromium.org - - Android: Records the total data downloaded by completion status. - - - - - - Removed 02/2020. - - qinmin@chromium.org - - Android: Records the total data wasted during download due to resumptions. - - - - - - Removed 09/2019, replaced by Download.CancelledDownloadRemovedFromHistory. - - qinmin@chromium.org - dtrainor@chromium.org - - Android: Records the number of cancelled download that are cleaned up from - the history, after loading all the downloads from the history DB on startup. - - - - - - Removed in 07/2019. - - qinmin@chromium.org - Android: Records the reason that a download is canceled. - - - - qinmin@chromium.org - - Android: Records various counts related to the save image context menu - option. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Android: Records whether download later dialog will be shown to the user. - Recorded when the download later preference is initialized in native. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Android: Records whether download dialog will be shown to the user. Recorded - when the download preference is initialized in native. - - - - - - Removed in 02/2020. - - qinmin@chromium.org - - Android: Records user interaction on the download resumption button. - - - - - - Removed in 02/2020. - - qinmin@chromium.org - - Android: Records the total time for a download by completion status. - - - - - - Removed in 07/2019. - - qinmin@chromium.org - - Android: Records various counts related to the duplicate download infobar. - - - - - - Removed in 02/2020. - - qinmin@chromium.org - hnakashima@chromium.org - hanxi@chromium.org - qinmin@chromium.org - - Android: Records the number of interruptions for the first download started - in background after it reaches a terminal state. - - - - - - Removed in 02/2020. - - hnakashima@chromium.org - hanxi@chromium.org - qinmin@chromium.org - - Android: Records all the interrupt reasons for the first download started in - background after every browser process launch. We only record the first - download so that we can compare the difference between service manager only - mode and full browser process mode. - - - - - - Removed in 02/2020. - - hnakashima@chromium.org - hanxi@chromium.org - qinmin@chromium.org - - Android: After every browser process launch, records the interrupt reason of - the first background download when it is started. This interrupt reason - allows us to know whether download was interrupted due to browser process - crash in an earlier attempt. - - - - - - Removed 09/2016 in Issue 647755 with all downloads going through Chrome. - - qinmin@chromium.org - - Android: Records the reason that Chrome fails to intercept a download and - pass it to the Android DownloadManager. - - - - - - Removed 09/2019, replaced by - Download.InterruptedDownloadsRemovedFromHistory. - - qinmin@chromium.org - dtrainor@chromium.org - - Android: Records the number of interrupted download that are cleaned up from - the history, after loading all the downloads from the history DB on startup. - - - - - - Removed 02/2020. - - qinmin@chromium.org - - Android: Records the total interruptions for a download by completion - status. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records the directory type when the user selects the download directory - through download location dialog. May be recorded even when the user didn't - download anything. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records whether the user accepted or dismissed the dialog to select a - download location. - - - - - xingliu@chromium.org - clank-downloads@google.com - - Records the download location dialog type when the dialog is shown to the - user. - - - - - xingliu@chromium.org - dtrainor@chromium.org - qinmin@chromium.org - - Records the directory type shown when a user opens download location dialog - or download location setting. This is recorded when the directory provider - generates a list of available directories. - - - - - xingliu@chromium.org - clank-downloads@google.com - Records the directory type when download is completed. - - - - xingliu@chromium.org - clank-downloads@google.com - - Records the directory type when the user selects the download directory - through download preference. May be recorded even when the user didn't - download anything. - - - - - - Removed 10/2017 in Issue 722320 with the removal of - DownloadNotificationService.hideDanglingSummaryNotification. - - dtrainor@chromium.org - - Android: Records the situation where we try to fix a standalone downloads - summary notification, which shouldn't be visible to the user. True if the - notification was a foreground notification, in which case we can't dismiss - it and need to attempt a more drastic workaround. False if it was a normal - notification and we can dismiss it easily (this is okay and expected - behavior in some scenarios). - - - - - qinmin@chromium.org - - Android: Records the number of resumptions for a download by resumption - type. For all resumption types, this is recorded when a download is - finished, completed or cancelled. For automatic resumptions, it is also - recorded when user manually resumes the download to clear the auto retry - count. - - - - - qinmin@chromium.org - - Android: Records various counts when requesting the storage permission. - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: Records the time it takes from object initialization to the - enterprise policy check completing. This check is often skipped when its - result becomes irrelevant. Histogram has suffixes depending if the timing - was faster or slower than inflation. - - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: Records the time it takes from object initialization to the device - ownership check completing. Histogram has suffixes depending if the timing - was faster or slower than inflation. - - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: Records how long it takes to load the enterprise CCT/ToS fragment. - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: The amount of time spent fetching child account status during the - FRE. Not applicable for light weight FRE. - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: Enterprise FRE cannot fully show the first page until the - appRestrictions call returns. This suffixed histogram measures when fragment - inflation was slower or faster than the appRestrictions call, and wether the - UI had to wait. Note this is recorded for all clients, not just enterprise. - Not applicable for light weight FRE. - - - - - skym@chromium.org - wenyufu@chromium.org - - Android: This suffixed histogram represents the amount of time from when the - FRE intent was initially constructed, until some event in the future occurs. - Not applicable for light weight FRE. - - - - - - Removed 04/2020 because the Privacy Notice is removed from FRE. (See - crbug.com/1065912) - - justincohen@chromium.org - - iOS: Records the status of the privacy page after user taps on the privacy - link on the first run welcome view. This metric is only recorded if and - after the TOS are accepted. This metric is specific to iOS. - - - - - bsazonov@chromium.org - msarda@chromium.org - droger@chromium.org - gogerald@chromium.org - chrome-signin-team@google.com - - Android: Records which states of the "first run experience" have - been reached. Each bucket represents a state and recorded everytime the - state changed. Pages can be double counted if the user goes backwards in the - flow. - - - - - aruslan@chromium.org - - Android: How the user left the sign-in part of the "first run - experience" activity (M-38+). - - - - - qinmin@chromium.org - - Android: Records the duration that a fullscreen video is played after device - rotates from portrait to landscape mode for the first time, and before it - exits fullscreen. If there is no device rotation or if the video starts with - landscape mode, it is not recorded. If there are mutiple rotations between - portrait and landscape mode, only one record is emitted and it is equal to - the time period from the first rotation to the moment when the video exits - fullscreen. - - - - - qinmin@chromium.org - - Android: Records the duration that a fullscreen video is played in landscape - mode. If a video starts playing in landscape mode, and then it is switched - back and forth between landscape and portrait mode, only the time period - before the first switch is accounted. If a video starts playing in portrait - mode, it is not recorded. - - - - - qinmin@chromium.org - - Android: Records whether a fullscreen video is switched from landscape to - portrait mode at any point during playback. - - - - - qinmin@chromium.org - - Android: Records the device orientation when a video enters fullscreen. The - value is true if device orientation is portrait, or false otherwise. The - video doesn't necessarily needs to be in a playing state. - - - - - qinmin@chromium.org - - Android: Records the duration that a fullscreen video is played in portrait - mode. If a video starts playing in portrait mode, and then it is switched - back and forth between landscape and portrait mode, only the time period - before the first switch is accounted. If a video starts playing in landscape - mode, it is not recorded. - - - - - qinmin@chromium.org - - Android: Records whether a fullscreen video is switched from portrait to - landscape mode at any point during playback. - - - - - qinmin@chromium.org - - Android: Records whether a video has a larger height than width when it - enters the fullscreen mode. - - - - - peconn@chromium.org - peter@chromium.org - - Recorded when Chrome on Android is launched to an internal Chrome scheme - (chrome://, chrome-native://, about://) by a first party app (not Chrome). - This metric is to be used to determine whether any first party app uses the - feature, and whether we can remove it. - - - - - - - tedchoc@chromium.org - - Android: Count of page loads started by intents from external apps. In M87 - the reporting of this histogram was updated to exclude intents sent from - Chrome itself. - - - - - gangwu@chromium.org - jdonnelly@chromium.org - - Recorded when user long presses and pastes clipboard content into omnibox. - The value indicates the estimated age of the clipboard. - - Intended to be compared to Omnibox.ClipboardSuggestionShownAge. - - - - - stkhapugin@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Recorded when the omnibox popup is closed. Indicates the duration it was - open. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - - When a user presses an omnibox suggestion based on the content of the - clipboard, this histograms records how long ago Chrome detected a change in - the clipboard. - - Intended to be compared to Omnibox.ClipboardSuggestionShownAge. - - If Chrome never detected a change to the clipboard, no clipboard suggestion - is shown, meaning this histogram will never be emitted to. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times the signin promo is implicitly dismissed (by closing - the bookmark manager) per impression. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times one of the "sign in" buttons (any of the - signed-out "Sign in to Chrome" button, the "Continue as - |name|" button, or the "Not |email|?" button) is clicked per - impression. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times the explicit "X"-to-close button is clicked - per impression. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times the signin promo is implicitly dismissed (by closing - the settings view) per impression. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times one of the "sign in" buttons (any of the - signed-out "Sign in to Chrome" button, the "Continue as - |name|" button, or the "Not |email|?" button) is clicked per - impression. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts how many times the explicit "X"-to-close button is clicked - per impression. - - - - - - Removed from the code 03/2020 - - tedchoc@chromium.org - - For cold starts of Chrome (native not initialized at the time of intent), - record in ChromeTabbedActivity whether the intent had the effect of opening - a new page or was a restore of last session. - - - - - tedchoc@chromium.org - twellington@chromium.org - - Android only. - - The number of times the tabbed mode of Chrome is launched within a given 24 - hour window. Recall that custom tabs is not considered tabbed mode. A - "launch" here is defined as anytime the tabbed mode is made - visible (foregrounded), but all Chrome activities must be completely hidden - before we'll count an additional launch. It includes all kinds of intents, - such as MAIN and VIEW. By ensuring all Chrome activities are hidden, we - avoid overcounting by going to Settings and returning to Chrome. - - This launch definition includes some items one might not expect: (i) click a - link in Chrome that opens in another app, then click back. (ii) have Chrome - in the foreground, then the screen times out (goes blank) or engages the - lock screen, then wake up/unlock the device. (iii) switch to - "Recents", then re-select Chrome. In all these cases, Chrome has - gone to the background so returning to it counts as another launch. - - The value reported reflects activity over a 24-hour window in the past, - possibly the distant past. Reporting is controlled by storing an initial - launch timestamp and counting all "launches" as a count until a - new launch happens after the 24hr window has elapsed (at this point, a new - 24hr window is started). The count is reported at the start of the next 24hr - window, so this is a retroactive count. For example, if a user uses Chrome - in one day two months ago, then doesn't use Chrome at all, then when Chrome - launches today it'll report the value during that 24-hour window. - - - - - tedchoc@chromium.org - twellington@chromium.org - yfriedman@chromium.org - - Android: The time it takes from creating an intent for ChromeActivity to - activity creation. This includes activity creation time spent in the - framework. - - - - - tedchoc@chromium.org - twellington@chromium.org - - The type of launching Chrome mobile app, e.g launch by hitting icon. - - Only recorded for tabbed mode launches of Chrome. Recall that custom tabs is - not considered tabbed mode. - - - - - - Deprecated and removed from the code 02/2020 - - tedchoc@chromium.org - twellington@chromium.org - - Android: Tracks whether a homepage was loaded on startup of - ChromeTabbedActivity. Launching a homepage is conditional on a homepage - being configured on the device and the absence of any existing tabs, so it - will only happen on a subsets of cold starts. The metric splits out whether - the homepage was the NTP or some other URL. - - - - - - Removed and removed from the code 05/2018 - - mariakhomenko@chromium.org - - Android: Records the first action the user does within 10s of starting - Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the - starting intent is of type MAIN. - - - - - - Removed 7/2019. No longer tracked. - - dtrainor@chromium.org - - Android: Number of instances of Chrome currently open during a MultiWindow - session. Emitted every time Chrome is paused. Only emitted on Android - MultiWindow devices. - - A MultiWindow session is any period of time that Chrome was not used in a - full screen mode but together with another Activity that is visible at the - same time. This is only supported in a few Android models. - - - - - - Removed 7/2019. No longer tracked. - - twellington@chromium.org - tedchoc@chromium.org - - Android: percent of the screen available for Chrome during a multi-window - session. Emitted every time chrome is paused. Only emitted on Android - MultiWindow devices. - - A multiwindow session is any period of time that Chrome was not used in full - screen mode but together with some other application that is visible at the - same time. This is only supported in a few Android models. - - - - - - Removed and removed from the code 05/2018 - - mariakhomenko@chromium.org - - Android: Records the first action the user does within 10s of starting - Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the - starting intent is not of type MAIN, e.g. VIEW, etc. - - - - - - Removed and removed from the code 05/2018 - - knn@chromium.org - - Android: The time since last use until Chrome is launched from the home - screen. This is measured from the time the last tab is closed until a Main - intent is received. Has a minute level precision for first 10 minutes - increasing exponentially till 30 days. - - Note: this metric is broken in M63 and below and only reliable in M64+. - - - - - - Removed and renamed to MobileStartup.ToolbarFirstDrawTime2 due to double - reporting bug (see https://crbug.com/857508). - - yusufo@chromium.org - - Android: The time it takes from launch to the completion of first draw for - Toolbar. This excludes activity creation time spent in framework. - - - - - - No longer useful, deprecated in M82. - - yusufo@chromium.org - - Android: The time it takes from launch to the completion of first draw for - Toolbar. This excludes activity creation time spent in framework. - - - - - - No longer useful, deprecated in M82 (see https://crbug.com/1053190). - - mheikal@chromium.org - - Android: The state of chrome startup at the first time the user focuses the - omnibox, if the user does so within the first 30s of the launch (excluding - activity creation time spent in the framework). - - - - - - Removed and renamed to MobileStartup.ToolbarFirstFocusTime2 due to double - reporting bug (see https://crbug.com/857508). - - pasko@chromium.org - - Android: The time it takes from launch to the first time the user focuses - the omnibox if the user does so within first 30s of the launch. This - excludes activity creation time spent in framework. - - - - - - No longer useful, deprecated in M82. - - pasko@chromium.org - - Android: The time it takes from launch to the first time the user focuses - the omnibox if the user does so within first 30s of the launch. This - excludes activity creation time spent in framework. - - - - - pasko@chromium.org - - Android: The time spent performing toolbar layout inflation. - - - - - pmonette@chromium.org - - Records the result of writing the path of the module blacklist cache to the - registry so that chrome_elf.dll can use it. A value is emitted every time - the cache is updated because another instance of Chrome with a different - User Data directory could have overwritten the path to point to their own - version of the cache. - - - - - pmonette@chromium.org - - The status of a blacklisted module in the process. Recorded when the cache - is updated. - - - - - pmonette@chromium.org - - The result of deleting the module blacklist cache when third-party module - blocking is disabled. Attempting to delete an empty file is considered a - success. - - - - - pmonette@chromium.org - - Records whether the MD5 digest of the module blacklist cache matched the one - recorded in the Local State file. - - - - - pmonette@chromium.org - - Records the number of modules in the module blacklist cache at the time it - was written to disk. - - - - - pmonette@chromium.org - - The result of reading the current module blacklist cache while updating it. - - - - - pmonette@chromium.org - The result of writing the updated module blacklist cache. - - - - anthonyvd@chromium.org - - Represents the amount of bytes in a module that are different on disk and in - memory. Logged when the ModuleIntegrityVerifier determines that a module is - different on disk and in memory after being triggered by an incident. - - - - - - Removed and removed from code as of 05/2015. - - anthonyvd@chromium.org - - Represents the difference in bytes deemed modified by the two - ModuleIntegrityVerifier code paths. The suffix indicates which path had a - higher value. Logged when the ModuleIntegrityVerifier determines that a - module is different on disk and in memory after being triggered by an - incident and the reported byte count for both methods is different. - - - - - grt@chromium.org - - Logged when the relocations in a module are not ordered causing the module - verification to abort. - - - - - - Removed 04/2015; replaced by - ModuleIntegrityVerification.RelocationsUnordered. - - anthonyvd@chromium.org - - Logged when the relocations in a module are not ordered causing the module - verification to abort. The value is the index of the affected module. - - - - - amistry@chromium.org - bgeffon@chromium.org - rockot@google.com - The number of handles sent with a channel message. - - - - amistry@chromium.org - bgeffon@chromium.org - rockot@google.com - - Measures the time taken to fully write a channel message to the underlying - channel. - - - - - amistry@chromium.org - bgeffon@chromium.org - rockot@google.com - The size of a message written to a channel. - - - - amistry@chromium.org - bgeffon@chromium.org - rockot@google.com - - Tracks whether or not a message is written directly to a channel or queued. - - - - - amistry@chromium.org - bgeffon@chromium.org - rockot@google.com - - The number queued messages waiting to be written, measured when a channel - flush is attempted. - - - - - siggi@chromium.org - rockot@chromium.org - - The maximal unread message quota used for the lifetime of a Connector. This - is sampled for a configurable percentage of Connectors only when the feature - MojoRecordUnreadMessageCount is enabled. By default 1% of Connectors are - sampled, as there's some overhead involved in enabling the unread message - quota on a MessagePipe. See //mojo/public/cpp/bindings/lib/connector.cc. - - - - - - The MachPortRelay was deleted in July 2019. - - amistry@chromium.org - erikchen@chromium.org - - Errors that the broker process encounters while trying to send or receive - Mach ports from a child process. - - - - - - The MachPortRelay was deleted in July 2019. - - amistry@chromium.org - erikchen@chromium.org - - Errors that a child process encounters while trying to receive Mach ports - from the broker process. - - - - - - Removed 2/2018. Has not actually been collected for some time. - - rockot@chromium.org - - Measures the time it takes for a new child process to receive an - initialization request from the Mojo shell. This is precisely the duration - of the MojoShellConnectionImpl::BindToMessagePipe() call in ChildThreadImpl. - - - - - - Removed 2/2018. Data no longer useful. - - rockot@chromium.org - - Measures the time it takes for a child to receive its parent platform handle - synchronously from the broker on startup. This only applies to the subset of - platforms on which the sync broker is used. - - - - - - Removed as of 6/2017. - - rockot@chromium.org - - Number of internal Mojo system messages processed synchronously during a - single execution of NodeController::AcceptIncomingMessages(). This is called - any time an event requires internal Mojo system messages to be pumped. - Values below 4 are no longer logged. - - - - - - Removed 2/2018. Data no longer useful. - - rockot@chromium.org - - Number of connected peer nodes tracked by a node. This is emitted any time a - peer is added to or dropped from a node. - - - - - - Removed 2/2018. Data no longer useful. - - rockot@chromium.org - - Number of connected pending child node connections tracked by a node. This - is emitted any time a parent-child node connection is initiated or dropped. - - - - - mek@chromium.org - Methods where leveldb's Mojo environment has IO errors. - - - - - Removed 2020-04. - - mek@chromium.org - - Errors (base::File::Error) encountered by a single leveldb method in - leveldb's Mojo environment. - - - - - - Removed April, 2020. - - mek@chromium.org - chrome-owp-storage@google.com - - When Mojo LevelDBEnv successfully retries an operation that had failed, - record the error from the most recent failed attempt. - - - - - - Removed in 2020-04. - - mek@chromium.org - - Time Mojo LevelDBEnv slept before successfully completing this operation. 0 - means success on the first try, as LevelDBEnv only sleeps when retries are - needed. - - - - - zentaro@chromium.org - cros-peripherals@chromium.org - Tracks mouse acceleration setting changes by the user. - - - - zentaro@chromium.org - cros-peripherals@chromium.org - Tracks mouse acceleration setting on startup. - - - - zentaro@chromium.org - cros-peripherals@google.com - - Tracks mouse sensitivity setting changes by the user. This replaces the old - Mouse.Sensitivity.Changed metric. - - - - - zentaro@chromium.org - cros-peripherals@google.com - - Tracks mouse sensitivity setting on startup. This replaces the old - Mouse.Sensitivity.Started metric. - - - - - lannm@chromium.org - Tracks mouse reverse scroll setting changes by the user. - - - - lannm@chromium.org - Tracks mouse reverse scroll setting on startup. - - - - - - khorimoto@chromium.org - zentaro@chromium.org - Whether mouse scroll acceleration is enabled. - - - - - - khorimoto@chromium.org - zentaro@chromium.org - Mouse scroll sensitivity value. - - - - - Removed as of 6/2013, replaced by Mouse.PointerSensitivity.Changed. - - Please list the metric's owners. Add more owner tags as needed. - Tracks mouse sensitivity setting. - - - - - Removed as of 6/2013, replaced by Mouse.PointerSensitivity.Started. - - Please list the metric's owners. Add more owner tags as needed. - Tracks mouse sensitivity setting on startup. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user mousedown-ed a link and when - the user clicked a link. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - For each click handled by an HTML anchor tag link, whether Blink saw a - mousedown event preceding it. This is only measured for clicks handled by - the anchor tag's default click event handler. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of mousedown events detected at HTML anchor-tag links' default - event handler. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user mouseover-ed a link and when - the user clicked a link. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user mouseover-ed a link and when - the user mouseout-ed a link without click. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of mouseover events detected at HTML anchor-tag links' default - event handler. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The tap gesture events detected before click at HTML anchor-tag links' - default event handler. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time elapsed between when the user tapdown-ed a link and when - the user clicked a link. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of gesturetapdown events detected at HTML anchor-tag links' - default event handler. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of gesturetapunconfirmed events detected at HTML anchor-tag - links' default event handler. - - - - - ppi@chromium.org - - The time it takes to spawn the first child subprocess (including sandbox - init). - - - - - ppi@chromium.org - - The time it takes to spawn child sub processes not counting the first one. - - - - - lizeb@chromium.org - - Time to call fork() or clone(), in ms. Recorded at each fork excluding from - the zygote, only on posix platforms. - - - - - - Removed 08/2016 due to lack of use (Histogram Eraser). - - lassey@google.com - - The time spent waiting for the renderer to acknowledge an input event. - - - - - - Removed 2/2013, renamed. - - Please list the metric's owners. Add more owner tags as needed. - - The time it takes to spawn the first renderer subprocess (including sandbox - init). - - - - - - Removed 2/2013, renamed. - - Please list the metric's owners. Add more owner tags as needed. - - The time it takes to spawn renderer sub processes not counting the first - one. - - - - - ppi@chromium.org - - The number of RenderProcessHosts (i.e. renderer processes) present when each - load completes. This is basically the average number of sub-processes over - time. See also Tabs.TabCountPerLoad. - - - - - - Removed 12/2017 due to lack of usage. - - amaralp@chromium.org - - The length of time the renderer is unresponsive according to the hang - monitor. Recorded when the renderer regains responsiveness. - - - - - - renamed MPArch.IIR_InputEventDelta. - - Please list the metric's owners. Add more owner tags as needed. - - The time spent waiting for the renderer to acknowledge an input event. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - The time spent inside RenderWidgetHost::OnMsgPaintRect. - - - - - Removed 09/2018 as message no longer exists. - - kylechar@chromium.org - vmiura@chromium.org - - The time delta for processing a paint message. On platforms that don't - support asynchronous painting, this is equivalent to - MPArch.RWH_TotalPaintTime. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - The time spent inside RenderWidgetHost::OnMsgScrollRect. - - - - - Removed 10/2017. Replaced with MPArch.RWH_OnMsgResizeOrRepaintACK. - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - jbauman@chromium.org - - Time from tab switch requested to tab appearing on screen (Aura and Mac - only). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time that the user sees a blank white page after switching to a - different tab, while the RenderWidgetHost receives data to paint from the - renderer process. - - - - - vecore@google.com - better-together-dev@google.com - - Indicates the feature state of the Better Together Suite feature. This - metric is emitted to at the creation of the user session (when the user logs - in), and when feature state updates occur. - - - - - vecore@google.com - better-together-dev@google.com - Result of trying to find eligible devices. - - - - vecore@google.com - better-together-dev@google.com - - Breaks down the percentages of reasons when failure occurs on - FindEligibleDevices. - - - - - vecore@google.com - better-together-dev@google.com - Result for when ForceEnrollmentNow is called. - - - - vecore@google.com - better-together-dev@google.com - Result for when ForceSyncNow is called. - - - - vecore@google.com - better-together-dev@google.com - - Breaks down which features failed when attempted to disable. - - - - - vecore@google.com - better-together-dev@google.com - Breaks down which features failed when attempted to enable. - - - - vecore@google.com - better-together-dev@google.com - Result of enabling and disabling features for devices. - - - - vecore@google.com - better-together-dev@google.com - - Breaks down the percentages of reasons when failure occurs on - SetSoftwareFeatureState. - - - - - vecore@google.com - better-together-dev@google.com - - Compares when the Forget Host Button is pressed and when setup completes. - - - - - vecore@google.com - better-together-dev@google.com - - Provides a count of how many times each page of the MultiDevice setup flow - was reached. This allows analysis of user dropoff between subsequent pages. - - The formula "Success page" / "Start page" provides the - overall "success rate" of the MultiDevice setup flow, at a quick - glance. - - The sum of each bucket's count is not meaningful. - - - - - vecore@google.com - better-together-dev@google.com - - A histogram measuring the success rate of authenticating a BLE channel once - a GATT connection has been established. This metric measures the effective - rate; i.e., a failure followed by a successful retry is counted as a - success. - - - - - vecore@google.com - better-together-dev@google.com - - A time histogram measuring the time from the moment a GATT connection is - made to the remote device, to the moment that an authenticated channel is - established with the remote device. - - In this context, "background" refers to the BLE advertising scheme - under which the remote device is persistently advertising "in the - background" at low power. - - - - - vecore@google.com - better-together-dev@google.com - - A time histogram measuring the time from the moment a background - advertisement is received, to the moment that a GATT connection is made to - the remote device. - - In this context, "background" refers to the BLE advertising scheme - under which the remote device is persistently advertising "in the - background" at low power. - - - - - vecore@google.com - better-together-dev@google.com - - A time histogram measuring the time it takes to create a secure connection - to a remote device, from the moment a SecureChannelService client asks for a - new connection (start scanning), to the moment that an authenticated channel - is established with the remote device. - - In this context, "background" refers to the BLE advertising scheme - under which the remote device is persistently advertising "in the - background" at low power. - - - - - vecore@google.com - better-together-dev@google.com - - A time histogram measuring the time it from the moment SecureChannelService - starts scanning for a background advertisement, to the moment that it - establishes a GATT connection to the remote device. - - In this context, "background" refers to the BLE advertising scheme - under which the remote device is persistently advertising "in the - background" at low power. - - - - - vecore@google.com - better-together-dev@google.com - - A time histogram measuring the time it from the moment SecureChannelService - starts scanning for a background advertisement, to the moment that it - receives an advertisement from the expected remote device. - - In this context, "background" refers to the BLE advertising scheme - under which the remote device is persistently advertising "in the - background" at low power. - - - - - vecore@google.com - better-together-dev@google.com - - A histogram measuring the success rate of authenticating a BLE channel once - an advertisement has been received. This metric measures the effective rate; - i.e., a failure followed by a successful retry is counted as a success. - - - - - vecore@google.com - better-together-dev@google.com - - A histogram measuring the success rate of creating a GATT connection once an - advertisement has been received. This metric measures the effective rate; - i.e., a failure followed by a successful retry is counted as a success. - - - - - vecore@google.com - better-together-dev@google.com - - Breaks down percentages of host statuses. This metric is emitted to at the - creation of the user session (when the user logs in), and when host status - updates occur. - - - - - nohle@chromium.org - better-together-dev@google.com - - Records if a multi-device host device has all of the crypto data necessary - for secure communication via Bluetooth. This will be false if v2 DeviceSync - data is not yet decrypted, for instance. Emitted when checking if a host is - verified. This occurs only if there is an existing host, and the check - occurs during start-up, when the host changes, or when new devices are - synced from CryptAuth. - - - - - vecore@google.com - better-together-dev@google.com - - Compares when the Verify Host Button is pressed to when setup completes. - - - - - cvandermerwe@google.com - better-together-dev@google.com - - Indicates the feature state of the Wifi Sync V2 feature. This metric is - emitted to at the creation of the user session (when the user logs in), and - when feature state updates occur. - - - - - vecore@google.com - better-together-dev@google.com - hsuregan@chromium.org - - Breaks down the percentage of users who either accepted or declined - MultiDevice OOBE setup. - - - - - vecore@google.com - better-together-dev@google.com - - Counts the number of each MultiDevice setup notification clicked by a user. - This metric should be compared with MultiDeviceSetup_NotificationShown. - - - - - vecore@google.com - better-together-dev@google.com - - Counts the number of each MultiDevice setup notification dismissed by a - user. This metric should be compared with - MultiDeviceSetup_NotificationShown. - - - - - vecore@google.com - better-together-dev@google.com - - Counts the number of each MultiDevice setup notification shown to a user. - - - - - - Removed 11/2017. Analysis confirms that the number of discards increases - with the number of logged in users. No action will be taken based on this - information. - - skuhne@chromium.org - - The relation of discarded tabs vs. the amount of simultaneous users. The - counts are the number of discards and the buckets are the number of users. - Since the count values are absolute numbers, they need to be normalized - before use - so divide the counts by the percentage of users per session - found under 'MultiProfile.UsersPerSessionIncremental'. - - - - - - Removed 09/2017 when side-by-side multi-profile mode was removed. There is - now only one multi-profile mode (separate desktop). See the metric - 'MultiProfile.UsersPerSessionIncremental' for overall usage of the - multi-profile feature on Chrome OS. - - skuhne@chromium.org - - The session counter for different multi profile modes which gets stored once - per session at the beginning of the session. - - - - - - Retired in M86. - - skuhne@chromium.org - - Count the number of times each UI path is taken for signing into a new - account in a Chrome OS multiprofile session. UI paths include the system - tray and the user account switcher on the browser frame. - - - - - skuhne@chromium.org - - Count the number of times each UI path is taken for switching the active - account in a Chrome OS multiprofile session. UI paths include the system - tray and the keyboard shortcut. - - - - - - Removed 04/2018. Was not being maintained - some cases leading to teleport - were not captured. See counts of 'MultiProfile.TeleportWindowType' to assess - the usage of the teleport window feature. - - skuhne@chromium.org - - Counts the number of window teleportations when using separated desktop - mode. - - - - - skuhne@chromium.org - - Counts the number of teleported windows by types in separated desktop mode. - - - - - - Removed 3/2014, renamed to MultiProfile.UsersPerSessionIncremental. - - skuhne@chromium.org - - The number of users simultaneously signed into a multiprofile session on - Chrome OS. This is recorded upon session end. - - - - - skuhne@chromium.org - - The number of users simultaneously signed into a multiprofile session on - Chrome OS. This is recorded whenever a user gets added to the session. To - get the correct count, all following counts must be subtracted. Example: If - 100 single user, 20 two user and 5 three user sessions, there were - 100-20-5=75 single user sessions, 100-80=20 dual user sessions and so on. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - Type of NaCl/PNaCl application/extension. Recorded at plugin creation time - after the permission check. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - When the browser started, what happened with the NaCl helper process? - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - When a NaCl application process was created, what had happened with the NaCl - helper process when the browser was started? - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The OS/Architecture of a nexe that was loaded. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The status code returned when trying to load a manifest inside an installed - app. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The status code returned when trying to load a manifest from a source other - than an installed app. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The status code returned when trying to load a NaCl executable inside an - installed app. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The status code returned when trying to load a NaCl executable from a source - other than an installed app. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The error code returned by NaCl's Chrome plugin. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The error code returned by NaCl's Chrome plugin, but only for installed - apps. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The error code returned by NaCl's Chrome plugin, but excluding installed - apps. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The error code returned by NaCl's sel_ldr. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The error code returned by NaCl's sel_ldr, but only for installed apps. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The error code returned by NaCl's sel_ldr, but excluding installed apps. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - Was the manifest specified as a data URI rather than a .nmf file? - - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - - The time it took to download the manifset file for a Native Client module. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The time a NaCl module ran before it crashed. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The time a NaCl module ran without crashing, at shutdown. - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - - The time it took to download the main .nexe for a Native Client module. - - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - - The size of the main .nexe file downloaded for a Native Client module. - - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - - The time it took between the Native Client plugin initialization and when - proxied execution of the NaCl module begins. This is the general startup - overhead of running as a NaCl module vs a trusted PPAPI plugin. - - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - - The time it took between the Native Client plugin initialization and when - proxied execution of the NaCl module begins. This is the general startup - overhead of running as a NaCl module vs a trusted PPAPI plugin. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The optimization level set for the initial Portable Native Client - translation from bitcode to native code. - - - - - - Removed 6/2011, renamed. - - adamk@chromium.org - The OS/Architecture of a nexe that was loaded. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - Did the Portable Native Client translation cache find an executable - translated from bitcode? - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The rate for compiling a Portable Native Client bitcode file to an object - file in Kilobytes per second. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to compile a Portable Native Client bitcode file to an - object file. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to link a Portable Native Client generated object file into - a Native Client executable. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to load and validate the Portable Native Client compiler. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to load and validate the Portable Native Client linker. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The percentage of a Portable Native Client application that is compiled by - the time the application is fully downloaded (compile and download happen in - parallel). - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The rate for completely translating a Portable Native Client bitcode file - into a Native Client executable and caching the result in Kilobytes per - second. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The total time it took to completely translate a Portable Native Client - bitcode file into a Native Client executable, and cache the result. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The time it took the NaCl module to shut down. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The size of the manifest file. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The size of the main .nexe file downloaded for a Native Client module. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The size of the main .pexe bitcode file downloaded for a Portable Native - Client module. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The size of the main .pexe bitcode file divided by the size of the .nexe - that is the result of translating the bitcode file, times 100. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The size of the main .nexe file that is the result of translating a Portable - Native Client .pexe bitcode file. This reflects the amount of cache - consumed. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - The time it took to load the NaCl module into sel_ldr. - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to load the NaCl module into sel_ldr. Normalized by the - size of the .nexe, in megabytes. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to download the manifset file for a Native Client module. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took between the Native Client plugin initialization and when - proxied execution of the NaCl module begins. This is the general startup - overhead of running as a NaCl module vs a trusted PPAPI plugin. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took between the Native Client plugin initialization and when - proxied execution of the NaCl module begins. This is the general startup - overhead of running as a NaCl module vs a trusted PPAPI plugin. Normalized - by the size of the .nexe, in megabytes. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to download the main .nexe for a Native Client module. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took to download the main .nexe for a Native Client module. - Normalized by the size of the .nexe, in megabytes. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took between the Native Client plugin initialization and when - the NaCl module is ready to be used. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - The time it took between the Native Client plugin initialization and when - the NaCl module is ready to be used. Normalized by the size of the .nexe, in - megabytes. - - - - - - Removed 5/2011, data is duplicated by NaCl.NexeStartupTime, and normalizing - to 'tab opens' is unusual. - - adamk@chromium.org - - The number of times that Native Client has been started by loading a .nexe - compared to the number of times that a tab has been opened. - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - Did a validation cache query find a previously known validation result? - - - - - dschuff@chromium.org - adamk@chromium.org - bbudge@chromium.org - - Was the validation cache updated with a new validation result? - - - - - - Removed in M77. This metric is not sufficiently used. - - eugenebut@chromium.org - pkl@chromium.org - - The number of times that Chrome detected that a request to download and - install another Google iOS app completed successfully. - - - - - mek@chromium.org - src/content/browser/native_file_system/OWNERS - - Did the user confirm read access to a directory via the Native File System - API. - - - - - mek@chromium.org - src/content/browser/native_file_system/OWNERS - - The number of files a user picked using the file picker in the Native File - System API. Recorded as 0 if the user cancelled the picker. - - - - - mek@chromium.org - src/content/browser/native_file_system/OWNERS - - The result of an attempt to request write permission to a file or directory - via the Native File System API. - - - - - mek@chromium.org - src/content/browser/native_file_system/OWNERS - - Records if the file or directory selected by the user through the Native - File System API is considered a sensitive directory, and thus was blocked. - - - - - mek@chromium.org - src/content/browser/native_file_system/OWNERS - - The result of an attempt to request write permission to a file or directory - via the Native File System API. - - - - - simmonsjosh@google.com - src/chrome/browser/chromeos/smb_client/OWNERS - - The method used to authenticate to a share. This is called on each attempted - mount. - - - - - simmonsjosh@google.com - src/chrome/browser/chromeos/smb_client/OWNERS - - The result of the GetShares operation for Native SMB File Share. This is - recorded after the D-Bus call to GetShares returns. - - - - - simmonsjosh@google.com - src/chrome/browser/chromeos/smb_client/OWNERS - - The number of active mounts that a user has. This is recorded after a share - has been successfully mounted. - - - - - simmonsjosh@google.com - src/chrome/browser/chromeos/smb_client/OWNERS - - The result of the mount operation for Native SMB File Share. This is - recorded after the D-Bus call to Mount returns. - - - - - zentaro@chromium.org - - The number of entries read when calling ReadDirectory. This is recorded - after the D-Bus call to ReadDirectory returns. - - - - - zentaro@chromium.org - - The duration of ReadDirectory call to SmbProvider in milliseconds. This is - recorded after the D-Bus call returns. - - - - - zentaro@chromium.org - - The result of the Remount operation during startup. This is recorded after - the D-Bus call to Remount returns. - - - - - pkasting@chromium.org - robliao@chromium.org - Time required to run ui::NativeTheme::GetSystemColor(). - - - - pkasting@chromium.org - robliao@chromium.org - Records if the color provider computed the color. - - - - shivanisha@chromium.org - csharrison@chromium.org - - This metric logs true if all the previous entries are marked to be skipped - on back/forward button via the history manipulation intervention. This is - logged when back button is pressed (see crbug.com/907167). The goal of the - intervention is to intervene against pages that manipulate browser history - such that the user is not able to use the back button to go to the previous - site they interacted with. - - - - - shivanisha@chromium.org - csharrison@chromium.org - - This metric counts the number of entries the history manipulation - intervention would have skipped when the user presses the back button (see - crbug.com/907167). The goal of the intervention is to intervene against - pages that manipulate browser history such that the user is not able to use - the back button to go to the previous site they interacted with. - - - - - clamy@chromium.org - The cache flags set on back-forward navigations. - - - - shivanisha@chromium.org - csharrison@chromium.org - - This metric counts the number of entries the history manipulation - intervention would have skipped when the user presses the forward button - (see crbug.com/907167). The goal of the intervention is to intervene against - pages that manipulate browser history such that the user is not able to use - the back button to go to the previous site they interacted with. - - - - - - Removed 2018-02, replaced by Navigation.IsSameProcess.BackForward. - - clamy@chromium.org - - Whether the back-forward navigation lead to a change of process or not. - - - - - shivanisha@chromium.org - csharrison@chromium.org - - This metric logs true if the existing entry being navigated to is marked to - be skipped on back/forward UI. This is logged at the start of navigation - initiated using long-press back/forward button. - - - - - - Removed 2018-02, replaced by - Navigation.ReadyToCommitUntilCommit.BackForward. - - clamy@chromium.org - - The time needed to commit a back forward-navigation once it is ready to - commit. This is the time between ReadyToCommit and DidFinishNavigation (for - a navigation that commits). - - - - - shivanisha@chromium.org - csharrison@chromium.org - - Whether an entry in the back-forward list is marked to be skipped on - subsequent back/forward button clicks as part of the history manipulation - intervention. This is logged when the entry is navigated away from. The goal - is to intervene against pages that manipulate browser history such that the - user is not able to use the back button to go to the previous site they - interacted with. - - - - - - Removed 2018-02, replaced by Navigation.TimeToReadyToCommit.BackForward. - - clamy@chromium.org - - The time delta between the start of a back-forward navigation and the time - it was ready to commit. - - - - - clamy@chromium.org - Whether the back-forward navigation was served from cache. - - - - msramek@chromium.org - - Recorded when a navigation is deferred while clearing site data. Indicates - how much time the clearing took. - - - - - msramek@chromium.org - - The parameters of the Clear-Site-Data header. Recorded when the header is - successfully parsed. - - - - - - Removed 11/2019 in favor of - Previews.DeferAllScript.RedirectLoopDetectedUsingCache. - - dougarnett@chromium.org - - Records when a client redirect cycle that is directly back to the referrer - is detected. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logs the error code for each navigation commit timeout. This will be used to - debug http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logs whether this was a main frame navigation for each navigation commit - timeout. This will be used to debug http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logged with the status of the renderer process for each navigation commit - timeout. This will be used to debug http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logged with the status of the network service for each navigation commit - timeout. This will be used to debug http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logged with the time since the last network service crash if available for - each navigation commit timeout. This will be used to debug - http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logs the time it takes to make a round trip call to the network service for - each navigation commit timeout. This will be used to debug - http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - Logged with the navigation URL scheme for each navigation commit timeout. - This will be used to debug http://crbug.com/934317. - - - - - - Removed 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV2. - - dgrogan@chromium.org - - Why and if cross-origin documents would be loaded in a world where we defer - loading until they are visible. - - - - - - Removed 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV3. - - dgrogan@chromium.org - - Why and if cross-origin documents would be loaded if we were to defer - loading as long as possible. - - - - - - Removed 3/2017 in favor of Navigation.DeferredDocumentLoading.StatesV4. - - dgrogan@chromium.org - - Why and if cross-origin documents would be loaded if we were to defer - loading as long as possible. Difference from V2: frames positioned both - above and to the left of the page have their own bucket and are no longer - counted in the "above" bucket. - - - - - - Removed 11/2018 because LazyLoading has real stats now. - - dgrogan@chromium.org - - Why and if cross-origin documents would be loaded if we were to defer - loading as long as possible. Changes from V3: replace detailed reasons with - summaries for four strategies. E.g. any document that would load under a - strategy of loading when a frame is two screens away is logged to the - WouldLoad2Screens AND WouldLoad3Screens bucket. We only record documents - below the current viewport, not to the right of it. - - - - - - Removed 03/2019 in favor of - Navigation.DownloadPolicy.LogArbitraryPolicyPerDownload and - Navigation.DownloadPolicy.LogPerPolicyApplied. - - csharrison@chromium.org - yaoxia@chromium.org - - When a navigation results in a download, logs the download policy applied to - that navigation. - - - - - csharrison@chromium.org - yaoxia@chromium.org - - When a navigation results in a download, logs the download policy applied to - that navigation. This is logged once per download and when multiple policies - exist, an arbitrary one will be chosen. - - - - - csharrison@chromium.org - yaoxia@chromium.org - - When a navigation results in a download, for each download policy applied to - that navigation, logs the policy. - - - - - estark@chromium.org - security-enamel@chromium.org - - The amount of time that an HTTP page was in the foreground. Recorded on - every page close/transition. - - - - - estark@chromium.org - security-enamel@chromium.org - - The amount of time that an HTTPS page was in the foreground. Recorded on - every page close/transition. - - - - - estark@chromium.org - security-enamel@chromium.org - - The percentage of time that HTTPS pages were in the foreground, as compared - to total foreground time. Recorded whenever user metrics are uploaded. - - - - - - Removed 03/2017 in Issue 703460. - - palmer@chromium.org - - Whether the navigation was to a URL that had embedded credentials. - - - - - - - mpearson@chromium.org - amaralp@chromium.org - chrome-analysis-team@google.com - - Emitted every time a user uses a Home button to go to their home page. - Records whether the page is chrome-internal (most likely the New Tab Page or - about:blank) or not (most likely an actual web site). For the purpose of - this histogram, about:, chrome: and chrome-native: are considered - chrome-internal; everything else is not. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - Removed May 2019 - - csharrison@chromium.org - - Records whether the InterceptNavigationThrottle ignored the navigation. This - is recorded at the end of every navigation the throttle observes. - - - - - - Removed May 2019 - - csharrison@chromium.org - - The microseconds it takes for the InterceptNavigationThrottle to determine - if the navigation should be ignored, at WillStartRequest time. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ajuma@chromium.org - eugenebut@chromium.org - - Logged when NavigationContext is null inside -[WKNavigationDelegate - webView:didFailProvisionalNavigation]. If Chrome stopped logging this metric - it means that it is now safe to remove workaround for - https://bugs.webkit.org/show_bug.cgi?id=198794. - - - - - - Removed from code April 2020. - - eugenebut@chromium.org - - Counts slow/fast back/forward WKWebView navigations on iOS. Fast navigation - is a back/forward navigation done with WKBackForwardList. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Whether the navigation commits in a process that is locked to an origin. - Logged at ready-to-commit time for every navigation excluding same-document - navigations and errors. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Whether the navigation commits in a process that is locked to an origin. - Logged at ready-to-commit time for every navigation that commits with a HTTP - or HTTPS URL scheme, excluding same-document navigations and errors. - - - - - - Removed from code March 2018. - - cjhopman@chromium.org - nyquist@chromium.org - - Signifies whether a succesfully finished page load for the main frame - content width fits within the device width and/or has a fixed page scale. - - - - - arthursonzogni@chromium.org - clamy@chromium.org - nasko@chromium.org - - Whether a main frame navigation led to a change of BrowsingInstance or not. - - - - - clamy@chromium.org - nasko@chromium.org - Whether the navigation led to a change of process or not. - - - - arthursonzogni@chromium.org - clamy@chromium.org - nasko@chromium.org - - Whether the navigation led to a change of SiteInstance or not. - - - - - - - boliu@chromium.org - alexmos@chromium.org - src/base/android/OWNERS - - The type of the source of a load from LoadIfNecessary. Recorded when - LoadIfNecessary starts a page load. For example, on Android, - kRequestedByClient is recorded when user switch back to a tab with a dead - renderer, which causes the tab to reload. - - - - - michaelpg@chromium.org - yilkal@chromium.org - cros-families-eng@google.com - - The number of frames that are present in a WebContents. Recorded once when - the main frame finishes loading. - - - - - michaelpg@chromium.org - yilkal@chromium.org - cros-families-eng@google.com - - The maximum number of loaded frames that are present in a WebContents. - Recorded once when the main frame is moving away from current page. This can - be when the WebContents is being destroyed or when it starts loading new - content. - - - - - meacer@chromium.org - security-enamel@chromium.org - - Site engagement level of the URL of the top frame of a navigation. Only - counts HTTP or HTTPS URLs and ignores downloads. - - - - - meacer@chromium.org - security-enamel@chromium.org - - Site engagement level of the URL of the top frame of a form submission. This - is a subset of Navigation.MainFrame.SiteEngagementLevel. - - - - - - Removed 03/2017 in Issue 703460. - - palmer@chromium.org - - Whether the main-frame navigation was to a URL that had embedded - credentials. - - - - - - Removed from code June 2020. Replaced with - Navigation.MainFrameHasRTLDomain2. Navigation.MainFrameHasRTLDomain was - logged differently for iOS and Navigation.MainFrameHasRTLDomain2 does not - have this discrepancy. - - cthomp@chromium.org - security-enamel@chromium.org - - Whether the main-frame navigation was to a URL with an RTL domain name. This - is only recorded for finished navigations and not attempts. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Whether the main-frame navigation was to a URL with an RTL domain name. This - is only recorded for finished navigations and not attempts. - - - - - - Removed from code June 2020. Replaced with - Navigation.MainFrameHasRTLDomainDifferentPage2. - Navigation.MainFrameHasRTLDomainDifferentPage was logged differently for iOS - and Navigation.MainFrameHasRTLDomainDifferentPage2 does not have this - discrepancy. - - cthomp@chromium.org - security-enamel@chromium.org - - Whether the main-frame navigation was to a URL with an RTL domain name, - recorded for each main-frame avigation that replaces a document object. This - is not reported for reference fragment navigations, pushState/replaceState - or same page history navigation. This is only recorded for finished - navigations and not attempts. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Whether the main-frame navigation was to a URL with an RTL domain name, - recorded for each main-frame avigation that replaces a document object. This - is not reported for reference fragment navigations, pushState/replaceState - or same page history navigation. This is only recorded for finished - navigations and not attempts. - - - - - - Removed from code June 2020. Replaced with Navigation.MainFrameProfileType2. - Navigation.MainFrameProfileType was logged differently for iOS and - Navigation.MainFrameProfileType2 does not have this discrepancy. - - rhalavati@chromium.org - chrome-privacy-core@google.com - - The browser profile type for each main-frame navigation, recorded after - navigation completion, including NTP. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - The browser profile type for each main-frame navigation, recorded after - navigation completion, including NTP. - - - - - - Removed from code June 2020. Replaced with Navigation.MainFrameScheme2. - Navigation.MainFrameScheme was logged differently for iOS and - Navigation.MainFrameScheme2 does not have this discrepancy. - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation. This is only recorded - for finished navigations and not attempts. - - - - - - Removed from code October 2017. - - meacer@chromium.org - - The mime type of the data: URL for each main-frame navigation. This only - contains mime types that can run scripts. This is only recorded for finished - navigations and not attempts. - - - - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation. This is only recorded - for finished navigations and not attempts. - - - - - - Removed from code June 2020. Replaced with - Navigation.MainFrameSchemeDifferentPage2. - Navigation.MainFrameSchemeDifferentPage was logged differently for iOS and - Navigation.MainFrameSchemeDifferentPage2 does not have this discrepancy. - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation that replaces a - document object. This is not reported for reference fragment navigations, - pushState/replaceState or same page history navigation. This is only - recorded for finished navigations and not attempts. - - - - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation that replaces a - document object. This is not reported for reference fragment navigations, - pushState/replaceState or same page history navigation. This is only - recorded for finished navigations and not attempts. - - - - - - Removed from code June 2020. Replaced with - Navigation.MainFrameSchemeDifferentPageOTR2. - Navigation.MainFrameSchemeDifferentPageOTR was logged differently for iOS - and Navigation.MainFrameSchemeDifferentPageOTR2 does not have this - discrepancy. - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation that replaces a - document object while in incognito. This is not reported for reference - fragment navigations, pushState/replaceState or same page history - navigation. This is only recorded for finished navigations and not attempts. - - - - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation that replaces a - document object while in incognito. This is not reported for reference - fragment navigations, pushState/replaceState or same page history - navigation. This is only recorded for finished navigations and not attempts. - - - - - - Removed from code June 2020. Replaced with Navigation.MainFrameSchemeOTR2. - Navigation.MainFrameSchemeOTR was logged differently for iOS and - Navigation.MainFrameSchemeOTR2 does not have this discrepancy. - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation while in incognito. - This is only recorded for finished navigations and not attempts. - - - - - elawrence@chromium.org - estark@chromium.org - - The scheme of the URL for each main-frame navigation while in incognito. - This is only recorded for finished navigations and not attempts. - - - - - jam@chromium.org - kinuko@chromium.org - - The sum of all the times spent posting tasks between the UI and IO threads - inside NavigationURLLoaderImpl. Recorded when each frame navigation gets the - response. - - Note: This metric drops reports on clients with low-resolution clocks, which - means these reports will be biased against a portion of the population on - Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - clamy@chromium.org - nasko@chromium.org - - Overhead time spent handling the OnBeforeUnload event from the browser - standpoint. More precisely, it is the total time between dispatch and - acknowledgment of the BeforeUnload event on the browser side, minus the - actual time spent executing the BeforeUnload handlers on the renderer side. - - - - - falken@chromium.org - chrome-loading@google.com - - Time between the two messages OnReceiveResponse and - OnStartLoadingResponseBody as observed by the browser process during a - navigation by NavigationURLLoader::URLLoaderRequestController. The idea is - to see whether there is a performance cost in having two separate messages, - as the plan is to combine them into one. - - - - - - Removed 2019-01 (M73), replaced by Navigation.ReadyToCommitUntilCommit2 - (same histogram, different bucketing). - - clamy@chromium.org - nasko@chromium.org - - The time needed to commit a navigation once it is ready to commit. This is - the time between ReadyToCommit and DidFinishNavigation (for a navigation - that commits). - - - - - clamy@chromium.org - nasko@chromium.org - - The time needed to commit a navigation once it is ready to commit. This is - the time between ReadyToCommit and DidFinishNavigation (for a navigation - that commits). - - - - - - Removed January 2019 because it wasn't used. - - donnd@chromium.org - - Total length of the redirect URL strings in navigation entry. Logged when - entry is committed. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - kinuko@chromium.org - - Reported when a user triggers reload without any other navigations after the - previous reload in the same page, and the previous reload variant was - RELOAD_MAIN_RESOURCE. Duration time between two reloads is reported. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - kinuko@chromium.org - - Reported when a user triggers reload without any other navigations after the - previous reload in the same page. Duration time between two reloads is - reported. - - - - - - Removed October 2019 - - arthursonzogni@chromium.org - clamy@chromium.org - nasko@chromium.org - - The time needed in the renderer process between receiving the message to - commit the navigation until the navigation has committed. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Whether the navigation commits in a SiteInstance that requires a dedicated - process. Logged at ready-to-commit time for every navigation excluding - same-document navigations and errors. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Whether the navigation commits in a SiteInstance that requires a dedicated - process. Logged at ready-to-commit time for every navigation that commits - with a HTTP or HTTPS URL scheme, excluding same-document navigations and - errors. - - - - - - Obsolete as of 06/2018. - - arthursonzogni@chromium.org - clamy@chromium.org - nasko@chromium.org - - The time delta between when the ResourceHandler is allowed to read the - response's body and when it has completed its first read. - - - - - - Obsolete as of 06/2018. - - arthursonzogni@chromium.org - clamy@chromium.org - nasko@chromium.org - - The time delta between when the ResourceHandler started receiving the - response and when it is allowed to read the response's body. - - - - - - Removed as of 09/2019. - - creis@chromium.org - dtapuska@chromium.org - - Counts session history navigations in sandboxed iframes that disallow top - level navigation, for cases that only stay within the iframe's subtree vs - those that affect other frames instead or as well. - - - - - - Removed August 2018 - - csharrison@chromium.org - - window.location and other scheduled navigation changes can cause the current - provisional load to be aborted. Many times these are initiated without user - gesture. This histogram logs counts of the various aborters. - - - - - - Removed August 2018 - - csharrison@chromium.org - - window.location and other scheduled navigation changes can cause the current - provisional load to be aborted. Many times these are initiated without user - gesture. This histogram logs the time between the aborted navigation start - and the scheduled navigation start, if the aborted navigation has a non-zero - navigationStart value. - - - - - - Removed 4/2017 in Issue 712843. - - palmer@chromium.org - felt@chromium.org - - The scheme of the URL for the first main-frame navigation per origin per - non-OffTheRecord session. - - - - - - Removed 4/2017 in Issue 712843. - - palmer@chromium.org - felt@chromium.org - - The scheme of the URL for the first main-frame navigation per origin per - OffTheRecord session. - - - - - jam@chromium.org - - True counts the events when a https URL commits with a SSL certificate. - False is when the certificate is missing. This should be at 100%, anything - less is probably a bug. - - - - - - Data collected and posted on issue 675833. - - csharrison@chromium.org - - The difference between Now() in the renderer and browser_navigation_start - for browser-initiated navigations if the difference is negative. This value - should ideally only reflect the IPC time between the browser process and - renderer process, but in practice could be skewed by inter-process timing - errors. If the clocks used for TimeTicks are monotonic across processes, all - samples should fall into the Positive bucket. - - - - - - Data collected and posted on issue 675833. - - csharrison@chromium.org - - The difference between Now() in the renderer and browser_navigation_start - for browser-initiated navigations if the difference is positive. This value - should ideally only reflect the IPC time between the browser process and - renderer process, but in practice could be skewed by inter-process timing - errors. If the clocks used for TimeTicks are monotonic across processes, all - samples should fall into the Positive bucket. - - - - - nasko@chromium.org - csharrison@chromium.org - - The time delta between the start of a navigation and the time it is - committed. - - - - - - Removed March 2018 in favor of Navigation.StartToCommit variants. - - carlosk@chromium.org - - Time between the start of a browser-started navigation request in and its - commit. - - - - - - Removed 2019-01 (M73), replaced by Navigation.TimeToReadyToCommit2 (same - histogram, different bucketing). - - clamy@chromium.org - nasko@chromium.org - - The time delta between the start of a navigation and the time it is ready to - commit. - - - - - clamy@chromium.org - nasko@chromium.org - - The time delta between the start of a navigation and the time it is ready to - commit. - - - - - carlosk@chromium.org - - Time between the start of a browser-started navigation request and the - reception of a corresponding ResourceRequest in the network stack. - - - - - - Removed 06/2018 in favor of PageLoad metrics. - - clamy@chromium.org - - Obsolete. Time between receiving an Android Intent and the navigation - commit. - - - - - - Removed 06/2018 in favor of PageLoad metrics. - - clamy@chromium.org - - Obsolete. Time between clicking on a link and the navigation commit. - - - - - - Removed 06/2018 in favor of PageLoad metrics. - - clamy@chromium.org - - Obsolete. Time between receiving an Android intent and the document load - complete event for a navigation in the main frame. - - - - - - Removed 06/2018 in favor of PageLoad metrics. - - clamy@chromium.org - - Obsolete. Time between clicking on a link and the document load complete - event for a navigation in the main frame. - - - - - estark@chromium.org - - When the navigation URL loader receives an OnComplete message from the - network service that contains certificate chains, this histogram records the - size in KB of those pickled certificate chains. This histogram is recorded - by the navigation URLLoader for navigations that fetch from network, for - every request which contains an SSLInfo in its OnComplete notification. - - - - - estark@chromium.org - - Whether the network service's OnComplete message to the navigation URL - loader contains an SSLInfo, which should only be present for main-frame - requests with certificate errors. This histogram is recorded for every - request completion by the navigation URL loader that fetches from network. - - - - - - Removed 10/2019 Milestone 80. - - tbansal@chromium.org - - Tracks the accuracy of the action taken by navigation predictor. Recorded at - the time of page click. - - - - - tbansal@chromium.org - - Tracks action taken by navigation predictor. Recorded at the time of page - load. - - - - - tbansal@chromium.org - ryansturm@chromium.org - - Reports data about the clicked link with regards to whether it was - prerendered by the Navigation Predictor. Recorded when the page is navigated - away from. - - - - - tbansal@chromium.org - ryansturm@chromium.org - - Reports data about the clicked link with regards to whether it was - prerendered by the Navigation Predictor. Recorded when the page is navigated - away from. - - - - - tbansal@chromium.org - ryansturm@chromium.org - - Reports data about the clicked link with regards to whether it was - prerendered by the Navigation Predictor. Recorded when the page is navigated - away from. - - - - - sophiechang@chromium.org - tbansal@chromium.org - - Count of likely URLs for the next navigation as reported by an external - Android app via mayLaunchUrl() Android API. Recorded at the time the - prediction was received by Chrome. - - - - - tbansal@chromium.org - ryansturm@chromium.org - - Set to true if the IP address of the origin of the main frame URL is - publically routable. Recorded everytime a preconnect attempt is made by the - navigation predictor. - - - - - ryansturm@chromium.org - tbansal@chromium.org - - Reports data about the clicked link with regards to whether it was - prerendered by the Navigation Predictor. Recorded when the user clicks a - link. - - - - - meacer@chromium.org - security-enamel@chromium.org - - Tracks events when the currently navigated domain name is a lookalike to one - of the top 10K domains or a domain that the user interacted with, resulting - in a navigation suggestion interstitial. - - - - - bmcquade@chromium.org - - The connection subtype of the network the client is connected to, when the - client is on a cellular connection. This histogram is logged once per UMA - record, if the user is on a cellular connection, at the time the record is - finalized. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on a 2G connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on a 3G connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on a 4G connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on a Bluetooth - connection, before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on an Ethernet - connection, before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen while the - NetworkChangeNotifier thought there was no network connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on an unknown connection - type, before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of the fastest round-trip-time seen on a Wifi connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to a 2G connection and receiving the first network - data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to a 3G connection and receiving the first network - data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to a 4G connection and receiving the first network - data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to a Bluetooth connection and receiving the first - network data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to an Ethernet connection and receiving the first - network data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between disconnecting and receiving the first network data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to an unknown connection type and receiving the first - network data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between switching to a Wifi connection and receiving the first network - data. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via a 2G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via a 3G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via a 4G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via a Bluetooth connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via an Ethernet connection, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while the NetworkChangeNotifier thought there - was no network connection, before the NetworkChangeNotifier detected a - connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via an unknown connection type, - before the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How much data was transfered while connected via a Wifi connection, before - the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on a 2G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on a 3G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on a 4G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on a Bluetooth connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on an Ethernet connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen while the NetworkChangeNotifier - thought there was no network connection, before the NetworkChangeNotifier - detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on an unknown connection type, before - the NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Rough estimate of peak throughput seen on a Wifi connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via a 2G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via a 3G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via a 4G connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via a Bluetooth connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via an Ethernet connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent disconnected, before the NetworkChangeNotifier detected a - connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via an unknown connection type, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - How long was spent connected via a Wifi connection, before the - NetworkChangeNotifier detected a connectivity change. - - This metric is recorded when the NetworkChangeNotifier detects a - connectivity change. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time from ConnectionTypeChanged message until IPAddressChanged message. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - Time between DNS configuration change messages. - - - - - Removed 05/2017 in Issue 677365. - - pauljensen@chromium.org - tbansal@chromium.org - - Records the result of querying the network info of the current active - network. Useful for investigating how frequently the current network was - unblocked, and why it was not unblocked. See http://crbug.com/677365. - - - - - - Code removed long ago. - - pauljensen@chromium.org - - How long does each call to NetworkChangeNotifier::GetConnectionType() take. - - - - - - Removed 5/2017 for Issue 592131. - - pauljensen@chromium.org - - True if the first call to ConnectivityManager.getNetworkInfo(Network) did - not throw NullPointerException, false if it did. Useful for investigating - and avoiding unexpected exceptions, see http://crbug.com/592131. - - - - - - Removed 5/2017 for Issue 592131. - - pauljensen@chromium.org - - Recorded after the first call to ConnectivityManager.getNetworkInfo(Network) - threw a NullPointerException. True if the second call to - ConnectivityManager.getNetworkInfo(Network) did not throw - NullPointerException, false if it did. Useful for investigating and avoiding - unexpected exceptions, see http://crbug.com/592131. - - - - - - Removed 5/2017 for Issue 592131. - - pauljensen@chromium.org - - True if the first call to WifiManager.getConnectionInfo() did not throw - NullPointerException, false if it did. Useful for investigating and avoiding - unexpected exceptions, see http://crbug.com/592131. - - - - - - Removed 5/2017 for Issue 592131. - - pauljensen@chromium.org - - Recorded after the first call to WifiManager.getConnectionInfo() threw a - NullPointerException. True if the second call to - ConnectivityManager.getNetworkInfo(Network) did not throw - NullPointerException, false if it did. Useful for investigating and avoiding - unexpected exceptions, see http://crbug.com/592131. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - Time between IP address change messages. - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time from IPAddressChanged message until ConnectionTypeChanged message. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between going online until we go offline change messages, using new - filtered signal. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between going offline until we go online change messages, using new - filtered signal. - - - - - tbansal@chromium.org - bengr@google.com - - The MCC (mobile country code) and MNC (mobile network code) of the network - operator when a new metrics log is created or when the network connection is - changed. A value of zero means a non-mobile network or the operator code is - unknown. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between going online until we go offline change messages. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between when we thought we went offline and when we received some - network data (a URLRequest read completed). - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Count of how many times we received network data (a URLRequest read - completed) while offline when some data was received at most five seconds - before going online. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between when we received the last network data (a URLRequest read - completed) while offline and when we thought we went online. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Count of how many times we polled the online/offline status before detecting - an offline to online transition. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between going offline until we go online change messages. - - - - - - Removed 6/2018. - - pauljensen@chromium.org - - Time between when we thought we went offline and when we received some - network data (a URLRequest read completed), while polling - NetworkChangeNotifier::GetConnectionType() still told us we were offline. - - - - - cclem@chromium.org - better-together-dev@google.com - - If the Nearby Share certificate manager successfully downloads public - certificates, then record the total number of certificates downloaded across - all pages. - - - - - cclem@chromium.org - better-together-dev@google.com - - If the Nearby Share certificate manager fails to download public - certificates, then record the page number of the page on which the failure - occurred. - - - - - cclem@chromium.org - better-together-dev@google.com - - Records the result of the async ListPublicCertificates API call to the - Nearby Sharing server when the certificate manager periodically downloads - public certificates. Recorded when the async callback is invoked or when the - call times out. - - - - - cclem@chromium.org - better-together-dev@google.com - - If the Nearby Share certificate manager successfully downloads public - certificates, then record the number of pages downloaded by the RPC. - - - - - cclem@chromium.org - better-together-dev@google.com - - Records whether the Nearby Share certificate manager successfully downloaded - public certificates from the server and stored them in leveldb. - - - - - cclem@chromium.org - better-together-dev@google.com - - Records the result of the async GetDecryptedPublicCertificate call in - certificate manager. - - - - - cclem@chromium.org - better-together-dev@google.com - - If the Nearby Share certificate storage successfully initializes the public - certificate database, then record the number of attempts it took. - - - - - cclem@chromium.org - better-together-dev@google.com - - For individual initialization attempts of the Nearby Share certificate - storage public certificate database, record the init status returned by - leveldb_proto. - - - - - cclem@chromium.org - better-together-dev@google.com - - Record success rate of Nearby Share storage operation {Operation}. - - - - - - - - - - - - - cclem@chromium.org - better-together-dev@google.com - - Records the result of the async UpdateDevice API call to the Nearby Sharing - server when the device data updater makes a request. Recorded when the async - callback is invoked or when the call times out. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Breakdown of the locations when SetBrokenAlternateProtocol is called. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Breakdown of how requests which could potentially make use of an alternate - protocol use or don't use the protocol. - - - - - - Removed 10/2014. - - dschinazi@chromium.org - src/net/OWNERS - - Breakdown of how requests which could potentially make use of an alternate - protocol use or don't use the protocol. Loaded data for 1000 servers and we - have persisted 1000 MRU servers. - - - - - - Removed 10/2014. - - dschinazi@chromium.org - src/net/OWNERS - - Breakdown of how requests which could potentially make use of an alternate - protocol use or don't use the protocol. Loaded data for 200 servers and we - have persisted 1000 MRU servers. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Breakdown of how requests which could potentially make use of an alternate - protocol use or don't use the protocol, for connections to Google servers. - - - - - tbansal@chromium.org - dschinazi@chromium.org - src/net/OWNERS - - Positive net error codes that failed alternative protocol requests end with. - Recorded only when an alternative job fails, and the main job succeeds. - - - - - - Obsoleted in April 2020. - - tbansal@chromium.org - rajendrant@chromium.org - robertogden@chromium.org - - Positive net error codes that failed alternative proxy requests end with. - Recorded when an alternative job fails, whether or not the main job - succeeds. - - As of M66 this superceded DataReductionProxy.Quic.OnAlternativeProxyBroken. - - - - - - Removed 2019/8. - - dschinazi@chromium.org - src/net/OWNERS - - The difference between the size of alternative service mappings in cache and - preferences. This tracks zero or negative values (when the difference - between preferences size is less than or equal to memory cache size). - Positive values are tracked by - Net.AlternativeServiceServers.MorePrefsEntries. - - - - - - Removed 2019/8. - - dschinazi@chromium.org - src/net/OWNERS - - The difference between the size of alternative service mappings in - preferences and cache. This tracks positive values (when the difference - between preferences size is greater than memory cache size). Non positive - values are tracked by Net.AlternativeServiceServers.MoreOrEqualCacheEntries. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Information about the AlternativeService used for each request. - - - - - - Removed 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The count of unacknowledged ResourceMsg_DataReceived messages. This message - is sent once per chunk of data read from the network. - - - - - - Removed 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The count of unacknowledged ResourceMsg_DataReceived messages at the point - where we pause network loading. - - - - - - Data collection finished on 2015-03-31. - - dschinazi@chromium.org - src/net/OWNERS - - The time between the call of AsyncResourceHandler::OnRequestRedirected and - the FollowRedirect IPC message from ResourceHost, that is, the length of the - redirect browser-renderer-browser hop. - - - - - - Removed 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - The size of a SharedIOBuffer allocation. - - - - - Removed 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - The number of bytes copied into a SharedIOBuffer. - - - - - Removed 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of a SharedIOBuffer allocation that is actually used. - - - - - - Removed in March 2017. See https://crbug.com/700568. - - ricea@chromium.org - - Counts of error codes received while reading the body of an async - revalidation before getting a response. Only async revalidations that had a - read error are counted. - - - - - - Removed in March 2017. See https://crbug.com/700568. - - ricea@chromium.org - - Counts of error codes received while performing an async revalidation before - getting a response. Only async revalidations that had in a response error - are counted. - - - - - - Removed in March 2017. See https://crbug.com/700568. - - ricea@chromium.org - - The result of an async revalidation resulting from application of the - Cache-Control: stale-while-revalidate directive. All async revalidations are - counted. - - - - - - Removed 01/2011 in https://crrev.com/70740 - - Please list the metric's owners. Add more owner tags as needed. - The time to generate a Basic HTTP authentication token. - - - - - Removed 01/2011 in https://crrev.com/70740 - - Please list the metric's owners. Add more owner tags as needed. - The time to generate a Digest HTTP authentication token. - - - - - Removed 01/2011 in https://crrev.com/70740 - - Please list the metric's owners. Add more owner tags as needed. - - The time to generate a Negotiate (or SPNEGO) HTTP authentication token. - - - - - - Removed 01/2011 in https://crrev.com/70740 - - Please list the metric's owners. Add more owner tags as needed. - The time to generate an NTLM HTTP authentication token. - - - - - Removed and removed 06/2019. - - mmenke@chromium.org - - Number of times auto-reload has been attempted before auto-reload stopped - without succeeding, either because the stop button was pressed or because - the renderer was destroyed. - - - - - - Removed and removed 06/2019. - - mmenke@chromium.org - - Number of times auto-reload had to attempt to reload a page before - succeeding. - - - - - - Removed and removed 06/2019. - - mmenke@chromium.org - - Original error code that started an auto-reload which then succeeded on the - first attempt. - - - - - - Removed and removed 06/2019. - - mmenke@chromium.org - - Error code, if any, when auto-reload stopped without succeeding, either - because the stop button was pressed or because the renderer was destroyed. - - - - - - Removed and removed 06/2019. - - mmenke@chromium.org - - Original error code that started an auto-reload which then eventually - succeeded. - - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - Number of bytes received over this stream. - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - Number of bytes sent over this stream. - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - - How long it takes from starting the request to reading the end of the - response. - - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - - How long it takes from starting the request to reading the start of the - response. - - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - - How long it takes from starting the request to when the last byte is sent. - - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - - How long it takes from starting the request to when we can start sending - data. - - - - - - Part of a concluded experiment, 2016-08-02. - - ellyjones@chromium.org - Counts of response bytes by cache state. - - - - - Part of a concluded experiment, 2016-08-02. - - ellyjones@chromium.org - - State of the cache for a request, delta-encoding eligible or otherwise. - - - - - - Part of a concluded experiment, 2016-08-02. - - ellyjones@chromium.org - - Counts of response bytes by cache state for delta-encoding eligible - requests. - - - - - - Part of a concluded experiment, 2016-08-02. - - ellyjones@chromium.org - State of the cache for a delta-encoding eligible request. - - - - - Fallback code removed 2018-01-23. - - rsleevi@chromium.org - - Whether the certificate common name was used for matching the hostname, - instead of the subjectAlternativeName. - - Measures results for all CAs (internal and publicly-trusted). - - - - - - Fallback code removed 2018-01-23. - - rsleevi@chromium.org - - Whether the certificate common name was used for matching the hostname, - instead of the subjectAlternativeName. - - Measures results ony for internal (non-publicly-trusted) CAs. - - - - - estark@chromium.org - - The net error code returned after attempting an AIA fetch on Android. - Recorded once per intermediate that Chrome attempts to fetch via AIA on - Android. - - - - - - Removed 03/2020, since the client cert dialog capping logic has been in - place for a year now without any problems. - - dmcardle@chromium.org - davidben@chromium.org - - As of 03/2019, abusive sites can create a nuisance for Android users by - repeatedly displaying client certificate request dialogs. This histogram - records how many client certificate request dialogs were displayed to the - user. At first, we would like to get a handle on the number of request - dialogs displayed by sites in the wild. Once we have sufficient data, we - will impose some limits to prevent abuse without breaking legitimate sites. - - This metric is emitted whenever a new main frame navigation commits and - whenever a WebContents is destroyed. - - https://crbug.com/817208 - - - - - martinkr@google.com - - Whether certificate validation was disabled for a set of public keys because - the --ignore-certificate-errors-spki-list switch was set on startup. - - - - - martinkr@google.com - - Whether certificate validation was disabled because the - --ignore-certificate-errors switch was set on startup. - - - - - - Removed 06/2017 as SHA-1 was successfully disabled in 01/2017. - - rsleevi@chromium.org - - Whether or not SHA-1 was present in a resource fetched for the main frame, - and if so, what its maximum validity period was. - - - - - - Removed 06/2017 as SHA-1 was successfully disabled in 01/2017. - - rsleevi@chromium.org - - Whether or not SHA-1 was present in a subresource fetch, and if so, what its - maximum validity period was. - - - - - estark@chromium.org - - This histogram is recorded every time Chrome successfully verifies a - certificate that chains to a private root. A value of true indicates that - the certificate contains the TLS Feature Extension, and false indicates that - it doesn't. - - - - - estark@chromium.org - - This histogram is recorded every time Chrome successfully verifies a - certificate that chains to a private root and the certificate contains the - TLS Feature Extension. A value of true indicates that the connection had an - OCSP response stapled, and a value of false indicates that it did not. - - - - - - - rsleevi@chromium.org - - The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust - anchor encountered in a successfully-verified certificate chain, during an - HTTP URL request. The associated root certificate can be looked up using - https://crt.sh/?spkisha256= . - - - - - - - rsleevi@chromium.org - - The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust - anchor encountered in a successfully-verified certificate chain, during - verification time. The associated root certificate can be looked up using - https://crt.sh/?spkisha256= . - - - - - - - rsleevi@chromium.org - - This histogram is recorded every time Chrome successfully validates a - certificate, but cannot determine a public trust anchor from the verified - chain. A value of true indicates that the trust anchor list is out of date, - as the OS believes a public trust anchor is being used, but the built-in - list does not know about this trust anchor, while a value of false indicates - that a public trust anchor was not used, thus there is no evidence that the - list is out of date. This histogram is temporary until the transition to a - unified root store (in source), at which point, the OS store will no longer - be consulted for known roots. - - - - - estark@chromium.org - - Whether or not certificate verification was successful after attempting AIA - fetching on Android. Recorded once per certificate verification on Android - that resulted in an untrusted-root error without AIA fetching. - - - - - - Renamed to Net.PublicKeyPinSuccess 28 Oct 2011. - - Please list the metric's owners. Add more owner tags as needed. - - A validated certificate chain may be subject to additional - "pinning" requirements on a per-domain basis. This records the - fraction of successful matches between a certificate chain and a pin list. - - - - - - Removed in Chrome 76. - - estark@chromium.org - rsleevi@chromium.org - - Whether an observed Signed Certificate Timestamp (SCT) can be checked for - inclusion. An SCT can be checked for inclusion if the client has a valid - Signed Tree Head (STH) and the STH currently known to the client was issued - 24 hours after the timestamp in the SCT (24 hours being the typical Maximum - Merge Delay). - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.ConnectionComplianceStatus2 - - estark@chromium.org - - The compliance of each QUIC connection with the Certificate Transparency - policy, recorded once on connection setup unless CT evaluation has been - disabled for that connection or the certificate is invalid. Connections can - be compliant, or they can be non-compliant for one of several reasons (not - enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the - build was old so CT compliance wasn't checked). - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.ConnectionComplianceStatus2 - - estark@chromium.org - - The compliance of each SSL connection with the Certificate Transparency - policy, recorded once on connection setup unless CT evaluation has been - disabled for that connection or the certificate is invalid. Connections can - be compliant, or they can be non-compliant for one of several reasons (not - enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the - build was old so CT compliance wasn't checked). - - - - - - - estark@chromium.org - - The compliance of each connection with the Certificate Transparency policy, - recorded once on connection setup unless CT evaluation has been disabled for - that connection or the certificate is invalid. Connections can be compliant, - or they can be non-compliant for one of several reasons (not enough Signed - Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old - so CT compliance wasn't checked). Not recorded for certificates that chain - to locally-installed roots. - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2 - - estark@chromium.org - - The compliance of each QUIC connection with the Certificate Transparency - policy, for connections for which CT compliance is required for the - connection to succeed. (For example, CT compliance is required for certain - Certificate Authorities, or a site can opt in to having CT be required.) - Recorded once on connection setup for applicable connections unless CT - evaluation has been disabled for that connection or the certificate is - otherwise invalid. - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2 - - estark@chromium.org - - The compliance of each SSL connection with the Certificate Transparency - policy, for connections for which CT compliance is required for the - connection to succeed. (For example, CT compliance is required for certain - Certificate Authorities, or a site can opt in to having CT be required.) - Recorded once on connection setup for applicable connections unless CT - evaluation has been disabled for that connection or the certificate is - otherwise invalid. Not recorded for certificates that chain to - locally-installed roots. - - - - - - - estark@chromium.org - - The compliance of each connection with the Certificate Transparency policy, - for connections for which CT compliance is required for the connection to - succeed. (For example, CT compliance is required for certain Certificate - Authorities, or a site can opt in to having CT be required.) Recorded once - on connection setup for applicable connections unless CT evaluation has been - disabled for that connection or the certificate is otherwise invalid. Not - recorded for certificates that chain to locally-installed roots. - - - - - estark@chromium.org - - The compliance of each HTTP request with the Certificate Transparency - policy, for requests on connections for which CT compliance is required for - the connection to succeed. (For example, CT compliance is required for - certain Certificate Authorities, or a site can opt in to having CT be - required.) Recorded once on request completion for requests on applicable - connections, unless CT evaluation has been disabled for that connection or - the certificate is otherwise invalid. Not recorded when the request's - certificate chains to a locally-installed root. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - Counts of specific error codes returned by LogDnsClient at the end of an - attempt to obtain an inclusion proof for a certificate from a Certificate - Transparency log. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - Counts of specific DNS response codes returned by LogDnsClient at the end of - an attempt to obtain an inclusion proof for a certificate from a Certificate - Transparency log. The response codes (rcodes) and meanings are listed on - https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - The time taken attempting to obtain an inclusion proof from a Certificate - Transparency log over DNS. This includes the time taken to obtain the leaf - index first. Emitted at the end of an attempt. Includes attempts that fail. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - The time taken to successfully obtain an inclusion proof from a Certificate - Transparency log over DNS. This includes the time taken to obtain the leaf - index first. Emitted at the end of an attempt. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - Counts of specific error codes returned by LogDnsClient at the end of an - attempt to obtain a leaf index for a certificate from a Certificate - Transparency log. - - - - - - Removed in Chrome 76. - - robpercival@chromium.org - - Counts of specific DNS response codes returned by LogDnsClient at the end of - an attempt to obtain a leaf index for a certificate from a Certificate - Transparency log. The response codes (rcodes) and meanings are listed on - https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6. - - - - - - Replaced by Net.CertificateTransparency.DnsQueryError, which provides the - full range of net::Error codes rather than summarising them into the limited - set used by this histogram. - - robpercival@chromium.org - - The status of each attempt to obtain an inclusion proof from a Certificate - Transparency log over DNS. This can consist of more than one DNS request. - Emitted at the end of an attempt. - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.EVCompliance2.QUIC - - estark@chromium.org - - The state of compliance with Certificate Transparency presence requirements - for each EV certificate. Recorded once on QUIC connection setup when the - connection uses an EV certificate unless CT evaluation has been disabled for - that connection or the certificate is invalid. - - - - - - Removed Nov 2017, replaced with - Net.CertificateTransparency.EVCompliance2.SSL - - estark@chromium.org - - The state of compliance with Certificate Transparency presence requirements - for each EV certificate. Recorded once on SSL connection setup when the - connection uses an EV certificate unless CT evaluation has been disabled for - that connection or the certificate is invalid. - - - - - - - estark@chromium.org - - The state of compliance with Certificate Transparency presence requirements - for each EV certificate. Recorded once on QUIC connection setup when the - connection uses an EV certificate unless CT evaluation has been disabled for - that connection or the certificate is invalid. Not recorded for certificates - that chain to locally-installed roots. - - - - - - Removed in Chrome 76. - - estark@chromium.org - rsleevi@chromium.org - - The result of an inclusion check for a Certificate Transparency log entry - (composed of a TLS certificate observed together with Signed Certificate - Timestamps). Emitted once per (TLS certificate, Signed Certificate - Timestamp) pair observed and checked for inclusion (check results are - cached). - - - - - - Removed 12/2018. - - eranm@chromium.org - - Number of valid Signed Certificate Timestamps (SCTs) present for the - main-frame resource. Emitted every time a main-frame resource is fetched. - - - - - - Removed in Chrome 76. - - estark@chromium.org - rsleevi@chromium.org - - Age of Pilot's Signed Tree Head, as observed by the client, in minutes. - Measuring the age of a particular log's Signed Tree Head will allow more - informed update frequency of the Component Updater component that provides - them. Emitted once for every STH update received by the component updater. - - - - - estark@chromium.org - - The compliance of each HTTP request with the Certificate Transparency - policy, recorded once on request completion unless CT evaluation has been - disabled for that request's connection or the certificate is otherwise - invalid. A request's connection can be compliant, or it can be non-compliant - for one of several reasons (not enough Signed Certificate Timestamps [SCTs], - not diverse enough SCTs, or the build was old so CT compliance wasn't - checked). Not recorded when the request's certificate chains to a - locally-installed root. - - - - - estark@chromium.org - rsleevi@chromium.org - - Time to verify a single SCT (Signed Certificate Timestamps) when setting up - a TLS connection. Recorded each time a single SCT is verified. Includes not - just the signature verification but also other operations that are involved - in verifying an SCT, such as notifying observers and looking up the log that - issued the SCT. - - - - - estark@chromium.org - rsleevi@chromium.org - - Time to verify the SCTs (Signed Certificate Timestamps) when setting up a - TLS connection. Recorded on each connection setup where at least one SCT is - verified. - - - - - estark@chromium.org - rsleevi@chromium.org - - The origin breakdown of Signed Certificate Timestamps (SCTs). Emitted once - for every SCT when first validated, which means 0 or more times during every - SSL connection establishment. - - - - - - Removed 12/2018. - - eranm@chromium.org - - The number of Signed Certificate Timestamps (SCTs) that were available for - each SSL connection, including SCTs embedded in the certificate. This metric - measures how many SSL connections had SCTs available. Emitted during every - SSL connection establishment. - - - - - estark@chromium.org - rsleevi@chromium.org - - Breakdown of Signed Certificate Timestamps (SCTs) validation status. Emitted - once for every SCT when first validated, which means 0 or more times during - every SSL connection establishment. - - - - - mattm@chromium.org - rsleevi@chromium.org - - Whether Name normalization was used in successfully validated certificate - chains, only recorded for chains ending in privately trusted roots. Suffixed - by the CertVerifyProc implementation. - - - - - mattm@chromium.org - rsleevi@chromium.org - - When using the builtin cert verifier, records the number of iterations taken - during path building for each attempted verification. - - - - - - - mattm@chromium.org - rsleevi@chromium.org - - The actual amount of time spent verifying a certificate using the underlying - cryptographic APIs. Because parallel verifications for the same certificate - may be coalesced, histograms such as Net.SSLCertVerificationTime may be - skewed, due to later verifications taking less overall time. This records - the overall time spent verifying the first job to capture initialization - costs. - - - - - - - rsleevi@chromium.org - mattm@chromium.org - - The actual amount of time spent verifying a certificate using the underlying - cryptographic APIs. Because parallel verifications for the same certificate - may be coalesced, histograms such as Net.SSLCertVerificationTime may be - skewed, due to later verifications taking less overall time. This records - the overall time spent verifying a single request, regardless of how many - parallel requests are being served by the verification. - - - - - mattm@chromium.org - rsleevi@chromium.org - - If the CertDualVerificationTrial is enabled, each certificate verification - associated with a (non-incognito) profile which is opted-in to SBER2(Scout) - will record the outcome of comparing the primary verifier and secondary - verifier results. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times we sent N packets, but could have sent N-1 packets. - - - - - - This experiment has concluded. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time taken before we failed to resolve the Comodo test DNS - record. This is an experiment, run in conjuction with Comodo, to test the - viability of a DNS based certificate revocation mechanism. - - - - - - This experiment has concluded. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time taken to successfully resolve the Comodo test DNS record. - This is an experiment, run in conjuction with Comodo, to test the viability - of a DNS based certificate revocation mechanism. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was compressed. - Only includes requests which did not go through an explicit proxy and did - not go over SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The compressed number of bytes received per request that was compressed. - Only includes requests which did not go through an explicit proxy and did - not go over SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was not - compressed but appears to have been compressible. Only includes requests - which did not go through an explicit proxy and did not go over SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was compressed. - Only includes requests sent through a proxy without SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The compressed number of bytes received per request that was compressed. - Only includes requests sent through a proxy without SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was not - compressed but appears to have been compressible. Only includes requests - sent through a proxy without SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was compressed. - Only includes requests sent over SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The compressed number of bytes received per request that was compressed. - Only includes requests sent over SSL. - - - - - - Removed as of 02/2015 - - Please list the metric's owners. Add more owner tags as needed. - - The uncompressed number of bytes received per request that was not - compressed but appears to have been compressible. Only includes requests - sent over SSL. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Application protocol used for main frame resources. Logged by the renderer - only for request that accessed the network and have received response - headers. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Application protocol used for subresources (resources other than main - frame). Logged by the renderer only for request that accessed the network - and have received response headers. - - - - - - The count was inaccurate (it counted transactions rather than connections) - - Please list the metric's owners. Add more owner tags as needed. - - Each bucket is the number of connections of a particular type that the user - has had during the session. - - - - - - Renamed to match HadConnectionType. - - Please list the metric's owners. Add more owner tags as needed. - - Each bucket is the number of successful connections of a particular type - that the user has had during the session. - - - - - - Removed May 2016. - - davidben@chromium.org - - Each bucket is the number of successful connections of a particular type - that the user has had during the session. - - - - - - No longer collected. - - Please list the metric's owners. Add more owner tags as needed. - - Each bucket is the number of failed connections of a particular type that - the user has had during the session. - - - - - - Replaced with Net.ConnectionUsedSSLDeprecatedCipherFallback2 in Chrome 44. - - davidben@chromium.org - - True if an HTTPS connection was made using the deprecated cipher suite - fallback. - - - - - - Removed May 2017. - - davidben@chromium.org - - For each successful HTTPS request, whether it used the deprecated cipher - suite fallback. - - - - - - Replaced by Net.ConnectionUsedSSLVersionFallback in Chrome 21. - - Please list the metric's owners. Add more owner tags as needed. - - True if the HTTP request was to a server which requires SSLv3 fallback - - - - - - Replaced with Net.ConnectionUsedSSLVersionFallback2 in Chrome 44. - - agl@chromium.org - - Nonzero if the HTTP request was to a server which requires SSL version - fallback. The value indicates the SSL version the request fell back on. - - - - - - Removed June 2016. - - davidben@chromium.org - - For each successful HTTPS request, whether it used the SSL version fallback. - The value indicates the SSL version the request fell back on - - - - - - Obsoleted in favor of Net.ContentDecodingFailed2.FilterType below. - - - For each CONTENT_DECODING_FAILED, record the filter that failed. - - - - - mef@chromium.org - pauljensen@chromium.org - - For each CONTENT_DECODING_FAILED, record the filter that failed. - - - - - - Obsoleted in favor of Net.ContentDecodingFailed2 above. - - mef@chromium.org - pauljensen@chromium.org - - For each CONTENT_DECODING_FAILED, record the filter that failed. - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - Whether or not updates to the backing store succeeded or failed, recorded - every update. - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - Intervals between access time updates for each cookie. - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - Number of cookies in the store (recorded every 10 minutes of active browsing - time) - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - For each cookie removed from the store, the reason it was removed. - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - For each domain, number of cookies in that domain (recorded every 10 minutes - of active browsing time). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - For every top level domain, number of subdomains in that top level domain - (recorded every 10 minutes of active browsing time). - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - For every top level domain, number of cookies in that domain (recorded every - 10 minutes of active browsing time). - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - For each evicted (not expired) cookie, the amount of time since it was last - used - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - Number of minutes until cookie expires when set. - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time (ms) to get cookies for each URL request. - - - - - - Initial typo; only here to get results from builds before r59117. See - "Cookie." group. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time (ms) to load the persistent cookie store at browser - start. - - - - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of CORS error types on the original network requests. This - reports whenever CORS checks detect an error on the original network - requests. - - - - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of CORS access check results. This reports whenever CORS - AccessCheck runs. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of active mojom::URLLoader instance counts including - network::URLLoader and network::CorsURLLoader in the network service. This - reports every 5 minutes. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - Each CorsURLLoader reports its completion status on finishing each request - to analyze how often requests are blocked by CORS checks. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the number of cache entries in the CORS preflight cache. - This counts the cache entries every 5 minutes. - - - - - - Removed 05/2019, related to cache organization changes that does not store - entries per origin any more. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the number of cache entries for each origin in the CORS - preflight cache. This counts the cache entries for each origin every 5 - minutes. - - - - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the key size in the CORS preflight cache. This counts - each key size when a new entry is added to the cache. - - - - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the CORS preflight cache query results. This counts on - each cache query. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the total number of cache entries that is sum of all - CORS preflight cache entries in the network service. This counts the cache - entries every 5 minutes. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of the total memory presure in bytes for all CORS preflight - cache in the network service. This counts the cache entries every 5 minutes. - - - - - - Removed 06/2019. - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of estimated memory pressure caused by each cache entry's - content in the CORS preflight cache. This counts each entry size when a new - entry is added to the cache. - - - - - toyoshim@chromium.org - yhirano@chromium.org - - The distribution of CORS error types on preflight requests. This reports - whenever CORS checks detect an error on the original network requests. - - - - - - Removed 2019/08. - - dschinazi@chromium.org - src/net/OWNERS - - The total number of servers (HostPortPairs) to which alternative protocol - was used. This counts the number of servers persisted to prefs file. - - - - - - Removed 2019/08. - - dschinazi@chromium.org - src/net/OWNERS - - The total number of servers (HostPortPairs in memory) to which alternative - protocol was used. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The number of broken alternative services loaded from the prefs file on - startup. Alternative services allow an origin server to specify additional - means of interacting with it on the network. A broken alternative service is - one whose most recent connection attempt failed and whose retry timeout - period has not yet expired. Recorded when broken alternative services are - loaded from the prefs file on startup. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The total number of servers (HostPortPairs) that support HTTP pipelining. - This counts the number of servers persisted to prefs file. - - - - - zhongyi@chromium.org - dschinazi@chromium.org - src/net/quic/OWNERS - - This counts the number of server configs persisted in prefs file. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The number of recently broken alternative services loaded from the prefs - file on startup. Alternative services allow an origin server to specify - additional means of interacting with it on the network. A recently broken - alternative service is one whose most recent connection attempt failed. - Recorded when broken alternative services are loaded from the prefs file on - startup. - - - - - - Removed on 2016-08. - - dschinazi@chromium.org - src/net/OWNERS - - The total number of SPDY server names persisted to prefs file. - - - - - - Removed on 2016-10-11. - - dschinazi@chromium.org - src/net/OWNERS - - The total number of SPDY Settings properties persisted to prefs file. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to block to fetch one or - more revocation lists. This measures the amount of time that failures to get - CRL information take. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to block to fetch one or - more revocation lists. This records the fraction of successful requests. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to block to fetch one or - more revocation lists. This measures the amount of time that each fetch - takes. - - - - - - Removed 2018-06-29 in crrev.com/571588. - - dschinazi@chromium.org - src/net/OWNERS - - Measures time spent to deserialize and populate the - net::CachingCertVerifier's cache. - - - - - - Removed 2018-06-29 in crrev.com/571588. - - dschinazi@chromium.org - src/net/OWNERS - - Measures time spent to serialize the net::CachingCertVerifier's cache. - - - - - - Removed 2019-04-23. - - mgersh@chromium.org - - Measures time spent creating the Cronet PrefService, including loading the - prefs from disk synchronously. - - - - - - Removed; refer to Experimental.Bytes.Network - - tbansal@chromium.org - - The total content size in KB of all HTTP/HTTPS response bodies in the - previous calendar day. The metric is reported when the first response in the - current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all HTTP/HTTPS response bodies in the - previous calendar day while the data reduction proxy setting was enabled. - The metric is reported when the first response in the current day is - received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all HTTPS response bodies in the previous - calendar day while the data reduction proxy setting was enabled. The metric - is reported when the first response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all long-bypassed HTTP response bodies in - the previous calendar day while the data reduction proxy setting was - enabled. The metric is reported when the first response in the current day - is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all short-bypassed HTTP response bodies in - the previous calendar day while the data reduction proxy setting was - enabled. The metric is reported when the first response in the current day - is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - bolian@chromium.org - - The total content size in KB of all HTTP response bodies for requests that - were not served by the enabled data reduction proxy for unknown reasons in - the previous calendar day while the data reduction proxy setting was - enabled. The metric is reported when the first response in the current day - is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all HTTP response bodies for requests that - were not served by the enabled data reduction proxy for unknown reasons in - the previous calendar day while the data reduction proxy setting was - enabled. The metric is reported when the first response in the current day - is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total content size in KB of all HTTP/HTTPS response bodies in the - previous calendar day via the data reduction proxy. The metric is reported - when the first response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total HTTP/HTTPS response body size while the data - reduction proxy is enabled to total HTTP/HTTPS response body size in the - previous calendar day. The metric is reported when the first response in the - current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total HTTPS response body size while the data reduction - proxy is enabled to total HTTP/HTTPS response body size in the previous - calendar day. The metric is reported when the first response in the current - day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total long-bypassed response body size while the data - reduction proxy is enabled to total HTTP/HTTPS response body size in the - previous calendar day. The metric is reported when the first response in the - current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total short-bypassed response body size while the data - reduction proxy is enabled to total HTTP/HTTPS response body size in the - previous calendar day. The metric is reported when the first response in the - current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total body size of responses that were not served by the - data reduction proxy for unknown reason while the data reduction proxy is - enabled to total HTTP/HTTPS response body size in the previous calendar day. - The metric is reported when the first response in the current day is - received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of total HTTP/HTTPS response body size via the data reduction - proxy to total HTTP/HTTPS response body size in the previous calendar day. - The metric is reported when the first response in the current day is - received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of data saving in the previous calendar day. A negative - saving will be shown as zero. The metric is reported when the first response - in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of data saving in the previous calendar day while the data - reduction proxy was enabled. A negative saving will be shown as zero. This - only counts responses while the data reduction proxy is enabled. The metric - is reported when the first response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of data saving in the previous calendar day while the data - reduction proxy was enabled. A negative saving will be shown as zero. This - only counts responses while the data reduction proxy is enabled. The metric - is reported when the first response in the current day is received. If no - video bytes were received while the data reduction proxy was enabled, the - metric will not be reported. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of data saving in the previous calendar day via the data - reduction proxy. A negative saving will be shown as zero. This only counts - responses via the data reduction proxy. The metric is reported when the - first response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The percentage of data saving in the previous calendar day via the data - reduction proxy. A negative saving will be shown as zero. This only counts - responses via the data reduction proxy. The metric is reported when the - first response in the current day is received. If no video bytes were - received via the data reduction proxy, the metric will not be reported. - - - - - - Removed; refer to Experimental.Bytes.Network - - bolian@chromium.org - - Total size in KB of all response bodies in the previous calendar day that - were received through the data reduction proxy. - - - - - - Removed; refer to Experimental.Bytes.Network - - bolian@chromium.org - - Total size in KB of all response bodies in the previous calendar day that - were received when the data reduction proxy was enabled. - - - - - - Removed; refer to Experimental.Bytes.Network - - bolian@chromium.org - - The percentage of data saving in the previous calendar day. A negative - saving will be shown as zero. - - - - - - Removed; refer to Experimental.Bytes.Network - - bolian@chromium.org - - The percentage of data saving in the previous calendar day when the data - reduction proxy was enabled for at least some responses during the day. A - negative saving will be shown as zero. - - - - - - Removed- see Net.DailyOriginalContentLength. - - bolian@chromium.org - - Total size in KB specified in the X-Original-Content-Length headers of all - responses in the previous calendar day. If the header is not present in a - response, the size of the response body is used. - - - - - - Removed- see Net.DailyContentLength. - - bolian@chromium.org - - Total size in KB of all response bodies in the previous calendar day. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total size in KB specified in the X-Original-Content-Length headers of - all HTTP/HTTPS response bodies in the previous calendar day. If the header - is not present in a response, the size of the response body is used. The - metric is reported when the first response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total size in KB specified in the X-Original-Content-Length headers of - all HTTP/HTTPS response bodies in the previous calendar day while the data - reduction proxy is enabled. If the header is not present in a response, the - size of the response body is used. The metric is reported when the first - response in the current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - tbansal@chromium.org - - The total size in KB specified in the X-Original-Content-Length headers of - all HTTP/HTTPS response bodies in the previous calendar day via the data - reduction proxy. If the header is not present in a response, the size of the - response body is used. The metric is reported when the first response in the - current day is received. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - bolian@chromium.org - - The percentage of Net.DailyHttpContentLengthViaDataReductionProxy in - Net.DailyHttpReceivedContentLength. - - - - - - Removed; refer to Experimental.Bytes.Network - - bengr@chromium.org - bolian@chromium.org - - The percentage of Net.DailyHttpContentLengthWithDataReductionProxyEnabled in - Net.DailyHttpReceivedContentLength. - - - - - - Removed in Chrome 57. - - kundaji@chromium.org - bengr@chromium.org - - The percentage of data savings in past - |DataReductionProxy::kNumDaysInHistorySummary| days. This number is - displayed to users as their data savings. - - - - - - Removed in Chrome 57. - - kundaji@chromium.org - bengr@chromium.org - - The total data saved in KB in past - |DataReductionProxy::kNumDaysInHistorySummary| days. This number is used to - compute the data savings displayed to the user. - - - - - yhirano@chromium.org - kinuko@chromium.org - src/net/OWNERS - - The maximum number of data pipes used for network::URLLoader in the network - service in every 20 minutes. - - - - - yhirano@chromium.org - kinuko@chromium.org - src/net/OWNERS - - The minimum number of data pipes used for network::URLLoader in the network - service in every 20 minutes. - - - - - yhirano@chromium.org - kinuko@chromium.org - src/net/OWNERS - - The maximum number of data pipes used for network::WebSocket in the network - service in every 20 minutes. - - - - - yhirano@chromium.org - kinuko@chromium.org - src/net/OWNERS - - The minimum number of data pipes used for network::WebSocket in the network - service in every 20 minutes. - - - - - - Removed in Chrome 64. - - yhirano@chromium.org - - Duration of time that a request associated with DetachableResourceHandler - takes. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Measures time from initiating a fetch of a PAC file from DHCP WPAD to - cancellation of the fetch. For a given fetch, only one of the cancellation - or completion histograms will be added to. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Measures time from initiating a fetch of a PAC file from DHCP WPAD to - completion of the fetch. For a given fetch, only one of the cancellation or - completion histograms will be added to. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Tracks the net error codes received when the DHCP WPAD fetch fails to - retrieve a PAC file (including PAC_NOT_IN_DHCP, which is not really an error - but an indication that a PAC URL was not configured in DHCP). - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Tracks the frequency of each of the different known error codes of calling - the GetAdaptersAddresses Win32 API. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Measures the time taken to call the GetAdaptersAddresses Win32 API, to - validate our understanding that it should complete quickly enough to call - synchronously from the network thread. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Total number of adapters enabled for DHCP as seen when the wait timer in the - DHCP WPAD code hits. This timer fires after a timeout from when we get some - information from the first adapter to finish. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Number of adapters enabled for DHCP that we have not completed retrieving - information for, as seen when the wait timer in the DHCP WPAD code hits. - This timer fires after a timeout from when we get some information from the - first adapter to finish. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - Counts the number of errors from the DhcpRequestParams API that we do not - have specific handling for, so that we can see if there is an abnormally - high rate. - - - - - - Removed in Chrome 65. - - erikchen@chromium.org - - The sum of the size of all files in the HTTP cache directory. - - This is recorded on startup, and then every 24 hours afterwards. However, it - is only recorded for 0.1% of profiles, to reduce overhead for most users. - This is meant to be a temporary metric to help debug a potential HTTP cache - leak. We do not yet know which milestone we expect it to be removed in. - - - - - - Removed 8/2019. - - pauljensen@chromium.org - - For devices using Android private DNS, are their DNS servers known to - support DNS-over-HTTPS. - - - - - - Removed 8/2019. - - pauljensen@chromium.org - - For devices not using Android private DNS, are their DNS servers known to - support DNS-over-HTTPS, thus potential candidates for automatic upgrading - from regular DNS to DNS-over-HTTPS. - - - - - - Removed 8/2019. - - pauljensen@chromium.org - - For devices using Android private DNS, was their DNS-over-TLS server - specified explicitly in their Android settings. When false, they were - automatically upgraded from the standard DNS protocol to DNS-over-TLS via - auto-detection. - - - - - ericorth@chromium.org - doh-core@google.com - - Records details of the secure DNS mode used to configure the host resolver - at construction of the network service. - - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of specific error codes returned by DnsTask. Only counts failures - that took less than 10ms, which are probably local failures. - - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of specific error codes returned by DnsTask. Only counts failures - that took at least 10ms, which are probably remote failures or connectivity - problems. - - - - - pauljensen@chromium.org - mef@chromium.org - - Counts of specific error codes returned by DnsTask if a subsequent ProcTask - succeeded. - - - - - - Removed 9/2019. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by DnsTask in resolutions that failed. Excludes time - spent in the subsequent fallback. - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of time taken by DnsTask (the grouping of all individual DNS - queries for a single instance of resolving a name) in resolutions that - succeeded. - - - - - ericorth@chromium.org - src/net/OWNERS - - Enumeration of the logic path used (e.g. different protocols) for each - started DnsAttempt (the representation of an individual network request to a - DNS server). - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - Total time elapsed from the beginning of ESNI-type DnsTasks to the - completion of ESNI-type DnsTransactions executed during these tasks. - Recorded only for DnsTasks specifically with DnsQueryType::ESNI, i.e. *not* - for those made during the normal built-in resolver flow. - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - For an UNSPECIFIED-type DnsTask, the total end-to-end elapsed time from the - beginning of the task to the completion of its final ESNI-type - DnsTransaction, minus the total end-to-end elapsed time to the completion of - the task's final non-ESNI-type transaction. Recorded only when the built-in - resolver is configured to make ESNI queries alongside A and AAAA queries, - and only when the task's ESNI transaction finishes after its final non-ESNI - transaction. - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - Total time elapsed from the beginning of a DnsTask to the completion of an - ESNI transaction. Recorded only when the built-in resolver is configured to - make ESNI queries alongside A and AAAA queries. - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - Total time elapsed from the beginning of an UNSPECIFIED-type DnsTask to the - completion of its final non-ESNI-type DnsTransaction. Recorded only when the - built-in resolver is configured to make ESNI queries alongside A and AAAA - queries. - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - For an UNSPECIFIED-type DnsTask, the total end-to-end elapsed time from the - beginning of the task to the completion of its final non-ESNI-type - DnsTransaction, minus the total end-to-end elapsed time to the completion of - the task's final ESNI-type transaction. Recorded only when the built-in - resolver is configured to make ESNI queries alongside A and AAAA queries, - and only when the task's final non-ESNI transaction finishes no earlier than - its ESNI transaction. - - - - - - As of 02/2020, no longer necessary because the ESNI record fetching - implementation has been superseded by the new HTTPSSVC DNS record type. - - davidvc@chromium.org - ericorth@chromium.org - - Records successful completions and DnsTask-level timeout cancellations of - ESNI (TLS 1.3 Encrypted Server Name Indication, Draft 4)-type DNS - transactions. Recorded only when the built-in resolver is configured to make - ESNI queries alongside A and AAAA queries. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by an insecure DnsTransaction to fail. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by an insecure DnsTransaction to succeed. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Counts of specific error codes returned by secure DnsTransactions to a DoH - server that is unavailable or has unknown availability. These transactions - may be probe queries or queries issued in the secure DNS mode. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTransaction to a DoH server that is - unavailable or has unknown availability to fail. These transactions may be - probe queries or queries issued in the secure DNS mode. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTransaction to a DoH server that is - unavailable or has unknown availability to succeed. These transactions may - be probe queries or queries issued in the secure DNS mode. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Counts of specific error codes returned by secure DnsTransactions to an - available DoH server. A DoH server is available if a probe has been - successfully completed and fewer than a threshold amount of failures have - occurred. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTransaction to an available DoH server - to fail. A DoH server is available if a probe has been successfully - completed and fewer than a threshold amount of failures have occurred. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTransaction to an available DoH server - to succeed. A DoH server is available if a probe has been successfully - completed and fewer than a threshold amount of failures have occurred. - - - - - ericorth@chromium.org - src/net/OWNERS - - Ratio (scaled up by 10) between the time taken by a successful secure - DnsTransaction attempt and the current dynamically-determined base timeout - in use for the DoH server that accomplished the resolve. Only recorded when - the DoH server is already known to be "available" (successful - probe request and failure thresholds not exceeded). - - - - - ericorth@chromium.org - src/net/OWNERS - - Enumerated status of whether a DNS over UDP response ID matched the expected - query ID and whether a mismatched ID is recognized as a recently-queried - one. Logged for every DNS over UDP response received with a parsable ID. - - - - - ericorth@chromium.org - src/net/OWNERS - - Time between receiving a mismatched DNS ID (when a DNS response contains an - ID that does not match the ID sent in the query) via UDP and the oldest - known use of the same ID in a query. Logged for every DNS over UDP response - receivied with a mismatched DNS ID. - - - - - ericorth@chromium.org - src/net/OWNERS - - Enumerated status of the reason why the built-in DNS resolver has detected a - "low entropy" situation for DNS over UDP and has switched to DNS - over TCP. - - - - - ericorth@chromium.org - src/net/OWNERS - - Number of recent uses found of a local port number used for DNS over UDP. - Logged for every DNS over UDP query sent. - - - - - ericorth@chromium.org - src/net/OWNERS - - Time between use of a local port number for DNS over UDP and the most recent - DNS over UDP use of the same port. Logged for every DNS over UDP query sent - with at least 1 recognized previous use of the local port. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Records which RCODE the DNS server specified when it responded to our - INTEGRITY query. If the query timed out before getting a response, - "TimedOut" is recorded instead of an RCODE value. Histograms are - emitted at the completion of a DnsTask's final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Indicates whether the result of an INTEGRITY query was intact (true) or - mangled (false). Only recorded when DnsRcode indicates NoError. Histograms - are emitted at the completion of a DnsTask's final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Records a sample of one when we receive an INTEGRITY record and an error - RCODE at the same time. Histograms are emitted at the completion of a - DnsTask's final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Counts the number of records received when we get any INTEGRITY record - (Intact or Mangled) for a non-experimental domain. Any INTEGRITY record in - the response would be a surprise! Histograms are emitted at the completion - of a DnsTask's final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Records how many ms the DNS server took to respond to an INTEGRITY query. - Histograms are emitted at the completion of a DnsTask's final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Records how many ms the DNS server took to respond to any query other than - an INTEGRITY query. Histograms are emitted at the completion of a DnsTask's - final transaction. - - - - - - - dmcardle@chromium.org - ericorth@chromium.org - - Records a ratio indicating the relative INTEGRITY resolve time compared to - the slower A or AAAA resolve time, where A/AAAA/INTEGRITY belong to the same - DnsTask. Multiply this value by 10 to obtain a percentage P. The INTEGRITY - query completed in roughly P% of the slower A/AAAA resolve time. Values - smaller than 10 indicate that INTEGRITY query was faster than A/AAAA. Values - larger than 10 indicate that the INTEGRITY query was slower than A/AAAA. - Histograms are emitted at the completion of a DnsTask's final transaction. - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of time taken by an insecure DnsTask in resolutions that failed. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Time elapsed between the time the HostResolverImpl::Job was created and the - time the Job was started. - - - - - dmcardle@chromium.org - ericorth@chromium.org - - The duration of time DnsTransactions spend waiting to be started by a - DnsTask, aggregated by HostResolverManager::Job. This metric is only - recorded when the Job failed. - - - - - dmcardle@chromium.org - ericorth@chromium.org - - The duration of time a DnsTransaction spends waiting to be started by a - DnsTask. The dominant factor is likely the time spent waiting for other - DnsTransactions to complete, i.e. waiting for DnsTask::StartNextTransaction - to be invoked by the dispatcher. If there were no limit on the number of - concurrent DNS queries, we would expect this metric to be near zero. - - - - - dmcardle@chromium.org - ericorth@chromium.org - - The duration of time DnsTransactions spend waiting to be started by a - DnsTask, aggregated by HostResolverManager::Job. This metric is only - recorded when the Job succeeded. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Time elapsed between the last time the priority of a HostResolverImpl::Job - changed (when a Request was attached or detached) and the time the Job was - started. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a probe attempt to fail. The time is measured - since the probe sequence was initiated due to a DNS config change. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a probe attempt to succeed. The time is measured - since the probe sequence was initiated due to a DNS config change. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a probe attempt to fail. The time is measured - since the probe sequence was initiated due to a network change. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a probe attempt to succeed. The time is measured - since the probe sequence was initiated due to a network change. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by ProcTask in resolutions that failed. - - - - - - Removed 11/2018. - - pauljensen@chromium.org - mef@chromium.org - - Duration of time taken by ProcTask in resolutions that succeeded. - - - - - - Removed 8/2019. - - dmcardle@chromium.org - davidben@chromium.org - - Length of domain name parsed by DnsRecordParser::ReadName(). - - - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of HostResolver requests from Start() until completion. Includes - requests resolved synchronously using fast local sources, e.g. from cache, - recorded as 0. Excludes speculative requests. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of HostResolver requests from Start() until completion. Excludes - speculative requests and requests resolved using fast local sources, e.g. - from cache. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - Whether a HostResolverManager::Job (the basic internal unit of work for - non-local host resolutions, potentially merging redundant requests from - Chrome) succeeded or failed, and whether it was speculative. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - For DNS resolutions that failed after less than 10 ms, which are probably - local failures, what error code the jobs failed with. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - For DNS resolutions that failed after at least 10 ms, which are probably - remote failures or connectivity problems, what error code the jobs failed - with. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of time taken by HostResolverManager::Job (the basic internal unit - of work for non-local host resolutions, potentially merging redundant - requests from Chrome) in resolutions that failed. This is the time to - resolve a hostname from start to finish. Excludes jobs where all requests - are speculative. - - - - - - - ericorth@chromium.org - src/net/OWNERS - - Duration of time taken by HostResolverManager::Job (the basic internal unit - of work for non-local host resolutions, potentially merging redundant - requests from Chrome) in resolutions that succeeded. This is the time to - resolve a hostname from start to finish. Excludes jobs where all requests - are speculative. - - - - - - Removed July 2018. - - mgersh@chromium.org - - When DnsUDPAttempt gets a malformed response, it returns an error but - continues running. This histogram records all attempt outcomes that are - returned to the transaction once a malformed response has been received, - including the original malformed response. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by HostResolverManager::Job (the basic internal unit - of work for non-local host resolutions, potentially merging redundant - requests from Chrome) in resolutions for in AUTOMATIC secure DNS mode. - Excludes jobs where all requests are speculative. - - - - - - Replaced 2020-06 by Net.DNS.SecureDnsMode.Automatic.ResolveTime - - dalyk@google.com - doh-core@google.com - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted for requests issued in AUTOMATIC mode. Excludes cancled, - evicted, and aborted requests. Includes cache hits (recorded as 0). Excludes - speculative requests. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by HostResolverManager::Job (the basic internal unit - of work for non-local host resolutions, potentially merging redundant - requests from Chrome) in resolutions for in OFF secure DNS mode. Excludes - jobs where all requests are speculative. - - - - - - Replaced 2020-06 by Net.DNS.SecureDnsMode.Off.ResolveTime - - dalyk@google.com - doh-core@google.com - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted for requests issued in OFF mode. Excludes cancled, evicted, - and aborted requests. Includes cache hits (recorded as 0). Excludes - speculative requests. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by HostResolverManager::Job (the basic internal unit - of work for non-local host resolutions, potentially merging redundant - requests from Chrome) in resolutions for in SECURE secure DNS mode. Excludes - jobs where all requests are speculative. - - - - - - Replaced 2020-06 by Net.DNS.SecureDnsMode.Secure.ResolveTime - - dalyk@google.com - doh-core@google.com - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted for requests issued in SECURE mode. Excludes cancled, - evicted, and aborted requests. Includes cache hits (recorded as 0). Excludes - speculative requests. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTask in resolutions that failed that - were issued in AUTOMATIC mode. Excludes time spent in the subsequent - fallback. - - - - - ericorth@chromium.org - doh-core@google.com - - Duration of time taken by a secure DnsTask in resolutions that failed that - were issued in SECURE mode. - - - - - ericorth@chromium.org - doh-core@google.com - - Counts of specific error codes returned by insecure DnsTasks after a secure - DnsTask failed. - - - - - ericorth@chromium.org - doh-core@google.com - - Counts of specific error codes returned by a ProcTask after a secure DnsTask - failed. Only records instances where there was no intermediary insecure - DnsTask. - - - - - - Replaced 2020-06 by Net.DNS.Request.TotalTime - - pauljensen@chromium.org - mef@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Excludes speculative requests. - - - - - - Replaced 2020-06 by Net.DNS.Request.TotalTimeAsync - - pauljensen@chromium.org - mef@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests and - requests that returned synchronously (such as cache hits). Excludes - speculative requests. - - - - - - Removed 9/2019. - - - - pauljensen@chromium.org - - Duration of time since a HostResolverImpl::Resolve request to the time a - result is posted. Excludes canceled, evicted, and aborted requests. Includes - cache hits (recorded as 0). Excludes speculative requests. - - - - - - - ericorth@chromium.org - doh-core@google.com - - Provider in a user-initiated dropdown change event that occured when this - provider was one of the dropown options. - - - - - ericorth@chromium.org - doh-core@google.com - - Records the outcome of a DoH probe attempt on the first valid entry in the - custom text field. - - - - - ericorth@chromium.org - doh-core@google.com - - Records the outcome of a formatting validation attempt on the custom text - field. - - - - - ericorth@chromium.org - doh-core@google.com - - True if upgrade to DoH from a DoT hostname was attempted and succeeded. - False if it was attempted and failed. - - - - - ericorth@chromium.org - doh-core@google.com - - True if there was at least one public nameserver during an attempt to - upgrade to DoH from insecure DNS. False if there were no public nameservers - during an attempt to upgrade to DoH from insecure DNS. - - - - - ericorth@chromium.org - doh-core@google.com - - True if upgrade to DoH was not attempted because the DoH config was already - specified. False if upgrade to DoH was not attempted for some other reason. - - - - - ericorth@chromium.org - doh-core@google.com - - True if upgrade to DoH was not attempted because of unhandled options in the - system config. False if upgrade to DoH was not attempted for some other - reason. Emitted each time the DnsConfig is updated. - - - - - ericorth@chromium.org - doh-core@google.com - - True if upgrade to DoH from insecure DNS was attempted and succeeded. False - if it was attempted and failed. - - - - - - Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 - - Please list the metric's owners. Add more owner tags as needed. - - - - - Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 - - Please list the metric's owners. Add more owner tags as needed. - - - - mmenke@chromium.org - - The time measured before starting DNS lookup until after the connection is - complete. - - - - - - Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 - - Please list the metric's owners. Add more owner tags as needed. - - - - - Removed 07/2017, not necessary to determine deprecation for invalid DNS - names. - - palmer@chromium.org - - True if |net::IsCanonicalizedHostCompliant| returns true. Used to see if - IsCanonicalizedHostCompliant() runs afoul of real websites. This histogram - is recorded when converting dotted DNS names into DNS query form, in - preparation for issuing a DNS request. This histogram is only recorded if - Net.ValidDNSName is true. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The number of HTTP request responses with MS Office Docs MIME types. The - responses are classified based on their method type and cacheability (POST, - cacheable GET and non-cacheable GET). The histogram is used in Double GET - Experiment, where successful non-cacheable GET requests are intercepted - after initial response and repeated in order to determine how much reissuing - non-cacheable GET requests influences their error rate. The histogram tracks - only initial requests (not the repeated ones). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The response codes encountered for GET request repeated in Double GET - Experiment. In the experiment successful non-cacheable GET requests are - intercepted after initial response and repeated. The goal of the experiment - is to measure how much reissuing non-cacheable GET requests influences their - error rate. - - - - - - Removed as of 03/2015. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - Kbps on download streams exceeding 25KB. Measures from the beginning of the - first byte received until the end of flowing data. - - - - - - Removed in favor of Net.ErrAborted.CountPerUpload2 which has a higher upper - bound - - csharrison@chromium.org - - The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time - histograms are being uploaded. - - - - - csharrison@chromium.org - - The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time - histograms are being uploaded. - - - - - csharrison@chromium.org - - The bucket proportion of the ABORTED bucket in Net.ErrorCodesForMainFrame3 - at the time histograms are being uploaded. - - - - - - Removed from Chromium as of 2018/7/2. - - csharrison@chromium.org - - The TotalReceivedBytes() at the time the request finishes with ERR_ABORTED. - - - - - - Removed from Chromium as of 2018/7/2. - - csharrison@chromium.org - - The TotalSentBytes() at the time the request finishes with ERR_ABORTED. - - - - - - Removed as of 2012/5/16, replaced by Net.ErrorCodesForHTTPSGoogleMainFrame2, - which measures the same data but includes ERR_ABORT and OK. - - Please list the metric's owners. Add more owner tags as needed. - - Errors resulting from loading pages from https://www.google.com. Note that - this only counts the errors in "main frames", so it is a measure - of the error pages that users actually see (it does not for example count - the error codes for subresoures on a page). This is a temporary histogram, - added in order to debug query loss from the SSL Search launch. - - - - - - Removed as of 7/2018, replaced by Net.ErrorCodesForHTTPSGoogleMainFrame3. - - mmenke@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" for - https://www.google.com. Subresources or main frame navigations to other - origins are not included. - - - - - - - mmenke@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" for - https://www.google.com (it does not for example count the error codes for - subresoures on a page). It excludes main frame navigations that are - converted to downloads (unless they fail / are aborted before it's known - that they would be a download), and requests handled externally (like mailto - links). - - - - - - Removed as of 7/2018, replaced by Net.ErrorCodesForImages2, which is - recorded in a net-service friendly way. - - skonig@chromium.org - hbengali@chromium.org - - Net error codes that requests for images end with, including net::OK and - net:ERR_ABORTED. - - - - - skonig@chromium.org - hbengali@chromium.org - - Net error codes that requests for images end with, including net::OK and - net:ERR_ABORTED. - - - - - - Removed as of 2011/5/24, replaced by Net.ErrorCodesForMainFrame2, which - measures the same data but uses a different bucket structure (adds guard - buckets). - - Please list the metric's owners. Add more owner tags as needed. - - Positive net error code that a page failed with. Note that this only counts - the errors in "main frames", so it is a measure of the error pages - that users actually see (it does not for example count the error codes for - subresoures on a page). - - - - - - Removed as of 2012/5/16, replaced by Net.ErrorCodesForMainFrame3, which - measures the same data but includes ERR_ABORTED and OK. - - Please list the metric's owners. Add more owner tags as needed. - - Positive net error code that a page failed with. Note that this only counts - the errors in "main frames", so it is a measure of the error pages - that users actually see (it does not for example count the error codes for - subresoures on a page). - - - - - - Removed as of 7/2018, replaced by Net.ErrorCodesForMainFrame4, which is - recorded in a net-service friendly way. - - mmenke@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" (it - does not for example count the error codes for subresoures on a page). - - - - - - - mmenke@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" (it - does not for example count the error codes for subresoures on a page). It - excludes main frame navigations that are converted to downloads (unless they - fail / are aborted before it's known that they would be a download), and - requests handled externally (like mailto links). - - - - - - Removed as of 2012/5/16, replaced by Net.ErrorCodesForSubresources2, which - measures the same data but includes ERR_ABORT and OK. - - Please list the metric's owners. Add more owner tags as needed. - - Positive net error code that a page failed with. Note that this only counts - the errors in "subresources". - - - - - - Removed as of 7/2018, replaced by Net.ErrorCodesForSubresources3, which is - recorded in a net-service friendly way. - - mmenke@chromium.org - - Net error codes that requests for "subresources" end with, - including net::OK and net::ERR_ABORTED. - - - - - - - mmenke@chromium.org - - Net error codes that requests for "subresources" end with, - including net::OK and net::ERR_ABORTED. - - - - - - Removed as of 7/2018, replaced by - Net.ErrorCodesForTLS13ExperimentMainFrame2, which is recorded in a - net-service friendly way. - - svaldez@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" for - endpoints used in the initial TLS 1.3 deployment. Subresources or main frame - navigations to other origins are not included. - - - - - svaldez@chromium.org - - Positive net error codes that requests for pages end with, including net::OK - and net::ERR_ABORTED. This only counts loads in "main frames" for - endpoints used in the initial TLS 1.3 deployment. Subresources or main frame - navigations to other origins are not included. - - - - - - Removed as of 2015/8/21 - - mmenke@chromium.org - - Temporary histogram to investigate http://crbug.com/500556. Records which - button on the network error page was pushed when either the URL Blink - reports for the page is not the internal error page URL or the - NetErrorHelper core has no error information for the current page (or both). - - - - - - Removed as of 2015/8/21 - - mmenke@chromium.org - - Temporary histogram to investigate http://crbug.com/500556. Records whether, - when the handler for a button press on the network error page runs, which of - the following are or are not true: The URL Blink reports for the page is not - the internal error page URL or the NetErrorHelper core has no error - information for the current page. - - - - - edwardjung@chromium.org - src/net/OWNERS - - Counts of various events that can occur on the network error page. Note that - this histogram enum buckets are not mutually exclusive and so a single error - page load might report samples into multiple ones. Each bucket has - descriptions that further explain the context of their samples. - - - - - - Removed as of 2020/07 - - edwardjung@chromium.org - security-enamel@chromium.org - - Counts of the type of navigation correction suggestions shown on the network - error page. Multiple suggestions can be shown at the same time. - - - - - - Removed as of 2020/07 - - edwardjung@chromium.org - security-enamel@chromium.org - - Usage of navigation correction suggestions shown on the network error page. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Counts of the type of offline content suggestions clicked on the network - error page. Reported upon click. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Counts of the type of offline content suggestions shown on the network error - page. Multiple suggestions can be shown at the same time. Reported when the - suggestions are presented. - - - - - - Removed 10/2016. - - mmenke@chromium.org - - The number of main frame 4xx/5xx responses that have content, to determine - if it's worth hooking up an error page for those that don't. Intended to be - removed from the binary soon. - - - - - - Removed 10/2016. - - mmenke@chromium.org - - The number of non-main frame 4xx/5xx responses that have content, to - determine if it's worth hooking up an error page for those that don't. - Intended to be removed from the binary soon. - - - - - mmenke@chromium.org - estark@chromium.org - - The number of entries loaded from the Expect-CT database when Chrome starts - up. - - - - - estark@chromium.org - - Sites can send an Expect-CT header to Chrome to indicate that they intend - their sites to comply with Chrome's Certificate Transparency policy. This - histogram is recorded whenever an Expect-CT header is processed on a - connection. True indicates that the header parsed successfully, and false - indicates that there was a parse failure. - - - - - estark@chromium.org - - Sites can send an Expect-CT header to Chrome to indicate that they intend - their sites to comply with Chrome's Certificate Transparency policy. This - histogram is recorded on connection setup, whenever Chrome connects to an - Expect-CT site using a publicly trusted root. The histogram records the CT - policy compliance status of the connection. - - - - - estark@chromium.org - - Sites can send an Expect-CT header to Chrome to indicate that they intend - their sites to comply with Chrome's Certificate Transparency policy. This - histogram is recorded whenever an Expect-CT header is successfully parsed on - a connection that chains to a publicly trusted root. The histogram records - the CT policy compliance status of the connection on which the header was - received. - - - - - - Removed 04/2017. - - estark@chromium.org - - Sites can send an Expect-CT header to Chrome to indicate that they want a - report to be sent when the connection does not comply with Certificate - Transparency policy. This histogram is recorded whenever Chrome receives an - Expect-CT header, and it records the result of processing the header, such - as whether it was ignored due to a bad value. - - - - - yoichio@chromium.org - ricea@chromium.org - yhirano@chromium.org - - Protocol used to fetch upload streaming with allowHTTP1ForStreamingUpload: - true property. This is recorded per fetch attempt regardless of result. - - - - - yoichio@chromium.org - ricea@chromium.org - yhirano@chromium.org - - Protocol used to fetch upload streaming with allowHTTP1ForStreamingUpload: - false property. This is recorded per fetch attempt regardless of result. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file Flush failed with. The code is OS dependent, - so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file GetSize failed with. The code is OS dependent, - so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file Open failed with. The code is OS dependent, so - when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file Read failed with. The code is OS dependent, so - when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file Seek failed with. The code is OS dependent, so - when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file SetEof failed with. The code is OS dependent, - so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code that a file Write failed with. The code is OS dependent, - so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file Flush failed with. Any value other than - 0 indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_Flush. The code is OS - dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file GetSize failed with. Any value other - than 0 indicates that we have received errors in a range outside of the one - in which we recorded the specific errors in Net.FileError_GetSize. The code - is OS dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file Open failed with. Any value other than 0 - indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_Open. The code is OS - dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file Read failed with. Any value other than 0 - indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_Read. The code is OS - dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file Seek failed with. Any value other than 0 - indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_Seek. The code is OS - dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file SetEof failed with. Any value other than - 0 indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_SetEof. The code is - OS dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - System error code range that a file Write failed with. Any value other than - 0 indicates that we have received errors in a range outside of the one in - which we recorded the specific errors in Net.FileError_Write. The code is OS - dependent, so when looking at the histogram don't mix OSes. - - - - - - Removed 2020-04 (M84). - - cmumford@chromium.org - - A compressed SVG file was loaded from the file scheme. This is a temporary - counter to determine how often (if at all) this feature is used. Recorded - during creation of file-request for .svgz resource. See - http://crbug.com/857117 for more information. - - - - - - Data collection ended, corresponding feature removed. - - dschinazi@chromium.org - src/net/OWNERS - - Track usage of alternative services forced by the force-alt-protocols - command line flag. Triggered each time alternative services are queried for - a given origin and the command line flag would make a difference (that is, - there is no advertised alternative service for that origin). - - - - - - Underlying implementation changed to no longer depend on OS. Removed in - Chrome 77. - - davidben@chromium.org - rsleevi@chromium.org - - Whether or not system installed trust anchors could be distinguished from - user installed trust anchors. Recorded on first certificate verification on - Android 4.2 and later. - - - - - tervay@google.com - asanka@chromium.org - - Each bucket is the result of whether or not the initiated FTP transaction. - Successful transactions are recorded as either authenticated or - unauthenticated. - - - - - - Removed in Chrome 76. - - phajdan.jr@chromium.org - The number of times each FTP Error was observed. - - - - - Removed in Chrome 76. - - phajdan.jr@chromium.org - - The number of Chrome sessions which encountered the indicates FTP Error. - This prevents allowing a user that retried a connection many times (getting - an error each time) from biasing the tallies. - - - - - - Replaced by Net.FtpServerTypeCount2 on 2012-11-03. - - phajdan.jr@chromium.org - - Each bucket is the number of times the FTP server type was encountered. - - - - - - Removed in Chrome 76. - - phajdan.jr@chromium.org - - Each bucket is the number of times the FTP server type was encountered. - - - - - - Removed at some time before 2014/09/15. - - Please list the metric's owners. Add more owner tags as needed. - - The time spent waiting for WinHttpGetProxyForUrl to return with error. - - - - - - Removed at some time before 2014/09/15. - - Please list the metric's owners. Add more owner tags as needed. - - The time spent waiting for WinHttpGetProxyForUrl to return with success. - - - - - - Removed June 2016. - - davidben@chromium.org - - Records a sample for each HTTPS request to a Google server that either - succeeded or received an inappropriate_fallback alert. This is used to - estimate how frequently the fallback is used to recover from a spurious - network failure. - - - - - - Replaced with Net.GoogleConnectionUsedSSLVersionFallback2 in Chrome 44. - - agl@chromium.org - - Nonzero if the HTTP request was to a Google server which required SSL - version fallback. The value indicates the SSL version the request fell back - on. Since Google servers support TLS 1.2, any fallback is an indication of - network middleware problems. - - - - - - Removed June 2016. - - davidben@chromium.org - - For each successful HTTPS request to a Google server, whether it used the - SSL version fallback. The value indicates the SSL version the request fell - back on. Since Google servers support TLS 1.2 and FALLBACK_SCSV, any - fallback is an indication of a broken local SSL MITM proxy. - - - - - - Removed around 2015/03/18. The code which implemented Gzip encoding fixup - was removed. - - asanka@chromium.org - - Resources are sometimes transferred with an incorrect encoding type of gzip. - net::Filter::FixupEncodingTypes() attempts to correct for these situations - by applying a set of heuristics. This histogram counts the frequency of - usage of these heuristics in the wild. - - - - - - The count was inaccurate (it counted transactions rather than connections). - - Please list the metric's owners. Add more owner tags as needed. - - Each bucket is a boolean (0 or 1) indicating whether the user has had a - connection of that type during the session. - - - - - - This statistic measures successful and failed connections, the new one only - measures successful ones. - - Please list the metric's owners. Add more owner tags as needed. - - Each bucket is a boolean (0 or 1) indicating whether the user has had a - connection of that type during the session. - - - - - - Removed May 2016. - - davidben@chromium.org - - Each bucket is a boolean (0 or 1) indicating whether the user has had a - successful connection of that type during the session. - - - - - - Replaced by Net.HadFtpServerType2 on 2012-11-13. - - phajdan.jr@chromium.org - - Each bucket is the number of sessions that encountered a given FTP server - type. Each session reports a given server type at most once. - - - - - - Removed in Chrome 76. - - phajdan.jr@chromium.org - - Each bucket is the number of sessions that encountered a given FTP server - type. Each session reports a given server type at most once. - - - - - davidben@chromium.org - - Records, on startup, for ARM devices running Android, whether the CPU is - known to have a broken NEON unit. See https://crbug.com/341598. - - - - - - Removed 2020-05. - - davidben@chromium.org - src/net/OWNERS - - Recorded for each host where we query the HSTS state, details on whether the - implementation matched the specification. See https://crbug.com/821811. - - - - - - Removed in 2017 March. - - dschinazi@chromium.org - src/net/OWNERS - Format of :status header value in HTTP/2 response. - - - - - Removed 2017-02. - - davidben@chromium.org - - The SSL/TLS cipher suite that was negotiated, recorded for each successful - HTTP/2 connection. - - - - - - Removed in Chrome 77. - - asanka@chromium.org - - Whether adding an entry to the HTTP auth cache evicted another entry. - - - - - - Removed in Chrome 77. - - asanka@chromium.org - - When an HTTP auth cache entry is evicted, the time since it was created. - - - - - - Removed in Chrome 77. - - asanka@chromium.org - - When an HTTP auth cache entry is evicted, the time since it was last used. - - - - - - Removed in Chrome 77. - - asanka@chromium.org - - Whether adding a path to an entry in the HTTP auth cache evicted another - path. - - - - - - Removed 10/2018 when changing the cache implementation such that the number - of entries examined no longer applies. - - chlily@chromium.org - - The number of entries examined (equal to the cache size) when attempting to - look up an HTTP auth cache entry (either by path or realm) and finding no - matching entries. This is recorded whenever the lookup fails (i.e., value 0 - in Net.HttpAuthCacheLookupPosition and - Net.HttpAuthCacheLookupByPathPosition). - - - - - - Removed 10/2018 when changing the cache implementation such that the lookup - position no longer applies. - - asanka@chromium.org - - When looking up an HTTP auth cache entry by path, the position (1-indexed) - of the entry on a hit, or 0 on a miss. - - - - - - Removed 10/2018 when changing the cache implementation such that the lookup - position no longer applies. - - asanka@chromium.org - - When looking up an HTTP auth cache entry by realm, the position (1-indexed) - of the entry on a hit, or 0 on a miss. - - - - - asanka@chromium.org - mmenke@chromium.org - - Per-authentication-scheme counts of authentication attempts and rejections. - - - - - asanka@chromium.org - mmenke@chromium.org - - Whether NTLMv2 was enabled for an authentication handshake. For a given data - set the number of samples here is expected to be equivalent to the - "NTLM Start" count in the "Net.HttpAuthCount" histogram. - Note that NTLMv2 being enabled makes the client behavior equivalent to - setting LmCompatibilityLevel to 3 or higher. - - - - - meacer@chromium.org - Type of the HTTP auth prompt displayed. - - - - - Removed in https://crrev.com/209100 - - Please list the metric's owners. Add more owner tags as needed. - - Count of authentication requests for top level pages vs. sub-resources, such - as images or iframes. - - - - - asanka@chromium.org - mmenke@chromium.org - - Per-authentication-scheme counts of authentication targets, such as secure - servers or proxies. - - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Time between the HttpNetworkTransaction requesting a connection and the time - it connected. - - - - - Please list the metric's owners. Add more owner tags as needed. - Length of time that a received resource will be cacheable. - - - - - Replaced by Net.HttpContentLengthV2 - - bengr@chromium.org - - Size of the response body. This is the actual number of bytes received, - which usually agrees with but is not necessarily the same as the size - specified by the Content-Length header. - - - - - - Removed 04/2018. - - bengr@chromium.org - - Size of the response body if it is cacheable. This is the actual number of - bytes received, which usually agrees with but is not necessarily the same as - the size specified by the Content-Length header. - - - - - - Removed 04/2018. - - bengr@chromium.org - - Size of the response body if it is cacheable for at least 24 hours. This is - the actual number of bytes received, which usually agrees with but is not - necessarily the same as the size specified by the Content-Length header. - - - - - - Removed 04/2018. - - bengr@chromium.org - - Size of the response body if it is cacheable for at least 4 hours. This is - the actual number of bytes received, which usually agrees with but is not - necessarily the same as the size specified by the Content-Length header. - - - - - - Removed 06/2018. - - bengr@chromium.org - - The difference between the size specified in the X-Original-Content-Length - header and the size of the response body. This is zero if the - X-Original-Content-Length header is not present in the response. - - - - - bengr@chromium.org - - The difference between the size specified in the X-Original-Content-Length - header and the size of the response body. Only includes resources that have - the X-Original-Content-Length header. - - - - - - - bengr@chromium.org - - Size of the response body. This is the actual number of bytes received, - which usually agrees with but is not necessarily the same as the size - specified by the Content-Length header. Replaces Net.HttpContentLength, - recording non-DRP Http traffic as "Http.Direct" instead of - "Http.Other". - - - - - - Removed 04/2018. - - bengr@chromium.org - - Size of the response body. Only includes resources that have the - X-Original-Content-Length header. - - - - - - Removed as of 12/2016. - - mmenke@chromium.org - - Records the frequency with which a number of hacky HTTP header parsing rules - are invoked. This histogram should be removed after we have enough data to - know if we can remove the hacks. - - - - - tsepez@chromium.org - - Count of requests which contained a basic auth username and password - embedded in the URL itself. - - - - - jkarlin@chromium.org - - Total prefilter (e.g., before decompression) bytes read for an HttpJob - request. - - - - - - - mmenke@chromium.org - - Time it takes to complete an HttpJob, from starting the transaction until we - are done reading. - - - - - - - mmenke@chromium.org - - Time it takes to complete an HttpJob, from starting the transaction until we - are done reading, for jobs served from the cache. - - - - - - - mmenke@chromium.org - - Time it takes to complete an HttpJob, from starting the transaction until - the job is killed. Note that we didn't detect the end of the data for this - job. - - - - - - - mmenke@chromium.org - - Time it takes to complete an HttpJob, from starting the transaction until we - are done reading, for jobs not served from the cache. - - - - - - - mmenke@chromium.org - - Time it takes to complete an HttpJob, from starting the transaction until we - are done reading, for jobs when we read until no more data is available. - - - - - - Replaced by Net.HttpOriginalContentLengthV2. - - bengr@chromium.org - - Size specified in the X-Original-Content-Length header. If this header is - not present in the response, the size of the response body is used. - - - - - - - bengr@chromium.org - - Net.HttpOriginalContentLength with non-data reduction proxy traffic properly - labeled with the "Direct" suffix. - - Size specified in the X-Original-Content-Length header. If this header is - not present in the response, the size of the response body is used. Replaces - Net.HttpOriginalContentLength, breaking down traffic by Direct, ViaDRP, - Bypassed, and Other. - - - - - bengr@chromium.org - - Size specified in the X-Original-Content-Length header. Only includes - resources that have the X-Original-Content-Length header. - - - - - eroman@chromium.org - tbansal@chromium.org - - Time taken to establish the connection to the HTTP proxy. Note that the - histogram expired briefly for M-86 and M-87 non-stable versions. Exact - counts during that period may not be meaningful. - - - - - - Removed as of 10/2016. - - mmenke@chromium.org - Time it takes to request a new (unused) HTTP proxy socket. - - - - - Removed 06/2016 because this is not continuously tracked. - - hiroshige@chromium.org - - Whether a request contains invalid request header values in RFC 7230. This - is counted once for every redirect leg. https://crbug.com/455099. - - - - - - Removed in M79. - - sclittle@chromium.org - bengr@chromium.org - - The network error code that the HTTP request completes with, including OK - and ABORTED. - - - - - - Removed in M79. - - sclittle@chromium.org - bengr@chromium.org - - The network error code that the HTTP main frame resource request completes - with, including OK and ABORTED. - - - - - - Removed 06/2016 because this is not continuously tracked. - - hiroshige@chromium.org - - Whether a response contains invalid response header values in RFC 7230. This - is counted once for every redirect leg. https://crbug.com/455099. - - - - - - - mmenke@chromium.org - The count of HTTP Response codes encountered. - - - - - Removed as of 06/2019. Net.HttpResponseCode has similar information, but for - all resources, not just the main frame, and includes the full response code. - - mmenke@chromium.org - - The count of HTTP Response codes encountered, in response to MAIN_FRAME - requests only; saving only the hundreds digit, e.g. 100->1, 300->3. - - - - - - Removed as of 06/2016. - - dschinazi@chromium.org - src/net/OWNERS - - Application protocol used in HTTP response. Recorded every time a URLRequest - completes. - - - - - - Removed as of July 2018. - - mmenke@chromium.org - - Application protocol used in HTTP responses to requests for main frames. - Only includes requests that went over the network. - - - - - - Removed as of July 2018. - - mmenke@chromium.org - - Application protocol used in HTTP responses to requests for resources other - than main frames. Does not include internal Chrome requests. Only includes - requests that went over the network. - - - - - zhongyi@chromium.org - mmenke@chromium.org - - The total number of ServerInfo structs written to the network service's - prefs file, recorded each time the HttpServerProperties are serialized to - update the copy stored on disk. - - - - - - Removed as of July 2019. - - dschinazi@chromium.org - src/net/OWNERS - - The location in http_server_properties_manager.cc where UpdatePrefs was - called. - - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The counts of the type of sockets (all HTTP sockets, regardless of any proxy - used) used for HTTP[s]. - - - - - - Removed as of 12/2016. - - ellyjones@chromium.org - - Records how often violations of RFC 7230's header parsing rules are - observed. - - - - - - Removed as of 1/2018. - - mef@chromium.org - pauljensen@chromium.org - Reports the next state that the Alternative Job is in. - - - - - Removed as of 1/2018. - - mef@chromium.org - pauljensen@chromium.org - Reports the state that the Alternative Job is in. - - - - - Removed as of 1/2018. - - mef@chromium.org - pauljensen@chromium.org - Reports the next state that the Main Job is in. - - - - - Removed as of 1/2018. - - mef@chromium.org - pauljensen@chromium.org - Reports the state that the Main Job is in. - - - - - Removed 08/2017. No longer tracked. - - zhongyi@chromium.org - Time it takes for OnStreamReadyCallback to be called. - - - - - - mmenke@chromium.org - - Time from when an HTTP request is issued to when the first byte is - processed. - - - - - - Removed 06/2019. - - mmenke@chromium.org - - Time from when an HTTP request is issued to when the first byte is - processed, for requests with an upload that is > 1 MiB. Excludes chunked - uploads. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The count of handleable socket errors (connection abort/close/reset) per - socket reuse type. - - - - - - Late bindings are on by default now. - - Please list the metric's owners. Add more owner tags as needed. - - The count of handleable socket errors (connection abort/close/reset) per - socket reuse type. Socket late binding is disabled. - - - - - - Late bindings are on by default now. - - Please list the metric's owners. Add more owner tags as needed. - - The count of handleable socket errors (connection abort/close/reset) per - socket reuse type. Socket late binding is enabled. - - - - - - Removed 11/2014. No longer tracked. - - bengr@chromium.org - - Time from when the IOThread is created to when the first URL request is - started. Only requests that are created for a profile while Chrome is - starting up are considered. - - - - - - Removed 1/2015. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - Duration of time spent during the UDP-connect IPv6 probe. - - - - - Removed 03/2015. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Whether the interface-enumeration IPv6 probe method failed given that the - UDP-connect IPV6 probe failed. - - - - - - Removed 03/2015. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Whether the interface-enumeration IPv6 probe method was successful given - that the UDP-connect IPV6 probe was successful. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - The probe results when a test for IPv6 support is done. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The probe results when a test for IPv6 support is done, after a network - change event. - - - - - - Removed 01/2018. - - zhongyi@chromium.org - - This counts number of all the job controllers that are still alive if the - count is a multiple of 100: 100, 200, 300, etc. - - - - - - Removed 01/2018. - - zhongyi@chromium.org - - This counts number of JobControllers that are still alive, not created for - preconnect, and still have a HttpStreamFactoryImpl::Request pending. - - - - - - Removed 01/2018. - - zhongyi@chromium.org - - This counts number of job controllers that are still alive, not created for - preconnect but HttpStreamFactoryImpl::Request has completed. - - - - - - Removed 01/2018. - - zhongyi@chromium.org - - This counts number of job controllers which are used for preconnect and are - still alive. - - - - - - Removed 01/2018. - - zhongyi@chromium.org - - This counts number of all the job controllers that are still alive. - - - - - - Removed 08/2017. - - zhongyi@chromium.org - - This counts number of alternative jobs which are still alive. - - - - - - Removed 08/2017. - - zhongyi@chromium.org - This counts number of main jobs which are still alive. - - - - - Removed 04/2017, replaced by - Net.JobController.CountOfJobController.NonPreconnect.PendingRequest. - - zhongyi@chromium.org - - This counts number of HttpStreamFactoryImpl::Request which are still alive. - - - - - - Removed 04/2017, replaced by - Net.JobController.CountOfJobController.Preconnect. - - zhongyi@chromium.org - - This counts number of job controllers which are used for preconnect and are - still alive. - - - - - yhirano@chromium.org - kinuko@chromium.org - - Whether and how keepalive requests are blocked. There is a similar histgoram - "Extensions.WebRequest.KeepaliveRequestState": This histogram - supports platforms where extensions are not supported. - "Extensions.WebRequest.KeepaliveRequestState" includes requests - rejected by WebRequest.onBeforeRequest() which are not counted in this - histogram. - - - - - yhirano@chromium.org - panicker@chromium.org - - The size of the request headers for each request with keepalive specified. - - - - - yhirano@chromium.org - kinuko@chromium.org - The end state of keepalive request. - - - - yhirano@chromium.org - panicker@chromium.org - - The sum of the size of the request headers and destination URL for each - request with keepalive specified. - - - - - yhirano@chromium.org - panicker@chromium.org - - The size of the destination URL for each request with keepalive specified. - - - - - - Removed 02/2018, replaced by - Net.KeepaliveStatisticsRecorder.PeakInflightRequests2 - - yhirano@chromium.org - - The peak number of concurrent outstanding requests with keepalive specified. - - - - - yhirano@chromium.org - - The peak number of concurrent outstanding requests with keepalive specified. - This histogram is reported whenever the peak number is updated. For example, - if the inflight number of requests were 0 => 1 => 2 => 1 => 2 - => 3 => 2, then 0, 1, 2, and 3 would be reported. - - - - - yhirano@chromium.org - - The peak number of concurrent outstanding requests with keepalive specified - per render process. - - - - - yhirano@chromium.org - - The peak number of concurrent outstanding requests with keepalive specified - per render process. This histogram is reported whenever the peak number is - updated. For example, if the inflight number of requests were 0 => 1 - => 2 => 1 => 2 => 3 => 2, then 0, 1, 2, and 3 would be - reported. - - - - - - Removed July 2018 - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - The completion status of prefetches that have finished loading. - -
- Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled - before that point are not registered. - - This applies to requests with net::LOAD_PREFETCH, used by various - prefetching features such as no-state prefetch and RESOURCE_TYPE_PREFETCH. - - Note that "success from cache" means that the - UrlRequest::was_cached() was true and unused_since_prefetch was false. - "success from network" means that was_cached() was false. - "success already prefetched" means that both was_cached() and - unused_since_prefetch were true. Validated results are considered cached, - even though a conditional network request is made. -
- - - - jkarlin@chromium.org - - The distribution of storable vs "cache-control: no-store" - main-frame resources. - - Counted after response headers have completed and before the content has - completed. Redirects are counted. All HTTP cache transactions are counted, - not just those that require the network. - - - - - morlovich@chromium.org - wicarr@microsoft.com - webmedia@microsoft.com - - Records decision points on whether response-side media content will be - cached or not. This is determined after receiving the HTTP response headers - and before attempting to write the the cache. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The time that a (non-cancelled) proxy resolution request was stalled waiting - for an execution thread, for MultiThreadedProxyResolver. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that it took for a (non-cancelled) proxy resolution request - to complete, for MultiThreadedProxyResolver. - - - - - davidben@chromium.org - - Records, on startup, for ARM devices running Android, whether the kernel is - missing AT_HWCAP2 from the ELF auxv and /proc/cpuinfo reports support for - ARMv8 features. Those features should also be reported in AT_HWCAP2. This is - to measure the workaround in https://crbug.com/boringssl/46. - - - - - - Removed in Chrome 44. - - eroman@chromium.org - - Counts the number of browser launches where chrome://net-internals and - chrome://net-internals/#tests are used. - - - - - mef@chromium.org - pauljensen@chromium.org - - This is logged when SCDynamicStoreCreate fails in - network_config_watcher_mac.cc. - - - - - mef@chromium.org - pauljensen@chromium.org - - This is logged when SCDynamicStoreCreateRunLoopSource fails in - network_config_watcher_mac.cc. - - - - - mef@chromium.org - pauljensen@chromium.org - - This is logged when retrying SCDynamicStore has stopped after either - receiving a success or hitting the maximum number of retries in - network_config_watcher_mac.cc. The 0 bucket is where no retry is performed, - and the maximal bucket is where all retries have failed. - - - - - - Removed 06/2020 for cleanup. https://crbug.com/1089011. Not actively used, - large size, and information is not actionable. - - chlily@chromium.org - - When Network Error Logging receives a "NEL:" header, what happens - to it. - - - - - - Removed 11/2019 for cleanup. https://crbug.com/1007122 - - chlily@chromium.org - - When Network Error Logging observes a completed request that might generate - a report, what happens to it. NEL observes all requests, both successful and - unsuccessful. It sends reports for successful and unsuccessful requests at - specified sampling rates so that error rates can be calculated. Insecure - requests are discarded for having an insecure origin regardless of existence - of a policy for the origin. - - - - - horo@chromium.org - ksakamoto@chromium.org - kinuko@chromium.org - - When Network Error Logging observes a completed request of signed exchange - that might generate a report, what happens to it. NEL observes all requests, - both successful and unsuccessful. It sends reports for successful and - unsuccessful requests at specified sampling rates so that error rates can be - calculated. Insecure requests are discarded for having an insecure origin - regardless of existence of a policy for the origin. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How often automatically retrying to download the main frame of a page in - response to specific HTTP network errors succeeds. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How often automatically retrying to download a subresource in response to - specific HTTP network errors succeeds. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How often automatically retrying to download the main frame of a page in - response to specific HTTP network errors returns another network error. - Histogram includes only the error code that triggered the retry. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - How often automatically retrying to download a subresource in response to - specific HTTP network errors returns another network error. Histogram - includes only the error code that triggered the retry. - - - - - pauljensen@chromium.org - - On Windows, NetworkChangeNotifierWin calls NotifyAddrChange, which can fail - for unknown reasons. This records the number of times it fails in a row - before a successful call. If it never succeeds, or takes over 100 tries, a - value of 100 is recorded. See http://crbug.com/69198 - - - - - - Removed 2015-08-17 as part of cookie histogram cleanup - (https://crbug.com/521135). - - Please list the metric's owners. Add more owner tags as needed. - - The number of duplicate cookies that were present in the cookie store during - startup. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of QUIC sessions when the QuicStreamFactory is destroyed. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to make one or more HTTP - fetches to OCSP responders in order to get revocation information. This - measures the amount of time that failures to get OCSP information take. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to make one or more HTTP - fetches to OCSP responders in order to get revocation information. This - records the fraction of successful requests. - - - - - - Removed 2017-04-21 as it was Linux/CrOS only. - - rsleevi@chromium.org - - When validating an HTTPS certificate we may have to make one or more HTTP - fetches to OCSP responders in order to get revocation information. This - measures the amount of time that each of those requests takes. - - - - - - Removed 12/2018. - - rsleevi@chromium.org - - When connecting over HTTPS, a server may include an OCSP response as part of - the TLS handshake so that clients do not have to fetch it, provided the - client requested the server do so. This measures whether or not a server - included an OCSP response when it was requested. - - - - - - Removed 11/2018. - - mgersh@chromium.org - - Positive error code that was returned by the system library - "getaddrinfo()". This error code is platform specific, so when - there is a Windows/Linux conflict, both decodings are shown. - - - - - - Removed 11/2018. - - mgersh@chromium.org - - Positive error code that was returned by the system library - "getaddrinfo()". - - - - - - Removed 11/2018. - - mgersh@chromium.org - - Positive error code that was returned by the system library - "getaddrinfo()". - - - - - - Removed 11/2018. - - mgersh@chromium.org - - Positive error code that was returned by the system library - "getaddrinfo()". - - - - - - Removed 4/27/2016. No longer tracked. - - eroman@chromium.org - - Proxy Auto Config (PAC) allows specifying an arbitrary javascript program to - pick network proxies on a per-request basis (based on the URL). This works - by calling the script's FindProxyForURL() function with the target URL as - its first argument. - - Traditionally, the URL parameter passed into the script contains the exact - URL being loaded, except maybe for having stripped the fragment and embedded - identity portions of the URL. - - This histogram records what happens when the URL passed into - FindProxyForURL() additionally has had its path component stripped. Does it - return the same proxy list as when calling FindProxyForURL() with the - original (unmodified) URL? - - This comparison is done only when the URL scheme implies a secure channel - (i.e. https:// and wss://), in order to gather data for crbug.com/593759. - - - - - - Removed 4/16/2014. No longer tracked. - - davidben@chromium.org - - How long it took for an <a ping> request to receive a response. Only - recorded if a response was received. - - - - - - Removed 4/16/2014. No longer tracked. - - davidben@chromium.org - - The result of an <a ping> request, whether it received a response or - timed out or failed for some other reason. - - - - - - No longer tracked. - - csharrison@chromium.org - - Indicate whether a link navigation was preceded by a recent pre-connect - trigger (within 10 seconds). There is a high chance that loading the page - used a preconnected TCP session. - - - - - - No longer tracked. - - csharrison@chromium.org - - Indicate whether a URLRequest was preceded by a recent pre-connect trigger - (within 10 seconds). There is a high chance that loading the resource used a - preconnected TCP session. - - - - - - Removed May 2018 - - csharrison@chromium.org - - When a preconnection is made, indicate what the motivation was. - -
- Currently, the most common (only?) motivations are SELF_REFERAL, - LEARNED_REFERAL and OMNIBOX. The SELF_REFERAL indicates that we made sure a - second connection was available for a resource that either was never before - seen, or has historically had no subresources. The LEARNED_REFERAL indicates - that we "learned" that a subresource was commonly needed, and that - motivated the TCP/IP preconnect. The OMNIBOX motivation happens when a - search is being suggested, and we preconnect to the search provider. - (WARNING: Prior to version 7.517.*, enums 7, 8, and 9 may be confused, as - EARLY_LOAD_MOTIVATED was inserted new 6 value.) -
- - - - - No longer tracked. - - csharrison@chromium.org - - Indicate whether there was a proxy to preclude preconnection. - - - - - - Removed September 2019 - - tbansal@chromium.org - - Indicates number of times a preconnect to proxy server was skipped due to an - existing pending preconnection request. - - - - - - Removed May 2018 - - csharrison@chromium.org - - What did we decide to do about a predicted resource, based on the historical - expected number of connection that this subresource will require. - -
- This is basically the current thresholding of the SubresourceExpectation, - relative to current static thresholds, and taking into account whether - preconnection is enabled (i.e., if preconnection is disabled, we'll never - decide to preconnect). -
- - - - - Removed May 2018 - - csharrison@chromium.org - - The expected number of connections, times 100, that we'll make to a given - subresource, based on learned history. - -
- By comparing this to thresholds, we decide if we will preconnect, - preresolve, or do nothing. This histogram can be used to select those static - thresholds. -
- - - - - No longer tracked. - - csharrison@chromium.org - - Indicate whether if a preconnect trigger is followed by a resource request - (from link navigations) to the host or not. This is to measure precision of - link-based preconnect triggers. - - - - - - Sourced data corrected, and replaced by NetPreconnectUtilization2 - - Please list the metric's owners. Add more owner tags as needed. - - Indicate final utilization for each attempted socket connection. - -
- We also include stats for non-speculative sockets. Some socket connections - may never connect, and others may never be used (as the user may abort - before then). -
- - - - - Removed in M68 (May 2018) - - csharrison@chromium.org - - Indicate final utilization for each attempted socket connection. - -
- We also include stats for non-speculative sockets. Some socket connections - may never connect, and others may never be used (as the user may abort - before then). -
- - - - - Dev data was collected which was good enough to make a decision on the size - of the predictor database. - - csharrison@chromium.org - - The index into the predictor's MRU on navigation. This is the size the MRU - had to be in order to effectively predict subresources for this navigation. - - - - - - Removed May 2018 - - csharrison@chromium.org - - The approximate size in bytes of the predictor's database on startup. - - - - - jkarlin@chromium.org - - Bytes read for requests that were served from a cache entry whose - unused_since_prefetch bit is true. - - - - - - Removed July 2018 - - jkarlin@chromium.org - - The completion status of prefetches that have finished loading. - -
- Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled - before that point are not registered. - - This applies to requests with RESOURCE_TYPE_PREFETCH. - - Note that "success from cache" means that the - UrlRequest::was_cached() was true and unused_since_prefetch was false. - "success from network" means that was_cached() was false. - "success already prefetched" means that both was_cached() and - unused_since_prefetch were true. Validated results are considered cached, - even though a conditional network request is made. -
- - - - jkarlin@chromium.org - - Number of bytes read from the network on behalf of prefetch requests. This - is prefilter, so before any decompression. - -
- This applies to requests with RESOURCE_TYPE_PREFETCH. -
- - - - - Removed July 2018 - - jkarlin@chromium.org - - Time spent on prefetch requests before the request was canceled. - -
- This applies to requests with RESOURCE_TYPE_PREFETCH. -
- - - - - Removed July 2018 - - jkarlin@chromium.org - - Time spent on requests that were served from a cache entry whose - unused_since_prefetch bit is true. - - - - - - Removed July 2018 - - jkarlin@chromium.org - Time spent on prefetch requests when fetched from cache. -
- This applies to requests with RESOURCE_TYPE_PREFETCH. -
- - - - - Removed July 2018 - - jkarlin@chromium.org - - Time spent on prefetch requests when fetched from the network, including - validation time. - - - - - - Removed in M52. - - sclittle@chromium.org - - Records how many *.googlezip.net Data Reduction Proxies were removed from - the effective proxy configuration when a proxy reconfiguration occurs. - - - - - - Replaced by Net.Priority_High_Latency_b. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the start of the http transaction until the first byte of the - response for high priority (currently frame and subframe) requests. Only - times under 10 minutes are recorded. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the start of the http transaction until the first byte of the - response for high priority (currently frame and subframe) requests. - - - - - - Replaced by Net.Priority_Low_Latency_b. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the start of the http transaction until the first byte of the - response for low priority (non-frame/subframe) requests. Only times under 10 - minutes are recorded. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the start of the http transaction until the first byte of the - response for low priority (non-frame/subframe) requests. - - - - - - Removed in Chrome 76. - - eroman@chromium.org - mmenke@chromium.org - - Counts how often a 302 (redirect) response is observed during CONNECT (proxy - tunnel establishment). The counts are bucketed by proxy settings source - (auto-detect vs explicit) and load type (subresource vs main frame). - - To interpret this histogram, the most interesting property will be the - number of users in each of the buckets, which can be used to approximate - what fraction of users would be affected by a policy change that blocked - redirects on subresources/non-autodetected proxies. - - - - - - Removed 2019/02/28, in a proxy auth refactor. - - dschinazi@chromium.org - src/net/OWNERS - - When a PROXY_AUTH_REQUESTED error code is handled in - net::HttpStreamFactoryImpl::Job::RunLoop, this is true if connection_ has an - associated value. - - - - - - Removed at some time before 2014/09/15. - - Please list the metric's owners. Add more owner tags as needed. - - The time in milliseconds spent fetch the system proxy configuration, when - polling it for changes. - - - - - - Removed in M85. - - eroman@chromium.org - - The breakdown of URL schemes seen for explicitly configured ProxyAutoConfig - (PAC). This metric is emitted once each time the proxy settings change - (including initial value). Note that this does not count implicitly inferred - PAC URLs (from WPAD). - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total amount of time that was spent executing the proxy script during - "tracing" runs (executions of the script which discovered a new - DNS dependency and were subsequently abandoned). - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total amount of time that was spent executing the proxy script during - "tracing" runs (executions of the script which discovered a new - DNS dependency and were subsequently abandoned). - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total amount of time that was spent in the non-blocking DNS bindings - while executing PAC scripts. This includes the times for abandoned - executions. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time inside of V8 that the proxy script spent executing for - the final pass. This includes the time spent in the javascript bindings. - This does not include the time spent in abandoned execution passes. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times that alert() was called in the final execution of the - script. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of errors that were seen in the final execution of the script. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times that the PAC script execution was restarted. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that the proxy resolution took. This includes all the time - spent waiting for DNS, PAC script execution, and restarts. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that proxy resolution spent waiting for DNS. This also - includes any queuing delays on the origin thread waiting for the DNS result - to be processed. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of unique DNS hostnames that the PAC script tried to resolve. The - *Ex() versions of the bindings count separately. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total amount of time that was spent in the non-blocking DNS bindings - while executing PAC scripts. This includes the times for abandoned - executions. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time inside of V8 that the proxy script spent executing for - the final pass. This includes the time spent in the javascript bindings - (which is probably dominated by Net.ProxyResolver.DnsWaitTotalTime). This - does not include the time spent in abandoned execution passes. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times that alert() was called in the final execution of the - script. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of errors that were seen in the final execution of the script. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times that the PAC script execution was restarted. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The amount of time it took upon completion to run the final task posted back - to the IO thread. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that the proxy resolution took. This includes all the time - spent waiting for DNS, PAC script execution, and restarts. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that proxy resolution spent waiting for DNS. This also - includes any queuing delays on the origin thread waiting for the DNS result - to be processed. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The total time that the proxy resolution took, not including the post back - to the origin thread. This includes all the time spent waiting for DNS, PAC - script execution, and restarts. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - - The number of unique DNS hostnames that the PAC script tried to resolve. The - *Ex() versions of the bindings count separately. - - - - - - Removed in Chrome 39. - - Please list the metric's owners. Add more owner tags as needed. - The length of the URL that was passed into the PAC script. - - - - eroman@chromium.org - - The time taken from requesting a PAC script to receiving the first byte of - the response body on successful fetches. This does not include time spent - doing proxy auto-discovery, or failed attempts at retrieving PAC scripts. If - the response body was empty, this measures the total time to fetch the - (empty) response body. - - - - - eroman@chromium.org - - The time taken to successfully fetch a PAC script. This does not include - time spent doing proxy auto-discovery, or failed attempts at retrieving PAC - scripts. - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - The network error code of resolving a URL by forwarding the request to the - proxy resolver and executing the PAC script. - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - The time taken to resolve a URL by forwarding the request to the proxy - resolver and executing the PAC script. This includes PAC script execution, - DNS queries, and internal retries. This does not include retries initiated - by the user, such as by calling ProxyService::ReconsiderProxyAfterError(). - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - Whether proxy resolution occured by forwarding the request to the proxy - resolver and executing the PAC script. This histogram records all URLs, - regardless of whether a proxy configuration is set. Note that in some cases, - the system proxy resolver is used. If so, this histogram indicates whether - the request was forwarded to the system resolver. However, on desktop - platforms, the number of users using the system resolver should be small - since the default is to use V8. Hence, the count of emissions to the 'True' - bucket on desktop caused by users of the system resolver should be small. - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - The total time taken to resolve a URL. This includes PAC script execution, - DNS queries, and internal retries. This does not include retries initiated - by the user, such as by calling ProxyService::ReconsiderProxyAfterError(). - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - Whether a proxy resolution resulted in the PAC script terminating - unexpectedly. This does not include terminations that occured during - initialization of a new proxy resolver. This only happens when the resolver - process crashes when using out-of-process PAC. - - - - - - Removed as of Chrome 61. - - eroman@chromium.org - - Whether the creation of a new proxy resolver resulted in the PAC script - terminating unexpectedly. This only happens when the resolver process - crashes when using out-of-process PAC. - - - - - - Removed as of November 2016 because of disuse. Historical data is likely - inaccurate due to changes in the data structure that calculated domain IDs - for this histogram. - - agl@chromium.org - - Second-level domains for which we have observed public key pinning failures. - - - - - - Removed as of 07/2016. Replaced with Net.PublicKeyPinReportSendingFailure2. - - estark@chromium.org - - A validated certificate chain may be subject to additional pinning - requirements on a per-domain basis. When pinning requirements are violated, - Chrome attempts to send a report about the incident. This records the net - error code when sending a pinning violation report fails. - - - - - estark@chromium.org - - A validated certificate chain may be subject to additional pinning - requirements on a per-domain basis. When pinning requirements are violated, - Chrome attempts to send a report about the incident. This records the net - error code when sending a pinning violation report fails. - - - - - agl@chromium.org - - A validated certificate chain may be subject to additional - "pinning" requirements on a per-domain basis. This records the - fraction of successful matches between a certificate chain and a pin list. - - - - - - Removed 11/2017. - - dschinazi@chromium.org - src/net/OWNERS - - Records whether HTTP/2 response headers have already arrived on a pushed - stream at the time the stream is matched up with a request. See - https://crbug.com/554220. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Information about the value of the Vary response header in HTTP/2 pushed - streams. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of active QUIC sessions before we activate a new QUIC session. - - - - - - Obsoleted in April 2020. - - tbansal@chromium.org - rajendrant@chromium.org - robertogden@chromium.org - - Breakdown of how requests which could potentially make use of an alternative - QUIC proxy server use or don't use the QUIC server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Tracks the number of QUIC alt-svc advertisements parsed by Chrome in Google - format vs in IETF format. - - - - - - Removed 11/2019, associated bug is root-caused and fixed. - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of times that QuicChromiumPacketReader should stop reading in the - loop at StartReading. This data will be compared against crashes and help - investigate https://crbug.com/1014092. - - - - - - Removed 11/2019, associated bug is root-caused and fixed. - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of times that QuicChromiumPacketReader should stop reading after - finishing the previous read. This data will be compared against crashes and - help investigate https://crbug.com/1014092. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The reject reasons for QUIC's CHLO (client hello) message from server - - - - - - Removed 08/2014, and replaced by - Net.QuicClientHelloServerConfig.InvalidDuration. - - dschinazi@chromium.org - src/net/quic/OWNERS - - How expired server config is for sending inchoate ClientHello to the server. - - - - - - Removed in 2018. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The time since expiration of server config when we sent inchoate ClientHello - to the server. - - - - - - Removed as of 11/2014. Replaced by Net.QuicInchoateClientHelloReason. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The reason (the state of the server config) for sending inchoate ClientHello - to the server. - - - - - - Removed 02/2018. No data for this histogram for more than 30 days. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times Connection's visitor is a nullptr when CloseConnection - is called. - - - - - wub@chromium.org - src/net/quic/OWNERS - - The write result returned by the packet writer when the connection attempts - to write a packet. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of active sessions that are degrading on network changes. The - suffix specifies the network change. Emitted when there are more than one - active sessions. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - The number of active QUIC sessions when a network change is detected. The - suffix specifies the network change. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of all sessions that detectes path degradation until a network - change happens, including both active sessions and closed sessions. The - suffix specifies the network change. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - The total number of sessions that reports path degradation before a network - change happens, including both still active sessions and closed sessions. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - The number of total sessions that has been tracked since the first - speculative error, including both active and closed sessions. Only recorded - if non-zero. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - The number of total sessions that has been closed due to - QUIC_PACKET_WRITE_ERROR before first path degradation detection. - - The histogram is emitted when session path degrading is detected for the - first time on the current network and there was a session closed with a - speculative signal (QUIC_PACKET_WRITE_ERROR). - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The percentage of active sessions that are degrading on network changes. The - suffix specifies the network change. Emitted when there are at least two - active sessions. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The percentage of all sessions that detectes path degradation until a - network change happens, including both active sessions and closed sessions. - Always emit 0 when there is no session reporting path degrading to speculate - a connectivity failure on the current network. The suffix specifies the - network change. - - The histogram is emitted when a network change happens which could affect - the current default network, which includes the default network being - changed, alternate networks being connected. It, however, doesn't emit when - disconnecting an alternate network because that does not affect the current - default network. - - - - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - When a packet write error is detected by the session, if path degradation - has been detected already on the same session. - - The histogram is emitted when a session encounters a QUIC_PACKET_WRITE_ERROR - and is soon to be closed. - - - - - - Removed in 2018. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times CryptoClientConfig's CachedState is populated from - canonical config whenever we create a new CryptoClientConfig::CachedState. - - - - - - Removed as of 4/15/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Tracks number of times data read/parse/write API calls of QuicServerInfo to - and from disk cache is called. - - - - - - Removed as of 10/2014. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Tracks the opening and closing of disk cache entries. Recorded each time a - disk cache entry is either opened or closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Tracks failure reasons to read/load/write of QuicServerInfo to and from disk - cache. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The reason a QUIC packet could not be processed, logged for each dropped - packet. - - - - - - Removed as of 04/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of ports suggested per server. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of QUIC packets received by a QUIC connection whose handshake was - not confirmed when that connection is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The state of a QUIC connection's crypto hanshake as it progresses from - starting to confirmation or failure. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The compression percentage, logged for each sent HPACK compressed header - frame. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - For each indexed representation decoded, records the time since the - corresponding entry was added to the dynamic table. This data is being - collected to help analyze a proposed solution to HPACK induced head of line - blocking. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The decompression percentage, logged for each received HPACK compressed - header frame. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - For each indexed representation encoded, records the time since the - corresponding entry was added to the dynamic table. This data is being - collected to help analyze a proposed solution to HPACK induced head of line - blocking. - - - - - - Removed 2016. No longer tracked. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times QuicHttpStream's session_ is a nullptr before - StartRequest() is called. - - - - - - Removed in 2018. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The reason (the state of the server config) for sending inchoate ClientHello - to the server. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Time from when QUIC detects performance degradation on the current network - to when QUIC notices a new network is connected. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Time from when QUIC detects performance degradation on the current network - to when QUIC notices the current network is disconnected. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The time from QUIC detecting network performance degradation to an - alternative network becoming default. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The time from network disconnection to an alternative network becoming - default. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of client hello messages sent. - - - - - see Net.QuicSession.Connect*PortForHTTP* - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of client hello messages sent when the crypto handshake was - confirmed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of times ServerConfigUpdateMessages ignored. - - - - - Removed in 07/2020. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of stream frames bundled within a received packet. - - - - - - Removed in 07/2020. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of stream frames per stream ID within a received packet. - - - - - - Removed as of 05/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times QuicHttpStream's stream_ is a nullptr before - IsDoneReading() is called. - - - - - - Removed as of 4/15/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - Time spent to load QUIC server information from disk cache. - - - - - Removed as of 10/2014. Replaced by DiskCacheWaitForDataReadyTime. - - dschinazi@chromium.org - src/net/quic/OWNERS - Time spent to load QUIC server information from disk cache. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The state of the QUIC server information when it's loaded from the disk - cache. - - - - - - Removed as of 4/19/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Time spent waiting to load QUIC server information from disk cache. - - - - - - Removed as of 4/15/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times AlternateProtocolMap supports QUIC, but there is no QUIC - server information in the disk cache. This is recorded whenever QUIC server - information is loaded from the disk cache. - - - - - - Removed as of 8/3/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The elapsed time between waiting for reading of QUIC server information from - disk cache, and receiving crypto handshake confirmation from the server. - Will measure the impact of cancelling the WaitForDataReady callback. Logged - after crypto handshake is confirmed. - - - - - - Removed as of 4/15/2017. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ratio of the time spent waiting to load QUIC server information from - disk cache to the min rtt. Logged when session is closed. - - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - - This histogram summarizes information about a 21 packet sequence, indicating - for each of the 21 possible prefixes of this pattern, how many packets were - received in that prefix. The first range uses buckets 0 and 1, and it - describes the 1st packet in the sequence. It indicates if the first packet - was missing (bucket 0), or the first packet was present (bucket 1). The - second range uses buckets 2 through 4, and describes the first 2 packets in - the prefix of this sequence. It indicates if there were no packets received - in the first two packets (bucket 2), or there was one out of two packets - received (bucket 3), or if there was two out of tow received (bucket 4). - etc. etc. Reading this histogram may require post-processing in a spread - sheet, but can indicate the potential value of using FEC packets to convey - data. - - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Each of the 64 buckets represents a different binary pattern of 6 - consecutive packets that were received by the client. The LSB of the bucket - number corresponds to the reception of the oldest packet. A bit in the - bucket-number being 1 indicates the packet was received, and a 0 means the - packet was never received (by the client). - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of pending stream requests aborted when the session is closed. - Pending streams are those which could not be created immediately because - there were too many active streams. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The number of active streams when the quic session decides to go away on - path degrading. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if the result of reading a packet from the network was ERR_IO_PENDING. - Recorded for each packet when Read() returns. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of BLOCKED frames recevied by a QuicSession when the session is - closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of BLOCKED frames sent by a QuicSession when the session is - closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code returned to a QUIC session from the CertVerifier when - a certification verification is attempted. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Time spent verifying a certificate when racing cert veriifcation with host - resolution. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The final maximum packet size of the connection used by the client before - the session is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code which resulted in all sessions being closed. - - - - - wub@chromium.org - src/net/quic/OWNERS - - For a QUIC session that is closed by a public reset, this boolean shows - whether it is a public reset sent from a Google server or not. - - - - - wub@chromium.org - fayang@chromium.org - src/net/quic/OWNERS - - For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is - the number of packets it received before it is closed. - - - - - wub@chromium.org - fayang@chromium.org - src/net/quic/OWNERS - - For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is - the number of packets it sent before it is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if the QUIC session is closed during the call to InitializeSession, - logged for each session just after InitializeSession is called. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code which resulted in the session being closed. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - When a new stream frame is added to a QUIC packet, record whether it's - coalesced with the existing stream frames. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Samples of the number of round-trips needed by a QUIC connection before a - request could be sent by the client. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if a QUIC connection connected successfully after having been broken. - Only emitted after a QUIC connection attempt to a server that was previous - marked as broken. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error which caused a QUIC connection to be closed before the - hanshake was confirmed, in the case where no packets were received. This - provides a breakdown of the entires in - Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value - is BLACK_HOLE. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error which caused a QUIC connection to be closed before the - hanshake was confirmed, in the case where at least 1 packet was received. - This provides a breakdown of the entires in - Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value - is UNKNOWN. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - The reason a QUIC handshake failed. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of streams open when a QUIC session crypto handshake timed out. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of streams open when a QUIC session timed out. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of total streams created when a QUIC session crypto handshake - timed out. - - - - - - Removed in M81. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the Google QUIC connection being - closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the Google QUIC connection being - closed by the client. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the Google QUIC connection being - closed by the client to a server ending in .google.com. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the Google QUIC connection being - closed by the server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the Google QUIC connection being - closed by the server with a name ending in .google.com. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server with a name ending in .google.com. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server, when the GQUIC error was missing. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server with a name ending in .google.com, when the GQUIC - error was missing. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC transport error code in a CONNECTION_CLOSE frame received from the - server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server with a name ending in .google.com. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC transport error code in a CONNECTION_CLOSE frame received from the - server, when the GQUIC error was missing. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC application transport error code in a CONNECTION_CLOSE frame - received from the server with a name ending in .google.com, when the GQUIC - error was missing. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The duration of a QUIC connection starting from 1-RTT key available to - connection close. - - - - - fayang@chromium.org - src/net/quic/OWNERS - Duration of connections received PUBLIC_RESET. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Whether QUIC session's connection is flow control blocked when a PING - message is sent to server. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - True if an active session already exists for a given Ip during connection. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The result of a QUIC connection migration attempt. The suffix specifies the - cause of connection migration. - - - - - fayang@chromium.org - zhongyi@chromium.org - src/net/quic/OWNERS - - The result of connectivity probing according to different migration causes. - Recorded for every connectivity probing when attempting connection - migrations. - - - - - renjietang@chromium.org - zhongyi@chromium.org - src/net/quic/OWNERS - - Logs the state of the connection from stale host when fresh dns resolution - is completed. This histogram is only valid when race_stale_dns_on_connection - experiment is enabled. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The IP Address family of this connection, as reported by the server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - The IP Address family of this connection, as seen locally. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Samples of the number of round-trips needed by a QUIC connection before a - request could be sent by the client, when handshake confirmation was - required. (The operating system randomly selected a source port for the - connection.) - - - - - - Removed in M75 - - dschinazi@chromium.org - src/net/quic/OWNERS - - Logs whether channel ID was used when a cookie is sent over QUIC to - https://accounts.google.com. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Count of errors during attempts to create a QUIC session (before even using - the session). - - - - - fayang@chromium.org - src/net/quic/OWNERS - - Times of retransmission time out of connections with successful handshake. - - - - - fayang@chromium.org - src/net/quic/OWNERS - - Times of crypto retransmission timeout of connections with failed handshake. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The number of draining streams when the quic session decides to go away on - path degrading. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of duplicate packets recevied by a QuicSession when the session - is closed. - - - - - fayang@chromium.org - src/net/quic/OWNERS - - The elapsed time between starting the crypto handshake and installing the - first encryption key that can carry application data (either 0-RTT or - 1-RTT). - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - Record where exactly packet serialization fails for investigation. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the TCP cubic sender's CWND when the session is closed. - - - - - renjietang@chromium.org - zhongyi@chromium.org - src/net/quic/OWNERS - - The time for a fresh DNS resolution from DoResolveHost to having a fresh DNS - result. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - This measures the time gap between the most recent write error and the - network disconnection. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Whether QuicGoAwayFrame is received from server for connection migration due - to client's port change. Logged when a QuicGoAwayFrame with error code - QUIC_ERROR_MIGRATING_PORT is received. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The elapsed time between starting the crypto handshake, and receiving - confirmation from the server. - - - - - - see Net.QuicSession.Connect*PortForHTTP* - - dschinazi@chromium.org - src/net/quic/OWNERS - - Samples of the number of round-trips needed by a QUIC connection before a - request could be sent by the client. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The handshake status when the session attempts to migrate the connection - according to different migration causes. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The handshake status when the session attempts to port migration on path - degrading. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Whether path degrading has been detected by the time a QUIC connection is - closed due to handshake timeout. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Header compression ratio as percentage for received headers using HPACK. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Header compression ratio as percentage for sent headers using HPACK. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Header compression ratio as percentage for received headers using QPACK. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Header compression ratio as percentage for sent headers using QPACK. - - - - - - The experiments with head of line blocking have been completed, and the code - tracking head of line blocking was removed. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The elapsed time that headers are head of line blocked on others, presumably - due to lost headers stream packets. - - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The frames received on the headers stream which arrived early. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The elapsed time between the end of resolving the DNS name of the server for - a QUIC connection, and receiving crypto handshake confirmation from the - server. Logged after crypto handshake is confirmed. - - - - - - Removed 08/2016. No longer tracked. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Time spent resolving the DNS name of the server for a QUIC connection. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number packets recevied by a QuicSession with an incorrect connection id - when the sesesion is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The source for the initial RTT estimate recorded when a QUIC session is - created. - - - - - - Removed 2018-10. No longer tracked. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The location where a QUIC internal error was generated, recorded any time an - internal error is generated, which should be once per connection. - - - - - fayang@chromium.org - src/net/quic/OWNERS - - Time from handshake completion to last packet was sent for connections - received PUBLIC_RESET. - - - - - fayang@chromium.org - src/net/quic/OWNERS - - A bitfield representing the last sent packet content before connection - receives PUBLIC_RESET. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - If a QUIC connection timed out locally with open streams, this contains the - time since any data was read from the network until the connection was - closed. The suffix specifies whether there were any unacked packets pending - when the connection timed out. {UnackedPackets} - - - - - Removed as of 08/2016. - - - - - Removed as of 08/2016. - - - - - Removed as of 08/2016. - - - - - - - fayang@chromium.org - src/net/quic/OWNERS - - Max consecutive retransmission timeout before making forward progress. - - - - - fayang@chromium.org - src/net/quic/OWNERS - - Max consecutive retransmission timeout before making forward progress when - blackhole has been detected. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The maximum packet sequence number reordering observed by a QUIC connection. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ratio of the maximum reordering time of a QUIC packet to the min rtt. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ratio of the maximum reordering time of a QUIC packet to the min rtt, - only for those sessions with a min rtt larger than 100 ms. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The minimum RTT observed during the life of a QUIC connection. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of MTU probes sent by the client during the session. Logged when - the connection is destroyed. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The number of active streams when idle timeout is detected and connection is - being closed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Number of connection migrations exercised before the connection receives a - public reset. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of QUIC streams opened when a new QUIC stream is created. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of pending stream requests when a new stream request is added to - the pending list. Pending streams are those which could not be created - immediately because there were too many active streams. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The number of pings a QUIC connection sends during its lifetime. - - - - - - Removed 04/2020, no longer needed. - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of queued packets when a connection is closed due to writing an - out of order packet. - - - - - - Removed in 2018. - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of queued packets when a connection starts to write queued - packets. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The number of streams waiting to write when idle timeout is detected and - connection is being closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The total number of streams created by the client when the session is - closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of missing packets between the current received packet and the - previously largest received packet sequence number, when the current - received packet had a lower sequence number than the previously received - packet sequence number. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times the current received packet had a lower sequence number - than the previously received packet sequence number, and the size of the - current packet is larger than the size of the previous packet. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of times the current received packet had a lower sequence number - than the previously received packet sequence number. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of missing packets between the current received packet and the - previously largest received packet sequence number. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of missing packets between the last received packet before a PING - frame sent and the first packet received after PING sent. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of missing packets between the current received packet and the - previously largest received packet sequence number, as reported by the - remote end of the connection. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ratio of the number of missing packets, to the maximum packet sequence - number received, for QUIC connections longer than 21 packets received via - - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Each bucket corresponds to a specific packet sequence number that was sent - by a server to Chrome at the start of a QUIC connection. This histogram is - compared, bucket by bucket, with a second histogram to compute the ratio for - each bucket (each packet sequence number). - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of packets retransmitted per 1000. Only sessions with - packets_sent >= 100 are included. Recorded in session destructor. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The time taken to Write() a QUIC packet to the socket. Recorded for each - packet when it is sent. The suffix specifies if the write completed - synchonously or asynchronously. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The wait time of the pending stream when it is finally serviced. Pending - streams are those which could not be created immediately because there were - too many active streams. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The platform notification received by QUIC when network change happens. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - The result of a QUIC port migration attempt. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if the QUIC session prefers to use AES GCM because of hardware support. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Number of retries to send connectivity probing packet on new path until - success. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The wait time to receive a matched probing response to mark connectivity - probing as successful. - - - - - - Removed 02/2018. Use Net.QuicSession.PublicResetAddressMismatch2. - - wtc@google.com - src/net/quic/OWNERS - - When a public reset packet is received, whether the client IP address and - port number in it differ from the client IP address and port number in the - ServerHello handshake message. In the comparison, the first address is the - one in ServerHello and the second address is the one in public reset. Note: - this histogram is obsolete because it failed to treat IPv4-mapped IPv6 - addresses as IPv4 addresses. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - When a public reset packet is received, whether the client IP address and - port number in it differ from the client IP address and port number in the - ServerHello handshake message. In the comparison, the first address is the - one in ServerHello and the second address is the one in public reset. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of push streams received when the session is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of pushed and used streams when the session is closed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of bytes that is pushed but not used when the session is closed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of bytes that is pushed when the session is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ordinality of a header list within a connection during the encoding of - which unacknowledged dynamic table entries could not be referenced due to - the limit on the number of blocked streams. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ordinality of a header list within a connection during the encoding of - which at least one dynamic table insertion was blocked. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ordinality of a header list within a connection during the encoding of - which no dynamic table insertion was blocked. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The ordinality of a header list within a connection during the encoding of - which the limit on the number of blocked streams did not prevent referencing - unacknowledged dynamic table entries. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - Version of the QUIC protocol used for this connection. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code returned when attempting to read from a QUIC - connection. The suffix specifies the condition/source of the read error. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The network error code returned when attempting to read on the current - network from a QUIC connection after handshake has been confirmed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the SETTINGS_QPACK_BLOCKED_STREAMS parameter received on an - HTTP/3 connection, if any. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of SETTINGS parameters received on an HTTP/3 connection, - incremented by one (the SETTINGS frame can be empty). - - - - - - Removed in M84. Use Net.QuicSession.ReceivedSettings.MaxHeaderListSize2 - instead. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the SETTINGS_MAX_HEADER_LIST_SIZE parameter received on an - HTTP/3 connection, if any. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the SETTINGS_MAX_HEADER_LIST_SIZE parameter received on an - HTTP/3 connection, if any. - - - - - - Removed in M84. Use Net.QuicSession.ReceivedSettings.MaxTableCapacity2. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the SETTINGS_QPACK_MAX_TABLE_CAPACITY parameter received on an - HTTP/3 connection, if any. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The value of the SETTINGS_QPACK_MAX_TABLE_CAPACITY parameter received on an - HTTP/3 connection, if any. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of reserved SETTINGS parameters (that is, with identifier in the - form 0x1f * N + 0x21 for a non-negative integer value of N) received on an - HTTP/3 connection, incremented by one (there might be zero reserved - identifiers). Defined at - https://quicwg.org/base-drafts/draft-ietf-quic-http.html#name-defined-settings-parameters. - These should not be treated specially on the receive side, because they are - sent to exercise the requirement that unknown identifiers are ignored. Here - an exception is made for logging only, to understand what kind of - identifiers are received. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if the QUIC REJ message received from the server contains a proof. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The length in bytes of a QUIC REJ message received from the server. - - - - - - Removed 11/2017. Use Net.QuicSession.RetryAfterWriteErrorCount2. - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of consecutive times a packet was retried after a write error. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of consecutive times a packet was retried after a write error, - using exponential backoff. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in a stream being reset by the client. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in a stream being reset by the server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of request for secure resources over QUIC sessions. True if the - session is secure, false if it is not. - - - - - zhongyi@google.com - src/net/quic/OWNERS - - When a SHLO handshake message is received, whether the client IP address and - port number in it differ from the local client IP address and port number. - In the comparison, the first address is the one in SHLO and the second - address is the client IP address. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The size in bytes of an encrypted QUIC packet sent to the peer at the - specified encryption level. - - - - - - Removed 03/2018 as crbug.com/817496 is resolved. - - zhongyi@chromium.org - - The number of times the connection sends connectivity probe to the peer. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The largest packet which the client received from the server during the - session. - - - - - - Removed in 9/19 because this metric was added to inspect a crash and the - crash had been fixed. - - renjietang@chromium.org - zhongyi@chromium.org - - True if at the time of Dns comparison between fresh resolution and stale - resolution, session_ is valid. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The final smoothed RTT observed during the life of a QUIC connection. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - True if fresh host lists contains stale host used in racing connection. - - - - - renjietang@chromium.org - zhongyi@chromium.org - src/net/quic/OWNERS - - The time a QUIC connection from invalid stale dns result takes to do Crypto - handshake. This starts on DoConnect and ends when the connection finishes. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - True if the stale host is used in racing connection. - - - - - Removed in 9/19 because this metric was added to inspect a crash and the - crash had been fixed. - - renjietang@chromium.org - zhongyi@chromium.org - - Logs places in code where stale host resolution doesn't have valid results. - For control purpose, it also logs when a valid stale result is used. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - Records when a STATELESS_RESET is received after a connectivity probing is - cancelled. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - When probing is cancelled, records whether a STATELESS_RESET is received. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the stream (and connection) being - closed by the client after the handshake was confirmed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The QUIC error code which resulted in the stream (and connection) being - closed by the client after the handshake was confirmed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Whether any of QUIC session's streams are flow control blocked when a PING - message is sent to server. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of stream frames received which were duplicates, out of every - 1000 stream frames received. Only for QUIC sessions which received at least - 100 packets. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The percentage of stream frames received which were duplicates. Only for - QUIC sessions which received at least 100 packets. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The percentage of stream frames received which were duplicates. Only for - QUIC sessions which received fewer than 100 packets. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of stream frames received which were duplicates, out of every - 1000 stream frames received. Only for QUIC sessions which received fewer - than 100 packets. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - If a QUIC connection timed out with open streams, this contains a count of - consecutive RTOs. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - If a QUIC connection timed out with open streams, this contains a count of - consecutive TLPs. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - If a QUIC connection timed out with open streams, this will be true when the - connection has unacked packets. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - If a QUIC connection timed out locally with open streams, this contains the - local port number for the connection. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - The time a QuicStreamFactory Job takes from host rersolution to connection - confirmation. - - - - - - Removed 04/2015. Tracked as Net.QuicSession.TooManyOpenStreams. - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if more than 100 streams are open when a new stream is activated. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - True if more than 100 streams are open when a new stream is activated. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - When a QUIC packet is sent at initial encryption that is smaller than the - minimum size, this records the size difference (minimum_size - - observed_size). - - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of truncated ACK frames received. - - - - - Removed 08/2016. - - dschinazi@chromium.org - src/net/quic/OWNERS - The number of truncated ACK frames sent. - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The number of undecryptable packets recevied by a QuicSession when the - sesesion is closed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The location in quic_client_session.cc where a session is unexpectedly not - going away. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The location in quic_client_session.cc where there were unexpected - observers. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The location in quic_client_session.cc where there were unexpected open - streams. - - - - - renjietang@chromium.org - zhongyi@chromium.org - src/net/quic/OWNERS - - The time a QUIC connection that will be confirmed takes for Crypto - handshake. The event starts on DoConnect, and ends when the connection - finishes. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Time spent verifying the signature and certificate chain. This is logged - whenever QUIC verifies the certificate chain and signature during crypto - handshake. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code returned when attempting to write to a QUIC - connection. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The network error code returned when attempting to write to a QUIC - connection after the handshake has been confirmed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The most recent network error code when attempting to write to a QUIC - connection when the network gets disconnected. - - - - - - Removed 06/2018 after https://crbug.com/818040 is fixed. - - wub@chromium.org - - Temporary histogram being used to investigate https://crbug.com/818040. - Records whether a connection is closed when an out of order queued packet is - about to be written. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - The reason QUIC packet writer needed to allocate a new buffer, rather than - the expected case of reusing its existing one. - - - - - nharper@chromium.org - src/net/quic/OWNERS - - Indicates whether a QUIC handshake attempted or used 0-RTT on the - connection, and if 0-RTT was not used, it provides reasons why. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - Indicates whether a QUIC handshake attempted or used 0-RTT on the - connection, and if 0-RTT was not used, it provides reasons why. Only records - connections with Google hosted servers. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - - Indicates whether a QUIC handshake attempted or used 0-RTT on the - connection, and if 0-RTT was not used, it provides reasons why. Only records - connections with non-Google servers. - - - - - renjietang@chromium.org - src/net/quic/OWNERS - Whether 0-RTT was successfully used in the connection. - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Records if a new connection on the alternate network is attempted when a - connection fails before handshake is confirmed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Connection type of the default network when the connection fails with - handshake not confirmed. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - A count of how often a user hits 1, 2, 3, 4 and 5 bad packet loss events for - port 443. Recorded whenever QUIC has bad packet loss (high packet loss on - multiple consecutive connections). - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Status of the connection on the non-default network when it finishes. A - connection may stay on the non-default network during the initial setup when - the platform's default network changes. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Records, for initial socket created for each new QUIC connection, whether - the bound network matched the default network tracked by QuicStreamFactory. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Rrecords reasons QUIC is disabled (for all ports), if sufficent recent - connections experience: public reset post crypto handshake, or timeouts with - streams open. QUIC is disabled until the next reboot of Chrome. Logged - during session close. - - - - - - Removed 11/2018. Replaced by MigrationBeforeHandshake2. - - zhongyi@chromium.org - - Status of the connection which is created for migration before handshake is - confirmed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Connection type of the alternate network when a connection is about to be - attempted when the original connection fails on the default network with - handshake not confirmed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Status of the connection which is created for migration before handshake is - confirmed. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - The network error code returned when the retried connection on the alternate - network before handshake fails. - - - - - zhongyi@chromium.org - src/net/quic/OWNERS - - Captures whether the default network has been changed when the new - connection succeeds on the "alternate" network. - - - - - - Depecated on 07/2020. Replaced by - Net.QuicConnectivityMonitor.NumAllDegradedSessions. - - zhongyi@chromium.org - src/net/quic/OWNERS - - The number of sessions that are degrading on network change. The suffix - specifies the network change. - - - - - - Deprecated on 07/2020. Replaced by - Net.QuicConnectivityMonitor.NumActiveQuicSessionsAtNetworkChange. - - zhongyi@chromium.org - rockot@chromium.org - src/net/quic/OWNERS - - The number of QUIC sessions when a network change is detected. - - - - - - Depecated on 07/2020. Replaced by - Net.QuicConnectivityMonitor.PercentageAllDegradedSessions. - - zhongyi@chromium.org - src/net/quic/OWNERS - - Of all the exisiting sessions, the percentage of sessions that detects - degrading on network change. The suffix specifies the network change. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Captures the maximum number of public resets post handshake that occurred - within a window of recent connections (default 20). Will help inform the - choice of threshold to disable QUIC for clients that experience pathalogical - errors. Logged during session close. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Recorded whenever QUIC is disabled for a port due to repeated lossy - connections (high packet loss on multiple consecutive connections). QUIC is - disabled until next reboot of Chrome. - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - Captures the maximum number of connection timeouts with streams open that - occurred within a window of recent connections (default 20). Will help - inform the choice of threshold to disable QUIC for clients that experience - pathalogical errors. Logged during session close. - - - - - - Removed 06/2016. No longer tracked. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Whether TSVIPCli DLL is loaded or not on windows when the socket is - configured. - - - - - - Removed 08/2016. No longer tracked. - - zhongyi@chromium.org - - Time duration from last packet sent to a new packet sent in QUIC connection. - - - - - vasilvv@chromium.org - src/net/quic/OWNERS - - The Google QUIC error code which resulted in the QuicTransport connection - being closed by the client. - - - - - vasilvv@chromium.org - src/net/quic/OWNERS - - The Google QUIC error code which resulted in the QuicTransport connection - being closed by the server. - - - - - vasilvv@chromium.org - src/net/quic/OWNERS - - The error code for cases when QuicTransport failed to establish a - connection. - - - - - vasilvv@chromium.org - src/net/quic/OWNERS - The code for QuicTransport errors. - - - - vasilvv@chromium.org - src/net/quic/OWNERS - - The state at which establishing a QuicTransport connection has failed. - - - - - vasilvv@chromium.org - src/net/quic/OWNERS - - The state at which the QuicTransportClient has been marked as failed. - - - - - - Removed in 2018. - - dschinazi@chromium.org - src/net/quic/OWNERS - - Logged whenever proof verification fails and if the failure occurred before - or after the crypto handshake is confirmed. - - - - - csharrison@chromium.org - rsleevi@chromium.org - - The total number of redirects encountered during processing a URLRequest. - This includes redirects generated by servers (for example, 302 Found) and - redirects generated internally (for example, HSTS redirects or error pages). - - - - - eustas@chromium.org - - True for redirect responses with unadvertised "Content-Encoding". - False for valid redirect responses. See http://crbug.com/714514 - - - - - - Removed 03/2015. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - True if the HTTP request was sent to a server which supports the TLS - renegotiation extension. - - - - - - Removed 06/2020. No longer tracked. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a single endpoint group in a - Report-To header once the header itself has been parsed. - - - - - - Removed 06/2020. No longer tracked. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a single endpoint in a Report-To - header once the header itself has been parsed. - - - - - - Removed 06/2020. No longer tracked. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a Report-To header. Once it is - parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints - within it. - - - - - - Removed June 2020 for cleanup. https://crbug.com/1089017 - - juliatuttle@chromium.org - - When Reporting successfully delivers a report, the number of unsuccessful - delivery attempts that preceded the successful one. - - - - - - Removed June 2020 for cleanup. https://crbug.com/1089017 - - juliatuttle@chromium.org - - The delivery latency of reports successfully delivered by Reporting. Starts - when the report is queued and finishes when the delivery attempt returns - successfully. - - - - - chlily@chromium.org - juliatuttle@chromium.org - - The outcome of Reporting trying to deliver a report, recorded when the - report is finally erased from memory. - - - - - - Removed June 2020 for cleanup. https://crbug.com/1089017 - - juliatuttle@chromium.org - - The error (net or HTTP) encountered by Reporting trying to upload one or - more reports to a single endpoint in a single request, recorded when the - upload attempt completes, if and only if the attempt failed with a net error - or an HTTP error other than 410 (which is specified to mean "remove - endpoint"). - - - - - - Removed June 2020 for cleanup. https://crbug.com/1089017 - - juliatuttle@chromium.org - - The outcome of Reporting trying to upload one or more reports to a single - endpoint in a single request, recorded when the upload attempt completes. - - - - - - Replaced by Net.RequestTime2 due to bug in original implementation. - - - The amount of time between request initiation and request completion for - success and various different errors. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - - The amount of time between request initiation and request completion for - success and various different errors. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - ERR_ABORTED when the request's scheme is http/s. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - ERR_ABORTED when the requests TotalReceivedBytes() > 0. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - ERR_ABORTED when the requests TotalReceivedBytes() = 0 and - received_response_content_length() = 0. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - ERR_ABORTED when the requests TotalReceivedBytes() = 0 and - received_response_content_length() > 0. - - - - - - Unused, so removed from Chromium as of 2017/8/31. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - ERR_ABORTED when the request's scheme is not http/s. - - - - - - Removed from Chromium as of 2018/7/2. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - success for main frame resources. - - - - - - Removed from Chromium as of 2018/7/2. - - csharrison@chromium.org - - The amount of time between request initiation and request completion for - success for non-main frame resources. - - - - - - Removed from Chromium as of 2018/7. - - mef@chromium.org - pauljensen@chromium.org - - The largest number of outstanding requests that are handled by the resource - dispatcher host for a single process. - - - - - - Removed from Chromium as of 2018/7. - - mef@chromium.org - pauljensen@chromium.org - - The largest number of outstanding requests that are handled by the resource - dispatcher host across all processes. - - - - - - Removed from code as of 03/2018. - - ksakamoto@chromium.org - - The largest number of outstanding requests handled by the resource - dispatcher host, during the last sample interval (60 seconds). Not logged if - there are no outstanding requests in the interval. This metric is temporary - for the Loading Dispatcher v0 (crbug.com/723233), and will be removed soon. - - - - - - Removed from code as of 11/2018. - - yhirano@chromium.org - toyoshim@chromium.org - - Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) - for HTTP "GET" requests. - - - - - - Removed from code as of 11/2018. - - yhirano@chromium.org - toyoshim@chromium.org - - Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) - for HTTP "POST" requests. - - - - - - Removed from code as of 11/2018. - - yhirano@chromium.org - toyoshim@chromium.org - - Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) - for HTTP "POST" requests whose url contains a port. - - - - - - Removed 10/2017. - - mmenke@chromium.org - maksim.sisov@intel.com - - Records how many times expected content size equals/less/more than size of - read body/buffer or content size is unkown. Recorded for each resource load. - - - - - - This experiment was turned down, see https://crbug.com/703188. - - tzik@chromium.org - - Counts whether the chunk inlining is applicable or not to a resource - loading. Counts the reason if inapplicable. - - - - - clamy@chromium.org - - When starting a cross-site navigation, the time between reading the headers - and body of the response. - - - - - - Removed 09/2020, no longer needed. - - tzik@chromium.org - - Time from the start to the end of receiving a response body. Recorded for - each resource load. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed from Chromium as of 2018/7/2. - - csharrison@chromium.org - - The time elapsed from URLRequest creation to when a ResourceLoader actually - calls Start on it. - - - - - - The code to record this histogram was removed November 2017. - - juliatuttle@chromium.org - - Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by - the browser process. - - - - - - The code to record this histogram was removed November 2017. - - juliatuttle@chromium.org - - Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by - a renderer process. - - - - - - The code to record this histogram was removed November 2017. - - juliatuttle@chromium.org - - Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by - a process not covered by one of the other ResponseSizeByProcess histograms. - - - - - - Removed Aug 2020. This was added to evaluate safety of proposed code - changes, and is no longer necessary as the necessary results were obtained. - - chlily@chromium.org - morlovich@chromium.org - - Logged whenever the RestrictedCookieManager sets a CanonicalCookie. True if - the domain of the cookie matches the domain of the URL, false otherwise. - - - - - morlovich@chromium.org - chlily@chromium.org - - Logged on any document.cookie or CookieStore API operation. True if the - browser-side site_for_cookies and the render-provided value match. - - - - - morlovich@chromium.org - chlily@chromium.org - - Logged on any document.cookie or CookieStore API operation. True if the - browser-side top_frame_origin and the render-provided value match. - - - - - chlily@chromium.org - morlovich@chromium.org - - The site engagement level of a frame that triggers the - CookieInsecureAndSameSiteNone warning, whether the cookie was actually - blocked or not. Recorded every time one or more cookies triggers the - warning. - - - - - chlily@chromium.org - morlovich@chromium.org - - The site engagement level of a frame that triggers the CookieNoSameSite - warning, whether the cookie was actually blocked or not. Recorded every time - one or more cookies triggers the warning. - - - - - - Removed as of 9/2017. - - mef@chromium.org - pauljensen@chromium.org - - Whether an idle socket is reused, timed out, or closed to make room for new - sockets. - - - - - - Removed as of 7/2017. - - mmenke@chromium.org - - Seconds a socket was idle before it was reused. Emitted upon reuse. Does not - record the times sockets were idle before first use. - - - - - - Removed as of 11/2016. - - mef@chromium.org - pauljensen@chromium.org - - Number of milliseconds an idle socket saved in connection establishment - because it is reused. - - - - - - Removed as of 06/2020. - - mmenke@chromium.org - Number of idle sockets when one of them was reused. - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - The time an already used socket sat idle before being used. - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The time an unused socket (all HTTP sockets, regardless of any proxy used) - sat idle before being used. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time a previously used socket sat idle before encountering a recoverable - socket IO error (connection abort/reset/close). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time an unused socket sat idle before encountering a recoverable socket - IO error (connection abort/reset/close). - - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Net error codes that socket initializations end with, including net::OK and - net::ERR_ABORTED. - - - - - - Replaced by Net.SocketUnchangeableReceiveBuffer 3/31/2014. - - - The size of a socket's receive buffer when the attempt to change it via - setsockopt failed. - - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - Time in milliseconds from initial RequestSocket() call until successfully - acquiring a connected socket. - - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - The time from the connection start to connection establish. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - The time waiting to be ready to start connecting. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - - Each bucket is the number of connection type of socket stream. - - - - - - Removed 2014-10-28. No longer generated. Replaced by Net.WebSocket.Duration. - - yhirano@chromium.org - ricea@chromium.org - The time a socket stream was open. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - - Each bucket is the number of protocol type on socket stream. - - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - Number of bytes on a socket stream. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - Number of reads on a socket stream. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - Number of bytes on a socket stream. - - - - - Removed 2014-10-28. No longer generated. No direct replacement. - - yhirano@chromium.org - ricea@chromium.org - Number of Write on a socket stream. - - - - - Removed as of 03/2015. - - Please list the metric's owners. Add more owner tags as needed. - - The counts of the type of sockets returned by the socket pools. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The size of a socket's receive buffer when the attempt to change it via - setsockopt failed. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The size of a socket's send buffer when the attempt to change it via - setsockopt failed. - - - - - - see SocketIdleTimeBeforeNextUse_ReusedSocket_SOCK - - Please list the metric's owners. Add more owner tags as needed. - - The time an already used SOCKS socket sat idle before being used. - - - - - - see SocketIdleTimeBeforeNextUse_UnusedSocket_SOCK - - Please list the metric's owners. Add more owner tags as needed. - The time an unused SOCKS socket sat idle before being used. - - - - - see SocketRequestTime_SOCK - - Please list the metric's owners. Add more owner tags as needed. - - Time from initial SOCKSClientSocketPool::RequestSocket() call until - successfully acquiring a connected SOCKS socket. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Time it takes to request a new (unused) SOCKS proxy socket. - - - - - see SocketType_SOCK - - Please list the metric's owners. Add more owner tags as needed. - - The counts of the type of sockets returned by the SOCKS pool. - - - - - - Replaced by Net.SpdyConnectionLatency_2 on 2014-10-21. - - dschinazi@chromium.org - src/net/OWNERS - Time from when the Connect() starts until it completes. - - - - - Removed 2018-02. - - dschinazi@chromium.org - src/net/OWNERS - Time from when the Connect() starts until it completes. - - - - dschinazi@chromium.org - src/net/OWNERS - - The counts of the flow control state of each frame (with stream and session - flow control on). - - - - - - The last protocol which would trigger this was deprecated in 2014 November. - This histogram is deprecated in 2016 January. - - dschinazi@chromium.org - src/net/OWNERS - - The counts of the flow control state of each frame (with stream flow control - on). - - - - - dschinazi@chromium.org - src/net/OWNERS - - The percent compression achieved when compressing HEADERS frames. - - - - - - Removed in 2020-03 once we confirmed the numbers looked as expected. - - dschinazi@chromium.org - - The highest number of capped frames queued in the SPDY write queue. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The compression percentage in received HPACK compressed header frames. - - - - - - Obsolete as HTTP/2 standard is finalized. - - dschinazi@chromium.org - src/net/OWNERS - - Frequencies of characters observed in request and response headers. - Temporarily being collected to inform the construction of an optimized - Huffman code for the HTTP/2 specification. Buckets are ASCII codes offset by - 1. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Status of checking if a SPDY domain can handle a IP match. If a match is - found, we successfully used the IP Pooling. If a match is not found, we - could have used IP Pooling, except the TLS Cert didn't match the IP-pooled - domain. - - - - - - Removed 2019-10-01. - - dschinazi@chromium.org - src/net/OWNERS - The RTT for SPDY's PING. - - - - - Removed 2016-05-26. - - dschinazi@chromium.org - src/net/OWNERS - The count of streams at each priority over Spdy sessions. - - - - dschinazi@chromium.org - src/net/OWNERS - - This histogram is recorded exactly once for every PUSH_PROMISE frame - received on an HTTP/2 connection, and tracks the fate of the pushed stream. - - - - - - Removed because it took up too much space and nobody used it. - - dschinazi@chromium.org - src/net/OWNERS - The number of bytes recevied per stream. - - - - dschinazi@chromium.org - src/net/OWNERS - - HTTP status codes received in HTTP/2 HEADERS frames. If a stream contains - one or more informational (1xx) response preceeding the main response, each - status code is logged separately. - - - - - - Removed because it took up too much space and nobody used it. - - dschinazi@chromium.org - src/net/OWNERS - The number of bytes sent per stream. - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - Total number of bytes recevied per session before closing session due to - EOF. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - Total number of bytes recevied per session before closing session due to an - error during read. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Net error codes when SpdySession was closed, doesn't inlcuding net::OK. - - - - - dschinazi@chromium.org - src/net/OWNERS - Socket connected status in SpdySession::CreateStream. - - - - zhongyi@chromium.org - src/net/OWNERS - - The number of bytes that is pushed but not used when the session is closed. - - - - - zhongyi@chromium.org - dschinazi@chromium.org - src/net/OWNERS - - The number of bytes that is pushed when the session is closed. - - - - - dschinazi@chromium.org - src/net/OWNERS - - Whether the server has advertised support for WebSockets over HTTP/2. - - - - - - Replaced by SpdySessionErrorDetails2 on 2013-04-19. - - dschinazi@chromium.org - src/net/OWNERS - - WARNING: r181910 added an enum value in the middle, so don't trust the - counts for values 9 and above for Chrome builds after that revision. - - The type of SPDY Protocol error encountered. - - - - - dschinazi@chromium.org - src/net/OWNERS - The type of SPDY Protocol error encountered. - - - - - Replaced by SpdySessionErrorDetails_Google2 on 2013-04-19. - - dschinazi@chromium.org - src/net/OWNERS - - The type of SPDY Protocol error encountered when talking to a google.com - server. - - - - - dschinazi@chromium.org - src/net/OWNERS - - WARNING: r181910 added an enum value in the middle, so don't trust the - counts for values 9 and above for Chrome builds after that revision. - - The type of SPDY Protocol error encountered when talking to a google.com - server. - - - - - dschinazi@chromium.org - src/net/OWNERS - The type of SPDY Session used when looking up a session. - - - - dschinazi@chromium.org - src/net/OWNERS - - Whether SpdySession::Get{Peer,Local}Address was called when the connection - had no socket. - - - - - - Removed 7/21/2014. No longer tracked. - - bengr@chromium.org - bolian@chromium.org - src/net/OWNERS - - The count of SPDY sessions using the data reduction proxy and the count of - other SPDY sessions. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - SpdySession::GetLocalAddress returned ERR_SOCKET_NOT_CONNECTED. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - SpdySession::GetPeerAddress returned ERR_SOCKET_NOT_CONNECTED. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - The count of SPDY Sessions with or without stalls. - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - The congestion window (in pkts) received at the end of a SpdySession. - - - - - - Removed 2016 July with removal of SPDY/3.1. - - dschinazi@chromium.org - src/net/OWNERS - - The congestion window (in pkts) sent at the beginning of a SpdySession. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - Percentage of sessions which received settings from the server. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - - The Download Retransmission Rate (%) received at the end of a SpdySession. - - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - The RTT received at the end of a SpdySession. - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - Percentage of sessions which sent settings to the server. - - - - - Removed because it took up too much space and nobody used it. - - dschinazi@chromium.org - src/net/OWNERS - - The time between receiving the first chunk and the last chunk of data on a - Spdy stream. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The number of pushed, but abandoned streams over a single session. - - - - - dschinazi@chromium.org - src/net/OWNERS - The number of streams issued over a single session. - - - - dschinazi@chromium.org - src/net/OWNERS - - The number of pushed, and used streams over a single session. - - - - - dschinazi@chromium.org - src/net/OWNERS - The number of push streams received over a single session. - - - - - Removed on 2016-10-10. - - dschinazi@chromium.org - src/net/OWNERS - The number of stream stalls per session. - - - - - Removed because it took up too much space and nobody used it. - - dschinazi@chromium.org - src/net/OWNERS - - The time of a Spdy stream. Measured from sending the first chunk to - receiving the last chunk of data. - - - - - - Removed because it took up too much space and nobody used it. - - dschinazi@chromium.org - src/net/OWNERS - - The time between sending the request and receiving the first chunk of data - on a Spdy stream. - - - - - - Removed on 2016-11-28, because SPDY/3 and, accordingly, SYN_STREAM frames - are no longer used. Compression values are now calculated slightly - differently. Replaced by Net.SpdyHeadersCompressionPercentage. - - dschinazi@chromium.org - src/net/OWNERS - - The percent compression achieved when compression SYN_STREAM frames. - - - - - - Removed on 2014-09-11, because the uploaded values were changing as - protocols were removed, therefore statistics couldn't be combined across - different builds. Replaced by Net.SpdyVersion2. - - dschinazi@chromium.org - src/net/OWNERS - - The SPDY protocol version that is used to talk to SPDY servers. - - - - - - Removed on 2016-02-01, because the incorrect bucket count caused data - corruption. Replaced by Net.SpdyVersion3. - - dschinazi@chromium.org - src/net/OWNERS - - The SPDY protocol version that is used to talk to SPDY servers. Logged every - time a SPDY session is initialized. - - - - - - Removed 2016 July with removal of SPDY/3.1. - - dschinazi@chromium.org - src/net/OWNERS - - The SPDY protocol version that is used to talk to SPDY servers. Logged every - time a SPDY session is initialized. - - - - - - Removed 2018-01 with the transition to a unified root list with OS fallback. - - rsleevi@chromium.org - - The results of comparing the built-in list of known Windows roots against - the CERT_AUTH_ROOT_SHA256_HASH_PROP_ID certificate property. Recorded for - each certificate verification on Windows. - - - - - - - agl@chromium.org - rsleevi@chromium.org - - The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS - connection in the socket pool where Connect() succeeds. - - - - - - - agl@chromium.org - - Counts of specific error codes returned when opening an SSL connection. - - - - - - Removed 7/21/2015. No longer tracked. - - bengr@chromium.org - - Counts of specific error codes returned when opening an SSL connection for - an endpoint which is eligible for fastradio padding. - - - - - - Removed 2018-03-07. No longer tracked. - - svaldez@chromium.org - - Counts of specific error codes returned when opening an SSL connection for - google.com and any subdomain of it. - - - - - svaldez@chromium.org - - Counts of specific error codes returned when opening an SSL connection for - an endpoint we are using in the initial TLS 1.3 deployment. - - - - - - Replaced by Net.SSL_Connection_Latency_2 on 2014-10-21. - - agl@chromium.org - Time from when the Connect() starts until it completes. - - - - - - agl@chromium.org - Time from when the Connect() starts until it completes. - - - - - Removed 7/21/2014. No longer tracked. - - bengr@chromium.org - bolian@chromium.org - - Time from when the Connect() starts until it completes when using the data - reduction proxy. This includes certificate retrieval and verification. - - - - - - Removed 2019-07-19. No longer tracked. - - agl@chromium.org - - Time from when the Connect() starts until it completes for full handshakes. - - - - - - Replaced by Net.SSL_Connection_Latency_Google2 on 2014-10-21. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it. - - - - - - Removed 2018-03-07. No longer tracked. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it. - - - - - - Removed 2018-03-07. No longer tracked. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it for full handshakes. - - - - - - Removed in 2011. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it. This only includes users in a 50% field trial that - disables revocation checking for certificate pinned sites. - - - - - - Removed 2018-03-07. No longer tracked. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it for resumption handshakes. - - - - - - Removed in 2011. - - agl@chromium.org - - Time from when the Connect() starts until it completes for google.com and - any subdomain of it. This only includes users not in a 50% field trail that - disables revocation for certificate pinned sites. - - - - - - Experiment ended 2019-10-01. - - agl@chromium.org - davidben@chromium.org - - Time from when the Connect() starts until it completes, but only for servers - that are part of the post-quantum experiment. - - - - - - Removed as of 2016-12-01. - - mab@chromium.org - - Time from when the Connect() starts until it completes (full handshakes - only), for a set of domains that we expect to always offer the experimental - post-quantum (CECPQ1) ciphersuites. - - - - - - Removed as of 2018-07-06. - - agl@chromium.org - - Time from when the Connect() starts until it completes for any server that - echos a dummy post-quantum padding extension. - - - - - - Removed 2019-07-19. No longer tracked. - - agl@chromium.org - - Time from when the Connect() starts until it completes for resumption - handshakes. - - - - - svaldez@chromium.org - - Time from when the Connect() starts until it completes for a set of domains - that we are using in the initial TLS 1.3 deployment. - - - - - - Removed as of 2016-12-01. - - mab@chromium.org - - For only browsers in the post-quantum (CECPQ1) ciphersuite experiment, - counts the full TLS handshakes where CECPQ1 was, or was not, negotiated on - hosts where we expect it to be negotiated. - - - - - - Removed as of 01/2016. - - eranm@chromium.org - rsleevi@chromium.org - - The state of compliance with Certificate Transparency presence requirements - for each EV certificate. An EV certificate could be non-compliant (in which - case it loses the EV status), comply through inclusion in the EV whitelist - or have the required number of Signed Certificate Timestamps. This metric - will gauge adoption rate of Certificate Transparency and will help identify - when the EV whitelist is no longer needed. Emitted during every SSL - connection establishment, but only if the client is checking compliance with - Certificate Transparency requirements (currently guarded by a Finch - experiment). - - - - - - Removed 06/2017 with the deprecation of the EV certificate whitelist after - all certificates expired. - - eranm@chromium.org - rsleevi@chromium.org - - Whether an EV certificate is present in the Certificate Transparency - whitelist. Emitted once for every EV certificate encountered (during SSL - connection establishment), but only if the client has a valid whitelist. - - - - - - Removed 06/2017 with the deprecation of distinct EV and !EV CT policies. - - eranm@chromium.org - rsleevi@chromium.org - - The state of compliance with Certificate Transparency presence requirements - for each EV certificate. An EV certificate could be non-compliant (in which - case it loses the EV status), comply through inclusion in the EV whitelist - or comply with the CT certificate policy. This metric will gauge adoption - rate of Certificate Transparency and will help identify when the EV - whitelist is no longer needed. Emitted during every SSL connection - establishment. - - - - - - Removed 06/2017 with the deprecation of the EV certificate whitelist after - all certificates expired. - - eranm@chromium.org - rsleevi@chromium.org - - Whether the client holds a valid EV Certificates whitelist or not. Only - emitted when an EV cert that is not compliant with the Certificate - Transparency requirement is encountered. This histogram is intended to be - short-lived and help determine if EV certificates are considered - non-compliant because they are not whitelisted or if the client does not - hold a valid instance of the whitelist. - - - - - - Removed September 2016. - - agl@chromium.org - rsleevi@chromium.org - sigbjorn@opera.com - - Bit strength of the key exchange for DHE. Recorded for each SSL/TLS - connection in the socket pool where Connect() succeeds. - - - - - - - agl@chromium.org - rsleevi@chromium.org - sigbjorn@opera.com - - The curve used for key exchange for ECDHE. Recorded for each SSL/TLS - connection in the socket pool where Connect() succeeds. - - - - - - Removed May 2016. - - agl@chromium.org - rsleevi@chromium.org - sigbjorn@opera.com - - Bit strength of the key exchange for RSA. Recorded for each SSL/TLS - connection in the socket pool where Connect() succeeds. See |SSL_SESSION|'s - key_exchange_info for more information. - - - - - - Removed on 01/2016. Only ever measured blacklisted Comodo serials, not any - of the other blacklisted certificates and keys. - - agl@chromium.org - - Counts the number of times that users have hit blacklisted certificates. The - indexes match up to the indexes in - net/base/x509_certificate.cc:IsBlacklisted. The details of the certificates - in question is confidential. - - - - - rsleevi@chromium.org - Time to complete a certificate verification (success case). - - - - rsleevi@chromium.org - Time to complete a certificate verification (error case). - - - - - Removed in 08/2017. - - davidben@chromium.org - - For each HTTPS connection to the TLS 1.3 experiment server set, whether the - TLS 1.3 anti-downgrade mechanism would have fired. This is to measure the - effects of non-compliant middleboxes on this otherwise safe security - feature. The numbers are only valid while the TLS 1.3 experiment set deploys - a TLS 1.3 draft version compatible with the corresponding Chrome version and - implement the our draft anti-downgrade signal. See - https://crbug.com/boringssl/226. - - - - - - Removed June 2016. - - davidben@chromium.org - - For each successful HTTPS request which used the TLS version fallback, the - error code of the last failed attempt. - - - - - - Removed June 2016. - - davidben@chromium.org - - For each successful HTTPS request which used the TLS version fallback, the - type of handshake failure of the last failed attempt. - - - - - davidben@chromium.org - src/net/OWNERS - - For each successful TLS handshake, what kind of handshake was used. This - metric distinguishes TLS 1.2 (or earlier) and TLS 1.3 as they have very - different resumption and round-trip behaviors. It also distinguishes full - handshakes, resumption, 0-RTT, and False Start. - - - - - davidben@chromium.org - svaldez@chromium.org - src/net/OWNERS - - Indicates whether a TLS 1.3 connection with 0-RTT enabled ended up using - 0-RTT or not, and why; this includes reasons such as the server declining to - resume the connection and the client not having enough tickets available. - - - - - - Removed in 2011. - - Please list the metric's owners. Add more owner tags as needed. - Time to complete a DNS lookup for a DNS CAA record. - - - - - Removed in 2011. - - Please list the metric's owners. Add more owner tags as needed. - - Time that we would have wasted had we waited for a CAA lookup in order to - validate a certificate. - - - - - - Removed in 2012. - - Please list the metric's owners. Add more owner tags as needed. - Time to complete a speculative certificate verification. - - - - cthomp@chromium.org - - Counts when the SSLKEYLOGFILE environment variable or --ssl-key-log-file - command-line flag are set, and when they enable the SSLKeyLogger feature. - - - - - davidben@chromium.org - src/net/OWNERS - - For each TLS connection, whether it needed the legacy crypto fallback and a - classification as to why. See https://crbug.com/658905 and - https://crbug.com/691888. Note some connections are reported as sending - SHA-1 certificates because, although SHA-1 is no longer accepted in - certificates, servers may send unused certificates in the handshake. Some - such servers additionally match their certificate chains against the - ClientHello. These servers require the client advertise legacy algorithms - despite not actually using them. - - - - - dschinazi@chromium.org - src/net/OWNERS - - For each TLS handshake, whether ALPN was negotiated; and if so, the - negotiated protocol. - - - - - - Removed in March 2016. - - davidben@chromium.org - - The cipher suite used when the corresponding operation on an SSLClientSocket - fails with ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when - https://crbug.com/593963 is resolved. - - - - - - Removed in March 2016. - - davidben@chromium.org - - The internal, version-specific BoringSSL error reason reported when the - corresponding operation on an SSLClientSocket fails with - ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when - https://crbug.com/593963 is resolved. - - - - - - Superseded by Net.SSLNegotiatedAlpnProtocol in 2016 August. - - dschinazi@chromium.org - src/net/OWNERS - - TLS extension used to negotiate protocol (ALPN or NPN); in case of NPN, - whether the protocol is indeed supported by both the client and the server - or is a fallback because of no overlap; and the negotiated protocol itself. - - - - - - Removed in January 2018. - - davidben@chromium.org - svaldez@chromium.org - - The number of bytes, excluding the record header, of each TLS record read. - - - - - - Removed 2020-06. - - davidben@chromium.org - - For each TLS connection which uses a known root, an RSA key, and TLS 1.2 or - below, what the result of checking the RSA key usage would have been. - - - - - davidben@chromium.org - - For each TLS connection which uses a unknown root, an RSA key, and TLS 1.2 - or below, what the result of checking the RSA key usage would have been. - - - - - - Removed in August 2019 - - davidben@chromium.org - - For each attempted SSL renegotiation (non-initial handshake), whether the - server supported the renegotiation_info extension (RFC 5746). - - - - - - Replaced by Net.SSLSignatureAlgorithm. - - davidben@chromium.org - - For each SSL connection with a full handshake using a DHE- or ECDHE-based - key exchange, the hash function used in the ServerKeyExchange signature. - - - - - - Removed on 2017-10-02. - - nharper@chromium.org - - For each SSL connection where we resume a session and negotiate HTTP/2, the - simulated minimum number of sessions retained per host it would have - required with TLS 1.3 single-use sessions. See https://crbug.com/631988. - - - - - - Removed on 2015-11-10. - - davidben@chromium.org - - For each SSL connection that resumed a session, whether the session was - resumed at the same version it was established at. This is only recorded in - BoringSSL ports. - - - - - - - davidben@chromium.org - src/net/OWNERS - - For each SSL connection with a full handshake using a DHE- or ECDHE-based - key exchange, the signature algorithm used to authenticate the peer. In TLS - 1.2, this is the signature on the ServerKeyExchange message. (Note: Although - the ECDSA values specify a curve, the curve is only enforced in TLS 1.3.) - - - - - - Removed 2020-07-28. - - svaldez@chromium.org - davidben@chromium.org - - For each HTTPS connection, whether the TLS 1.3 anti-downgrade mechanism - would have fired. This is only recorded if enforcement has been disabled and - includes samples from non-1.3 servers. See https://crbug.com/boringssl/226. - - - - - - Removed 2020-07-28. - - svaldez@chromium.org - davidben@chromium.org - - For each HTTPS connection to the TLS 1.3 experiment server set, whether the - TLS 1.3 anti-downgrade mechanism would have fired. This is only recorded if - enforcement has been disabled and is only valid while the TLS 1.3 experiment - set deploys the final TLS 1.3 version. See https://crbug.com/boringssl/226. - - - - - - Removed 2020-07-28. - - svaldez@chromium.org - davidben@chromium.org - - For each HTTPS connection that triggered the TLS 1.3 anti-downgrade - mechanism, the key exchange and whether the root was known. - - - - - - Removed 2020-07-28. - - svaldez@chromium.org - davidben@chromium.org - - For each HTTPS connection to the TLS 1.3 experiment server set that - triggered the TLS 1.3 anti-downgrade mechanism, the key exchange and whether - the root was known. - - - - - - Removed 2020-03. - - davidben@chromium.org - vasilvv@chromium.org - - For each session added to TLS session cache that uses TLS 1.3 or later, the - lifetime of the session. Note that this incorporates both the - server-supplied timeout and any local restrictions imposed by the client - itself. - - - - - - Removed 2020-03. - - davidben@chromium.org - vasilvv@chromium.org - - For each TLS 1.3 session successfully retrieved from the session cache, the - time between the session was added and the time it was retrieved. - - - - - - Removed on 2014-08-20. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times that we have performed SSLv3 fallback and found a TLS - renegotiation patched server. - - - - - - Removed in 2012. - - Please list the metric's owners. Add more owner tags as needed. - Was a speculative certificate verification used? - - - - - Removed in 2012. - - Please list the metric's owners. Add more owner tags as needed. - Time saved by a speculative certificate vertification. - - - - - - davidben@chromium.org - - The SSL/TLS version that was negotiated. Recorded for each SSL/TLS - connection in the socket pool where Connect() succeeds. - - - - - davidben@chromium.org - rsleevi@chromium.org - - The SSL/TLS version that was negotiated to a Google host. Recorded for each - appplicable SSL/TLS connection in the socket pool where Connect() succeeds. - Google servers all support TLS 1.2, so any occurrences of TLS 1.0 or TLS 1.1 - indicate an outdated insecure TLS MITM proxy, such as some antivirus - configurations. TLS 1.0 and 1.1 are deprecated, so record these to see how - prevalent they are. See https://crbug.com/896013. - - - - - - Removed April 2018. - - davidben@chromium.org - svaldez@chromium.org - - For each detected SSL version interference against a server in the initial - TLS 1.3 deployment, details on how the initial connection failed. - - - - - - Removed April 2019. - - davidben@chromium.org - - For each detected SSL version interference, what network error the original - failed connection reported. - - - - - - Removed April 2019. - - davidben@chromium.org - - For each SSL version interference probe, what network error triggered it. - Probes are only triggered for a small set of network errors. - - - - - - Removed in 07/2017. - - palmer@chromium.org - - True if a DNS name contains only characters for which - |net::IsValidLabelCharacter| returns true. Used to see if we can deprecate - and remove support for arbitrary bytes in DNS names. This histogram is - recorded after DNS resolution has completed successfully. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Number of idle sockets when the Connect() succeeded. - - - - - - mmenke@chromium.org - - Time from when the Connect() starts until it completes. Only times under 10 - minutes are logged. - - - - - mgersh@chromium.org - - Time from when the Connect() starts until it completes when the network - address only contains IPv4 addresses. Only times under 10 minutes are - logged. - - - - - mgersh@chromium.org - - Time from when the Connect() starts until it completes when the IPv4 - fallback connection won the race against IPv6. Only times under 10 minutes - are logged. - - - - - mgersh@chromium.org - - Time from when the Connect() starts until it completes when we race an IPv6 - connection against an IPv4 connection with a 300ms delay. Only times under - 10 minutes are logged. - - - - - mgersh@chromium.org - - Time from when the Connect() starts until it completes when the network - address only contains IPv6 addresses. Only times under 10 minutes are - logged. - - - - - eroman@chromium.org - src/net/OWNERS - - Time taken when failed to establish a TCP connection to an individual - endpoint. This includes the case when the attempt was aborted by a higher - layer (likely because it took too long). - - - - - eroman@chromium.org - src/net/OWNERS - - Time taken to successfully establish a TCP connection to an individual - endpoint. - - - - - eroman@chromium.org - src/net/OWNERS - - Time taken when failed to establish a TCP connection to an individual - endpoint, expressed as a multiple of the transport RTT. This includes the - case when the attempt was aborted by a higher layer (likely because it took - too long). This may have fewer samples than Net.TcpConnectAttempt.Latency.* - in cases where the network quality estimation was unknown. - - - - - eroman@chromium.org - src/net/OWNERS - - Time taken to successfully establish a TCP connection to an individual - endpoint, expressed as a multiple of the transport RTT. This may have fewer - samples than Net.TcpConnectAttempt.Latency.* in cases where the network - quality estimation was unknown. - - - - - - Removed 02/2019, as fast open support has been removed. - - dschinazi@chromium.org - src/net/OWNERS - - For sockets for which a TCP Fast Open protocol might be used, the result of - trying to use it. - - - - - - see SocketIdleTimeBeforeNextUse_ReusedSocket_TCPforSOCKS - - Please list the metric's owners. Add more owner tags as needed. - - The time an already used TCP socket sat idle before being used for a SOCKS - request. - - - - - - see SocketIdleTimeBeforeNextUse_UnusedSocket_TCPforSOCKS - - Please list the metric's owners. Add more owner tags as needed. - - The time an unused TCP socket sat idle before being used for a SOCKS - request. - - - - - - see SocketRequestTime_TCPforSOCKS - - Please list the metric's owners. Add more owner tags as needed. - - Time from initial SOCKSClientSocketPool::RequestSocket() call until - successfully acquiring a connected TCP socket. - - - - - - see SocketType_TCPforSOCKS - - Please list the metric's owners. Add more owner tags as needed. - - The counts of the type of sockets returned by the TCP pool used by the SOCKS - pool. - - - - - bmcquade@chromium.org - - The kernel's estimated TCP round trip time. Recorded for each TCP socket, at - the time it is disconnected. - - - - - - Was only used for HTTP[S] connections, renamed to Net.HTTPSocketType. - - Please list the metric's owners. Add more owner tags as needed. - The counts of the type of TCP socket returned. - - - - - Experiment complete, code removed. - - davidben@chromium.org - - The time it took to do an IO to UI round-trip in the - ThreadHopResourceThrottle. This is part of an experiment to determine the - feasibility to moving some high-level resource loading checks to the UI - thread. - - - - - - Token Binding was removed in Q4 2018 and this histogram was removed in - 3/2019. - - nharper@chromium.org - Time spent creating a Token-Binding header. - - - - - Token Binding was removed in Q4 2018 and this histogram was removed in - 3/2019. - - nharper@chromium.org - - Logs on each request that is sent on a connection where Channel ID was sent - whether the key that would be used for Token Binding matches the key used - for Channel ID. - - - - - - Token Binding was removed in Q4 2018 and this histogram was removed in - 3/2019. - - nharper@chromium.org - - For each request to accounts.google.com on a connection where Channel ID was - sent, this logs whether the Cookie store and the Channel ID store were - ephemeral or persistent. - - - - - - Token Binding was removed in Q4 2018 and this histogram was removed in - 3/2019. - - nharper@chromium.org - - The number of secure HTTP requests broken down by support for Token Binding, - indicating if Token Binding was negotiated and supported by both client and - server, or why it wasn't if not. - - - - - - Discontinued as of 4/12/09 - - Please list the metric's owners. Add more owner tags as needed. - - Effective bandwidth in KByte/Second of transactions logged to - Transaction_Latency histogram. Note that only samples durations greater than - zero ms, and less than 1 hour are tallied into this ratio. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the when the network transaction is requested, until the first - byte of the header is received. - - - - - - Replaced by Net.Transaction_Connected_New_b. - - Please list the metric's owners. Add more owner tags as needed. - - When a new connection is established, the time from the when the network - transaction is requested, until the first byte of the header is received. - Only items under 10 minutes are logged. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - When a new connection is established, the time from the when the network - transaction is requested, until the first byte of the header is received. - - - - - - Replaced by Net.Transaction_Connected. - - Please list the metric's owners. Add more owner tags as needed. - - Time from the when the network transaction is requested, until the first - byte of the header is received. Only items under 10 minutes are logged. - - - - - - Replaced by Net.Transaction_Latency_b. - - Please list the metric's owners. Add more owner tags as needed. - - Time from first byte sent until last byte received by the new network stack. - Only items under 1 hour are logged. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Time from first byte sent until last byte received by the new network stack. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a network transaction is requested until last byte received - by the new network stack. - - - - - - Removed as of 11/2014. - - Please list the metric's owners. Add more owner tags as needed. - - When an existing TCP/IP connection is NOT reused, the time from when a - network transaction is requested until last byte received by the new network - stack. - - - - - - Replaced by Net.Transaction_Latency_Total_New_Connection. - - Please list the metric's owners. Add more owner tags as needed. - - When an existing TCP/IP connection is NOT reused, the time from when a - network transaction is requested until last byte received by the new network - stack. Only items under 10 minutes are logged. - - - - - - Replaced by Net.Transaction_Latency_Total. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a network transaction is requested until last byte received - by the new network stack. Only items under 10 minutes are logged. - - - - - - Replaced by Net.Transaction_Latency. - - Please list the metric's owners. Add more owner tags as needed. - - Time from first byte sent until last byte received by the new network stack. - Only items under 10 minutes are logged. - - - - - - Removed a long time ago. - - Please list the metric's owners. Add more owner tags as needed. - - Time from first byte sent until last byte received with old WinHTTP network - stack. Only items under 1 hour are logged. - - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time an already used TCP socket sat idle before being used (either for - direct or non-socks use). - - - - - - Please list the metric's owners. Add more owner tags as needed. - - The time an unused TCP socket sat idle before being used (either for direct - or non-socks use). - - - - - - Please list the metric's owners. Add more owner tags as needed. - - Time from initial ClientSocketPool::RequestSocket() call until successfully - acquiring a connected socket (either for direct or non-socks use). - - - - - - Please list the metric's owners. Add more owner tags as needed. - - The counts of the type of sockets returned by the TCP pool (either for - direct or non-socks use). - - - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - The //net status codes for resource requests that had started Trust Tokens - operations. This captures the reasons why requests with Trust Tokens - operations fail and might help debug a surfeit of "TypeError: failed to - fetch" observed in live testing. - - - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - Time taken to execute a Trust Tokens operation's outbound Begin half (see - network::TrustTokenRequestHelper). - - - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - Time time to taken a Trust Tokens operation's inbound Finalize half (see - network::TrustTokenRequestHelper). - - - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - Time between finishing a Trust Tokens Tokens operation's outbound Begin half - and beginning its inbound Finalize half (see - network::TrustTokenRequestHelper). - - - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - Time elapsed from the beginning of a Trust Tokens operation's outbound Begin - half to the end of its inbound Finalize half (see - network::TrustTokenRequestHelper), when the operation succeeded overall. - - - - - davidvc@chromium.org - privacy-sandbox-dev@chromium.org - - For a Trust Tokens operation associated with a subresource request, stores - whether the browser believed the frame had the Feature Policy feature - necessary for executing the operation. - - - - - - Removed as of 10/2017. - - Please list the metric's owners. Add more owner tags as needed. - Posix error code from call to bind() UDP socket. - - - - - Removed as of 10/2017. - - Please list the metric's owners. Add more owner tags as needed. - Windows error code from call to bind() UDP socket. - - - - mgersh@chromium.org - Chromium error code from call to RandomBind() UDP socket. - - - - dschinazi@chromium.org - src/net/OWNERS - The time spent in closesocket call in UDPSocketWin::Close. - - - - - - davidvc@chromium.org - kaustubhag@chromium.org - - Records for each URLRequest whether its referrer contains more information - than just its origin (this is the case exactly when it has at least one - character apart from a leading slash in its path, e.g. http://example.com/a - but not http://example.com/ nor http://example.com). - - - - - - - davidvc@chromium.org - kaustubhag@chromium.org - - Records the distribution of referrer policies provided with outgoing - URLRequests, and whether or not the requests were cross-origin. - - - - - estark@chromium.org - - Records the usage of the Referrer-Policy header on redirect responses. This - histogram is recorded on each HTTP redirect response, with the value true if - a Referrer-Policy header was present and false otherwise. - - - - - - Removed 6/23/2014. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - True if a URLRequest's referrer is empty or valid when set. - - - - - Removed 1/1/2018. No longer tracked. - - - Indicates the number of URLRequests that are handed out by a - URLRequestContext and are not yet destroyed. - - - - - - Removed 1/1/2018. No longer tracked. - - - Records the annotation type of the URLRequest that is handed out by a - URLRequestContext when Net.URLRequestContext.OutstandingRequests is - recorded. - - - - - - Removed 07/2017, not necessary to determine deprecation for invalid DNS - names. - - palmer@chromium.org - - True if a DNS name contains only characters for which - |net::IsValidLabelCharacter| returns true. Used to see if we can deprecate - and remove support for arbitrary bytes in DNS names. This histogram is - recorded when converting dotted DNS names into DNS query form, in - preparation for issuing a DNS request. - - - - - ricea@chromium.org - yhirano@chromium.org - yoichio@chromium.org - - Records the status code with which WebSockets are closed. Logged once for - every successfully opened WebSocket. Includes codes "No Status - Rcvd" and "Abnormal Closure" which are never sent over the - wire but generated internally. See RFC6455 section 7.4.1 for the meanings of - the codes. Newer codes are documented at - https://www.iana.org/assignments/websocket/websocket.xhtml#close-code-number. - Codes that have not been standardised are bucketed to save storage space. - Used to determine if changes in framing change the error rate. - - - - - - Removed in March 2020. - - rajendrant@chromium.org - bengr@chromium.org - - Records the downstream data use of WebSockets. Logged on every read - operation in the WebSocket. - - - - - - Removed in March 2020. - - rajendrant@chromium.org - bengr@chromium.org - - Records the upstream data use of WebSockets. Logged on every write operation - in the WebSocket. - - - - - - Removed in June 2019. - - yhirano@chromium.org - ricea@chromium.org - - Count the number of WebSockets that accepted permessage-deflate extension - for each context take over mode. Used by the new Chromium-based WebSocket - implementation. - - - - - - Removed in June 2019. - - yhirano@chromium.org - ricea@chromium.org - - The time from a WebSocket is successfully opened until it's closed. Used to - study how WebSockets are used. - - - - - - - yhirano@chromium.org - ricea@chromium.org - - Positive net error codes that WebSockets end with, including OK and ABORTED. - - - - - - Removed 03/2018, replaced by Net.WebSocket.HandshakeResult2. - - yhirano@chromium.org - ricea@chromium.org - - Results of WebSocket handshakes. Use this histogram as a baseline for - investigating feature usage counters. - - - - - - - yhirano@chromium.org - ricea@chromium.org - src/net/OWNERS - - Results of WebSocket handshakes, including information whether the handshake - happened over HTTP/2. Use this histogram as a baseline for investigating - feature usage counters. - - - - - - - yhirano@chromium.org - ricea@chromium.org - All HTTP status codes seen during WebSocket handshakes. - - - - - Removed 2020-04. - - mattreynolds@chromium.org - deviceapi-team@google.com - - The number of Wi-fi adapters on the computer. Because the histogram is - logged each time Chrome performs a Wi-fi scan, it's better to see results in - the "user count" view. - - - - - - Removed 2020-04. - - mattreynolds@chromium.org - deviceapi-team@google.com - The time that a request to Location Based Services takes. - - - - - Removed 2020-04. - - mattreynolds@chromium.org - deviceapi-team@google.com - The time that a Wi-fi scan takes. - - - - - Removed 02/2019. - - eroman@chromium.org - - Duration of time that a failing WPAD QuickCheck takes. WPAD QuickCheck does - a name lookup for "wpad" and times out quickly to fail fast when - there's no WPAD server on the network. - - - - - - Removed 02/2019. - - eroman@chromium.org - - Duration of time that a successful WPAD QuickCheck takes. WPAD QuickCheck - does a name lookup for "wpad" and times out quickly to fail fast - when there's no WPAD server on the network. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the first pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the first pipeline connectivity response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the first pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the second pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the second pipeline connectivity - response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the second pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the third pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the third pipeline connectivity response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the third pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the fourth pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the fourth pipeline connectivity - response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the fourth pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the fifth pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the fifth pipeline connectivity response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the fifth pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The network error, if any, of the stats pipeline connectivity request. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The HTTP response code, if any, of the stats pipeline connectivity response. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - The result of the stats pipeline connectivity request. - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - True if all requests received by the pipelining test server were HTTP/1.1. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - True if the non-pipelined canary request sent immediately before the - pipelining test requests succeeded. Note that if this fails, the rest of the - NetConnectivity.Pipeline.* stats are not collected. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - - The maximum depth of pipelined requests received by the test server. - - - - - - Removed 05/2014, related field trial already long expired. - - Please list the metric's owners. Add more owner tags as needed. - True if the entire pipeline connectivity trial passed. - - - - - Removed 6/25/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP at port 6121 as - rapidly as possible, just after successfully sending an UMA upload. Each - packet was numbered, as was its ACK sent back by Google. If no packets (of - the 21) were ever ACKed, then the port is assumed to be blocked, and no data - is recorded in this histogram. If the port is not blocked, then this - histogram shows the number of echo responses received from the first - - - - - - Removed 6/25/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP at port 6121 as - rapidly as possible, just after successfully sending an UMA upload. Each - packet was numbered, as was its ACK sent back by Google. This histogram - records, for each packet number, how often we received an ACK for that - packet. - - - - - - Removed 6/25/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP at port 6121 as - rapidly as possible, just after successfully sending an UMA upload. If no - packets (of the 21) were ever ACKed, then the port is assumed to be blocked. - The histogram shows if we ever got an ACK for a packet in our series of 21. - - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 100 bytes of TCP data unsuccessfully. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 1K bytes of TCP data successfully. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Status for TCP protocol for echoing - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - Status for echoing 100 bytes of TCP data. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - Status for echoing 1K bytes of TCP data. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for TCP protocol for echoing - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 100 bytes of TCP data successfully. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 1K bytes of TCP data successfully. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 100 bytes of UDP data unsuccessfully. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 1K bytes of UDP data successfully. - - - - - Removed 6/25/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome sends 4 UDP packets in a row to test to see if there is a - probabalistic dependency in packet loss for consecutive packets. We record a - bit vector of packets received, where the least significant bit is a 1 if - the first packet was received, etc. For example, if packets 1 and 3 are - received, but packets 2 and 4 are lost, then we'd record a sample of binary - 0101B, or 5. - - - - - - Removed 6/25/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome sends 6 UDP packets in a row to test to see if there is a - probabalistic dependency in packet loss for consecutive packets. We record a - bit vector of packets received, where the least significant bit is a 1 if - the first packet was received, etc. For example, if all packets other than - packet 2 and 4 are responded to, then we'd have a sample (in binary) of - 110101B, or 53. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Status for UDP protocol for echoing - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - Status for echoing 100 bytes of UDP data. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - Status for echoing 1K bytes of UDP data. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for UDP protocol for echoing - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 100 bytes of UDP data successfully. - - - - - Removed 4/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - The RTT for echoing 1k bytes of UDP data successfully. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - This histogram records how many packets (out of 6 attempted) were sent via - UDP as rapidly as possible, just after successfully sending an UMA upload. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome sends 6 UDP packets in a row to test to see if there is a - probabalistic dependency in packet loss for consecutive packets. We record a - bit vector of packets received, where the least significant bit is a 1 if - the first packet was received, etc. For example, if all packets other than - packet 2 and 4 are responded to, then we'd have a sample (in binary) of - 110101B, or 53. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP as rapidly as - possible, just after successfully sending an UMA upload. Each packet was - numbered, as was its ACK sent back by Google. If no packets (of the 21) were - ever ACKed, then the port is assumed to be blocked, and no data is recorded - in this histogram. If the port is not blocked, then this histogram shows the - number of echo responses received from the first - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP as rapidly as - possible, just after successfully sending an UMA upload. Each packet was - numbered, as was its ACK sent back by Google. This histogram records, for - each packet number, how often we received an ACK for that packet. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP as rapidly as - possible, just after successfully sending an UMA upload. If no packets (of - the 21) were ever ACKed, then the port is assumed to be blocked. The - histogram shows if we ever got an ACK for a packet in our series of 21. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - This histogram records how many packets (out of 21 attempted) were sent via - UDP as rapidly as possible, just after successfully sending an UMA upload. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, 21 packets were sent to Google via UDP on port 443 or - 6121. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 9/2012. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - This histogram records how many packets (out of 6 attempted) were sent via - UDP as rapidly as possible, just after successfully sending an UMA upload. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, a few packets were sent from Google to clients via UDP - on port 443 or 80 to perform net connectivity test. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - In this experiment, a few packets were sent from Google to clients via UDP - on port 443 or 80 to perform net connectivity test. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Next NetConnectivity5 experiment weren't started because there is an - outstading pending write. - - - - - stevenjb@chromium.org - benchan@chromium.org - The time the Gobi modem takes to complete activation. - - - - stevenjb@chromium.org - benchan@chromium.org - - The time the Gobi modem takes to connect to the cellular network. - - - - - stevenjb@chromium.org - benchan@chromium.org - - The time the Gobi modem takes to disconnect from the cellular network. - - - - - stevenjb@chromium.org - benchan@chromium.org - Number of attempts taken to install Gobi firmware. - - - - stevenjb@chromium.org - benchan@chromium.org - The time it takes to install Gobi firmware. - - - - stevenjb@chromium.org - benchan@chromium.org - - The time the Gobi modem takes to register on the cellular network. - - - - - stevenjb@chromium.org - benchan@chromium.org - Errors experienced during Gobi device powerup. - - - - azeemarshad@chromium.org - cros-system-services-networking@google.com - - Tracks the Cellular network activation state when the primary user logs-in - to the device. - - - - - azeemarshad@chromium.org - cros-system-services-networking@google.com - - Tracks when cellular network is connected and when cellular network is - disconnected without explicit user action. - - - - - azeemarshad@chromium.org - cros-system-services-networking@google.com - - Tracks the amount fo time taken between when cellular device starts and - finishes connecting. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network metric sampling the time spent using Cellular to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join a 3G/Cellular - network and configure Layer 3 state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that a - 3G/Cellular network is online after configuring Layer 3 state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that a - 3G/Cellular network is in a captive portal after configuring Layer 3 state. - - - - - azeemarshad@chromium.org - cros-system-services-networking@google.com - - Tracks the number of times a cellular network is connected as the only - network, or with other network or not connected at all. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Chrome OS cellular usage API request status codes. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network metric sampling the time spent using Ethernet to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join a wired - Ethernet network and configure Layer 3 state (typically acquire a DHCP - lease). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that an - Ethernet network is online after configuring Layer 3 state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that an - Ethernet network is in a captive portal after configuring Layer 3 state. - - - - - - Removed 8/2015. - - cschuet@chromium.org - - Chrome OS metric counting the number of network configurations that - contained a NSS nickname identifying a CA certificate, which triggered the - migration to PEM encoding. This metric doesn't consider whether the - migration was successful but once a migration was successful the nickname is - removed. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Chrome OS connection manager service errors seen. - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of cellular network - flakes. A network flake occurs when the signal strength goes below detection - level for a short duration. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the total amount of time spent - from the start of the first auto-connect request until when the cellular - modem successfully connects to the network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of auto-connect - tries that were attempted before the cellular modem successfully connected - to the network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the presence of a Cellular device in - the system. A sample is emitted once every 3 minutes. - - - - - - Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. - - benchan@chromium.org - - Chrome OS network metric that tracks the number of DHCP option failures - encountered by Shill. This indicates that Shill is using minimal DHCP - options due to suspected MTU issues on the return path from the DHCP server - back to the client. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks whether the cellular network was - disconnected due to an error or was explicitly disconnected by the user. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS cellular network metric that tracks the number of drops based on - the network technology. - - - - - - Removed since Chrome OS build 10010.0.0 and superceded by - Network.Shill.Cellular.ExpiredLeaseLengthSeconds2 due to change in number of - buckets (crosreview.com/557297, crosreview.com/703679). - - benchan@chromium.org - - Chrome OS network performance metric that tracks the length of a lease for a - cellular network at the time it expired without the DHCP client being able - to renew it. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the length of a lease for a - cellular network at the time it expired without the DHCP client being able - to renew it. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the presence of complete IPv6 - configuration at the time when cellular connection is established. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the types of IP configuration used for - establishing cellular connections. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS cellular network metric that tracks the number of out-of-credits - detected based on the cause that triggered the out-of-credits. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of portal detection - attempts per pass for a cellular network. This includes failure, timeout and - successful attempts. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the total number of portal - detection attempts performed for a cellular network between the Connected - and Online state. This includes failure, timeout and successful attempts. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the result of portal detections - for a cellular network. - - - - - kuabhs@chromium.org - cros-network-metrics@google.com - - Chrome OS connection manager service errors for cellular interface. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the signal strength (0-100) of the - cellular modem before it dropped from the network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the time spent using cellular to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to join a cellular - network and configure Layer 3 state. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to connect a cellular - modem. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to disable a cellular - modem. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to enable a cellular - modem. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to initialize a - cellular modem. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that a - cellular network is online after configuring Layer 3 state. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that a - cellular network is in a captive portal after configuring Layer 3 state. - - - - - matthewmwang@chromium.org - hugobenichi@chromium.org - - Chrome OS network performance metric sampling the time to determine that a - cellular network is in a captive portal with a valid redirect URL after - configuring Layer 3 state. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to scan a cellular - network and register a modem. - - - - - stevenjb@chromium.org - benchan@chromium.org - - Chrome OS network metric that tracks the connectivity issue diagnosed by the - ConnectionDiagnostics class in Shill. This metric is logged each time a - ConnectionDiagnostics object completes its diagnostics actions and reports - the results to its caller. - - - - - stevenjb@chromium.org - benchan@chromium.org - - Chrome OS cellular network metric that tracks the number of corrupted - profiles encountered by Shill. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS device time on line in the previous 24-hour sample period. - "On line" means shill believes the device is on the internet. The - shill state is sampled every 5 minutes. The start of each 24-hour period is - the end of the previous period, unless the device is inactive at that time - (suspended or off), in which case it is the time of the next - resume/power-on. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS fraction of daily cumulative time on a cellular connection when - both cellular and WiFi adaptors are available. Each sample is the ratio of - the corresponding DailyChosenTimeOnLine.{Cellular,Any} samples. Reported - only when both a cellular and a WiFi adaptor are present (independently of - whether they would both be able to connect). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS fraction of daily cumulative time on a WiFi connection when both - cellular and WiFi adaptors are available. Each sample is the ratio of the - corresponding DailyChosenTimeOnLine.{Cellular,Any} samples. Reported only - when both a cellular and a WiFi adaptor are present (independently of - whether they would both be able to connect). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS daily cumulative time on line when both cellular and WiFi adaptors - are available. Reported only when both kinds of adaptor are present - (independently of whether they would both be able to connect). Each sample - contains the total on-line time in the 24-hour slot following the previous - sample. The time granularity is 5 minutes. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS daily cumulative time on a cellular connection when both cellular - and WiFi adaptors are available. Reported only when both kinds of adaptor - are present (independently of whether they would both be able to connect). - Each sample contains the total on-line time in the 24-hour slot following - the previous sample. The time granularity is 5 minutes. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS daily cumulative time on a WiFi connection when both cellular and - WiFi adaptors are available. Reported only when both kinds of adaptor are - present (independently of whether they would both be able to connect). Each - sample contains the total on-line time in the 24-hour slot following the - previous sample. The time granularity is 5 minutes. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of dark resume - actions that successfully complete or fail when shill suspends. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes dark resume actions to complete when shill suspends. - - - - - - Removed 01/2015. Migrated to Network.Shill.DarkResumeActionsTimeTaken. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes dark resume actions to complete when shill suspends. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of times a dark resume scan is - retried in a single dark resume. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks whether dark resume scan retries led to - the system suspending from dark resume in a connected state. This metric is - only recorded in dark resumes when at least one dark resume scan retry was - launched. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the connection status of - the device. A sample is emitted once every 3 minutes. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the network device removed events for - each device type. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the MTU value proposed by the - DHCP server. A sample is emitted each time the DHCP client completes - negotiation with a server. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the current state of the DHCP - client. A sample is emitted each time the DHCP client state changes. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the number of DHCP option failures - encountered by Shill for each network technology. This indicates that Shill - is using minimal DHCP options due to suspected MTU issues on the return path - from the DHCP server back to the client. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the presence of an Ethernet device in - the system. A sample is emitted once every 3 minutes. - - - - - - Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. - - benchan@chromium.org - - Chrome OS network metric that tracks the number of DHCP option failures - encountered by Shill. This indicates that Shill is using minimal DHCP - options due to suspected MTU issues on the return path from the DHCP server - back to the client. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks whether the Ethernet network was - disconnected due to an error or was explicitly disconnected by the user. - - - - - - Removed since Chrome OS build 10010.0.0 and superceded by - Network.Shill.Ethernet.ExpiredLeaseLengthSeconds2 due to change in number of - buckets (crosreview.com/557297, crosreview.com/703679). - - benchan@chromium.org - - Chrome OS network performance metric that tracks the length of a lease for - an Ethernet network at the time it expired without the DHCP client being - able to renew it. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the length of a lease for - an Ethernet network at the time it expired without the DHCP client being - able to renew it. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of LinkMonitor - broadcast errors that were accrued on an Ethernet network at the time that - the link was declaired to be failed. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS metric that signals the type of failure the LinkMonitor - encountered which caused it to stop monitoring an Ethernet network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of milliseconds - between an ARP request and a received reply on an Ethernet network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of seconds from - the start of the LinkMonitor until failure on an Ethernet network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of LinkMonitor - unicast errors that were accrued on an Ethernet network at the time that the - link was declaired to be failed. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of portal detection - attempts per pass for an Ethernet network. This includes failure, timeout - and successful attempts. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the total number of portal - detection attempts performed for an Ethernet network between the Connected - and Online state. This includes failure, timeout and successful attempts. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the result of portal detections - for an Ethernet network. - - - - - kuabhs@chromium.org - cros-network-metrics@google.com - - Chrome OS connection manager service errors for ethernet interface. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the time spent using Ethernet to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to join a wired - Ethernet network and configure Layer 3 state (typically acquire a DHCP - lease). - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to initialize an - Ethernet device. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that an - Ethernet network is online after configuring Layer 3 state. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that an - Ethernet network is in a captive portal after configuring Layer 3 state. - - - - - matthewmwang@chromium.org - hugobenichi@chromium.org - - Chrome OS network performance metric sampling the time to determine that an - Ethernet network is in a captive portal with a valid redirect URL after - configuring Layer 3 state. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS fraction of monthly cumulative time on a cellular connection when - both cellular and WiFi adaptors are available. Each sample is the ratio of - the corresponding MonthlyChosenTimeOnLine.{Cellular,Any} samples. Reported - only when both a cellular and a WiFi adaptor are present (independently of - whether they would both be able to connect). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS fraction of monthly cumulative time on a WiFi connection when both - cellular and WiFi adaptors are available. Each sample is the ratio of the - corresponding MonthlyChosenTimeOnLine.{Cellular,Any} samples. Reported only - when both a cellular and a WiFi adaptor are present (independently of - whether they would both be able to connect). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS monthly cumulative time on line when both cellular and WiFi - adaptors are available. Reported only when both kinds of adaptor are present - (independently of whether they would both be able to connect). Each sample - contains the total on-line time in the 30-day slot following the previous - sample. The time granularity is 5 minutes. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS monthly cumulative time on a cellular connection when both - cellular and WiFi adaptors are available. Reported only when both kinds of - adaptor are present (independently of whether they would both be able to - connect). Each sample contains the total on-line time in the 30-day slot - following the previous sample. The time granularity is 5 minutes. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS monthly cumulative time on a WiFi connection when both cellular - and WiFi adaptors are available. Reported only when both kinds of adaptor - are present (independently of whether they would both be able to connect). - Each sample contains the total on-line time in the 30-day slot following the - previous sample. The time granularity is 5 minutes. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric recording portal detection results of both the HTTP - and HTTPS probes. This is recorded every time a portal detection trial - finishes. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the MTU value provided by the - upstream PPP peer. A sample is emitted each time the client successfully - negotiates an MTU value via PPP. - - - - - - Removed March 2019. - - mortonm@chromium.org - - Chrome OS metric signifying whether a system is running shill in a sandbox - or not. This is controlled through a VariationsService flag, but requires - 1-2 reboots to take affect. This metric will help us ensure that shill is - being run with sandboxing enabled/disabled at the proportion that we expect. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS connection manager service errors across all technologies. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of services that are connected - to the currently connected network. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of suspend actions - that successfully complete or fail when shill suspends. - - - - - - Removed 03/2020. Migrated to Network.Shill.SuspendActionTimeTaken. - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes suspend actions to complete when shill suspends. Note that this was a - misspelling of the metric that is really in use by Shill. No histogram - should ever have included this entry. - - - - - - Removed 01/2015. Migrated to Network.Shill.SuspendActionsTimeTaken. - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes suspend actions to complete when shill suspends. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes suspend actions to complete when shill suspends. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of termination - actions that successfully complete or fail when shill terminates. Previously - deprecated in 10/2012 and brought back in 10/2014. - - - - - - Removed 10/2014. Migrated to Network.Shill.SuspendActionResult. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the number of termination - actions that successfully complete or fail when shill suspends. - - - - - - Removed 10/2014. Migrated to Network.Shill.TerminationActionResult. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the number of termination - actions that successfully complete or fail when shill terminates. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes termination actions to complete when shill terminates. - - - - - - Removed 01/2015. Migrated to Network.Shill.TerminationActionsTimeTaken. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes termination actions to complete when shill terminates. - - - - - - Removed 10/2014. Migrated to Network.Shill.SuspendActionTime. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes termination actions to complete when shill suspends. - - - - - - Removed 10/2014. Migrated to Network.Shill.TerminationActionTime. - - benchan@chromium.org - - Chrome OS network diagnostic metric sampling the time in milliseconds it - takes termination actions to complete when shill terminates. - - - - - stevenjb@chromium.org - benchan@chromium.org - cros-network-metrics@google.com - - Chrome OS network stability metric sampling the time in seconds between the - networking going online to going offline. Offline events due to device - shutdown or suspend are ignored (along with the online time before that - offline event). - - - - - stevenjb@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the number of user-initiated events. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled on each successful VPN connection - that tracks the VPN connection type. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled on each successful VPN connection - that tracks the remote authentication method. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the time spent using VPN to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). A sample is emitted - every time the system transitions from primary connectivity through a VPN to - some other type of connectivity. The value of the sample is the time delta - in seconds from the instant the system transitioned to VPN connectivity. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on a VPN network (typically acquire a DHCP lease). - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that a - VPN connection is online after configuring Layer 3 state. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled on each successful VPN connection - that tracks the user authentication method. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of Wireless Access Points that - support the 802.11k standard, sampled on successful connections to an AP. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of Wireless Access Points that - support the 802.11r standard, sampled on successful connections to an AP. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of Wireless Access Points that - support the 802.11v BSS Max Idle Period feature, sampled on successful - connections to an AP. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of Wireless Access Points that - support the 802.11v BSS Transition feature, sampled on successful - connections to an AP. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of Wireless Access Points that - support the 802.11v DMS feature, sampled on successful connections to an AP. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled when an AP switches channels. Shows - the old frequency band and the new frequency band. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Reason code reported when the AP disconnects - a WiFi connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Broad category of reason AP disconnected a - WiFi connection. - - - - - - Removed as of 05/2019. - - kirtika@chromium.org - - Chrome OS network usage metric. The AP mode setting for each successful WiFi - connection. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Status code reported when an 802.11 - association fails. Note that not all disconnects are caused by an assoc - failure, and so this metric shold not be correlated with the DisconnectType - metrics. - - - - - akhouderchah@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Status code reported when an 802.11 - authentication fails. Note that not all disconnects are caused by an auth - failure, and so this metric should not be correlated with the DisconnectType - metrics. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of wifi services available for - auto-connect when auto-connect is initiated for wifi device. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of BSSes (endpoints) available - for the currently connecting wifi service. - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric recording BSS Transition Management statuses. This - is recorded every time a BSS Transition Management request is received from - a wireless access point. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. The channel used for each successful WiFi - connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Reason code reported when the client - disconnects a WiFi connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. Broad category of reason client disconnected - a WiFi connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks whether any unmatched scan results are - received during dark resume cycles. An unmatched scan result is a set of - scan results received by shill in response to a scan request that was not - sent directly by shill in the same dark resume cycle. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the wake reason for dark resume. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the presence of a WiFi device in the - system. A sample is emitted once every 3 minutes. - - - - - - Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. - - kirtika@chromium.org - - Chrome OS network metric that tracks the number of DHCP option failures - encountered by Shill. This indicates that Shill is using minimal DHCP - options due to suspected MTU issues on the return path from the DHCP server - back to the client. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks whether an 802.11 wireless - network was disconnected due to an error or was explicitly disconnected by - the user. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled on each successful 802.1x wireless - connection that tracks the configured inner authentication method. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric sampled on each successful 802.1x wireless - connection that tracks the configured outer authentication method. - - - - - - Removed since Chrome OS build 10010.0.0 and superceded by - Network.Shill.Wifi.ExpiredLeaseLengthSeconds2 due to change in number of - buckets (crosreview.com/557297, crosreview.com/703679). - - kirtika@chromium.org - - Chrome OS network performance metric that tracks the length of a lease for a - WiFi network at the time it expired without the DHCP client being able to - renew it. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the length of a lease for a - WiFi network at the time it expired without the DHCP client being able to - renew it. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the result of the fallback - DNS test. The fallback DNS test is performed when portal detection failed - due to DNS failure. - - - - - - Removed 06/2020. - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS metric sampling the number of different frequencies (i.e. - channels) on which a device has connected to a WiFi network. This value is - recorded every time a WiFi connection is established - (WPASupplicant::kInterfaceStateCompleted). Note that the word - "Ever" in the metric name is misleading. Chrome OS actually ages - out historical information, currently after 3 weeks. - - - - - tnagel@chromium.org - cros-network-metrics@google.com - cros-privacy-core@google.com - - Chrome OS network metric tracking WiFi networks configured with hidden SSID. - The metric includes networks from system and user profile and it's recorded - each time a user configuration profile is loaded, such as when a user logs - in. The fraction of non-zero buckets should roughly correspond to the - fraction of devices that are trying to connect to hidden SSIDs at any given - point in time. - - - - - kglund@google.com - cros-network-metrics@google.com - - Chrome OS network metric that tracks the Hotspot 2.0 support of access - points that devices connect to. Results are recorded every time a device - connects to an access point. The metric records either the HS20 version the - AP supports, or that the AP does not support HS20. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the presence of complete IPv6 - configuration at the time when WiFi connection is established. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of LinkMonitor - broadcast errors that were accrued on an 802.11 wireless network at the time - that the link was declared to be failed. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS metric that signals the type of failure the LinkMonitor - encountered which caused it to stop monitoring an 802.11 wireless network. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of milliseconds - between an ARP request and a received reply on an 802.11 wireless network. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of seconds from - the start of the LinkMonitor until failure on an 802.11 wireless network. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the number of LinkMonitor - unicast errors that were accrued on an 802.11 wireless network at the time - that the link was declaired to be failed. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks the types of IP configuration used for - establishing WiFi connections. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the network problems - encountered by TrafficMonitor after WiFi connection is established. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. The channel type used for each successful - WiFi connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of portal detection - attempts per pass for an 802.11 wireless network. This includes failure, - timeout and successful attempts. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the total number of portal - detection attempts performed for an 802.11 wireless network between the - Connected and Online state. This includes failure, timeout and successful - attempts. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the result of portal detections - for an 802.11 wireless network. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks which country the WiFi regulatory - domain is set to. Recorded every time a WiFi regulatory domain change is - triggered or determined initially (Shill startup). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of 802.11 wireless - networks known by the connection manager at the time a configuration profile - has been loaded. A configuration profile is loaded at each system startup, - and when a user logs in. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of 802.11 wireless networks - configured from the system configuration profile. This metric is sampled - each time a user configuration profile is loaded, such as when a user logs - in. - - It might be surprising to have a system configuration profile metric sampled - when a user configuration profile is loaded. But this ensures that we have - equal numbers of samples for system and user configuration profiles. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the number of 802.11 wireless networks - configured from a user configuration profile. This metric is sampled each - time a user configuration profile is loaded, such as when a user logs in. - - - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric recording roam successes or failures. This is - recorded every time a client succeeds or fails to roam from one wireless - access point to another. - - - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric recording roam time in milliseconds. This is - recorded every time a successful roam from one wireless access point to - another occurs. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric describing, for a WiFi scan attempt, what - scan method is used and whether it ends in a connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric describing, for a WiFi scan attempt, how many - milliseconds were spent waiting to talk to the kernel/drivers. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric. The security setting for each successful - WiFi connection. - - - - - kuabhs@chromium.org - cros-network-metrics@google.com - - Chrome OS connection manager service errors for wifi interface. - - - - - - - matthewmwang@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric recording session length in milliseconds. This is - recorded every time an uninterrupted session with a wireless access point is - terminated. - - - - - silberst@google.com - cros-network-metrics@google.com - - Chrome OS network metric indicating the negative of the dBm received signal - strength recorded at the time of a WiFi disconnect. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric indicating the negative of the dBm received signal - strength recorded at the time a successful WiFi connection started. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric indicating the maximal length of any stopped - mac80211 transmit queue. The metric is reported when a queue-status check - determines that at least one transmit queue is stopped, and has more than a - threshold number of frames queued. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric indicating the reason that mac80211 transmit queues - were stopped. The metric is reported when a queue-status check determines - that at least one queue is stopped, and has more than a threshold number of - frames queued. - - One measurement is reported per stop reason, per queue-status check. Reasons - that apply to multiple queues are reported only once per queue-status check. - Reasons that only apply to queues that have a below-threshold number of - frames are skipped. - - Note that, because we may report multiple stop reasons for a single - queue-status check, this histogram is not suitable for determining the - number of times a queue-status check found that the queues were stopped. To - determine that number, use the count of - Network.Shill.WiFi.StoppedTxQueueLength reports. - - - - - briannorris@chromium.org - chromeos-kernel-wifi@google.com - cros-network-metrics@google.com - - Number of attempts required for a WiFi device to be established with WPA - supplicant (shill retries on failure). This metric is reported either on - success, reporting the number of attempts performed; or after repeated - failures (currently 6), we give up and report an artificial maximum (10). - - Thus, a value of 10 means we aborted after repeated failures. Values of 1 to - 6 represent successful connections on the first to sixth try. Values of 7 to - 9 (which should not occur) represent successful connections after seven or - more attempts (success reports are capped at 9). - - - - - semenzato@chromium.org - briannorris@chromium.org - cros-network-metrics@google.com - - Time spent in suspended state, on a resume, for the case when wake on wifi - is disabled (WoWOff), and after resume, the NIC is found to be already - connected. - - - - - semenzato@chromium.org - briannorris@chromium.org - cros-network-metrics@google.com - - Time spent in suspended state, on a resume, for the case when wake on wifi - is enabled (WoWOff), and after resume, the NIC is found to be disconnected. - - - - - semenzato@chromium.org - briannorris@chromium.org - cros-network-metrics@google.com - - Time spent in suspended state, on a resume, for the case when wake on wifi - is enabled (WoWOn), and after resume, the NIC is found to be already - connected. - - - - - semenzato@chromium.org - briannorris@chromium.org - cros-network-metrics@google.com - - Time spent in suspended state, on a resume, for the case when wake on wifi - is enabled (WoWOn), and after resume, the NIC is found to be disconnected. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the time spent using WiFi to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time from the resume event - to the time when an 802.11 wireless network has configured its Layer 3 - state. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on an 802.11 wireless network (typically acquire a DHCP lease). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to connect to a WiFi - Basic Service Set (which consists of the access point and associated - stations on a particular WiFi channel for a specific network). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to initialize an - 802.11 wireless device. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to join (associate - plus authenticate) an 802.11 wireless network. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that an - 802.11 wireless network is online after configuring Layer 3 state. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that an - 802.11 wireless network is in a captive portal after configuring Layer 3 - state. - - - - - matthewmwang@chromium.org - hugobenichi@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to determine that an - 802.11 wireless network is in a captive portal with a valid redirect URL - after configuring Layer 3 state. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time to scan WiFi until a - connection is found. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric sampling the time between the beginning - of a WiFi scan (if the scan includes both a progressive scan and a full - scan, the TimeToScanAndConnect starts with the first scan of the series) and - the completion of a successful connection. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the transmit bitrate in - Mbps for the wifi device when it is connected to a network. The bitrate is - reported once every minute after the wifi connection is established. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric sampling the signal strength (0-100) of the wifi - network when it becomes unreliable (experiencing multiple link failures in a - short period of time). - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the reasons of failed - user-initiated WiFi connection attempts. The result of the user-initiated - WiFi connection attempts are being tracked by - Network.Shill.WiFi.UserInitiatedConnectionResult. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network performance metric that tracks the result of - user-initiated WiFi connection attempts. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network diagnostic metric sampling the number of times NIC wake on - WiFi settings verification succeeds or fails in shill. This metric is - recorded every time wake on WiFi settings are requested and verified after - the NIC is programmed with wake on WiFi settings. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks the wake on WiFi features that - are enabled in shill. Recorded once every 10 minutes. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks whether wake on WiFi was disabled - during a period of system suspension because of too many dark resume wakes. - This metric is only recorded for system suspends where wake on WiFi - functionality has been programmed into the NIC. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network metric that tracks whether a wake reason was received - during dark resume before executing WakeOnWiFi::OnDarkResume. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Chrome OS network usage metric that tracks the WiFi connection status after - waking from suspend, both when wake on WiFi is enabled and disabled. - Recorded 1 second after waking from suspend. - - - - - - Wimax support has been dropped from shill since M76. - - benchan@chromium.org - - Chrome OS network metric that tracks the presence of a WiMax device in the - system. A sample is emitted once every 3 minutes. - - - - - - Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. - - benchan@chromium.org - - Chrome OS network metric that tracks the number of DHCP option failures - encountered by Shill. This indicates that Shill is using minimal DHCP - options due to suspected MTU issues on the return path from the DHCP server - back to the client. - - - - - - Removed since Chrome OS build 10010.0.0 and superceded by - Network.Shill.Wimax.ExpiredLeaseLengthSeconds2 due to change in number of - buckets (crosreview.com/557297, crosreview.com/703679). - - benchan@chromium.org - - Chrome OS network performance metric that tracks the length of a lease for a - WiMax network at the time it expired without the DHCP client being able to - renew it. - - - - - - Wimax support has been dropped from shill since M76. - - benchan@chromium.org - - Chrome OS network performance metric that tracks the length of a lease for a - WiMax network at the time it expired without the DHCP client being able to - renew it. - - - - - - Wimax support has been dropped from shill since M76. - - benchan@chromium.org - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on a WiMax network (typically acquire a DHCP lease). - - - - - - Wimax support has been dropped from shill since M76. - - benchan@chromium.org - - Chrome OS network performance metric sampling the time to initialize a WiMax - device. - - - - - - Wimax support has been dropped from shill since M76. - - benchan@chromium.org - - Chrome OS network performance metric sampling the time to determine that a - WiMax network is online after configuring Layer 3 state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join a 3G/Cellular - network and configure Layer 3 state. Note this metric is deprecated; see - Network.Cellular.TimeToConfig. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join a wired - Ethernet network and configure Layer 3 state (typically acquire a DHCP - lease). Note this metric is deprecated; see Network.Ethernet.TimeToConfig. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on an 802.11 wireless network (typically acquire a DHCP lease). Note - this metric is deprecated; see Network.Wifi.TimeToConfig. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network stability metric sampling the time in seconds between the - networking going online to going offline. Offline events due to device - shutdown or suspend are ignored (along with the online time before that - offline event). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join (associate - plus authenticate) an 802.11 wireless network. Note this metric is - deprecated; see Network.Wifi.TimeToJoin. - - - - - yzshen@chromium.org - - How much, in bytes, of the response body has been read from network by a - URLLoader before it pauses reading, when it receives a - PauseReadingBodyFromNet() call. If there are multiple calls to - PauseReadingBodyFromNet(), only a single value is recorded for the last - call. This histogram is recorded by URLLoader implementations that fetch - from network. When SafeBrowsing indicates that a resource may be unsafe and - therefore a more time-consuming check is required to classify it, reading - response body from network is paused in order to reduce the chance of - writing unsafe contents into cache. This histogram is useful to evaluate how - much data is cached during this window. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on an 802.11 wireless network (typically acquire a DHCP lease). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Network metric reporting the download speed test results run at setup time. - Recorded at least once per day. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Chrome OS network usage metric. The channel used for each successful WiFi - connection. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Chrome OS network usage metric. The channel type used for each successful - WiFi connection. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Network metric reporting the average round trip time to the WiFi gateway. - Recorded at least once per day. - - - - - Please list the metric's owners. Add more owner tags as needed. - cast-analytics@google.com - - Chrome OS network usage metric. The security setting for each successful - WiFi connection. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the failure reason for all connection attempts, - manual or automatic, to Wi-Fi networks which were added from Chrome Sync. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the result of all connection attempts, manual - or automatic, to Wi-Fi networks which were added from Chrome Sync. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the failure reason for manual connection - attempts to Wi-Fi networks which were added from Chrome Sync. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the result of manual connection attempts to - Wi-Fi networks which were added from Chrome Sync. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the total number of Wi-Fi networks which are - stored in Chrome Sync for the active user. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the failure reason for update attempts to - synced Wi-Fi networks. This includes create/modify/remove operations. Each - retry is counted seperately. - - - - - jonmann@chromium.org - better-together-dev@google.com - - Chrome OS metric that tracks the result of update attempts to synced Wi-Fi - networks. This includes create/modify/remove operations. failures are only - recorded after all retries have been exhausted. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network metric sampling the time spent using WiFi to transport - data. These data are mostly useful when summed and compared to TimeOnline - for other network technologies (e.g. WiFi vs Cellular). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time from the resume event - to the time when an 802.11 wireless network has configured its Layer 3 - state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to configure Layer 3 - state on an 802.11 wireless network (typically acquire a DHCP lease). - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to join (associate - plus authenticate) an 802.11 wireless network. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that an - 802.11 wireless network is online after configuring Layer 3 state. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS network performance metric sampling the time to determine that an - 802.11 wireless network is in a captive portal after configuring Layer 3 - state. - - - - - stevenjb@chromium.org - - Number of shared remembered (preferred) networks on Chrome OS. Updated any - time the network list changes. - - - - - stevenjb@chromium.org - - Number of private remembered (preferred) networks on Chrome OS. Updated any - time the network list changes. - - - - - stevenjb@chromium.org - - Number of visible (in-range) networks on Chrome OS. Updated any time the - network list changes. - - - - - mmenke@chromium.org - - Whether a request going through the network service has one of a number of - concerning headers added by the caller when the request is redirected. - Entries are only recorded when headers are actually added during a redirect. - We want to figure out if we can ban any of these headers from being set - outside the network service. For comparison with - NetworkService.ConcerningRequestHeader.HeaderAddedOnRedirect. - - - - - mmenke@chromium.org - - Tracks how often each of a number of concerning headers are added by the - caller when a network service request is redirected. We want to figure out - if we can ban any of these headers from being set outside the network - service. To get meaningful percentages of requests, need to compare with - NetworkService.ConcerningRequestHeader.AddedOnRedirect. - - - - - mmenke@chromium.org - - Tracks how often each of a number of concerning headers are set by the - caller when a network service request is started. We want to figure out if - we can ban any of these headers from being set outside the network service. - To get meaningful percentages of requests, need to compare with - NetworkService.ConcerningRequestHeader.PresentOnStart. - - - - - mmenke@chromium.org - - Whether a request going through the network service has one of a number of - concerning headers set by the caller when the request starts. We want to - figure out if we can ban any of these headers from being set outside the - network service. For comparison with - NetworkService.ConcerningRequestHeader.HeadersPresentOnStart. - - - - - mkwst@chromium.org - yhirano@chromium.org - - Records the result of the Cross-Origin Resource Policy check, with - cross-origin-embedder-policy-report-only involvement. - - - - - mkwst@chromium.org - yhirano@chromium.org - - Records the result of the Cross-Origin Resource Policy check. - - - - - qingsi@chromium.org - jeroendb@chromium.org - - Errors that the mDNS responder service encounters during its lifetime. These - may be system errors in mDNS socket creation and IO, or user-induced by - invalid IP addresses. - - - - - jam@chromium.org - - How long the browser waits for the network process to exit at shutdown. - - - - - cduvall@chromium.org - cmumford@chromium.org - - How long it takes the network service to respond to the first mojo call. - This will be used to debug http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - How long it takes the network service to respond to the first mojo call - after a network service crash. This will be used to debug - http://crbug.com/934317. - - - - - cduvall@chromium.org - cmumford@chromium.org - - How long it takes the network service to respond to the first mojo call on - startup. This will be used to debug http://crbug.com/934317. - - - - - lukasza@chromium.org - creis@chromium.org - jam@chromium.org - - Whether the request origin (i.e. - network::ResourceRequest::request_initiator) matches the origin that the - browser process expected when creating the URLLoaderFactory (i.e. whether it - matches URLLoaderFactoryParams::request_initiator_origin_lock). - - Recorded when a request is started (i.e. at the time of constructing - network::URLLoader). - - - - - jam@chromium.org - juncai@chromium.org - mmenke@chromium.org - - Whether the Origin header is the same as the request origin in the - URLLoaderFactory when it creates a URLLoader. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker observes a tick clock and a wall clock to determine - whether a timestamp retrieved from the network in the past can be used to - compute a current timestamp. When the tick clock and wall clock diverge from - each other, the NetworkTimeTracker must discard the network timestamp - because it has no way to compute a reliable current timestamp. Whenever the - NetworkTimeTracker discards a network timestamp due to the tick and wall - clocks diverging, this histogram records the difference of the tick clock's - delta minus the wall clock's delta since the network timestamp was - retrieved. For cases where the the tick clock delta is bigger than the wall - clock delta, see NetworkTimeTracker.ClockDivergence.Positive. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker observes a tick clock and a wall clock to determine - whether a timestamp retrieved from the network in the past can be used to - compute a current timestamp. When the tick clock and wall clock diverge from - each other, the NetworkTimeTracker must discard the network timestamp - because it has no way to compute a reliable current timestamp. Whenever the - NetworkTimeTracker discards a network timestamp due to the tick and wall - clocks diverging, this histogram records the difference of the tick clock's - delta minus the wall clock's delta since the network timestamp was - retrieved. For cases where the the wall clock delta is bigger than the tick - clock delta, see NetworkTimeTracker.ClockDivergence.Negative. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker makes periodic queries to obtain a secure timestamp over - the network. This histogram records the delta between each secure timestamp - and the previous one, to measure how often time queries are made. The first - time query is not recorded, because there is no previous query from which to - compute a delta. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker makes periodic queries to obtain a secure timestamp over - the network. This histogram records the latency of each time query. - - - - - - Removed 08/2016 because it does not provide additional information beyond - NetworkTimeTracker.UpdateTimeFetchFailed and - NetworkTimeTracker.UpdateTimeFetchValid. - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker makes periodic queries to obtain a secure timestamp over - the network. This histogram increments whenever such a query is attempted. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker makes periodic queries to obtain a secure timestamp over - the network. This histogram records the request's net error code whenever a - secure timestamp fetch results in a network error or a non-200 HTTP status - code. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker makes periodic queries to obtain a secure timestamp over - the network. Whenever one of these requests results in a successful 200 - status code, this histogram records true if the response parsed and - validated successfully, and false otherwise. - - - - - estark@chromium.org - mab@chromium.org - - NetworkTimeTracker observes a tick clock and a wall clock to determine - whether a timestamp retrieved from the network in the past can be used to - compute a current timestamp. When the NetworkTimeTracker observes that the - wall clock ran backwards, the NetworkTimeTracker must discard the network - timestamp because it has no way to compute a reliable current timestamp. - Whenever the NetworkTimeTracker discards a network timestamp due to the wall - clock running backwards, this histogram records the magnitude of the - difference of the current wall clock time minus the wall clock time when the - network timestamp was retrieved. - - - - - - Removed as of 01/2017. Replaced by NewTabPage.ActionAndroid2. - - newt@chromium.org - - Actions taken by users from the new tab page on Android. These actions may - navigate away from the NTP (e.g. searching in the omnibox or opening a - bookmark), but can also happen without navigating away from the NTP (e.g. - opening a bookmark in a new tab). - - - - - twellington@chromium.org - finkm@chromium.org - - Actions taken from the new tab page on Android. These actions may navigate - away from the NTP (e.g. searching in the omnibox or opening a bookmark), but - can also happen without navigating away from the NTP (e.g. opening a content - suggestion in a new tab). - - - - - justincohen@chromium.org - gambard@chromium.org - - Actions taken by users from the new tab page on iOS. These actions may - navigate away from the NTP (e.g. searching in the omnibox or opening a - bookmark), but can also happen without navigating away from the NTP (e.g. - opening a bookmark in a new tab). - - - - - - Removed 06/2019. No longer used. - - treib@chromium.org - - The amount of time it takes to download the animated logo. Android only. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Histogram for the source of app page drags. For any succesful drop onto an - apps pane of the NTP, this logs where the drag originated. - - - - - - Removed 02/2019 with the removal of the associated service integration. - - ramyan@chromium.org - yyushkina@chromium.org - - The time it took until a request from the New Tab Page for Google Photos - albums was served. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The time it took until a request from the New Tab Page for Backdrop - Collections was served. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The time it took until a request from the New Tab Page for Backdrop Images - was served. - - - - - ramyan@chromium.org - yyushkina@chromium.org - - The time it took until a request from the New Tab Page for the next Backdrop - Image in a collection was served. The duration is measured from time the - client invokes the service call, to the time it receives the callback. - - - - - - Removed 02/2019 with the removal of the associated service integration. - - ramyan@chromium.org - yyushkina@chromium.org - - The time it took until a request from the New Tab Page for Google Photos (in - a specific album) was served. - - - - - - Removed on M33 with the change to native NTP. - - Please list the metric's owners. Add more owner tags as needed. - - Actions taken by users on partner bookmarks (editing / renaming) on the NTP - on Android. - - - - - - Not used anymore. Removed in April 2020. - - jkrcal@chromium.org - - Android: Result of fetching a favicon for an article suggestion on the New - Tab Page. - - - - - - Not used anymore. Removed in April 2020. - - jkrcal@chromium.org - - Android: Time it takes to fetch a favicon for an article suggestion on the - New Tab Page. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: Whether article suggestions on New Tab Page are set visible by user - on startup and when the visibility is changed. - - - - - skym@chromium.org - carlosk@chromium.org - Android: Loading of Zine was artifically delayed - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The type of trigger that caused a background fetch of NTP content - suggestions from a suggestion server. Every background fetch is recorded. - - - - - - Removed in October 2017 (M64) and replaced by - NewTabPage.ContentSuggestions.BreakingNews.ReceivedMessageAction, when - adding support for push-to-refresh messages. - - vitaliii@chromium.org - - Android: Number of received messages and whether they contain pushed news. A - message contains pushed news if the payload key exists in the message. The - payload content is not checked at all (e.g. it may be empty). Recorded when - a message is received. - - - - - - Removed 04/2019. Breaking News feature removed. - - mamir@chromium.org - - Android: Action of a received message. An action can be either push-by-value - or push-to-refresh. A message with a missing or invalid action is recorded - as well. Recorded when a message is received. - - - - - - Removed 04/2019. Breaking News feature removed. - - vitaliii@chromium.org - - Android: The result of a subscription request for breaking news at the - content suggestions server. Recorded when a request finishes. Analogous to - NewTabPage.ContentSuggestions.BreakingNews.UnsubscriptionRequestStatus. - - - - - - Removed 04/2019. Breaking News feature removed. - - vitaliii@chromium.org - - Android: Time between a token validation and the last successful token - retrieval from InstanceID. Recorded when InstanceID answers our token - request for a validation either with a token or an error. If the token was - never received before the validation, the metric is not recorded. - - - - - - Removed 04/2019. Breaking News feature removed. - - vitaliii@chromium.org - - Android: The result of our inquiry to InstanceID to receive the current - token. Recorded when InstanceID replies to our inquiry for a token - (including for a validation). - - - - - - Removed 04/2019. Breaking News feature removed. - - vitaliii@chromium.org - - Android: The result of an unsubscription request for breaking news at the - content suggestions server. Recorded when a request finishes. Analogous to - NewTabPage.ContentSuggestions.BreakingNews.SubscriptionRequestStatus. - - - - - - Removed 04/2019. Breaking News feature removed. - - vitaliii@chromium.org - - Android: Whether a token validation detected an invalid token. This is - recorded only for validations where no error occured and the token was - actually retrieved. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: A category of content suggestions that was dismissed (by swiping - away its empty state card). - - - - - - Removed in July 2017. This metric was replaced by CountOnNtpOpenedIfVisible. - Initially the metric was not recorded properly if any category was not - visible. This was fixed in https://codereview.chromium.org/2874213002/, - however, not visible categories still were polluting the metric (they were - recorded as showing 0 suggestions). - - treib@chromium.org - - Android: The number of suggestion cards that were available at the time an - NTP was opened. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The number of suggestion cards that were available at the time an - NTP was opened. Only visible categories (i.e. which can be seen by the user - on this NTP) are recorded, including empty ones. - - - - - - Removed in October 2017 (M63) and replaced by - CountOnNtpOpenedIfVisible.Articles.Prefetched.Offline2, because - underreported. UI checked whether a URL is prefetched asynchronously. As a - result, there was a race condition and this metric could be reported before - all URLs are checked. - - vitaliii@chromium.org - - Android: The number of prefetched suggestion cards that were available in - Articles category if it was visible at the time an NTP was opened and the - user was offline. Analogous to - NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The number of prefetched suggestion cards that were available in - Articles category if it was visible at the time an NTP was opened and the - user was offline. Analogous to - NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible, except that this - metric is reported after all URL prefetched asynchronous checks finish. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The position of a suggestion card on the NTP that is dismissed, - typically by swiping it away. The suggestion had a URL that was NOT visited - before. We track the position the card had in the list when it was first - seen by the user. This tracked position can be different from the position - observed by the user, e.g. when the user dismissed some suggestions from the - list or requested more that got inserted in the middle of the feed. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The position of a suggestion card on the NTP that is dismissed, - typically by swiping it away. The suggestion had a URL that was visited - before. We track the position the card had in the list when it was first - seen by the user. This tracked position can be different from the position - observed by the user, e.g. when the user dismissed some suggestions from the - list or requested more that got inserted in the middle of the feed. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The position of a suggestion card whose long-press menu was opened, - analogous to NewTabPage.ContentSuggestions.Opened. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The age of a suggestion card on the NTP whose long-press menu was - opened, analogous to NewTabPage.ContentSuggestions.OpenedAge. - - - - - - Replaced by NewTabPage.ContentSuggestions.MenuOpenedScoreNormalized. - - treib@chromium.org - - Android: The relevance score of a suggestion card on the NTP whose - long-press menu was opened, analogous to - NewTabPage.ContentSuggestions.OpenedScore. - - - - - tschumann@chromium.org - - Android: The relevance score of a suggestion card on the NTP whose - long-press menu was opened, analogous to - NewTabPage.ContentSuggestions.OpenedScoreNormalized. Scores (which are - typically floats within (0,1]) get reported as discrete integers within - [1,10]. For instance, the discrete value 1 represents score values from - (0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly - high scores. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The position of a "More" suggestion card that was clicked - on the NTP. A card is considered shown when at least 2/3 of its height is - visible on the screen. We track the position the card had in the list when - it was first seen by the user. This tracked position can be different from - the position observed by the user, e.g. when the user dismissed some - suggestions from the list or requested more that got inserted in the middle - of the feed. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The position of a "More" suggestion card that was shown - on the NTP. A card is considered shown when at least 2/3 of its height is - visible on the screen. For each card, at most one impression is recorded per - NTP instance. We track the position the card had in the list when it was - first seen by the user. This tracked position can be different from the - position observed by the user, e.g. when the user dismissed some suggestions - from the list or requested more that got inserted in the middle of the feed. - - - - - vitaliii@chromium.org - - Android: The new index of a category on the NTP after it has been moved up - due to a click. The index of a category, which has been overtaken, is not - recorded here. This tracked index can be different from the position - observed by the user, e.g. empty categories are not shown. This metric - ignores all other order changes (e.g. dismissing a category or clearing - history). - - - - - zea@chromium.org - - Android: The number of actions taken on displayed notifications, either - user-initiated (tapping to open or swiping to dismiss), or automatic (hiding - due to a change in circumstances). - - - - - zea@chromium.org - - Android: The number of times a user opted out, keyed by method: IMPLICIT - (user ignored enough notifications consecutively that we think they're not - interested), or EXPLICIT (via explicit setting). - - - - - zea@chromium.org - - Android: The number of notifications that were shown, keyed by category. One - bucket counts the server-provided ARTICLES category; the other counts - everything else. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: How an article linked from a suggestion card on the NTP was opened - (e.g. plain click, open in new tab, open in incognito). - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The position of the suggestion card on the NTP, that is clicked - through to the host website of the content. We track the position the card - had in the list when it was first seen by the user. This tracked position - can be different from the position observed by the user, e.g. when the user - dismissed some suggestions from the list or requested more that got inserted - in the middle of the feed. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The position of the prefetched suggestion card on the NTP, that is - clicked through to the host website of the content, when the user is - offline. Analogous to NewTabPage.ContentSuggestions.Opened. That is we track - the position the card had in the list when it was first seen by the user. - This tracked position can be different from the position observed by the - user, e.g. when the user dismissed some suggestions from the list or - requested more that got inserted in the middle of the feed. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The age of a suggestion card on the NTP that is clicked through to - the host website of the content. The age is measured from the moment the - content has been published. - - - - - vitaliii@chromium.org - - Android: The index of a category on the NTP, whose suggestion card is - clicked through to the host website of the content. This tracked index can - be different from the position observed by the user, e.g. for the user a - category may be at the top of the NTP, but with index 1, because they - dismissed the one that was previously at the top. - - - - - - Replaced by NewTabPage.ContentSuggestions.OpenedScoreNormalized. - - treib@chromium.org - - Android: The score of a suggestion card on the NTP that is clicked through - to the host website of the content. The recorded score is from the moment - the suggestion was fetched, it could have changed since. - - - - - tschumann@chromium.org - - Android: The score of a suggestion card on the NTP that is clicked through - to the host website of the content. The recorded score is from the moment - the suggestion was fetched, it could have changed since. Scores (which are - typically floats within (0,1]) get reported as discrete integers within - [1,10]. For instance, the discrete value 1 represents score values from - (0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly - high scores. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Whether content suggestions from the remote service are enabled. It is - recored at startup. Note: This histogram is not specific to the New Tab - Page. - - - - - vitaliii@chromium.org - - Android: The number of suggestion sections that were shown at the time an - NTP was opened. All shown sections (including empty ones) are counted. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The position of a suggestion card that was shown on the NTP. A card - is considered shown when at least 2/3 of its height is visible on the - screen. For each card, at most one impression is recorded per NTP instance. - We track the position the card had in the list when it was first seen by the - user. This tracked position can be different from the position observed by - the user, e.g. when the user dismissed some suggestions from the list or - requested more that got inserted in the middle of the feed. - - - - - - Removed in October 2017 (M63) and replaced by - Shown.Articles.Prefetched.Offline2, because underreported. UI checked - whether a URL is prefetched asynchronously. As a result, there was a race - condition and for suggestions immediately visible on the suggestions surface - this metric could be reported before their URLs are actually checked. - - vitaliii@chromium.org - - Android: The position of a prefetched suggestion card that was shown on the - NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is - a card is considered shown when at least 2/3 of its height is visible on the - screen. For each card, at most one impression is recorded per NTP instance. - We track the position the card had in the list when it was first seen by the - user. This tracked position can be different from the position observed by - the user, e.g. when the user dismissed some suggestions from the list or - requested more that got inserted in the middle of the feed. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The position of a prefetched suggestion card that was shown on the - NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is - a card is considered shown when at least 2/3 of its height is visible on the - screen. For each card, at most one impression is recorded per NTP instance. - We track the position the card had in the list when it was first seen by the - user. This tracked position can be different from the position observed by - the user, e.g. when the user dismissed some suggestions from the list or - requested more that got inserted in the middle of the feed. This metric is - reported not immediately after the impression, but once the request to - Offline Page model to check the URL finishes. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The age of a suggestion card that was shown on the NTP. A card is - considered shown when at least 2/3 of its height is visible on the screen. - For each card, at most one impression is recorded per NTP instance. - - - - - - Replaced by NewTabPage.ContentSuggestions.ShownScoreNormalized. - - treib@chromium.org - - Android: The score of a suggestion card that was shown on the NTP. A card is - considered shown when at least 2/3 of its height is visible on the screen. - For each card, at most one impression is recorded per NTP instance. - - - - - tschumann@chromium.org - - Android: The score of a suggestion card that was shown on the NTP. A card is - considered shown when at least 2/3 of its height is visible on the screen. - For each card, at most one impression is recorded per NTP instance. Scores - (which are typically floats within (0,1]) get reported as discrete integers - within [1,10]. For instance, the discrete value 1 represents score values - from (0.0, 0.1]. The discrete value 11 is the overflow bucket for - unexpectedly high scores. - - - - - - Replaced by NewTabPage.ContentSuggestions.TimeSinceSuggestionFetched. - - markusheintz@chromium.org - - Android: The time since the last successful background fetch of remote - content suggestions. Recorded when the user looks at content suggestions on - the NTP. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the displayed content suggestions was fetched. - Recorded when the user looks at content suggestions on the NTP. The metric - is only recorded for suggestions of the Articles for you section. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the last fetch, recorded upon the first on-shown - fetch trigger. The first on-shown trigger does not necessarily cause a fetch - (if it comes before the end of the respective scheduling interval). This - metric is recorded at most once after each fetch (and additionaly at most - once after each startup of Chrome before the next fetch). This is used to - understand how changing scheduling intervals will impact traffic of - background fetches. - - - - - - Removed as of July 2017, in favor of - NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and - NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger. - - jkrcal@chromium.org - - Android: The time since the last fetch, recorded upon the first soft fetch - trigger. The first soft trigger does not necessarily cause a fetch (if it - comes before the end of the respective scheduling interval). This metric is - recorded at most once after each fetch (and additionaly at most once after - each startup of Chrome before the next fetch). This is used to understand - how changing scheduling intervals will impact traffic of background fetches. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the last fetch, recorded upon the first startup - fetch trigger. The first startup trigger does not necessarily cause a fetch - (if it comes before the end of the respective scheduling interval). This - metric is recorded at most once after each fetch (and additionaly at most - once after each startup of Chrome before the next fetch). This is used to - understand how changing scheduling intervals will impact traffic of - background fetches. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the last fetch, recorded upon a persistent fetch. - This is used to understand what are the real persistent fetching intervals - in the wild. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the last fetch, recorded upon a soft fetch. This is - used to understand what are the real soft fetching intervals in the wild. - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time since the last fetch, recorded upon a startup fetch. This - is used to understand what are the real soft fetching intervals in the wild. - - - - - - Replaced by NewTabPage.ContentSuggestions.UIUpdateResult2 in January 2017. - - jkrcal@chromium.org - - Android: The result of updating the list of content suggestions in the UI. - - - - - - Not used anymore. Removed in April 2020. - - jkrcal@chromium.org - - Android: The result of updating the list of content suggestions in one UI - section. - - - - - - Not used anymore. Removed in April 2020. - - jkrcal@chromium.org - - Android: The number of content suggestions that have been seen by the user - in the UI section before the section was successfully updated. The seen - suggestions were not removed in the update so that we do not change visible - parts of the UI. This histogram is only recorded when the UIUpdateResult2 is - "Success (some suggestions replaced)". - - - - - carlosk@chromium.org - freedjm@chromium.org - feed@chromium.org - - Android: The time of day (in the local timezone) when the user used content - suggestions. Recorded for example when the user scrolls to the articles - suggestions or opens an article suggestions. - - - - - freedjm@chromium.org - feed@chromium.org - - Android: Time spent reading the page linked by an opened suggestion card. - Exit conditions include the tab not being in the foreground or starting a - new navigation. - - - - - tmartino@chromium.org - chrome-creation@google.com - - Tracks the outcome of Probabilistic Cryptid Rendering (succeeded, failed, or - was disabled because preconditions were not met). - - - - - - Removed 2019-08. - - dbeam@chromium.org - yyushkina@chromium.org - - The availability of New Tab Page background customization features on - Desktop, based on feature flags or other configuration settings; logged per - NTP load. - - - - - - Removed 2019-08. - - dbeam@chromium.org - yyushkina@chromium.org - - The availability of New Tab Page shortcut customization features on Desktop, - based on feature flags or other configuration settings; logged per NTP load. - - - - - - - dbeam@chromium.org - yyushkina@chromium.org - chrome-analysis-team@google.com - - Customization actions performed by the user on the New Tab Page; logged as - each interaction occurs. This may indicate popularity of a particular - customization type. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - Captures the actions performed when configuring a 'Chrome background' image - on the New Tab Page. Since most actions are sequential, this may indicate - steps in the configuration process where users drop off. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The New Tab Page features that have been customized by the user; logged per - NTP load. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The New Tab Page shortcut settings that can be customized by the user, - including shortcut type (i.e. most visited vs custom links) and visibility; - logged per NTP load. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Captures the actions performed when uploading a local image as the - background on the New Tab Page. Since most actions are sequential, this may - indicate steps in the configuration process where users drop off. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Captures the actions performed when configuring shortcuts on the New Tab - Page. - - - - - - Removed 2016-02. - - Please list the metric's owners. Add more owner tags as needed. - The default pane when the NTP is first opened. - - - - - Deprecated as of 08/2020. - - shaktisahu@chromium.org - clank-downloads@google.com - - Android: Records user actions on the explore offline card on the NTP. - - - - - - Removed in favor of ContentSuggestions.Feed.Image.FetchResult. - - wylieb@chromium.org - - Android: Represents success/failure of Feed image loading. Recorded upon - each individual image retrieved from the feed_image_cache. - - - - - - Removed in favor of ContentSuggestions.Feed.Image.LoadFromCacheTime. - - wylieb@chromium.org - - Android: The time it takes for Feed to load an image from the cache. - - - - - - Removed in favor of ContentSuggestions.Feed.Image.LoadFromNetworkTime. - - wylieb@chromium.org - - Android: The time it takes for Feed to load an image from the network. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Histogram of the time, in milliseconds, users have the cursor over a most - visited thumbnail before clicking. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Histogram of the time, in milliseconds, users have the cursor over a most - visited thumbnail before moving it away from the thumbnail without clicking. - - - - - - Removed 2017-04, replaced by NewTabPage.TileType and - NewTabPage.SuggestionsImpression.IconsColor. - - newt@chromium.org - - The number of most visited tiles on the new tab page that are displayed - using a fallback color (as opposed to having an icon, or simply being gray). - Android only. - - - - - - Removed 2017-04, replaced by NewTabPage.TileType and - NewTabPage.SuggestionsImpression.IconsGray. - - newt@chromium.org - - The number of most visited tiles on the new tab page that are displayed as - gray (as opposed to having an icon, or a fallback color). Android only. - - - - - - Removed 2017-04, replaced by NewTabPage.TileType and - NewTabPage.SuggestionsImpression.IconsReal. - - newt@chromium.org - - The number of most visited tiles on the new tab page that are displayed with - the site's icon (as opposed using a fallback color or just gray). Android - only. - - - - - - Removed 2017-05 (and not recorded for some time before that). - - knn@chromium.org - - Android: Whether an attempt to download the image for an interest was - successful. - - - - - - Removed 2017-05 (and not recorded for some time before that). - - knn@chromium.org - - Android: Whether an attempt to fetch the interests for a user was - successful. - - - - - - Removed 2017-05 (and not recorded for some time before that). - - knn@chromium.org - - Android: The number of interests fetched for a user to display on the NTP. - - - - - jkrcal@chromium.org - - Android: Percentage of how much in browsing is the UI language of Chrome - used compared to overall use of the two top languages that are reported to - Chrome content suggestion server. - - - - - - Removed 2018-04 with full launch of NTP condensed layout. - - peconn@chromium.org - - Android: A histogram detailing how the NewTabPageLayout is laid out on the - device (eg, whether it fits fully above the fold or not). This is logged - once per NewTabPageLayout creation (so once per NTP). - - - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Histogram of the time, in milliseconds, it took for the NTP to load all of - its tiles since navigation start. - - - - - - Removed 2020-06 because it was no longer being monitored. - - mvanouwerkerk@chromium.org - - Android: the type of load for the NTP, such as cold or warm start. It's a - warm start if the native library is already loaded and initialized at the - time the activity is created. This might happen if for example a service was - already running. - - - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-analysis-team@google.com - chrome-desktop-ntp@google.com - - The number of clicks on the static/call-to-action/animated logo on the NTP. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Outcome of downloading search provider's logos. It measures whether - download/parsing is successful, revalidation and parsing work properly, etc. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The amount of time it took to download the static logo. This includes - requests where there was no logo, or where an existing logo was revalidated - (so no new image data was downloaded), but it does not include failed - requests. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - A logo image (static or CTA) was downloaded. Recorded only when the image - was downloaded and decoded without errors. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The number of static logos and animated logos shown to users. Note that the - base version of this histogram is recorded both for logos from the cache and - for fresh logos, so it can be recorded twice per NTP impression. - - - - - - Removed 2017-08 because it was only recorded for cached logos. Replaced by - LogoShownTime2. - - treib@chromium.org - - The amount of time between opening an NTP and the logo appearing. Only - recorded when there is a logo, and only recorded once per NTP. Android only. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The amount of time between opening an NTP and the logo appearing. Only - recorded when there is a logo, and only recorded once per NTP. - - - - - fserb@chromium.org - zmin@chromium.org - - Record the network status when a new tab page is opened. True if user is - online and false for offline. - - - - - - Removed on M33 with the change to native NTP. - - Please list the metric's owners. Add more owner tags as needed. - - Android: Tallies counts for how the user interacted with the NTP promo page. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Histogram of the time, in milliseconds since navigation start, it took until - the modules showed up on the NTP. - - - - - - - justincohen@chromium.org - mastiz@chromium.org - tiborg@chromium.org - yyushkina@chromium.org - chrome-analysis-team@google.com - chrome-desktop-ntp@google.com - - Histogram for user clicks of the most visited tile. The value is equal to - the index of the tile. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - justincohen@chromium.org - newt@chromium.org - - Action taken by the user on the Most Visited NTP pane. If the user switches - panes during this use of the NTP, this action is sometimes not recorded. Ask - mpearson@ for details. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The age of the data at click time, that is, the elapsed time since the - suggestion was generated by a ranking algorithm. - - - - - - Removed 2016-05. - - treib@chromium.org - - The schemes of URLs of most visited thumbnails that the user clicked on. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - justincohen@chromium.org - newt@chromium.org - - Records anomalous events for the Most Visited Tile Placement experiment, - where it is unable to operate as expected. These are recorded during New Tab - Page load time, once for every NTP. - - - - - treib@chromium.org - - The time from the New Tab page being shown until the user to clicked on a - most visited tile. Only recorded if the user clicked on a tile, as opposed - to e.g. searching via the omnibox. Only measured on Android. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - The number of screenshots that were cached for the non-visible but ranked - suggestions on the Suggested NTP pane. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Given that the user has typed a URL, and given that that specific URL was - ranked but not visible on the Suggested pane of the NTP, this is the rank - that the Suggested pane had for that URL. - - - - - - Removed 2016-07. - - - The number of tiles for which we relied on external tiles as a fallback - because a local screenshot was not available to be used as a thumbnail. - External tiles are those for which the visuals are handled by the page - itself, not by the iframe. Recorded before reloading the suggestions, - navigating to a URL, switching tabs, changing the active window, or closing - the tab/shutting down Chrome. - - - - - - Removed 2016-07. - - - The number of external tiles that are displayed on the NTP. External tiles - are those for which the visuals are handled by the page itself, not by the - iframe. Recorded before reloading the suggestions, navigating to a URL, - switching tabs, changing the active window or closing the tab/shutting down - Chrome. - - - - - - Removed 2016-07. - - - The number of tiles for which we displayed a gray tile with the domain name - as a fallback because a local screenshot was not available to be used as a - thumbnail. Recorded before reloading the suggestions, navigating to a URL, - switching tabs, changing the active window or closing the tab/shutting down - Chrome. - - - - - - Removed 2016-07. - - - The number of tiles for which no thumbnail was specified, but a domain was - so we displayed a gray tile with the domain name in it. Recorded before - reloading the suggestions, navigating to a URL, switching tabs, changing the - active window or closing the tab/shutting down Chrome. - - - - - - Removed 2016-07. - - - The total number of times the user hovered the mouse over Most Visited tile - or title elements before changing focus away from the NTP, be it by - navigating to a URL, switching tabs, changing the active window or closing - the tab/shutting down Chrome. - - - - - - Removed 01/2014. Replaced by NewTabPage.NumberOfThumbnailTiles. - - Please list the metric's owners. Add more owner tags as needed. - - The number of tiles for which we attempted to use a local screenshot as a - thumbnail. Recorded before reloading the suggestions, navigating to a URL, - switching tabs, changing the active window or closing the tab/shutting down - Chrome. - - - - - - Removed 2016-07. - - - The number of thumbnails for which a local screenshot was not available so - we were not able to display them on the Most Visited section of the NTP. - Recorded before reloading the suggestions, navigating to a URL, switching - tabs, changing the active window or closing the tab/shutting down Chrome. - - - - - - Removed 2016-07. - - - The number of tiles for which we attempted to use a local screenshot as a - thumbnail. Recorded before reloading the suggestions, navigating to a URL, - switching tabs, changing the active window or closing the tab/shutting down - Chrome. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The number of tiles that are on the NTP, no matter if they are thumbnails, - gray tiles, or external tiles. Recorded before reloading the suggestions, - navigating to a URL, switching tabs, changing the active window or closing - the tab/shutting down Chrome. The sum of this histogram does not have to - equal to the total count of tile impressions (such as the total count in - NewTabPage.TileType). The reason is that not all tiles have to be impressed - initially (e.g., the second row of tiles may be initially out of sight on - iOS). - - - - - - Removed in M58. - - dewittj@chromium.org - - The amount of time spent waiting for the offline page model to return which - New Tab Page URLs are available offline. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The time it took until a request from the New Tab page for the OneGoogleBar - script was served. Recorded only on the local NTP. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Histogram of the time, in milliseconds since navigation start, it took until - the OneGoogleBar showed up on the NTP. Recorded only on the local NTP. - - - - - - Removed 05/2015. Feature was removed. - - Please list the metric's owners. Add more owner tags as needed. - - Histogram for usage of the menu on the NTP that allows the user to access - tabs from other devices. - - - - - - Removed 2016-02. - - Please list the metric's owners. Add more owner tags as needed. - - The pane that had been previously selected when the user switches panes in - the NTP. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - Histogram for NTP bubble promo activity. - - - - wenyufu@chromium.org - twellington@chromium.org - - Records events related to the homepage promo card on the new tab page. - Recorded for Android only. - - - - - wenyufu@chromium.org - twellington@chromium.org - - The number of times that the homepage promo was shown to the user before - they took action. Recorded when the user accepts the homepage promo. - Recorded for Android only. - - - - - wenyufu@chromium.org - twellington@chromium.org - - The number of times that the homepage promo was shown to the user before it - was manually dismissed. Recorded when the user dismisses the promo. Recorded - for Android only. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - Histogram for NTP notification promo activity. - - - - - - dbeam@chromium.org - yyushkina@chromium.org - chrome-analysis-team@google.com - - Emitted each time a promo linked is clicked on the local NTP. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - mahmadi@chromium.org - chrome-desktop-ntp@google.com - - Logs how many times various promo browser commands are executed. Triggered - when a supported and enabled promo browser command is sent via the New Tab - Page promos and is executed by the PromoBrowserCommandHandler. - - - - - - Removed 2018-03 as it doesn't correctly capture all request states. - - kmilka@chromium.org - ramyan@chromium.org - - The time it took until a request from the New Tab page for the middle slot - promo script was served. Recorded only on the local NTP. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The time it took until a request from the New Tab page for the middle slot - promo script was served. Recorded on the local and WebUI NTP. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Histogram of the time, in milliseconds since navigation start, it took until - a middle slot promo showed up on the NTP. Recorded on the local and WebUI - NTP. - - - - - mahmadi@chromium.org - tommycli@chromium.org - chrome-desktop-ntp@google.com - - Records the time taken between a keystroke being typed in the NTP realbox - and the time when we're ready to render the results in the DOM. If there are - multiple keystrokes before the results are rendered, logs the time since the - earliest one. This is most comparable to Omnibox's - Omnibox.CharTypedToRepaintLatency.ToPaint as it does not take into account - the time the DOM change task spends in the message loop nor its duration. - - - - - - Removed March 2020. - - pkotwicz@chromium.org - treib@chromium.org - - Records the amount of time that the "Recent Tabs" page is visible - and Chrome is in the foreground on Android. The metric is recorded whenever - the "Recent Tabs" page moves out of the foreground. The metric is - recorded when the "Recent Tabs" page is closed, when the user - switches from the "Recent Tabs" page to a different tab and when - Chrome is backgrounded. - - - - - jkrcal@chromium.org - - Records how many background requests of the given type the browser tried to - perform each day where the type is specified by the _suffix of the - histogram. The histogram is emitted only after midnight of the given day - passes - right before the first following request (which can be several days - later if the user does not use Chrome in the meantime). The histogram counts - requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count - can easily exceed the daily quota. - - - - - jkrcal@chromium.org - - Records how many interactive requests of the given type the browser tried to - perform each day where the type is specified by the _suffix of the - histogram. The histogram is emitted only after midnight of the given day - passes - right before the first following request (which can be several days - later if the user does not use Chrome in the meantime). The histogram counts - requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count - can easily exceed the daily quota. - - - - - jkrcal@chromium.org - - Records the status w.r.t. the quota for all requests of the given type. The - type of request is specified by the _suffix of the histogram. - - - - - - Removed February 2017. - - mvanouwerkerk@chromium.org - - The time until the search box became available on the NTP in a cold start. - It's a cold start if the native library is not already loaded and - initialized at the time the activity is created. Only measured on Android. - - - - - - Removed February 2017. - - mvanouwerkerk@chromium.org - - The time until the search box became available on the NTP in a warm start. - It's a warm start if the native library is already loaded and initialized at - the time the activity is created. This might happen if for example a service - was already running. Only measured on Android. - - - - - fgorski@chromium.org - ender@google.com - yyushkina@chromium.org - - The time until the search box became available on the NTP in a cold start. - It's a cold start if the native library is not already loaded and - initialized at the time the activity is created. Only measured on Android. - - - - - fgorski@chromium.org - ender@google.com - yyushkina@chromium.org - - The time until the search box became available on the NTP in a warm start. - It's a warm start if the native library is already loaded and initialized at - the time the activity is created. This might happen if for example a service - was already running. Only measured on Android. - - - - - - - dbeam@chromium.org - yyushkina@chromium.org - chrome-analysis-team@google.com - - The index of the search suggestion tile that was clicked on the local NTP. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - Removed 2019-03 as it doesn't correctly capture all request states. - - kmilka@chromium.org - ramyan@chromium.org - - The time it took until a request from the New Tab page for the search - suggestions script was served. Recorded only on the local NTP. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The time it took until a request from the New Tab page for the search - suggestions script was served. Recorded only on the local NTP. - - - - - - Removed 2019-03 as it grouped together requests that returned no suggestions - with those that failed completely, which is misleading. - - kmilka@chromium.org - ramyan@chromium.org - - Whether a request was made for search suggestions on NTP load; and if a - request was not made, the reason why. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - Whether a request was made for search suggestions on NTP load; and if a - request was not made, the reason why. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The number of search suggestion tiles that were shown on the local NTP. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - TBD. - - - - - Removed 2016-02. - - Please list the metric's owners. Add more owner tags as needed. - The pane selected when the user switches panes in the NTP. - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Histogram for user clicks of the Recently Closed items. The value is the - recency of the entry being restored (0 is most recent). - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Histogram to track how many times a user switched pages in a single NTP - session. - - - - - - Replaced by NewTabPage.ContentSuggestions.Opened. - - knn@chromium.org - - Android: The position of the snippets card on the NTP, that is clicked - through to the host website of the content. We track the position the - snippet had in the list when NTP was loaded. This tracked position is thus - different from the position observed by the user whenever before scrolling - down to the given snippet, the user discards some snippets in the top of the - list. - - - - - - Replaced by NewTabPage.ContentSuggestions.OpenedAge. - - jkrcal@chromium.org - - Android: The age of the snippets card on the NTP, that is clicked through to - the host website of the content. The age is measured from the moment the - content has been published. In each "_x_y" suffix of the - histogram, only snippets on positions \gt;=x and \lt;=y are tracked. We - track the position the snippet had in the list when NTP was loaded. This - tracked position is thus different from the position observed by the user - whenever before scrolling down to the given snippet, the user discards some - snippets in the top of the list. - - - - - - Removed as of 6/2016 - - jkrcal@chromium.org - - Android: The score of the snippets card on the NTP, that is clicked through - to the host website of the content. The recorded score is from the moment - the snippet was fetched, it could have changed since. In each "_x" - suffix of the histogram, only snippets on positions \lt;=x are tracked. We - track the position the snippet had in the list when NTP was loaded. This - tracked position is thus different from the position observed by the user - whenever before scrolling down to the given snippet, the user discards some - snippets in the top of the list. - - - - - - Replaced by NewTabPage.ContentSuggestions.OpenedScore. - - jkrcal@chromium.org - - Android: The score of the snippets card on the NTP, that is clicked through - to the host website of the content. The recorded score is from the moment - the snippet was fetched, it could have changed since. In each "_x" - suffix of the histogram, only snippets on positions \lt;=x are tracked. We - track the position the snippet had in the list when NTP was loaded. This - tracked position is thus different from the position observed by the user - whenever before scrolling down to the given snippet, the user discards some - snippets in the top of the list. In contrast to CardClickedScore, this - histogram has a proper maximal value of 100 000. - - - - - - Removed as of 4/2016 - - knn@chromium.org - - Android: The position of the snippets card on the NTP, that is expanded to - reveal more content. - - - - - - Removed as of 4/2016 - - knn@chromium.org - - Android: The position of the snippets card on the NTP, for which the - expanded content was minimized/hidden. - - - - - - Replaced by NewTabPage.ContentSuggestions.MenuOpened. - - peconn@chromium.org - - Android: The position of a snippet card when it is long pressed, analagous - to NewTabPage.Snippets.CardClicked. - - - - - - Replaced by NewTabPage.ContentSuggestions.MenuOpenedAge. - - peconn@chromium.org - - Android: The time difference between when a snippet card is long pressed and - when its content was published. Analagous to - NewTabPage.Snippets.CardClickedAge. - - - - - - Replaced by NewTabPage.ContentSuggestions.MenuOpenedScore. - - peconn@chromium.org - - Android: The relevance score of an interest card that is long pressed, - analagous to NewTabPage.Snippets.CardClickedScoreNew. - - - - - - Replaced by NewTabPage.ContentSuggestions.Shown. - - knn@chromium.org - - Android: The position of the snippets card that is shown on the NTP. Each - snippet (its position) is recorded whenever at least 2/3 of its height - becomes visible by scrolling through the NTP. Each snippet is recorded at - most once for a given instance of NTP and a given data set of snippets that - is shown. We track the position the snippet had in the list when NTP was - loaded. This tracked position is thus different from the position observed - by the user whenever before scrolling down to the given snippet, the user - discards some snippets in the top of the list. Previously (in the code - before 2016/05/27), this histogram was recorded each time a snippet became - visible (e.g. by scrolling up and down) at least by 1px; the first snippet - was thus recorded even without scrolling down. - - - - - - Replaced by NewTabPage.ContentSuggestions.ShownAge. - - jkrcal@chromium.org - - Android: The age of the snippets card that is shown on the NTP. Each snippet - (its age) is recorded whenever at least 2/3 of its height becomes visible by - scrolling through the NTP. Each snippet is recorded at most once for a given - instance of NTP and a given data set of snippets that is shown. The age is - measured from the moment the content has been published. In each - "_x_y" suffix of the histogram, only snippets on positions \gt;=x - and \lt;=y are tracked. By this, we mean the position the snippet had in the - list when NTP was loaded. This tracked position is thus different from the - position observed by the user whenever before scrolling down to the given - snippet, the user discards some snippets in the top of the list. - - - - - - Removed as of 6/2016 - - jkrcal@chromium.org - - Android: The score of the snippets card that is shown on the NTP. Each - snippet (its score) is recorded whenever at least 2/3 of its height becomes - visible by scrolling through the NTP. Each snippet is recorded at most once - for a given instance of NTP and a given data set of snippets that is shown. - The recorded score is from the moment the snippet was fetched, it could have - changed since. In each "_x" suffix of the histogram, only snippets - on positions \lt;=x are tracked. By this, we mean the position the snippet - had in the list when NTP was loaded. This tracked position is thus different - from the position observed by the user whenever before scrolling down to the - given snippet, the user discards some snippets in the top of the list. - - - - - - Replaced by NewTabPage.ContentSuggestions.ShownScore. - - jkrcal@chromium.org - - Android: The score of the snippets card that is shown on the NTP. Each - snippet (its score) is recorded whenever at least 2/3 of its height becomes - visible by scrolling through the NTP. Each snippet is recorded at most once - for a given instance of NTP and a given data set of snippets that is shown. - The recorded score is from the moment the snippet was fetched, it could have - changed since. In each "_x" suffix of the histogram, only snippets - on positions \lt;=x are tracked. By this, we mean the position the snippet - had in the list when NTP was loaded. This tracked position is thus different - from the position observed by the user whenever before scrolling down to the - given snippet, the user discards some snippets in the top of the list. In - contrast to CardShownScore, this histogram has a proper maximal value of 100 - 000. - - - - - treib@chromium.org - - Android: The time it took to load the database of persisted content - suggestions. Recorded only when the database is loaded successfully. - - - - - treib@chromium.org - - Android: The state of the RemoteSuggestionsProvider. Recorded when the state - changes, typically once at startup and rarely afterwards, e.g. on database - errors. - - - - - mastiz@chromium.org - - Response or error codes encountered when attempting to fetch snippets. - - - - - mastiz@chromium.org - - Result of attempting a fetch, logged once per issued trigger. - - - - - mastiz@chromium.org - - Time spent fetching snippets. Only recorded for fetch attempts that resulted - in an actual network request. - - - - - finkm@chromium.org - - Records the time of the day in minutes when a snippets background fetch was - initiated. Counts minutes since midnight UTC. - - - - - finkm@chromium.org - - Records the time of the day in minutes when a snippets background fetch was - initiated. Counts minutes since midnight local time. - - - - - maybelle@chromium.org - - Whether we discarded any of the snippets after fetching them due to having - incomplete metadata. - - - - - - Removed 2016-10. - - knn@chromium.org - - Android: A histogram giving an overall summary of important events like - impressions, scroll events, clicks etc. - - - - - treib@chromium.org - - Android: The number of snippet articles available to show on the NTP, logged - once every time the list is updated. - - - - - mastiz@chromium.org - - Android: The number of valid snippet articles fetched from the server, - logged every time a fetch finishes successfully. - - - - - - Removed 2016-10. - - mastiz@chromium.org - - Android: The number of snippet articles available to the user in the UI, - logged when the user scrolls below the fold (at max once per NTP load). - - - - - mastiz@chromium.org - - Android: The number of snippet articles discarded by the user, logged every - time the list is updated resulting in an empty list (all articles - discarded). - - - - - treib@chromium.org - - The number of snippets that we discard per fetch due to having incomplete - data. - - - - - - Replaced by NewTabPage.ContentSuggestions.OpenDisposition. - - peconn@chromium.org - - Android: A histogram detailing how the articles linked from snippets are - opened (eg, plain click, open in new tab, open in incognito). - - - - - - Replaced by NewTabPage.ContentSuggestions.VisitDuration. - - mastiz@chromium.org - - Android: Time spent reading the page linked by an opened (clicked) snippet - card. Exit conditions include the tab not being in the foreground or - starting a new navigation. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Histogram for user clicks of the suggested site thumbnails. The value is - equal to the index of the thumbnail. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - Action taken by the user on the Suggested Sites NTP pane. - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - Time to load the Suggested Sites NTP pane, in milliseconds. - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - Time spent on the Suggested Sites NTP pane, in seconds. - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Histogram for impressions on the various most visited tiles. The value is - equal to the index of the thumbnail. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - The age of the data at impression time, that is, the elapsed time since the - suggestion was generated by a ranking algorithm. - - - - - - Removed 2016-07. - - - Indicate, for each impression of the New Tab Page, whether the suggestions - were obtained from the client or server. Recorded before changing focus away - from the NTP, be it by navigating to a URL, switching tabs, changing the - active window or closing the tab/shutting down Chrome. - - - - - - Removed 01/2014. Replaced by NewTabPage.NumberOfThumbnailAttempts and - NewTabPage.NumberOfThumbnailErrors. - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of errors per attempts to load image thumbnails on the New - Tab Page. When an error occurs, a grey tile is shown instead of a thumbnail - image. We measure the rate instead of the number of errors because multiple - attempts are made to load images at different times during the NTP's - lifetime. Each NTP session's error rate is logged after the user navigates - to a new URL from that NTP. - - - - - - Removed 01/2014. Replaced by NewTabPage.NumberOfGrayTileFallbacks and - NewTabPage.NumberOfExternalFallbacks. - - Please list the metric's owners. Add more owner tags as needed. - - The percentage of times most visited tiles use the fallback thumbnail. Only - requests that actually specify a fallback thumbnail are considered here. We - measure the rate instead of the number of errors because multiple attempts - are made to load thumbnails at different times during the NTP's lifetime. - Each NTP session's error rate is logged after the user navigates to a new - URL from that NTP. - - - - - - Removed 07/2019 because the histogram was unused and close to expiration. - - jkrcal@chromium.org - - Mobile only. The result of fetching a favicon for a tile on the New Tab - Page. This is recorded for each gray MostVisited tile on the New Tab Page - once per impression of the tile. - - - - - - Removed 07/2019 because the histogram was unused and close to expiration. - - jkrcal@chromium.org - - Mobile only. The result of fetching a favicon for a tile on the New Tab - Page. This is recorded for each gray PopularSites tile on the New Tab Page - once per updating the set of tiles (notably upon each NTP impression). - - - - - - Removed 06/2017. Replaced by NewTabPage.TileFaviconFetchStatus.Server. - - jkrcal@chromium.org - - Mobile only. The result of fetching a favicon for a tile on the New Tab - Page. This is recorded for each gray MostVisited tile on the New Tab Page - once per lifetime of Chrome (there as an in-memory cache of failed - requests). - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The favicon type that was chosen to represent a most visited tile displayed - on the new tab page, logged at impression time. Note that these values don't - involve an actual icon being displayed because a scrabble time might have - been displayed instead (see NewTabPage.TileType). - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The favicon type that was chosen to represent a most visited tile displayed - on the new tab page, logged when a tile is clicked. Note that these values - don't involve an actual icon being displayed (see - NewTabPage.TileTypeClicked). - - - - - treib@chromium.org - - The number of times a tile was available offline, per tile index - compare - to the NewTabPage.SuggestionsImpression.* histograms. This is recorded when - the NTP finishes loading. Only measured on Android. - - - - - - Removed 06/2019. No longer used. - - treib@chromium.org - - Histogram of the time, in milliseconds since navigation start, it took for - the NTP most visited iframe to receive the data for all of its tiles. This - does not include actually loading the DOM elements for the tiles, in - particular the thumbnail images; see NewTabPage.LoadTime for that. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Records the source of the title for each most visited tiled displayed when - an NTP is opened, e.g. a short_name from a manifest, or the page title. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Records the source for the name a most visited tile showed when the user - clicked it, e.g. a URL, or the page title. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The visual type of each most visited tile displayed on the new tab page, - e.g. actual thumbnail or placeholder thumbnail. This is recorded for each - most visited item when the NTP is opened. - - - - - dbeam@chromium.org - yyushkina@chromium.org - - The visual type of the most visited item that the user clicked on, e.g. - actual thumbnail or placeholder thumbnail. - - - - - freedjm@chromium.org - feed@chromium.org - - The time spent on the new tab page as measured from when it was loaded or - last brought to the foreground until it was navigated away from or hidden. - Only measured on Android. - - - - - - Removed 01/2019, replaced by NewTabPage.TimeToFirstDraw2 when a bug in how - this was calculated was fixed. - - skym@chromium.org - twellington@chromium.org - - The time from when a new tab page is created until the first pre-draw call - on the main UI containing the search provider logo (if available), fake - search box, most visited tiles, etc. More specifically, this is the time - between NewTabPage's constructor and the first pre-draw pass on - NewTabPageLayout. - - - - - freedjm@chromium.org - feed@chromium.org - - The time from when a new tab page is created until the first pre-draw call - on the root view containing the search provider logo (if available), fake - search box, most visited tiles, articles etc. More specifically, this is the - time between NewTabPage's constructor and the first pre-draw pass on this - root view. This typically means that the fixed UI elements are shown to the - user, but the articles below are not filled in yet. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Records the status of the New Tab page URL when an NTP is opened. - - - - - jkrcal@chromium.org - - Android: The estimated average number of hours between two successive times - when a new tab page is opened. Recorded after each opening of a NTP (and - after updating the model used for the estimate). - - - - - jkrcal@chromium.org - - Android: The estimated average number of hours between two successive times - when the list of content suggestions on a new tab page is shown (i.e. when - the user scrolls below the fold). Recorded after each time the suggestions - are shown (and after updating the model used for the estimate). - - - - - freedjm@chromium.org - feed@chromium.org - - Android: The estimated average number of hours between two successive times - when the user opens a content suggestion or clicks on the "More" - button. Recorded after each time a suggestion or a More button is clicked - (and after updating the model used for the estimate). - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - The number of screenshots that were cached for the visible suggestions on - the Suggested NTP pane. - - - - - - Removed 2016-02 (and not recorded for some time before that). - - Please list the metric's owners. Add more owner tags as needed. - - Given that the user has typed a URL, and given that that specific URL was - visible on the Suggested pane of the NTP, this is the rank that the - Suggested pane had for that URL. - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Actions taken by users of Voice Search on the local New Tab Page on Desktop. - These actions may navigate away from the NTP (e.g. submitting a speech - query), but can also happen without navigating away from the NTP (e.g. - initiating or retrying Voice Search). - - - - - tiborg@chromium.org - yyushkina@chromium.org - chrome-desktop-ntp@google.com - - Errors that occur during Voice Search use on the local New Tab Page on - Desktop. These may be user-induced (e.g. the user's utterance could not be - recognized - no match), or resulting from external circumstances (e.g. - offline, lack of microphone permission). - - - - - dewittj@chromium.org - - The actions taken on notifications, recorded every time they happen. This - histogram will record every single event that happens separately. - - - - - peter@chromium.org - - Records the delay between scheduling a job with the JobScheduler (with a - desired latency of 0ms, in response to a notification click) and receiving - the onStartJob callback. Only measured on Android N and above. - - - - - peter@chromium.org - - Recorded when the Sites channel (which we hope to deprecate) is used as a - fallback, when a site-specific notification channel is expected to exist but - does not. Note, we only log when the sites channel is *used*, not when it is - not used. - - - - - dtrainor@chromium.org - xingliu@chromium.org - - Records the events when the announcement notification is shown, clicked, or - closed. - - - - - - - peter@chromium.org - - Records whether notifications are enabled for Chrome, as the Android app, - for each Web Notification that is being shown to the user. - - - - - peter@chromium.org - - The size, in bytes, of the author-provided data associated with a Web - Notification. Recorded when a persistent Web Notification is being shown by - the developer. - - - - - - Replaced by Notifications.AuthorDataSize in February 2016. - - peter@chromium.org - - The size, in kilobytes, of the author-provided data associated with a Web - Notification. Recorded when a persistent Web Notification is being shown by - the developer. - - - - - hesen@chromium.org - xingliu@chromium.org - - - - Various events when Chrome interacts with Chime notification platform. - Recorded when Chrome registers to Chime service, receives notifications, and - the user interacts with the notification. - - - - - hesen@chromium.org - xingliu@chromium.org - - - - Records the result of Chime notification platform registration. Each device - may have multiple accounts registered. The registration happens right after - opening Chrome. - - - - - tengs@chromium.org - gzadina@google.com - - Records the notification type when a notification interaction occurs. See - suffixes for all event types. ChromeOS only. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of deleting all notification data for given - origins. This happens when notification permissions are revoked for a site. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of deleting notification data from the Web - Notification database that share their tag (replacement identifier) with a - notification that's about to be shown. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of deleting notification data from the Web - Notification database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of deleting all notification data associated - with a Service Worker registration ID. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of destroying the Web Notification database - altogether. - - - - - knollr@chromium.org - peter@chromium.org - adelm@google.com - - Records the age of the oldest notification for an origin. Logged after - handling a push event for that origin. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of opening the Web Notification database - after it has been destroyed in response to data corruption. - - - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of opening the Web Notification database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of reading data of all notifications - associated with a Service Worker from the Web Notification database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of reading resources for a notification from - the Web Notification database. This happens when a previously scheduled - notification has triggered. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of reading resources for a notification from - the Web Notification database. This happens when a scheduled notification is - read from the database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of reading data of a single notification - from the Web Notification database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of writing data for a notification to the - Web Notification database. - - - - - knollr@chromium.org - peter@chromium.org - - Records the result status codes of updating the triggered flag for a - notification in the Web Notification database. This happens after fetching - data and resources for a triggered notification, just before displaying it. - - - - - - Removed July 2015. No longer tracked since M42. - - peter@chromium.org - - Records if the requesting and embedding origins are different when - requesting permission to display Web Notifications. - - - - - - Removed October 2017 (fullscreen notifications feature enabled by default). - - bmalcolm@chromium.org - - Counts the number of times a notification was shown for the various types of - sources. The suffix distinguishes between the window state of the app or - webpage that sent the notification. This will be used to determine whether a - legacy mode is required when we allow apps or webpages to display - notifications over fullscreen content in the future. - - - - - - Removed in July 2020 as the metrics are not needed anymore, and - documentation has been amended as a result of this collection. - - dewittj@chromium.org - peter@chromium.org - - The number of action buttons the developer provided for a notification - created using the extensions notification API. Logged when creating the - notification. - - - - - - Removed in June 2019 because this was measuring risk for a feature that has - now been implemented and shipped. - - peter@chromium.org - - The length, in characters, of the id given to an extension notification. - These can be automatically generated, in which case they will be either 36 - bytes (GUID) or 16 bytes (random data) in length, or provided by the - developer. Measured when the notification is being displayed through the - chrome.notifications.create() extension API. - - - - - - Removed in July 2020 as the metrics are not needed anymore as platforms have - moved to native notifications, for which these metrics were used. - - dewittj@chromium.org - peter@chromium.org - - The type of a notification created using the extensions notification API. - Logged when creating the notification. - - - - - - - thomasanderson@chromium.org - - Whether the notification server supports the capability in question. (Linux - only) Logged when the proxy to /org/Freedesktop/Notifications is set up - successfully, which happens at most once on startup. - - - - - - Removed Nov 2019 because the histogram data was not being used. - - knollr@chromium.org - peter@chromium.org - - Whether a click on a notification header caused it to collapse, expand or - had no effect at all. Logged when clicking on the notification header. - - - - - - Removed Nov 2016 in favor of Notifications.LoadFileSize.* - - peter@chromium.org - The number of bytes loaded for a Web Notification icon. - - - - - Removed Nov 2016 in favor of Notifications.LoadFailTime.* - - peter@chromium.org - - The number of milliseconds it took to fail loading an icon for a Web - Notification. - - - - - - Removed Nov 2016 in favor of Notifications.LoadFinishTime.* - - peter@chromium.org - - The number of milliseconds it took to finish successfully loading an icon - for a Web Notification. - - - - - - Removed Nov 2016 in favor of Notifications.LoadScaleDownTime.* - - peter@chromium.org - - The number of milliseconds it took to scale down an icon for a Web - Notification. - - - - - thomasanderson@chromium.org - - The status code for initializing NotificationPlatformBridgeLinux. (Linux - only) Logged on each start up. - - - - - - Removed in June 2019. - - - - peter@chromium.org - - The number of milliseconds it took to fail loading an icon/image for a Web - Notification. - - - - - - Removed in June 2019. - - - - peter@chromium.org - - The number of bytes loaded for a Web Notification icon/image. - - - - - - Removed in June 2019. - - - - peter@chromium.org - - The number of milliseconds it took to finish successfully loading an - icon/image for a Web Notification. - - - - - - Removed in June 2019. - - - - peter@chromium.org - - The number of milliseconds it took to scale down an icon/image for a Web - Notification. - - - - - finnur@chromium.org - - The execute status of a ComServerModule class instance. Logged whenever a - notification_helper process is launched by Windows. - - - - - chengx@chromium.org - finnur@chromium.org - - The primary execute status of NotificationActivator::Activate. Logged - whenever a notification_helper process is launched by Windows. - - - - - chengx@chromium.org - finnur@chromium.org - - The secondary execute status of NotificationActivator::Activate. Logged - whenever a notification_helper process is launched by Windows. - - - - - - Removed 06/2018. Replaced by NotificationActivatorPrimaryStatus and - NotificationActivatorSecondaryStatus. - - chengx@chromium.org - - The execute status of NotificationActivator::Activate. Logged whenever a - notification_helper process is launched by Windows. - - - - - finnur@chromium.org - - The runtime of the notification_helper server process. This process is - created when a notification is activated from the Windows Action Center. - Once created, this process does some COM class registration work, so that - Windows can call certain APIs to handle the notification activation. Upon - finishing the API calls, Windows signals this process to exit. - - - - - tengs@chromium.org - - The number of times a notification was added for the various types of - sources. - - - - - knollr@chromium.org - peter@chromium.org - - The number of notifications that got deleted from the NotificationDatabase - after the notification permissions got revoked. - - - - - dewittj@chromium.org - - The actions taken on notifications, recorded once per notification, when it - is closed. This differs from the Notifications.Actions histogram in that - multiple events of the same type on a single notification will only record a - single UMA event. - - - - - peter@chromium.org - - The number of action buttons the developer provided for a persistent Web - Notification. Logged whenever showNotification is called. - - - - - - Removed 01/2016, no longer used. - - peter@chromium.org - deepak.m1@samsung.com - - Recorded when the data associated with a persistent Web Notification gets - deleted. The value will be true if data deletion succeeded, and false if - there was an error. - - - - - peter@chromium.org - deepak.m1@samsung.com - - Recorded delivery status for persistent notification clicks to a Service - Worker when handling a click on a persistent WebNotification has finished. - - - - - peter@chromium.org - knollr@chromium.org - - Records delivery status for persistent notification close events sent to a - Service Worker when the event has been handled. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the various events when running the background task in notification - scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the number of notifications shown in each background task run. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the hour (0-23) when the notification scheduler background task - starts. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the initialization result of icon database for the notification - scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the database operation result (except initialization) of icon - database for the notification scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the number of records of icon database for the notification - scheduling system when the icon database is initialized. - - - - - - - xingliu@chromium.org - hesen@chromium.org - - Records events for inline helpful/unhelpful action buttons on the - notification when the buttons are shown or clicked. - - - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the number of impression records in impression db right after the - impression database is initialized. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records various events in impression history tracker in notification - scheduling system when the user interacts with the notification. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the initialization result of impression database for the - notification scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the database operation result (except initialization) of impression - database for the notification scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the number of records of impression database for the notification - scheduling system when the impression database is initialized. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the initialization result of notification database for the - notification scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the database operation result (except initialization) of - notification database for the notification scheduling system. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the number of records of notification database for the notification - scheduling system when the notification database is initialized. - - - - - - - xingliu@chromium.org - hesen@chromium.org - - Records life cycle events for a scheduled notification, when notification is - scheduled, shown or encountering any error. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the result of png icon converter decoding process in icon store for - the notification scheduling system. It will be logged typically when - scheduling system trying to display the notification to the client - the - icon store will load entries, and decode icons to PNG format for delivery. - - - - - xingliu@chromium.org - hesen@chromium.org - - Records the result of png icon converter encoding process in icon store for - the notification scheduling system. It will be logged typically when the - client scheduled notification with icons - the icon store will then encode - icons to string and store them in protodb. - - - - - - - xingliu@chromium.org - dtrainor@chromium.org - - Records the type of user action when the user interacts with notification - sent from notification scheduler system. - - - - - knollr@chromium.org - peter@chromium.org - - Delay between the expected and actual display time of a notification. - Recorded just before displaying a notification with a show trigger. - - - - - - Removed July 2020 as the Origin Trial is ramping down. - - knollr@chromium.org - peter@chromium.org - - Indicates if the notificaiton has a show trigger. This is recorded before a - notification is written to the database if the notification triggers feature - is enabled. - - - - - - Removed July 2020 as the Origin Trial is ramping down. - - knollr@chromium.org - peter@chromium.org - - The specified delay until the notification is displayed. This is recorded - before writing a notification with a valid show trigger to the database. - - - - - - - peter@chromium.org - knollr@chromium.org - thomasanderson@chromium.org - - Indicates if Chrome is using system notifications or the Chrome notification - center. Logged on each start up. - - - - - finnur@chromium.org - peter@chromium.org - chengx@chromium.org - - The status of Activation requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever an activation from a notification occurs. - - - - - finnur@chromium.org - peter@chromium.org - - The status of Close requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever a notification is closed. - - - - - finnur@chromium.org - peter@chromium.org - - The HRESULT returned by the Windows Action Center, when trying to create a - toast manager fails. This provides a more detailed error in the cases the - histogram Notifications.Windows.DisplayStatus reported - CREATE_TOAST_NOTIFIER_WITH_ID_FAILED. - - - - - finnur@chromium.org - peter@chromium.org - - The HRESULT returned by the Windows Action Center, when showing a - notification fails. - - - - - finnur@chromium.org - peter@chromium.org - - The status of Display requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever a notification is displayed. For a more detailed - error about CREATE_TOAST_NOTIFIER_WITH_ID_FAILED and SHOWING_TOAST_FAILED, - see Notification.Windows histograms CreateToastManagerErrorCode and - ShowFailedErrorCode (respectively). - - - - - finnur@chromium.org - peter@chromium.org - - The status of decoding launch ids while processing a GetDisplayed requests - in NotificationPlatformBridgeWin (Windows only). Logged whenever a request - to retrieve all displayed notifications comes in. - - - - - finnur@chromium.org - peter@chromium.org - - The status of GetDisplayedStatus requests in NotificationPlatformBridgeWin - (Windows only). Logged whenever a request to retrieve all displayed - notifications comes in. - - - - - finnur@chromium.org - peter@chromium.org - - The status of GetNotificationLaunchId requests in - NotificationPlatformBridgeWin (Windows only). Logged whenever a request to - decode the GetNotificationLaunchId comes in. - - - - - finnur@chromium.org - peter@chromium.org - - The policy value provided by get_Setting in NotificationPlatformBridgeWin - (Windows only). Logged whenever a request to show a notification comes in. - - - - - finnur@chromium.org - peter@chromium.org - - The return value of get_Setting calls in NotificationPlatformBridgeWin - (Windows only). Logged whenever a request to show a notification comes in. - - - - - finnur@chromium.org - peter@chromium.org - - The status of HandleEvent requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever a notification event is being handled. - - - - - finnur@chromium.org - peter@chromium.org - - The status of History requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever history is requested for notifications. - - - - - - Obsolete 10/2018 as we no long record this metric. - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - Amount of time taken to destroy a NotificationImageRetainer object when the - image directory is valid. - - - - - - Obsolete 10/2018 as we no long record this metric. - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - Amount of time taken to initialize the image retainer directory. - - - - - chengx@chromium.org - finnur@chromium.org - - Used to indicate the status of decoding an input launch id string (Windows - only). Logged whenever a notification event is being handled. - - - - - - Obsolete 06/2020 as we no long record this metric. - - chengx@chromium.org - peter@chromium.org - - The status of OnDismissed requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever a dismiss event is handled. - - - - - chengx@chromium.org - peter@chromium.org - - The status of OnFailed requests in NotificationPlatformBridgeWin (Windows - only). Logged whenever a failed event is handled. - - - - - - Replaced with Notifications.Windows.SetReadyCallbackStatus2 which is not - skewed. - - finnur@chromium.org - peter@chromium.org - - The status of SetReadyCallback requests in NotificationPlatformBridgeWin - (Windows only). Logged once at startup. - - - - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - The status of SetReadyCallback requests in NotificationPlatformBridgeWin - (Windows only). Logged once at startup. - - - - - finnur@chromium.org - peter@chromium.org - - The HRESULT returned by the Windows Action Center, when trying to create a - toast manager fails. This provides a more detailed error in the cases the - histogram Notifications.Windows.DisplayStatus reported SHOWING_TOAST_FAILED. - - - - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - Used to indicate the status of start menu shortcut (Windows only). Logged - whenever a notification display attempt is made. - - - - - - Removed 06/2018. Replaced with Notifications.Windows.StartMenuShortcutStatus - where typo is fixed. - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - Used to indicate the status of start menu shortcut (Windows only). Logged - whenever a notification display attempt is made. - - - - - - Removed 12/2018 as this is no longer needed. - - chengx@chromium.org - finnur@chromium.org - peter@chromium.org - - Used to indicate the reason why toast activator CLSID in shortcut is - different from the one retrieved from the installer (Windows only). Logged - whenever this mismatch is detected during a notification display attempt. - - - - - - Removed 05/2018 as this is no longer needed. - - chengx@chromium.org - peter@chromium.org - - Used to indicate the code path where the user profile manager shows up - during startup (Windows only). Logged whenever a notification event is being - handled. - - - - - peter@chromium.org - rsesek@chromium.org - - Mac only. Records the different events of a Notification XPC connection. - These are recorded by monitoring the different error callbacks provided by - the XPC connection object. - - - - - - Obsoleted in Jan 2019 - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated downstream throughput (in - kilobits per second) and the observed downstream throughput (in kilobits per - second). Downstream throughput estimated by the network quality estimator at - the time of navigation start is compared with the downstream throughput - observed during the specified time interval following the start of the - navigation. - - - - - - Obsoleted in Jan 2019 - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated effective connection type and - the observed effective connection type. Effective connection type is - estimated by the network quality estimator at the time of navigation start - is compared with the effective connection type observed during the specified - time interval following the start of the navigation. - - - - - - Obsoleted in Jan 2019 - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated HTTP RTT and the observed HTTP - RTT. HTTP RTT estimated by the network quality estimator at the time of - navigation start is compared with the HTTP RTT observed during the specified - time interval following the start of the navigation. - - - - - - Obsoleted in Jan 2019 - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated transport RTT and the observed - transport RTT. Transport RTT estimated by the network quality estimator at - the time of navigation start is compared with the transport RTT observed - during the specified time interval following the start of the navigation. - - - - - - Obsoleted in October 2018 - - devdeepray@chromium.org - tbansal@chromium.org - - The value of the downstream throughput used to compute the bandwidth delay - product. The 80th percentile throughput observation is used to calculate the - bandwidth delay product. This gets recorded everytime the BDP is computed. - - - - - - Obsoleted in October 2018 - - devdeepray@chromium.org - tbansal@chromium.org - - The value of the TransportRTT used to compute the bandwidth delay product. - The 20th percentile TransportRTT observation is used to calculate the - bandwidth delay product. This gets recorded everytime the BDP is computed. - - - - - - Obsoleted in October 2018 - - devdeepray@chromium.org - tbansal@chromium.org - - An estimate of the bandwidth delay product which is computed on main-frame - requests. It is calculated using the 80th percentile throughput and 20th - percentile TransportRTT values whenever |ComputeEffectiveConnectionType| is - called and the throughput and TransportRTT estimates are available. - - - - - tbansal@chromium.org - bengr@chromium.org - - Records if the cached network quality (from memory or from a persistent - source) was available. Recorded right after connection change event. - - - - - - Obsoleted April 2020. - - tbansal@chromium.org - - Cellular signal strength level reported by the device at the time of ECT - computation. Recorded only on cellular networks, and only when the value is - available. The value ranges between 0 and 4 (both inclusive). - - - - - tbansal@chromium.org - - Number of buckets by which effective connection type was reduced or capped - due to low cellular signal strength. Recorded only on cellular networks, and - only when the value of the effective connection typed is capped. - - - - - tbansal@chromium.org - bengr@chromium.org - - Whether the signal strength for the cellular network was available or not. - Recorded right before a connection change event. Recorded only on cellular - connections on Android platform. - - - - - - Obsoleted. - - tbansal@chromium.org - bengr@chromium.org - - Difference between the minimum and the maximum received signal strength - since the last connection change event. Recorded only on cellular - connections on Android platform when the cellular signal strength was - available. Recorded right before a connection change event. - - - - - - Replaced by NQE.CellularSignalStrength.LevelAvailable in June 2017. - - tbansal@chromium.org - bengr@chromium.org - - Whether the signal strength for the cellular network was available or not. - Recorded right before a connection change event. Recorded only on cellular - connections on Android platform. - - - - - - Replaced by NQE.CellularSignalStrength.LevelDifference in June 2017. - - tbansal@chromium.org - bengr@chromium.org - - Difference between the minimum and the maximum received signal strength - since the last connection change event. Recorded only on cellular - connections on Android platform when the cellular signal strength was - available. Recorded right before a connection change event. - - - - - - Obsoleted in Apr 2020. - - jfwang@chromium.org - tbansal@chromium.org - - Records the count of in-flight requests causing the peak queueing delay - within the current ongoing measurement period. These samples are bucketized - into 10 peak queueing delay levels. This is emitted at the end of the - current measurement period. - - - - - - Obsoleted in April 2020. - - jfwang@google.com - tbansal@chromium.org - - Records the score that evaluates the mapping between the count of in-flight - requests to the peak observed queueing delay. The score is the percentage of - total samples that follow the rule 'the more in-flight requests, the higher - peak queueing delay' when a new peak queueing delay mapping sample is - acquired. This is emitted at the end of the current measurement period and - only when there are at least 10 cached mapping samples. - - - - - rockot@google.com - zhongyi@chromium.org - - When ConnectivityMonitor establishes that the current default network may be - failing and is Wi-Fi, it asks the operating system to activate a mobile - network for subsequent use. Whenever the system's default network changes, - this logs the relationship between the new default network and the network - preemptively activated by ConnectivityMonitor, if any. - - - - - rockot@google.com - zhongyi@chromium.org - - The Network Quality Estimator (NQE) observes network activity to look for - connectivity issues. If it begins to observe failures on a previously - functioning network, it tracks the time at which the failures were first - observed. If the device subsequently switches its default network to - different network (or offline), this histogram logs the number of - milliseconds elapsed since the original failures were observed. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - - This metric is recorded when the network quality change notification is - received by content and before the network quality change is notified to the - renderers. Records true if the notified network quality change is - meaningfully different from the last network quality notified to the - renderers. - - - - - - Obsoleted in December 2017. - - tbansal@chromium.org - bengr@chromium.org - - Records estimated network quality (estimated RTT, estimated downlink - bandwidth), resource load size, and the resource load time in a single UMA - sample. This metric is recorded randomly when a resource load finishes. Each - sample in this sparse histogram consists of multiple metrics (each occupying - few bits in the sample). The data in the histogram would be analyzed using - custom scripts. A sample is recorded only when the resource size is between - 0 Kilobits (inclusive) and 128 Kilobits (exclusive). - - - - - - Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. - - bengr@chromium.org - tbansal@chromium.org - - Difference between the actual RTT observation and the estimated RTT. This - metric is recorded on every request when the actual observation is higher - than the estimated value. - - - - - - Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. - - bengr@chromium.org - tbansal@chromium.org - - Difference between the estimated RTT and the actual RTT observation. This - metric is recorded on every request when the estimated value is higher than - the actual observation. - - - - - tbansal@chromium.org - src/net/nqe/OWNERS - - Effective connection type estimated by the network quality estimator. - Recorded every time the effective connection type is computed. - - - - - tbansal@chromium.org - src/net/nqe/OWNERS - - Rough estimate of the computed end-to-end round trip time. Recorded by the - network quality estimator every time the effective connection type is - computed. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - bengr@chromium.org - - This histogram records whether the estimate of the network quality metric - was available or not. Recorded at every main frame request. - - - - - - Obsoleted in February 2018. - - bengr@chromium.org - tbansal@chromium.org - - Records the estimate of the downlink bandwidth (in Kbps) provided by the - external estimate provided. Recorded every time the external estimate - provider provides a valid downlink bandwidth estimate to the network quality - estimator. - - - - - - Obsoleted in February 2018. - - bengr@chromium.org - tbansal@chromium.org - - Records the estimate of the RTT provided by the external estimate provided. - Recorded every time the external estimate provider provides a valid RTT - estimate to the network quality estimator. - - - - - - Obsoleted in February 2018. - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the HTTP RTT estimated by the external - estimate provider and the observed HTTP RTT. The HTTP RTT estimated by the - external estimate provider at the time of navigation start is compared with - the HTTP RTT observed during the specified time interval following the start - of the navigation. - - - - - - Obsoleted in February 2018. - - bengr@chromium.org - tbansal@chromium.org - - Records the interaction (availability and query count) of Network Quality - Estimator with external estimates provider. Logged on network change events, - everytime external estimate provider is queried for an updated estimate, and - when it proactively notifies that an updated estimate is available. - - - - - - Obsoleted in August 2017 - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the fastest round-trip-time, before a connectivity change - is detected. - - This metric is recorded when a connectivity change is detected. This will - miss data from users whose connection type never changes and will be biased - to users whose connection type changes frequently. - - - - - - Obsoleted in April 2020. - - tbansal@chromium.org - bengr@chromium.org - - Number of Kbps observations indexed by the source of the observation. - Recorded by the network quality estimator every time a new observation is - made or synthesized. - - - - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the downstream peak throughput (in kilobits per second). - Recorded by the network quality estimator every time the effective - connection type is computed. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - bengr@chromium.org - - Downstream throughput observation received or synthesized by network quality - estimator. Observations from different sources are recorded in separate - histograms. - - - - - - Obsoleted in M84. - - tbansal@chromium.org - bengr@chromium.org - - Effective connection type estimated by network quality estimator. Suffixed - with the connection type reported by the operating system. - - This metric is recorded on main-frame requests. - - - - - - Obsoleted in M81. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the downstream peak throughput at different percentiles. - - This metric is recorded on main-frame requests. - - - - - - Obsoleted in M84. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the URLRequest layer at - different percentiles. - - This metric is recorded on main-frame requests. - - - - - - Obsoleted in M81. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the transport layer at - different percentiles. - - This metric is recorded on main-frame requests. - - - - - tbansal@chromium.org - bengr@chromium.org - - Whether the NetworkID (SSID of the Wi-Fi network, or the MCC/MNC operator of - the cellular network) was available or not. Recorded only on Wi-Fi and - cellular networks. Recorded right after the connection type changes. - - - - - - Obsoleted in August 2017 - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of downstream peak throughput, before a connectivity change - is detected. - - This metric is recorded when a connectivity change is detected. This will - miss data from users whose connection type never changes and will be biased - to users whose connection type changes frequently. - - - - - - Obsoleted in Apr 2020. - - tbansal@chromium.org - ryansturm@chromium.org - - Records the duration of the time period for which there was at least one - peer to peer active connection. Recorded when the count of peer to peer - connections drop from a non-zero value to a zero value. - - - - - tbansal@chromium.org - bengr@chromium.org - - Number of times the network quality prefs were read by the network quality - estimator. - - - - - tbansal@chromium.org - bengr@chromium.org - - Count of the number of network IDs in the prefs read by the network quality - estimator. - - - - - tbansal@chromium.org - bengr@chromium.org - - Number of times the network quality prefs were written by the network - quality estimator. - - - - - - Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. - - bengr@chromium.org - tbansal@chromium.org - - Ratio of the estimated RTT to the actual RTT observation multiplied by 100. - - - - - - Obsoleted in M-77. - - tbansal@chromium.org - bengr@chromium.org - - Count of the number of times renderers were notified of the changes in the - network quality estimator. This metric makes sense to compare in frequency - relative to other events like the number of page loads or the number of - renderers seen. It is expected that we will see at least 1 notification per - renderer (on average), and less than 100. - - - - - - Removed 01/2018. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the URLRequest layer at - different percentiles. - - This metric is recorded immediately after a connectivity change is detected. - The metric name is suffixed with the connection type before the connectivity - change was detected. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - HTTP RTT observation received by the network quality estimator. Recorded - when the request is detected as hanging. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - HTTP RTT observation received by the network quality estimator. Recorded at - the beginning of a request if the request is detected as not hanging because - the observed HTTP RTT was comparable to the end to end RTT estimate. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - HTTP RTT observation received by the network quality estimator. Recorded - when the request is detected as not hanging because it was comparable to the - HTTP RTT estimate. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - HTTP RTT observation received by the network quality estimator. Recorded - when the request is detected as not hanging because the RTT value was lower - than the minimum threshold RTT needed to be categorized as a hanging - request. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - HTTP RTT observation received by the network quality estimator. Recorded - when the request is detected as not hanging because it was comparable to the - transport RTT estimate. - - - - - tbansal@chromium.org - bengr@chromium.org - - Number of RTT observations indexed by the source of the observation. - Recorded by the network quality estimator every time a new observation is - made or synthesized. - - - - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the round trip time at the URLRequest layer. Recorded by - the network quality estimator every time the effective connection type is - computed. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - bengr@chromium.org - - RTT observation received or synthesized by network quality estimator. - Observations from different sources are recorded in separate histograms. - - - - - - Replaced in May 2016 by NQE.MainFrame.RTT.* metrics. - - bengr@chromium.org - tbansal@chromium.org - - RTT observations at the URLRequest layer made by network quality estimator, - recorded on every request. - - - - - tbansal@chromium.org - mcrouse@chromium.org - - Recorded as true when the signal strength of the current network is queried. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - Count of the requests that were marked as hanging by the heuristic algorithm - in the throughput analyzer in the network quality estimator. A sample is - recorded everytime the heuristic algorithm is run. - - - - - - Obsoleted in Feb 2019. - - tbansal@chromium.org - - Count of the requests that were not marked as hanging by the heuristic - algorithm in the throughput analyzer in the network quality estimator. A - sample is recorded everytime the heuristic algorithm is run. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - - Throughput observation made by network quality estimator, and eventually - discarded because the window (over which the througput was computed) was - detected as hanging. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - - Throughput observation made by network quality estimator, and used when the - window (over which the througput was computed) was detected as not hanging. - - - - - - Removed 01/2018. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the transport layer at - different percentiles. - - This metric is recorded immediately after a connectivity change is detected. - The metric name is suffixed with the connection type before the connectivity - change was detected. This will miss data from users whose connection type - never changes and will be biased to users whose connection type changes - frequently. - - - - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the transport layer. - Recorded by the network quality estimator every time the effective - connection type is computed. - - - - - - Obsoleted in August 2017. - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated HTTP RTT and the observed HTTP - RTT. HTTP RTT estimated by the network quality estimator at the time of - navigation start is compared with the HTTP RTT observed during the specified - time interval following the start of the navigation. Both the estimated and - the observed RTT are computed using average algorithm that assigns equal - weight to all observations. - - - - - - Obsoleted in August 2017. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the URLRequest layer - computed using average algorithm that assigns equal weight to all - observations. - - This metric is recorded on main-frame requests. - - - - - - Obsoleted in August 2017. - - tbansal@chromium.org - bengr@chromium.org - - Records the difference between the estimated HTTP RTT and the observed HTTP - RTT. HTTP RTT estimated by the network quality estimator at the time of - navigation start is compared with the HTTP RTT observed during the specified - time interval following the start of the navigation. Both the estimated and - the observed RTT are computed using weighted average algorithm. - - - - - - Obsoleted in August 2017. - - bengr@chromium.org - tbansal@chromium.org - - Rough estimate of the computed round trip time at the URLRequest layer - computed using weighted average algorithm. - - This metric is recorded on main-frame requests. - - - - - - Obsoleted April 2020. - - tbansal@chromium.org - - Wifi signal strength level reported by the device at the time of ECT - computation. Recorded only on Wifi networks, and only when the value is - available. The value ranges between 0 and 4 (both inclusive). - - - - - tbansal@chromium.org - bengr@chromium.org - - Whether the signal strength for the Wifi network was available or not. - Recorded right before a connection change event. Recorded only on Wifi - connections on Android platform. - - - - - - Obsoleted in M81. - - tbansal@chromium.org - bengr@chromium.org - - Difference between the minimum and the maximum received signal strength - since the last connection change event. Recorded only on Wifi connections on - Android platform when the Wifi signal strength was available. Recorded right - before a connection change event. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - - Removed 10/2011. No longer tracked, replaced with NewTabPage.DefaultPageType - - Please list the metric's owners. Add more owner tags as needed. - The default pane when the NTP is first opened. - - - - - Removed 10/2011. No longer tracked, replaced with - NewTabPage.SelectedPageType - - Please list the metric's owners. Add more owner tags as needed. - The pane selected when the user switches panes in the NTP. - - - - - Long removed. - - knn@chromium.org - - This histogram records whether the account ID is actually an email if we - detect an account that has an account ID but not email. - - - - - - Long removed. - - knn@chromium.org - - This histogram records the account ID migration status from email to GAIA ID - if we detect an account that has an account ID but not email. - - - - - - Long removed. - - tbarzic@chromium.org - - Failure reason of final OAuth2 access token retrieval call during Chrome OS - login. - - - - - - Long removed. - - tbarzic@chromium.org - - Retry reason of failed OAuth2 access token retrieval call during Chrome OS - login. - - - - - - Removed 2015-05-22. Replaced by Signin.ListAccountsFailure. - - zelidrag@chromium.org - - Failure reason of final ListAccounts call failure during Chrome OS login. - This data is now included in Signin.ListAccountsFailure. - - - - - - Removed 2015-05-22. Replaced by Signin.ListAccountsRetry. - - zelidrag@chromium.org - - Retry reason of failed ListAccounts call during Chrome OS login. This data - is now included in Signin.ListAccountsRetry. - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Failure reason of MergeSession call during Chrome OS login, Chrome Signin or - account addition. On all OSes as of M44 (previously CrOS only). - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Retry reason of failed MergeSession call during Chrome OS login, Chrome - Signin or account addition. On all OSes as of M44 (previously CrOS only). - - - - - - Long removed. - - tbarzic@chromium.org - - Failure reason of final OAuthLogin (with SID+LSID) call during Chrome OS - login. - - - - - - Long removed. - - tbarzic@chromium.org - - Retry reason of failed OAuthLogin (with SID+LSID) call during Chrome OS - login. - - - - - - Removed 2015-05-22 - - zelidrag@chromium.org - - Failure reason of final OAuthLogin (with uber token) call during Chrome OS - login. This data is now (M44+) included in Signin.UberTokenFailure. - - - - - - Removed 2015-05-22 - - zelidrag@chromium.org - - Retry reason of failed OAuthLogin (with uber token) call during Chrome OS - login. This data is now (M44+) included in Signin.UberTokenRetry. - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Outcome of Chrome OS GAIA cookie post-merge session verification process. It - measures how often /MergeSession request collided with browser session - restore process resulting in partially authenticated primary GAIA session. - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Outcome of Chrome OS GAIA cookie pre-merge session verification process. It - measures how often we need to perform /MergeSession request to - re-authenticated exisitng user with GAIA. - - - - - - Long removed. - - knn@chromium.org - - Only applicable on M47 on Android. Measure the frequency of a suppressed - error state when the account is not seeded. - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - Outcome of Chrome OS GAIA cookie session restore process. - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - How long it takes for the session restore to fail. - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - How long it takes for the session restore to finish succeessfully. - - - - - davidbienvenu@chromium.org - fdoray@chromium.org - - Incremented each time a mouse event is handled by a window that is marked as - occluded. This number should be 0 or very close to 0. It should be much less - than the number of times a window is mark occluded - - WindowOcclusionChanged.Occluded. - - - - - sinansahin@google.com - twellington@chromium.org - - For OfflineIndicatorV2, records whether the native browser controls can be - animated and whether the omnibox is focused. Recorded when the device goes - offline. - - - - - sinansahin@google.com - twellington@chromium.org - - For OfflineIndicatorV2, records whether the native browser controls can be - animated and whether the omnibox is focused. Recorded when the device goes - online. - - - - - dimich@chromium.org - jianli@chromium.org - - Records events related to click through rate (CTR) calculation for Offline - Indicator UI. The CTR can be calculated by computing Clicked/Displayed. - - - - - sinansahin@google.com - twellington@chromium.org - - The duration the offline indicator was shown. Recorded when the offline - indicator hides. - - - - - jianli@chromium.org - - Number of accesses to the offline page since its creation. This is reported - when the offline page was deleted. - - - - - jianli@chromium.org - offline-dev@chromium.org - - Logs the UI location from which an offline page was launched. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Counts the number of times an offline page is accessed. Events are reported - per offline pages namespace. - - - - - - Removed 2016-10, and replaced by OfflinePages.AggregatedRequestResult2. - - dimich@chromium.org - jianli@chromium.org - Result of servicing requests that may contain offline page. - - - - dimich@chromium.org - jianli@chromium.org - offline-dev@chromium.org - Result of servicing requests that may contain offline page. - - - - - Removed 2017-10, and replaced by - OfflinePages.ArchiveManager.ArchiveDirsCreationResult2 with suffixes for - temporary and persistent pages. - - dimich@chromium.org - - This is recorded every time the archive directory is being created. It - doesn't include the case which the archive directory exists. - - - - - dimich@chromium.org - offline-dev@chromium.org - - This is recorded every time the archive directory is being created. It - doesn't include the case which the archive directory exists. It has suffixes - indicating results for temporary or persistent archives directories. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - This is recorded every time the auto-fetch complete notification is shown or - interacted with. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - This is recorded every time the auto-fetch in-progress notification is shown - or interacted with. - - - - - - Removed in M61. - - chili@chromium.org - The error codes that caused a page load failure. - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - Reason for the Chrome Custom Tabs API prerender call to be ignored. - - There are several causes for the Chrome Custom Tabs API calls to be ignored, - this tracks the potential causes so we can see how often the prerenderer - doesn't prerender due to these being switched off. Since this is checked - elsewhere (CCTAPI), this only catches the user switching off the third party - cookies or navigation prediction after the CCT API has checked. - - - - - petewil@chromium.org - offline-dev@chromium.org - - Effective connection type at the start of an offlining attempt for an - attempt that eventually failed. - - This metric is recorded for RequestCoordinator::SavePageLater API calls. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Effective connection type when pausing one or more background loads is - requested. - - This metric is recorded for RequestCoordinator::PauseRequests API calls. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Effective connection type when removing one or more background loads is - requested. - - This metric is recorded for RequestCoordinator::RemoveRequests API calls. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Effective connection type when resuming one or more background loads is - requested. - - This metric is recorded for RequestCoordinator::ResumeRequests API calls. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Effective connection type when a background load is requested. - - This metric is recorded for RequestCoordinator::SavePageLater API calls. - - - - - chili@chromium.org - offline-dev@chromium.org - - Status code of background offlining requests at the final step. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests available for processing when - processing starts immediately (vs. scheduled). This is for non-svelte - devices (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests available for processing when - processing starts immediately (vs. scheduled). This is for svelte devices - (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests unavailable for processing when - processing starts immediately (vs. scheduled). This is for non-svelte - devices (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests unavailable for processing when - processing starts immediately (vs. scheduled). This is for svelte devices - (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Status of attempt to immediately start offlining a page in the background - while application is still concurrently using the foreground. This may be - attempted when an web page download is initially requested or resumed. - - - - - chili@chromium.org - offline-dev@chromium.org - - The combined http and net error codes that caused a page load failure. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Status code of background offlining (loading and saving) requests. - - - - - petewil@chromium.org - offline-dev@chromium.org - - Whether any previews were selected for a page we were asked to make - available offline. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of started attempts by failed background load requests. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of started attempts by successful background load requests. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - True if all requested CSS was loaded when a background page loaded. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - True if all requested images were loaded when a background page loaded. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - True if all requested XHRs were completed when a background page loaded. - - - - - chili@chromium.org - offline-dev@chromium.org - Whether the save page result came from chrome custom tabs. - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests available for processing when - background scheduled processing starts. This is for non-svelte devices - (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests available for processing when - background scheduled processing starts. This is for svelte devices (where - svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests unavailable for processing when - background scheduled processing starts. This is for non-svelte devices - (where svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Number of queued background load requests unavailable for processing when - background scheduled processing starts. This is for svelte devices (where - svelte is determined by base::SysInfo::IsLowEnd()). - - - - - dougarnett@chromium.org - offline-dev@chromium.org - Time from background request until it was canceled. - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Time from background request until it was successfully saved. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Time from background request until processing it was first started. This is - for non-svelte devices. - - - - - dougarnett@chromium.org - offline-dev@chromium.org - - Time from background request until processing it was first started on svelte - device. Svelte is determined by base::SysInfo::IsLowEnd(). - - - - - - Removed in M61. - - dougarnett@chromium.org - offline-dev@chromium.org - - Connection type when prerenderer reports Unsupported Scheme error. - - To give insight about Unsupported Scheme errors that may be due to lost - network connection (as data URL used for rendering an error page will - manifest as an Unsupported Scheme error by the prerenderer). - - - - - - Removed 2/2018. No longer used. - - jianli@chromium.org - Number of offline pages that are deleted in a batch. - - - - - Removed in M65. - - jianli@chromium.org - - Total size, in kilobytes, of all offline pages that are deleted in a batch. - - - - - - Removed on 6/2019. No longer considered useful. - - carlosk@chromium.org - fgorski@chromium.org - - Reports whether a web page complies with all requirements for it to be - allowed to be saved as an offline page. This is reported only on Android, - after a successful main frame navigation is finished. - - - - - harringtond@chromium.org - offline-dev@chromium.org - Number of thumbnails removed by the thumbnail cleanup task. - - - - - Removed 3/2016, and replaced by OfflinePages.ClearAllStatus2. - - jianli@chromium.org - Status code of wiping out the offline page data. - - - - - Removed a long time ago, marked as expired for M83. - - jianli@chromium.org - Status code of wiping out the offline page data. - - - - - Removed as of Jan 2018, replaced by - OfflinePages.ClearTemporaryPages.BatchSize. - - dimich@chromium.org - - Number of pages deleted in a batch during one clear-storage request. - - - - - - Removed in Oct 2017 and replaced by OfflinePages.ClearStoragePreRunUsage2 as - it was reporting data in bytes instead of the expected MiB. - - petewil@chromium.org - - The total storage size used by all offline pages from a specific client - namespace. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - The total disk storage size used by all offline pages from a specific client - namespace. - - - - - - Removed as of Jan 2018, replaced by OfflinePages.ClearTemporaryPages.Result. - - dimich@chromium.org - Result of asking storage manager to clear storage. - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of pages deleted in a batch in one clear storage task. - - - - - romax@chromium.org - offline-dev@chromium.org - - Result of clearing temporary pages to release storage space. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - When a temporary page is deleted due to storage pressure, reports the time - since its creation. This metric should be useful to track the occurrence of - "content thrashing", when automatically created temporary pages - are forcing the deletion of recently saved temporary pages. - - - - - - Removed 12/2017, replaced by OfflinePages.ConsistencyCheck.Temporary.Result - and OfflinePages.ConsistencyCheck.Persistent.Result. - - romax@chromium.org - - Whether an attempt to delete archive files without metadata was successful. - - - - - - Removed 12/2017, replaced by OfflinePages.ConsistencyCheck.Temporary.Result - and OfflinePages.ConsistencyCheck.Persistent.Result. - - romax@chromium.org - - Whether an attempt to delete pages without archives was successful. - - - - - - Removed 11/2016, replaced by - OfflinePages.Consistency.DeletePagesMissingArchiveFileResult. - - romax@chromium.org - - Whether an attempt to expire pages without archives was successful. - - - - - - Removed 12/2017, replaced by - OfflinePages.ConsistencyCheck.Temporary.PagesMissingDbEntryCount and - OfflinePages.ConsistencyCheck.Persistent.PagesMissingDbEntryCount. - - romax@chromium.org - - Number of archives without metadata entry when checking consistency. - - - - - - Removed 12/2017, replaced by - OfflinePages.ConsistencyCheck.Temporary.PagesMissingArchiveFileCount and - OfflinePages.ConsistencyCheck.Persistent.PagesMissingArchiveFileCount. - - romax@chromium.org - - Number of offline pages without archive file when checking consistency. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of files which are deleted during legacy dir clearing since they have - no associated DB entry and live in private directory. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of DB entries (in persistent namespaces) that have been missing their - files for longer than 365 days, and deleted during maintenance task. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of files that are found missing during maintenance task, which is - also the number of DB entries that are updated with valid file missing time. - - - - - - Removed 04/2018, since saving public offline pages to external download - directory needs a different consistency check strategy. - - romax@chromium.org - - Number of persistent offline pages without archive file when checking - consistency. It will only be reported if the number is larger than 0. - - - - - - Removed 04/2018, since saving public offline pages to external download - directory needs a different consistency check strategy. - - romax@chromium.org - - Number of archives without database entry when checking persistent page - consistency. It will only be reported if the number is larger than 0. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of files that were marked as missing reappeared in the file system, - which is also the number of DB entries that removes file missing time. - - - - - dimich@chromium.org - offline-dev@chromium.org - Result of persistent page consistency check. - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of temporary offline pages without archive file when checking - consistency. It will only be reported if the number is larger than 0. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Number of archives without database entry when checking temporary page - consistency. It will only be reported if the number is larger than 0. - - - - - dimich@chromium.org - offline-dev@chromium.org - Result of temporary page consistency check. - - - - - Removed as of 12/2017. Replaced by OfflinePages.AccessCount. - - jianli@chromium.org - - Number of accesses to the offline page since its creation. This is reported - when the offline page was deleted. - - - - - - Removed 2/2018. No longer used, duplicate of - OfflinePages.SavePage.FreeSpaceMB. - - jianli@chromium.org - - The amount of free space available, in megabytes, on the user's device after - the page is deleted. - - Note that before M52 this operation was started before delete operation. - - - - - - Removed as of 5/2016. Marginal applicability. - - jianli@chromium.org - - The percentage of free space available on the user's device when the page is - being deleted. - - - - - - Removed as of 01/2018. Replaced by OfflinePages.PageAccessInterval. - - jianli@chromium.org - - Length of time between when an offline page was created and was opened last - time. This is reported when the page was deleted. - - - - - - Removed 2/2018. No longer used, duplicate of OfflinePages.PageSize. - - jianli@chromium.org - Size of the offline page, in kilobytes, that was deleted. - - - - - Removed as of 01/2018. Replaced by OfflinePages.PageAccessInterval. - - jianli@chromium.org - - Length of time between when an offline page was last opened and was deleted. - - - - - - Removed as of 03/2018. Replaced by similar metric - OfflinePages.StorageInfo.InternalUsagePercentage and - OfflinePages.StorageInfo.ExternalUsagePercentage. - - fgorski@chromium.org - jianli@chromium.org - - The percentage of space taken by offline pages from the free space that - could be available, if the feature was not present. I.e. considering - situation where the user has: Free Space, Offline content, other apps and - data. This is a percentage of: Offline content / (Offline content + Free - Space). - - The value will be recorded after user deletes a single or multiple offline - pages. In case pages are removed in bulk, this value will be reported once. - This value is only reported with deleting, as we are trying to infer if lack - of free space might have caused the user to delete. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Counts the number of times an offline page is deleted. Events are reported - per offline pages namespace. - - - - - jianli@chromium.org - offline-dev@chromium.org - Result of removing an offline copy for a page. - - - - - Removed 2/2018. No longer used. - - dewittj@chromium.org - dimich@chromium.org - - The number of downloaded pages with the same URL that exist at the time that - we delete a downloaded page. - - - - - dewittj@chromium.org - fgorski@chromium.org - offline-dev@chromium.org - - If at request time there is another request with the same URL, this tracks - this amount of time between creation of the most recent request and the - current request. - - - - - dewittj@chromium.org - fgorski@chromium.org - offline-dev@chromium.org - - If at request time there is another downloaded page with the same URL, this - tracks this amount of time between creation of the most recent existing page - and the current request. - - - - - - Removed 2/2018. No longer used. - - dewittj@chromium.org - dimich@chromium.org - - The number of downloaded pages with the same URL that exist at the time that - we save a downloaded page. - - - - - - Removed 2/2018. No longer used. - - dewittj@chromium.org - dimich@chromium.org - - If at save time there is another downloaded page with the same URL, this - tracks this amount of time between creation of the most recent existing page - and the current page. - - - - - harringtond@chromium.org - offline-dev@chromium.org - - Whether or not a thumbnail was provided for a prefetched offline article. - Recorded when the item is shown in Downloads Home. - - - - - - Removed 5/2016. Offline pages no longer depend on bookmarks UI. - - dougarnett@chromium.org - - Whether a user-edited bookmark URL had a saved offline page. - - - - - - Removed 11/2016. Offline pages no longer use two-step expiration. - - romax@chromium.org - Number of pages that are expired in a batch. - - - - - Removed 11/2016. Offline pages no longer use two-step expiration. - - romax@chromium.org - - Length of time between when an offline page was created and was expired. - - - - - - Removed 11/2016. Offline pages no longer use two-step expiration. - - romax@chromium.org - Result of updating expired page in store. - - - - - Removed 11/2016. Offline pages no longer use two-step expiration. - - romax@chromium.org - - Length of time between when an offline page was last opened and was expired. - - - - - - Removed 5/2016. Offline pages no longer depend on bookmarks UI. - - fgorski@chromium.org - jianli@chromium.org - - Whether user is connected when entering the filter with offline only - content. - - - - - - Removed 5/2016. Offline pages no longer depend on bookmarks UI. - - fgorski@chromium.org - jianli@chromium.org - - Whether user is connected when leaving the filter with offline only content. - - - - - - Removed 2/2018. Merged to OfflinePages.PageAccessInterval. - - jianli@chromium.org - - The time elapsed between creation of the offline page and the first time it - was opened. - - - - - - Removed 5/2016. Not longer needed. - - jianli@chromium.org - - Whether the page that was being saved offline was in incognito mode. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Upon starting saving a new last_n offline page snapshot, report if that is - being done for a page that is new (a navigation happened) or for one that - has been previously saved in the same session (no navigation happened). This - metric will assist in determining if there is the need to better track - actual content changes in pages saved more than once by last_n. - - - - - - Removed 5/2016. Offline pages no longer depend on bookmarks UI. - - fgorski@chromium.org - jianli@chromium.org - Logs a UI location from which an offline page is launched. - - - - - Removed in M65. - - jianli@chromium.org - - Status code of loading from the offline pages metadata store. - - - - - - Removed 10/2015, and replaced by OfflinePages.LoadStatus. - - jianli@chromium.org - - Whether an attempt to load the offline pages metadata store was successful. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Result of an attempt to load an MHTML archive to display a trusted offline - page, recorded per offline namespace by OfflinePageTabHelper after renderer - attempts to load the archive. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Result of an attempt to load an MHTML archive to display an untrusted - offline page, recorded by OfflinePageTabHelper after the renderer attempts - to load the archive. - - - - - - Removed 2/2018. No longer used. - - dewittj@chromium.org - jianli@chromium.org - - The amount of time to create the offline pages archive directory. - - - - - - Removed in M65. - - dewittj@chromium.org - jianli@chromium.org - - The amount of time to create the offline pages archive directory and load - the offline page model. - - - - - - Removed 2/2018. No longer used. - - dimich@chromium.org - - Whether the metadata database was successfully loaded, after possibly - several retries. - - - - - - Removed 2/2018. No longer used. - - dimich@chromium.org - - The count of attempts spent to open the metadata database. In the best case, - it's 1. There is a small upper limit. This is recorded only at success. - Failures are counted by OfflinePages.Model.FinalLoadSuccessful. - - - - - - Removed 5/2016. This was the dup of OfflinePages.SavedPageCount. - - fgorski@chromium.org - jianli@chromium.org - Number of offline pages the user has. Android only. - - - - dimich@chromium.org - offline-dev@chromium.org - - Counts user-days when Chrome was used in specific ways regarding navigation - to online and offline content. Buckets are mutually exclusive so that only - one bucket is incremented per reported day. This metric is not recorded to - UMA immediately due to potential data loss while offline. So day counters - are persisted to prefs and reported to the histogram only when the next UMA - data upload is likely to succeed. For more details see: - https://goo.gl/GJXwFe. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Counts user-days when Chrome was used in specific ways regarding navigation - to online and offline content. Buckets are mutually exclusive so that only - one bucket is incremented per reported day. - - This metric is a mirror of OfflinePages.OfflineUsage but it doesn't use any - of the offline resilient mechanisms that one has. Ideally both should report - exactly the same values but it is expected this one will lose more samples. - - - - - - Removed 5/2016. Offline pages no longer depend on bookmarks UI. - - jianli@chromium.org - - Whether the user was online when a saved page with offline copy was opened. - - - - - - Removed 2/2018. Merged to OfflinePages.PageAccessInterval. - - jianli@chromium.org - Length of time between two consecutive opens. - - - - dimich@chromium.org - offline-dev@chromium.org - - Length of time between accesses to an offline page. This is the same time - period used for expiring temporary pages. This metric is recorded when an - offline page is accessed. - - - - - jianli@chromium.org - offline-dev@chromium.org - - Length of time between when an offline page was created and was removed. - - - - - jianli@chromium.org - offline-dev@chromium.org - Size of the saved copy of an offline page. - - - - carlosk@chromium.org - offline-dev@chromium.org - - Records the archive size of an offline page loaded during a navigation that - took place while the device was considered to be offline or with poor - connectivity. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Records the archive size of an offline page loaded during a navigation that - took place while the device was considered to be online. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Counts user-days when candidate articles were suggested to the Offline - Prefetch pipeline while it was enabled. This metric is not recorded to UMA - immediately due to potential data loss while offline. So day counters are - persisted to prefs and reported to the histogram only when the next UMA data - upload is likely to succeed. For more details see: https://goo.gl/GJXwFe. - - - - - dewittj@chromium.org - offline-dev@chromium.org - - Number of attempts to perform a specific retriable pipeline action for each - finished prefetch item. - - - - - - Removed 9/2017. Replaced by OfflinePages.Prefetching.ActionAttempts - - carlosk@chromium.org - - Number of attempts to perform a specific retriable pipeline action for each - finished prefetch item. - - - - - - Removed 8/2018. - - carlosk@chromium.org - - Reports differences between the expected size of a prefetch archive -- as - reported by the service -- and the actual downloaded file size. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Actual size of archive file successfully downloaded by offline page - prefetching. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Expected download size of archive file, after gzip content encoding, that - started being downloaded by offline page prefetching. Sizes reported in this - metric are less than the sizes reported in DownloadedFileSize due to content - gzip encoding. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Reports the possible outcomes of an archive download finishing and its - respective prefetch item being updated in the store. Downloads are expected - to succeed or fail but a respective item should always exist and be updated. - The "item not found" cases are exceptions. - - - - - - Removed as of 5/2018. Replaced with - OfflinePages.Prefetching.FetchThumbnail.Complete2. - - harringtond@chromium.org - - Records the final status of attempts to fetch thumbnails for prefetched - offline pages. - - - - - - Removed as of 2/2019. - - harringtond@chromium.org - carlosk@chromium.org - - Records the final status of attempts to fetch thumbnails for prefetched - offline pages. The 1st attempt takes place right after the prefetch item was - sent to the cloud service as part of a request for the creation of its - offline snapshot. The 2nd attempt occurs right after the offline snapshot - was successfully downloaded by the client. - - - - - - Removed as of 2/2019. - - harringtond@chromium.org - Reports each time a thumbnail fetch is attempted. - - - - carlosk@chromium.org - offline-dev@chromium.org - - Error code representing the reason why each offline prefetch item was - finalized. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - The lifetime of an offline prefetch item, from creation until - "zombie-fication" (after metrics collection). - - - - - dewittj@chromium.org - offline-dev@chromium.org - - Actions taken with respect to the offline prefetch notification, includes - show attempts to calculate CTR. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Final result of an attempt to import a prefetched article into the Offline - Pages system. - - - - - petewil@chromium.org - offline-dev@chromium.org - - Status returned by a request to the Offline Page Service's GetOperation - method. - - - - - petewil@chromium.org - offline-dev@chromium.org - - Status returned by a request to the Offline Page Service's GetPageBundle - method. - - - - - petewil@chromium.org - offline-dev@chromium.org - - A prefetch item was seen in this state when starting the background task. - - - - - petewil@chromium.org - offline-dev@chromium.org - - A prefetch item was found in this state after more than 7 days since its - creation, time enough for it to have been finalized by the pipeline. - - - - - dewittj@chromium.org - offline-dev@chromium.org - - When receiving suggestions in the prefetch pipeline, emits the number of new - suggestions added to the database. If there is an error, nothing is emitted. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Counts when the offline pages prefetch store is opened or closed. - - - - - - Removed as of 8/2019. No longer needed. - - carlosk@chromium.org - offline-dev@chromium.org - - Tracks the time between store closing and reopening again within a session. - The store is meant to close itself after a period of inactivity. We are - trying to assess how much time the store is unloaded from memory vs. time it - is loaded and not used. This event will be reported when the store is opened - after being closed within the same lifetime of Chrome. - - - - - dimich@chromium.org - offline-dev@chromium.org - - Counts user-days categorized by how Offline Prefetch performed and had its - content accessed by the user. Buckets are mutually exclusive so that only - one bucket is incremented per reported day. This metric is not recorded to - UMA immediately due to potential data loss while offline. So day counters - are persisted to prefs and reported to the histogram only when the next UMA - data upload is likely to succeed. For more details see: - https://goo.gl/GJXwFe. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - When publishing an archive, we create the download directory if it doesn't - already exist. If we get an error, we record it here. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - When publishing an offline page, the move file step can fail. This returns - the reason for failure as a linux errno. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - When a move file fails for publishing, what caused the failure. - - - - - petewil@chromium.org - - When publishing an offline page, a page might not be found. This returns the - publishing path that was used (ex: by Guid or by OfflineId). - - - - - - Removed on 04/2020 in favor of becoming a special case of - OfflinePages.SavePageResult2. - - petewil@chromium.org - - Failure attempting to move a file while publishing downloaded page. - - - - - - Removed 8/2016. Use OfflinePages.RequestResult instead. - - dimich@chromium.org - - Result of automatic redirect to offline version of the page or back. Emitted - exactly once when offline-to-online or online-to-offline redirect is - determined to be needed and conveys the outcome of redirect. - - - - - - Removed 6/2016. Refactored into OfflinePages.RedirectResult. - - jianli@chromium.org - - Number of times an offline copy was loaded instead when the user is trying - to load the online version of a saved page and there is no network - connection. - - - - - - Removed 6/2016. Refactored into OfflinePages.RedirectResult. - - jianli@chromium.org - - Number of times an online version was loaded instead when the user is trying - to load the offline copy of a saved page and there is network connection. - connection. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Records whether the content read from intent URI (file:// or content://) - changed after the initial validation that was done to route the request when - the intent was received. This is recorded at the time that Offline Page - Request Handler tried to read the data, in preparation to show an offline - page to a user. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Positive net error code for opening the underlying file to serve the offline - page, including net::OK. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Track whether the range header is provided when an offline page is served. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Positive net error code for the failure to read the underlying file to serve - the offline page. net::OK is not included. - - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - - Positive net error code for the failure to seek the underlying file to serve - the offline page. net::OK is not included. - - - - - - Removed as of 2/2018. Replaced by OfflinePages.SavedPageCountUponQuery. - - jianli@chromium.org - - Number of saved pages restored from the offline pages metadata store when it - is logged. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Total number of saved offline pages recorded when they are all queried from - the store. This value is more meaningful when filtered by unique users as - that eliminates multiple reports from the same Chrome instance. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to successfully create the store metadata entry for an offline - page archive during the process of saving an offline page. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to successfully compute the digest of an offline page archive - during the process of saving an offline page. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to successfully create an offline page archive during the process - of saving an offline page. - - - - - - Removed as of 03/2018. Replaced by similar metric - OfflinePages.StorageInfo.InternalFreeSpaceMB. - - jianli@chromium.org - - The amount of free space available, in megabytes, on the user's device after - the page is saved. - - Note that before M52 this operation was started before save operation. - - - - - - Removed as of 5/2016. Marginal applicability. - - jianli@chromium.org - - The percentage of free space available on the user's device when the page is - being saved. - - - - - twellington@chromium.org - ianwen@chromium.org - - The percentage of the page load completed when the button to save an offline - page is pressed. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to successfully move an offline page archive to the public - downloads folder during the process of saving an offline page. - - - - - - Removed on 04/2020. The same information can be obtained from - OfflinePages.SavePageResult2.* (from each namespace suffix). - - dimich@chromium.org - - Counts the number of times an offline page is saved. Events are reported per - offline pages namespace. - - - - - - Removed on 04/2020. Replaced with OfflinePages.SavePageResult2. - - jianli@chromium.org - Result of saving an offline copy for a page. - - - - jianli@chromium.org - offline-dev@chromium.org - Result of saving an offline copy for a page. - - - - jianli@chromium.org - offline-dev@chromium.org - - The amount of time taken to save an offline copy for a page. - - - - - dewittj@chromium.org - offline-dev@chromium.org - Whether a shared page was an offline page or not. - - - - dimich@chromium.org - offline-dev@chromium.org - - Result of publishing internal page while sharing. CANCELLED means the page - to publish isn't found. ALREADY_EXISTS means the page have already been - published before. - - - - - - Removed 6/2016. Refactored into OfflinePages.RedirectResult. - - jianli@chromium.org - - Whether an offline page is shown, instead of error page, when the network is - disconnected or poor condition. - - - - - - Removed 3/2019. - - dimich@chromium.org - - If the directory to store the SQLite database file does not exist, it is - created. This is recorded every time the database is opened, even if the - directory already exists, in which case it's reported as FILE_OK. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Used as a counter to track different events related to offline page store - inner working. - - - - - - Removed as of 8/2019. No longer needed. - - carlosk@chromium.org - offline-dev@chromium.org - - Tracks the time between store closing and reopening again. The store is - meant to close itself after a period of inactivity. We are trying to assess - how much time the store is unloaded from memory vs. time it is loaded and - not used. This event will be reported when the store is opened after being - closed within the same lifetime of Chrome. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The storage space used by the archive files of offline pages, including all - files in public directory with mhtml/mht extensions. Collected after every - time an offline page is saved successfully. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The amount of free space on the external drive (which contains the public - download directory). Collected after every time an offline page is saved - successfully. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The percentage of storage space on the external volume (that contains public - download directory) used by offline pages archives. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The storage space used by the archive files of offline pages, including the - files in temporary and private directory. Collected after every time an - offline page is saved successfully. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The amount of free space on the internal drive (which contains the app - directory). Collected after every time an offline page is saved - successfully. - - - - - dimich@chromium.org - offline-dev@chromium.org - - The percentage of storage space on internal volume (that contains the app - directory) used by offline pages archives. - - - - - carlosk@chromium.org - offline-dev@chromium.org - - Tracks the reload of contents of an existing tab that is being restored - either because that tab is being presented for the first time after Chrome - was restarted or because its contents were discarded. All buckets are - mutually exclusive (adding up all reported values amounts to the total - number of tracked tab restores). This metric is focused on last_n offline - pages and is exclusive to Chrome on Android. - - - - - - Removed as of 03/2018. Replaced by similar metric - OfflinePages.StorageInfo.TotalArchiveSize. - - fgorski@chromium.org - jianli@chromium.org - - Total size of all the offline pages saved by the user. - - This value is recorded whenever the number of pages change, meaning after a - page is added or removed. If pages are removed in bulk, this value will be - reported only once. - - - - - - Removed as of 5/2016. Marginal applicability. - - fgorski@chromium.org - jianli@chromium.org - - Total size of all the offline pages saved by the user as a percentage of - total storage size. - - This value is recorded whenever the number of pages change, meaning after a - page is added or removed. - - - - - jianli@chromium.org - - The trust state of the offline page. This is recorded when an offline page - is being opened. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - jianli@chromium.org - - Percentage of battery remaining when the offline page background loading - task wakes up to check for work. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - jianli@chromium.org - - Whether the device is plugged in when the offline page background load task - wakes up to check or work. - - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - jianli@chromium.org - - Time delay from a dinosaur page to connection being available. - - - - - - Removed in M77. - - petewil@chromium.org - jianli@chromium.org - - Which network is available (if any) when the offling page background loading - task wakes up to check for work. - - - - - - Removed as of 8/2019. No longer needed. - - carlosk@chromium.org - offline-dev@chromium.org - - Indicates whether the browser was connected when Open online button was - clicked on Page Info popup, which causes a reload of an offline page to - online version. - - - - - fgorski@chromium.org - - Indicates whether Open online was visible in Page Info popup, when it was - shown for an offline page. (The button is visible only when Chrome is - connected when the Page Info popup is opened for offline page.) - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - When a page is loaded in offline mode, the percentage of resources on that - page that were successfully loaded. - - - - - - Removed 2019/08, this metrics doesn't reflect the measurement speed because - it is dependent on the length of text. - - yiyix@chromium.org - fserb@chromium.org - - Time spent in microseconds to perform calls to measure TextMetrics for - OffscreenCanvas. It's measured each time TextMetrics is called. - - - - - yiyix@chromium.org - fserb@chromium.org - - Time spent in microseconds to perform call SetFont in canvas for - OffscreenCanvas. It's measured each time SetFont is called. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Aggressive HistoryURL provider field trial deleted in spring 2012. - - Please list the metric's owners. Add more owner tags as needed. - - A number that indicates what omnibox ranking behavior the user is seeing as - part of the OmniboxAggressiveHistoryURLProvider field trial - (OmniboxAggressiveHistoryURLProvider). - - - - - - Removed in August 2020. - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-android-omnibox-team@google.com - - Records number of times an Answer is presented as one of the Omnibox - Suggestions at the time the user exited the omnibox. Exiting the omnibox - includes navigating (to entered text or any suggestion), pressing the system - back key, clearing omnibox, blanking screen / locking the phone (whether - intentionally or due to inactivity), or closing the Chrome app. This metric - is logged every time the omnibox is exited, including when no answer is - present in the list of suggestions. - - Nota bene: in some circumstances this histogram is double counting on - purpose. Scenarios cover repetitive actions that expose same answer - suggestion, ie. leave-enter-leave application, or leave-enter-clear where no - new suggestion fetches are done. - - This histogram assumes that no more than 1 AiS suggestion is shown at a - time, which was enforced by the backend at the time the histogram was - created. Additional histogram/s may be required to properly track how - frequently answers are shown in general - and in what quantity. - - This histogram is related to Omnibox.SuggestionUsed.AnswerInSuggest. - - - - - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - For each answer received in suggest responses, the number that are - well-formed and contain all the required elements. - - - - - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - The number of times each omnibox suggestion answer type (e.g., weather, - sports score) was received and parsed successfully. Can be normalized with - the count of emits to Omnibox.SuggestRequest.Success.GoogleResponseTime, - which counts all successful suggest responses from Google, not just those - with answers attached. Note that GoogleResponseTime is technically off given - that it will still count cases where we fail to extract, deserialize, or - parse the response. But these cases are rare to non-existent. - - - - - - - manukh@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - The time elapsed between the ChromeOmniboxClient requesting a suggestion's - image to receiving the image. This includes both uncached and cached - requests. See BitmapFetcher.Fetch and BitmapFetcher.Decode for what - contributes to uncached images latency; however, the sum of those metrics - can be greater than this metric as image prefetching begins before the - ChromeOmniboxClient requests an image. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - asvitkine@chromium.org - - Records the time taken between a keystroke being typed in the omnibox and - the text being painted. If there are multiple keystrokes before a paint, - logs the time since the earliest one. - - This duration is composed of three parts: - - a) the time spent processing the initial input event - - b) the time spent for the repaint task to be scheduled on the message loop - - c) the time spent painting the Omnibox - - d) (on views platforms) the time until the pixels are actually composited - - There's a number of breakdown metrics to help diagnose a regression. First, - Omnibox.CharTypedToRepaintLatency.ToPaint measures the combined time of (a) - and (b). Omnibox.QueryTime2 is a good proxy for just (a). And there's also - Omnibox.PaintTime that corresponds to (c). We don't have a direct metric for - (d), but if neither Omnibox.CharTypedToRepaintLatency.ToPaint nor - Omnibox.PaintTime regressed, then the regression must be in (d). - - Note: The semantics of this metric on views platforms changed in M62, as - previously time (d) was not included in the metric. - - - - - - This became the new implementation of Omnibox.CharTypedToRepaintLatency as - of 08/2017. - - asvitkine@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - A refinement of the Omnibox.CharTypedToRepaintLatency metric that attempts - to more accurately track the latency by measuring until the point when the - compositor has actually put pixels on the screen. In particular, this will - capture the time used to also paint the Omnibox result views as a result of - the character insertion, which is not covered by - Omnibox.CharTypedToRepaintLatency. If there are multiple keystrokes before a - paint, logs the time since the earliest one. - - - - - asvitkine@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - A refinement of Omnibox.CharTypedToRepaintLatency metric. It measures the - time between the first character insertion in a series that happen during a - frame, to the time the compositor reports the text was rendered on-screen. - Compositor-provided timestamps are used for this version of the metric, so - it is expected to be more accurate: the baseline CharTypedToRepaintLatency - uses now() from when the subsequent has-processed notification arrives back - on the UI thread, which may overestimate user-visible latency. - - - - - asvitkine@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records the time between when OnPaint() is called to the time the compositor - reports pixels were successfully drawn to the screen. This a subset of the - time reported in Omnibox.CharTypedToRepaintLatency.InsertToPresent. - - - - - asvitkine@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records the time taken between a keystroke being typed in the omnibox and - the time when we're ready to paint the omnibox. This is a breakdown - diagnostic metric for Omnibox.CharTypedToRepaintLatency, to help diagnose - regressions in that metric. See that metric's description for more info. - - - - - gangwu@chromium.org - fgorski@chromium.org - - Recorded every time the clipboard suggestion is removed from omnibox - suggestion list and the system clipboard. The value indicates the estimated - age of the clipboard. - - - - - gangwu@chromium.org - jdonnelly@chromium.org - - Recorded every time the omnibox is focussed and recent content from the - user's clipboard is suggested. The value indicates the estimated age of the - clipboard. (If Chrome observed the clipboard modification, this age is - exact. If Chrome did not observe the modification, then it's a conservative - estimate: the last time Chrome observed a clipboard modification, which is - certainly older than the current clipboard. If Chrome never observed a - clipboard modification, no clipboard suggestion is shown, meaning this - histogram will never be emitted to.) - - Intended to be compared with MobileOmnibox.PressedClipboardSuggestionAge. - - - - - gangwu@chromium.org - jdonnelly@chromium.org - - Recorded every time the omnibox is focussed and a recent content from the - user's clipboard is suggested. The number emitted is the number of times the - clipboard content has been suggested within the same session including the - current time. Thus, the third time it is shown, we'll emit a three to this - histogram, and this histogram will have previously seen emits of one and - two. If the clipboard content was the same during a previous run of Chrome - and this clipboard content was suggested during that run, those impressions - are not counted. Also, if the clipboard content changes during a particular - run of Chrome to other content, the omnibox is focused and that clipboard - content is suggested, then content changes back and Chrome starts suggesting - the older clipboard content again, the counts start again from scratch. - Chrome only remembers the number of times the clipboard content was shown - consecutively. - - This value is useful to compare with the number of times a clipboard - suggestion has been shown when it is clicked. This value can be obtained - from OmniboxEvent records in which the selected suggestion is from Clipboard - provider. In those cases, look in the Clipboard provider's ProviderInfo - field for |times_returned_results_in_session|. Note that at the time of this - writing that OmniboxEvent logs aren't recorded in incognito whereas - histograms are. Thus, the total counts will not be comparable, though the - distributions should be. - - - - - gangwu@chromium.org - jdonnelly@chromium.org - - Recorded every time the omnibox is focussed and a recent content from the - user's clipboard is suggested. The value indicates whether the current URL - was shown (which would appear above the clipboard suggestion) or was absent - (which ought to only happen when the omnibox is empty / the user is on the - NTP). - - On Android, the total count for this histogram can be usefully compared with - the count of the user action FocusLocation in order to determine the rate at - which a clipboard suggestion is shown in the omnibox. To determine the same - rate on iOS, one needs to compare this histogram's count with the sum of the - user actions MobileFocusedOmniboxOnNtp, MobileFocusedFakeboxOnNtp, and - MobileFocusedOmniboxNotOnNtp. - - Furthermore, on either platform, this histogram's count can be usefully - compared with the count in the clipboard bucket of the - Omnibox.SuggestionUsed.Provider histogram to determine the clickthrough rate - on these suggestions. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The number of cut or copy commands on all selected text in the omnibox. - Gathered on desktop platforms (Win, Mac, Linux, Chrome OS). - - - - - mpearson@chromium.org - jdonnelly@chromium.org - skare@chromium.org - - Counts the number of document suggest requests the omnibox sent, were - invalidated, and were completed successfully. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - skare@chromium.org - - Number of results returned in each document suggestion reply. Logged for - successful requests where the provider returned a parseable result set. - - - - - - Removed 06/2020. Use "Omnibox.EditUrlSuggestion.*" user actions - instead. - - jdonnelly@chromium.org - mdjones@chromium.org - fgorski@chromium.org - ender@chromium.org - - The action performed on the edit-URL omnibox suggestion that contains the - "what you typed"/current URL. If visible, this is the first - suggestion. - - - - - livvielin@chromium.org - tommycli@chromium.org - - The state of URL elision in the omnibox, e.g. URL default behavior, - prevented by context menu option, or prevented by Chrome extension. This - histogram is recorded the first time ShouldPreventElision is called on - ChromeLocationBarModelDelegate with an existing profile. This occurs every - time a browser window is open, including when opening a new profile or - moving a tab to a new window. This metric measures the percentage of browser - windows that use each type of elision behavior. - - - - - - Removed 10/2018 and replaced with "Omnibox.EnteredKeywordMode2". - - mpearson@chromium.org - - The number of times users enter keyword hint mode "Search ___ - for:" and how. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The new enumeration of how many times users enter keyword hint mode - "Search ___ for:" and how. Note that we don't recognize the - changing of the keyword itself as entering keyword mode, if the user never - left keyword mode e.g. if the user was arrowing around the suggestions, so - we'll preserve the original keyword mode entry method in this case. - - - - - ender@chromium.org - jdonnelly@chromium.org - mpearson@chromium.org - tommycli@chromium.org - - This records whether user initiated navigation after focusing the Omnibox - versus switches focus elsewhere without navigating. This metric includes - accidental focus-then-losing-focus events, including brief ones. It also - includes ones in which the user did not type any text or otherwise engage - with the Omnibox. E.g., the user tabbing through all top Chrome UI controls - will cause this metric to be recorded. If the user switches focus from the - Chrome window to another window while the Omnibox is focussed, that also - counts as a loss of focus. - - This metric is not recorded for the Realbox interactions. - - Recorded every time the Omnibox focus is cleared. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The length of time between when a user focused on the omnibox and first - modifies the omnibox. - - - - - - Replaced with Omnibox.FocusToOpenTimeAnyPopupState in April 2014. - - mpearson@chromium.org - - The length of time between when a user focused on the omnibox and opened an - omnibox match (which could be what they typed or a suggestion). - - - - - - Replaced with Omnibox.FocusToOpenTimeAnyPopupState2 in August, 2016. - - mpearson@chromium.org - - The length of time between when a user focused on the omnibox and opened an - omnibox match (which could be what they typed or a suggestion). This is - recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. - - - - - - Replaced with Omnibox.FocusToOpenTimeAnyPopupState3 in January, 2017, which - only differs in the bucketing and range. - - mpearson@chromium.org - - The length of time between when a user focused on the omnibox and opened an - omnibox match (which could be what they typed or a suggestion). This is - recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. - It is not recorded if a match is opened without triggering a focus event, - e.g., when a user drags a URL to the omnibox to navigate. - - To know how common this last condition is, compare the total count of this - histogram to the total number of omnibox events. - - Android started logging this in M76. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The length of time between when a user focused on the omnibox and opened an - omnibox match (which could be what they typed or a suggestion). This is - recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. - It is not recorded if a match is opened without triggering a focus event, - e.g., when a user drags a URL to the omnibox to navigate. - - To know how common this last condition is, compare the total count of this - histogram to the total number of omnibox events. - - - - - - Removed 2020-07-15 - - mpearson@chromium.org - jdonnelly@chromium.org - pkl@chromium.org - - iOS: Records whether a hardware keyboard is used to input text. This is - recorded each time a UIKeyboardWillChangeFrameNotification is sent while - editing the omnibox text. - - - - - - Removed 2015-01-27 - - mpearson@chromium.org - - Whether there was at least one legal default match without an - |inline_autocompletion|. Recorded every time - AutocompleteResult::SortAndCull() is called, which could happen multiple - times on each keystroke. - - - - - - Removed in August 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Times URLIndexPrivateData::HistoryIDSetFromWords(), which is called by the - omnibox's HistoryQuick provider. - URLIndexPrivateData::HistoryIDSetFromWords() can be called multiple times - per keystroke due to, for example, the cursor being in the middle of the - input string or SearchProvider's calls to Classify(). - - - - - estark@chromium.org - carlosil@chromium.org - - The time duration that the user hovers the mouse over the omnibox before - exiting the hover or focusing the omnibox. Whenever the user's mouse enters - the omnibox, this histogram is recorded when the mouse next exits or the - omnibox is focused, whichever comes first. The recorded value is a delta - from a timestamp noted when the user's mouse first entered the omnibox. - - - - - ender@chromium.org - jdonnelly@chromium.org - mpearson@chromium.org - chrome-android-omnibox-team@google.com - - Records suggestions decorated with specific icon or favicon at the time the - user exited the omnibox. Exiting the omnibox includes navigating (to entered - text or any suggestion), pressing the system back key, clearing omnibox, - blanking screen / locking the phone (whether intentionally or due to - inactivity), or closing the Chrome app. This metric is logged every time the - omnibox is exited, including when no answer is present in the list of - suggestions. - - This histogram is related to Omnibox.SuggestionUsed.IconOrFaviconType. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The kind of input the user provided when using the omnibox to go somewhere. - The type can be misleading. For example if the user typed 'http:/', it gets - marked as a query because it cannot be opened as a URL even though the user - probably wanted and selected a URL from the list of suggestions. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Whether an omnibox interaction is a paste-and-search/paste-and-go action. - (This histogram records both of these in the "True" bucket for - this histogram because both of these are referred to as paste-and-go in the - code.) These typically involve right-clicking in the omnibox and selecting - that option from the dropdown. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - Whether the omnibox popup (a.k.a. dropdown) is open at the time the user - used the omnibox to go somewhere. It can be closed if, for instance, the - user clicked in the omnibox and hit return to reload the same page. Also, - because paste-and-search/paste-and-go actions ignore the current content of - the omnibox dropdown (if it is open) when they happen, we pretend the - dropdown is closed when logging these. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Whether the user deleted text immediately before selecting an omnibox - suggestion. This is usually the result of pressing backspace or delete. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - mahmadi@chromium.org - tommycli@chromium.org - - The length of time it takes for the corresponding URLs that would produce a - deleted match to be queried asynchronously and deleted. Triggered when user - deletes a local history zero-prefix suggestion. - - - - - - Made obsolete in July 2020 for the M86 Milestone. - - mahmadi@chromium.org - tommycli@chromium.org - - The maximum number of matches returned by the provider. Triggered when - zero-prefix suggestions are enabled and requested as a result of user focus - into the Omnibox or the Realbox on the NTP. - - - - - mahmadi@chromium.org - tommycli@chromium.org - - The number of search terms extracted from the keyword search terms database - and examined (e.g., sorted) to produce local zero-prefix suggestions. - Triggered when zero-prefix suggestions are enabled and requested as a result - of user focus into the Omnibox or the Realbox on the NTP. - - - - - mahmadi@chromium.org - tommycli@chromium.org - - The length of time it takes to extract search terms from the keyword search - terms database and examine (e.g., sort) them to produce local zero-prefix - suggestions. - - - - - - Made obsolete in July 2020 for the M86 Milestone. - - mahmadi@chromium.org - tommycli@chromium.org - - The number of search terms examined until the maximum possible matches are - fulfilled. Used to determine the upper bound of search terms to query from - the keyword search terms database. Triggered when zero-prefix suggestions - are enabled and requested as a result of user focus into the Omnibox or the - Realbox on the NTP. - - - - - mahmadi@chromium.org - tommycli@chromium.org - - The length of time it takes to handle the deletion request for a match and - to update the list of provider matches synchronously. Triggered when user - requests to delete a local history zero-prefix suggestion. - - - - - - Removed 2019-11-10. Replaced by Omnibox.MatchStability.AsyncMatchChange2. - - tommycli@chromium.org - jdonnelly@chromium.org - - This histogram was buggy and the data should be disregarded. - - The original intent was to count asynchronous match updates for each - position. The implementation had a bug, and it overcounted. - - - - - tommycli@chromium.org - jdonnelly@chromium.org - - This tracks how unstable our matches are due to asynchronous updates. - Whenever a dropdown position gets asynchronously set to a new match that's - different from the old match, this histogram logs the index. - - We primarily care the default match, which is logged at index 0. All indices - matter though, so we track the other indices too. When the number of matches - changes asynchronously, matches that are removed are considered a - "change" and logged here. Matches that are appended are less - disruptive to the user, and are not logged. - - This is because this metric is primarily interested in how many times the - user could be looking at a match with the intention of selecting it, and - then it surprisingly goes away. - - Note that merely adding a new asynchronous provider will increase these - counts. That's intentional. Swapping matches out annoys users, and to avoid - this, we should do some things like: caching, update coaslescing, update - deferral until next keystroke, provider timeouts, etc. - - This metric is designed to be normalized by the True count of - Omnibox.Start.WantAsyncMatches, which will yield the number of match changes - asynchronously per keystroke or other user gesture. - - - - - tommycli@chromium.org - jdonnelly@chromium.org - - This tracks how unstable our matches are due to asynchronous updates. - - For each asynchronous autocomplete update, this histogram logs whether any - match in any position has changed. Note: if the only change is new matches - appended to the end of the list, that does not count as a change, since it's - not very disruptive to the user. - - This metric is designed to be normalized by the True count of - Omnibox.Start.WantAsyncMatches, which will yield the number of times any - match changes asynchronously per keystroke or other user gesture. - - This histogram can be considered a boolean analogue to - Omnibox.MatchStability.AsyncMatchChange2. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The number of times users used the omnibox to go somewhere. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The number of terms in the text the user entered in the omnibox when they - used the omnibox to go somewhere. Terms are defined by splitting on - whitespace. All values larger than 6 are recorded in bucket 6. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - cch@chromium.org - suggest-2g@google.com - - Time it takes for omnibox on device head provider to fulfill the - asynchronous suggest request. - - - - - cch@chromium.org - suggest-2g@google.com - - The number of results returned by the on device head model which matches the - user input. Note all numbers greater than 5 are recorded in bucket 5. - - - - - asvitkine@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Records the time to paint the omnibox contents. This is a subcomponent of - Omnibox.CharTypedToRepaintLatency. Implemented on desktop platforms. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The number of paste commands on the text in the omnibox. Reported every time - a paste command is done. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - - The number of paste-and-go commands on the text in the omnibox. Reported - every time a paste-and-go command is done. - - - - - jdonnelly@chromium.org - orinj@chromium.org - chrome-omnibox-team@google.com - - Counts the type (concept ID) of omnibox pedals shown when the user used the - omnibox to go somewhere. - - Pedals are a button attached to a search suggestion that either navigate to - a chrome:// URL or trigger a Chrome action (for example, opening the page - translation dialog or opening a new window in Incognito mode). - - Note that, while it is uncommon, it is possible for multiple pedals to be - shown at one time so this can't be used as a count of how many times a pedal - or pedals were present. - - This histogram is related to Omnibox.SuggestionUsed.Pedal. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Records a boolean value indicating whether the Physical Web provider was - invoked by focusing the omnibox during the current omnibox session. This is - unexpected; it's probably a bug somwhere. Recorded when the user selects an - omnibox suggestion. Does not record when the Physical Web omnibox provider - is disabled. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - The number of matches returned by PhysicalWebProvider. Emitted when the - omnibox is first focused, unless the user is in incognito mode. Capped at - 10. - - - - - - Obsolete 05/16/2017. Data is unused (crbug.com/719801). - - kkimlabs@chromium.org - - The number of progress bar break point updates from page load started to - page load finished. - - - - - - Obsolete 05/16/2017. Data is unused (crbug.com/719801). - - kkimlabs@chromium.org - - The number of progress bar frame updates from page load started to page load - finished. If there is no animation, this matches - Omnibox.ProgressBarBreakPointUpdateCount. Note that there can be additional - updates after page load finished, animating to 100%, but this histogram - doesn't include them. - - - - - - Removed 2015-06-12. Replaced by Omnibox.ProviderTime2. - - mpearson@chromium.org - - The length of time taken by the named provider"s synchronous pass. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The length of time taken by the named provider"s synchronous pass. - - - - - - Removed 2012-11-14. Replaced by Omnibox.ProviderTime. - - Please list the metric's owners. Add more owner tags as needed. - - Time the HistoryContentProvider takes to perform a bookmark search. - - - - - - Removed in June 2019 for M-78. - - mpearson@chromium.org - jdonnelly@chromium.org - stkhapugin@chromium.org - - The elapsed time to acquire the location sent in the X-Geo header for an - Omnibox query. - - - - - - Removed in June 2019 for M-78. - - mpearson@chromium.org - jdonnelly@chromium.org - stkhapugin@chromium.org - - The estimated horizontal accuracy of the location sent in the X-Geo header - for an Omnibox query. - - - - - - Removed in August 2020 - - mpearson@chromium.org - jdonnelly@chromium.org - stkhapugin@chromium.org - - For iOS, whether the application is authorized to use location services when - the user enters a search query into the Omnibox. - - - - - - Removed 2015-06-12. Replaced by Omnibox.QueryTime2. - - mpearson@chromium.org - - Time it takes for the omnibox to become responsive to user input after the - user has typed N characters. This measures the time it takes to start all - the asynchronous autocomplete providers (but not wait for them to finish). - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Time it takes for the omnibox to become responsive to user input after the - user has typed N characters. This measures the time it takes to start all - autocomplete providers (but not wait for the asynchronous ones to finish). - - - - - - Removed in August 2020. - - ender@chromium.org - jdonnelly@chromium.org - mpearson@chromium.org - chrome-android-omnibox-team@google.com - - Records, for each entity suggestion (people, music, ...) whether it was - decorated with image / color / icon at the time the user exited the omnibox. - Exiting the omnibox includes navigation (url or query), pressing back key, - locking the phone, clearing the omnibox, closing Chrome, or just screen - blacking out due to prolonged inactivity. - - This metric is currently only recorded on Android, though it could be added - to the other platforms. - - - - - - Removed in August 2020. - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-android-omnibox-team@google.com - - Records number of presented Rich Entity suggestions at the time the user - exited the omnibox. Exiting the omnibox includes navigating (to entered text - or any suggestion), pressing the system back key, clearing omnibox, blanking - screen / locking the phone (whether intentionally or due to inactivity), or - closing the Chrome app. This metric is logged every time the omnibox is - exited, including when no entities are present in the list of suggestions. - - Nota bene: in some circumstances this histogram is double counting on - purpose. Scenarios cover repetitive actions that expose same entity - suggestions, ie. leave-enter-leave application, or leave-enter-clear where - no new suggestion fetches are done. - - This histogram is related to Omnibox.SuggestionUsed.RichEntity. - - - - - - Removed in June 2019 for M-78. - - mpearson@chromium.org - jdonnelly@chromium.org - - When a user switches tabs, whether the omnibox had an edit in progress. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records the number of searches done from omnibox using - default search engine on desktop and android devices, sliced based on being - in regular mode or private modes. - - - - - - Made obsolete around Chrome 32. Use Omnibox.SearchEngineType instead. - - Please list the metric's owners. Add more owner tags as needed. - - The id of search engine that was used for search in omnibox. See - src/chrome/browser/search_engines/template_url_prepopulate_data.cc for more - info. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The type of search engine associated with a match opened from the omnibox. - - - - - - Removed in June 2019 for M-78. - - mpearson@chromium.org - jdonnelly@chromium.org - - Time it takes to add all the raw history results to the list of matches. - - - - - - Deleted in August 2018 in M-70. - - mpearson@chromium.org - - Time it takes to convert all the results to matches and add them to a map, - to keep the most relevant match for each result. - - - - - - Deleted in August 2018 in M-70. - - mpearson@chromium.org - - Time it takes for the omnibox to search the previous query history database - for queries that start with the omnibox text. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The number of matches returned by SearchProvider. Emitted on every call to - SearchProvider::Start(), which effectively means every key stroke in the - omnibox. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - The index of the item that the user selected in the omnibox popup (a.k.a. - dropdown) list. 0 means the inline suggestion shown within the omnibox. This - is also the same suggestion shown as the top item in the dropdown. The - second item in the dropdown will be recorded as bucket 1. The selected - position is always set to 0 when the popup is closed at the time of - navigation or if the user did a paste-and-search or paste-and-go action. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - livvielin@chromium.org - tommycli@chromium.org - - Tracks whether the context menu option to prevent URL elisions in the - omnibox is enabled. Recorded when the pref is toggled. - - - - - tommycli@chromium.org - jdonnelly@chromium.org - - Whether asynchronous matches are requested. Recorded every time - AutocompleteController::Start() is called. - - False counts roughly correspond to non-interactive invocations of - AutocompleteController - like when we are classifying user text as a Search - or URL. - - True counts roughly correspond to keystrokes or on-focus events, and can be - used as a normalizer for per-user-gesture metrics. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Counts how often omnibox suggestions are used, and in the case an Answer - suggestion was selected - records the type of an answer. This histogram is - useful because there is no distinct suggestion type recorded for answers so - their use is not recorded by Omnibox.SuggestionUsed.ProviderAndResultType. - - - - - - Removed in M84. - - chrome-android-omnibox-team@google.com - ender@chromium.org - jdonnelly@chromium.org - mpearson@chromium.org - - Counts how often omnibox suggestions are used, and in the case a regular - search / url (not an Answer, Entity or any other specialized) suggestion was - selected - records how the suggestion was decorated. - - This histogram is related to Omnibox.IconOrFaviconShown. - - - - - - Removed in M58, replaced with Omnibox.SuggestionUsed.NearbyURLCount.AtFocus - and Omnibox.SuggestionUsed.NearbyURLCount.AtMatchCreation. - - - The number of nearby Physical Web URLs when the user focused the omnibox. - Recorded when the user accepts an omnibox suggestion, regardless of whether - the suggestion came from PhysicalWebProvider. Capped at 50. - - In M57, the values recorded by this histogram were determined to be bugged. - It's believed that it was recording uninitialized values due to a corner - case on Android that allows an omnibox suggestion to be selected without - first focusing the omnibox. In addition to the new histograms, - Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus was added to - detect this case. https://crbug.com/691059 - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - The number of nearby Physical Web URLs when Physical Web Provider was last - focused (i.e., the start of the current session). Recorded when the user - accepts an omnibox suggestion, regardless of whether the suggestion came - from PhysicalWebProvider. Capped at 50. - - Does not record if the omnibox was not focused during the current session. - Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus records true - when we hit this case. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - The number of nearby Physical Web URLs when Physical Web Provider last - constructed matches. Recorded when the user accepts an omnibox suggestion, - regardless of whether the suggestion came from PhysicalWebProvider. Capped - at 50. - - - - - gangwu@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Measures whether the suggestion that was selected by the user offered a tab - match. A tab match occurs when the URL specified by the suggestion matches - the URL navigated to by another tab in the browser, within the margin of our - URL stripping scheme. - - This metric typically only makes sense with respect to - Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser - send the metric. Therefore, other metrics may include datapoints not covered - by this metric (unless one narrows the data by version.) - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - jdonnelly@chromium.org - orinj@chromium.org - chrome-omnibox-team@google.com - - Counts how often omnibox pedals are used and records the type (concept ID) - of the pedal used. - - Pedals are a button attached to a search suggestion that either navigate to - a chrome:// URL or trigger a Chrome action (for example, opening the page - translation dialog or opening a new window in Incognito mode). - - This histogram is related to Omnibox.PedalShown. - - - - - - Removed in August 2020. - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-android-omnibox-team@google.com - - Whether a Rich Entity omnibox suggestion was selected when the user used the - omnibox to go somewhere. - - This histogram is related to Omnibox.RichEntityShown. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from the page first appearing in the foreground to its - first meaningful paint. Only recorded on navigations that use a prerender - that is to a search query suggestion selected from the omnibox. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Measures the time from navigation start to first meaningful paint. Only - recorded for a search query suggestion selected from the omnibox. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from the page first appearing in the foreground to its - first contentful paint. Only recorded on navigations that use a prerender - that is to a search query suggestion selected from the omnibox. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Measures the time from navigation start to first contentful paint. Only - recorded for a search query suggestion selected from the omnibox. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from a page being navigated to in prerender to it first - showing up in foreground. Only recorded on navigations that used a prerender - that was to a search query suggestion selected from the omnibox. This is - only recorded on pages that experience a first contentful paint. - - - - - gangwu@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Measures whether the suggestion that was selected by the user offered a tab - match and specifically that the user chose the tab match over normal - navigation. A tab match occurs when the URL specified by the suggestion - matches the URL navigated to by another tab in the browser, within the - margin of our URL stripping scheme. By selecting the tab match, the browser - simply switches focus to the matching tab. - - This metric typically only makes sense with respect to - Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser - send the metric. Therefore, other metrics may include datapoints not covered - by this metric (unless one narrows the data by version.) - - This metric should be stricly less than - Omnibox.SuggestionUsed.OfferedTabMatch, and is typically used to discover - the percentage of offered tab matches that the user accepts. - - In M-74 and earlier, this was only recorded if the user had no incognito - windows open. In M-75 and later, it records all omnibox interactions - regardless, in order to be consistent with how user actions and histograms - are handled. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from the page first appearing in the foreground to its - first meaningful paint. Only recorded on navigations that use a prerender - that is to a URL suggestion selected from the omnibox. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Measures the time from navigation start to first meaningful paint. Only - recorded for a URL suggestion selected from the omnibox. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from the page first appearing in the foreground to its - first contentful paint. Only recorded on navigations that use a prerender - that is to a URL suggestion selected from the omnibox. - - - - - jdonnelly@chromium.org - mpearson@chromium.org - chrome-omnibox-team@google.com - - Measures the time from navigation start to first contentful paint. Only - recorded for a URL suggestion selected from the omnibox. - - - - - - Prerender was retired from the code long ago; this histogram was finally - removed in July 2020. - - mpearson@chromium.org - jdonnelly@chromium.org - - Measures the time from a page being navigated to in prerender to it first - showing up in foreground. Only recorded on navigations that used a prerender - that was to a URL suggestion selected from the omnibox. This is only - recorded on pages that experience a first contentful paint. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - cch@chromium.org - - The time elapsed between the sending of a suggest request to Google until - the time the request was returned with status==failed. Ignores requests that - were canceled before being returned. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - cch@chromium.org - - The time elapsed between the sending of a suggest request to Google until - the time the request was returned with status==success. Ignores requests - that were canceled before being returned. - - - - - manukh@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - The number of images prefetched by the search provider on retrieving a - successful search response. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - cch@chromium.org - - Counts about the number of suggest requests the omnibox sent, invalidated, - and replies received. - - - - - - Removed as of 12/2019 - - mdjones@chromium.org - lzbylut@google.com - - The amount of time that passes in ms between the user focusing the omnibox - and performing some action on Android. This is only recorded the first time - the user performs this action per omnibox focus event. Other - Omnibox.TimeUntilFirst.* events are not recorded past the first event. - - - - - mahmadi@google.com - chrome-omnibox-team@google.com - - Counts the number of times a suggestion group ID is prevented form appearing - in the results. This is recorded when the user hides a set of grouped - suggestions, such as proactive zero-suggest, in the omnibox UI using the - control in the grouped suggestions' header. - - - - - mahmadi@google.com - chrome-omnibox-team@google.com - - Counts the number of times a suggestion group ID is permitted to appear in - the results. This is recorded when the user makes a set of previously hidden - grouped suggestions, such as proactive zero-suggest, visible in the omnibox - UI using the control in the grouped suggestions' header. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - chrome-omnibox-team@google.com - - The scheme of the destination URL for the selected omnibox suggestion. This - could be a what-you-typed suggestion (if the user fully typed a URL), an - inline autocompletion, or something in the dropdown, anything as long as - it's a URL navigation, not a search query. Excludes omnibox URL navigations - that are effectively reloads as well as cut-and-pastes of URLs. Also does - not take into account any redirects that destination URL may do before - finally serving a page. In other words, it's the scheme of the first request - in a possible chain. - - - - - - Removed in 06/2020 for M-85. - - mpearson@chromium.org - jdonnelly@chromium.org - cthomp@chromium.org - - The amount of time, in milliseconds, between the start of a typed URL - navigation in the omnibox (the user typing a URL to completion, or selecting - a URL from the inline autocomplete or dropdown) and the start of a redirect - upgrading the URL to HTTPS. This is only recorded when the upgraded URL is - the same except for the scheme and the addition/removal of a - "www." prefix. - - To calculate the percentage of HTTP URL navigations that have been upgraded - in this way, divide the count of this histogram by the count for HTTP in - Omnibox.URLNavigationScheme. - - - - - kenjibaheux@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Counts the number of times that the user text is cleared. IME users are - sometimes in the situation that IME was unintentionally turned on and failed - to input latin alphabets (ASCII characters) or the opposite case. In that - case, users may delete all the text and the user text gets cleared. This - histogram helps us estimate how often this scenario happens. - - Note that since we don't currently correlate "text cleared" events - with IME usage, this also captures many other cases where users clear the - text; though it explicitly doesn't log deleting all the permanent text as - the first action of an editing sequence (see comments in - OnAfterPossibleChange()). - - - - - etienneb@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Time it takes for the omnibox to process the first user interaction after - startup. This measures the time it takes to start all autocomplete providers - and their initialisation steps. This metric may be recorded twice as there - is the normal omnibox path and also the "classify text" path to - the autocomplete system. - - - - - - Removed 05/2019 because histogram was not recorded in every circumstance. - Superseded by Omnibox.ZeroSuggest.Eligible.OnFocusV2. - - mpearson@chromium.org - jdonnelly@chromium.org - - Whether the user has settings configured so that the current page URL can be - sent to the suggest server to request contextual suggestions. For example, - this is only supported for users who have Google as their default search - engine (unmodified version of Google), have search suggest enabled, are - signed-in and syncing without a custom passphrase, and don't have an - incognito window open. There are other criteria too. Recorded on focus in - the omnibox if there is default search provider and we've constructed a - suggest URL. - - Some additional guidelines: if an incognito window is open, all focus events - will go into the "generally ineligible" bucket. Likewise, if the - current page is a search results page, we don't allow contextual suggestions - either so focus events on those pages go in the "generally - ineligible" bucket. The difference between "eligible" and - "generally eligible but not this time" depends only the properties - of the current URL. - - Recorded regardless of whether contextual or non-contextual zero suggest is - currently enabled on the user's platform. However, if zero suggest (in all - forms) is entirely disabled, the user will be perpetually ineligible. - - - - - mpearson@chromium.org - jdonnelly@chromium.org - - Whether the user has settings configured so that the current page URL can be - sent to the suggest server to request contextual suggestions. For example, - this is only supported for users who have Google as their default search - engine (unmodified version of Google), have search suggest enabled, are - signed-in and syncing without a custom passphrase, and don't have an - incognito window open. There are other criteria too. Recorded on focus in - the omnibox if there is default search provider and we've constructed a - suggest URL. - - Some additional guidelines: if an incognito window is open, all focus events - will go into the "generally ineligible" bucket. Likewise, if the - current page is a search results page, we don't allow contextual suggestions - either so focus events on those pages go in the "generally - ineligible" bucket. The difference between "eligible" and - "generally eligible but not this time" depends only the properties - of the current URL. - - Recorded regardless of whether contextual or non-contextual zero suggest is - currently enabled on the user's platform. However, if zero suggest (in all - forms) is entirely disabled, the user will be perpetually ineligible. - - This histogram captures all scenarios that are generally ineligible for zero - suggest suggestions (including incognito mode), and reports eligibility for - suggestions even if kOmniboxPopupShortcutIconsInZeroState is enabled - (meaning: suggestions are not shown, but current URL is eligible). - - - - - mpearson@chromium.org - jdonnelly@chromium.org - - Whether the user has settings configured so that the current page URL could - be sent to the suggest server to request contextual suggestions. For - example, this is only supported for users who have Google as their default - search engine (unmodified version of Google), have search suggest enabled, - and are signed-in and syncing without a custom passphrase. There are other - criteria too. Recorded on profile open. Note that opening an incognito - window (if none are currently open under the given profile) counts as - opening a new profile. - - Some additional guidelines: unlike Omnibox.ZeroSuggest.Eligible.OnFocus, - because this is recorded on profile open, users cannot be declared - ineligible because they have an incognito window open (it's impossible to - have an incognito window open for a given profile at the time of profile - open) and also cannot be declared ineligible because the user is viewing a - search results page. (We test this on-profile-open using an arbitrary URL.) - - Recorded regardless of whether contextual or non-contextual zero suggest is - currently enabled on the user's platform. However, if zero suggest (in all - forms) is entirely disabled, the user will be perpetually ineligible. - - - - - - Removed from code as of M87 / September 2020. This is no longer useful. - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Whether the user is eligible to receive personalized zero suggestions on the - NTP. This histogram is updated only when the user focuses the omnibox on the - NTP and is emitted only once even if multiple criteria make a user - ineligible. Consult the source code to learn more about the precedence of - these values. - - This metric is recorded for all contexts (including users non-syncing, in - incognito mode, or using different search engines) and targets specifically - eligibility in the current situation. - - - - - - Removed from code as of M87 / September 2020. This is no longer useful. - - ender@chromium.org - mpearson@chromium.org - jdonnelly@chromium.org - - Whether the user is eligible to receive personalized zero suggestions on the - NTP. This histogram is updated every time Chrome registers a profile change. - - This metric is recorded for all contexts (including users non-syncing, in - incognito mode, or using different search engines) and targets overall - profile eligibility to receive zero-prefix query suggestions on a New Tab - Page. - - - - - - Obsolete as of M85. Added back in 2013 (https://crrev.com/23600051), this is - no longer useful. - - mpearson@chromium.org - jdonnelly@chromium.org - hfung@chromium.org - - The number of most visited suggestions returned when ZeroSuggest would have - triggered. The suggestions appear when the user has focused but not modified - the omnibox. - - - - - ender@chromium.org - tommycli@chromium.org - chrome-omnibox-team@google.com - - Counts about the number of zero suggest requests (requests for suggestions - when the user has focused but not modified the omnibox) the omnibox sent, - invalidated, and replies received. - - - - - - Obsolete because of using suffixes. - - jeffreycohen@chromium.org - sebsg@chromium.org - - Whether the user has clicked the item when it is shown" Logged when the - share option is shown in the omnibox context menu" - - - - - raleksandrov@google.com - cros-oac@google.com - - Whether the review Google Play following setup box is checked. Recorded when - user leaves ArcTermsOfService screeen. - - - - - alemate@chromium.org - rsorokin@chromium.org - cros-oac@google.com - Time from the login screen start to user session start. - - - - raleksandrov@google.com - cros-oac@google.com - - Time spent on error screens during enrollment or autoenrollment. - - - - - raleksandrov@google.com - cros-oac@google.com - Time spent on error screens during signin. - - - - raleksandrov@google.com - cros-oac@google.com - - Time spent on error screens during supervised user creation. - - - - - raleksandrov@google.com - cros-oac@google.com - Time spent on error screens during update. - - - - raleksandrov@google.com - cros-oac@google.com - - Tracks all user actions on the EULA screen. Recorded when user clicks on - buttons on the EULA screen. - - - - - - - rsorokin@chromium.org - alemate@chromium.org - cros-oac@google.com - - Time from acceptance of the EULA until the login screen is first displayed. - - - - - raleksandrov@google.com - cros-oac@google.com - - Tracks all user actions on the fingerprint screen. Recorded when user clicks - on buttons on the fingerprint screen. - - - - - - - mmourgos@chromium.org - tbarzic@chormium.org - - Records the amount of time that each page within the gesture navigation OOBE - screen is shown. Recorded when the gesture navigation oobe screen is - exiting. - - - - - rrsilva@google.com - cros-oac@google.com - - The result of a request performed by the MarketingBackendConnector used in - the OOBE MarketingOptInScreen when subscribing the user to Chromebook - emails. This data is used to determine the success rate of the requests - being performed. - - - - - rrsilva@google.com - cros-oac@google.com - - Records the choice a user takes when prompted with a toggle on the OOBE - MarketingOptInScreen to subscribe to Chromebook emails. - - - - - rrsilva@google.com - cros-oac@google.com - - Records whether the user's geolocation was resolved successfully. - - - - - rrsilva@google.com - cros-oac@google.com - - Records the length of the country code that was returned when determining - the user's geolocation. - - - - - achuith@google.com - - Number of times error screen has appeared during enrollment or - autoenrollment. - - - - - achuith@google.com - Number of times error screen has appeared during signin. - - - - - Obsolete as of M85. Supervised screen has gone so this metric became - obsolete. - - raleksandrov@google.com - cros-oac@google.com - - Number of times error screen has appeared during supervised user creation. - - - - - achuith@google.com - Number of times error screen has appeared during update. - - - - raleksandrov@google.com - cros-oac@google.com - play-bm-eng@google.com - The number of recommended apps. - - - - rsorokin@chromium.org - cros-oac@google.com - play-bm-eng@google.com - The time it takes to fetch the recommended apps. - - - - rsorokin@chromium.org - cros-oac@google.com - chromesky-eng@google.com - The response code of fetching the recommended apps. - - - - rsorokin@chromium.org - cros-oac@google.com - chromesky-eng@google.com - The result of parsing the recommend-apps response. - - - - - Removed as of 08/27/2020. No longer needed to track size of a response. - - raleksandrov@google.com - cros-oac@google.com - chromesky-eng@google.com - The size of the recommend-apps JSON response. - - - - rsorokin@chromium.org - cros-oac@google.com - chromesky-eng@google.com - The user action on the recommend apps screen. - - - - rsorokin@chromium.org - cros-oac@google.com - chromesky-eng@google.com - The number of apps user selected. - - - - raleksandrov@google.com - cros-oac@google.com - chromesky-eng@google.com - The ratio of selected and recommended apps. - - - - rsorokin@chromium.org - cros-oac@google.com - chromesky-eng@google.com - Whether the reocmmend apps screen is shown. - - - - - - alemate@chromium.org - antrim@chromium.org - rsorokin@chromium.org - cros-oac@google.com - Time spent on specific OOBE screen. - - - - raleksandrov@google.com - cros-oac@google.com - Time spent on specific OOBE screen grouped by exit reason. - - - - jamescook@chromium.org - cros-oac@google.com - - Whether the sync consent screen was shown, skipped with sync disabled, or - skipped with sync enabled. Recorded when the screen is closed. Metrics - Sync.InitialState and OOBE.SyncConsentScreen.SyncEnabled provide more detail - on the state of the sync engine. - - - - - raleksandrov@google.com - cros-oac@google.com - - Whether the review following setup box is checked. Recorded when user leaves - SyncConsent screen. - - - - - jamescook@chromium.org - cros-oac@google.com - - Final state of the sync service at the end of the sync consent OOBE step. - The dialog may have been shown or skipped (e.g. by enterprise policy). See - OOBE.SyncConsentScreen.Behavior for skip reasons. - - - - - jamescook@chromium.org - cros-oac@google.com - - Which button the user clicked on the out-of-box sync consent screen. - Recorded when the user clicks the button, which also closes the screen. - - - - - dkuzmin@google.com - cros-oac@google.com - - Time spent on Checking of the ChromeOS update. Recorded when the stage is - done and the next stage is about to start. - - - - - dkuzmin@google.com - cros-oac@google.com - - Time spent on Downloading of the ChromeOS update. Recorded when the stage is - done and the next stage is about to start. - - - - - dkuzmin@google.com - cros-oac@google.com - - Time spent on Finalizing of the ChromeOS update. Recorded when the stage is - done and the next stage is about to start. - - - - - dkuzmin@google.com - cros-oac@google.com - - Time spent on Verifying of the ChromeOS update. Recorded when the stage is - done and the next stage is about to start. - - - - - raleksandrov@google.com - cros-oac@google.com - - Time spent on downloading ChromeOS update when critical updated is found - during OOBE. Recorded when update is uploaded and ChromeOS device is about - to restart to apply the update. - - - - - rsorokin@chromium.org - cros-oac@google.com - - Measures time spent by switch between WebUI and Views-based display hosts. - - - - - dkuzmin@google.com - cros-oac@google.com - - Measures usage of the accessibility options on the welcome screen during - OOBE. Recorded when user enables or disables any of the accessibility - options from accessibility menu on the welcome screen. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - The decision made for whether the optimization type can be applied on the - page load. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - Records the decision made for whether the optimization type can be applied - on a page load when all information for that page load has been sufficiently - gathered. This will be recorded once per callback registered, so if two - callbacks were registered for the same optimization type and page load, this - will be recorded twice for that case. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records whether the optimization guide store was available when fetched - hints are cleared from the store after browser history is cleared. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records whether the optimization guide store was available when host model - features are cleared from the store after browser history is cleared. - - - - - - Removed as of 01/2020. - - mcrouse@chromium.org - dougarnett@chromium.org - - The remaining time a fetched hint that was loaded for use has before it - expires and is removed from the hint cache store. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - dougarnett@chromium.org - sophiechang@chromium.org - - Records when the optimization guide hint cache has a hint entry for a URL's - host at commit time. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - dougarnett@chromium.org - sophiechang@chromium.org - - Records when the optimization guide hint cache has a hint entry for a URL's - host before commit time (e.g., at original navigation time or redirected - navigation time). - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the store entry type of a hint when it is loaded from the hint cache - store. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - dougarnett@chromium.org - sophiechang@chromium.org - - Records when the optimization guide hint cache has a loaded hint entry - matching a URL's host at commit time. This is recorded regardless of whether - an associated preview type is allowed for the navigation or not. If no - associated preview type is allowed, the hint will not be loaded from a - backing store, so this will only capture matches for in-memory hints. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - dougarnett@chromium.org - sophiechang@chromium.org - - Records when the optimization guide hint cache has a loaded page hint for a - URL at commit time. This is recorded regardless of whether an associated - preview type is allowed for the navigation or not. If no associated preview - type is allowed, the hint will not be loaded from a backing store, so this - will only capture matches for in-memory hints. - - - - - dougarnett@chromium.org - sophiechang@chromium.org - - Records the result of loading the metadata while initializing the - HintCacheLevelDBStore. - - - - - dougarnett@chromium.org - sophiechang@chromium.org - - Records each status change within the HintCacheLevelDBStore. - - - - - - Removed as of 01/2020. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records that a fetched hint loaded from the store has expired. If expired, - the hint is not provided. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - mcrouse@chromium.org - sophiechang@chromium.org - - Records once per navigation if the host that was navigated to was included - in a hints fetch request in the last 7 days, even if no hints were returned, - or had a hint served via the Optimization Hints component at commit. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - sophiechang@chromium.org - mcrouse@chromium.org - - Records once per navigation if the host that was navigated to was included - in a hints fetch request in the last 7 days, even if no hints were returned, - or had a hint served via the Optimization Hints component before commit. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - Records when an in-flight hints request was canceled before it finished. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - The duration of a request to fetch hints from the remote Optimization Guide - Service starts until it completes. Recorded every time hints are fetched and - parsed successfully. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the number of hints received from the remote Optimization Guide - Service for every successful HintsFetch request. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts selected for sending a hint request. This will - be captured when any hint request is initiated. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - Net error codes for HintsFetch requests to the Optimization Guide Service on - success and failure. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - For each HintsFetch request to the Optimization Guide Service, log the HTTP - response code on success and failure. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the number of URLs selected for sending a hint request. This will be - captured when any hint request is initiated. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records when hints fetching is enabled whether the HTTPS host being - navigated to was included in a hints fetch request and any hints returned - have not since expired. Captured at navigation start so it will not include - hints fetched based on the current navigation. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records whether the host being navigated to was included in a hints fetch - request and any hints returned have not since expired. Captured after a - navigation is committed in order to determine if the fetch attempt made at - navigation start succeeded or not. - - - - - - Obsolete as of 04/2020 since this histogram no longer makes sense with the - current request flow. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records whether the host being navigated to was included in a hints fetch - request and any hints returned have not since expired. Captured at - navigation start so will not include any newly fetched hints for this - navigation. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - The status of making a Batch Update context request of the OptmizationGuide - HintsFetcher. This includes whether a network request was actually sent or - not. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - The status of making a Page Navigation context request of the - OptmizationGuide HintsFetcher. This includes whether a network request was - actually sent or not. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts placed on the HintsFetcherTopHostBlacklist when - it is initialized. - - - - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts on the HintsFetcherTopHostBlacklist when top - hosts are requested. - - - - - - Removed as of 08/2019 - - mcrouse@chromium.org - dougarnett@chromium.org - - Records whether the host being navigated to was included in a hints fetch - and any hints returned have not since expired. - - - - - - Removed as of 08/2019 - - dougarnett@chromium.org - sophiechang@chromium.org - - The percentage (0-100) of hints loaded over all attempted page loads between - component updates. Recorded when the OptimizationGuideService receives a - component with a new version. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - The number of active hints fetches initiated by the hints manager. Recorded - when a fetch is initiated to the remote Optimization Guide Service at - navigation start. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Status of a fetch attempt being raced against the current navigation start - and whether it includes hosts and urls. Recorded on navigation start - (including client redirects) by the hints manager. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records whether the prediction model being constructed for an optimization - target is valid or not. Recorded when prediction models are loaded into - memory by the prediction manager. - - - - - dougarnett@chromium.org - sophiechang@chromium.org - - Status of processing OptimizationFilter configurations for server-provided - blacklists. Recorded when the OptimizationGuideService receives a - notification to process hints. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - Records the major version of the Optimization Hints component that was - pushed to the client. This will be recorded at startup and when a new - component is received. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Whether the PredictionManager had HostModelFeatures for the host of the - navigation. Recorded when ShouldTargetNavigation is called. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the number of host model features loaded into the map used by the - PredictionManager. This is recorded when the host model features are loaded - from the store. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - The duration of evaluating a prediction model for a registered optimization - target. Recorded every time a prediction model is successfuly evaluated by - the prediction manager. Not recorded if a cached decision is used or if the - evaluation fails. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the number of hosts included in a remote Optimization Guide Service - client model request. This will be captured when any GetModelsRequest is - initiated. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the number of host model features received from the remote - Optimization Guide Service for every successful GetModelsRequest. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Net error codes for GetModelsRequest to the Optimization Guide Service on - success and failure. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - For each GetModelsRequest to the Optimization Guide Service, log the HTTP - response code on success and failure. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the version of the prediction model that was loaded from the store - and used until updated by a fetch. Recorded only if the loaded model was - valid. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the result of loading the host model features metadata while - initializing the OptimizationGuideStore. - - - - - - Removed as of 01/2020 since it rarely ever happens that there is a load - collision. - - mcrouse@chromium.org - sophiechang@chromium.org - - For each load of a prediction model from the OptimizationGuideStore, reports - whether the load collided with an update being made to the store. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the version of the prediction model that was fetched as an update. - Recorded only if a model returned was valid and is available for use. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the duration of construction and validation of a prediction model - when the prediction manager loads it into memory for a given optimization - target. Recorded only if the model is valid and successfully loaded into - memory for use. - - - - - - Removed as of 05/2020 to in favor of recording the version on update and on - load. - - mcrouse@chromium.org - sophiechang@chromium.org - - Records the version of the prediction model being updated and stored in the - prediction model store and made available for use. Recorded only if the - model is valid and successfully loaded into memory for use. - - - - - dougarnett@chromium.org - sophiechang@chromium.org - - Whether processing the hints succeeded or failed at a particular step. - Recorded when the OptimizationGuideService receives a notification to - process hints. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - Whether the session is enabled for fetching information from the remote - Optimization Guide Service. Recorded when the profile is initialized for the - session if Optimization Hints are enabled and the profile is a non-incognito - profile. - - - - - mcrouse@chromium.org - sophiechang@chromium.org - - The status of the prediction model for an optimization target within the - prediction manager. Recorded when the manager is asked if a navigation - should be targeted and the decision for the navigation has not already been - made. - - - - - sophiechang@chromium.org - mcrouse@chromium.org - - The decision made for whether the page load matches the optimization target. - - - - - - Removed with CL 731423002. OriginChip has been removed. - - gbillock@chromium.org - The number of clicks on the origin chip. - - - - - Obsolete as of Chrome 54. Sort of replaced by OriginTrials.ValidationResult. - - chasej@chromium.org - iclelland@chromium.org - - Counts the results of origin trial checks to enable experimental features. - The result for each feature check is counted at most once per execution - context (e.g. page, worker). - - - - - - Obsolete as of Chrome 54. - - chasej@chromium.org - iclelland@chromium.org - - Counts how often an error message is generated for each origin trial check - to enable an experimental feature. - - - - - chasej@chromium.org - iclelland@chromium.org - feature-control@chromium.org - - Counts the results of token validation checks to enable experimental - features. The result for each token validation check is counted once per - token per execution context (e.g. page, worker). - - - - - cfroussios@chromium.org - mamir@chromium.org - - The backend selected for this user and whether it was initialised - successfully. - - - - - - Obsolete as of Chrome M81. - - cfroussios@chromium.org - vasilii@chromium.org - - Error code returned by SecKeychainFindGenericPassword when the encryption - key is retrieved. - - - - - - Obsolete as of Chrome 72. - - tsabolcec@google.com - vasilii@chromium.org - - The number of times that Chrome prevented overwriting the encryption key in - a row. This metric is logged once on startup. - - - - - - Obsolete as of Chrome M81. - - cfroussios@chromium.org - vasilii@chromium.org - - Result of the second call to SecKeychainFindGenericPassword when the - encryption key was not found but was expected to be there. - - - - - - Obsolete as of Chrome M81. - - cfroussios@chromium.org - vasilii@chromium.org - - Action taken when retrieving the encryption key from the Keychain. This - metric is logged once on startup. - - - - - wfh@chromium.org - forshaw@chromium.org - - The Windows GetLastError after a failure from calling into DPAPI to decrypt - the master key for the os_crypt library on Windows. This is recorded during - the OSCrypt::Init each time the decryption fails. - - - - - - Obsolete as of Chrome 73. This has been replaced by Bluetooth.Availability. - - erikchen@chromium.org - - The availability and capabilities of the Bluetooth driver on OSX devices. - This metric is logged on startup. - - - - - - Obsolete as of Chrome 43. See OmahaProxy for more relevant statistics. - - mark@chromium.org - The cat's flavor and how many bits there are in it. - - - - mark@chromium.org - Events seen by the OSX NSException swizzle. - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - Records the Fast User Switching events that occur. - - - - - Removed as of Chrome 40. See OSX.Fullscreen.Enter.Style, - OSX.Fullscreen.Enter.WindowLocation and - OSX.Settings.ScreensHaveSeparateSpaces. - - erikchen@chromium.org - - This event is recorded each time a user triggers fullscreen for a browser - window. The value's bits reflect different parameters. Bit 0: Fullscreen - entry mechanism (AppKit vs Immersive). Bit 1: Whether the window was on the - primary screen (Primary vs. Secondary). Bit 2: Whether displays have - separate spaces options is enabled (Seperate vs Shared). Bit 3: Whether - there are multiple screens. - - - - - spqchan@chromium.org - - This event is recorded each time a user triggers fullscreen for a browser - window. It indicates if the fullscreen is triggered for the browser or the - tab content. - - - - - erikchen@chromium.org - - This event is recorded each time a user triggers fullscreen for a browser - window. It indicates the mechanism (immersive vs. AppKit) and the type of - AppKit Fullscreen (Presentation Mode vs. Canonical Fullscreen). - - - - - erikchen@chromium.org - - This event is recorded each time a user triggers fullscreen for a browser - window. It indicates the screen in which the window was fullscreened, and - the number of screens available. - - - - - - Removed as of 11/2018. - - spqchan@chromium.org - - This event is recorded each time a user triggers fullscreen and when the - fullscreen toolbar is updated with a new style. - - - - - erikchen@chromium.org - - This event is recorded each time a Handoff is received by Chrome on OSX. The - enumeration indicates the source of the Handoff. - - - - - avi@chromium.org - mark@chromium.org - - The instances of other copies of Google Chrome on the user's Mac. Logged - once on startup, and only for Chrome Beta and Chrome Dev. Will be used to - determine if/how home directory migration will be done for side-by-side. - - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - Records the filesystem type that the app lives on. - - - - - Removed 2020 August. - - kerrnel@chromium.org - mark@chromium.org - - The number of previous times that the keychain reauthorization did not - complete, when run during the main browser launch. - - - - - - Removed 2020 August. - - kerrnel@chromium.org - mark@chromium.org - - The number of previous times that the keychain reauthorization did not - complete, when run at update time. - - - - - - Removed 2020 August. - - kerrnel@chromium.org - mark@chromium.org - - How many times the keychain reauthorization ran before finally succeeding, - when run at update time. - - - - - - Removed 2020 August. - - kerrnel@chromium.org - mark@chromium.org - - How many times the keychain reauthorization ran before finally succeeding, - when run during the main browser launch. - - - - - lgrey@chromium.org - - Whether the user successfully shared via a native sharing extensions after - selecting it from the share menu. False can indicate failure or - user-initiated cancellation. - - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - - Records how many other instances of this binary are running at startup. - - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - - The result of the update process's check for other instances of Chrome. - - - - - - Removed as of 11/2015. - - erikchen@chromium.org - - This event records the amount of time that the browser process main thread - blocks, waiting for a frame with the right dimensions to arrive from the gpu - process. - - - - - erikchen@chromium.org - - The configuration of the setting "Screens Have Separate Spaces" - available in OSX 10.9+. - - - - - - Removed as of Chrome 51 since Mach has become the default mechanism. - - erikchen@chromium.org - - A histogram entry is emitted each time a base::SharedMemory object is - constructed. The value of the entry indicates the mechanism used to back the - shared memory region. - - - - - - Removed as of 02/2019 in favor of StagingDirectoryLocation2. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - Records first staging directory location that works. - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - - Records, during Chrome startup, the first staging directory location that - works. This is for the change to the updating system. - - - - - - Removed 2020 January. - - avi@chromium.org - rsesek@chromium.org - mark@chromium.org - - Records, during Chrome startup, the state of any staged updates. - - - - - erikchen@chromium.org - - Whether an attempt to load the system hotkeys on a Mac was successful. - - - - - mad@chromium.org - - Counts the number of times the user clicked on the later button of the - outdated upgrade bubble, before clicking on the enable updates button in the - same Chrome session. - - - - - mad@chromium.org - - Counts the number of times the user clicked on the later button of the - outdated upgrade bubble, before clicking on the reinstall button in the same - Chrome session. - - - - - - Replaced with HeapProfiling.ProfiledProcess.Type. - - erikchen@chromium.org - - One metric is emitted every 24-hours after Chrome is launched for every - process that is being profiled. The timer is reset if Chrome exits. - - - - - - Replaced with HeapProfiling.ProfilingMode. - - erikchen@chromium.org - - One metric is emitted every 24-hours after Chrome is launched for every - Chrome instance that is using out of process heap profiling. The timer is - reset if Chrome exits. - - - - - - Replaced with HeapProfiling.RecordTrace.Success. - - erikchen@chromium.org - - The metric is emitted each time Chrome attempts to record a memory-infra - trace to upload an out-of-process heap-profiling memory dump. - - - - - - Replaced with HeapProfiling.UploadTrace.Size. - - erikchen@chromium.org - - The metric is emitted each time Chrome uploads a trace. It reflects the - uncompressed size of the trace. - - - - - - Replaced with HeapProfiling.UploadTrace.Success. - - erikchen@chromium.org - - The metric is emitted each time Chrome uploads a trace. It reflects whether - the upload was successful. - - - - - - Removed as of Chrome 59 in favour of Overscroll.Cancelled3. - - rbyers@chromium.org - nzolghadr@chromium.org - - Overscroll gestures that were aborted before they were completed. - - - - - nzolghadr@chromium.org - - Overscroll gestures that were aborted before they were completed. - - - - - - Removed as of Chrome 44 in favour of Overscroll.Cancelled and - Overscroll.Navigated2. - - rbyers@chromium.org - mfomitchev@chromium.org - Completed overscroll gestures. -
- An overscroll gesture starts when user scrolls past the edge of the web page - and continues scrolling in the same direction. An overscroll gesture is - completed when user stops scrolling (e.g. by lifting the fingers from the - touchscreen or touchpad). -
- - - - - Removed as of Chrome 44 to switch to NavigationDirection enum. - - rbyers@chromium.org - mfomitchev@chromium.org - - Navigations that were triggered due to completed overscroll gesture. Note - that not all completed overscroll gestures trigger a navigation. - - - - - - Removed as of Chrome 59 in favour of Overscroll.Navigated3. - - rbyers@chromium.org - mfomitchev@chromium.org - - Navigations that were triggered due to completed overscroll gesture. Note - that not all completed overscroll gestures trigger a navigation. - - - - - nzolghadr@chromium.org - - Navigations that were triggered due to completed overscroll gesture. Note - that not all completed overscroll gestures trigger a navigation. - - - - - - Removed as of Chrome 44 to switch to NavigationDirection enum. - - rbyers@chromium.org - mfomitchev@chromium.org - - Overscroll gestures initiated by the user. Note that not all overcroll - gestures started are completed (e.g. the overscroll gesture is aborted if - user clicks or presses a key during the gesture). - - - - - - Removed as of Chrome 59 in favour of Overscroll.Started3. - - rbyers@chromium.org - mfomitchev@chromium.org - - Overscroll gestures initiated by the user. Note that not all overscroll - gestures started are completed (e.g. the overscroll gesture is aborted if - user clicks or presses a key during the gesture). - - - - - nzolghadr@chromium.org - - Overscroll gestures initiated by the user. Note that not all overscroll - gestures started are completed (e.g. the overscroll gesture is aborted if - user clicks or presses a key during the gesture). - - - - - napper@chromium.org - robsc@chromium.org - - When a stylus is touched to screen, the number of palms on the device at - that time. - - - - - napper@chromium.org - robsc@chromium.org - - The time between a finger and a stylus touch. The finger may or may not - still be on the touchscreen. - - - - - napper@chromium.org - robsc@chromium.org - - The time between a palm and a stylus touch. The palm may or may not still be - on the touchscreen. - - - - - robsc@chromium.org - - The count of the number of held events cancelled when we decide to finally - cancel a stroke. Only reported if events have been held, and will be - positive. Events are only held from PalmDetectionFilter. - - - - - robsc@chromium.org - - The count of the number of held events released at once for a stroke when we - decide to release. Only reported if events have been held, and will be - positive. Events are only held from PalmDetectionFilter. - - - - - - Removed Nov 2019 - - pkotwicz@google.com - - The squared distance between taps which occur in quick succession. Only - reported when the taps are far apart and touch noise filtering is enabled. - - - - - - Removed Nov 2019 - - pkotwicz@google.com - - The horizontal distance from a "touch press" to the closest other - touch. Only reported if there are two or more fingers onscreen and touch - noise filtering is enabled. - - - - - - Removed Nov 2019 - - pkotwicz@google.com - - The amount of time between noisy touches. The amount of time since Chrome - startup is recorded for the first noisy touch after startup. - - - - - - Removed Nov 2019 - - pkotwicz@google.com - - The time between taps which occur in quick succession at the same screen - location. Only reported when touch noise filtering is enabled. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The wall-clock time spent until a lookup was canceled. This is reported - every time p2p is used to find a candidate but the request was canceled. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of candidates on the LAN, i.e. the number of peers on the LAN - offering at least N bytes of the requested file X. This is reported after - examining responses from all peers on the LAN and picking a candidate. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of p2p downloads of the peer that the returned URL points to. - This is reported after examining responses from all peers on the LAN and - picking a candidate. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The wall-clock time spent waiting for the LAN-wide number of p2p downloads - (i.e. the sum of p2p downloads from each peer on the LAN) to drop below the - threshold. This is reported after examining responses from all peers on the - LAN and picking a candidate. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The result of the lookup. Possible values include "Found" (if a - candidate - i.e. a peer offering at least N bytes of file X - was chosen), - "Not Found" (if no candidate could be found), "Vanished" - (if a candidate was found but vanished while waiting in line), - "Canceled" (if a candidate was found but the request was canceled - while waiting in line), and "Filtered" (if it was detected that - mDNS was filtered). This is reported after examining responses from all - peers on the LAN when p2p is used to find a candidate. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of peers implementing p2p file sharing on the network. This is - reported every time p2p is used to look up a resource on a network where - mDNS is not filtered. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The wall-clock time spent waiting for one or more candidates (i.e. peers - offering at least N bytes of file X) that all vanished before the LAN-wide - number of p2p downloads dropped below the threshold. This is reported every - time candidates were found using p2p but then vanished. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of currently connected HTTP clients. This is reported every time - a HTTP client connects. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - Number of megabytes (1,000,000 bytes) served from the device (via HTTP) - where the client disconnects prematurely. This is reported every time a file - is served and the client disconnects before receiving all data. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - Number of megabytes (1,000,000 bytes) served from the device (via HTTP). - This is reported every time a file have been served successfully. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The average speed at which the download was served at, in kB/s. This is - reported every time a file have been served successfully. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of files available via p2p. This is reported every time a file is - added or removed to the /var/cache/p2p directory. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - When a client resumes a download, the HTTP request includes range specifier - to skip the bytes it already has. This metric conveys this as a percentage - of the file size. This is reported every time a file is served, even if the - request does not include a range specifier (in which case 0 is reported). - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The result of the HTTP request. Possible values include "Response - Sent" (the resource was found and the response was successfully sent), - "Response Interrupted" (the resource was found but the client - disconnected), "Malformed" (the request was malformed), "Not - Found" (the request was for a resource that was not found), and - "Index" (the request was for the '/' or '/index.html' resource). - This is reported for every HTTP request handled. - - - - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of Extensions that have Page Actions. Measured once per startup - per profile. - - - - - - Removed In June 2019. - - kouhei@chromium.org - - Number of pages that had any HTML form interaction before next page load. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - bmcquade@chromium.org - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted due to being backgrounded. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a client side redirect (Javascript navigation). - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by the user closing the tab or browser. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a forward or back navigation. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a new navigation. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted. The abort cause is unknown. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a reload. - - - - - - Removed in favor of PageLoad.Experimental.AbortTiming equivalent. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by the user pressing stop. - - - - - - We now have sufficient infrastructure to always characterize aborts that - resulted in new navigations. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a navigation with unknown transition type. - - - - - - Removed 07/2020. Replaced with - PageLoad.Clients.Ads.AdPaintTiming.NavigationToFirstContentfulPaint2; see - http://crbug.com/1103782. - - jkarlin@chromium.org - johnidel@chromium.org - - Records the time from frame navigation start to FirstContentfulPaint of each - ad frame that receives a FirstContentfulPaint. The time could be quite - large, as some ads don't paint until they're scrolled into view. But the - metric is still useful in aggregate. - - Recorded for all ad frames with non-zero bytes or cpu usage that receive a - FirstContentfulPaint. Recorded when the ad frame or page is destroyed. - - - - - jkarlin@chromium.org - johnidel@chromium.org - - Records the time from frame navigation start to FirstContentfulPaint of each - ad frame that receives a FirstContentfulPaint. The time could be quite - large, as some ads don't paint until they're scrolled into view. But the - metric is still useful in aggregate. - - Recorded for all ad frames with non-zero bytes or cpu usage that receive a - FirstContentfulPaint. Recorded when the ad frame or page is destroyed. - - - - - altimin@chromium.org - bmcquade@chromium.org - hajimehoshi@chromium.org - - Counts the events related to the back-forward cache, like when the page is - put into the back-forward cache. - - - - - jkarlin@chromium.org - johnidel@chromium.org - - Only recorded if the page has at least one identified ad frame. Recorded in - PageLoadMetrics when the page is destroyed. Bytes include all bytes used by - the network to load a resource and response body bytes for cached resources - (from both the HTTP and memory caches). An ad frame consists of the - identified ad frame and all of its children (which may also be ads, but are - counted as part of the ancestor ad frame). Includes resources that did not - finish loading. - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.Network. - - jkarlin@chromium.org - - The size (in KB) of the resources loaded for all of the ad frames on the - page that loaded over the network. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.PercentNetwork. - - jkarlin@chromium.org - - The percentage of bytes loaded for all ad frames that were loaded over the - network. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.Total. - - jkarlin@chromium.org - - The size (in KB) of the resources loaded for all of the ad frames on the - page. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.Network. - - jkarlin@chromium.org - - The size (in KB) of the resources loaded for an ad frame from the network. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.PercentNetwork. - - jkarlin@chromium.org - - The percentage of bytes loaded for a single ad frame that were loaded over - the network. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.Total. - - jkarlin@chromium.org - - The size (in KB) of the resources loaded for an ad frame. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Network. - - jkarlin@chromium.org - - The size (in KB) of all of the page's resources that loaded over the - network. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.FullPage.Network.PercentAds. - - jkarlin@chromium.org - - The percentage of bytes loaded for the page (from the network) that came - from resource loads in ad frames (from the network). - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Total. - - jkarlin@chromium.org - - The size (in KB) of all of the page's resources. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.FullPage.Total.PercentAds. - - jkarlin@chromium.org - - The percentage of bytes loaded for the page that came from resource loads in - ad frames. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - - Removed 01/2019. Replaced with - PageLoad.Clients.Ads.Bytes.NonAdFrames.Aggregate.Total. - - jkarlin@chromium.org - - The size (in KB) of all of the page's resources except for those loaded in - ad frames. - - Only recorded if the page has at least one identified ad frame. Bytes are - measured as over-the-wire (e.g., compressed) response body KBs and do not - include header bytes. An ad frame consists of the identified ad frame and - all of its children (which may also be ads, but are counted as part of the - ancestor ad frame). - - - - - justinmron@chromium.org - johnidel@chromium.org - - The page's maximum ad density by area over its lifecycle as a percent from - 0-100. The density measurement is throttled in page load metrics propagation - from renderer to browser and in the ads page load metrics observer, this may - lead to inaccurate maximum density. Recorded at the time a page is - destroyed. - - - - - justinmron@chromium.org - johnidel@chromium.org - - The page's maximum ad density by height over its lifecycle as a percent from - 0-100. The density measurement is throttled in page load metrics propagation - from renderer to browser and in the ads page load metrics observer, this may - lead to inaccurate maximum density. Recorded at the time a page is - destroyed. - - - - - justinmron@chromium.org - johnidel@chromium.org - - Whether the ad density was recorded on the page for both density by area and - density by height. Recorded at the time a page is destroyed. - - - - - - Removed In July 2018, metric was buggy for subresource filter ads. - - jkarlin@chromium.org - - When a frame that is (or previously was) an ad frame renavigates, record - whether it renavigated to an ad frame or a non-ad frame. - - An ad frame consists of the identified ad frame and all of its children. Its - children (which may also be ads) are not counted when they renavigate. - - This metric is recorded as the event happens. Note that this is unlike most - other Clients.Ads metrics, which are recorded when the page load is - complete. - - - - - - Removed In July 2018. - - jkarlin@chromium.org - - When a frame that has never been part of an ad frame renavigates, record - whether it renavigated to an ad frame or a non-ad frame. - - This metric is recorded as the event happens. Note that this is unlike most - other Clients.Ads metrics, which are recorded when the page load is - complete. - - - - - - Removed in September 2018. At deprecation, 98.12% of parent frames were - known. - - jkarlin@chromium.org - - Records whether or not a parent frame is found for a subframe that finishes - navigating. - - - - - - Removed in September 2018. At time of deprecation: Subframe 80%, Script - 6.5%, Images 10%, and XHR was 3%. - - jkarlin@chromium.org - - Records the content::ResourceType when a resource finishes loading but the - ads metrics aren't aware of a committed frame for the resource. - - - - - alexmt@chromium.org - johnidel@chromium.org - - Total number of network bytes that went towards loading non-ad resources for - a single page over its entire lifetime. This includes resources that did not - finish or were canceled. Only recorded for pages with non-zero total bytes, - including those without an ad frame and pages with no ad resources. Recorded - when the page is destroyed. - - - - - alexmt@chromium.org - johnidel@chromium.org - - The percentage of network bytes loaded by the page that are attributed to ad - resources (including ad resources in the main frame) across the entire page - load. Only recorded for pages with non-zero network bytes, including those - without an ad frame and pages with no ad resources. Recorded when the page - is destroyed. - - - - - alexmt@chromium.org - johnidel@chromium.org - - The percentage of all bytes loaded by the page that are attributed to ad - resources (including ad resources in the main frame) across the entire page - load. Only recorded for pages with non-zero total bytes, including those - without an ad frame and pages with no ad resources. Recorded when the page - is destroyed. - - - - - - Removed 01/19. - - johnidel@chromium.org - jkarlin@chromium.org - - Whether or not the ad frame had a display: none style set, meaning it was - not visible to the user. Only recorded for ad frames with non-zero total - bytes. Recorded when the page is destroyed or navigated. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records whether a frame that was created by ad script was ignored by - restricted AdTagging heuristics. This can occur if the frame was navigated - same-domain to the top-level page and did not have a matching blocklist - rule, or if the frame was navigated to an allowlist rule. If a frame is - initially ignored then later considered an ad, this is recorded twice for - that frame. For ignored frames, this is recorded at the time they would have - been initially tracked for metrics. For non-ignored frames, this is recorded - when the frame is destroyed, or when the page is destroyed/navigated. - - - - - - Removed In May 2017. - - jkarlin@chromium.org - - The number of frames (with parent frame of main frame) that are on the page - identified as Google Ad Frames. - - Only recorded if the page has at least one identified ad frame. Child frames - of an ad frame are not included in the count. - - - - - - Removed In May 2017. - - jkarlin@chromium.org - - The percentage of frames (with parent frame of main frame) on the page that - are identified as Google Ad Frames. - - Only recorded if the page has at least one identified ad frame. An ad frame - consists of the identified ad frame and all of its children (which may also - be ads, but are counted as part of the ancestor ad frame). - - - - - - Removed In May 2017. - - jkarlin@chromium.org - - The number of frames (with parent frame of main frame) on the page. - - Only recorded if the page has at least one identified ad frame. - - - - - - Removed In July 2017. Use - PageLoad.Clients.Ads.All.Navigations.AdFrameRenavigatedToAd instead. - - jkarlin@chromium.org - - When a frame that is (or previously was) an ad frame renavigates, record - whether it renavigated to an ad frame or a non-ad frame. - - An ad frame consists of the identified ad frame and all of its children. Its - children (which may also be ads) are not counted when they renavigate. - - This metric is recorded as the event happens. Note that this is unlike most - other Clients.Ads metrics, which are recorded when the page load is - complete. - - - - - - Removed In July 2017. Use - PageLoad.Clients.Ads.All.Navigations.NonAdFrameRenavigatedToAd instead. - - jkarlin@chromium.org - - When a frame that has never been part of an ad frame renavigates, record - whether it renavigated to an ad frame or a non-ad frame. - - This metric is recorded as the event happens. Note that this is unlike most - other Clients.Ads metrics, which are recorded when the page load is - complete. - - - - - - Removed In July 2017. Use PageLoad.Clients.Ads.All.ParentExistsForSubFrame - instead. - - jkarlin@chromium.org - - Records whether or not a parent frame is found for a subframe that finishes - navigating. - - - - - - Removed In July 2017. Use - PageLoad.Clients.Ads.All.ResourceTypeWhenNoFrameFound instead. - - jkarlin@chromium.org - - Records the content::ResourceType when a resource finishes loading but the - ads metrics aren't aware of a committed frame for the resource. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records whether the heavy ad intervention was disallowed by the blocklist on - a frame. Only recorded when the heavy ad blocklist is enabled and available - (e.g. this is not recorded in incognito mode). - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records whether a heavy ad frame was deleted prior to the page being - destroyed/navigated. Recorded per-frame, only if the frame is considered a - heavy ad, when the frame is destroyed. For example, this is true if the - iframe element is deleted by javascript. This is recorded whether or not the - ads are actually unloaded by the intervention. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records whether a possible intervention was ignored because the page was the - result of a reload. This is checked prior to checking whether a given site - is blocklisted. Therefore it is possible this histogram records |Ignored| - when the intervention wouldn't have actually triggered. This is recorded - when an ad frame becomes eligible for the heavy ad intervention to unload - it. - - - - - johnidel@chromium.org - justinmiron@google.com - - Records the number of network bytes used by a heavy ad unloaded due to - network usage by the heavy ad intervention. It is recorded at the time of - unload and the value may be larger than the heavy ads threshold due to the - delay in unloading an ad. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records whether a page with a heavy ad is reloaded or navigated/destroyed - for any other reason. Only recorded for pages that had at least one heavy ad - prior to being navigated/reloaded/destroyed. This is recorded whether or not - the ads are actually unloaded by the intervention. - - - - - - Removed March 2019 in favor of PageLoad.Clients.Ads.Resources.Bytes.Ads2. - - jkarlin@chromium.org - johnidel@chromium.org - - Total number of network bytes that went towards loading ad resources for a - single page over it's entire lifetime. This includes resources that did not - finish or were canceled. Only recorded for pages with non-zero ad bytes. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Total number of network bytes that went towards loading ad resources for a - single page over it's entire lifetime. This includes resources that did not - finish or were canceled. Only recorded for pages with non-zero ad bytes. - - - - - - Removed 02/2019. Replaced with - PageLoad.Clients.Ads.Bytes.MainFrame.Ads.Network. - - jkarlin@chromium.org - johnidel@chromium.org - - Total number of network bytes that were used to load top-level ad resources - on the page. This includes resources that did not finish or were canceled. - Only recorded for pages with non-zero ad bytes. - - - - - - Removed 01/19. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Network. - - jkarlin@chromium.org - johnidel@chromium.org - - Total number of network bytes that were used to load resources on the page. - This includes resources that did not finish loading or were canceled. Only - recorded for pages with non-zero ad bytes. - - - - - - Removed 04/2019 in favor of PageLoad.Experimental.Bytes.Unfinished. - - jkarlin@chromium.org - johnidel@chromium.org - - Total number of network bytes that were used to load resources that did not - finish loading on the page (e.g. ongoing video). This includes resource - loads that were canceled or resource loads that were ongoing when the page - was destroyed. Only recorded for pages with non-zero ad bytes. - - - - - - Removed 7/2019, replaced by - PageLoad.Clients.AMP.LayoutInstability.CumulativeShiftScore.Subframe - - bmcquade@chromium.org - skobes@chromium.org - - Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred - during the session, in the AMP subframe. Recorded for same-document - navigations. - - - - - - Removed 7/2019, replaced by - PageLoad.Clients.AMP.LayoutInstability.CumulativeShiftScore.Subframe.FullNavigation - - bmcquade@chromium.org - skobes@chromium.org - - Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred - during the session, in the AMP subframe. Recorded for non-same-document - navigations. - - - - - bmcquade@chromium.org - - The time from the user input that triggers the top-level navigation for an - AMP document to the time that the navigation for the AMP document is - initiated in the AMP frame. This gives insight into how often AMP documents - are navigated to via same document navigations without being prerendered. - - - - - bmcquade@chromium.org - - The time from the main frame navigation to the subsequent subframe - navigation for the AMP document. Only recorded for non-same-page - navigations. - - - - - bmcquade@chromium.org - - The time from navigation in the AMP frame to the user input that triggers - the top-level navigation for that AMP document. This gives insight into the - delta between when an AMP frame is prerendered and when it is actually - displayed for same document navigations. - - - - - - Removed July 2019 in favor of FirstInputDelay4. - - bmcquade@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation, in an AMP subframe document. Recorded on first page - interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes - scrolls. Only same-document navigations are included. - - - - - - Removed July 2019 in favor of FirstInputDelay4. - - bmcquade@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation, in an AMP subframe document. Recorded on first page - interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes - scrolls. Only non-same-document navigations are included. - - - - - bmcquade@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation, in an AMP subframe document. Recorded on first page - interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes - scrolls. Only same-document navigations are included. - - - - - bmcquade@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation, in an AMP subframe document. Recorded on first page - interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes - scrolls. Only non-same-document navigations are included. - - - - - bmcquade@chromium.org - skobes@chromium.org - - Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has - occurred in the AMP subframe. Recorded for same-document AMP navigations in - the main frame, at the end of the AMP document lifetime, such as when the - document is being navigated away from. - - - - - bmcquade@chromium.org - skobes@chromium.org - - Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has - occurred in the AMP subframe. Recorded for non same-document AMP navigations - in the main frame, at the end of the AMP document lifetime, such as when the - document is being navigated away from. - - - - - bmcquade@chromium.org - - The time from user input to first "contentful" paint in an AMP - subframe document. Will be zero or near-zero in cases where the AMP subframe - document was prerendered. Only same-document navigations are included. - - - - - bmcquade@chromium.org - - The time from user input to first "contentful" paint in an AMP - subframe document. Only non-same-document navigations are included. - - - - - bmcquade@chromium.org - - The time from user input to largest "contentful" paint in an AMP - subframe document. Only same-document navigations are included. - - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - Will be zero or near-zero in cases where the AMP subframe document was - prerendered. - - - - - bmcquade@chromium.org - - The time from user input to largest "contentful" paint in an AMP - subframe document. Only non-same-document navigations are included. - - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - - - - - Removed 7/2019. - - bmcquade@chromium.org - - The time from user input to largest "contentful" paint in an AMP - subframe document. Only same-document navigations are included. - - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - Will be zero or near-zero in cases where the AMP subframe document was - prerendered. - - - - - - Removed 7/2019. - - bmcquade@chromium.org - - The time from user input to largest "contentful" paint in an AMP - subframe document. Only non-same-document navigations are included. - - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - - - - - Removed 5/2019 - - bmcquade@chromium.org - Count of same document page views for AMP pages. - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - 100 times the ratio of network bytes received to network bytes the user - would have seen without data reduction proxy (not including headers) in a - page load that had its main resource loaded through data reduction proxy. - Recorded as a percent if the data reduction proxy saved the user data. - Recorded per page load when the user navigates away, hides the tab, or - backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - 100 times the ratio of network bytes received to network bytes the user - would have seen without data reduction proxy (not including headers) in a - page load that had its main resource loaded through data reduction proxy. - Recorded as a percent if the data reduction proxy saved the user data. - Recorded per page load when the user navigates away, hides the tab, or - backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the data - reduction proxy inflated for the user in a page load that had its main - resource was loaded through data reduction proxy. Recorded per page load - when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the data - reduction proxy inflated for the user in a page load that had its main - resource was loaded through data reduction proxy. Recorded per page load - when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The inflation in network kilobytes (not including headers) the user saw due - to using data reduction proxy in a page load that had its main resource was - loaded through data reduction proxy. Recorded as a percent when the user saw - inflated data. Recorded per page load when the user navigates away, hides - the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The inflation in network kilobytes (not including headers) the user saw due - to using data reduction proxy in a page load that had its main resource was - loaded through data reduction proxy. Recorded as a percent when the user saw - inflated data. Recorded per page load when the user navigates away, hides - the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes that were not fetched through the data - reduction proxy (not including headers) in a page load that had its main - resource was loaded through data reduction proxy. Recorded per page load - when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes that were not fetched through the data - reduction proxy (not including headers) in a page load that had its main - resource was loaded through data reduction proxy. Recorded per page load - when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the user would - have seen without using data reduction proxy in a page load that had its - main resource was loaded through data reduction proxy. Recorded per page - load when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the user would - have seen without using data reduction proxy in a page load that had its - main resource was loaded through data reduction proxy. Recorded per page - load when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The percent of network kilobytes (not including headers) in a page load that - went through data reduction proxy when the main resource was loaded through - data reduction proxy. Recorded per page load when the user navigates away, - hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The percent of network kilobytes (not including headers) in a page load that - went through data reduction proxy when the main resource was loaded through - data reduction proxy. Recorded per page load when the user navigates away, - hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes that were fetched through the data reduction - proxy (not including headers) in a page load that had its main resource was - loaded through data reduction proxy. Recorded per page load when the user - navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes that were fetched through the data reduction - proxy (not including headers) in a page load that had its main resource was - loaded through data reduction proxy. Recorded per page load when the user - navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the data - reduction proxy saved the user in a page load that had its main resource was - loaded through data reduction proxy. Recorded per page load when the user - navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that the data - reduction proxy saved the user in a page load that had its main resource was - loaded through data reduction proxy. Recorded per page load when the user - navigates away, hides the tab, or backgrounds the app. - - - - - - Removed 10/2018 - - bengr@chromium.org - ryansturm@chromium.org - - The percent of completed resources loaded from network in a page load that - use data reduction proxy when the main resource was loaded through data - reduction proxy. Recorded per page load when the user navigates away, hides - the tab, or backgrounds the app. - - - - - - Removed 05/2020 - - bengr@chromium.org - ryansturm@chromium.org - - Records info about the completed resources loaded from network in a page - load that use data reduction proxy when the main resource was loaded through - data reduction proxy. Recorded per page load when the user navigates away, - hides the tab, or backgrounds the app. The number of proxies, non-proxied, - percent of proxied are recorded as suffixes. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The actual delay added to page loads by DelayNavigationThrottle, for page - loads that started in the foreground and reached first paint in the - foreground. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The absolute delta between the specified and actual delays added to main - frame navigations by DelayNavigationThrottle, for page loads that started in - the foreground and reached first paint in the foreground. - - - - - - Removed March 2018 - - bmcquade@chromium.org - - The specified delay added to main frame navigations by - DelayNavigationThrottle, for page loads that started in the foreground and - reached first paint in the foreground. - - - - - bmcquade@chromium.org - - Counts the number of pages where a script loaded via document.write could - have been blocked. - - - - - shivanisha@chromium.org - bmcquade@chromium.org - jkarlin@chromium.org - - This metric measures the counts of pages for various loading behaviors of - document.written scripts. - - - - - shivanisha@chromium.org - bmcquade@chromium.org - - This metric measures reloads in pages that have synchronous, cross-origin - document.written scripts that could be blocked if document.write script - blocking feature is enabled. - - - - - - Removed in August 2020 as the behavior is launched - - xiaochengh@chromium.org - rendering-core-dev@chromium.org - - This metrics measures PageLoad.LayoutInstability.CumulativeShiftScore when - the first rendering cycle has been delayed in favor of font preloading - - - - - - Removed in August 2020 as the behavior is launched - - xiaochengh@chromium.org - rendering-core-dev@chromium.org - - This metrics measures - PageLoad.Experimental.PaintTiming.NavigationToLargestImagePaint when the - first rendering cycle has been delayed in favor of font preloading - - - - - - Removed in August 2020 as the behavior is launched - - xiaochengh@chromium.org - rendering-core-dev@chromium.org - - This metrics measures - PageLoad.Experimental.PaintTiming.NavigationToLargestTextPaint when the - first rendering cycle has been delayed in favor of font preloading - - - - - - Removed May 2018 - - mdw@chromium.org - Events related to Google CAPTCHA pages being seen by users. - - - - - Functionality removed in M77. - - bengr@chromium.org - ryansturm@chromium.org - - The number of network kilobytes (not including headers) that LoFi resources - used in a page load that had at least one LoFi resource. Recorded per page - load when the user navigates away, hides the tab, or backgrounds the app. - - - - - - Functionality removed in M77. - - bengr@chromium.org - ryansturm@chromium.org - - The number of network LoFi resources in a page load that had at least one - LoFi resource. Recorded per page load when the user navigates away, hides - the tab, or backgrounds the app. - - - - - - Removed June 2019. - - ksakamoto@chromium.org - - Records the number of tabs with inflight loading activities. Recorded when a - new page load starts. - - - - - tbansal@chromium.org - - Records if the time from navigation to first contentful paint was less than - the specified threshold. Also, records the total number of first contentful - paints. For a single first contentful paint event, data may be recorded in - multiple buckets. Recorded at the time when first contentful paint happens. - Recorded only for page loads that have scheme http://. - - - - - dougarnett@chromium.org - tbansal@chromium.org - - Records if the time from navigation to first contentful paint was less than - the specified threshold. Also, records the total number of first contentful - paints. For a single first contentful paint event, data may be recorded in - multiple buckets. Recorded at the time when first contentful paint happens. - Recorded only for page loads that have scheme http://, are user-initiated, - and are new navigations (that is, they are not reloads nor forward or back - navigations). - - - - - tbansal@chromium.org - - Records if the time from navigation to first contentful paint was less than - the specified threshold. Also, records the total number of first contentful - paints. For a single first contentful paint event, data may be recorded in - multiple buckets. Recorded at the time when first contentful paint happens. - Recorded only for page loads that have scheme https://. - - - - - dougarnett@chromium.org - tbansal@chromium.org - - Records if the time from navigation to first contentful paint was less than - the specified threshold. Also, records the total number of first contentful - paints. For a single first contentful paint event, data may be recorded in - multiple buckets. Recorded at the time when first contentful paint happens. - Recorded only for page loads that have scheme https://, are user-initiated, - and are new navigations (that is, they are not reloads nor forward or back - navigations). - - - - - - Removed June 2018 (M69) in favor of - PageLoad.Clients.ServiceWorker2.PageTransition. - - falken@chromium.org - - The core transition type for main frame page loads controlled by a service - worker. - - - - - falken@chromium.org - - The core transition type for main frame page loads controlled by a service - worker that has a fetch event handler. - - - - - dtapuska@chromium.org - kenjibaheux@google.com - - Measures the time from navigation start to first contentful paint. Recorded - for pages that contain a resource that may benefit from stale while - revalidate. - - - - - dtapuska@chromium.org - kenjibaheux@google.com - - Measures the time from parse start to first contentful paint. Recorded for - pages that contain a resource that may benefit from stale while revalidate. - - - - - - Removed May 2018 (M68) in favor of - SubresourceFilter.PageLoad.ActivationDecision - - bmcquade@chromium.org - - Records the policy decision to activate subresource filtering for a page - load. 'Activated' indicates that subresource filtering was activated. All - other reasons indicate that subresource filtering was not activated. Page - loads where subresource filtering was activated ('Activated') and at least - one subresource matched the subresource filter are counted in - PageLoad.Clients.SubresourceFilter.Count. - - - - - - Removed May 2018 (M68) in favor of - SubresourceFilter.PageLoad.NumSubresourceLoads.MatchedRules (e.g. by looking - at 0 and non-zero buckets). - - bmcquade@chromium.org - - Records 'true' for page loads where the subresource filter matched a - subresource loaded by the page. Includes dryrun matches. To compute the - percentage of total page loads affected by subresource filtering, divide by - the sum of counts for (PageLoad.ParseTiming.NavigationToParseStart + - PageLoad.ParseTiming.NavigationToParseStart.Background). - - - - - robertogden@chromium.org - tbansal@chromium.org - - How long the query to the cookie manager took to complete. Recorded on every - query response. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The number of days since any origin in the redirect chain was last visited, - according to the history service. Recorded whenever there was a previous - visit to record. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Whether or not there was a previous visit to any origin in the redirect - chain, as reported by the history service. Each positive entry corresponds - to a single entry in - "PageLoad.Clients.SubresourceLoading.DaysSinceLastVisitToOrigin". - Recorded on page end for every committed page load. - - - - - robertogden@chromium.org - tbansal@chromium.org - - How long the query to the history service took to complete. Recorded on - every query response. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The count of CSS or JS subresources on a page that were loaded from cache - before FCP occurred. Only recorded for Lite mode (AKA Data Saver) users. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The count of CSS or JS subresources on a page that were loaded from the - network before FCP occurred. Only recorded for Lite mode (AKA Data Saver) - users. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Whether or not any main frame request in the redirect chain had cookies. - - - - - - Removed in 12/2019. - - jkarlin@chromium.org - johnidel@chromium.org - - The time from navigation start to the first contentful paint of third-party - frames on pages. Note that this can be significantly delayed due to lazy - loading. - - - - - - Removed in 01/2020. - - jkarlin@chromium.org - johnidel@chromium.org - - The time from navigation start to the first contentful paint of third-party - (third party in respect to eTLD+1) frames on pages. Note that this can be - significantly delayed due to lazy loading. - - - - - jkarlin@chromium.org - johnidel@chromium.org - - The time from navigation start to the first contentful paint of third-party - (in respect to scheme://eTLD+1) frames on pages. Note that this can be - significantly delayed due to lazy loading. - - - - - - Removed in 01/2020. - - jkarlin@chromium.org - - The number of third party origins on a page that read cookies either via - resource request headers or document.cookie. - - - - - jkarlin@chromium.org - yaoxia@chromium.org - - The number of third party (in respect to scheme://eTLD+1) origins on a page - that read cookies either via resource request headers or document.cookie. - - - - - - Removed in 01/2020. - - jkarlin@chromium.org - - The number of third party origins on a page that changed cookies either via - resource response headers or document.cookie. - - - - - jkarlin@chromium.org - yaoxia@chromium.org - - The number of third party (in respect to scheme://eTLD+1) origins on a page - that changed cookies either via resource response headers or - document.cookie. - - - - - - Removed in 01/2020. - - yaoxia@chromium.org - - The number of third party origins on a page that access local storage via - window.localStorage. - - - - - yaoxia@chromium.org - jkarlin@chromium.org - - The number of third-parties (in respect to scheme://eTLD+1) on a page that - access local storage via window.localStorage. - - - - - - Renamed to PageLoad.Clients.ThirdParty.Origins.CookieRead. - - jkarlin@chromium.org - - The number of third party origins on a page that read cookies either via - resource request headers or document.cookie. - - - - - - Removed in 01/2020. - - yaoxia@chromium.org - - The number of third party origins on a page that access session storage via - window.sessionStorage. - - - - - yaoxia@chromium.org - jkarlin@chromium.org - - The number of third-parties (in respect to scheme://eTLD+1) on a page that - access session storage via window.sessionStorage. - - - - - - Renamed to PageLoad.Clients.ThirdParty.Origins.CookieWrite. - - jkarlin@chromium.org - - The number of third party origins on a page that changed cookies either via - resource response headers or document.cookie. - - - - - shivanisha@chromium.org - jkarlin@chromium.org - - Records the largest contentful paint only for pages that load a third party - font and whose largest contentful resource type is text. See - PageLoad.PaintTiming.NavigationToLargestContentfulPaint for details. - - - - - ericrobinson@chromium.org - csharrison@chromium.org - - Only recorded if the page has at least one identified ad frame. Recorded in - PageLoadMetrics when the page is destroyed. Cpu measures the wall time of - tasks attributable to a frame as reported by the MainThreadTaskScheduler as - well as time spent servicing scripted animations by each document (not - attributable by the MainThreadTaskScheduler). An ad frame consists of the - identified ad frame and all of its children (which may also be ads, but are - counted as part of the ancestor ad frame). Includes resources that did not - finish loading. Does not consider time while a page is backgrounded. - - - - - alexmt@chromium.org - johnidel@chromium.org - - Recorded when the page is destroyed or the app is backgrounded on mobile. - Records the total wall time of tasks attributable to the page across its - lifetime. Considers both the CPU usage while the page is in the foreground - and in the background. - - - - - alexmt@chromium.org - johnidel@chromium.org - - Recorded when the page is destroyed or the app is backgrounded on mobile. - Records the total wall time of tasks attributable to the page across its - lifetime. Does not consider CPU usage while a page is backgrounded. - - - - - - Removed in May 2018 (M69). - - csharrison@chromium.org - - The time spent parsing author style sheets before the first contentful - paint. - - - - - - Removed in May 2018 (M69). - - csharrison@chromium.org - - The sum of CSSTiming.Update and CSSTiming.Parse variants for this page load. - - - - - - Removed in May 2018 (M69). - - csharrison@chromium.org - - The time spent in Document::updateStyle before the first contentful paint. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - DOMContentLoaded event is fired, for main frame documents. - - - - - - Removed 12/2019. Use NavigationToFirstContentfulPaint instead. - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first layout is performed, for main frame documents. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - load event is fired, for main frame documents. - - - - - - deprecated in favor of PageLoad.Events.* - - csharrison@chromium.org - bmcquade@chromium.org - - Captures counts of various page load events. These are enumerated in the - enum page_load_metrics::PageLoadEvent, and include events like 'page load - aborted before first layout' - - - - - - Removed in favor of PageLoad.Timing2.NavigationToCommit and - PageLoad.AbortTiming. - - csharrison@chromium.org - bmcquade@chromium.org - - Captures counts of load events post-commit, on relevant page loads (i.e. - http/https, not same-page, not an error page). These events include aborts - before first layout and successful first layouts. Note that the event - 'Committed load started' when segmented by background/foreground specifies - whether the eventually committed load started in the background or - foreground, not whether we backgrounded before the actual commit event. This - is because we don't have all the data to filter relevant page loads on - provisional loads. - - - - - - Removed in favor of PageLoad.Internal.ErrorCode. - - csharrison@chromium.org - bmcquade@chromium.org - - Counts of various internal error conditions in the page_load_metrics system. - - - - - - Removed Feb 2016 in favor of PageLoad.AbortTiming and - PageLoad.Timing2.NavigationToFailedProvisionalLoad. Note that the - corresponding background enumerations are no longer being tracked in the - timing histograms. - - csharrison@chromium.org - bmcquade@chromium.org - - Captures counts of provisional load events. These include aborted, failed, - and successful (committed) provisional loads. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted due to being backgrounded. - - - - - - Removed in favor of PageLoad.Internal.ClientRedirect.*. - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a client side redirect (Javascript navigation). - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by the user closing the tab or browser. - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a forward or back navigation. - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a new navigation. - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted. The abort cause is unknown. - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by a reload. - - - - - csharrison@chromium.org - - This metric is still experimental and not yet ready to be relied upon. - Measures the time from navigation start to the time the page load was - aborted by the user pressing stop. - - - - - - Removed in favor of PageLoad.Experimental.Bytes.Cache2. - - jkarlin@chromium.org - - The number of prefiltered (e.g., compressed) response body KiloBytes loaded - from the cache via the browser process for a page load. Recorded when the - page load is terminated. Only recorded for complete resources. - - - - - jkarlin@chromium.org - johnidel@chromium.org - - The number of prefiltered (e.g., compressed) response body KiloBytes loaded - from the cache via the browser process for a page load. Recorded when the - page load is terminated. Only recorded for complete resources. Includes - resources from both the http cache and memory cache. - - - - - jkarlin@chromium.org - - The number of prefiltered (e.g., compressed) response body KiloBytes loaded - over the network via the browser process for a page load. Does not include - any header or overhead bytes. Recorded when the page load is terminated. - Only recorded for complete resources. - - - - - jkarlin@chromium.org - - The number of prefiltered (e.g., compressed) KiloBytes loaded over the - network via the browser process for a page load. This includes network - headers/overhead. Recorded when the page load is terminated. Recorded for - incomplete resources. - - - - - - Removed in favor of PageLoad.Experimental.Bytes.Total2. - - jkarlin@chromium.org - - The number of prefiltered (e.g., compressed) response body KiloBytes loaded - via the browser process for a page load. Does not include any header or - overhead bytes. Recorded when the page load is terminated. Only recorded for - complete resources. - - - - - jkarlin@chromium.org - johnidel@chromium.org - - The number of prefiltered (e.g., compressed) response body KiloBytes loaded - via the browser process for a page load. Does not include any header or - overhead bytes. Recorded when the page load is terminated. Only recorded for - complete resources. Includes resources from both the http and memory cache. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Total number of network bytes that were used to load resources that did not - finish loading on the page (e.g. ongoing video). This includes resource - loads that were canceled or resource loads that were ongoing when the page - was destroyed. - - - - - - Removed Jan 2018 - - csharrison@chromium.org - - The percent of resources loaded from cache for the given page load. Recorded - at the end of HTML parsing. - - - - - - Removed Jan 2018 - - csharrison@chromium.org - - The number of resources a given page finished loading from cache at parse - stop. - - - - - dougarnett@chromium.org - tbansal@chromium.org - tdresser@chromium.org - - The maximum size click input burst for the page load. A click input burst is - a sequence of user click inputs at approximately the same screen position - where the clicks each occur soon after the previous one (e.g., within half - second). This is intended to detect possible rage clicks by the user. - - - - - - Removed in favor of PageLoad.Experimental.CompletedResources.Cache2. - - csharrison@chromium.org - jkarlin@chromium.org - - The number of completed resources loaded from the cache via the browser - process for a page load. Recorded when the page load is terminated. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - The number of completed resources loaded from the cache via the browser - process for a page load. Recorded when the page load is terminated. Includes - resources from both the http and memory cache. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - The number of completed resources loaded from the network via the browser - process for a page load. Recorded when the page load is terminated. - - - - - - Removed in favor of PageLoad.Experimental.CompletedResources.Total2. - - csharrison@chromium.org - jkarlin@chromium.org - - The total number of completed resources loaded via the browser process for a - page load. Recorded when the page load is terminated. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - The total number of completed resources loaded via the browser process for a - page load. Recorded when the page load is terminated. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the headers of the 103 Early Hints response is - received in reply to the final HTTP request and when the headers of the - final HTTP response is received for the main resource of a main frame - navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the final HTTP request is sent and when the - headers of the 103 Early Hints response is received in reply to the request - for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the first HTTP request is sent and when the - headers of the 103 Early Hints response is received in reply to the request - for the main resource of a main frame navigation. - - - - - sullivan@chromium.org - tdresser@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the navigation actually starting. - - - - - sullivan@chromium.org - tdresser@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the navigation actually starting, for background loads. - - - - - sullivan@chromium.org - tdresser@chromium.org - - The time between the OS-level click/tap event and navigation start, for - clicks on links in the renderer. - - - - - sullivan@chromium.org - tdresser@chromium.org - - The time between the OS-level keypress/tap event in the omnibox and - navigation start, for navigations from the omnibox. - - - - - - Removed 7/2019, replaced by PageLoad.LayoutInstability.CumulativeShiftScore - - bmcquade@chromium.org - skobes@chromium.org - - Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred - on the page (including all subframes) during the session. - - - - - - Removed 7/2019, replaced by - PageLoad.LayoutInstability.CumulativeShiftScore.MainFrame - - bmcquade@chromium.org - skobes@chromium.org - - Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred - in the main frame during the session. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when a callback for the navigation loader is last - invoked and when navigation commit message is sent to a renderer process for - the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the final HTTP request is sent and when the - headers of the final HTTP response is received for the main resource of a - main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the headers of the final HTTP response is received - and when a callback for the navigation loader is last invoked for the main - resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the first HTTP request is sent and when the - headers of the first HTTP response is received for the main resource of a - main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The interval between when the headers of the first HTTP response is received - and when a callback for the navigation loader is first invoked for the main - resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that a callback for the navigation - loader is last invoked for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that the final HTTP request is sent - for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that the headers of the final HTTP - response is received for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that a callback for the navigation - loader is first invoked for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that the first HTTP request is sent - for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that the headers of the first HTTP - response is received for the main resource of a main frame navigation. - - - - - nhiroki@chromium.org - chrome-loading@google.com - - The time relative to navigation start that navigation commit message for a - main frame navigation is sent to a renderer process. - - - - - - Removed 1/2020. - - dproy@chromium.org - tdresser@chromium.org - - Measures Time to Interactive, a metric based on main thread and network - heuristics to approximate the point in time when the page feels interactive - to the user. See https://goo.gl/TFw6xz for detailed explanation. This - histogram uses First Meaningful Paint as the lower bound for quiescent - windows. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - Determines the PageLoadType for this page load. That is, records whether the - page was never foregrounded, was foregrounded but did not reach FCP, or did - reach FCP. The metric is recorded at the end of each page load. As usual - with PageLoad metrics, we consider app backgrounding on Android to be the - end of page load as well as the app could be evicted by Android anytime - after that happens. - - - - - - Removed in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint. - - bmcquade@chromium.org - - Measures the total time the page load was active after first paint, up until - being backgrounded, prior to the page load terminating. Recorded only for - page loads that started in the foreground. - - - - - - Removed in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint. - - bmcquade@chromium.org - - Measures the total time the page load was active after first paint, for page - loads that spend the entire time in the foreground. - - - - - - Removed in favor of PageLoad.PageTiming.ForegroundDuration. - - bmcquade@chromium.org - - Measures the total time the page load was active, up until being - backgrounded, for page loads that started in the foreground. - - - - - - Removed in favor of PageLoad.PageTiming.ForegroundDuration. - - bmcquade@chromium.org - - Measures the total time the page load was active, for page loads that spend - the entire time in the foreground. - - - - - - Removed in favor of - PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2. - - ksakamoto@chromium.org - - Whether the user had any interaction on the page (except mouse move) after - first paint, and whether the user left the page before network stable or - not. - - - - - - Removed as of 05/17/2017. - - ksakamoto@chromium.org - - Whether the user had any interaction on the page (except mouse move) after - first paint, and whether the user left the page before network stable or - not. Not logged if page load was aborted before first paint. - - - - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - - Records whether the First Meaningful Paint metric was reported for the page - load, or why it wasn't if not. See http://bit.ly/ttfmp-doc for the - definition of First Meaningful Paint. - - - - - - Removed as of 05/17/2017. - - ksakamoto@chromium.org - - Measures the time between when the first meaningful paint - (http://bit.ly/ttfmp-doc) was computed to have happened, and when we - actually logged the metric. - - This metric is useful in helping us tweak when FirstMeaningfulPaintDetector - should stop observing layout operations. - - - - - - Removed in Sep 2020. - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from a background tab being switched to the foreground to - the time the first meaningful paint is performed, for main frame documents. - - - - - sullivan@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the first contentful paint of the page that was loaded in the navigation. - - - - - sullivan@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the first contentful paint of the page that was loaded in the navigation, - for background loads. - - - - - sullivan@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the first paint of the page that was loaded in the navigation. - - - - - sullivan@chromium.org - - The time between the OS-level input event that initiated a navigation, and - the first paint of the page that was loaded in the navigation, for - background loads. - - - - - - Removed 7/2019, replaced by - PageLoad.PaintTiming.LargestContentfulPaint.ContentType - - maxlg@chromium.org - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest content paint, whose timestamp is measured by - PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaintAllFrames, - comes from text or image. This value is recorded whenever - PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaintAllFrames - is recorded. - - - - - - Removed 7/2019, replaced by - PageLoad.PaintTiming.LargestContentfulPaint.MainFrame.ContentType - - maxlg@chromium.org - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest content paint, whose timestamp is measured by - PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaint, comes - from text or image. This value is recorded whenever - PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaint is - recorded. - - - - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the first - meaningful paint (http://bit.ly/ttfmp-doc), for main frame documents. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - Removed 7/2019, replaced by - PageLoad.PaintTiming.NavigationToLargestContentfulPaint.MainFrame - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, for main frame documents. - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - - - - - Removed 7/2019, replaced by - PageLoad.PaintTiming.NavigationToLargestContentfulPaint - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, for main frame documents. - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. Compared with NavigationToLargestContentPaint, this is the - aggregate results from all frames, while NavigationToLargestContentPaint is - only for main frame. See http://bit.ly/fcp_plus_plus for details. - - - - - - Removed Mar 2020 in favor of - PageLoad.PaintTiming.NavigationToLargestContentfulPaint. - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest image is first painted after fully loaded, for main frame documents. - The value is recorded at the end of each page load. See - http://bit.ly/fcp_plus_plus for details. - - - - - - Removed Mar 2020 in favor of - PageLoad.PaintTiming.NavigationToLargestContentfulPaint. - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest text is first painted, for main frame documents. The value is - recorded at the end of each page load. See http://bit.ly/fcp_plus_plus for - details. - - - - - - Removed Mar 2019 - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - last image is first painted after fully loaded, for main frame documents. - The value is recorded at the end of each page load. See - http://bit.ly/fcp_plus_plus for details. - - - - - - Removed Mar 2019 - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - last text is first painted, for main frame documents. The value is recorded - at the end of each page load. The value is recorded at the end of each page - load. See http://bit.ly/fcp_plus_plus for details. - - - - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from when the HTML parser started, to the first meaningful - paint (http://bit.ly/ttfmp-doc), for main frame documents. - - - - - - Removed Jan 2018 - - csharrison@chromium.org - - The parse duration of the page load where 0-50% of all subresources (loaded - during parsing) were served from the HTTP cache (including 304s). - - - - - - Removed Jan 2018 - - csharrison@chromium.org - - The parse duration of the page load where 51-100% of all subresources - (loaded during parsing) were served from the HTTP cache (including 304s). - - - - - - Renamed to - PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.FirstMeaningfulPaintOrdering - - ksakamoto@chromium.org - - Whether the two variants of First Meaningful Paint reported different - values, and if so, which one was reported first. - - - - - - Renamed to - PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.HadNetworkQuiet - - ksakamoto@chromium.org - - Recorded when the page load reached network 0-quiet (no active network - connection for 0.5 seconds), or network 2-quiet (no more than 2 active - network connections for 2 seconds). - PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2 - histogram gives the fraction of page loads that had network 2-quiet, so it - can be used as a baseline. - - - - - - Removed 1/2020. - - tdresser@chromium.org - dproy@chromium.org - - Records whether the Time To Interactive metric was reported for the page - load, or why it wasn't if not. See https://goo.gl/TFw6xz for definition of - Time to Interactive. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - The total amount of time the page spent in the foreground. Note that this - metric adds all foreground durations occurring for the page. For example: if - the page starts foregrounded during 1 second, then goes to the background - for a while, then is foregrounded again for 2 seconds, and then is unloaded, - this metric reports 3 seconds. The metric is recorded at the end of each - page load. As usual with PageLoad metrics, we consider app backgrounding on - Android to be the end of page load as well as the app could be evicted by - Android anytime after that happens. - - - - - - Removed Jan 2018 - - csharrison@chromium.org - - The number of resources a given page finished loading at parse stop. - - - - - cammie@chromium.org - jkarlin@chromium.org - - For each identified ad frame, whether the origin of the ad creative frame - matches or differs from the origin of the main frame. - - The ad creative frame is heuristically determined, from among an identified - ad frame and all of its children, as the first of these frames to record a - First Contentful Paint. If no FCP is recorded, the creative origin status is - marked as indeterminate. - - - - - cammie@chromium.org - jkarlin@chromium.org - - For each identified ad frame, whether the origin of the ad creative frame - matches or differs from the origin of the main frame, further split by - whether the frame has lifecycle updates throttled. Metric is emitted on - frame deletion. - - The ad creative frame is heuristically determined, from among an identified - ad frame and all of its children, as the first of these frames to record a - First Contentful Paint. If no FCP is recorded, the creative origin status is - marked as indeterminate. Frames that are render-throttled will not have an - FCP. Ad frames with indeterminate creative origin status are broken out as - throttled or not. - - - - - - Removed April 2018, replaced by OriginStatus. - - ericrobinson@chromium.org - - For each identified ad frame, whether the origin of the ad matches the - origin of the main frame. - - An ad frame consists of the identified ad frame and all of its children - (which may also be ads, but are counted as part of the ancestor ad frame). - Frames of zero bytes (e.g., never had a document or their document was - doc.written and no sub-resources were loaded) are not counted. - - - - - ericrobinson@chromium.org - - For each identified ad frame, whether the origin of the ad matches the - origin of the main frame, differs from the origin of the main frame, or is - indeterminable. - - An ad frame consists of the identified ad frame and all of its children - (which may also be ads, but are counted as part of the ancestor ad frame). - Frames of zero bytes (e.g., never had a document or their document was - doc.written and no sub-resources were loaded) are not counted. - - - - - - Removed July 2019 in Issue 962616. - - johnidel@chromium.org - jkarlin@chromium.org - - Whether or not the ad frame would have triggered the Adframe size - intervention. This is determined by checking if a frame does not have a user - gesture when its size exceeds 1050 kilobytes. Only recorded for ad frames - with non-zero total bytes. Recorded for each frame when the page is - destroyed or navigated. - - - - - - Removed July 2019 in Issue 962616. - - johnidel@chromium.org - jkarlin@chromium.org - - Whether or not the ad frame that would have triggered the Adframe size - intervention had media playing at any point in its lifetime. An adframe will - trigger the intervention if it does not have a user gesture when its size - exceeds 1050 kilobytes. Recorded for each offending frame when the page is - destroyed or navigated. - - - - - - Removed 01/2020. Available in UKM via AdFrameLoad.Visibility.FrameHeight and - AdFrameLoad.Visibility.FrameWidth. - - johnidel@chromium.org - jkarlin@chromium.org - - The smallest dimension of a root ad frame in pixels. Only recorded for ad - frames with non-zero total bytes. Recorded when the page is destroyed or - navigated. Display none iframes will not always update their size because - they lack a content view. This uses the last size of frame before it was set - to display: none. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - The square root of the area of a root adframe in pixels. Only recorded for - ad frames with non-zero total bytes. Recorded when the page is destroyed or - navigated. Display none iframes will not always update their size because - they lack a content view. This uses the last size of frame before it was set - to display: none. - - - - - johnidel@chromium.org - csharrison@chromium.org - - For each identified ad frame, whether the sticky user activation bit was - ever set on the frame. Recorded for each ad frame when the page is destroyed - or navigated away from, including ad frames that no longer exist. - - An ad frame consists of the identified ad frame and all of its children - (which may also be ads, but are counted as part of the ancestor ad frame). - Frames of zero bytes (e.g., never had a document or their document was - doc.written and no sub-resources were loaded) are not counted. - - - - - jkarlin@chromium.org - - The number of frames on the page that have loaded more than 0 bytes of - content or had non-zero CPU usage. - - For pages with zero ad frames, the other PageLoad.Clients.Ads metrics are - not recorded unless otherwise specified. This metric is not recorded on - sites where the subresource filter is enabled. - - Child frames of an ad frame are not included in the count. - - - - - - Removed 09/2019 in favor of PageLoad.FrameCounts.AdFrames.Total. - - jkarlin@chromium.org - - The number of frames on the page that have loaded more than 0 bytes of - content. - - For pages with zero ad frames, the other PageLoad.Clients.Ads metrics are - not recorded unless otherwise specified. - - Child frames of an ad frame are not included in the count. - - - - - - Removed 09/2018 in favor of PageLoad.HeavyAds.ComputedType2. - - johnidel@chromium.org - jkarlin@chromium.org - - Records heavy ad type for each ad frame, as determined by the first - threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of - feature flag or other conditions that prevent the heavy ad intervention from - occuring. Recored for all ad frames with non-zero bytes. Recorded when the - ad frame destroyed or when the page is destroyed. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records heavy ad type for each ad frame, as determined by the first - threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of - feature flag or other conditions that prevent the heavy ad intervention from - occuring. Recored for all ad frames with non-zero bytes. Recorded when the - ad frame destroyed or when the page is destroyed. - - It is possible for multiple thresholds to be hit at the same time, with the - higher valued enums winning those race conditions. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records heavy ad type for each ad frame, as determined by the first - threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of - feature flag or other conditions that prevent the heavy ad intervention from - occuring. This includes 1 megabyte of random additive noise on the network - threshold. As such, it is possible for this histogram to record different - values for the same frame than PageLoad.HeavyAds.ComputedType2. - - Recored for all ad frames with non-zero bytes. Recorded when the ad frame - destroyed or when the page is destroyed. - - It is possible for multiple thresholds to be hit at the same time, with the - higher valued enums winning those race conditions. - - - - - - Removed 09/2018 in favor of PageLoad.HeavyAds.InterventionType2. - - johnidel@chromium.org - jkarlin@chromium.org - - Records the type of heavy ad unloaded by the heavy ad intervention. Heavy ad - type is determined by the first threshold hit. This is not recorded for ad - frames that are considered heavy but did not fufill other criteria for the - intervention. This includes the feature being enabled and being below the - per-origin intervention cap. - - - - - johnidel@chromium.org - jkarlin@chromium.org - - Records the type of heavy ad unloaded by the heavy ad intervention. Heavy ad - type is determined by the first threshold hit. This is not recorded for ad - frames that are considered heavy but did not fufill other criteria for the - intervention. This includes the feature being enabled and being below the - per-origin intervention cap. - - It is possible for multiple thresholds to be hit at the same time, with the - higher valued enums winning those race conditions. - - - - - tdresser@chromium.org - - Measures the time to first non-scroll input after the first paint. - - - - - tdresser@chromium.org - input-dev@chromium.org - - Measures the time to first scroll input after the first paint. - - - - - - Removed on January 2019 in favor of - PageLoad.InteractiveTiming.FirstInputDelay2 which correctly excludes some - scrolling cases that were previously not excluded from this metric. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation. See https://goo.gl/tr1oTZ for a detailed explanation. - In ms. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - speed-metrics-dev@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per back-forward navigation. Recorded on first page interaction after - the page is restored from the back-forward cache. See https://goo.gl/tr1oTZ - for a detailed explanation. Excludes scrolls. - - - - - - Removed January 2020 as the SkipTouchFilter experiment is completed. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - This metric will be used to compare first inputs during the - SkipTouchEventFilter experiment. - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation. Recorded on first page interaction. See - https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - - - - - Removed on February 2019 in favor of - PageLoad.InteractiveTiming.FirstInputDelay3 which brings the metric more in - line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation. Recorded on first page interaction. See - https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - Removed in July 2019 in favor of PageLoad.InteractiveTiming.FirstInputDelay4 - which includes input events which were filtered previously. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation. Recorded on first page interaction. See - https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - Measures First Input Delay, the duration between the hardware timestamp and - the start of event processing on the main thread for the first meaningful - input per navigation. Recorded on first page interaction. See - https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - Log of major changes: http://bit.ly/chrome-speed-metrics-changelog - - - - - - Removed on January 2019 in favor of - PageLoad.InteractiveTiming.FirstInputTimestamp2 which correctly excludes - some scrolling cases that were previously not excluded from this metric. - - tdresser@chromium.org - - The duration between navigation start and the hardware timestamp of the - first meaningful input per navigation. See https://goo.gl/tr1oTZ for a - detailed explanation. In ms. - - - - - - Removed January 2020 as the SkipTouchFilter experiment is completed. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - This metric will be used to compare first inputs during the - SkipTouchEventFilter experiment. - - The duration between navigation start and the hardware timestamp of the - first meaningful input per navigation. Recorded on first page interaction. - See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - - - - - Removed on February 2019 in favor of - PageLoad.InteractiveTiming.FirstInputTimestamp3 which brings the metric more - in line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - first meaningful input per navigation. Recorded on first page interaction. - See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - - - - - Removed in July 2019 in favor of - PageLoad.InteractiveTiming.FirstInputTimestamp4 which includes input events - which were filtered previously. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - first meaningful input per navigation. Recorded on first page interaction. - See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - first meaningful input per navigation. Recorded on first page interaction. - See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. - - - - - - Removed on January 2019 in favor of PageLoad.InteractiveTiming.InputDelay2 - which correctly excludes some scrolling cases that were previously not - excluded from this metric. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between the hardware timestamp and the start of event - processing on the main thread for a meaningful input. In ms. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - Removed on February 2019 in favor of PageLoad.InteractiveTiming.InputDelay3 - which brings the metric more in line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between the hardware timestamp and the start of event - processing on the main thread for a meaningful input. Excludes scrolls. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - The duration between the hardware timestamp and the start of event - processing on the main thread for a meaningful input. Excludes scrolls. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - WARNING: The long tail of this metric is buggy on Mac (overflows for a - subset of users) which can lead to surprising false regressions or - improvements. - - - - - - Removed on January 2019 in favor of - PageLoad.InteractiveTiming.InputTimestamp2 which correctly excludes some - scrolling cases that were previously not excluded from this metric. - - tdresser@chromium.org - - The duration between navigation start and the hardware timestamp of a - meaningful input. In ms. - - - - - - Removed on February 2019 in favor of - PageLoad.InteractiveTiming.InputTimestamp3 which brings the metric more in - line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of a - meaningful input. Excludes scrolls. - - - - - - - sullivan@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of a - meaningful input. Excludes scrolls. - - - - - - Removed on January 2019 in favor of - PageLoad.InteractiveTiming.LongestInputDelay2 which correctly excludes some - scrolling cases that were previously not excluded from this metric. - - tdresser@chromium.org - - Measures longest Input Delay, the longest duration between the hardware - timestamp and the start of event processing on the main thread for the - meaningful input per navigation. In ms. - - - - - - Removed on February 2019 in favor of - PageLoad.InteractiveTiming.LongestInputDelay3 which brings the metric more - in line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures longest Input Delay, the longest duration between the hardware - timestamp and the start of event processing on the main thread for the - meaningful input per navigation. Excludes scrolls. - - - - - - Removed in October 2019 in favor of LongestInputDelay4, which updates naming - to be consistent with LongestInput UKM. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures longest Input Delay, the longest duration between the hardware - timestamp and the start of event processing on the main thread for the - meaningful input per navigation. Excludes scrolls. - - - - - sullivan@chromium.org - speed-metrics-dev@chromium.org - - Measures longest Input Delay, the longest duration between the hardware - timestamp and the start of event processing on the main thread for the - meaningful input per navigation. Excludes scrolls. - - - - - - Removed on January 2019 in favor of - PageLoad.InteractiveTiming.LongestInputTimestamp2 which correctly excludes - some scrolling cases that were previously not excluded from this metric. - - tdresser@chromium.org - - The duration between navigation start and the hardware timestamp of the - meaningful input with longest queuing delay per navigation. In ms. - - - - - - Removed on February 2019 in favor of - PageLoad.InteractiveTiming.LongestInputTimestamp3 which brings the metric - more in line with the EventTiming API. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - meaningful input with longest queuing delay per navigation. Excludes - scrolls. - - - - - - Removed in October 2019 in favor of LongestInputTimestamp4, which updates - naming to be consistend with LongestInput UKMs. - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - meaningful input with longest queuing delay per navigation. Excludes - scrolls. - - - - - sullivan@chromium.org - speed-metrics-dev@chromium.org - - The duration between navigation start and the hardware timestamp of the - meaningful input with longest queuing delay per navigation. Excludes - scrolls. - - - - - bmcquade@chromium.org - - The delay between first paint and a client-side redirect navigation, for - pages that reported a first paint. This metric is only intended to help in - choosing a heuristic delay to distinguish between client-side redirects and - other client initiated navigations, and will be deprecated in M54. Please - contact bmcquade@chromium.org before using this metric. - - - - - bmcquade@chromium.org - - Counts how often a client-side redirect was initiated from a page that did - not report a first paint. This metric is only intended to help in choosing a - heuristic delay to distinguish between client-side redirects and other - client initiated navigations, and will be deprecated in M54. Please contact - bmcquade@chromium.org before using this metric. - - - - - - Removed in favor of PageLoad.Internal.ClientRedirect.FirstPaintToNavigation - and PageLoad.Internal.ClientRedirect.NavigationWithoutPaint. - - bmcquade@chromium.org - - The delay between first paint and a client-side redirection. This metric is - only intended to help in choosing a heuristic delay to distinguish between - client-side redirects and other client initiated navigations, and will be - deprecated in M54. Please contact bmcquade@chromium.org before using this - metric. - - - - - - Removed on 10/14/2016. No longer needed. - - bmcquade@chromium.org - - The delay between commit and completion, for page loads that did not receive - any timing IPCs. This metric is only intended to help understand the cases - where committed page loads don't receive timing IPCs. Please contact - bmcquade@chromium.org before using this metric. - - - - - csharrison@chromium.org - bmcquade@chromium.org - - Counts of various internal error conditions in the page_load_metrics system. - - - - - - Removed 1/2020. - - dproy@chromium.org - tdresser@chromium.org - - Measures time delta between Time to Interactive and when we can detect TTI. - TTI cannot be detected in real time - we have to wait sufficiently long to - determine main thread and network quiescence. See https://goo.gl/TFw6xz for - detailed explanation of Time to Interactive. This histogram uses First - Meaningful Paint as the lower bound for quiescent windows. - - - - - bmcquade@chromium.org - Whether a navigation started in the foreground. - - - - bmcquade@chromium.org - - The difference in magnitude between existing and updated timing, for - inter-frame timings that are received out of order. Page load metrics - observes timing updates in all frames on a page. It's possible for timings - in different frames to arrive out of order. This metric tracks how often - this happens, along with the magnitude of the difference. - - - - - bmcquade@chromium.org - - Whether a page load completed after the app entered the background. We log a - 'Started' value for each PageLoadTracker that is active when the app enters - the background, and a 'Completed' value for each of those PageLoadTrackers - that successfully runs its destructor. This helps to understand how many - trackers are destroyed while the app is in the background before they are - able to run their destructor. This metric is only intended to help in - understanding how often app background leads to data loss, and will be - deprecated in a subsequent release. Please contact bmcquade@chromium.org - before using this metric. - - - - - bmcquade@chromium.org - - The status of PageLoadTiming structs received from the render process over - IPC. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest contentful paint, whose timestamp is measured - by PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint, - comes from text or image. This value is recorded whenever - PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint is - recorded. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest content paint in the main frame, whose - timestamp is measured by - PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint.MainFrame, - comes from text or image. This value is recorded whenever - PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint.MainFrame - is recorded. - - - - - - Removed July 2019. - - ksakamoto@chromium.org - - Whether the user had any interaction on the page before - FirstMeaningfulPaint. Recorded when the page load reaches network idle. - - - - - maxlg@chromium.org - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest contentful paint, whose timestamp is measured - by PageLoad.PaintTiming.NavigationToLargestContentfulPaint, comes from text - or image. This value is recorded whenever - PageLoad.PaintTiming.NavigationToLargestContentfulPaint is recorded. - - - - - maxlg@chromium.org - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures whether the largest content paint in the main frame, whose - timestamp is measured by - PageLoad.PaintTiming.NavigationToLargestContentPaint.MainFrame, comes from - text or image. This value is recorded whenever - PageLoad.PaintTiming.NavigationToLargestContentfulPaint.MainFrame is - recorded. - - - - - sullivan@chromium.org - - Breakdown of NavigationToFirstContentfulPaint counts by process that - initiated the navigation (this will only be renderer or browser). - - - - - bmcquade@chromium.org - - Counts the number of prerender navigations. Only logs true values. - - - - - csharrison@chromium.org - - This histogram counts the number of provisional loads aborted by other - navigations, until a final forward back navigation commits. - - - - - csharrison@chromium.org - - This histogram counts the number of provisional loads aborted by new - navigations, until a final new navigation commits. - - - - - csharrison@chromium.org - - This histogram counts the number of provisional loads aborted by new - navigations. In this case the chain never ends with a commit. This is logged - on the next abort signal comes in (e.g. tab close or new navigation). - - - - - csharrison@chromium.org - - This histogram counts the number of provisional loads aborted by other - navigations, until a final reload navigation commits. - - - - - csharrison@chromium.org - - This histogram counts the number of consecutive provisional loads aborted by - other navigations with the same url (before redirects). It's logged when a - provisional abort does not share a URL, or when a load finally commits. Note - that we don't log chains of length 0. - - - - - - Removed July 2019. - - ksakamoto@chromium.org - - Whether the two variants of First Meaningful Paint reported different - values, and if so, which one was reported first. - - - - - - Removed July 2019. - - ksakamoto@chromium.org - - Recorded when the page load reached network 0-quiet (no active network - connection for 0.5 seconds), or network 2-quiet (no more than 2 active - network connections for 2 seconds). - PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2 - histogram gives the fraction of page loads that had network 2-quiet, so it - can be used as a baseline. - - - - - panicker@chromium.org - - For first paint, first contentful paint, first meaningful paint, first text - paint, and first image paint, we use the swap timestamp of the corresponding - paint, which is the timestamp the CC SwapPromise was positively fulfilled - (i.e. DidSwap() was invoked). If the swap did not occur (DidNotSwap() was - invoked), we use the timestamp when the swap promise fails. However, in the - future we may stop reporting timestamps for certain failure reasons. This - metric records whether or not the swap occurred, and the reason for failure - if it failed. The distribution of this metric will help determine the effect - of not reporting timestamps in certain cases. - - - - - - deprecated May 2018: The swap-timestamp comes from a different process, and - comparing that with the paint-time (which is from the local process) does - not produce a reliable metric. - - panicker@chromium.org - - Records the delta between the renderer timestamp and swap timestamp for - first paint, first contentful paint, first meaningful paint, first text - paint, and first image paint. The renderer timestamp is recorded on the - Paint path, while the swap timestamp is the result of a CC SwapPromise - (queued on the Paint path) either being successfully fulfilled, or broken in - cases where the swap did not occur. As we switch to using the swap - timestamps in place of their renderer counterparts, this metric allows us to - see the discrepancies between the two timestamps. - - - - - sadrul@chromium.org - - 'Swap time' is the timestamp of the renderer submitting a CompositorFrame, - and 'Presentation time' is the timestamp of the frame becoming visible on - screen. This metric measures the duration between the swap-time and the - presentation-time. This is recorded only if a valid presentation-timestamp - is available. See PageLoad.Internal.Renderer.PresentationTime.Valid for how - often the presentation-timestamp is valid. This is reported only for - compositor-frames that report a paint-timing metric (e.g. - FirstContentfulPaint etc.), and after that frame has been displayed on - screen. - - - - - sadrul@chromium.org - - This boolean keeps track of whether a valid presentation-timestamp was - received or not. This is reported only for compositor-frames that report a - paint-timing metric (e.g. FirstContentfulPaint etc.), and after that frame - has been displayed on screen. - - - - - bmcquade@chromium.org - skobes@chromium.org - - Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has - occurred on the page (including all subframes). Recorded at the end of the - page lifetime, such as when the page is being navigated away from or when a - tab is being closed. Stable since M79; previous versions are expermental and - subject to fluctuation between releases. - - Log of major changes: http://bit.ly/chrome-speed-metrics-changelog - - - - - - Removed in 07/2020 due to misspelling. Use - PageLoad.LayoutInstability.CumulativeShiftScore.AfterBackForwardCacheRestore - instead. - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Measures the cumulative layout shift score (bit.ly/3fQz29y) that has - occurred on the page (including all subframes) after the page is restored - from the back-forward cache. Recorded when the user navigates away or closes - the page after the page was restored from back-forward cache. - - - - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Measures the cumulative layout shift score (bit.ly/3fQz29y) that has - occurred on the page (including all subframes) after the page is restored - from the back-forward cache. Recorded when the user navigates away or closes - the page after the page was restored from back-forward cache. - - - - - bmcquade@chromium.org - skobes@chromium.org - - Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has - occurred in the main frame. Recorded at the end of the page lifetime, such - as when the page is being navigated away from or when a tab is being closed. - - - - - - Removed in 07/2020 due to misspelling. Use - PageLoad.LayoutInstability.CumulativeShiftScore.MainFrame.AfterBackForwardCacheRestore - instead. - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Measures the cumulative layout shift score (bit.ly/3fQz29y) that has - occurred in the main frame after the page is restored from the back-forward - cache. Recorded when the user navigates away or closes the page after the - page was restored from back-forward cache. - - - - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - - Measures the cumulative layout shift score (bit.ly/3fQz29y) that has - occurred in the main frame after the page is restored from the back-forward - cache. Recorded when the user navigates away or closes the page after the - page was restored from back-forward cache. - - - - - csharrison@chromium.org - - The number of URLs in the redirect chain for this navigation. This excludes - the first URL. - - - - - bmcquade@chromium.org - - For page loads that start in the foreground, measures the duration of time - until one of the following events occurs: the load of the main resource - fails, the page load is stopped, the tab hosting the page is closed, the - render process hosting the page goes away, a new navigation which later - commits is initiated in the same tab, or the tab hosting the page is - backgrounded. This metric has a very long tail, for pages that spend a long - period of time in the foreground. As such, use of the mean or tail values - are not recommended. - - - - - jkarlin@chromium.org - - The time since navigation start before the user presses the back button on a - page. Only measures page loads that remained in foreground and were created - by user gesture inside the renderer (as opposed to browser UX gestures). - - - - - bmcquade@chromium.org - shivanisha@chromium.org - - Measures the time from navigation timing's navigation start to the time the - provisional load failed. Only measures provisional loads that failed in the - foreground. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - user first foregrounds an initially backgrounded tab. Only measures - navigations that started in the background. - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from a background tab being switched to the foreground to - the time the first contentful paint is performed, for main frame documents. - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from a background tab being switched to the foreground to - the time the first paint is performed, for main frame documents. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, across all frames. See - PageLoad.PaintTiming.NavigationToLargestContentfulPaint for more - information. This experimental version includes content that has been - removed. - - - - - npm@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, for main frame documents. - See PageLoad.PaintTiming.NavigationToLargestContentfulPaint for more - information. This experimental version includes content that has been - removed. - - - - - - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - The time from navigation start to first "contentful" paint. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - Log of major changes: http://bit.ly/chrome-speed-metrics-changelog - - - - - tdresser@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first image is painted, for main frame documents. For images that render - progressively, this is recorded as soon as any image pixels have been drawn. - - - - - ksakamoto@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first paint is performed, for main frame documents. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - altimin@chromium.org - hajimehoshi@chromium.org - bfcache-dev@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from back-forward navigation timing's navigation start to - the time the first paint is performed, for main frame documents. Recorded - only when the page is restored from back-forward cache. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - - - - - Discontinued Nov 2018 because data is no longer being used. - - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first non-blank text is painted, for main frame documents. - - - - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, across all frames. - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. Stable since M79; - previous versions are experimental and subject to fluctuation between - releases. - - Log of major changes: http://bit.ly/chrome-speed-metrics-changelog - - - - - maxlg@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from navigation timing's navigation start to the time the - largest content (text or image) is first painted, for main frame documents. - Excludes any content painted after user input. The value is recorded at the - end of each page load unless there is an abort or user input before text or - image paint. See http://bit.ly/fcp_plus_plus for details. - - - - - bmcquade@chromium.org - csharrison@chromium.org - speed-metrics-dev@chromium.org - - Measures the time from when the HTML parser started, to when the page first - paints content. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - parser started, for main frame documents. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the execution of - scripts, for main frame documents that finished parsing. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the execution of - scripts inserted from document.write, for main frame documents that finished - parsing. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts, - for main frame documents that finished parsing. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts - inserted from document.write, for main frame documents that finished - parsing. - - - - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser was active, for main frame documents - that finished parsing. - - - - - - deprecated in favor of PageLoad.Timing2.* - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - DOMContentLoaded event is fired, for main frame documents. - - - - - - deprecated in favor of PageLoad.Timing2.* - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first layout is performed, for main frame documents. - - - - - - deprecated in favor of PageLoad.Timing2.* - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - load event is fired, for main frame documents. - - - - - - deprecated in favor of PageLoad.DocumentTiming.ParseDuration - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from when DOM loading occurs (the time that HTML parsing - begins) to the time the DOMContentLoaded event is fired, for main frame - documents. This is equivalent to the time that the HTML document resource - was being parsed. - - - - - - deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from when DOM loading occurs (the time that HTML parsing - begins) to first "contentful" paint. - - - - - - deprecated in favor of PageLoad.PaintTiming.ForegroundToFirstPaint - - pkotwicz@chromium.org - - Measures the time from a background tab being switched to the foreground to - the time the first paint is performed, for main frame documents. - - - - - - Removed in favor of PageLoad.ParseTiming.NavigationToParseStart - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - navigation committed, for main frame documents. - - - - - - deprecated in favor of - PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - DOMContentLoaded event is fired, for main frame documents. This metric is - being phased out in favor of the PageLoad.DocumentTiming equivalent and will - be deprecated in M54. - - - - - - deprecated in favor of PageLoad.PageTiming.NavigationToFailedProvisionalLoad - - bmcquade@chromium.org - shivanisha@chromium.org - - Measures the time from navigation timing's navigation start to the time the - provisional load failed. Only measures provisional loads that failed in the - foreground. - - - - - - deprecated in favor of PageLoad.AbortTiming.Background.* - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - user first backgrounds the tab. Only measures navigations that started in - the foreground. - - - - - - deprecated in favor of PageLoad.PaintTiming.NavigationToFirstContentfulPaint - - ksakamoto@chromium.org - - The time from navigation start to first "contentful" paint. This - metric is being phased out in favor of the PageLoad.PaintTiming equivalent - and will be deprecated in M54. - - - - - - deprecated in favor of PageLoad.PageTiming.NavigationToFirstForeground - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - user first foregrounds an initially backgrounded tab. Only measures - navigations that started in the background. - - - - - - deprecated in favor of PageLoad.PaintTiming.NavigationToFirstImagePaint - - ksakamoto@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first image is painted, for main frame documents. For images that render - progressively, this is recorded as soon as any image pixels have been drawn. - This metric is being phased out in favor of the PageLoad.PaintTiming - equivalent and will be deprecated in M54. - - - - - - deprecated in favor of PageLoad.DocumentTiming.NavigationToFirstLayout - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first layout is performed, for main frame documents. This metric is being - phased out in favor of the PageLoad.DocumentTiming equivalent and will be - deprecated in M54. - - - - - - deprecated in favor of PageLoad.PaintTiming.NavigationToFirstPaint - - ksakamoto@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first paint is performed, for main frame documents. This metric is being - phased out in favor of the PageLoad.PaintTiming equivalent and will be - deprecated in M54. - - - - - - deprecated in favor of PageLoad.PaintTiming.NavigationToFirstTextPaint - - ksakamoto@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first non-blank text is painted, for main frame documents. This metric is - being phased out in favor of the PageLoad.PaintTiming equivalent and will be - deprecated in M54. - - - - - - deprecated in favor of PageLoad.DocumentTiming.NavigationToLoadEventFired - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from navigation timing's navigation start to the time the - load event is fired, for main frame documents. This metric is being phased - out in favor of the PageLoad.DocumentTiming equivalent and will be - deprecated in M54. - - - - - - deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts, - for main frame documents that started parsing. - - - - - - deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts, - for main frame documents that finished parsing. This metric is being phased - out in favor of the PageLoad.ParseTiming equivalent and will be deprecated - in M54. - - - - - - deprecated in favor of - PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts - inserted from document.write, for main frame documents that started parsing. - - - - - - deprecated in favor of - PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser spent blocked on the load of scripts - inserted from document.write, for main frame documents that finished - parsing. This metric is being phased out in favor of the - PageLoad.ParseTiming equivalent and will be deprecated in M54. - - - - - - deprecated in favor of PageLoad.ParseTiming.ParseDuration - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time that the HTML parser was active, for main frame documents - that finished parsing. This metric is being phased out in favor of the - PageLoad.ParseTiming equivalent and will be deprecated in M54. - - - - - - deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint - - bmcquade@chromium.org - csharrison@chromium.org - - Measures the time from when the HTML parser started, to when the page first - paints content. This metric is being phased out in favor of the - PageLoad.PaintTiming equivalent and will be deprecated in M54. - - - - - panicker@chromium.org - - Tracks the transitions of the page between the various PageLifecycleStates: - active, hidden/backgrounded, hidden/foregrounded, and frozen. A page is - considered active if is visible. A page is considered backgrounded if not - visible and not currently providing a useful service, such as playing audio. - A page is considered foregrounded if it is not backgrounded. A page can be - frozen due to being hidden/backgrounded for a specified amount of time, or - frozen due to critical resources. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Total time the browser process waited for all render processes to save their - respective frames while saving a page into MHTML. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time the browser process waited on a single frame to be saved by a render - processes while saving a page into MHTML. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to encode into MTHML the fully serialized contents of a frame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sclittle@chromium.org - offline-dev@chromium.org - Final status of the MHTML save operation for a page. - - - - sclittle@chromium.org - offline-dev@chromium.org - Time taken to save a page into an MHTML file. - - - - - Removed 6/2019. No longer used. - - jianli@chromium.org - offline-dev@chromium.org - - Recorded when the popup overlays are removed from MHTML serialization. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time spent by the main threads of all involved render processes while saving - the frame tree of a page to MHTML. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time spent by the renderer main thread while saving one frame of a page to - MHTML. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - The longest time taken by the main thread of a render processes to save one - frame of a page being saved to MHTML. In other words this is the maximum - value reported in - PageSerialization.MhtmlGeneration.RendererMainThreadTime.SingleFrame for one - page save operation. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to fully serialize the contents of a frame, including HTML and - CSS and image resources. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time spent writing a frame's encoded MHTML data to the file or data pipe - handle passed to the Renderer, recorded when the writing is done and the - handle is closed. Note that when writing to a data pipe, this metric does - not precisely reflect the time taken to write the data to disk. - - - - - sclittle@chromium.org - offline-dev@chromium.org - Reports the result of an attempt to load an MHTML archive. - - - - dimich@chromium.org - - Percentage of loaded CSS elements in the main frame at the time of - serialization. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Percentage of loaded images in the main frame at the time of serialization. - - - - - dimich@chromium.org - - Total number of CSS elements in the main frame for serialization. - - - - - dimich@chromium.org - Total number of images in the main frame for serialization. - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time spent serializing a CSS element (including embedded "sub"-CSS - and images). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time taken to generate HTML data from a frame's DOM and serialize it - (without sub-resources like CSS and images). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - sclittle@chromium.org - offline-dev@chromium.org - - Time spent serializing an image element. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by PaintHolding.CommitTrigger2 in M-79 - - schenney@chromium.org - paint-dev@chromium.org - - Records the reason that a commit was triggered, to enable research into - which event (non-same-origin, FCP, timeout, etc) led to the first commit. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Records the reason that a commit was triggered, to enable research into - which event (non-same-origin, FCP, timeout, etc) led to the first commit. - - - - - - Replaced with PaintHolding.InputTiming2 in M-79. - - schenney@chromium.org - paint-dev@chromium.org - - Records whether or not input arrived before the first commit. - - - - - schenney@chromium.org - paint-dev@chromium.org - - Records whether or not input arrived before the first commit. - - - - - - Removed Aug 2017 - - csharrison@chromium.org - - The delay from when bytes are received on the main thread to when the - BackgroundHTMLParser starts tokenizing them. Always a shorter time than the - time emitted to Parser.PreloadTokenizeDelay. - - - - - - Removed May 2017 - - csharrison@chromium.org - - The time it takes to enqueue a ParsedChunk onto the shared parser queue. - - - - - - Removed Feb 2020 - - csharrison@chromium.org - - The number of speculative tokens discarded by the parser when a rewind is - needed. - - - - - - Removed Aug 2017 - - csharrison@chromium.org - - The maximum number of pending Chunks in the ParsedChunkQueue after the - parser is detached. - - - - - - Removed Aug 2017 - - csharrison@chromium.org - - The maximum number of pending tokens in the ParsedChunkQueue after the - parser is detached. - - - - - - Removed May 2017 - - csharrison@chromium.org - - The delay from when bytes are received on the main thread to when they are - tokenized and preloads are sent back to the main parser. Always a greater - time than the time emitted to Parser.AppendBytesDelay. - - - - - - Removed as of 07/2019. Use Memory.Renderer.* and - Memory.Experimental.Renderer2.* instead. - - haraken@chromium.org - - The committed memory size in PartitionAlloc. The value is reported when we - see the highest memory usage we've ever seen in the renderer process. - - - - - - Removed 2017-12 by PartnerBookmark.Count2. - - wychen@chromium.org - - The number of partner bookmark entries. Note that zero would be - under-represented because reading is throttled if the last result is zero. - Logged when using the bookmark, not skipped (PartnerBookmark.Skipped == - False), and at most once per cold start. Note that the distribution is - weighted by bookmark usage. - - - - - bttk@chromium.org - wychen@chromium.org - - The number of partner bookmark entries. Logged when using the bookmark, and - at most once per cold start. Note that the distribution is weighted by - bookmark usage. - - - - - tedchoc@chromium.org - wychen@chromium.org - - The response we got back from our favicon fetching throttler, once for each - bookmark at each cold start. Only recorded on Android. - - - - - bttk@chromium.org - wychen@chromium.org - - The time spent on loading partner bookmarks, from kickOffReading() to - bookmarkModelLoaded() callback. - - - - - - No longer recorded as of Apr 2018 - - wychen@chromium.org - - Whether there's no partner bookmark provider. By default, the system image - contains a dummy partner bookmarks provider that provides zero entries. - Logged when using the bookmark, not skipped (PartnerBookmark.Skipped == - False), and at most once per cold start. - - - - - - No longer recorded as of Apr 2018 - - wychen@chromium.org - - Whether reading of partner bookmark is skipped. Logged when using the - bookmark, and at most once per cold start. - - - - - - Removed 2017-12. Use PartnerBookmark.TimeSinceLastEmptyRead2. - - wychen@chromium.org - - When trying to load the partner bookmarks, if no partner bookmark is read - last time, record the time elapsed since then. It is recorded no matter - whether loading would be skipped. - - - - - - No longer recorded as of Apr 2018 - - wychen@chromium.org - - When trying to load the partner bookmarks, if no partner bookmark is read - last time, record the time elapsed since then. It is recorded no matter - whether loading would be skipped. - - - - - - Removed 2019-07. See crbug.com/975263 for wrap-up analysis. - - tedchoc@chromium.org - wychen@chromium.org - - Number of elements read from the partner bookmarks favicon cache, recorded - once per cold start when reading partner bookmarks. Only recorded on - Android. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Whether the user proceeded to the list of the left compromised passwords - from the bubble following save/update password. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The state of the bubble shown after users saves/updates a password. It - notifies the user about leftover compromised passwords. - - - - - vasilii@chromium.org - - When the password management bubble opened, what state was it in? - - - - - jdoerrie@chromium.org - kolos@chromium.org - vasilii@chromium.org - - Measures the frequency of various password generation events. - - Note that this histogram is logged from the renderer process, and - consequently the numbers should not be directly compared to the other - PasswordGeneration.* histograms, which are logged from the browser process. - Histograms logged in different processes are lost at different rates, which - introduces systematic bias between histograms logged in the renderer process - vs. those logged in the browser process. - - - - - kolos@chromium.org - - Measures the frequency of user editing of generated passwords. Uploaded once - per generated password save. Applicable to automatic and manual generations. - - - - - kolos@chromium.org - - Measures the frequency of manually triggered password generations. - - - - - - Removed 2020-04. - - vasilii@chromium.org - jdoerrie@chromium.org - - Records whether there is a username conflict with existing credentials when - the user clicks 'Generate Password'. - - - - - jdoerrie@chromium.org - kolos@chromium.org - - Measures the frequency of submission events for passwords that could have - been generated, but the user didn't choose to use the feature. This is to - compare with PasswordGeneration.SubmssionEvent. - - - - - jdoerrie@chromium.org - kolos@chromium.org - - Measures the frequency of submission events for generated passwords. This is - similar to PasswordManager.ActionsTakenWithPsl but only tracks events which - are interesting for generated passwords. - - - - - jdoerrie@chromium.org - kolos@chromium.org - vasilii@chromium.org - - The number of times that we try to upload a form that we believe should - trigger password generation. False means that something about the form would - not allow us to try upload (not an Autofillable field, uploading disabled, - Autofill servers in backoff, etc.). True does not mean that the upload - actually completed successfully, just that it was started. - - - - - ioanap@chromium.org - vasilii@chromium.org - - Records user-triggered events related to a generated password. Only the last - occurring event is logged. The recording takes place when the password form - is destroyed. - - - - - - Removed 10/2018 in favor of PasswordGeneration.UserDecision. - - ioanap@chromium.org - vasilii@chromium.org - - Records user-triggered events related to a generated password. Each event is - logged at most once per lifetime of the generated password. - - - - - mlerman@chromium.org - - Time required to create the local hash of the user's GAIA password. - - - - - vasilii@chromium.org - src/components/password_manager/OWNERS - - Records attempts to prompt user to save a password when password store is - not ready for saving passwords due to an initialization error. Recorded once - per form submission. - - - - - - Removed July 2019. - - alexmos@chromium.org - battre@chromium.org - - Records attempts to submit a password on a form in an about:blank frame, - indicating whether this attempt is for a main frame or subframe. Recorded - once per form submission. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The type of event that the Password Manager used for detecting a password - form submission when saving or updating a password. Recorded each time a - user accepts a password save/update prompt. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Recorded whenever the user accesses the passwords in the settings page. - - - - - - Removed as of Chrome 56. See the histograms for one and more accounts. - - vasilii@chromium.org - The dismissal reason of the account chooser. - - - - - Removed as of 06/19. - - vasilii@chromium.org - The number of accounts displayed in the account chooser. - - - - - Removed as of 06/19. - - vasilii@chromium.org - - The count of the placeholder avatars shown in the account chooser. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The dismissal reason of the account chooser with multiple accounts. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The dismissal reason of the account chooser with one account. - - - - - - Removed as of 06/19. - - vasilii@chromium.org - - Whether the account chooser includes an empty username or any duplicates - - - - - - Removed in M79 in favor of PasswordManager.AccountsPerSiteHiRes. - - dvadym@chromium.org - vasilii@chromium.org - - The number of accounts stored per site in the password manager (one event - per site) - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The number of accounts stored per site in the password manager's - profile-scoped store. Records one event per site, split by whether created - by the user or generated by Chrome, and further by whether the user used - sync with custom passphrase or not. - - - - - - Removed 2020/02 because it's unused. - - dvadym@chromium.org - engedy@chromium.org - vasilii@chromium.org - - Records, for each account, the number of other accounts (across all sites - and usernames) that reuse the same password. Only non-blacklisted, - HTML-form-based accounts are considered. - - For each account, samples will only be recorded into the histograms that - have the first suffix corresponding to whether that account was saved on a - secure website or not. The second suffix is used to further categorize the - other accounts that reuse the same password based on how they relate to the - account in question, and whether they are secure. The number of other - accounts in each category will be reported into histogram with the - respective second suffixes. - - Metrics are collected once per browser start-up. In case of multiple - profiles, the counts are for the profile for which a WebContents is first - created. - - - - - mamir@chromium.org - treib@chromium.org - - Records whether the account-scoped password storage had to be cleared during - profile initialization. - - - - - mamir@chromium.org - treib@chromium.org - - Recorded whenever the opt-in for the account-scoped password storage is - cleared for all Google Accounts. This typically happens because the signin - cookies were cleared. The recorded value is the number of opt-ins that were - cleared. - - - - - treib@chromium.org - victorvianna@google.com - - When the user accepts to move a password from the profile store to the - account store, this records what user action caused the moving flow to be - offered. If the flow is offered but rejected by the user, the histogram is - not recorded. Recorded only in Win/Mac/Linux. - - - - - treib@chromium.org - victorvianna@google.com - - When the user is offered to move a password from the profile store to the - account store, this records what user action caused the moving flow to be - offered. Recorded only in Win/Mac/Linux. - - - - - mamir@chromium.org - treib@chromium.org - - Recorded whenever a user opts in to the account-scoped password storage. The - recorded value is the total number of opted-in accounts in this profile, - including the new opt-in. - - - - - mamir@chromium.org - treib@chromium.org - - Recorded whenever a user opts out of the account-scoped password storage. - The recorded value is the total number of opted-in accounts remaining in - this profile after the current opt-out. - - - - - treib@chromium.org - victorvianna@google.com - - Records whether a signed-in account was still found by the time Chrome - attempted to opt out the user of passwords account storage and clear the - associated settings. If no signed-in account is found, the opt-out and clean - up won't happen. Recorded only in Win/Mac/Linux, when opting out of the - account-scoped passwords storage. One example would be when the user clicks - the opt-out button in chrome://settings/passwords. - - - - - treib@chromium.org - victorvianna@google.com - - Records how many passwords in the account store were unsynced when the user - signed out of their Google Account. Recorded only in Win/Mac/Linux when a - user of the account-scoped password storage signs out. - - - - - - - mamir@chromium.org - treib@chromium.org - - The amount of active browsing time that was spent in different user states - related to the PasswordManager's account-scoped storage. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser (as determined by - DesktopSessionDurationTracker) or their user state changes. These end-points - are when the metric is emitted. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - - - - jdoerrie@chromium.org - mamir@chromium.org - treib@chromium.org - vasilii@chromium.org - - The number of accounts stored per site in the password manager's - account-scoped store. Records one event per site, split by whether created - by the user or generated by Chrome, and further by whether the user used - sync with custom passphrase or not. - - - - - jdoerrie@chromium.org - mamir@chromium.org - treib@chromium.org - vasilii@chromium.org - - The total number of sites that the user has blacklisted in the password - manager's account-scoped store. Recorded by iterating over stored passwords - once per run of Chrome. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - mamir@chromium.org - treib@chromium.org - - Number of password forms with empty username in the account-scoped Login - Database. This is recorded on startup. - - - - - vasilii@chromium.org - mamir@chromium.org - treib@chromium.org - - The number of saved passwords in the account-scoped store that could not be - decrypted. Recorded once for the profile on startup. - - - - - battre@chromium.org - jdoerrie@chromium.org - mamir@chromium.org - treib@chromium.org - - The number of times each saved password from the account-scoped storage has - been used to log in. Split by whether created by the user or generated by - Chrome, and further by whether the user used sync with custom passphrase or - not. Recorded by iterating over stored passwords once per browser run, soon - after startup. - - - - - battre@chromium.org - mamir@chromium.org - treib@chromium.org - vasilii@chromium.org - - The number of accounts stored in the password manager's account-scoped store - (across all sites), split by whether created by the user or generated by - Chrome, and further by whether the user used sync with custom passphrase or - not. - - - - - battre@chromium.org - mamir@chromium.org - treib@chromium.org - vasilii@chromium.org - - The number of accounts stored in the password manager's account-scoped store - (across all sites) for origins with the scheme (e.g., HTTP, HTTPS, FTP) as - given in the histogram suffix. For each scheme, the count is recorded once - per browser start-up. (In case of multiple profiles, the counts are for the - profile that first has a WebContents created.) - - - - - mamir@chromium.org - treib@chromium.org - - The number of accounts stored in the password manager's account-scoped store - that don't exist in the profile-scoped store. Recorded once per run of - Chrome, soon after startup. - - - - - mamir@chromium.org - treib@chromium.org - - The number of accounts stored in the password manager with a conflicting - password between the account-scoped store and profile-scoped store (i.e. the - signon realm and username match, but the password does not). Recorded once - per run of Chrome, soon after startup. - - - - - mamir@chromium.org - treib@chromium.org - - The number of accounts stored in both the password manager's account-scoped - store and profile-scoped store. Recorded once per run of Chrome, soon after - startup. - - - - - mamir@chromium.org - treib@chromium.org - - The number of accounts stored in the password manager's profile-scoped store - that don't exist in the account-scoped store. Recorded once per run of - Chrome, soon after startup. - - - - - - Removed as of Chrome 32. See PasswordManagerActionsTakenWithPsl - - - Stats documenting how we handle every form containing a password, bucketed - by the actions taken. - - - - - - Removed as of 12/10/2019. - - estark@chromium.org - - Stats documenting how we handle every form containing a password on a - non-secure page, bucketed by the actions taken. - - - - - - Removed as of 12/10/2019. - - dvadym@chromium.org - vasilii@chromium.org - - Stats documenting how we handle every form containing a password, bucketed - by the actions taken. - - - - - - Removed as of 3/18/2014. See PasswordManagerActionsTakenV3. - - yfriedman@chromium.org - - Stats documenting how we handle every form containing a password, bucketed - by the actions taken. - - - - - engedy@chromium.org - - The number of facets for which affiliation information was requested in a - network fetch. Recorded for each network fetch. - - - - - engedy@chromium.org - - The time elapsed between creation of the AffiliationBackend and the first - time it needed to issue a network fetch. - - - - - engedy@chromium.org - - The elapsed time between subsequent network fetches. Recorded whenever the - AffiliationBackend initiated a network fetch, regardless of success or - failure. - - - - - - No longer recorded as of May 2015. - - engedy@chromium.org - - The number of facets affiliated with a dummy Web facet, according to the - affiliation information retrieved from the cache. Recorded for each dummy - Web facet, once shortly after start-up, and then periodically every hour; - but only if getting affiliations succeeded for the Web facet. - - - - - - No longer recorded as of May 2015. - - engedy@chromium.org - - Whether or not affiliations of a dummy Web facet could be successfully - retrieved from the cache. Recorded for each dummy Web facet, once shortly - after start-up, and then periodically every hour. - - - - - engedy@chromium.org - - The network error code, as reported by the underlying URLFetcher. Recorded - only for each network fetch that failed due to network/server errors. - - - - - engedy@chromium.org - - The HTTP response code, as reported by the underlying URLFetcher. Recorded - only for each network fetch that failed due to network/server errors. - - - - - engedy@chromium.org - - Whether the network fetch succeeded, failed due to network/server errors, or - contained malformed data. Recorded for each network fetch. - - - - - - The bubble isn't shown anymore. Become obsolete in Feb. 2015. - - melandory@chromium.org - vasilii@chromium.org - Why was "Allow to collect URL?" bubble closed? - - - - - No longer recorded as of June 2019. - - fhorschig@chromium.org - vasilii@chromium.org - - Records what happened to the progress bar during exporting passwords when - its dismissal was requested. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a password credential entry in the preferences - on Android. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a password of a password credential entry in - the preferences on Android. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a username of a password credential entry in - the preferences on Android. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a website of a password credential entry on - Android. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a password exception entry in the preferences - on Android. - - - - - fhorschig@chromium.org - ioanap@chromium.org - - Records the action taken with a website of a password exception entry in the - preferences on Android. - - - - - - No longer recorded as of June 2019. - - fhorschig@chromium.org - - Records whether a user triggered the search function while visiting the - password preferences page on Android. - - - - - mamir@chromium.org - mastiz@chromium.org - - Records different results upon adding a remote password to the password - manager. It is recorded every time after receiving remote password - incremental updates from the server. - - - - - mamir@chromium.org - mastiz@chromium.org - - Records different results upon updating a remote password to the password - manager. It is recorded every time after receiving remote password - incremental updates from the server. - - - - - mamir@chromium.org - mastiz@chromium.org - - Records different states upon applying remote sync changes to the password - manager. It recorded every time after receiving remote password incremental - updates from the server. - - - - - - Removed February 2019. - - gcasto@chromium.org - - If the password manager UI was suppressed because generation UI was already - being displayed for the same field. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The dismissal reason of the auto-signin first run experience. - - - - - - Corresponding clean-up logic got introduced in M70 and has run its course. - - jdoerrie@chromium.org - - The number of duplicates forms from the password store. Recorded once for - the profile on startup. - - - - - - Removed in M76 in favor of PasswordManager.BlacklistedSitesHiRes. - - jdoerrie@chromium.org - vasilii@chromium.org - - The total number of sites that the user has blacklisted in the password - manager's profile-scoped store. Recorded by iterating over stored passwords - once per run of Chrome. - - - - - - Corresponding clean-up logic got introduced in M76 and has run its course. - - jdoerrie@chromium.org - vasilii@chromium.org - - Records once on startup whether the blacklisted sites in the password store - need to be normalized. - - - - - - Corresponding clean-up logic got introduced in M70 and has run its course. - - jdoerrie@chromium.org - vasilii@chromium.org - - Records once on startup whether the blacklisted sites in the password store - need to be cleared of duplications. - - - - - - Removed August 2018. - - vasilii@chromium.org - - Records once on startup whether the blacklisted sites in the password store - need to be updated to remove username/password. Can be removed around Chrome - M69 (https://crbug.com/817754). - - - - - - Removed April 2019. - - jdoerrie@chromium.org - vasilii@chromium.org - - Boolean indicating whether adding a blacklist entry was prevented due to an - already existing entry. Recorded after every blacklist site submission. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The total number of sites that the user has blacklisted. Recorded by - iterating over stored passwords once per run of Chrome. - - - - - battre@chromium.org - vasilii@chromium.org - - The number of accounts stored in password_manager::StatisticsTable. These - are accounts for which the user ignored the save bubble at least once. The - count is recorded once per browser start-up. (In case of multiple profiles, - the counts are for the profile that first has a WebContents created.) - - - - - - Removed as of 07/2020. - - battre@chromium.org - vasilii@chromium.org - - The number of accounts that do not trigger password save prompts anymore. - The count is recorded once per browser start-up. (In case of multiple - profiles, the counts are for the profile that first has a WebContents - created.) - - - - - - Removed as of 07/2020. - - battre@chromium.org - vasilii@chromium.org - - The number of domains for which at least one account exists that does not - trigger password save prompts anymore. The count is recorded once per - browser start-up. (In case of multiple profiles, the counts are for the - profile that first has a WebContents created.) - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of credentials initially to be checked when the password bulk check - was canceled. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The time the password bulk check was running until canceled by the user. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of credentials analyzed when the password bulk check completed - successfully. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - Error encountered during the password bulk check. - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of leaked credentials found when the password bulk check completed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Referrer of a navigation to the Password Check page. Recorded when the user - visits the Password Check settings page, either via native or Web UI. - - - - - ioanap@chromium.org - fhorschig@chromium.org - - Referrer of a navigation to the Password Check UI Settings view. Recorded - when the user enters the view. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The time it took for the password bulk check to complete successfully. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - The average time per credential when the password bulk check completed - successfully. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - User actions performed on the Password Check settings page. - - - - ioanap@chromium.org - fhorschigg@chromium.org - User actions performed on the Password Check settings view. - - - - kolos@chromium.org - - The time (ms) it takes to infer button titles within a form tag. - - - - - kolos@chromium.org - - The time (ms) it takes to infer button titles outside of form tags. - - - - - battre@chromium.org - jdoerrie@chromium.org - chrome-password-manager-team@google.com - - When the password manager sees new forms on the page, it records in this - histogram whether there were any SSL certificate errors. The presence of SSL - errors likely means that the password manger will stop working, so the - reporting is done at the last point when password manager is still - guaranteed to be active. Some particular errors are distinguished, with the - rest being reported in a catch-all bucket. - - - - - vakh@chromium.org - vasilii@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a password hash was saved or not on Chrome sign-in page. - Recorded whenever the user types a password on Chrome sign-in page. - - - - - vasilii@chromium.org - src/components/password_manager/OWNERS - - Collects positive number of undecryptable passwords that were successfully - deleted when syncing was enabled. Called for sync user for each profile if - there is at least one password deleted when merging logins from Sync and - local database. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Collects the type of compromised credential when it is added, updated, or - removed from the table. Compromised credentials are saved passwords that are - added when they are leaked or phished, updated when signon_realm and/or - username is changed, or removed when the password is dropped from the - password_manager or the password has changed. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of known leaked credentials in the database on start-up. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of known leaked credentials in the database on start-up if the - password bulk check was executed at least once. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Count of known phished credentials in the database on start-up. - - - - - fhorschig@chromium.org - mamir@chromium.org - - Records how many credentials from the account store are available to a user - right after they unlocked the account store. If a credential is an exact - duplicate with a local credential, it still counts into this metric. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The number of stored (non-blacklisted) credentials for which - "duplicates" exist. A duplicate is a credential with the same - signon realm, username, and password - i.e. indistinguishable from the - user's point of view. This records the number of *sets* of duplicated - credentials; the number of credentials in each set of duplicates is not - recorded. Recorded once per browser start-up. (In case of multiple profiles, - the counts are for the profile that first has a WebContents created.) - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The number of stored (non-blacklisted) credentials for which - "mismatched duplicates" exist. A mismatched duplicate is a - credential with the same signon realm and username, but different password. - This records the number of *sets* of duplicated credentials; the number of - credentials in each set of duplicates is not recorded. Recorded once per - browser start-up. (In case of multiple profiles, the counts are for the - profile that first has a WebContents created.) - - - - - mamir@chromium.org - treib@chromium.org - - The default store for newly-saved passwords (profile-scoped store or - account-scoped store), recorded whenever it is set explicitly. - - - - - - Removed as of 06/2020. - - vasilii@chromium.org - - Records the result of removing passwords that cannot be decrypted when - retrieving passwords from LoginDatabase. Called for Mac users for each - profile. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Records the return value of the DeleteUndecryptableLogins method in the - LoginDatabase class. Called for sync user and for each profile when merging - logins from Sync and local database. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Records availability of password manager suggestions in regular and - off-the-record modes. - - - - - jdoerrie@chromium.org - battre@chromium.org - - Records a bitmask of password form changes after the first time this form is - seen by Password Manager. Recorded once per a form when the form is removed - from DOM. Bit 0 - changes in number of fields, bit 1 - changes in fields - renderer ids, bit 2 - changes in autocomplete attributes, bit 3 - changes in - form control types. - - - - - battre@chromium.org - vasilii@chromium.org - - Indication whether users change the credentials (username and password) in - the save bubble of the password manager, considering only cases where the - user saves a new credential or updates a credential. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Number of password forms with empty username in the profile-scoped Login - Database. This is recorded on startup. - - - - - - Removed as of 06/2019. - - msramek@chromium.org - vasilii@chromium.org - - When parsing a password form, and no username field is detected, whether - this was a password change form. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - When offering to save a password, whether the username is empty. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - When parsing a password form, whether a username field is detected. - - - - - - Removed as of 09/2018. The investigation this metric was supporting has been - concluded in 2016. - - msramek@chromium.org - vasilii@chromium.org - - The number of password fields for password forms that do not have a username - field. This is recorded every time such a password form is successfully - parsed. Note that the parsing is attempted when the form is encountered (i.e - when the document is loaded) and also when it is submitted. - - - - - - Removed as of 09/2018. The investigation this metric was supporting has been - concluded in 2016. - - msramek@chromium.org - vasilii@chromium.org - - The total number of text and password fields for password forms that do not - have a username field. This is recorded every time such a password form is - successfully parsed. Note that the parsing is attempted when the form is - encountered (i.e when the document is loaded) and also when it is submitted. - - - - - - Removed as of 06/2019. - - msramek@chromium.org - vasilii@chromium.org - - Number of password forms with empty username in the Login Database for which - there is not another password form from the same realm with a nonempty - username. In other words, number of password forms with empty username which - we do not suspect to be reauthentication forms. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Indicates whether the password manager is enabled when a tab is opened. This - includes prerendered tabs. - - - - - - Removed as of 2019/07. Password exporting has been rolled out. - - cfroussios@chromium.org - ioanap@chromium.org - vasilii@chromium.org - The number of passwords exported in CSV format per user. - - - - - Removed as of 2019/07. Password exporting has been rolled out. - - cfroussios@chromium.org - ioanap@chromium.org - vasilii@chromium.org - The success or error type of exporting passwords into CSV. - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Records number of rows in FieldInfoTable, which contains locally learned - predictions about field types. Recorded once for the profile on startup. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - When a credential is filled, whether it comes from an Android app. - - - - - jdoerrie@chromium.org - battre@chromium.org - - This metric records the user experience with regards to passwords filling. - It is only recorded on password form submissions that are considered to be - successful. - - The first 4 buckets (0..3) are ranging from the best filling behavior - (automatic filling on page load without user interaction necessary) to the - worst (the user had to manually type a password that was already saved). - - The following buckets (4..5) indicate cases when it was impossible to fill - credentials because unknown credentials were submitted, meaning that the - submitted password was not saved before. - - The last bucket (6) corresponds to the strange cases, where the submitted - form has neither user input nor autofilled data in password fields. This - might indicate third-party password manager use, or might be a - measurement/submission classification error. - - - - - mamir@chromium.org - treib@chromium.org - - This metric records the source of filled passwords: The profile-scoped - store, the account-scoped store, both of them, or none of them (if the user - typed the password manually). It is only recorded on password form - submissions that are considered to be successful. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - When offering to fill the username and password, whether at least one of the - credentials in the dropdown comes from an Android app. - - - - - jdoerrie@chromium.org - battre@chromium.org - - Records whether the PasswordAutofillAgent in the renderer manages to fill - credentials as instructed by the browser or records a failure reason - otherwise. Only the outcome of the first attempt to fill is recorded. - - This is replicated as PasswordForm.Fill.FirstFillingResultInRenderer in UKM. - - - - - jdoerrie@chromium.org - battre@chromium.org - - This metric records why the browser instructs the renderer not to fill the - credentials on page load but to wait for the user to confirm the credential - to be filled. Only the value of the first decision to fill is recorded. - - This is replicated as PasswordForm.Fill.FirstWaitForUsernameReason in UKM. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The success or failure of deserializing saved FormData. Failure either - indicates corrupted data or the presence of bugs in the serialization or - deserialization code. - - - - - jdoerrie@chromium.org - kolos@chromium.org - - When the generation state of a password was changed, records whether an - existing form corresponding to the password was found. - - - - - - Removed as of 05/2017. This metric has been replaced by - PasswordManager.MediationOptional. - - vasilii@chromium.org - - Tracks result of navigator.credentials.get() with unmediated=false. That is - the result of account chooser. - - - - - - Removed as of 05/2017. This metric has been replaced by - PasswordManager.MediationSilent. - - vasilii@chromium.org - - Tracks result of navigator.credentials.get() with unmediated=true. That is - the result of auto sign-in. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The result of an attempted navigation to the Google Password Manager. - Recorded when a signed-in and password syncing user navigates to - https://passwords.google.com by clicking a link. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took for a failed navigation to the Google Password Manager. - Recorded when a signed-in and password syncing user navigates to - https://passwords.google.com by clicking a link and the navigation fails - before timing out. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took for a successful navigation to the Google Password Manager. - Recorded when a signed-in and password syncing user navigates to - https://passwords.google.com by clicking a link and the navigation succeeds - before timing out. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Breakdown of HTTP credentials with regard to the existence of a HTTPS - credential with the same username and whether the corresponding website has - HSTS enabled. Recorded once for each HTTP credential of the profile on - startup. - - - - - - Removed as of M72. Superseded by PasswordManager.HttpCredentials. - - gemene@google.com - jdoerrie@chromium.org - - Number of HTTP credentials, with HSTS enabled as given in the histogram - suffix, for which a conflicting (i.e.same host and username, but different - password) HTTPS credential exists. Recorded once for the profile on startup. - - - - - - Removed as of M72. Superseded by PasswordManager.HttpCredentials. - - gemene@google.com - jdoerrie@chromium.org - - Number of HTTP credentials, with HSTS enabled as given in the histogram - suffix, for which an equivalent (i.e. same host, username and password) - HTTPS credential exists. Recorded once for the profile on startup. - - - - - - Removed as of M72. Superseded by PasswordManager.HttpCredentials. - - gemene@google.com - jdoerrie@chromium.org - - Number of HTTP credential, with HSTS enabled as given in the histogram - suffix, for which no HTTPS credential for the same username exists. Recorded - once for the profile on startup. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Number of HTTP saved passwords that were migrated to HTTPS. Recorded on - HTTPS password form load when there are no credentials saved. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The mode of migration applied to HTTP passwords migrating to HTTPS. Recorded - on HTTPS password form load when there are no credentials saved. - - - - - - Removed as of 07/2018. This metric was deleted at - https://chromium-review.googlesource.com/c/chromium/src/+/1131495. - - - The result of importing passwords stored in IE7 into Chrome's password - store. - - - - - vasilii@chromium.org - src/components/password_manager/OWNERS - The number of passwords imported in CSV format per user - - - - vasilii@chromium.org - src/components/password_manager/OWNERS - - The response code of successful or failed password import attempt from a CSV - file. - - - - - vasilii@chromium.org - mamir@chromium.org - - The number of saved passwords in the profile-scoped store that could not be - decrypted. Recorded once for the profile on startup. - - - - - - Removed as of 03/2016. This metric has been replaced by - PasswordManager.UIDismissalReason. - - - The distribution of responses to the "Do you want Chrome to remember - this password"? info bar prompt. - - - - - - Corresponding clean-up logic got introduced in M71 and has run its course. - - jdoerrie@chromium.org - vasilii@chromium.org - - Records once on startup whether forms with wrong signon_realm created by - HTTP to HTTPS migration need to be removed. See https://crbug.com/881731 for - more details. - - - - - djean@chromium.org - sczs@google.com - - This metric counts how many times the Save Password infobar is shown. - - - - - djean@chromium.org - sczs@google.com - - This metric counts how many times the Update Password infobar is shown. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric reports whether a sync password hash is saved. Recorded shortly - after Chrome startup. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric is recorded shortly after Chrome Startup, only for Advanced - Protection users. This is a subset of - PasswordManager.IsSyncPasswordHashSaved. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Records selection of password manager suggestions in regular and - off-the-record modes. - - - - - jdoerrie@chromium.org - battre@chromium.org - - Records whether a successfully submitted password form has only values that - came from JavaScript. - - - - - - Removed as of 09/2016. - - vasilii@chromium.org - - After migration from the Mac Keychain fails, records the number of passwords - in the Keychain owned by Chrome but not accessible by it. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - After migration from the Mac Keychain fails, records the number of passwords - in the Chrome Password Manager database for which the corresponding values - in the Keychain are not accessible by Chrome. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - After migration from the Mac Keychain fails, records the number of passwords - in the Chrome Password Manager database to be migrated. As there is no - partial migration, it's the total number of passwords in the DB. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - The status of passwords migration from the Keychain. It's recorded shortly - after startup. - - - - - - Removed as of 07/2019. - - dvadym@chromium.org - cfroussios@chromium.org - - The success or failure of deserializing PasswordForms in KWallet. Failure - either indicates corrupted data or the presense of bugs in the - deserialization code. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Status of an attempted fetch of an access token. Recorded when a token fetch - completes. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Net Error Code of a failed attempt to fetch an access token. Recorded when a - token fetch completes with an error state. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - Result of analyzing a single leak response. - - - - jdoerrie@chromium.org - vasilii@chromium.org - The time it took to analyze a single leak lookup response. - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Reason of the dismissal of the leak detection dialog. Recorded when a leaked - credential is detected and the dialog is shown. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Indicates whether the password manager leak detection feature is enabled. - Recorded for each profile on browser start-up. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Shows the error that happened in password leak detection on sign-in. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - HTTP response code of a leak lookup request. Only recoded for each network - fetch that failed due to network/server errors. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - When a password is determined as leaked, records if it's saved for other - sites. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - When a password is determined as leaked, records if it's saved in Chrome. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - When a password is determined as leaked, records if the user is syncing - passwords without passphrase. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Whether the network fetch succeeded, failed due to network/server errors, or - contained malformed data. Recorded for each leak lookup. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Network error code of a leak lookup request. Only recoded for each network - fetch that failed due to network/server errors. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took from starting a leak check to notifying the user about a - leak. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took to obtain an access token for an authenticated leak lookup - request. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took to prepare the payload for a single leak lookup request. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The time it took to receive a server response after issuing a request for a - single leak lookup. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The number of matched prefixes in a single leak lookup response. Only - recorded if the network response was wellformed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The size of a single leak lookup response in bytes. Only recorded if there - was no network or server error. - - - - - - Removed as of Sept 2020. - - cfroussios@chromium.org - jdoerrie@chromium.org - - Whether the password store has been migrated to an encrypted login database. - This is recorded on startup, before any migration attempts. - - - - - - Removed as of Sept 2020. - - cfroussios@chromium.org - jdoerrie@chromium.org - - Whether the password store has been migrated to an encrypted login database. - This is recorded at the end of a migration attempt. - - - - - - Removed 02/2020. - - cfroussios@chromium.org - dvadym@chromium.org - - The time it took to read credentials from the native backend and write them - into the encrypted login database. This is logged once per migration - (normally once per client), at the end of copying into the database. The - migration is triggered on the first operation to the password store. - - - - - - Removed 10/2019. - - cfroussios@chromium.org - dvadym@chromium.org - - The time it took to read credentials from the unencrypted login database and - insert them into the native backend. This is logged once per migration - (normally once per client), at the end of copying into the backend. The - migration is triggered on the first operation to the password store. - - - - - - Removed 07/2019. - - cfroussios@chromium.org - dvadym@chromium.org - - Information about usage of password storage backends on Linux. It also - includes whether a command line flag for a specific backend is given. - - - - - - Removed 06/2019. - - vasilii@chromium.org - - The version of LoginDatabase if the migration to a new one failed. - - - - - vasilii@chromium.org - mamir@chromium.org - An error on LoginDatabase initialization. - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Referrer of a navigation to the "Manage Passwords" page. Recorded - when the user attempts to see their list of passwords, either via native or - Web UI. - - - - - ioanap@chromium.org - vasilii@chromium.org - - Referrer of a navigation to the "Manage Passwords" page. Recorded - only for signed in users syncing passwords without a custom passprase, when - the user attempts to see their list of passwords. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Tracks result of navigator.credentials.get() with - mediation="optional". That is the result of account chooser. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Tracks result of navigator.credentials.get() with - mediation="required". That is the result of forced account - chooser. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Tracks result of navigator.credentials.get() with - mediation="silent". That is the result of auto sign-in. - - - - - mamir@chromium.org - mastiz@chromium.org - - Records different results upon adding a remote password to the password - manager. It is recorded during the initial sync when merging remote and - local data. - - - - - mamir@chromium.org - mastiz@chromium.org - - Records different results upon updating a remote password in the password - manager. It is recorded during the initial sync when merging remote and - local data. - - - - - - - mamir@chromium.org - treib@chromium.org - - Why was the "move password to account?" bubble closed? Recorded - whenever the bubble is closed, either because the user clicked one of the - buttons or it went away automatically (lost focus). - - - - - - Removed 03/2018 in favor of PasswordManager.UpdateUIDismissalReason. - - dvadym@chromium.org - - A user action when a password update bubble with multiple accounts is shown. - - - - - nepper@chromium.org - battre@chromium.org - kolos@chromium.org - - For a newly saved password, whether the password was generated by Chrome or - typed manually by the user. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric reports a type of a password hash change event where the - associated account is not syncing. Recorded when a non sync password hash is - saved or cleared. - - - - - jdoerrie@chromium.org - kazinova@google.com - - Records how many FormManagers are deleted on the main frame navigation. This - metric is useful for estimation of memory footprint. - - - - - - Removed as of 09/2020. - - jdoerrie@chromium.org - kazinova@google.com - - Records the number of password forms extracted by PasswordFormHelper at the - moment of submission. This metric is needed to check the assumption that - received and parsed message contains only one form at a a time. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - Number of passwords deleted when the user chooses to clear passwords via the - clear browsing data UI. - - - - - - Removed as of 06/2019. - - vasilii@chromium.org - - Number of passwords deleted when browsing data is cleared during rollback. - - - - - - Removed as of 08/2015. - - - When the user chooses to never remember passwords for a form, we remove all - previously saved credentials for that form. This is the count of those - credentials. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The password manager only shows those credentials that are considered the - best match for a particular form. This stat keep track of the credentials - that were not as good of a match and were suppressed. - - - - - - Removed as of 04/2020. - - achulkov@google.com - ioanap@chromium.org - - Result of the combined saving flow consisting of the potentially shown - onboarding dialog and the save infobar. Recorded when the user is prompted - to save their password. - - - - - - Removed as of 04/2020. - - achulkov@google.com - ioanap@chromium.org - - Result of the combined saving flow consisting of the shown onboarding dialog - and the save infobar. Recorded when the user is propmpted to save their - password only if the onboarding was actually shown. - - - - - - Removed as of 04/2020. - - achulkov@google.com - ioanap@chromium.org - - The current state of showing the password manager onboarding to the user. - Recorded on startup. - - - - - - Removed as of 04/2020. - - achulkov@google.com - ioanap@chromium.org - - Reason of dismissal of the password manager onboarding dialog. Recorded when - the user is propmpted to save their password and the dialog is shown. - - - - - vasilii@chromium.org - jdoerrie@chromium.org - - Indicates whether the user's OS password is blank or not at browser startup. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Breakdown of how other possible usernames are displayed. Recorded every time - we autofill a password form. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Logs the type of the suggestion in the password dropdown when selected. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - Logs the state of the password dropdown when it's shown. - - - - - Removed as of May 17 2017. Replaced by - PasswordProtection.RequestOutcome.ProtectedPasswordEntry. - - dvadym@chromium.org - chrome-safebrowsing-alerts@google.com - - A password reuse is an event when the user typed a string that is equal to a - saved password on another domain, and this saved password is called reused - password. - - This metric shows whether a password reuse happens on a page whose main - frame url matches CSD whitelist. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric shows how many saved credentials (num unique registry-controlled - domains) have password that's equal to the reused password. - - Before M63 this logged a "0" for sync-reuse. - - A "password reuse" is when the user typed a string that is equal - to a saved password on another domain or is equal to the sync password on a - non google-login domain. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric reports whether a password field had been detected on a page - when a password reuse happened. - - A "password reuse" is when the user typed a string that is equal - to a saved password on another domain or is equal to the sync password on a - non google-login domain. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric shows the length of the reused password. - - Change in M63: If multiple passwords are matched simultaneously, this logs - the length of the longest password. Also, before M63, a "0" was - logged for sync-reuse. - - A "password reuse" is when the user typed a string that is equal - to a saved password on another domain or is equal to the sync password on a - non google-login domain. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric shows how many credentials are stored in Password Manager when a - password reuse happened. This counts unique registry-controlled domains with - passwords saved. - - A "password reuse" is when the user typed a string that is equal - to a saved password on another domain or is equal to the sync password on a - non google-login domain. - - During M61/M62 this metric logged a "1" for every sync-reuse. It - was fixed in M63 such that it logs actual Password Manager credential count. - - - - - kolos@chromium.org - - Measures whether users save passwords with automatic prompt or manual - fallback. - - - - - kolos@chromium.org - battre@chromium.org - - PasswordScriptsFetcher's cache state when the fetcher is requested to return - script availability. - - - - - kolos@chromium.org - battre@chromium.org - - HTTP response code or network error code of fetching a list of available - password scripts. - - - - - kolos@chromium.org - battre@chromium.org - Result of parsing of a list of available password scripts. - - - - kolos@chromium.org - battre@chromium.org - - Response time for fetching a list of available password scripts. - - - - - dullweber@chromium.org - treib@chromium.org - mamir@chromium.org - - Records how often browsing data succeeds to delete account store passwords - from the Sync server. False is emitted in the rare situations when the - operation times out or the user disables Sync before the deletions are fully - propagated to the Sync server. True is emitted when the password deletion is - successfully propagated to the server. - - - - - vasilii@chromium.org - src/components/password_manager/OWNERS - - Success rate of initialization of password store. Recorded for every user - once on the Chrome profile startup. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Whether the passwords are syncing and, if not, then what's causing sync - failures. Recorded after the first sync attempt either succeeds or fails. - - - - - - Removed as of 05/2018. - - kolos@chromium.org - - Measures whether users update passwords with automatic prompt or manual - fallback. - - - - - koerber@google.com - - Records successful fills of prefilled username values known as placeholders - and unsuccessful fills that were blocked because the prefilled value was not - identified as a placeholder. Recorded once per PasswordAutofillAgent - instance, when attempting to fill a password form that contains a username - value which was prepopulated by the website. - - - - - - Removed 2020-04. - - vasilii@chromium.org - jdoerrie@chromium.org - - Why was the update password UI closed when a generated password caused a - conflict? - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Breakdown of cases where a password is submitted, but we don't even try and - save it. Recorded for every password form submit. - - - - - - Removed 01/2020. - - dvadym@chromium.org - vasilii@chromium.org - - Breakdown on trigger rate of providing a password form autofill entry based - on matching stored information using the public suffix list (PSL) for - possible matches. In addition, this metric also counts cases where a - existing federated entry was successfully matched via PSL. For example, this - includes cases where an existing federated credential for - https://example.com was used for https://subdomain.example.com. - - - - - - Removed 03/2019. - - engedy@chromium.org - - Records, for each password form seen by the password manager, whether the - PasswordStore responded quickly enough so that - PasswordManager.SuppressedAccount histogram samples could be computed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Recorded whenever the user interacts with reauthentication in order to - access the passwords in settings, or when such reauthentication is skipped - for a well-defined reason. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Collects the cause of the change in the Password Store login which causes a - call of a remove SQL statement on the compromised credentials table. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Collects the cause of why remove SQL statement is called on the compromised - credentials table. - - - - - - Removed as of 06/2020. - - vasilii@chromium.org - - Collects positive number of inaccessible passwords that were successfully - deleted when retrieving them from the database. Recorded for Mac users. - - - - - battre@chromium.org - jdoerrie@chromium.org - - HTTP response code of fetching a password requirements file. - - - - - battre@chromium.org - jdoerrie@chromium.org - - Network error code of fetching a password requirements file. - - - - - battre@chromium.org - jdoerrie@chromium.org - - Time until the lookup for a password requirements file completed (or was - aborted). - - - - - battre@chromium.org - jdoerrie@chromium.org - - Result of fetching requirements for password during password generation. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the type of password (e.g saved password, sync password, enterprise - password etc) reused by the user. This is logged when a password reuse - happens. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of enterprise password hashes that have been saved for - password reuse detection. This is logged during the initialization of - PasswordStore class. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of Gaia password hashes that have been saved for password - reuse detection. This is logged during the initialization of PasswordStore - class. - - - - - - Removed as of 03/2016. - - - Indicates whether the save password prompt disappeared in less than one - second. This most likely indicates that the prompt was dismissed - automatically, e.g. due to a page navigation, before the user was able to - respond to the infobar. - - - - - - Removed as of 03/2016. - - Indicates whether the save password prompt was displayed. - - - - - Removed as of 03/2016. - - - Breakdown of which response the user selected from the save password prompt. - - - - - - - vasilii@chromium.org - treib@chromium.org - mamir@chromium.org - Why was the save password UI (bubble or infobar) closed? - - - - ioanap@chromium.org - vasilii@chromium.org - - Why was the save password UI (bubble or infobar) closed? This is currently - recorded only for Android and only after the user has unblacklisted an - origin for saving from the accessory sheet. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Records user actions when Chrome offers to save a username on a page which - is considered to be a username first flow. Recorded on a successful - submission. - - - - - - Removed 03/2019. - - dvadym@chromium.org - miniailau@google.com - - Measures sending/not sending password forms to the browser process by - PasswordAutofillAgent::SendPasswordForms. - - - - - - Removed 06/2017 - - engedy@chromium.org - melandory@chromium.org - - Tracks the pair of initial values and pair of final values for the legacy - preference for controlling the Chrome Password Manager and the new - preference for controlling Smart Lock on Android. A single sample is - recorded after sync has merged last snapshot and finished initialization for - sync users, and on profile initialization for non-sync users. - - - - - - Removed 06/2017 - - engedy@chromium.org - melandory@chromium.org - - Tracks the pair of initial values for both for the legacy preference for - controlling the Chrome Password Manager and new preference for controlling - Smart Lock on Android. Sample is recorded on every profile initialization - before reconciliation logic is taken place, e.g. when user logs in to - browser, on a startup of a browser. - - - - - - Removed as of M78. PasswordManager.ProvisionalSaveFailure contains strictly - more information. - - jdoerrie@chromium.org - - This metric is recorded every time Chrome detects a password form - submission. The credential might be proposed to be saved, or it might be - blocked. It is blocked if the previously detected password form submission - was successful, and the current submission is from a URL with the same - origin, but a different and insecure scheme. That is, if the previously - provisionally saved credential is for https://example.com, a new credential - for http://example.com would be blocked. More details can be found in the - doc associated with http://crbug.com/571580. - - - - - - Removed 06/2019 - - vasilii@chromium.org - - Records if the user still has to click through the first run experience to - benefit from auto sign-in behavior. Recorded on every start-up. - - - - - - Removed 08/2018 because the decision this should have helped with is now - moot. See https://crbug.com/871509#c3. - - dvadym@chromium.org - - Records results of the new and the old algorithm for detecting whether to - show a password prompt to the user. Recorded on each password form - successful submission. - - - - - - Removed 08/2020. - - vasilii@chromium.org - fhorschig@chromium.org - - Recorded when the "Show all saved passwords" fallback is accepted. - - - - - - Removed 08/2020. - - vasilii@chromium.org - fhorschig@chromium.org - - Recorded when the "Show all saved passwords" fallback is shown. - - - - - - Removed 05/2018 because the feature never launched. - - estark@chromium.org - - Recorded (at most once per main-frame navigation) when a password form shows - a warning that the form is not secure. - - - - - - Removed as of 06/19. - - vasilii@chromium.org - - User action on the Chrome Sync promo that appears in the password bubble. - The promo offers to sign in to Chrome. - - - - - - Removed as of 12/16/16. New statistic is - PasswordManager.SignInPromoCountTil*. - - vasilii@chromium.org - - The number of times the Sign In promo in the password bubble was shown - before user clicked on it. - - - - - - Removed as of 06/19. - - vasilii@chromium.org - - The number of times the Sign In promo in the password bubble was shown - before user clicked on "No thanks". - - - - - - Removed as of 06/19. - - vasilii@chromium.org - - The number of times the Sign In promo in the password bubble was shown - before user clicked on "Sign in". - - - - - - Removed as of 06/19. - - vasilii@chromium.org - - The number of times the Sign In promo in the password bubble was implcitly - dismissed. Recorded each time the promo is implicitly dismissed. - - - - - cfroussios@chromium.org - jdoerrie@chromium.org - - Describes the result of decrypting a password value from the LoginDatabase. - - - - - - Removed as of 14 September 2017, due to being no longer useful. - - xunlu@chromium.org - - Whether password manager stored passwords imported from CSV file - successfully. - - - - - - Removed as of October 2019 - - cfroussios@chromium.org - dvadym@chromium.org - - The time (ms) it takes for the synchronous part of the AddLogin on the - PasswordStore to complete. - - - - - - Removed as of October 2019 - - cfroussios@chromium.org - dvadym@chromium.org - - The time (ms) it takes for the synchronous part of the GetLogin on the - PasswordStore to complete. - - - - - - Removed as of October 2019 - - cfroussios@chromium.org - dvadym@chromium.org - - The time (ms) it takes for the synchronous part of the GetLogins on the - PasswordStore to complete. - - - - - - Removed as of October 2019 - - cfroussios@chromium.org - dvadym@chromium.org - - The time (ms) it takes for the synchronous part of the RemoveLogin on the - PasswordStore to complete. - - - - - - Removed as of October 2019 - - cfroussios@chromium.org - dvadym@chromium.org - - The time (ms) it takes for the synchronous part of the UpdateLogin on the - PasswordStore to complete. - - - - - - Removed since August 28, 2018, due to removing the corresponding feature. - - - When the user logs in with their sync credential, PasswordManager checks if - there are any outdated copies of it in the password store, in order to purge - them. This histogram records whether password store data are ready during - this check. - - - - - mamir@chromium.org - treib@chromium.org - - Which of the password manager's stores (the profile-scoped one and/or the - account-scoped one) were used within the last 28 days for filling passwords. - Recorded whenever a password form is successfully submitted. This should - typically only be used with "Count unique clients". - - - - - mamir@chromium.org - treib@chromium.org - - Which of the password manager's stores (the profile-scoped one and/or the - account-scoped one) were used within the last 7 days for filling passwords. - Recorded whenever a password form is successfully submitted. This should - typically only be used with "Count unique clients". - - - - - - Removed 06/2019. - - dvadym@chromium.org - - Indicates whether submitting a password login form changes the registry - controlled domain of the main frame. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Records a frame type (eg. main frame, iframe with the same url as the main - frame) of a submitted password form. - - - - - jdoerrie@chromium.org - kolos@chromium.org - - The type (e.g. signup, login, change password) of all submitted password - forms. This is logged on form submission, but doesn't require that the - password manager saves. - - - - - estark@chromium.org - - The type (e.g. signup, login, change password) of all submitted password - forms on non-secure pages. This is logged on form submission, but doesn't - require that the password manager saves. - - - - - nepper@chromium.org - battre@chromium.org - kolos@chromium.org - - For a successful login, whether the origin is HTTPS or HTTP. A succesful - login is detected by local heuristics. The heuristics can misclassify - whether a login succeeded, so this is an approximation. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - The type of event that the Password Manager used for detecting a password - form submission. Recorded for each successful password form submission. - - - - - - Removed 07/2019. - - vasilii@chromium.org - - The type of password suggestion on iOS displayed in the keyboard accessory. - Recorded for each tap on the suggestion. - - - - - - Removed 07/2019. - - vasilii@chromium.org - - The type of password suggestions on iOS displayed in the keyboard accessory. - Recorded each time the password suggestion is shown. - - - - - - Removed 03/2019. - - engedy@chromium.org - - Records, for each password form seen by the password manager, whether there - were `suppressed` credentials, meaning stored credentials that were not - filled because they were for an origin that was similar to, but not exactly - (or PSL) matching the origin of the observed form (see the suffix - description for the possible classes of such near-matches). If there were - such credentials, the histogram also records whether the username and - password of such suppressed credentials matched those submitted. - - - - - - Password manager no longer supports this behavior and the code that could - generate values in this histogram is gone as of M74. - - battre@chromium.org - vasilii@chromium.org - - This histogram is reported for those forms on accounts.google.com, on which - Chrome is forced by Finch/flags during autofilling to remove sync - credentials from password store results. It reports true if sync credentials - were indeed removed from the store results, and false if there were no sync - credentials in the results to begin with. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - chrome-password-manager-team@google.com - - Information about the user's current sync status crossed with whether their - synced password is saved. - - - - - mamir@chromium.org - mastiz@chromium.org - - This metric reports the error observed when trying to read the Sync metadata - from the password store during the start of Password sync. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - This metric reports a type of a sync password hash change event. Recorded - when a sync password hash is saved or cleared. - - - - - jdoerrie@chromium.org - battre@chromium.org - - The time between receiving saved credentials from the password store and - predictions from the Autofill server. Recorded each time when predictions - for a form are received. - - - - - - Removed as of 2019/07. Password exporting has been rolled out. - - battre@chromium.org - cfroussios@chromium.org - ioanap@chromium.org - - The time it takes to fetch and serialise the passwords for export. - - - - - - Removed as of 11/11/14. New statistic is - PasswordManager.TimesPasswordUsed.AutoGenerated. - - - The number of times each generated password has been used to log in. - Recorded by iterating over stored passwords once per run. This information - is persisted and synced. - - - - - battre@chromium.org - jdoerrie@chromium.org - - The number of times each saved password from the profile-scoped storage has - been used to log in. Split by whether created by the user or generated by - Chrome, and further by whether the user used sync with custom passphrase or - not. Recorded by iterating over stored passwords once per run. This - information is persisted and synced. - - - - - - Removed in M76 in favor of PasswordManager.TotalAccountsHiRes.ByType. - - battre@chromium.org - vasilii@chromium.org - - The number of accounts stored in the password manager (across all sites), - split by whether created by the user or generated by Chrome, and further by - whether the user used sync with custom passphrase or not. - - - - - battre@chromium.org - vasilii@chromium.org - - The number of accounts stored in the password manager's profile-scoped store - (across all sites), split by whether created by the user or generated by - Chrome, and further by whether the user used sync with custom passphrase or - not. - - - - - battre@chromium.org - vasilii@chromium.org - - The number of accounts stored in the password manager's profile-scoped store - (across all sites) for origins with the scheme (e.g., HTTP, HTTPS, FTP) as - given in the histogram suffix. For each scheme, the count is recorded once - per browser start-up. (In case of multiple profiles, the counts are for the - profile that first has a WebContents created.) - - - - - jdoerrie@chromium.org - fhorschig@chromium.org - - The index of a selected credential in the Touch To Fill sheet. Only recorded - when the sheet showed at least two entries. - - - - - jdoerrie@chromium.org - fhorschig@chromium.org - - The reason why a user dismissed the Touch To Fill sheet. Recorded once for - each dismissal. - - - - - jdoerrie@chromium.org - fhorschig@chromium.org - The number of credentials shown in the Touch To Fill sheet. - - - - jdoerrie@chromium.org - fhorschig@chromium.org - - The action a user took when interacting with the Touch To Fill sheet. - - - - - vasilii@chromium.org - - Why was the password manager's UI (bubble or infobar) closed? Save and - update UI are tracked separately. - - - - - - Removed 03/2018 in favor of PasswordManager.UpdateUIDismissalReason. - - dvadym@chromium.org - vasilii@chromium.org - - The password submission event happened when the user changes their password - on a website, say foo.com or types new password on a sign-in form for saved - credential (which might mean that the password was changed in a different - browser). The later case called password overriding. This histogram measures - whether the user has any passwords saved in the Chrome password manager for - foo.com or the password was overriden on sign-in form, and what action the - user performed on the offered bubble. It's recorded when the bubble is - closed. - - - - - vasilii@chromium.org - Why was the update password UI (bubble or infobar) closed? - - - - kolos@chromium.org - - Chrome saves locally all fields a user typed on a sign-up form. If Chrome - saved an incorrect username and the user changes the username on a sign-in - form to a value of another field from the sign-up form, then Chrome uploads - a username correction vote which points to the correct username field. This - histogram measures how many correction votes are uploaded. - - - - - kolos@chromium.org - - Measures what method was used for username field detection in the renderer - code. The metric may be recorded several times for page visit because it is - recorded at every PasswordForm creation. If a site changes HTML attributes - of fields or server-side predictions is received, different values can be - recorded for the same form. If an outcome of HTML classifier or a - server-side prediction coincides with the outcome of base heuristic, the - metric points to base heuristic method. - - - - - - Removed 07/2016 because this information is no longer stored in - PasswordForm. See also http://crbug.com/413020. - - xunlu@chromium.org - gcasto@chromium.org - - Whether saved password for HTTPS site had a valid SSL cert when the password - was saved. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - A JSON file with change password form url is fetched from gstatic. This - metric logs if the response arrived in time and if the url override was - available for a given origin. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Logs the error code when the fetch to the gstatic file failed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Logs the response code when the fetch to the gstatic file failed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - - Logs if the request for the gstatic file succeeded, failed or if the - response was malformed. - - - - - jdoerrie@chromium.org - vasilii@chromium.org - Logs the loading time for the gstatic file request. - - - - - Removed since caching is not the root cause of time out issue. - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes for PasswordProtectionService to cache a verdict. - - - - - - Removed since 03/2020 due to no usage. - - vakh@chromium.org - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how a user interacts with the chrome://settings page that displays - the password protection warning. Logged when the page is shown and when the - user chooses to change their password on the page. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes to extract the DOM features of a login page before sending - a PasswordProtectionRequest. Logged on every password reuse PhishGuard ping. - - - - - - Removed in M78. The DOM features always parsed successfully, so this - histogram wasn't useful. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether the DOM features were parsed successfully when returned from - the renderer. This is logged on every PhishGuard ping. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of Gaia password reuse warnings shown to user before user changes - their password. Logged when we see that user has changed their Gaia - password. The number of reuses will be reset to zero if current session of - browser process ends. This count doesn't include the reuses that user marked - as legitimate. - - - - - - Removed since caching is not the root cause of time out issue. - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes for PasswordProtectionService to get a cached verdict. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how a user interacts with the password protection interstitial - (a.k.a chrome://reset-password page). Logged when the interstitial is shown - and when the user chooses to change their password. - - - - - - Removed 2019-01 due to lack of usage. https://crbug.com/915894 - - chrome-safebrowsing-alerts@google.com - - When user manually navigates to chrome://reset-password page, records how - this user interacts with this page. Logged when the interstitial is shown - and when the user chooses to change their password. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the type of strings shown to the user on chrome://reset-password - page. Logged when the interstitial in initialized. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how a user interacts with the password protection modal warning - dialog. Logged when the dialog is shown and when the user chooses to change - their password, ignore warning, or navigate away. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the interval between when the password protection modal warning - dialog is constructed and when the dialog is destructed. The dialog can be - destructed when the user takes action or the web content is destroyed. - - - - - - Removed since 07/2018 due to lack of usage. - - chrome-safebrowsing-alerts@google.com - - Number of password protection verdicts stored in content settings of a - profile before this profile is destructed. - - - - - - Removed in M71+. - - chrome-safebrowsing-alerts@google.com - - We start changing the way of caching password protection verdicts in M69. - This histogram counts the number of verdicts migrated to the new way during - initialization of PasswordProtectionService. It helps determine when we can - remove migration code. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how a user interacts with page info bubble that displays the - password protection warning. Logged when such page info bubble is shown and - when the user chooses to change their password, ignore warning, or mark site - as legitimate via buttons on the page info bubble. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Reports the zoom factor for a login page, when the protected password is - entered. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the outcome of the password alert mode, indicating if password alert - warning is shown successfully or if it is skipped for some reason. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Response or error codes for PasswordProtectionRequest. Logged after chrome - receives response of PasswordProtectionRequest from Safe Browsing service. - - - - - - Removed since May 12 2017. Replaced by - PasswordProtection.Verdict.ProtectedPasswordEntry. - - chrome-safebrowsing-alerts@google.com - - Verdict types returned by Safe Browsing server for password reuse events. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - When password protection service detects a reuse of Chrome sync password, - record the type of Chrome sync account on which the reuse happens (e.g. - @gmail.com, @googlemail.com, or other dasher account). - - - - - - Removed September 18 2018. This wasn't being used, and can be recreated on - the backend if needed. - - chrome-safebrowsing-alerts@google.com - - The referrer chain size of a password protection request. This is recorded - when Chrome receives a verdict for this request. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The result from the renderer after DOM feature extraction. This is collected - when Chrome password protection detects password reuse, or (for SBER users), - when the user focuses on a password field. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes for PasswordProtectionService request. It is not recorded - for requests that were canceled. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the outcome of the password protection request, indicating if - request is sent out successfully or if it is skipped or canceled for some - reason. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs when an event where users reuse their password or focus on a password - field is sent as a sample ping when the URL in the allowlist to Safe - Browsing. Events only happen 1% of the time when URLs match the allowlist. - - - - - - Removed since May 12 2017. Replaced by - PasswordProtection.Verdict.PasswordFieldOnFocus. - - chrome-safebrowsing-alerts@google.com - - Verdict types returned by Safe Browsing server for unfamiliar login pages. - - - - - - Removed since 07/2018 due to lack of usage. - - chrome-safebrowsing-alerts@google.com - - Whether the user has clicked through the Safe Browsing interstitial before - the password protection ping is triggered on the same page. Logged right - before password protection ping is sent. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Verdict types returned by Safe Browsing server for a password protection - request. Request can be triggered when user focuses on a password field or - enters a protected password (syncing, signed-in, or saved). - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes to extract the visual features of a login page before - sending a PasswordProtectionRequest. Logged every time visual features are - extracted (when an SBER user sends an On Focus ping). - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when CanMakePayment was not called by the - merchant. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the merchant used the CanMakePayment method during a Payment - Request. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - The effect of the CanMakePayment return value on whether Show was called. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when CanMakePayment was called by the - merchant and returned false. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when CanMakePayment was called by the - merchant and returned true. - - - - - danyao@chromium.org - web-payments-team@google.com - - Counts the number of Payment Requests (PR) that go through each checkout - step. A single PR may be counted in multiple buckets depending on its final - status. e.g. A completed PR will be counted in all of the following buckets - 1- Initiated, 2- show() called 3- Payment request triggered 4- Payment - handler invoked, 5- Completed. - - - - - danyao@chromium.org - web-payments-team@google.com - The reason that lead to an abort of the Payment Request. - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - When the merchant has processed the user's Payment Request. - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - When a Payment Request gets initiated by the user. - - - - danyao@chromium.org - web-payments-team@google.com - - The reason that leads to the Payment Request not being shown to the user. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - When the user clicks the "pay" button in the Payment Request UI. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - When the browser retrieves the instrument details from the payment app to - complete a purchase. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - When the Payment Request UI gets shown after initialization. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - When the Payment Request UI gets skipped to go directly to the payment app. - - - - - danyao@chromium.org - web-payments-team@google.com - - A bitfield representing the different events that happened during the - Payment Request. - - - - - sahel@chromium.org - web-payments-team@google.com - - Whether a journey logger has recorded an events bit field or not. - - - - - sahel@chromium.org - web-payments-team@google.com - - When a journey logger attempts to record multiple events bit fields. - - - - - sahel@chromium.org - web-payments-team@google.com - - A bitfield representing different missing fields of the contact section in - payment sheet. This only gets recorded when no complete contact profile is - available. In case of multiple partially complete profiles, this is only - recorded for the most complete one which is also the first profile in the - suggestion list. - - - - - sahel@chromium.org - web-payments-team@google.com - - A bitfield representing different missing fields of the payment info section - in the payment sheet. This only gets recorded when no complete payment - instrument is available (SW based instruments are always considered as - complete). In case of multiple partially complete cards this is only - recorded for the first card in the suggestion list. - - - - - sahel@chromium.org - web-payments-team@google.com - - A bitfield representing different missing fields of the shipping section in - the payment sheet. This only gets recorded when no complete shipping profile - is available. In case of multiple partially complete profiles, this is only - recorded for the most complete one which is also the first profile in the - suggestion list. - - - - - - Removed 09/2020. Made decision in issue 1128111 to remove unused payment - sheet histograms. - - danyao@chromium.org - web-payments-team@google.com - - The number of times the user added an entry during a Payment Request. - - - - - - Removed 09/2020. Made decision in issue 1128111 to remove unused payment - sheet histograms. - - danyao@chromium.org - web-payments-team@google.com - - The number of times the user changed an entry during a Payment Request. - - - - - - Removed 09/2020. Made decision in issue 1128111 to remove unused payment - sheet histograms. - - danyao@chromium.org - web-payments-team@google.com - - The number of times the user edited an entry during a Payment Request. - - - - - danyao@chromium.org - web-payments-team@google.com - - The number of suggestions shown to the user during a payment request. - - - - - sahel@chromium.org - web-payments-team@google.com - - True when chrome crawls to refetch the missing icon of an already installed - payment app. - - - - - - M62+ Included in PaymentRequest.Events - - danyao@chromium.org - - Tracks what user information is required by merchants to complete a Payment - Request. - - - - - danyao@chromium.org - web-payments-team@google.com - - Records the size of Credential ID for secure-payment-confirmation method in - bytes. - - - - - - M62+ Included in PaymentRequest.Events - - danyao@chromium.org - - Tracks what payment method was used to complete a transaction in Payment - Request. - - - - - sahel@chromium.org - web-payments-team@google.com - True when a service worker times out 5 mins after request. - - - - sahel@chromium.org - web-payments-team@google.com - - Records the time between a payment request .show() and its completion. - - - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the time between a payment request .show() and its completion when - payment sheet is shown. - - - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the time between a payment request .show() and its completion when - payment sheet is skipped. - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the time between a payment request .show() and its termination by - any factors other than the user (e.g. merchant). - - - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the time between a payment request .show() and its termination by - user. - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the transaction amounts completed using payment request API after - converting to USD. - - - - - sahel@chromium.org - web-payments-team@google.com - - Records the transaction amounts triggered using payment request API after - converting to USD. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when the user did not have a complete - suggestion offered for each requested information. - - - - - - Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July - 19th 2017. - - danyao@chromium.org - - Whether the flow was completed when the user did not have a a form of - payment on file when the Payment Request was shown. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when the user did not have suggestions - offered for each requested information. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - - Whether the flow was completed when the user had at least one complete - suggestion offered for each requested information. - - - - - - Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July - 19th 2017. - - danyao@chromium.org - - Whether the flow was completed when the user had a form of payment on file - when the Payment Request was shown. - - - - - - M62+ Part of PaymentRequest.Events - - danyao@chromium.org - web-payments-team@google.com - - Whether the flow was completed when the user had suggestions offered for - each requested information. - - - - - hnakashima@chromium.org - - Tracks user actions in the PDF viewer. Logged when the document is opened - and when one of the relevant user actions is taken, such as opening the - bookmarks bar or setting the zoom mode to fit-to-page. The enum values that - are named "First" are logged only once per document, so that we - can measure in what percentage of documents a given action was performed at - least once. - - - - - - Removed in February 2020. - - hnakashima@chromium.org - - Tracks documents opened in the PDF viewer that displayed one or more pages - with the given annotation type. - - - - - - Removed in March 2020. - - thestig@chromium.org - - Tracks which features are used by documents opened in the PDF viewer, logged - when the document finishes loading. - - - - - - Removed in July 2019. - - thestig@chromium.org - The size of PDF documents opened in the PDF viewer. - - - - rharrison@chromium.org - thestig@chromium.org - - Tracks what types of forms are present in PDF document, logged when the - document finishes loading. - - - - - hnakashima@chromium.org - thestig@chromium.org - - Measures if PDFs opened in the PDF viewer have attachments. This is logged - whenever a document is opened in the PDF viewer. - - - - - - Removed in June 2019. - - npm@chromium.org - - Measures if PDFs opened in the PDF viewer require fonts to be substituted. - This is logged whenever a document is opened in the PDF viewer. - - - - - - Removed in July 2019. - - hnakashima@chromium.org - - Measures if PDFs opened in the PDF viewer are Linearized PDFs. This is - logged whenever a document is opened in the PDF viewer. - - - - - dmazzoni@chromium.org - thestig@chromium.org - - Tracks documents opened in the PDF viewer that are Tagged PDFs. - - - - - thestig@chromium.org - ankk@microsoft.com - mohitb@microsoft.com - virens@microsoft.com - - Records the number of overlapping link and highlight annotations in a PDF - page. This is logged once per page whenever accessibility tree creation is - triggered for that page. It will not be logged on render or scroll - operations. - - - - - kmoon@chromium.org - thestig@chromium.org - - Tracks what happens when Chrome tries to load a PDF. This metric tracks all - cases, but is focused on measuring failed PDF embeds, which occur if the - user is on Android, or if PDF plugin is disabled. - - - - - hnakashima@chromium.org - thestig@chromium.org - - Tracks the number of pages in PDF documents opened in the PDF viewer. - - - - - dhoss@chromium.org - thestig@chromium.org - Tracks versions of documents opened in the PDF viewer. - - - - - Removed as of 5/2019. - - raymes@chromium.org - - Counts various actions related to the Pepper Broker interface. - - - - - jbauman@chromium.org - - True if a non-flash Pepper Graphics3D context has a share group. - - - - - bbudge@chromium.org - raymes@chromium.org - - The number of out-of-process plugin processes that have loaded a particular - PPB interface version. - - - - - raymes@chromium.org - rsleevi@chromium.org - - Whether a Pepper TCP connect attempt comes from a plugin in a secure or an - insecure origin. - - - - - raymes@chromium.org - rsleevi@chromium.org - - Whether a Pepper UDP bind attempt comes from a plugin in a secure or an - insecure origin. - - - - - - Removed as of 8/2017. - - raymes@chromium.org - - Whether a Pepper media stream request (mic/cam access) comes from a plugin - in a secure or an insecure origin. - - - - - - Removed as of June 2019. - - maxlg@chromium.org - - The count of possible incoming values to the endMark parameter in - performance.measure(). The purpose is to investigate how much the change of - API of User Timing L3 will impact the real world use cases. This histogram - was deprecated in 05/2018 and re-reenabled in 11/2018. The re-enabled - histogram adds the counting of undefined, null, number and unprovided, to - the original navigation-timing names, object and string. This value is - recorded at each call to performance.measure(). - - - - - - Removed as of June 2019. - - maxlg@chromium.org - - The count of possible incoming values to the startMark parameter in - performance.measure(). The purpose is to investigate how much the change of - API of User Timing L3 will impact the real world use cases. This histogram - was deprecated in 05/2018 and re-reenabled in 11/2018. The re-enabled - histogram adds the counting of undefined, null, number and unprovided, to - the original navigation-timing names, object and string. This value is - recorded at each call to performance.measure(). - - - - - jds@chromium.org - src/chrome/browser/performance_hints/OWNERS - - Records the result of querying PerformanceHintsObserver for a URL-specific - performance hint. This enables tracking how often the - OptimizationGuideDecider provides a hint in time for a HintForURL request. - - - - - jds@chromium.org - src/chrome/browser/performance_hints/OWNERS - - Records the PerformanceClass determined for a given URL. This value - represents the expected loading performance for the URL. This is recorded - before any overrides are performed by the PerformanceHintsObserver. - - - - - jds@chromium.org - src/chrome/browser/performance_hints/OWNERS - - Records the result of a hint lookup in a single source (e.g. link hints of - the current page, the page's OptimizationMetadata, etc). See the - PerformanceHintsSource suffix for name completions. All source suffix - histograms should have the same total count. - - - - - bokan@chromium.org - kouhei@chromium.org - platform-architecture-dev@chromium.org - - Tracks the total number of agents hosted by the browser by time. An entry in - bucket N corresponds to N agents being hosted across all live renderer - process for 1 second. Recorded on state changes and every 5 minutes. - - - - - bokan@chromium.org - kouhei@chromium.org - platform-architecture-dev@chromium.org - - Tracks the number of agents hosted per renderer by time. An entry in bucket - N corresponds to N agents being hosted by a renderer process for 1 second. - Recorded on state changes and every 5 minutes. - - - - - bokan@chromium.org - kouhei@chromium.org - platform-architecture-dev@chromium.org - - Tracks the number of unique agents hosted by the browser by time. An entry - in bucket N corresponds to N unique agents being hosted across all live - renderer process for 1 second. Unique means that the agent count would - remain the same if they were in one process (i.e. they have different - protocol+site). Recorded on state changes and every 5 minutes. - - - - - - Removed 2020-01-06 as this was only added for a brief exploration. - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the plurality and visibility state of all BrowsingInstances over - time. An entry in each bucket corresponds to a page in a BrowsingInstance - being in that state for one second. This is effectively "page - seconds" of time spent in each state. Recorded on state changes and - every 5 minutes. - - - - - - Removed 2020-01-06 as this was only added for a brief exploration. - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the plurality and visibility state of all BrowsingInstances over - time. An entry in each bucket corresponds to a BrowsingInstance being in - that state for one second. Recorded on state changes and every 5 minutes. - - - - - - Removed 2019-06-04 in favour of variant 2. - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the types of frames that are being hosted by a process over its - entire lifetime. An entry in the - "AllFramesHaveDistinctSiteInstances" means that the process only - ever hosted frames with distinct site instances over its entire lifetime. - Recorded on state changes and every 5 minutes. - - - - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the types of frames that are being hosted by a process over its - entire lifetime. An entry in the - "AllFramesHaveDistinctSiteInstances" means that the process only - ever hosted frames with distinct site instances over its entire lifetime. - Recorded on state changes and every 5 minutes. - - - - - - Removed 2019-06-04 in favour of variant 2. - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the types of frames that are being hosted by a process, aggregated - over time. Each entry in each bucket corresponds to a process being in that - state for one second. Recorded on state changes and every 5 minutes. - - - - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the types of frames that are being hosted by a process, aggregated - over time. Each entry in each bucket corresponds to a process being in that - state for one second. Recorded on state changes and every 5 minutes. - - - - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the number of frames hosted per renderer by time. An entry in bucket - N corresponds to N frames being hosted by a renderer process for 1 second. - Recorded on state changes and every 5 minutes. - - - - - chrisha@chromium.org - catan-team@chromium.org - - Tracks the number of site instances hosted per renderer by time. An entry in - bucket N corresponds to N site instances being hosted by a renderer process - for 1 second. Recorded on state changes and every 5 minutes. - - - - - pmonette@chromium.org - catan-team@chromium.org - - Records a boolean indicating if a worker's client frame node could be found - when trying to connect the worker to a client frame, given its ID. This is - supposed to be always true if the performance manager has perfect coverage - of WebContents objects. - - - - - oysteine@chromium.org - - Average CPU utilization of a process, read out at each two-minute interval. - The utilization is in the 0-100% range per CPU, which is then summed up. - I.e. a quadcore system fully loaded would read as 400%. - - - - - etienneb@chromium.org - oysteine@chromium.org - - Average disk utilization of a process, recorded at every two-minute - interval. The amount of data transferred (Total I/O bytes per second) for a - given process. - - - - - lgrey@chromium.org - markchang@chromium.org - - (Mac only) A synthetic power use estimate, as displayed in macOS Activity - Monitor and the battery menu. This incorporates CPU utilization, idle - wakeups, IO, and task QoS level using per-machine-model weights. Divide by - 100 to match Activity Monitor's scale. Recorded every two minutes. - - - - - oysteine@chromium.org - - The number of times a process has continuously stayed above a certain - threshold of CPU utilization over a certain time period (currently set to - two minutes). - - - - - lgrey@chromium.org - markchang@chromium.org - - The average CPU idle wakeups per second, sampled every two minutes. - - - - - lgrey@chromium.org - markchang@chromium.org - - (Mac only) The average package exit idle wakeups per second, sampled every - two minutes. This is a subset of wakeups that indicate that the processor - complex was taken out of low-power state. For more info, see the - powermetrics man page on macOS. - - - - - - Expired on 2019-07-01. - - sebmarchand@chromium.org - - Average percentage of time during which the disk has been idle, logged at - regular intervals. If the system has multiple disks then this is the average - value for all of them. Windows only. - - - - - - Expired on 2019-07-01. - - sebmarchand@chromium.org - - The amount of free physical memory available, logged at regular intervals. - Windows only. - - - - - nator@chromium.org - rayankans@chromium.org - - Records the number of `periodicsync` events which were fired in a batch. A - batch is defined as the set of `periodicsync` events dispatched at the same - time by the BackgroundSyncManager. Periodic syncs usually run in a batch. - - - - - nator@chromium.org - rayankans@chromium.org - - Records whether the fired `periodicsync` events upon completion orginated - from a background wakeup task or the foreground. - - - - - nator@chromium.org - rayankans@chromium.org - - Time taken to execute a batch of periodicsync events. A batch is defined as - the set of `periodicsync` events dispatched at the same time by the - BackgroundSyncManager. Periodic syncs often run in a batch. - - - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks whether a permission was granted, rejected, etc. The suffix of the - histogram indicates which particular permission. - - - - - - Removed on 2020-06-19 as most permissions are no longer exposed to insecure - origins to begin with, and even those few that are recorded no useful data - any longer. - - dominickn@chromium.org - engedy@chromium.org - hkamila@chromium.org - mlamouri@chromium.org - - Tracks whether a permission was granted, rejected, etc on an insecure - origin. The suffix of the histogram indicates which particular permission. - - - - - - Removed on 2020-06-19 as most permissions are no longer exposed to insecure - origins to begin with, and even those few that are recorded no useful data - any longer. - - dominickn@chromium.org - engedy@chromium.org - hkamila@chromium.org - mlamouri@chromium.org - - Tracks whether a permission was granted, rejected, etc on a secure origin. - The suffix of the histogram indicates which particular permission. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Tracks the action that a user had taken per permission prompt UI - disposition. Suffixed by the UI disposition that the prompt used. Recorded - when a permission prompt has been resolved. - - - - - dominickn@chromium.org - kcarattini@chromium.org - - For every permission request that would show a prompt to the user, this - metric tracks whether the request is suppressed by embargo (and the source - of that embargo), or whether there is no embargo and the prompt is shown. - This is the proportion of permission prompts that the user would have seen - that have been blocked due to embargo. - - If the (origin, permission) pair was previously placed under embargo, no - prompt is displayed and the reason for embargo is recorded. Otherwise, the - prompt is shown and a no embargo reason is recorded. - - - - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks the reason that an (origin, permission) pair has been placed under - embargo (blocked from making requests for that permission for a period of - time). This is triggered when a permission is placed under embargo for - blacklisting (once Safe Browsing has returned a result), when a permission - prompt has been shown and it is placed under embargo for repeated - dismissals, or when a permission prompt is shown and not embargoed. - - - - - - Permission blacklisting was removed in M67. - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks the response (if received) from Safe Browsing when the API blacklist - is queried for an (origin, permission) pair. The response could be that the - origin was blacklisted, not blacklisted, or Safe Browsing timed out before a - response was received. - - - - - - Permission blacklisting was removed in M67. - - dominickn@chromium.org - kcarattini@chromium.org - - Records the elapsed time between the client sending a request to Safe - Browsing and receiving a result, or the maximum wait time is exceeded and - Safe Browsing is deemed to have timed out. - - - - - timloh@chromium.org - - Battery percentage when a geolocation permission prompt was accepted on - Android. - - - - - timloh@chromium.org - - Battery percentage when a location settings dialog was accepted. - - - - - timloh@chromium.org - - Battery percentage when a geolocation permission prompt was denied on - Android. - - - - - timloh@chromium.org - - Battery percentage when a location settings dialog was denied. - - - - - timloh@chromium.org - - Battery percentage when a geolocation permission prompt was dismissed on - Android. - - - - - bsep@chromium.org - engedy@chromium.org - olesiamarukhno@google.com - - Records how long it takes for the user to click on the permission chip after - it was shown. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Whenever a notification permission prompt is to be displayed, crowd deny - might trigger based on site reputation which will result in a quiet - permission prompt UI to be used. Whenever this happens, there is a small - chance that the normal UI will still be used. This records, when a quiet UI - is supposed to be shown, whether it has been randomly selected into the - hold-back group. In this case the normal UI will be displayed unless - overriden by the user Prefences. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records, each time a notification permission prompt is about to be shown, - the NotificationUxQuality result for the requesting origin. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records, each time a notification permission prompt is about to be shown, - the whether there is preload data that indicates the origin being on a - warning list. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records, each time a Safe Browsing request is made in response to a website - requesting the notification permission, how long that Safe Browsing request - took. This also includes all delays introduced by thread hopping. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records, each time a Safe Browsing request is made in response to a website - requesting the notification permission, the Safe Browsing verdict regarding - the notification prompt experience on that site. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks the engagement score for sites where permission prompts are accepted. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks the engagement score for sites where permission prompts are denied. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks the engagement score for sites where permission prompts are - dismissed. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks the engagement score for sites where permission prompts are ignored. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Recorded when the "Chrome needs permission..." infobar is - resolved. Records the resulting action that was taken. Suffixed by - `PermissionTypes` to provide information per permission type. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Recorded when the "Chrome needs permission..." infobar might be - displayed to the user because a site already has the permission but Chrome - does not. Records whether the infobar should be displayed or not. Ignores - situations when the infobar cannot be displayed (for example because there - is no appropriate web contents) as in those cases no decision is actually - made. Suffixed by `PermissionTypes` to provide information per permission - type. - - - - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks the permission bubbles (merged and non-merged) that are accepted. - Merged bubbles are considered accepted if all permissions are allowed. - - - - - - Persist toggle experiments ran from M56 to M59. - - dominickn@chromium.org - kcarattini@chromium.org - - For each granted permission prompt displayed with a persistence toggle - (remember my decision), records whether the persistence toggle was enabled - (persist) or not enabled (don't persist). - - - - - - Replaced by Permissions.Prompt.Accepted.PriorDismissCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt accept, records the - total number of prompt dismissal events for this origin since the last time - the user cleared their history or site data and prior to the accept. The - suffix of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt accept, records the - total number of prompt dismissal events for this origin since the last time - the user explicitly set the permission state or cleared history / site data - and prior to the accept. The suffix of the histogram indicates which - particular permission. - - - - - - Replaced by Permissions.Prompt.Accepted.PriorIgnoreCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt accept, records the - total number of prompt ignore events for this origin since the last time the - user cleared their history or site data and prior to the accept. The suffix - of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt accept, records the - total number of prompt ignore events for this origin since the last time the - user explicitly set the permission state or cleared history / site data and - prior to the accept. The suffix of the histogram indicates which particular - permission. - - - - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks the permission bubbles (merged and non-merged) that are denied. - Merged bubbles are considered denied if any permission is denied. - - - - - - Persist toggle experiments ran from M56 to M59. - - dominickn@chromium.org - kcarattini@chromium.org - - For each denied permission prompt displayed with a persistence toggle - (remember my decision), records whether the persistence toggle was enabled - (persist) or not enabled (don't persist). - - - - - - Replaced by Permissions.Prompt.Denied.PriorDismissCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt deny, records the - total number of prompt dismissal events for this origin since the last time - the user cleared their history or site data and prior to the accept. The - suffix of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt deny, records the - total number of prompt dismissal events for this origin since the last time - the user explicitly set the permission state or cleared history / site data - and prior to the accept. The suffix of the histogram indicates which - particular permission. - - - - - - Replaced by Permissions.Prompt.Denied.PriorIgnoreCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt deny, records the - total number of prompt ignore events for this origin since the last time the - user cleared their history or site data and prior to the accept. The suffix - of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt deny, records the - total number of prompt ignore events for this origin since the last time the - user explicitly set the permission state or cleared history / site data and - prior to the accept. The suffix of the histogram indicates which particular - permission. - - - - - - Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt dismissal, records - the total number of prompt dismissal events for this origin since the last - time the user cleared their history or site data, inclusive of the current - dismissal. Every event in a bucket larger than 1 in this histogram will also - have an event in each smaller bucket. The suffix of the histogram indicates - which particular permission. - - - - - - Replaced by Permissions.Prompt.Dismissed.PriorDismissCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt dismiss, records - the total number of prompt dismissal events for this origin since the last - time the user cleared their history or site data and prior to the dismiss. - The suffix of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt dismiss, records - the total number of prompt dismissal events for this origin since the last - time the user explicitly set the permission state or cleared history / site - data and prior to the dismiss. The suffix of the histogram indicates which - particular permission. - - - - - - Replaced by Permissions.Prompt.Dismissed.PriorIgnoreCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt dismiss, records - the total number of prompt ignore events for this origin since the last time - the user cleared their history or site data and prior to the dismiss. The - suffix of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt dismiss, records - the total number of prompt ignore events for this origin since the last time - the user explicitly set the permission state or cleared history / site data - and prior to the dismiss. The suffix of the histogram indicates which - particular permission. - - - - - - Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt ignore, records the - total number of prompt ignore events for this origin since the last time the - user cleared their history or site data, inclusive of the current ignore. - Every event in a bucket larger than 1 in this histogram will also have an - event in each smaller bucket. The suffix of the histogram indicates which - particular permission. - - - - - - Replaced by Permissions.Prompt.Ignored.PriorDismissCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt ignore, records the - total number of prompt dismissal events for this origin since the last time - the user cleared their history or site data and prior to the ignore. The - suffix of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt ignore, records the - total number of prompt dismissal events for this origin since the last time - the user explicitly set the permission state or cleared history / site data - and prior to the ignore. The suffix of the histogram indicates which - particular permission. - - - - - - Replaced by Permissions.Prompt.Ignored.PriorIgnoreCount2 on 05/2020. - - dominickn@chromium.org - kcarattini@chromium.org - - This metric, recorded at the time of a permission prompt ignore, records the - total number of prompt ignore events for this origin since the last time the - user cleared their history or site data and prior to the ignore. The suffix - of the histogram indicates which particular permission. - - - - - engedy@chromium.org - elklm@chromium.org - - This metric, recorded at the time of a permission prompt ignore, records the - total number of prompt ignore events for this origin since the last time the - user explicitly set the permission state or cleared history / site data and - prior to the ignore. The suffix of the histogram indicates which particular - permission. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Tracks whether the user has expanded the infobar notification permission - request. - - - - - - Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same - counts are available in Permissions.Prompt.Accepted. - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks acceptance of permission bubble request types that have been merged - into coalesced bubbles. - - - - - - Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same - counts are available in Permissions.Prompt.Denied. - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks denial of permission bubble request types that have been merged into - coalesced bubbles. - - - - - - Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same - counts are available in Permissions.Prompt.Shown. - - dominickn@chromium.org - kcarattini@chromium.org - - Tracks the permission bubble request types that are being merged into - coalesced bubbles. - - - - - - Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same - counts are available in Permissions.Prompt.Shown. - - dominickn@chromium.org - kcarattini@chromium.org - - How many permission requests each permissions prompt shown to the user - contains. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Tracks how many times permission prompts are shown to users. - - - - - bsep@chromium.org - engedy@chromium.org - olesiamarukhno@google.com - - Records how long it takes for the user to make a decision about permission - request, from when permission prompt is shown until when the user clicks on - one of the buttons in the prompt (accept, block or close). - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records, each time the quiet UI gets enabled in preferences, whether it was - enabled by the adaptive activation logic. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records when the quiet notification permission UI state changes, that is, it - either gets enabled or disabled, in preferences. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Records whether the quiet notification permission UI is enabled in - preferences at profile creation. No sample recorded when notifications are - set to be blocked completely. - - - - - - Removed 02/2017, no longer used - - dominickn@chromium.org - kcarattini@chromium.org - keenanb@google.com - jww@chromium.org - - The embedder's permission setting at the time of a cross-origin iframe - permission request for a given permission type. See the corresponding - histogram suffixes. - - A request is when a website makes a permission request and the user has the - permission set to prompt (i.e. not blocked or allowed). - - Note this is probably not the metric you want - it does not correspond to - the total number of times websites request a permission. Also, because - specific permissions have code that can automatically block or grant - permissions based on things like incognito, installed extensions etc., this - does also not correspond to the number of times users are prompted to allow - permissions. - - See https://crbug.com/638076 for more details. - - - - - - Removed 02/2017, no longer used - - dominickn@chromium.org - kcarattini@chromium.org - keenanb@google.com - jww@chromium.org - - The permission type (geolocation, and such) of a same-origin permission - request. - - A request is when a website makes a permission request and the user has the - permission set to prompt (i.e. not blocked or allowed). - - Note this is probably not the metric you want - it does not correspond to - the total number of times websites request a permission. Also, because - specific permissions have code that can automatically block or grant - permissions based on things like incognito, installed extensions etc., this - does also not correspond to the number of times users are prompted to allow - permissions. - - See https://crbug.com/638076 for more details. - - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the time elapsed since the grant of the permission until it's - revoked. - - - - - reillyg@chromium.org - src/content/browser/serial/OWNERS - - Records the reason why the Serial API chooser, triggered by a call to - navigator.serial.requestPort(), was closed. - - - - - reillyg@chromium.org - src/content/browser/serial/OWNERS - Records when permission to access a serial port is revoked. - - - - engedy@chromium.org - src/components/permissions/PERMISSIONS_OWNERS - - Records the time elapsed since the grant of the permission until it's latest - usage. This histogram will be recorded only for the first usage of a given - permission after the site has loaded. - - - - - - - khorimoto@chromium.org - better-together-dev@google.com - - Indicates the feature state of Phone Hub features. This metric is emitted to - at the creation of the user session (when the user logs in), and when - feature state updates occur. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Referer used by user to reach the main Physical Web Activity. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - Initial state of the Physical Web in Chrome for iOS. - - - - - Removed 01/2017, no longer used - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Time between the most recent opt in notification update and when the user - arrives at the ListUrlsActivity. - - - - - - Removed 01/2017, no longer used - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Time between the most recent standard notification update and when the user - arrives at the ListUrlsActivity. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Round trip time to the metadata server for a Physical Web URL resolution - which the client requests during a background scan. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Round trip time to the metadata server for a Physical Web URL resolution - which the client requests during a foreground scan, that is not explicitly - requested via a refresh. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Round trip time to the metadata server for a Physical Web URL resolution - which the client requests during a foreground scan, that is explicitly - requested via a refresh. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - olivierrobin@chromium.org - Round trip time to the metadata server for Physical web. - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - Whether bluetooth is on, off, or unknown. - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - Whether the data connection is active. - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - Whether location permission has been accepted. - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - Whether location services are enabled. - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Whether the preference is on, off, or if the user is in an onboarding state - when Chrome first starts up. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - The number of URLs displayed to a user when a list of nearby URLs is first - displayed. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - The number of URLs displayed to a user when a list of nearby URLs is - displayed after refreshing. - - - - - - Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). - - cco3@chromium.org - mattreynolds@chromium.org - mmocny@chromium.org - - Count of how many times the user selected a nearby URL at the specified - index in the Physical Web WebUI list view (zero-based). Capped at 50. - - - - - fbeaufort@chromium.org - media-dev@chromium.org - - Records Picture-in-Picture window control buttons pressed by user (basically - everything except user tap gestures). - - - - - fbeaufort@chromium.org - media-dev@chromium.org - - Records Picture-in-Picture window control user tap gestures. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of crashes (user, kernel, and unclean shutdowns) during the previous - day, or the most recent day the device was in use. Reported at most once a - day. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of crashes (user, kernel, and unclean shutdowns) during the previous - epoch-week, or the most recent epoch-week the device was in use. Reported at - most once a week. Epoch-weeks divide the time in 7-day intervals starting at - the UNIX epoch. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS (ARM Chromebooks using Exynos 5250 only) Adaptive Support Voltage - Group, recorded once per bootup. Indicates which "bin" the SoC is - part of, which sets the voltage that different rails on the system will run - at. The values 0-11 are valid. A value of 12 indicates an error parsing - dmesg and should be investigated. See also Platform.LotIdEnum. - - - - - cernekee@chromium.org - - Indicates whether the kernel's ACPI Smart Battery System driver logged an - error trying to find the battery on boot. - - - - - mnissler@chromium.org - dossym@chromium.org - - Indicates the status of the developer switch on Chrome OS hardware. The - developer switch allows users to run their own code on the device. - - - - - mnissler@chromium.org - dossym@chromium.org - - On Chrome OS hardware, indicates whether flash write protection is enabled - for the firmware indicated by the histogram suffix. - - - - - mnissler@chromium.org - dossym@chromium.org - - Indicates the status of the hardware write protect switch on Chrome OS - hardware. The write protect switch protects firmware from being rewritten. - - - - - sonnyrao@chromium.org - chromeos-performance@google.com - - Chrome OS number of disk sectors read at boot from kernel start to - login-prompt-ready. - - - - - sonnyrao@chromium.org - chromeos-performance@google.com - - Chrome OS number of disk sectors written at boot from kernel start to - login-prompt-ready. - - - - - - Removed 11/2018 in favor of Platform.Cast.MeminfoMemAvailable2 with a larger - range. - - halliwell@chromium.org - - /proc/meminfo's 'MemAvailable' in Mbytes. Collected on Cast devices with - kernel version 3.14 and above and capped at 500. - - - - - halliwell@chromium.org - - /proc/meminfo's 'MemAvailable' in MiB. Collected every 5s on Cast devices - with kernel version 3.14 and above and capped at 2000. - - - - - - Removed 11/2018 in favor of Platform.Cast.MeminfoMemFreeDerived2 with a - larger range. - - halliwell@chromium.org - - free + buffers + cache memory in Mbytes on Cast devices, capped at 500. - - - - - halliwell@chromium.org - - Collect free + buffers + cache memory in MiB every 5s on Cast devices, - capped at 2000. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Chrome OS size of allocated swap area in megabytes (before compression) - - - - - sonnyrao@chromium.org - chromeos-performance@google.com - - CPU frequency as percent of the baseline frequency, sampled every 30s. This - may be throttled down from 100% due to power dissipation issues (too high - temperature). It may also be throttled up (turbo), but the kernel does not - report the actual turbo frequency, so we put such samples in the 101% - bucket. - - - - - sonnyrao@chromium.org - cast-analytics@google.com - - Peak total (single core) CPU usage for the last sample interval. The sample - interval may vary from seconds to several minutes. - - - - - vbendeb@chromium.org - - A sparse histogram of values of Board ID flags programmed in H1 devices in - the field. Board ID flags is a 32 bit field, and while there only are a few - expected values, conceivably any bit combination could be encountered. - - - - - vbendeb@chromium.org - apronin@chromium.org - cros-hwsec+uma@chromium.org - - A sparse histogram of values indexed by 4 byte Board ID code programmed in - H1 reported by devices where there is a mismatch between the RLZ code and - the Board ID value programmed in the H1. - - - - - apronin@chromium.org - vbendeb@chromium.org - cros-hwsec+uma@chromium.org - - A histogram of flash log event types collected from the H1 device. Log event - type is an 8 bit value. This histogram does not allow to drill into - particular log entries' contents, but allows to collect a general statistics - of events. A script running on the Chrome OS device polls the H1 for new - flash log events after every start up. - - - - - vbendeb@chromium.org - - A sparse histogram of values indexed by 4 byte Board ID code programmed in - H1, reported by devices where there is no mismatch between the RLZ code and - the Board ID value. - - - - - vbendeb@chromium.org - apronin@chromium.org - cros-hwsec+uma@chromium.org - - A sparse histogram of values indexed by 4 byte RLZ code reported by devices - where there is a mismatch between the RLZ code and the Board ID value - programmed in the H1. Since RLZ code could be misprogrammed, a sparse - histogram is used to allow keeping track of outliers. - - - - - iby@chromium.org - mutexlox@chromium.org - cros-telemetry@google.com - - (Chrome OS only) An enum indicating the reasons for removal of crash reports - on devices. Generally, we'll remove crash reports after successfully sending - them, but there are other reasons for removal (e.g. if the metadata file was - malformed). These should be rare, but bugs in the crash reporting system may - cause us to start removing crashes before sending them more often. This - metric is intended to monitor crash reporting system health. - - - - - - - - - iby@chromium.org - mutexlox@chromium.org - vapier@chromium.org - - Generic event of interest from Chrome OS. Intended mainly to help assess the - frequency of rare error conditions. - - - - - drinkcat@chromium.org - dnschneid@chromium.org - - Detects presence of /run/crouton, indicating that crouton has been started - since the previous boot. Value 0/"Total count" is reported on - boot, 1/"Started" is reported after the file presence is detected - (checked periodically). - - - - - semenzato@chromium.org - bsimonnet@chromium.org - - Total CPU time accumulated since the last version update. Reported at most - once a day. - - - - - semenzato@chromium.org - bsimonnet@chromium.org - - Total use time (device ON and not asleep) since last version update. - Reported at most once a day. - - - - - semenzato@chromium.org - bsimonnet@chromium.org - - Total use time (device ON and not asleep) in the previous day, or the most - recent day the device was in use. Reported at most once a day. - - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - - Ratio of time a detachable base keyboard is active, i.e. when the USB - interface is not auto-suspended. Reported every 30 seconds when the base is - connected. - - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - - For devices with a detachable base: whether or not the base is connected on - boot. Recorded by upstart task on boot. - - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - Result of a detachable base pair operation. - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - - Detachable base firmware updates can be configured to only occur on boot. In - this mode, any update will be considered "pending" until the - system is rebooted, at which point the update may take place. Every time a - detachable base is connected to the system, a metric representing the - pending update status is recorded. Its possible values are as follows: (0) - communication error; (1) no update available; (2) critical update available; - or (3) non-critical update available. The definition of "critical" - is up to the software performing updates, and would typically be used in the - case of a security issue, or broken functionality in a previous firmware - version. - - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - Result of a detachable base RO firmware update. - - - - drinkcat@chromium.org - fshao@chromium.org - chromeos-kukui@google.com - Result of a detachable base RW firmware update. - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Average size of user's Cache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Maximum size of user's Cache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Average size of user's Cache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Maximum size of user's Cache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Average size of user's GCache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Maximum size of user's GCache directory. Logged once a day, if disk usage is - high. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Days since the least frequently used account signed in. Logged once a day, - if disk usage is high. - - - - - achuith@chromium.org - tls@chromium.org - - Number of users home directories on the device. Logged once a day. - - - - - achuith@chromium.org - omrilio@chromium.org - - Days since last login of the least recently user on device. Logged once a - day, if disk usage is high. - - - - - achuith@chromium.org - omrilio@chromium.org - - Number of user home dirs on device. Logged once a day, if disk usage is - high. - - - - - keescook@google.com - - Chrome OS KB in use in the /home/chronos filesystem tree. Logged once a day - during log file cleanup. - - - - - keescook@google.com - - Chrome OS KB in use in the /var filesystem tree. Logged once a day during - log file cleanup. - - - - - andrewlassalle@chromium.org - chromeos-core-services@google.com - - The result of an attempt to Install a DLC package. DLCs are ChromiumOS - Software packages that are installed in the stateful partition. - - - - - andrewlassalle@chromium.org - chromeos-core-services@google.com - - The result of an attempt to Uninstall a DLC package. DLCs are ChromiumOS - Software packages that are installed in the stateful partition. - - - - - gwendal@google.com - - eMMC [5.0] Device life time estimation for flash. This field provides an - estimated indication about the device life time that is reflected by the - averaged wear out of memory of a given type relative to its maximum - estimated lifetime. - - - - - gwendal@google.com - - Number of file system errors, as reported by dumpe2fs "FS Error - count" field. Reported once per boot. - - - - - gwendal@google.com - - True when kernel reports that the file system needs deep recovery. File - system has corruption the kernel can not fix by itself. Reported once per - boot. - - - - - gwendal@google.com - - True when kernel reports that the file system needed recovery at boot. It - indicates the filesytem was not properly unmounted, but was recovered. - Reported once per boot. - - - - - fbarchard@chromium.org - pwnall@chromium.org - - The maximum supported micro-architecture on an Intel platform. This value is - logged at program start time. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of kernel crashes during the previous day, or the most recent day the - device was in use. Reported at most once a day. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of kernel crashes since the last OS update, normalized as number of - crashes per year of active use (active use = device is ON and not asleep). - Reported daily. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of kernel crashes since the last OS update, normalized as number - crashes per year of CPU time. Reported daily. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of kernel crashes since the last OS update, reported daily. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Count of kernel crashes during the previous epoch-week, or the most recent - epoch-week the device was in use. Reported at most once a week. Epoch-weeks - divide the time in 7-day intervals starting at the UNIX epoch. - - - - - grundler@chromium.org - groeck@chromium.org - sonnyrao@chromium.org - - Time elapsed between the last two kernel crashes. Sent after every kernel - crash. - - - - - - Removed 8/2019 due to lack of usage. - - Please list the metric's owners. Add more owner tags as needed. - - The 32-bit hash of a kernel warning. This is the hash of the - "file:line" string corresponding to the location of the warning, - for instance: "/mnt/host/source/src/third_party/kernel/files/drivers - /gpu/drm/i915/intel_dp.c:351" (ignore spurious spaces). The hash is - produced by this code: while (*string) hash = (hash << 5) + hash + - *string++; Separately each warning is also collected (with its hash) via the - crash reporter, but only its first occurrence in each boot session. - - - - - sonnyrao@chromium.org - chromeos-performance@google.com - - Number of logical processors. This includes Hyperthreaded cores. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Chrome OS (ARM Chromebooks using Exynos 5250 only) indication about whether - we're part of a special lot ID. Special lot IDs are groups of chips that - have special case handling in the kernel for the Adaptive Support Voltage - code (the normal logic doesn't work). See also Platform.AsvGroup. Note that - fused devices are never part of a special lot (currently) and only some - unfused lots are "special". - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - sonnyrao@chromium.org - chromeos-memory@google.com - - Various memory usage % of total memory on Chrome OS devices (snapshotted - every 30s). - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - sonnyrao@chromium.org - chromeos-memory@google.com - - Various memory usage amount on Chrome OS devices (snapshotted every 30s). - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of all ARC processes in Chrome OS, reported every 10 minutes. - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of browser and helper processes (excluding GPU process and - renderers) in Chrome OS, reported every 10 minutes. - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of user-level daemons in Chrome OS, reported every 10 minutes. - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of the GPU process in Chrome OS, reported every 10 minutes. - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of renderer processes in Chrome OS, reported every 10 minutes. - - - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Memory usage of VMs (crostini) in Chrome OS, reported every 10 minutes. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - cast-analytics@google.com - - Peak memory bandwith (read and write) usage during the last sample interval. - The sample interval may vary from seconds to several minutes. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Chrome OS total anonymous memory (active + inactive) as % of total memory 1 - minute after boot. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Chrome OS total anonymous memory (active + inactive) as % of total memory 5 - minutes after boot. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Chrome OS total anonymous memory (active + inactive) as % of total memory 30 - minutes after boot. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Chrome OS total anonymous memory (active + inactive) as % of total memory - 150 minutes after boot. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Chrome OS total anonymous memory (active + inactive) as % of total memory - 750 minutes after boot. - - - - - - Removed 6/2020 due to lack of usage. - - gwendal@chromium.org - sarthakkukreti@chromium.org - - Type of encrypted mount used for the encrypted stateful file system on - Chrome OS. - - - - - apronin@chromium.org - mnissler@chromium.org - cros-hwsec+uma@chromium.org - - File system encryption key status for the encrypted stateful file system on - Chrome OS. The encryption key is the one that is used by the kernel to - protect actual file contents on disk. - - - - - apronin@chromium.org - mnissler@chromium.org - cros-hwsec+uma@chromium.org - - Type/Origin of the system key used for the encrypted stateful file system on - Chrome OS. This key is used to wrap the actual file system encryption key. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Page faults per second averaged over 30s interval, sampled continuously. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Page faults per second averaged over 1s interval, sampled every 30s. - - - - - gwendal@google.com - - Number of disk sectors per second read by Chrome OS in a long interval - (currently 30s) - - - - - gwendal@google.com - - Number of disk sectors per second read by Chrome OS in a short interval - (currently 1s, sampled every 30s) - - - - - asavery@chromium.org - gwendal@chromium.org - - The remaining reserved space (SMART 232). The value counts down typically - from 100 to 0, sent at boot. - - - - - asavery@chromium.org - gwendal@chromium.org - - The total number of 512-byte sectors written during the lifetime of the - device, sent at boot. - - - - - asavery@chromium.org - gwendal@chromium.org - - The total number of 512-byte sectors written during the lifetime of the - device, sent at boot. - - - - - asavery@chromium.org - gwendal@chromium.org - - Percentage Used Endurance Indicator. A value of 0 indicates a new device, a - value of 100 indicates the device is at the end of its lifespan as projected - by the manufacturer. Values greater than 100 indicate the device is beyond - the projected lifespan. Maximum value is 255, sent at boot. - - - - - - Removed 8/2019 due to lack of usage. - - ddavenport@chromium.org - - The 32-bit hash of the name of the service that failed. The name of the - service is hashed using the same algorithm as used for the hashes in - Platform.KernelWarningHashes. The first instance of each service failure is - also collected separately via the crash reporter. - - - - - gwendal@google.com - Disk communication errors (SMART 199), sent at boot. - - - - gwendal@google.com - Uncorrectable disk errors (SMART 187), sent at boot. - - - - vpalatin@google.com - - USB device ID of the charger plugged into a Spring device (if any), sent - once a minute. The Device ID is composed from the following 4 8-bit - registers of the TSU6721 chip: ADC (07h), Device Type 3 (15h), Device Type 2 - (0Bh), Device Type 1 (0Ah). Device Type 1/2/3 is a bitmap and most of bits - are mutually exclusive (excepted VBUS debounce). ADC is the 5-bit value of - the ID pin, but for most types (as in Device Type), there are only one or - two possible ID pin connections/values. The datasheet can be found here: - http://www.ti.com/lit/ds/symlink/tsu6721.pdf. - - Note that different brand/models of the charger can have the same ID. - - - - - jamescook@chromium.org - gwendal@chromium.org - - Chrome OS stateful partition space free. Sampled once daily. - - - - - asavery@chromium.org - gwendal@chromium.org - - Chrome OS stateful partition lifetime writes. Sampled once daily. - - - - - asavery@chromium.org - gwendal@chromium.org - - The amount of time in hours since the last trim when chromeos-trim triggers - a trim for the stateful partition. The chromeos-trim script is run daily, - but a trim is only triggered if the previous run was interrupted, the amount - of writes since the last trim is greater than X% of the remaining space in - stateful or we have not trimmed in 7 days. Reported at most once a day. - - - - - asavery@chromium.org - gwendal@chromium.org - - The amount of data in the stateful partition that is erased when - chromeos-trim triggers a trim. The chromeos-trim script is run daily, but a - trim is only triggered if the previous run was interrupted, the amount of - writes since the last trim is greater than X% of the remaining space in - stateful or we have not trimmed in 7 days. Reported at most once a day. - - - - - achuith@chromium.org - omrilio@chromium.org - Chrome OS stateful partition usage level. - - - - asavery@chromium.org - gwendal@chromium.org - - Chrome OS stateful partition space used. Sampled once daily. - - - - - asavery@chromium.org - gwendal@chromium.org - - Chrome OS stateful partition KiB writes per day. Sampled once daily. - - - - - dehrenberg@chromium.org - cast-analytics@google.com - - The number of blocks marked bad in an MTD partition. This is relevant for - devices with raw NAND flash, such as Chromecast. Sampled once daily, if the - Chromecast is on for any significant length of time in the day. - - - - - asavery@chromium.org - gwendal@chromium.org - - Vendor specific estimate of the percentage of NVM subsystem life used based - on the actual usage and the manufacturer's prediction of NVM life. A value - of 100 indicates the estimated endurance has been consumed, but may not - indicate a failure. Values can exceed 100, with percentages greater than 254 - represented as 255. - - - - - asavery@chromium.org - gwendal@chromium.org - - UFS Device life time estimation. This field provides an indication of the - device life time based on the amount of performed program/erase cycles. The - calculation is vendor specific. - - - - - asavery@chromium.org - chromeos-storage@google.com - Number of pages swapped IN over a day, sampled daily. - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Average pages/second swapped IN over a 30s interval, sampled every 30s. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Average pages/second swapped IN over a 1s interval, sampled every 30s. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - CPU utilization for the specified swap group and time interval after a tab - switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - - Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. - - Please list the metric's owners. Add more owner tags as needed. - - Page faults/second for the specified swap group and time interval after a - tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. - - - - - asavery@chromium.org - chromeos-storage@google.com - Number of pages swapped OUT over a day, sampled daily. - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Average pages/second swapped OUT over a 30s interval, sampled every 30s. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Average pages/second swapped OUT over a 1s interval, sampled every 30s. - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 0 (TSR0) taken every 30s. - - This metric is specific to Chrome OS - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 0 (TSR0) taken after resume - from sufficiently long suspend. - - This metric is specific to Chrome OS - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 1 (TSR1) taken every 30s. - - This metric is specific to Chrome OS - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 1 (TSR1) taken after resume - from sufficiently long suspend. - - This metric is specific to Chrome OS - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 2 (TSR2) taken every 30s. - - This metric is specific to Chrome OS - - - - - fletcherw@chromium.org - - Temperature reading from EC temperature sensor 2 (TSR2) taken after resume - from sufficiently long suspend. - - This metric is specific to Chrome OS - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 3 (I2C_PCH-Object) taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 4 (I2C_DDR-Die) taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 5 (I2C_DDR-Object) taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 6 (Charger-Die), taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 7 (Charger-Object) taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Temperature reading at sensor 8 (ECInternal) taken every 30s. - - - - - Please list the metric's owners. Add more owner tags as needed. - Temperature reading at sensor 9 (PECI) taken every 30s. - - - - julanhsu@google.com - caiz@google.com - - Temperature reading at sensor 0 of the CPU collected every few seconds (may - vary between devices). - - This metric is specific to Chrome OS. - - - - - fletcherw@chromium.org - - Temperature reading at sensor 0 of the CPU collected when resuming from a - sufficiently long suspend. - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - Temperature reading at wireless interface 0 collected every few seconds (may - vary between devices). - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - Temperature reading at wireless interface 1 collected every few seconds (may - vary between devices). - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - Temperature reading at wireless interface 2 collected every few seconds (may - vary between devices). - - This metric is specific to Chrome OS. - - - - - julanhsu@google.com - caiz@google.com - - State of the thermal zone of the CPU collected every second. State depends - on device, higher state corresponds to a higher temperature. - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - State of the thermal zone of wireless interface 0 collected every second. - State depends on device, higher state corresponds to a higher temperature. - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - State of the thermal zone of wireless interface 1 collected every second. - State depends on device, higher state corresponds to a higher temperature. - - This metric is specific to Chrome OS. - - - - - - Removed 09/2020 - - mka@chromium.org - - State of the thermal zone of wireless interface 2 collected every second. - State depends on device, higher state corresponds to a higher temperature. - - This metric is specific to Chrome OS. - - - - - semenzato@chromium.org - - Each sample is the result code of a TPM authorized command issued through - tcsd. Success is 0. For the other error codes, see - /usr/include/tss/tpm_error.h. - - - - - cylai@chromium.org - cros-hwsec-userland-eng+uma@chromium.org - - Each sample is the value of the TPM dictionary attack counter reported at - boot and hourly while running. Any non-zero value is unexpected. - - - - - cylai@chromium.org - cros-hwsec-userland-eng+uma@chromium.org - - Each sample is the status of an hourly attempt to reset the TPM dictionary - attack counter. - - - - - semenzato@chromium.org - - Each sample is the result code of a TPM command issued through tcsd. Success - is 0. For the other error codes, see /usr/include/tss/tpm_error.h. - - - - - mnissler@chromium.org - cros-hwsec+uma@chromium.org - - Number of attempts until a successful TPM firmware update. This is the total - sum of attempts, i.e. number of failed attempts + 1 for the final successful - attempt. Note that we're not in a position to report UMA after failed - attempts, so this will only be reported by devices that eventually see a - successful attempt. - - - - - mnissler@chromium.org - cros-hwsec+uma@chromium.org - Status of a complete TPM firmware update attempt. - - - - mnissler@chromium.org - cros-hwsec+uma@chromium.org - Exit status of the TPM firmware updater script. - - - - anatol@google.com - - Trusted Platform Module hardware alerts that signal about the chip abnormal - situation. - - - - - mnissler@chromium.org - cros-hwsec+uma@chromium.org - - Indicates a fingerprint of hardware + firmware versions for the TPM chip - present in a Chrome OS device. - - - - - - Removed 06/2020 as there is no data and no mention of it in the codebase. - - apronin@chromium.org - cros-hwsec+uma@chromium.org - - Each sample is the number of consecutive reboots performed while attempting - to clear a TPM (Trusted Platform Module) error. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Retries needed to enable a FET on tps65090 (AKA tpschrome). Tps65090 is a - power management unit (PMU) used on many ARM Chromebooks. Until version ES7 - was rolled into production we would sometimes run into a problem where FET1 - (the FET used to switch on and off the backlight) wouldn't turn on properly. - This problem was especially prevalent when the voltage was high (like when - the device was plugged into the wall). Retrying by turning the FET off and - on again is nearly always effective, so the kernel will retry up to 5 times - (currently) and will also log the fact that it needed to retry. On newest - kernels (kernel 3.8 and up) a kernel warning will be logged with WARN_ON if - the FET still failed to turn on after 5 tries. Refer to the kernel warning - reports to find that information. For more details about this bug refer to - http://crbug.com/338657 and http://crosbug.com/p/16009. Note that we log - retries on all 7 FETs even though we've only ever seen failures of FET1. - - - - - cylai@chromium.org - cros-hwsec-userland-eng+uma@chromium.org - Records occurrences of U2F commands sent to cr50. - - - - cylai@chromium.org - cros-hwsec-userland-eng+uma@chromium.org - Records occurrences of legacy U2F commands sent to cr50. - - - - semenzato@chromium.org - bsimonnet@chromium.org - - Count of crashes (unclean shutdown) during the previous day, or the most - recent day the device was in use. Reported at most once a day. - - - - - semenzato@chromium.org - bsimonnet@chromium.org - - Count of crashes (user) during the previous day, or the most recent day the - device was in use. Reported at most once a day. - - - - - tnagel@chromium.org - - Number of unknown RW_VPD entries on Chrome OS, sent once per boot. - - - - - briannorris@chromium.org - cros-network-metrics@google.com - - Sample collected 10s after boot, showing how many WiFi interfaces are - present. - - - - - rajatja@chromium.org - briannorris@chromium.org - chromeos-kernel-wifi@google.com - cros-network-metrics@google.com - - Logged (with a constant value of 1) if a WiFi device experienced a PCI - failure such that it is being removed from the system. Typically, Chrome OS - will follow such a removal with an attempt to rescan the bus and recover - device functionality. See also Platform.WiFiStatusAfterForcedPCIRescan for - the result of such attempts. - - - - - rajatja@chromium.org - briannorris@chromium.org - cros-network-metrics@google.com - - Shows the WiFi status after the PCI bus is rescanned to recover WiFi. The UI - depends on shill noticing that wlan0 is back up, so the only happy case is - one where shill recognizes wlan0 after the rescan completes. - - - - - gwendal@google.com - - Number of disk sectors per second written by Chrome OS in a long interval - (currently 30s) - - - - - gwendal@google.com - - Number of disk sectors per second written by Chrome OS in a short interval - (currently 1s, sampled every 30s) - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - Compressed swap size in megabytes. This is the actual amount of RAM used by - the system to compress memory (i.e. after compression). Snapshot every 30s. - - - - - sonnyrao@chromium.org - chromeos-memory@google.com - - The ratio of compressed memory (zram) before and after compression when the - denominator at least 1 MB. Ratios of interest are between 1 and 6 (typically - between 2 and 3), and we express them as a percentage (between 100% and - 600%). The size of memory before compression includes zero-filled pages. - Values close to 100% indicate low compression effectiveness. Snapshot every - 30s. - - - - - asavery@chromium.org - gwendal@chromium.org - - Number of incompressible pages stored in zram. A large number suggests lower - compression effectiveness. Snapshot every 30s. - - - - - asavery@chromium.org - gwendal@chromium.org - - The fraction of compressed memory that consists of incompressible pages. We - express this as a percentage (between 0% and 100%). Values close to 100% - mean we are not able to effectively benefit from compression. Snapshot every - 30s. - - - - - asavery@chromium.org - gwendal@chromium.org - - The fraction of the uncompressed memory size that consists of incompressible - pages. We express this as a percentage (between 0% and 100%). Values close - to 100% mean we are not able to effectively benefit from compression. - Snapshot every 30s. - - - - - sonnyrao@google.com - chromeos-memory@google.com - - RAM savings in megabytes from using memory compression. This is the - difference between the RAM size before and after compression. Snapshot every - 30s. - - - - - sonnyrao@google.com - chromeos-memory@google.com - - Number of zero-filled pages that the OS is compressing. A large number - suggests wasteful allocation. Snapshot every 30s. - - - - - sonnyrao@google.com - chromeos-memory@google.com - - The fraction of compressed memory that consists of zero-filled pages. - Snapshot every 30s. - - - - - - Removed as of 2016-07 because the histogram's purpose of adding colour to - the description of File::Flush() has been fulfilled. - - tnagel@chromium.org - The time it takes to run File::Flush(). - - - - - Removed as of 2013-05, replaced by PlatformFile.UnknownCreateFileErrorsWin - in chrome 29. - - Please list the metric's owners. Add more owner tags as needed. - - Errors returned by CreateFile on windows that PlatformFileError doesn't yet - support. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Errors returned by CreateFile on POSIX that PlatformFileError doesn't yet - support. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Errors returned by CreateFile on Windows that PlatformFileError doesn't yet - support. - - - - - olka@chromium.org - handellm@chromium.org - - Realtime period the thread is attempted to be configured with. Zero means - the default empirical configuration is used. Reported only on Mac. - - - - - olka@chromium.org - handellm@chromium.org - - Realtime thread period logged if it was applied successfully. Zero means the - default empirical configuration is used. Comparison with - PlatformThread.Mac.AttemptedRealtimePeriod may point to problematic - configurations. Reported only on Mac. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - Distribution of actual finished pages, vs abandoned pages, where we needed - to declare a finish time prematurely since the page was being closed - (exited). - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - - The PLT.Abandoned histogram for pages loaded after WebRequest API was used. - - - - - - Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - Diagnose why a page load was considered abandoned. - - - - - Use PageLoad.Timing2.NavigationToCommit instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "begin" to "commit." "Begin"== - "request" if user requested, and "start" otherwise. - "Request"== time when user requested document. "Start"== - time when renderer requested load of document, after any unload of last - document. "Commit"== time when renderer got first byte of - document. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - - Removed as of http://crrev.com/392823002 - - kouhei@chromium.org - - PLT.BeginToFinish, but for pages requested just after a new preconnect - request. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - PLT.BeginToFinish, but for pages which contained prefetch links. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - PLT.BeginToFinish, but for pages which were referred to by pages which - contained prefetch links. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadNormal_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadNormal_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - No longer needed. - - - The PLT.BeginToFinish histogram for pages loaded by following a link, after - WebRequest API was used. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadNormal_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadNormal_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadNormal_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadReload_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadReload_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - No longer needed. - - - The PLT.BeginToFinish histogram for pages reloaded by JavaScript or by - following a link, after WebRequest API was used. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadReload_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadReload_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadReload_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - No longer needed. - - - The PLT.BeginToFinish histogram for pages loads initiated by back/forward - buttons, or by a change of encoding, after WebRequest API was used. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by - BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - No longer needed. - - - The PLT.BeginToFinish histogram for pages loaded by entering a URL or a - search query into Omnibox, after WebRequest API was used. - - - - - - Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. - - Please list the metric's owners. Add more owner tags as needed. - - - - - - Use PLT.PT_BeginToFinish_DataReductionProxy instead. - - Please list the metric's owners. Add more owner tags as needed. - PLT.BeginToFinish, but for pages fetched over a SPDY proxy. - - - - - Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead. - - Please list the metric's owners. Add more owner tags as needed. - TBD - - - - - Removed as of http://crrev.com/392823002 - - kouhei@chromium.org - - PLT.BeginToFinishDoc, but for pages requested just after a new preconnect - request. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - PLT.BeginToFinishDoc, but for pages which contained prefetch links. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - PLT.BeginToFinishDoc, but for pages which were referred to by pages which - contained prefetch links. - - - - - - Use PLT.PT_BeginToFinishDoc_DataReductionProxy instead. - - Please list the metric's owners. Add more owner tags as needed. - - PLT.BeginToFinshDoc, but for pages fetched over a SPDY proxy. - - - - - - Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. - - pmeenan@chromium.org - - Time from "begin" to "first paint." "Begin"== - "request" if user requested, and "start" otherwise. - "Request"== time when user requested document. "Start"== - time when renderer requested load of document, after any unload of last - document. "First paint"== time when first paint operation was - performed. - - - - - - No longer needed. - - bmcquade@chromium.org - - Magnitude and difference between begin and first paint, when first_paint - precedes begin. This is a temporary metric used to better understand the - root cause of http://crbug.com/125273. - - - - - - The first paint after load is not useful for most documents. Consider using - PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. - - pmeenan@chromium.org - - Time from "big" to "first paint after load." - "Begin"== "request" if user requested, and - "start" otherwise. "Request"== time when user requested - document. "Start"== time when renderer requested load of document, - after any unload of last document. "First paint after load"== time - after onload() when first paint operation is performed. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "commit" to "finish." "Commit"== - time when renderer got first byte of document. "Finish"==after - onload() and all resources are loaded. - - - - - - Use PageLoad.ParseTiming.ParseDuration instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "commit" to "finish doc." "Commit"== - time when renderer got first byte of document. "Finish doc" == - main document loaded, before onload(). "Finish"==after onload() - and all resources are loaded. - - - - - - Use PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "commit" to "first paint." - "Commit"== time when renderer got first byte of document. - "First paint"== time when first paint operation was performed. - - - - - - The first paint after load is not useful for most documents. Consider using - PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "commit" to "first paint after load." - "Commit"== time when renderer got first byte of document. - "First paint after load"== time after onload() when first paint - operation is performed. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "finish doc" to "finish." "Finish - doc"== main document loaded, before onload(). "Finish"==after - onload() and all resources are loaded. - - - - - - The first paint after load is not useful for most documents. Consider using - PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "finish " to "first paint after load." - "Finish"==after onload() and all resources are loaded. "First - paint after load"== time after onload() when first paint operation is - performed. - - - - - djean@chromium.org - eugenebut@chromium.org - - Page load time for Browser-initiated navigations. Recorded when - CRWWebRequestController::didFinishWithURL completes successfully. iOS - specific. - - - - - - Experiment has ended 2020-06. - - djean@chromium.org - eugenebut@chromium.org - - Page load time for Browser-initiated navigations when battery level is below - a certain threshold (20%). Recorded when - CRWWebRequestController::didFinishWithURL completes successfully. iOS - specific. - - - - - djean@chromium.org - eugenebut@chromium.org - - Page load time for Renderer-initiated navigations. Recorded when - CRWWebRequestController::didFinishWithURL completes successfully. iOS - specific. - - - - - - Experiment has ended 2020-06. - - djean@chromium.org - eugenebut@chromium.org - - Page load time for Renderer-initiated navigations when battery level is - below a certain threshold (20%). Recorded when - CRWWebRequestController::didFinishWithURL completes successfully. iOS - specific. - - - - - - Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.* - instead. - - Please list the metric's owners. Add more owner tags as needed. - - Probability distribution for enumerated varieties of page loads. - - - - - - Removed as of 2014-06. - - Please list the metric's owners. Add more owner tags as needed. - - Diagnose error conditions in PLT reporting. A start time should always be - present. - - - - - - deprecated 2012-01-19 in favour of PLT.PT_* - - Please list the metric's owners. Add more owner tags as needed. - - The time elapsed between the Navigation Timing metrics navigationStart and - loadEventEnd. Definitions: http://www.w3.org/TR/navigation-timing/ - - - - - - deprecated 2012-01-19 in favour of PLT.PT_* - - Please list the metric's owners. Add more owner tags as needed. - - The time elapsed between the Navigation Timing metrics navigationStart and - loadEventStart. Definitions: http://www.w3.org/TR/navigation-timing/ - - - - - - Removed 09/2016. - - bolian@chromium.org - - Time from connectStart to connectEnd based on Navigation Timing. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from domanLookupEnd to connectStart based on Navigation Timing. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from fetchStart to domainLookupStart based on Navigation Timing. - - - - - - Removed as of 7/19/2016. Replaced by - PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired. - - bolian@chromium.org - - Time from responseStart to domLoading based on Navigation Timing. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from navigationStart to fetchStart based on Navigation Timing when no - redirect. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from navigationStart to fetchStart excluding time spent on redirects - based on Navigation Timing. Only page loads with redirects are considered. - - - - - - Removed as of 7/19/2016. Replaced by - PageLoad.DocumentTiming.NavigationToLoadEventFired. - - bolian@chromium.org - - Time from domContentLoadedEventEnd to loadEventStart based on Navigation - Timing. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from connectEnd to requestStart based on Navigation Timing. - - - - - - Removed 09/2016. - - bolian@chromium.org - - Time from domainLookupStart to domainLookupEnd based on Navigation Timing. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToDOMContentLoadedEventFired - instead. - - bolian@chromium.org - - Time from domContentLoadedEventStart to domContentLoadedEventEnd based on - Navigation Timing. - - - - - - Removed 09/2016. - - bolian@chromium.org - - Time from domInteractive to domContentLoadEventStart based on Navigation - Timing. - - - - - - Removed 09/2016. - - bolian@chromium.org - - Time from domLoading to domInteractive based on Navigation Timing. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - bolian@chromium.org - - Time from loadEventStart to loadEventEnd based on Navigation Timing. - - - - - - Removed as of 7/19/2016. - - bolian@chromium.org - - Time from redirectStart to redirectEnd based on Navigation Timing when - redirects exist. - - - - - - Removed as of 7/19/2016. Replaced by - PageLoad.ParseTiming.NavigationToParseStart. - - bolian@chromium.org - - Time from requestStart to responseStart based on Navigation Timing. - - - - - - Removed as of 7/19/2016. Replaced by PageLoad.ParseTiming.ParseDuration. - - bolian@chromium.org - - Time from responseStart to responseEnd based on Navigation Timing. - - - - - - Removed as of 5/02/2011. - - Please list the metric's owners. Add more owner tags as needed. - Distribution of discarded and displayed prerendered pages. - - - - - Removed as of 5/02/2011, replaced by Prerender.RendererPLT. - - Please list the metric's owners. Add more owner tags as needed. - - Perceived load time of a page. For non-prerendered pages, this is just - BeginToFinish. For displayed prerendered pages, this is the time from when - the prerendered page is moved into a TabContents until finish. - "Finish" == after onload() and all resources are loaded. Note that - this is 0 if the loading finishes before the page is moved into a - TabContents. - - - - - - Removed as of 5/02/2011, replaced by Prerender.RendererPerceivedPLTMatched. - - Please list the metric's owners. Add more owner tags as needed. - - Perceived load time of a prerendered page that is displayed. This is the - time from when the prerendered page is moved into a TabContents until - finish. "Finish" == after onload() and all resources are loaded. - Note that this is 0 if the loading finishes before the page is moved into a - TabContents. - - - - - - Removed as of 5/02/2011, replaced by Prerender.RendererTimeUntilDisplay. - - Please list the metric's owners. Add more owner tags as needed. - - The time elapsed between when the prerendering of a page starts and when the - page is displayed. Prerendered pages discarded without being displayed are - excluded from this count. - - - - - - Removed as of 5/02/2011, replaced by Prerender.RendererIdleTime. - - Please list the metric's owners. Add more owner tags as needed. - - This is the time from when a prerendered page finishes loading to when it is - displayed. When a page is displayed before it finishes loading, no value is - recorded in this histogram. - - - - - - Removed. Use PageLoad.Timing2.* instead. - - bmcquade@chromium.org - - Measures the time from navigation timing's navigation start to the time the - first document layout is performed. - - - - - - Removed. Use PageLoad.Timing2.* instead. - - bmcquade@chromium.org - - Measures the time from navigation timing's response start to the time the - first document layout is performed. - - - - - - Use PageLoad.Timing2.NavigationToCommit instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or - navigationStart if user-initiated request. - - - - - - Removed 9/2016. Use Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToCommit - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or - navigationStart if user-initiated request. Only page loads through the data - reduction proxy are considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.BeginToFinish. Finish: loadEventEnd. Begin: requestStart or - navigationStart if user-initiated request. - - - - - - Removed 9/2016. Use Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.BeginToFinish_SpdyProxy. Finish: loadEventEnd. Begin: - requestStart or navigationStart if user-initiated request. Only page loads - through the data reduction proxy are considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.BeginToFinishDoc. FinishDoc: loadEventStart. Begin: - requestStart or navigationStart if user-initiated request. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.BeginToFinishDoc_SpdyProxy. FinishDoc: loadEventStart. Begin: - requestStart or navigationStart if user-initiated request. Only page loads - through the data reduction proxy are considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd. - Only page loads through the data reduction proxy are considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc: - loadEventStart. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc: - loadEventStart. Only page loads through the data reduction proxy are - considered. - - - - - - No longer needed. - - Please list the metric's owners. Add more owner tags as needed. - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc: - loadEventStart. - - - - - - Removed 09/2016. - - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc: - loadEventStart. Only page loads through the data reduction proxy are - considered. - - - - - - Use PageLoad.Timing2.NavigationToCommit instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and measures the time until - the renderer got first byte of document. Commit: time when renderer got - first byte of document. Request: navigationStart. - - - - - - Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and measures the time until - the beginning of the DOMContentLoaded event. DOMContentLoaded: - domContentLoadedEventStart. Request: navigationStart. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.RequestToFinish. Finish: loadEventEnd. Request: - navigationStart. - - - - - - Removed 09/2016. Use - PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired - instead. - - pmeenan@chromium.org - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.RequestToFinish. Finish: loadEventEnd. Request: - navigationStart. Only page loads through the data reduction proxy are - considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - pmeenan@chromium.org - - This time is based on the NavigationTiming spec and measures the page load - time until the beginning of the load event. Finish: loadEventStart. Request: - navigationStart. - - - - - Please list the metric's owners. Add more owner tags as needed. - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.RequestToStart. Start: requestStart. Request: - navigationStart. - - - - - - Removed 09/2016. - - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.RequestToStart. Start: requestStart. Request: - navigationStart. Only page loads through the data reduction proxy are - considered. - - - - - Please list the metric's owners. Add more owner tags as needed. - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.StartToCommit. Start: requestStart. Commit: responseStart. - - - - - - Removed 09/2016. - - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.StartToCommit. Start: requestStart. Commit: responseStart. - Only page loads through the data reduction proxy are considered. - - - - - Please list the metric's owners. Add more owner tags as needed. - - This time is based on the NavigationTiming spec and is a more accurate - version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd. - - - - - - Removed 09/2016. - - bengr@chromium.org - megjablon@chromium.org - - This time is based on the PerformanceTiming spec and is a more accurate - version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd. - Only page loads through the data reduction proxy are considered. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "request" to "finish." "Request" == - time when user requested document. "Finish" == after onload() and - all resources are loaded. - - - - - Please list the metric's owners. Add more owner tags as needed. - - Time from "request" to "start." "Request"== - time when user requested document. "Start"== time when renderer - requested load of document, after any unload of last document. - - - - - - Use PageLoad.Timing2.NavigationToCommit instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "start" to "commit." "Start"== time - when renderer requested load of document, after any unload of last document. - "Commit"== time when renderer got first byte of document. - - - - - - Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. - - Please list the metric's owners. Add more owner tags as needed. - - Time from "start" to "finish." "Start"== time - when renderer requested load of document, after any unload of last document. - "Finish"==after onload() and all resources are loaded. - - - - - - Removed as of 07/2014. - - Please list the metric's owners. Add more owner tags as needed. - StartToFinish times when using http and no proxy. - - - - - Removed as of 07/2014. - - Please list the metric's owners. Add more owner tags as needed. - StartToFinish times when using https and no proxy. - - - - - Removed as of 07/2014. - - Please list the metric's owners. Add more owner tags as needed. - StartToFinish times when using http over a proxy. - - - - - Removed as of 07/2014. - - Please list the metric's owners. Add more owner tags as needed. - StartToFinish times when using https over a proxy. - - - - - Removed as of 09/2016. - - pmeenan@chromium.org - - This time is based on the User Timing spec and measures the time from - Navigation Timing navigationStart until the point where the page called - performance.mark(). - - - - - - Removed as of 09/2016. - - pmeenan@chromium.org - - This time is based on the User Timing spec and reports the time between two - arbitrary points defined by the page being loaded and directly matches the - measurement exposed by performance.measure(). - - - - - - Removed as of 01/2017 (M65). - - xhwang@chromium.org - media-dev@chromium.org - - The availability status of Widevine CDM. In normal cases, this is reported - per render process if EME API is used. This is not reported if EME API is - not used. This could be reported multiple times per render process until - PLUGIN_AVAILABLE is reported (which should be a rare case). - - - - - - Removed as of 06/2019 (M77). - - pastarmovj@chromium.org - tommycli@chromium.org - Tracks whether plugins that were disabled were migrated. - - - - - Removed 10/2019. - - tommycli@chromium.org - - Aspect ratio of Flash plugins users click at least once. The aspect ratio is - multiplied by 100 and stored as a rounded integer. - - - - - - Removed 10/2019. - - tommycli@chromium.org - Height of Flash plugins users click at least once. - - - - - Removed 10/2019. - - tommycli@chromium.org - Width of Flash plugins users click at least once. - - - - - Removed 12/2017 in Issue 781644 as we no longer use Site Engagement Index as - a signal for Flash display. - - dominickn@chromium.org - - The engagement score of origins which have passed through a site engagement - check to permit or block Flash. Recorded every time the Flash plugin is - requested with the PreferHtmlOverPlugins feature active. - - - - - - Removed 10/2019. - - tommycli@chromium.org - - Collects the sizes of all loaded Flash plugin instances. This is for - determining the prevalence of tiny flash plugin instances. - - - - - - Removed from code 07/2019. - - mlamouri@chromium.org - media-dev@chromium.org - - Records the YouTube Flash embed rewrite status when attempted. - - - - - Please list the metric's owners. Add more owner tags as needed. - Record usage of PPB_Flash.Navigate() Pepper API. - - - - yzshen@chromium.org - thestig@chromium.org - Collects Flash usage data. - - - - - Removed due to NPAPI removal. - - wfh@chromium.org - - The plugin group of an NPAPI plugin that is no longer supported. Recorded - when the NPAPI removal infobar is shown for a plugin which is no longer - supported. - - - - - - Removed due to NPAPI removal. - - wfh@chromium.org - - The plugin group of an NPAPI plugin that will be unsupported soon. Recorded - when the NPAPI removal infobar is shown after an NPAPI plugin first loads to - warn the user that NPAPI support for this plugin will be removed soon. - - - - - - Removed due to NPAPI removal. - - wfh@chromium.org - - Records whether NPAPI plugins are supported by the platform, and if so, - whether they are enabled or disabled. Recorded once at browser startup. - - - - - - Removed in favor of Plugin.PowerSaver.PeripheralHeuristicInitialDecision. - - tommycli@chromium.org - - Records each decision of the Plugin Power Saver peripheral content - heuristic. This UMA is counted once per peripheral query, and may count a - single plugin instance multiple times as it is resized. - - - - - - Removed 10/2019. - - tommycli@chromium.org - - Records the initial decision of the Plugin Power Saver peripheral content - heuristic for each plugin instance. This is recorded once per plugin - instance. - - - - - - Removed 10/2019. - - tommycli@chromium.org - - Record how many plugin object tags use poster param. This is recorded once - per plugin instance, and is currently restricted to Flash plugin instances. - - - - - tommycli@chromium.org - - Record how many throttled plugins are unthrottled, and by what method. - - - - - xhwang@chromium.org - media-dev@chromium.org - - The error code of a PPAPI broker load failure. Only reported on Windows. - - - - - xhwang@chromium.org - media-dev@chromium.org - The result from an attempt to load a PPAPI broker. - - - - xhwang@chromium.org - media-dev@chromium.org - The time spent to load a PPAPI broker. - - - - xhwang@chromium.org - media-dev@chromium.org - - The error code of a PPAPI plugin load failure. Only reported on Windows. - - - - - xhwang@chromium.org - media-dev@chromium.org - The result from an attempt to load a PPAPI plugin. - - - - xhwang@chromium.org - media-dev@chromium.org - The time spent to load a PPAPI plugin. - - - - gab@chromium.org - - The time it took to complete a synchronous IPC made from the PPAPI process. - - - - - - Removed from code 07/2019. - - mlamouri@chromium.org - Result of HTMLPluginElement::requestObject in Blink. - - - - - Removed due to NPAPI removal. - - gab@chromium.org - - Roundtrip times for synchronous IPC calls from the renderer to NPAPI plugin - processes. - - - - - - Removed 10/2019. - - twellington@chromium.org - wfh@chromium.org - - Error codes when parsing the built-in plugin list. Logged when the - PluginFinder singleton is created. - - - - - timloh@google.com - joelhockey@google.com - - Records the number of Plugin VM apps in the registry at login time. This - only logs if Plugin VM has already benn enabled for the current user. - - - - - kimjae@google.com - timloh@google.com - Recorded at each time PluginVM DLC is installed. - - - - timloh@google.com - joelhockey@google.com - - Times when user is engaged and Plugin VM apps are running in the background, - but the user isn't focusing on an Plugin VM app window. See - PluginVm.EngagementTime.Total for further details. - - - - - timloh@google.com - joelhockey@google.com - - Times when user is engaged and focuses on a Plugin VM window. See - PluginVm.EngagementTime.Total for further details. - - - - - timloh@google.com - joelhockey@google.com - - Total of PluginVm.EngagementTime.Background and .Foreground, which is the - time the user is engaged and Plugin VM is running either in the foreground - or background. See PluginVm.EngagementTime.Total for further details. - - - - - timloh@google.com - joelhockey@google.com - - Total CrOS user session time (from login to logout) excluding times when - user "disengages": screen is locked or dims down due to user idle. - Engagement time metrics, along with foreground and background time, are only - collected on users with Plugin VM enabled. All four metrics are accumulated - and recorded to UMA once a day. For Total Plugin VM engagement time, see - PluginVm.EngagementTime.PluginVmTotal. - - - - - aoldemeier@chromium.org - okalitova@chromium.org - timloh@chromium.org - - The size of the PluginVm image downloaded in MB. Recorded each time PluginVm - image is sucessfully downloaded. - - - - - aoldemeier@chromium.org - okalitova@chromium.org - timloh@chromium.org - - Recorded at each attempt to launch PluginVm, recording whether this attempt - is successful or not. - - - - - timloh@chromium.org - chromeos-core-services@google.com - Recorded when the Plugin VM installer fails. - - - - aoldemeier@chromium.org - okalitova@chromium.org - timloh@chromium.org - - Recorded at each attempt to set up PluginVm, recording the setup result. As - of M83, errors are grouped together here and broken down in - PluginVm.SetupFailureReason. - - - - - aoldemeier@chromium.org - okalitova@chromium.org - timloh@chromium.org - - Recorded at each successful attempt to set up PluginVm, recording the time - that user spent waiting for setup to be finished. When error occurs during - setup and user clicks retry button - time between pressing retry button and - setup being finished is recorded. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Total seconds of CPU time consumed by Chrome, split by process type as well - as core type and core frequency. Currently only implemented on Android. For - every second of CPU time consumed by a process on a specific CPU core type - and at a specific frequency, a sample is recorded into the bucket for the - frequency range. Samples are recorded periodically depending on the task - load of each process's main thread. The histogram thus shows the total sum - of CPU time seconds spent for a specific process and core type across all - users. - - Compared with Power.CpuTimeSecondsPerCoreTypeAndFrequency, the values in - this histogram are approximated from more widely supported global - per-CPU-core time_in_state stats, while - Power.CpuTimeSecondsPerCoreTypeAndFrequency reads per-thread time_in_state - stats that are only supported on newer Pixel devices (as of mid-2020). - - For a histogram of daily per-user values, select "Per-Client - Aggregation Mode". - - - - - tbroch@chromium.org - - The level of the backlight as a percentage when the user is on AC. Sampled - every 30 seconds. - - - - - tbroch@chromium.org - - The level of the backlight as a percentage when the user is on battery. - Sampled every 30 seconds. - - - - - tbroch@chromium.org - - Chrome OS battery charge health percentage. Sampled once when device starts - charging. - - - - - - Removed 02/2017 in favor of power benchmarks that have less variability than - data from users' machines. - - jeremy@chromium.org - - The percentage of battery capacity used per hour relative to a full battery. - Reported once when the power adaptor is plugged back in after the system is - on battery power for more than 30 minutes. If at any point the system is - suspended or all Chrome renderers are closed the measurement is not - recorded. Anytime the user unplugs the power adaptor, a new measurement will - begin being recorded. Collection of this histogram only starts after 30 - minutes of uptime at which point the clock starts (assuming the user is on - battery power at that point). The system will need to remain unplugged for - at least another 30 minutes in order for any measurement to be recorded. - Values are normalized to a percent per hour scale. This measurement is tied - tightly to hardware model/OS and is not comparable across different hardware - configurations. - - - - - tbroch@chromium.org - - Chrome OS battery discharge rate in mW sampled every 30 seconds while the - device runs on battery. - - - - - - Removed 02/2017 in favor of power benchmarks that have less variability than - data from users' machines. - - jeremy@chromium.org - - The percent of depleted battery capacity relative to a full battery over the - first 15 minutes after battery power collection information starts. - Collection of this histogram only starts after 30 minutes of uptime at which - point the clock starts (assuming the user is on battery power at that - point). The system will need to remain unplugged for at least another 15 - minutes in order for any measurement to be recorded. Values are normalized - to a percent per hour scale. This measurement is tied tightly to hardware - model/OS and is not comparable across different hardware configurations. - - - - - - Removed 02/2017 in favor of power benchmarks that have less variability than - data from users' machines. - - jeremy@chromium.org - - The percent of depleted battery capacity relative to a full battery over the - first 30 minutes after battery power collection information starts. - Collection of this histogram only starts after 30 minutes of uptime at which - point the clock starts (assuming the user is on battery power at that - point). The system will need to remain unplugged for at least another 30 - minutes in order for any measurement to be recorded. Values are normalized - to a percent per hour scale. This measurement is tied tightly to hardware - model/OS and is not comparable across different hardware configurations. - - - - - - Removed 02/2017 in favor of power benchmarks that have less variability than - data from users' machines. - - jeremy@chromium.org - - The percent of depleted battery capacity relative to a full battery over the - first 5 minutes after battery power collection information starts. - Collection of this histogram only starts after 30 minutes of uptime at which - point the clock starts (assuming the user is on battery power at that - point). The system will need to remain unplugged for at least another 5 - minutes in order for any measurement to be recorded. Values are normalized - to a percent per hour scale. This measurement is tied tightly to hardware - model/OS and is not comparable across different hardware configurations. - - - - - tbroch@chromium.org - - Chrome OS battery discharge rate in mW while the system was suspended, - sampled at resume. Only reported if the system was on battery power both - before suspending and after resuming, if the energy level didn't increase - while suspended (which would indicate that an AC adapter was connected), and - if the system was suspended for at least a minute. - - - - - tbroch@chromium.org - - Counts the number of times we have read the battery status from sysfs and if - it gave us sensible values. - - - - - ryansturm@chromium.org - tbansal@chromium.org - - The drop in battery since the last operating system battery update as a - percent of total device battery. If the drop is not a round percentage - point, the unreported amount will be carried over until the battery level - drops by a full percentage point. Recorded when the battery level drops by - more than a percentage point. If the user charges the device, the battery - tracking is reset (the amount carried over is reset). This histograms sum is - most likely the most useful figure when comparing experiments. Recorded even - when Chrome is in the background. - - - - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge, - sampled at the end of a user session when the device is on AC. - - - - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge, - sampled at the end of a user session when the device is on battery. - - - - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge, - sampled at the start of a user session when the device is on AC. - - - - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge, - sampled at the start of a user session when the device is on battery. - - - - - - Removed as of 03/2012, no longer being generated by powerd. - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge - sampled when the device runs on battery. - - - - - tbroch@chromium.org - - Chrome OS remaining battery charge as percent of the maximum battery charge, - sampled when charging starts. - - - - - - Removed as of 03/2012, no longer being generated by powerd. - - tbroch@chromium.org - - Chrome OS remaining time to empty battery in minutes sampled when the device - runs on battery. - - - - - dianders@chromium.org - - Chrome OS (Snow RO firmware 2695.90.0 only) number of 8K chunks that were - fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0 - around 97% of the time and a non-zero value around 3% of the time. - - - - - dianders@chromium.org - - Chrome OS (Snow RO firmware 2695.90.0 only) number of 4-byte words that were - fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0 - around 97% of the time and a non-zero value around 3% of the time. Would be - exactly equal to Power.BitfixChunks if there were only one corrupted word in - each chunk but is sometimes several times higher. - - - - - - Removed as of 5/2013. See Accel_BrightnessDown_F6 and Accel_BrightnessUp_F7 - user actions instead. - - tbroch@chromium.org - - Number of times the user has adjusted brightness up and down while running - on battery power. - - - - - - Removed as of 5/2013. See Accel_BrightnessDown_F6 and Accel_BrightnessUp_F7 - user actions instead. - - tbroch@chromium.org - - Number of times the user has adjusted brightness up and down while running - on AC power. - - - - - - Removed 11/2014 in issue 427057. - - tbroch@chromium.org - - External power supply type such as MAINS_CHARGER, USB_CHARGER, - UNCONFIRMED_SPRING_CHARGER, SAFE_SPRING_CHARGER. A sample is reported each - time a charger is connected to the device. - - - - - bleung@chromium.org - tbroch@chromium.org - - Connected charging ports on Chrome OS. A sample is reported every time that - the power manager polls sysfs (typically every 30 seconds). Ordinals are - assigned based on the lexicographical ordering of power supply names from - sysfs and have no implied correspondence with ports' physical locations. For - example, with ports 'CROS_USB_PD_CHARGER0' and 'CROS_USB_PD_CHARGER1', - 'first' refers to the former and 'second' to the latter. To determine a - port's physical location, see the powerd charging_ports pref in the device's - overlay. - - - - - eseckler@chromium.org - skyostil@chromium.org - - For clients enrolled in CPU affinity restriction experiments (e.g. - restricting execution to little cores only), records whether the CPU - affinity for a process could be succcessfully set. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Total seconds of CPU time consumed by Chrome, split by process type as well - as core type and core frequency. Currently only implemented on Android. For - every second of CPU time consumed by a process on a specific CPU core type - and at a specific frequency, a sample is recorded into the bucket for the - frequency range. The histogram thus shows the total sum of CPU time seconds - spent for a specific process and core type across all users. - - For a histogram of daily per-user values, select "Per-Client - Aggregation Mode". - - - - - eseckler@chromium.org - skyostil@chromium.org - - Total seconds of CPU time consumed by Chrome, split by process type. - Currently only implemented on Android. For every second of CPU time consumed - by one process, a sample is recorded into the bucket for the process's type. - The histogram thus shows the total sum of CPU time seconds spent per process - type across all users. - - For a histogram of daily per-user values, select "Per-Client - Aggregation Mode". - - - - - eseckler@chromium.org - skyostil@chromium.org - - Total seconds of CPU time consumed by Chrome, split by process type and - thread type. Currently only implemented on Android. For every second of CPU - time consumed by one thread, a sample is recorded into the bucket for the - thread's type. CPU time consumed by a process that cannot be attributed to a - specific thread is recorded into the "UnattributedThread" bucket. - The histogram thus shows the total sum of CPU time seconds spent per thread - type (within processes of a specific type) across all users. - - For a histogram of daily per-user values, select "Per-Client - Aggregation Mode". - - - - - chirantan@chromium.org - abhishekbh@chromium.org - ravisadineni@chromium.org - - The amount of time a system spent awake every time it woke up in dark - resume. - - - - - chirantan@chromium.org - abhishekbh@chromium.org - ravisadineni@chromium.org - - The amount of time a system spent awake every time it woke up in dark resume - triggered by an unknown or unsupported wake trigger. - - - - - chirantan@chromium.org - abhishekbh@chromium.org - ravisadineni@chromium.org - - The amount of time a system spent awake every time it woke up in dark resume - triggered by a WiFi disconnect. - - - - - chirantan@chromium.org - abhishekbh@chromium.org - ravisadineni@chromium.org - - The amount of time a system spent awake every time it woke up in dark resume - triggered by a WiFi packet pattern match. - - - - - chirantan@chromium.org - abhishekbh@chromium.org - ravisadineni@chromium.org - - The amount of time a system spent awake every time it woke up in dark resume - triggered by a net detect SSID match. - - - - - chirantan@chromium.org - - The number of times a system woke up in dark resume in an hour. Note that - this value is scaled up or down to an hour based on the amount of time the - system spent in suspend. So if the system suspended for 20 minutes and woke - up 3 times, it would report a value of 9. - - - - - tbroch@chromium.org - - The result of attempting to read an external display's brightness on Chrome - OS. A read attempt is made after successfully requesting the brightness (see - Power.ExternalBrightnessRequestResult). - - - - - tbroch@chromium.org - - The result of requesting an external display's brightness on Chrome OS. A - request is sent when the user presses a brightness key and the current - brightness is not already cached. A successful request is followed shortly - thereafter by a read attempt (see Power.ExternalBrightnessReadResult). - - - - - tbroch@chromium.org - - The result of attempting to change an external display's brightness on - Chrome OS. A request is sent when the user presses a brightness key and the - current brightness is either already cached or successfully loaded. - - - - - tbroch@chromium.org - - The result of attempting to open an I2C device to control an external - display's brightness on Chrome OS. An attempt is made when a display is - connected to a device that lacks an internal display. - - - - - tbroch@chromium.org - - The time that the firmware took to resume the Chrome OS device from - suspend-to-RAM state when running on AC at pre-suspend time. - - - - - tbroch@chromium.org - - The time that the firmware took to resume the Chrome OS device from - suspend-to-RAM state when running on battery at pre-suspend time. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Records a sample for every 0.1 milliampere-hours of battery capacity that - are drained while Chrome is the foreground app and the device is on battery - power. Only supported on Android. The histogram thus shows the total sum of - battery capacity consumed across all users. - - For a histogram of daily per-user values, see the computed histogram - Power.DailyForegroundBatteryDrain. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Periodically samples the battery capacity drained while Chrome is the - foreground app and the device is on battery power. Sampled every 30 seconds - and when Chrome is backgrounded or the device connects to a charger. Sample - values are reported as provided by the battery capacity counter (in - microampere-hours). Because the resolution of this counter is rather coarse - (usually between .5 and 50 mAh), the uAh value may have been drained over a - longer time period than 30 seconds. See also - Power.ForegroundBatteryDrain.30SecondsAvg, which averages the values over - successive sampling points without change in counter values. - - Only supported on Android. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Periodically samples the battery capacity drained while Chrome is the - foreground app and the device is on battery power. Sampled every 30 seconds - and when Chrome is backgrounded or the device connects to a charger. Sample - values are reported as provided by the battery capacity counter (in - microampere-hours). Because the resolution of this counter is rather coarse - (usually between .5 and 50 mAh), the uAh value may have been drained over a - longer time period than 30 seconds. Only time intervals where Chrome was the - only foreground app are reported. See also - Power.ForegroundBatteryDrain.30SecondsAvg.Exclusive, which averages the - values over successive sampling points without change in counter values. - - Only supported on Android. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Periodically samples the battery capacity drained while Chrome is the - foreground app and the device is on battery power. Sampled every 30 seconds - and when Chrome is backgrounded or the device connects to a charger. Sample - values are reported in microampere-hours and averaged over successive - sampling points without a change in capacity counter values. - - Only supported on Android. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Periodically samples the battery capacity drained while Chrome is the - foreground app and the device is on battery power. Sampled every 30 seconds - and when Chrome is backgrounded or the device connects to a charger. Sample - values are reported in microampere-hours and averaged over successive - sampling points without a change in capacity counter values. Only time - intervals where Chrome was the only foreground app are reported. - - Only supported on Android. - - - - - eseckler@chromium.org - skyostil@chromium.org - - Records a sample for every 0.1 milliampere-hours of battery capacity that - are drained while Chrome is the foreground app and the device is on battery - power. Only supported on Android. The histogram thus shows the total sum of - battery capacity consumed across all users. Only time intervals where Chrome - was the only foreground app are reported. - - For a histogram of daily per-user values, see the computed histogram - Power.DailyForegroundBatteryDrain.Exclusive. - - - - - eseckler@chromium.org - skyostil@chromium.org - - A companion metric for Power.ForegroundBatteryDrain.30SecondsAvg which - reports the time interval between successive capacity drops reported by the - battery manager. - - Only supported on Android. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Number of times that that the screen has been dimmed in response to user - inactivity, reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Number of times that that the screen has been turned off in response to user - inactivity, reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Number of times that that the system has suspended in response to user - inactivity, reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time since the screen dimmed sampled when the user - becomes active again if the device runs on AC. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time since the screen dimmed sampled when the user - becomes active again if the device runs on battery. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time since the screen turned off sampled when the user - becomes active again if the device runs on AC. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time since the screen turned off sampled when the user - becomes active again if the device runs on battery. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time sampled when the user becomes active again if the - device runs on AC. - - - - - tbroch@chromium.org - jiameng@chromium.org - - Chrome OS user idle time sampled when the user becomes active again if the - device runs on battery. - - - - - tbroch@chromium.org - - The time that the kernel took to resume the Chrome OS device from - suspend-to-RAM state when running on AC at pre-suspend time. - - - - - tbroch@chromium.org - - The time that the kernel took to resume the Chrome OS device from - suspend-to-RAM state when running on battery at pre-suspend time. - - - - - tbroch@chromium.org - - The time that the kernel took to suspend-to-RAM the Chrome OS device when - running on AC. - - - - - tbroch@chromium.org - - The time that the kernel took to suspend-to-RAM the Chrome OS device when - running on battery. - - - - - tbroch@chromium.org - - The level of the keyboard backlight as a percentage. Sampled every 30 - seconds. - - - - - tbroch@chromium.org - - The length of time, in seconds, that a user spent in a single session. - Values for this metric are clamped to 12 hours, so the last bucket should be - considered to be including all metrics above 12 hours. - - - - - tbroch@chromium.org - - Number of times that that the system has suspended in response to its lid - being closed, reported daily. The count is accumulated through the day, - spanning reboots, and sent once the system clock indicates that a full day - or more has passed since the last report. If the system is suspended or off - for more than a day, the current count will be reported immediately the next - time the system boots, but the skipped days will not be reported. Chrome OS - only. - - - - - lgrey@chromium.org - markchang@chromium.org - - Instantaneous power consution in milliwatts, for the system as a whole and - broken down by component. Only recorded on macOS. NB: The collection method - was changed in May 2019, which may look like a regression in timeline view. - - - - - lgrey@chromium.org - - When metrics collection started, records true if a handle to the System - Management Controller (SMC) was successfully opened to monitor power - consumption, false otherwise. If false, a system API might have changed in a - new version of macOS, or Chrome might be running in a nonstandard - environment (VM, hackintosh). Only recorded on macOS. - - - - - olivierli@chromium.org - lgrey@chromium.org - - Every minute after startup a measure of the remaining and maximum battery - capacity is taken. Then a ratio of the remaining capacity over the maximum - capicity is calculated and scaled by 10000. (For example: 13 / 2000 = 0.0065 - ; 0.0065 * 10000 = 65). Power.Mac.BatteryDischarge is the the delta in this - relative capacity measure compaired to the measurement that was taken a - minute before. This metric is only recorded when on battery power. Only - recorded on macOS. - - - - - lgrey@chromium.org - - Whether the user's machine is on battery power. Sampled once per minute. - - - - - lgrey@chromium.org - - Thermal state of the user's machine as reported by macOS's [NSProcessInfo - thermalState]. Sampled once per minute. - - - - - tbroch@chromium.org - - Reasons why power-management-related daily metrics were reported. Chrome OS - only. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average power consumption, measured in milli-units per hour, when sync - invalidator listens to on_application_active events. Values for this metric - are per session, i.e. from battery level at application entering foreground - to returning to background, and normalized to an hourly average consumption. - This is an iOS only measurement. Due to how iOS reports battery levels, it - is likely to see many readings of 0. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average power consumption, measured in milli-units per hour, for other - sync invalidator methods. Values for this metric are per session, i.e. from - battery level at application entering foreground to returning to background, - and normalized to an hourly average consumption. This is an iOS only - measurement. Due to how iOS reports battery levels, it is likely to see many - readings of 0. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average power consumption, measured in milli-units per hour, when sync - invalidator uses peer-to-peer notifications. Values for this metric are per - session, i.e. from battery level at application entering foreground to - returning to background, and normalized to an hourly average consumption. - This is an iOS only measurement. Due to how iOS reports battery levels, it - is likely to see many readings of 0. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The average power consumption, measured in milli-units per hour, when sync - invalidator uses server-based non-blocking invalidator. Values for this - metric are per session, i.e. from battery level at application entering - foreground to returning to background, and normalized to an hourly average - consumption. This is an iOS only measurement. Due to how iOS reports battery - levels, it is likely to see many readings of 0. - - - - - tbroch@chromium.org - jiameng@chromium.org - - The number of times that the Automatic Light Sensor (ALS) adjusted the - brightness during a session. Values for this metric are clamped to 10k - count, so the last bucket should be considered to be including all metrics - above 10k. - - - - - tbroch@chromium.org - - The number of user sessions that occured since the last time that the device - was charged. Values for this metric are clamped at 10k, so the last bucket - should be considered to include all metrics about 10k. - - - - - tbroch@chromium.org - - The amount of time between the user pressing the power button and Chrome - acknowledging the button-down event on Chrome OS. Values for this metric are - capped to two seconds. - - - - - tbroch@chromium.org - - The amount of time between the user pressing the power button and releasing - it on Chrome OS. - - - - - minch@chromium.org - xdai@chromium.org - Actions performed while the power button menu is open. - - - - minch@chromium.org - xdai@chromium.org - - Press power button in laptop mode will result in different scenarios - according to the power button up state. Counts the different power button - press scenarios in laptop mode. - - - - - minch@chromium.org - xdai@chromium.org - - Press power button in tablet mode will result in different scenarios - according to the power button up state. Counts the different power button - press scenarios in tablet mode. - - - - - bleung@chromium.org - tbroch@chromium.org - - The maximum power supported by the connected power supply on Chrome OS. A - sample is reported every time that the power manager polls sysfs (typically - every 30 seconds) and sees a connected supply. - - - - - bleung@chromium.org - tbroch@chromium.org - - The maximum voltage supported by the connected power supply on Chrome OS. A - sample is reported every time that the power manager polls sysfs (typically - every 30 seconds) and sees a connected supply. - - - - - bleung@chromium.org - tbroch@chromium.org - - The type of the connected power supply on Chrome OS. A sample is reported - every time that the power manager polls sysfs (typically every 30 seconds) - and sees a connected supply. - - - - - - Removed Feb 2014 by Power.SuspendAttemptsBeforeCancel and - Power.SuspendAttemptsBeforeSuccess. - - tbroch@chromium.org - - The number of times Chrome OS retried suspend due to previous failure. - - - - - tbroch@chromium.org - - The reason for the Chrome OS power manager shutting down or rebooting the - system. - - - - - thanhdng@chromium.org - jiameng@chromium.org - Type of messages that are reported by smart charging. - - - - tbroch@chromium.org - - The number of suspend attempts on Chrome OS. Samples are reported before - each attempt, so this histogram may include cases where the system crashed - instead of suspending. - - - - - tbroch@chromium.org - - The number of suspend attempts performed for a single suspend request (e.g. - triggered by the lid being closed) that was eventually canceled on Chrome - OS. This also includes requests that were canceled due to the system - eventually shutting down due to repeated suspend failures. - - - - - tbroch@chromium.org - - The number of suspend attempts performed for a single suspend request (e.g. - triggered by the lid being closed) that eventually succeeded on Chrome OS. - This includes the successful attempt. - - - - - tbroch@chromium.org - - The results of suspend attempts on Chrome OS. Samples are reported after - each attempt. - - - - - - Removed Jan 2014 by Power.SuspendAttempt and Power.SuspendResult. - - tbroch@chromium.org - Chrome OS suspend status. - - - - - No longer sent. - - tbroch@chromium.org - - The percentage of aborted fan attempts out of total fan attempts per - session, where an abort is due to hysteresis. This value is computed from - boot and sent when powerd starts and then every 15 minutes afterwards. - - - - - - No longer sent. - - tbroch@chromium.org - - The percentage of fan trip point passes that are more than one trip point. - This value is computed from boot and sent when powerd starts and then every - 15 minutes afterwards. - - - - - tbroch@chromium.org - - Chrome OS time in minutes spent in suspend-to-RAM mode sampled at boot - (i.e., the device most likely ran out of battery while in suspend). - - - - - tbroch@chromium.org - - Chrome OS time in minutes spent in suspend-to-RAM mode sampled at resume. - - - - - tbroch@chromium.org - jiameng@chromium.org - - The number of times that the user adjusted the brightness during a session - when on AC. Values for this metric are clamped to 10k count, so the last - bucket should be considered to be including all metrics above 10k. - - - - - tbroch@chromium.org - jiameng@chromium.org - - The number of times that the user adjusted the brightness during a session - when on battery. Values for this metric are clamped to 10k count, so the - last bucket should be considered to be including all metrics above 10k. - - - - - jiameng@chromium.org - - What happens when UserActivityManager receives a screen dim imminent - notification. Only applicable to Chrome OS. - - - - - jiameng@chromium.org - - What happens after screen is dimmed following model instruction. Only - applicable to Chrome OS. - - - - - jiameng@chromium.org - - What happens after screen dim is deferred following model instruction. Only - applicable to Chrome OS. - - - - - jiameng@chromium.org - - What happens after screen is dimmed by powerd by ignoring the model - instruction. Only applicable to Chrome OS. - - - - - jiameng@chromium.org - - Status of logging previous idle event after a screen dim imminent signal is - received. Only applicable to Chrome OS. - - - - - alanlxl@chromium.org - amoylan@chromium.org - jiameng@chromium.org - - Records the event (various failures or success) of loading smart dim - component. Only applicable to Chrome OS. - - - - - alanlxl@chromium.org - amoylan@chromium.org - jiameng@chromium.org - - Records the type of expected version (default, experimental or empty) used - by smart dim component installer. Only applicable to Chrome OS. - - - - - alanlxl@chromium.org - amoylan@chromium.org - jiameng@chromium.org - - Records the worker type that is used by smart dim ml agent to make a - decision. Only applicable to Chrome OS. - - - - - amoylan@chromium.org - jiameng@chromium.org - napper@chromium.org - pmalani@chromium.org - - The time elapsed between a Smart Dim Inference Request being sent to the ML - model, and the request being canceled before the result is returned. - - - - - amoylan@chromium.org - jiameng@chromium.org - napper@chromium.org - pmalani@chromium.org - - The time elapsed between a Smart Dim Inference Request being sent to the ML - model and a result being returned. - - - - - jiameng@chromium.org - - This is the status code returned by the model when calculating a user - inactivity score. If it is any value other than 0 (success), then some issue - has occurred in the score calculation, either because preprocess was not - loaded or parsed correctly, or the preprocessor failed to process a - RankerExample. Only applicable to Chrome OS. - - - - - jiameng@chromium.org - - The result of parsing the dim threshold parameter value. Only applicable to - Chrome OS. - - - - - - Removed July 11 2017. - - bengr@chromium.org - rajendrant@chromium.org - - The battery level in percentage when the precache task was started. - - - - - - Removed July 11 2017. - - bengr@chromium.org - rajendrant@chromium.org - - Measures the difference between the battery level percentage when the - precache task is started and ended. This value indicates the possible - battery usage due to the precache task. Logged when the precache task ends, - which could be due to successful completion, time-out, error conditions, max - download limit exceeded, etc. - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - The size in kilobytes occupied by all the entries existing in the cache at - the time of the last precache. - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - Like HttpCache.Pattern but only for requests not made during precaching. - Logged per-request. - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - Like Precache.CacheStatus.NonPrefetch but only for requests which having a - matching URL in the precache. Measures the amount of precache misses due to - expiration or eviction. Logged per-request. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - jamartin@chromium.org - - Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer - not in the user's top visited hosts. See History.TopHostsVisitsByRank for - details on the top hosts computation. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - jamartin@chromium.org - - Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer - in the user's top visited hosts. See History.TopHostsVisitsByRank for - details on the top hosts computation. - - - - - - Removed July 11 2017. - - jamartin@chromium.org - twifkak@chromium.org - - Like HttpCache.Pattern but only for requests made during precaching. Logged - per-request. - - - - - - Removed July 11 2017. - - bengr@chromium.org - - The number of bytes that were downloaded over the network for HTTP/HTTPS - fetches that were not motivated by precaching. Logged per-request. - - - - - - Removed July 11 2017. - - bengr@chromium.org - - The number of bytes that were downloaded because of precaching. Logged - per-request. - - - - - - Removed July 11 2017. - - rajendrant@chromium.org - bengr@chromium.org - - Enumerates the various failure reasons and events of interest for - precaching. The events are persisted when the native library is not loaded, - and recorded when the library loads next time. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - bengr@chromium.org - - A bit vector of reasons why the precache fetch failed to start. Bit values - are documented in the FailureReason Java enum. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - - The minimum resource weight that is fetched in a given precache run. - Reported if the precache completed successfully or was canceled due to the - byte cap, but not if it was cancelled due to an ill-formed manifest or - exceeding the time limit. Reported only if global_ranking is true. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - bengr@chromium.org - - The percent of manifests for which all resources have been downloaded. - Logged per prefetch run. - - - - - - Removed July 29 2015. - - twifkak@chromium.org - bengr@chromium.org - - The total number of response bytes received from all prefetch requests, - including config, manifests, and resources. Logged per prefetch run. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - - The total number of response bytes in 24 hours received over the network - from all prefetch requests, including config, manifests, and resources. - Logged during the next precache run after the 24 hours has elapsed. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - bengr@chromium.org - - The total number of response bytes received over the network from all - prefetch requests, including config, manifests, and resources. Logged per - prefetch run. - - - - - - Removed July 11 2017. - - rajendrant@chromium.org - bengr@chromium.org - - The total number of response bytes received over the network for a wasted - resource precache fetch. Logged when a partially downloaded resource - precache fetch gets cancelled due to per-resource size limit or max precache - size limit. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - bengr@chromium.org - - The total number of response bytes contained in all prefetch requests, - including config, manifests, and resources. Logged per prefetch run. - - - - - - Removed July 11 2017. - - twifkak@chromium.org - bengr@chromium.org - - The time, in milliseconds, to complete a prefetch run. Only applies to - non-cancelled runs (those for which PercentCompleted is 100). - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - The freshness lifetimes of the resources that were precached from the moment - they were fetched or revalidated as described in RFC 2616 13.2.4. Logged per - precache request. - - - - - - Removed March 7 2017. - - twifkak@chromium.org - bengr@chromium.org - - The latency for requests that were not made during precaching. Logged - per-request. - - - - - - Removed March 7 2017. - - twifkak@chromium.org - bengr@chromium.org - - Like Precache.Latency.NonPrefetch, but limited to requests with a referer - not in the user's top visited hosts. See History.TopHostsVisitsByRank for - details on the top hosts computation. - - - - - - Removed March 7 2017. - - twifkak@chromium.org - bengr@chromium.org - - Like Precache.Latency.NonPrefetch, but limited to requests with a referer in - the user's top visited hosts. See History.TopHostsVisitsByRank for details - on the top hosts computation. - - - - - - Removed March 7 2017. - - twifkak@chromium.org - bengr@chromium.org - - The latency for requests that were made during precaching. Logged - per-request. - - - - - - Removed July 11 2017. - - rajendrant@chromium.org - bengr@chromium.org - - The time between successive precache periodic GCM task invocations. When - precache task is started, the time interval from previous task invocation is - logged. - - - - - - Removed July 11 2017. - - bengr@chromium.org - - The number of bytes during user browsing that were served from the cache, - but would have been downloaded over a network if precaching was disabled. - Logged per-request. - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - The freshness lifetimes (RFC 2616 13.2.4) of the resources that were - precached and later used (and thus served from the cache). This is computed - at serving time and thus possibly different from the precached value if the - cache entry was revalidated. Logged per-request but only once per URL and - precaching cycle (as Precache.Saved). - - - - - - Removed July 11 2017. - - jamartin@chromium.org - bengr@chromium.org - - The time between the the beginning of the last precache session and each of - the URL fetches made by the user ever since. Logged per-request. - - - - - - Removed March 31 2020. - - dom@chromium.org - yhirano@chromium.org - yoavweiss@chromium.org - - Recorded when a prefetch request is made, and when a prefetch request is - redirected. Specifically, PrefetchURLLoader::PrefetchURLLoader records - "Prefetch request made", and PrefetchURLLoader::FollowRedirect - records one of the two redirection values. This is to collect data on how - often prefetch requests experience redirects. Note that when the - PrefetchRedirectError flag is enabled, no events are recorded. We do not - want to interact with this histogram when we're experimenting with the - redirect mode for prefetch requests. - - - - - horo@chromium.org - webpackage-dev@chromium.org - - The body size of each prefetched signed exchanges in - PrefetchedSignedExchangeCache which is attached to a frame. Recorded when - the frame is deleted or is navigated to different document. - - - - - horo@chromium.org - webpackage-dev@chromium.org - - The total body size of prefetched signed exchanges in - PrefetchedSignedExchangeCache which is attached to a frame. This metric is - recorded when the frame is deleted or is navigated to different document. - This is not recorded when there is no prefetched signed exchanges. - - - - - horo@chromium.org - webpackage-dev@chromium.org - - The number of prefetched signed exchanges in PrefetchedSignedExchangeCache - which is attached to a frame. This metric is recorded when the frame is - deleted or is navigated to different document. This is not recorded when - there is no prefetched signed exchanges. - - - - - horo@chromium.org - webpackage-dev@chromium.org - - The total headers size of prefetched signed exchanges including outer - response headers and inner response headers in PrefetchedSignedExchangeCache - which is attached to a frame. This metric is recorded when the frame is - deleted or is navigated to different document. This is not recorded when - there is no prefetched signed exchanges. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - The amount of time that elapsed during CreateProfilePrefs. - - - - - Removed as of 7/2019. No longer needed. - - petewil@chromium.org - - Count events where Network Prediction was enabled or disabled. - - - - - holte@chromium.org - The status when loading PersistedLogs from Prefs. - - - - csharp@chromium.org - - Enumeration of errors that happened when reading Preferences files. - - - - - - Removed 5/25/2016 in favor of PreloadScanner.Counts2 - - csharrison@chromium.org - The number of preloads generated by the preload scanner. - - - - - Removed 5/25/2016 in favor of PreloadScanner.Counts2.Miss - - csharrison@chromium.org - - The number of unused preloads generated by the preload scanner. Note that - some link rel preloads are not referenced until after this point, so they - will be falsely marked as preload misses. These will show up in the Raw - bucket. - - - - - - Removed Feb 2018, no longer useful. - - csharrison@chromium.org - The number of preloads generated by the preload scanner. - - - - - Removed Feb 2018, no longer useful. - - csharrison@chromium.org - - The number of unused preloads generated by the preload scanner. Note that - some link rel preloads are not referenced until after this point, so they - will be falsely marked as preload misses. - - - - - - DocumentWriteEvaluator was removed in 07/2017 - - csharrison@chromium.org - - Time spent executing a script tag in the blink preload scanner, for the - purpose of preloading scripts that will be fetched via a call to - document.write. The execution failed to generate a preload request. - - - - - - DocumentWriteEvaluator was removed in 07/2017 - - csharrison@chromium.org - - Time spent executing a script tag in the blink preload scanner, for the - purpose of preloading scripts that will be fetched via a call to - document.write. The execution successfully resulted in a preload request. - - - - - - DocumentWriteEvaluator was removed in 07/2017 - - csharrison@chromium.org - - The reason a particular inline script was blocked from evaluation. - - - - - - DocumentWriteEvaluator was removed in 07/2017 - - csharrison@chromium.org - - Time spent initializing a new V8 context for the purpose of evaluating it - and preloading document.written strings. - - - - - - No longer needed - - csharrison@chromium.org - - The length of the inline script that is being considered for document write - evaluation. - - - - - - Removed August 2018 - - csharrison@chromium.org - - The number of preloads generated by scanning an external preloaded CSS - resource. As of 4/25/2016 this only includes @import declarations. - - - - - - Removed August 2018 - - csharrison@chromium.org - - Microseconds it took to scan the first chunk of external CSS for preloads. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed May 2018 - - csharrison@chromium.org - - The time between preload discovery and when the resource is actually - referenced. This is implemented by marking when a preload is discovered by - the scanner, and when it has its first ResourceClient added to it. Note that - for link rel preloads, this tracks the time from scanner discory to DOM - discovery of the link declaration, not the actual resource. - - - - - - Removed May 2018 - - csharrison@chromium.org - - The time between preload discovery and when the first bytes of the response - data arrive. - - - - - - Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). - - davidben@chromium.org - pasko@chromium.org - - Time from when a prerendered page is abandoned to when it is first used due - to user navigation. If the page is swapped before begin abandoned, a zero is - recorded. - - - - - - Removed March 13 2015. - - pasko@chromium.org - - Enumeration of what types of cookies were sent for a prerender. - - - - - - Removed March 13 2015. - - pasko@chromium.org - Enumeration of what cookie actions a prerender caused. - - - - - Removed Dec 12 2014. - - - Enumeration of what events related to prerendering have occurred. - - - - - - deprecated May 10 2012 - - Please list the metric's owners. Add more owner tags as needed. - Hover Event counts for prerendering. - - - - ryansturm@chromium.org - tbansal@chromium.org - - Final status for prerender pages - either success, or why it was canceled. - - - - - - deprecated 2016-05-12 - - - Final status for prerender pages - either success, or why it was canceled. - This is for the MatchComplete set of pages (including some pages that were - not actually prerendered), to match the control group. - - - - - - Removed Jan 14 2014. - - Please list the metric's owners. Add more owner tags as needed. - - For prerenders that are swapped in, the percentage of pixels that is already - final at swap-in time compared to when the spinner stops. - - - - - - deprecated May 10 2012 - - Please list the metric's owners. Add more owner tags as needed. - - Duration that a user hovers a link before clicking on it. - - This is recorded for all pages loaded in a session. - - - - - - deprecated May 10 2012 - - Please list the metric's owners. Add more owner tags as needed. - - Duration that the mouse pointer hovers on a link before the mouse pointer - moves off of it. - - This is recorded for all pages loaded in a session. - - - - - - Removed April 2015 - - pasko@chromium.org - - Enumeration of what events related to the local predictor have occurred - - - - - - Removed April 2015 - - pasko@chromium.org - - Time to perform the LoggedIn Lookup for the local predictor. This operation - checks whether a user is likely logged into a page that we would like to - prerender. - - - - - - Removed April 2015 - - pasko@chromium.org - - The PrerenderLocalPredictor uses local browsing history and the prerender - service to predict pages likely visited soon. Some of these URLs are - prefetched. When such prefetched likely next pages are visited, this - histogram records the PLT for such pages. In particular, this also happens - if prefetch is actually disabled, allowing (by pivoting on whether or not - prefetch is enabled) to compare the effect of prefetch on PLT. - - - - - - Removed April 2015 - - pasko@chromium.org - - Time to perform the Service Lookup for the local predictor. This operation - queries a Google service to obtain pages to prerender, as well as whether - prerender candidate pages are likely safe for prerendering. - - - - - - Removed April 2015 - - pasko@chromium.org - - Time from when a prerendered page is started to when it is first used due to - user navigation. If the page is never used, it is not included in this - histogram. This only refers to prerenders based on the local predictor. - - - - - - Removed April 2015 - - pasko@chromium.org - - Time to perform the URL Lookup for the local predictor. This operation - retrieves from the user's local browsing history the URLs corresponding to - URLIDs. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - The transition type for each new visit as recorded in the local visits - database. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - Size of the local visits database (number of entries). - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - Enumeration of what events related to local visits have occurred - - - - - - Removed as of 10/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Previous version of the Prerender.PagespeedHeader.* histograms. - - - - - - Removed May 13th 2014, use Prerender.NetworkBytesTotalForProfile instead. - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents - deletion. Includes prerender bytes. Bytes are only counted when prerendering - is enabled and not in a control group. The sum of the distribution for a - single user represents all of that user's network transfers for resource for - that time period while prerendering was enabled. - - - - - - Removed May 13th 2014, use Prerender.NetworkBytes.Used instead. - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been - used). - - - - - - Removed May 13th 2014, use Prerender.NetworkBytes.Wasted instead. - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead) for a prerender that was not used. - - - - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents - deletion. Includes prerender bytes. Bytes are only counted when prerendering - is enabled and not in a control group. The sum of the distribution for a - single user represents all of that user's network transfers for resource for - that time period while prerendering was enabled. - - - - - - Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been - used). - - - - - hajimehoshi@chromium.org - jkarlin@chromium.org - kouhei@chromium.org - - Number of bytes transferred on the network for URLRequests (not including - HTTP/TLS/TCP/IP overhead) for a prerender that was not used. All - nostate-prefetch bytes are currently counted as wasted because it is hard to - track byte use in HTTP cache. - - - - - - Removed December 28, 2016, use Prerender.PrefetchAge instead. - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - Time between the prefetch and the actual load of the page. - - - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Length of the redirect chain for main resources loaded by NoStatePrefetch. - Recorded when the final response in the chain is received. - - - - - jam@chromium.org - - Time a prefetch renderer is kept alive after parsing to wait for - subresources to finish loading. - - - - - jam@chromium.org - - Time between prefetch renderer startup and when parsing is complete. - - - - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Type of responses received by NoStatePrefetch, distinguishing cacheable - resources from no-store resources, and main resources from sub-resources. - Recorded when a response is received, including on each redirect. - - - - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Length of the redirect chain for sub-resources loaded by NoStatePrefetch. - Recorded when the final response in the chain is received. - - - - - - Removed 2020-04, as NoStatePrefetch is launched everywhere. - - pasko@chromium.org - - A boolean that indicates whether the Omnibox navigation being committed - could have been prerendered by the Omnibox Prerender system. This provides - an upper bound for Prerender.OmniboxNavigationsUsedPrerenderCount and allows - the potential for Omnibox Prerendering coverage to be understood. If Omnibox - Prerendering is disabled, this histogram will register a 'false' entry. The - total count is the equivalent of the deprecated - NetworkActionPredictor.NavigationCount histogram. - - - - - - Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). - - pasko@chromium.org - - The number of navigations that use a prerender initiated from the Omnibox. - The count is incremented when the Prerendered tab is swapped in if the - Prerender was initiated by the Omnibox, which obviously requires - Prerendering from the Omnibox to be enabled. - - - - - - Removed 2017-09. - - pasko@chromium.org - - The number of prerenders initiated from the Omnibox. This is incremented - when the NetworkActionPredictor suggests Prerendering as an optimal strategy - given the text the user has entered and the Autocomplete suggestion - currently selected. It is only incremented if Prerendering from the Omnibox - is enabled. - - - - - - Removed April 2018 - - pasko@chromium.org - - The number of responses received bucketed into the range [0,4]: bucket 0 is - the total number of responses received; bucket 1 is the number of responses - received with an X-Mod-Pagespeed header [indicating a mod_pagespeed server]; - bucket 2 is the number of responses received with an X-Page-Speed header and - a header value in the X-Mod-Pagespeed format (a.b.c.d-e) [indicating an - ngx_pagespeed server]; bucket 3 is the number of responses received with an - X-Page-Speed header and a header value in the PageSpeed Service format - (a_b_c) [indicating a PSS server]; and bucket 4 is the number of responses - received with an X-Page-Speed header and a header value in neither of the - preceding formats [indicating some other server; IISpeed is the only known - one at this stage]. - - - - - - Removed April 2018 - - pasko@chromium.org - - The number of responses received that either have an X-Mod-Pagespeed header - or have an X-Page-Speed header with a value in the X-Mod-Pagespeed format - (a.b.c.d-e), bucketed into the range [1,99]: bucket 1 is for header values - that aren't in the a.b.c.d-e format, the remaining buckets are an encoding - of the value: 2 + 2 * (max(c, 10) - 10) + (d > 1 ? 1 : 0). The rationale - is that 'c' is incremented with each new release and 'd' is initially 0 but - is incremented for each patch to a release. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - Types of pages rendered. - - - - - deprecated March 30, 2015 - - pasko@chromium.org - - Indicates whether the user has ever visited (in the past) a URL for which a - prerender is launched. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLT_ContentPrefetchPrerenderControl. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This particular histogram is for all page loads for users who do not have - prerendering enabled. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLTMatched_ContentPrefetchPrerenderControl. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This particular histogram is only for pages that would have been prerendered - if the user had prerender enabled. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLTMatched_ContentPrefetchPrerender. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This particular histogram is for all prerendered page loads for users who - have prerender enabled. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLT_ContentPrefetchPrerender. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This particular histogram is for all page loads for users who have - prerendering enabled. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLTWindowed_ContentPrefetchPrerenderControl. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This particular histogram is for all page loads within 30 seconds after a - prefetch tag is seen for users who do not have prerendering enabled. - - - - - - Removed 03/24/11. Replaced by - Prerender.PerceivedPLTWindowed_ContentPrefetchPrerender. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load pre navigation. - - This particular histogram is for all page loads within 30 seconds after a - prefetch tag is seen for users who have prerendering enabled. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded for all pages loaded in a session. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded for the first page load completing immediately after a - prerender. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - "FirstAfterMiss" means the first pageload after a prerender miss. - There are two types: Any, and Non-overlapping. The latter only applies to - page loads initiated after the prerender. This variable records cases where - only Any triggered. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - "FirstAfterMiss" means the first pageload after a prerender miss. - There are two types: Any, and Non-overlapping. The latter only applies to - page loads initiated after the prerender. This variable records cases where - both triggered. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded for the first page load completing immediately after a - prerender, but which has also started after the prerender has been - initiated. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - "FirstAfterMiss" means the first pageload after a prerender miss. - There are two types: Any, and Non-overlapping. The latter only applies to - page loads initiated after the prerender. This variable records cases where - only Non-overlapping triggered. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded only for prerendered pages, or for pages which would have - been prerendered in the control case. - - - - - - Removed August 2016 - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded only for prerendered pages, or for pages which would have - been prerendered in the control case. - - In MatchedComplete, the prerender group also contains cancelled prerenders, - so as to produce a perfect match of page views attributed this group in the - prerender group with those attributed to this group in the control group. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded for all page loads which happen within 30 seconds after a - prefetch tag is observed. - - - - - - Removed 2017-03. - - pasko@chromium.org - - Time from when a user navigates to a page to when it loads. Since the pages - may start loading before the user navigates to it, this does not include any - portion of load prior to navigation. - - This is recorded for all page loads which happen within 30 seconds after a - prefetch tag is observed and which do not correspond to a prerender tag. - - - - - - Obsoleted in Feb 2019. - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Whether the perceived Time to First Contentful Paint (TTFCP) was recorded - successfully for a prerendered page. Since a prerendered page will start - loading before a user navigates to it, the perceived TTFCP does not include - an time prior to the user navigation. If true, there is an associated - PrefetchTTFCP that records the TTFCP from the swapped-in navigation start. - If false, no PrefetchTTFCP was recorded. - - - - - - Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). - - pasko@chromium.org - - For prerenders that are swapped in, the percentage of the time from load - start until the onload event fires that has elapsed at the time of the - swapin. - - - - - - Removed 2020-04. - - pasko@chromium.org - - How long the cleanup portion of PrerenderManager::PeriodicCleanup takes, to - measure jank. - - - - - - Removed 2020-04. - - pasko@chromium.org - - How long the resource check portion of PrerenderManager::PeriodicCleanup - takes, to measure jank. - - - - - - Deprecated July 2020 - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Time between a prefetch or effective prefetch and the actual load of the - page. For NoState prefetch, this is the time of the actual prefetch. For - prerendering, it is the time that prerender began. For control groups in - NoState prefetch experiments, it is the time that prefetch would have - occurred. - - - - - - Deprecated July 2020 - - droger@chromium.org - mattcary@chromium.org - pasko@chromium.org - - Time to first contentful paint (TTFCP) for navigations related to prefetch - (including prerender, no-state prefetch, and associated experiments). This - measures user-visible TTFCP. For no-state prefetch this is standard - navigation-to-FCP; for prerender this is the time from navigation start when - the prerender is swapped in to FCP. - - - - - - Removed 2017-03. - - pasko@chromium.org - - After launching a prerender, how many simultanious prerenders are recorded - as running, out of a maximum of three. - - - - - gambard@chromium.org - justincohen@chromium.org - - Whether the load was completed when the pre-render was used. If the - prerender is cancelled, this is not logged. Only on iOS. - - - - - justincohen@chromium.org - - Whether or not a successful prerender happens on a NTP with no history. - - - - - justincohen@chromium.org - - The last comitted index before a successful preload is committed. Recorded - only on iOS. - - - - - - Removed 2017-03. - - pasko@chromium.org - - For prerenders that finish loading before they are ever swapped in, their - page load time until the onload event fires. - - - - - ryansturm@chromium.org - tbansal@chromium.org - - The number of sessions that have at least X successful prerenders. Recorded - only on iOS since 2017-09. - - - - - - Removed 2020-05-07 - - justincohen@chromium.org - - This is the time from when a prerendered page begins to load to when it is - swapped in as the main page load. Recorded when the swap occurs, only on - iOS. - - - - - gambard@chromium.org - justincohen@chromium.org - - This is the time from when a prerendered page begins to load to when it is - swapped in as the main page load or to when the pre-loaded page is fully - loaded, whichever came first. Recorded when the swap occurs, only on iOS. - - - - - - Removed 2020-04. - - pasko@chromium.org - - For each prerender link added to a document, records the rel types present - on the link element. - - - - - - Removed 2020-04. - - pasko@chromium.org - - For each prerender in a document which starts prerendering, records the rel - types present on the link element. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - This is the time from when a prerendered page finishes loading to when it is - displayed, as measured by the renderer process. When a page is displayed - before it finishes loading, no value is recorded in this histogram. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - Perceived load time of a page, as measured by the renderer process. For - non-prerendered pages, this is just BeginToFinish. For displayed prerendered - pages, this is the time from when the prerendered page is moved into a - TabContents until finish. "Finish" == after onload() and all - resources are loaded. Note that this is 0 if the loading finishes before the - page is moved into a TabContents. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - Perceived load time of a prerendered page that is displayed, as measured by - the renderer process. This is the time from when the prerendered page is - moved into a TabContents until finish. "Finish" == after onload() - and all resources are loaded. Note that this is 0 if the loading finishes - before the page is moved into a TabContents. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - - The time elapsed between when the prerendering of a page starts and when the - page is displayed, as measured by the renderer process. Prerendered pages - discarded without being displayed are excluded from this count. - - - - - - Removed 2020-04. - - pasko@chromium.org - - The detailed reason why a prerender is canceled with - FINAL_STATUS_UNSUPPORTED_SCHEME - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - Enumeration of how prerender was used per session. - - - - - Removed Dec 12 2014. - - pasko@chromium.org - Time to perform the session storage namespace merge. - - - - - Removed April 2015 - - pasko@chromium.org - - For simulated local browsing prerendering, the baseline PLT of pages without - any prerendering for pages that would be prerendered. - - - - - - Removed April 2015 - - pasko@chromium.org - - For simulated local browsing prerendering, the estimated PLT of pages with - prerendering enabled for pages that would be prerendered. - - - - - - Obsoleted in Dec 2019. - - pasko@chromium.org - - A boolean that indicates how often we suppress a dialog from a tab when - swapping it with a prerender. - - - - - pasko@chromium.org - - A boolean that indicates how often we fail to delete an old prerendered tab - before the timeout. - - - - - - Removed April 2015 - - pasko@chromium.org - - Enumeration of what events related to the TabHelper class have occurred. - - - - - - Removed 2017-09. - - pasko@chromium.org - Time between subsequent prerender requests. - - - - - Removed 2017-09. - - pasko@chromium.org - - The time elapsed between the most recent visit to a URL and when an - attempted prerender of the same URL is cancelled with - FINAL_STATUS_RECENTLY_VISITED. - - - - - - deprecated Nov 16 2012 - - Please list the metric's owners. Add more owner tags as needed. - Duration that a user hovers a link before clicking on it. - - - - - deprecated Nov 16 2012. See Prerender.TimeUntilUsed2, which has a larger - range. - - Please list the metric's owners. Add more owner tags as needed. - - Time from when a prerendered page is started to when it is first used due to - user navigation. If the page is never used, it is not included in this - histogram. - - - - - - Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). - - pasko@chromium.org - - Time from when a prerendered page is started to when it is first used due to - user navigation. If the page is never used, it is not included in this - histogram. - - - - - dougarnett@chromium.org - mcrouse@chromium.org - src/components/data_reduction_proxy/OWNERS - - Blocked previews due to Cache-Control:no-transform directive. - - - - - ryansturm@chromium.org - - The actual data used for a page load using a preview optimization. - - - - - - Functionality removed in M77. - - bengr@chromium.org - tbansal@chromium.org - - User interactions with the Lo-Fi context menu options. These include: - - Displays and clicks on the "Load image" and "Load - images" context menu options. Count of pages where the user has clicked - "Load image" at least once. - - - - - ryansturm@chromium.org - - The estimated amount that the content was inflated for a page load using a - previews optimization. Recorded when a page load using a previews - optimization inflates the data used. - - - - - ryansturm@chromium.org - - The estimated percent of data used that a page load would have otherwise - cost for a page load using a previews optimization. Recorded when a page - load using a previews optimization inflates the data used. - - - - - ryansturm@chromium.org - - The estimated data savings for a page load using a previews optimization. - Recorded when a page load using a previews optimization reduces the data - used. - - - - - ryansturm@chromium.org - - The estimated percent of data savings for a page load using a previews - optimization. Recorded when a page load using a previews optimization - reduces the data used. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - Records true when a URL matches the regex of denylist. Recorded at the time - of navigation commit. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - Records true when a redirect loop is detected when defer all script is in - use. Recorded at the time of navigation commit. - - - - - ryansturm@chromium.org - - When evaluating whether to show a user a preview, the preview might be - disallowed for various reasons. If the preview is disallowed, then this - reports the reason for disallowing it. If the preview is allowed, then this - generally reports "Previews Allowed". It may instead report - "Previews Allowed without server rule check" for a preview that - expects to check server rules but they are not enabled. Recorded throughout - navigation at the beginning of each navigation, after each redirect, and - during commit. - - - - - - Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in - 07/2019. - - jegray@chromium.org - - Records the result of loading the metadata while initializing the - HintCacheLevelDBStore. - - - - - - Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in - 07/2019. - - jegray@chromium.org - - Records each status change within the HintCacheLevelDBStore. - - - - - - Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in - 07/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records that a fetched hint loaded from the store has expired. If expired, - the hint is not provided. - - - - - - Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.HostCount in - 06/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts selected for sending a OnePlatform client hint - request. This will be captured when any OnePlatform client hint request is - initiated. - - - - - - Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.NetErrorCode in - 06/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - Net error codes for HintsFetch requests to the Optimization Guide Service on - success and failure. - - - - - - Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.Status in - 06/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - For each HintsFetch request to the Optimization Guide Service, log the HTTP - response code on success and failure. - - - - - - Replaced by - OptimizationGuide.HintsFetcher.TopHostProvider.BlacklistSize.OnInitialize in - 06/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts placed on the HintsFetcherTopHostBlacklist when - it is initialized. - - - - - - Replaced by - OptimizationGuide.HintsFetcher.TopHostProvider.BlacklistSize.OnRequest in - 06/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the number of hosts on the HintsFetcherTopHostBlacklist when top - hosts are requested. - - - - - - Removed in M76. - - bengr@chromium.org - tbansal@chromium.org - - User interactions with the previews "Saved data" infobar. These - include: - - Displays of the infobar and clicks on the "Load original" link. - Whether the infobar was dismissed by navigation or the user clicking on - "X" close button. - - - - - - Replaced by Previews.StalePreviewTimestampShown as of 09/2018. - - megjablon@chromium.org - - Whether the timestamp for a stale preview was shown on the infobar. If the - timestamp was not shown, states the reason why. - - - - - robertogden@chromium.org - src/components/data_reduction_proxy/OWNERS - - User interactions with the HTTPS Server Previews notification InfoBar. - - - - - - Offline Previews functionality removed in M86. - - robertogden@chromium.org - tbansal@chromium.org - - Whether or not an offline preview that was committed showed an error page. - This metric is recorded every time an offline preview is committed. - - - - - - Offline Previews functionality removed in M86. - - robertogden@chromium.org - ryansturm@chromium.org - - Whether or not the navigated URL was allowed to trigger an offline preview. - This is done by checking an in-memory cache of all available offline - previews which is designed to prevent false positive triggering. This metric - is recorded on every preview eligible navigation when the - OfflinePreviewsFalsePositivePrevention feature is enabled. - - - - - - Offline Previews functionality removed in M86. - - robertogden@chromium.org - ryansturm@chromium.org - - The number of entries in the false positive prevention pref. This is - recorded every time we update the pref from a DB query, at most once per - session. - - - - - robertogden@chromium.org - User interactions with the Previews Android Omnibox UI. - - - - - Removed July 2019. - - robertogden@chromium.org - - Whether the verbose status string was shown on a Preview page. This is - recorded on every transition from a non-preview page to a preview page. An - entry of false means that the Previews Icon appeared without the - "Lite" string only because there was not enough room to show the - string. - - Note that it is possible for the Lite string to not be shown on the page - after true is recorded if the user rotates their device or enters - multi-window mode while viewing the page, or the converse. - - - - - - Removed in favor of OptimizationGuide.OptimizationFilterStatus as of - 07/2019. - - dougarnett@chromium.org - - Status of processing OptimizationFilter configurations for server-provided - blacklists. Recorded when the PreviewsOptimizationGuide receives a - notification to process hints. - - - - - - Removed in favor of OptimizationGuide.HintCache.FetchedHint.TimeToExpiration - as of 08/2019. - - mcrouse@chromium.org - dougarnett@chromium.org - - The remaining time a fetched hint that was loaded for use has before it - expires and is removed from the hint cache store. - - - - - - Removed in favor of OptimizationGuide.HintCache.HasHint.AtCommit as of - 08/2019. - - dougarnett@chromium.org - - Records the effective connection type when the optimization guide hint cache - has a hint entry for a URL's host at commit time. - - - - - - Removed in favor of OptimizationGuide.HintCache.HasHint.BeforeCommit as of - 08/2019. - - dougarnett@chromium.org - - Records the effective connection type when the optimization guide hint cache - has a hint entry for a URL's host before commit time (e.g., at original - navigation time or redirected navigation time). - - - - - - Replaced by OptimizationGuide.HintCache.HintType.Loaded in 07/19. - - mcrouse@chromium.org - dougarnett@chromium.org - - Records the store entry type of a hint when it is loaded from the hint cache - store. - - - - - - Removed in favor of OptimizationGuide.HintCache.HostMatch.AtCommit as of - 08/2019. - - dougarnett@chromium.org - - Records the effective connection type when the optimization guide hint cache - has a loaded hint entry matching a URL's host at commit time. This is - recorded regardless of whether an associated preview type is allowed for the - navigation or not. If no associated preview type is allowed, the hint will - not be loaded from a backing store, so this will only capture matches for - in-memory hints. - - - - - - Removed in favor of OptimizationGuide.HintCache.PageMatch.AtCommit as of - 08/2019. - - dougarnett@chromium.org - - Records the effective connection type when the optimization guide hint cache - has a loaded page hint for a URL at commit time. This is recorded regardless - of whether an associated preview type is allowed for the navigation or not. - If no associated preview type is allowed, the hint will not be loaded from a - backing store, so this will only capture matches for in-memory hints. - - - - - - No longer used as of 06/2018. - - ryansturm@chromium.org - - The number of rows in the Previews opt out SQLite table at profile startup. - - - - - - No longer used as of 06/2018. - - ryansturm@chromium.org - - The SQLite error code that the previews opt out store saw when trying to - open the SQLite database. This is logged when an unexpected error occurs - when trying to open the database file. - - - - - ryansturm@chromium.org - - Whether the user chose to reload the original page when shown a preview. - - - - - ryansturm@chromium.org - - The estimated content length of a page load using a preview optimization. - - - - - robertogden@chromium.org - Records why the page load ended on a given preview type. - - - - - Merged with OptimizationGuide.ProcessHintsResult in 07/2019. - - dougarnett@chromium.org - - Whether processing the previews hints succeeded and if any previews hints - were found. Recorded when the PreviewsOptimizationGuide receives a - notification to process hints. - - - - - - Removed in M84. - - robertogden@chromium.org - - The reason that a navigation is blacklisted from loading a server lite page - preview by a dynamic blacklist. Recorded only after the observed navigation - has passed static eligibility checks. - - - - - - Removed in M84. - - robertogden@chromium.org - tombergan@chromium.org - src/components/data_reduction_proxy/OWNERS - - Whether or not the server directed Chrome to blacklist the requested host on - a bypass response. - - - - - - Replaced January 2019 by Previews.ServerLitePage.Penalty.* - - robertogden@chromium.org - - The time spent on a navigation request that loaded a fallback signal from - the lite page previews server. This does not include any penalty incurred - because of network errors. - - - - - - Removed in M84. - - robertogden@chromium.org - - The reasons that a navigation is not eligible to be shown a server lite page - preview by static eligibility checks. Each check is evaluated on every - observed navigation when the feature is enabled. - - - - - - Removed November 2018 when PLM support was reverted. - - robertogden@chromium.org - - Every time a navigation is restarted on account of this preview we attempt - to report the cumulative total penalty to page load metrics. This histogram - tracks penalties that were not successfully reported. The penalty is the - amount of time between the navigation start of the original (i.e.: - user-initiated) navigation and the current navigation when this histogram is - reported. This histogram is reported at the start of every navigation for - every navigation seen by the Lite Page Redirect Navigation Throttle. - - - - - - Removed in M79. - - robertogden@chromium.org - - The lost time spent attempting a server lite page via canceling and - restarting navigations. This value is the difference between the final - navigation's start time and the start time of the original navigation. This - metric is recorded everytime the Previews NavigationThrottle acts on a - response, whether that is from the previews server or a network error. - - This histogram is only recorded in M73 for the non-URLLoader implementation - of this feature. For M72, refer to - Previews.ServerLitePage.HttpOnlyFallbackPenalty which records this penalty - for failure statuses only. - - - - - - Removed in M84. - - robertogden@chromium.org - tbansal@chromium.org - - Recorded whenever lite page preview predictor preconnects to a URL. True is - recorded when the URL that is preconnected is for the lite pages previews - server, False is when the origin is preconnected. - - - - - - Removed in M84. - - robertogden@chromium.org - tbansal@chromium.org - - Recorded whenever the lite page preview predictor state is changed. True is - recorded when preresolving or preconnecting starts and False is recorded - when it stops. - - - - - - Removed in M84. - - robertogden@chromium.org - tbansal@chromium.org - - Recorded whenever lite page preview preresolver preresolves a URL. True is - recorded when the URL that is preresolved is for the lite pages previews - server, False is when the origin is preresolved. - - - - - - Removed November 2018 when PLM support was reverted. - - robertogden@chromium.org - - Every time a navigation is restarted on account of this preview we attempt - to report the cumulative total penalty to page load metrics. This histogram - tracks penalties that were successfully reported. The penalty is the amount - of time between the navigation start of the original (i.e.: user-initiated) - navigation and the current navigation when this histogram is reported. This - histogram is reported at the start of every navigation for every navigation - seen by the Lite Page Redirect Navigation Throttle. - - - - - - Removed in favor of - Previews.ServerLitePage.ServerNetError.(After|Before)Commit - - robertogden@chromium.org - ryansturm@chromium.org - - The net error from connecting to the previews server. Recorded every time a - connection to the server is finished. - - - - - - Removed in M84. - - robertogden@chromium.org - ryansturm@chromium.org - - The net error from connecting to the previews server after commit. Recorded - every time a connection to the server is finished after commit. - - - - - - Removed in M84. - - robertogden@chromium.org - ryansturm@chromium.org - - The net error from connecting to the previews server before commit. Recorded - every time a connection to the server is finished before commit. - - - - - - Removed in M84. - - robertogden@chromium.org - - The type of response given by the previews server when a server lite page - preview was triggered. - - - - - - Replaced by Previews.ServerLitePage.PredictorToggled. - - robertogden@chromium.org - tbansal@chromium.org - - Recorded whenever the lite page preview preresolver state is changed. True - is recorded when preresolving starts and False is recorded when it stops. - - - - - - Removed in M79. - - robertogden@chromium.org - - Whether or not the server lite page preview is triggered. Recorded on every - observed navigation when the feature is enabled. - - - - - - Removed in M84. - - ryansturm@chromium.org - - Whether or not the server lite page preview was attempted during a - navigation. Recorded when the lite page URLLoader feature is enabled, during - any leg of the navigation (redirects trigger recording the histogram). - - - - - - Stale timestamp functionality removed in M86. - - robertogden@chromium.org - - Whether the timestamp for a stale preview was shown on the UI. If the - timestamp was not shown, states the reason why. - - - - - - Replaced by Previews.Triggered.EffectiveConnectionType2 as of 01/2019. - - dougarnett@chromium.org - - Records the effective connection type of a navigation that triggers a - preview. This is captured for slow page preview types - that is, ones that - support variable thresholds depending on matching a page pattern in the - optimization guide hints. - - - - - dougarnett@chromium.org - mcrouse@chromium.org - src/components/data_reduction_proxy/OWNERS - - Records the effective connection type of a navigation that triggers a - preview. This is captured at commit time but uses the effective connection - type from the beginning of the navigation. - - - - - - Removed 06/2017 as part of crbug.com/734161. - - thestig@chromium.org - - Count of events in PrinterService on Chrome OS related to USB printers. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to EMF. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to EMF with - the GDI Text experiment turned on. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to EMF with - the reduced rasterization feature turned on. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to EMF with - the reduced rasterization feature turned on and the GDI Text experiment - turned on. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to level 2 - PostScript. - - - - - thestig@chromium.org - awscreen@chromium.org - - On Windows, the average size of a printed page after converting to level 3 - PostScript. - - - - - thestig@chromium.org - awscreen@chromium.org - - On desktop, the average size of a printed page after converting to PWG - Raster format. - - - - - skau@chromium.org - - Records whether resolution of a .local address via mDNS was successful. The - metric is recorded during attempted setup of a printer discovered via mDNS. - - - - - - Removed 2020-05. - - valleau@chromium.org - skau@chromium.org - - Records the source from which a network printer was configured in Chrome OS - if it was setup automatically with unpopulated make and model fields. Used - to determine the source pathway from which printers without any make and - model information are able to be setup automatically with a PPD. - - - - - - Removed 2020-05. - - valleau@chromium.org - skau@chromium.org - - Records the source from which a USB printer was configured in Chrome OS if - it was setup automatically with unpopulated make and model fields. Used to - determine the source pathway from which printers without any make and model - information are able to be setup automatically with a PPD. - - - - - skau@chromium.org - pawliczek@chromium.org - - Records the highest IPP version reported by a printer when we query the - printer for attributes. Useful to understand the population of printers - currently used. Recorded during printer setup for IPP printers. Recorded - only on ChromeOS. - - - - - - Removed 06/2020 because it is not longer needed (Issue 1046125). - - luum@chromium.org - skau@chromium.org - - Records when a synced printer's invalid PPD reference has been resolved by - stripping off the autoconf flag. Recorded during initial sync across - PrintersSyncBridge. - - - - - vkuzkokov@chromium.org - skau@chromium.org - - Records when advanced attribute is set for a print job. Recorded when print - job is being formed for sending. - - - - - vkuzkokov@chromium.org - skau@chromium.org - - Records the number of advanced capabilities made available by a single - printer. Recorded when attributes are pulled from the printer. - - - - - skau@chromium.org - - Record if the request for IPP attributes was successful during printer - setup. This only occurs for setup attempts of IPP and IPPS printers. - Starting with M79, this is only recorded if the printer was reachable. - - - - - vkuzkokov@chromium.org - skau@chromium.org - - Records the number of advanced attributes used by a single print job. - Recorded when print job is being formed for sending. - - - - - skau@chromium.org - - Record if the request for IPP attributes was successful in reaching the - printer. Recorded during the attempt to setup IPP/IPPS printers. - - - - - jschettler@chromium.org - project-bolton@google.com - - Records the print job duration of a cancelled print job. Includes time spent - in a suspended or error state. Only recorded on Chrome OS. - - - - - jschettler@chromium.org - project-bolton@google.com - - Records the print job duration of a done/completed print job. Includes time - spent in a suspended or error state. Only recorded on Chrome OS. - - - - - skau@chromium.org - - The final status of every print job that was succesfully queued. Only used - on Chrome OS. - - - - - luum@chromium.org - cros-printing-dev@chromium.org - - Records when a synced printer's outdated separate make and model strings - have been migrated to the new merged form. Recorded during initial sync - across PrintersSyncBridge. - - - - - skau@chromium.org - project-bolton@google.com - - The number of detected network printers that have not been saved. Recorded - when the user navigates to the OS Settings Printing page to set up printers. - Only recorded on Chrome OS. - - - - - - Most users do not provide their own PPDs. - - skau@chromium.org - - Records the source of PostScript Printer Description files used during - printer setup. Entries are recorded for every attempted configuration. Only - recorded on Chrome OS. - - - - - jschettler@chromium.org - project-bolton@google.com - - Records the total size of the printed document (PDF) sent to CUPS. Only - recorded on Chrome OS. - - - - - skau@chromium.org - - The protocol for a printer that was added. Used to track printer churn by - protocol. Only on Chrome OS. - - - - - skau@chromium.org - - The protocol for a printer that was removed. Used to track printer churn by - protocol. Only on Chrome OS. - - - - - skau@chromium.org - - The number of printers shown in the discovered printers dialog during - printer set up. Only recorded on Chrome OS. - - - - - skau@chromium.org - - The success or error code for the setup of a CUPS printer. Recorded when - setup is attempted through the settings dialogs. Only recorded on Chrome OS. - - - - - gavinwill@chromium.org - cros-peripherals@google.com - - Records the success outcome of a printer status query to a local printer. - - - - - gavinwill@chromium.org - cros-peripherals@google.com - - Records the status reasons returned by a local printer from a printer status - query. Each returned printer status request can contain multiple status - reasons so summing these buckets will overcount the total # of status - queries. - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - nikitapodguzov@chromium.org - skau@chromium.org - - The number of entries in the print job database. Recorded when the database - is initialized. - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - nikitapodguzov@chromium.org - skau@chromium.org - - The size in bytes of the entry in the print job database. Recorded every - time when new print job is written to the database. - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - nikitapodguzov@chromium.org - skau@chromium.org - - Records the time it takes to fetch compeleted print jobs from the database. - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - nikitapodguzov@chromium.org - skau@chromium.org - - Indicates whether we were successful performing saving print job database - operation. - - - - - - Removed 09/2020 as it is no longer needed for analysis. - - nikitapodguzov@chromium.org - skau@chromium.org - - Indicates whether we were successful performing deleting print jobs database - operation. - - - - - skau@chromium.org - - The size of the print queue when a print job is initially queued. When the - first job is started, a zero is recorded. Only used on Chrome OS. - - - - - jimmyxgong@chromium.org - cros-peripherals@google.com - - Records the entry point of where the Print Management App was launched from - in Chrome OS. Used to track the relative entry points of the app. - - - - - skau@chromium.org - - Records the protocol for a selected printer in Chrome OS. Used to track - usage of the various printer protocols. Since a selection occurs when print - preview is opened, this will count at least one every time that happens if a - CUPS printer was selected. - - - - - - Removed 2020-04. - - valleau@chromium.org - skau@chromium.org - - Records whether a printer supports the - pwg-raster-document-resolution-supported attribute. - - - - - skau@chromium.org - project-bolton@google.com - - The total number of detected network printers. Recorded when the user - navigates to the OS Settings Printing page to set up printers. Only recorded - on Chrome OS. - - - - - dhoss@chromium.org - thestig@chromium.org - - Records instances in which print preview encounters an unknown PPD color - model. - - - - - baileyberro@chromium.org - cros-peripherals@google.com - - Records the source from which a USB printer was configured in Chrome OS. - Used to track relative usage of the various printer setup routes. Only emits - after a successful printer setup. - - - - - skau@chromium.org - luum@chromium.org - - Tracks printer setups with a valid/invalid PpdReference. PpdReferences are - invalid if more than one field is specified. Due to a bug, some invalid - references could be saved in users' profile, track if they need to be - migrated. Recorded during printer install. Only tracked on ChromeOS. - - - - - kdlee@chromium.org - cros-printing-dev@chromium.org - - The success or error code for the setup of a Zeroconf printer. Recorded when - setup is attempted through the settings dialogs. Only recorded on Chrome OS. - Printer setup results go into either this histogram or the - Printing.CUPS.PrinterSetupResult histogram - not both. - - - - - - Removed in 2020-06. kUseFrameAssociatedLoaderFactory has shipped in M83 and - Printing.FrameIsActiveOnCreateLoaderFactory is true in 100% of cases on all - platforms. - - yhirano@chromium.org - lukasza@chromium.org - - Records whether the associated frame is active when - PrepareFrameAndViewForPrint::CreateURLLoaderFactory is called. If it is - always active we want to replace the CreateFailingURLLoaderFactory call with - a DCHECK. - - - - - vkuzkokov@chromium.org - skau@chromium.org - - Records the time it takes to pull capabilities of a single printer from - OS-specific backend. Recorded immediately on completion. - - - - - pawliczek@chromium.org - skau@chromium.org - - Records the number of print servers that must be queried according to - policies. Only non-zero values are recorded. The histogram is emitted when - ExternalPrintServers* policies are loaded and processed. It happens when a - profile is opened or when one of the policies is modified. - - - - - rbpotter@chromium.org - thestig@chromium.org - - Actions performed by the user when the print destination search widget is - shown to the user. - - - - - - Removed 01/2015 as part of crbug.com/278148. - - thestig@chromium.org - - Count of font file formats embeeded in print preview PDFs. These numbers are - biased by what the platforms supports in terms of detection. - - - - - - No longer used as of 09/2017. - - thestig@chromium.org - - Actions performed by the user when the Google Cloud Print add-printers - promotion is shown to the user. - - - - - thestig@chromium.org - dhoss@chromium.org - - Time from when print preview is initiated until the initial preview is sent - to the preview tab for rendering. - - - - - - - thestig@chromium.org - dhoss@chromium.org - - Time from when print preview is initiated until the preview PDF generation - is started. - - - - - - No longer used as of 07/2019. - - nasko@chromium.org - - Logged when a document calls the window.print() API. The boolean value - indicates whether it is invoked by the main frame. It will be false for - documents in subframes. - - - - - thestig@chromium.org - - Count the number of requests received to show the manage printers dialog. - - - - - thestig@chromium.org - dhoss@chromium.org - - Count the total number of printers shown in destination drop down list. - - - - - - No longer used as of 07/2019. - - nasko@chromium.org - - Logged when a document calls the window.print() API in any frame. The - boolean value will be true when the API call is invoked by a document which - is in a process different than the top level document. It will be false in - all other cases. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The page count of the initial print preview, a.k.a. the total number of - pages in documents to be printed. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to PDF and - opened in Preview.app on Mac. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to a cloud - printer. - - - - - - No longer used as of 01/2016. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to a cloud - printer using web dialog. - - - - - - Removed 07/2019. - - rbpotter@chromium.org - thestig@chromium.org - - The final page count (after page selection) of documents printed to Google - Drive. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to PDF. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to a - printer. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to an - extension printer (using printerProvider API). - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed to a privet - printer. - - - - - - Removed 07/2019. - - thestig@chromium.org - - The final page count (after page selection) of documents printed using - system dialog. - - - - - - Removed 07/2019. - - rbpotter@chromium.org - - Actions taken on the PDF viewer inside Print Preview's preview area. - - - - - - Removed 06/2020. - - thestig@chromium.org - Print preview events. - - - - thestig@chromium.org - dmazzoni@chromium.org - - The average size of a page in the printed document when the source is HTML. - - - - - thestig@chromium.org - dhoss@chromium.org - - The average size of a page in the printed document when the source is PDF. - - - - - rbpotter@chromium.org - - Track type of documents printed (HTML vs PDF). Recorded immediately after a - user requests that a document be printed. - - - - - gavinwill@chromium.org - cros-peripherals@google.com - - Records true if the user printed, or false if the user canceled, while being - shown a red/error status for their selected printer on Chrome OS. - - - - - gavinwill@chromium.org - cros-peripherals@google.com - - Records true if the user printed, or false if the user canceled, while being - shown a green/good status for their selected printer on Chrome OS. - - - - - gavinwill@chromium.org - cros-peripherals@google.com - - Records true if the user printed, or false if the user canceled, while being - shown a grey/unknown status for their selected printer on Chrome OS. - - - - - thestig@chromium.org - - Track the popularity of print settings. (Settings when printing to PDF are - excluded from this statistic.) - - - - - rbpotter@chromium.org - thestig@chromium.org - - Actions performed by the user interacting with print settings UI elements. - - - - - thestig@chromium.org - - The number of times regenerate preview requests received before the user - clicked the cancel button. - - - - - thestig@chromium.org - - The number of times regenerate preview requests received before the first - preview data is available. - - - - - thestig@chromium.org - dhoss@chromium.org - - The number of times regenerate preview requests received before the user - clicked the print button. - - - - - - - thestig@chromium.org - dhoss@chromium.org - - Time taken to render and generate PDF for print preview. (Includes time to - reflow the page back to normal, but not the time to reflow the page to - prepare for printing.) - - - - - - - thestig@chromium.org - dhoss@chromium.org - - Time taken to render and generate PDF for print preview divided by the - number of pages. (Includes time to reflow the page back to normal, but not - the time to reflow the page to prepare for printing.) - - - - - thestig@chromium.org - dhoss@chromium.org - - Count how frequently a set of pre-defined print preview errors occur. - - - - - thestig@chromium.org - Time taken to render each PDF page for print preview. - - - - thestig@chromium.org - Time taken to render to PDF for print preview. - - - - - Removed 01/2020. - - alexmos@chromium.org - - The number of cross-site frames contained in a document being printed, as - defined by comparing scheme and eTLD+1. - - - - - - Removed 01/2020. - - alexmos@chromium.org - - The number of cross-site visible frames contained in a document being - printed. - - - - - - Removed 01/2020. - - alexmos@chromium.org - - The number of out-of-process frames contained in a document being printed. - - - - - thestig@chromium.org - - Action taken by the user in the preview tab such as print, cancel, print to - pdf and show advanced print settings dialog. - - - - - msramek@chromium.org - sauski@google.com - - The number of unique cookie domains for which accesses has been recorded for - in the Access Context Audit database. Logged on initialization of the Access - Context Audit DB on 1% of starts. - - - - - msramek@chromium.org - sauski@google.com - - Size of the Access Context Audit database file in KiB. Determined by - directly inspecting the database file. Logged on initialization of the - Access Context Audit DB on 1% of starts. - - - - - msramek@chromium.org - sauski@google.com - - The total number of access records stored in the Access Context Audit - database. Logged on initialization of the Acceess Context Audit DB on 1% of - starts. - - - - - msramek@chromium.org - sauski@google.com - - The number of unique origins associated with origin keyed storage APIs - recorded in the Access Context Audit database. Logged on initialization of - the Access Context Audit DB on 1% of starts. - - - - - msramek@chromium.org - sauski@google.com - - The number of unique top frame origins for which access to storage APIs has - been recorded in the Access Context Audit database. Logged on initialization - of the Acceess Context Audit DB on 1% of starts. - - - - - markusheintz@google.com - msramek@google.com - - Logged each time the user grants a consent for a feature integrated with the - consent auditor. The value indicates which feature. - - - - - markusheintz@google.com - msramek@google.com - - Logged each time the user denies or revokes a consent for a feature - integrated with the consent auditor. The value indicates which feature. - - - - - - Removed as of 4/2018. - - dullweber@google.com - msramek@google.com - - Logs whether the UserEventServiceReady is ready when recording a consent. - This should always be true as the service is created at startup. - - - - - dullweber@chromium.org - huanzhong@chromium.org - - Whether the cookie controls setting is enabled. Recorded at the Profile - startup. - - - - - mkwst@chromium.org - msramek@chromium.org - - Whether the Do Not Track setting is enabled. Recorded at the Profile - startup. - - - - - dullweber@chromium.org - huanzhong@chromium.org - - Records whether third party cookie blocking was enabled for a site on page - load. Only recorded for users who enabled the cookie controls ui. - - - - - - - mkwst@chromium.org - msramek@chromium.org - dullweber@chromium.org - - Whether the third party cookie blocking setting is enabled. Recorded at the - Profile startup. - - Previously recorded as the "ThirdPartyCookieBlockingEnabled" and - "ThirdPartyCookieBlockingDisabled" actions. - - - - - - The check seems to be needed for as long as Windows 7 is supported. Removed - 2020-05. - - pastarmovj@chromium.org - - Measure how often the automatic recognition for terminal services - environment would have incorrectly decided that the job object should be - applied, when it shouldn't have been as dictated by the flag - --allow-no-sanbox-job. This histogram will guide the final removal of the - flag, which will be possible when the number of false values becomes - insignificant. - - - - - forshaw@chromium.org - wfh@chromium.org - - Errors returned while launching sandboxed process on Windows. For decoding - error code please refer to http://goo.gl/fJJiAv. - - - - - forshaw@chromium.org - wfh@chromium.org - - Warnings returned while launching sandboxed process on Windows. For decoding - error code please refer to http://goo.gl/fJJiAv. This will only be logged - when SpawnTarget succeeds with SBOX_ALL_OK but the last warning result does - not equal SBOX_ALL_OK. - - - - - forshaw@chromium.org - wfh@chromium.org - - The warning launch error returned while launching sandboxed process on - Windows. This will only be logged when SpawnTarget succeeds with SBOX_ALL_OK - but the last warning result does not equal SBOX_ALL_OK. - - - - - shrikant@chromium.org - - Errors returned while launching lowbox enabled sandboxed process on Windows. - For decoding error code please refer to http://goo.gl/fJJiAv. - - - - - - Replaced by PolicyGlobalSizeOnSuccess as failure cases were uninteresting. - Removed 2020-04. - - ajgo@chromium.org - src/sandbox/policy/win/OWNERS - - Size of policy global memory used when policy was committed on Windows for - all outcomes. 0 indicates that no rules were used. - - - - - - Policy size reduced, metric no longer required. Removed 2020-06. - - ajgo@chromium.org - src/sandbox/policy/win/OWNERS - - Size of policy global memory used when policy was committed after successful - process start on Windows. 0 indicates that no rules were used. - - - - - - Removed 04/2020. See crrev.com/c/2129507 - - - - mrefaat@google.com - The time spent in product tour screens for ios. - - - - rogerta@chromium.org - The frequency of ways that new user profiles are added. - - - - jkrcal@chromium.org - droger@chromium.org - - Classification of what account categories out of {consumer, enterprise} - appear or appeared in this profile since the last time gaia cookies got - deleted. Thus, this also includes signed-out accounts. If both categories - appeared, it also distinguishes whether sync is enabled and for which of - them. Recorded on every activation of a Chrome window (for the respective - profile). - - - - - jkrcal@chromium.org - droger@chromium.org - - Classification of what gaia names appear or appeared in this profile since - the last time gaia cookies got deleted. Thus, this also includes signed-out - accounts. In order to protect privacy, only reports whether multiple - distinct gaia names appeared in this profile and if so, whether sync is - enabled for one of them. Furthermore, this metric uses a low-entropy hash to - detect distinct names. In case of a rare hash collision (less than 0.1% of - cases), multiple names get recorded as a single name. Recorded on every - activation of a Chrome window (for the respective profile). - - - - - bsazonov@chromium.org - chrome-signin-team@google.com - - Track user interactions that can be performed in the Android account - management menu. - - - - - Please list the metric's owners. Add more owner tags as needed. - The number of installed apps when a profile is opened. - - - - - Not accessed in months. All results say "authentication was - unnecessary". Removed 2020-03. - - bcwhite@chromium.org - - Counts of authorization results when trying to open a locked profile from - the User Manager. - - - - - jkrcal@chromium.org - droger@chromium.org - The frequency of selection of each avatar. - - - - - No longer recorded as of M87. - - chengx@chromium.org - Load status of an avatar for decorating the Windows taskbar - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the bookmarks database. - - - - msarda@chromium.org - tangltom@chromium.org - - Recorded every time a browser window becomes active. Each profile on a - client is assigned a unique bucket, i.e. whenever a browser window of - profile x becomes active, an entry is recorded in bucket x. - - Example: A user has 2 profiles and opens 1 browser window for each of them. - When the user switches back and forth between the windows, multiple entries - will be recorded in bucket 1 and 2, corresponding to the profiles. - - Note: The guest profile has bucket 0. Regular profiles start at bucket 1. - Incognito browser windows count towards the original profile. - - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the cookies database. - - - - - Removed 07/2019. - - rkaplow@chromium.org - Length of time to setup profile. - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the CreateBrowserContextServices call - within OnPrefsLoaded. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during ProfileManager::CreateProfileHelper. - This is called when a profile is created synchronously (usually at startup). - - - - - treib@chromium.org - rogerta@chromium.org - msarda@chromium.org - Result (final status) when creating a new profile. - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Back-end time elapsed while creating a new profile. The max is 30 seconds, - when an external timeout was applied. - - - - - - Removed as of 8/2013. - - Please list the metric's owners. Add more owner tags as needed. - - Time elapsed before the user decided to cancel creation of a new profile. - Since only managed-user profile creation can be canceled, this time comes - from managed-user registration. The max is 30 seconds, when an external - timeout was applied. - - - - - - Removed as of 6/2019. - - treib@chromium.org - michaelpg@chromium.org - - Time elapsed from when the handler received the message that a user clicked - 'Create' until the user decided to cancel creation of a new profile. Since - only managed-user profile creation can be canceled, this time comes from - managed-user registration. - - - - - treib@chromium.org - michaelpg@chromium.org - msarda@chromium.org - - Time elapsed from when the handler received the message that a user clicked - 'Create' until the creation either failed with a local error (see - Profile.CreateResult), was canceled (also recorded in - Profile.CreateTimeCanceledNoTimeout), or completed successfully. - - - - - msarda@chromium.org - droger@chromium.org - - This histogram tracks the deletion of the profile. This tracks when the - cleanup actually takes place, not the UI interaction. The parameter - indicates if the profile was signed in or not; true means the profile was - signed in, false means the profile was not signed in. - - - - - msarda@chromium.org - droger@chromium.org - anthonyvd@chromium.org - - This histogram tracks which UI screen was used to initiate and confirm the - deletion of a profile. This does not track when the profile is actually - deleted, which is an asynchronous process that happens later. - - - - - - Replaced by Profile.Menu.ClickedActionableItem in M81. - - msarda@chromium.org - tangltom@chromium.org - - Track user interactions that can be performed in the user menu and user - manager. The origin of the action, whether the an interaction in the content - area or some other source, is noted in the histogram suffix. - - - - - msarda@chromium.org - tangltom@chromium.org - - This histogram tracks whether the accounts cached in the GAIA cookie service - manager are stale when presenting the user menu when DICE is enabled. - - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the extension cookies database. - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the favicons database. - - - - - Removed 02/2015. Profile.CreateAndInitializeProfile is more useful. - - rkaplow@chromium.org - Length of time to retrieve profile. - - - - - Removed 06/2020. There are no recordings of this event since M83. - - msarda@chromium.org - alexilin@chromium.org - - Whether Profile::GetProfileInfoPath is called with a profile that does not - have the user data directory as a parent directory. This is expected to - never happen, but there are a few events recorded on stable as of M80. This - metric should be removed once http://crbug.com/981374 is fixed. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - Size of the history database. - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - This histogram records the lifetime duration of incognito profiles. It is - recorded once an off the record profile for an incognito session is closed. - - - - - - Removed 06/2020. There are no recordings of this event since M83. - - msarda@chromium.org - alexilin@chromium.org - - Whether Profile::InitProfileUserPrefs is called with a profile that does not - have the user data directory as a parent directory. This is expected to - never happen, but there are a few events recorded on stable as of M80. This - metric should be removed once http://crbug.com/981374 is fixed. - - - - - - Removed 03/2020. - - rogerta@chromium.org - - Number of times users launch a browser window from either a primary or - secondary profile (i.e., each time a browser window is opened we log which - type of profile it belongs to). - - - - - - Removed 12/2019. We do not lock profiles anymore. - - msarda@chromium.org - - How long locked profiles have been locked for. This is logged each time any - profile is loaded. Note that this does not track the total time the profile - was locked, but rather the span from when the profile was locked to when the - measurement takes place. - - - - - droger@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Recorded when an actionable item(e.g. button, link) in the profile menu is - clicked. - - - - - droger@chromium.org - jkrcal@chromium.org - - When the profile menu is opened, after the identity animation was shown, - this records the time since the animation was shown. In the control group - for the identity pill experiment, this is still recorded as the time since - the animation *would have been* shown. - - - - - droger@chromium.org - siyua@chromium.org - - When the profile menu is opened, after the avatar was highlighted, this - records the time since the highlight was shown. - - - - - rogerta@chromium.org - - Counts of users added and deleted. Percentages are not meaningful. Please - look at the ratio of the counts/percentages. - - - - - - Removed 2017-10-16. No longer tracked. Feature removed. - - mlerman@chromium.org - - Tracks user interactions with the 'Not You?' bubble that users can navigate - to from the Upgrade bubble after upgrade to the New Avatar Menu. - - - - - - Removed 2017-10-19. No longer tracked. Feature removed. - - mlerman@chromium.org - - Tracks user interactions with the signin bubble that appears in the New - Avatar Menu upon signin. This bubble appears after the user signs in using - the Inline Signin flow. - - - - - - Removed 2017-10-16. No longer tracked. Feature removed. - - mlerman@chromium.org - - Tracks user interactions with the bubble that appears for users in the new - avatar menu after upgrade. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the Notify() of - NOTIFICATION_PROFILE_CREATED during ProfileImpl::DoFinalInit(). - - - - - msarda@chromium.org - droger@chromium.org - - Counts the number of Google-managed accounts linked to a profile. This may - be counted multiple times per profile. Please review with the "Show - user counts" option enabled on the dashboard. - - - - - droger@chromium.org - feuunk@chromium.org - - Counts the number of profiles on a user's machine every 24 hours while - Chrome is running. - - As opposed to Profile.NumberOfProfiles, this counts only profiles that have - been used in the last 28 days. - - - - - agawronska@chromium.org - michaelpg@chromium.org - cros-families@google.com - - Counts the number of locally managed profiles on a user's machine every 24 - hours while Chrome is running, among cases with at least one profile. - - This counts only profiles that have been used in the last 28 days. - - - - - feuunk@chromium.org - msarda@chromium.org - - Counts the number of profiles that have a user-defined name on a user's - machine every 24 hours while Chrome is running. - - This counts only profiles that have been used in the last 28 days. - - - - - droger@chromium.org - jkrcal@chromium.org - - Counts the number of profiles on a user's machine every 24 hours while - Chrome is running. - - This counts the total number of profiles on the user's device, regardless of - whether they've been used recently. - - - - - - Removed 2013-04-09. No longer tracked. See Profile.NumberOfProfiles. - - rogerta@chromium.org - - Counts the number of profiles on a user's machine whenever a profile is - added or deleted. - - - - - jkrcal@chromium.org - droger@chromium.org - - Records the count of profiles for each profile switch (incl. switching - between concurrently open profiles by activating their browser windows). The - count excludes the Guest profile so records in bucket 1 denote switches - between the single profile and the Guest profile. - - - - - - Removed; replaced by Profile.NumberOfProfiles on 2013-04-09. Data are - suspect, especially after 2012-02-24: see https://crbug.com/189213. - - rogerta@chromium.org - - Counts the number of profiles on a user's machine when Chrome starts up. - - - - - msarda@chromium.org - droger@chromium.org - - Counts the number of signed-in (syncing) profiles with GAIA authentication - error on a user's machine every 24 hours while Chrome is running. - - This counts only profiles that have been used in the last 28 days. - - - - - droger@chromium.org - jkrcal@chromium.org - - Counts the number of signed-in (syncing) profiles on a user's machine every - 24 hours while Chrome is running. - - This counts only profiles that have been used in the last 28 days. - - - - - - Removed; replaced by Profile.NumberOfSignedInProfiles on 2013-04-09. - - rogerta@chromium.org - - Counts the number of profiles that are signed in to Chrome when Chrome - starts up. - - - - - msarda@chromium.org - droger@chromium.org - - Counts the number of signed-in (syncing) profiles that are using the GAIA - image as the avatar icon. Note that profiles with a GAIA image but without - Sync consent are not counted. This is counted every 24 hours while Chrome is - running. - - This counts only profiles that have been used in the last 28 days. - - - - - - Removed 03/2020. - - anthonyvd@chromium.org - - Counts the number of times profiles were switched in a browser session. This - value is incremented when a profile is switched to and the result is logged - during shutdown. - - - - - msarda@chromium.org - droger@chromium.org - - Counts the number of profiles unused within the past 28 days on a user's - machine. This is recorded every 24 hours while Chrome is running. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during ProfileImpl::OnLocaleReady. This - happens once after profile was loaded. - - - - - - Removed 04/2015, and replaced by Profile.OnLocaleReadyTime. - - rkaplow@chromium.org - - The amount of time that elapsed during ProfileImpl::OnPrefsLoaded. - - - - - - Removed because it did not present the information clearly. - - Please list the metric's owners. Add more owner tags as needed. - The frequency of ways that the profiles are opened. - - - - - Removed 03/2020. - - rogerta@chromium.org - - The frequency with which the user opens the different profile menus or - switches profiles. For the open statistics, this does not mean the user - necessarily opened a profile after clicking. The switch statistics indicate - how often and how the user switches profiles. They are provided together for - comparison of how often the user actually switches after opening the avatar - bubble menu. - - - - - agawronska@chromium.org - michaelpg@chromium.org - cros-families@google.com - - Tracks the percentage (0-100) of profiles that are locally managed, recorded - when Chrome starts up. - - - - - tnagel@chromium.org - - The error with the current user profile that caused an error dialog to be - shown. This dialog is shown usually when there is some sort of corruption in - the user's profile data. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the ProfileImpl::DoFinalInit(). - - - - - - Removed 02/2020 since the histogram indicators were stable. - - dullweber@chromium.org - - The amount of time that elapsed during profile statistics calculation. - - - - - msarda@chromium.org - tangltom@chromium.org - - Browsing session duration in minutes, recorded per profile. Each profile on - a client is assigned a unique bucket. - - Recorded when the user switches profiles, after some time of - inactivity(usually 5 minutes) or at browser shutdown. - - Example: A user has 2 profiles. They open a browser window of profile 1 and - interact with the browser for 8 minutes. Then they open a browser window of - profile 2 and interact with the browser for 3 minutes. Then they do nothing - (=stay inactive) for while. The recorded values will be: (bucket 1: 8), - (bucket 2: 3). - - Note: The guest profile has bucket 0. Regular profiles start at bucket 1. - Incognito profiles count towards the original profile. - - - - - jkrcal@chromium.org - droger@chromium.org - - The state of profile avatars as would be displayed to the user in the - profile picker. Recorded on startup of Chrome and whenever Chrome is used - after at least 30 minutes of inactivity. - - - - - jkrcal@chromium.org - droger@chromium.org - - The number of days since a profile was last used. Recorded on startup of - Chrome and whenever Chrome is used after at least 30 minutes of inactivity. - - - - - jkrcal@chromium.org - droger@chromium.org - - The state of profile name as would be displayed to the user in the profile - picker. Recorded on startup of Chrome and whenever Chrome is used after at - least 30 minutes of inactivity. - - - - - jkrcal@chromium.org - droger@chromium.org - - The type of profile's unconsented primary account. Recorded on startup of - Chrome and whenever Chrome is used after at least 30 minutes of inactivity. - - - - - - Long removed. - - Please list the metric's owners. Add more owner tags as needed. - - The error code generated in the final step (registration step) of creating a - new supervised profile. - - - - - - Long removed. - - Please list the metric's owners. Add more owner tags as needed. - - The error code generated in the final step (registration step) of importing - a supervised profile. - - - - - - Long removed. - - Please list the metric's owners. Add more owner tags as needed. - - Time elapsed from when the handler received the message that a user clicked - 'Create' to create a new supervised user profile until the registration ends - either successfully or with a failure (both recorded in - Profile.SupervisedProfileCreateResult). - - - - - - Long removed. - - Please list the metric's owners. Add more owner tags as needed. - - Time elapsed from when the handler received the message that a user clicked - 'Import supervised user' until the registration ends either successfully or - with a failure (both recorded in Profile.SupervisedProfileImportResult). - - - - - Please list the metric's owners. Add more owner tags as needed. - - Counts of when users switch to using their GAIA photo instead of an avatar - icon or the opposite when they switch back to an avatar icon instead of - their GAIA photo. - - - - - - Removed because it did not present the information clearly. - - Please list the metric's owners. Add more owner tags as needed. - Activity of the user with regards to sync. - - - - msalama@chromium.org - chrome-signin-team@google.com - - Number of times and ways the user customized the sync options of their - profile. Percentages are not meaningful. To determine percentages, take the - count of a given action over the count of number of customizations. The - histogram has expired in '2018-08-30' and is resurrected in '2020-03-09'. - - - - - - Removed 11/2018 as this histogram is not of sufficient value anymore. It - only records events made through the advanced settings dialog which are very - rare and not representative for most analysis purposes. - - tschumann@google.com - - Number of times the user signed into sync from original or secondary - profile. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - Size of the thumbnails database. - - - - - Removed 07/2019. Replaced by Profile.TimeToOpenUserManagerUpTo1min with the - max time increased from 10 seconds to 1 minute. - - msarda@chromium.org - tangltom@chromium.org - - Time required to open the UserManager, from when it started to show until - when its javascript started executing. - - - - - msarda@chromium.org - droger@chromium.org - - Time required to open the UserManager, from when it started to show until - when its javascript started executing. - - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the top sites database. - - - - Please list the metric's owners. Add more owner tags as needed. - Total size of all history databases. - - - - Please list the metric's owners. Add more owner tags as needed. - Total size of the profile data (excluding sub-folders). - - - - robertshield@chromium.org - - Indicates whether a profile had a reset trigger that caused it to launch a - reset flow. The presence of this trigger is recorded during profile - creation. - - - - - msarda@chromium.org - droger@chromium.org - - Recorded when a profile name and/or avatar was updated from the settings - page. - - - - - - Removed 6/3/2020. No longer needed. - - phillis@chromium.org - cmumford@chromium.org - - Record the result of updating taskbar decoration on Windows. - - - - - - Removed 8/2014. Upgrade Promotional UI removed. - - mlerman@chromium.org - - The process which leads a user to enroll in New Profile Management. Also - tracks if the user chooses to opt out, and tutorials which guide the user - into New Profile Management. - - - - - msarda@chromium.org - tangltom@chromium.org - - Helper histogram to track user actions per profile. Recorded when there is - an active profile browser instance and a UMA UserAction is recorded, i.e. if - there's an active profile, a recording of a UMA UserAction will result in a - recording of a sample in this histogram. - - Each profile on a client is assigned a unique bucket, i.e. whenever a user - action happens in a browser of profile x, an entry is recorded in bucket x. - - Example: A user has 2 profiles and opens a browser window for each of them. - When the user adds a new tab in each of the browsers, an entry is recorded - in bucket 1 and 2, corresponding to the profiles. (Adding a new tab is a - recorded user metrics action.) - - Note: The guest profile has bucket 0. Regular profiles start at bucket 1. - Incognito profiles count towards the original profile. - - - - - anthonyvd@chromium.org - - Whether the active profile is a guest profile when -validateMenuItem in the - ProfileMenuController gets an invalid value for the current profile's index. - - - - - anthonyvd@chromium.org - - The count of profiles in the avatar menu when -validateMenuItem in the - ProfileMenuController gets an invalid value for the current profile's index. - - - - - anthonyvd@chromium.org - - The selector associated with the menu item when -validateMenuItem in the - ProfileMenuController gets an invalid value for the current profile's index. - - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the visited links database. - - - - Please list the metric's owners. Add more owner tags as needed. - Size of the web data database. - - - - vasilii@chromium.org - ewald@chromium.org - - Whether any profile was shown in the list when the profile chooser was - opened. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the state of the "Ask on startup" user preference that - controls whether the profile picker should be shown on startup. Recorded on - startup of Chrome. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the state of the "Ask on startup" checkbox upon user - action to check/uncheck "Ask on startup" in the profile picker - main screen. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Whether the user picked to create a desktop shortcut for the new profile - created through the local profile creation in the profile picker. Recorded - on platforms where desktop shortcut is enabled. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the theme color of a new profile just created through the profile - picker local profile creation. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the reason why the profile picker has been shown to the user. - Recorded every time the profile picker window is shown or reactivated. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the time between Chrome startup and the call to - ProfilePickerView::Display(). Only recorded when the profile picker is shown - at startup. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the time between web view creation and the first paint. Only - recorded when the profile picker is shown at startup. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the time between web view creation and main view being initialized - in javascript. Only recorded when the profile picker is shown at startup. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the time between ProfilePickerView::Display() is called and the web - view creation. Only recorded when the profile picker is shown at startup. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Represents user navigation in the profile picker. Recorded every time a - different UI is visible in the profile picker. - - - - - msalama@chromium.org - chrome-signin-team@google.com - - Records the action performed by the user in the profile picker. - - - - - proberge@chromium.org - - Encodes from where the request for resetting the profile settings - originated. - - - - - - Removed 07/2019. No longer tracked. - - engedy@chromium.org - vasilii@chromium.org - - Signifies if the user selected "Send feedback" checkbox in the - Reset Profile dialog. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Errors that Protector detects about default search provider in Web Data. - Reported once when Web Data is loaded. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - Errors that Protector detects about protected settings in Preferences. - Reported once when profile is loaded. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - When the default search provider setting is changed outside of Chrome, which - is detected by the Protector, this histogram reports the new setting. - - - - - - Removed 8/2013. No longer tracked. - - Please list the metric's owners. Add more owner tags as needed. - - When the startup settings are changed outside of Chrome, which is detected - by the Protector, this histogram reports the new setting. - - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB Destroy call was successful or not. - - - - nyquist@chromium.org - ssid@chromium.org - - The LevelDB Status returned from a failed ProtoDatabase Get call. - - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB Get call found what was requested. - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB Get call was successful or not. - - - - nyquist@chromium.org - ssid@chromium.org - The LevelDB Status from a ProtoDatabase Init call. - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB LoadEntries call was successful or not. - - - - nyquist@chromium.org - ssid@chromium.org - - Whether a ProtoDB LoadKeysAndEntries call was successful or not. - - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB LoadKeys call was successful or not. - - - - ssid@chromium.org - salg@chromium.org - - Tracks the init state progress of a proto database. An enum value is - recorded for each state of progression through the initialization process. - Shows the number of users hitting each stage. The enum values starting with - success and failure indicate that the final output of initialization is a - success or failure. See - //components/leveldb_proto/internal/proto_init_state_description.md. - - - - - nyquist@chromium.org - ssid@chromium.org - - The LevelDB Status returned from a failed Protodatabase UpdateEntries call. - - - - - nyquist@chromium.org - ssid@chromium.org - Whether a ProtoDB UpdateEntries call was successful or not. - - - - hansberry@chromium.org - - Provides a breakdown of how often each BLE weave connection result occurs. - - - - - hansberry@chromium.org - - Provides a breakdown of how many times each possible Bluetooth GATT - connection result occurs. - - The bucket "Unknown result" indicates that the Bluetooth platform - returned an unknown error code; if it has any counts, the client code should - be changed to account for the new error code. - - - - - hansberry@chromium.org - - Provides a breakdown of how many times each possible Bluetooth GATT - "notify session" attempt result occurs. - - The bucket "Unknown result" indicates that the Bluetooth platform - returned an unknown error code; if it has any counts, the client code should - be changed to account for the new error code. - - - - - hansberry@chromium.org - - Provides a breakdown of how many times each possible Bluetooth GATT - "write characteristic" attempt result occurs. - - - - - - Removed 9/2016. Never added to histograms.xml and value is always 1. - - - The number of extensions overriding the proxy, triggering the proxy override - extension warning bubble. - - - - - rdevlin.cronin@chromium.org - - The action taken by the user when the "proxy overridden" extension - warning bubble is shown. Logged immediately after the action is taken. - - - - - - - tasak@google.com - - The growth of the background renderer's memory usage after a background - renderer is purged. This is recorded 5, 10 and 15 minutes after the purge. - - - - - tasak@google.com - - Time elapsed from when the backgrounded and purged renderer is foregrounded - until the renderer is painted. This is recorded every time the backgrounded - and purged renderer is foregrounded. - - - - - tasak@google.com - - Time elapsed from when the renderer, which is kept backgrounded for more - than 5 minutes, is foregrounded until the renderer is painted. This is - recorded every time such renderer is foregrounded. - - - - - - Removed April 2017. - - tasak@google.com - - The memory usage of the BlinkGC allocator after a background renderer is - purged and suspended. Note: this metric is for A/B testing. - - - - - - Removed April 2017. - - tasak@google.com - - The memory usage of the discardable memory after a background renderer is - purged and suspended. Note: this metric is for A/B testing. - - - - - - Removed April 2017. - - tasak@google.com - - The memory usage of the malloc after a background renderer is purged and - suspended. Note: this metric is for A/B testing. - - - - - - Removed April 2017. - - tasak@google.com - - The memory usage of PartitionAlloc after a background renderer is purged and - suspended. Note: this metric is for A/B testing. - - - - - - Removed April 2017. - - tasak@google.com - - The sum of the memory usages of PartitionAlloc, malloc, discardable memory, - mainThreadIsolate() and BlinkGC allocator after a backgrounded renderer is - purged and suspended. Note: this metric is for A/B testing. - - - - - - Removed April 2017. - - tasak@google.com - - The memory usage of mainThreadIsolate() after a backgrounded renderer is - purged and suspended. Note: this metric is for A/B testing. - - - - - - Removed Oct 2017. - - tasak@google.com - - This records how many tasks are still in task queues when a backgrounded - renderer is suspended. - - - - - peter@chromium.org - - Whenever a Service Worker receives a push message, this records the budget - available to the service worker, which is an internal Chrome value for the - amount of background processing a service worker is allowed to do without - visibly alerting the user. Scale for the budget is 0 to 100. - - - - - peter@chromium.org - - When a Service Worker receives a push message, this records whether the - overall operation was successful, or otherwise the type of error - encountered. - - - - - peter@chromium.org - - When attempting to deliver a push message to a Service Worker, this records - the result of finding the Service Worker registration given its ID and - origin. - - - - - peter@chromium.org - - When a Service Worker receives a push message, this records the precise - result received from the Service Worker code. - - - - - peter@chromium.org - - When a webpage asks for details about its current push messaging - registration, this records whether the request is successful, or otherwise - the type of error encountered. - - - - - peter@chromium.org - rayankans@chromium.org - knollr@chromium.org - viviy@google.com - - When a Service Worker receives a pushsubscriptionchange event, this records - whether the overall operation was successful, or otherwise the type of error - encountered. - - - - - - Removed April 2020 - - mamir@chromium.org - - When a message arrives for a lazy subscription and Chrome isn't in the - foreground, it is persisted on disk until next time Chrome is in the - foreground. This is recorded before adding the message the persisted queue - to estimate how large does the queue grow. - - - - - peter@chromium.org - knollr@chromium.org - - Whenever a Service Worker receives a push message, this records whether - Chrome is completely running in the background. A successful report means - that the message was received when Chrome was in complete background mode, - without UI, while a failure means it was in some other state: in background - with some apps running, showing browser windows, etc. - - - - - peter@chromium.org - knollr@chromium.org - - When a webpage registers for push messaging, this records whether the - request is successful, or otherwise the type of error encountered. - - - - - peter@chromium.org - - When a Service Worker hits low budget when servicing a push message, this - records what the Site Engagement Service score is at that time. - - - - - peter@chromium.org - - When a Service Worker hits zero budget when servicing a push message, this - records what the Site Engagement Service score is at that time. - - - - - - Removed Dec 2019 - - peter@chromium.org - knollr@chromium.org - - When a message arrives to a subscription while Chrome is in the background, - the subscription is checked first for being lazy, and accordingly the - message is forwarded or persisted on disk. Since this check may require disk - access, this histogram measures the time spent in checking if the - subscription is lazy. - - - - - peter@chromium.org - knollr@chromium.org - - When a message arrives for a lazy subscription and Chrome isn't in the - foreground, it is persisted on disk until next time Chrome is in the - foreground. This histogram measures the time spent in reading and replaying - persisted messages when Chrome goes to the foreground. - - - - - peter@chromium.org - - When unregistering a legacy non-InstanceID push messaging subscription, this - records the result returned by the GCMDriver (note that exceeding the - maximum number of retries due to network errors is logged as SERVER_ERROR). - - - - - peter@chromium.org - knollr@chromium.org - - When unregistering an InstanceID push messaging subscription, this records - the result returned from deleting the InstanceID (note that exceeding the - maximum number of retries due to network errors is logged as SERVER_ERROR). - - - - - peter@chromium.org - - When unregistering a website from push messaging, this records the reason - why it is being unregistered. - - - - - peter@chromium.org - - When unregistering a website from push messaging, this records whether the - request is successful, or otherwise the type of error encountered. - - - - - peter@chromium.org - - When a Service Worker receives a push message, this records whether it - showed user-visible UX (like a notification), or whether we showed a forced - notification on its behalf. - - - - - knollr@chromium.org - peter@chromium.org - - Records the number of visible notifications for a Service Worker when it - receives a push message. Counted and recorded after handling the push event. - - - - - llin@google.com - croissant-eng@chromium.org - - For quick answer impression that fulfills a user's intent, records the - result type. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For quick answer impression that fulfills a user's intent, records the - impression duration. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answer click event, records the result type. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answer click event, records the duration between fetch - finish and user clicks. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answers consent impression, records how many times the user - has seen the consent. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answers consent interaction event, records how long the user - has seen the consent before. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answers consent interaction event, records how many times - the user has seen the consent before. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For quick answer fetch, records the intent generated on-device. ChromeOS - only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answers fetch, records the duration between fetch start and - fetch finish. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answers fetch, records the result status. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answer result received event, records the result type. - ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answer result received event, records the duration between - fetch start and fetch finish. ChromeOS only. - - - - - llin@google.com - croissant-eng@chromium.org - - For every quick answer request, records the length of the selected text that - is being considered for fetching quick answers. ChromeOS only. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of cells that contain formatting data in the default - worksheet when a comma separated value spreadsheet is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of non-empty cells in the default worksheet when a comma - separated value spreadsheet is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of worksheets when a comma separated value spreadsheet is - opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the page count when a compound binary format document is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the paragraph count when a compound binary format document is - opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the section count when a compound binary format document is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the page count when an OOXML format document is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the paragraph count when an OOXML format document is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the section count when an OOXML format document is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the various different error types encountered when opening and - reading MS Office file formats in the Quickoffice viewer. These range from - Nacl crashes and uncaught javascript exceptions to document errors inside - Quickoffice Web Toolkit (eg QOWT). The errors are recorded against the file - format in which they occurred. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the various different file types supported by Quickoffice (like MS - Word, Excel, Powerpoint files) when they opened in the browser to measure - which file formats are most popular. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of slide masters when a compound binary format - presentation is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the slide count when a compound binary format presentation is - opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of slide masters when an OOXML format presentation is - opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the slide count when an OOXML format presentation is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of cells that contain formatting data in the default - worksheet when a compound binary format spreadsheet is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of non-empty cells in the default worksheet when a - compound binary format spreadsheet is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of worksheets when a compound binary format spreadsheet - is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of cells that contain formatting data in the default - worksheet when an OOXML format spreadsheet is opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of non-empty cells when an OOXML format spreadsheet is - opened. - - - - - dpnkar@google.com - meenakshiv@google.com - - Records the number of worksheets when an OOXML format spreadsheet is opened. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - How many kilobytes are how old. Similar to |AgeOfOrigin| except a sample is - added for each kilobyte of an origin's data. Logged hourly for all origins - with stored data. - - - - - jarrydg@chromium.org - - How many days it's been since an origin's temporary storage has been - accessed. Logged hourly for all origins with stored data. - - - - - jarrydg@chromium.org - - Amount of free disk space for the storage directory. Logged at irregular - intervals. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Amount of free disk space for the storage directory. Logged when collecting - usage information. - - - - - jarrydg@chromium.org - - The number of days since an origin was last chosen to be evicted from the - storage, recorded each time the origin is evicted (except for the first - eviction). - - - - - - Removed June 2019 - - jarrydg@chromium.org - - The number of days since an origin's data was last accessed. Logged upon - access when the time since last access is at least 24 hours. - - - - - jarrydg@chromium.org - - Difference between acceptable lower limit of diskspace and actual free - diskspace at beginning of an eviction round. - - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - - Number of errors on evicting origin by QuotaTemporaryStorageEvictor in an - hour. - - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - - Number of errors on getting usage and quota by QuotaTemporaryStorageEvictor - in an hour. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Amount of usage used by evicted origins in an eviction round. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - The number of times the evicted origin was accessed. Logged when the origin - is evicted. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - The number of days since the evicted origin was last accessed. Logged when - the origin is evicted. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - Number of evicted origins in an hour. - - - - - calamity@chromium.org - - The time since the evicted origin was last accessed. Logged when the origin - is evicted. - - - - - jarrydg@chromium.org - Number of eviction rounds in an hour. - - - - - jarrydg@chromium.org - Amount of free disk space for profile directory. - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - The size of the global temporary storage pool. Logged at irregular - intervals. - - - - - jarrydg@chromium.org - Global usage of persistent storage. - - - - jarrydg@chromium.org - Global usage of temporary storage. - - - - - jarrydg@chromium.org - Initial quota for global temporary storage. - - - - - Removed July 2018 - - dgrogan@chromium.org - - Types of origins that are initially selected for eviction via LRU. Some of - these types are exempt from eviction. - - - - - jarrydg@chromium.org - Number of evicted origins per round. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of origins using persistent storage. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of protected origins using persistent storage. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of protected origins using temporary storage. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of origins using temporary storage. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of unlimited origins using persistent storage. - - - - - Expired on 2018-08-30. Removed in M74. - - tzik@chromium.org - Number of unlimited origins using temporary storage. - - - - jarrydg@chromium.org - - If our hardcoded OS accomodation is too large for the volume size, we define - the value as a fraction of the total volume size instead. The - OSAccomodationDelta is the difference between the hardcoded and computed - values. - - - - - jarrydg@chromium.org - - Percentage of the storage device that is free. Logged at irregular - intervals. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Percentage of the storage device that is free. Logged when collecting usage - information. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Percentage of an origin's quota that is being used by the origin. Logged at - irregular intervals. - - - - - - jarrydg@chromium.org - - Percentage of the storage device that is being use for temporary storage. - Logged at irregular intervals (during eviction). - - - - - jarrydg@chromium.org - - Percentage of the storage device that is being use for temporary storage. - Logged when collecting usage information. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - The quota value computed for an origin using temporary storage. Logged at - irregular intervals. (In the process of writing new data, storage systems - consult the quota system for "usage and quota" to determine if - there is sufficient space available for the new data. This value is logged - at the time of that consultation. The frequency is dependent on how - individual websites use the various storage apis.) - - - - - jarrydg@chromium.org - Number of skipped eviction rounds in an hour. - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - While accumulating usage information, ClientUsageTracker is encountering - invalid origins. This enum histogram will capture the type of invalid - origins that are encountered. - - - - - - calamity@chromium.org - - Time since an origin was last chosen to be evicted from the storage, - recorded each time the origin is evicted (except for the first eviction). - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - Time between two consecutive active eviction rounds. - - - - jarrydg@chromium.org - Time spent to an eviction round. - - - - - Removed June 2019 - - jarrydg@chromium.org - - Time spent querying the embedder for the settings values. Logged at - irregular intervals as the values are refreshed. - - - - - - Removed November 2016 - - michaeln@chromium.org - - Time spent initializing the global quota. Logged when the storage - partition's quota manager is initialized. - - - - - jarrydg@chromium.org - - Total disk space for the storage directory. Logged at irregular intervals. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - Disk space (in MB) currently used by an origin. Logged hourly. - - - - - - Expired on 2018-08-30. Removed in M75. - - tzik@chromium.org - - Overage of the temporary global storage usage at beginning of an eviction - round. - - - - - holte@chromium.org - Counts how often daily interval events were fired. - - - - holte@chromium.org - - For each Rappor log that is discarded, the reason that it was discarded. - - - - - holte@chromium.org - Net error codes for failed Rappor uploads. - - - - - Removed 2015/05/05. - - holte@chromium.org - - Rappor.DailyEvent.IntervalType reported under the wrong name. - - - - - holte@chromium.org - - Success or errors encountered when loading Rappor cohort pref. - - - - - holte@chromium.org - - Success or errors encountered when loading Rappor secret pref. - - - - - holte@chromium.org - - For each upload to the Rappor server, log the response received from the - server. - - - - - gambard@chromium.org - bling-team@google.com - - The action chosen by the user after displaying the reading list context - menu. - - - - - gambard@chromium.org - bling-team@google.com - - Number of tries before the download of the entry is successful. - - - - - gambard@chromium.org - bling-team@google.com - Final status of the download of a reading list entry. - - - - gambard@chromium.org - bling-team@google.com - - Time since the first read of the reading list entry getting deleted. 0 if it - has never been read. - - - - - gambard@chromium.org - bling-team@google.com - Whether the displayed version is the offline one. - - - - gambard@chromium.org - bling-team@google.com - - Time since the creation of the read reading list entry getting deleted. - - - - - gambard@chromium.org - bling-team@google.com - Number of read entries in reading list. - - - - gambard@chromium.org - bling-team@google.com - - Time since the creation of the unread reading list entry getting deleted. - - - - - gambard@chromium.org - bling-team@google.com - Number of unread entries in reading list. - - - - robertshield@chromium.org - Log each stage of a recovery component event. - - - - - Replaced by RecurrenceRanker.InitializationStatus. - - tby@chromium.org - charleszhao@chromium.org - - Reports different kinds of misconfigurations of a RecurrenceRanker. - - - - - - - tby@chromium.org - charleszhao@chromium.org - - Records situations that can occur during the configuration and - initialization of a RecurrenceRanker. - - - - - - - tby@chromium.org - charleszhao@chromium.org - - Whether the conversion of a JSON config for a RecurrenceRanker succeeded for - failed. - - - - - - Removed December 2019. Distribution between file open types is approximately - 33% download, 26% launch, 26% open, 15% save as. - - jiameng@chromium.org - thanhdng@chromium.org - tby@chromium.org - - Records number of file opens for each file open type events. - - - - - - Replaced by RecurrenceRanker.SerializationStatus. - - tby@chromium.org - charleszhao@chromium.org - - Reports various saving/loading errors for a RecurrenceRanker or - RecurrencePredictor. - - - - - - - tby@chromium.org - charleszhao@chromium.org - - Reports the result of a save or load of a RecurrenceRanker model. - - - - - - - tby@chromium.org - charleszhao@chromium.org - - Reports when the functions of a RecurrenceRanker model are used. - - - - - - The cases this reported can no longer occur. - - tby@chromium.org - charleszhao@chromium.org - - Reports when a RecurrenceRanker is used in a way not supported by its - underlying RecurrencePredictor. - - - - - - We successfully shipped a 4k restriction in M77, and no longer require the - data on `referer` header length. - - mkwst@chromium.org - - The size of each outgoing request's 'Referer' header field's value, in - bytes. - - - - - grt@chromium.org - - The result of an attempt to show a relaunch notification dialog. - - - - - - Removed Dec 2016. This metric did not report the number of shared workers - correctly, since it used the RenderProcessHostImpl ref counts, which in the - shared worker case is more like a boolean flag (zero or one or maybe two) - than the number of shared workers. So its results can be thought of as - roughly the number of service workers only. - - kinuko@chromium.org - - Maximum number of workers (SharedWorker or ServiceWorker) that are - simultaneously hosted in a single renderer process. Recorded when the - renderer process host is being destructed. - - - - - - Removed May 2018. There are no longer accelerated fixed root backgrounds. - - Please list the metric's owners. Add more owner tags as needed. - - Keeps track of the number of main frame scrolls with an accelerated fixed - root background, the number of main frame scrolls with an unaccelerated - fixed root background, and the total number of main frame scrolls. - - - - - hartmanng@chromium.org - - Total count of the number of RenderLayers which are scrollable areas, need - to be promoted to stacking containers, and will use composited scrolling. - Each bucket is sampled at most once per RenderLayer, when the RenderLayer - first becomes scrollable, first needs to become a stacking container, and - first uses composited scrolling, respectively. - - - - - - Replaced by Scheduling.Renderer.DrawDuration. This metric did not - differentiate between processes. - - brianderson@chromium.org - The time it takes for the compositor to draw a frame. - - - - - Measurement no longer taken. - - brianderson@chromium.org - - The amount by which the compositor's draw duration was overestimated in a - particular frame (0 if the duration was perfectly predicted or - underestimated). - - - - - - Measurement no longer taken. - - brianderson@chromium.org - - The amount by which the compositor's draw duration was underestimated in a - particular frame (0 if the duration was perfectly predicted or - overestimated). - - - - - - Measurement no longer taken. - - brianderson@chromium.org - - The delay between the compositor submitting a command to the GPU and that - command executing on the GPU. This delay is measured once per frame. - - - - - - Measurement no longer taken. - - brianderson@chromium.org - - The amount by which GPU latency was overestimated in a particular frame (0 - if the latency was perfectly predicted or underestimated). - - - - - - Measurement no longer taken. - - brianderson@chromium.org - - The amount by which GPU latency was underestimated in a particular frame (0 - if the latency was perfectly predicted or overestimated). - - - - - avi@chromium.org - - The length of time render processes are hung, in milliseconds. Note that - because technically speaking render processes are "hung" from the - moment an input event is sent to them until the moment that they return an - ACK, only hangs of minimum length 5s are recorded. Note that this combines - measurements from both renderer processes that recover on their own, and - render processes that are killed. - - - - - dfalcantara@chromium.org - - Android: Records the terminal event associated with a hung renderer infobar. - This includes both the explicit user actions as well as implicit dismissals, - e.g., when the renderer regains responsiveness before the infobar is - interactively dismissed. - - - - - - Removed as of 3/2015. - - benjhayden@chromium.org - - Duration of the FrameView::performLayout trace event, which occurs at most - once per frame. - - - - - - Removed as of 3/2015. - - benjhayden@chromium.org - - Amount of time spent doing line layout during FrameView::performLayout. - - - - - falken@chromium.org - chrome-loading@google.com - - Time between the two messages OnReceiveResponse and - OnStartLoadingResponseBody as observed by the renderer process in - URLLoaderClientImpl. The idea is to see whether there is a performance cost - in having two separate messages, as the plan is to combine them into one. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the number of milliseconds spent blocking Blink's main thread while - capturing the main frame. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records a boolean indicating whether a capture for the main frame succeeded. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records the number of milliseconds spent blocking Blink's main thread while - capturing a subframe. - - - - - ckitagawa@chromium.org - mahmoudi@chromium.org - fredmello@chromium.org - - Records a boolean indicating whether a capture for a subframe succeeded. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - A lower-bound on the percentage increase in memory that would result from - promoting all layers that have a webkit-transition on opacity or transform. - - - - - - Removed as of 10/2013. - - Please list the metric's owners. Add more owner tags as needed. - - This measures how long all unload event handlers required to run whenever an - unload event is processed. - - - - - kkhorimoto@chromium.org - - [iOS] A boolean that is used to indicate that the WebKit rendering bug in - http://crbug.com/583231 has occurred. This occurs when a page with no - viewport tag is rendered with an unusable zoom scale. Only logged on iOS. - - - - - - Removed 12/2019 as it is no longer hit or recorded. - - michaeldo@chromium.org - - [iOS] Counts the number of times a WKNavigationDelegate callback was called - after the CRWWebController was closed. This is unexpected and could be the - cause of many crashes. If this histogram is ever logged, it means that - Chrome needs to gracefully handle the case when WKNavigationDelegate - callbacks are called for a destroyed web controller. Only logged on iOS. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a document finished loading to when all it's resources - are also loaded. - - - - - - Removed 6/15/09. Replaced by Renderer2.RequestToFinish_L - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page was requested by a user to when it is fully - loaded. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page was requested by a user to when it is fully - loaded. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page was requested by a user to its first layout. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page was requested by a user to when it starts loading. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page started loading to when it is fully loaded. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page starts loading to when the main document is - finished loading. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - The time from when a page starts loading to its first layout. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Distribution of actual finished pages, vs abandoned pages, where we needed - to declare a finish time prematurely since the page was being closed - (exited). - - - - - - Removed 2014-05 because of impl-side painting. - - wiltzius@chromium.org - - Time spent by WebKit painting the page, in milliseconds, when the GPU - acceleration is active, for paints that affect non-root layers. - - - - - - Removed 2014-05 because of impl-side painting. - - wiltzius@chromium.org - - WebKit paint throughput, measured in megapixels per second, when GPU - acceleration is active, for paints that affect non-root layers. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - Time between frames when GPU acceleration is active. - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time spent by WebKit painting the page, in milliseconds, when the GPU - acceleration is active, for paints that affect the root layer. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - WebKit paint throughput, measured in megapixels per second, when GPU - acceleration is active, for paints that affect the root layer. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from when the animation callback was posted to when it ran. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "begin" to "commit." "Begin"== - "request" if user requested, and "start" otherwise. - "Request"== time when user requested document. "Start"== - time when renderer requested load of document, after any unload of last - document. "Commit"== time when renderer got first byte of - document. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - TBD - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - TBD - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "begin" to "first paint." "Begin"== - "request" if user requested, and "start" otherwise. - "Request"== time when user requested document. "Start"== - time when renderer requested load of document, after any unload of last - document. "First paint"== time when first paint operation was - performed. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "big" to "first paint after load." - "Begin"== "request" if user requested, and - "start" otherwise. "Request"== time when user requested - document. "Start"== time when renderer requested load of document, - after any unload of last document. "First paint after load"== time - after onload() when first paint operation is performed. - - - - - - Obsolete as of M80. Partial raster has shipped for a long period of time / - is not being tuned. - - ericrk@chromium.org - - Percentage of pixels which would have been rastered, but were skipped due to - the partial raster optimization. Logged for each raster task run in a - Browser process. The histogram is suffixed by the RasterBufferProvider which - is in use. - - - - - - Obsolete as of 11/2019. Replaced by - Renderer4.Browser.RasterTaskSchedulingDelayNoAtRasterDecodes since the - semantics changed: we used to count raster tasks that depended on at-raster - image decodes, but this is no longer the case. - - andrescj@chromium.org - chromeos-gfx@google.com - - The wall time elapsed between creating a raster task in the client and being - ready to issue raster work to the driver in the GPU process. This includes - time decoding and uploading images. - - - - - andrescj@chromium.org - chromeos-gfx@google.com - - The wall time elapsed between creating a raster task in the client and being - ready to issue raster work to the driver in the GPU process. This includes - time decoding and uploading images. Note that this does not count raster - tasks that depend on at-raster image decodes. Since this metric is only - reported for Chrome OS clients, it has data only from high-resolution - clocks. - - - - - khushalsagar@chromium.org - chrome-gpu@google.com - - Time spent completing all work for a compositor rasterization task. This - includes the time in the renderer process for sending GL or paint commands - to the GPU process and the time for flushing these commands to the driver. - - WARNING: This metric is only reported for clients with high resolution - clocks, which means this will be biased to a portion of the population on - windows. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "commit" to "finish." "Commit"== - time when renderer got first byte of document. "Finish"==after - onload() and all resources are loaded. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "commit" to "finish doc." "Commit"== - time when renderer got first byte of document. "Finish doc" == - main document loaded, before onload(). "Finish"==after onload() - and all resources are loaded. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "commit" to "first paint." - "Commit"== time when renderer got first byte of document. - "First paint"== time when first paint operation was performed. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "commit" to "first paint after load." - "Commit"== time when renderer got first byte of document. - "First paint after load"== time after onload() when first paint - operation is performed. - - - - - - Removed in 12/2017. Renderer4.MainThreadGestureScrollReason and - Renderer4.MainThreadWheelScrollReason could track more detailed reasons of - main thread scrolling. - - vollick@chromium.org - - It's possible for compositor hit testing to determine conclusively that - compositor thread scrolling can or cannot be done. It's also possible that - the hit testing result is inconclusive. We would like to see the I-don't- - know result as little as possible. This histogram tracks the ratios. - - - - - - Removed in 06/2018, M69. Renderer4.CompositorThreadImplDrawDelay is no - longer needed due to issue 851784. - - wiltzius@chromium.org - - Time between frames, as measured on the compositor thread. This is collected - once per frame while it is being drawn to the screen in the compositor. - - - - - tdresser@chromium.org - Whether the scroll from touch is executed on main thread. - - - - tdresser@chromium.org - - Whether the scroll from mouse wheel is executed on main thread. - - - - - - Renamed to Renderer4.pixelCountCulled_Draw. - - wiltzius@chromium.org - - Number of pixels that culling prevented being drawn to the screen, - normalized to the viewport size. This is collected once per frame while it - is being drawn to the screen in the compositor. - - - - - - Renamed to Renderer4.pixelCountOpaque_Draw. - - wiltzius@chromium.org - - Number of pixels drawn to the screen and known opaque, normalized to the - viewport size. This is collected once per frame while it is being drawn to - the screen in the compositor. - - - - - - Renamed to Renderer4.pixelCountTranslucent_Draw. - - wiltzius@chromium.org - - Number of pixels drawn to the screen and not known opaque, normalized to the - viewport size. This is collected once per frame while it is being drawn to - the screen in the compositor. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "finish doc" to "finish." "Finish - doc"== main document loaded, before onload(). "Finish"==after - onload() and all resources are loaded. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "finish " to "first paint after load." - "Finish"==after onload() and all resources are loaded. "First - paint after load"== time after onload() when first paint operation is - performed. - - - - - - Removed 9/2018 and merged into Renderer4.MainThreadGestureScrollReason. - - tdresser@chromium.org - - For every touch scroll, we record whether the scroll occurred on the main - thread, on the compositor thread, or on the compositor thread but blocked on - the main thread. The last case will happen when there is a blocking event - listener. - - - - - cblume@chromium.org - vmpstr@chromium.org - - Gpu image decode usage statistics. Images are decoded and locked prior to - upload; this indicates how that decode is used during tile management. - - - - - sashamcintosh@chromium.org - ericrk@chromium.org - - The current number of bytes locked by the GpuImageDecodeCache compared to - the maximum allowed number of bytes to lock. This value is recorded every - time the tile manager assigns GPU memory to tiles. - - - - - cblume@chromium.org - vmpstr@chromium.org - - Indication whether the first lock of an image decode was wasted (image was - not used). Images are decoded and locked prior to raster; this indicates - whether the decode was used or not during the first lock. - - - - - cblume@chromium.org - khushalsagar@chromium.org - - Gpu image upload usage statistics. Images are uploaded and locked prior to - use; this indicates how that upload is used during tile management. - - - - - ericrk@chromium.org - - Indication whether the first lock of an image upload was wasted (image was - not used). Images are uploaded and locked prior to raster; this indicates - whether the upload was used or not during the first lock. - - - - - - Removed as of 06/2017. No longer generated. - - vmpstr@chromium.org - - Indication whether the first ref of a GPU image upload was wasted (not used - in raster). Images are uploaded prior to raster; this indicates whether the - upload was used during the first ref. - - - - - - Removed as of 06/2017. No longer generated. - - vmpstr@chromium.org - - Indication whether the GPU image upload was used in raster. Images are - uploaded prior to raster; this indicates whether the upload was used during - raster. - - - - - ericrk@chromium.org - enne@chromium.org - - Whether gpu rasterization is enabled (checked once after the page is painted - for the first time). - - - - - - Removed 10/2019. - - ericrk@chromium.org - enne@chromium.org - - If gpu rasterization is enabled, whether this page contains both slow-paths - (making it suitable for MSAA) and non-AA paints (making it not-suitable for - MSAA). This indicates a case where we would like to use MSAA, but may have - to avoid it for correctness reasons. - - - - - - Removed 10/2019. Gpu rasterization is no longer dynamically triggerd by - content. - - ericrk@chromium.org - enne@chromium.org - - If gpu rasterization is enabled, whether the page contents contain no more - than 5 slow paths, and is suitable for non-MSAA gpu rasterization (checked - once after the page is painted for the first time). - - - - - - Removed 09/2019. Gpu rasterization is no longer dynamically triggerd by - content. - - ericrk@chromium.org - enne@chromium.org - - If gpu rasterization is enabled, whether it was triggered (checked once - after the page is painted for the first time). - - - - - - Removed 02/2019. Due to changes in the code, this is synonymous with - Renderer4.GpuRasterizationEnabled. - - alokp@chromium.org - - If gpu rasterization is enabled, whether it was actually used for the page - (checked once after the page is painted for the first time). - - - - - - Removed 02/2018. The ideal content scale closely matches the default device - scale factor. - - vmpstr@chromium.org - - The contents scale at which picture layer impl should be rasterized in order - to appear crisp. This is also known as ideal contents scale. This value is - recorded any time the ideal contents scale changes. Some examples of this - are pinch-zoom and JavaScript transform changes. - - - - - - Removed 06/2019. - - khushalsagar@chromium.org - - The mip level at which images are decoded for rasterization in the renderer. - This value is recorded each time an image is decoded in the compositor and - records the mip level used for the decode. Note that the mip levels recorded - lie between [1, 32], with the value of 1 indicating the use of the original - image. - - - - - - - - - - - cblume@chromium.org - vmpstr@chromium.org - sashamcintosh@chromium.org - - This metric records the duration of an image decode for the raster path in - the compositor. It is recorded every time we decode an image. It is suffixed - by the type of rasterization we're in (either Gpu or Software). The - rasterization suffix is optionally prefixed by the image type (WebP, Jpeg, - etc.) or OutOfRaster. - - Warning: Before version M78 this metric may include reports from clients - with low-resolution clocks (i.e. on Windows, ref. - |TimeTicks::IsHighResolution()|). Such reports will cause this metric to - have an abnormal distribution. - - - - - - Removed July 2020, expired and no longer useful. - - ccameron@chromium.org - - For each cc::Layer that has more than zero discardable images, this metric - records the percent of image pixels that were from images that were - originally specified in an sRGB color space. - - - - - - Removed July 2020, expired and no longer useful. - - ccameron@chromium.org - - For each cc::Layer that has more than zero discardable images, this metric - records the percent of images that were originally specified in an sRGB - color space. - - - - - - - sashamcintosh@chromium.org - chromeos-gfx@google.com - - This metric records the duration of an image upload for the raster path in - the compositor. It is recorded every time we upload an image. The metric is - optionally suffixed by the image type (WebP, Jpeg, etc.) or OutOfRaster. - - - - - wiltzius@chromium.org - - Number of rects inside of a PictureLayer's invalidation region per commit. - - - - - - Removed in 06/2018, M69. Renderer4.LanguageDetection is no longer needed due - to issue 851784. - - wiltzius@chromium.org - - Time to determine the page language. This is done after the page has been - loaded. - - - - - - Removed as of 02/2015. No longer generated. - - wiltzius@chromium.org - - The ratio of LCDText CC Layers / candidate LCDText layers. Recorded in - LayerTreeHost, after LayerTreeHostCommon::CalculateDrawProperties() has - computed the properties we need. Only recorded for the first 50 frames of - every page. - - - - - - Removed as of 02/2015. No longer generated. - - wiltzius@chromium.org - - The ratio of CC Layers which are candidates for LCDText AA / total picture - or content Layers. Recorded in LayerTreeHost, after - LayerTreeHostCommon::CalculateDrawProperties() has computed the properties - we need. Only recorded for the first 50 frames of every page. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Probability distribution for enumerated varieties of page loads. - - - - - - Removes as of 6/2020. We now get enough cache hit information from - Renderer4.SoftwareImageDecodeState* and don't need to divide it into tile - bins. - - cblume@chromium.org - vmpstr@chromium.org - - For each attempted lock of a cached image, records whether it was - successful. - - - - - tdresser@chromium.org - pdr@chromium.org - - Ideally we'd always scroll on the impl thread, but there are a variety of - situations where we need to scroll on main. We should try to drive these - down. For every gesture, we record whether or not the scroll occurred on the - main thread or it should scroll on the impl thread but is blocked on main - thread, and if it did, what the reason was. - - - - - tdresser@chromium.org - pdr@chromium.org - - Ideally we'd always scroll on the impl thread, but there are a variety of - situations where we need to scroll on main. We should try to drive these - down. For every wheel tick, we record whether or not the the scroll occurred - on the main thread or it should scroll on the impl thread but is blocked on - main thread, and if it did, what the reason was. - - - - - ericrk@chromium.org - - The percentage of input events which are janks (not processed in the - expected frame) during each momentum scroll gesture. Computed by tracking - the number of extra coalesced momentum scroll events during a gesture. Extra - coalesced event indicates that the events were not handled in the target - frame. Logged once after a scroll with momentum events completes. - - - - - - Obsolete after 07/2019. Investigation concluded. - - ericrk@chromium.org - - The percentage of input events which are janks (not processed in the - expected frame) during each momentum scroll gesture due to unstable ordering - of begin frame with regards to input delivery. Computed by tracking the - number of times we coalesce an extra input event close to the point at which - we process it. Added to track the impact of https://crbug.com/952930. Logged - once after a scroll with momentum events completes. - - - - - wiltzius@chromium.org - - Number of pixels that culling prevented being drawn to the screen, recorded - as 10 times the percentage of the viewport that these pixels cover. This is - collected once per frame while it is being drawn to the screen in the - compositor. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Number of pixels known to be opaque, recorded as 10 times the percentage of - the viewport that these pixels cover. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Number of pixels painted by WebKit into main memory, recorded as 10 times - the percentage of the viewport that these pixels cover. This is collected - once per commit from WebKit to the compositor. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Number of pixels not known to be opaque opaque, recorded as 10 times the - percentage of the viewport that these pixels cover. - - - - - - Not used after M77. No longer tuning this code. - - ericrk@chromium.org - - The type of clear which was needed for each cc::RasterSource rasterized. - - - - - - Removed 02/2017 in Issue 675840. - - vmpstr@chromium.org - - For each tile that was ready to draw at some point, logs whether the tile - was actually used in a draw. This is logged at tile destruction time. - - - - - - Obsolete as of M80. Partial raster has shipped for a long period of time / - is not being tuned. - - ericrk@chromium.org - - Percentage of pixels which would have been rastered, but were skipped due to - the partial raster optimization. Logged for each raster task run in a - Renderer process. The histogram is suffixed by the RasterBufferProvider - which is in use. - - - - - - Obsolete as of 11/2019. Replaced by - Renderer4.Renderer.RasterTaskSchedulingDelayNoAtRasterDecodes since the - semantics changed: we used to count raster tasks that depended on at-raster - image decodes, but this is no longer the case. - - andrescj@chromium.org - chromeos-gfx@google.com - - The wall time elapsed between creating a raster task in the client and being - ready to issue raster work to the driver in the GPU process. This includes - time decoding and uploading images. - - - - - andrescj@chromium.org - chromeos-gfx@google.com - - The wall time elapsed between creating a raster task in the client and being - ready to issue raster work to the driver in the GPU process. This includes - time decoding and uploading images. Note that this does not count raster - tasks that depend on at-raster image decodes. Since this metric is only - reported for Chrome OS clients, it has data only from high-resolution - clocks. - - - - - khushalsagar@chromium.org - chrome-gpu@google.com - - Time spent completing all work for a compositor rasterization task. This - includes the time in the renderer process for sending GL or paint commands - to the GPU process and the time for flushing these commands to the driver. - - WARNING: This metric is only reported for clients with high resolution - clocks, which means this will be biased to a portion of the population on - windows. - - - - - enne@chromium.org - chrishtr@chromium.org - - The number of render passes (or render targets) in the renderer's frame. If - the value is more than one, then an intermediate rendering target must be - used during the rendering of the frame for each render pass greater than - one. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "request" to "finish." "Request"== - time when user requested document. "Finish"==after onload() and - all resources are loaded. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "request" to "start." "Request"== - time when user requested document. "Start"== time when renderer - requested load of document, after any unload of last document. - - - - - - Removed in M85 as no longer being needed. - - bbudge@chromium.org - - The size of the contiguous memory block reserved in the renderer so that - large allocations are more likely to succeed. The reservation is currently - made in BlinkInitializer. - - - - - - 07/2020: Replaced by the Compositing.ResourcePoolMemoryUsage. - - ericrk@chromium.org - - Size of the in-use portion of the ResourcePool. Recorded each time resources - are reclaimed after tile work completes. - - - - - - - bokan@chromium.org - input-dev@chromium.org - - For each scroll gesture (i.e. at GestureScrollBegin), records whether the - scroll is: handled unblocked on the compositor thread, handled on the - compositor thread but blocked on main thread event listeners, or being - handled on the main thread. Broken down by scroll device. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - Time to capture a renderer snapshot. - - - - - Removed in 06/2018, M69. Renderer4.SoftwareCompositorThreadImplDrawDelay is - no longer needed due to issue 851784. - - wiltzius@chromium.org - - Time between frames when the software renderer is being used, as measured on - the compositor thread. This is collected once per frame while it is being - drawn to the screen in the compositor. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - Time between frames when the page is not GPU accelerated. - - - - cblume@chromium.org - vmpstr@chromium.org - - Software image decode usage statistics. Images are decoded and locked prior - to raster; this indicates how that decode is used during tile management. - - - - - cblume@chromium.org - vmpstr@chromium.org - - Indication whether the first lock of an image decode was wasted (image was - not used). Images are decoded and locked prior to raster; this indicates - whether the decode was used or not during the first lock. - - - - - - Removed in issue 755432 as no longer being needed. - - wiltzius@chromium.org - - Time spent by WebKit painting the page, in milliseconds, when the page is - not GPU accelerated. - - - - - - Removed in issue 755432 as no longer being needed. - - wiltzius@chromium.org - - WebKit paint throughput, measured in megapixels per second, when the page is - not GPU accelerated. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "start" to "commit." "Start"== time - when renderer requested load of document, after any unload of last document. - "Commit"== time when renderer got first byte of document. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Time from "start" to "finish." "Start"== time - when renderer requested load of document, after any unload of last document. - "Finish"==after onload() and all resources are loaded. - - - - - reveman@chromium.org - - Time between the issue of a texture copy operation and detecting that it has - completed as measured by the GPU process. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - The number of microseconds it took to upload a tile's full texture as - measured on the GPU process. - - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - Time to capture a renderer thumbnail. - - - - - Removed at an unknown time. No longer used in code. - - wiltzius@chromium.org - - Number of tiles that culling prevented being uploaded to texture memory. - This is an approximation and is recorded as a 100 times the percentage of - the number of tiles, of default size, needed to cover the viewport. This is - collected once per commit from WebKit to the compositor. - - - - - - Removed as of 04/2012, replaced with Renderer4.tileCountCulled_Upload. - - wiltzius@chromium.org - - Number of pixels that culling prevented being uploaded to texture memory, - normalized to the viewport size. This is collected once per commit from - WebKit to the compositor. - - - - - - Renamed to Renderer4.pixelCountOpaque_Upload. - - wiltzius@chromium.org - - Number of pixels uploaded to texture memory and known to be opaque, - normalized to the viewport size. This is collected once per commit from - WebKit to the compositor. - - - - - - Renamed to Renderer4.pixelCountTranslucent_Upload. - - wiltzius@chromium.org - - Number of pixels uploaded to texture memory and not known opaque, normalized - to the viewport size. This is collected once per commit from WebKit to the - compositor. - - - - - - Removed 9/2018 and merged into Renderer4.MainThreadWheelScrollReason. - - tdresser@chromium.org - - For every wheel tick, we record whether the scroll occurred on the main - thread, on the compositor thread, or on the compositor thread but blocked on - the main thread. The last case will happen when there is a blocking event - listener. - - - - - - Removed 6/2018 and replaced with PageScheduler.PageLifecycleStateTransition. - - fmeawad@chromium.org - panicker@chromium.org - - Tracks the transitions of the renderer scheduler when it is backgrounded. - Once it is backgrounded, it can be stopped after a timeout, stopped due to - critical resources, resumed or foregrounded. - - - - - - Replaced with RendererScheduler.BackgroundRendererMainThreadLoad2 as of May - 2017. - - altimin@chromium.org - - Renderer main thread load when renderer is backgrounded, i.e. percentage of - time spent on running tasks. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per minute per - renderer amortized. - - - - - - Replaced with - RendererScheduler.RendererMainThreadLoad3.Background.AfterFirstMinute as of - July 2017. - - altimin@chromium.org - - Renderer main thread load when renderer is backgrounded, i.e. percentage of - time spent on running tasks. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per minute per - renderer amortized. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus2 as of Feb - 2018. Buckets were changed. - - npm@chromium.org - tdresser@chromium.org - - Expected queueing time split by tasks according to their frame status, in - microseconds. The sum of the split values will be equal to the total, - reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded for - each 1000 ms window. - - - - - - Removed March 2019. - - npm@chromium.org - tdresser@chromium.org - - Expected queueing time split by tasks according to their frame status, in - microseconds. The sum of the split values will be equal to the total, - reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded for - each 1000 ms window. - - - - - - Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus as of - December 2017. - - npm@chromium.org - - Expected queueing time split by tasks according to their frame type. The sum - of the split values should be equal to the total, reported on - RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms - window. - - - - - - Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue2 as of Feb - 2018. Buckets were changed. - - npm@chromium.org - tdresser@chromium.org - - Expected queueing time split by tasks according to the type of their task - queue, in microseconds. The sum of the split values should be equal to the - total, reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded - for each 1000 ms window. - - - - - - Removed February 2019. - - npm@chromium.org - tdresser@chromium.org - - Expected queueing time split by tasks according to the type of their task - queue, in microseconds. The sum of the split values should be equal to the - total, reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded - for each 1000 ms window. - - - - - - Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue as of - December 2017. - - npm@chromium.org - - Expected queueing time split by tasks according to the type of their task - queue. The sum of the split values should be equal to the total, reported on - RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms - window. - - - - - - Removed 04/2018. - - tdresser@chromium.org - - Expected queueing time for events which were queued on the main thread - longer or shorter than a threshold, given by the QueueingTimeThreshold - suffix. - - Team: input-dev@chromium.org. - - - - - - Removed June 2020. - - tdresser@chromium.org - - The estimated queueing duration which would be observed for additional high - priority tasks posted to the RendererScheduler. Recorded for each 1000 ms - window. - - - - - - Replaced with RendererScheduler.ExpectedTaskQueueingDuration3 as of Feb - 2018. Buckets were changed. - - tdresser@chromium.org - npm@chromium.org - - The estimated queueing duration which would be observed for additional high - priority tasks posted to the RendererScheduler, in microseconds. Recorded - for each 1000 ms window. - - - - - - Removed June 2020. - - tdresser@chromium.org - npm@chromium.org - speed-metrics-dev@chromium.org - - The estimated queueing duration which would be observed for additional high - priority tasks posted to the RendererScheduler, in microseconds. Recorded - for each 1000 ms window. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed March 2019. - - tdresser@chromium.org - npm@chromium.org - - The estimated queueing duration which would be observed for additional high - priority tasks posted to the RendererScheduler, in microseconds, for - renderer processes that do not host any main frame. Recorded for each 1000 - ms window. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced with RendererScheduler.ForegroundRendererMainThreadLoad2 as of May - 2017. - - altimin@chromium.org - - Renderer main thread load when renderer is foregrounded, i.e. percentage of - time spent on running tasks. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per minute per - renderer amortized. - - - - - - Replaced with - RendererScheduler.RendererMainThreadLoad3.Foreground.AfterFirstMinute as of - July 2017. - - altimin@chromium.org - - Renderer main thread load when renderer is foregrounded, i.e. percentage of - time spent on running tasks. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per minute per - renderer amortized. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - lpy@chromium.org - - This boolean keeps track the count of the visibility change of a frame. - Recorded every time when the visibility of a frame is changed. - - - - - - Removed June 2020. - - maxlg@chromium.org - - The single maximum estimated queueing duration (or max queueing time) - between when user starts navigation and user navigates away. Navigate-away - is defined as a fast shutdown or a natural ending of renderer, or the new - navigation start which replacing the old navigation. - - The queueing time is estimated on a sliding window basis. The width of the - sliding window is 1 second, the sliding step being 50ms. The max queueing - time keeps track of the largest queueing time on each slide. - - This metric resets itself at navigation start, updates the max of queueing - time with the sliding window moving, reports the max queueing times to the - histogram at the next navigation start of the same or different renderer - process. - - - - - - Replaced with RendererScheduler.NumberOfTasksPerQueueType2 as of May 2017. - - altimin@chromium.org - alexclarke@chromium.org - - The number of completed renderer tasks split per task queue type. Used to - monitor usage of each type of task queue. Reported each time when task is - completed. - - - - - - Replaced with RendererScheduler.TaskCountPerQueueType as of July 2017. - - altimin@chromium.org - alexclarke@chromium.org - - The number of completed renderer tasks split per task queue type. Used to - monitor usage of each type of task queue. Reported each time when task is - completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - - kdillon@chromium.org - shaseley@chromium.org - - Tracks the queueing time of tasks on the main thread of the renderer broken - down by queue type. Reported when the task is completed. - - Note that this metric is only recorded when a renderer is not backgrounded. - - - - - - Removed as of 08/2017. Replaced with - RendererScheduler.ExpectedQueueingTimeWhenQueueingTime. - - tdresser@chromium.org - - Time between sending an event to the renderer main thread and when the - renderer begins to process that event, for events which were dispatched when - the expected queueing time was past some threshold. - - Team: input-dev@chromium.org. - - - - - - This metric still used 1-minute reporting chunks. Replaced with - RendererMainThreadLoad4 as of July 2017. - - altimin@chromium.org - - Renderer main thread load (percentage of time spent in tasks), reported in - one minute chunks. - - See http://bit.ly/chromium-renderer-main-thread-load-metric for details. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per second per - renderer amortized. - - - - - - Replaced with RendererMainThreadLoad5 as of August 2017. - - altimin@chromium.org - - Renderer main thread load (percentage of time spent in tasks), reported in - one second chunks. - - See http://bit.ly/chromium-renderer-main-thread-load-metric for details. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per second per - renderer amortized. - - - - - altimin@chromium.org - - Renderer main thread load (percentage of time spent in tasks), reported in - one second chunks. - - See http://bit.ly/chromium-renderer-main-thread-load-metric for details. - - This metric is emitted when the renderer main thread task is completed or - renderer is backgrounded or foregrounded, at most once per second per - renderer amortized. - - - - - farahcharab@chromium.org - altimin@chromium.org - - Used to track the number of resource loading tasks split by net priority. - Recorded each time the resource's request priority is changed. - - - - - farahcharab@chromium.org - altimin@chromium.org - - Used to track the number of resource loading tasks split by execution - priority. Recorded each time a task is executed. - - - - - altimin@chromium.org - - The number of completed renderer tasks split per frame type. Used to monitor - usage of each type of frame. Reported each time when task is completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - tasak@google.com - - The number of completed renderer tasks which have safepoints, split per - frame type. Used to monitor usage of each type of frame. Reported each time - when task is completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - - The number of completed renderer tasks split per task queue type. Used to - monitor usage of each type of task queue. Reported each time when task is - completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskCPUDurationPerTaskType2.DedicatedWorker - as of June 2018 due to overflows (crbug.com/809668). Some metrics are - incremented with large amounts that they sometimes overflow and roll - negative before they get uploaded. - - altimin@chromium.org - - Total duration of dedicated worker tasks (thread time) split by per thread - type. Reported each time when task is completed and current accumulated - duration is longer than 1ms. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - - Total duration (reported in full seconds) of dedicated worker tasks (thread - time) split by per thread type. Note that partial seconds are rounded - up/down so that they average to the correct value when many reports are - added. For more details, check base::ScaledLinearHistogram. - - This is reported each time a task is completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskCPUDurationPerThreadType2 as of June - 2018 due to overflows (crbug.com/809668). Some metrics are incremented with - large amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - - Total cpu time of renderer tasks split by per thread type. Wall time is - tracked by RendererScheduler.TaskDurationPerThreadType histogram. This - histogram is used to compare CPU usage of tasks from different threads. - - Only 1% of randomly sampled tasks have cpu time measured and report duration - for this histogram. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - - Total cpu time (reported in full seconds) of renderer tasks split by per - thread type. Note that partial seconds are rounded up/down so that they - average to the correct value when many reports are added. For more details, - check base::ScaledLinearHistogram. - - Wall time is tracked by RendererScheduler.TaskDurationPerThreadType - histogram. This histogram is used to compare CPU usage of tasks from - different threads. - - Only 1% of randomly sampled tasks have cpu time measured and report duration - for this histogram. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskDurationPerFrameOriginType2 as of June - 2018 due to overflows (crbug.com/809668). Some metrics are incremented with - large amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - - Total cpu time of renderer tasks split by per frame origin type (main frame - vs same-origin frame vs cross-origin frame). - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - - Total cpu time (reported in full seconds) of renderer tasks split by per - frame origin type (main frame vs same-origin frame vs cross-origin frame). - Note that partial seconds are rounded up/down so that they average to the - correct value when many reports are added. For more details, check - base::ScaledLinearHistogram. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskDurationPerFrameType2 due to the - introduction of new types of frames as of 11/2017. - - altimin@chromium.org - - Total duration of renderer per-frame tasks split per frame type. Used to - monitor workload coming from different frames. Reported each time when task - is completed and current accumulated duration is longer than 1ms. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - - Replaced with RendererScheduler.TaskDurationPerFrameType3 as of June 2018 - due to overflows (crbug.com/809668). Some metrics are incremented with large - amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - - Total duration of renderer per-frame tasks split per frame type. Used to - monitor workload coming from different frames. Reported each time when task - is completed and current accumulated duration is longer than 1ms. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - altimin@chromium.org - - Total duration (reported in full seconds) of renderer per-frame tasks split - per frame type. Note that partial seconds are rounded up/down so that they - average to the correct value when many reports are added. For more details, - check base::ScaledLinearHistogram. - - Used to monitor workload coming from different frames. Reported each time a - task is completed. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - - Replaced with RendererScheduler.TaskDurationPerQueueType2 as of May 2017. - - altimin@chromium.org - alexclarke@chromium.org - - Total duration of renderer tasks split per task queue type. Used to monitor - usage of each type of task queues. Reported each time when task is completed - and current accumulated duration is longer than 1ms. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - - Replaced with RendererScheduler.TaskDurationPerQueueType3 as of June 2018 - due to overflows (crbug.com/809668). Some metrics are incremented with large - amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - alexclarke@chromium.org - - Total duration of renderer tasks split per task queue type. Used to monitor - usage of each type of task queues. Reported each time when task is completed - and current accumulated duration is longer than 1ms. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - scheduler-dev@chromium.org - - Total duration (reported in full seconds) of renderer tasks split per task - queue type. Note that partial seconds are rounded up/down so that they - average to the correct value when many reports are added. For more details, - check base::ScaledLinearHistogram. - - Used to monitor usage of each type of task queues. Reported each time a task - is completed. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - - Replaced with RendererScheduler.TaskDurationPerTaskType2 as of June 2018 due - to overflows (crbug.com/809668). Some metrics are incremented with large - amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - hajimehoshi@chromium.org - - Total duration of renderer per-frame tasks split per task type. Used to - monitor usage of each task type. Reported each time when task is completed - and current accumulated duration is longer than 1ms. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - - Replaced with RendererScheduler.TaskDurationPerTaskType2.DedicatedWorker as - of June 2018 due to due to overflows (crbug.com/809668). Some metrics are - incremented with large amounts that they sometimes overflow and roll - negative before they get uploaded. - - altimin@chromium.org - - Total duration of dedicated worker tasks (wall time) split by per thread - type. Reported each time when task is completed and current accumulated - duration is longer than 1ms. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - hajimehoshi@chromium.org - - Total duration (reported in full seconds) of renderer per-frame tasks split - per task type. Note that partial seconds are rounded up/down so that they - average to the correct value when many reports are added. For more details, - check base::ScaledLinearHistogram. - - Used to monitor usage of each task type. Reported each time a task is - completed. - - This metric is susceptible to problematic outliers and should be analyzed - with custom scripts accounting for that rather than from a dashboard. - - - - - altimin@chromium.org - - Total duration (repored in full seconds) of dedicated worker tasks (wall - time) split by per thread type. Note that partial seconds are rounded - up/down so that they average to the correct value when many reports are - added. For more details, check base::ScaledLinearHistogram. - - Reported each time a task is completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskDurationPerThreadType2 as of June 2018 - due to overflows (crbug.com/809668). Some metrics are incremented with large - amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - lpy@chromium.org - - Total duration of renderer tasks split by per thread type. Used to compare - CPU usage of tasks from different threads. Reported each time when task is - completed and current accumulated duration is longer than 1ms. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - altimin@chromium.org - lpy@chromium.org - - Total duration (reported in full seconds) of renderer tasks split by per - thread type. Note that partial seconds are rounded up/down so that they - average to the correct value when many reports are added. For more details, - check base::ScaledLinearHistogram. - - Used to compare CPU usage of tasks from different threads. Reported each - time a task is completed. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskDurationPerUseCase2 as of June 2018 due - to overflows (crbug.com/809668). Some metrics are incremented with large - amounts that they sometimes overflow and roll negative before they get - uploaded. - - altimin@chromium.org - farahcharab@chromium.org - - Total duration (measured in ms) of renderer main thread tasks split by - scheduler use case. Use case is a scheduler's educated guess of the current - state of the world. See renderer/use_case.h and - RendererSchedulerImpl::UpdatePolicy for more details. - - - - - altimin@chromium.org - farahcharab@chromium.org - - Total duration (reported in full seconds) of renderer main thread tasks - split by scheduler use case. Note that partial seconds are rounded up/down - so that they average to the correct value when many reports are added. For - more details, check base::ScaledLinearHistogram. - - Use case is a scheduler's educated guess of the current state of the world. - See renderer/use_case.h and - - RendererSchedulerImpl::UpdatePolicy for more details. - - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - - The delta between when a delayed task was scheduled to run and when the - RendererScheduler actually ran it. Note: to reduce overhead only 10% of - tasks are sampled. - - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - - The queueing duration for non-delayed tasks posted to the RendererScheduler. - This metric is only recorded if TrackingInfo::time_posted is set (i.e. not - on android). Note: to reduce overhead only 10% of tasks are sampled. - - - - - tasak@google.com - keishi@chromium.org - - Number of safepoints (defined by cooperative scheduling manager) inside a - single non-nested task executed on the main thread of a renderer process. - This is recorded when each non-nested task stops executing. - - - - - tasak@google.com - keishi@chromium.org - - The duration of every task slices. The non-nested task executed in main - thread of the renderer process scheduler is split into slices by the - safepoints defined by cooperative scheduling manager. This metrics doesn't - record the duration of task without any safepoints. This is recorded both - inside a safepoint and when the tasak finishes. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - tasak@google.com - keishi@chromium.org - - The duration of every non-nested task executed in main thread of the - renderer process which has more than one safepoint. This is recorded when - the task finishes. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - - - - - Replaced with RendererScheduler.TaskTime2 as of May 2017. - - sunyunjia@chromium.org - tdresser@chromium.org - - The duration of every task queued in the _renderer_ scheduler to see the - distribution of the task duration. - - - - - sunyunjia@chromium.org - tdresser@chromium.org - - The duration of every task queued in the _renderer_ scheduler to see the - distribution of the task duration. - - Note that this metric discards tasks longer than 30 seconds because they are - considered to be a result of measurement glitch. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 07/2020. Summary of collected data: https://crbug.com/1019856#c6. - - fdoray@chromium.org - etiennep@chromium.org - - Time spent running tasks from other agents between when an agent task - becomes ready and when it starts running. A non-delayed task is ready when - it is posted. A delayed task is ready when its delay expires. Recorded for 1 - out of 1000 tasks. - - - - - - Removed 11/2019. Replace with - RendererScheduler.TimeRunningOtherAgentsWhileTaskReady. - - fdoray@chromium.org - etiennep@chromium.org - - Time spent running tasks from other frames between when a frame task becomes - ready and when it starts running. A non-delayed task is ready when it is - posted. A delayed task is ready when its delay expires. Recorded for 1 out - of 1000 tasks. - - - - - maxlg@chromium.org - - The count of same-document-navigations split by whether it is the - same-document backward/forward navigation, history API navigation, or other - fragment navigation. - - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - Duration of gestures (scrolls and pinches). - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - Whether a user gesture was predicted correctly. - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - - Time between when the UserModel was last reset (which happens on navigation) - and a gesture starting. - - - - - - Removed from code 2017-08. - - alexclarke@chromium.org - Time between subsequent gestures (scrolls and pinches). - - - - altimin@chromium.org - - Number of web frame schedulers per renderer scheduler. Recorded once per - navigation. - - - - - altimin@chromium.org - - Number of web view schedulers per renderer scheduler. Recorded once per - navigation. - - - - - ppi@chromium.org - - Roundtrip times for synchronous IPC calls from the renderer to browser. - - - - - engedy@chromium.org - - For each load and dropped Mojo interface request in a frame, records a - sample with a value corresponding to the hash of the interface name, - calculated as the lower 31 bits of the interface name's metric name hash. - - Interface requests to RenderFrame::GetRemoteInterfaces are dropped when they - arrive to the RenderFrameHostImpl after the RenderFrameHostImpl had already - committed the next cross-document navigation. - - This means that |document_scoped_interface_provider_binding_| was already - unbound at the time from the interface connection that had been used to - service RenderFrame::GetRemoteInterface for the previous load, so those - interface requests are dropped. - - - - - engedy@chromium.org - - For each load in a frame, records the number of interface requests to - RenderFrame::GetRemoteInterfaces that arrived to the RenderFrameHostImpl - after the RFHI had already committed the next cross-document navigation. - - This means that |document_scoped_interface_provider_binding_| was already - unbound at the time from the interface connection that had been used to - service RenderFrame::GetRemoteInterface for the previous load, so those - interface requests are dropped. This histogram measures how often, if at - all, that happens in practice. - - - - - - Removed Oct 2018. - - alexmos@chromium.org - boliu@chromium.org - - Record whether a local root frame ever received post messages from another - cross origin frame that's not a descendent. This is useful to evaluate if a - frame is safe to be reloaded automatically. Recorded when a frame crashed - while invisible, and then becomes visible to the user; this is the point a - crashed frame would be reloaded. Note this is not logged for the main frame, - which only has descendant frames. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidChangeScrollOffset. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidClearWindowObject. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidCommitProvisionalLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidCreateScriptContext. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidFailProvisionalLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidFinishDocumentLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidFinishLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidMeaningfulLayout. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.DidStartProvisionalLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.FocusedNodeChanged. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.OnMessageReceived. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.ScriptedPrint. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.WillCommitProvisionalLoad. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.WillSendSubmitEvent. - - - - - - Removed 2/2018 - - joelhockey@chromium.org - - Cumulative time spent by all RenderFrameObservers in - RenderFrameImpl.WillSubmitForm. - - - - - ccameron@chromium.org - etienneb@chromium.org - - Time retrieve the fallback fonts on the system used for - RenderTextHarfBuzz::ShapeRuns. This metric is known to be quite slow on bad - cases. - - - - - ccameron@chromium.org - etienneb@chromium.org - - Time retrieve the preferred fallback font on the system used for - RenderTextHarfBuzz::ShapeRuns. Fallback font is determined based on the - input text and locale. - - - - - ccameron@chromium.org - etienneb@chromium.org - - This metric records the fallback font mechanism required to complete the - shaping of a text. - - - - - ccameron@chromium.org - etienneb@chromium.org - - Time to perform RenderTextHarfBuzz::ShapeRuns with retrieved the fallback - fonts. This metric is known to be quite slow on bad cases. - - - - - - Removed as of June 2020. - - jochen@chromium.org - - State of the profile that is activated via the "Open Link as User" - menu. Logged when one of the "Open Link as User" context menu - options is selected. - - - - - - Removed as of June 2020. - - jochen@chromium.org - - Whether or not other profiles are active when the "Open Link as - User" context menu is shown. Logged when the context menu is created. - - - - - - Removed as of June 2020. - - jochen@chromium.org - - Count of the profiles shown for the "Open Link as User" context - menu. Logged when the context menu is created. - - - - - avi@chromium.org - mpearson@chromium.org - Count of renderer view context menu items shown. - - - - - - avi@chromium.org - mpearson@chromium.org - chrome-analysis-team@google.com - - Count of renderer view context menu items (Only commands now) used. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - Moved to Net.Reporting.HeaderEndpointGroupOutcome. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a single endpoint group in a - Report-To header once the header itself has been parsed. - - - - - - Moved to Net.Reporting.HeaderEndpointOutcome. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a single endpoint in a Report-To - header once the header itself has been parsed. - - - - - - Moved to Net.Reporting.HeaderOutcome. - - juliatuttle@chromium.org - - The outcome of Reporting trying to process a Report-To header. Once it is - parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints - within it. - - - - - - Moved to Net.Reporting.ReportDeliveredAttempts. - - juliatuttle@chromium.org - - When Reporting successfully delivers a report, the number of unsuccessful - delivery attempts that preceded the successful one. - - - - - - Moved to Net.Reporting.ReportDeliveredLatency. - - juliatuttle@chromium.org - - The delivery latency of reports successfully delivered by Reporting. Starts - when the report is queued and finishes when the delivery attempt returns - successfully. - - - - - - Moved to Net.Reporting.ReportOutcome. - - juliatuttle@chromium.org - - The outcome of Reporting trying to deliver a report, recorded when the - report is finally erased from memory. - - - - - chlily@chromium.org - sburnett@chromium.org - - The outcome of updating the backing store. This is recorded whenever a batch - of pending operations is committed to the backing store. Success occurs when - all operations are committed successfully. Trouble is recorded when some - operations are unsuccessful but committing the batch succeeds. Failure is - recorded when the commit fails. - - - - - chlily@chromium.org - sburnett@chromium.org - - Records the detection of a corrupted meta table for the Reporting and NEL - DB. This is recorded when database migration fails to update the database to - the current version. - - - - - chlily@chromium.org - sburnett@chromium.org - - Records a failure to recover a corrupted meta table for the Reporting and - NEL DB. This is recorded when a corrupt meta table is detected (see - ReportingAndNEL.CorruptMetaTable), and attempting to recover by deleting and - reinitializing the database fails. - - - - - - Removed as of March 9, 2020. - - chlily@chromium.org - sburnett@chromium.org - - Size on disk of the Reporting and NEL database. This is recorded when the - database is initialized, which typically happens upon the first network - request after startup. - - - - - chlily@chromium.org - sburnett@chromium.org - - The outcome of initializing the SQLite database. This is recorded upon the - first load request after startup, which will typically occur upon the first - network request. - - - - - chlily@chromium.org - sburnett@chromium.org - - Whether killing the database because it was corrupted beyond repair - succeeded. This is recorded when a fatal SQLite error is detected. - - - - - chlily@chromium.org - sburnett@chromium.org - - The number of NEL policies loaded from the store. This is recorded when the - NetworkErrorLoggingService requests a load from the backing store, which - typically happens upon the first network request after startup. - - - - - chlily@chromium.org - sburnett@chromium.org - - The number of Reporting endpoint groups loaded from the store. This is - recorded when the ReportingCache requests a load from the backing store, - which happens upon receipt of the first Report-To header or queued report - after startup. - - - - - chlily@chromium.org - sburnett@chromium.org - - The number of Reporting endpoints loaded from the store. This is recorded - when the ReportingCache requests a load from the backing store, which - happens upon receipt of the first Report-To header or queued report after - startup. - - - - - chlily@chromium.org - sburnett@chromium.org - - The time (ms) taken to initialize the Reporting and NEL DB. This is recorded - when the DB is initialized, which typically occurs upon the first network - request after startup. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - The state of the requestAutocomplete() dialog when it was dismissed. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - The initial state of a user that's interacting with a freshly shown - requestAutocomplete() dialog. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - User interactions with the Autofill popup shown while filling an - requestAutocomplete() dialog. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the frequency of security warnings and errors in the - RequestAutocomplete dialog. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the duration for which an requestAutocomplete() dialog was shown. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the duration for which an requestAutocomplete() dialog was shown, - in cases where the user ended up canceling out of the dialog. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the duration for which an requestAutocomplete() dialog was shown, - in cases where the user ended up accepting the dialog. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures how users are interacting with the requestAutocomplete() dialog UI. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the duration of time it takes for the requestAutocomplete() UI to - be actionable by the user after it is shown. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the frequency of errors in communicating with the Google Online - Wallet server. - - - - - - Removed as of 5/5/2016. - - estade@chromium.org - - Measures the frequency of required user actions returned by the Google - Online Wallet server. - - - - - merkulova@chromium.org - - Records the number of times the factory reset dialog was shown. Grouped by - the viewtype. - - - - - - Removed as of 18/1/2019. - - lpy@chromium.org - - The number of IPCs from frame to GRC. Recorded every 1 minute. - - - - - - Removed as of 18/1/2019. - - lpy@chromium.org - - The number of IPCs from page to GRC. Recorded every 1 minute. - - - - - - Removed as of 18/1/2019. - - lpy@chromium.org - - The number of IPCs from process to GRC. Recorded every 1 minute. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database after deleting - it after a failed repair attempt. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database after a repair - attempt. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - The result of trying to repair the Local Site Characteristics database after - a failed open. - - - - - - Removed July 2020. - - - - sebmarchand@chromium.org - - The cumulative observation time before a feature tracked in the Local Site - Characteristics database gets used. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - The size of the Local Site Characteristics database on disk. Recorded at - startup when the database gets opened. - - - - - - Removed July 2020. - - sebmarchand@chromium.org - - Boolean indicating if the read operation from the Local Site Characteristics - database has completed when we query for the characteristics of a site. - - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - The amount of wall-clock time a measurement cycle occupied. - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - - The number of unexpected processes encountered during memory measurement. - This is expected to be non-zero as new processes can be created after a - measurement cycle is initiated, plus non-renderer processes are counted here - at the moment. - - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - - A boolean that measures how often a performance measurement notification - arrives at a WebContents that has been re-navigated. - - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - - An enumeration indicating the outcome of each memory measurement attempt. - - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - - The number of processes that didn't get a memory measurement. This can - happen if processes die as or after measurement is initiated. - - - - - - Removed April 2019. No longer recorded. - - siggi@chromium.org - - The number of processes that were measured for CPU at least. - - - - - - Obsoleted July 2020. - - tbansal@chromium.org - - The count of resource loading blocking patterns received by the renderer. - Recorded every time resource loading hints mojom message is received. - Recorded at most once per triggered navigation. - - - - - - Removed 03/2019 as it was never a useful metric. - - tbansal@chromium.org - - The count of page hints received by the browser from the component updater. - Recorded every time a page hint is received by the browser from the - optimization guide service. - - - - - - Removed 03/2019 as it was never a useful metric. - - tbansal@chromium.org - - The total count of page hints received by the browser from the component - updater. Only the page hints that have at least one resource loading hint - are counted. One sample is recorded every time optimization guide service - processes the optimization hints provided by the component updater. The - count of hints loaded to memory may be lower than this. - - - - - - Removed 03/2019 as it was never a useful metric. - - tbansal@chromium.org - - The total count of resource loading hints across all page hints received by - the browser from the component updater. One sample is recorded every time - optimization guide service processes the optimization hints provided by the - component updater. The count of hints loaded to memory may be lower than - this. - - - - - tbansal@chromium.org - - Records if the loading of a resource was blocked because the resource URL - matched the resource loading hints. Recorded every time a resource load is - requested. - - - - - tbansal@chromium.org - - Records the resource load priority of a resource when its loading is not - blocked due to the resource loading hints. Recorded every time a resource - load is requested, and the load is not blocked due to the resource loading - hints. - - - - - tbansal@chromium.org - - Records the resource load priority of a resource when its loading is blocked - due to the resource loading hints. Recorded every time a resource load is - requested and the resource load is blocked because the resource URL matched - the resource loading hints. - - - - - - Obsoleted July 2020. - - tbansal@chromium.org - - Records if the resource patterns were available at the time of page commit - if the committed previews type was RESOURCE_LOADING_HINTS. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - Records if the resource patterns were available at the time of page commit - if the committed previews type was RESOURCE_LOADING_HINTS and the navigation - was redirected. This is a subset of the ResourcePatternsAvailableAtCommit - histogram. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - Like HttpCache.Pattern but only for requests made during speculative - prefetch. Logged per successful request. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - This metric measures the host coverage of the predictor database: On each - navigation, it records what percentage of the top X history entries are - found in the predictor DB. Caveats: (1) This metric is only recorded once - the user has accumulated enough browsing history, implemented as a minimum - threshold of total page visits by the user. (2) This metric is sampled, so - it's actually only recorded for 1 out of every K navigations. - - - - - - Removed October 2016. No longer recorded. - - zhenw@chromium.org - - A boolean that used to indicate a corner case when certain resources are not - written to the Predictor database becuase their URLs are too long. We - monitor this number to ensure that we do not discard too many resources. - - - - - - Removed 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent. - - zhenw@chromium.org - - A boolean that indicates if the speculative resource prefetch predictor has - predictions for a Navigation. This is updated on each navigations and helps - us determine the coverage of the predictor. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - A boolean that used to indicate a corner case when we may not have prefetch - results even though prefetching is enabled and predictions are present, - because another navigation in the same tab canceled the prefetching of the - previous load. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - The visit count of a URL in the history database, measured when the onload - fires for the URL. Helpful in figuring out what visit count should be used - to start learning about a URL. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Assuming a fixed number (25 or 50) of URLs could be prefetched max, how many - would be available for prefetch (after we apply our heuristics for picking - subresources to prefetch for a navigation). - - This stat is recorded when the predictor uses the host of the main frame url - as the key for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the cache restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the host of the main frame url - as the key for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the network restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the host of the main frame url - as the key for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Similar to ResourcePrefetchPredictor.Host.PredictedPrefetchFromNetwork but - as a percent of the total number of resources the page actually fetched from - the network. This depcits the major gains that we can get. - - This stat is recorded when the predictor uses the host of the main frame url - as the key for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page not used - by the page, restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the host of the main frame url - as the key for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - prefetches cancelled as a percentage of the total number of resources that - the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - prefetches failed as a percentage of the total number of resources that the - predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from cache while prefetching but were not - requested by the page, as a percentage of the total number of resources that - the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from cache while prefetching and also came - from the cache when the page requested it, as a percentage of the total - number of resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from cache while prefetching but came from - the network when the page requested it, as a percentage of the total number - of resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from network while prefetching but were not - requested by the page, as a percentage of the total number of resources that - the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from network while prefetching but came from - the cache when the page requested it, as a percentage of the total number of - resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of - successful prefetches that came from cache while prefetching and also came - from the network when the page requested it, as a percentage of the total - number of resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of resources - that were prefetchable but were not prefetched as a percentage of - prefetchable resources. - - - - - - Removed January 2017. This is effectively the same as - ResourcePrefetchPredictor.HostTableRowCount2 after refactoring of the - predictor database. - - zhenw@chromium.org - - The count of number of unique hosts in the HostTable, i.e. the number of - hosts that the database has prediction data for. This data is useful for - determining the recall/precision as a function of the number of hosts that - need to be tracked by the database. Measured at startup. - - - - - - Removed January 2017. Replaced by - ResourcePrefetchPredictor.HostTableRowCount2. - - zhenw@chromium.org - - The count of number of rows in the HostTable. This is effecively the number - of (host, resource URL) pairs in the database. This is measured at startup - and used to get an estimate of the data size. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - The number of rows in the HostTable. This is effectively the number of hosts - in the database. This is measured at startup and used to get an estimate of - the data size. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - When the prefetch predictor has resources in the local database for a given - navigation, the count of predicted urls. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - When the prefetch predictor has resources in the local database for a given - navigation, the precision of the predictions, in percentage. This is - computed as 100 \times \frac{correct predictions}{predictions}. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - When the prefetch predictor has resources in the local database for a given - navigation, the recall of the predictions, in percentage. This is computed - as 100 \times \frac{correct predictions}{all prefetchable subresources}. - - - - - - Obsoleted in M-69. - - alexilin@chromium.org - - Records stats about main frame navigations. Records the total number of - requests/responses/redirects for main frame urls along with the numbers for - how often the predictor can process such events. This is useful to figure - out what percentange of requests are handled by the predictor and also for - sanity checking the other stats. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Records stats about various interesting events such as - request start, - response start, redirect, onload, etc during the load of a main frame. - Essential for understanding the complete life of a navigation request start - to the onload fire and the events that occur in between. - - - - - - Removed 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent. - - zhenw@chromium.org - - The status of various navigations from the view point of the 'onload' event. - Since we measure the prediction accuracy and learn navigation subresources - on the onload event, it is useful to know how many of the navigations are - abandoned before 'onload' fires. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Records the number of pages on each type of network after a page is loaded. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Page load time. It starts from when the main frame URL request is sent out - to when the main frame document load is completed. - - This is recorded for both prefetched and non-prefetched pages. - - - - - - Removed 01/2013. Replaced with specific ones for Url and Host. - - zhenw@chromium.org - - Assuming a fixed number of URLs could be prefetched max, how many would be - available for prefetch (after we apply our heuristics for picking - subresources to prefetch for a navigation). - - - - - - Removed 01/2013. Replaced with specific ones for Url and Host. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the cache restricted to some max predictions. - - - - - - Removed 01/2013. Replaced with specific ones for Url and Host. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the network restricted to some max predictions. - - - - - - Removed 01/2013. Replaced with specific ones for Url and Host. - - zhenw@chromium.org - - Similar to ResourcePrefetchPredictor.Predicted.PrefetchFromNetwork but as a - percent of the total number of resources the page actually fetched from the - network. This depcits the major gains that we can get. - - - - - - Removed 01/2013. Replaced with specific ones for Url and Host. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page not used - by the page, restricted to some max predictions. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - The count of successfully prefetched subresources for a single page. - Recorded after all subresource prefetches have reached a terminal - success/failure state. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - The total amount of data consumed by predictor for a single page. Only - successfully finished requests taken into account. Recorded after all - subresource prefetches have reached a terminal success/failure state. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Number of resources that were prefetched and requested by a page load, for - cached requests. Logged after the prefetcher completes. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Number of resources that were prefetched and requested by a page load, for - non cached requests. Logged after the prefetcher completes. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Amount of useful data fetched from the network for a prefetch request. This - is the total size of the resources accounted for in - ResourcePrefetchPredictor.PrefetchHitsCount.NotCached. Logged after the - prefetcher completes. - - - - - - Removed at M72. No longer recorded. - - alexilin@chromium.org - - Amount of time available for prefetching. Specifically, this is a time - interval between corresponding StartPrefetching() and StopPrefetching() - calls. This is recorded for both prefetched and non-prefetched pages. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Number of resources that were prefetched but not requested by a page load, - for cached requests. Logged after the prefetcher completes. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Number of resources that were prefetched but not requested by a page load, - for non cached requests, that is waste. Logged after the prefetcher - completes. - - - - - - Removed at M66. No longer recorded. - - lizeb@chromium.org - - Amount of wasted data fetched from the network for a prefetch request. This - is the total size of the resources accounted for in - ResourcePrefetchPredictor.PrefetchMissesCount.NotCached. Logged after the - prefetcher completes. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - When the prefetch predictor has resources in the local database for a given - navigation, records stats about whether redirect was predicted correctly or - incorrectly. - - - - - - Removed at M72. No longer recorded. - - alexilin@chromium.org - - Records stats about various interesting events such as - when partial or all - of history is cleared. It will include events which do not necessarily - happen during a navigation (which are reported in - ResourcePrefetchPredictor.NavigationEvent). - - - - - - Obsoleted in M-69. - - alexilin@chromium.org - - Records stats about requests, redirects, and responses observed by the - LoadingPredictorObserver. These stats are useful as a baseline for other - stats. - - - - - - Removed 08/2016 with the removal of the recording code. - - zhenw@chromium.org - - The distribution of the reasons for which subresources are ignored during - prefetching. This helps us prioritze reasons we should further investigate - to increase coverage. This is reported as a bit map and every status will be - a bitwise or of the underlying reasons. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Assuming a fixed number of URLs could be prefetched max (25 or 50), how many - would be available for prefetch (after we apply our heuristics for picking - subresources to prefetch for a navigation). - - This stat is recorded when the predictor uses the main frame url as the key - for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the cache restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the main frame url as the key - for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page and served - from the network restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the main frame url as the key - for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - Similar to ResourcePrefetchPredictor.Url.PredictedPrefetchFromNetwork but as - a percent of the total number of resources the page actually fetched from - the network. This depcits the major gains that we can get. - - This stat is recorded when the predictor uses the main frame url as the key - for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - When we have predictions for a navigation, we measure the accuracy of the - predictions against the actual resources downloaded. This histogram gives - the distribution of the predictions that were fetched by the page not used - by the page, restricted to some max predictions (25 or 50). - - This stat is recorded when the predictor uses the main frame url as the key - for prediction. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of prefetches - cancelled as a percentage of the total number of resources that the - predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of prefetches - failed as a percentage of the total number of resources that the predictor - tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from cache while prefetching but were not requested by - the page, as a percentage of the total number of resources that the - predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from cache while prefetching and also came from the - cache when the page requested it, as a percentage of the total number of - resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from cache while prefetching but came from the network - when the page requested it, as a percentage of the total number of resources - that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from network while prefetching but were not requested - by the page, as a percentage of the total number of resources that the - predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from network while prefetching but came from the cache - when the page requested it, as a percentage of the total number of resources - that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on the main frame URL, the percentage of successful - prefetches that came from cache while prefetching and also came from the - network when the page requested it, as a percentage of the total number of - resources that the predictor tried to prefetch. - - - - - - Removed September 2016. No longer recorded. - - zhenw@chromium.org - - For prefetching based on host of main frame URL, the percentage of resources - that were prefetchable but were not prefetched as a percentage of - prefetchable resources. - - - - - - Removed September 2016. This is effectively the same as - ResourcePrefetchPredictor.UrlTableRowCount2 after refactoring of the - predictor database. - - zhenw@chromium.org - - The count of number of unique main frame urls in the UrlTable, i.e. the - number of webpages that the database has prediction data for. This data is - useful for determining the recall/precision as a function of the number of - webpages that need to be tracked by the database. Measured at startup. - - - - - - Removed October 2012. No longer recorded. - - zhenw@chromium.org - - The count of number of unique main frame urls that are deleted from the URL - table at startup because they are no longer in history. Essential to figure - out how much data we are loosing out. - - - - - - Removed October 2012. No longer recorded. - - zhenw@chromium.org - - Same as ResourcePrefetchPredictor.UrlTableMainFrameUrlsDeletedNotInHistory - but recording percentage of URLs in the table rather than absolute numbers. - - - - - - Removed January 2017. Replaced by - ResourcePrefetchPredictor.UrlTableRowCount2. - - zhenw@chromium.org - - The count of number of rows in the UrlTable. This is effecively the number - of (main frame URL, resource URL) pairs in the database. This is measured at - startup and used to get an estimate of the data size. - - - - - - Removed at M66. No longer recorded. - - alexilin@chromium.org - - The number of rows in the UrlTable. This is effectively the number of main - frame URLs in the database. This is measured at startup and used to get an - estimate of the data size. - - - - - - Removed 04/2020. - - afakhry@chromium.org - - The CPU usage range reported for the browser process when the Chrome OS - device memory pressure (which is the percentage of total memory used by the - system) is critical. This is emitted only when memory pressure changes from - a low pressure to a higher pressure. - - - - - - Removed 04/2020. - - afakhry@chromium.org - - The system memory usage range reported for the browser process when the - Chrome OS device memory pressure (which is the percentage of total memory - used by the system) is critical. This is emitted only when memory pressure - changes from a low pressure to a higher pressure. - - - - - - Removed 04/2020. - - afakhry@chromium.org - - The CPU usage range reported for the GPU process when the Chrome OS device - memory pressure (which is the percentage of total memory used by the system) - is critical. This is emitted only when memory pressure changes from a low - pressure to a higher pressure. - - - - - - Removed 04/2020. - - afakhry@chromium.org - - The system's RAM memory usage range reported for the GPU process when the - Chrome OS device memory pressure (which is the percentage of total memory - used by the system) is critical. This is emitted only when memory pressure - changes from a low pressure to a higher pressure. - - - - - tbansal@chromium.org - - The number of active resource scheduler clients indicates the severity of - system contention. A client is active when it has at least one request - either in the pending request queue owned by the client or in flight. This - is emitted when a new resource scheduler client is created. - - - - - tbansal@chromium.org - - The amount of time the ResourceScheduler queued a browser initiated request - that was expected to be heavy (i.e., has large request/response sizes). - Recorded when the request is dispatched by the resource scheduler to the - network stack. Recorded only when the traffic annotation tag of the request - is present in the set of annotation tags that can be throttled. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the ResourceScheduler is informed of a - Client's creation or starts loading and when that Client finishes loading in - a Client which has been user-observable the entire time. - - Note: Will not include time for the main resource if PlzNavigate is in use. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the ResourceScheduler is informed of a - Client's creation or starts loading and when that Client finishes loading in - a Client which has been background the entire time. - - Note: Will not include time for the main resource if PlzNavigate is in use. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the ResourceScheduler is informed of a - Client's creation or starts loading and when that Client finishes loading in - a Client which has switched between Active and Background. - - Note: Will not include time for the main resource if PlzNavigate is in use. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between the last time that a Client becomes - user-observable and when that Client finishes loading in a Client that was - user-observable when the load completed. - - Note: Will not include time for the main resource if PlzNavigate is in use. - - - - - tbansal@chromium.org - - Records how long after the start of a delayable resource request, a - non-delayable resource request arrived. This is the duration of time that - the delayable request should have been queued for so as to avoid any network - contetion with later-arriving non-delayable requests. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - The duration of time between the end of a non-delayable resource request to - the start of the next non-delayable resource request. Recorded at the start - of all non-delayable requests that are preceeded by at least one completed - non-delayable request in the same resource scheduler client. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - The duration of time between the end of a non-delayable resource request to - the start of the next non-delayable resource request. Recorded at the start - of all non-delayable requests that are preceeded by at least one completed - non-delayable request in the same resource scheduler client. Recorded only - when a non-delayable request is NOT in-flight. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - The duration of time between the start of a non-delayable resource request - or end of a non-delayable request (whichever happened later) to the start of - the next non-delayable resource request. Recorded at the start of all - non-delayable requests that are preceeded by at least one started - non-delayable request in the same resource scheduler client. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - The duration of time between the start of a non-delayable resource request - to the start of the next non-delayable resource request. Recorded at the - start of all non-delayable requests that are preceeded by at least one - started non-delayable request in the same resource scheduler client. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - The duration of time between the start of a non-delayable resource request - to the start of the next non-delayable resource request. Recorded at the - start of all non-delayable requests that are preceeded by at least one - started non-delayable request in the same resource scheduler client. - Recorded only when a delayable request is in-flight. - - - - - tbansal@chromium.org - - Records the number of delayable requests in-flight when a non-delayable - request is started. - - - - - csharrison@chromium.org - - The number of LoadAnyStartablePendingRequests scans that were skipped due to - smarter task scheduling around reprioritization. - - - - - tbansal@chromium.org - - Records the highest number of delayable requests that were in-flight when - the given request with higher priority was in-flight. - - - - - tbansal@chromium.org - dougarnett@chromium.org - - Within a request's lifetime, the peak observed queueing delay tells whether - the request was affected by the network congestion. Records the maximum - network queueing delay when the given request was in-flight. This is emitted - when the request is completed. - - - - - tbansal@chromium.org - - The amount of time the ResourceScheduler queued a request. Recorded in - separate histograms based on the request loading priority at the time the - request was dequeued. - - - - - jfwang@chromium.org - tbansal@chromium.org - - Records the count of number of requests in-flight. Recorded when a request - is started by the resource scheduler. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time the ResourceScheduler is throttling a request after - WillStartRequest is called for a request in a client that was - user-observable at creation and start time. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time the ResourceScheduler is throttling a request after - WillStartRequest is called for a request in a client that was background at - creation and start time. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time the ResourceScheduler is throttling a request after - WillStartRequest is called on a request without a Client or a request in a - Client which is in a different state since the request was made. Note that - this won't capture requests which have switched state an even number of - times. Switching from Active to Background back to Active will be recorded - in the Active version of this histogram. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the request was created and when the - ResourceScheduler stops throttling the request in a client that was - user-observable at creation and start time. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the request was created and when the - ResourceScheduler stops throttling the request in a client that was - background at creation and start time. - - - - - - Removed 1/2016 - - aiolos@chromium.org - - The amount of time between when the request was created and when the - ResourceScheduler stops throttling a request without a client or a request - in a Client which is in a different state since the request was made. Note - that this won't capture requests which have switched state an even number of - times. Switching from Active to Background back to Active will be recorded - in the Active version of this histogram. - - - - - wzang@chromium.org - - Record if updating |should_send_rlz_ping| in RW_VPD is successful within the - maximum retry counts. - - - - - mpolzer@google.com - managed-platforms@google.com - - The result when attempting to restore data during a Chrome OS rollback. - - - - - mpolzer@google.com - managed-platforms@google.com - - The result when attempting to save data during a Chrome OS rollback. - - - - - - Removed in M76. - - shampson@chromium.org - steveanton@chromium.org - - The amount of data that gets read out via each call to the RTCQuicStream - readInto() API. The RTCQuicStream can record multiple ReadIntoAmountBytes in - its lifetime. - - - - - - Removed in M76. - - shampson@chromium.org - steveanton@chromium.org - - How data is read out with a finish (FIN) bit for each call to the - RTCQuicStream readInto API. The RTCQuicStream can record multiple - ReadIntoResults in its lifetime. - - - - - - Removed in M76. - - shampson@chromium.org - steveanton@chromium.org - - The amount of data that gets written via each call to the RTCQuicStream - write() API. The RTCQuicStream can record multiple WriteAmountBytes in its - lifetime. - - - - - - Removed in M76. - - shampson@chromium.org - steveanton@chromium.org - - How data is written with a finish (FIN) bit for each call to the - RTCQuicStream write() API. The RTCQuicStream can record multiple WriteUsages - in its lifetime. - - - - - - Replaced with Tabs.SadTab.* in R20. - - Please list the metric's owners. Add more owner tags as needed. - - Track number of times we built a sad tab page for a renderer crash or kill. - The user may not have seen the page if it was not the frontmost tab. - - - - - - Replaced with Tabs.SadTab.* in R20. - - Please list the metric's owners. Add more owner tags as needed. - - Track number of times the user actually saw a sad tab page for a renderer - crash or kill. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - For users known to be already enrolled in Advanced Proection, records the - service error of refreshing OAuth2 access token during fetching the user's - advanced protection status. Logged once a day and will retry on transient - failures. This is a subset of - SafeBrowsing.AdvancedProtection.TokenFetchStatus. - - - - - drubey@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the service error of refreshing OAuth2 access token during fetching - the user's advanced protection status. Logged at startup for all users, once - a day for AP users, and will retry on transient failures. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records if the telemetry ping sent for APK download contained a full - referrer chain, or if there was an error collecting the referrer chain. - Logged each time a user opted into extended reporting downloads an APK file - from a normal window on Android. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a telemetry ping for APK download was sent, or if not, then - why not. Logged each time a user downloads an APK file on Android. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the resource type that triggers the safe browsing blocking page. Logged - each time a safe browsing blocking page is created. This metric is useful to - show the priority of checking each resource type in real time. Note that - this metric may be bias towards mainframe, because the default resource type - is set to mainframe. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether the Safe Browsing check via CheckBrowseUrl method matched any - local hash prefixes. Logged each time the Safe Browsing reputation of a URL - is checked using local blocklists. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts the number of times the Safe Browsing reputation lookup timeout - happens. Logged each time the Safe Browsing reputation of a URL is checked. - - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the height of content area when the user opens a new browser window - or when the user finishes resizing a browser window. - - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the width of content area when the user opens a new browser window - or when the user finishes resizing a browser window. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the duration from the time the binary is uploaded for deep - scanning of a download request until the time the user decides to bypass the - verdict. It is logged once for each binary upload when the user bypasses the - verdict. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the bytes/sec from the size of a download request divided by - the duration of a successful deep scanning upload request. It is logged once - for each successful binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request. It is - logged once for each binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - FailedToGetToken result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - non-successful scan verdict. It is logged once for each binary upload with - that result. - - - - - rogerta@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - FileEncrypted result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - FileTooLarge result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - Success result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - SB.This records the deep scanning duration of a user download request with a - Timeout result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with an - Unknown result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user download request with a - UnsupportedFileType result. It is logged once for each binary upload with - that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the bytes/sec from the size of an upload request caused by a - "drag and drop" from the user divided by the duration of a - successful deep scanning upload request. It is logged once for each - successful binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the duration from the time the binary is uploaded for deep - scanning of a "drag and drop" until the time the user decides to - cancel the upload. It is logged once for each binary upload when the user - bypasses the verdict. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request. It is logged once for each binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a FailedToGetToken result. It is logged once for each binary - upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a non-successful scan verdict. It is logged once for each - binary upload with that result. - - - - - rogerta@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a FileEncrypted result. It is logged once for each binary - upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a FileTooLarge result. It is logged once for each binary upload - with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a Success result. It is logged once for each binary upload with - that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - SB.This records the deep scanning duration of a user "drag and - drop" request with a Timeout result. It is logged once for each binary - upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with an Unknown result. It is logged once for each binary upload - with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user "drag and drop" - request with a UnsupportedFileType result. It is logged once for each binary - upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the bytes/sec from the size of a user paste request divided by - the duration of a successful deep scanning upload request. It is logged once - for each successful binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the duration from the time the binary is uploaded for deep - scanning of a paste until the time the user decides to cancel the upload. It - is logged once for each binary upload when the user bypasses the verdict. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request. It is - logged once for each binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - FailedToGetToken result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - non-successful scan verdict. It is logged once for each binary upload with - that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - FileTooLarge result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - Success result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - Timeout result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with an - Unknown result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user paste request with a - UnsupportedFileType result. It is logged once for each binary upload with - that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the bytes/sec from the size of an upload request divided by the - duration of a successful deep scanning upload request. It is logged once for - each successful binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the duration from the time the binary is uploaded for deep - scanning of an upload until the time the user decides to cancel the upload. - It is logged once for each binary upload when the user bypasses the verdict. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request. It is - logged once for each binary upload. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - FailedToGetToken result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - non-successful scan verdict. It is logged once for each binary upload with - that result. - - - - - rogerta@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - FileEncrypted result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - FileTooLarge result. It is logged once for each binary upload with that - result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - Success result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - SB.This records the deep scanning duration of a user upload request with a - Timeout result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with an - Unknown result. It is logged once for each binary upload with that result. - - - - - domfc@chromium.org - webprotect-team@google.com - - This records the deep scanning duration of a user upload request with a - UnsupportedFileType result. It is logged once for each binary upload with - that result. - - - - - meacer@chromium.org - chrome-safebrowsing-alerts@google.com - - Records when a user in the Delayed Warnings experiment group visits a page - with a delayed SafeBrowsing phishing warning, triggers the delayed warning - (via keypress), or leaves the page without interacting. Only recorded when - user has not disabled URL elision via "Always Show Full URLs" - context menu item, or by installing the Suspicious Site Reporter extension. - - - - - meacer@chromium.org - chrome-safebrowsing-alerts@google.com - - Same as SafeBrowsing.DelayedWarnings.Event but only recorded when user has - disabled URL elision via "Always Show Full URLs" context menu - item, or by installing the Suspicious Site Reporter extension. - - - - - meacer@chromium.org - estark@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how long a user in the Delayed Warnings experiment group spends on a - page with a delayed SafeBrowsing phishing warning. The time is recorded from - when the page loads to when the warning is shown or the user leaves the - page, whichever comes first. Only recorded when user has not disabled URL - elision via "Always Show Full URLs" context menu item, or by - installing the Suspicious Site Reporter extension. - - - - - meacer@chromium.org - estark@chromium.org - chrome-safebrowsing-alerts@google.com - - Same as SafeBrowsing.DelayedWarnings.TimeOnPage but only recorded when user - has disabled URL elision via "Always Show Full URLs" context menu - item, or by installing the Suspicious Site Reporter extension. - - - - - - Not in the code anymore (10/2015). - - feng@chromium.org - - Records the user action that enables/disables safe browsing feature in the - Settings page on Android. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The result of reading/parsing/accepting a new proto for the FileTypePolices - repo of file extensions and their meta data. - - This is for the file types loaded from the component-update system. This - includes both those loaded from disk shortly after startup, and those - received over the network when the component version changes - - - - - - Removed in M80 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Number of file types (aka file extensions) present in the FileTypePolicies - proto loaded. - - This is for the file types loaded from the component-update system. This - includes both those loaded from disk shortly after startup, and those - received over the network when the component version changes - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Integer version number citing which version of the proto data chrome just - loaded. Latest version is in download_file_types.asciipb. - - This is for the file types loaded from the component-update system. This - includes both those loaded from disk shortly after startup, and those - received over the network when the component version changes - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The result of reading/parsing/accepting a new proto for the FileTypePolices - repo of file extensions and their meta data. - - This is for the file types loaded from the resource bundle packaged with - Chrome, which is always loaded at startup. - - - - - - Removed in M80 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Number of file types (aka file extensions) present in the FileTypePolicies - proto loaded. - - This is for the file types loaded from the resource bundle packaged with - Chrome, which is always loaded at startup. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Integer version number citing which version of the proto data chrome just - loaded. Latest version is in download_file_types.asciipb. - - This is for the file types loaded from the resource bundle packaged with - Chrome, which is always loaded at startup. - - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Records the default font size on user startup. - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Records the default fixed font size on user startup. - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Records the minimum font size on user startup. - - - - - Removed in M77. Was used to get a general sense of this value when planning - visual features in PhishGuard pings. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Records the minimum logical font size on user startup. - - - - - Replaced by SafeBrowsing.V4GetHash.Network.Result. - - kcarattini@google.com - - Response or error codes from the SafeBrowsing Pver4 service. Logged after a - GetHash or request finishes to capture the response code or error code for - that call. - - - - - - Replaced by SafeBrowsing.V4GetHash.Network.Time. - - kcarattini@chromium.org - - The time that it took to receive a response from the Safe Browsing servers - for a V4 GetHash request. - - - - - - Replaced by SafeBrowsing.V4GetHash.Result. - - kcarattini@chromium.org - - Track return status from V4 GetHash attempts. The buckets of this histogram - overlap, so the counts cannot be used as percentages. - - - - - ntfschr@chromium.org - src/android_webview/OWNERS - - Which interstitial type is being displayed to the user? This currently - applies only to WebView (where we show Loud vs. Quiet interstitials). - - - - - - No longer used. Removed 2020-06. - - csharp@chromium.org - proberge@google.com - - A windows only historgram. Records when an unknown base relocation type is - encountered while reading the reloc table of a loaded module. - - - - - - Removed in M71+. - - chrome-safebrowsing-alerts@google.com - - Count of how many ResolvedIPAddresses get removed in each periodic clean up. - This is a rough estimation of the number of IPs associated with main frame - and sub-frame navigations every two minutes. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Count of how many NavigationEvents get removed in each periodic clean up. - This is a rough estimation of the number of navigations every two minutes. - - - - - - Removed in M85+. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The net error code for failed reports sent by NotificationImageReporter, or - net::OK if successful. - - - - - - Replaced by SafeBrowsing.V4GetHash.Parse.Result. - - kcarattini@chromium.org - - Track the parsing results of a status 200 GetV4Hash request. - - - - - - Replaced by SafeBrowsing.V4Update.Parse.Result. - - chrome-safebrowsing-alerts@google.com - - Track the parsing results of a status 200 GetV4Update request. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the Safe Browsing enhanced protection service is currently enabled. - Recorded for all non-Incognito profiles on profile startup. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the Safe Browsing extended reporting service is currently enabled. - Recorded for all non-Incognito profiles on profile startup. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the Safe Browsing service is currently enabled. Recorded for all - non-Incognito profiles on profile startup. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the current user has ever seen a security interstitial. Recorded for - all non-Incognito profiles on profile startup. - - - - - - Removed in or before M86. See SafeBrowsing.Pref.Extended - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the Extended Reporting preference transition. Suffixes track which - opt-in text users are viewing and the values of each Extended Reporting - preference. Recorded for all non-Incognito profiles on profile startup. - - - - - - This is unused due to it being part of SBER1. Deprecated 06/01/2020. - - lpz@chromium.org - - Tracks user decisions about the Extended Reporting opt-in on security - interstitials by comparing the initial and final states of the preference. - Suffixes specify the type of change that was made. Recorded when a user - closes a security interstitial or navigates away. - - - - - - Removed in or before M86. See SafeBrowsing.Pref.Extended.* - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the Extended Reporting preference being changed. Suffixes track which - Extended Reporting preference was changed, and the specific UI that the - change was made on. Recorded when a user changes the preference on any UI. - - - - - - Removed in or before M86. - - lpz@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks reasons for the Extended Reporting preference transition, such as a - user entering an experiment group or seeing a security interstitial for the - first time. Recorded for all non-Incognito profiles on profile startup. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The result of referrer attribution, including different types of success or - failure. This is incremented each time a safe browsing ping or download ping - is generated. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Number of times referrer attribution encounters an invalid tab ID. This is - incremented a safe browsing ping or download ping is generated and an - invalid tab ID is encountered during attribution. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The length of referrer URL chain we get from referrer attribution. This is - logged each time a safe browsing ping or download ping is generated. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether the local Safe Browsing stores are available. If not, all URLs - are marked as safe during real time URL lookup. Logged each time a top frame - URL navigation happens for users who have the real time URL lookups enabled. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs if the real time URL lookup service is currently in backoff state due - to previous errors. Logged each time a top frame URL navigation happens in - non-incognito mode for users who have real time URL lookups enabled. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the time it takes to run a cleanup task in cache manager. Logged each - time a cleanup task is run. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of real time URL verdicts stored for this profile. Logged - each time a new real time url verdict is cached. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether Safe Browsing database can be checked in Safe Browsing URL - checker. Logged each time a URL is checked by Safe Browsing URL checker. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the latency between the start of getting a result from the cache and - when the cache is actually obtained. The time includes bouncing between IO - and UI threads. This is an indicator of the efficiency of loading the cache. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the result of real time URL cache lookup. If the result is - VERDICT_TYPE_UNSPECIFIED, that means cache miss and a ping will be sent - afterwards. Otherwise, ping won't be sent. This is an indicator of cache hit - rate. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the latency between the start of a token request and when the token is - actually obtained. Logged each time a user performs a real-time Safe - Browsing check with token. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether a token received from the token fetcher is nonempty. Logged - each time a response is received from the token fetcher. It shows the - validity of the tokens received from the token fetcher. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether a token is attached when a URL lookup request is sent. Logged - each time a URL lookup request is sent. It shows the percentage of URL - lookup requests that are attached with tokens. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs if cache manager is valid when real time URL check is enabled. Logged - each time if the URL doesn't match the high confidence allowlist. Ideally, - cache manager should be valid whenever real time URL check is enabled. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether the real time lookup service is available when a real time URL - check is needed. The real time lookup service is available if it is not - nullptr and it is not in backoff mode. Logged when real time URL check is - enabled and the URL doesn't match the allowlist. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs whether the response of the real time URL lookup is successful. Logged - on each resource check for which a lookup request is sent to the server. A - failure can be either a network error or a parsing error. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the result of checking the URL against the local Safe Browsing high - confidence allowlist. Logged each time a top frame URL navigation happens - for users who have the real time URL lookups enabled. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Response or error codes from SafeBrowsing real time URL lookups. Logged on - each resource check for which a lookup request is sent to the server. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the roundtrip time it took to perform a Safe Browsing real time URL - lookup. Logged on each resource check for which a lookup request is sent to - the server. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the user population that was checked by Safe Browsing real time URL - lookup. Logged on each resource check for which a lookup request is sent to - the server. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the resource type that was checked by Safe Browsing real time URL - lookup. Logged on each resource check that is eligible for real time checks. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the resource type that was requested to be checked by Safe Browsing - real time URL lookup. Logged on each resource check. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the number of verdicts received in the real time URL check response. - Logged on each resource check for which a lookup request is sent to the - server. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the user action performed on the Safe Browsing settings page. Depending - on the enum value, logged when the page is showned to the user or when the - user performs an action on the page. - - - - - - Removed in M78 due to lack of use and utility. See crbug.com/975258 - - lpz@chromium.org - - A threat report contains a DOM hierarchy that is ambiguous. This indicates - that the parent/child relationship among the elements in the DOM may not be - accurate. - - - - - - Removed in M78 due to lack of use and utility. See crbug.com/975258 - - lpz@chromium.org - - Whether the threat report generated for a subframe of a page hit the maximum - number of nodes. When this is true, the data from that frame will be - truncated. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Logs the error type from the token fetcher. Logs each time safe browsing - gets a response from the token fetcher. When the error type is none, it - means the token is obtained successfully. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the actions taken by the Ad Popup trigger whenever it is executed. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the actions taken by the Ad Redirect trigger whenever it is executed. - It is logged when we detect a blocked redirect attempt caused by an ad. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the actions taken by the Ad Sampling trigger whenever it is executed. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the state of the Suspicious Site trigger when its report delay timer - fires. Used to investigate variance in event order. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the events occurring in the Suspicious Site trigger whenever it is - executed. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Tracks the reasons that a report requested by the Suspicious Site trigger is - rejected by the Trigger Manager. - - - - - - Removed 09-2020 since this is no longer recorded. - - dtrainor@chromium.org - chrome-safebrowsing-alerts@google.com - - File types that were allowed to be downloaded without verifying their - content nor their source URLs with Safe Browsing. - - - - - - Removed 09-2020 since this is no longer recorded. - - dtrainor@chromium.org - chrome-safebrowsing-alerts@google.com - - File types that were allowed to be downloaded without verifying their - content nor their source URLs with Safe Browsing due to the requestor URL - being on the Safe Browsing whitelist. Each sample recorded on this histogram - is also recorded in SafeBrowsing.UnverifiedDownloads.Allowed. - - - - - - Removed 09-2020 since this is no longer recorded. - - dtrainor@chromium.org - chrome-safebrowsing-alerts@google.com - - File types that were allowed to be downloaded without verifying their - content nor their source URLs with Safe Browsing due to the SafeBrowsing - service being disabled. Each sample recorded on this histogram is also - recorded in SafeBrowsing.UnverifiedDownloads.Allowed. - - - - - - Removed 09-2020 since this is no longer recorded. - - dtrainor@chromium.org - - Count of alternate extensions that were supplied when attempting to download - a file without verifying their content nor their source URLs with Safe - Browsing. - - - - - - Removed 09-2020 since this is no longer recorded. - - dtrainor@chromium.org - chrome-safebrowsing-alerts@google.com - - File types that were blocked from downloaded without verifying their content - nor their source URLs with Safe Browsing. - - - - - - Removed 04/25/2018 since it was not being used actively or monitored. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to copy the SafeBrowsing list update as a string, - into a map which contains the hash prefixes that are looked up when a client - queries for the reputation of a resource (URL, full hash, etc.). - - - - - - Replaced by SafeBrowsing.V4AddUnlumpedHashes.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to copy the SafeBrowsing list update as a string, - into a map which contains the hash prefixes that are looked up when a client - queries for the reputation of a resource (URL, full hash, etc.). - - - - - - Replaced by SafeBrowsing.V4*.ApplyUpdate.Result. - - chrome-safebrowsing-alerts@google.com - - Track the result of applying the update fetched from the PVer4 service for a - particular store. - - - - - - Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Result. - - chrome-safebrowsing-alerts@google.com - - Track the result of applying an update read from disk after parsing it - successfully as a protobuf. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The size of the SafeBrowsing database or file on disk in kilobytes, after - reading it from disk on startup and after a database update has occurred. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes to parse and load the SafeBrowsing database from disk, in - milliseconds. - - - - - - Replaced by SafeBrowsing.V4*.DecodeAdditions.Result. - - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of additions of 4-byte - hash prefixes. This is logged once per store, per update containing - Rice-encoded additions. - - - - - - Replaced by SafeBrowsing.V4*.DecodeAdditions.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded additions to the - blacklist into raw format. - - - - - - Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Result. - - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of indexes of hash - prefixes to remove since the last update. This is logged once per store, per - update containing Rice-encoded removals. - - - - - - Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded removals from the - blacklist into raw format. - - - - - - Replaced by SafeBrowsing.V4GetHash.CacheHit.Result. - - kcarattini@chromium.org - chrome-safebrowsing-alerts@google.com - Track cache hits for V4 full hashes. - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Track cache hits for V4 full hashes. - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - Track get hash response hits for V4 full hash requests. - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of prefixes included in a full hash request sent to the Google - Safe Browsing servers. - - - - - vakh@google.com - kcarattini@google.com - chrome-safebrowsing-alerts@google.com - - Response or error codes from the SafeBrowsing Pver4 service. Logged after a - GetHash or request finishes to capture the response code or error code for - that call. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that it took to receive a response from the Google SafeBrowsing - servers for a full hash request. - - - - - - - vakh@chromium.org - kcarattini@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the parsing results of a status 200 GetV4Hash request. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track return status from V4 GetHash attempts. The buckets of this histogram - overlap, so the counts cannot be used as percentages. - - - - - - Replaced by SafeBrowsing.V4GetHash.Check.Result. - - kcarattini@chromium.org - chrome-safebrowsing-alerts@google.com - Track get hash response hits for V4 full hash requests. - - - - - Replaced by SafeBrowsing.V4GetHash.Network.Time. - - chrome-safebrowsing-alerts@google.com - - The time that it took to receive a response from the Google SafeBrowsing - servers for a full hash request. - - - - - - Removed in favor of the TimeUs variant - - chrome-safebrowsing-alerts@google.com - - The time that it took to check a URL against our in-memory database. It is - dominated by the time to perform checks for CheckBrowseUrl. - - - - - - Removed 01/2019 due to lack of use (Histogram Eraser). - - csharrison@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that it took to check a URL against our in-memory database. It is - dominated by the time to perform checks for CheckBrowseUrl. Note that this - metric is recorded even for users with low resolution clocks. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the outcome of a check to AreAllStoresAvailableNow. This will be - logged whenever the database is queried (several times in the process of a - download, and once when a potentially dangerous subresource is loaded). - - - - - ajuma@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a network response has been received for a request to update - the Safe Browsing local database, since the browser was launched. This will - be logged whenever the database is queried. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of verdicts received in the full hash check. Logged each - time a full hash check response is received. - - - - - ajuma@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time since the last network response was received for a request - to udpate the Safe Browsing local database. This will be logged whenever the - database is queried, but only if at least one such network response has been - received since the browser was launched. - - - - - - Replaced by SafeBrowsing.V4*.MergeUpdate.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to merge the existing state of the list with the - update. The update may have been received from the server, or it may have - just been read from disk. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of additions hashes in a SafeBrowsing list full update. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of applying a full update for a store received from PVer4 - SafeBrowsing service. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to process a SafeBrowsing list full update. It - includes V4AddUnlumpedHashes.Time for each prefix-sized list, and - V4ProcessFullUpdate.MergeUpdate.Time. Additionally, if the update is - Rice-encoded, it includes V4ProcessFullUpdate.DecodeAdditions.Time for each - prefix-sized list that's Rice-encoded. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of additions of 4-byte - hash prefixes. This is logged once per store, per update containing - Rice-encoded additions. This histogram is specific to processing full - updates received from the server. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded additions to the - blacklist into raw format when applying a full update to a store. - - - - - - Removed 04/25/2018 since it was not being used actively or monitored. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to merge the existing state of the list with a - full update received from the server. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of removals hashes in a SafeBrowsing list full update. - - - - - - Replaced by SafeBrowsing.V4ProcessFullUpdate.ApplyUpdate.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to process a SafeBrowsing list full update. It - includes V4AddUnlumpedHashesTime for each prefix-sized list, and - V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes - V4DecodeAdditionsTime for each prefix-sized list that's Rice-encoded. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of additions hashes in a SafeBrowsing list partial - update. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of applying a partial update for a store received from - PVer4 SafeBrowsing service. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to process a SafeBrowsing list partial update. It - includes V4AddUnlumpedHashes.Time for each prefix-sized list, and - SafeBrowsing.V4ProcessPartialUpdate.MergeUpdate.Time. Additionally, if the - update is Rice-encoded, it includes - V4ProcessPartialUpdate.DecodeRemovals.Time, and - V4ProcessPartialUpdate.DecodeAdditions.Time for each prefix-sized list - that's Rice-encoded. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of additions of 4-byte - hash prefixes. This is logged once per store, per update containing - Rice-encoded additions. This histogram is specific to processing partial - updates received from the server. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded additions to the - blacklist into raw format when applying a partial update to a store. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of indexes of hash - prefixes to remove since the last update. This is logged once per store, per - update containing Rice-encoded removals. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded removals from the - blacklist into raw format when applying a partial update to a store. - - - - - - Removed 04/25/2018 since it was not being used actively or monitored. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to merge the existing state of the list with a - partial update received from the server. - - - - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of removals hashes in a SafeBrowsing list partial update. - - - - - - Replaced by SafeBrowsing.V4ProcessPartialUpdate.ApplyUpdate.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to process a SafeBrowsing list partial update. It - includes V4AddUnlumpedHashesTime for each prefix-sized list, and - V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes - V4DecodeRemovalsTime, and V4DecodeAdditionsTime for each prefix-sized list - that's Rice-encoded. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of applying an ListUpdateResponse read from disk after - parsing it successfully as a protobuf. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to read, parse, and process a SafeBrowsing list - stored on disk. This happens at Chromium start-up. It includes - V4AddUnlumpedHashes.Time for each prefix-sized list, and - SafeBrowsing.V4ReadFromDisk.MergeUpdate.Time. Additionally, if the file is - Rice-encoded, it includes V4ReadFromDisk.DecodeAdditions.Time for each - prefix-sized list that's Rice-encoded. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the result of decoding the Rice-encoded list of additions of 4-byte - hash prefixes. This is logged once per store, per Chrome launch. It is - specific to processing V4StoreFileFormat proto read from disk. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes to decode the Rice-encoded additions to the - blacklist into raw format when reading a store file from disk. - - - - - - Removed 04/25/2018 since it was not being used actively or monitored. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to perform in-memory copy of the map of raw hash - prefixes read from disk. - - - - - - Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Time. - - chrome-safebrowsing-alerts@google.com - - Records the time it takes to read, parse, and process a SafeBrowsing list - stored on disk. This happens at Chromium start-up. It includes - V4AddUnlumpedHashesTime for each prefix-sized list, and V4MergeUpdateTime. - Additionally, if the file is Rice-encoded, it includes V4DecodeAdditionsTime - for each prefix-sized list that's Rice-encoded. - - - - - - Removed in M77 since the histogram was very stable: crbug.com/984286. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how often IsStoreAvailable fails due to an invalid store identifier. - This is logged each time a store is checked (a few times for each download, - and once when a potentially dangerous subresource is loaded). - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a store has valid data, when it is queried. This is logged - each time a store is checked (a few times for each download, and once when a - potentially dangerous subresource is loaded). - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the parsing results of reading the SafeBrowsing V4 store file from - disk. Recorded every time a store is read from disk. - - - - - - Replaced by SafeBrowsing.V4StoreRead.Result. - - chrome-safebrowsing-alerts@google.com - - Track the parsing results of reading the SafeBrowsing V4 store file from - disk. Recorded every time a store is read from disk. - - - - - - Removed in M78 since there's only ever been just 1 version number. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Version of V4Store read from a store file. This would be useful in tracking - the usage and rollout of new V4Store versions. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the results of writing the SafeBrowsing V4 store file to disk. - Recorded every time a store is written to disk. - - - - - - Replaced by SafeBrowsing.V4StoreWrite.Result. - - chrome-safebrowsing-alerts@google.com - - Track the results of writing the SafeBrowsing V4 store file to disk. - Recorded every time a store is written to disk. - - - - - - Removed in M86. See https://crbug.com/1089439 - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the presence of store files that were previously created but have been - deprecated since so need to be removed from disk. Logged once per startup. - - - - - - Removed in M73. See https://crbug.com/916192 - - chrome-safebrowsing-alerts@google.com - - Track the presence of Safe Browsing list files used for PVer3, which has - been deprecated. Logged once per startup. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Response or error codes when fetching updates from the SafeBrowsing PVer4 - service. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track the parsing results of a status 200 GetV4Update request. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The size of the response sent by the SafeBrowsing PVer4 service, in KB. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Track return status from V4 update attempts. The buckets of this histogram - overlap, so the counts cannot be used as percentages. - - - - - - Removed in M78 due to lack of use and timed out rate being less than 0.03% - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - True if a PVer4 update request timed out. - - - - - Replaced by SafeBrowsing.V4Update.Network.Result. - - chrome-safebrowsing-alerts@google.com - - Response or error codes when fetching updates from the SafeBrowsing PVer4 - service. - - - - - - Replaced by SafeBrowsing.V4Update.ResponseSizeKB. - - chrome-safebrowsing-alerts@google.com - - The size of the response sent by the SafeBrowsing PVer4 service, in KB. - - - - - - Replaced by SafeBrowsing.V4Update.Result. - - chrome-safebrowsing-alerts@google.com - - Track return status from V4 update attempts. The buckets of this histogram - overlap, so the counts cannot be used as percentages. - - - - - - Removed in June 2020. - - ricea@chromium.org - - Time spent on SafeBrowsing lookup. Since this includes any time spent on the - interstitial page the average may not be useful. - - - - - - Removed in June 2019. - - ricea@chromium.org - - Results of a SafeBrowsing lookup for a WebSocket handshake. All lookups are - counted. Note: the "ABANDONED" bucket contains both connections - that were abandoned before the check completed and those that were cancelled - when the user navigated away from the SafeBrowsing interstitial. - - - - - ntfschr@chromium.org - src/android_webview/OWNERS - - Records whether the application has explicitly opted in or out of Safe - Browsing by manifest tag, or if they're relying on the default behavior. - This is recorded once during startup. - - - - - - Removed in December 2019 because logic was simplified to remove this race. - - ntfschr@chromium.org - - WebView can simultaneously check for user opt-in and Safe-Browsing-check the - first URL, with both asynchronous checks racing to finish. This records the - outcome of that race: (1) which asynchronous method finished first; (2) if - user consent finished first, what was the outcome; and (3) did we show - malicious content to the user. This is recorded only once, for the first - Safe Browsing check. - - - - - ntfschr@chromium.org - src/android_webview/OWNERS - - Records whether the user has explicitly opted in or out of Safe Browsing - (determined by the Google Play Protect Verify Apps setting in GMS). This - also captures when WebView cannot determine user preference due to a GMS API - failure. This is recorded once during startup. - - - - - ntfschr@chromium.org - src/android_webview/OWNERS - - When encountering an unsafe resource, this indicates whether the WebView is - considered to be viewable or not. Currently, we define "viewable" - as getVisibility() == View.VISIBLE and attached to the Android View - hierarchy. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records the verdict of deep scanning for Advanced Protection users. It - can be used to determine how often we warn the user about malware after they - upload a file for deep scanning. It is recorded after every Advanced - Protection deep scan. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records whether DLP scanning succeeded or not. It is logged once for - each binary upload with DLP scanning enabled (file download or upload with - the appropriate enterprise policies enabled). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records the duration of each binary upload request. It is logged once - for each binary upload (file download or upload with the appropriate - enterprise policies enabled). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records whether the malware deep scanning succeeded or not. It is - logged once for each binary upload with malware scanning enabled (file - download or upload with the appropriate enterprise policies enabled). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records the verdict of deep scanning for enterprise users. It can be - used to determine how often we warn the user about malware after they upload - a file for deep scanning. It is recorded after every enterprise malware deep - scan. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records the outcome of each binary upload request. It is logged once - for each binary upload (file download or upload with the appropriate - enterprise policies enabled). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This record how long it took for the request to get the FCM token. It is - logged every time a deep scanning request successfully gets a token. - - - - - - Removed 06/2020 as SafeBrowsingBinaryUploadRequest.TimeToGetFCMToken - provides the same information with a better range of durations. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This record how long it took for the request to get the FCM token. It is - logged every time a deep scanning request successfully gets a token. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the incoming message has the expected key. Recorded on every FCM - message received by the Safe Browsing FCM handler. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the incoming message has a token that was previously registered with - the FCM handler. Recorded on every FCM message received by the Safe Browsing - FCM handler. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the incoming message was successfully parsed as valid base64-encoded - data. Recorded on every FCM message received by the Safe Browsing FCM - handler. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the incoming message was successfully parsed as a valid - base64-encoded serialized proto. Recorded on every FCM message received by - the Safe Browsing FCM handler. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The first stage check that measures the time that Chrome took to check if a - URL is present in our in-memory bloom filter. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - TBD. - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The second stage check that measures the time that Chrome took to check if a - URL is present in our SQLite database. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The second stage check that mesures the time that Chrome took to check if a - URL is present in our SQLite database. This time includes the filter check - time. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - This measures the time that SafeBrowsing actually delayed the browsing - experience. It records the difference between the time when Chrome would - have started reading the response for a URL and when the SafeBrowsing system - completed its check of that URL. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The first stage check that measures the time that Chrome took to check if a - URL is present in our in-memory hash table. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The third and final stage check that mesures the time that Chrome took to - get a response from the Google SafeBrowsing servers for a particular URL. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - The third and final stage check that mesures the time that Chrome took to - get a response from the Google SafeBrowsing servers for a particular URL. - This time includes the filter and database check time. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - - This measures the time that SafeBrowsing actually delayed the browsing - experience. It records the difference between the time when Chrome would - have started reading the response for a URL and when the SafeBrowsing system - completed its check of that URL. - - - - - - Has not been generated for years (7/8/14). - - Please list the metric's owners. Add more owner tags as needed. - TBD. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The number of add prefixes stored in the database after the last update. - - - - - - Bloom filter support deleted in October 2012. - - Please list the metric's owners. Add more owner tags as needed. - - Track failures when in processing the safe-browsing database bloom filter. - - - - - - This became misleading around M-22 (September 2012), deleted in M-32 - (November 2013). - - Please list the metric's owners. Add more owner tags as needed. - - All prefix misses (server returned no full hashes) and prefix misses due to - false positives in the bloom filter. - - - - - - Bloom filter support deleted in October 2012. - - Please list the metric's owners. Add more owner tags as needed. - Time to load the BloomFilter file. - - - - - Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.Browse. - - chrome-safebrowsing-alerts@google.com - - The size of the browsing SafeBrowsing database file on disk in kilobytes, - after an update has occurred. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The time that it took to regenerate the filter after we have received all - the update chunks. - - - - - - Removed because it was exceeding the range. Replaced by - SB2.BuildReadKilobytes. - - Please list the metric's owners. Add more owner tags as needed. - - The number of bytes read by the browser process during the bloom filter - generation phase. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The number of kilobytes read by the browser process during the filter - generation phase. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The number of read operations issued by the browser process during the - filter generation phase. - - - - - - Removed because it was exceeding the range. Replaced by - SB2.BuildWriteKilobytes. - - Please list the metric's owners. Add more owner tags as needed. - - The number of bytes written by the browser process during the bloom filter - generation phase. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The number of kilobytes written by the browser process during the filter - generation phase. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The number of write operations issued by the browser process during the - filter generation phase. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The time that it takes to write one redirect URL (which can contain multiple - chunks) to the database. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The network time between the request and response for a chunk. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - The size of one chunk URL. - - - - - Removed because it was exceeding the range. Replaced by - SB2.DatabaseKilobytes. - - Please list the metric's owners. Add more owner tags as needed. - The size of the SafeBrowsing database file on disk. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - Track failures when updating the safe-browsing database. - - - - - Replaced by SB2.BrowseDatabaseKilobytes. - - chrome-safebrowsing-alerts@google.com - - The size of the SafeBrowsing database file on disk in kilobytes. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The time it takes to initialize the SafeBrowsing storage backend, in - milliseconds. - - - - - - Removed after the launch of PVer4 in M57. - - gab@chromium.org - - The size of one of the SafeBrowsing database file on disk in kilobytes, - after a database update has occurred (once a few minutes after startup, and - every thirty minutes or so thereafter). - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The size of the update file before merging with the database file, in - kilobytes. - - - - - - Removed in M65. Replaced by SB2.NoUserActionResourceLoadingDelay - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that SafeBrowsing actually delayed the browsing experience. It - records the difference between the time when Chrome would have started - reading the response for a URL and when the SafeBrowsing system completed - its check of that URL. This is the sum of .Mainframe and .Subresource - breakout metrics. - - - - - - Removed in M65. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that SafeBrowsing actually delayed the browsing experience. It - records the difference between the time when Chrome would have started - reading the response for a URL and when the SafeBrowsing system completed - its check of that URL. Logged for main frame resources only. - - - - - - Removed in M65. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that SafeBrowsing actually delayed the browsing experience. It - records the difference between the time when Chrome would have started - reading the response for a URL and when the SafeBrowsing system completed - its check of that URL. Logged for non-main frame resources only. - - - - - - Deleted in M-34 (February 2014). - - Please list the metric's owners. Add more owner tags as needed. - Obsolete download BINHASH add chunks deleted. - - - - - Deleted in M-34 (February 2014). - - Please list the metric's owners. Add more owner tags as needed. - Obsolete download BINHASH sub chunks deleted. - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records results of SafeBrowsing download check, including both url check and - downloaded file hash check. - - - - - - Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.Download. - - chrome-safebrowsing-alerts@google.com - - The size of the downloads SafeBrowsing database file on disk in kilobytes, - after an update has occurred. - - - - - - Removed 01/2017. Was measuring the lifetime of a network request - corresponding to a download, which may or may not correspond to the total - duration of a download. - - chrome-safebrowsing-alerts@google.com - The time it takes for a download to finish. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - The time it takes for SafeBrowsing to check hash of a download file. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - The time it takes for SafeBrowsing to check a download url. - - - - - Removed 3/11/11, and replaced by SB2.DownloadChecks. - - Please list the metric's owners. Add more owner tags as needed. - Records results of SafeBrowsing download url check. - - - - - Removed 03/2015. Replaced by - SecurityInterstitialInteraction::EXTENDED_REPORTING_IS_ENABLED. - - felt@chromium.org - - Whether the user has Safe Browsing extended reporting enabled at the time a - Safe Browsing warning was dismissed. This tracks the fraction of all SB - interstitials that had reporting enabled. - - - - - - Removed, replaced by SB2.DatabaseFailure BROWSE_DB_UPDATE_FINISH. - - Please list the metric's owners. Add more owner tags as needed. - - The count of the number of times an update failed when being committed to - the database. - - - - - - Removed in favor of SafeBrowsing.V4GetPrefixMatches.TimeUs - - chrome-safebrowsing-alerts@google.com - - The time that it took to check a URL against our in-memory filter. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - The size of the current bloom filter in kilobytes. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - Which filter file the database loaded from disk. - - - - - Removed, replaced by SB2.DatabaseFailure FILTER_MISSING. - - Please list the metric's owners. Add more owner tags as needed. - - The count of the number of times we attempted to load the bloom filter file - but it was missing. - - - - - - Removed, replaced by SB2.DatabaseFailure FILTER_READ. - - Please list the metric's owners. Add more owner tags as needed. - - The count of the number of times we attempted to load the bloom filter file - but failed while reading the file on disk. - - - - - - Removed because it was exceeding the range. Replaced by SB2.FilterKilobytes. - - Please list the metric's owners. Add more owner tags as needed. - The size of the current bloom filter. - - - - - Removed, replaced by SB2.DatabaseFailure FILTER_WRITE. - - Please list the metric's owners. Add more owner tags as needed. - - The count of the number of times we attempted to save the bloom filter file - but failed while writing the file to disk. - - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - Collection of boolean events for SafeBrowsingFileStore instances. Includes - corruptions detected, old versions detected, and various failures detected. - - - - - - Removed after the launch of PVer4 in M57. - - vakh@google.com - - Response or error codes from the SafeBrowsing service. Logged after a - GetChunk request finishes to capture the response code or error code for - that call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49. - - - - - - Removed in favor of SB2.GetHashResult STATUS_200. - - Please list the metric's owners. Add more owner tags as needed. - - The number of GetHash requests that returned data (valid requests). - - - - - - Removed in favor of SB2.GetHashResult STATUS_204. - - Please list the metric's owners. Add more owner tags as needed. - - The number of GetHash requests that returned empty data (false positives). - - - - - vakh@google.com - - Response or error codes from the SafeBrowsing service. Logged after a - GetHash request finishes to capture the response code or error code for that - call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49. - - - - - - Removed after the launch of PVer4 in M57. - - mattm@chromium.org - - Track return status from GetHash attempts (STATUS_200, STATUS_204, - NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result - failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT, - MISS). EMPTY means the response had no full hashes, and should contain all - of the 204 responses plus all *_ERROR cases. HIT means that one of the full - hashes matched. MISS means that none of the hashes matched (there was a - prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and - BACKOFF_ERROR were added in M36.) - - - - - - Removed after the launch of PVer4 in M57. - - mattm@chromium.org - - Track return status from GetHash attempts (STATUS_200, STATUS_204, - NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result - failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT, - MISS). EMPTY means the response had no full hashes, and should contain all - of the 204 responses plus all *_ERROR cases. HIT means that one of the full - hashes matched. MISS means that none of the hashes matched (there was a - prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and - BACKOFF_ERROR were added in M36.) - - - - - - Removed in favor of SB2.GetHashResult FULL_HASH_* and - SB2.BloomFilterFalsePositives. It is unclear if this histogram ever reported - useful data. - - Please list the metric's owners. Add more owner tags as needed. - - The number of GetHash requests returning full hashes that didn't match the - URL that initiated the request. - - - - - - Removed, replaced by SB2.DatabaseFailure CORRUPT. - - Please list the metric's owners. Add more owner tags as needed. - - The count of the number of times a database was found corrupt and reset. - - - - - - Removed, replaced by: interstitial.malware.* and interstitial.phishing.*. - - felt@chromium.org - - Track number of times Safe Browsing interstitials have been shown, and how - many times they have been clicked through or not. - - - - - - Removed, replaced by: interstitial.malware.* and interstitial.phishing.*. - - felt@chromium.org - - Tracks the click-through rate for specific cases of the interstitial. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user navigating away by for example, closing the tab, clicking the browser - back button or typing another URL in the address bar. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user clicking on diagnostic page link. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user expanding the "see more info" section of the page. (Only - applies to field trial version 2 of the interstitial.) - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user clicking on the learn more about malware link. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user clicking on the privacy policy link. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user clicking on the proceed link. - - - - - - Removed 9/2014. - - felt@chromium.org - - The time between when we show the SafeBrowsing malware interstitial and the - user clicking on the big green back button. - - - - - - Removed in M65. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that it took to receive a response from the Google SafeBrowsing - servers for a GetHash request. - - - - - - Removed in M77 since it is fairly flat and not really useful. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The total delay, in milliseconds, caused by SafeBrowsing for a resource - load, if the SafeBrowsing interstitial page is not shown and therefore no - user action is involved. At most one value is reported for each resource - load. If SafeBrowsing causes delays at different stages of a load, the sum - of all the delays will be reported. - - - - - - Removed 7/2014. No longer generated. - - chrome-safebrowsing-alerts@google.com - Size of v1 database deleted from client profile. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - - Indicates how sharded safe-browsing on-disk stores are. Values like 0 to 4 - are reasonable. - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user navigating away by for example, closing the tab, clicking the browser - back button or typing another URL in the address bar. - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user expanding the "see more info" section of the page. (Only - applies to field trial version 2 of the interstitial.) - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user clicking on the learn more link. - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user clicking on the proceed link. - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user clicking on the report error link. - - - - - felt@chromium.org - - The time between when we show the SafeBrowsing phishing interstitial and the - user clicking on the big green back button. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - - The size of the PrefixSet storage in bits, divided by the number of prefixes - represented. Should almost always be 16. - - - - - - Removed 9/2012. No longer generated, BloomFilter being removed. - - Please list the metric's owners. Add more owner tags as needed. - - Records how well the PrefixSet implementation matches the BloomFilter - implementation. - - - - - - Removed 01/2014. Replaced by suffixed SB2.PrefixSetSizeKilobytes. - - chrome-safebrowsing-alerts@google.com - The size of one of the PrefixSet files in kilobytes. - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - Time to load one of the PrefixSet files. - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. How many extra results GetPrefixes returns. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. How many fewer results GetPrefixes returns. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - - The size of one of the PrefixSet files in kilobytes. Logged after a database - update has occurred and the PrefixSet has been flushed to disk (once a few - minutes after startup, and every thirty minutes or so thereafter). - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. How far unsorted deltas are from expected value. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. Distance of unsorted elements from expected - location. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. How far into the results unsorted elements were - found. Interesting values would be 0%, 50%, or 100%. - - - - - - Removed 9/2012. No longer generated. - - Please list the metric's owners. Add more owner tags as needed. - - For debugging PrefixSet. Size of unsorted sets. To see if there is a problem - with a particular size of dataset. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - Version read from one of the PrefixSet files. - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - Time to store one of the PrefixSet files. - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Count of how many URLs were actually checked vs skipped via - RemoteSafeBrowsingDatabaseManager because the scheme is not supported by - Safe Browsing. Incremented each time a resource load is initiated. - - - - - - Removed in M84. This feature is not launched. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates whether the local Safe Browsing blacklists can be used on this - Android device. Logged once on first URL check request. - - - - - vakh@chromium.org - csharrison@chromium.org - chrome-safebrowsing-alerts@google.com - - The microseconds between sending the Safe Browsing API call and receiving - the response. Logged in java code and does not include any thread hops or - extra work. Note that this does include task queue time to respond to the - IPC (and that queue time is often non-trivial). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed Oct 2018 - - csharrison@chromium.org - chrome-safebrowsing-alerts@google.com - - Wall time in microseconds for calling - Java_SafeBrowsingApiBridge_startUriLookup. Logged at every Safe Browsing - check on Android. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M64 (Nov 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - - Number of outstanding calls for URLs getting classified through - RemoteSafeBrowsingDatabaseManager. The size of the queue is logged before - initiating each request. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Latency of URL-classification API calls from Chrome via - RemoteSafeBrowsingDatabaseManager, logged per-request. This includes the - time to go through JNI, check the URL, and return the result and includes - several thread hops betwetween IO and UI threads. The resource-load will not - necessarily be delayed this much (see SB2.Delay for that). - - - - - - No longer generated. Replaced by SB2.RemoteCall.InternalErrorStatusCode2 - - chrome-safebrowsing-alerts@google.com - - The status code provided by GmsCore if it is unable to respond to a URL - check request due to incorrect initialization, not being ready, etc. Logged - on each URL check that hits the internal error condition. The total number - of these should add up to the INTERNAL_ERROR reports under - SB2.RemoteCall.Result. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The status code provided by GmsCore if it is unable to respond to a URL - check request due to incorrect initialization, not being ready, etc. Logged - on each URL check that hits the internal error condition. The total number - of these should add up to the INTERNAL_ERROR reports under - SB2.RemoteCall.Result. - - - - - - Removed M81. The latency looks good, not needed anymore. - - xinghuilu@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates the time for synchronous local allowlist lookup on Java side. This - metrics provides the evidence of whether asynchronous implementation is - needed for local allowlist. - - - - - - Removed in M84. This feature is not launched. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates the time since the local blacklists were successfully updated - last. Logged each time the verdict of local blacklists lookup is stale or - possibly unsafe, if the local blacklists feature is enabled (i.e. - SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) - - - - - - Removed in M84. This feature is not launched. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates the result of local Safe Browsing blacklist lookup on Android. - Logged for each URL lookup, if the local blacklists feature is enabled (i.e. - SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) - - - - - - Removed in M84. This feature is not launched. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates the result of local blacklists' update. Logged each time an update - of local blacklists is attempted, if the local blacklists feature is enabled - (i.e. SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Result of URL-classification API calls from Chrome via - RemoteSafeBrowsingApiHandler. Logged after each URL is judged safe/not-safe, - or hits a deadline. The INTERNAL_ERROR cases are further classified under - SB2.RemoteCall.InternalErrorStatusCode. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The threat sub-type annotated for URLs classified as PHA via remote calls - through RemoteSafeBrowsingApiHandler. "PHA" classifications - generate "malware" interstitials. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The threat sub-type annotated returned for URLs classified as social - engineering via remote calls through RemoteSafeBrowsingApiHandler. - "Social engineering" classifications generate "phishing" - interstitials. - - - - - - Removed 06/2014. Replaced by SB2.ExtendedReportingIsEnabled. - - Please list the metric's owners. Add more owner tags as needed. - - Whether the user has Safe Browsing extended reporting enabled at the time a - Safe Browsing warning was dismissed. This tracks the fraction of all SB - interstitials that had reporting enabled. - - - - - - Superseded by SB2.ResourceTypes2 in December 2015. - - chrome-safebrowsing-alerts@google.com - - Resource types of resources that were inspected by Safe Browsing in the - SafeBrowsingResourceThrottle. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Resource types of resources that were inspected by Safe Browsing in the - SafeBrowsingResourceThrottle. - - - - - - Removed 03/2015. Replaced by - SecurityInterstitialInteraction::SET_EXTENDED_REPORTING_ENABLED. - - felt@chromium.org - - Tracks changes to the Safe Browsing extended reporting opt-in which is shown - in the Safe Browsing interstitial. - - - - - - Removed 06/2014. Replaced by SB2.SetExtendedReportingEnabled. - - Please list the metric's owners. Add more owner tags as needed. - - Tracks changes to the Safe Browsing extended reporting opt-in which is shown - in the Safe Browsing interstitial. - - - - - - Removed 12/2014. Merged into SB2.PrefixSetWrite. - - chrome-safebrowsing-alerts@google.com - - Time to store the Side Effect Free Whitelist PrefixSet file. Note: this - histogram was intended to be stored as - SB2.SideEffectFreeWhitelistPrefixSetWrite but was actually reported as - SB2.SideEffectFreePrefixSetWrite from its inception to its deprecation... - - - - - - Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.SideEffectFreeWhitelist. - - chrome-safebrowsing-alerts@google.com - - The size of the Side Effect Free Whitelist SaafeBrowsing database file on - disk in kilobytes, after an update has occurred. - - - - - - Removed 12/2014. Moved to - SB2.PrefixSetSizeKilobytes.SideEffectFreeWhitelist. - - chrome-safebrowsing-alerts@google.com - - The size of the Side Effect Free Whitelist PrefixSet file in kilobytes, - after an udpate has occurred. - - - - - - Removed 12/2014. Merged into SB2.PrefixSetLoad. - - chrome-safebrowsing-alerts@google.com - Time to load the Side Effect Free Whitelist PrefixSet file. - - - - - Removed 4/2015. - - chrome-safebrowsing-alerts@google.com - The instantiation status of the SideEffectFreeWhitelist. - - - - - Removed after the launch of PVer4 in M57. - - chrome-safebrowsing-alerts@google.com - Version read from the store file. - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - - The number of sub prefixes stored in the database after the last update. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - - The time from the receipt of the update request to the receipt of the final - update chunk. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - The payload size of update requests to the server. - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - Result from trying to update the SafeBrowsing data. - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - The size of all the chunk URLs in an update response. - - - - - Was used for an experiment in late 2014. - - chrome-safebrowsing-alerts@google.com - - The size of all the chunk URLs in an update response when Chrome is in the - background. - - - - - - Was used for an experiment in late 2014. - - chrome-safebrowsing-alerts@google.com - - The size of all the chunk URLs in an update response when Chrome is in the - foreground. - - - - - - Removed in M58 (Aug 2017). No longer generated. - - chrome-safebrowsing-alerts@google.com - The number of chunk URLs in an update response. - - - - - The operation this is tracking has been deleted as of 09/2014. - - chrome-safebrowsing-alerts@google.com - - Older versions of the safe-browsing code incorrectly added additional - SBPrefix items when receiving full hashes. This caused errors when - calculating when to send gethash requests to the server. An additional pass - over the data has been added to remove the excess prefixes. This histogram - tracks progress of that code for purposes of informing a decision on when to - remove the additional pass. See http://crbug.com/361248 . - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - chrome-safebrowsing-alerts@google.com - dtrainor@chromium.org - - Records a histogram of archive file types that were found while examining a - downloaded ZIP file. Each archive file type in a single ZIP file is recorded - at most once. The relative incidence rate of each filetype in this histogram - should indicate the probability of finding that file type in a ZIP file - given that that ZIP file contains an archive file. - - - - - - This histogram was marked obsolete in 08/2020 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records a histogram of how often users download a file with a possibly - dangerous file extension (e.g., exe, class) within an archive. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records a histogram of the reason why downloads are marked as being - malicious or clean by the improved SafeBrowsing binary download protection. - Note that UNSUPPORTED_URL_SCHEME was split out of the INVALID_URL bucket in - M41. The NOT_BINARY_FILE check was moved before the UNSUPPORTED_URL_SCHEME - check in M42. The WHITELISTED_URL check was moved to before NOT_BINARY_FILE - in M62. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - For each download supported by the SafeBrowsing download protection service, - records if it matches a certain whitelist (e.g. matches URL whitelist, - matches signature whitelist, or does not match any whitelists). - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The original number of archived_binaries found in a DMG-like file when it's - scanned, if at least one is found. The actual number sent in the download - request may be capped below this value. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of DMG-like file types that failed to be successfully analyzed by the - SafeBrowsing download service. - - - - - - Replaced by SBClientDownload.DmgFileHas[No]ExecutableByType in M51. - - rsesek@chromium.org - - For each DMG file analyzed by the SafeBrowsing download service, records if - the DMG contained an executable file. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of DMG-like file types which were analyzed by the SafeBrowsing - download service that contained an executable file. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of DMG-like file types which were analyzed by the SafeBrowsing - download service that did NOT contain an executable file. - - - - - - Replaced by SBClientDownload.DmgFile{Success,Failure}ByType in M51. - - rsesek@chromium.org - - For each DMG file analyzed by the SafeBrowsing download service, records - true if the analysis was successful, or false if there was an error - analyzing the file. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of DMG-like file types that were successfully analyzed by the - SafeBrowsing download service. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a given DMG download was too big to unpack, as specified by - configuration option set in SafeBrowsing download service. This metric is - logged each time the user downloads a DMG file on Mac. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records a histogram of how often users download a file with a file extension - that is possibly dangerous (e.g., exe, class). - - - - - - Removed 09/19, since the metric was not being actively used and there were - no near-term plans to begin using it. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - A Mac-only metric that records whether a given download contains a detached - code signature file. This metric is logged before Chrome sends SafeBrowsing - download pings. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - A Mac-only metric that records whether a given download file is a - cryptographically signed DMG archive. This metric is logged before Chrome - sends SafeBrowsing download pings. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether download files without an Apple disk image file extension - have a 'koly' signature. This can be used to identify distribution of disk - image files to Mac users without simply relying on file extension. This - metric is logged before Chrome sends SafeBrowsing download pings. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the total time it takes for the SafeBrowsing download service to - check whether the content of a download is malicious or not, including file - feature extraction, whitelist checking, and server ping. This histogram only - includes checks that sent a ping to the SafeBrowsing server. It does not - include requests that were cancelled, but does include requests that - received a bad response. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - The net error code for all CheckClientDownloadRequest URLFetchers. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the time it takes for the SafeBrowsing download service ping. It is - not recorded for requests that were cancelled. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the results of SafeBrowsing binary download checks which caused a - server ping. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - The size of the upload data for CheckClientDownloadRequest URLFetchers. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - For CheckClientDownloadRequest URLFetchers with successful status, the HTTP - response code that was received. - - - - - - Removed in M78, since the metrics were not being actively used and there was - no near-term plan to begin using them. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the portion of the SafeBrowsing download service check starting with - the point CheckClientDownloadRequest::StartTimeout() is called. It is - recorded regardless if a ping was sent or not. It is not recorded for - requests that were cancelled. - - - - - - Removed in M78, since the metrics were not being actively used and there was - no near-term plan to begin using them. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - For SafeBrowsing binary download checks which reached the - CheckClientDownloadRequest::StartTimeout() call, records the final result - (once the check finishes or is cancelled). - - - - - - Removed in M76, replaced by SBClientDownload.ExtractDmgFeaturesTimeMedium. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - rsesek@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded DMG file. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - rsesek@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded DMG file. - - - - - - Removed in M77. Extracting image headers was usually fast (84% were less - than 1ms), so this histogram was not providing useful data. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - grt@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - image headers from a downloaded binary. - - - - - - Removed in M76, replaced by SBClientDownload.ExtractRarFeaturesTimeMedium. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded rar file. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded rar file. - - - - - - Removed in M78, since the metrics were not being actively used and there was - no near-term plan to begin using them. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - signature info from a downloaded binary. This includes both unsigned and - signed binaries. - - - - - - Removed in M76, replaced by SBClientDownload.ExtractZipFeaturesTimeMedium. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded zip file. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the time it takes for the SafeBrowsing download service to extract - info from a downloaded zip file. - - - - - - Removed in 08/2018. - - dtrainor@chromium.org - Time taken to complete a PPAPIDownloadRequest. - - - - - Removed in 08/2018. - - dtrainor@chromium.org - - Outcome of running CheckPPAPIDownloadRequest. Most failure modes cause an - UNKNOWN result to be returned to the caller. If the attempt succeeds, the - result returned to the caller is based on the SafeBrowsing resopnse. The - final result returned is counted in - SBClientDownload.PPAPIDownloadRequest.Result. - - - - - - Removed in 08/2018. - - dtrainor@chromium.org - Result returned to the caller of CheckPPAPIDownloadRequest. - - - - - Removed 09-2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The original number of archived_binaries found in a rar-like file when it's - scanned, if at least one is found. The actual number sent in the download - request may be capped below this value. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each rar file analyzed by the SafeBrowsing download service, records - true if the rar did not contain any executables but did contain another - archive file, false otherwise. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each rar file analyzed by the SafeBrowsing download service, records if - the rar contained an executable file. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each rar file analyzed by the SafeBrowsing download service, records if - the unpacking was 100% successful. - - - - - - Marked obsolete 07-2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether the RAR headers are encrypted, preventing any meaningful - content analysis. This is in contrast to encryption of the content of the - archive, which still exposes file name information. This histogram is - recorded every time a RAR archive is downloaded. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each rar file analyzed by the SafeBrowsing download service, records if - the file could be opened. This should be close to 100% success because the - library doesn't actually open the file; it is handed an open file handle and - the Open() function call sets that as the file handle to use. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each rar file analyzed by the SafeBrowsing download service, records if - the unrar library considers this file a valid RAR archive. It includes - checking the following, and more: magic number is present, valid RAR version - format can be parsed, headers are valid, etc. - - - - - - Removed in M78, since the metrics were not being actively used and there was - no near-term plan to begin using them. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Records the number of signed vs. unsigned executables that are downloaded. - - - - - - Removed in Chrome 50. Replaced by SBClientDownload.CheckWhitelistResult.*. - - mattm@chromium.org - - Counter which is incremented whenever an executable is downloaded which is - either signed or whose URL matches the download whitelist. - - - - - - Removed M76, since there had been no such downloads for over a year. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how often different file extensions are downloaded with schemes that - aren't supported by Safe Browsing (e.g. ftp, gopher, content, cid, etc). - - - - - - Removed in M79 due to lack of use, and no future plans for use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether the total uncompressed size of a ZIP overflowed our total. - This is logged once per ZIP file scanned. - - - - - - Removed in M79 due to lack of use, and no future plans for use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the compression ratio for each scanned ZIP archive. This is logged - once per ZIP file scanned, unless - SBClientDownload.ZipArchiveUncompressedSizeOverflow is true. - - - - - - Removed in M79 due to lack of use, and no future plans for use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the uncompressed size of each entry in a scanned ZIP file. This - histogram is logged once per entry in the ZIP. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The original number of archived_binaries found in a zip-like file when it's - scanned, if at least one is found. The actual number sent in the download - request may be capped below this value. - - - - - - Removed in 12/2018 during a refactoring. The data was not being actively - used. - - chrome-safebrowsing-alerts@google.com - - A Mac-only metric that records whether a downloaded zip file contains an - .app directory, signifying the presence of installable software. - - - - - - Removed 09/19, since the metric was not being actively used and there were - no near-term plans to begin using it. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of ZIP-like file types that failed to be successfully analyzed by the - SafeBrowsing download service. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - For each zip file analyzed by the SafeBrowsing download service, records - true if the zip did not contain any executables but did contain another zip - file, false otherwise. - - - - - - This histogram was marked obsolete in 05/2020 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - For each zip file analyzed by the SafeBrowsing download service, records if - the zip contained an executable file. - - - - - - Removed 04/19. This approach to measuring platform-dependent extraction does - not work, so the data was not useful. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of Local File Headers (identified by their magic number) present - in the file, that were not extracted during ZIP inspection. A non-zero entry - implies some potential files were not extracted. That could be intended, or - it could indicate ZIPs with platform-dependent extraction. This metric is - sampled with small probability during each ZIP download. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - For each zip file analyzed by the SafeBrowsing download service, records if - the unpacking was 100% successful. - - - - - - Removed 09/19, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts of ZIP-like file types were successfully analyzed by the SafeBrowsing - download service. - - - - - - Removed in M77, since the metric was not being actively used and there were - no near-term plans to begin using it. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether a given ZIP download was too big to unpack, as specified by - configuration option set in SafeBrowsing download service. This metric is - logged each time the user downloads a ZIP file. - - - - - - Removed in 07-2020 since the SBClientMalware feature was removed. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of pages that we could have possibly classified (essentially the - number of top page navigations by users with SBClientMalware enabled). The - name is slightly misleading as it is recorded before - "Preclassification" happens. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The net error code for all ClientMalwareRequest URLFetchers. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The size of the upload data for ClientMalwareRequest URLFetchers. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For ClientMalwareRequest URLFetchers with successful status, the HTTP - response code that was received. - - - - - - Removed in 07-2020 since the SBClientMalware feature was removed. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of malware classifications that were skipped because a - pre-classification check failed. - - - - - - Removed in 07-2020 since the SBClientMalware feature was removed. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - True if at least one resource url matched the malware IP list. Recorded when - client side malware feature extraction is done. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Measures the success rate of sending malware reports. Sending a report can - fail due to a client reaching the limit on the number of reports it can send - per day or due to the report failing to be serialized. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - The counts for malware verdicts given by server side model. - - - - - Removed 03/2014. That part of the code got deleted. - - noelutz@chromium.org - - Counts the number of times the page ID that completed the page load does not - match the browse info page ID. We expect that number to be zero. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The counts for various reasons why an in-progress phishing classification - was canceled. - - - - - - Removed in M47. - - noelutz@chromium.org - - The number of times client-side phishing classifier expected to have no - pending classifications running but that check failed. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of pages that we could have possibly classified (essentially the - number of top page navigations by users with SBClientPhishing enabled). The - name is slightly misleading as it is recorded before - "Preclassification" happens. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Records events in the phishing classifier including reasons that prevents - phishing detection to complete on the renderer side. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the result of the last model fetch. This is only recorded when - classification fails because the model is not ready. This is useful for - distinguishing different reasons the model may not be ready (never fetched, - fetch failed, etc.) - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The counts for phishing verdicts given by client side model. - - - - - vakh@google.com - - Response or error codes from the SafeBrowsing service. Logged after a - request for the client side model finishes to capture the response code or - the error code for that HTTP request. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The counts for various model status codes that we get after loading a new - client-side phishing model. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the version of the local phishing detection model fetched. This - histogram is logged each time we load a model. - - - - - gab@chromium.org - - The time that an individual chunk of DOM feature extraction work took. - - - - - gab@chromium.org - - The number of times that DOM feature extraction finished early because the - active WebDocument's frame was removed during traversal. - - - - - gab@chromium.org - - The number of iterations that the DOM feature extractor took to finish. - - - - - gab@chromium.org - - The time that it took to resume DOM feature extraction for the phishing - classifier. Longer times may indicate that the page DOM changed between - chunks of work and the extractor had to re-traverse up to the saved - position. - - - - - gab@chromium.org - - The number of phishing classifications that were aborted because DOM feature - extraction took too long. - - - - - gab@chromium.org - - The time that the DOM feature extarctor took to finish, summed across all - chunks of work. - - - - - - Removed in M47 - - noelutz@chromium.org - Time spent generating the thumbnail. - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of features which were omitted from phishing classification - because they were added with an illegal value. This would indicate a bug. - - - - - - Removed in Chrome 37, which now uses //net's internal matching. - - mattm@chromium.org - - The number of times that the phishing detection service could not be - initialized due to an error parsing the private IP networks. This would - indicate a bug. - - - - - - Removed 12/2011. Whitelist entries are no longer part of - ClientPhishingResponse. - - Please list the metric's owners. Add more owner tags as needed. - - The number of whitelist_expression entries in a ClientPhishingResponse that - could not be canonicalized. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether the local phishing detection model detects phishing. This - histogram is logged each time the model is run (roughly on every navigation - to a non-allowlisted site) - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - This records whether a page capture event matches the last URL requested - from the browser process. This histogram is recorded on every page capture - event. - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the duration it takes for client side phishing detection to finish. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - The result enum received from the renderer-side classifier - - - - - This was replaced by SBClientPhishing.PreClassificationCheckResult in - 08-2020, since that histogram is easier to reason about. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the number of phishing classifications that were skipped because a - pre-classification check failed. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the result of phishing pre-classification checks. This is recorded - on every classification attempt (roughly every page load). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of phishing classifications that were previously cached as being - phishing but that will get re-classified (to possibly fix false positives). - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of phishing classifier pingbacks that were skipped because - serializing the request protocol buffer to string failed. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of times that a cached phishing classification result was used, - rather than pinging the server. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Records the status when we create a scorer object for the client-side - phishing detection classifier. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The counts for phishing verdicts given by server side model. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records whether the server-side phishing detection model detects phishing. - This histogram is logged each time we contact Safe Browsing to evaluate - whether a site is phishing. - - - - - - Removed in M77 due to lack of use. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The counts for various reasons why a phishing classification is skipped. - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of phishing classifications that were aborted because the term - feature extractor failed to initialize an ICU break iterator. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that an individual chunk of term feature extraction work took. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of iterations that the term feature extractor took to finish. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of phishing classification that were aborted because term feature - extraction took too long. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time that the term feature extarctor took to finish, summed across all - chunks of work. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of times that the limit on the number of phishing classifier - features for a page was reached. This may indicate a bug, or that - kMaxFeatureSize is too small. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time taken to extract URL features for the phishing classifier. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how long it took to compare visual features against the visual - phishing model. This is recorded on every phishing classification. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Records how long it took to extract visual features. This is recorded on - every phishing classification. - - - - - - Removed in M77, since the information was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Count of times download feedback has been started, broken down by danger - type. - - - - - - Marked obsolete 07-2020 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - When a new download feedback request is added, records the number of - download requests currently active and/or pending. - - - - - - Removed in M85, since the histogram is not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Count of times eligible download notifications are shown. Broken down by - danger type. - - - - - - Removed in M77, since the information was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - Count of times download feedback cannot be sent due to empty file path. - - - - - - Removed in M86, since the information was not being used. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The net error or response code that caused the TwoPhaseUploader to fail - while uploading the file. This is logged whenever the TwoPhaseUploader fails - while uploading the file. - - - - - - Removed in M86, since the information was not being used. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The net error or response code that caused the TwoPhaseUploader to fail - while uploading metadata. This is logged whenever the TwoPhaseUploader fails - while uploading metadata. - - - - - - Starting with M32, replaced by SBDownloadFeedback.Eligible. - - mattm@chromium.org - - Count of times download feedback button has been shown, broken down by - danger type. - - - - - - Removed in M77, since the information was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Size of downloads that were of the correct danger type, regardless if they - meet the max file size check or if they are actually uploaded or not. - - - - - - Marked obsolete 07-2020 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Size of downloads that failed to be uploaded to the feedback service. - - - - - - Marked obsolete 07-2020 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Size of downloads that were successfully uploaded to the feedback service. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time it takes for the TwoPhaseUploader to complete. This is logged on - every upload. - - - - - - Removed in M77, since the information was not being used. - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - For each non-SAFE file, records whether the server requested that that file - be uploaded. - - Logged before checking the file size, so it may be dropped there. - - - - - - Marked obsolete 07-2020 due to lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - mattm@chromium.org - - Final result of attempt to upload binary to download feedback service. - - - - - - Blacklist Load analysis was removed in M63. - - caitkp@google.com - - The elapsed time to compute the hash of a blacklisted module. - - - - - - Blacklist Load analysis was removed in M63. - - caitkp@google.com - - The elapsed time to validate the signature of a blacklisted module. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident discarded by the safe browsing incident reporting - service as a result of profile or service destruction. - - - - - caitkp@chromium.org - The result of deleting a profile's download metadata file. - - - - caitkp@chromium.org - The result of reading a profile's download metadata file. - - - - caitkp@chromium.org - The result of writing a profile's download metadata file. - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident given to the safe browsing incident reporting service - but dropped as a result of not participating in safe browsing. - - - - - caitkp@google.com - - The elapsed time to collect environmental data for a safe browsing incident - report. - - - - - caitkp@google.com - - The elapsed time to find the most recent binary download from all loaded - profiles when creating a safe browsing incident report. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident included in an incident report by the safe browsing - incident reporting service. - - - - - - Removed 07/2019. - - caitkp@google.com - - The number of incidents collated into a single safe browsing incident - report. - - - - - caitkp@google.com - - The elapsed time between two successive incidents collated into the same - incident report by the safe browsing incident reporting service. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident pruned by the safe browsing incident reporting service - as a result of not having a matching binary download. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident pruned from a report in the safe browsing incident - reporting service as a result of having previously been reported. - - - - - - Removed 08/2015. - - caitkp@google.com - - The percentage of incidents pruned from a safe browsing incident report on - account of having been previously reported. - - - - - - Removed Jan 2020. - - grt@google.com - - The size, in bytes, of a profile's platform state store. This histogram is - logged on each write, which always replaces any previous contents. - - - - - - Removed Jan 2020. - - grt@google.com - The result of loading data from the platform state store. - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - - The type of incident received by the safe browsing incident reporting - service. - - - - - - - vakh@chromium.org - chrome-safebrowsing-alerts@google.com - The size, in bytes, of a safe browsing incident report. - - - - - Removed 07/2019. - - caitkp@google.com - The elapsed time to upload a safe browsing incident report. - - - - - Removed 07/2019. - - proberge@google.com - - The result of initializing the state store and comparing the preferences to - the platform-specific state store. - - - - - - Suspicious Module detection was removed in M63. - - proberge@google.com - - The elapsed time to check loaded modules against the module whitelist. - - - - - - Suspicious Module detection reporting removed in M63. - - proberge@google.com - The number of suspicious modules found. - - - - - Suspicious Module detection reporting removed in M63. - - proberge@google.com - - The elapsed time to create incidents for suspicious modules. - - - - - caitkp@google.com - - The result of an attempted report upload by the safe browsing incident - reporting service. - - - - - caitkp@google.com - - The elapsed time to verify the binary integrity of chrome.exe. - - - - - caitkp@google.com - - The elapsed time to verify the binary integrity of chrome.dll. - - - - - caitkp@google.com - - The elapsed time to verify the binary integrity of chrome_child.dll. - - - - - caitkp@google.com - - The elapsed time to verify the binary integrity of chrome_elf.dll. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Measures the total duration (including delay due to retries) of a failed - upload request. This is recorded after the last retry on every failed - upload. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The HTTP response code or net error from each upload attempt. This is - recorded once for each network request made as part of an upload, i.e. if an - upload fails the first time, but a retry succeeds, this metric is recorded - twice. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Counts how many retries were needed to complete the upload request. This is - emitted for every successful upload. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Measures the total duration (including delay due to retries) of a successful - upload request. This is recorded for every successful upload. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The size of the upload request body. This is a combination of the upload - data and metadata. This is recorded once for each upload, regardless of - whether it was successful. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the overall upload request succeeded or not. This is recorded once - for an upload request, regardless of how many retries were needed to - complete the upload. - - - - - - Superseded by SBOffDomainInclusion2.Abort in December 2015. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis was aborted. This histogram is suffixed with the abort - reason. - - - - - - Removed 01/2015. - - gab@chromium.org - - Logs the resource type of each resource request for which an off-domain - inclusion was detected by the OffDomainInclusionDetector. - - - - - - Removed 01/2015. Moved to SBOffDomainInclusion.Abort.EmptyMainFrameURL. - - gab@chromium.org - - Logs the resource type of each resource request for which the main frame URL - was unexpectedly empty in the OffDomainInclusionDetector. - - - - - - Superseded by SBOffDomainInclusion2.InHistory in December 2015. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis concluded in no inclusion whitelist hit but a browsing - history hit. - - - - - - Removed 01/2015 (was never reported, confirming experiment that handling it - is irrelevant). - - gab@chromium.org - - Logs the resource type of each resource request for which the main frame URL - was unexpectedly invalid (and not empty) in the OffDomainInclusionDetector. - - - - - - Superseded by SBOffDomainInclusion2.RequestAnalyzed in December 2015. - - gab@chromium.org - - Logs the resource type of each resource request analyzed by the - OffDomainInclusionDetector. - - - - - - Superseded by SBOffDomainInclusion2.Suspicious in December 2015. - - gab@chromium.org - - Logs the resource type of each resource request for which an off-domain - inclusion was detected by the OffDomainInclusionDetector and considered - suspicious. - - - - - - Superseded by SBOffDomainInclusion2.Suspicious in December 2015. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis concluded in an inclusion whitelist hit. - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis was aborted. This histogram is suffixed with the abort - reason. - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis concluded in no inclusion whitelist hit but a browsing - history hit. - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - gab@chromium.org - - Logs the resource type of each resource request analyzed by the - OffDomainInclusionDetector. - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - gab@chromium.org - - Logs the resource type of each resource request for which an off-domain - inclusion was detected by the OffDomainInclusionDetector and considered - suspicious. - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - gab@chromium.org - - Logs the resource type of each resource request for which the off-domain - inclusion analysis concluded in an inclusion whitelist hit. - - - - - - 2020-02-25: Replaced by Scheduler.CancelableTaskTracker.TaskState, which - allows correlation of live/canceled with same/off-sequence states. - - wez@chromium.org - scheduler-dev@chromium.org - - True if a task posted to CancelableTaskTracker was canceled before it got - the chance to run. Recorded for every task posted via CancelableTaskTracker, - immediately before it would be run. - - - - - - 2020-02-25: Replaced by Scheduler.CancelableTaskTracker.TaskDuration2_* - which correllate duration with liveness, off-sequence and task priority - states. - - wez@chromium.org - scheduler-dev@chromium.org - - Time taken for a task posted to a CancelableTaskTracker to run. Durations - are not recorded for canceled tasks. - - - - - - - wez@chromium.org - scheduler-dev@chromium.org - - Time taken for a task posted to a CancelableTaskTracker to run. Durations - are not recorded for tasks skipped due to having been canceled. - - - - - wez@chromium.org - scheduler-dev@chromium.org - - Records whether a task posted to CancelableTaskTracker was canceled before - it got the chance to run, and whether it was same-sequence or off-sequence. - Recorded for every task posted via CancelableTaskTracker, immediately before - it would be run. - - - - - - - kdillon@chromium.org - shaseley@chromium.org - - Queueing time of a task posted via the postTask API. Reported when the task - is starts and bycked by priority. Tasks who have had their priority changed - are skipped. - - - - - kdillon@chromium.org - shaseley@chromium.org - - Records whether or not a task posted via scheduler.postTask had it's - priority changed. Records when the task is started. - - - - - altimin@chromium.org - - Total wall time of all tasks in scheduler-managed threads split per thread. - - The bucket value is the sum of thread durations of all tasks in this thread - across all browsing instances. This metric is reported each time we execute - a task which has cpu time measurement. - - - - - altimin@chromium.org - - Total cpu time of scheduler-managed threads in the renderer process. - - It is supposed that Scheduler.Experimental.Renderer.CPUTimePerThread.Tracked - and Scheduler.Experimental.Renderer.CPUTimePerThread.Untracked histograms - should be analysed together. - - The bucket value is the sum of thread durations of all tasks in this thread - across all browsing instances. This metric is reported each time we execute - a task. Due to thread time being expensive to measure, only 0.01% of threads - report this metric. - - - - - altimin@chromium.org - - Sum of durations of all scheduler-managed tasks in the renderer process. - - Due to implementation constraints a difference between .Positive and - .Negative subhistograms should be analysed. See - blink::scheduler::TotalDurationMetricReporter for details. - - These metrics are updated each time a new task is executed. - - - - - altimin@chromium.org - - The results of the attempts to sample scheduling tasks into the UKM. Used to - ensure that we're not silently dropping tasks, which can lead to biases in - our analyses. - - Recorded each time a scheduling task UKM is recorded. - - - - - altimin@chromium.org - - Total wall time of all tasks in scheduler-managed threads split per thread. - - The bucket value is the sum of thread durations of all tasks in this thread - across all browsing instances. This metric is reported each time we execute - a task which has wall time measurement. - - - - - - Replaced by ActivateDuration2, due to inefficient bucketing scheme. - - brianderson@chromium.org - - How long it takes for the compositor to simply activate the pending tree. - Does not include any PrepareTiles or raster time. - - - - - stanisc@chromium.org - - The time from v-sync to when the main side actually starts the - BeginImplFrame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by BeginMainFrameIntervalCritical2, due to inefficient bucketing - scheme. - - brianderson@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - - - - - Replaced by BeginMainFrameIntervalNotCritical2, due to inefficient bucketing - scheme. - - brianderson@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is not set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - - - - - Replaced by BeginMainFrameQueueDurationCritical2, due to inefficient - bucketing scheme. - - brianderson@chromium.org - - How long it takes for the main side to start the BeginMainFrame in response - to the compositor's SendBeginMainFrame when the on_critical_path flag is - set. - - - - - - Replaced by SendBeginMainFrameToCommit.BeginMainSentToStarted of - CompositorLatency metrics as of 02/2020. - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes for the main side to start the BeginMainFrame in response - to the compositor's SendBeginMainFrame when the on_critical_path flag is - set. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by BeginMainFrameQueueDurationNotCritical2, due to inefficient - bucketing scheme. - - brianderson@chromium.org - - How long it takes for the main side to start the BeginMainFrame in response - to the compositor's SendBeginMainFrame when the on_critical_path flag is not - set. - - - - - - Replaced by BeginMainFrameStartToCommitDuration2, due to inefficient - bucketing scheme. - - brianderson@chromium.org - - The time from when the main side actually starts the BeginMainFrame to when - the commit completes on the impl side. - - - - - - Replaced by SendBeginMainFrameToCommit of CompositorLatency metrics as of - 02/2020. - - vmiura@chromium.org - sadrul@chromium.org - - The time from when the main side actually starts the BeginMainFrame to when - the commit completes on the impl side. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by BeginMainFrameQueueDurationCritical, - BeginMainFrameQueueDurationNotCritical, and - BeginMainFrameStartToCommitDuration. - - brianderson@chromium.org - - How long it takes for the blink main thread to respond to the compositor's - SendBeginMainFrame. - - - - - - Removed in 08/2018, M69. Since there is no impl thread on Browser side, - there is no activation state for Browser. - - brianderson@chromium.org - - How long it takes for the compositor to simply activate the pending tree. - Does not include any PrepareTiles or raster time. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 06/2018, M69, due to too much noise in the collected data. - - brianderson@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - Removed in 07/2018, M69. All begin frames are in critical path for browser, - no data is reported. - - brianderson@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is not set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69. All begin frames are in critical path for browser, - no data is reported. - - brianderson@chromium.org - - How long it takes for the main side to start the BeginMainFrame in response - to the compositor's SendBeginMainFrame when the on_critical_path flag is not - set. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by BeginMainFrameStartToCommitDuration. This was recorded as a - result of a typo in the code that didn't include "Duration". - - brianderson@chromium.org - - The time from when the main side actually starts the BeginMainFrame to when - the commit completes on the impl side. - - - - - - Replaced by BeginMainFrameStartToCommitDuration2. This was recorded as a - result of a typo in the code that didn't include "Duration". - - brianderson@chromium.org - - The time from when the main side actually starts the BeginMainFrame to when - the commit completes on the impl side. - - - - - - Removed in 06/2018, M69, due to too much noise in the collected data. - - brianderson@chromium.org - - The time delta between the *draw* times of back-to-back BeginMainFrames that - result in a commit. - - The interval is only recorded when the BeginMainFrames are running and - committing continuously, where continuously means when another - BeginMainFrame is requested by the next BeginImplFrame after activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - Removed in 06/2018, M69, due to too much noise in the collected data. - - brianderson@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - Removed in 07/2018, M69, due to too much noise in the data. - - paint-dev@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap, when there is at least - one composited animation. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69, due to too much noise in the data. - - paint-dev@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames of new - active trees only, regardless of whether or not they result in a swap, when - there is at least one main thread animation. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 08/2018, M69, since there is no impl thread in Browser side, this - metric does not record any meaningful data. - - brianderson@chromium.org - - Recorded every time the compositor draws with a new active tree. A value of - 0 indicates the main-side started and finished within the same frame - interval as the impl-side. Positive values correspond to how old any - main-side updates are compared to the impl-side updates. If there are no - mid-frame updates, this metric is a good proxy for how well the main and - impl threads are synchronized. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69. Since there is no pending tree in Browser, no data - is ever reported. - - ericrk@chromium.org - - Time between creating a pending tree and activating that tree. This differs - from Scheduling.ActivateDuration in that it includes time taken to raster - the pending tree, not just the time to activate it. - - The interval is recorded each time a pending tree is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69. Since there is no pending tree in Browser, no data - is ever reported. - - khushalsagar@chromium.org - - Time between starting raster work on the pending tree and when it is ready - to activate. Unlike PendingTreeDuration which - includes the time to commit - to this tree, the raster duration and the time for which the pending tree - waits before it can be activated - this only measures the time taken to - rasterize tiles required for activation. - - The interval is recorded each time we are notifed that a pending tree is - ready for activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69. No data reported because there is no pending tree - on impl thread for browser side. - - brianderson@chromium.org - - How long does the pending tree wait after it is ready to be activated and - before it is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. Impl side invalidation initiated pending tree - - - - - - Replaced by EndCommitToActivation of CompositorLatency metrics as of - 08/2020. - - vmiura@chromium.org - sadrul@chromium.org - - How long does the pending tree wait after it is ready to be activated and - before it is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. Commit initiated pending tree. - - - - - - Replaced by CommitInterval2, due to inefficient bucketing scheme. - - brianderson@chromium.org - - The time delta between the *draw* times of back-to-back BeginMainFrames that - result in a commit. - - The interval is only recorded when the BeginMainFrames are running and - committing continuously, where continuously means when another - BeginMainFrame is requested by the next BeginImplFrame after activation. - - - - - - Replaced by CommitToReadyToActivateDuration2, due to inefficient bucketing - scheme. - - brianderson@chromium.org - - How long it takes for the compositor to rasterize pending tree content after - a commit before it is ready for activation. - - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes for the compositor to rasterize pending tree content after - a commit before it is ready for activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by DrawDuration2, due to inefficient bucketing scheme. - - brianderson@chromium.org - How long it takes the compositor to draw a frame. - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes the compositor to draw a frame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by DrawInterval2, due to inefficient bucketing scheme. - - brianderson@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap. - - The interval is only recorded when every BeginImplFrame wants to draw. - - - - - - Removed 05/2018 because the experiment described in Issue 754471 is - completed. - - paint-dev@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames of new - active trees only, regardless of whether or not they result in a swap, when - there is at least one main thread animation that could be composited but - not, due to running experiment. - - The interval is only recorded when every BeginImplFrame wants to draw. - - - - - - Removed 03/28/2018 - - khushalsagar@chromium.org - - Duration for updating animated images and invalidating layers for images - invalidated on the sync tree in the compositor. This interval is recorded - each time the sync tree is updated after a commit or an impl-side - invalidation. - - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes for the compositor to rasterize pending tree content after - an impl-side invalidation before it is ready for activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by MainAndImplFrameTimeDelta2, due to inefficient bucketing scheme. - - brianderson@chromium.org - - Recorded every time the compositor draws with a new active tree. A value of - 0 indicates the main-side started and finished within the same frame - interval as the impl-side. Positive values correspond to how old any - main-side updates are compared to the impl-side updates. If there are no - mid-frame updates, this metric is a good proxy for how well the main and - impl threads are synchronized. - - - - - - Replaced by PrepareTIlesDuration2, due to inefficient bucketing scheme. - - brianderson@chromium.org - - How long it takes the compositor to PreapreTiles, which determines what - rasterization work to do. - - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes the compositor to PreapreTiles, which determines what - rasterization work to do. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by ReadyToActivateToActivationDuration2, due to inefficient - bucketing scheme. - - brianderson@chromium.org - - How long does the pending tree wait after it is ready to be activated and - before it is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by Activation stage of CompositorLatency metrics as of 08/2020. - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes for the compositor to simply activate the pending tree. - Does not include any PrepareTiles or raster time. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This is no longer usefull and would not be replaced, as of 08/2020. - - vmiura@chromium.org - sadrul@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - This is no longer usefull and would not be replaced. as of 02/2020 - - vmiura@chromium.org - sadrul@chromium.org - - This is the time delta between back-to-back BeginMainFrames completions on - the compositor side when the on_critical_path flag is not set, regardless of - whether they abort (have no updates) or commit (have updates). - - The interval is only recorded when the BeginMainFrames are running - continuously; sepcifically when another BeginMainFrame is requested by the - next BeginImplFrame after a) an abort or b) activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes for the main side to start the BeginMainFrame in response - to the compositor's SendBeginMainFrame when the on_critical_path flag is not - set. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This is no longer usefull and would not be replaced. as of 02/2020 - - vmiura@chromium.org - sadrul@chromium.org - - The time delta between the *draw* times of back-to-back BeginMainFrames that - result in a commit. - - The interval is only recorded when the BeginMainFrames are running and - committing continuously, where continuously means when another - BeginMainFrame is requested by the next BeginImplFrame after activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - - vmiura@chromium.org - sadrul@chromium.org - speed-metrics-dev@chromium.org - chrome-analysis-team@google.com - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Do not modify this metric in any way without contacting - speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for - the solution. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - flackr@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap, when there is at least - one composited animation. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - xidachen@chromium.org - animations-dev@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames, - regardless of whether or not they result in a swap, when there is at least - one custom property animation. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - flackr@chromium.org - - The time delta between the draw times of back-to-back BeginImplFrames of new - active trees only, regardless of whether or not they result in a swap, when - there is at least one main thread animation. - - The interval is only recorded when every BeginImplFrame wants to draw. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This is no longer usefull and would not be replaced. as of 02/2020 - - vmiura@chromium.org - sadrul@chromium.org - - Recorded every time the compositor draws with a new active tree. A value of - 0 indicates the main-side started and finished within the same frame - interval as the impl-side. Positive values correspond to how old any - main-side updates are compared to the impl-side updates. If there are no - mid-frame updates, this metric is a good proxy for how well the main and - impl threads are synchronized. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This duration is reported in EndCommitToActivation and Activation of - CompositorLatency metrics, and is removeded as of 03/2020. - - ericrk@chromium.org - - Time between creating a pending tree and activating that tree. This differs - from Scheduling.ActivateDuration in that it includes time taken to raster - the pending tree, not just the time to activate it. - - The interval is recorded each time a pending tree is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - khushalsagar@chromium.org - - Time between starting raster work on the pending tree and when it is ready - to activate. Unlike PendingTreeDuration which - includes the time to commit - to this tree, the raster duration and the time for which the pending tree - waits before it can be activated - this only measures the time taken to - rasterize tiles required for activation. - - The interval is recorded each time we are notifed that a pending tree is - ready for activation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Replaced by EndCommitToActivation of CompositorLatency metrics as of - 08/2020. - - vmiura@chromium.org - sadrul@chromium.org - - How long does the pending tree wait after it is ready to be activated and - before it is activated. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in 07/2018, M69. The swap ack is always received within 8 seconds. - - brianderson@chromium.org - - True if the swap ack was received within approximately 8 seconds of the - swap. Although 8 seconds isn't exactly fast, it is a threshold that - represents a hang or the appearance of a hang. - - - - - - Replaced by SwapToAckLatency2, due to inefficient bucketing scheme. - - brianderson@chromium.org - How long it takes the swap ack to return after a swap. - - - - vmiura@chromium.org - sadrul@chromium.org - - How long it takes the swap ack to return after a swap. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - antrim@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - ultrotter@chromium.org - - What type of authentication was attempted when the user failed to unlock the - lock screen. - - - - - antrim@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - ultrotter@chromium.org - The time spent for authentication in case of a failure. - - - - antrim@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - ultrotter@chromium.org - - What type of authentication was attempted when the user successfully - unlocked the lock screen. - - - - - antrim@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - ultrotter@chromium.org - The time spent for authentication in case of a success. - - - - antrim@chromium.org - jessejames@chromium.org - rsorokin@chromium.org - ultrotter@chromium.org - The time spent before the screen locker is ready. - - - - - Experiment complete, histogram gathering code removed. - - ellyjones@chromium.org - - Whether an SDCH dictionary was advertised over a secure scheme or not. This - histogram is logged inside SdchManager at advertisement time. - - - - - - Removed 2017-9. - - - The number of dictionaries advertised in an HTTP GET transaction that - supports SDCH. Note that only non-zero advertisements are logged. - - - - - - Removed 2017-9. - - - The reason why a blacklist blocking a request from advertising SDCH was - implemented. There is one entry in this histogram per inhibited request. - - - - - - Removed 2017-9. - - - Each sample is the byte count for a dictionary that is loaded by Chrome. A - dictionary is loaded shortly after the first Google query performed in each - session, and allows future SDCH transactions to be encoded/decoded using - that dictionary. - - - - - - Removed 2017-9. - - - The fate, both on input and output, of dictionary requests. There is - intended to be two entries in this histogram for each Get-Dictionary seen - (except failed requests are not currently tracked). - - - - - - Removed 2017-9. - - - The number of times a dictionary has been successfully used for decoding, - recorded at the time it is evicted from the manager. - - - - - - Replaced by Sdch3.Experiment3_Holdback. - - - Duration in time from when a request was made, until all bytes were - received. During the running of an SDCH latency experiment, these packets - were part of an SDCH encoded transmission made after the link had proven it - was capable of handling SDCH compression. - - - - - - Replaced by Sdch3.Experiment3_Holdback. - - - Duration in time from when a request was made, until all bytes were - received. During the running of an SDCH latency experiment, these packets - were part of a holdback, which precluded SDCH despite the fact that the link - had proven it was capable of handling SDCH compression. - - - - - - Removed 2017-9. - - - Duration in time from the first byte of a request was received, until all - bytes were received. During the running of an SDCH latency experiment, these - packets were part of an SDCH encoded transmission made after the link had - proven it was capable of handling SDCH compression. - - - - - - Removed 2017-9. - - - Duration in time from the first byte of a request was received, until all - bytes were received. During the running of an SDCH latency experiment, these - packets were part of a holdback, which precluded SDCH despite the fact that - the link had proven it was capable of handling SDCH compression. - - - - - - Replaced by Sdch3.Experiment2_Decode. - - - Duration in time from when a request was made, until all bytes were - received. During the running of an SDCH latency experiment, these packets - were part of an SDCH encoded transmission made after the link had proven it - was capable of handling SDCH compression. - - - - - - Replaced by Sdch3.Experiment2_Holdback. - - - Duration in time from when a request was made, until all bytes were - received. During the running of an SDCH latency experiment, these packets - were part of a holdback, which precluded SDCH despite the fact that the link - had proven it was capable of handling SDCH compression. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - During the running of an SDCH latency experiment, these packets were part of - a holdback, which precluded SDCH despite the fact that the link had proven - it was capable of handling SDCH compression. - - - - - - Removed 2016-11. - - - The duration between receipt of the 1st holdback (non-SDCH encoded) packet - and receipt of the last packet. Only groups that are part of the holdback - (i.e., could have been sdch encoded) are sampled. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - During the running of an SDCH latency experiment, these packets were part of - a holdback, which precluded SDCH despite the fact that the link had proven - it was capable of handling SDCH compression. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - During the running of an SDCH latency experiment, these packets were part of - a holdback, which precluded SDCH despite the fact that the link had proven - it was capable of handling SDCH compression. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - During the running of an SDCH latency experiment, these packets were part of - a holdback, which precluded SDCH despite the fact that the link had proven - it was capable of handling SDCH compression. - - - - - - Removed 2016-11. - - - If SDCH decoding was disabled client side, this records how many URLs were - processed by the SDCH filter before disabling this feature. The most common - number is 1, which happens when there is one home-page tab that contains - SDCH encoded data, for which there is no dictionary loaded into the Chrome - process (yet), since Chrome was just restarted. Large values in this - histogram are indicative of flaky decompression, that works for a while, and - then is disabled. Values of 2 or 3 may appear if a user has more than one - home page with a query, and restarts there browser. - - - - - - Removed 2017-9. - - - The amount of time between creation/load of an SDCH dictionary and its first - use. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 1st SDCH encoded packet and receipt of the 2nd packet, for - processing by the SDCH filter. Packet count boundaries are calculated each - time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - The duration between receipt of the 1st SDCH encoded packet and receipt of - the last packet, for processing by the SDCH filter. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 2nd SDCH encoded packet and receipt of the 3rd packet, for - processing by the SDCH filter. Packet count boundaries are calculated each - time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 3rd SDCH encoded packet and receipt of the 4th packet, for - processing by the SDCH filter. Packet count boundaries are calculated each - time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 4th SDCH encoded packet and receipt of the 5th packet, for - processing by the SDCH filter. Packet count boundaries are calculated each - time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - (discontinued 7/29/2009, and replaced by - Sdch3.Network_Decode_Bytes_Processed_b) The number of bytes processed - (received over the net or from cache) by the SDCH filter chain. - - - - - - Removed 2017-9. - - - The number of bytes processed (received over the net or from cache) by the - SDCH filter chain. - - - - - - Removed 2016-11. - - - The number of bytes emitted after decoding by the SDCH filter. - - - - - - Removed 2016-11. - - - The duration between putting the first byte of a request (such as a GET) on - the wire, until the last by of compressed SDCH encoded content is received - (with durations over 10 minutes discarded). During a planned latency - experiment, some clients will receive encoded SDCH data, and other will - received mere gzip'ed data (that passes through the SDCH filter unchanged). - - - - - - Removed 2016-11. - - - An approximation to the total number of SDCH encoded packets received for - processing by the SDCH filter. Packet count boundaries are calculated each - time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - The ratio of the number of bytes read from the network (or cache) and fed to - the filter chain (usually the gunzip filter) vs. the number of bytes emitted - by the SDCH filter to be rendered. This is commonly described as the SDCH - compression ratio. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - The duration between receipt of the 1st **NON**-SDCH encoded packet to - receipt of the last packet, for processing by the SDCH filter. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - Sampling only transmissions with 5 or more packets, the duration between - receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet, - for processing by the SDCH filter. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - - The duration between putting the first byte of a request (such as a GET) on - the wire, until the last by gzip compressed content is received and - passed-through unchanged by the SDCH filter (with durations over 10 minutes - discarded). During a planned latency experiment, some clients will receive - encoded SDCH data, and other will received mere gzip'ed data (that passes - through the SDCH filter unchanged). - - - - - - Removed 2016-11. - - - The total number of **NON**-SDCH encoded packets received for processing by - the SDCH filter in one URL fetch. Packet count boundaries are calculated - each time a read from the filter is called, assuming 1430 bytes of data per - packet since the last boundary calculation. This *tends* to properly count - small packets, but can err if small packets come at roughly the same time. - - - - - - Removed 2016-11. - - ellyjones@chromium.org - - The absolute difference in bytes between the amount of data entering the - SDCH filter and the amount of data exiting the SDCH filter. - - - - - - Removed 2017-9. - - ellyjones@chromium.org - - Absolute sizes, in bytes, of SDCH dictionaries fetched over the network. - These are logged in SdchOwner when dictionary fetches complete. - - - - - - Removed 2016-11. - - - If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF - decoder still has internally buffered data that has never been read, this - histogram reports the number of bytes that were received over the net (or - from the cache) and fed to the start of the filter chain (usually to the - gunzip filter). - - - - - - Removed 2016-11. - - - If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF - decoder still has internally buffered data that has never been read, this - histogram reports the number of bytes that were received over the net (or - from the cache) and fed to VCDIFF decoder (usually after gunzipping). - - - - - - Removed 2016-11. - - - If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF - decoder still has internally buffered data that has never been read, this - histogram reports the number of bytes that were output by the VCDIFF decoder - (and sent toward the renderer). - - - - - - Removed 2017-9. - - - Tracks failures that occur when reading in or writing out persisted - dictionary information. - - - - - - Removed 2014-11. Sdch3.ProblemCodes_5 used instead. - - Each sample is the report of a distinct problem code. - - - - - Removed 2014-11. Sdch3.ProblemCodes_5 used instead. - - Each sample is the report of a distinct problem code. - - - - - Removed 2017-9. - - Each sample is the report of a distinct problem code. - - - - - Removed 2017-9. - - - Attempted SDCH decoding can fail at the Read() filter processing stage. In - some of those cases, the request is corrupted enough that it must be either - retried or failed completely. This histogram records the details of why the - request was considered corrupted, for results returned from the cache. - - - - - - Removed 2017-9. - - - Attempted SDCH decoding can fail at the Read() filter processing stage. In - some of those cases, the request is corrupted enough that it must be either - retried or failed completely. This histogram records the details of why the - request was considered corrupted for results returned from the network. - - - - - - Removed 2017-9. - - ellyjones@chromium.org - - Measures the time-weighted memory use of SDCH dictionaries, in bytes. The - numerator is bytes of dictionary times seconds that dictionary was in - memory, and the denominator is seconds that the Chrome process lives. - - - - - - Removed 2016-11. - - - If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is - still buffering output of the VCDIFF decoder that has never been read, this - histogram reports the number of bytes that were in that buffer. - - - - - - Removed 2016-11. - - - If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is - still buffering output of the VCDIFF decoder that has never been read, this - histogram reports the number of bytes that were received over the net (or - from the cache) and fed to the start of the filter chain (usually to the - gunzip filter). - - - - - - Removed 2016-11. - - - If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is - still buffering output of the VCDIFF decoder that has never been read, this - histogram reports the number of bytes that were received over the net (or - from the cache) and fed to VCDIFF decoder (usually after gunzipping). - - - - - - Removed 2016-11. - - - If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is - still buffering output of the VCDIFF decoder that has never been read, this - histogram reports the number of bytes that were output by the VCDIFF decoder - (and sent toward the renderer). - - - - - - Use Sdch3.UsageInterval2 instead. - - - The amount of time from the last time an SDCH dictionary was used. For the - first use of a dictionary, the maximum time is used. - - - - - - Removed 2017-9. - - - The amount of time from the last time an SDCH dictionary was used. Not - recorded on first dictionary use. First use is recorded as - Sdch3.FirstUseInterval. - - - - - - Replaced by Search.AddSearchProvider2, which is also now obsolete. - - estade@chromium.org - - Measures how much the user modifies their search engines, whether through - window.external.AddSearchProvider or chrome://settings. - - - - - - AddSearchProvider was removed 05/2016. - - estade@chromium.org - - Measures usage of window.external.AddSearchProvider and user interaction - with the resulting confirmation dialog (if any). Only works on Views - platforms (Win, Linux, CrOS). - - - - - - - - - donnd@chromium.org - twellington@chromium.org - chrome-analysis-team@google.com - - Records whether the user opened the panel when it was shown. Recorded for - all gestures for all users when the UX is hidden. Implemented for Android. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - donnd@chromium.org - twellington@chromium.org - - The type of card returned in the Search Term Resolution Response from the - server when a search is resolved in response to a Tap gesture that uses - surrounding text to determine the best search. This characterises what we'll - show in the Bar. Recorded when the panel is closed. Implemented for Android. - - - - - - - donnd@chromium.org - twellington@chromium.org - - The type of card shown in the Bar when the panel has been opened. Recorded - when the panel is closed. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records the duration of persisted outcomes between the time they were stored - and the time that they were sent back to the server. Recorded when persisted - data is sent to the server. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Logs that the UX has entered a state where features are available to be - recorded to Ranker. A value of true indicates that the available features - include outcomes, false if they are just features at inference-time. Use to - correlate with what actually gets recorded in the Search. - ContextualSearch.Ranker.Recorded histogram. Recorded when a tap gesture is - recognized that might trigger our UX (for pure features), and when the UX is - actually shown (for outcomes). Implemented for Android. - - - - - donnd@chromium.org - charleszhao@chromium.org - Tracks the outcome of attempts to download a Ranker Model. - - - - donnd@chromium.org - twellington@chromium.org - - Records whether the user opened the panel when a tap was not suppressed by - Ranker. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Logs that features were recorded to Ranker and whether it was an outcome or - not. Recorded when the UX is shown or hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Logs that features were recorded to Ranker from native code and whether it - was an outcome or not. Recorded when the UX is shown or hidden. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records Ranker's prediction about whether a tap should be suppressed or not. - Recorded when the UX is hidden. Implemented for Android. - - - - - charleszhao@chromium.org - donnd@chromium.org - - Time taken for the Ranker Model Loader to download its model from the - configured URL, in ms. - - - - - charleszhao@chromium.org - donnd@chromium.org - - Time taken for the Ranker Model Loader to parse its model, in ms. - - - - - charleszhao@chromium.org - donnd@chromium.org - - Time taken for the Ranker Model Loader to read its model from local storage - (cache), in ms. - - - - - charleszhao@chromium.org - donnd@chromium.org - - Time taken for the Ranker Model Loader to write its model to local storage, - in ms. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether Ranker was able to make a prediction about tap suppression. - Recorded when the UX is triggered by tap. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether the user opened the panel when a tap would be suppressed by - Ranker if suppression was enforced. Recorded when the UX is hidden. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records that a resolve response was received from the server, and whether - that was due to a Tap gesture or not (vs longpress). Recorded when the user - triggers the feature and the server responds. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records that a resolve request was sent to the server, and whether that was - due to a Tap or not (vs longpress). Recorded when the user triggers the - feature. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records that a resolve request from the server caused the selection to be - expanded, and whether that original selection was due to a Tap or not (vs - longpress). Recorded when the qualifying server response is received. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether the user opened the panel when it was shown in response to a - tap gesture, for all users. Recorded when the UX is hidden. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether the user opened the panel when it was shown for sync-enabled - users only (this is an approximation for the population that logs to UKM). - Recorded for all gestures for users with sync enabled when the UX is hidden. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records that a translation is needed for the current Contextual Search, and - whether the selection was originally created by a Tap gesture. This is - recorded regardless of whether the user will actually be shown a translation - or not. Recorded any time a selection is established or changed with the - Contextual Search Translations feature enabled. Implemented for Android. - - - - - donnd@chromium.org - contextual-search-eng@google.com - - Records whether an IPH promoting the Opt-in for the Translations experiment - has ever been shown for the current user. Recorded when the Overlay Panel is - closed. Implemented for Android. - - - - - donnd@chromium.org - contextual-search-eng@google.com - - Records whether the user actually did Opt-in right after seeing the IPH for - the Translations experiment. Recorded when the Overlay Panel is closed. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records the previous state of the user's enabled preference to indicate - whether they were decided or undecided about fully enabling this feature. - Recorded during the rollout of Unified Consent when the Contextual Search - preference is changed. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether throttling for Unified Consent was done for all requests. - Recorded when the user taps on text and the system would like the server to - suggest what to search for using page context, regardless of feature-enabled - state. Recorded multiple times for each request. Supports the rollout of - Unified Consent for Contextual Search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Records whether this user had a request throttled or not when needed. - Recorded when the user taps on text and the system would like the server to - suggest what to search for using page context, and throttling is in effect - for this user. Supports the rollout of Unified Consent for Contextual - Search. Implemented for Android. - - - - - - Removed 05/2017 because it's no longer ever used. - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen during a contextual search where the - selected text consisted of all capital letters. Only logged when contextual - search is triggered due to a tap. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration that the panel was peeking before being opened when triggered - by a tap that was in a part of the screen where it overlaps the Bar. Logged - when the panel is closed after being opened. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a Tap was suppressed because the Bar overlapped the selection area. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration that the panel was peeking before being opened when triggered - by a tap at the bottom of the screen where it overlaps the Bar. Logged when - the panel is closed after being opened. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether the Bar overlapped the selection area and whether the results were - seen. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The protocol of the base page, logged at the time that any Search Term - Resolution Response is received. - - - - - - Discontinued on 5/2017 due to experiment being completed. - - donnd@chromium.org - pedrosimonetti@chromium.org - twellington@chromium.org - - The details (blacklist reason and whether the results were seen) of every - search term issued by a tap gesture. Implemented for Android. - - - - - - - donnd@chromium.org - twellington@chromium.org - - Whether Contextual Cards data was shown in the Contextual Search Bar. - Contextual Cards data is included with the search term resolution response. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen as part of a Contextual Search when - Contextual Cards data was shown. This indicates that the panel was opened. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration between the panel being triggered and the panel being dismissed - due to a scroll when search results were not seen. Implemented for Android. - Prior to M57 this was recorded on tap and longpress; on M57+ it is only - recorded on tap. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration between the panel being triggered and the panel being dismissed - due to a scroll when search results were seen. Implemented for Android. - Prior to M57 this was recorded on tap and longpress; on M57+ it is only - recorded on tap. - - - - - - Discontinued on 2/2017 Due to data being buggy and not useful. - - donnd@chromium.org - twellington@chromium.org - - The time from opening the panel until the SERP is fully loaded. Applies only - to non-prefetched requests. Implemented for Android. - - - - - - Discontinued on 2/2017 Due to data being buggy and not useful. - - donnd@chromium.org - twellington@chromium.org - - The time from opening the panel until the SERP is fully loaded. Applies only - to prefetched requests. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from initiating to ending a contextual search, when results were - seen as part of the search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from initiating to ending a contextual search, when results were - not seen as part of the search and the search did not end with the beginning - of another contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from initiating to ending a contextual search, when results were - not seen as part of the search and the search ended with the beginning of - another contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (previous state and reason) of the first entry into the closed - panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (previous state and reason) of the first entry into the expanded - panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (previous state and reason) of the first entry into the - maximized panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (previous state and reason) of the first entry into the peeked - panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen as part of a Contextual Search when a tap - was on a word that we think is an entity. Recorded when Contextual Search is - dismissed. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (destination state and reason) of the first exit out of the - closed panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (destination state and reason) of the first exit out of the - expanded panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (destination state and reason) of the first exit out of the - maximized panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The details (destination state and reason) of the first exit out of the - peeked panel state within a contextual search. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The status of the Contextual Search fallback Search request. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The state of the Contextual Search Preference after the first run flow. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether the first run flow's panel was seen as part of a contextual search. - Only logged when the user triggered the first run flow yet exited the search - still in the undecided preference state. Implemented for Android. - - - - - - Contextual Search icon sprite removed 04/2017. - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen, whether the search provider icon sprite - was animated when the panel first appeared, and the triggering gesture. If - animation is disabled due to a field trial, we still log - "animated" if the animation would have run otherwise. - - - - - donnd@chromium.org - mahmoudi@chromium.org - twellington@chromium.org - - The number of times the Contextual Search panel is opened, categorized by - whether In-Product Help for Contextual Search was shown before. Logged when - the panel is opened. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from starting a literal search until the results in the SERP start - to become viewable. Applies only to prefetched requests. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The status of the Contextual Search low priority Search request. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The outcome of the mandatory Promo broken down by original triggering - gesture. Logged for each view of the promo. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The status of the Contextual Search normal priority Search request. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from opening the panel beyond peek until the panel is closed. - Implemented for Android. - - - - - donnd@chromium.org - mahmoudi@chromium.org - twellington@chromium.org - - The number of times the Contextual Search panel is opened, categorized by - whether In-Product Help for opening the panel was shown before. Logged when - the panel is opened. Implemented for Android. - - - - - - Removed because the feature no longer exists. - - donnd@chromium.org - pedrosimonetti@chromium.org - twellington@chromium.org - - The number of times the Peek Promo was seen. This histogram will be emitted - when the Panel closes. The panel is always visible when the Peek Promo is - shown, so this histogram will always be emitted after a Promo is shown - (except in the case of a crash). This histogram does not care whether the - Panel was opened. - - - - - - Removed because the feature no longer exists. - - donnd@chromium.org - pedrosimonetti@chromium.org - twellington@chromium.org - - The number of times the Peek Promo was seen until the Panel was opened. This - histogram will be emitted when the Panel closes, if the Panel was opened - with the Peek Promo visible. If the Panel is not opened, nothing will be - emitted. - - - - - - Removed because the feature no longer exists. - - donnd@chromium.org - pedrosimonetti@chromium.org - twellington@chromium.org - - The outcome of the Contextual Search Peek Promo for those who have seen the - promo and for those who would have seen the promo if it was enabled, so we - can compare the effect of the promo on users opening the Panel. This - histogram will be emitted when the Panel closes, if the conditions to - display the Peek Promo are met, regardless of whether the Peek Promo was - actually visible (the Promo is controlled by Finch) and regardless of - whether the Panel was opened. - - - - - - - donnd@chromium.org - twellington@chromium.org - - The state of the Contextual Search Preference. Can be logged multiple times. - Used to determine the population size (user view). Implemented for Android. - - - - - - - donnd@chromium.org - twellington@chromium.org - - The Contextual Search preference state after a modification from the - preference menu. Implemented for Android. - - - - - - Discontinued on 2/2017 Due to data not being useful. - - donnd@chromium.org - twellington@chromium.org - - A summary histogram for prefetch timings, indicating fully preloaded, etc. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The CTR from the previous 28 day period for each user, expressed as a - percentage. Logged the first time the panel is closed in each new week. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The number of user impressions of the Bar from the previous 28 day period. - Logged the first time the panel is closed in each new week. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The CTR from the previous week for each user, expressed as a percentage. - Logged the first time the panel is closed in each new week. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The number of user impressions of the Bar from the previous week. Logged the - first time the panel is closed in each new week. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The total count of times that the bar with the promo has been opened. Once - the user decides, this counter is no longer updated. - - - - - donnd@chromium.org - twellington@chromium.org - - The outcome of the promo broken down by original triggering gesture. Logged - for each view of the promo. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether the promo was seen, broken down by original triggering gesture. - Logged each time the promo was activated. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The historic number of taps that showed a peeking bar with the opt-out promo - before the first time the user opened the panel. - - - - - donnd@chromium.org - twellington@chromium.org - - The historic number of taps that showed a peeking bar with the opt-out promo - for users who have never opened the panel. This count may be limited by the - Finch config param promo_on_limited_taps. - - - - - donnd@chromium.org - twellington@chromium.org - - The number of remaining taps that can trigger the promo for this user. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The category of quick actions shown in the Contextual Search bar. Recorded - when the quick action is set. Implemented for Android. - - - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a quick action in the Contextual Search bar was clicked, which - activates the associated intent. Recorded when Contextual Search is - dismissed due to a click on a QuickAction in the Bar. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a Contextual Search quick action intent resolved to zero, one, or - many apps. Recorded when the quick action intent URI is resolved. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen as part of a Contextual Search when a quick - action was shown. Recorded when Contextual Search is dismissed. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a quick action was shown in the Contextual Search bar. Recorded when - the quick action is set. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a Quick Answer was activated, considered an answer, and seen. - Implemented for Android. - - - - - - Removed 02/2017. - - donnd@chromium.org - twellington@chromium.org - - The duration since a recent scroll when the results were not seen. Recorded - when the UX is hidden. Implemented for Android. - - - - - - Removed 02/2017. - - donnd@chromium.org - twellington@chromium.org - - The duration since a recent scroll when the results were seen. Recorded when - the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether showing the Tap to Search UX in response to a Tap was suppressed by - a recent scroll. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from starting a resolving search until the Search Term Resolves. - Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time from starting a resolving search until the results in the SERP - start to become viewable. Applies only to prefetched requests. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether the search term was single or multi-word, logged at the time that - any Search Term Resolution Response is received. - - - - - - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen as part of a contextual search. Implemented - for Android. - - - - - - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen, broken down by original triggering - gesture. Only includes users that have enabled. Implemented for Android. - - - - - - Removed 05/2017 because it's no longer ever used. - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen (Contextual Search panel was opened) when - the selection was part of a URL, broken down by original triggering gesture. - Includes both users that have enabled Contextual Search and users that are - undecided (have neither enabled or disabled the feature). Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether Taps near the top of the screen was suppressed. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a second tap that was allowed to override ML - Tap Suppression. Recorded when the UX is hidden. Implemented for Android. - - - - - - Removed 11/2017 because the data is no longer valuable. - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap during suppression when Tap Suppression - is enabled. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The length of the triggering selection when search results were not seen. - Only logged when contextual search is triggered due to a tap. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The length of the triggering selection when search results were seen. Only - logged when contextual search is triggered due to a tap. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a Tap was suppressed because the selection length was less than the - minimum selection length. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether a Contextual Search selection was valid. Implemented for Android. - - - - - - Removed 02/2017 because the data is no longer valuable. - - donnd@chromium.org - twellington@chromium.org - - Whether the SERP was fully loaded when an opened panel was closed. - - - - - - Removed in M75 because the data is no longer needed. - - donnd@chromium.org - twellington@chromium.org - - Emitted when a translate one-box should be forced, to indicate if it - actually was forced or simply would have been forced if not disabled by a - flag in the variations_service. - - - - - - Removed 05/2017 because the data is no longer needed. - - donnd@chromium.org - twellington@chromium.org - - Whether search results were seen during a contextual search where the - selected text started with a capital letter but was not all capital letters. - Only logged when contextual search is triggered due to a tap. Implemented - for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration of a tap that triggered a Contextual Search when the user does - not open the panel. Implemented for Android. Logged when the panel closes - after being triggered by a tap. - - - - - donnd@chromium.org - twellington@chromium.org - - The duration of a tap that triggered a Contextual Search when the user does - open the panel. Implemented for Android. Logged when the panel closes after - being triggered by a tap and subsequently opened. - - - - - donnd@chromium.org - mahmoudi@chromium.org - twellington@chromium.org - - The number of times the Contextual Search is triggered by tapping, - categorized by whether In-Product Help for tapping was shown before. Logged - when Contextual Search is triggered by tapping. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap that was of long duration. Recorded when - the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap that was on a word considered long. - Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap that was on the middle part of a word. - Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap that was of short duration. Recorded - when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap that was on a word considered short. - Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The count of taps that showed a peeking bar without the opt-out promo since - this user has last opened the panel. - - - - - donnd@chromium.org - twellington@chromium.org - - The count of taps that showed a peeking bar with the opt-out promo since - this user has last opened the panel. - - - - - - Removed 11/2017 because the data is no longer valuable. - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap before suppression when Tap Suppression - is enabled. Recorded when the UX is hidden. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - Whether results were seen for a Tap and whether any suppression heuristic - was satisifed. Recorded when the UX is still shown (suppression not enabled, - only logged). Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The time between tapping on a word and performing a search. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The DPs count histogram for Taps that were not seen. Implemented for - Android. - - - - - donnd@chromium.org - twellington@chromium.org - - The DPs count histogram for Taps that were seen. Implemented for Android. - - - - - donnd@chromium.org - twellington@chromium.org - - For each contextual search that is triggered by tap, records whether the - translation conditions are met. Implemented for Android. - - - - - mathp@chromium.org - - The origin/cause of a change to the default search provider. - - - - - - Made obsolete around Chrome 32. Use Search.DefaultSearchProviderType - instead. - - Please list the metric's owners. Add more owner tags as needed. - - The id of the default search engine that is loaded after Chrome startup. See - src/chrome/browser/search_engines/prepopulate_engines.json for more info. - - - - - mpearson@chromium.org - csharp@chromium.org - - The type of the default search engine that is loaded when a profile is - opened or after a profile reset. Note that at least one profile is opened on - startup. Due to an error, there was a period from roughly May 9 2014 to May - 23 2014 during which this was not being logged. - - - - - - Removed 05/2016 because desktop searches are no longer opened in the default - browser. - - fdoray@chromium.org - - The action performed by the user to close the infobar explaining that a - desktop search has been redirected to the default search engine. - - - - - - Removed 05/2016 because desktop searches are no longer opened in the default - browser. - - fdoray@chromium.org - - The action performed when a desktop search URL is passed to the browser - through the command line. - - - - - lizeb@chromium.org - - On Android, when GSA tells Chrome about an account change, what is the - notification mechanism used, which is either the service connection, or a - broadcast. Recorded once per account change. - - - - - lizeb@chromium.org - - On Android, whether GSA tells Chrome about account changes through the - service or through a broadcast. This is reported at most once per Chrome - startup. - - - - - - Removed 06/2017, no longer recorded. - - lizeb@chromium.org - - On Android, when Chrome connects to a bound service exposed by GSA, the - memory footprint of the GSA process in KB, as measured by PSS. Reported at - most once per Chrome startup. - - - - - wychen@chromium.org - yusufo@chromium.org - - The last sequential number in the delta file for Icing. This is measured on - cold start. - - - - - wychen@chromium.org - yusufo@chromium.org - - The number of entries in the delta file level DB for Icing. This is measured - on cold start. - - - - - wychen@chromium.org - yusufo@chromium.org - - The number of entries in the usage report level DB for Icing. This is - measured on cold start. - - - - - donnd@chromium.org - - Records the reason why a context report to Icing failed, every time Chrome - attemps to record the current context (tab switching, navigations, etc). - Also records reasons why context reporting might be disabled. Recorded on - Android only. - - - - - sczs@chromium.org - gambard@chromium.org - - When an iOS user changes the default search engine in chrome Settings, - records the search engine's type. - - - - - - Removed after migrator is deleted in 12/2016. - - caitkp@chromium.org - - The number of times that a user-selected DSE was migrated from separate - String/List/..Value preferences to the new single DictionaryValue used in - M36. - - - - - yusufo@chromium.org - - The entry point used for all searches performed under partnership after the - Android search engine promo dialog was shown. This is a dialog prompting the - user to pick a default search engine. This metric is collected for every - search query performed. - - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Indicates whether or not a bitmap could be shown for a tile. - - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the time taken to fetch a bitmap for a tile when a bitmap could be - found. It includes the time starting from the UI layer requesting the - backend till the backend returns the associated bitmap. - - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - - Records duration from time when first task scheduled to time the fetch task - completed. - - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - Records the hour (0-23) when the TileFetcher task starts. - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - Records the HTTP response code get from TileFetcher. - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - Records the net error code get from TileFetcher. - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - - Records the reasons caused the tile group pruned in TileManager. - - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - - Records the TileManager status after initialized and loaded completed. - - - - - xingliu@chromium.org - chrome-upboarding-eng@google.com - - Records the image preloading events when the query tile images are fetched - from the background task. - - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the time taken by the bitmap request for a tile when no bitmap could - be found. It includes the time starting from the UI layer requesting the - backend till the backend returns the associated bitmap. - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the index of the query tile chip that was clicked from the fake - search box on the new tab page. - - - - - hesen@chromium.org - chrome-upboarding-eng@google.com - - Records the TileFetcher status after request send to server and response - received. - - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the index of the tile that was clicked. The index refers to the - position of the tile in the carousel. - - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - Indicates whether the tile clicked was a top level tile. - - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Indicates the number of tiles displayed in the UI after the backend was - loaded. - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the number of tiles per row that can be fit into the screen in the - default scroll position. - - - - - shaktisahu@chromium.org - chrome-upboarding-eng@google.com - - Records the width of a single query tile when shown in the carousel. - - - - - - - yusufo@chromium.org - - The search engines listed in the options for search engine promo. This is an - Android specific dialog prompting the user to pick a default search engine. - The dialog was shown on a device that had Chrome before it was first - introduced. - - - - - yusufo@chromium.org - - The search engine selected by the user from the search engine promo. This is - an Android specific dialog prompting the user to pick a default search - engine. The dialog was shown on a device that had Chrome before it was first - introduced. - - - - - yusufo@chromium.org - - The current state for search widget use and whether the device is a - partnership device related with the Android Search Widget. Collected on - every cold start. - - - - - mmourgos@chromium.org - newcomer@chromium.org - Time between showing and hiding the answer card. - - - - newcomer@chromium.org - - Time between sending an answer server request and the end of loading of the - answer card. Failed requests and requests not returning an answer are not - counted. - - - - - newcomer@chromium.org - - Time between sending an answer server request and successful finish of - navigation. Failed requests and requests not returning an answer are not - counted. - - - - - newcomer@chromium.org - Result of a answer server request. - - - - newcomer@chromium.org - - Time between successfully loading an answer card request and updating its - preferred size. There might be no or more than one size update per card - load. Size updates that happen before the card finishes loading are ignored - since they are not visible. - - - - - estark@chromium.org - - The compliance of each main frame navigation's connection with the - Certificate Transparency policy. Recorded whenever a main-frame, - non-same-page navigation is committed. Connections can be compliant, or they - can be non-compliant for one of several reasons (not enough Signed - Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old - so CT compliance wasn't checked). - - - - - jdeblasio@chromium.org - - When TLS client authentication is requested by the server, Chrome must - choose whether to return a certificate or to abort the handshake. This - histogram records how this determination was made, either as a result of - user action, or as chosen automatically due to content settings. It only - records when a fresh certificate selection would be attempted (and thus - ignores cache hits). This histogram is recorded in SSLClientAuthObserver for - user-selected outcomes and in ChromeContentBrowserClient for policy - outcomes. This histogram does not cover mobile, as certificate handling is - not handled by Chrome on Android nor iOS. - - - - - - Removed 2018-12 after HTTPBad was rolled out for all HTTP pages. This metric - was recorded only after sensitive input events, which were removed. - - estark@chromium.org - - Records the time from when a page was put into a warning state because of a - sensitive input on an HTTP page until a navigation starts. Recorded at most - once per main-frame navigation. The Finch trial 'mark-non-secure-as' - controls whether the user sees an omnibox warning for this state, or just a - console warning. - - - - - - Removed on 2016-11-10 because this is replaced by two separate metrics: - Security.HTTPBad.UserWarnedAboutSensitiveInput.CreditCard and - Security.HTTPBad.UserWarnedAboutSensitiveInput.Password. - - elawrence@chromium.org - estark@chromium.org - - Whether a "Not Secure" warning was shown in the omnibox because a - security-sensitive form field was rendered in a non-secure context. Logged - at most once per main-frame navigation. - - - - - - Removed 2018-12 after HTTPBad was rolled out for all HTTP pages, and - discrete credit card / password tracking was removed. - - elawrence@chromium.org - estark@chromium.org - - Whether a "Not Secure" warning was shown in the omnibox because a - credit card form field was rendered in a non-secure context. Logged at most - once per main-frame navigation. - - - - - - Removed 2018-12 after HTTPBad was rolled out for all HTTP pages, and - discrete credit card / password tracking was removed. - - elawrence@chromium.org - estark@chromium.org - - Whether a "Not Secure" warning was shown in the omnibox because a - password form field was rendered in a non-secure context. Logged at most - once per main-frame navigation. - - - - - - Removed 2018-12 after HTTPBad was rolled out for all HTTP pages. This metric - was recorded only after sensitive input events, which were removed. - - estark@chromium.org - - Records the time delta between when a page was put into a warning state - because of a sensitive input on an HTTP page and when the WebContents was - destroyed. Recorded at most once per main-frame navigation, and it is not - recorded if the user starts a navigation before the WebContents is - destroyed. The Finch trial 'mark-non-secure-as' controls whether the user - sees an omnibox warning for this state, or just a console warning. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records whether the page would have a legacy TLS warning (if the user were - in the appropriate field trial) when a download is initiated from the page - (*not* the legacy TLS status of the download URL itself). This is recorded - regardless of whether the warning is actually displayed. This histogram is - not recorded for downloads that are initiated in a new tab or window, as the - legacy TLS status of the initiating page cannot be tracked. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records whether the page would have a legacy TLS warning (if the user were - in the appropriate field trial) when submitting a form. This is recorded - whenever a form submission navigation begins. The recorded status is of the - page the form was submitted from, not the one that the form targets. - - - - - cthomp@chromium.org - estark@chromium.org - security-enamel@chromium.org - - Records whether the page would have a legacy TLS warning (if the user were - in the appropriate field trial) when the navigation to the page commits. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Tracks Page Info bubble actions along with whether the page would have a - legacy TLS warning (if the user were in the appropriate field trial). - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the reason the page visit ended (e.g., reload, tab closed, new - navigation, etc.) for page loads that committed. - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on an HTTPS URL that has - been marked dangerous or not secure (such as for malware or broken HTTPS). - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on a valid HTTPS URL that - has a security issue (e.g. mixed content). - - - - - - Removed 2018-01-31, split into ValidEV and ValidNonEV. - - estark@chromium.org - - Tracks Page Info bubble actions that take place on a valid HTTPS URL with no - security issues (e.g. no mixed content). - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on a valid HTTPS URL with no - security issues (e.g. no mixed content) and an Extended Validation - Certificate. - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on a valid HTTPS URL with no - security issues (e.g. no mixed content), but no Extended Validation - Certificate. - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on an HTTP URL that has been - marked dangerous (such as for malware). - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on an HTTP URL that does not - have an omnibox security indicator warning associated with it. - - - - - estark@chromium.org - - Tracks Page Info bubble actions that take place on an HTTP URL that has been - given a "Not secure" warning in the omnibox. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the amount of time the Page Info bubble is open before the user - closes it or takes an action which closes it. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the amount of time the Page Info bubble is open before the user - closes it, for cases where the user has performed an action inside it. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the amount of time the Page Info bubble is open before the user - closes it, for cases where the user performed no action inside it. - - - - - meacer@chromium.org - security-enamel@chromium.org - - Site engagement level of the URL of the top frame of the navigation when the - user modifies a password field on the page. Only recorded once per - navigation for the top frame. - - - - - meacer@chromium.org - security-enamel@chromium.org - - Site engagement level of the URL of the top frame of the navigation when the - user focuses on a password field on the page. Only recorded once per - navigation for the top frame. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records the Safety Tip status on a page that initiated a download (*not* the - Safety Tip status of the download URL itself). This is recorded regardless - of whether the Safety Tip UI is enabled or disabled. This histogram is not - recorded for downloads that are initiated in a new tab or window, as the - Safety Tip status of the initiating page cannot be tracked. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records the Safety Tip status of a page when submitting a form. This - histogram is recorded whenever a form submission navigation begins. The - recorded safety tip status is the status of the page the form was submitted - from, not the one that the form targets. Recorded regardless of whether the - Safety Tip UI is enabled or disabled. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records a user's interaction with a Safety Tip. Recorded every time a user - uses one of the Safety Tip's buttons or dismisses it explicitly. Can be - normalized against Security.SafetyTips.SafetyTipShown, filtered to users - with the feature enabled to show the UI. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user explicitly closed the bubble. This is recorded in addition to the more - specifc metric that indicates how the user dismissed the Safety Tip. - - - - - jdeblasio@chromium.org - estark@chromium.org - livvielin@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user explicitly closed the bubble with the close button. This is recorded in - addition to the base dismiss metric. - - - - - jdeblasio@chromium.org - estark@chromium.org - livvielin@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user explicitly closed the bubble with the esc key. This is recorded in - addition to the base dismiss metric. - - - - - jdeblasio@chromium.org - estark@chromium.org - livvielin@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user explicitly closed the bubble with the ignore button. This is recorded - in addition to the base dismiss metric. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user closed the bubble by heeding the call-to-action to leave the site. - - - - - jdeblasio@chromium.org - estark@chromium.org - - Records the amount of time a Safety Tip bubble is open, for cases where the - user did not dismiss or take action in the bubble. - - - - - estark@chromium.org - jdeblasio@chromium.org - - Tracks Page Info bubble actions along with the Safety Tip status of the - page. - - - - - jdeblasio@chromium.org - src/chrome/browser/reputation/OWNERS - - Records the Safety Tip status of a page after navigation commit or page - visibility change. This is the same as SafetyTipShown, but with additional - suffixes for clarity. - - - - - jdeblasio@chromium.org - livvielin@chromium.org - - Records the Safety Tip status of a page after navigation commit for a page - where the Safety Tip has previously been ignored. - - - - - jdeblasio@chromium.org - livvielin@chromium.org - - Records the Safety Tip status of a page after navigation commit or page - visibility change. - - - - - jdeblasio@chromium.org - src/chrome/browser/reputation/OWNERS - - TEMPORARY histogram that records the Safety Tip status of a page after - navigation commit or page visibility change. This is the same as - SafetyTipShown, but records *after* the flag is checked to evaluate the - impact of starts_active. - - - - - jdeblasio@chromium.org - meacer@chromium.org - - Records the Safety Tip status of a page after navigation commit, alongside - how the corresponding navigation was initiated. Only recorded on navigations - that were visible at commit time. - - - - - - - - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the high-water-mark of the number of reports in the SCT auditing - cache size over each browser session. Recorded when the SCT auditing cache - is destroyed (normally during browser shutdown, and potentially if the - network service crashes). - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records whether a report was deduplicated (i.e., the SCTs were already in - the cache) or not. Recorded on each new report seen by the SCT auditing - cache (i.e., on each connection using certificate transparency). - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records whether a report was sampled to be sent to Safe Browsing. Recorded - for each new report seen by the SCT auditing cache that was not - deduplicated. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the size of an SCT auditing report that will be sent to Safe - Browsing (i.e., was not deduplicated and was sampled). - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records whether sending an SCT auditing report succeeded or not. This is - recorded after we receive the headers from the server (or we stop due to a - connection error). - - - - - estark@chromium.org - - Records the security level of a page with a cryptographic scheme (e.g. - https). This histogram is recorded once at navigation commit time, and can - be called again for the same document if the security level changes - dynamically. Note that the security level can change very quickly after - commit time, for example if the page includes mixed content on load (which - can downgrade the security level). This histogram should be analyzed with - care because each recorded security level is not necessarily user-visible: - in particular, a page may commit as a secure level (SECURE, EV_SECURE, - SECURE_WITH_POLICY_INSTALLED_CERT) but get quickly downgraded to NONE if it - shows mixed content on load. Therefore the histogram values should be - regarded as an upper-bound on what the user actually sees for these security - levels. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the security level of the page that initiated a download (rather - than the security state of the connection to the download URL itself). The - recorded security level is the level of the page the download was initiated - from, not that of the download URL. This histogram is not recorded for - downloads that are initiated in a new tab or window, as the security level - of the initiating page cannot be tracked. - - - - - carlosil@chromium.org - cthomp@chromium.org - - Records the security level of a page when submitting a form. This histogram - is recorded whenever a form submission navigation begins. The recorded - security level is the level of the page the form was submitted from, not the - one that the form targets. - - - - - estark@chromium.org - livvielin@chromium.org - - Records the security level of a page when submitting a form on a top-frame - navigation with a non-cryptographic scheme. This histogram is recorded - whenever a form submission navigation begins. The recorded security level is - the level of the page the form was submitted from, not the one that the form - targets. - - - - - estark@chromium.org - livvielin@chromium.org - - Records the security level of a page on top-frame navigations with a - non-cryptographic scheme that are not form submissions. This histogram is - compared against Security.SecurityLevel.InsecureMainFrameFormSubmission. - - - - - estark@chromium.org - - Records the security level of a page with a non-cryptographic scheme (e.g. - http). This histogram is recorded once at navigation commit time, and can be - called again for the same document if the security level changes - dynamically. Note that the security level can change very quickly after - commit time, for example if the page includes a password field on load - (which can downgrade the security level). This histogram should be analyzed - with care because each recorded security level is not necessarily - user-visible: in particular, a page may commit as NONE or WARNING but get - quickly downgraded to WARNING or DANGEROUS, depending on field trial - configuration, if it shows a password field on load. Therefore the histogram - values should be regarded as an upper-bound on what the user actually sees - for the NONE and WARNING levels. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the security level of a page at the time the navigation commits. - Note that the security level of a page can change after commit time, so this - histogram should often be compared against - Security.SecurityLevel.OnComplete. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the security level of a page at the end of the page visit (i.e., - navigating away from the page, reloading the page, clicking a link, closing - the tab, etc.). Note that this security level can be different than the - initial security level of the page, so this histogram should often be - compared against Security.SecuritLevel.OnCommit. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - The final Site Engagement score (0 to 100) of a URL during a visit to a - page. Recorded when the user closes the page or initiates a new navigation. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - The change in Site Engagement score for a site between the page navigation - committing and the user closing the page or navigating away. Recorded when - the user closes the page or initiates a new navigation. - - The delta is logged as a linear count in [0, 100]. To use, convert back to - the original difference (in the range [-100,100]) by multiplying by 2 and - subtracting 100. - - - - - - Removed March 2019 in favor of Security.TimeOnPage2. - - cthomp@chromium.org - - Records the time spent on the page (the time that the page was in the - foreground from the start of the navigation to the page visit completing due - to a new navigation or the tab being closed). This aggregates all foreground - time over the entire visit (multiple times in the foreground are added - together). For pages that were never backgrounded, this histogram - (accidentally) collects 0 instead of the actual foreground time. - - - - - cthomp@chromium.org - security-enamel@chromium.org - - Records the time spent on the page (the time that the page was in the - foreground from the start of the navigation to the page visit completing due - to a new navigation or the tab being closed). This aggregates all foreground - time over the entire visit (multiple times in the foreground are added - together). - - - - - - Removed April 2020 as it is no longer used. - - mkwst@chromium.org - - Records the number of origins which will be treated as secure based on their - presence in the '--unsafely-treat-insecure-origin-as-secure' command-line - flag. - - - - - mkwst@chromium.org - arthursonzogni@chromium.org - - Record uses of the X-Frame-Options header when a page is loaded as an - iframe. - - - - - jeffreycohen@chromium.org - tgupta@chromium.org - Tracks the user flow for sending a tab for SendTabToSelf. - - - - jeffreycohen@chromium.org - sebsg@chromium.org - tgupta@chromium.org - - Record whether the user has clicked the item when it is shown. - - - - - - Removed 05/2020. - - jeffreycohen@chromium.org - sebsg@chromium.org - tgupta@chromium.org - - Record how many valid devices are shown when user trigger to see the device - list. - - - - - - Removed 05/2020. - - sebsg@chromium.org - jeffreycohen@chromium.org - tgupta@chromium.org - - The use of desktop notification for SendTabToSelf. - - These notifications are tied to a sync type so there is a distinction - between user initiated actions (Opened, Dismissed) and actions that are - initiated by changes to the sync model (Shown, DismissedRemotely). - - - - - - Removed 05/2020. - - jeffreycohen@chromium.org - sebsg@chromium.org - - The result of the add entry method when a tab is shared via SendTabToSelf - - - - - - Removed 05/2020. - - jeffreycohen@chromium.org - sebsg@chromium.org - - The result of the ApplySyncChanges method when a tab is shared via - SendTabToSelf - - - - - - Removed 05/2020. - - tgupta@chromium.org - - Whether or not the SendTabToSelf model was loaded in time to perform the - necessary update. - - - - - - Removed 05/2020. - - jeffreycohen@chromium.org - tgupta@chromium.org - - The number of entry that are sent to the SendTabToSelf NotificationHandler. - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from activating a sensor in the ISensor API, used in - the implementation of W3C sensors on Windows. This includes both errors and - successes (S_OK). - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from starting a sensor in the ISensor API, used in the - implementation of W3C sensors on Windows. This includes both errors and - successes (S_OK). - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from stopping a sensor in the ISensor API, used in the - implementation of W3C sensors on Windows. This includes both errors and - successes (S_OK). - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from activating a sensor in the - Windows.Devices.Sensors WinRT API, used in the implementation of W3C sensors - on Windows. This includes both errors and successes (S_OK). - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from starting a sensor in the Windows.Devices.Sensors - WinRT API, used in the implementation of W3C sensors on Windows. This - includes both errors and successes (S_OK). - - - - - - Removed in M82 after the WinRT backend experiment concluded. - - reillyg@chromium.org - wensh@microsoft.com - - The HRESULTs returned from stopping a sensor in the Windows.Devices.Sensors - WinRT API, used in the implementation of W3C sensors on Windows. This - includes both errors and successes (S_OK). - - - - - - Removed 02/2018. SequencedWorkerPool has been removed. - - gab@chromium.org - - How long it takes to wait for tasks that block shutdown to complete. - - - - - - Histogram wasn't even reported anymore when ownership was taken in 11/2015. - - gab@chromium.org - - How many pending tasks there are on each request for work from a worker - thread. - - - - - - Histogram wasn't even reported anymore when ownership was taken in 11/2015. - - gab@chromium.org - How many tasks we skip over to find the next runnable task. - - - - alemate@chromium.org - - Records result of fetching and parsing OEM customization manifest. See - ServicesCustomizationDocument class for more info. Used only on Chrome OS. - - - - - nhiroki@chromium.org - jinho.bang@samsung.com - - The time taken between dispatching an AbortPaymentEvent to a Service Worker - and receiving a message that it finished handling the event. Includes the - time for the waitUntil() promise to settle. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - horo@chromium.org - - The time taken for the browser to find and possibly start an active worker - to dispatch a FetchEvent for a main frame resource request. BEWARE: This - metric includes the time taken for redirects. It starts when the URLRequest - is created, and ends when the worker is ready. For context, a FetchEvent can - only be dispatched to an ACTIVATED worker that is running (it has been - successfully started). The measurements starts when the browser process - receives the request. The browser then finds the worker appropriate for this - request (if there is none, this metric is not recorded). If that worker is - already started, the browser process can send the request to it, so the - measurement ends quickly. Otherwise the browser process has to start the - worker and the measurement ends when the worker is successfully started (we - do not include in the time it takes for the worker to become ACTIVATED). The - metric is not recorded in the following situations: 1) The worker was in - state INSTALLED or ACTIVATING, and the browser had to wait for it to become - ACTIVATED. This is to avoid including the time to execute the activate event - handlers in the worker's script. 2) The worker was started for the fetch AND - DevTools was attached during startup. This is intended to avoid including - the time for debugging. 3) The request is for New Tab Page. This is because - it tends to dominate the stats and makes the results largely skewed. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - - Removed June 2019. - - falken@chromium.org - - The type of preparation needed for the browser to find and possibly start an - active worker to dispatch a FetchEvent for a main frame resource request. - See details at ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. - The suffixed histograms for .Time record the time required for each type. - - - - - shimazu@chromium.org - chrome-worker@google.com - - Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for - waitUntil() promise to settle. - - - - - - Removed 2015-05 in favor of ServiceWorker.ActivateEvent.Time. - - shimazu@chromium.org - - Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for - waitUntil() promise to settle. - - - - - falken@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - The result of dispatching the activate event to the worker. This is recorded - to both ServiceWorker.ActivateEventStatus and whichever of - ServiceWorker.ActivateEventStatus_InShutdown - ServiceWorker.ActivateEventStatus_NotInShutdown is appropriate. (InShutdown - means the context was null or ServiceWorkerProcessManger::Shutdown was - called.) - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - The time taken between dispatching a BackgroundFetchAbortEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - The time taken between dispatching a BackgroundFetchClickEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - - Removed 08/2018, and renamed to BackgroundFetchSuccessEvent. See - ServiceWorker.BackgroundFetchSuccessEvent.Time instead. - - peter@chromium.org - - The time taken between dispatching a BackgroundFetchedEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - The time taken between dispatching a BackgroundFetchFailEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - nator@chromium.org - peter@chromium.org - rayankans@chromium.org - - The time taken between dispatching a BackgroundFetchSuccessEvent to a - Service Worker and receiving a message that it finished handling the event. - Includes the time for the waitUntil() promise to settle. This event is sent - when the background fetch succeeds. - - - - - nator@chromium.org - rayankans@chromium.org - - The time taken between dispatching a SyncEvent to a Service Worker and - receiving a message that it finished handling the event. Includes the time - for the waitUntil() promise to settle. - - - - - horo@chromium.org - wanderview@chromium.org - - The length of cached metadata of scripts which are stored to the - CacheStorage by the installing service worker. - - - - - horo@chromium.org - wanderview@chromium.org - - The total length of cached metadata of scripts which are stored to the - CacheStorage by the installing service worker. - - - - - horo@chromium.org - wanderview@chromium.org - - The counts of scripts which are stored to the CacheStorage by the installing - service worker. - - - - - horo@chromium.org - wanderview@chromium.org - - The length of scripts which are stored to the CacheStorage by the installing - service worker. - - - - - horo@chromium.org - wanderview@chromium.org - - The total length of scripts which are stored to the CacheStorage by the - installing service worker. - - - - - nhiroki@chromium.org - jinho.bang@samsung.com - - The time taken between dispatching an CanMakePaymentEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - rayankans@chromium.org - platform-capabilities@chromium.org - - The time taken between dispatching a ContentDeleteEvent to a Service Worker - and receiving a message that it finished handling the event. Includes the - time for the waitUntil() promise to settle. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - The result of ServiceWorkerContextRequestHandler handling a request for a - service worker script. The histogram is suffixed to distinguish new vs - installed workers and main vs imported scripts. - - Note that since M64, this no longer includes most script loads because those - are handled by ServiceWorkerInstalledScriptsManager, which doesn't record - this histogram. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - pwnall@chromium.org - - The time taken between dispatching a CookieChangeEvent to a Service Worker - and receiving a message that it finished handling the event. Includes the - time for the waitUntil() promise to settle. - - - - - bashi@chromium.org - nhiroki@chromium.org - - Records result of destroy database operations in ServiceWorkerDatabase. - - - - - - - nhiroki@chromium.org - - Records result of opening a database for ServiceWorkerDatabase. - - - - - bashi@chromium.org - nhiroki@chromium.org - Records result of read operations in ServiceWorkerDatabase. - - - - bashi@chromium.org - nhiroki@chromium.org - - Records result of write operations in ServiceWorkerDatabase. - - - - - bashi@chromium.org - nhiroki@chromium.org - - Records result of opening a disk cache for ServiceWorkerDiskCache. - - - - - bashi@chromium.org - nhiroki@chromium.org - - Records result of reading response from ServiceWorkerDiskCache. - - - - - bashi@chromium.org - nhiroki@chromium.org - - Records result of writing response into ServiceWorkerDiskCache. This is not - recorded when response has no body. Note that this is recorded on every - write operation, and can there can be multiple write operations for the same - response if it is large enough. - - - - - - Removed because the migrator was removed as of 12/2015. - - nhiroki@chromium.org - - Records result of ServiceWorkerDiskCacheMigrator::Start that migrates - resources in BlockFile backend to Simple backend. - - - - - - Removed because the migrator was removed as of 12/2015. - - nhiroki@chromium.org - - Execution time of ServiceWorkerDiskCache migration from BlockFile to Simple. - - - - - - Removed because the migrator was removed as of 12/2015. - - nhiroki@chromium.org - - The counts of resources migrated by ServiceWorkerDiskCacheMigrator. This - includes the main script and imported scripts. - - - - - panicker@chromium.org - - Records when StartWorker is received on the renderer. This is used to - surface discrepancy between StartWorker being sent on the browser side and - not getting received by renderer. - EmbeddedWorkerInstance.Start.TimeToSendStartWorker should be used as a - baseline. TODO(panicker): This should be removed after investigation of - crbug/790903, potentially in M68. - - - - - - Removed Oct 2018 (M72) - - horo@chromium.org - - The time taken between sending an event IPC from the browser process to a - Service Worker and executing the event handler in the Service Worker. - - For subresource fetch events (_FETCH_SUB_RESOURCE suffix) When NetS13nSW - (https://crbug.com/715640) is enabled, this is the time between sending a - DispatchFetchEvent message from the main thread and executing the event - handler in the Service Worker. - - - - - - Removed July 2018 (M69) - - kinuko@chromium.org - - Records the proportion of (non foreign) fetch events that are handled - compared to the number of events that are fired for a ServiceWorker. - Recorded each time the ServiceWorker is stopped when at least one event was - fired. - - - - - - Removed July 2018 (M69) - - mek@chromium.org - - Records the proportion of foreign fetch events that are handled compared to - the number of events that are fired for a ServiceWorker. Recorded each time - the ServiceWorker is stopped when at least one event was fired. - - - - - nhiroki@chromium.org - chrome-worker@google.com - - The time taken between dispatching an ExtendableMessageEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - lazyboy@chromium.org - - The duration an external request spent to keep a service worker alive. - Currently, extension service workers use external requests to keep the - worker alive during the time the worker requests an extension API. - - - - - falken@chromium.org - chrome-worker@google.com - - The time taken between dispatching a FetchEvent to a Service Worker and - receiving a fallback-to-network reply. - - - - - falken@chromium.org - chrome-worker@google.com - - The time taken between dispatching a FetchEvent to a Service Worker and - receiving a response. Includes the time for the respondWith() promise to - settle. - - - - - falken@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - The result of dispatching a fetch event to a Service Worker for a main - resource request (i.e., a request for a navigation or a shared worker). - - - - - asamidoi@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - The time that a fetch event was queued. The start time is when the event is - created on the service worker thread and added to the - ServiceWorkerEventQueue. The end time is when the event is dequeued and the - event handler starts to execute. - - - - - falken@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - The result of dispatching a fetch event to a Service Worker for a - subresource request (i.e., not a navigation or a shared worker request). - - - - - - Removed on 2015-07-13; please use ServiceWorker.FetchEvent.HasResponse.Time - or ServiceWorker.FetchEvent.Fallback.Time. - - shimazu@chromium.org - - Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for - the respondWith() promise to settle. - - - - - shimazu@chromium.org - chrome-worker@google.com - - The time taken between dispatching a FetchEvent to a Service Worker and - finishing the FetchEvent. Includes the time for the waitUntil() promise to - settle. If there is no waitUntil promise, this will be almost the same with - HasResponse.Time or Fallback.Time. - - - - - - Removed 2015-05 in favor of ServiceWorker.FetchEvent.Time. - - shimazu@chromium.org - - Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for - the respondWith() promise to settle. - - - - - wanderview@chromium.org - - Measures how long the service worker thread is blocked creating a - mojo::DataPipe during FetchEvent.respondWith() processing. - - - - - - Removed April 2018. - - mek@chromium.org - - The number of origins a particular service worker with foreign fetch - registrations will intercept fetches from. A value of zero indicates that - the foreign fetch service worker intercepts requests from any origin. - Recorded at the end of a successful install event, if the service worker - registered for foreign fetch. A service worker that registers for foreign - fetch must always intercept fetches from at least one origin or intercept - fetches from all origins. - - - - - - Removed April 2018. - - mek@chromium.org - - The number of foreign fetch scopes a particular service worker registered - for. Recorded at the end of every successful install event. A value of zero - indicates that the service worker did not register for foreign fetch. - - - - - - Removed 2018 - - mek@chromium.org - - The time taken between dispatching a ForeignFetchEvent to a Service Worker - and receiving a fallback-to-network reply. Includes the time for the - waitUntil() promise to settle, if any. - - - - - - Removed 2018 - - mek@chromium.org - - The time taken between dispatching a ForeignFetchEvent to a Service Worker - and receiving a response. Includes the time for the respondWith() promise to - settle. - - - - - - Removed 2018 - - shimazu@chromium.org - - The time taken between dispatching a ForeignFetchEvent to a Service Worker - and finishing the ForeignFetch. Includes the time for the waitUntil() - promise to settle. If there is no waitUntil promise, this will be almost the - same with HasResponse.Time or Fallback.Time. - - - - - bashi@chromium.org - chrome-worker@google.com - - Execution time of ServiceWorkerContextWrapper::GetAllOriginsInfo(). - - - - - shimazu@chromium.org - chrome-worker@google.com - - The time taken between dispatching an InstallEvent to a Service Worker and - receiving a message that it finished handling the event. Includes the time - for the waitUntil() promise to settle. - - - - - - Removed 2015-05 in favor of ServiceWorker.InstallEvent.Time. - - shimazu@chromium.org - - Execution time of ServiceWorkerGlobalScope.oninstall. Includes the time for - the waitUntil() promise to settle. - - - - - falken@chromium.org - chrome-worker@google.com - The result of dispatching the install event to the worker. - - - - bashi@chromium.org - chrome-worker@google.com - - The method that the user takes to arrive at - chrome://serviceworker-internals, based on the query string. Specifically, - it logs if a user accessed it through the DevTools link in the Application - Panel, or not. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) renderer process sends an IPC message to notify that - a resource loading request needs to be fall back to network, to (b) browser - process received the IPC. Recorded when no fetch event handler provided a - response to the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) renderer process sends an IPC message to notify that - a promise of respondWith() is settled, to (b) browser process received the - IPC message. Recorded when a fetch event handler handled the request and - provided a response to the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) a fetch event is dispatched, to (b) respondWith() is - settled for the fetch event, or fetch event dispatch is finished without - respondWith() being called. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - - Removed 2018-11 in favor of - ServiceWorker.LoadTiming.MainFrame.MainResource.ForwardServiceWorkerToWorkerReady2. - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) a resource loading request is routed to service - worker path, to (b) a service worker is ready to handle the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) a resource loading request is routed to service - worker path, to (b) a service worker is ready to handle the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - - Removed 2018-11 in favor of - ServiceWorker.LoadTiming.MainFrame.MainResource.ResponseReceivedToCompleted2. - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) response headers from service worker are received, - to (b) reading response body is completed. Recorded when a fetch event - handler handled the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) response headers from service worker are received, - to (b) reading response body is completed. Recorded when a fetch event - handler handled the request. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) the start of a navigation request, to (b) the - request is forwarded to a service worker code path. This includes looking up - a service worker registration and throttling. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) browser process sends an IPC message to dispatch a - fetch event, to (b) a renderer process received the IPC message and is about - to dispatch a fetch event. - - Recorded for each navigation request (including redirects) where there is a - fetch event handler and the fetch event was successfully dispatched to the - service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) service worker sends a mojo message to notify that a - resource loading request needs to be fall back to network, to (b) the mojo - message is received on the other side of mojo endpoint (a background thread - executing subresource loading). Recorded when no fetch event handler - provided a response to the request. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) service worker sends a mojo message to notify that a - promise of respondWith() is settled, to (b) the mojo message is received on - the other side of mojo endpoint (a background thread executing subresource - loading). Recorded when a fetch event handler handled the request and - provided a response to the request. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) a subresource request is routed to the URLLoader (on - a background thread) for service worker controlled loads starts handling a - subresource request, to (b) a service worker is ready to handle the request. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - - Removed 2018-12 in favor of - ServiceWorker.LoadTiming.Subresource.ResponseReceivedToCompleted2. - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) response headers from service worker are received, - to (b) reading response body is completed. Only recorded when a fetch event - handler handled the request. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) response headers from service worker are received, - to (b) reading response body is completed. Only recorded when a fetch event - handler handled the request. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - bashi@chromium.org - chrome-worker@google.com - - The time taken from (a) a fetch event is dispatched, to (b) respondWith() is - settled for the fetch event, or fetch event dispatch is finished without - respondWith() being called. - - Recorded for each subresource request where there is a fetch event handler - and the fetch event was successfully dispatched to the service worker. - - - - - shimazu@chromium.org - chrome-worker@google.com - - The time taken from (a) a resource loading request is routed to service - worker path, to (b) existance of a registered service worker is looked up. - This metric only cares about looking up a registration for navigation. This - doesn't include look-ups for updating a service worker. - - Please refer to the suffixed histograms for each of the cases where a - registration is found, not found, and an error happens. - - - - - falken@chromium.org - chrome-worker@google.com - - Counts main frame page loads controlled by a service worker. - - - - - - Removed 2018-01 in favor of PageLoad.Clients.ServiceWorker.PageTransition. - - horo@chromium.org - - The transition type for main frame page loads controlled by a service - worker. - - - - - - Removed 2018-01. - - horo@chromium.org - - Total length of the server redirects during main frame page loads controlled - by a service worker. - - - - - - Removed 2018-11, see https://crbug.com/902100 - - falken@chromium.org - chrome-worker@google.com - - Describes whether a main resource request (i.e., a request for a main frame, - subframe, or shared worker) was routed to service worker or network and why. - The purpose is to debug why ServicifiedServiceWorker has a lower count of - ServiceWorker.MainResource.FetchEvent.Status than the control: - https://crbug.com/866335. - - Recorded for every main resource request that is seen by - ServiceWorkerControlleeRequestHandler (usually means all http(s) requests). - If redirects occur, it is recorded for each redirect. - - - - - - Removed 2016-04 in favor of ServiceWorker.ExtendableMessageEvent.Time. - - shimazu@chromium.org - Execution time of ServiceWorkerGlobalScope.onmessage. - - - - - Removed 2015-05 in favor of ServiceWorker.MessageEvent.Time. - - shimazu@chromium.org - Execution time of ServiceWorkerGlobalScope.onmessage. - - - - - This experiment was turned down, see https://crbug.com/616502. - - horo@chromium.org - - The precision of the speculative launch of Service Workers for navigation - hints. Recorded when the worker is stopped. If there was no main/sub frame - fetch event fired on the worker, this value is false. This means that the - speculative launch wasn't helpful. - - - - - - Removed June 2017 in favor of ServiceWorker.NavPreload.ConcurrentTime, see - https://crbug.com/728035. - - falken@chromium.org - - The duration of time when both (1) a service worker is being found and - possibly started up, (2) the navigation preload request is in-flight. The - measurement ends once either the worker is prepared, or the navigation - preload response is received (OnReceiveResponse() is called). This is a - rough estimate of the performance win of using navigation preload, ignoring - concurrency overhead. This histogram is recorded when a navigation preload - response is succesfully forwarded to the service worker's fetch event, with - the same restrictions as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - additionally recorded to the appropriate suffixed histograms. - - - - - - Removed June 2017 in favor of ServiceWorker.NavPreload.FinishedFirst, see - https://crbug.com/728035. - - falken@chromium.org - - Whether the navigation preload response arrived before the activated and - running service worker was prepared. This histogram is recorded when a - navigation preload response is succesfully forwarded to the service worker's - fetch event, with the same restrictions as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - additionally recorded to the appropriate suffixed histograms. - - - - - - Expired June 2020. - - horo@chromium.org - - The size of Service-Worker-Navigation-Preload header when the navigation - preload request is to be sent. The default value of the header is - "true", so the default size is 4. - - - - - - Removed June 2017. No replacement exists. See https://crbug.com/728035. - - falken@chromium.org - - This is recorded in the case where the activated and running service worker - was prepared before the navigation preload response arrived. It is the - remaining time it took to receive the response after the worker was - prepared. - - This histogram is recorded when a navigation preload response is succesfully - forwarded to the service worker's fetch event (for the case mentioned - above), with the same restrictions as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - additionally recorded to the appropriate suffixed histograms. - - - - - - Removed June 2017 in favor of ServiceWorker.NavPreload.ResponseTime. See - https://crbug.com/728035. - - falken@chromium.org - - The time taken for the navigation preload response to start, i.e., when - OnReceiveResponse() is called. This histogram is recorded when a navigation - preload response is successfully forwarded to the service worker's fetch - event, with the same restrictions as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - additionally recorded to the appropriate suffixed histograms. - - - - - - Removed June 2017 in favor of ServiceWorker.NavPreload.WorkerWaitTime. See - https://crbug.com/728035. - - falken@chromium.org - - This is recorded in the case where the navigation preload response arrived - before the activated and running service worker was prepared. It is the - remaining time it took to prepare the worker after the response arrived. - - This histogram is recorded when a navigation preload response is succesfully - forwarded to the service worker's fetch event (for the case mentioned - above), with the same restrictions as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - additionally recorded to the appropriate suffixed histograms. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - The duration of time when both (1) a service worker is being found and - possibly started up, (2) the navigation preload request is in-flight. The - measurement ends once either the worker is prepared, or the navigation - preload response is received (OnReceiveResponse() is called). This is a - rough estimate of the performance win of using navigation preload, ignoring - concurrency overhead. This histogram is recorded when a navigation preload - response is succesfully forwarded to the service worker's fetch event, with - the same restrictions enumerated 1) through 3) for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - only recorded to the appropriate suffixed histograms. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - Whether the navigation preload response arrived before the activated and - running service worker was prepared. This histogram is recorded when a - navigation preload response is succesfully forwarded to the service worker's - fetch event, with the same restrictions numbered 1) through 3) for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - only recorded to the appropriate suffixed histograms. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - The time taken for the navigation preload response to start, i.e., when - OnReceiveResponse() is called. This histogram is recorded when a navigation - preload response is successfully forwarded to the service worker's fetch - event, with the same restrictions numbered 1) through 3) for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - only recorded to the appropriate suffixed histograms. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - The type of preparation needed for the browser to find and possibly start an - active worker to dispatch a FetchEvent for a main frame resource request, - when navigation preload also occurred. - - This histogram is recorded when a navigation preload response is succesfully - forwarded to the service worker's fetch event (for the case mentioned - above), with the same restrictions numbered 1) through 3) as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - only recorded to the appropriate suffixed histograms. - - This is similar to - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Type_NavigationPreloadEnabled. - The difference is ServiceWorker.NavPreload.WorkerPreparationType gets logged - if the navigation preload successfully occurred, at the same time as the - other ServiceWorker.NavPreload.* metrics so is more safely comparable to - them. We could deprecate the Type_NavigationPreloadEnabled histogram if it - turns out there is no significant difference. - - It will be removed after NetS13nSW ships. https://crbug.com/715640 - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - This is recorded in the case where the navigation preload response arrived - before the activated and running service worker was prepared. It is the - remaining time it took to prepare the worker after the response arrived. - - This histogram is recorded when a navigation preload response is succesfully - forwarded to the service worker's fetch event (for the case mentioned - above), with the same restrictions numbered 1) through 3) as for - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is - only recorded to the appropriate suffixed histograms. - - - - - peter@chromium.org - knollr@chromium.org - - The time taken between dispatching a NotificationClickEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - - Removed 2015-05 in favor of ServiceWorker.NotificationClickEvent.Time. - - peter@chromium.org - - Execution time of ServiceWorkerGlobalScope.onnotificationclick. - - - - - nsatragno@chromium.org - peter@chromium.org - - The time taken between dispatching a NotificationCloseEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - falken@chromium.org - chrome-worker@google.com - Counts page loads controlled by a service worker. - - - - nhiroki@chromium.org - jinho.bang@samsung.com - - The time taken between dispatching an PaymentRequestEvent to a Service - Worker and receiving a message that it finished handling the event. Includes - the time for the waitUntil() promise to settle. - - - - - nator@chromium.org - platform-capabilities@chromium.org - - The time taken between dispatching a PeriodicSyncEvent to a Service Worker - and receiving a message that it finished handling the event. Includes the - time for the waitUntil() promise to settle. - - - - - peter@chromium.org - - The time taken between dispatching a PushEvent to a Service Worker and - receiving a message that it finished handling the event. Includes the time - for the waitUntil() promise to settle. - - - - - - Removed 2015-05 in favor of ServiceWorker.PushEvent.Time. - - peter@chromium.org - Execution time of ServiceWorkerGlobalScope.onpush. - - - - peter@chromium.org - rayankans@chromium.org - knollr@chromium.org - viviy@google.com - - The time taken between dispatching a PushSubscriptionChangeEvent to a - Service Worker and receiving a message that it finished handling the event. - Includes the time for the waitUntil() promise to settle. The event is - dispatched and finishes in PushMessagingRouter::FireSubscriptionChangeEvent. - - - - - falken@chromium.org - chrome-worker@google.com - - The number of origins that have a service worker registration. Recorded near - browser startup, when the service worker storage system is initialized. - - - - - - No longer needed as found the cause of stability issue to be number of - registrations rather than size of registrations. Removed in July 2020. - - nidhijaju@google.com - bashi@chromium.org - chrome-worker@google.com - - Number of service worker registrations to be added in - ServiceWorkerRegistry::DidGetAllRegistrations(). - - - - - - No longer needed as found the cause of stability issue to be number of - registrations rather than size of registrations. Removed in July 2020. - - nidhijaju@google.com - bashi@chromium.org - chrome-worker@google.com - - The length of the scope url in the ServiceWorkerRegistrationInfo is measured - for each service worker registration to give a better idea of the data - structure as a whole. This metric is collected in - ServiceWorkerRegistration::GetInfo(). - - - - - - Removed June 2019. - - falken@chromium.org - - The number of Service Worker request timeouts, by request type. - - - - - falken@chromium.org - - The amount of time a service worker ran for (wall time). Starts recording - when the service worker finished starting, and stops when the service worker - finished stopping. Not recorded if DevTools was attached to the service - worker at some point while it was running. - - - - - falken@chromium.org - chrome-worker@google.com - - The length of cached metadata of Service Worker scripts. Logged on each load - of Service Worker script only when the cached metadata is available. It - doesn't include the size of imported scripts. This histogram is only - recorded for classic workers, not module workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The total length of cached metadata of Service Worker scripts. Logged on - each start of Service Worker only when the cached metadata is available. It - includes the main script and imported scripts. This histogram is only - recorded for classic workers, not module workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The counts of scripts per Service Worker. Logged on each start of Service - Worker. It includes the main script and imported scripts. This histogram is - only recorded for classic workers, not module workers. - - - - - - Removed June 2018 (M69). This was recorded as 100% success since service - worker script streaming launched in M64, since load failures didn't reach - this UMA. When there is an error reading the script from storage, it's - typically recorded as a start worker failure under - SERVICE_WORKER_ERROR_DISK_CACHE. - - falken@chromium.org - - Whether loading the service worker script succeeded. Only recorded for - installed service workers. Recorded by the browser process when reported - back by the renderer during worker startup. - - - - - falken@chromium.org - chrome-worker@google.com - - The length of Service Worker scripts. Logged on each load of Service Worker - script. It doesn't include the size of imported scripts. This histogram is - only recorded for classic workers, not module workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The total length of Service Worker scripts. Logged on each start of Service - Worker. It includes the main script and imported scripts. This histogram is - only recorded for classic workers, not module workers. - - - - - falken@chromium.org - - The result of trying to send the IPC message to a renderer process telling - it to stop an embedded worker. Recorded in EmbeddedWorkerInstance::Stop. - This was previously recorded for both the IPC and Mojo service worker - implementations, but as of Jan 2017, this is only recorded for the IPC - implementation. This histogram will be removed after the IPC implementation - is removed. - - - - - falken@chromium.org - chrome-worker@google.com - - The result of starting a service worker for a navigation hint. - - - - - - Removed June 2019. - - horo@chromium.org - - The precision of the speculative launch of Service Workers for navigation - hints. Recorded when the worker is stopped. True if a fetch event for a - main/sub frame navigation was fired on the worker before it stopped; - otherwise, false. False means the speculative launch wasn't helpful. - - - - - - Removed June 2019. - - falken@chromium.org - - The result of trying to start a Service Worker that has not yet installed. - See also ServiceWorker.StartWorker.Status for installed workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The time taken to start a Service Worker that has not yet installed, from - process allocation to ACK of started from the renderer (which occurs after - script execution). This may include script download time. The metric is not - recorded if DevTools was ever attached to the Service Worker during startup. - See also ServiceWorker.StartWorker.Time for installed workers. - - - - - kinuko@chromium.org - - The sum of all the times spent posting tasks between the UI and IO threads - during ServiceWorker startup. Recorded on a successful startup and when - DevTools was not attached. - - Note: This metric drops reports on clients with low-resolution clocks, which - means these reports will be biased against a portion of the population on - Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. - - Also note that this one's recorded slightly different from others as it's - recorded even if the inter-process timings were inconsistent (see - ServiceWorker.StartTiming.ClockConsistency). - - - - - falken@chromium.org - shimazu@chromium.org - - Recorded on each successful service worker startup. - ServiceWorker.StartTiming.* uses timing data from both the renderer process - and browser process. This histogram describes whether the clocks are known - to be accurate and consistent accross processes, and whether the actual - timing data for this worker startup was consistent, i.e., TimeTicks did not - go backwards. - - If the clocks and timing were inconsistent, ServiceWorker.StartTiming.* - metrics (other than this one) are not recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken to start a service worker that is already installed, from - start of the start sequence (finding a renderer) to ACK of started from the - renderer (which occurs after script execution). The metric is not recorded - if DevTools was ever attached to the Service Worker during startup. It does - not include time, if any, waiting for the service worker to finish stopping - before asking it to start, if that occurred. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the renderer receiving the start worker IPC message, - to (b) initial JavaScript evaluation starting on the worker thread. Recorded - when ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) initial JavaScript evaluation finishing on the - worker thread, to (b) the browser receiving the worker started IPC message - (the final step of worker startup). Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) initial JavaScript evaluation starting on the worker - thread, to (b) initial JavaScript evaluation finishing on the worker thread. - Recorded when ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the browser sending the start worker IPC message, to - (b) the renderer receiving the start worker IPC message. Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the start of service worker startup, to (b) the - renderer receiving the start worker IPC message. Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the start of service worker startup, to (b) initial - JavaScript evaluation finishing on the worker thread. Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the start of service worker startup, to (b) initial - JavaScript evaluation starting on the worker thread. Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - shimazu@chromium.org - - The time taken from (a) the start of service worker startup, to (b) the - browser sending the start worker IPC message. Recorded when - ServiceWorker.StartTiming.Duration is recorded. - - - - - falken@chromium.org - chrome-worker@google.com - - The result of trying to start a service worker after it has failed - consecutively. Recorded only for installed workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The number of consecutive startup failures of a service worker. Recorded - each time the service worker failed (so there is double counting: failing - twice results in 1 and 2 being logged). Only for installed workers. - - - - - falken@chromium.org - chrome-worker@google.com - - When a worker startup succeeded after failing, the number of times the - worker had consecutively failed. Recorded only for installed workers. - - - - - - Removed from code in July 2019 since ServiceWorkerScriptStreaming - successfully launched. - - shimazu@chromium.org - - The result of sending installed scripts over - ServiceWorkerInstalledScriptsSender. This is recorded after every start - worker attempt that sent the scripts through - ServiceWorkerInstalledScriptsSender. - - - - - falken@chromium.org - chrome-worker@google.com - - The purpose for starting up a service worker. Recorded only for installed - workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The result of trying to start a Service Worker that is already installed. - See also ServiceWorker.StartNewWorker.Status for new workers. See also - ServiceWorker.StartWorker.StatusByPurpose_* for the breakdown by event type. - - - - - falken@chromium.org - chrome-worker@google.com - - The result of trying to start a service worker for a particular event type - (see ServiceWorker.StartWorker.Status for the total). Only recorded for - installed workers. For event type: - - - - - falken@chromium.org - chrome-worker@google.com - - The time taken to start a Service Worker that is already installed, from - process allocation to ACK of started from the renderer (which occurs after - script execution). The metric is not recorded if DevTools was ever attached - to the Service Worker during startup. See also - ServiceWorker.StartNewWorker.Time for new workers. - - - - - falken@chromium.org - chrome-worker@google.com - - Records the start purpose for a service worker that timed out while starting - up. Recorded only for installed workers. - - - - - falken@chromium.org - chrome-worker@google.com - - The phase the EmbeddedWorker was in when ServiceWorker startup timed out. - - - - - - Removed from code in Oct 2015, replaced with ServiceWorker.WorkerStopped. - - falken@chromium.org - - The result of trying to stop a Service Worker. Recorded only for installed - Service Workers that succesfully stopped or were detected as stalling. If a - worker stalled and later stopped, it will be recorded as both STALLED and - STALLED_THEN_STOPPED. - - - - - falken@chromium.org - The time taken to stop a Service Worker. - - - - bashi@chromium.org - chrome-worker@google.com - - Records result of storage recovery operations in ServiceWorkerStorage. - - - - - - Removed because the migrator was removed as of 12/2015. - - nhiroki@chromium.org - - Records the final result of diskcache migration in ServiceWorkerStorage. - ServiceWorker.DiskCacheMigrator.MigrationResult records more detailed status - of migration operations. - - - - - nhiroki@chromium.org - - Records successes and failures of purging a stale resource in - ServiceWorkerStorage. - - - - - wanderview@chromium.org - - The time between when the ServiceWorkerSubresourceLoader receives a Response - and when it notifies the loader's client that the body has started loading. - This is different from SubresourceStartBlobReadingDelay in that notifying - the client about the Response may take place some time later than when the - blob body reading begins. This will be triggered for every successful - subresource load handled by a ServiceWorker with servification enabled. - - - - - - Removed in M77. - - wanderview@chromium.org - - The time between when the ServiceWorkerSubresourceLoader receives a Response - with a blob body and when the main blob data starts to get read. This will - be triggered for every successful subresource load handled by a - ServiceWorker with ServiceWorker servification enabled. - - - - - - Removed in June 2017. - - falken@chromium.org - - The time taken in the renderer process between the main thread asking the - worker thread to terminate and getting ACK that it terminated. - - - - - - Removed in June 2017. - - falken@chromium.org - - Called at the beginning of each ServiceWorkerVersion::Dispatch*Event - function: the time elapsed since idle. Generally this is the time between - one event ending and one event starting, if the worker remained running in - the interim. - - - - - - Removed 2015-06 in favor of ServiceWorker.EventHandledStatus*. - - kinuko@chromium.org - - Records the ratio of unhandled events to all events that are dispatched to - each ServiceWorker. Recorded when each ServiceWorkerVersion is destructed. - - - - - - Removed 2020-07 because we could confirm byte-for-byte update checking for - imported scripts works. - - shimazu@chromium.org - - Records the result of byte-for-byte update checking. If it's not OK, it - means that script comparison doesn't work well. Recorded only when - ServiceWorkerImportedScriptUpdateCheck is enabled. - - - - - - Removed 2020-07 because we could confirm byte-for-byte update checking for - imported scripts works. - - shimazu@chromium.org - - Records the result of byte-for-byte update checking. Recorded only when - ServiceWorkerImportedScriptUpdateCheck is enabled and - ServiceWorker.UpdateCheck.Result is OK. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - horo@chromium.org - - Records the the mode of request that was fallbacked to the network by the - Service Worker. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - Records the result of a main resource request forwarded to a Service Worker. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - Records the error provided when the renderer returns a response with status - code zero to a main resource request forwarded to a Service Worker (i.e., - ServiceWorker.URLRequestJob.MainResource.Result was - REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO). - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - Records the result of a subresource request forwarded to a Service Worker. - - - - - - No longer recorded since NetS13nSW shipped on Dec 2018. - - falken@chromium.org - - Records the error provided when the renderer returns a response with status - code zero to a subresource request forwarded to a Service Worker (i.e., - ServiceWorker.URLRequestJob.Subresource.Result was - REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO). - - - - - - No longer needed as found the cause of stability issue to be number of - registrations rather than size of registrations. Removed in July 2020. - - nidhijaju@google.com - bashi@chromium.org - chrome-worker@google.com - - Number of clients associated with each service worker version, for better - estimation of the size of ServiceWorkerRegistrationInfo. This metric is - collected in ServiceWorkerVersion::GetInfo(), and clients for all versions - (active, waiting, and installing) are counted for now. - - - - - - No longer needed as found the cause of stability issue to be number of - registrations rather than size of registrations. Removed in July 2020. - - nidhijaju@google.com - bashi@chromium.org - chrome-worker@google.com - - The length of the script url in ServiceWorkerVersionInfo is measured for - each service worker version to give a better idea of the memory size of - ServiceWorkerRegistrationInfo as a whole. This metric is collected in - ServiceWorkerVersion::GetInfo(). - - - - - falken@chromium.org - - True if a message from the renderer intended for a browser-side embedded - worker instance found its recipient. False if the instance did not exist - when the message was received (e.g., it was a detached worker). Recorded in - EmbeddedWorkerRegistry::GetWorkerForMessage. - - - - - falken@chromium.org - chrome-worker@google.com - - The mechanism by which a service worker entered running status STOPPED. - - - - - wanderview@chromium.org - dmurph@chromium.org - chrome-owp-storage@google.com - - The time to perform operations on the Cache object in the ServiceWorker - Cache API. - - - - - - This histogram was removed in M77. - - nhiroki@chromium.org - - Records the response type to be added in the Cache by Cache.add()/addAll(). - - - - - jkarlin@chromium.org - - Records the response type to be added in the Cache by all operations that - write to the cache. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The time to perform a 'match' operation on a given Cache when that cache is - known to be fully initialized. This includes measurements for hits, misses, - and errors. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The time to perform a 'match' operation on a given Cache when the operation - was initiated from a service worker currently processing a FetchEvent with a - matching request URL. This includes measurements for hits, misses, and - errors. - - - - - dmurph@chromium.org - wanderview@chromium.org - chrome-owp-storage@google.com - - The time to perform operations on the CacheStorage object in the - ServiceWorker Cache API. - - - - - jkarlin@chromium.org - - Whether a new ServiceWorkerCacheStorage and its directory were successfully - created on disk. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - Whether the origin provided in the - DidGenerateCacheableMetadataInCacheStorage message is allowed for the given - renderer process. This message is sent when the renderer has generated code - cache for a script and wants to store it in cache_storage. - - - - - - Expired 2020-04. - - wanderview@chromium.org - chrome-owp-storage@google.com - - The network result code produced by disk_cache::Backend::CreateEntry() when - cache_storage is attempting to put a new request/response pair on disk. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - Records where the generic kErrorStorage value is triggered within the - cache_storage code. - - - - - - No longer used. Removed in April 2020. - - cmumford@chromium.org - - The absolute difference between the ServiceWorker Cache size saved to the - CacheStorage index and the actual cache size when opened. - - - - - jkarlin@chromium.org - - The result of opening the backend in the ServiceWorker Cache API. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The result from parsing and validating the index protobuf while calculating - the list of cache_storage origins. - - - - - - Replaced in M78 with ServiceWorkerCache.PeakParallelSharedOps2 that uses a - smaller histogram range with the same number of buckets in order to improve - bucket granularity. - - wanderview@chromium.org - chrome-owp-storage@google.com - - The peak number of shared operations that ran simultaneously during a single - "batch" of operations. A batch is defined as the time from when an - idle scheduler begins running a shared operation until the count of running - shared operations drops back to zero. - - - - - - Removed in M85 since the parallel operation trial launched already. Also, - this histogram did not provide very useful information. - - wanderview@chromium.org - chrome-owp-storage@google.com - - The peak number of shared operations that ran simultaneously during a single - "batch" of operations. A batch is defined as the time from when an - idle scheduler begins running a shared operation until the count of running - shared operations drops back to zero. - - - - - - This histogram was removed in M77 when we began deleting entries with the - deprecated url field. - - horo@chromium.org - - True if a response read from the CacheStorage has a url field. This field - was deprecated in M57. - - - - - - This histogram was removed in M85 in favor of the OperationDuration2 - histograms that provide full timing information for operations. - - wanderview@chromium.org - - An operation is slow (true) if it takes at least 10 seconds to run. If an - operation never completes, it will still be recorded as slow. - - - - - - This histogram was deprecated in M72 in favor of - ServiceWorkerCache.Scheduler.OperationDuration2. - - wanderview@chromium.org - - The time in ms from when an operation is started until it completes. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The time in ms from when an operation is started until it completes. This - histogram differs from the old OperationDuration in that it uses a different - bucket size to measure longer values. - - - - - - This histogram was deprecated in M72 in favor of - ServiceWorkerCache.Scheduler.QueueDuration2. - - wanderview@chromium.org - - The time in ms from when an operation was queued until its task is posted. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The time in ms from when an operation was queued until its task is posted. - This histogram differs from the old QueueDuration in that it uses a - different bucket size to measure longer values. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - The number of operations in the scheduling queue just before enqueuing a new - operation. - - - - - wanderview@chromium.org - chrome-owp-storage@google.com - - Whether the size was calculated using the values stored in the origin's - index file. If this is false, then the size was recalculated by loading all - of the individual cache backends. - - - - - - Removed 2019-02 in favour of Servicification.Startup2. The data was - incompelete since it was only recorded the first time when the - ServiceManager was launched. - - hanxi@chromium.org - yfriedman@chromium.org - hnakashima@chromium.org - mheikal@chromium.org - - Histogram of how Chrome is launched, either in ServiceManager only mode or - as full browser, as well as either cold start or warm start. See - go/servicification_startup_metrics for more details. - - - - - hanxi@chromium.org - yfriedman@chromium.org - hnakashima@chromium.org - mheikal@chromium.org - - Histogram of how Chrome is launched, either in ServiceManager only mode or - as full browser, as well as either cold start or warm start. See - go/servicification_startup_metrics for more details. - - - - - hanxi@chromium.org - yfriedman@chromium.org - hnakashima@chromium.org - mheikal@chromium.org - - Histogram of how Chrome is launched, either in ServiceManager only mode or - as full browser, as well as either cold start or warm start. See - go/servicification_startup_metrics for more details. The UMA data is cached - in the SharedPreference compared with Servicification.Startup2, which might - lose some data when Chrome is running in the ServiceManager only mode. - - - - - asvitkine@chromium.org - src/base/metrics/OWNERS - - Sum of this metric yields the total time Chrome was running in the - background. A single session may be represented by multiple values, so that - this histogram is always present in an uploaded log that represents - background activity. - - Android-only. - - - - - rohitrao@chromium.org - marq@chromium.org - - The number of tabs closed by the user during the current session - (launch/foregrounding to backgrounding). - - This histogram is only logged on iOS when the application is backgrounded. - - - - - rohitrao@chromium.org - marq@chromium.org - - The number of tabs created by the user during the current session - (launch/foregrounding to backgrounding). - - This histogram is only logged on iOS when the application is backgrounded. - - - - - rohitrao@chromium.org - marq@chromium.org - - The number of times the user changed the active tab (this can happen when - manually selecting a new tab, when a pre-rendered tab is made active, when - closing the current tab and the next one is selected) during the current - session (launch/foregrounding to backgrounding). - - This histogram is only logged on iOS when the application is backgrounded. - - - - - yiningwang@google.com - chrome-desktop-ui-sea@google.com - - Time spent in focus mode browser. This is recorded when the focus mode - window closes. This metric is only recorded on Win/Mac/Linux/ChromeOS. - - - - - - - asvitkine@chromium.org - chrisha@chromium.org - chrome-analysis-team@google.com - - The length of a session (launch/foregrounding to quitting/backgrounding) in - milliseconds, recorded at the end of the session. See - Session.TotalDurationMax1Day for the same histogram with a higher maximum - value. (The one's maximum is 1 hour.) - - Windows/Mac/Linux: A session ends (i) when the user puts another app in the - foreground, unless audio is playing. (The Chrome windows can still be shown. - What matters is that a different app has focus.) (ii) when Chrome quits. - (iii) when the screensaver turns on (again, unless audio is playing). (iv) - when the user is inactive for five minutes (again, unless audio is playing). - In this case (starting in M-55), that five minutes is not included in the - sesson length. (v) when audio stops playing, if the user has been inactive - for five minutes or Chrome is not in the foreground. Also, until M69, there - was a bug that caused double-counting of some sessions. - - ChromeOS: not implemented. The ChromeOS histogram Platform.DailyUseTime is - somewhat similar. - - Android: Session boundaries are wonky. Thus, only look at total duration for - a client over a day; don't look at individual durations. A session ends (i) - when the Chrome app leaves the foreground. This sounds obvious yet there are - many subtle though common edge cases here. Going to the Android Home screen - via the Home button is an obvious case. Yet, merely pressing the Recents - button, even if the user reselects the Chrome app (i.e., doesn't leave the - app) also ends a session. Another set of cases is the screen time-out - (blanking the screen) or the lock screen. Either will cause Chrome to be - considered to leave the foreground, ending the session. (ii) some in-app - actions. Yes, some in-app events trigger the end of a session. - - Android continued: These in-app actions that trigger the end of a session - can mostly be considered bugs. Cases: (a) switching to viewing Bookmarks, - History, Downloads, or Settings causes the session to end. Note that - switching out of those modes does not cause the end of a session, only - switching in. Oddly, though the interface looks similar, switching to Recent - Tabs does not trigger the end of a session. Nor does going into the tab - switcher view. (b) modal pop-ups. JavaScript dialogs and other things that - take focus away from the Chrome activity can cause this metric to record a - session end prematurely. See: crbug.com/678276. (c) switching Chrome from as - a single app in the foreground into multi-window mode. (d) switching Chrome - from being one of a set of multi-window apps that are displayed to be the - only app displayed. - - iOS: A session starts when Chrome is launched to the foreground and ends - when Chrome leaves the screen. This is generally straightforward. Chrome - leaves the screen when the screen goes blank or shows the lock screen, when - Chrome clicks a link that opens in another app, or when the user switches to - the app switcher. Note that, unlike on desktop, even if Chrome is playing - media in the background, the session is still terminated when Chrome leaves - the screen. - - iOS continued: These are some edge cases to be aware of: (i) OS overlays. - These can appear, for examples, when a link is clicked that could go to a - non-Google app that has not yet been set to default and the OS asks whether - to open the link in the app by default, or when a user has set the OS to - block certain sites or types of sites by default and require authentication - to access them. This authentication prompt is an OS overlay. At the time of - writing this description, we're not sure if displaying an overlay will end - the session. (ii) full-screen media playing. Because media is played through - iOS's technology stack, if the user takes media that's playing within Chrome - and displayed it full-screen, the session ends because no part of Chrome is - on the screen anymore. (iii) multi-window support. Not yet launched as of - M-85. Sessions end and immediately restart when a user switches from a - single-window to a multi-window view and vice versa, and also ends when - resizing the Chrome window. The end is because Chrome is considered no - longer active during the time the OS animates the windows to change their - sizes. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - chrome-analysis-team@google.com - - The amount of active browsing time that was spent not being opted in to sync - but while having a refresh token for a user's account. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin or - sync status changes. These end-points are when the metric is emitted. For - details on how "stopped interacting with the browser" is decided, - see the description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - chrome-analysis-team@google.com - - The amount of active browsing time that was spent not being opted in to sync - and not having a refresh token for a user's account. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin or - sync status changes. These end-points are when the metric is emitted. For - details on how "stopped interacting with the browser" is decided, - see the description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - chrome-analysis-team@google.com - - The total session duration (see Session.TotalDuration) that was spent being - opted in to sync while having a valid refresh token for the account. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin or - sync status changes. These end-points are when the metric is emitted. For - details on how "stopped interacting with the browser" is decided, - see the description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - chrome-analysis-team@google.com - - The total session duration (see Session.TotalDuration) that was spent being - opted in to sync without a having a valid refresh token for the account. - - This can for example be the case if the user signed out of the web, changed - their password, or otherwise invalidated their signin. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin or - sync status changes. These end-points are when the metric is emitted. For - details on how "stopped interacting with the browser" is decided, - see the description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - collinbaker@chromium.org - chrome-desktop-ui-sea@google.com - - Time spent in touch mode in each session (as defined by - DesktopSessionDurationTracker). Samples correspond one-to-one with - Session.TotalDuration samples. - - This histogram should be analyzed with Session.TotalDuration. For example, - the sum of this histogram divided by the sum of Session.TotalDuration is the - total proportion of active browsing time spent in touch mode. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - - The total session duration (see Session.TotalDuration) that was spent with - an account signed into the content area. - - The difference between the With(out)Account measurements and the - Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are - derived from the user's cookies, not their refresh tokens. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin - status changes. These end-points are when the metric is emitted. For details - on how "stopped interacting with the browser" is decided, see the - description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - - - - - - bsazonov@chromium.org - droger@chromium.org - msarda@chromium.org - treib@chromium.org - tschumann@chromium.org - - The total session duration (see Session.TotalDuration) that was spent - without an account signed into the content area. - - The difference between the With(out)Account measurements and the - Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are - derived from the user's cookies, not their refresh tokens. - - This time is measured from when the user starts interacting with the browser - until either they stopped interacting with the browser or their signin - status changes. These end-points are when the metric is emitted. For details - on how "stopped interacting with the browser" is decided, see the - description of Session.TotalDuration. - - Because a duration can end either because the user became inactive or - because their status changed, the distribution of individual durations - measured are unlikely to be helpful. Instead, please compare total - durations. - - This metric is only recorded on Win/Mac/Linux. - - One caveat with this metric is that if the user has multiple profiles open - at the same time, their session activity will be logged from all the - profiles, instead of only from the profile that the user is using at that - moment. - - - - - - - asvitkine@chromium.org - chrisha@chromium.org - chrome-analysis-team@google.com - - The length of a session (launch/foregrounding to quitting/backgrounding) in - milliseconds, recorded at the end of the session. See Session.TotalDuration - for details on how the end of a session is decided. The histogram - Session.TotalDuration records exactly the same values as this histogram, - just with a smaller maximum value. (That one's maximum is 1 hour.) - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - Number of forward navigation items when navigation was committed/finished. - Recorded when main frame navigation was finished and there is at least one - navigation item. In conjunction with - Session.WebStates.HasForwardItemsAfterNavigation this metric will help to - understand how many navigation items Chrome should restore after relaunch. - - - - - ajuma@chromium.org - eugenebut@chromium.org - gambard@chromium.org - - True if navigation manager has forward navigation items when navigation was - committed/finished. Recorded when main frame navigation was finished. Can be - used to understand how often the users load items in the middle of - back-forward list. In conjunction with - Session.WebStates.ForwardItemsCountAfterNavigation this metric will help to - understand how many navigation items Chrome should restore after relaunch. - - - - - eugenebut@chromium.org - sdefresne@chromium.org - - Recorded when CRWNavigationItemStorage encodes the data, which happens on - page loads, tab changes and app backgrounding. Estimated size, the actual - size can be larger than recorded number. - - - - - justincohen@chromium.org - rohitrao@chromium.org - - The time needed to read iOS session webState data from a file. It's recorded - every time a webState is restored, typically on app startup. - - - - - justincohen@chromium.org - rohitrao@chromium.org - - The size of the file used to persist iOS session history. It's recorded - every time the file is written to storage, which happens on page loads, tab - changes and app backgrounding. - - - - - justincohen@chromium.org - rohitrao@chromium.org - - The time needed to write iOS session webState data to a file. It's recorded - every time the file is written to storage, which happens on page loads, tab - changes and app backgrounding. - - - - - yiyaoliu@chromium.org - How did the user interact with the SessionCrashed Bubble? - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - - The actions that have occurred in a session restore timeline. These are to - be interpreted as raw event counts. Tabs are almost certainly deferred due - to the existence memory pressure, but this may not always be the case. - - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - catan-team@chromium.org - - The time from SessionRestore start until all tabs have finished loading. - - - - - chrisha@chromium.org - - The number of tabs involved in a single session restore that were observed - to have historically made use of background communication mechanisms - (favicon and tab title changes, notifications, etc). - - - - - chrisha@chromium.org - - The number of tabs involved in a single session restore that were observed - to have historically made use of background communication mechanisms - (favicon and tab title changes, notifications, etc) and that were actually - loaded. - - - - - - Removed 2017-02 as not actionable. - - - The size of the commands written to disk. See CommandStorageBackend for - details. - - - - - - Removed 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint and - ultimately SessionRestore.ForegroundTabFirstPaint3. - - jeremy@chromium.org - sky@chromium.org - TBD - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - catan-team@chromium.org - - The time from SessionRestore start until a visible tab has finished loading. - - - - - - Removed 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2 and - ultimately SessionRestore.ForegroundTabFirstPaint3. - - jeremy@chromium.org - sky@chromium.org - - Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2 - and ultimately SessionRestore.ForegroundTabFirstPaint3. - - - - - - Removed 2015-05 in favor of SessionRestore.ForegroundTabFirstPaint3. - - jeremy@chromium.org - sky@chromium.org - - The time from SessionRestore start until a visible tab's first paint. This - metric only records paints that have occurred after a tab has loaded. - - - - - - Removed 06/2019 in favor of SessionRestore.ForegroundTabFirstPaint4. - - chrisha@chromium.org - georgesak@chromium.org - - The time from SessionRestore start until a visible tab's first paint. - - - - - - - chrisha@chromium.org - catan-team@chromium.org - - The time from SessionRestore start until a restored tab's first paint. - Recorded when a restored tab stays visible from the beginning of session - restore until its first paint, and no non-restored tab is painted during - that time. See SessionRestore.ForegroundTabFirstPaint4.FinishReason for when - this is not recorded. - - - - - - - chrisha@chromium.org - catan-team@chromium.org - - The reason for which attempt to record - SessionRestore.ForegroundTabFirstPaint4 was deemed complete. Logged once per - session restore. - - - - - - Removed 2018-05-02. This data was used to confirm that the unique name - generation change succeeded in reducing memory usage, and is no longer - needed. - - dcheng@chromium.org - - The size of a unique name derived from the browsing context name. Emitted - when generating a unique name for a new subframe or when a subframe's - browsing context name is changed before the first real load is committed. - Only applies to subframes as main frames always have an empty unique name. - - - - - - Removed 2017-08 due to unique name generation change. Please use - SessionRestore.FrameUniqueNameFromRequestedNameSize and - SessionRestore.FrameUniqueNameWithFramePathSize instead. - - dcheng@chromium.org - - Records the length of unique names for web frames that are saved as part of - session restore data. It is logged each time the unique name changes, which - typically happens when a web frame is first created or its name is changed - by mutating window.name. - - - - - - Removed 2018-05-02. This data was used to confirm that the unique name - generation change succeeded in reducing memory usage, and is no longer - needed. - - dcheng@chromium.org - - The size of the browsing context name (based on the iframe name attribute or - window.name) when generating the unique name. Emitted when generating a - unique name for a new subframe or when a subframe's browsing context name is - changed before the first real load is committed. Only applies to subframes - as main frames always have an empty unique name. - - - - - - Removed 2018-05-02. This data was used to confirm that the unique name - generation change succeeded in reducing memory usage, and is no longer - needed. - - dcheng@chromium.org - - The size of a unique name when falling back to the frame path algorithm. The - fallback path is used when the browsing context name is empty or non-unique. - Emitted when generating a unique name for a new subframe or when a - subframe's browsing context name is changed before the first real load is - committed. Only applies to subframes as main frames always have an empty - unique name. - - - - - - Removed 2018-05-02. This data was used to confirm that the unique name - generation change succeeded in reducing memory usage, and is no longer - needed. - - dcheng@chromium.org - - The size of a unique name when falling back to the frame path algorithm, - divided by the depth of the frame. Used to normalize sizes for deeper nodes - in a frame tree. Emitted when generating a unique name for a new subframe or - when a subframe's browsing context name is changed before the first real - load is committed. Only applies to subframes as main frames always have an - empty unique name. - - - - - - Removed 2017-02 as not actionable. - - The size, in k, of the last session file on disk. - - - - - Removed 2017-02 as not actionable. - - - Like NavEntryCommittedPeriod, but specifically to provide a clearer - breakdown of samples in the 10 minutes - 8 hours range. - - - - - - Removed 2017-02 as not actionable. - - - Milliseconds between subsequent Save() operations due to a nav entry being - committed (new tab created + nav initiated). - - - - - - Removed 2017-02 as not actionable. - - - Like NavListPrunedPeriod, but specifically to provide a clearer breakdown of - samples in the 10 minutes - 8 hours range. - - - - - - Removed 2017-02 as not actionable. - - - Milliseconds between subsequent Save() operations due to the navigation list - being pruned (typically a change in back/forward stacks). - - - - - - Removed 2017-02 as not actionable. - - - The number of tabs that were loaded simultaneously when restoring a session. - - - - - - Removed 2017-02 as not actionable. - - - Amount of time to read and assemble the commands from the last session. - - - - - - Removed in July 2019 / M77. - - creis@chromium.org - - How often history navigations in subframes restore a different URL than the - frame's default src URL. This indicates how much users rely on subframe - session history items. - - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - - The site engagement score associated with a tab restored by session restore, - recorded at the moment the tab is restored. - - - - - chrisha@chromium.org - - The time since a restored tab was last active. This is the cumulative amount - of time that has passed since the tab was last visible. Time accrues while a - browser is active and the tab remains inactive. If the tab is restored and - remains inactive in a subsequent browsing session the time continues to - accrue. Visible tabs report a value of 0 for this. This is recorded at the - moment the tab is restored during a session restore. - - - - - - Removed in July 2019 / M77, since new approach landed in r493153 (M62). - - creis@chromium.org - - Records the length of unique names that include frame paths, for subframes - that are restoring a different URL than the frame's default src URL during a - history navigation. Large values here would indicate a possible challenge - for the plan to truncate frame unique names (to save memory). - - - - - - Removed 2017-02 as not actionable. - - - Like SavePeriod, but specifically to provide a clearer breakdown of samples - in the 10 minutes - 8 hours range. - - - - - - Removed 2017-02 as not actionable. - - - Amount of time between subsequent SessionService Save() operations (aka - updates to session data). - -
- Periods longer than 10 minutes are grouped together; see SaveLongPeriod for - resolution. -
- - - - - Removed 2019-05 as data is no longer needed. - - dcheng@chromium.org - - How often a subframe is assigned a new name between the initial empty - document and the first navigation. - - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - - A breakdown of key events that occur to individual tabs as they are - processed by an ongoing session restore. - - - - - - Removed 2017-02 as not actionable. - - - TabClosedPeriod, but specifically to provide a clearer breakdown of samples - in the 10 minutes - 8 hours range. - - - - - - Removed 2017-02 as not actionable. - - - Milliseconds between subsequent Save() operations due to a tab being closed. - - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - - The number of tabs involved in a single session restore event. - - - - - - Removed 2020-05. Not actively used in current projects. - - chrisha@chromium.org - - The boolean indicates whether the tab load was initiated because a previous - tab load completed (including the tab was closed) or whether the tab load - was initiated because a timer fired to start the next load (true) during - session restore. - - - - - mek@chromium.org - dmurph@chromium.org - - Total size of the HTML5 SessionStorage browser-side cache purged in KB when - memory pressure signal was triggered or cache size hit the limits. - - - - - mek@chromium.org - dmurph@chromium.org - - Total size of the HTML5 SessionStorage databases in KB in the browser-side - cache. Recorded each time a new database is opened in memory. - - - - - mek@chromium.org - dmurph@chromium.org - - The result of an attempt to commit SessionStorage data to the database. - - - - - mek@chromium.org - dmurph@chromium.org - - The result of a failed attempt to open a LevelDB database for - SessionStorage. - - - - - mek@chromium.org - dmurph@chromium.org - - The result of a failed attempt to open a LevelDB database for SessionStorage - on disk. - - - - - mek@chromium.org - dmurph@chromium.org - - The result of a failed attempt to open a LevelDB database for SessionStorage - in memory. - - - - - mek@chromium.org - dmurph@chromium.org - - The result of attempting to delete the SessionStorage database. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason opening a directory for the LevelDB database that backs - LocalStorage failed. - - - - - mek@chromium.org - dmurph@chromium.org - dullweber@chromium.org - - Recorded when the database connection is closed unexpectedly. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason opening the LevelDB database that backs SessionStorage failed. - - - - - - - mek@chromium.org - dmurph@chromium.org - - The result of opening the LevelDB database that backs SessionStorage. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason reading the namespaces metadata of the SessionStorage database - failed. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason reading the next data map id metadata of the SessionStorage - database failed. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason reading the schema version of the SessionStorage database failed. - - - - - - Removed during the SessionStorage onion soup refactoring. - - cmumford@chromium.org - The result of a commit to the sessionStorage database. - - - - - - mek@chromium.org - dmurph@chromium.org - - The result (success, failure, or database recreated) of trying to open the - LevelDB database for sessionStorage. - - - - - - Removed in Chrome 30. Use Search.DefaultSearchProviderType instead. - - Please list the metric's owners. Add more owner tags as needed. - - The id of the default search engine domain that is specified in user - preferences when a profile is loaded. - - - - - - Removed from the codebase in M85. This trial has long been obsolete. - - gab@chromium.org - - Whether the SettingsEnforcement group was successfully determined from the - field trial or if it had to revert to the hardcoded default. - - - - - gab@chromium.org - - The amount of time it took to run PrefHashFilter::FilterOnLoad on startup. - - - - - gab@chromium.org - - The amount of time it took to run PrefHashFilter::FilterSerializeData on the - UI thread prior to writing the Preferences file to disk. Only logged when - PrefHashFilter::FilterSerializeData actually had work to do. - - - - - mpearson@chromium.org - twellington@chromium.org - - Whether or not the home page user preference is set to the default NTP value - when a profile is loaded. This is only logged if the home button is shown. - - - - - csharp@chromium.org - gab@chromium.org - - Logged on profile load. Indicates whether the hashes dictionary for this - profile is trusted. - - - - - bttk@chromium.org - twellington@chromium.org - wenyufu@chromium.org - - The location type for the homepage if the homepage is enabled. Recorded on - deferred startup iff the homepage is enabled. Android only. - - - - - - Removed in Chrome 30. Replaced by Settings.HomePageEngineType. - - Please list the metric's owners. Add more owner tags as needed. - - The id of the home page domain that is specified in user preferences when a - profile is loaded. - - - - - mpearson@chromium.org - csharp@chromium.org - - Tries to pretend the home page URL is a search URL, and records the search - engine type of that URL by comparing the TLD+1 of the home page URL with - those of the different known search engines. Recorded when a profile is - opened, if a home page URL has been set. Note that at least one profile is - opened on startup. - - - - - twellington@chromium.org - tedchoc@chromium.org - - Whether or not the user has customized their homepage. This is recorded for - all users with a configurable homepage, regardless of whether they have - explicitly disabled the home button in settings. Recorded for Android only - on deferred startup and when the user changes their homepage URL. - - - - - - Removed 08/05/2013. Replaced by - Settings.GivenShowHomeButton_HomePageIsNewTabPage. - - Please list the metric's owners. Add more owner tags as needed. - - Whether or not the home page user preference is set to the default NTP value - when a profile is loaded. - - - - - - Removed in Aug 2018. - - Please list the metric's owners. Add more owner tags as needed. - - The value of the home-page-is-new-tab-page pref when pulled down from sync - to update an out-of-sync local pref store. - - - - - - Removed in Aug 2018. - - Please list the metric's owners. Add more owner tags as needed. - - The value of the home-page-is-new-tab-page pref when pushed up to sync from - a change made locally. - - - - - - Removed in July 2019. - - csharp@chromium.org - gab@chromium.org - - Logged on first run when generating the Preferences file from - master_preferences. True if serializing the generated Preferences file to - disk was successful, false otherwise. Note: this event does not occur if - there is no master_preferences file on first run. - - - - - gab@chromium.org - - The size (in kilobytes) of the JSON settings read from disk on startup. - Suffixed with the name of the corresponding JSON file. - - - - - - Removed 02/2015. Replaced by Settings.JsonDataReadSizeKilobytes. - - gab@chromium.org - - The size of the JSON settings content about to be written to disk in - kilobytes. Suffixed with the name of the JSON file being written to disk. - - - - - - Removed 11/2018 due to lack of use. - - raymes@chromium.org - - The number of writes of a JSON file that occur in every 5 minute period of - running Chrome. Suffixed with the name of the corresponding JSON file. - - - - - - Removed 07/2019. LegacyMachineIdGeneration failed extremely rarely. - - proberge@chromium.org - - Whether generation of the RLZ deterministic machine-specific device id was - successful when creating the ProfilePrefStore. - - - - - - Removed 07/2019. Non MD version of Settings has been deprecated. - - stevenjb@chromium.org - - The amount of time between the render frame host StartProvisionalLoad event - and the render frame DocumentOnLoadCompleted event for the settings page. - - - - - dpapad@chromium.org - dbeam@chromium.org - - The amount of time between the render frame host StartProvisionalLoad event - and the render frame DocumentOnLoadCompleted event for the MD Settings page. - - - - - - Removed 07/2019. Non MD version of Settings has been deprecated. - - stevenjb@chromium.org - - The amount of time between the render frame host StartProvisionalLoad and - DidFinishDocumentLoad events for the settings page. - - - - - dpapad@chromium.org - dbeam@chromium.org - - The amount of time between the render frame host StartProvisionalLoad and - DidFinishDocumentLoad events for the MD Settings page. - - - - - - Removed in Chrome 63, as we verified that machine id generation was not - flaky. - - proberge@chromium.org - - Whether generation of the deterministic machine-specific device id was - successful when initializing the PrefHashStore. - - - - - - Removed in Chrome 54, as we stopped legacy migration of preferences. - - csharp@chromium.org - gab@chromium.org - - Whether, while loading a profile, any preference hashes were migrated from - Local State to either Preferences or Protected Preferences. - - - - - mpearson@chromium.org - csharp@chromium.org - - Tries to pretend pinned tab URLs are search URLs, and records the search - engine types of those URLs by comparing the TLD+1s of the URLs with those of - the different known search engines. Recorded when a profile is opened, if - there are pinned tabs. Note that at least one profile is opened on startup. - - - - - - Removed September 2020; no longer necessary. - - mpearson@chromium.org - The number of pinned tabs opened when a profile is loaded. - - - - rsorokin@chromium.org - jessejames@chromium.org - cros-oac@google.com - - The users progress through the pin unlock setup wizard. Each type - corresponds to the user completeing a different stage of the setup wizard. - - - - - harrisonsean@chromium.org - msramek@chromium.org - sauski@chromium.org - - Which privacy related settings elements a user interacted with. Recorded - every time a user interacts with an element of interest. - - - - - - Removed 07/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during RegisterProfilePrefs. - - - - - rainhard@chromium.org - msramek@chromium.org - Resulting state of the safety check Chrome cleaner check. - - - - andzaytsev@google.com - msramek@chromium.org - Resulting state of the safety check extensions check. - - - - rainhard@chromium.org - msramek@chromium.org - anaudrey@chromium.org - - Which user actions were taken in safety check. Recorded every time a user - does an interaction in safety check. Value 5 and 6 got added with M86. - - - - - andzaytsev@google.com - msramek@chromium.org - Resulting state of the safety check password check. - - - - andzaytsev@google.com - msramek@chromium.org - Resulting state of the safety check Safe Browsing check. - - - - andzaytsev@google.com - msramek@chromium.org - Resulting state of the safety check updates check. - - - - dschuyler@chromium.org - - The number of characters typed in the chrome://settings page search box. - Intended to determine if we are making the user type too much to find what - they are looking for (the search is incremental). - - - - - dschuyler@chromium.org - - If no matches are found when searching within the chrome://settings page, - record the length of the search text. - - - - - dschuyler@chromium.org - - The number of search page hits within the chrome://settings page. This is - especially important when the count is zero (i.e. we returned no hits for a - given search in settings). A search is considered complete via timeout since - there is no concrete way to define the end of a search (the search is - incremental). - - - - - dschuyler@chromium.org - - If there is no further activity in the search box for 1 second, this records - one tick each time a settings section is shown as a result of searching - withing the chrome://settings page. If multiple matches are found within the - same section, the section match is only recorded once. - - - - - dschuyler@chromium.org - - The number of search subpage hits within the chrome://settings page. This is - different from Settings.SearchPageMatchCount in that it is tracking hits in - subpages rather than top level pages. See also - Settings.SearchPageMatchCount. - - - - - mpearson@chromium.org - twellington@chromium.org - - Whether or not the home button is enabled in user preferences when a profile - is loaded. - - - - - - Removed in Aug 2018. - - mpearson@chromium.org - - The enabled state of the Home button pref when pulled down from sync to - update an out-of-sync local pref store. - - - - - - Removed in Aug 2018. - - mpearson@chromium.org - - The enabled state of the Home button pref when pushed up to sync from a - change made locally. - - - - - twellington@chromium.org - tedchoc@chromium.org - - If the home button is enabled or disabled. This is only recorded if the - force homepage feature flag is enabled or the home button is partner - provided. Recorded for Android only on deferred startup and when the user - changes their home button enabled setting. - - This histogram is currently being updated to - ShowHomeButtonPreferenceStateManaged and will eventually be removed. - - - - - twellington@chromium.org - tedchoc@chromium.org - - The new state of the show home button preference after it is changed by the - user. Recorded for Android only. - - - - - twellington@chromium.org - tedchoc@chromium.org - - If the home button is enabled or disabled, either by user or by policy. - Recorded for Android only on deferred startup and when the user changes - their home button enabled setting. - - Note: HomeButtonPreferenceStateType#ManagedDisabled is currently not used. - - - - - pmonette@chromium.org - - The user clicked "Make Google Chrome the default browser" on the - settings page. - - - - - - Removed in Chrome 30. Replaced by Settings.StartupPageEngineTypes. - - Please list the metric's owners. Add more owner tags as needed. - - The ids of startup page domains that are specified in user preferences when - a profile is loaded. - - - - - mpearson@chromium.org - csharp@chromium.org - - Tries to pretend the startup page URLs are search URLs, and records the - search engine types of those URLs by comparing the TLD+1s of the URLs with - those of the different known search engines. Recorded when a profile is - opened, if startup page URLs have been set. Note that at least one profile - is opened on startup. - - - - - mpearson@chromium.org - ramyan@chromium.org - tiborg@chromium.org - chrome-desktop-ntp@google.com - The startup page settings when a profile is loaded. - - - - - Removed in Aug 2018. - - mpearson@chromium.org - - The startup page setting when pulled down from sync to update an out-of-sync - local pref store. - - - - - - Removed in Aug 2018. - - mpearson@chromium.org - - The startup page setting when pushed up to sync from a change made locally. - - - - - - Not needed. Removed August 2019. - - mpearson@chromium.org - - The number of URLs to be loaded on startup when a profile is loaded, if the - startup page setting is set to load URLs. - - - - - - Removed 12/2015. - - mad@chromium.org - The startup URLs pref migration steps. - - - - - Removed 12/2015. - - mad@chromium.org - - The time elapsed in milliseconds in between startup URLs pref migration. A - value of 0 indicates that the last migration time was in the future due to - e.g. an incorrect system time. - - - - - - Removed March 2020. - - msalama@chromium.org - chrome-signin-team@google.com - - Tracks the sWAA value we show to the user in chrome://settings/syncSetup for - sync users. This tracks as well the different states for which sWAA can be - off. This is recorded everytime the sWAA state is calculated/refreshed. Only - Desktop. - - - - - dschuyler@chromium.org - - The time between when the chrome://settings page is opened to the first time - a search is done within that page. This is intended to evaluate how long a - user looks for a setting before giving up and searching for it. - - - - - dbeam@chromium.org - dpapad@chromium.org - - The time until the settings Web UI is loaded, rendered, and interactive for - users (as in they can change a setting). Automatically logged each time the - settings page is opened (if not closed before interactive). - - - - - proberge@chromium.org - - The id of a tracked preference whose value has been changed since the last - time Chrome set it. Without a suffix, this histogram stands for preference - validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - - The id of a tracked preference whose value has been cleared since the last - time Chrome set it. Without a suffix, this histogram stands for preference - validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - - The id of a tracked preference whose last value isn't known. We may be just - starting to track the preference, or local state may have been changed - outside of Chrome. This should only happen once per pref per profile. - Without a suffix, this histogram stands for preference validation using MACs - in the JSON pref files. - - - - - - Removed 2014-07. - - gab@chromium.org - - Logs the tracked preference id when it is migrated to the new MAC algorithm. - This should only happen once per pref per profile. - - - - - proberge@chromium.org - - The id of a tracked preference whose value has not changed since the last - time Chrome set it, but which was last set using a legacy device ID. Each - user should report this at most once per preference id and immediately be - migrated to the latest hashing model. Without a suffix, this histogram - stands for preference validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - - The id of a tracked preference which was initialized despite the absence of - a MAC as its value was NULL. Without a suffix, this histogram stands for - preference validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - The id of a tracked preference which was reset by Chrome. - - - - - Removed 2014-06. - - gab@chromium.org - - The version of a PrefHashStore, reported once for each alternate - PrefHashStore (not associated to the default profile) from a delayed task on - startup. - - - - - - Removed 2014-06. - - gab@chromium.org - - The previous version of an alternate PrefHashStore (not associated to the - default profile) that was updated from a delayed task on startup. This - should match Settings.TrackedPreferencesAlternateStoreVersion fairly closely - for all versions but VERSION_LATEST which should never be reported here. - - - - - - Removed 2014-02 in favor of - Settings.TrackedPreferencesAlternateStoreVersionUpdatedFrom. - - gab@chromium.org - - Preference tracking was initialized for an unloaded profile. This should - happen at most once per profile. - - - - - gab@chromium.org - - Whether settings enforcement was cancelled for a machine joined to a domain. - Reported once per session on browser startup (note: this histogram was - disabled for part of M40). - - - - - proberge@chromium.org - - The id of a tracked preference which was initialized despite the absence of - a MAC as the current MACs are trusted, inferring that this is a newly - tracked pref. Without a suffix, this histogram stands for preference - validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - - The id of a tracked preference whose value has not changed since the last - time Chrome set it. Without a suffix, this histogram stands for preference - validation using MACs in the JSON pref files. - - - - - proberge@chromium.org - - The id of a tracked preference which Chrome would have reset had the config - allowed it. - - - - - - No longer used. Removed 2020-04. - - gab@chromium.org - - The number of items that had changed in a dictionary pref when - Settings.TrackedPreferenceChanged is reported for that pref. - - - - - - Removed 2015-08-18. - - wjmaclean@chromium.org - - Tracks migration to per-partition zoom-level preferences during profile - initialization. - - - - - - Removed 06/2019. All signs indicate that it is exceptionally rare for - initialization to fail. - - grt@chromium.org - - Indicates whether or not the Windows Settings app monitor was initialized. - - - - - - Removed 04/2020. Replaced with Settings.PrivacyElementInteractions to stick - to naming conventions. - - harrisonsean@chromium.org - msramek@chromium.org - sauski@chromium.org - - Which privacy related settings elements a user interacted with. Recorded - every time a user interacts with an element of interest. - - - - - - Removed 03/2020. Recording too much duplicate data with route navigation - histogram (WebUI.Settings.PathVisited). - - harrisonsean@chromium.org - msramek@chromium.org - - Which settings a user interacted with. Recorded every time a user interacts - with a setting. - - - - - mad@chromium.org - - Counts the number of times the user clicked on the No Thanks button of the - settings reset bubble before clicking on the Reset button in the same Chrome - session. - - - - - alito@chromium.org - - Indicates if an error was detected in the settings reset prompt config data - while initializing the reset prompt configuration. - - - - - - Removed 07/2019. - - alito@chromium.org - - The feature parameter determining the amount of time to wait after startup - before attempting to show the settings reset prompt. Logged once after - startup. - - - - - alito@chromium.org - - Indicates whether the settings reset prompt dialog was shown to the user. - - - - - - Removed on 2018-01-16. - - alito@chromium.org - - The number of extensions that were disabled after the user accepted the - settings reset prompt. - - - - - - Removed on 2018-01-16. - - alito@chromium.org - - The number of extensions that will be disabled if the user accepts the - settings reset prompt. Logged once after startup. - - - - - alito@chromium.org - - Indicates whether the user accepted the settings reset prompt. - - - - - alito@chromium.org - - Indicates whether the settings reset prompt should be shown to the user - based on the state of the user's settings. - - - - - alito@chromium.org - - Indicates whether the settings reset prompt is enabled for the user's - setting, or the reason for it being disabled. Logged once after startup. - - - - - alito@chromium.org - - Indicates which settings were reset after the user accepted the settings - reset prompt. - - - - - alito@chromium.org - - The time between the settings reset prompt dialog being shown and the user - accepting the prompt. - - - - - alito@chromium.org - - The time between the settings reset prompt dialog being shown and the user - declining the prompt by clicking the cancel button. - - - - - - Removed in M59 in April 2017 and replaced by - SettingsResetPrompt.TimeUntilCanceled and - SettingsResetPrompt.TimeUntilDismissed. - - alito@chromium.org - - The time between the settings reset prompt dialog being shown and the user - declining the prompt. - - - - - alito@chromium.org - - The time between the settings reset prompt dialog being shown and the user - dismissing the prompt, for example by clicking on the 'x' in the dialog or - pressing the Escape key. - - - - - forshaw@chromium.org - - True if the the installer successfully added AppContainer ACEs to the - application directory during installation and updating. - - - - - - Removed 06/2019. - - grt@chromium.org - - The elapesed time to apply a patch to a previous version's chrome.7z archive - to generate a new chrome.7z archive. This histogram only applies to diff - updates. - - - - - - Expired in M82, then replaced by Setup.Install.CumulativeDiskUsage2 on - 06/2020. - - etiennep@chromium.org - grt@chromium.org - - The cumulative disk usage in MB during install or uninstall attempt, - recorded right after the install/uninstall attempt on windows only. - - - - - etiennep@chromium.org - grt@chromium.org - - The cumulative disk usage in MB during install or uninstall attempt, - recorded right after the install/uninstall attempt on windows only. - - - - - - Removed 2020-02 - - grt@chromium.org - - Hit following a successful install or update when the legacy - "app_host.exe" binary is deleted from the filesystem. - - - - - grt@chromium.org - src/chrome/installer/OWNERS - - Hit following a successful install or update when the legacy "app - launcher" Clients key is deleted from the registry. - - - - - grt@chromium.org - src/chrome/installer/OWNERS - - Hit following a successful install or update when the legacy - "binaries" Clients key is deleted from the registry. - - - - - grt@chromium.org - src/chrome/installer/OWNERS - - Hit following a successful install or update when the COM registration for - the legacy "IExecuteCommand" implementation class key is deleted - from the registry. - - - - - grt@chromium.org - src/chrome/installer/OWNERS - - Hit following a successful install or update when the legacy - "install-extension" app command is deleted from the registry. - - - - - - Removed 06/2019. - - grt@chromium.org - - True if the chrome.packed.7z archive contains a patch (in which case a diff - update is taking place) or false if it contains a full archive (in which - case a new install or a full update is taking place). - - - - - - Removed 03/2020. - - zmin@chromium.org - - Record the NTSTATUS code of unpacking the contents of a 7z file. - - - - - - Removed 03/2020. - - etiennep@chromium.org - - Record the return value of unpacking the contents of a 7z file. - - - - - zmin@chromium.org - grt@chromium.org - Record the status of unpacking the contents of a 7z file. - - - - - Removed 2020-02 - - grt@chromium.org - - Hit following a successful install or update when data from a legacy - multi-install Chrome Frame is deleted from the registry. - - - - - - Removed 06/2019. In 88% of cases, we aborted after the maximum number of - attemps was reached. The remaining 12% of cases occured when another process - tried to acquire the setup singleton. - - fdoray@chromium.org - - Number of calls to DeleteOldVerions() made by a --delete-old-versions - process that didn't delete all files that belong to old versions of Chrome. - A --delete-old-versions process exits when another process tries to acquire - the SetupSingleton or after too many unsuccessful attempts to delete all old - files. A --delete-old-versions process that successfully acquires the - SetupSingleton records to either the - Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the - Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram. - - - - - - Removed 06/2019. 50th percentile: 1.5. 75th percentile: 1.77. 99th - percentile: 2.75. - - fdoray@chromium.org - - Number of calls to DeleteOldVersions() made by a --delete-old-versions - process that successfully deleted all files that belong to old versions of - Chrome. A --delete-old-versions process that successfully acquires the - SetupSingleton records to either the - Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the - Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram. - - - - - huangs@chromium.org - - The peak page file usage by setup.exe in KB during install or uninstall - attempt. - - - - - huangs@chromium.org - - The peak working set size of setup.exe in KB during install or uninstall - attempt. - - - - - waffles@chromium.org - - Hit following a successful install or update when the legacy profile count - keys / values are deleted from the registry. - - - - - - - grt@chromium.org - bcwhite@chromium.org - - The final exit-result of the entire run of setup.exe on Windows. - - - - - ganesh@chromium.org - sorin@chromium.org - xiaolingbao@chromium.org - The outcome of attempting to install a service on Windows. - - - - ganesh@chromium.org - sorin@chromium.org - xiaolingbao@chromium.org - - The outcome of attempting to rollback an install of a service on Windows. - - - - - - Removed 06/2019 because it is not used. - - fdoray@chromium.org - - The result of trying to acquire a setup singleton. On Windows, a setup.exe - process must hold the setup singleton of a Chrome installation when it makes - changes to it. - - - - - - Removed 2017-01 - - grt@chromium.org - - The disposition of a stranded Chrome install discovered while updating - multi-install Chrome Binaries. This metric is only logged in an edge case. - The buckets indicate whether or not the "stranded" Chrome install - has been used in the last 28 days. If so, it respresents a Chrome that has - not been updating due to a logic flaw in the installer and will be repaired - in the current update. If not, it likely represents Chrome Binaries that - were previously used by Chrome Frame that has since been uninstalled and - that will be uninstalled in a future update. - - - - - - Removed 06/2019. - - grt@chromium.org - - The elapsed time to uncompress a chrome.7z patch. This histogram only - applies to diff updates. - - - - - - Removed 06/2019. - - grt@chromium.org - - The elapsed time to uncompress a full chrome.7z archive. This histogram only - applies to new installs and to full updates. - - - - - - Removed 06/2019. - - grt@chromium.org - - The elapsed time to unpack the uncompressed chrome.7z archive. This - histogram applies to all installs and updates. - - - - - - - ganesh@chromium.org - sorin@chromium.org - xiaolingbao@chromium.org - Win32 APIs that error out during setup. - - - - - Not accessed in months. Primary error was CREATE_FILE_MAPPING_FAILURE by - far. Removed 2020-03. - - erikchen@chromium.org - alexilin@chromium.org - - A histogram entry is emitted each time a shared memory object is constructed - (for example, base::ReadOnlySharedMemoryRegion or the deprecated - base::SharedMemory). The value of the entry indicates the type of error - encountered during construction. - - - - - - Not accessed in months and no data reported for it at all. Removed 2020-03. - - alexilin@chromium.org - - Emitted each time a shared memory region could not be created due to a - failed Mac system call. The value of the entry indicates the return value of - the failed call. - - - - - - Not accessed in months. Primary error was #1455 by far. Removed 2020-03. - - bcwhite@chromium.org - - A histogram entry is emitted each time a shared memory object could not be - created due to a failed Windows system call (for example, - base::ReadOnlySharedMemoryRegion or the deprecated base::SharedMemory). The - value of the entry indicates the result of the GetLastError() API call. - - - - - dcheng@chromium.org - rsesek@chromium.org - - Tracks whether an attempt to map shared memory was blocked due to too much - shared memory already being mapped into the address space. - - - - - - Removed 2015-06 because the Finch experiment SharedMemoryCreateStrategy has - finished running. - - erikchen@chromium.org - - The time spent making a new region of shared, anonymous memory. This metric - is not emitted if the shared memory region is read only. - - - - - - Replaced with BrowserRenderProcessHost.KeepAliveDuration as of Aug 2017. - - horo@chromium.org - - A survival time of RenderProcessHostImpl for the In-renderer Shared Worker - from when FastShutdownIfPossible() is called. - - - - - - Removed June 2019. - - horo@chromium.org - - The lifetime of a SharedWorkerHost. This roughly corresponds to the lifetime - of SharedWorker. - - - - - - Removed June 2019. - - horo@chromium.org - - The time from the creation of SharedWorkerHost until when WorkerScriptLoaded - is called. - - - - - - Removed June 2019. - - horo@chromium.org - - The time from the creation of SharedWorkerHost until when - WorkerScriptLoadFailed is called. - - - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - The number of available apps that are about to be shown in a UI for picking - an app to start a phone call with. Desktop only. - - - - - - Removed in M84 after gathering enough data as a baseline. - - himanshujaju@chromium.org - knollr@chromium.org - peter@chromium.org - - Time taken to find a phone number in highlighted text for context menu. - Desktop only. - - Note: This metric drops reports on clients with low-resolution clocks, which - means these reports will be biased against a portion of the population on - Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. - - - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - The number of available devices that are about to be shown in a UI for - picking a device to start a phone call on. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Logged when we try to fire a dial intent in click to call. Distinguishes - between if the user has an app that can handle dial intent or not. Android - only. - - - - - - Removed in M81 in favor of Sharing.ClickToCallDialerPresent - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Logged when a user taps a Click to Call notification and a dial intent is - fired to open the dialer. Distinguishes between empty string (no phone - number) and not empty. Android only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Logged whenever a dialog is shown for the Click to Call feature. Desktop - only. - - - - - - Removed in M81 as there was not a lot of usage of the help link. - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Logged whenever a user clicks on the help text in a Click to Call dialog. - The value is used to distinguish which dialog type was shown. Desktop only. - - - - - - Removed in M82 after collecting enough data. See https://crbug.com/1053140. - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time from opening the dialer until a phone call is initiated. This is - logged when we detect an outgoing phone call after opening the dialer as - part of the Click to Call feature. Android only. - - - - - - Removed in M82 as the experiment has been stopped. - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The number of digits in a phone number. Logged when right clicking on a - selected phone number or tel link, showing the Click to Call dialog and when - selecting a device. Desktop only. - - - - - - Removed in M82 as the experiment has been stopped. - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The number of characters in a phone number including digits and non-digits. - Logged when right clicking on a selected phone number or tel link, showing - the Click to Call dialog and when selecting a device. Desktop only. - - - - - knollr@chromium.org - mvanouwerkerk@chromium.org - - Duration of the phone number regex precompilation task. This is recorded - once after startup. Desktop only. - - - - - - Removed in M82 as the experiment has been stopped. - - - - knollr@chromium.org - mvanouwerkerk@chromium.org - - The result of comparing a phone number regex variant against the simple - version. Logged after right clicking on a selection and when selecting a - device from the context menu. Desktop only. - - - - - - Removed in M82 after collecting enough data. See https://crbug.com/1053140. - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The device state when receiving a Click to Call message. Indicates if the - screen is on or off and if Chrome is running in foreground. Recorded when - handling a Click to Call message. Android only. - - - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - The index of the app selected by the user for Click to Call. Zero based. - Desktop only. - - - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - The index of the device selected by the user for Click to Call. Zero based. - Desktop only. - - - - - knollr@chromium.org - mvanouwerkerk@chromium.org - - Whether a device identified by its guid is available in the local - DeviceInfoTracker. Logged before sending a message to that guid. - - - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The number of hours since the target device timestamp was last updated. - Logged when a message is sent to the device. Not logged for sending ack - messages. All platforms. - - - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The number of hours since the target device timestamp was last updated. - Logged when a message is sent to the device and the result is known. Not - logged for sending ack messages. All platforms. - - - - - alexchau@chromium.org - peter@chromium.org - - Result of Sharing device registration. Logged after Sharing registration is - attempted. - - - - - alexchau@chromium.org - peter@chromium.org - - Result of Sharing device un-registration. Logged after Sharing - un-registration is attempted. - - - - - - Removed 06/2020. Never launched. - - gayane@chromium.org - src/components/send_tab_to_self/OWNERS - - Records how long it took to the failed attempt to save the QR code image. - - - - - - Removed 06/2020. Never launched. - - gayane@chromium.org - src/components/send_tab_to_self/OWNERS - - Records how long it took to successfully save the QR code image. - - - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The comparison of the major version of Chrome on this (the sender) device - and the receiver device. Logged when a message is sent. All platforms. - - - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time from sending a FCM message from the Sharing service until an ack - message is received for it. - - - - - - - mvanouwerkerk@chromium.org - himanshujaju@chromium.org - - The time from receiving a SharingMessage in SharingFCMHandler until an ack - is sent back. Recorded when SendAckMessage callback is run in - SharingMessageHandler. - - - - - mvanouwerkerk@chromium.org - peter@chromium.org - - The type of SharingMessage (aka the PayloadCase). This is logged when a - message is received through FCM by the handler in the Sharing service. All - platforms. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - The time to decode an image for Remote Copy. Desktop only. - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The result of handling a Remote Copy message. Logged once per message, when - the handler for the Remote Copy FCM message is finished handling it. Desktop - only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Result code from loading an image for Remote Copy. Logs net::Error if it's - not net::OK. Logs net::OK if response header is not present. Otherwise, logs - HTTP status code. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - The time to load an image for Remote Copy. Desktop only. - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The size of the image loaded from the image URL specified in a Remote Copy - message received from FCM, after decoding. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The size of the image loaded from the image URL specified in a Remote Copy - message received from FCM, before decoding. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The size of the text in a Remote Copy message received from FCM. Desktop - only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - The time to resize an image for Remote Copy. Desktop only. - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time to detect a clipboard image write for Remote Copy. Logged after - writing the image. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time to write an image to the clipboard for Remote Copy. Logged after - writing the image. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time to detect a clipboard text write for Remote Copy. Logged after - writing the text. Desktop only. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The time to write text to the clipboard for Remote Copy. Logged after - writing the text. Desktop only. - - - - - jeffreycohen@chromium.org - kristipark@chromium.org - src/components/send_tab_to_self/OWNERS - Whether the editor was dismissed during editor recreation. - - - - - - alexchau@chromium.org - knollr@chromium.org - - Result of sending an ack for a SharingMessage by the Sharing service. Logged - in the callback for sending the message to FCM. All platforms. - - - - - - Replaced by SendAckMessageResult in M78. - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Whether an ack message was sent successfully by the Sharing service. Logged - in the callback for sending the message to FCM. All platforms. - - - - - - - alexchau@chromium.org - knollr@chromium.org - - Result of sending a SharingMessage by the Sharing service. Logged after the - send message callback is run. Not logged for sending ack messages. All - platforms. - - - - - - Replaced by SendMessageResult in M78. - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Whether a SharingMessage was sent successfully by the Sharing service. - Success requires receiving an ack message before the timeout. Logged after - the send message callback is run. Not logged for sending ack messages. All - platforms. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The number of available devices that are about to be shown in a UI for - picking a device to share the clipboard with. On desktop, it gets recorded - when the user right clicks on selected text. On Android, it gest recorded - when the user does long press, share and "Send text to Your - Devices". - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - Logged whenever a dialog is shown for the Shared Clipboard feature. - - - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The retry count for sending a shared clipboard message. The zero value is - for the first attempt to send the message, which is not a retry. Logged when - the result of sending the message is known. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The index of the device selected by the user for Shared Clipboard gets - recorded when the user chooses the destination device for sharing text. Zero - based. - - - - - mvanouwerkerk@chromium.org - knollr@chromium.org - - The size of the selected text in Shared Clipboard gets recorded when the - user shares selected text. - - - - - kmilka@chromium.org - src/components/send_tab_to_self/OWNERS - - Records the index of the third party app selected from the bottom row of the - sharing hub. - - - - - kmilka@chromium.org - src/components/send_tab_to_self/OWNERS - - Records the amount of time taken for the user to select a share target after - initiating a share. - - - - - kmilka@chromium.org - src/components/send_tab_to_self/OWNERS - - Records the amount of time taken for the custom share sheet to open after a - share was initiated. - - - - - - Removed 2020-06 as the result is always successful. - - alexchau@chromium.org - peter@chromium.org - - Result of Sharing VAPID key generation during registration. Logged after - Sharing VAPID key generation is attempted. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - Result of parsing received ice candidate. Logged when trying to add received - ice candidate. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - Error reason for closing a WebRTC connection. Logged when a p2p WebRTC - connection is closed. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - Type of routing used to establish a connection with a remote device. Logged - when a p2p connection is established using WebRTC by SharingService. - - - - - himanshujaju@chromium.org - knollr@chromium.org - - Number of ice servers fetched by network traversal API call. Logged after - receiving response of API call. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - Result of receiving and handling a message via WebRTC. Logged after - receiving a message from remote device via WebRTC. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - Result of sending a SharingMessage by SharingService via WebRTC. Logged - after sending the message. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - himanshujaju@chromium.org - knollr@chromium.org - - State of the WebRTC connection when it timed out. Logged when the connection - has been inactive for 30 seconds. - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - - - himanshujaju@chromium.org - knollr@chromium.org - - Sharing WebRTC timing events logged during an active WebRTC connection. - - - - - mpearson@chromium.org - - The number of entries in shortcuts backend's database when initialized, - which happens during profile load. - - - - - - Removed 09/11/2020 as it has been unused for a while with no expectation to - be used in the future. - - manukh@chromium.org - chrome-omnibox-team@google.com - - The time it takes for the ShortcutsProvider to perform a query after the - user has typed N characters. - - - - - - Replaced by Shutdown.browser_exit.time2 to get more resolution into the tail - of the distribution (10/2016). - - hashimoto@chromium.org - - Time for shutdown initiated by the browser exit menu command. - - - - - hashimoto@chromium.org - - Time for shutdown initiated by the browser exit menu command. - - - - - hashimoto@chromium.org - - Time for shutdown initiated by the browser exit menu command per renderer - process. - - - - - - Replaced by Shutdown.end_session.time2 to get more resolution into the tail - of the distribution (10/2016). - - hashimoto@chromium.org - - Time for shutdown initiated by an end session (user logs off, shuts down or - reboots without explicitly exiting). - - - - - hashimoto@chromium.org - - Time for shutdown initiated by an end session (user logs off, shuts down or - reboots without explicitly exiting). - - - - - hashimoto@chromium.org - - Time for shutdown initiated by an end session (user logs off, shuts down or - reboots without explicitly exiting) per renderer process. - - - - - hashimoto@chromium.org - - The number of renderer processes that couldn't be shutdown quickly due to - onbeforeunload or onunload listeners. - - - - - hashimoto@chromium.org - - The number of renderer processes running when shutdown was called. - - - - - hashimoto@chromium.org - The type of the last shutdown. - - - - - Replaced by Shutdown.window_close.time2 to get more resolution into the tail - of the distribution (10/2016). - - hashimoto@chromium.org - - Time for shutdown initiated by the last browser window being closed. - - - - - hashimoto@chromium.org - - Time for shutdown initiated by the last browser window being closed. - - - - - hashimoto@chromium.org - - Time for shutdown initiated by the last browser window being closed per - renderer process. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Records if the fetched Signed Exchange certchain was served from HTTP cache - or not. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Reports the result of Signed Exchange cert verification, including success. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Reports the result of Signed Exchange CT verification, including success. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Records true when a fallback redirect of Signed Exchange has failed with - ERR_TO_MANY_REDIRECTS. - - Total count of SignedExchange.LoadResult2 should be used as a baseline of - this histogram. - - - - - - Removed 2/2019 in favor of SignedExchange.LoadResult2. - - kinuko@chromium.org - kouhei@chromium.org - ksakamoto@chromium.org - - Records the result of loading a resource from Signed HTTP Exchange. Emitted - each time a response is handled as Signed Exchange. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Records the result of loading a resource from Signed HTTP Exchange. Emitted - each time a response is handled as Signed Exchange. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - The status of OCSP response in Signed Exchange certificates. Reported each - time Signed Exchange's OCSP check is performed. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Reports the revocation status of OCSP response in Signed Exchange - certificates. Emitted when Signed Exchange's OCSP check is performed, but - only when an up-to-date OCSP response was stapled. - - - - - - Removed 2/2019 in favor of SignedExchange.Prefetch.LoadResult2. - - kinuko@chromium.org - kouhei@chromium.org - - Records if the prefetched Signed Exchange was properly formatted and passed - verification steps. Reported for each completed SignedExchange prefetch. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Records if the prefetched Signed Exchange was properly formatted and passed - verification steps. Reported for each completed SignedExchange prefetch. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Records if the prefetched Signed Exchange was actually the target of a - navigation which happened within 30 seconds. Reported when a corresponding - navigation is observed, or from an periodic timer event which cleans up the - unmatched prefetch entries. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Records how much Signed Exchange navigations were prefetched and not - prefetched. Matched against 30 seconds window. Reported for each Signed - Exchange navigations. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Recorded when Signed Exchange signature was expired. Records the time delta - between current time and signature's "expires" value. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - Recorded when Signed Exchange signature was not yet valid. Records the time - delta between current time and signature's "date" value. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Reports the result of Signed Exchange signature verification, including - success. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - The amount of time elapsed to fetch certificate chain from certUrl, for - which the fetch has failed. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - The amount of time elapsed to fetch certificate chain from certUrl, for - which the fetch has succeeded. - - - - - ksakamoto@chromium.org - kinuko@chromium.org - horo@chromium.org - - The amount of time that elapsed during - SignedExchangeSignatureVerifier::Verify. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - Number of seconds until the Signed Exchange's expiration time. Recorded when - Signed Exchange signature verification is performed, and emitted only for - Signed Exchanges within the validity period. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - - The amount of time elapsed to ping the original publisher of the Signed - Exchanges. - - - - - kinuko@chromium.org - ksakamoto@chromium.org - horo@chromium.org - Reports the result of the Signed Exchange validity ping. - - - - mlerman@chromium.org - - Tracks user interactions as they sign in through a flow. The suffix of the - histogram indicates what UI widget or application flow triggered the signin - flow. - - - - - bsazonov@chromium.org - aliceywang@chromium.org - - This histogram records the action taken by user after receiving the header - from Gaia in the web sign-in flow. Currently only recorded on Android. - - - - - droger@chromium.org - skym@chromium.org - - There are two separate ways to test for account equality, using the account - id or the email. Historically the email was always used, but going forward - email will be modifiable. Now when we check account equality we use both - approaches and emit this metric to capture if they agreed or not. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Records the state of the account reconcilor when GAIA returns a specific - response. - - - - - - - msarda@chromium.org - sdefresne@chromium.org - - Number of accounts loaded from preferences by the AccountTracker. Invalid - accounts are not counted. - - This is recorded on each profile load. - - - - - - Instrumentation code has been removed as the conversion has been completed. - - msarda@chromium.org - sdefresne@chromium.org - - This histogram records the removal of the ServiceState property from the - identities known to the AccountTracker. It records whether the deprecated - flag was found in the loaded data and had to be deleted. - - This histogram will be used to check whether the migration has completed for - all active installs on a given platform or not (and whether the code can be - removed). - - This is recorded on each profile load. - - - - - msarda@chromium.org - sdefresne@chromium.org - - This histogram records the AccountTracker account ID migration status from - email to GAIA ID after the data is loaded from disk. It is more general than - OAuth2Login.AccountRevoked.MigrationState that only record the event in case - of errors and only on Android. - - This histogram will be used to check whether the migration has completed for - all active installs on a given platform or not (and whether the code can be - removed). - - This is recorded on each profile load. - - - - - - Removed 2019-07 as it was never used by the sign-in team. - - msarda@chromium.org - droger@chromium.org - - Track when chrome successfully adds an account. Failures are not tracked. - - - - - bsazonov@chromium.org - - The time it takes to seed accounts before proceeding to the account - confirmation screen. - - - - - bsazonov@chromium.org - aliceywang@chromium.org - - Number of Android accounts on device when entering the First Run Experience - sign-in screen. - - - - - alexilin@chromium.org - bsazonov@chromium.org - - The time it takes to retrieve Gaia ids for all accounts from GoogleAuthUtil. - - - - - alexilin@chromium.org - bsazonov@chromium.org - - The time it takes to retrieve the list of accounts from the system. - - - - - alexilin@chromium.org - bsazonov@chromium.org - - The time it takes to retrieve the list of accounts from the system on the UI - thread. - - - - - bsazonov@chromium.org - - How long the "Waiting for Google Play Services to finish updating" - dialog is shown. - - - - - bsazonov@chromium.org - chrome-signin-team@google.com - - The time UI thread spent waiting for the list of accounts to be populated. - - - - - - Removed this histogram since we have had newly designed histograms - Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and - Signin.SigninReason. - - guohui@chromium.org - Track how a user interfacts with the android signin promo. - - - - - Removed on 2020-03 as it is not needed by the signin team. - - bsazonov@chromium.org - droger@chromium.org - - Duration of time between UpdateAccountList calls. Recorded when - OAuth2TokenServiceDelegateAndroid::UpdateAccountList completes. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - Records the UI event when user clicks a locked profile on UserManager. - Please note that if the local reauth failed, UserManager might show Gaia - Reauth dialog. - - - - - msarda@chromium.org - droger@chromium.org - - Log the type of GAIA authentication error that occur whenever the error - state changes. - - - - - - Removed 2019-09. No longer useful after Dice is launched. - - droger@chromium.org - - Logs the state of the Chrome account when the user signs out on the web. - This assumes that a logout of the web is always a complete logout of all the - web accounts (e.g. single session signout is not supported). - - - - - - - droger@chromium.org - skym@chromium.org - - The relation between the account signed into chrome, and the account(s) in - the cookie jar. This metric is never recorded when not signed into chrome. - - - - - - - droger@chromium.org - skym@chromium.org - The number of signed in accounts in the cookie jar. - - - - jkrcal@chromium.org - droger@chromium.org - - The number of signed in accounts in the cookie jar for users that have a - (possibly unconsented) primary account. Reported at most every 24 hours - (using a persistent timer). Reporting is split based on the type of the - primary account. - - - - - - - droger@chromium.org - skym@chromium.org - The number of signed out accounts in the cookie jar. - - - - - - droger@chromium.org - skym@chromium.org - The amount of time since the cookie jar last changed. - - - - - - droger@chromium.org - skym@chromium.org - The total number of accounts in the cookie jar. - - - - - Replaced by Signin.DiceMigrationStatus. Does not have any meaningful - information. - - droger@chromium.org - - Whether Dice is enabled for the current profile, recorded at startup. - - - - - - Removed M80. Dice migration is complete. - - msalama@chromium.org - msarda@chromium.org - - Tracks the reason of why DICE migration is not ready. It is computed by Dice - reconcilor delegate on every reconciliation cycle. - - - - - - Removed 03/2020, as it was equivalent to Signin.SigninAllowed. - - droger@chromium.org - - The Dice migration status, recorded at startup for each profile. - - - - - - - droger@chromium.org - msarda@chromium.org - Records Dice responses (signin and signout). - - - - - - droger@chromium.org - msarda@chromium.org - Outcome of the token fetch in Dice signin. - - - - - Removed M77 in favor of Signin.SigninCompletedAccessPoint - - msarda@chromium.org - droger@chromium.org - - Track if the profile sign in took place during First Run or not. Logged at - signin time. True means signin took place during First Run, False means - anytime after. - - - - - - Removed M77 as not relevant. - - msarda@chromium.org - droger@chromium.org - - Track how many minutes of local system time elapsed from when Chrome was - installed to when Signin occured for this profile. - - - - - alexilin@chromium.org - droger@chromium.org - - Result of the browser remote consent flow, which is a part of the - chrome.identity.getAuthToken() extension API call. Desktop only. - - - - - - - alexilin@chromium.org - droger@chromium.org - - Result of the chrome.identity.getAuthToken() extension API call. Recorded - right before returning the result to an extension. Desktop only. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - The number profile load events that needs a force-sign-in verification - request. It's recorded when profile is loaded with an authentication token - and force-sign-in policy is enabled. - - - - - zmin@chromium.org - pastarmovj@chromium.org - - Elapsed time of the force-sign-in verfication if it's finished. It includes - total network delay, retry delay and wait time due to no connection. The - verfication will not be recorded if it's not finished before profile is - signed out or removed from memory. - - - - - - - droger@chromium.org - msarda@chromium.org - - The number of requests initiated by the browser to log the user out from - Google web. The Chrome account reconcilor enforces account consistency for - Google accounts between the browser and web. In some cases it must force - logout the user from Google web and then it sends a request to the Gaia - logout endpoint. The expectation is that brower initiated logout is a rare - event and should only occur in the following cases: a) it to be triggered - when the browser fails to exchange an auth code for refresh tokens after a - web sign-in (events which is counted by histogram - Signin.DiceTokenFetchResult), b) when all refresh tokens are invalid (e.g - when they cannot be loaded from disk). - - - - - droger@chromium.org - msarda@chromium.org - - Reconds finished access token requests during Chrome reconcile, both - successful or not, and return the GoogleAuthError state NONE is a success, - other values are failures. - - - - - droger@chromium.org - msarda@chromium.org - - Retry reason of failed access token requests during Chrome reconcile. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the duration of the account info fetch after signin interception. - - - - - droger@chromium.org - alexilin@chromium.org - - Records the outcome of the signin interception heuristic, which runs for - each signin interception. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the duration of the signed-in profile creation after signin - interception. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the duration of the signed-in profile switch after signin - interception. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the duration of session startup time after signin interception. This - includes waiting for the account to be available on the web. - - - - - - - alexilin@chromium.org - droger@chromium.org - - Records the outcome of the enterprise signin interception bubble. Recorded - when the bubble is dismissed. - - - - - - - droger@chromium.org - msarda@chromium.org - - Reason for invalid Gaia credentials. Recorded when Signin.AuthError records - invalid credentials. - - - - - treib@chromium.org - mmoskvitin@google.com - - Records the general type of signin that is occuring in relation to previous - signin and local data. - - - - - fernandex@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Records whether the Gaia cookie is present when a user navigates to a - Google-owned domain that is eligible for Mirror account consistency to track - authentication cookies that have been remove by an external force (e.g. - Apple's ITP). This logging is limited to once every hour due to performance - constraints. - - - - - jebel@chromium.org - fernandex@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Tracks the combination of sign-in method and sync state for signed-in users - on iOS. If the user is signed in, this histogram is updated with the sign-in - method and the sync state each time the application goes to foregrond. - "Client Login" corresponds to users that have signed in via the - legacy client login flow (Chrome iOS M27 and before). "Shared - Authentication" corresponds to user that have signed in via the iOS - Shared Authentication library. "Sync off" corresponds to users - that have sync turned off. "Sync on" corresponds to users that - have sync turned on. - - - - - fernandex@chromium.org - jlebel@chromium.org - msarda@chromium.org - chrome-signin-team@google.com - - Count of the number of SSO accounts present on the device. Note that this is - different to the number of accounts signed in in Chrome. The count is logged - in this histogram each time the application goes to foreground. - - - - - droger@chromium.org - skym@chromium.org - - Current best guess if this device is shared between multiple users. - - - - - - - msarda@chromium.org - droger@chromium.org - - Failure reason of ListAccounts call failure during account reconciliation, - Chrome OS login, or signin internals queries. - - - - - - - msarda@chromium.org - droger@chromium.org - - Retry reason of failed ListAccounts calls (these calls calls are used to - fetch the list of Google accounts present in the Gaia cookies). - - - - - jlebel@chromium.org - msarda@chromium.org - - Counts the number of identities loaded by SSO library using the keychain - API. The metric is recorded every time SSO updates the identity list (either - on the first run, or when the cache is staled). See: - https://crbug.com/897470. - - - - - jlebel@chromium.org - msarda@chromium.org - - Tracks the time it takes to load identities by SSO library using the - keychain API. The metric is recorded every time SSO updates the identity - list (either on the first run, or when the cache is staled). See: - https://crbug.com/897470. - - - - - jlebel@chromium.org - msarda@chromium.org - - Tracks the time it takes to load one identity in average by SSO library - using the keychain API. This value is the total time taken by the keychain - API to finish, divided by the number of identities returned. The metrics is - recorded every time SSO updates the identity list (either on the first run, - or when the cache is staled). See: crbug.com/897470. - - - - - - - droger@chromium.org - msarda@chromium.org - - Action taken for tokens being loaded from the token database, at Chrome - startup. Tokens can be either loaded into Chrome's token service or revoked. - - - - - - - droger@chromium.org - msarda@chromium.org - - Number of accounts in tokens sent to Gaia Multilogin. Recorded when Chrome - does a request to /oauth/multilogin. - - - - - - Removed in M76. Use Signin.OAuthMultiloginResponseStatus instead. - - droger@chromium.org - msarda@chromium.org - - Reconds finished calls to Gaia Multilogin endpoint, both successful or not, - and return the GoogleAuthError state NONE is a success, other values are - failures. - - - - - - Removed in M76, because multilogin switched to a new error type. - - droger@chromium.org - msarda@chromium.org - - Retry reason of failed Multilogin call during Chrome reconcile. - - - - - alexilin@chromium.org - droger@chromium.org - - Result of the OAuth2MintToken API call. Recorded after the response is - processed. Desktop only. - - - - - - Replaced on 2020-04 by Signin.OAuth2TokenGetResult. - - msarda@chromium.org - droger@chromium.org - - Reason fetching an OAuth2 Token failed. Available on all OSes. - - - - - - - msarda@chromium.org - droger@chromium.org - - Reason fetching an OAuth2 Token failed or none in case of success. Available - on all OSes. - - - - - - - msarda@chromium.org - droger@chromium.org - - Reason fetching an OAuth2 Token is being retried. Available on all OSes. - - - - - - - droger@chromium.org - msarda@chromium.org - Response status received from gaia Multilogin. - - - - noms@chromium.org - - Count of the ways users interact with the confirmation dialogs of the new - web based sign in to Chrome flow (accessed via the one click signin). - - - - - noms@chromium.org - Tracks events related to the reauthentication Gaia page. - - - - - Removed 2014-09 because chrome no longer tries to reconcile from the cookie - jar to the browser. - - mlerman@chromium.org - - How many accounts were added to the browser's token service because they - were in the cookie jar. - - - - - - - msarda@chromium.org - droger@chromium.org - - How many accounts were added to the cookie jar because they were in the - browser's token service. - - - - - - - msarda@chromium.org - droger@chromium.org - - Records whether all external connections have been successfully checked (a - value of "true") or not ("false") when the reconciler - attempts to perform MergeSession. - - - - - - - msarda@chromium.org - droger@chromium.org - - After execution of the account reconcilor, compares the primary account in - the token service to the primary GAIA account of the cookie jar. - - - - - - Removed in favor of Signin.Reconciler.Duration.UpTo3mins. - - rogerta@chromium.org - msarda@chromium.org - Records the execution time of the account reconciler. - - - - - - droger@chromium.org - msarda@chromium.org - - Records the execution time of the account reconciler using 100 buckets, up - to 3 minutes. - - - - - - - msarda@chromium.org - droger@chromium.org - - Records the time it took to successfully check all external connections - whenever the reconciler performs a reconciliation. - - - - - - - msarda@chromium.org - droger@chromium.org - - Records the time it took to check only a portion of external connections - whenever the reconciler performs a reconciliation. This means that either a - network error occured while checking some sites or the site did not respond - before the check timeout. - - - - - - - msarda@chromium.org - droger@chromium.org - - How many accounts were removed from the cookie jar because they were not in - the browser's token service. - - - - - - Removed this histogram along with the code that was logging it. - - pavely@chromium.org - - Track when chrome successfully sends RefreshTokenAnnotationRequest. - - - - - droger@chromium.org - msarda@chromium.org - - Reports the status (including error details) of token revocation requests - after they complete. This is recorded once per token, even if the request is - retried multiple times. It will be either a success if the token has been - revoked or the error on the last retry. - - - - - droger@chromium.org - - Tracks the progress of revocation requests for refresh tokens, and can be - used to check how many requests do not complete and why. Recorded for each - refresh token revocation request from the token service. - - - - - droger@chromium.org - msarda@chromium.org - - Reports the status (including error details) of token revocation requests - after they complete. - - - - - - - droger@chromium.org - msarda@chromium.org - - Source for refresh token revocation. This is used to track the sources for - signing out of Google accounts and is required to validate that the browser - is not revoking tokens for large parts of the user population. - - - - - - - droger@chromium.org - msarda@chromium.org - - Source for refresh token updated to invalid tokens. The refresh token is - updated to an permanently invalid token when the user attempts to sign out - of the primary account without turning off sync. This histogram is used to - track the sources for invalidating the token of the primary account and is - required to validate that the browser is not invalidating the token of the - primary account for large parts of the user population. - - - - - - - droger@chromium.org - msarda@chromium.org - - Source for refresh token updated to valid tokens. This is used to track the - sources for adding Google accounts to the browser. - - - - - - Removed 2019-07, replaced with a log message. - - msarda@chromium.org - - Tracks when Chrome adds or removes the Desktop Identity Consistency HTTP - header to Gaia. - - - - - - Removed 2019-07, replaced with a log message. - - msarda@chromium.org - - Tracks when Chrome adds or removes the the X-Chrome-Connected HTTP header to - Gaia. - - - - - anastasiian@chromium.org - sinhak@chromium.org - - The result of logging the parent consent for secondary EDU account addition - in child account sessions. - - - - - - - msarda@chromium.org - droger@chromium.org - - This histogram records the success of setting each cookie after Multilogin - response is received and parsed. - - - - - fernandex@chromium.org - jlebel@chromium.org - msarda@chromium.org - - Track the number of times the view that displays the accounts that are - signed is shown. This view only exists on iOS and is shown every time the - application enters forground iff the accounts changed while it was in - background. Only bucket "Shown" is being recorded (this histogram - is a counter). - - This histogram was added following crbug.com/1006717 (stable regression) - where the signed-in accounts view was repeatedly shown for a set of users. - It is used as a counter to monitor that there are no bumps in its timeline. - - - - - - Removed in 7/2019 as the information it provides is no longer useful. - - msarda@chromium.org - droger@chromium.org - - Track how many minutes of real time (not browser active time) elapsed - between profile signin and signout. - - - - - - - droger@chromium.org - msarda@chromium.org - tangltom@chromium.org - - Tracks the state of a user's signin-allowed preference. This is recorded at - every startup. - - - - - msarda@chromium.org - bsazonov@chromium.org - droger@chromium.org - chrome-signin-team@google.com - Logs the original access point of each completed sign in. - - - - msarda@chromium.org - bsazonov@chromium.org - droger@chromium.org - chrome-signin-team@google.com - Logs the reason of each completed sign in. - - - - - Removed this histogram since we have had newly designed histograms - Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and - Signin.SigninReason. - - noms@chromium.org - - Logs the original source that displayed the signin or reauth Gaia page, - before the page is displayed. - - - - - msarda@chromium.org - bsazonov@chromium.org - droger@chromium.org - chrome-signin-team@google.com - - Logs the original access point that displayed the signin or reauth Gaia - page, before the page is displayed. - - - - - skym@chromium.org - - If the user chose to delete their profile or not when signing out of an - unmanaged account. When the user is not given a choice this metric is not - recorded. - - - - - - - msarda@chromium.org - droger@chromium.org - Track how a profile gets signed out. - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Tracks the error code by -[SSOService identitiesWithError:]. See: - https://crbug.com/981082. - - - - - - - jlebel@chromium.org - fernandex@chromium.org - - Tracks the SSO identity cache state before calling -[GCRSSOService - identitiesWithError:] or -[GCRSSOService identitiesForDisplay]. See: - https://crbug.com/897470. - - - - - - - jlebel@chromium.org - fernandex@chromium.org - - Tracks the time it takes to call -[GCRSSOService identitiesWithError:] or - -[GCRSSOService identitiesForDisplay]. See: https://crbug.com/897470. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts the number of cookies returned by -[WKHTTPCookieStore - getAllCookies:]. This histogram is to help to understand how many callbacks - from |getAllCookies:| can be missing. And if the number of cookies is - related in that iOS bug. See: crbug.com/880981. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Tracks the time it takes for -[WKHTTPCookieStore getAllCookies:] to finish - and call its callback. Note that nothing is logged is -[WKHTTPCookieStore - getAllCookies:] fails to calls its callback. This histogram is to help to - understand how many callbacks from |getAllCookies:| can be missing, related - to a bug from iOS. And if the number of cookies is related in that iOS bug. - See: crbug.com/880981. - - - - - jlebel@chromium.org - chrome-signin-team@google.com - - Counts the number of times -[WKHTTPCookieStore getAllCookies:] is called and - the number of times it calls its callback. This histogram is to help to - understand how many callbacks from |getAllCookies:| can be missing, related - to a bug from iOS. And if the number of cookies is related in that iOS bug. - See: crbug.com/880981. - - - - - - Obsolete after Unified Consent launch. - - bsazonov@chromium.org - - Tracks the usage of different flows that switch sync accounts. Logged after - accounts have been switched. - - - - - - - triploblastic@chromium.org - bsazonov@chromium.org - - Records various UI and user action events related to the sync error infobar. - Android only. - - - - - triploblastic@chromium.org - bsazonov@chromium.org - Tracks where FirstSetupComplete bit is set from. - - - - - Removed M80. Obsolete after Dice migration completed. - - msalama@chromium.org - msarda@chromium.org - - Tracks the state of kTokenServiceDiceCompatible preference. This is recorded - at every startup, if the account consistency method is in Dice migration and - is not ready yet to migrate to Dice. - - - - - - Removed 2019-09. Obsolete after Dice is launched. - - droger@chromium.org - - Tracks the changes of refresh token states for all accounts. Tokens can have - three states: Regular (retrieved from Gaia), Invalid (created by Chrome and - known to be invalid) or None (no token). Recorded when a token is loaded or - changed. - - - - - - - msarda@chromium.org - - Counts how many times the SQL statements to get all tokens is valid. - - - - - - - msarda@chromium.org - - Counts the results of loading a refresh token from the token database. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the time from when the user confirms transactional reauth to when - the backround navigation to the Gaia reauth endpoint completes. - - - - - alexilin@chromium.org - droger@chromium.org - - Records the time from when the user triggers transactional reauth to when - the background navigation to Gaia reauth endpoint completes. - - - - - - - alexilin@chromium.org - fhorschig@chromium.org - - Recorded whenever the user interacts with reauthentication to complete a - transaction (like interacting with the account store for passwords) and - whether the reauth challenge was cleared. - - - - - - - alexilin@chromium.org - droger@chromium.org - - Records user actions performed in the reauthentication dialog/tab. - - - - - - - msarda@chromium.org - droger@chromium.org - - Reason of failure to acquiring an ubertoken based on an already-minted - access token. Available on all OSes. - - - - - - - msarda@chromium.org - droger@chromium.org - - Retry reason of failure to acquire an ubertoken based on an already-minted - access token. Available on all OSes. - - - - - triploblastic@google.com - bsazonov@chromium.org - User requested to wipe local device data on signout. - - - - - Obsolete because the XDevicePromo never shipped. - - anthonyvd@chromium.org - mlerman@chromium.org - - How long a browsing session was measured to be. Logged when a Browser window - becomes active if the previous activation was longer than the minimum - configured in the "CrossDevicePromo" experiment. Desktop only. - - - - - - Obsolete because the XDevicePromo never shipped. - - anthonyvd@chromium.org - mlerman@chromium.org - - How often browsers are considered activated, which in turn triggers the - CrossDevicePromo. Logged every time a Browser window becomes active. We need - this to estimate QPS for RPC calls. Desktop only. - - - - - - Obsolete because the XDevicePromo never shipped. - - anthonyvd@chromium.org - mlerman@chromium.org - - The reasons for which a profile is or is not eligible for the Desktop Cross - Device Sign In Promo. Logged every time a new Browsing session is detected - as part of a Browser window becoming active. Desktop only. - - - - - - Obsolete because the XDevicePromo never shipped. - - anthonyvd@chromium.org - mlerman@chromium.org - - Tracks if profiles initialized the XDevicePromo, and if not, why. Logged at - Profile startup and (if not initialized then) when a new browsing session is - detected during Browser window activation. Desktop only. - - - - - jkarlin@chromium.org - - The size of the cache at the time that the index has finished initializing. - - - - - morlovich@chromium.org - wanderview@chromium.org - - Whether or not the CRC was checked at the moment when the last reference to - a read-only entry stream is closed. - - - - - wanderview@chromium.org - morlovich@chromium.org - - Record the outcome of the simple DiskCache consistency check. The - consistency check is executed every time a simple DiskCache is initialized. - This check includes both inspecting the schema on disk and upgrading the - schema to the latest version if necessary. - - - - - wanderview@chromium.org - morlovich@chromium.org - - Record the final consistency check value after index files have been deleted - from an empty simple DiskCache. This histogram will tell us how often the - index deletion code results in a functioning cache. It will also tell us - what kind of consistency failures cannot be recovered due to index file - deletion. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time from the creation of the simple cache backend until the index has - been loaded from disk. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time from the creation of the simple cache backend until the index fails - to load. - - - - - wanderview@chromium.org - morlovich@chromium.org - - Record if any simple DiskCache index files were deleted from an otherwise - empty cache after the cache failed the initialization consistency check. - This histogram will tell us how often the deletion code is triggering and - modifying the disk. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time to close (write out footers and close the file) the cache entry on - disk. Includes only successful operations. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time to access (open for creation and write initial headers) the cache - entry on disk. Includes only successful operations. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time to remove the cache entry on disk. Includes only individually - doomed entries, not entries bulk-erased during eviction. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time to access (open and read headers from all files) the cache entry on - disk. Includes only successful operations. - - - - - - Removed 2020-08. - - morlovich@chromium.org - - The time to open the stream 2 file successfully on disk cache entry open - with known key, when the size of payload is greater than 32 bytes. - - - - - - Removed 2020-08. - - morlovich@chromium.org - - The time to open the stream 2 file successfully on disk cache entry open - with known key, when the size of payload is 32 bytes or less. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time to write a chunk to the cache entry on disk. Includes only - successful operations. - - - - - - Removed 2018-02. Not creating stream 2 on CreateEntry entries is indeed a - good idea, since stream 2 writes are done on things opened with OpenEntry. - (Which also means this metric wasn't good at evaluating the prevalence of - stream 2 in general). - - morlovich@chromium.org - - Whether, upon creation of a new cache entry, the file for stream 2 was - omitted since that stream was empty. - - - - - - Removed 2020-08. Look at SyncOpenResult and SyncCreateResult. - - morlovich@chromium.org - - For entry creation operations that were sent to the disk, the result of - creation. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The time, in ms, spent creating a new entry on disk. This measures time from - when the method got removed from SimpleEntryImpl's operation queue till when - the callback is about to be invoked, and includes all Open and Create - operations, despite what the name may suggest. - - - - - - Removed 2020-08-17 - - morlovich@chromium.org - - Whether, upon opening of an existing cache entry, stream 2 was empty and the - file for that stream was therefore removed. - - - - - - Removed 2019-03. - - morlovich@chromium.org - - At the time that operations are run, the number of pending operations on a - particular entry. - - - - - wanderview@chromium.org - morlovich@chromium.org - - The difference between EntryTrailerPrefetchSize and EntryTrailerSize in - bytes within a single ReadAndValidateStream0AndMaybe1() method call. If the - prefetch read too many bytes then this will be a positive value. If the - prefetch did not read enough bytes, then this will be a negative value. - - - - - wanderview@chromium.org - morlovich@chromium.org - - The number of bytes prefetched from the end of the entry file in an attempt - read the EOF footer and the stream 0 data in a single file operation. - Ideally this value should match the EntryTrailerSize histogram indicating - the actual trailer size on disk was. - - - - - - Removed 2020-05 due to excessive quantities of data. - - wanderview@chromium.org - - The number of bytes read at the end of the entry file in order to process - the EOF footer and the stream 0 data. - - - - - - Removed 2013 in favour of SimpleCache.Eviction.CacheSizeOnStart2 - - morlovich@chromium.org - The size of the cache at the beginning of an eviction. - - - - morlovich@chromium.org - The size of the cache at the beginning of an eviction. - - - - morlovich@chromium.org - The number of entries to be erased in an eviction. - - - - - Removed 2013 in favour of SimpleCache.Eviction.MaxCacheSizeOnStart2 - - morlovich@chromium.org - - The maximum allowed size of the cache at the beginning of an eviction. - - - - - morlovich@chromium.org - - The maximum allowed size of the cache at the beginning of an eviction. - - - - - morlovich@chromium.org - wanderview@chromium.org - The result of an eviction. - - - - - Removed 2013 in favour of SimpleCache.Eviction.SizeOfEvicted2 - - morlovich@chromium.org - The number of bytes to be erased in an eviction. - - - - morlovich@chromium.org - wanderview@chromium.org - The amount of memory freed in an eviction. - - - - - Removed 2013 in favour of SimpleCache.Eviction.SizeWhenDone2 - - morlovich@chromium.org - The size of the cache after running an eviction. - - - - morlovich@chromium.org - wanderview@chromium.org - The size of the cache after running an eviction. - - - - morlovich@chromium.org - wanderview@chromium.org - Time spent completing an eviction. - - - - morlovich@chromium.org - wanderview@chromium.org - Time spent selecting entries for eviction. - - - - morlovich@chromium.org - wanderview@chromium.org - - This even is emitted when SimpleCache is forced to either close some files - due to being over FD limit, or reopen files it had to close due to such - limit earlier. - - - - - - Removed 2019-07-03 - - morlovich@chromium.org - - The maximum limit of how many file descriptors a process can open. Emitted - each time the browser is launched, if the limit could be retrieved. (This is - the highest value we could raise the current limit to if we liked.) - - - - - - Removed 2019-07-03. Consider Memory.Browser.OpenFDsSoftLimit for similar - information. - - morlovich@chromium.org - - The current limit of how many file descriptors a process can open. Emitted - each time the browser is launched, if the limit could be retrieved. (We can - raise this to the maximum limit if we like, without root access.) - - - - - - Removed 2019-07-03 - - morlovich@chromium.org - - The result of trying to get the file descriptor limit. Emitted each time the - browser is launched. - - - - - - Removed 2019-07-03. - - morlovich@chromium.org - - The number of open entries across all caches backed by the Simple Cache. An - entry is opened whenever a caller asks to open it to read or write cache - data, and remains open until the last caller asks to close it. Logged - whenever an entry is opened or closed. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The size of the header stream of a Simple Cache entry, emitted every time - the headers are written or rewritten. - - - - - - Removed 2018-06-05 - - morlovich@chromium.org - - How the header size has changed in a Simple Cache entry, emitted every time - a write operation occurs on the header stream. (This includes the initial - write, rewrites, and other writes that we couldn't classify.) - - - - - - Removed 2018-06-05 - - morlovich@chromium.org - - The absolute size decrease of the header stream of a Simple Cache entry, - emitted every time the headers are rewritten with a smaller size. - - - - - - Removed 2018-06-05 - - morlovich@chromium.org - - The relative size decrease of the header stream of a Simple Cache entry, - emitted every time the headers are rewritten with a smaller size. - - - - - - Removed 2018-06-05 - - morlovich@chromium.org - - The absolute size increase of the header stream of a Simple Cache entry, - emitted every time the headers are rewritten with a larger size. - - - - - - Removed 2018-06-05 - - morlovich@chromium.org - - The relative size increase of the header stream of a Simple Cache entry, - emitted every time the headers are rewritten with a larger size. - - - - - - Removed in M85, but code was missing at that point already. - - morlovich@chromium.org - For each index load, whether the index file was corrupt. - - - - morlovich@chromium.org - wanderview@chromium.org - The number of entries in a newly created index file. - - - - - Removed in M85 - - morlovich@chromium.org - Number of entries loaded from the index file on start. - - - - - Removed in M85 - - morlovich@chromium.org - - Number of entries restored from disk when there was no index or the index - was corrupted. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The state the index file is at when an attempt is made to load from it. - - - - - - Removed in M85 - - morlovich@chromium.org - - At the time of index initialization, the number of enqueued jobs awaiting - index initialization. - - - - - wanderview@chromium.org - morlovich@chromium.org - The method used to initialize the simple cache index. - - - - - Removed in M85, but didn't actually work before that. - - morlovich@chromium.org - - Time (as measured on the worker pool) spent loading the index file. - - - - - jkarlin@chromium.org - - The number of entries in the index at the time that the index has finished - initializing. - - - - - morlovich@chromium.org - wanderview@chromium.org - The number of entries written to the index on a flush. - - - - morlovich@chromium.org - wanderview@chromium.org - - Time (as measured on the worker pool) spent restoring the index file by - iterating directory entries. - - - - - - Removed 07/2013, and replaced by IndexFileStateOnLoad. - - morlovich@chromium.org - For each index load, whether the index file was stale. - - - - - Removed pre-M85. - - morlovich@chromium.org - - The interval between index saves, for apps in the background. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - The interval between index saves, for apps in the foreground. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The reason an index was written to disk. Recorded every time an index is - saved. - - - - - morlovich@chromium.org - wanderview@chromium.org - - Recorded immediately after loading a fresh index (INDEX_STATE_FRESH or - INDEX_STATE_FRESH_CONCURRENT_UPDATES), the reason the loaded index was - written to disk. - - - - - - Removed 2013-05 in favour of - SimpleCache.SimpleIndexWriteToDiskTime.Background and - SimpleCache.SimpleIndexWriteToDiskTime.Foreground. - - morlovich@chromium.org - - The amount of time spend writing the index file to disk, measured starting - at the beginning of the write on the callback thread, and calculated using - the completion time on the worker pool. - - - - - - Removed in M85 - - morlovich@chromium.org - - The amount of time spend writing the index file to disk, for apps in the - background, measured starting at the beginning of the write on the callback - thread, and calculated using the completion time on the worker pool. - - - - - - Removed in M85 - - morlovich@chromium.org - - The amount of time spend writing the index file to disk, for apps in the - foreground, measured starting at the beginning of the write on the callback - thread, and calculated using the completion time on the worker pool. - - - - - - Removed 2016-05 as the match checking was moved back into the entry itself, - so this result is now reported in the SimpleCache.x.SyncOpenResult - histograms. - - morlovich@chromium.org - - For each call to OpenEntry, whether the key on disk matched the request key. - - - - - - Removed 2018-01; not viewed as actionable. - - morlovich@chromium.org - - For each file in the Simple Cache, the percentage of disk space used by the - cluster loss, the unused disk space in the last 4096 byte cluster of the - file. - - - - - - Removed 2018-01; not viewed as actionable. - - morlovich@chromium.org - - For each file in the Simple Cache, the number of bytes in the last 4096 byte - cluster when the entry is saved to disk. - - - - - jkarlin@chromium.org - - The maximum allowed size of the cache at the time that the index has - finished initializing. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - Number of operations that were queued behind a particular doom operation - (with a mass doom counting as a single operation). - - - - - morlovich@chromium.org - wanderview@chromium.org - - At the time that an entry is opened, the state of that entry in the index. - - - - - wanderview@chromium.org - morlovich@chromium.org - - Record the original consistency error produced by a simple DiskCache before - a retry was attempted and succeeded. This histogram will tell us what kind - consistency errors can be recovered from in practice. - - - - - jkarlin@chromium.org - - The fullness (in percent) of the cache at the time that the index has - finished initializing. The percentage is calculated as (cache_size * 100) / - max_cache_size. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - Delay between when the I/O portion of CreateEntry is enqueued and when its - execution begins. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - Delay between when the I/O portion of OpenEntry is enqueued and when its - execution begins. - - - - - - Removed pre-M85. - - morlovich@chromium.org - bingler@chromium.org - - Delay between when the I/O portion of OpenOrCreateEntry is enqueued and when - its execution begins. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - Delay between when an operation is deferred due to a pending doom for its - key, and when it can resume execution. - - - - - - Removed 2018-07-02. See https://crrev.com/c/1122706 - - morlovich@chromium.org - - For each Read operation, whether it could have been issued in parallel of a - previous Read operation. - - - - - - Removed pre-M85. - - morlovich@chromium.org - The outcome of Entry::ReadData in the simple cache. - - - - - Removed pre-M85 - - morlovich@chromium.org - - Whether a read from stream 1 (conventionally used for payload body) was - satisfied from prefetched data. Reported only on the first read operation on - the stream (including if there are multiple readers, or even some writers). - - - - - wanderview@chromium.org - morlovich@chromium.org - - Record the outcome of the simple DiskCache consistency check after retrying - initialization on an empty cache directory. The retry may occur after - corrupt index files were deleted from an empty cache. The retry may also - occur if the original failed initialization left an empty directory without - any index files. This histogram will tell us how often the retry succeeds in - recovering caches and also which consistency checks cannot be recovered. - - - - - morlovich@chromium.org - wanderview@chromium.org - - Count of the number of entries recorded in the index, but not actually - present in the cache. Recorded each time a stale index is found and a - directory rescan is required. - - - - - morlovich@chromium.org - wanderview@chromium.org - - Count of the number of entries present in a cache, but not recorded in the - index. Recorded each time a stale index is found and a directory rescan is - required. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The quality of a "stale" index compared to a full directory - rescan. Recorded immediately after every directory scan for stale indexes. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - For each EOFRecord found with a valid magic number, indicates if the record - also contains a CRC. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The result, at the synchronous layer, of checking the EOF record of a cache - entry. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The result, at the synchronous layer, of closing a cache entry. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The platform error reported when attempting to create a new cache entry at - the synchronous layer. - - - - - - Removed pre-M85. Consider SyncCreatePlatformFileError - - morlovich@chromium.org - - The result, at the synchronous layer, reported when attempting to create a - new cache entry. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - The result of the the key SHA256 check done when opening stream 0 for each - entry. - - - - - - Replaced Dec, 2018 by SimpleCache.SyncOpenPrefetchMode. The new histogram is - an enumeration that can distinguish between full file prefetching from - trailer prefetching. - - morlovich@chromium.org - - Whether an attempt was made to prefetch the entire file when executing - disk_cache::Backend::OpenEntry. - - - - - - Removed pre-M85. - - morlovich@chromium.org - - The age of the entry (time since last modified), when opened at the - synchronous layer. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The platform error reported when attempting to create a new cache entry at - the synchronous layer. - - - - - wanderview@chromium.org - morlovich@chromium.org - - The kind of prefetching performed, if any, when executing - SimpleSynchronousEntry::ReadAndValidateStream0AndMaybe1(). - - - - - morlovich@chromium.org - wanderview@chromium.org - - The result, at the synchronous layer, reported when attempting to open a new - cache entry. - - - - - morlovich@chromium.org - wanderview@chromium.org - - The result, at the synchronous layer, of writing to a cache entry. - - - - - - Removed 2018-07-02. See https://crrev.com/c/1122706 - - morlovich@chromium.org - - Shows whether a write operation depends on the previous operation in queue - particularly in the aspect of its possibility to run in parallel. - - - - - - Replaced 2013/09/03 by WriteResult2, which adds "fast empty - return", which previously showed up as "success". - - morlovich@chromium.org - The outcome of Entry::WriteData in the simple cache. - - - - - Removed pre-M85. SyncWriteResult may be of interest. - - morlovich@chromium.org - The outcome of Entry::WriteData in the simple cache. - - - - - - alemate@chromium.org - michaelpg@chromium.org - Events in reqests processing of IP-based SimpleGeolocation. - - - - - - alemate@chromium.org - michaelpg@chromium.org - skylarc@chromium.org - - This boolean histogram counts SimpleGeolocationRequests carrying a nonzero - number of cell towers. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - - This boolean histogram counts SimpleGeolocationRequests carrying nonzero - number of WiFi access points. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - Http response codes in IP-based SimpleGeolocation. - - - - - - alemate@chromium.org - michaelpg@chromium.org - - The time elapsed between the sending of the first API request and the time - the final (failed) response was recorded. Includes all retries. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - - The time elapsed between the sending of the first API request and the time - the final (successfull) response was recorded. Includes all retries. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - Result of SimpleGeolocationRequest. - - - - - - alemate@chromium.org - michaelpg@chromium.org - Number of retries until the final response was recorded. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of stages in the pipeline while processing a single - frame on the single thread compositor, where the Main frame did not miss its - deadline. - - A Main frame that missed its deadline is a frame such that - SubmitCompositorFrame happened before a commit and activation happened. E.g. - BeginImplFrame1 -> BeginMainFrame1 -> SubmitCompositorFrame -> - BeginImplFrame2 -> Commit1 -> Activate1 -> SubmitCompositorFrame - - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - sadrul@chromium.org - graphics-dev@chromium.org - - Tracks the duration of stages in the pipeline while processing a single - frame on the single thread compositor, where the Main frame missed its - deadline. - - A Main frame that missed its deadline is a frame such that - SubmitCompositorFrame happened before a commit and activation happened. E.g. - BeginImplFrame1 -> BeginMainFrame1 -> SubmitCompositorFrame -> - BeginImplFrame2 -> Commit1 -> Activate1 -> SubmitCompositorFrame - - - - - - Removed on 9/2019. Did not provide enough information about latency. - - sadrul@chromium.org - graphics-dev@chromium.org - - The latency increase of an abnormally long activation stage on the single - thread compositor pipeline when the frame is missed. - - These latency increases are determined by comparing the stage duration to - the times from past non-missed frames. These times are also reported to - "SingleThreadedCompositorLatency.MissedFrame.<StageName>" - - - - - peconn@chromium.org - peter@chromium.org - - Logs which way had the user navigated into settings screens when they press - "Clear and Reset" button in settings of a single website. - - - - - calamity@chromium.org - dominickn@chromium.org - - The number of days between launches of an origin saved to homescreen or as a - bookmark app shortcut. Recorded at the second and each following launch of a - specific origin from a shortcut, independently per origin. - - - - - - Removed in M60. See crbug.com/712493. - - calamity@chromium.org - dominickn@chromium.org - felt@chromium.org - - The percentage of total site engagement accumulated by this profile for - HTTPS URLs as a proportion of all engagement for HTTPS and HTTP URLs. - Recorded at startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. - - - - - calamity@chromium.org - dominickn@chromium.org - - Distribution of the engagement scores accumulated by a user, recorded at - startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. - - - - - - Removed in M60. See crbug.com/712493. - - calamity@chromium.org - dominickn@chromium.org - felt@chromium.org - - Distribution of the engagement scores accumulated by a user, recorded at - startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. Limited specifically to - HTTP URLs. - - - - - - Removed in M60. See crbug.com/712493. - - calamity@chromium.org - dominickn@chromium.org - felt@chromium.org - - Distribution of the engagement scores accumulated by a user, recorded at - startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. Limited specifically to - HTTPS URLs. - - - - - - Removed in M81. - - charleszhao@chromium.org - dominickn@chromium.org - kcarattini@chromium.org - - The distribution of zero versus non-zero engagement scores accumulated by - the user, recorded at the same time as - SiteEngagementService.EngagementScore. - - - - - calamity@chromium.org - dominickn@chromium.org - - The percentage of sites on a user's profile that have engagement scores that - fall in these buckets, recorded at startup per non-incognito profile, and - then upon the first engagement-increasing event every hour thereafter. - - - - - calamity@chromium.org - dominickn@chromium.org - - The type of engagement (navigation, user input, etc.) which led to an - accumulation in site engagement. - - - - - calamity@chromium.org - dominickn@chromium.org - - The mean site engagement per origin accumulated by this profile, recorded at - startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. - - - - - calamity@chromium.org - dominickn@chromium.org - - The median site engagement per origin accumulated by this profile, recorded - at startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. - - - - - calamity@chromium.org - dominickn@chromium.org - - The total number of origins with a non-zero site engagement score for this - profile, recorded at startup per non-incognito profile, and then upon the - first engagement-increasing event every hour thereafter. - - - - - calamity@chromium.org - dominickn@chromium.org - - The number of origins which have reached the daily site engagement point - cap, recorded at startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. Thus, each bin N contains - the number of clients where at least N origins have reached the maximum - daily site engagement point cap. - - - - - calamity@chromium.org - dominickn@chromium.org - - The number of origins which have reached the absolute site engagement point - cap, recorded at startup per non-incognito profile, and then upon the first - engagement-increasing event every hour thereafter. Thus, each bin N contains - the number of clients where at least N origins have reached the maximum - absolute site engagement point cap. - - - - - - Removed in M81. - - calamity@chromium.org - dominickn@chromium.org - - The percentage of all origins recorded by the site engagement service which - have reached the absolute site engagement point cap, recorded at startup per - non-incognito profile, and then upon the first engagement-increasing event - every hour thereafter. - - - - - - Removed in M81. - - calamity@chromium.org - dominickn@chromium.org - - The site engagement score of an origin prior to applying decay. Recorded at - the first engagement event after decay, independently per decay event. - - - - - - Removed in M81. - - calamity@chromium.org - dominickn@chromium.org - - The site engagement score of an origin once decay has occured. Recorded at - the first engagement event after decay, independently per decay event. - - - - - calamity@chromium.org - dominickn@chromium.org - - The total site engagement accumulated by this profile, recorded at startup - per non-incognito profile, and then upon the first engagement-increasing - event every hour thereafter. - - - - - - Split this histogram into SiteIsolatedCodeCache.JS.Behaviour and - SiteIsolatedCodeCache.WASM.Behaviour to collect statistics for JS and WASM - code caches in separate histograms. - - mythria@chromium.org - - The behaviour of site isolated javascript code cache recorded for each cache - transaction. It records if the request was serviced and if serviced how it - was serviced for ex: hit, miss, update. - - - - - mythria@chromium.org - v8-team@google.com - - The behaviour of site isolated javascript code cache recorded for each cache - transaction. It records if the request was serviced and if serviced how it - was serviced for ex: hit, miss, update. - - - - - bbudge@chromium.org - - The behaviour of site isolated web assembly code cache recorded for each - cache transaction during WASM compilation. It records if the request was - serviced and if serviced how it was serviced for ex: hit, miss, update. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of all network responses received by a renderer. Each response is - corresponding to one URL requested by a renderer. Incremented when the first - network packet of a response of this type is received. - - - - - alexmos@chromium.org - creis@chromium.org - - The count of all current BrowsingInstances. Recorded once per UMA ping. - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - The blocking decision CORB would have made on the response, if the request - was cross-origin. Reported if the response looked sensitive under the cache - heuristic (i.e. had Cache-Control: Private and Vary: Origin response - headers). - - - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - True if the response has an Accept-Ranges header, which indicates the server - supports range requests on the resource and could be used to bypass CORB. - Only reported if the resource looked sensitive under the Cache heuristic and - was a protected MIME type. - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - The blocking decision CORB would have made on the response, if the request - was cross-origin. Reported if the response looked sensitive under the CORS - heuristic (i.e. had the Access-Control-Allow-Origin header with a value - other than * or null). - - - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - True if the response has an Accept-Ranges header, which indicates the server - supports range requests on the resource and could be used to bypass CORB. - Only reported if the resource looked sensitive under the CORS heuristic and - was a protected MIME type. - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - True if the response has a nosniff header. If the nosniff header is not - present, then CORB must have decided to block without sniffing due to a - partial response, or because the MIME type was a never sniff type. Only - reported on resources CORB would have blocked/protected without sniffing - that have a protected MIME type. - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - True if the resource was found to be sensitive by either the CORS or Cache - heuristics. Recorded for every resource CORB sees. - - - - - krstnmnlsn@chromium.org - creis@chromium.org - - True if the response has an Accept-Ranges header, which indicates the server - supports range requests on the resource. Only reported if the response - looked sensitive under the cache or CORS heuristics. - - - - - - Deprecated in March 2020; see Memory.RenderProcessHost.Count.* instead. - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - The count of all renderer processes, including WebUI and extensions. - Recorded once per UMA ping. - - - - - lukasza@chromium.org - nasko@chromium.org - - Logged when FileSystemManagerImpl::Open fails CanAccessDataForOrigin check. - The value indicates whether the requested origin came from a http/https - origin VS from another origin (possibly from a Chrome App). - - - - - - Deprecated in March 2020. For about:flags usage, see Launch.FlagsAtStartup. - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - True if the --isolate-origins mode was enabled from the command line, - about:flags, or enterprise policy. Recorded on browser startup and then once - every 24 hours. - - - - - - Deprecated in March 2020. For about:flags usage, see Launch.FlagsAtStartup. - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - True if the --site-per-process mode was enabled from the command line, - about:flags, or enterprise policy. Recorded on browser startup and then once - every 24 hours. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since site-per-process has already shipped on desktop in M67 (see - https://crbug.com/810843). - - creis@chromium.org - - The upper bound of the predicted renderer process count if we isolated all - sites, subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since site-per-process has already shipped on desktop in M67 (see - https://crbug.com/810843). - - creis@chromium.org - - The lower bound of the predicted renderer process count if we isolated all - sites, subject to the process limit. Happens to be the number of unique - sites. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since site-per-process has already shipped on desktop in M67 (see - https://crbug.com/810843). - - creis@chromium.org - - The predicted renderer process count if we isolated all sites and if there - were no process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since site-per-process has already shipped on desktop in M67 (see - https://crbug.com/810843). - - creis@chromium.org - - The predicted total process count if we isolated all sites, subject to the - process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since isolate-extensions has already shipped in M56 (see - https://crbug.com/545200). - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The upper bound of the predicted renderer process count if we isolated only - Chrome extensions, subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since isolate-extensions has already shipped in M56 (see - https://crbug.com/545200). - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The lower bound of the predicted renderer process count if we isolated only - Chrome extensions, subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since isolate-extensions has already shipped in M56 (see - https://crbug.com/545200). - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted renderer process count if we isolated only Chrome extensions - and if there were no process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77 - the histogram is no longer useful - since isolate-extensions has already shipped in M56 (see - https://crbug.com/545200). - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted total process count if we isolated only Chrome extensions, - subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The upper bound of the predicted renderer process count if we isolated only - HTTPS (not HTTP) sites, subject to the process limit. Recorded once per UMA - ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The lower bound of the predicted renderer process count if we isolated only - HTTPS (not HTTP) sites, subject to the process limit. Happens to be the - number of isolated sites. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted renderer process count if we isolated only HTTPS (not HTTP) - sites and if there were no process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted total process count if we isolated only HTTPS (not HTTP) - sites, subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The upper bound of the estimated renderer process count if we isolated no - sites, subject to the process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The lower bound of the predicted renderer process count if we isolated no - sites, subject to the process limit. Happens to be the number of isolated - sites. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted renderer process count if we isolated no sites and if there - were no process limit. Recorded once per UMA ping. - - - - - - Logging code has been removed in M77. - - creis@chromium.org - lukasza@chromium.org - site-isolation-dev@chromium.org - - The predicted total process count if we isolated no sites, subject to the - process limit. Recorded once per UMA ping. - - - - - - Deprecated in March 2020. - - alexmos@chromium.org - - The number of currently enabled isolated origins. This includes origins - specified via the --isolate-origins command-line flag as well as those - configured via enterprise policy. Recorded on browser startup. - - - - - alexmos@chromium.org - lukasza@chromium.org - - Logs whether or not a password form was submitted from a site-isolated - process that's dedicated to a single site. Recorded when a password form is - submitted. - - - - - - Code deleted in June 2020. - - rsesek@chromium.org - - The number of times a render process transitions its main thread isolate - into or out of memory savings mode. This is recorded per-renderer-process - upon the creation of the first main frame or the destruction of the last - main frame. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - nasko@chromium.org - - The count of all out-of-process iframes. Recorded once per UMA ping. - - - - - - Deprecated in March 2020. - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - Whether or not the RenderProcessHost is disqualified from process reuse - because it has a pending navigation to a URL for which SiteInstance does not - assign a site URL, such as chrome-native://newtab. This is intended to - measure how often this scenario results in spinning up extra processes. - Measured once per IsSuitableHost() invocation. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - The count of all RenderFrameProxyHosts. Recorded once per UMA ping. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - The count of RenderFrameProxyHosts in each BrowsingInstance. Recorded each - UMA ping, once per BrowsingInstance. - - - - - clamy@chromium.org - - Whether SiteInstances with a ProcessReusePolicy of - REUSE_PENDING_OR_COMMITTED_SITE could reuse an existing RenderProcessHost or - they had to create a new one. True when they reused an existing process, - false when they created a new one. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - - The number of currently saved user-triggered isolated sites. This includes - sites where the user has entered a password while using Site Isolation for - password sites (which is the target Site Isolation mode for Android). - Recorded once on browser startup. - - - - - alexmos@chromium.org - creis@chromium.org - lukasza@chromium.org - nasko@chromium.org - - The count of SiteInstances in a single BrowsingInstance. Recorded each UMA - ping, once per BrowsingInstance. - - - - - creis@chromium.org - lukasza@chromium.org - - Various actions related to cross-site document blocking in the browser - process, indicating whether the response was blocked from the renderer. - Recorded as the response is processed in the network stack. - - - - - - Removed in June 2019 / M77. Some old data have been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - The total count of responses that were would be blocked by the cross-site - document blocking logic in the browser process, but were only allowed - because the request was initiated by a content script of an extension. - Recorded with a resource type (0-17) when the response is allowed. - - Note that this histogram is not reimplemented in the NetworkService version - of Cross-Origin Read Blocking feature. This should be okay since we hope to - gather enough data before NetworkService ships. - - - - - - Removed in September 2020 / M87. (It was not needed anymore, since - CORS-for-content-scripts has successfully shipped in M85.) - - creis@chromium.org - lukasza@chromium.org - - Logs an upper bound of how many new content script requests might be blocked - if we start making them subject to CORS. We haven't yet started passing - Origin headers on these requests, so this will report true/risky even if in - the future the server might respond with a valid Access-Control-Allow-Origin - header when presented with an expected Origin request header. - - Logged when 1) CORB processes a http response (so excluding requests from - allowlisted content script and requests from extension background pages - where CORB is disabled) and 2) the request was associated with a non-http - isolated world origin (so not logging anything when the - CorbAllowlistAlsoAppliesToOorCors and OOR-CORS features are enabled since - the former feature forces ignoring the isolated world origin when OOR-CORS - is enabled) and 3) CORB allows the response (based on non-CORB-content-type - header OR sniffing decided that this is not a CORB type). - - Logs "risky" if the request would be blocked by CORS if made from - a web page (cross-origin, mode=cors, and no valid ACAO response header). - Logs "safe" otherwise. - - - - - - Removed in June 2019 / M77. Some old data have been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - The total count of responses that were blocked by the cross-site document - blocking logic in the browser process. Recorded with a resource type (0-17) - when the response is blocked; up to 1024 bytes of the response are - considered. This is also recorded with a suffix indicating the MIME type - category. - - - - - creis@chromium.org - lukasza@chromium.org - - The total count of responses that were blocked by the cross-site document - blocking logic in the browser process. Recorded with a canonical MIME type - when the response is blocked. - - - - - - Removed in June 2019 / M77. Some old data has been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - For each responses blocked by the cross-site document blocking logic in the - browser process, logs network::ResourceResponseInfo::content_length of the - response (but only if the content length value was available - if the value - was not -1). - - - - - - Removed in June 2019 / M77. Some old data has been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - For each responses blocked by the cross-site document blocking logic in the - browser process, logs whether network::ResourceResponseInfo::content_length - was available (i.e. value was 0 or greated) or not available (i.e. value was - equal to -1) if the value was available (i.e. the value was not -1). - - - - - - Removed in June 2019 / M77. Some old data have been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - The total count of responses that were blocked by the cross-site document - blocking logic in the browser process, due to the presence of a Javascript - parser-breaker pattern (like "for(;;);", or ")]}'", or a - non-empty JSON dictionary like "{\"a\":". Recorder with - a resource type (0-17) when the response is blocked; up to 1024 bytes of the - response are considered. - - - - - - Removed in June 2019 / M77. Some old data has been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - creis@chromium.org - lukasza@chromium.org - - The number of bytes of the network response buffered for sniffing purposes, - when attempting to sniff the response to determine if it should be blocked - as a cross-site document. Recorded after sniffing is attempted. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The number of bytes in the first network packet for a response with headers - that imply potential illegal cross-site access. Recorded when the first - network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having HTML - content type header and contents sniffed as HTML. Sampled with value of 1 - when the first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to their HTML contents. Sampled with value - 1 when the first network packet of a response of this type is received. - - - - - - Superseded by SiteIsolation.XSD.HTML.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.) among blocked - cross-site document responses due to their HTML contents. Sampled with a - resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.) among blocked - cross-site document responses due to their HTML contents. Sampled with a - resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to having HTML content type and nosniff - headers. Sampled with value 1 when the first network packet of a response of - this type is received. - - - - - - Superseded by SiteIsolation.XSD.HTML.NoSniffBlocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having HTML content type and nosniff - headers. Sampled with a resource type (0-14) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having HTML content type and nosniff - headers. Sampled with a resource type (0-17) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of not blocked responses despite having an HTML content type - header due to the failure of content sniffing. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses that may be parsed as JavaScript among not blocked - responses. Sampled with value 1 when the first network packet of a response - of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having JSON - content type header and contents sniffed as JSON. Sampled with value 1 when - the first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to their JSON contents. Sampled with value - 1 when the first network packet of a response of this type is received. - - - - - - Superseded by SiteIsolation.XSD.JSON.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their JSON contents. Sampled with a - resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their JSON contents. Sampled with a - resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to having JSON content type and nosniff - headers. Sampled with value 1 when the first network packet of a response of - this type is received. - - - - - - Superseded by SiteIsolation.XSD.JSON.NoSniffBlocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having JSON content type and nosniff - headers. Sampled with a resource type (0-14) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having JSON content type and nosniff - headers. Sampled with a resource type (0-17) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of not blocked responses despite having an JSON content type - header due to the failure of content sniffing. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses that may be parsed as JavaScript among not blocked - responses with a JSON content type header. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - MIME type codes for content type header values of potentially cross-site - document responses, excluding same-site or not http(s) urls. Sampled with a - MIME type code (0-4) when the first network packet of a response of this - type is received. - - - - - - Removed in May 2019. - - creis@chromium.org - lukasza@chromium.org - - Logs whether CORB blocking might have been caused by treating - |request_initiator| as opaque when |request_initiator_origin_lock| is - incompatible (as may be the case for HTML Imports). - - Logged when CORB allows or blocks a response, only when NetworkService is - enabled. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having Plain - content type header and contents sniffed as HTML. Sampled with value 1 when - the first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - responses due to their Plain.HTML contents. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Superseded by SiteIsolation.XSD.Plain.HTML.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.HTML contents. Sampled with - a resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.HTML contents. Sampled with - a resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having Plain - content type header and contents sniffed as JSON. Sampled with value 1 when - the first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to their Plain.JSON contents. Sampled with - value 1 when the first network packet of a response of this type is - received. - - - - - - Superseded by SiteIsolation.XSD.Plain.JSON.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.JSON contents. Sampled with - a resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.JSON contents. Sampled with - a resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to having Plain content type and nosniff - headers. Sampled with value 1 when the first network packet of a response of - this type is received. - - - - - - Superseded by SiteIsolation.XSD.Plain.NoSniffBlocked.RenderableStatusCode2 - in December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having Plain content type and nosniff - header. Sampled with a resource type (0-14) when the first network packet of - a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having Plain content type and nosniff - header. Sampled with a resource type (0-17) when the first network packet of - a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of not blocked responses despite having an Plain content type - header due to the failure of content sniffing. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses that may be parsed as JavaScript among not blocked - responses with a Plain content type header. Sampled with value 1 when the - first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having Plain - content type header and contents sniffed as XML. Sampled with value 1 when - the first network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to their Plain.XML contents. Sampled with - value 1 when the first network packet of a response of this type is - received. - - - - - - Superseded by SiteIsolation.XSD.Plain.XML.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with renderable HTTP status codes sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.XML contents. Sampled with - a resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with renderable HTTP status codes sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their Plain.XML contents. Sampled with - a resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of blocked cross-site document responses due to having XML content - type header and contents sniffed as XML. Sampled with value 1 when the first - network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with nonrenderable HTTP status codes among blocked - cross-site document responses due to their XML contents. Sampled with value - 1 when the first network packet of a response of this type is received. - - - - - - Superseded by SiteIsolation.XSD.XML.Blocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with renderable HTTP status codes sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their XML contents. Sampled with a - resource type (0-14) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with renderable HTTP status codes sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to their XML contents. Sampled with a - resource type (0-17) when the first network packet of a response of this - type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a nonrenderable HTTP status code among blocked - cross-site document responses due to having XML content type and nosniff - headers. Sampled with value 1 when the first network packet of a response of - this type is received. - - - - - - Superseded by SiteIsolation.XSD.XML.NoSniffBlocked.RenderableStatusCode2 in - December 2015. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having XML content type and nosniff - headers. Sampled with a resource type (0-14) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses with a renderable HTTP status code sub-categorized by - their requesting context type (e.g., image, script, etc.), among blocked - cross-site document responses due to having XML content type and nosniff - headers. Sampled with a resource type (0-17) when the first network packet - of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of not blocked responses despite having an XML content type header - due to the failure of content sniffing. Sampled with value 1 when the first - network packet of a response of this type is received. - - - - - - Removed in March 2018; in M67+, browser-process CORB policy is enabled. - - creis@chromium.org - - The count of responses that may be parsed as JavaScript among not blocked - responses with an XML content type. Sampled with value 1 when the first - network packet of a response of this type is received. - - - - - ericrk@chromium.org - The scale factor of any images drawn by Skia. - - - - ericrk@chromium.org - - Whether a call to drawBitmap(Rect) or drawImage(Rect) used the tiled or - non-tiled rasterization path. - - - - - ericrk@chromium.org - - The count of images drawn by Skia with a given filter quality. - - - - - ericrk@chromium.org - - The path taken by Skia when it attempts to lock a texture for use. - - - - - hansberry@chromium.org - better-together-dev@google.com - Records the user's sign in method choice. - - - - hansberry@chromium.org - better-together-dev@google.com - - The state Smart Lock was in when the user chose to use their password to - sign into their device. - - - - - hansberry@chromium.org - better-together-dev@google.com - Records the user's unlock method choice. - - - - hansberry@chromium.org - better-together-dev@google.com - - An enumerated histogram that breaks down what state Smart Lock was in when - the user chose to use their password to unlock their device. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Count of successful and failed attempts to sign in the Chromebook, after the - user selects their profile photo. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Shows why a sign in attempt failed during the authentication phase. Breaks - down the failure bucket of SmartLock.AuthResult.SignIn. - - - - - hansberry@chromium.org - better-together-dev@google.com - - An enumerated histogram that breaks down why the UserController could not - decrypt the account. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Count of successful and failed attempts to unlock the Chromebook, after the - user selects their profile photo. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Shows why an unlock attempt failed during the authentication phase. Breaks - down the failure bucket of SmartLock.AuthResult.Unlock. - - - - - hansberry@chromium.org - better-together-dev@google.com - - A count of the number of eligible SmartLock devices which can be used to - unlock the user's Chromebook. Logged each time the list of eligible devices - is updated. TODO(jhawkins): Log this again once we send this data from - eligible phones. - - - - - hansberry@chromium.org - better-together-dev@google.com - - A count of the number of SmartLock devices which the user has enabled to - unlock the user's Chromebook, i.e., the device connected to in the SmartLock - setup flow. Logged each time the list of eligible devices is updated. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The state of the SmartLock feature for the current user, set at login. The - value is 'enabled' if the user has successfully enabled SmartLock via setup, - disabled if the user has explicitly disabled the feature after it has been - enabled, and unset if the feature is passively disabled, i.e., has never - been enabled by the user. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The resolution of Smart Lock trying to find the host device during the - initial scan window at the signin screen. - - - - - hansberry@chromium.org - better-together-dev@google.com - - The resolution of Smart Lock trying to find the host device during the - initial scan window at the lock screen. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Count of successful and failed attempts to get the 'remote status' of the - host device, i.e., determine if the Chromebook can be signed into. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Shows why a sign in attempt failed during the connection phase. Breaks down - the failure bucket of SmartLock.ConnectionResult. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Count of successful and failed attempts to get the 'remote status' of the - host device, i.e., determine if the Chromebook can be unlocked. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Shows why an unlock attempt failed during the connection phase. Breaks down - the failure bucket of SmartLock.ConnectionResult. - - - - - hansberry@chromium.org - better-together-dev@google.com - - Indicates the feature state of the SmartLock feature. This metric is emitted - to at the creation of the user session (when the user logs in), and when - feature state updates occur. - - - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when Smart Lock successfully establishes a - secure channel connection to the host device, and receives the initial - remote status from it -- this informs if the device can be unlocked on the - first remote status (i.e., if the Smart Lock icon is yellow or green). - - Suffixed by the type of remote status which was the first to be received. - View the base histogram to see results for all remote status types - aggregated together, and suffixed histograms for the results of just that - particular remote status type. - - See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the - remote status from the host. - - - - - - Removed 2019/08. - - hansberry@chromium.org - - The duration of time between when Smart Lock successfully establishes a - secure channel connection to the host device, and receives an - "authenticated" remote status from it (i.e., the Smart Lock icon - becomes green). - - - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when the user locks their screen or wakes their - device (either opening a clamshell device or waking up a tablet), and when - the user is first provided a visible indication of Smart Lock's status (the - Smart Lock icon presents as either yellow or green, with a tooltip - explaining the status). - - Suffixed by the type of status which the user is first presented with. View - the base histogram to see results for all status types aggregated together, - and suffixed histograms for the results of just that particular remote - status type. - - See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the - remote status from the host. - - - - - - - hansberry@chromium.org - better-together-dev@google.com - - The duration of time between when Smart Lock begins to try to find the host - device, and receives the initial remote status from it -- this informs if - the device can be unlocked on the first remote status (i.e., if the Smart - Lock icon is yellow or green). - - Suffixed by the type of remote status which was the first to be received. - View the base histogram to see results for all remote status types - aggregated together, and suffixed histograms for the results of just that - particular remote status type. - - See - MultiDevice.SecureChannel.BLE.Performance.StartScanToAuthenticationDuration.Background - and - SmartLock.Performance.AuthenticationToReceiveFirstRemoteStatus.Unlock.Duration - for breakdowns of this metric. - - See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the - remote status from the host. - - - - - - Removed 2019/08. - - hansberry@chromium.org - - The duration of time between when Smart Lock begins to try to find the host - device, and receives an "authenticated" remote status from it, - which allows the device to be unlocked (i.e., the Smart Lock icon becomes - green). - - See - MultiDevice.SecureChannel.BLE.Performance.StartScanToAuthenticationDuration.Background - and SmartLock.AuthenticationToReceiveUnlockableRemoteStatus.Unlock.Duration - for breakdowns of this metric. - - See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the - remote status from the host. - - - - - jhawkins@chromium.org - better-together-dev@google.com - - The number of times the user actively enabled or disabled the SmartLock - feature via Settings. - - - - - jhawkins@chromium.org - better-together-dev@google.com - The result of the operation to disable SmartLock. - - - - - - pavely@chromium.org - src/chrome/browser/ui/messages/OWNERS - - Records the identifier of a snackbar every time one is shown. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Keeps a tally of IPC related errors between chrome_cleaner and chrome. The - first two bytes of the bucket represent the error category and the two last - bytes represent the actual error code. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time between sending the user's response to the Chrome Cleaner process - and the Cleaner process terminating. This histogram is logged only for - successfully completed runs of the cleaner. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The final status of the Chrome Cleanup Tool run (e.g. succeeded, failed, - reboot required). - - - - - - Removed as of 09/2017. Replaced with - SoftwareReporter.Cleaner.DownloadStatusErrorCode. - - joenotcharles@google.com - - The HTTP response code for the Chrome Cleanup Tool download request. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - An indication if an attempt to download the Chrome Cleanup Tool succeeded or - the reason why it failed. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The HTTP response or net error code when trying to download the Chrome - Cleanup Tool. - - - - - - Removed 07-2020 because of lack of use. - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The state of software reporter cleaner tool runs. A value of "Not - Completed" can mean either the tool crashed, or the tool was still - running when Chrome checked. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether a reboot happened since the software reporter cleaner tool has - finished execution with a pre-reboot exit code. - - - - - - Removed on 2018-01-15. - - joenotcharles@google.com - - The number of attempts to download the Chrome Cleanup tool until it either - succeeds or fails. - - - - - - Removed on 2019-05-29. - - joenotcharles@google.com - - Indicates how the user was prompted to reboot the machine to complete a run - of the Chrome Cleanup Tool. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates that the user accepted to initiate a reboot to complete a run of - the Chrome Cleanup Tool. This is logged the user starts a reboot from the - cleanup card in the Settings page. We can't track when the reboot is not - initiated, because it can happen at any moment in the future (there is no - prompt blocking the user). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - How long it took to run the software reporter cleaner tool. - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time between launching the Chrome Cleaner process and the cleaner having - scanned the user's machine and Chrome receiving an IPC call with the - results. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates if the Settings page was the active tab once a cleanup finished - with reboot required. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time between the first attempt to download the Chrome Cleanup tool and a - successful download or the last unsuccessful attempt to download without - retrying. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - The build version of the software reporter cleaner tool. - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the user accepted to upload logs from Chrome Cleanup Tool. This is - logged when the user accepts the Chrome prompt to start a cleanup either - from the prompt dialog or from the cleanup card in the Settings page. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the Chrome Cleanup Tool card in the Settings page has been shown. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates where the user started a cleanup from (e.g. from the prompt dialog - or the settings page). - - - - - bdea@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether a configuration error prevented the experimental Software Reporter - from running. - - - - - - Deprecate in M82 as the histogram is renamed to - SoftwareReporter.ConfigurationErrors. - - joenotcharles@google.com - - Whether a configuration error prevented the experimental Software Reporter - from running. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether there was an error reading the registry key containing UwS found by - the Software Removal Tool. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates when the IPC with the Chrome Cleanup Tool process is disconnected - from Chrome. Success is logged when it's disconnected and no longer needed - (the user already responded to the prompt in Chrome or the cleaner process - terminated normally); failures are logged when the IPC is disconnected, but - communication between Chrome and the cleaner process is still required (e.g. - while Chrome is waiting for scanning results or when the cleaner is waiting - for the user's response from Chrome). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - The result of the most recent SRT log upload. - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - If logs uploads are enabled in the Software Reporter or the reason why it is - disabled. Recorded before each run of the Software Reporter. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The result of the most recent Software Reporter logs upload. Written by the - Software Reporter in the registry and sent by Chrome after the reporter - finishes. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Error encountered when reading the software reporter logs upload result from - the registry. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - As SoftwareReporter.MinorVersion, but a double word combination of the other - components of the version of the software reporter. The high word is the - first component when there are more than one, and the low word is either the - second or third one, depending if there are at least 3, or 4 components. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The memory used by the software reporter tool as reported by the tool itself - via the registry. Logged just after the software reporter tool has finished. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The last component of the version of the software reporter that was executed - so we can identify when users are not getting their component updated as - quickly as we expect it. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The reason why the user has not been prompted to run the Chrome Cleanup Tool - (e.g. no unwanted software found, user recently prompted). - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of files to be deleted by the Chrome Cleanup Tool. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether an on-demand update of the Software Reporter component was needed - for a user-initiated cleanup. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether an on-demand update of the Software Reporter component succeeded, - when needed for a user-initiated cleanup. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The number of profiles whose settings will be reset once a successful - cleanup completes. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The time between the Chrome Cleaner dialog being shown and the dialog being - closed. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The user response on the modal Chrome Cleanup Tool prompt dialog (e.g. - accepted, cancelled). - - - - - - Replaced 2017-08-01 with SoftwareReporter.PromptShownWithType. - - joenotcharles@google.com - - Whether the user has been prompted to run the Chrome Cleanup Tool. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the user has been prompted to run the Chrome Cleanup Tool and which - type of prompt has been shown. - - This is logged once a prompt is presented to the user. - - - - - - Removed as of 2017-11-01. Replaced with - SoftwareReporter.PromptDialogResponse. - - joenotcharles@google.com - Usage of the Software Removal Tool (SRT) Prompt. - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - Indicates the result of a reporter sequence once it ends. - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Indicates the type of a reporter sequence run on the user system. Logged - when the sequence is scheduled to start. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The amount of time it took to run the software reporter tool as reported by - the tool itself via the registry. Logged just after the software reporter - tool has finished. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The amount of time it took for the software reporter to run as measured by - chrome. Logged just after the software reporter tool has finished. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Error encountered when reading the software reporter tool's start and end - times from the registry. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Whether the user accepted to upload scanner logs from Chrome Cleanup Tool. - This is logged when the user starts a scan for the Settings page and is only - logged for user-initiated cleanups. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The registration and execution steps for the software reporter. - - - - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - Registers when a profile is tagged for settings reset before a run of the - Chrome Cleanup Tool. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The total count of SRT log upload failures experienced by this machine for - all time. This value is reported at startup by Chrome and is capped at 64. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The longest run of upload failures logged by SRT runs. This value is - reported at startup by Chrome and is capped at 64. - - - - - - Removed 07-2020 due to lack of use - - drubery@chromium.org - chrome-safebrowsing-alerts@google.com - - The total count of successful SRT log uploads experienced by this machine - for all time. This value is reported at startup by Chrome and is capped at - 64. - - - - - ianwen@chromium.org - - Records how users interact with the special locale promotion dialog. - - - - - timvolodine@chromium.org - - Whether the Android spellchecking service was available at the start of a - new spellchecking session. Note that the user can disable the Android - spellchecking service in settings, in which case it will show up as not - available in the histogram. - - - - - timvolodine@chromium.org - - Measures the amount of time it takes to receive results from the - spellchecking service on Android. More precisely this is the - SystemClock.elapsedRealtime() between the - SpellCheckerSession.getSentenceSuggestions() and the invocation of the - onGetSentenceSuggestions() callback. - - - - - gujen@google.com - chrome-language@google.com - The percentage of misspelled words within checked words. - - - - gujen@google.com - chrome-language@google.com - The percentage of replaced words within misspelled words. - - - - groby@chromium.org - chrome-language@google.com - - Whether the user has opted in to asking Google for spelling suggestions. - Recorded both when spelling is initialized and when the preference is - changed. - - - - - yyushkina@google.com - gujen@google.com - chrome-language@google.com - - The elapsed time, in ms, between the moment the SimpleURLLoader starts - downloading the request and the moment the SimpleURLLoader callback is - invoked after the request finishes, whether an error or a success. - - - - - yyushkina@google.com - gujen@google.com - chrome-language@google.com - The HTTP code of Spelling service responses. - - - - yyushkina@google.com - gujen@google.com - chrome-language@google.com - - Describes the results returned by the Spelling service by assigning them to - one of three high-level buckets: request/service error, success with no - suggestions, and success with spelling suggestions. - - - - - gujen@google.com - chrome-language@google.com - - The percentage of replacement executions within suggestion occurrences. - - - - - gujen@google.com - chrome-language@google.com - - Counts how many languages are added to Chrome by the user but are not - supported for spell check (today Chrome only supports a hard-coded list of - locales for spell check). - - This is a measure of the potential impact of adding support for non-Hunspell - locales in the spell check settings. This also helps answer the following - question: should the Chrome spell check settings raise awareness of Windows - language packs and / or link to documentation describing how to install a - Windows language pack? - - This is recorded once during spell check initialization, and then once each - time the user changes their Chrome languages. - - - - - - Reworked as Spellcheck.Windows.ChromeLocalesSupport.NoSupport and - Spellcheck.Windows.ChromeLocalesSupport.NativeOnly in M80. - - gujen@google.com - chrome-language@google.com - - Counts how many languages are currently added to Chrome by the user but are - not eligible for spellchecking because we have no Hunspell dictionaries for - them. This is recorded once during spellcheck initialization, and then once - each time the user changes their Chrome languages. - - - - - - Reworked as Spellcheck.Windows.SpellcheckLocalesSupport.HunspellOnly and - Spellcheck.Windows.SpellcheckLocalesSupport.NoSupport in M80. - - gujen@google.com - chrome-language@google.com - - Counts how many Hunspell spellcheck locales are currently enabled by the - user but are not supported by the Windows OS spellchecker because there are - no language packs installed for them. Locales that are not supported by - Hunspell are not counted. This is recorded once during spellcheck - initialization, and then once each time the user changes which spellcheck - languages are enabled. - - - - - gujen@google.com - chrome-language@google.com - - Of all the currently enabled spell check languages, counts how many are - supported by the different spell checkers (Hunspell and the Windows OS). - - This helps measure the impact and reach of the native spell checker - integration. - - This is recorded once during spell check initialization, and then once each - time the user changes their enabled spell check languages. - - - - - gujen@google.com - chrome-language@google.com - - Measures the time it takes to perform one spell check end to end. The start - time is taken just before invoking Hunspell or the native spell checker (via - Mojo), and the end time is taken just before invoking the Blink spell check - callback. - - This is recorded every time a spell check is performed. - - - - - gujen@google.com - chrome-language@google.com - - Measures the time it takes to generate spelling suggestions when a user - right clicks a misspelled word. The start time is taken just before invoking - Hunspell for the suggestions, and the end time is taken just after the final - suggestion list is constructed. - - This is recorded every time the user opens the context menu on a misspelled - word, but only if the suggestions hadn't been pre-generated (which happens - when all spell check locales are supported by the OS spell checker). - - - - - - Moved to Sqlite.Error.AppCache in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite for the appcache db. - - - - - Removed in M74. - - costan@google.com - - Record times for INSERT/UPDATE/DELETE statements run outside of an explicit - transaction. - - - - - costan@google.com - Error which prevented database close. - - - - - Removed in M74. - - costan@google.com - Record time spent in explicit COMMIT statements. - - - - - Moved to Sqlite.Error.Cookie in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite the cookie db. - - - - - Moved to Sqlite.Error.DatabaseTracker in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite the websqldb tracker db. - - - - costan@google.com - - Annotations for which bits of sql::MetaTable::CheckDeprecated() fire. - - - - - - Moved to Sqlite.Error.DomainBoundCerts in M-27. - - Please list the metric's owners. Add more owner tags as needed. - - Error codes returned by sqlite for the domain-bound certs db. - - - - - - Moved to Sqlite.Error.DomStorageDatabase in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite for the domstorage db. - - - - costan@google.com - SQLite extended error codes. - - - - - Replaced 5/14/2013 by expanded Sqlite.Error histogram. - - Please list the metric's owners. Add more owner tags as needed. - SQLite extended SQLITE_IOERR codes for all databases. - - - - - Moved to Sqlite.Error.History in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite for the history db. - - - - costan@google.com - - SQLite memory footprint from sqlite3_memory_used() recorded 1 day after - first database is opened by sql::Database. - - - - - costan@google.com - - SQLite memory footprint from sqlite3_memory_used() recorded 1 hour after - first database is opened by sql::Database. - - - - - costan@google.com - - SQLite memory footprint from sqlite3_memory_used() recorded 1 week after - first database is opened by sql::Database. - - - - - costan@google.com - - SQLite memory footprint from sqlite3_memory_used() recorded 10 minutes after - first database is opened by sql::Database. - - - - - costan@google.com - - Time used to migrate History database schema to a new version. - - - - - costan@google.com - src/storage/OWNERS - Error which prevented database open. - - - - costan@google.com - Error from first read of the database. - - - - - Removed in M74. - - costan@google.com - Record times for all statements run against the database. - - - - - Moved to Sqlite.Error.Quota in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite for the quota db. - - - - costan@google.com - Errors attempting to Raze() database. - - - - costan@google.com - Errors on second attempt to Raze() database. - - - - costan@google.com - Errors truncating database for Raze(). - - - - costan@google.com - - SQLite error code from failed ATTACH in sql::Recovery::Init(). - - - - - costan@google.com - - Records specific failure and success cases in sql::Recovery implementation, - to determine which cases warrant further development. This histogram tracks - detected errors, some of which may cause multiple results. See recovery.cc - for details. - - - - - costan@google.com - Error from sqlite3_backup_init() in sql::Recovery. - - - - costan@google.com - Error from sqlite3_backup_step() in sql::Recovery. - - - - - Removed in M75. - - peria@chromium.org - costan@google.com - Size in kilobytes of pre-existing database at startup. - - - - - Removed in favor of Sqlite.Stats2 in M74. - - costan@google.com - Stats for different API calls in sql/. - - - - pwnall@chromium.org - - SQLite failures encountered by //sql code. Intended to be viewed using - unique user counts. SQLite errors should be caused by media failures (random - variable with fairly low probability) or bad A/V software (not random, but - hopefully low enough that we can pretend it is). - - - - - - Moved to Sqlite.Error.Text in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite the full text db. - - - - - Moved to Sqlite.Error.Thumbnail in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite for the thumbnail db. - - - - - Removed in M74. - - costan@google.com - - Record times for statements which could update the database file. Includes - commit and autocommit time. - - - - - costan@google.com - Version of pre-existing database at startup. - - - - - Removed 2018/02/06. - - shess@chromium.org - - Buffer sizes passed to browser-process SQLite VFS functions. - - - - - - Removed 2018/02/06. - - shess@chromium.org - - I/O operations measured by browser-process SQLite VFS wrapper. - - - - - - Moved to Sqlite.Error.Web in M-27. - - Please list the metric's owners. Add more owner tags as needed. - Error codes returned by sqlite the web db. - - - - - Removed 07/2017. Reference: crbug.com/708041 - - jww@chromium.org - - When resources are checked for mismatching integrity and whether the - mismatch forces a refetch. - - - - - - Removed 03/2020. Reference: crbug.com/1059826 - - carlosil@chromium.org - - When the "Learn more" link on an SSL interstitial is clicked, this - histogram records if the navigation succeded, if it failed with an - interstitial, or if it failed with a different error. - - - - - meacer@chromium.org - - Users can opt in to send reports of certificate validation errors to Google. - This records the outcome whenever Chrome sends such a report. - - Some certificate validation reports might not be received because proxies, - firewalls or other content filters might filter report uploads. - - - - - estark@chromium.org - - Users can opt in to send reports of certificate validation errors to Google. - This records the error code whenever Chrome fails to send such a report. - - - - - - Removed as of 07/2016. Replaced with SSL.ExpectCTReportFailure2. - - estark@chromium.org - - Sites can opt in to Expect CT, a reporting feature that sends a report - whenever a TLS connection does not have valid Certificate Transparency - information associated with it. This records the error code when Chrome - fails to send an Expect CT report. - - - - - estark@chromium.org - - Sites can opt in to Expect CT, a reporting feature that sends a report - whenever a TLS connection does not have valid Certificate Transparency - information associated with it. This records the error code when Chrome - fails to send an Expect CT report. - - - - - estark@chromium.org - - Sites can opt in to Expect CT, a reporting feature that sends a report - whenever a TLS connection does not have valid Certificate Transparency - information associated with it. This metric fires whenever Chrome attempts - to send an Expect CT report. - - - - - estark@chromium.org - - Keeps track of various insecure content events, such as loading an HTTP - script from an HTTPS page. - - - - - - Removed December 2017 (M65). This information in this histogram can be found - in LoginCustomFlags (for users who have set a flag) or by filtering to users - with the MarkHttpAs feature enabled (for seeing the field trial breakdown). - - estark@chromium.org - felt@chromium.org - - Reports whether the user has selected to mark HTTP origins with an - experimental UI treatment (such as showing a warning on HTTP pages that - collect sensitive information). This histogram is recorded whenever the - security level (the overall security state of a page, roughly corresponding - to the lock icon) is computed for an HTTP page. - - - - - - Removed 09/2016 and replaced with SSL.MarkHttpAsStatus. - - palmer@chromium.org - - Reports whether the user has selected to mark non-secure origins as Neutral - (the status quo), Dubious, or Non-Secure. - - - - - carlosil@chromium.org - Tracks when mixed content is displayed or run. - - - - carlosil@chromium.org - estark@chromium.org - - Tracks when mixed content is loaded from a "non-webby" URL, e.g. - an external protocol. The security of such URLs is unknown, but they are - exempt from mixed content UI treatment because they don't usually return - data to the browser. This histogram tracks how often such content is loaded - so that we can decide whether to block such resources unless an enterprise - policy is enabled. - - - - - msarda@chromium.org - - Number of accounts available for Single Sign On with the current device, - recorded at the time the SSO Promo is shown. - - - - - msarda@chromium.org - - Action the user takes when the Single Sign On promotion is shown. - - - - - msarda@chromium.org - - Number of times the promotion has been seen on the current device. - - - - - boliu@chromium.org - ssid@chromium.org - - Records the reverse rank of a child process when it is killed by android if - applicable. Chrome on Android ranks some child processes and provides hints - to android that it should kill from lowest to highest ranked. The lowest - ranked process has reverse rank 0. This is a measure how good the hints to - android are; if hints were perfect, then all android kills should have - reverse rank 0. - - - - - boliu@chromium.org - ssid@chromium.org - - Getting value for OomKillReverseRank may fail. Recorded when an applicable - child process is killed by android. - - - - - - Removed in M60. Roughly 50% of Chrome startups that had *any* pending - minidumps had at least one pending minidump without any logcat output. About - 5% had multiple minidumps without any logcat output. - - isherman@chromium.org - - The number of un-uploaded minidumps present in the Android Crash Reports - directory. Each minidump file (should) correspond to a crash. This is - recorded on startup, just prior to initiating uploading for these minidumps. - This is intended as a temporary metric, to be removed around M60: - http://crbug.com/699785 - - - - - - Removed in M60. Roughly 50% of Chrome startups that had *any* pending - minidumps had at least one pending minidump without any logcat output. About - 5% had multiple minidumps without any logcat output. - - isherman@chromium.org - - The number of un-uploaded minidumps present in the Android Crash Reports - directory that do not yet have logcat output attached. Each minidump file - (should) correspond to a crash. This is recorded on startup, just prior to - initiating uploading for all pending minidumps. This is intended as a - temporary metric, to be removed around M60: http://crbug.com/699785 - - - - - boliu@chromium.org - - Individual enum counts specific conditions of child process terminations. - There are too many individual states to enumerate into a single histogram, - so this effectively does the aggregration that normally happens on the - server side in the client instead. The benefit is this is easily extensible - in the future, and downside is that it does not allow additional server side - analysis. Note a single child process termination may fall into multiple - enums. - - - - - - Removed 04/2019 as we no longer record it in favour of the two variants - below. - - mheikal@chromium.org - smaier@chromium.org - wnwen@chromium.org - - Records the number of minidumps processed by Crashpad, split by process - type. This metric is similar to one that could be computed server-side based - on received crash uploads; but the client-side metric also includes any - minidumps that were not successfully uploaded. - - - - - mheikal@chromium.org - smaier@chromium.org - wnwen@chromium.org - - Records the number of non-simulated minidumps processed by Crashpad, split - by process type. This metric is similar to one that could be computed - server-side based on received crash uploads; but the client-side metric also - includes any minidumps that were not successfully uploaded. - - - - - mheikal@chromium.org - smaier@chromium.org - wnwen@chromium.org - - Records the number of simulated minidumps processed by Crashpad, split by - process type. This metric is similar to one that could be computed - server-side based on received crash uploads; but the client-side metric also - includes any minidumps that were not successfully uploaded. - - - - - wnwen@chromium.org - - Counts renderer crashes including OOMs. Android only. Mirrors old stability - proto renderer crashes. - - - - - boliu@chromium.org - ssid@chromium.org - - Record the state of child service bindings left when a child service with - strong binding is OOM killed by Android. Recorded when such a OOM kill is - detected by browser. Note this does not distinguish process type, and is for - example recorded for both GPU and renderer process. - - - - - boliu@chromium.org - ssid@chromium.org - - Record the count of strongly bound child services left when a child service - with strong binding is OOM killed by Android. Recorded when such a OOM kill - is detected by browser. Note this does not distinguish process type, and is - for example count both GPU and renderer process. - - - - - creis@chromium.org - jamescook@chromium.org - - Count of processes killed by chrome/browser because they sent an IPC that - couldn't be properly handled. Categories are the reasons (code locations) - for the kills. - - - - - jam@chromium.org - jamescook@chromium.org - - Count of child processes killed because they sent an IPC that couldn't be - properly handled. Categories are the reasons (code locations) for the kills. - - - - - jamescook@chromium.org - - Count of extension processes killed because they sent an IPC that couldn't - be properly handled. Categories are the reasons (code locations) for the - kills. - - - - - mcnee@chromium.org - - Count of processes killed because they sent a bad IPC that couldn't be - properly handled. Categories are the reasons (code locations) for the kills. - - - - - creis@chromium.org - jamescook@chromium.org - - Count of processes killed because they sent a NaCl IPC that couldn't be - properly handled. Categories are the reasons (code locations) for the kills. - - - - - creis@chromium.org - jamescook@chromium.org - - Count of processes killed because they sent a bad IPC that couldn't be - properly handled. Categories are the reasons (code locations) for the kills. - - - - - - - siggi@chromium.org - chrome-stability-core@google.com - - Records the exit code of the browser process (on Windows) from the previous - launch. On crash, the exit code will indicate the exception code of the - crash. This is emitted in stability data with the first report on a - subsequent launch. Note: Due to https://crbug.com/805754, the enum labels - for RESULT_CODE_* are off by 1 for M56 and earlier. - - - - - alexmos@chromium.org - boliu@chromium.org - lukasza@chromium.org - - Logs the reason that a crashed subframe was shown. Logged at most once per - crash, and only if the subframe was hidden when it crashed and became - visible later. - - - - - alexmos@chromium.org - boliu@chromium.org - - Logs whether or not a tab is marked for reload when a cross-process subframe - crashes. Logged once per subframe process crash. - - - - - alexmos@chromium.org - boliu@chromium.org - - Logs the visibility of a subframe when a subframe process crashes and the - corresponding tab is marked for reload. This indicates whether the crashed - subframe was visible or scrolled out of view at the time of crash. - - - - - alexmos@chromium.org - boliu@chromium.org - lfg@chromium.org - lukasza@chromium.org - - Logged after detecting that a sad subframe is shown (logged at most once per - crash). - - - - - - Removed 04/2020 (data for go/site-isolation-stability has been collected - long time ago; nobody on chrome-stability@ spoke in defense of this - histogram). - - lukasza@chromium.org - - The age of a crashed extension process. Not logged on iOS. Logged together - with CrashExitCodes.Extension. - - - - - - Removed 04/2020 (data for go/site-isolation-stability has been collected - long time ago; nobody on chrome-stability@ spoke in defense of this - histogram). - - lukasza@chromium.org - - The age of a crashed extension process. Not logged on iOS. Logged together - with CrashExitCodes.Renderer. - - - - - siggi@chromium.org - - Temporary instrumentation to record the Windows browser's exit path. See - http://crbug.com/412384. - - - - - rkaplow@chromium.org - chrome-metrics-team@google.com - - Collects various counters related to stability. The majority of them are - crash types. - - - - - siggi@chromium.org - - Number of times stability data was discarded. This is accumulated since the - last report, even across versions. This is logged during stability metric - recording for the following log sent. - - - - - michaelbai@chromium.org - src/base/metrics/OWNERS - - The number of the unsent files at the time the stability recorded. - - - - - michaelbai@chromium.org - src/base/metrics/OWNERS - - The total number of samples that will be lost if ASSOCIATE_INTERNAL_PROFILE - isn't enabled since the previous stability recorded. This is different than - the previous browser run because one file was just uploaded before the - stability is recorded. - - - - - siggi@chromium.org - - Number of times the initial stability log upload was deferred to the next - startup. This is logged during stability metric recording for the following - log sent. - - - - - siggi@chromium.org - - Number of times a browser crash was detected, where the browser was last - known to be alive in a Windows system session that terminated abnormally. - - - - - siggi@chromium.org - - Number of times the version number stored in prefs did not match the - serialized system profile version number. This is logged during stability - metric recording. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - Number of kilobytes available for "important" data. When an iOS - device is critically low on space, actions generally assumed to succeed can - fail. In extreme cases, this could potentially include writing the - "unclean shutdown" bit to signal a clean shutdown. Logged on - application launch if the last session terminated in an unclean state. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - The last known battery charge before a crash occurred. This will only be - logged for devices which were last known to be in the "unplugged" - state because the intention is to identify devices which may have died - leading to unexpected terminations. Logged on application launch if the last - session terminated in an unclean state. - - - - - - Removed 09/2019 after having collected enough data. - - eugenebut@chromium.org - olivierrobin@chromium.org - - Recorded when Chrome for iOS attempts to create a config for synthetic crash - report. Used to debug the feature, which suppose to upload synthetic crash - report using Breakpad. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - The thermal state of the device when a crash occured. Logged on application - launch if the last session terminated in an unclean state. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - Indicates whether or not one of the Stability.iOS.UTE.* metrics could - explain the cause of the UTE which terminated the previous session. Logged - on application launch if the last session terminated in an unclean state. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - The power mode of the device when a crash occurred. Logged on application - launch if the last session terminated in an unclean state. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - Recorded when app starts after Unexplained Termination Event (UTE) or - Explained Termination Event (XTE). Values other than Active indicate that - prefs::kLastSessionExitedCleanly was not properly stored. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - sdefresne@chromium.org - - Recorded when app starts after Unexplained Termination Event (UTE) or - Explained Termination Event (XTE). UTEs/XTEs can be caused by large memory - allocations and this histogram provides information which memory heavy - operation has being performed before UTE/XTE. - - - - - eugenebut@chromium.org - michaeldo@chromium.org - - true if OS was restarted after the previous session. Logged on application - launch if the last session terminated in an unclean state. If this is false - then UTE was not caused by OS restart or shutdown. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - Logged on the session following a crash with the result of a comparison - between the OS version of the session which crashed and the current OS - version. Logged on application launch if the last session terminated in an - unclean state. - - - - - michaeldo@chromium.org - olivierrobin@chromium.org - - The estimated amount of time between when a crash occurred and when the user - relaunched the application. Logged on application launch if the last session - terminated in an unclean state. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - Type of the shutdown. This histogram is recorded at startup and logs a - sample for the previous session. A clean shutdown is one where the app - enters the background before being killed. Other shutdowns are all some sort - of crash. The absence of a crash log indicates that the app was killed by - the OS, normally due to memory pressure. If memory pressure is extremely - high, the app may not have had a chance to response to a memory warning - before being killed. For first launch after upgrade, the crash reports may - be discarded before this histogram is written to so it's not possible to - determine if there's a valid crash log present or not. - - - - - dtapuska@chromium.org - - If the renderer is considered unresponsive from the browser's perspective - before the process is terminated. This metric is being used to figure out - crash reports that have all idle threads and perhaps the process is being - terminated when it shouldn't be. crbug.com/615090. - - - - - - Removed 5/2019 after having collected enough data to analyze jank. - - chengx@chromium.org - wittman@chromium.org - - Amount of time taken to deserialize all pending call stack profiles. - - - - - charliea@chromium.org - wittman@chromium.org - - The number of sample metadata item slots used after successfully setting a - metadata item. This count reflects both active and inactive metadata items. - - - - - - Removed 11/2018 as we no longer record this metric. - - chengx@chromium.org - wittman@chromium.org - - Amount of time taken to deserialize a call stack profile string. - - - - - - Removed 11/2018 as we no longer record this metric. - - chengx@chromium.org - wittman@chromium.org - Amount of time taken to serialize a call stack profile. - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the bookmarks bar view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the depth of a folio when it is selected in the clipper. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the number of folios visible when a folio is selected in the clipper. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of folios when the clipper is opened. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the folio view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips with Google related urls (points to internal Google - resources). Logs every time user goes to chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips with Google related urls within first 20 (points to - internal Google resources). Logs every time user goes to chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips with images. Logs every time user goes to - chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips with images within first 20. Logs every time user goes - to chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when a bookmark is launched from the - bookmarks bar view. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when a bookmark is launched from the folio - view. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when a bookmark is launched from the search - view. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when a bookmark is launched from the smart - group view. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when a bookmark is launched from the - timeline view. - - - - - - Removed 01/2020 as we no longer record this metric. - - lpromero@chromium.org - - Logs every time a bookmark is launched from an assortment of different UI - surfaces with Stars, the new bookmarks UI. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips without images or snippets. Logs every time user goes to - chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Percentage of clips without images or snippets within first 20. Logs every - time user goes to chrome://bookmarks. - - - - - - Removed 01/2020 as we no longer record this metric. - - yefim@chromium.org - - Logs number of bookmark nodes every time stars extension is loaded. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the profile view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - jbbegue@chromium.org - - Count the actions performed by the user on the stars promo panel currently - only on android and ios. - - - - - - Removed 01/2020 as we no longer record this metric. - - lpromero@chromium.org - - A boolean that indicates if a salient image was found for a displayed - bookmark. It is recorded every single time a bookmark is displayed. That - way, this histogram shows the proportion of bookmarks the user sees with an - image. This is used only with Stars, the new bookmarks UI. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the search view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the smart group view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - - Logs the approx number of clips when the timeline view is activated. - - - - - - Removed 01/2020 as we no longer record this metric. - - accamed@google.com - Logs the extension version the user is using. - - - - michaeln@chromium.org - - The number of after-startup tasks that were queued prior to startup - completion and deferred until that time. - - - - - michaeln@chromium.org - - Time from the process creation until deferred after-startup tasks began - running. - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records whether or not the cached Feed visibility in the SharedPreferences - is consistent with the Feed visibility user preference on the disk. It's - recorded when overview mode is shown because of Return to Tab Switcher, and - only on cold start. By recording this histogram, the number of mismatches - between the criteria of whether the Feed placeholder of Instant Start - pre-native is shown and the criteria of whether Feed articles after native - initialization are shown is recorded. - - - - - pasko@chromium.org - alexilin@chromium.org - - Android: The time from the activity creation point to the first contentful - paint of the first loaded page. It's not recorded when the first loaded page - is non http(s) page like a chrome error page, a new tab page, a blank page. - It's also not recorded if the application wasn't in the foreground since the - start till the end of event. - - - - - pasko@chromium.org - alexilin@chromium.org - - Android: The time from the activity creation point to the moment the first - navigation is committed, i.e. when renderer gets the first byte of the - document. It's not recorded when the first loaded page is non http(s) page - like a chrome error page, a new tab page, a blank page. It's also not - recorded if the application wasn't in the foreground since the start till - the end of event. - - - - - - This metric was deprecated in M68 in favour of - "Startup.Android.Cold.TimeToFirstContentfulPaint.Tabbed". It has - moved out of experimental and records a smaller range of numbers (medium - times instead of long times). The ".Tabbed" suffix is added since - the histogram is being tracked for WebApkActivity using the - ".WebApk" suffix. - - pasko@chromium.org - alexilin@chromium.org - - Android: The time from the activity creation point to the first contentful - paint of the first loaded page. It's not recorded when the first loaded page - is non http(s) page like a chrome error page, a new tab page, a blank page. - It's also not recorded if the application wasn't in the foreground since the - start till the end of event. - - - - - - This metric was deprecated in M68 in favour of - "Startup.Android.Cold.TimeToFirstNavigationCommit.Tabbed". It has - moved out of experimental and records a smaller range of numbers (medium - times instead of long times). The ".Tabbed" suffix is added since - the histogram is being tracked for WebApkActivity using the - ".WebApk" suffix. - - pasko@chromium.org - alexilin@chromium.org - - Android: The time from the activity creation point to the moment the first - navigation is committed, i.e. when renderer gets the first byte of the - document. It's not recorded when the first loaded page is non http(s) page - like a chrome error page, a new tab page, a blank page. It's also not - recorded if the application wasn't in the foreground since the start till - the end of event. - - - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records the time duration from a cold start till the Feeds articles are - first loaded on the StartSurface. This histogram is only recorded when - StartSurface is shown at launch due to "return to tab switcher" - feature. - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records the time duration from a cold start till the Feeds loading - placeholder is shown on the StartSurface. This placeholder is only shown - when the feature flag InstantStart is enabled and StartSurface is shown at - launch due to "return to tab switcher" feature. - - - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records the time duration from a cold start till the Feeds stream is created - on the StartSurface. This histogram is only recorded when StartSurface is - shown at launch due to "return to tab switcher" feature. - - - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records the time duration from a cold start till the first draw completes. - - - - - mthiesse@chromium.org - yfriedman@chromium.org - - Measures the amount of time startup has likely been delayed due to GURL - waiting on the native library to be initialized. - - - - - - - hanxi@chromium.org - spdonghao@chromium.org - wychen@chromium.org - - Records the time duration from a cold start till the title of the single Tab - is shown on the StartSurface. This histogram is only recorded when - StartSurface is shown at launch due to "return to tab switcher" - feature. - - - - - skyostil@chromium.org - - Android: Whether or not creation of a profile lead to the - StartupTabPreloader speculatively created a tab. Recorded when a profile is - created, assuming a StartupTabPreloader has been constructed for intents - with a url and either regular Chrome or a Custom Tab will be loaded. - - - - - skyostil@chromium.org - - Android: Whether or not a tab speculatively created by the - StartupTabPreloader was subsequently adopted by ChromeTabCreator. Recorded - when a tab is loaded, assuming a StartupTabPreloader has been constructed - for intents with a url for either regular Chrome or a Custom Tab will be - loaded. - - - - - yusufo@chromium.org - yfriedman@chromium.org - - Android: The number of thumbnails fetched for the first meaningful paint of - the Grid Tab Switcher. First meaningful paint is defined as having all the - thumbnails shown. This is recorded at most once per activity lifecycle. This - is gated by feature "TabSwitcherOnReturn". - - - - - yusufo@chromium.org - yfriedman@chromium.org - - Android: The elapsed time from the activity creation point to the first - meaningful paint of the Grid Tab Switcher. First meaningful paint is defined - as having all the thumbnails shown. This is recorded at most once per - activity lifecycle. This is gated by feature - "TabSwitcherOnReturn". - - - - - yusufo@chromium.org - yfriedman@chromium.org - - Android: The elapsed time from the activity creation point to the first - meaningful paint of the Grid Tab Switcher. First meaningful paint is defined - as having all the thumbnails shown. This is recorded at most once per - activity lifecycle. This is gated by feature - "TabSwitcherOnReturn". It's only recorded on cold startup. - - - - - yusufo@chromium.org - yfriedman@chromium.org - - Android: The elapsed time from the activity creation point to the first - meaningful paint of the Grid Tab Switcher. First meaningful paint is defined - as having all the thumbnails shown. This is recorded at most once per - activity lifecycle. This is gated by feature - "TabSwitcherOnReturn". It's only recorded on warm startup. - - - - - - Removed 03/2018 with Mash AppList refactoring. - - tapted@chromium.org - - Time for a newly created browser process to perform the first paint of the - app launcher, when started with the --show-app-list flag and with no - currently running Chrome processes. - - - - - - Removed 03/2018 with Mash AppList refactoring. - - tapted@chromium.org - - Time for a running browser process to perform the first paint of the app - launcher. Measured from the time a second Chrome process started, which sent - its --show-app-list command line argument to the already-running process and - will soon exit. - - - - - mark@chromium.org - crashpad-dev@chromium.org - - The amount of time that elapsed during in - crash_report::BlockUntilHandlerStarted(). - - - - - peter@chromium.org - - Records the cause, each time Chrome is brought to the foreground. Currently - only checks if a NotificationUIManager notification was shown in the last 5 - seconds (includes Web Notifications, but not media or Cast). - - - - - - Removed as of 02/2020. - - rkaplow@chromium.org - - Measured when Chrome is invoked, this counts the number of URLs passed via - command line. Note that this handles the case of a URL passed to Chrome - starting up, or when a running Chrome is given the message to open a new - URL. - - - - - robliao@chromium.org - - The amount of time that elapsed during BrowserMainRunnerImpl::Initialize. - - - - - robliao@chromium.org - - The amount of time that elapsed during the first section of - BrowserMainRunnerImpl::Initialize. - - - - - robliao@chromium.org - - The amount of time that elapsed during the second section of - BrowserMainRunnerImpl::Initialize. - - - - - - Removed 01/2020. Data is not used. - - fdoray@chromium.org - - Time from the ChromeMain() entry in the browser process to the first - RendererMain() entry. - - - - - - Removed 2/2018, as MessageLoopStart is after MainNavigationStart with - browser-side navigation. - - asvitkine@chromium.org - - Time between Startup.BrowserMessageLoopStartTime and - Startup.FirstWebContents.MainNavigationStart. Recorded explicitly to allow - easy breakdown of Startup.FirstWebContents.MainNavigationStart when - diagnosing issues. - - - - - asvitkine@chromium.org - - Time between Startup.BrowserMessageLoopStartTime and - Startup.FirstWebContents.NonEmptyPaint2. Recorded explicitly to allow easy - breakdown of Startup.FirstWebContents.NonEmptyPaint2 when diagnosing issues. - - - - - - - chrisha@chromium.org - fdoray@chromium.org - - The number of hard faults incurred in the browser process from startup to - start of the main thread's message loop, not including first runs of the - browser. - - - - - - Removed 1/2016. - - chrisha@chromium.org - - The number of hard faults incurred in the browser process from startup to - start of the main thread's message loop on first run. This is only reported - on Windows 7 and greater. - - - - - - Removed 12/2015. No longer tracked because values collected on stable show - that the function pretty much never fails (succeeds 99.9996% of the time). - - chrisha@chromium.org - fdoray@chromium.org - - If OS support was detected (Windows 7 and greater) indicates whether it was - possible to determine the number of hard faults that have occurred in the - process from startup to start of the main thread's message loop. This can - fail because the underlying call is inherently racy. - - - - - - - fdoray@chromium.org - gab@chromium.org - - Time from application start to the start of the main thread's message loop. - Not recorded for first run. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - - fdoray@chromium.org - gab@chromium.org - - Time from application start to the start of the main thread's message loop. - Recorded for a first run of the browser. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - Removed 12/2016. crbug.com/634408 - - fdoray@chromium.org - gab@chromium.org - - Time from main entry to the start of the main thread's message loop. This - stat is only recorded after 7 minutes of OS uptime to try to mitigate the - variance resulting from Chrome being autostarted. Replaced with - Startup.BrowserMessageLoopStartTimeFromMainEntry2 which is recorded all the - time. - - - - - - Removed 12/2016. crbug.com/634408 - - fdoray@chromium.org - gab@chromium.org - - Time from main entry to the start of the main thread's message loop on first - run. This stat is only recorded after 7 minutes of OS uptime to try to - mitigate the variance resulting from Chrome being autostarted. Replaced with - Startup.BrowserMessageLoopStartTimeFromMainEntry.FirstRun2 which is recorded - all the time. - - - - - - Removed 01/2020. Replaced with Startup.BrowserMessageLoopStartTime.FirstRun. - - fdoray@chromium.org - gab@chromium.org - - Time from main entry to the start of the main thread's message loop on first - run. - - - - - - Removed 2018-01 in favor of - Startup.BrowserMessageLoopStartTimeFromMainEntry3 which does not involve a - conversion from Time to TimeTicks. - - fdoray@chromium.org - gab@chromium.org - - Time from main entry to the start of the main thread's message loop. - - - - - - Removed 01/2020. Startup.BrowserMessageLoopStartTime has similar data. - - fdoray@chromium.org - gab@chromium.org - - Time from main entry to the start of the main thread's message loop. - - - - - - Removed 01/2020. Data is not used. - - fdoray@chromium.org - - Time taken to open the initial tab or to restore tabs from previous session. - - - - - rkaplow@chromium.org - - The amount of time that elapsed during - BrowserProcessImpl::PreMainMessageLoopRun. - - - - - sebmarchand@chromium.org - mblsha@yandex-team.ru - - Time from application start to the time the first Browser window has - finished painting its children. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - sebmarchand@chromium.org - mblsha@yandex-team.ru - - Time from application start to the time the GPU has finished compositing - after first Browser window has finished painting its children. At this point - the Browser interface is visible on screen. Measures how much time does it - take for GPU to actually paint the first time. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - - fdoray@chromium.org - gab@chromium.org - - Time from application start to the time the browser window initially becomes - visible. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - Removed 7/2015. To be replaced with Cast events. - - jeremy@chromium.org - - The elapsed time from the ChromeCast application launch to the first video - frame displayed. - - - - - djean@chromium.org - eugenebut@chromium.org - - The duration of all initializations from process creation time to UI ready. - This includes code loading, static initializers and the execution time - contained in Startup.ColdStartWithExternalURLTime and - Startup.ColdStartWithoutExternalURLTime metrics. iOS specific. - - - - - jif@chromium.org - - The duration of all initializations in a cold start triggered by an external - URL. - - - - - jif@chromium.org - - The duration of all initializations in a cold start not triggered by an - external URL. - - - - - - - fdoray@chromium.org - gab@chromium.org - - How long it takes to load the original profile synchronously on the UI - thread. - - - - - - Removed in M-41. - - erikchen@chromium.org - - An experimental metric only collected on the dev and canary channels. - Measure the elapsed time from process launch to the first main frame load of - the first web contents. Uses significantly more buckets, with reduced - ranges. - - - - - - Moved to Startup.FirstWebContents.MainFrameLoad in M-41. - - erikchen@chromium.org - - An experimental metric only collected on the dev and canary channels. - Measure the elapsed time from process launch to the first main frame load of - the first web contents. Uses standard bucket ranges. - - - - - - Removed in M-41. - - erikchen@chromium.org - - An experimental metric only collected on the dev and canary channels. - Measure the elapsed time from process launch to the first non-empty paint of - the first web contents. Uses significantly more buckets, with reduced - ranges. - - - - - - Moved to Startup.FirstWebContents.NonEmptyPaint in M-41. - - erikchen@chromium.org - - An experimental metric only collected on the dev and canary channels. - Measure the elapsed time from process launch to the first non-empty paint of - the first web contents. Uses standard bucket ranges. - - - - - - Replaced by Startup.FirstCommitNavigationTime2 - - pasko@chromium.org - - [Android only] The time from the earliest entry point in the browser process - to the moment the first navigation is committed, i.e. when renderer gets the - first byte of the document. - - - - - - Replaced with Startup.FirstCommitNavigationTime3 on 6/2017 - - pasko@chromium.org - wnwen@chromium.org - - [Android only] The time from the first foreground entry point in the app to - the moment the first navigation is committed, i.e. when renderer gets the - first byte of the document. - - - - - - Replaced with Startup.Android.Experimental.Cold.TimeToFirstNavigationCommit - on 11/2017 - - pasko@chromium.org - wnwen@chromium.org - - [Android only] The time from the first foreground entry point in the app to - the moment the first navigation is committed, i.e. when renderer gets the - first byte of the document. - - - - - - - fdoray@chromium.org - gab@chromium.org - - [Desktop] The reason for which startup profiling was deemed complete. Logged - once per session on startup. - - - - - - Removed with 3/2016 with M48. - - erikchen@chromium.org - gab@chromium.org - - [Desktop] DEPRECATED (but kept as a known basis until M48 is phased out). - Measure the elapsed time from process launch to the first main frame load of - the first web contents. Deprecated in favor of - Startup.FirstWebContents.MainFrameLoad2 which now avoids counting ill-cases - (ref. FirstWebContentsProfiler::FinishReason). - - - - - - Removed with M77. Startup.FirstWebContents.NonEmptyPaint3 is a better - indicator of startup time as perceived by users. - - fdoray@chromium.org - gab@chromium.org - - [Desktop] Measure the elapsed time from process launch to the first main - frame load of the first web contents. Only comprised of cases where the - initial foreground tab gets to complete its rendering task unimpeded (an - improvement over Startup.FirstWebContents.MainFrameLoad). - - - - - - - fdoray@chromium.org - gab@chromium.org - - [Desktop] Measure the elapsed time from application start to the moment when - the navigation is committed (first bytes received) in the first web - contents' main frame. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - - fdoray@chromium.org - gab@chromium.org - - [Desktop] Measure the elapsed time from application start to the beginning - of navigation in the first web contents' main frame. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - Removed with 3/2016 with M48. - - erikchen@chromium.org - gab@chromium.org - - [Desktop] DEPRECATED (but kept as a known basis until M48 is phased out). - Measure the elapsed time from process launch to the first non- empty paint - of the first web contents. Deprecated in favor of - Startup.FirstWebContents.NonEmptyPaint2 which now avoids counting ill-cases - (ref. FirstWebContentsProfiler::FinishReason). - - - - - - Replaced with Startup.FirstWebContents.NonEmptyPaint3 on 06/2020, which uses - application start time instead of process creation time to reduce noise. - - fdoray@chromium.org - gab@chromium.org - chrome-analysis-team@google.com - - [Desktop] Measure the elapsed time from process launch to the first non- - empty paint of the first web contents. Only comprised of cases where the - initial foreground tab gets to complete its rendering task unimpeded (an - improvement over Startup.FirstWebContents.NonEmptyPaint). - - This histogram is of special interest to the chrome-analysis-team@. Do not - change its semantics or retire it without talking to them first. - - - - - - - etiennep@chromium.org - fdoray@chromium.org - gab@chromium.org - chrome-analysis-team@google.com - - Measure the elapsed time from the application start to the first non empty - paint of the first web contents. Only comprised of cases where the initial - foreground tab gets to complete its rendering task unimpeded (an improvement - over Startup.FirstWebContents.NonEmptyPaint). - - Application start is a time recorded as early as possible in the startup - process. On Android, the application start is the time at which the Java - code starts. On Windows, application start is when chrome.exe:main starts, - before chrome.dll is loaded. On other platforms, it is when - ChromeMainDelegate is constructed. - - - - - hans@chromium.org - - Time between RenderFrameHostImpl::Init and - Startup.FirstWebContents.NonEmptyPaint2. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the execution time for a single task to execute on UI if - it was not possible to execute UI tasks under 1/60s within certain limits, - after WebContents was painted at least once. This is recorded at most once - per Chrome launch. Used as a measure of responsiveness on startup. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the elapsed time for a single task to execute on UI if it - was not possible to execute it under 1/60s within certain limits, 10 second - after first WebContents was painted at least once. This is recorded at most - once per Chrome launch. Used as a measure of responsiveness on startup. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the elapsed time for a single task to execute on UI if it - was not possible to execute it under 1/60s within certain limits, 1 second - after first WebContents was painted at least once. This is recorded at most - once per Chrome launch. Used as a measure of responsiveness on startup. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the elapsed time it takes for a task to execute on UI - under 1/60s after first WebContents was painted at least once. This is - recorded at most once per Chrome launch. Used as a measure of responsiveness - on startup. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the elapsed time it takes for a task to execute on UI - under 1/60s, 10 second after the first WebContents was painted. This is - recorded at most once per Chrome launch. Used as a measure of responsiveness - on startup. - - - - - - Removed 10/2015. - - gayane@chromium.org - - [Desktop] Measures the elapsed time it takes for a task to execute on UI - under 1/60s, 1 second after the first WebContents was painted. This is - recorded at most once per Chrome launch. Used as a measure of responsiveness - on startup. - - - - - - Removed 7/2015. To be replaced with Cast events. - - jeremy@chromium.org - - The elapsed time from the Fling application launch to the first video frame - displayed. - - - - - - Removed 12/2011. Merged into MobileSessionStartType. - - jeremy@chromium.org - Whether a startup is a resume (vs a cold start). - - - - - - fdoray@chromium.org - etiennep@chromium.org - gab@chromium.org - - Time from the application start to the C++ ChromeMain() function being - invoked. - - - - - - Removed 12/2016. crbug.com/634408 - - fdoray@chromium.org - gab@chromium.org - - Time from the main() function in chrome.exe to chrome.dll's main(). This - stat is only recorded after 7 minutes of OS uptime to try to mitigate the - variance resulting from Chrome being autostarted. Replaced with - Startup.LoadTime.ExeMainToDllMain2 which is recorded all the time. - - - - - - Removed 03/2020. Replaced with Startup.LoadTime.ApplicationStartToChromeMain - which applies to most platforms. - - fdoray@chromium.org - gab@chromium.org - - Time from the main() function in chrome.exe to chrome.dll's main(). - - - - - - - fdoray@chromium.org - etiennep@chromium.org - gab@chromium.org - - Time from the process creation to application start, i.e. time recorded as - early as possible in the startup process. - - - - - - Removed 12/2016. crbug.com/634408 - - fdoray@chromium.org - gab@chromium.org - - Time from the process creation to chrome.dll's main(). This stat is only - recorded after 7 minutes of OS uptime to try to mitigate the variance - resulting from Chrome being autostarted. Replaced with - Startup.LoadTime.ProcessCreateToDllMain2 which is recorded all the time. - - - - - - Removed 03/2020. Replaced with - Startup.LoadTime.ProcessCreateToApplicationStart which applies to most - platforms. - - fdoray@chromium.org - gab@chromium.org - Time from the process creation to chrome.dll's main(). - - - - - Removed 12/2016. crbug.com/634408 - - fdoray@chromium.org - gab@chromium.org - - Time from the process creation to executing the main() function in - chrome.exe. This stat is only recorded after 7 minutes of OS uptime to try - to mitigate the variance resulting from Chrome being autostarted. Replaced - with Startup.LoadTime.ProcessCreateToExeMain2 which is recorded all the - time. - - - - - - Removed 03/2020. Now covered by - Startup.LoadTime.ProcessCreateToApplicationStart and - Startup.LoadTime.ApplicationStartToChromeMain. - - fdoray@chromium.org - gab@chromium.org - - Time from the process creation to executing the main() function in - chrome.exe. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The action requested on the application startup when called from another app - or the OS. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - The calling application (if any). - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - -[AppControllerMac awakeFromNib]. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - -[AppControllerMac didFinishLaunching:]. At that point, the dock icon will - finish its current animation and stop bouncing. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - ChromeBrowserMainPartsMac::PostMainMessageLoopStart. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - ChromeBrowserMainPartsMac::PostProfileInit. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - ChromeBrowserMainPartsMac::PreMainMessageLoopStart. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - ChromeBrowserMainPartsMac::PreProfileInit. - - - - - erikchen@chromium.org - - The amount of time that elapsed between main entry and the invocation of - -[AppControllerMac willFinishLaunching:]. - - - - - rkaplow@chromium.org - - The amount of time that elapsed during - ChromeBrowserMainParts::PreMainMessageLoopRunImpl. - - - - - - Removed as of 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the first untracked section of - ChromeBrowserMainParts::PreMainMessageLoopRunImpl. - - - - - - Removed as of 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the second untracked section of - ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android. - - - - - - Removed as of 7/2019. - - rkaplow@chromium.org - - The amount of time that elapsed during the third untracked section of - ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android. - - - - - - Removed as of 2/2015. - - rkaplow@chromium.org - - The amount of time that elapsed during - ChromeBrowserMainParts::PreMainMessageLoopRunImpl. - - - - - - Removed 8/2019. See startup_metric_utils.cc for a summary of old data. - - fdoray@chromium.org - gab@chromium.org - - The number of startups the current version has been through. Reported once - per Chrome session, on startup. Any user that reports X for this version - will also have previously reported [1,X-1] for this version through the - previous X-1 Chrome sessions. - - - - - - Removed 2018-03. - - tapted@chromium.org - - Time for a newly created browser process to reach the code that starts - showing the app launcher, when started with the --show-app-list flag and - with no currently running Chrome processes. - - - - - - Removed 2018-03. - - tapted@chromium.org - - Time for a running browser process to reach the code that starts showing the - app launcher. Measured from the time a second Chrome process started, which - sent its --show-app-list command line argument to the already-running - process and will soon exit. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to load bookmarks from disk. This measurement is only sent for - startups that take >10 seconds after an uptime of 7 minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to finish initialization of the extension service including - loading built-in extensions. This measurement is only sent for startups that - take >10 seconds after an uptime of 7 minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time the final stages of profile initialization taking including - initialization of profile keyed services. This measurement is only sent for - startups that take >10 seconds after an uptime of 7 minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to load the NSS libraries and initialize it. This measurement - is only sent for startups that take >10 seconds after an uptime of 7 - minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to load preferences from disk. This measurement is only sent - for startups that take >10 seconds after an uptime of 7 minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to initialize the ProfileIOData object - this includes - initialization of the cookie store. This measurement is only sent for - startups that take >10 seconds after an uptime of 7 minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to load the safe browsing database from disk. This measurement - is only sent for startups that take >10 seconds after an uptime of 7 - minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes to initialize the safe browsing service. This measurement is - only sent for startups that take >10 seconds after an uptime of 7 - minutes. - - - - - - Removed 06/2015. - - jeremy@chromium.org - - Time it takes for session restore to finish initiating creation of restored - tabs and windows. This measurement is only sent for startups that take - >10 seconds after an uptime of 7 minutes. - - - - - - Removed 02/2015. Startup.StartupBrowserCreator_Start is more useful. - - rkaplow@chromium.org - - The amount of time that elapsed during - StartupBrowserCreator::ProcessCmdLineImpl. - - - - - rkaplow@chromium.org - - The amount of time that elapsed during StartupBrowserCreator::Start(). - - - - - - Remove 01/2020. Data is no longer used. - - fdoray@chromium.org - - The time elapsed between system boot and Chrome browser process launch. This - is recorded just before the main message loop starts. - - - - - - - chrisha@chromium.org - fdoray@chromium.org - - Indicates whether or not the given startup was warm, cold or unable to be - determined. This is based off observing the number of hard faults that occur - during startup prior to Startup.BrowserMessageLoopStartTime. The threshold - for cold startup was updated Jan 2020, a bump in the metric is expected. - - - - - - Removed 06/2019. - - feuunk@chromium.org - - The time of day in GMT that the startup was performed. This is logged in - HHMM format, with the minutes rounded down to the nearest 10 minute - interval. - - This can be used to make traffic estimates for requests made from startup. - - - - - - Removed 08/2019. See startup_metric_utils.cc for a summary of old data. - - fdoray@chromium.org - - Time elapsed since the last startup that went up to the main message loop - start. This is recorded just before the main message loop starts. - - - - - - Removed 01/2020. The data is no longer used. - - fdoray@chromium.org - - Time for a running browser process to start processing the command line - passed in by a second Chrome process, which just sent its command line - arguments to the already-running process and will soon exit. Measured from - the time the second Chrome process started. - - - - - pbos@chromium.org - robliao@chromium.org - - Time from application start until the first web footer finishes painting. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - pbos@chromium.org - robliao@chromium.org - - Time from application start until the first WebView used to display a web - footer is created. - - April 8, 2020: Changed the reference from process creation to application - start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of - application start. - - - - - - Removed as of 10/2014. - - dschinazi@chromium.org - src/net/OWNERS - - Time duration measured from the time the startup timebomb was started and - when it went off. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - This is recorded for every site that the user blacklists when they when they - clear browsing data. It indicates which signals were used to show the given - site to the user that the user then chose to exclude from clearing. - - - - - mek@chromium.org - dmurph@chromium.org - enne@chromium.org - - Recorded when an error occurs in the BlobUrlLoader, which is used to load - blobs from urls in the Renderer. - - - - - mek@chromium.org - dmurph@chromium.org - - If a newly constructed blob is broken. See Storage.Blob.BrokenReason for a - the broken reasons. - - - - - mek@chromium.org - dmurph@chromium.org - - The reason a blob is broken, reported only for broken blobs upon - construction. See Storage.Blob.Broken for the breakdown of blobs broken vs - unbroken. - - - - - mek@chromium.org - - The result of constructing a blob using the BlobRegistry.RegisterFromStream - API. - - - - - mek@chromium.org - dmurph@chromium.org - - Recorded when the old blob storage directories are cleared. This occurs on - storage partition initialization, and is not recorded if there are no - directories to clear. The value indicates if the file operations were a - success. - - - - - - No longer relevant. There are almost never any failures. - - dmurph@chromium.org - - Recorded when we create the blob storage directory for the blob storage - system. When we need to write blob data to files, we create this directory - if it doesn't exist. We write blob data to files when either we have a new - blob that's larger than our memory limit, or we're approaching our in-memory - limit for blob storage. - - - - - - Removed as of 3/2016. Use Storage.Blob.Broken to see the fraction of blobs - that are broken, and Storage.Blob.BrokenReason for the number of broken - blobs that are broken because of memory constraints. - - dmurph@chromium.org - - True if a created blob exceeded the internal in-memory storage memory limit - for blobs. - - - - - mek@chromium.org - dmurph@chromium.org - - Recorded when an error occurs in the FileReaderLoader, which is used to load - blobs in the Renderer. FileReaderUser is mostly used for Javascript's - 'FileReader', but can also be used to read blobs for the IndexedDB - renderer-side implementation. For the read error category, see - Storage.Blob.FileReaderLoader.ReadError for a breakdown of the specific read - error reasons. - - - - - mek@chromium.org - dmurph@chromium.org - - The error code reported by the blob system while trying to read a blob in - the FileReaderLoader. Compare with the - Storage.Blob.IDBRequestLoader.ReadError histogram to eliminate IndexedDB - large-value blobs. - - - - - mek@chromium.org - - The amount of time taken to complete the synchronous - BlobRegistry.GetBlobFromUUID mojo call. - - - - - mek@chromium.org - dmurph@chromium.org - - The error code reported by the blob system while trying to read an IndexedDB - large-value blob in the IDBRequestLoader. These blobs are automatically - created in Blink when a website writes a large value to IndexedDB. - - - - - mek@chromium.org - dmurph@chromium.org - - Counts the number of times we have an invalid refcount operation. An invalid - increment means the blob didn't exist, and an invalid decrement means we - don't have any record of the blob in our host. - - - - - mek@chromium.org - dmurph@chromium.org - - Counts the number of times we have an invalid url registration operation. An - invalid increment means the blob isn't in use by the host yet or the url is - already mapped. An invalid decrement means the url isn't registered. - - - - - - Removed as of 12/18. Metric wasn't used for anything and wasn't useful. - - dmurph@chromium.org - - The number of blob items in a blob, recorded at blob construction. (Blobs - are immutable, so this won't change afterwards). - - - - - - Removed as of 12/18. Use Storage.Blob.MaxDiskSpace2 instead. - - dmurph@chromium.org - - Records the calculated max disk space the blob storage system can use. - Recorded on storage partition initialization. - - - - - mek@chromium.org - dmurph@chromium.org - - Records the calculated max disk space the blob storage system can use. - Recorded on storage partition initialization, and only if the disk is - enabled. - - - - - mek@chromium.org - dmurph@chromium.org - - Recorded when the blob system changes adjustment types on its disk size. The - disk can either be Frozen, Adjusted (near min external available disk - space), or Normal. We record when we transition between these states, which - can happen after any file operations in the blob system (paging data to disk - or saving a new blob directly to disk). - - - - - mek@chromium.org - dmurph@chromium.org - - Size of a page file created for blob data by the blob storage system. - Recorded before we create the file and write the blob items. We page blob - data to files when we get close to our maximum blob memory usage. - - - - - mek@chromium.org - dmurph@chromium.org - - Recorded when we disable paging blobs to file in the blob storage system. - This occurs when we experience a filesystem error during writing blob data - to disk. We write blob data to files when either we have a new blob that's - larger than our memory limit, or we're approaching our in-memory limit for - blob storage. The relevant error is recorded here. - - - - - mek@chromium.org - dmurph@chromium.org - - The amount of time taken to complete the synchronous mojo call - BlobRegistry.Regsiter - - - - - mek@chromium.org - dmurph@chromium.org - - The amount of time taken to complete the synchronous mojo call - BlobURLStore.Register IPC. - - - - - mek@chromium.org - dmurph@chromium.org - - Whether seeking within a file (in order to write a part of a blob) failed in - the renderer. - - - - - mek@chromium.org - dmurph@chromium.org - - Whether writing part of a blob to a file failed in the renderer. - - - - - mek@chromium.org - dmurph@chromium.org - - True if we reuse an item for a blob created from using Blob.slice, recorded - in BlobStorageContext on blob creation. - - - - - ssid@chromium.org - mek@chromium.org - Records the total size of in-memory blobs evicted to disk. - - - - - Not an accurate way to measure the normal max blob usage. - - dmurph@chromium.org - - Records the total in-memory storage size of blobs before a blob item is - appended. Can be subtracted by Storage.Blob.StorageSizeBeforeAppend to find - the true distribution of blob storage sizes. - - - - - - Not an accurate way to measure the normal max blob usage. - - dmurph@chromium.org - - Records the total in-memory storage size of blobs before a blob item is - appended. Can be subtracted from Storage.Blob.StorageSizeAfterAppend to find - the true distribution of blob storage sizes. - - - - - mek@chromium.org - dmurph@chromium.org - - The total in-memory size in KB of finished blobs. Recorded in - BlobStorageContext when the blob is finished being created. This can include - memory that is shared with other blobs or memory from repeated internal - items. - - - - - mek@chromium.org - dmurph@chromium.org - - The total amount of unique memory used to create a blob. Recorded in - BlobStorageContext when the blob is finished being created. This does not - include memory that is shared with other blobs. If multiple of the same blob - item is present, then this number will reflect the size of the single item. - - - - - - Removed on 12/18. Metric wasn't used for anything and wasn't useful. - - dmurph@chromium.org - - The size in KB of items (or parts of items) appended to blobs. - - - - - - Removed on 12/18. Metric wasn't used for anything and wasn't useful. - - dmurph@chromium.org - - The size in KB of items (or parts of items) appended to blobs that come from - the slicing of other blobs. This happens when using Blob.slice, where we are - using a part of an item in the original blob (not the whole item). - - - - - mek@chromium.org - dmurph@chromium.org - - True if the file size on blob append is unknown (which means the full file), - or false if a specific file length was populated. Recorded in - BlobStorageContext when we are adding a file item to a blob. - - - - - - Removed on 12/18. Metric was always false. - - dmurph@chromium.org - - True if the file size of a filesystem object on blob append is unknown - (which means the full file), or false if a specific file length was - populated. Recorded in BlobStorageContext when we are adding a filesystem - item to a blob. - - - - - - Removed in 2020-04. - - mek@chromium.org - chrome-owp-storage@google.com - The number of bytes read. Recorded on each read. - - - - - Removed in 2020-04. - - mek@chromium.org - chrome-owp-storage@google.com - The number of bytes written. Recorded on each write. - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - When a user chooses to blacklist one or more sites when they clear browsing - data, this is recorded for every reason each chosen site was marked as - important. It indicates which signals were used to show the given site to - the user that the user then chose to exclude from clearing. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - This records the number of reasons each important site had that the user - chose to blacklist when clearing browsing data. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - When a user chooses to blacklist one or more sites when they clear browsing - data, this is recorded for every reason each unchosen site was marked as - important. It indicates which signals were used to show the given site to - the user, which the user then ignored and did not select to blacklist from - clearing data. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - This records the number of reasons each important site had that the user - chose to NOT blacklist when clearing browsing data. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - Recorded when we generate a list of important sites. This can happen when - the user opens the Clear Browsing Data dialog on Android, views the Storage - tab in Site Settings on Android, or launches 'Manage Storage' from Android - System Settings for Chrome. We record every reason each site was chosen in - this metric. This means that we can report this metric multiple times for a - single site. - - - - - dmurph@chromium.org - chrome-owp-storage@google.com - - This records the number of reasons qualifying a site for being 'important'. - We record this for every site when we generate a list of important sites, - described in "Storage.ImportantSites.GeneratedReason". - - - - - dmurph@chromium.org - pwnall@chromium.org - - The time it takes to generate the list of 'important' sites. This list is - generated when the user enters the 'Clear Browsing Dialog' or the 'Manage - Space' screens for Chrome, both of which are on Android. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the size of a blob used in an IndexedDB add/put operation. Recorded - for every put operation that contains a blob. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records if a blob intended to be used in an IndexedDB add/put operation is a - valid blob. Recorded for every put operation that contains a blob. - - - - - - No longer emitted. - - dmurph@chromium.org - mek@chromium.org - - Records if a blob attempted to be written to IndexedDB used the - base::CopyFile optimization. Recorded for every blob attempted to be written - to IndexedDB. - - - - - jarrydg@chromium.org - chrome-owp-storage@google.com - - How did the user interact with the StoragePressure Bubble? Ignored means the - user did not click on the positive button before the bubble is closed - (either manually closed or when the browser closes). - - - - - - Removed 2019-02, no longer used. - - futhark@chromium.org - - Microseconds spent in StyleSheetContents::ParseAuthorStyleSheet. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - futhark@chromium.org - - Microseconds spent in StyleEngine::InvalidateStyle. Only samples from high - resolution timers are recorded. - - - - - - Removed 07/2018, no longer used. - - csharrison@chromium.org - - Tracks % of lazy rules that ended up needing to be parsed. A sheet logs - counts into this histogram as it is parsed (i.e. as properties are parsed - lazily). Once a certain percent of rules have been parsed, we log a count - immediately. Note that this implies that a stylesheet which uses all of its - rules will log counts in every bucket. - - - - - futhark@chromium.org - - Microseconds spent in RebuildLayoutTree called from Document::UpdateStyle. - - - - - futhark@chromium.org - - Microseconds spent in RecalcStyle called from Document::UpdateStyle. - - - - - - Removed 07/2018, no longer used. - - csharrison@chromium.org - - Tracks the total number of rules that have parsing lazily deferred in an - author style sheet. - - - - - - Removed 07/2018, no longer used. - - csharrison@chromium.org - - Tracks the total number of rules that have parsing lazily deferred in an - author style sheet, for sheets that ended up needing all their rules. - - - - - - Removed 07/2018, replaced by Style.RecalcTime and - Style.RebuildLayoutTreeTime. - - futhark@chromium.org - - Microseconds spent in Document::UpdateStyle. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed June 2018 in favor of SubresourceFilter.Actions2 - - csharrison@chromium.org - - Counts of various UI and user action events related to the - SubresourceFilter. This will be triggered in response to Content Settings - changes, as well as when portions of the UI are shown or interacted with. - Main frame navigations are also tracked for ease of comparison and analysis. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Counts of various UI and user action events related to the - SubresourceFilter. This will be triggered when portions of the UI are shown - or interacted with. - - - - - - Removed April 2019 - - csharrison@chromium.org - jkarlin@chromium.org - - Logs the delay the ad delay throttle added to a request. Logged for every - subresource request that was delayed. - - - - - - Removed April 2019 - - csharrison@chromium.org - jkarlin@chromium.org - - Logs the expected delay the ad delay throttle added to a request. This is - the delay imposed assuming no task queuing delay. Logged for every - subresource request that was delayed. - - - - - - Removed April 2019 - - csharrison@chromium.org - jkarlin@chromium.org - - Logs the task queuing delay the ad delay throttle added to a request. This - is the actual delay minus the expected delay. Logged for every subresource - request that was delayed. - - - - - - Removed July 2018. Replaced with Ads.Features.AdResourceIsIsolated. - - csharrison@chromium.org - jkarlin@chromium.org - - For a given ad request, logs information related to whether it is isolated - from the top-level context. Logged per ad subresource request. - - - - - - Removed July 2018. Replaced with Ads.Features.ResourceIsSecure. - - csharrison@chromium.org - jkarlin@chromium.org - - For a given request, logs information related to whether it is marked as an - ad, and whether it is secure (e.g. https). Logged per subresource request. - - - - - pkalinnikov@chromium.org - - Records how much thread CPU time it takes to decide whether subresource - filtering should be activated for a main frame or subframe. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - pkalinnikov@chromium.org - - Records how long it takes to decide whether subresource filtering should be - activated for a main frame or subframe. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed July 2019. - - csharrison@chromium.org - - Records the total time the activation state navigation throttle within a - document is delayed while calculating activation. Recorded at resume time. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed July 2019. - - csharrison@chromium.org - - Records the total time the activation state navigation throttle within a - main frame document is delayed while calculating activation. Recorded at - resume time. - - - - - engedy@chromium.org - - Whenever a document load is committed in a main frame or subframe, records - whether subresource filtering should be activated for that load. - - - - - - Expired in M77, then deprecated in July 2019. - - engedy@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total number of subresource - loads that have been disallowed. This only differs from `MatchedRules` when - filtering is performed in dry-run mode. - - - - - - Expired in M77, then deprecated in July 2019. - - engedy@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total number of subresource - loads that have been evaluated. This only differs from 'Total' when the - document is subject to a deactivating rule with DOCUMENT activation type. - - - - - - Expired in M78, then deprecated in July 2019. - - engedy@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total number of subresource - loads that have matched filtering rules. This only differs from `Disallowed` - when filtering is performed in dry-run mode. - - - - - - Expired in M77, then deprecated in July 2019. - - engedy@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total number of subresource - loads that have gone through the subresource filtering pipeline. - - - - - engedy@chromium.org - - Whenever a document load is committed in a main frame or subframe and - subresource filtering should be activated, records whether the filtering - rules are available. - - - - - csharrison@chromium.org - - Records the total time a subframe navigation was delayed while calculating - whether it should be disallowed or not. Logged for all navigations that were - allowed. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in August 2019. Replaced by SubframeFilteringDelay.Disallowed2. - - csharrison@chromium.org - - Records the total time a subframe navigation was delayed while calculating - whether it should be disallowed or not. Logged for all navigations that were - disallowed or would be disallowed. - - - - - csharrison@chromium.org - justinmiron@google.com - - Records the total time a subframe navigation was delayed while calculating - whether it should be disallowed or not. Logged for all navigations with the - disallowed load policy. - - - - - csharrison@chromium.org - justinmiron@google.com - - Records the total time a subframe navigation was delayed while calculating - whether it should be disallowed or not. Logged for all navigations with the - would_disallow load policy. - - - - - - Removed in July 2019. - - pkalinnikov@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total thread CPU time spent on - processing subresource requests in allowLoad. - - Note: this histogram is emitted for all clients, both ones which have - high-resolution timer available and those which don't. - - - - - - Removed in July 2019. - - pkalinnikov@chromium.org - - Whenever a document load is finished in a main frame or subframe with - subresource filtering activated, records the total real time spent on - processing subresource requests in allowLoad, including the time spent on - waiting or being descheduled. - - Note: this histogram is emitted for all clients, both ones which have - high-resolution timer available and those which don't. - - - - - pkalinnikov@chromium.org - - The total CPU time it took to parse and index all rules. Does not include - time when the indexing thread was not doing actual work, e.g. waiting for - I/O or being descheduled. Recorded every time the RulesetService kicks off a - ruleset indexing process. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - The number of rules that could be not be successfully indexed and therefore - have been ignored. Recorded every time the RulesetService kicks off a - ruleset indexing process and it reaches the point where rules are getting - indexed. - - - - - ericrobinson@chromium.org - csharrison@chromium.org - - The result of the IndexRulesetMatcher Verify method. Either pass if both the - checksum and verifier succeeded, or a value indicating which combination of - them failed. Note that a zero checksum indicates that the checksum has not - yet been stored during indexing (for rulesets indexed prior to the - checksumming code). - - - - - - Removed in favor of the Verify2 metric - - csharrison@chromium.org - - The total time it took to verify the indexed ruleset in the browser process. - Logged every time verification occurs, which usually occurs when the first - page with activation is navigated to. - - - - - csharrison@chromium.org - - The total time it took to verify the indexed ruleset in the browser process. - Logged every time verification occurs, which usually occurs when the first - page with activation is navigated to. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - The total time it took to read and index all rules. Includes I/O time for - reading the unindexed rules, but not for writing the indexed ruleset. - Recorded every time the RulesetService kicks off a ruleset indexing process. - - - - - alexmt@chromium.org - jkarlin@chromium.org - - Whenever a document load is committed in the main frame, records whether the - filtering rules are available. This is independent of whether or not - subresource filtering should be activated. - - - - - csharrison@chromium.org - - Records how much thread CPU time it takes to decide whether subresource - filtering should be activated for a main frame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in favor of SubresourceFilter.PageLoad.Activation.RedirectPosition2 - - ericrobinson@chromium.org - - For pages that trigger Safe Browsing activations (not including dry runs), - records the position in the redirect chain for the page the activation was - triggered by. If SubresourceFilterConsiderRedirects is disabled, then always - returns "Only navigation". - - - - - ericrobinson@chromium.org - csharrison@chromium.org - - For pages that match a given subresource_filter activation list, records the - position in the redirect chain of the latest non-NONE list. - - - - - csharrison@chromium.org - - Records how long it takes to decide whether subresource filtering should be - activated for a main frame. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Records the policy decision to activate subresource filtering for a page - load. 'Activated' indicates that subresource filtering was activated. All - other reasons indicate that subresource filtering was not activated. - - - - - csharrison@chromium.org - - The ActivationList or NONE that the main frame navigation matched with. - Recorded at WillProcessResponse time for a main frame navigation. - - - - - csharrison@chromium.org - - Whenever a document load is committed in a main frame, records whether - subresource filtering should be activated for that load. - - - - - - Metric is broken and will be replaced by - ContentSettings.Popups.StringBlocked.NumBlocked. This only logged values for - sites which are also activated for subresource filtering, when most sites - will probably only be marked for popup blocking. - - csharrison@chromium.org - - Records the number of popups blocked per page load due to subresource filter - logic. Recorded when a new main frame navigation commits. Note that this - histogram is recorded for all pages which are activated by the subresource - filter, including ones which do not trigger the stronger popup blocker. - - - - - - Removed in favor of SubresourceFilter.PageLoad.ActivationList. - - melandory@chromium.org - - Records, for each main frame navigation, whether the last URL in the - redirect chain matched the Safe Browsing blacklist specified by the - histogram suffix. - - - - - - Removed May 2018 in favor of SubresourceFilter.PageLoad.ActivationDecision - - csharrison@chromium.org - - Logged when the first resource is disallowed from a page with forced - activation. For example, if the devtools ad blocking option is set. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total number of subresource loads that have been disallowed. - This only differs from `MatchedRules` when filtering is performed in dry-run - mode. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total number of subresource loads that have been evaluated. This - only differs from 'Total' when some of subdocuments is subject to a - deactivating rule with DOCUMENT activation type. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total number of subresource loads that have matched filtering - rules. This only differs from `Disallowed` when filtering is performed in - dry-run mode. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total number of subresource loads that have gone through the - subresource filtering pipeline. - - - - - - Removed May 2018 - - melandory@chromium.org - - Total number of server redirects during the navigation. This histogram is - recorded in several for every list where subresource fiter is active. - - - - - - Obsolete as of April 2017, since the don't have correct data to record - anymore. - - melandory@chromium.org - - For each main frame navigation, records a pattern that indicates which URLs - in the redirect chain matched Safe Browsing blacklists, and which did not. - For example, for the redirect chain A-B-C-D metric tracks: 1. If initial URL - (A) was on a Safe Browsing blacklist. 2. If any if middle urls (B, C) were - on a Safe Browsing blacklist. 3. If committed URL (B) was on a Safe Browsing - blacklist. This histogram is recorded in several flavours: with prefix - SubresourceFilterOnly in case the redirect chain contains url from the Safe - Browsing SubresourceFilter list and without the prefix for all other - redirect chains. - - - - - csharrison@chromium.org - - The navigation delay imposed by the subresource filter on a given navigation - due to Safe Browsing checks. - - - - - - Removed in May 2018 (M69). We have enough data to show that the redirect - speculations we do are necessary, especially for Android. - - csharrison@chromium.org - - The navigation delay that would have been imposed by the subresource filter - on a given navigation due to Safe Browsing checks if redirect speculation - was removed. Removing this feature would cause more delay if a navigation - has redirects. - - - - - pkalinnikov@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total thread CPU time spent on evaluating subresource requests, - aggregated across all frames. - - Note: this histogram is emitted for all clients, both ones which have - high-resolution timer available and those which don't. - - - - - pkalinnikov@chromium.org - - Whenever a page load is finished with subresource filtering activated, - records the total real time spent on evaluating subresource requests, - aggregated across all frames. This includes the time spent on waiting or - being descheduled. - - Note: this histogram is emitted for all clients, both ones which have - high-resolution timer available and those which don't. - - - - - - Removed in favor of the whitelisted bucket in SubresourceFilter.Actions2 - - melandory@chromium.org - - Number of times the user has requested a reload for the page by clicking on - the reload button. - - - - - - Removed in favor of SubresourceFilter.Action - - melandory@chromium.org - - Number of times Safebrowsing Subresource Filter decided to toggle visibility - of the prompt. - - - - - yaoxia@chromium.org - - Records the ruleset verification status at some point in a browsing session. - If AdTagging is disabled, this happens when the user first visits a site - that is failing the Better Ads Standard, and gets ads blocked on that site; - if AdTagging is enabled, this happens immediately on startup. Note that this - is recorded only once per browsing session (the lifetime of the browser - process). - - - - - - Removed in May 2018 in favor of the more general - SB2.RemoteCall.CheckDispatchTime. - - csharrison@chromium.org - - The microseconds it took to dispatch the Safe Browsing check. This includes - IPC descheduling delays to communicate with SafetyNet on Android, and - synchronous db checks on desktop. - - Note: this histogram is emitted for all clients, both ones which have - high-resolution timer available and those which don't. - - - - - - Removed in May 2019 in favor of the TotalCheckTime variant. - - csharrison@chromium.org - - The time an individual Safe Browsing URL check took before finishing. Logged - when a check is complete or cancelled due to a timeout. - - - - - csharrison@chromium.org - ericrobinson@chromium.org - - The time an individual Safe Browsing URL check took before finishing, - including posting tasks to and from the IO thread. Measured on the UI - thread. - - - - - pkalinnikov@chromium.org - - Whenever a subresource of a document is evaluated against the ruleset, - records the thread CPU time spent on calculating whether it should be - allowed to load. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - pkalinnikov@chromium.org - - Whenever a subresource of a document is evaluated against the ruleset, - records how much time was spent on calculating whether it should be allowed - to load. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - csharrison@chromium.org - jkarlin@chromium.org - - Records the exact error whenever writing a ruleset fails at the step where - the ruleset would be moved from the scratch directory to its final location. - - - - - ericrobinson@chromium.org - csharrison@chromium.org - - Whether indexing a version of the ruleset and writing it to disk succeeded, - or failed at a particular step. Recorded every time the RulesetService kicks - off a ruleset indexing process. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records the duration that the subresource redirect feature was stopped due - to fetch failure. When such a redirected fetch times out or fails with 503 - (loadshed failure), subresource redirect is disabled for subsequent - pageloads for a random duration or duration mentioned in the Retry-After - response header. Recorded for each fetch failure. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The server response code of an attempt to compress an image subresource. The - initial redirect to the compression server will always be logged as a - HTTP_TEMPORARY_REDIRECT, in addition to logging the return code from the - compression server. - - - - - robertogden@chromium.org - tbansal@chromium.org - - Whether or not the request to the compression server succeeded at the - network layer. Records true if there was no error at the network layer, - otherwise false. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Recorded whenever the subresource redirect times out, and leads to a random - bypass of 1-5 minutes. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The bytes of data saved from the SubresourceRedirect. Recorded every time a - SubresourceRedirect returns with a 200 HTTP response code. - - - - - robertogden@chromium.org - tbansal@chromium.org - - The percent of data saved from the SubresourceRedirect. Recorded every time - a SubresourceRedirect returns with a 200 HTTP response code. - - - - - rajendrant@chromium.org - src/components/data_reduction_proxy/OWNERS - - Records the user interaction with the HTTPS Image compression notification - InfoBar. Recorded when the one-time InfoBar is shown. - - - - - rajendrant@chromium.org - mcrouse@chromium.org - - Records whether the subresource redirect was bypassed or not for a pageload. - Recorded once per pageload. - - - - - mathp@chromium.org - - The counts of network error codes encountered by SuggestionsService when an - attempt to fetch suggestions from the server fails. - - - - - mathp@chromium.org - - The counts of HTTP response codes encountered by SuggestionsService when - attempting to fetch suggestions from the server. - - - - - mathp@chromium.org - - The latency of a SuggestionsService fetch that results in a success - response. - - - - - siggi@chromium.org - - Number of URLs present in the Suggestions local blacklist when the - Suggestions service is created. - - - - - mathp@chromium.org - - The counts of response states (such as empty or invalid) encountered by - SuggestionsService when attempting to fetch suggestions from the server. - - - - - - Long removed. - - aberent@chromium.org - - Time to get the response to requesting whether a URL should be accessible to - the supervised user, when Chrome was not previously running. - - - - - - Long removed. - - aberent@chromium.org - - Time to get the response to requesting whether a URL should be accessible to - the supervised user, when Chrome was already running. - - - - - - Long removed. - - aberent@chromium.org - - True if a request to find out whether a URL should be accessible to a - supervised user timed out. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Records supervised users trying to enable or disable extensions. Enabled - count increments when the supervised user successfully enables an extension. - Disabled count increments when the supervised user successfully disables an - extension. Enable attempt failed count increments when the parent has turned - off the "Permissions for sites, apps and extensions" toggle and - the supervised user tries to enable an extension that requires custodian - approval or has a permissions increase. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Records the actions of supervised users on the Extension Install Dialog. - Opened count increments when the supervised user tries to install an - extension from the Chrome Web Store and launches the Extension Install - Dialog. Asked Parent count increments when the supervised user clicks - "Ask a parent". Child Canceled count increments when the - supervised user clicks "Cancel". - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Measures the amount of time in milliseconds for the child user to click the - "Ask a parent" button on the Extension Install Dialog. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Measures the amount of time in milliseconds for the child user to click the - "Cancel" button on the Extension Install Dialog. - - - - - - Renamed to SupervisedUsers.Extensions2 in M84. - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Records the progress of supervised users as they try to install Chrome - extensions. New extension approval granted count increments when the - custodian initially grants approval to install the extension. New version - approval granted count increments when the supervised user approves a newer - version of an existing extension. Removed count increments when the - supervised user removes an extension. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Records the progress of supervised users as they try to install Chrome - extensions. Extension Approval Granted count increments when the custodian - initially grants approval to install the extension. Permissions Increase - Granted count increments when the supervised user approves a newer version - of an existing extension with increased permissions. Extension Approval - Removed count increments when the supervised user removes an extension. - - - - - - Removed in April 2020 (M84). - - tobyhuang@chromium.org - cros-families@google.com - - Records the progress of supervised users as they try to install Chrome - extensions during the COVID-19 crisis, before the parent approval dialog is - ready. kAllowlistMiss count increments whenever we query for an extension id - in the allowlist and it is not found. kAllowlistHit count increments - whenever the extension id is found in the allowlist. - - - - - tobyhuang@chromium.org - cros-families@google.com - - Records the state of the "Permissions for sites, apps and - extensions" toggle. When parents/custodians have the toggle enabled, - supervised users may install extensions with parent/custodian approval, and - can approve permission updates by themselves. Otherwise, supervised users - cannot install extensions and cannot approve permission updates. If the - toggle is disabled and an extension has permissions updates, the extension - would remain force-disabled. The Disabled count increments when the parent - flips the toggle off, and increments twice if the supervised user logs in - while the toggle is in the off state. The Enabled count increments when the - parent flips the toggle on, and increments twice if the supervised user logs - in while the toggle is in the on state. While the double counting upon - logging in is less than ideal, at least the counts are balanced relative to - each other. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Records the actions of parents on the Parent Permission Dialog. Opened count - increments when the Parent Permission Dialog first opens. Parent Approved - count increments when the parent successfully types their password and - approves the extension. Parent Canceled count increments when the parent - cancels the dialog, denying the supervised user's attempt to enable the - extension. Failed count increments when there was some sort of failure in - the Parent Permission Dialog. No Parent Error count increments when the - supervised user doesn't have any associated parent email addresses for - asking approval. Note that this error also increments the Failed count. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Measures the amount of time in milliseconds after opening for the Parent - Permission Dialog to fail due to various reasons. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Measures the amount of time in milliseconds for the parent to successfully - type their password and approve the extension. - - - - - tobyhuang@chromium.org - agawronska@chromium.org - danan@chromium.org - cros-families@google.com - - Measures the amount of time in milliseconds for the parent to cancel the - Parent Permission Dialog. - - - - - agawronska@chromium.org - yilkal@chromium.org - cros-families@google.com - - The count of applications with time limit set by parents. Recorded once per - PerAppTimeLimit policy change. - - - - - agawronska@chromium.org - yilkal@chromium.org - cros-families@google.com - - The count of applications blocked by parents. It only applies to ARC++ - applications. Recorded once per PerAppTimeLimit policy change. - - - - - agawronska@chromium.org - yilkal@chromium.org - cros-families@google.com - - Per-App Time Limits feature engagement measured by the number of apps with - time limits set for child user. Reported at the beginning of each user - session. - - - - - agawronska@chromium.org - yilkal@chromium.org - cros-families@google.com - - The total number of PerAppTimeLimits policy changes seen in a session. - Recorded once at the end of the session. - - - - - agawronska@chromium.org - cros-families@google.com - - Action originated in parent access code dialog. Logged every time the action - happens. - - - - - agawronska@chromium.org - cros-families@google.com - - The context in which parent access code was used. Logged every time the new - parent access dialog is shown. - - - - - escordeiro@google.com - brunoad@google.com - ldaguilar@google.com - - The event that triggered status report for supervised account. - - - - - - Removed in M53. - - zea@chromium.org - - Time taken during app association (M18 and earlier were mispelled with this - histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of apps run failures, used to compare failure rates between data types - for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by AppSettingsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of app settings association failures. - - - - - Replaced by AppsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of app association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of app association failures (M18 and earlier were - mispelled with this histogram). - - - - - - Removed in M80. - - jkrcal@chromium.org - mastiz@chromium.org - Time taken during association of this data type. - - - - - Removed 2018-04, Sync attachments were never launched. - - maxbogue@chromium.org - Whether attachment checksums match on download or not. - - - - - Removed 2018-04, Sync attachments were never launched. - - maxbogue@chromium.org - Response or error codes from downloading sync attachments. - - - - - Removed 2018-04, Sync attachments were never launched. - - maxbogue@chromium.org - - The total time a download takes including request and server overhead. - - - - - - Removed 2018-04, Sync attachments were never launched. - - maxbogue@chromium.org - The result of initializing the sync attachment store. - - - - - Removed 2018-04, Sync attachments were never launched. - - maxbogue@chromium.org - Response or error codes from uploading sync attachments. - - - - - Removed in M85. - - mastiz@chromium.org - mmoskvitin@google.com - - Enumeration of results from attempting to migrate Sync's nigori node and its - encryption keys to support keystore. - - - - - - Removed in M53. - - zea@chromium.org - - Age of all auth tokens rejected by the invalidation server. Measured from - the time they were created. - - - - - - Removed in M53. - - zea@chromium.org - - Age of auth tokens younger than one hour that were rejected by the - invalidation server. Measured from the time they were created. - - - - - - Removed in M53. - - zea@chromium.org - Time taken during initial authorization. - - - - - Removed in M53. - - zea@chromium.org - - Age of all auth tokens rejected by the sync server. Measured from the time - they were created. - - - - - - No longer relevant since transition to OAuth. - - zea@chromium.org - - Age of auth tokens younger than one hour that were rejected by the sync - server. Measured from the time they were created. - - - - - - Removed in M77. - - jkrcal@chromium.org - treib@chromium.org - - Reported for autofill profile sync once per every locally committed entity - creation/update. It breaks down the origin of such a local change. - - - - - - Removed in M77. - - jkrcal@chromium.org - treib@chromium.org - - Reported for autofill profile sync once per every locally committed entity - deletion. It breaks down the origin of such a local deletion. - - - - - - Replaced by Sync.AutofillProfilesAssociationTime. - - zea@chromium.org - - Time taken during autofill profile association (M18 and earlier were - mispelled with this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of autofill profiles run failures, used to compare failure rates - between data types for a particular profile (see other Sync*RunFailures - histograms). - - - - - - Replaced by AutofillProfilesConfigureFailure. See crbug.com/478226. - - zea@chromium.org - - Enumeration of types of autofill profile association failures. - - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of autofill profile association failures (M18 and - earlier were mispelled with this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of autofill (autocomplete) run failures, used to compare failure rates - between data types for a particular profile (see other Sync*RunFailures - histograms). - - - - - - Replaced by AutofillConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of autofill association failures. - - - - - Removed in M85. - - mastiz@chromium.org - mmoskvitin@google.com - - Number of times this client has overwritten the nigori node to update the - encryption keys without a user action (during this instantiation of Chrome). - - - - - mastiz@chromium.org - treib@chromium.org - - Tracks sync backend initialization time during initial sync setup. - - - - - mastiz@chromium.org - treib@chromium.org - - Tracks sync backend initialization success rate during initial sync setup. - - - - - - Removed in M53. - - zea@chromium.org - - Compares sync's has_setup_completed pref against the set of types actually - restored from the sync DB. Mismatches should be rare. - - - - - mastiz@chromium.org - treib@chromium.org - - Tracks sync backend initialization success rate in cases where sync was - previously initialized. - - - - - mastiz@chromium.org - treib@chromium.org - - Tracks sync backend initialization time in cases where sync was previously - initialized. - - - - - - Removed in M53. - - zea@chromium.org - - Number of bad requests since application startup, when the Sync error - infobar asking the user to update their account details is displayed. - - - - - - Removed as of m18 - - zea@chromium.org - Time taken during bookmark association. - - - - - Removed as of 12/2019. Replaced by Sync.BookmarkGUIDSource2 which fixes a - bug affecting bucket 2 (field left empty) which counted permanent nodes. - - psivieroleitao@google.com - mamir@chromium.org - mastiz@chromium.org - - Records the source of GUIDs for remote bookmark updates, recorded when - processing a remote bookmark update. - - - - - mastiz@chromium.org - treib@chromium.org - - Records whether a GUID was found within BookmarkSpecifics, if an - originator_client_item_id of valid GUID format was used to replace it, or if - the field was left empty. Recorded when processing a remote bookmark update, - except for permanent nodes, which are created server-side and don't have an - originator client item ID. - - - - - mamir@chromium.org - mastiz@chromium.org - - Represents whether the proto field client_tag_hash in locally persisted sync - metadata is present and matches the local bookmark's GUID. It's recorded - after successfully loading the metadata (i.e. must not be corrupt). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of bookmark run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Removed as of M80. - - mamir@chromium.org - - Estimated number of bookmark duplications after bookmark association. - - - - - mastiz@chromium.org - rushans@google.com - - Records different types of bookmark entities having the same GUIDs. It's - recorded on each found duplicate when processing remote bookmarks from the - sync server during the initial merge. - - - - - mamir@chromium.org - mastiz@chromium.org - - The reason why the persisted metadata for a bookmark model is considered - corrupted. It either has corrupted data or doesn't match the bookmark model. - It's recorded at start up only if the initial sync has been performed - already. It's recorded after loading the metadata. - - - - - - Removed 2020-05. - - mamir@chromium.org - treib@chromium.org - - Time used to parse the Bookmarks persisted sync metadata after being read - from the Bookmarks JSON file. It includes the time spent in initializing - Bookmark Sync data structures as well as the time spent to check the - correctness of the data. It's reported on every startup for already syncing - users. It's not reported for non-syncing users or users going through the - first sync experience. - - - - - - Removed as of M80. - - mamir@chromium.org - - Tracks state of local bookmark model version relative to the sync version - when a new bookmark duplication occurs during bookmark association. - - - - - - Removed as of M80. - - mamir@chromium.org - - Estimated number of new bookmark duplications after bookmark association. - - - - - - Replaced by BookmarksConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of bookmark association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of bookmark association failures (M18 and earlier were - mispelled with this histogram). - - - - - rushans@google.com - mastiz@chromiumg.org - - Number of remote bookmarks which don't have full title in specifics. - Recorded when processing an initial merge. - - - - - rushans@google.com - mastiz@chromiumg.org - - Number of remote bookmarks which don't have full title in specifics. - Recorded when processing a remote bookmark update. - - - - - - Removed 10/2019. Was used for investigation of not completed Nigori - migration to keystore and recorded 0 suspicious samples. - - mmoskvitin@google.com - mastiz@chromium.org - - Records whether Nigori keybag can be decrypted with base64 decoded keystore - keys, when Nigori is not migrated to keystore and cryptographer is not - ready. - - - - - - Removed in 2019-02. - - pavely@chromium.org - - Records events encountered during sync's ClearServerData flow. - - - - - mastiz@chromium.org - treib@chromium.org - - Records the time between the local model being changed until the commit - response is completed and propagated to the model thread. Note: This is only - recorded with a data type suffix. The base version is never recorded. - - - - - - - rushans@google.com - treib@chromium.org - - Emitted per network Commit() request to the sync server and datatype. - Records the outcome of each commit attempt per data type (success or one of - various error codes). - - - - - treib@chromium.org - - Whether the full Sync feature or only the Sync transport layer is being - configured. Recorded when configuring the data types for any reason: Most - commonly during browser startup, but also after initial setup, after a - reconfiguration by the user, or when switching between full feature mode and - transport mode. - - - - - mastiz@chromium.org - treib@chromium.org - - Breakdown of sync data types being configured at first time signin, restart, - or user-initiated reconfiguration. This is different from Sync.CustomTypes - in that this captures all active devices, not just those that are choosing a - custom sync configuration. - - Note that not all platforms support all data types. As such, comparing - across platforms should only look at the common data types. - - - - - mastiz@chromium.org - treib@chromium.org - Count of model association failures for each type. - - - - - Removed in M80. - - jkrcal@chromium.org - mastiz@chromium.org - - Enumeration of types of configuration failures of this data type. - - - - - - Replaced by Sync.ConfigureTime_Long.ABORTED in m21. - - zea@chromium.org - - Time spent configuring data types in the case where configuration is - aborted. - - - - - - Replaced by Sync.ConfigureTime_Long.OK in m21. - - zea@chromium.org - - Time spent configuring data types in the case where configuration succeeds. - - - - - - Replaced by Sync.ConfigureTime_Long.PARTIAL_SUCCESS in m21. - - zea@chromium.org - - Time spent configuring data types in the case where only some data types - succeed. - - - - - - Replaced by Sync.ConfigureTime_Long.UNRECOVERABLE_ERROR in m21. - - zea@chromium.org - - Time spent configuring data types in the case where configuration encounters - an unrecoverable error. - - - - - victorvianna@google.com - jkrcal@chromium.org - - Time spent configuring data types for the first sync. Recorded when - DataTypeManagerImpl finishes. - - - - - - Replaced by Sync.ConfigureTime_Initial.ABORTED and - Sync.ConfigureTime_Subsequent.ABORTED in M75. - - zea@chromium.org - - Time spent configuring data types in the case where configuration is - aborted. - - - - - - Replaced by Sync.ConfigureTime_Initial.OK and - Sync.ConfigureTime_Subsequent.OK in M75. - - zea@chromium.org - - Time spent configuring data types in the case where configuration succeeds. - - - - - - Removed in M75. - - zea@chromium.org - - Time spent configuring data types in the case where only some data types - succeed. - - - - - - Replaced by Sync.ConfigureTime_Initial.UNRECOVERABLE_ERROR and - Sync.ConfigureTime_Subsequent.UNRECOVERABLE_ERROR in M75. - - zea@chromium.org - - Time spent configuring data types in the case where configuration encounters - an unrecoverable error. - - - - - victorvianna@google.com - jkrcal@chromium.org - - Time spent configuring data types for a subsequent (i.e. non-first) sync. - Recorded when DataTypeManagerImpl finishes. - - - - - - Removed 12/2011. No longer tracked. See crbug.com/107816. - - zea@chromium.org - - Number of times we fix a circularity sync conflict. This is not expected to - be hit anymore. - - - - - - Removed 12/2011. No longer tracked. See crbug.com/107816. - - zea@chromium.org - - Number of times we fix a removed directory with content sync conflict. This - is not expected to be hit anymore - - - - - zea@chromium.org - - Whether the gaia cookie jar was empty. Recorded on every SESSIONS commit - where the gaia cookie jar does not include the signed in user ( - CookieJarMatchOnNavigation == false). - - - - - zea@chromium.org - - Whether the gaia cookie jar included the signed in user (matched) or not. - Recorded on every SESSIONS commit. - - - - - - Removed in M53. - - zea@chromium.org - - Whether or not we detected missing credentials during startup. This may be - related to crbug.com/121755. - - - - - vitaliii@chromium.org - treib@chromium.org - - Key derivation method used for sync custom passphrase when a new custom - passphrase is set. "Not set" will never be reported for this - metric, since we always have an explicit key derivation method when a new - passphrase is set. - - - - - vitaliii@chromium.org - treib@chromium.org - - Key derivation method used for sync custom passphrase on successful - decryption of pending keys, i.e. when a passphrase is requested and the user - types in the correct one. "Not set" will never be reported for - this metric, since we always have an explicit key derivation method on - successful decryption. - - - - - vitaliii@chromium.org - treib@chromium.org - - State of the derivation method used for sync custom passphrase on startup. - Reported only when the passphrase type is CUSTOM_PASSPHRASE. - - - - - vitaliii@chromium.org - treib@chromium.org - - Time taken to derive keys in Nigori using a given key derivation method. - This histogram is always recorded with one of the key derivation method - suffixes. - - - - - mastiz@chromium.org - treib@chromium.org - - Breakdown of sync users whose cryptographer has pending keys. - - - - - mastiz@chromium.org - treib@chromium.org - - Breakdown of sync users whose cryptographer is fully ready for encryption - and decryption (initialized and no pending keys). - - - - - mastiz@chromium.org - treib@chromium.org - - Histogram that keeps track of how users encrypt their sync data. All users - start off with default encryption during initial setup, while a subset of - users go on to encrypt their sync data with a custom passphrase. - - - - - - Removed as of m26. - - zea@chromium.org - - Boolean histogram for whether a custom passphrase was entered during sync - setup. Samples are taken every time sync is (re)configured, and the unique - userid count shows how many users entered a custom passphrase. - - - - - - Removed 10/2018, replaced by Sync.CustomSync2. - - zea@chromium.org - - Samples are taken every time sync is (re)configured, and the unique userid - count shows how many users explicitly chose to sync this data type via the - "Advanced Sync Preferences" dialog. - - - - - treib@chromium.org - mastiz@chromium.org - - For users who have *not* selected the "Sync Everything" option, - this records all the data types they have selected to sync. Samples are - taken every time the Sync data types are (re)configured, which typically - happens during startup and when the user changes any Sync settings. - - - - - - Removed in M53. - - zea@chromium.org - - Number of clients that have fixed themselves up from a datatype preference - loss. Clients are not expected to have this happen more than once. This - value can be compared to Sync.BackendInitializeRestoreSuccess to determine - what percentage of users are still recovering. - - - - - - Removed 10/2018. Replaced by Sync.DataTypeRunFailures2 which correctly - splits run and start failures. - - zea@chromium.org - - Histogram of the run failures for the different sync datatypes. These are - failures that occur after startup while the datatype is syncing. Note: Due - to an enumeration reordering, pre-M23 labels are inaccurate (see - sync/base/model_type.h). - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Histogram of the run failures for the different sync datatypes. These are - failures that occur after startup while the datatype is syncing. This is one - of the base sync health metrics. - - - - - - Removed 10/2018. Replaced by Sync.DataTypeStartFailures2 which correctly - splits run and start failures. - - zea@chromium.org - - Histogram of the startup failures for the different sync datatypes. These - are failures due to missing top level sync nodes or model association Note: - Due to an enumeration reordering, pre-M23 labels are inaccurate (see - sync/base/model_type.h). - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Histogram of the startup failures for the different sync datatypes. These - are failures that occur during startup before the data type is fully loaded. - For USS datatypes, these errors are caused by failures in reading metadata - (or data) from the DB or by another failure in interaction with the model. - For Directory datatypes, startup errors are due to missing top level sync - nodes or model association. This is one of the base sync health metrics. - - - - - - Removed in 2020-08 (M86). - - grt@chromium.org - pastarmovj@chromium.org - - Reports the result of an attempt to delete a Windows user's roaming User - Data directory. This directory was erroneously created for signed-in users - who were not using the local sync server. See https://crbug.com/980487 for - details. - - - - - - Removed in M74. - - mastiz@chromium.org - jkrcal@chromium.org - - The largest number of active syncing devices known to any profile. May be 0 - when there are no signed in/syncing profiles open. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - The largest number of active and concurrently syncing devices known to any - profile. May be 0 when there are no signed in/syncing profiles open. Logged - with every UMA log. - - - - - - Removed in M53. - - pavely@chromium.org - - When signin_scoped_device_id from pref doesn't match the one in - DeviceInfoSpecfics this histogram tells if sync or pref copy was empty. This - will indicate how often such mismatch happens and what was the state before. - - - - - - Replaced by DictionaryConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of dictionary association failures. - - - - - Removed in M85. - - jkrcal@chromium.org - - Whether the Sync Directory encountered a catastrophic error. - - - - - - Removed 11/2011. No longer tracked. - - zea@chromium.org - Number of failures trying to open the sync database on mac. - - - - - Removed 11/2011. No longer tracked. - - zea@chromium.org - - Number of failures trying to open the sync database on a non-windows non-mac - platform. - - - - - - Removed 11/2011. No longer tracked. - - zea@chromium.org - - Number of failures trying to open the sync database on windows. - - - - - - Removed 2020-05. - - zea@chromium.org - Tracks success of failure of sync directory initialization. - - - - - Removed 06/2020. - - mastiz@chromium.org - treib@chromium.org - - Whether the sync cache GUID and birthday are stored consistently across the - sync directory and prefs. - - - - - - Removed 01/2020. No longer tracked. - - mamir@chromium.org - mastiz@chromium.org - - Counts the number of password updates downloaded in case of error during the - MergeSyncData(). This is introduced to detect if there is corrleation - between number of password updates and failure during merge. Recorded only - for USS implementation. - - - - - rushans@google.com - mastiz@chromium.org - - Counts the number of cases when there are duplicate sync entities while - processing remote update. It is introduced to detect cases when one of those - entities (or both) is a tombstone. Recorded for each duplicate entities - within GetUpdates cycle. - - - - - - Removed 2019-09 - we collected sufficient data, see crbug.com/995534. - - treib@chromium.org - jkrcal@chromium.org - - Whether ModelTypeWorker received any duplicate client tag hashes within a - full GetUpdates cycle (which, in the case of pagination, might consist of - multiple individual GetUpdates responses). - - - - - - Removed 2019-09 - we collected sufficient data, see crbug.com/995531. - - treib@chromium.org - jkrcal@chromium.org - - Whether ModelTypeWorker received any duplicate client tag hashes within a - single GetUpdates response (which, in the case of pagination, might be only - part of a full GetUpdates cycle). - - - - - - Removed 2019-09 - we collected sufficient data, see crbug.com/995528. - - mamir@chromium.org - treib@chromium.org - - Whether ModelTypeWorker received any duplicate client tag hashes within a - full GetUpdates cycle that happen to have different server ids (which, in - the case of pagination, might consist of multiple individual GetUpdates - responses). - - - - - - Removed 2019-09 - we collected sufficient data, see crbug.com/995529. - - mamir@chromium.org - treib@chromium.org - - Whether ModelTypeWorker received any duplicate server ids within a full - GetUpdates cycle (which, in the case of pagination, might consist of - multiple individual GetUpdates responses). - - - - - mastiz@chromium.org - melandory@chromium.org - - Recorded for a subset of users (Finch-controlled) per sync reflection, that - is, server-side updates that represent a local change. The time represents - the E2E time from the local change happening, the corresponding invalidation - being received and the relevant updates being fetched from the sync server. - Note: This is only recorded with a data type suffix. The base version is - never recorded. - - - - - - Removed as of m26. - - zea@chromium.org - - Boolean histogram for whether the "Encrypt all synced data" radio - button was selected during sync setup. Samples are taken every time sync is - (re)configured, and the unique userid count shows how many users chose to - encrypt their sync data. - - - - - - Removed 02/2020, Sync.PassphraseType2 can give the same data in a better - way. - - mmoskvitin@google.com - mastiz@chromium.org - mamir@chromium.org - - Records EncryptEverything state when Nigori is not migrated to keystore and - cryptographer is not ready. - - - - - - Removed as of M85. - - mamir@chromium.org - mastiz@chromium.org - - The positioning scheme used within sync entities. It is reported for data - types migrated to USS only. While it is reported for all data types, the - positioning information are expected to be set for bookmarks only. - "MISSING" is reported only for non deleted bookmarks. - - - - - mastiz@chromium.org - treib@chromium.org - A UI event occured. - - - - - Removed in M53. - - zea@chromium.org - - Time taken during extension association (M18 and earlier were mispelled with - this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of extension run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by ExtensionSettingsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - - Enumeration of types of extension settings association failures. - - - - - - Replaced by ExtensionsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of extension association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of extension association failures (M18 and earlier were - mispelled with this histogram). - - - - - - Removed as of 07/2018. No longer tracked (because it is directory-specific - and related to now obsolete metrics Sync.ModelTypeCount). - - gangwu@chromium.org - - Counts the total number of extra copies of sync data in memory. This count - is emitted once, after loading Sync Directory. The count will indicate how - many Directory entities fail to share client and server specifics. - - - - - - Replaced by a Sync.SyncedHistoryFaviconAvailability in M77. Note: Last data - entries will be inconsistent since we keep recording this histogram while - behavior has not been changed for every SyncFaviconRequestOrigin histogram - suffix. In particular, Sync.FaviconAvailability.RECENTLY_CLOSED_TABS on - Android has always been recorded for remote only entries. - - victorvianna@google.com - jkrcal@chromium.org - - Records the availability status (local, sync or non-available) for each - favicon displayed by an interface. Recorded when the recent tabs menu is - opened or when a request is done to chrome://favicon by page url, which - happens for example for the chrome://history and chrome://history/syncedTabs - interfaces. - - - - - - Removed in M84. - - zea@chromium.org - Whether a sync favicon cache lookup succeeded or not. - - - - - Removed in M53. - - zea@chromium.org - Number of synced favicons at initialization time. - - - - - Replaced by FaviconImagesConfigureFailure. See crbug.com/478226. - - zea@chromium.org - - Enumeration of types of favicon images association failures. - - - - - - Removed in M53. - - zea@chromium.org - - Number of client that have filled their sync favicon cache and must evict - old favicons vs those whose cache is not full. - - - - - - Replaced by FaviconTrackingConfigureFailure. See crbug.com/478226. - - zea@chromium.org - - Enumeration of types of favicon tracking association failures. - - - - - - Removed in M53. - - zea@chromium.org - Time between updates to a synced favicon's visit time. - - - - - Removed 11/2011. Was counted incorrectly. Replaced by - Sync.BackendInitializeFirstTimeSuccess. - - zea@chromium.org - - Tracks sync backend initialization success rate during initial sync setup. - - - - - - Backup logic has been removed since 02/2016. - - haitaol@chromium.org - First sync delay casued by backing up user data. - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for apps. Used as estimate of datatype commit frequency. - Logged when a sync cycle is performed for apps. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for autofill entries. Used as estimate of datatype - commit frequency. Logged when a sync cycle is performed for autofill - entries. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for autofill profiles. Used as estimate of datatype - commit frequency. Logged when a sync cycle is performed for autofill - profiles. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for bookmarks. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for boomarks. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for dictionary. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for dictionary. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for extensions. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for extensions. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for favicon images. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for favicon images. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for favicon tracking. Used as estimate of datatype - commit frequency. Logged when a sync cycle is performed for favicon - tracking. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for nigori. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for nigori. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for passwords. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for passwords. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for preferences. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for preferences. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for search engines. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for search engines. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for sessions. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for sessions. - - - - - - Removed in M53. - - zea@chromium.org - - Time between nudges for synced notifications. Used as estimate of datatype - commit frequency. Logged when a sync cycle is performed for synced - notifications. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for themes. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for themes. - - - - - - Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. - - zea@chromium.org - - Time between nudges for typed urls. Used as estimate of datatype commit - frequency. Logged when a sync cycle is performed for typed urls. - - - - - - Removed in M53. - - zea@chromium.org - - Time between nudges for WiFi credentials. Used as estimate of datatype - commit frequency. Logged when a sync cycle is performed for WiFi - credentials. - - - - - - Removed as of 06/2020. - - mastiz@chromium.org - treib@chromium.org - - Two navigations with different unique_ids shared a global_id/timestmap. This - means that user events will be ambiguously referencing navigations. - - - - - - Removed 02/2020. Instrumented in a wrong way and replaced by - Sync.NigoriConfigurationWithInvalidatedCredentials. - - mmoskvitin@google.com - mastiz@chromium.org - - Recorded when Nigori-only configuration failed. Indicates whether there was - a valid access token when failure happened. - - - - - - Removed 02/2020. Instrumented in a wrong way and replaced by - Sync.NigoriConfigurationWithInvalidatedCredentials. - - mmoskvitin@google.com - mastiz@chromium.org - - Recorded when Nigori-only configuration failed with 5 seconds backoff. - Indicates whether there was a valid access token when failure happened. - - - - - treib@chromium.org - mastiz@chromium.org - - An approximate state of sync at startup. Logs a few reasons sync definitely - wouldn't be able to start, or that it probably can start. The user having - turned off sync on mobile will be logged as "turned off by user". - A dashboard stop and clear will fall under "turned off and setup not - completed". See the SyncInitialState enum in profile_sync_service.cc - for more information. - - - - - - - melandory@chromium.org - - Histogram tracks the number of invalidations received per sync data type. - - - - - - Removed as of 5/2016. - - pkotwicz@chromium.org - - Count of the number of session sync invalidations. The goal of the metric is - to track how the number of session sync invalidations changes over time. - - - - - mamir@chromium.org - mastiz@chromium.org - rushans@google.com - - Records different causes for BookmarkSpecifics to be deemed invalid. Issues - are recorded upon verifying validity of specifics received from the server. - - - - - - Removed as of 04/2020 because directory implementation of Nigori is no - longer used and enough data for corresponding investigation was recorded. - - mmoskvitin@google.com - mastiz@chromium.org - - Indicates whether Nigori node state is migrated after the migration attempt. - - - - - mastiz@chromium.org - treib@chromium.org - - The reason for a failure decrypting the keystore decryptor token. - - - - - pastarmovj@chromium.org - - Tracks the number of times the local sync backend was enabled by the user. - - - - - - Removed as of 6/2019 in favor of Sync.Local.FileSizeKB. - - pastarmovj@chromium.org - Tracks the size of the local sync backend database file. - - - - pastarmovj@chromium.org - - Tracks the size of the local sync backend database file. Recorded every time - the roaming profile file is written by the client. - - - - - pastarmovj@chromium.org - - Tracks the types of requests that caused errors inside of the local server. - - - - - pastarmovj@chromium.org - - Tracks the number of times the Roaming profile cannot be retrieved. - - - - - - Removed 2019-09. Was only ever recorded for passwords. - - vasilii@chromium.org - - Counts cases when a sync type failed to load the local data during startup. - - - - - - Removed 2019-09. Was only ever recorded for bookmarks. - - zea@chromium.org - - Counts instances of out of sync local models detected during startup. - - - - - rushans@google.com - mastiz@chromium.org - - Counts cases when data in sync preferences is invalid. Recorded during sync - startup of the Sync transport layer. It happens soon after a signed-in - profile is opened. - - - - - - Removed 2019-11. - - pnoland@chromium.org - - Counts instances of navigations that are recorded locally but not synced. - Recorded once per active tab for every inferred sync cycle. Sync cycles are - inferred by examining the is_synced and is_syncing flags of sync directories - when recording local changes to tabs or windows. Sync cycles that occur - without changes to tabs or windows won't cause this metric to be logged. - - - - - - Removed 2019-07. - - gangwu@chromium.org - - Counts the number of times a user's sync service received a - MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down - cleanly. The sync service emits this number the next time the user's sync - service is started, which will likely happen the next time the user's - profile is opened after a Chrome restart. This count is emitted once per - user/profile. Things like browser crashes that implicitly bring down all - users' sync services will cause unclean shutdown tags to appear on all open - profiles, meaning that there will be multiple emissions to this histogram as - those profiles are re-opened. - - - - - - Removed 2019-07. - - gangwu@chromium.org - - Counts the number of times a user's sync service received a - MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down - uncleanly. The sync service emits this number the next time the user's sync - service is started, which will likely happen the next time the user's - profile is opened after a Chrome restart. This count is emitted once per - user/profile. Things like browser crashes that implicitly bring down all - users' sync services will cause unclean shutdown tags to appear on all open - profiles, meaning that there will be multiple emissions to this histogram as - those profiles are re-opened. - - - - - mamir@chromium.org - mastiz@chromium.org - - Recorded after applying the first sync merge for Bookmarks in case of merge - failure. Merge failure is detected by missing one or more permanent nodes in - the merge result. This metric records which permanent nodes are missing. - It's recorded only for USS infrastrucre. - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Recorded once per activation of an ephemeral (in-memory) data type; the - value is the duration of the setup (time from the start of the configuration - of sync until the data type receives all its sync data and the data is ready - for the user). This metric is used for monitoring general health of sync - client-side code. - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Recorded once per activation of a persistent (on-disk) data type; the value - is the duration of the setup (time from the start of the configuration of - sync until the data type receives all its sync data and the data is ready - for the user). This metric is used for monitoring general health of sync - client-side code. - - - - - - Removed as of 7/2018. Replaced by Sync.ModelTypeCount2 which does record - data consistently for both directory data types and USS data types. - - gangwu@chromium.org - - Counts the number of entries for each model type in sync DB at startup. - - - - - - Removed as of 8/2018. Replaced by Sync.ModelTypeCount3 which fixes a bug in - recording the counts for USS data types - - gangwu@chromium.org - - Counts the number of entries for each model type. For directory types, the - count is based on the directory contents, for USS types, the count is based - on metadata entries for the type. Recorded after sync configuration. This - metric is used for monitoring general health of sync client-side code. - - - - - - Removed as of 9/2018. Replaced by Sync.ModelTypeCount4 which fixes a - off-by-one bug that the root node get also recorded for directory data - types. - - jkrcal@chromium.org - - Counts the number of entries for each model type. For directory types, the - count is based on the directory contents, for USS types, the count is based - on metadata entries for the type. Recorded after sync configuration. This - metric is used for monitoring general health of sync client-side code. - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Counts the number of entries for each model type. For directory types, the - count is based on the directory contents (excl. the root node), for USS - types, the count is based on metadata entries for the type. Recorded after - sync configuration. This metric is used for monitoring general health of - sync client-side code. - - - - - - Removed as of 10/2018. Replaced by Sync.ModelTypeEntityChange3 which splits - initial remote updates from incremental remote updates. - - jkrcal@chromium.org - - Recorded once for every sync entity change (whenever it is commited to the - server or updated from the server). This metric is used for monitoring - general health of sync client-side code. Note: This is only recorded with a - data type suffix. The base version is never recorded. - - - - - - Removed as of 11/2018. Replaced by Sync.ModelTypeEntityChange3 which fixes a - bug affecting a subset of datatypes (directory codepath). - - jkrcal@chromium.org - - Recorded once for every sync entity change (whenever it is commited to the - server or updated from the server). This metric is used for monitoring - general health of sync client-side code. Note: This is only recorded with a - data type suffix. The base version is never recorded. - - - - - jkrcal@chromium.org - - Recorded once for every sync entity change (whenever it is commited to the - server or updated from the server). This metric is used for monitoring - general health of sync client-side code. Note: This is only recorded with a - data type suffix. The base version is never recorded. - - - - - - - jkrcal@chromium.org - rushans@google.com - - Recorded whenever ClientTagBasedModelTypeProcessor triggers a data type - failure (recorded for both Start and Run failures). It distinguishes call - sites for triggering such failures. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - Estimated memory usage by sync datatype in kilobytes. Recorded after sync - configuration. This metric is used for monitoring general health of sync - client-side code. - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Records whenever an orphan metadata is encountered by the - ClientTagBasedModelTypeProcessor. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - Records the model type when a local change is made and sync optimized it - away because nothing actually changed. - - - - - - Removed as of 05/2020. - - mastiz@chromium.org - - Records the number of write batches committed to leveldb - (ModelTypeStoreBackend) per datatype. - - - - - - - qjw@chromium.org - ortuno@chromium.org - treib@chromium.org - mastiz@chromium.org - - Record the LevelDB Status outcome for ModelTypeStore CommitWriteBatch - operations. - - - - - - Removed in M78 after sufficient data was gathered. - - mastiz@chromium.org - - Records the result of ModelTypeStoreBackend initialization. Used to analyze - frequency and causes of backend initialization failures. - - - - - - - jkrcal@chromium.org - rushans@google.com - - Recorded whenever a remote update for a particular data type gets dropped - for the following reason: - - - - - - Removed in M84 after corresponding investigation was completed. - - mmoskvitin@google.com - mastiz@chromium.org - - Recorded when Nigori-only configuration pending while user credentials were - invalidated. - - - - - - Removed as of 04/2020 because directory implementation of Nigori is no - longer used and enough data for corresponding investigation was recorded. - - mmoskvitin@google.com - mastiz@chromium.org - - Records whether Nigori was attempted to migrate before recording migration - failure. - - - - - - Removed in M84 because directory implementation of Nigori is no longer used - and enough data for corresponding investigation was recorded. - - mmoskvitin@google.com - mastiz@chromium.org - - Records the condition, which triggered Nigori migration to keystore. - - - - - - Removed in M85. - - mastiz@chromium.org - mmoskvitin@google.com - Breakdown of sync's nigori node keystore migration state. - - - - - Removed as of 04/2020 because directory implementation of Nigori is no - longer used and enough data for corresponding investigation was recorded. - - mmoskvitin@google.com - mastiz@chromium.org - - Records the method, which triggered Nigori migration to keystore. - - - - - - Was used during the launch to compare new and old implemetations. - - melandory@chromium.org - - The number of invalidations received per sync data type for cases when only - single invalidation was emited by the invalidation component. In some cases - the invalidation component emits many invalidations grouped together, this - histogram doesn't track those cases. - - - - - - Was used during the launch to compare new and old implementations. - - melandory@chromium.org - - The sync datatype of the recieved invalidation. Recorded only for the - invalidations with known version and recieved not in a group. - - - - - - Was used during the launch for the new implementation. - - melandory@chromium.org - - The sync datatype of the recieved invalidation with fresh version. - - - - - - Removed as of 05/2019 because it recorded freshness only up to 1hr and most - samples were thus out of bounds. Replaced by - Sync.NonReflectionUpdateFreshnessPossiblySkewed2 which records freshness up - to 7 days. - - mastiz@chromium.org - melandory@chromium.org - - Freshness of the sync data per received sync entity update, excluding - reflections. The time represents the clock difference from the model being - modified (usually on another device) until the change is processing by this - instance of the browser. Beware of potential clock skew due to two clients - being involved. - - - - - mastiz@chromium.org - melandory@chromium.org - - Freshness of the sync data per received sync entity update, excluding - reflections. The time represents the clock difference from the model being - modified (usually on another device) until the change is processing by this - instance of the browser. The time is capped at 1 week. Beware of potential - clock skew due to two clients being involved. - - - - - - Removed in M66. - - skym@chromium.org - - The client side execution time to check for revisits with bookmarks data. - - - - - - Removed in M66. - - skym@chromium.org - - Age of bookmark that matches a navigation event, where matching means the - urls match. If multiple bookmarks match, the most recently created is used. - - - - - - Removed in M66. - - skym@chromium.org - Transition type to a page that matched a bookmark. - - - - - Removed in M66. - - skym@chromium.org - Transition type to a page that didn't match a bookmark. - - - - - Removed in M66. - - skym@chromium.org - - Difference in time between finding the match and the creation of the most - recent foreign modification of the parent tab. The parent tab's modification - will not always be indicative of when the matching navigation occurred. - - - - - - Removed in M66. - - skym@chromium.org - - The number of navigations forward or backwards the matching noncurrent - navigation is from the current navigation in its tab. Negative values - represent backwards and positive values represent forwards. Zero should not - occur since it would cease to be noncurrent. - - - - - - Removed in M66. - - skym@chromium.org - Transition type that matched a synced navigation. - - - - - Removed in M66. - - skym@chromium.org - Transition type that didn't match a synced navigation. - - - - - Removed in M66. - - skym@chromium.org - - The client side execution time to check for revisits with session data. - - - - - - Removed in M66. - - skym@chromium.org - - Difference in time between finding the match and the creation of the most - recent foreign modification of the given tab. - - - - - - Removed in M66. - - skym@chromium.org - Transition type that matched a synced tab. - - - - - Removed in M66. - - skym@chromium.org - Transition type that didn't match a synced tab. - - - - - Removed in M66. - - skym@chromium.org - - The client side execution time to check for revisits with typed URL data. - - - - - - Removed in M66. - - skym@chromium.org - - Difference in time between finding the match and the last time this URL was - typed on a foreign client. - - - - - - Removed in M66. - - skym@chromium.org - Transition type that matched a typed URL. - - - - - Removed in M66. - - skym@chromium.org - Transition type that didn't match a typed URL. - - - - - Removed 2020-05. - - zea@chromium.org - - Number of partially synced types (those with a progress marker but no - initial sync ended bit) that exist at sync startup. - - - - - - Removed 2020-05. - - zea@chromium.org - Whether a passphrase decryption attempt succeeded or not. - - - - - Removed 2020-05. - - zea@chromium.org - Enumeration of how a user dismissed the passphrase dialog. - - - - treib@chromium.org - mastiz@chromium.org - The active sync passphrase type at sync startup. - - - - - - mmoskvitin@google.com - mastiz@chromium.org - Sync passphrase type collected at each metrics upload. - - - - - Removed in M53. - - zea@chromium.org - - Time taken during password association (M18 and earlier were mispelled with - this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of passwords run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by PasswordsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of password association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of password association failures (M18 and earlier were - mispelled with this histogram). - - - - - tschumann@chromium.org - treib@chromium.org - - Number of times the Sync engine got stopped because of an account state - change, e.g. the user signed out of the web. This should only affect the - sync-transport layer, as the sync feature would go into sync-paused state. - (credentials change). The histogram is emitted by minute of the emit-time to - aid with identifying the source of regular traffic spikes. Recorded before - the sync engine gets stopped. - - - - - tschumann@chromium.org - treib@chromium.org - - Number of times the Sync engine got stopped because of changed credentials. - Today this should not happen (but we have plans to use this path for - sync-paused state). The histogram is emitted by minute of the emit-time to - aid with identifying the source of regular traffic spikes. Recorded before - the sync engine gets stopped. - - - - - tschumann@chromium.org - treib@chromium.org - - Number of times the Sync engine got stopped because of a change in the - managed-sync pref (enterprise configuration). The histogram is emitted by - minute of the emit-time to aid with identifying the source of regular - traffic spikes. Recorded before the sync engine gets stopped. - - - - - tschumann@chromium.org - treib@chromium.org - - Number of times the Sync engine got stopped because of an enterprise policy - or the user not being signed in. The histogram is emitted by minute of the - emit-time to aid with identifying the source of regular traffic spikes. - Recorded before the sync engine gets stopped. - - - - - mastiz@chromium.org - mamir@chromium.org - - Emitted when the model type id in the persisted sync metadata mismatches the - model type id expected by the processor. It's recorded upon loading the - metadata and before trying to connect to sync. It's recorded per data type. - - - - - mastiz@chromium.org - - Number of network requests issued by sync to the sync server, grouped by - content type. - - - - - mastiz@chromium.org - - A sync error code received from the sync server as a result of a - client-initiated request. Note that this excludes network errors (e.g. - client offline) and HTTP errors. - - - - - mastiz@chromium.org - - Time taken for a client-initiated request to be sent over the network and - receive the response from the sync server. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - Emitted per network Commit() request to the sync server and datatype. It - helps estimate how much load each datatype puts on the server. Note that the - sum across buckets does not represent the total number of requests sent to - the server, since multiple datatypes can be grouped in a single request. See - Sync.PostedClientToServerMessage for the total number of requests/messages. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - Emitted per network GetUpdates() request to the sync server and datatype. It - represents how much load each datatype puts on the server. Note that the sum - across buckets does not represent the total number of requests sent to the - server, since multiple datatypes can be grouped in a single request. See - Sync.PostedClientToServerMessage for the total number of requests/messages. - - - - - mastiz@chromium.org - jkrcal@chromium.org - - Emitted per network GetUpdates() request to the sync server, it represents - the reason for sending such GetUpdates() request. - - - - - - Removed in M53. - - zea@chromium.org - - Time taken during preference association (M18 and earlier were mispelled - with this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of preferences run failures, used to compare failure rates between - data types for a particular profile (see other Sync*RunFailures histograms). - - - - - tschumann@chromium.org - treib@chromium.org - - Counts the number of times a syncable pref got registered using a type that - mismatched the type present in the pref store. In these events, the - persisted value gets removed from the pref store. - - - - - - Removed 2020-06. - - tschumann@chromium.org - treib@chromium.org - - Counts the number of times a client received a remote pref update with a - value type different from the registered pref type. The client will ignore - those remote updates. - - - - - - Removed in M79 because support for lazy pref registration was removed. - - tschumann@chromium.org - treib@chromium.org - - The number of unknown prefs being synced. This number is computed after the - sync model has been associated. Preferences which get handled by sync even - before being registered are considered "unknown". This might be - limited to a whitelist of preferences. - - - - - - Replaced by PreferencesConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of preference association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of preference association failures (M18 and earlier - were mispelled with this histogram). - - - - - mastiz@chromium.org - rushans@google.com - - Records different issues encountered when processing incremental bookmark - updates from the sync server. - - - - - mastiz@chromium.org - rushans@google.com - - Records different issues encountered when processing remote bookmarks from - the sync server during the initial merge procedure. - - - - - - Removed in M53. - - zea@chromium.org - Time taken from startup for the user to reauthorize. - - - - - Removed 05/2019. - - jkrcal@chromium.org - mastiz@chromium.org - - Recorded for each GetUpdates response (and each data type included). Records - whether the newly received token is new (as this data type had none before) - or whether it is the same as before or whether it has changed. - - - - - melandory@chromium.org - treib@chromium.org - - The sync datatype of the recieved invalidation with not-fresh version. - - - - - - Removed 04/2016 as not useful since it always logged true. - - zea@chromium.org - - Whether OAuth2 refresh token was available at the time when - ProfileSyncService was starting backend. - - - - - - Deleted in M75, Issue 900075. - - gangwu@chromium.org - - The request content size for a single HTTP/HTTPS call from sync client to - server. The content is compressed by gzip. - - - - - - Deleted in M75, Issue 900075. - - gangwu@chromium.org - - The original request content size for a single HTTP/HTTPS call from sync - client to server. It is the size before content got compressed. - - - - - - Deleted in M84. - - victorvianna@google.com - jkrcal@chromium.org - - Records the number of active requests simultaneously done to the Google - favicon server that were associated with a same icon url and could have thus - been grouped. Recorded when one of the following is displayed: entries in - chrome://history that are known to be present in remote history data; all - entries in chrome://history/syncedTabs; tabs from other devices in the 3 - dots history menu (desktop); tabs from other devices in the android Recent - Tabs UI. - - - - - - Deleted 2020-02. - - treib@chromium.org - mastiz@chromium.org - - Enumeration of types of conflict resolutions. Recorded every time a conflict - is resolved for a data type that has been converted to USS. - - - - - - Removed 06/2020. - - mastiz@chromium.org - treib@chromium.org - Enumeration of types of simple conflict resolutions. - - - - - Deleted in M75, Issue 900073. - - gangwu@chromium.org - - The response content size for a single HTTP/HTTPS call from sync server to - client. The content is compressed by gzip. - - - - - - Deleted in M75, Issue 900073. - - gangwu@chromium.org - - The original response content size for a single HTTP/HTTPS call from sync - server and client. It is the size after content got uncompressed. - - - - - - Removed 11/2011. Was counted incorrectly. Replaced by - Sync.BackendInitializeRestoreSuccess. - - zea@chromium.org - - Tracks sync backend initialization success rate in cases where sync was - previously initialized. - - - - - - Removed in M53. - - zea@chromium.org - - Time taken during search engine association (M18 and earlier were mispelled - with this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of search engine run failures, used to compare failure rates between - data types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by SearchEnginesConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of search engine association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of search engine association failures (M18 and earlier - were mispelled with this histogram). - - - - - - Replaced by Sync.ConfigureTime_Initial.{OK, ABORTED, UNRECOVERABLE_ERROR} in - M75 when solving bug 169053. - - zea@chromium.org - - Time spent on first-time configure. May include time spent on retries. - - - - - - Replaced by Sync.ConfigureTime_Subsequent.{OK, ABORTED, UNRECOVERABLE_ERROR} - in M75 when solving bug 169053. - - zea@chromium.org - - Time spent on non-first-time configure. May include time spent on retries. - - - - - - Removed in M53. - - zea@chromium.org - - Time taken during session association (M18 and earlier were mispelled with - this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of sessions run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Removed as of 2018-11. - - mastiz@chromium.org - treib@chromium.org - - Number of foreign sessions entries detected with bad client tag hash value - during MergeDataAndStartSyncing. These will be immediately deleted. The - overwhelming majority of clients should report a value of 0 upon startup. - - - - - - Removed 2020-05. - - zea@chromium.org - - Delay from the time chrome://history is loaded until the other devices' - sessions data became available. - - - - - - Replaced by SessionsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of session association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of session association failures (M18 and earlier were - mispelled with this histogram). - - - - - mastiz@chromium.org - treib@chromium.org - - For each Chrome window, records the number of tabs present at the time Sync - associates the SESSIONS datatype. - - - - - - Removed as of 2018-11. - - mastiz@chromium.org - treib@chromium.org - - The number of windows present within Chrome at the time Sync associates the - SESSIONS datatype. - - - - - - Removed in M69. - - mastiz@chromium.org - - https://crbug.com/639009, count of duplicate sync ids (tab node id) when any - are encountered. Likely caused from a persistence race between native tab - storage and sync db on Android. Should be trending to zero. - - - - - rushans@google.com - treib@chromium.org - - Counts the number of commit results while committing sharing message. - - - - - - Removed in M84 because directory implementation of Nigori is no longer used - and enough data for corresponding investigation was recorded. - - mmoskvitin@google.com - mastiz@chromium.org - - Indicates that Nigori would be migrated again right after migration if - AttemptToMigrateNigoriToKeystore called. - - - - - - Removed 2020-05. - - zea@chromium.org - - Time taken from the start of sync shutdown (in ProfileSyncService) until the - backend (SyncEngine) is fully destroyed. - - - - - - Removed in M53. - - zea@chromium.org - - Amount of time the UI thread waits (at shutdown) to stop the - SyncBackendRegistrar. - - - - - - Removed in M53. - - zea@chromium.org - - Amount of time the UI thread waits (at shutdown) to stop the sync thread. - - - - - - Replaced by Sync.RequestGroupSizeForSyncedHistoryFavicons in M77. - - victorvianna@google.com - jkrcal@chromium.org - - Records the number of active requests simultaneously done to the Google - favicon server that were associated with a same icon url and could have thus - been grouped. Recorded when opening the recent tabs menu, chrome://history - or chrome://history/syncedTabs with both history sync and the - EnableHistoryFaviconsGoogleServerQuery feature enabled. - - - - - mastiz@chromium.org - treib@chromium.org - The type of event that triggered sync initialization. - - - - - Removed, see TimeDeferred2. - - jeremy@chromium.org - zea@google.com - - Time spent after ProfileSyncService *creation* but before SyncEngine - initialization. - - - - - mastiz@chromium.org - treib@chromium.org - - Time spent after ProfileSyncService *creation* but before SyncEngine - initialization. - - - - - mastiz@chromium.org - treib@chromium.org - Data type that first requests sync initialization. - - - - treib@chromium.org - mastiz@chromium.org - - Tracks how sync was turned off. Logged every time sync is told to stop - permanently by the user (e.g. it won't come back on by itself). - - - - - - Removed in M53. - - zea@chromium.org - - Counts the number of times sync clients have encountered an auth error and - number of times auth errors are fixed. - - - - - - Removed 2019-03. - - treib@chromium.org - - The interval between successive sync cycles. Recorded whenever a sync cycle - starts, except for the very first one after Chrome startup. - - - - - victorvianna@google.com - jkrcal@chromium.org - - Records the availability status (local, sync or non-available) for favicons - associated with synced history entries. Recorded when one of the following - is displayed: entries in chrome://history that are known to be present in - remote history data; all entries in chrome://history/syncedTabs; tabs from - other devices in the 3 dots history menu (desktop); tabs from other devices - in the android Recent Tabs UI. - - - - - jkrcal@chromium.org - mastiz@chromium.org - - Records the latency of loading favicons associated with synced history - entries. Recorded when one of the following is displayed: entries in - chrome://history that are known to be present in remote history data; all - entries in chrome://history/syncedTabs; tabs from other devices in the 3 - dots history menu (desktop); tabs from other devices in the android Recent - Tabs UI. - - - - - - Removed in M53. Replaced by SyncedNotificationsConfigureFailure. See - crbug.com/478226. - - zea@chromium.org - - Enumeration of types of synced notifications association failures. - - - - - - Removed 12/2011. No longer tracked. See crbug.com/107816. - - zea@chromium.org - - Number of times the sync conflict resolver gets stuck. This is not expected - to be hit anymore. - - - - - fernandex@chromium.org - chrome-signin-team@google.com - - Enumeration of error conditions that displays an infobar to the user. iOS - only. - - - - - - Removed 10/2018, replaced by Sync.SyncEverything2. - - zea@chromium.org - - Boolean histogram for whether the "Sync Everything" option was - selected during sync setup. Samples are taken every time sync is - (re)configured, and the unique userid count shows how many users chose to - sync all available data types. - - - - - treib@chromium.org - mastiz@chromium.org - - Boolean histogram for whether the "Sync Everything" option was - selected by the user. Samples are taken every time the Sync data types are - (re)configured, which typically happens during startup and when the user - changes any Sync settings. - - - - - - Removed as of m19 - - zea@chromium.org - - Time taken during theme association (M18 and earlier were mispelled with - this histogram). - - - - - - Removed as of m19. - - zea@chromium.org - - Count of theme run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by ThemesConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of theme association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of theme association failures (M18 and earlier were - mispelled with this histogram). - - - - - mmoskvitin@google.com - mastiz@chromium.org - - Records whether attempt of adding trusted vault keys was successful (i.e. - whether pending keys state resolved). - - - - - mmoskvitin@google.com - mastiz@chromium.org - - Records whether user action was required to fetch trusted vault keys upon - startup. Recorded only if trusted vault passphrase type is used and at most - once per browser/profile lifetime. - - - - - mmoskvitin@google.com - mastiz@chromium.org - - Records number of trusted vault keys fetched upon fetching completion. - - - - - mmoskvitin@google.com - mastiz@chromium.org - Recorded when fetching trusted vault keys is attempted. - - - - mmoskvitin@google.com - mastiz@chromium.org - - Recorded when user clicks/taps on trusted vault error button. Buckets - represents the UI elements which contain trusted vault error button. - - - - - - Removed in M53. - - zea@chromium.org - - Time taken during typed url association (M18 and earlier were mispelled with - this histogram). - - - - - - Removed in M53. - - zea@chromium.org - - The percentage of history DB operations initiated by the typed URL change - processor that return an error. The cumulative count for the current sync - session is logged after every typed URL change. - - - - - - Removed 2020-05. - - zea@chromium.org - - The percentage of history DB operations during merge data that return an - error. This is logged at the end of typed URL merge data, which happens once - each time sync starts up. - - - - - - Removed in M53. - - zea@chromium.org - - The percentage of history DB operations during model association that return - an error. This is logged at the end of typed URL model association, which - happens once each time sync starts up. - - - - - - Removed as of m19. - - zea@chromium.org - - Count of typed url run failures, used to compare failure rates between data - types for a particular profile (see other Sync*RunFailures histograms). - - - - - - Replaced by TypedUrlsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - Enumeration of types of typed url association failures. - - - - - Removed as of m19. - - zea@chromium.org - - Enumeration of types of typed url association failures (M18 and earlier were - mispelled with this histogram). - - - - - victorvianna@google.com - treib@chromium.org - - This records the number of sync entities that were still undecrypted by the - time the data type was disabled (typically during browser shutdown). - - - - - - Removed as of 06/2020. - - mastiz@chromium.org - treib@chromium.org - - Enumeration of the different reasons for unrecoverable errors and how often - they have occurred. - - - - - mastiz@chromium.org - treib@chromium.org - - Counts of responses (both http code and net error code) for Sync URL - fetches. - - - - - mastiz@chromium.org - treib@chromium.org - - Time spent waiting for a sync cycle to complete the url fetch. - - - - - mastiz@chromium.org - treib@chromium.org - - Whether a url fetch timed out or not. Timing out implies the fetch was - stalled for an unknown reason. - - - - - - Removed in M53. - - zea@chromium.org - Time the user spends looking at the authorization dialog. - - - - - Removed in M53. - - zea@chromium.org - Time taken during bookmark association. - - - - - Removed in M82. - - pavely@chromium.org - Time it took sync to load models for USS datatypes. - - - - - Removed in M85. - - mastiz@chromium.org - - Counts the number of sync entities per model type successfully migrated from - directory to USS. - - - - - - Removed in M85. - - treib@chromium.org - mastiz@chromium.org - Counts directory to USS migration failures per model type. - - - - - Removed in M85. - - treib@chromium.org - mastiz@chromium.org - Counts directory to USS migration successes per model type. - - - - - Removed as of 05/2019. - - jkrcal@chromium.org - feuunk@chromium.org - - Counts number of data entities that are removed when sync / Wallet sync gets - disabled. - - - - - - Removed as of 2020-03. - - rushans@google.com - jkrcal@chromium.org - - Records errors with storage keys in ClientTagBasedModelTypeProcessor during - updates and loading of metadata for AUTOFILL_WALLET_DATA data type. - - - - - - Removed as of 2019-08. - - jkrcal@chromium.org - mastiz@chromium.org - - Counts number of old orphan metadata entities that are removed on startup. - - - - - - Removed in M53. - - zea@chromium.org - Time taken during WiFi credentials association. - - - - - Removed in M53. - - zea@chromium.org - - Enumeration of types of WiFi credentials configuration failures. - - - - - - Replaced by WifiCredentialsConfigureFailure. See crbug.com/478226. - - zea@chromium.org - - Enumeration of types of WiFi credentials association failures. - - - - - - Removed in M67. After more than a year, almost all clients are reporting - FALSE. - - skym@chromium.org - - Whether there are still encrypted updates that the cryptographer cannot - decrypt during ApplyUpdates in the ModelTypeWorker (USS Only). Emitting true - is an invalid state that hopefully never happens, as it is a potential data - loss scenario. - - - - - - Removed in M66. - - skym@chromium.org - Upon NTP load, the age of the youngest synced foreign tab. - - - - - Removed in M53. - - petewil@chromium.org - zea@chromium.org - - The actions taken on synced notifications, recorded every time they happen. - This histogram will record every single event that happens separately. - - - - - tzik@chromium.org - - Overridden conflict resolution policy of Sync FileSystem API. Recorded for - each API call to override the policy. - - - - - tzik@chromium.org - The result of opening the Sync FileSystem backend database. - - - - tzik@chromium.org - - The number of cached backing remote file metadata in the Sync FileSystem - database. Recorded at the initialization phase of Sync FileSystem. - - - - - tzik@chromium.org - - The number of Chrome Apps that uses Sync FileSystem with V2 backend. - Recorded at the initialization phase of Sync FileSystem. - - - - - tzik@chromium.org - - The result of the registration of Chrome App to Sync FileSystem. - - - - - peria@chromium.org - tzik@chromium.org - - Time elapsed to register a Chrome App to SyncFilesystem. Recorded for each - registration request by apps. - - - - - tzik@chromium.org - The result of opening the Sync FileSystem tracker database. - - - - tzik@chromium.org - - The number of the directory tree node that maps backing files to local files - in the Sync FileSystem database. Recorded at the initialization phase of - SyncFileSystem. - - - - - - Removed 06/2019. - - dbeam@chromium.org - - Shows actions taken on the "Not signed in? You're misssing out" - link on the top right of chrome://apps. Logged once per visit of - chrome://apps as well as on each click of the sync promo. - - - - - - Removed 03/2018. SyzyAsan has been deprecated. - - georgesak@chromium.org - - Record whether the deferred free mechanism was successfully enabled or not. - This is only recorded in syzyasan builds with the feature enabled. - - - - - dtrainor@chromium.org - yfriedman@chromium.org - - [Android] Age (time since the last display in previous sessions) of a tab - being restored due to the first tab switch after the browser cold start, - recorded upon such restore. When the browser is started from cold, this - metric is not recorded for the foreground, automatically restored tab, so - that the metric tracks only the restores triggered by direct user decision - to switch tabs. - - - - - wnwen@chromium.org - [Android] Count of upload success/failures by crash type. - - - - ppi@chromium.org - - Mobile-specific metric: when a tab that was opened in background (via - "Open link in new tab") is switched to, we record whether the - eagerly loaded tab was still memory resident, or we lost the loaded page due - to memory pressure. - - - - - - Removed 06/2020 - - pkotwicz@chromium.org - - Whether a tab which was opened in the background (e.g. via "Open link - in new tab") is foregrounded prior to being closed. - - - - - - Removed 06/2020 - - pkotwicz@chromium.org - - Counts the number of background tabs opened via the context menu per page - URL. The count is reset on each navigation of the parent tab. Zero counts - are not recorded. - - - - - - Removed 01/2019. - - - Time in milliseconds from trying to close the tab to actually closing it. - Includes time that's spent in JS OnUnload handlers. - - - - - - Removed 01/2019. - - - Time in milliseconds from when JS OnUnload handlers have finished to - actually closing tab. Doesn't include time that's spent in JS OnUnload - handlers. If there are no UnLoad handlers, should be identical to Tab.Close. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Number of open tabs in each guest window. Recorded once a new tab in a guest - window is opened and adds one to the bucket of number of tabs in that - particular window (it does not count the total number of tabs in all open - guest windows). Please note that this metric double counts the lower - numbers, meaning that if user opens three tabs (without closing any in - between), then buckets 1, 2, and 3 will all be incremented in turn. - - - - - rhalavati@chromium.org - chrome-privacy-core@google.com - - Number of open tabs in each incognito window. Recorded once a new tab is - opened in an incognito window and adds one to the bucket of number of tabs - in that particular window (it does not count the total number of tabs in all - open incognito windows). Please note that this metric double counts the - lower numbers, meaning that if user opens three tabs (without closing any in - between), then buckets 1, 2, and 3 will all be incremented in turn. - - - - - - Removed 11/2016. No longer useful after finding out that it has no effect on - tab reactivation rates. - - pmonette@chromium.org - - A tab was deactivated. Closing tabs are not included. This histogram also - records if the tab's URL was bookmarked. - - - - - - No longer recorded. - - pmonette@chromium.org - - A tab was deactivated. Closing tabs are not included. This histogram also - records if the tab had any form interaction. - - - - - - No longer recorded. - - pmonette@chromium.org - - A tab was deactivated. Closing tabs are not included. This histogram also - records if the tab was pinned to the tab strip or not. - - - - - - Removed 10/2015, not needed anymore. - - georgesak@chromium.org - - Metric to track counts of actions related to tab discarding. Namely, we get - an event for every tab switch, split into two groups, whether it was a - discarded tab not. We also get an event whenever a tab gets discarded as - well as when a tab that's playing audio gets discarded. - - - - - - Removed 10/2015, and replaced by TabManager.Discarding.DiscardCount. - - georgesak@chromium.org - - Metric to track the number of discards tabs have gone through. Each time a - tab is discarded, this histogram is recorded. Therefore, this metric is - cumulative, ie. as a tab gets discarded over and over, it gets a hit in each - bin (1, 2, 3...). - - - - - - Removed as of 10/2016. - - - [iOS] When switching to an evicted tab, this histogram records whether or - not the tab had ever been active. For example, the tab was opened via - "Open in new tab" but evicted before being viewed for the first - time. - - - - - mrefaat@chromium.org - bling-team@google.com - - [iOS] Used on External App launcher Prompt to determine if the user clicked - open or cancel. - - - - - - Removed as of 10/2016. - - - A count of form activity (e.g. fields selected, characters typed) in a tab. - Recorded only for tabs that are evicted due to memory pressure and then - selected again. - - - - - pkl@chromium.org - - [iOS] Used on iOS 9+ iPad to report the usage of Compact or Regular - horizontal size class. This is logged at startup and on each size class - change. - - - - - - Removed 06/2020 - - pkotwicz@chromium.org - - [Android] When a tab that was opened in the background (e.g. via "Open - link in new tab") is evicted prior to the first time that it is shown, - we record the tab's age at the time that the tab is shown. - - - - - tbergquist@chromium.org - bsep@chromium.org - - Tracks the different ways users are opening new tabs. Does not apply to - opening existing links or searches in a new tab, only to brand new empty - tabs. Note: Currently the "Regular menu option" includes some - programmatic actions in addition to user actions. - - - - - - Removed 07/2020, no longer used. - - kmilka@chromium.org - ramyan@chromium.org - - The time for the new tab page to fire the "DOMContentLoaded" - event. - - - - - carlosk@chromium.org - harringtond@chromium.org - - The time for the new tab page to load. Only recorded on Android. Recorded - only once per tab, i.e. excluding back/forward navigations. - - - - - - Removed 07/2020, no longer used. - - kmilka@chromium.org - ramyan@chromium.org - - The time for the new tab page to start executing JavaScript. - - - - - - Removed in favor of Tab.TabUnder.PopupToTabUnderTime. - - csharrison@chromium.org - - Measures the time from when a tab opens a popup to when it navigates itself - cross-origin in the background. - - - - - - Removed in favor of Tab.TabUnder.VisibleTime. - - csharrison@chromium.org - - Measures the total time a tab is visible after it navigates itself - cross-origin in the background. Measured at WebContents destruction. The tab - must have opened a popup (as classified by the popup blocker) before the - navigation. - - - - - pkl@chromium.org - - [iOS] Used on iOS 9+ iPad to report the usage of Compact or Regular - horizontal size class. Recorded on page load. - - - - - marq@chromium.org - [iOS] The orientation of the device. Recorded on page load. - - - - dtrainor@chromium.org - - [Android] The number of page loads since the last switch to an evicted tab - on Android. This was sampled each time an evicted tab was reloaded. - - - - - dtrainor@chromium.org - yfriedman@chromium.org - - [Android] User-perceived load time for a successful tab restore, measured - from the first time the user sees the tab being restored until the load - completes. - - - - - dfried@chromium.org - collinbaker@chromium.org - Records how a tab preview image was generated. - - - - dfried@chromium.org - collinbaker@chromium.org - - When generating a preview for a background tab, this measures the time - between requesting a video capture and receiving the first usable frame. - - - - - dfried@chromium.org - collinbaker@chromium.org - - When generating a preview, a tab's contents are captured as an uncompressed - image, compressed in the background, then sent to subscribers on the main - thread. This roughly measures the time between the capture completing and - the compressed image being available on the main thread. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - dfried@chromium.org - collinbaker@chromium.org - - When generating a preview for a background tab, this measures the time - between receiving a frame and storing it as the current thumbnail. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - dfried@chromium.org - collinbaker@chromium.org - - On tab switch, the visible content area is captured and stored as a - thumbnail. This measures the time between requesting the capture and storing - it as the current thumbnail. - - - - - dfried@chromium.org - collinbaker@chromium.org - - Measures the total time spent in video capture mode when generating a - preview for a background tab. This is emitted at the end of each capture - session. - - - - - gambard@chromium.org - kkhorimoto@chromium.org - - Record the action executed when the user performs a pull down gesture. This - feature is currently iOS only. - -
- A pull down gesture is an action completed when the user scrolls past the - edge of the web page and continues scrolling in the same direction revealing - a specific UI on the header with multiple actions icons. The user can then - choose an action by scrolling left or right and lift the finger or cancel by - scrolling back up. This is currently an iOS specific feature. -
- - - - - Removed 11/2016. No longer useful after finding out that it has no effect on - tab reactivation rates. - - pmonette@chromium.org - - A tab was reactivated after being hidden. This histogram also records if the - tab's URL was bookmarked. - - - - - - No longer recorded. - - pmonette@chromium.org - - A tab was reactivated after being hidden. This histogram also records if the - tab had any form interaction. - - - - - - No longer recorded. - - pmonette@chromium.org - - A tab was reactivated after being hidden. This histogram also records if the - tab was pinned to the tab strip. - - - - - tedchoc@chromium.org - clank-team@google.com - - [Android] The status of a tab and an application when a renderer crashes. - This is recorded only for Android when a renderer crashes. - - - - - wnwen@chromium.org - - [Android] Breakdown of renderer exit status for renderers that have strong - bindings. An extension of the counts in Tab.RendererExitStatus. Only - recorded on Android. - - - - - wnwen@chromium.org - - [Android] Breakdown of renderer exit status for renderers that do not have - strong bindings. An extension of the counts in Tab.RendererExitStatus. Only - recorded on Android. - - - - - wnwen@chromium.org - - [Android] The status of a renderer when the browser notices that the process - has exited. Only recorded on Android. - - - - - pkl@chromium.org - - [iOS] A count of the number of alive renderers when a renderer termination - occurs. - - - - - pkl@chromium.org - - [iOS] The number of renderers which are either currently alive or recently - terminated at the time of a renderer termination. - - - - - pkl@chromium.org - - [iOS] Records whether a memory warning had recently been received before a - renderer termination. - - - - - dtrainor@chromium.org - marq@chromium.org - - [Android and iOS] When the browser restores a tab, whether the load was - successful. Loads can fail for instance when there is no connectivity. - - - - - dtrainor@chromium.org - marq@chromium.org - [Android and iOS] Load time for a successful tab restore. - - - - dtrainor@chromium.org - - [Android] When the browser restores a tab, whether the user waits for - completion of the load or if the user gives up by switching to another tab - or leaving Chrome. - - - - - ramyan@chromium.org - cyflee@chromium.org - - Records actions taken after one or more screenshots of a page were taken. - This will not be recorded if Chromium is killed before leaving the page. If - several types of action (IPH and Sharing) occur, only the last is recorded. - We think that both IPH and Sharing happening at the same time is rare, so we - do not expect to lose much data this way. - - - - - ramyan@chromium.org - cyflee@chromium.org - - Records the number of screenshots taken of a specific page. It is recorded - when the user navigates away from this page or the tab is destroyed. This - will not be recorded if Chromium is killed before leaving the page. - - - - - eugenebut@chromium.org - olivierrobin@chromium.org - - The state (foreground/background) of a tab when its renderer is terminated. - - - - - - No longer logged - - - The status of a tab collected each time the tab is displayed on Android, - including user switching to the tab and displays of newly created tabs, such - as NTP or tabs opened to handle intents. - - - - - marq@chromium.org - - [Android and iOS] The status of a tab collected each time the user switches - to it on mobile. That does not include tabs being created at the time the - user switches to them, such as NTP or tabs opened to handle intents. - - - - - - No longer logged - - marq@chromium.org - - [Android and iOS] The status of a tab collected each time the user switches - to it on mobile with the data reduction proxy enabled. This is populated - identically, and in addition to Tab.StatusWhenSwitchedBackToForeground for - any given tab switching event if the proxy is enabled. - - - - - dtrainor@chromium.org - - [Android] Age (in ms) when the tab was switched to foreground. - - - - - - Removed as of 04/2014. - - - Each time a tab is brought to the foreground, this histogram indicates if - chrome was launched without an URL (i.e., from the launcher), or with an URL - (i.e., from another app). - - - - - - Removed as of 04/2014. - - - Rank in MRU order (0 being first) when the tab was switched to foreground. - - - - - - No longer logged - - Count of all tabs when a tab is switched. - - - - - Removed as of 04/2014. - - - Each time a tab is brought to the foreground, this histogram indicates if - this is the first viewing of the tab since Chrome was put into foreground, - or if it was a return to a tab that has already been shown in this session. - - - - - csharrison@chromium.org - - The position of the URL in the framebust UI list (desktop only) when it is - clicked. Note that this UI surface is shared with the framebusting - intervention, so elements in the list could come from either features. This - metric will only be logged when a URL from the tab under intervention is - clicked. - - - - - - Removed August 2018 - - csharrison@chromium.org - - Measures the engagement score associated with the URL that is detected as - the target of a tab-under navigation. - - - - - csharrison@chromium.org - - Measures the time from when a tab opens a popup to when it performs a - tab-under (i.e. navigates cross origin, in the background without a user - gesture). - - - - - csharrison@chromium.org - - Measures the total time a tab is visible after it navigates itself - cross-origin in the background, without a user gesture. The tab must have - opened a popup since the last user gesture in the tab. Measured at - WebContents destruction. The total visible time for the tab is the sum of - this metric and Tab.TabUnder.VisibleTimeBefore. - - - - - csharrison@chromium.org - - Measures the total time a tab is visible before it navigates itself - cross-origin in the background, without a user gesture. The tab must have - opened a popup since the last user gesture in the tab. Measured at - WebContents destruction. The total visible time for the tab is the sum of - this metric and Tab.TabUnder.VisibleTime. - - - - - csharrison@chromium.org - - Various actions related to the tab under intervention, logged during main - frame navigation. - - - - - - Removed as of 10/2016. - - - [iOS] When an existing tab becomes active, this histogram records the time - since it was made inactive. - - - - - - Removed as of 10/2016. - - - [iOS] When an evicted tab becomes active, this histogram records the time - since it was made inactive. - - - - - - Removed as of 10/2016. - - - Time elapsed since there was form activity (e.g. fields selected, characters - typed) in a tab. Recorded only for tabs that are evicted due to memory - pressure and then selected again. - - - - - - No longer recorded. - - pmonette@chromium.org - - The time elapsed from the moment a tab was deactivated until it was - reactivated. Only recorded for tabs that are pinned or had form interaction. - - - - - - No longer recorded. - - pmonette@chromium.org - - The time elapsed from the moment a tab was deactivated until it was - reactivated. Only recorded for tabs that are not pinned nor had form - interaction. - - - - - tedchoc@chromium.org - clank-team@google.com - - [Android] The total count of tabs which were kept while Chrome process is in - the foreground. This is recorded only for Android right before Chrome - process goes into the background. - - - - - fdoray@chromium.org - - Time spent by a tab in a given visibility state. Recorded when the - visibility changes and when the tab is closed. - - - - - csharrison@chromium.org - - Measures the total time a tab is visible. Measured at the WebContents layer - so this metric does not attempt to account for things like session restore. - Logged at WebContents destruction. - - - - - - This metric was deprecated in favor of just using Tab.TabUnder.VisibleTime - directly. Consider bringing it back if we care about visible time after a - suspicious redirect without an associated popup. - - csharrison@chromium.org - - Measures the total time a tab is visible after it navigates itself - cross-origin in the background. Measured at WebContents destruction. - - - - - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The number of tabs groups that are collapsed in all browsers (counting - app-mode windows) when a load completes. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the number of sessions of a selected tab group - whenever Chrome comes to the foreground, or switch tab in the tab switcher. - This number is accumulated until that group id is outdated, meaning all the - tabs with that group id has been closed. - - - - - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The time a tab group spends in the collapsed state before the group is - either expanded or closed. - - - - - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The time a tab group spends in the expanded state before the group is either - collapsed or closed. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The number of tabs groups with a user-set name or color open in all browsers - (counting app-mode windows) when a load completes. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the number of tab groups whenever Chrome comes to the - foreground. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The number of tabs groups open in all browsers (counting app-mode windows) - when a load completes. - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the number of tab groups that have customized group - name whenever Chrome comes to the foreground. - - - - - corising@chromium.org - chrome-desktop-ui-sea@google.com - - This histogram records the number of tab hover cards seen between the last - active tab change and a tab change by mouse click. - - - - - corising@chromium.org - chrome-desktop-ui-sea@google.com - - This histogram records the time between when a hover card was last hidden to - when it is shown again. Since users can easily hover out of the tab strip we - want to reshow the tab hover card with no delay if we think they - unintentionally exited the tab strip. If the user reenters the tab strip - within X ms we want to reshow the hover card immediately. This histogram - will help to better refine that number. - - - - - minch@chromium.org - omrilio@chromium.org - - Drag an app window from top in tablet mode will result in different window - states. Logged when the app drag ended to record the window end state. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of the action that drag an app window from top in tablet mode. - Logged when the TabletModeController is destructed, which means the user - session is ended. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of the action that drag an app window from top in tablet mode - when splitview is active. Logged when the TabletModeController is - destructed, which means the user session is ended. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of each volume adjust type in tablet mode. Logged when starts - volume adjust while in tablet mode. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of the action that drag a tab of the browser window in tablet - mode. Logged when the TabletModeController is destructed, which means the - user session is ended. - - - - - minch@chromium.org - omrilio@chromium.org - - The type of a tab drag done in tablet mode. Logged when start to drag a tab - of the browser window in tablet mode. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of the action that drag a tab of the browser window in tablet - mode when splitview is active. Logged when the TabletModeController is - destructed, which means the user session is ended. - - - - - minch@chromium.org - omrilio@chromium.org - - The type of the window (app window or tab strip) drag end event in tablet - mode. Logged when the window drag in tablet mode ended. - - - - - minch@chromium.org - omrilio@chromium.org - - The number of windows in overview when dragging a window from top in tablet - mode. Logged when start the window drag and overview has been opened behind. - - - - - - Removed June 2020. - - chrisha@chromium.org - - The expected queueing duration of tasks in a foreground tab during a - background tab opening session (the duration of time from when the browser - starts to open background tabs until the time the browser has finished - loading those tabs or otherwise decided to stop loading them). The metric - reflects the responsiveness of a tab. A lower value means the tab will - respond to inputs faster. This metric is equivalent to - RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all - tasks in each 1000-ms window. The metric is not recorded when the session - overlaps with session restore. - - - - - chrisha@chromium.org - - The loading state of a tab at the time the user switches to it during a - background tab opening session (the duration of time from when the browser - starts to open background tabs until the time the browser has finished - loading those tabs or otherwise decided to stop loading them). The metric is - only recorded when a tab is switched to from another tab within the same - tabstrip. As a result, the case when switching between different windows is - not included, either between two tabs in different browser windows, or when - switching to a different application and switching back to the browser. The - metric is not recorded when the session overlaps with session restore. - - - - - chrisha@chromium.org - - The max number of background tabs pending or loading when opening background - tabs. This is recorded at the end of the background tab opening session (the - duration of time from when the browser starts to open background tabs until - the time the browser has finished loading those tabs or otherwise decided to - stop loading them). The metric is not recorded when the session overlaps - with session restore. - - - - - chrisha@chromium.org - - The number of background tabs whose loading was triggered by TabManager - automatically when opening background tabs. This is recorded at the end of - the background tab opening session (the duration of time from when the - browser starts to open background tabs until the time the browser has - finished loading those tabs or otherwise decided to stop loading them). The - metric is not recorded when the session overlaps with session restore. - - - - - chrisha@chromium.org - - Whether the tab load is timed out during background tab opening session (the - duration of time from when the browser starts to open background tabs until - the time the browser has finished loading those tabs or otherwise decided to - stop loading them). The metric is not recorded when the session overlaps - with session restore. - - - - - chrisha@chromium.org - - The number of background tabs whose loading was triggered by user action - when opening background tabs. For example, when the user selects a - background tab and brings it to foreground, that tab will start to load - immediately if not already loading. This is recorded at the end of the - background tab opening session (the duration of time from when the browser - starts to open background tabs until the time the browser has finished - loading those tabs or otherwise decided to stop loading them). The metric is - not recorded when the session overlaps with session restore. - - - - - chrisha@chromium.org - - The max number of background tabs paused to load due to memory pressure when - opening background tabs. This is recorded at the end of the background tab - opening session during a background tab opening session (the duration of - time from when the browser starts to open background tabs until the time the - browser has finished loading those tabs or otherwise decided to stop loading - them). The metric is not recorded when the session overlaps with session - restore. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Cumulative number of tabs discarded due to low memory conditions, recorded - once per tab discard event. For example, a user who had 3 tabs discarded - records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the number - of sessions where users experienced N or more tab discard events. - - - - - - Removed 11/2017. Analysis showed that MRU was as good as engagement score to - choose which tabs to discard. The new plan is to build a machine learning - model to choose which tabs to discard. - - georgesak@chromium.org - - Site engagement score of a discarded tab. Recorded for each discard if the - score is available. - - - - - oysteine@chromium.org - - Recorded for each discarding, indicates whether the discarded tab succeeded - in doing a render process fast shutdown or not. - - - - - oysteine@chromium.org - - Recorded for each discarding, allowing us to know whether the discarded tab - succeeded an unsafe process shutdown (not invoking unload handlers). - - - - - georgesak@chromium.org - - Recorded for each discarding, allowing us to know whether the discarded tab - had a before unload handler or not. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Elapsed time between a tab getting discarded to eventually being reloaded by - the user. - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Elapsed time between the time a tab switched from being active to inactive - (that eventually gets discarded) until it gets reloaded. - - - - - - Removed 07/2018, and replaced by ResourceCoordinator.LocalDB.DatabaseInit. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database. - - - - - - Removed 07/2018, and replaced by - ResourceCoordinator.LocalDB.DatabaseInitAfterDelete. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database after deleting - it after a failed repair attempt. - - - - - - Removed 07/2018, and replaced by - ResourceCoordinator.LocalDB.DatabaseInitAfterRepair. - - sebmarchand@chromium.org - - The result of opening the Local Site Characteristics database after a repair - attempt. - - - - - - Removed 07/2018, and replaced by ResourceCoordinator.LocalDB.DatabaseRepair. - - sebmarchand@chromium.org - - The result of trying to repair the Local Site Characteristics database after - a failed open. - - - - - - Removed 06/2019, check Arc.LowMemoryKiller.FirstKillLatency instead. - - cywang@chromium.org - georgesak@chromium.org - - Elapsed time to collect memory usage of each tab triggered by a LogMemory() - call(). - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Cumulative number of discarded tabs that have been reloaded by the user, - recorded once per tab discard event. For example, a user who had 3 tabs - reloaded records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is - the number of sessions where users experienced N or more tab reload events. - - - - - - Removed 11/2017. Analysis showed that MRU was as good as engagement score to - choose which tabs to discard. The new plan is to build a machine learning - model to choose which tabs to discard. - - georgesak@chromium.org - - Site engagement score of a reloaded tab. Recorded for each reload if the - score is available. Note that this will be the same score the tab had when - discarded (which could have changed by the time it gets reloaded). - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Elapsed time between the last time a discarded tab was reloaded and the time - it gets closed. - - - - - chrisha@chromium.org - - The number of pages compressed per second when opening background tabs. This - is recorded at the end of the background tab opening session as an average - over the entire period (the duration of time from when the browser starts to - open background tabs until the time the browser has finished loading those - tabs or otherwise decided to stop loading them). The metric is not recorded - when the session overlaps with session restore. Only recorded on macOS. - Warning: This metric is a ratio and the session interval differs for each - session. It is hard to tell if it is average rate for each second in the - interval or it has a huge spike. - - - - - chrisha@chromium.org - - The number of pages decompressed per second when opening background tabs. - This is recorded at the end of the background tab opening session as an - average over the entire period (the duration of time from when the browser - starts to open background tabs until the time the browser has finished - loading those tabs or otherwise decided to stop loading them). The metric is - not recorded when the session overlaps with session restore. Only recorded - on macOS. Warning: This metric is a ratio and the session interval differs - for each session. It is hard to tell if it is average rate for each second - in the interval or it has a huge spike. - - - - - chrisha@chromium.org - - The number of swap-ins per second when opening background tabs. This is - recorded at the end of the background tab opening session as an average over - the entire period (the duration of time from when the browser starts to open - background tabs until the time the browser has finished loading those tabs - or otherwise decided to stop loading them). The metric is not recorded when - the session overlaps with session restore. Warning: This metric is a ratio - and the session interval differs for each session. It is hard to tell if it - is average rate for each second in the interval or it has a huge spike. - - - - - chrisha@chromium.org - - The number of swap-outs per second when opening background tabs. This is - recorded at the end of the background tab opening session as an average over - the entire period (the duration of time from when the browser starts to open - background tabs until the time the browser has finished loading those tabs - or otherwise decided to stop loading them). The metric is not recorded when - the session overlaps with session restore. Warning: This metric is a ratio - and the session interval differs for each session. It is hard to tell if it - is average rate for each second in the interval or it has a huge spike. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.BackgroundTabOpening.TabSwitchLoadTime.UntilTabIsLoaded. - - zhenw@chromium.org - - The tab load time of a tab that is switched to during a background tab - opening session (the duration of time from when the browser starts to open - background tabs until the time the browser has finished loading those tabs - or otherwise decided to stop loading them). Tab load time is defined as the - time between when the user switches to a backround tab, and the time when - that tab finishes loading in the foreground. If the user switches away - before the tab finishes loading, a metric will not be recorded unless the - user switches back, in which case the tab load time is measured from that - point in time. The metric is only recorded when a tab is switched to from - another tab within the same tabstrip. As a result, the initial forground tab - is not included in this metric since it was not switched to from another - tab. The metric is not recorded when the session overlaps with session - restore. - - - - - chrisha@chromium.org - - The tab load time of a tab that is switched to during a background tab - opening session (the duration of time from when the browser starts to open - background tabs until the time the browser has finished loading those tabs - or otherwise decided to stop loading them). Tab load time is defined as the - time between when the user switches to a backround tab, and the time when - that tab finishes loading in the foreground. If the user switches away - before the tab finishes loading, a metric will not be recorded unless the - user switches back, in which case the tab load time is measured from that - point in time. The metric is only recorded when a tab is switched to from - another tab within the same tabstrip. As a result, the initial forground tab - is not included in this metric since it was not switched to from another - tab. The metric is not recorded when the session overlaps with session - restore. - - - - - chrisha@chromium.org - - The number of pages compressed per second during session restore. Recorded - at the end of session restore as an average over the entire period, defined - as the period of time when session restore is actively loading tabs, which - ends when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. The metric is not recorded when the session overlaps with - background tab opening session. Only recorded on macOS. Warning: This metric - is a ratio and the session interval differs for each session. It is hard to - tell if it is average rate for each second in the interval or it has a huge - spike. - - - - - chrisha@chromium.org - - The number of pages decompressed per second during session restore. Recorded - at the end of session restore as an average over the entire period, defined - as the period of time when session restore is actively loading tabs, which - ends when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. The metric is not recorded when the session overlaps with - background tab opening session. Only recorded on macOS. Warning: This metric - is a ratio and the session interval differs for each session. It is hard to - tell if it is average rate for each second in the interval or it has a huge - spike. - - - - - chrisha@chromium.org - - Elapsed time between the start of the loading and the first contentful paint - of foreground tabs when the browser loads tabs in session restore. - - - - - chrisha@chromium.org - - Elapsed time between the start of the loading and the first meaningful paint - of foreground tabs when the browser loads tabs in session restore. - - - - - chrisha@chromium.org - - Elapsed time between the start of the loading and the first paint of - foreground tabs when the browser loads tabs in session restore. - - - - - chrisha@chromium.org - - The number of swap-ins per second during session restore. Recorded at the - end of session restore as an average over the entire period, defined as the - period of time when session restore is actively loading tabs, which ends - when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. The metric is not recorded when the session overlaps with - background tab opening session. Warning: This metric is a ratio and the - session interval differs for each session. It is hard to tell if it is - average rate for each second in the interval or it has a huge spike. - - - - - chrisha@chromium.org - - The number of swap-outs per second during session restore. Recorded at the - end of session restore as an average over the entire period, defined as the - period of time when session restore is actively loading tabs, which ends - when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. The metric is not recorded when the session overlaps with - background tab opening session. Warning: This metric is a ratio and the - session interval differs for each session. It is hard to tell if it is - average rate for each second in the interval or it has a huge spike. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.SessionRestore.TabSwitchLoadTime.UntilTabIsLoaded. - - chrisha@chromium.org - - The tab load time of a tab that is switched to during a session restore. Tab - load time is defined as the time between when the user switches to a - backround tab, and the time when that tab finishes loading in the - foreground. If the user switches away before the tab finishes loading, a - metric will not be recorded unless the user switches back, in which case the - tab load time is measured from that point in time. The metric is only - recorded when a tab is switched to from another tab within the same - tabstrip. As a result, the initial forground tab is not included in this - metric since it was not switched to from another tab. The metric is only - recorded when session restore is actively loading tabs, which ends when - either all tabs have been loaded and their pages rendered, or tab loading - needs to be deferred in cases where the system is under memory pressure. The - metric is not recorded when the session overlaps with background tab opening - session. - - - - - chrisha@chromium.org - - The tab load time of a tab that is switched to during a session restore. Tab - load time is defined as the time between when the user switches to a - backround tab, and the time when that tab finishes loading in the - foreground. If the user switches away before the tab finishes loading, a - metric will not be recorded unless the user switches back, in which case the - tab load time is measured from that point in time. The metric is only - recorded when a tab is switched to from another tab within the same - tabstrip. As a result, the initial forground tab is not included in this - metric since it was not switched to from another tab. The metric is only - recorded when session restore is actively loading tabs, which ends when - either all tabs have been loaded and their pages rendered, or tab loading - needs to be deferred in cases where the system is under memory pressure. The - metric is not recorded when the session overlaps with background tab opening - session. - - - - - - Removed on 21/1/2019. - - chrisha@chromium.org - lpy@chromium.org - - Measures the time duration from when the tab is backgrounded to when a - JavaScript alert is updated. Only recorded when the tab is in the - background. - - - - - - Removed on 21/1/2019. - - chrisha@chromium.org - lpy@chromium.org - - Measures the time duration from when the tab is backgrounded to when audio - starts to play. Only recorded when the tab is in the background. - - - - - chrisha@chromium.org - lpy@chromium.org - - Measures the time duration from when the tab is backgrounded to when its - favicon is updated. The first-time set of favicon will be ignored; this - metric will only be recorded after 5 minutes from main frame navigation - committed and when the tab is in the background. - - - - - chrisha@chromium.org - lpy@chromium.org - - Measures the time duration from when the tab is backgrounded to when a - non-persistent notification is created. Only recorded when the tab is in the - background. - - - - - chrisha@chromium.org - lpy@chromium.org - - Measures the time duration from when the tab is backgrounded to when its - title is updated. The first-time set of title will be ignored; this metric - will only be recorded after 5 minutes from main frame navigation committed - and when the tab is in the background. - - - - - chrisha@chromium.org - - Whether background tab opening session is overlapped with other types of - session, e.g., session restore. Background tab opening session is the - duration of time from when the browser starts to open background tabs until - the time the browser has finished loading those tabs or otherwise decided to - stop loading them. This metric helps to understand how often background tab - opening has overlap with other sessions. - - - - - chrisha@chromium.org - - Whether session restore is overlapped with other types of session, e.g., - background tab opening. Session restore is the duration from the time when - the browser starts to restore tabs until the time when the browser has - finished loading those tabs or when the browser stops loading tabs due to - memory pressure. This metric helps to understand how often session restore - has overlap with other sessions. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.SessionRestore.CompressedPagesPerSecond. - - fmeawad@chromium.org - - The number of pages compressed per second during session restore. Recorded - at the end of session restore as an average over the entire period, defined - as the period of time when session restore is actively loading tabs, which - ends when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. Only recorded on macOS. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.SessionRestore.DecompressedPagesPerSecond. - - fmeawad@chromium.org - - The number of pages decompressed per second during session restore. Recorded - at the end of session restore as an average over the entire period, defined - as the period of time when session restore is actively loading tabs, which - ends when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. Only recorded on macOS. - - - - - - Removed June 2020. - - chrisha@chromium.org - - The expected queueing duration of tasks in a foreground tab during session - restore. This metric reflects the responsiveness of a tab. A lower value - means the tab will respond to inputs faster. This metric is equal to - RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all - tasks in each 1000-ms window. The metric is not recorded when the session - overlaps with background tab opening session. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.SessionRestore.SwapInPerSecond. - - fmeawad@chromium.org - - The number of swap-ins per second during session restore. Recorded at the - end of session restore as an average over the entire period, defined as the - period of time when session restore is actively loading tabs, which ends - when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. - - - - - - Removed 08/2017, and replaced by - TabManager.Experimental.SessionRestore.SwapOutPerSecond. - - fmeawad@chromium.org - - The number of swap-outs per second during session restore. Recorded at the - end of session restore as an average over the entire period, defined as the - period of time when session restore is actively loading tabs, which ends - when either all tabs have been loaded and their pages rendered, or tab - loading needs to be deferred in cases where the system is under memory - pressure. - - - - - chrisha@chromium.org - - The loading state of a tab at the time the user switched to it during a - session restore. The metric is only recorded when a tab is switched to from - another tab within the same tabstrip. As a result, there are two cases where - tabs are not included. The first case is when the initial forground tab is - shown, since it was not switched to from another tab. The second case is - when switching between different windows, either between two tabs in - different browser windows, or when switching to a different application and - switching back to the browser. The metric is only recorded when session - restore is actively loading tabs, which ends when either all tabs have been - loaded and their pages rendered, or tab loading needs to be deferred in - cases where the system is under memory pressure. The metric is not recorded - when the session overlaps with background tab opening session. - - - - - michaelpg@chromium.org - charleszhao@chromium.org - - Logged when calculating a tab reactivation score for a background tab. Any - value other than "none" may indicate a bug in the inference code, - a problem with the preprocessor configuration shipped with the model, or a - bug in the code that populates the RankerExample for a tab. - - - - - aebacanu@chromium.org - carlscab@chromium.org - sreejakshetty@chromium.org - - Duration between restoring a tab when "Reopen Closed Tab" button - was clicked or any of Ctrl+Shift+T (on Linux/Windows/Chrome OS) and - Command+Shift+T (on Mac) were pressed and the closing of the same tab. - Recorded when the user manually restores a tab. - - - - - aebacanu@chromium.org - carlscab@chromium.org - sreejakshetty@chromium.org - - Duration between restoring a whole window (multiple tabs) when "Reopen - Closed Window" button was clicked or any of Ctrl+Shift+T (on - Linux/Windows/Chrome OS) and Command+Shift+T (on Mac) were pressed and the - closing of the same window. Recorded when the user manually restores a - window. - - - - - sky@chromium.org - - Error code returned by [moveItemAtPath:toPath:error:] when moving previous - session file to backup file before restoring. 0 in case of success. - - - - - sky@chromium.org - - Error code returned by [removeItemAtPath:error:] when removing previous - session backup file. 0 in case of success. - - - - - sky@chromium.org - - Error code returned by [removeItemAtPath:error:] when removing previous - session file. 0 in case of success. - - - - - marq@chromium.org - - [iOS] The number of tabs open when the app comes out of the background. - - - - - marq@chromium.org - [Android and iOS] The number of tabs open at cold launch. - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The tab index from the beginning of the tab strip when switching into a tab. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The tab index from the end of the tab strip when switching into a tab. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The offset between the tab currently selected tab and the newly selected - tab. - -
- If the user switches to a tab to the left of their currently selected tab, - we log a positive offset value indicating how many tabs to the left they - moved. If the user switches to a tab to the right of their currently - selected tab, we log a negative offset value. -
- - - - - Removed 10/2015, and replaced by TabManager.Discarding.DiscardCount. - - jamescook@chromium.org - - Cumulative number of tabs discarded due to low memory conditions, recorded - once per tab discard event. For example, a user who had 3 tabs discarded - records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the number - of sessions where users experienced N or more tab discard events. - - - - - - Removed 11/2017. Average number of minutes between discard events is - available in Tabs.Discard.InitialTime2 and Tabs.Discard.IntervalTime2. - - jamescook@chromium.org - - Whether or not a tab was discarded in the last minute of usage. Total count - is number of minutes of device usage. 100 / discard percentage gives the - average number of minutes between discard events. - - - - - - Removed May 4, 2012. Replaced by Tabs.Discard.InitialTime2 because this stat - had too low of a range maximum. No longer tracked. - - jamescook@chromium.org - - Time in seconds between system startup and when the first tab is discarded - due to low memory conditions. Higher is better. - - - - - - Removed 11/2017. Replaced with Discarding.Urgent.TimeSinceStartup which is - recorded when Chrome has to discard tabs or apps urgently (instead of before - an individual tab is urgently or proactively discarded). - - jamescook@chromium.org - - Time in seconds between system startup and when the first tab is discarded - due to low memory conditions. Higher is better. Range maximum is - approximately one day. - - - - - - Removed May 4, 2012. Replaced by Tabs.Discard.IntervalTime2 because this - stat had too low of a range maximum. No longer tracked. - - jamescook@chromium.org - - Time in seconds between tab discard events after the first one, recorded - once per discard event. Higher is better. - - - - - - Removed 11/2017. Replaced with Discarding.Urgent.TimeSinceLastUrgent which - is recorded before a set of tabs/apps are urgently discarded (instead of - before an individual tab is urgently or proactively discarded). - - jamescook@chromium.org - - Time in milliseconds between tab discard events after the first one, - recorded once per discard event. Should occur no faster than once every 750 - ms. Higher is better. - - - - - - Removed 05/2019 - - jamescook@chromium.org - - System-wide memory allocation at the time a tab was discarded, roughly - equivalent to the sum of memory allocated with malloc() in userspace plus - graphics driver memory. - - - - - - Removed December 7, 2012. Replaced by Tabs.Discard.MemAllocatedMB because - this stat has insufficient precision in the 2-4 GB range and does not - properly account for graphics memory on ARM. - - jamescook@chromium.org - - System-wide anonymous memory allocation at the time a tab was discarded, - roughly equivalent to memory allocated with malloc(). - - - - - - Removed 05/2019 - - jamescook@chromium.org - - System-wide file-backed memory plus free memory, roughly equivalent to what - the kernel uses to trigger low-memory notifications for tab discards. If - lower than the kernel's threshold then we are not effectively freeing memory - in response to the initial notification and are repeatedly being notified. - - - - - - Removed 05/2019 - - jamescook@chromium.org - - Graphics driver (GEM object) memory at the time of a tab discard. - - - - - - Removed 05/2019 - - jamescook@chromium.org - - System-wide shared memory at the time of a tab discard. Used primarily for - shared buffers in the graphics system. Tracked because it's a historical - source of leaks on Chrome OS. - - - - - - Removed 10/2015, and replaced by TabManager.Discarding.ReloadCount. - - jamescook@chromium.org - - Cumulative number of times a tab was reloaded because it was discarded and - the user clicked on it later, recorded once per reload event. For example, a - user who clicks on 3 discarded tabs will record a count in the 1 bin, 2 bin, - and 3 bin. Thus each bin N is the number of sessions where users experienced - N or more reload events. Compare to Tabs.Discard.DiscardCount. - - - - - - Removed 11/2017. Replaced with Discarding.Urgent.NumAliveTabs which records - the number of tabs that are not pending load or discarded when an urgent - discard request is received (vs. this that records the total number of tabs - every time a tab is discarded, no matter the reason). - - jamescook@chromium.org - - The number of tabs open across all browser windows when a tab was discarded - due to low memory conditions. - - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between closing a tab and opening another, to - track very frequent tabs. - - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between opening a tab and opening another, to - track very frequent tabs. - - - - - - Removed 2019-07. - - joenotcharles@google.com - - Fine-grained (in msec) time between opening a tab and closing it, to track - very short-lived tabs. - - - - - pkotwicz@chromium.org - - Records the "Tab Creation Rank" for the first background tab which - was switched to the foreground. The "Tab Creation Rank" is - relative to other background tabs which were opened from the same URL via - the context menu. The oldest background tab has a rank of zero. - - - - - pkotwicz@chromium.org - - Records the "Reverse Tab Creation Rank" for the first background - background tab which was switched to the foreground. The "Reverse Tab - Creation Rank" is relative to other background tabs which were opened - from the same URL via the context menu. The newest background tab has a - "Reverse Tab Creation Rank" of zero. - - - - - dtrainor@chromium.org - yusufo@chromium.org - - [Android] Age (time since the last display in previous sessions) of the - foreground tab being restored on the browser cold start. - - - - - - Removed 2020-06. - - - - adityakeerthi@google.com - fdoray@chromium.org - - The percentage of hidden tabs that are frozen. This metric is recorded every - 5 minutes, as a tab heartbeat metric. Desktop only. - - - - - mattsimmons@chromium.org - memex-team@google.com - The number of entries/cards shown in the grid tab switcher. -
- When the user is shown the grid tab switcher, logs the number of entries - (tabs or tab groups) open in the grid tab switcher. -
- - - - - Code removed long ago. - - pauljensen@chromium.org - - Page load time (PLT) for iOS that does not include time spent following - redirects. On other platforms this is calculated from Navigation Timings but - on iOS Navigation Timings are not available so we're recreating a - calculation similar to PLT.PT_RequestToFinish but not including time spent - following redirects. This metric represents the time between when navigation - is initiated (prior to DNS, TCP connect, etc but after following redirects) - until loading ends (i.e. JS onload event). On non-iOS Chrome this is - (performance.timing.loadEventEnd - performance.timing.redirectEnd). On - Chrome for iOS we're calculating the time between the creation of the - top-level URLRequest and when webDidFinishWithURL is called. - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The maximum number of tabs that Chrome displays at the same time over the - course of a day. Desktop only. - - NOTE: This metric is asynchronous, the value reported on a given day - represents the previous day's observations (which can be from a different - build). - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The maximum number of tabs per window that Chrome displays over the course - of a day. Desktop Only. - - NOTE: This metric is asynchronous, the value reported on a given day - represents the previous day's observations (which can be from a different - build). - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The maximum number of windows existing at the same time over the course of a - day. Desktop only. - - NOTE: This metric is asynchronous, the value reported on a given day - represents the previous day's observations (which can be from a different - build). - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - The number of tabs total at resume from sleep/hibernate. This is being - logged on all desktop platforms. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - CriticalPersistedTabData stores data pertinent to the running of the app - such as tab id, parent id, web contents. This data is serialized and stored - across restarts. This records if the deserialization succeeds or fails. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - CriticalPersistedTabData stores data pertinent to the running of the app - such as tab id, parent id, web contents. This data is serialized and stored - across restarts. This records if the serialization succeeds or fails. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - FilePersistedTabData storage stores serialized PersistedTabData (metadata - persisted across restarts) in a file. This metric records if a delete was - successful or unsuccessful. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - FilePersistedTabData storage stores serialized PersistedTabData (metadata - persisted across restarts) in a file. This metric records if a delete - operation was found to have the file not existing. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - FilePersistedTabData storage stores serialized PersistedTabData (metadata - persisted across restarts) in a file. This metric records if a restore was - successful or unsuccessful. - - - - - yusufo@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - davidjm@chromium.org - - FilePersistedTabData storage stores serialized PersistedTabData (metadata - persisted across restarts) in a file. This metric records if a save was - successful or unsuccessful. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab crashed with "Aw, Snap!", - recorded once per tab crash event. For example, a user who crashed 3 tabs - will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the - number of sessions where users experienced N or more crash events. The user - may not have actually seen the sad tab page, as it might have been an - inactive tab. Compare to Tabs.SadTab.CrashDisplayed. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab crashed with "Aw, Snap!" and the - user saw the page, recorded once per tab crash event. For example, a user - who crashed 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus - each bin N is the number of sessions where users experienced N or more crash - events. Compare to Tabs.SadTab.CrashCreated. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Counts of events from the style of sad tab which has a feedback button as - its primary action. Currently, events include being displayed (actually - visible in a window), and the actions a user can take on the page. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab was killed with a "He's dead, - Jim!" page, which is usually due to the renderer being killed, recorded - once per tab kill event. For example, a user who loses 3 tabs will record a - count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of - sessions where users experienced N or more kill events. The user may not - have actually seen the sad tab page, as it might have been an inactive tab. - Compare to Tabs.SadTab.KillDisplayed. This can happen due to out of memory, - malformed IPC messages, or a SIGINT/TERM/KILL signal sent by a user. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab was killed with a "He's dead, - Jim!" page due to the kernel out-of-memory killer, recorded once per - tab kill event. For example, a user who loses 3 tabs will record a count in - the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions where - users experienced N or more kill events. The user may not have actually seen - the sad tab page, as it might have been an inactive tab. Compare to - Tabs.SadTab.KillDisplayed. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab was killed with a "He's dead, - Jim!" page and the user saw the page, recorded once per tab kill event. - For example, a user who loses 3 tabs will record a count in the 1 bin, 2 - bin, and 3 bin. Thus each bin N is the number of sessions where users - experienced N or more kill events. Compare to Tabs.SadTab.CrashCreated. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Cumulative number of times a tab was killed with a "He's dead, - Jim!" page due to the kernel out-of-memory killer and the user saw the - page, recorded once per tab kill event. For example, a user who loses 3 tabs - will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the - number of sessions where users experienced N or more kill events. Compare to - Tabs.SadTab.CrashCreated. - - - - - wfh@chromium.org - - Cumulative number of times a tab crashed with "Aw, Snap!", - recorded once per tab oom event. For example, a user who ran out of memory - in 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin - N is the number of sessions where users experienced N or more oom events. - The user may not have actually seen the sad tab page, as it might have been - an inactive tab. Compare to Tabs.SadTab.OomDisplayed. - - - - - wfh@chromium.org - - Cumulative number of times a tab ran out of memory with "Aw, - Snap!" and the user saw the page, recorded once per tab oom event. For - example, a user who ran out of memory in 3 tabs will record a count in the 1 - bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions where users - experienced N or more oom events. Compare to Tabs.SadTab.OomCreated. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - Counts of events from the style of sad tab which has a reload button as its - primary action. Compare to Tabs.SadTab.Feedback.Event. - - - - - sonnyrao@chromium.org - jamescook@chromium.org - - The number of times a tab was reloaded because it was killed (usually by the - kernel OOM killer) and the user clicked on it later, recorded once per - reload event. For example, a user who clicks on 3 discarded tabs will record - a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of - sessions where users experienced N or more reload events. Compare to - Tabs.Discard.DiscardCount. - - - - - davidjm@chromium.org - nyquist@chromium.org - dtrainor@chromium.org - yusufo@chromium.org - - Records load time of a Tab using {SavedTabMethod} storage and whether the - {SavedTabLoadResult} - - - - - - - - - - - - - corising@chromium.org - chrome-desktop-ui-sea@google.com - - This histogram records the number of tabs that are 'scrubbed' by key press - during a given interval of time (i.e. ctrl+tab navigation). For this metric, - a tab is considered 'scrubbed' if it was active for less than or equal to a - given amount of time. - - - - - corising@chromium.org - chrome-desktop-ui-sea@google.com - - This histogram records the number of tabs that are 'scrubbed' by mouse press - during a given interval of time. For this metric, a tab is considered - 'scrubbed' if it was active for less than or equal to a given amount of - time. - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The distance a user multi-finger scrubbed to change tabs. Always positive - (ignores left / right). - - - - - afakhry@chromium.org - tclaiborne@chromium.org - - The duration a user spent doing multi-finger scrubbing to change tabs before - a different tab than the currently active one was actually activated. - - - - - - No longer logged - - - Applicability of speculative tab restore, recorded every time a tab is - switched. This allows to estimate the fraction of tab restores experienced - on mobile that can be mitigated using speculative restore. Options higher in - the enum take precedence over the lower ones (i.e. low-memory tablet will be - accounted as tablet). - - - - - - No longer logged - - - Accuracy of the tab switch predictions made when the user begins the side - swipe gesture. - - - - - - No longer logged - - - Accuracy of the tab switch predictions made when the user enters the tab - switcher. - - - - - - No longer logged - - - Status of a tab recorded when the tab is targeted with speculative restore. - - - - - - No longer logged - - - Time between starting the speculative load and actual tab switch for correct - speculative load predictions made when the user begins the side swipe - gesture. - - - - - - No longer logged - - - Time between starting the speculative load and actual tab switch for correct - speculative load predictions made when the user enters the tab switcher. - - - - - kouhei@chromium.org - tzik@chromium.org - - Recorded once per tab activation. The number of tabs that were activated - while the tab was inactive. - -
- This metric is to be removed after M46 hits stable. We don't expect this - metric to change over release, so we will remove this once we have the - numbers from stable. -
- - - - kouhei@chromium.org - tzik@chromium.org - - Number of tabs between the previously active tab and the new active tab. - -
- This metric is to be removed after M46 hits stable. We don't expect this - metric to change over release, so we will remove this once we have the - numbers from stable. -
- - - - kouhei@chromium.org - tzik@chromium.org - - The state to which a tab transitioned. Recorded when a tab transitions from - the state in the histogram name to a new state. - -
- kouhei@ and tzik@ will remove some variation of these once M46 hits stable. -
- - - - - Removed as of 4/2017. - - kouhei@chromium.org - tzik@chromium.org - - Tabs.StateTransfer.TimeA_B measures the time a tab was in state A before it - transferred to state B. - - - - - - Removed as of 07/2020. Rename to - Tabs.Suggestions.NumSuggestionsChanged.Closing. - - yusufo@chromium.org - davidjm@chromium.org - - The user is presented with recommendations on which Tabs they could close. - The user has the option to: 1) Remove a Tab from the recommendation 2) Add a - Tab which wasn't in the recommendation to the recommendation - - This metric records the sum of the number of times the user does 1) or 2) - and is a measure of how useful the recommendation is. This metric is - recorded after the user accepts a recommendation - potentially with edits by - performing 1) or 2). - - - - - yusufo@chromium.org - davidjm@chromium.org - meiliang@chromium.org - - The user is presented with recommendations on which Tabs they could take the - suggested action. The user has the option to: 1) Remove a Tab from the - recommendation 2) Add a Tab which wasn't in the recommendation to the - recommendation. - - This metric records the sum of the number of times the user does 1) or 2) - and is a measure of how useful the recommendation is. This metric is - recorded after the user accepts a recommendation - potentially with edits by - performing 1) or 2). - - Note: Adding and removing the same Tab, or vice versa, would be counted as - 0. - - - - - dtrainor@chromium.org - yusufo@chromium.org - - [Android] Time between the event that closes a tab and the start of - rendering. - - - - - dtrainor@chromium.org - yusufo@chromium.org - - [Android] Time between the event that exits an app and the start of - rendering. - - - - - dtrainor@chromium.org - yusufo@chromium.org - - [Android] Time between the event that creates a tab and the start of - rendering. - - - - - dtrainor@chromium.org - yusufo@chromium.org - - [Android] Time between the event that selects a tab and the start of - rendering. - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Counts the number of tabs across all windows, reported every 5 minutes. - Desktop only. - - - - - - - markchang@google.com - - The number of tabs open in the active window when a load completes. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The number of tabs in the current active group when a load completes. - Records 0 if the active tab is not in a group. - - - - - mattsimmons@chromium.org - memex-team@google.com - - The number of tabs open when the grid tab switcher is shown. - -
- When the user is shown the tab switcher, logs the total number of individual - open tabs. Android only. -
- - - - mattsimmons@chromium.org - memex-team@google.com - - The number of tabs open when the user is returned to the tab switcher on - start. - -
- When the user is returned to the tab switcher on starting Chrome due to - inactivity, logs the overall number of tabs open. Android only. -
- - - - mpearson@chromium.org - chrome-desktop-ui-sea@google.com - sbirch@google.com - - The number of tabs open in all browsers (counting app-mode windows) when a - load completes. - -
- This is basically the average number of tabs over time. - - See also MPArch.RPHCountPerLoad for the number of processes used by these - tabs. -
- - - - mpearson@chromium.org - chrome-desktop-ui-sea@google.com - - The number of tabs open per window (counting app-mode windows) when a load - completes. - -
- This value will be recorded multiple times per load if more than one window - is open. -
- - - - yusufo@chromium.org - - How many tabs a user moved forward or backward in the Android tab switcher. - -
- Logged by the Android tab switcher when a user switches tabs (other than by - opening a new tab). If the user switches to an earlier tab in the stack, we - log a positive offset value indicating how many tabs back they moved. If the - user switches to a later tab, we log a negative offset value. If the user - stays on the same tab, we log 0. If the user switches to a tab in a - different stack (i.e. they switch from normal to incognito or vice-versa), - we don't log a value. -
- - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search for and switch to - their desired tabs. The Tab Search UI is shown in a bubble anchored to an - element of the UI in the browser window. - - The bubble is dismissed when it loses focus or the escape key is pressed. - This metric tracks if the UI bubble was dismissed as a result of an action - taken from within the UI (such as switching to an open tab) or dismissed - without direct interaction with the Tab Search UI. - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for their desired tabs and close any currently open tabs. This records the - number of tabs closed from a single instance of the UI (the number of tabs - closed from within Tab Search in the time between when the UI is open and - when it is closed). - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for their desired tabs. It can be opened and closed. This records the number - of tabs there are in the payload Tab Search is sent when it is first opened. - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for their desired tabs. It can be opened and closed. This records the number - of windows there are in the payload Tab Search is sent when it is first - opened. - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search for and switch to - their desired tabs. The Tab Search UI is shown in a bubble anchored to an - element of the UI in the browser window. - - The bubble can be invoked via a number of different means including mouse - click, keyboard navigation, keyboard shortcut or touch gesture. This metric - tracks the kind of action the user took to invoke the Tab Search bubble UI. - - - - - tluk@chromium.org - robliao@chromium.org - - Records the time taken to load the Tab Search WebUI and render (at least) - the initial list of tabs. This is roughly equivalent to 'time to first - meaningful paint' for the Tab Search UI. - - - - - tluk@chromium.org - robliao@chromium.org - - The amount of time between the render frame host StartProvisionalLoad event - and the render frame DocumentOnLoadCompleted event for the Tab Search WebUI - page. - - - - - tluk@chromium.org - robliao@chromium.org - - The amount of time between the render frame host StartProvisionalLoad and - DidFinishDocumentLoad events for the Tab Search WebUI page. - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for and switch to their desired tabs. This records whether the user used Tab - Search to switch to a tab from a filtered search results list or the default - unfiltered list. - - - - - - Removed as of 09/2020 as the way the metric is emitted has changed. Replaced - with Tabs.TabSearch.WindowDisplayedDuration2. - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for their desired tabs. It can be opened and closed. This records the amount - of time between when a Tab Search bubble is opened and when it is closed. It - does so by recording the difference in time between when the Tab Search's - WebView is first set visible and when the WebView's destructor is called. - - The Tab Search UI is a bubble anchored to an element within a browser window - and is closed if the user switches to a tab, presses the escape key or - performs an action to return focus to the hosting window. The Tab Search UI - bubble will also close if the hosting browser window is closed or crashes. - - Users may leave the bubble open for long periods of time without directly - interacting with the UI which could result in a long tail of displayed - durations. - - - - - tluk@chromium.org - robliao@chromium.org - - Tab Search is a feature that allows users to better search their browsers - for their desired tabs. It can be opened and closed. This records the amount - of time between when a Tab Search bubble is opened and when it is closed. It - does so by recording the difference in time between when the Tab Search's - bubble is first shown and when the bubble's destructor is called. - - The Tab Search UI is a bubble anchored to an element within a browser window - and is closed if the user switches to a tab, presses the escape key or - performs an action to return focus to the hosting window. The Tab Search UI - bubble will also close if the hosting browser window is closed or crashes. - - Users may leave the bubble open for long periods of time without directly - interacting with the UI which could result in a long tail of displayed - durations. - - - - - sebmarchand@chromium.org - - Counts how often tab stats daily interval events were fired. - - - - - yusufo@chromium.org - wychen@chromium.org - - The average tab group size, average number of tabs in a group, on a cold - start after all tabs are restored. - - - - - yusufo@chromium.org - wychen@chromium.org - - During tab restoration, a tab is considered as a duplicated tab when it has - an identical url with another restored tab. - - This histogram records the number of duplicated tabs on a cold start after - all tabs are restored. The possible range for this number is from 0 to total - number of restored tabs minus 1. In other words, this number is equals to - total number of restored tabs minus the number of unique URLs. - - - - - yusufo@chromium.org - wychen@chromium.org - - During tab restoration, a tab is considered as a duplicated tab when it has - an identical url with another restored tab. - - This histogram records the ratio of duplicated tabs to the total number of - tabs on a cold start after all tabs are restored. This ratio will never - reach 100%, since the highest possible number of duplicated tabs is total - number of restored tabs minus 1. - - - - - - - yusufo@chromium.org - wychen@chromium.org - - The cumulative number of "spokes" from any "hub" page in - every tab. A "hub" is any page that the user navigates away from, - and a "spoke" is a page that's navigated to. The - "spokes" count is incremented and recorded each time the user - navigates back to a "hub" page via navigation back button and then - navigates to a new "spoke". - - - - - - - yusufo@chromium.org - wychen@chromium.org - zea@chromium.org - - This recorded value is the number of currently open tabs that were created - from a given source. This is recorded when entering the tab switcher mode. - - - - - - - yusufo@chromium.org - wychen@chromium.org - zea@chromium.org - - The recorded value is the percentage of the number of currently open tabs - that are created from a given source, relative to the total number of - currently open tabs. This is recorded when entering the tab switcher mode. - - - - - yusufo@chromium.org - wychen@chromium.org - - The number of tab groups on a cold start after all tabs are restored. - - - - - yusufo@chromium.org - wychen@chromium.org - - The tab group density, the ratio of the number of tab groups to the total - number of tabs, on a cold start after all tabs are restored. - - - - - yusufo@chromium.org - wychen@chromium.org - - The number of tabs is belonging to a tab group on a cold start after all - tabs are restored. - - - - - yusufo@chromium.org - wychen@chromium.org - - The ratio of all tabs in tab groups to the total number of tabs on a cold - start after all tabs are restored. - - - - - - Removed 2019-07. - - alexmos@chromium.org - dcheng@chromium.org - - Reports the delta between the last user interaction time with a WebContents - and the time browser code wants to verify a recent user interaction with - that WebContents. Used to tune the threshhold for timing out a user - interaction. - - - - - mattsimmons@chromium.org - memex-team@google.com - - When a tab is revisited and subsequently the omnibox is focused within a - certain threshold of time, this reports the amount of time in seconds that - has passed since the last user engagement with the tab. Currently - Android-only. - - - - - mattsimmons@chromium.org - memex-team@google.com - - When a tab is closed, this reports the amount of time in seconds that has - passed since the last user engagement with the tab. Currently Android-only. - - - - - mattsimmons@chromium.org - memex-team@google.com - - When a tab is revisited, this reports the amount of time in seconds that has - passed since the last user engagement with the tab. Currently Android-only. - - - - - sebmarchand@chromium.org - - The number of tabs that haven't been interacted with, visible or audible - over a given interval time, but which no longer exist at all at the end of - this interval. - - - - - sebmarchand@chromium.org - - The number of tabs that haven't been interacted with, visible or audible or - visible during a given interval of time and still exist at the end of this - interval. - - - - - sebmarchand@chromium.org - - The number of tabs that have been interacted with, visible or audible over a - given interval of time, but which no longer exist at all at the end of this - interval. - - - - - sebmarchand@chromium.org - - The number of tabs that have been interacted with, visible or audible during - a given interval of time, includes tabs that don't exist at the end of this - interval. - - - - - - - sebmarchand@chromium.org - catan-team@chromium.org - - Counts the number of Chrome windows, reported every 5 minutes. Desktop only. - - - - - - Removed 2019-06. - - afakhry@chromium.org - - The requested window creation state from the tabs extensions API when it's - used to create a new window or update the state of an existing one. - - - - - collinbaker@chromium.org - chrome-desktop-ui-sea@google.com - - Total time spent in each call of TabStrip::PaintChildren(). This comprises - the paint time for all parts of the TabStrip that do not paint to their own - layers. This is recorded at the end of TabStrip::PaintChildren(), when all - child views are finished painting. - - As of writing (May 17, 2019), this always includes the tab backgrounds, - strokes, labels, close buttons. The tab icons and new tab button sometimes - paint to their own layer; in frames where this is so, their times won't be - included here. - - - - - yusufo@chromium.org - wychen@chromium.org - - When conditional tab strip shows, records which kind of intentional - tab-related action triggered it. - - - - - collinbaker@chromium.org - chrome-desktop-ui-sea@google.com - - Time spent painting a tab icon. This includes a page's favicon and loading - animation (when loading). This is recorded at the end of TabIcon::OnPaint(). - - - - - yusufo@chromium.org - wychen@chromium.org - - This histogram records the number of tabs within the group during page load. - - If the loading happens in a tab that does not belong to a group, we log 0. - Else, we log a positive number >= 2. - - - - - connily@chromium.org - cyan@chromium.org - chrome-desktop-ui-sea@google.com - - The amount of time from cursor entering the tabstrip to first click on a tab - to switch. - -
- This will exclude some kinds of switching (hotkeys, between windows) where - it would be difficult to define a start time. Entering the tabstrip is an - approximation which will vary between users, but should still be useful for - A/B comparison. -
- - - - yusufo@chromium.org - wychen@chromium.org - - A tab strip session starts when the last time Chrome comes to the foreground - was more than an hour ago. At the beginning of a tab strip session, records - the user status of conditional tab strip feature in the last tab strip - session. - - - - - altimin@chromium.org - farahcharab@chromium.org - - Used to track the number of active task queues in the task queue manager. - Reported every time a task is selected for execution. - - - - - altimin@chromium.org - farahcharab@chromium.org - - Used to track the number of tasks serviced due to starvation versus the - number of tasks serviced due to priroity. Incremented whenever a task queue - is selected to service. - - - - - - Removed 10/2018. Instead of recording a histogram with the number of - BLOCK_SHUTDOWN tasks posted during shutdown, we generate a crash when too - many BLOCK_SHUTDOWN tasks are posted during shutdown. A crash dump is more - actionnable than a histogram. - - fdoray@chromium.org - - Number of BLOCK_SHUTDOWN tasks that were posted to a base::TaskScheduler - after its Shutdown() method was called but before it returned. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Time elapsed between when the thread managed by a SchedulerWorker is - detached and when the main function of a new thread managed by the same - SchedulerWorker is entered (following a wake up). Recorded each time that a - thread is recreated for a given SchedulerWorker. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Latency of dummy "heartbeat" tasks posted with specific traits - (see suffix). The heartbeat recording avoids dependencies between this - report and other work in the system. See - TaskScheduler.TaskLatencyMicroseconds.* for a metric that is closer to the - real workload. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - etiennep@chromium.org - fdoray@chromium.org - gab@chromium.org - - Number of workers running a task in a given SchedulerWorkerPool. Recorded - every 59 minutes (sampling rate is not expected to affect the distribution). - - - - - - Removed as of 03/2019. The number of cancelled delayed tasks found by the - lazy approach is 0 more than 99% of the time. - - adityakeerthi@google.com - fdoray@chromium.org - - Lower-bound number of cancelled tasks that remain in the DelayedTaskManager. - An exact number is not recorded, as it could potentially be expensive to - calculate. Instead, a lazy count is maintained by noting cancelled tasks as - new delayed tasks are added. Recorded every time the ServiceThread performs - a heartbeat latency report. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Number of tasks executed by a SchedulerWorker before it detached. Recorded - when a SchedulerWorker detaches. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Number of tasks executed by a SchedulerWorker between two waits on its - WaitableEvent. This should be maximized without affecting perceived browser - performance. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - - Number of tasks run by TaskScheduler while task was queuing (from time task - was posted until time it was run). Recorded for dummy "heartbeat" - tasks posted with specific traits (see suffix). The heartbeat recording - avoids dependencies between this report and other work in the system. - Recorded every time the ServiceThread performs a heartbeat latency report. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - etiennep@chromium.org - fdoray@chromium.org - gab@chromium.org - - Number of workers that live in a given SchedulerWorkerPool. Recorded every - 59 minutes (sampling rate is not expected to affect the distribution). - - - - - - Removed as of 03/2019. The number of cancelled delayed tasks found by the - lazy approach is 0 more than 99% of the time. - - adityakeerthi@google.com - fdoray@chromium.org - - Lower-bound percentage of tasks in the DelayedTaskManager that have been - cancelled. An exact number is not recorded, as it could potentially be - expensive to calculate. Instead, a lazy count is maintained by noting - cancelled tasks as new delayed tasks are added. Recorded every time the - ServiceThread performs a heartbeat latency report. - - - - - - Removed 4/2017. Units changed from milliseconds to microseconds. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Time elapsed between when a task is posted and when it starts to run. - Recorded for each task that runs inside the TaskScheduler. This metric is - useful to determine true latency of the average task in the average runtime - scenario. Its total count can also be used as a proxy for the number of - tasks posted to a given category. On the other hand, a fallout of this - metric is that timing every task means each report is dependent on the many - things that can cause an individual task to be delayed (e.g. tasks on a - single bogged down sequence will be reported with high latency even if not - stalling the scheduler itself). See - TaskScheduler.HeartbeatLatencyMicroseconds.* for a metric that is - independent of such factors. - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Time elapsed between when a task is posted and when it starts to run. - Recorded for each task that runs inside the TaskScheduler. - - - - - - Removed 07/2020. - - alancutter@chromium.org - calamity@chromium.org - joelhockey@chromium.org - - Number of times that each menu item is clicked from the terminal system app - menu button. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether we found multiple matches for a selector. Recorded when - TextFragmentAnchor finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether the page did a non-zero scroll in order to scroll the match into - view. Only recorded if we found a match and scrolled it into view. Recorded - when TextFragmentAnchor finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The raw length of the directive in the URL (e.g. spaces count as the three - characters '%20'), regardless of how many text= terms there are. Recorded if - there was a text directive, regardless of whether a match was found. - Recorded when TextFragmentAnchor finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether an element-id based fragment was found in the document. Counted only - when a fragment was specified and it wasn't parsed into a |targetText| style - anchor. - - - - - nburris@chromium.org - bokan@chromium.org - - The length of the end parameter, in the case of a range match. Only recorded - if a match was found. Recorded when TextFragmentAnchor finishes searching - once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The length of the matched text, in the case of an exact match. Only recorded - if a match was found. Recorded when TextFragmentAnchor finishes searching - once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether the match was within a list item. Only recorded for exact text - fragments and only if a match was found. Recorded when TextFragmentAnchor - finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The percentage of selectors for which a match was found in the document. - Recorded when TextFragmentAnchor finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - An enum indicating which parameters were specified in the text fragment - anchor. Only recorded if a match was found. Recorded when TextFragmentAnchor - finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The length of the matched text, in the case of a range match. Only recorded - if a match was found. Recorded when TextFragmentAnchor finishes searching - once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether the scroll into view was cancelled by a user gesture or programmatic - scroll. Recorded when TextFragmentAnchor finishes searching once the page is - loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The number of selectors in the text fragment anchor if it is present. - Recorded when TextFragmentAnchor finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The length of the start parameter, in the case of a range match. Only - recorded if a match was found. Recorded when TextFragmentAnchor finishes - searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - Whether the match was within a table cell. Only recorded for exact text - fragments and only if a match was found. Recorded when TextFragmentAnchor - finishes searching once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The time between creating the TextFragmentAnchor (i.e. when it is parsed) - and scrolling the target into view. Only recorded if there is a match and we - scroll it into view. Recorded when TextFragmentAnchor finishes searching - once the page is loaded. - - - - - nburris@chromium.org - bokan@chromium.org - - The time between scrolling a match into view and the user scrolling back to - the top of the page. Used as a signal for whether a match was useful. Only - recorded if a match is scrolled into view and the user subsequently scrolled - back to the top of the page. Recorded when TextFragmentAnchor finishes - searching once the page is loaded. - - - - - dmazzoni@chromium.org - - Events fired by the text-to-speech engine when speaking an utterance. - - - - - - Removed 06/2020 as it is no longer needed for analysis. - - katie@chromium.org - dtseng@chromium.org - dmazzoni@chromium.org - - The user picked a default voice of the specified voice ID, which is hashed - from a JSON string of the voice name and extension ID. - - - - - - Removed 06/2020 as it is no longer needed for analysis. - - katie@chromium.org - dtseng@chromium.org - dmazzoni@chromium.org - - When the user requests a preview of a text-to-speech voice, records which - voice was previewed. - - - - - dmazzoni@chromium.org - katie@chromium.org - - Indicates if an utterance spoken via synthesized text-to-speech was - triggered by the Chrome TTS extension API or the web speech API. - - - - - dmazzoni@chromium.org - - True if an utterance spoken via synthesized text-to-speech requested a - specific gender. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance spoken via synthesized text-to-speech specified a - language code. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance spoken via synthesized text-to-speech requested a - specific pitch other than the default. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance spoken via synthesized text-to-speech requested a - specific speech rate other than the default. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance spoken via synthesized text-to-speech requested a - specific voice by name. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance spoken via synthesized text-to-speech requested a - specific volume other than the default. - - - - - dmazzoni@chromium.org - katie@chromium.org - - True if an utterance is spoken with native speech provided by the operating - system, otherwise it's spoken via a Chrome extension that implements - text-to-speech support. - - - - - dmazzoni@chromium.org - katie@chromium.org - - The length of an utterance to be spoken via synthesized text-to-speech. - - - - - - Removed 08/2018. - - katie@chromium.org - dtseng@chromium.org - dmazzoni@chromium.org - - True if a voice parsed from a ttsEngine extension manifest has a specific - gender. This is recorded each time a TTS extension is parsed, which may - occur multiple times per extension, in tts_engine_manifest_handler: - TtsVoices::Parse. - - - - - - Removed 08/2018. - - katie@chromium.org - dtseng@chromium.org - dmazzoni@chromium.org - - True if a voice specified in chrome.ttsEngine.updateVoices by a ttsEngine - extension has a specific gender. - - - - - chrisha@chromium.org - - The total number of certificates for modules loaded (or potentially loaded) - into the browser process that are signed by Microsoft. A catalog counts as a - single certificate, and may refer to many modules. Measured shortly after - startup. Windows only. - - - - - chrisha@chromium.org - - The total number of certificates for modules loaded (or potentially loaded) - into the browser process. A catalog counts as a single certificate, and may - refer to many modules. Measured shortly after startup. Windows only. - - - - - pmonette@chromium.org - - Records whether an equivalent driver letter path was found for a device - path. - - - - - pmonette@chromium.org - - Records the number of modules that were blocked from loading into the - browser process by the third-party DLL blocking feature. This is recorded - every 5 minutes. - - - - - pmonette@chromium.org - - Records whether or not Chrome is still blocking third-party DLLs. This is a - bit that turns to false when the in-process printing is invoked. Recorded - every 5 minutes. - - - - - pmonette@chromium.org - - Records the number of unique modules that were blocked from loading into the - browser process by the third-party DLL blocking feature. This is recorded - every 5 minutes. - - - - - pmonette@chromium.org - - The number of registered input method editors found on the user's machine. - This is emitted shortly after startup when the IME enumeration takes place. - - - - - pmonette@chromium.org - - Records the time it took to gather the list of installed third-party - programs and their install location or components. - - - - - pmonette@chromium.org - - Records whether retrieving the current user SID was successful. - - - - - - Removed 12/2017. - - pmonette@chromium.org - - Records the size of the in-memory representation of the installed - third-party programs on the user's machine. - - - - - - Removed 07/2018. - - pmonette@chromium.org - - Records the time it took to gather the list of installed third-party - programs and their install location or components. - - - - - chrisha@chromium.org - - The total number of third-party modules (neither Microsoft nor Google) that - are loaded in the browser process. Measured shortly after startup. Windows - only. - - - - - chrisha@chromium.org - - The total number of third-party modules (neither Microsoft nor Google) that - are not yet loaded in the browser process, but may potentially be (shell - extensions, for example). Measured shortly after startup. Windows only. - - - - - chrisha@chromium.org - - The total number of signed modules loaded (or potentially loaded) into the - browser process. Measured shortly after startup. Windows only. - - - - - chrisha@chromium.org - - The total number of modules loaded (or potentially loaded) into the browser - process that are signed via a catalog. Measured shortly after startup. - Windows only. - - - - - chrisha@chromium.org - - The total number of modules loaded (or potentially loaded) into the browser - process that are signed by Microsoft. Measured shortly after startup. - Windows only. - - - - - chrisha@chromium.org - - The total number of modules loaded (or potentially loaded) into the browser - process. Measured shortly after startup. Windows only. - - - - - chrisha@chromium.org - - The total number of unsigned modules loaded (or potentially loaded) into the - browser process. Measured shortly after startup. Windows only. - - - - - - Removed as of 14 Aug 2018 as reporting to this metric was incorrect since - its inception. Replaced by ThirdPartyModules.ShellExtensionsCount2. - - pmonette@chromium.org - - The number of registered shell extensions found on the user's machine. This - is emitted shortly after startup when the shell extensions enumeration takes - place. - - - - - - Removed on 30/08/2018 now that the enumeration removes duplicate entries. - - pmonette@chromium.org - - The number of registered shell extensions found on the user's machine. This - is emitted shortly after startup when the shell extensions enumeration takes - place. - - - - - pmonette@chromium.org - - The number of registered shell extensions found on the user's machine. This - is emitted shortly after startup when the shell extensions enumeration is - done. Doesn't count duplicates. - - - - - pmonette@chromium.org - - Indicates whether the TimeDateStamp for a loaded module was successfully - obtained. - - - - - pmonette@chromium.org - - Records whether or not a loaded third party module could be uninstalled - using the Windows Apps & Features page. - - - - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Time elapsed between when the thread managed by a SchedulerWorker is - detached and when the main function of a new thread managed by the same - SchedulerWorker is entered (following a wake up). Recorded each time that a - thread is recreated for a given SchedulerWorker. - - - - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Latency of dummy "heartbeat" tasks posted with specific traits - (see suffix). The heartbeat recording avoids dependencies between this - report and other work in the system. See - ThreadPool.TaskLatencyMicroseconds.* for a metric that is closer to the real - workload. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed 7/2020. Not used in active investigations. - - etiennep@chromium.org - fdoray@chromium.org - gab@chromium.org - - Number of workers running a task in a given SchedulerWorkerPool. Recorded - every 59 minutes (sampling rate is not expected to affect the distribution). - - - - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Number of tasks executed by a SchedulerWorker before it detached. Recorded - when a SchedulerWorker detaches. - - - - - - Removed 8/2019. Not used in active investigations. - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Number of tasks executed by a SchedulerWorker between two waits on its - WaitableEvent. This should be maximized without affecting perceived browser - performance. - - - - - - Stopped recording on 21/4/2020 due to a bug. - - fdoray@chromium.org - scheduler-dev@chromium.org - - Number of tasks in a ThreadPool sequence, recorded every time a task is - pushed to a sequence. This is recorded to determine how often the size of a - sequence grows above 10000 tasks, and whether it is reasonable to upload a - process dump when that happens. - - - - - fdoray@chromium.org - - Number of tasks run by ThreadPool while task was queuing (from time task was - posted until time it was run). Recorded for dummy "heartbeat" - tasks posted with specific traits (see suffix). The heartbeat recording - avoids dependencies between this report and other work in the system. - Recorded every time the ServiceThread performs a heartbeat latency report. - - - - - - Removed 7/2020. Not used in active investigations. - - etiennep@chromium.org - fdoray@chromium.org - gab@chromium.org - - Number of workers that live in a given SchedulerWorkerPool. Recorded every - 59 minutes (sampling rate is not expected to affect the distribution). - - - - - fdoray@chromium.org - gab@chromium.org - robliao@chromium.org - - Time elapsed between when a task is posted and when it starts to run. - Recorded for each task that runs inside the ThreadPool. - - - - - dschinazi@chromium.org - src/net/OWNERS - - The time it takes indicated thread to respond with a pong message for a ping - message from WatchDog thread. - - - - - dschinazi@chromium.org - src/net/OWNERS - - This is the total number of watched threads that are responding when we got - no response from the watched thread. - - - - - dschinazi@chromium.org - src/net/OWNERS - - This is the total unresponsive time since last pong message for the - indicated thread when we got no response from the watched thread. - - - - - dschinazi@chromium.org - src/net/OWNERS - - This is the total number of watched threads that are not responding when we - got no response from the watched thread. - - - - - - Doesn't exist anymore as of 2019-06. - - treib@chromium.org - - A page thumbnail (for use on the New Tab page) was added to TopSites. - - - - - - Removed 2019-03. - - treib@chromium.org - - The result of trying to capture a thumbnail of the current page. - - - - - dfried@chromium.org - pbos@chromium.org - - While taking a screenshot of the current tab for use as a thumbnail, the - time it took to copy the tab's contents into a bitmap. - - - - - carlosk@chromium.org - skym@chromium.org - - The time it takes to detect whether a thumbnail requires a gradient overlay. - This is run when thumbnails are downloaded for content suggestions, as they - load and the result is cached for future use. It is Android specific. - - - - - carlosk@chromium.org - skym@chromium.org - - Whether a thumbnail used for a suggestions image requires a gradient to be - overlaid to not fade into the background. It applies to the thumbnails used - for content suggestions and is Android specific. - - - - - dfried@chromium.org - pbos@chromium.org - - While taking a screenshot of the current tab for use as a thumbnail, the - time it took to post-process the captured bitmap. - - - - - pdr@chromium.org - vmpstr@chromium.org - - Measures whether the tile manager exceeded the hard GPU memory budget - (OOMed). Recorded each time the tile manager assigns GPU memory to tiles. - - - - - - Replaced by Compositing.Renderer.GPUMemoryForTilingsInKb which is an - existing metric tracking the same value. - - xidachen@chromium.org - ericrk@chromium.org - - The amount of GPU memory, in kilobytes. Recorded on devices with less than - or equal to 512MB of memory and when tile manager had sufficient memory to - schedule all visible tiles. - - - - - - Replaced by Compositing.Renderer.GPUMemoryForTilingsInKb which is an - existing metric tracking the same value. - - pdr@chromium.org - ericrk@chromium.org - - The amount of GPU memory used for tiles, in kilobytes. Recorded when the - tile manager had sufficient memory to schedule all visible tiles. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - Events in TimeZoneRequest. - - - - - - alemate@chromium.org - michaelpg@chromium.org - Http response codes in TimeZoneRequest. - - - - - - alemate@chromium.org - michaelpg@chromium.org - - The time elapsed between the sending of the first API request and the time - the final (failed) response was recorded. Includes all retries. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - - The time elapsed between the sending of the first API request and the time - the final (successfull) response was recorded. Includes all retries. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - Result of TimeZoneRequest. - - - - - - alemate@chromium.org - michaelpg@chromium.org - Number of retries until the final response was recorded. - - - - - We no longer have component actions. - - rdevlin.cronin@chromium.org - - The number of component action icons the Browser Actions Container knows - about (visible or in the overflow bucket). Does not count icons that have - been permanently hidden by the user. Measured once per startup per - (non-incognito) profile. - - - - - - After the removal of component actions, this histogram is equivalent to - ExtensionToolbarModel.BrowserActionsCount. See that histogram instead. - - rdevlin.cronin@chromium.org - - The total number of action icons the Browser Actions Container knows about - (visible or in the overflow bucket). Does not count icons that have been - permanently hidden by the user. Measured once per startup per - (non-incognito) profile. - - - - - - Obsolete. See ExtensionToolbarModel.BrowserActionsVisible instead. Stopped - recording 2019-07. - - rdevlin.cronin@chromium.org - extensions-core@chromium.org - - The number of visible toolbar icons in the Browser Actions Container - (visible as in number of icons not in the overflow bucket). 0 means all - icons are in the overflow bucket. MAX_INT means the toolbar is always - showing all icons. Measured once per startup per (non-incognito) profile but - only for those profiles that have one or more browser actions showing in the - toolbar. - - - - - - Stopped recording 2019-07. - - rdevlin.cronin@chromium.org - - The number of millseconds between when the user opens the app menu and when - the app menu is closed. Logged once per app menu run when the menu closes. - Not recorded for menu runs that are initiated by a drag-and-drop sequence. - Note that the code paths for Views-platforms vs Mac are different, so cross- - platform comparison may not always be reasonable. - - - - - peterlaurens@chromium.org - - The number of millseconds between the user requesting a new incognito tab, - e.g. by tapping the New Incognito Tab entry in the main tools menu, and it - completing its animation on screen. - - - - - - Long removed. - - peterlaurens@chromium.org - - The number of millseconds between the user requesting a new tab, e.g. by - tapping the New Tab entry in the main tools menu, and it completing its - animation on screen. - - - - - peterlaurens@chromium.org - - Number of milliseconds passed between the event that triggers the - presentation of the tools menu (the main menu of actions accessed from the - toolbar), and the actual appearance of the menu on screen. Includes the - animation duration. - - - - - peterlaurens@chromium.org - - The number of millseconds between the user requesting a new incognito tab, - from within the tab switcher, e.g. by tapping the New Tab button from the - tab switcher UI, and it completing its animation on screen. - - - - - peterlaurens@chromium.org - - The number of millseconds between the user requesting a new tab, from within - the tab switcher UI, e.g. by tapping the New Tab button from the tab - switcher UI, and it completing its animation on screen. - - - - - - Removed in M86. - - alemate@chromium.org - - The number of times TopSitesImpl::ApplyBlockedUrls is called. - - - - - - Removed in M86. - - alemate@chromium.org - - The number of urls blocked in TopSites. Logged every time - TopSitesImpl::ApplyBlockedUrls is called. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - - Tracks how often each touch action is allowed (AKA the frequency of each - effective touch action) at the end of each touch sequence. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - - Tracks how often the effective touch action computed by blink is or is not - equivalent to the whitelisted touch action computed by the compositor at the - end of each touch sequence. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - - Tracks how often a gesture event is or is not dropped due to the current - allowed touch action state not matching the gesture event. - - - - - - Removed in 06/2020. - - xidachen@chromium.org - nzolghadr@chromium.org - - Track whether a gesture event is allowed or filtered or deferred. - - - - - spqchan@chromium.org - Tracks the usage of the default touch bar buttons. - - - - zentaro@chromium.org - cros-peripherals@chromium.org - Tracks touchpad acceleration setting changes by the user. - - - - zentaro@chromium.org - cros-peripherals@chromium.org - Tracks touchpad acceleration setting on startup. - - - - jhawkins@chromium.org - Tracks touchpad device state. - - - - - Removed 8/2017. - - jhawkins@chromium.org - - Tracks unusual CrOS touchpad operational states (e.g. running into the noisy - ground issue). This is sampled at every touchpad event. - - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad natural scroll setting changes by the user. - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad natural scroll setting on startup. - - - - zentaro@chromium.org - cros-peripherals@google.com - - Tracks touchpad sensitivity setting changes by the user. This replaces the - old Touchpad.Sensitivity.Changed metric. - - - - - zentaro@chromium.org - cros-peripherals@google.com - - Tracks touchpad sensitivity setting on startup. This replaces the old - Touchpad.Sensitivity.Started metric. - - - - - - - khorimoto@chromium.org - zentaro@chromium.org - Whether touchpad scroll acceleration is enabled. - - - - - - khorimoto@chromium.org - zentaro@chromium.org - Touchpad scroll sensitivity value. - - - - - Removed as of 6/2013, replaced by Touchpad.PointerSensitivity.Changed. - - jhawkins@chromium.org - Tracks touchpad sensitivity setting changes by the user. - - - - - Removed as of 6/2013, replaced by Touchpad.PointerSensitivity.Started. - - jhawkins@chromium.org - Tracks touchpad sensitivity setting on startup. - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad TapDragging setting changes by the user. - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad TapDragging setting on startup. - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad TapToClick setting changes by the user. - - - - zentaro@chromium.org - cros-peripherals@google.com - Tracks touchpad TapToClick setting changes by the user. - - - - - Removed as of 7/2013. - - jhawkins@chromium.org - - - - - Removed as of 7/2013. - - jhawkins@chromium.org - - - - nzolghadr@chromium.org - input-dev@chromium.org - - The touch device driver failed to send a TOUCHEVENTF_UP, and chromium - generated a simulated event to maintain consistency/correctness. - - This workaround will be removed once usage drops off. See - https://crbug.com/811273 for details. - - - - - - Removed as of 7/2018. - - aelias@chromium.org - - How the user interacted with the tap disambiguation feature on Android. - - - - - tdresser@chromium.org - - Tracks whether Touch Event Feature Detection is enabled. This is based on - the touch events enabled flag and the presence of a touchscreen. - - Team: input-dev@chromium.org. - -
- NOTE: This metric was incorrectly recorded on Chrome OS for versions 42 - through 45, see http://crbug.com/499476 for more details. As of - http://crbug.com/644318, we changed the internal name to - TouchEventFeatureDetection, but we still keep the old histogram name here to - keep consistensy. -
- - - - semenzato@google.com - - Reported at boot if the previous boot session was interrupted in the middle - of a TPM command during the first 30 seconds of uptime. - - - - - ssid@chromium.org - - Reason why background tracing finalization was not allowed. Also see - "Tracing.Background.ScenarioState" metric, which records the total - number of times finalization was allowed and not allowed. - - - - - oysteine@chromium.org - - The size, in kilobytes, of a finalized trace ready to be uploaded. - - - - - ssid@chromium.org - - Connection type of the network used to determine the trace buffer size, when - background tracing was triggered. Recorded only on Android. - - - - - ssid@chromium.org - - Connection type of the network used to determine the trace upload limit, - when background tracing upload was started. Recorded only on Android. - - - - - oysteine@chromium.org - - Records state of the Background Tracing system, from when scenarios are - attempted to be activated until they're completed (successfully or failed) - - - - - eseckler@chromium.org - tracing@chromium.org - - Records success or failure of creating the shared buffer in - ProducerClient::InitSharedMemoryIfNeeded() - - - - - - Removed as of 09/2017. Code measured by this histogram no longer exists. - - fdoray@chromium.org - - Time spent in base::ThreadData::GetRetiredOrCreateThreadData(). This method - is called at most once per thread, when its name is set, when it posts a - task or when it runs a task (whichever comes first). - - - - - - Removed 2018/07. - - sclittle@chromium.org - bengr@chromium.org - - The amount of time spent waiting to perform an amortization run. This is - logged at the end of each amortization run, before passing any DataUse - objects to their respective callbacks. - - - - - - Removed 2018/07. - - sclittle@chromium.org - bengr@chromium.org - - The number of DataUse objects processed in an amortization run. - - - - - - Removed 2018/07. - - sclittle@chromium.org - bengr@chromium.org - - The number of unique tabs seen across all DataUse objects buffered for a - single amortization run by the TrafficStatsAmortizer. This is recorded even - if TrafficStats byte counts are unavailable, but not recorded if no DataUse - objects have been buffered. - - - - - - Removed 2018/07. - - sclittle@chromium.org - bengr@chromium.org - - The total bytes after performing amortization across all DataUse objects - buffered for a single amortization run by the TrafficStatsAmortizer. This is - recorded even if TrafficStats byte counts are unavailable, but not recorded - if no DataUse objects have been buffered. - - - - - - Removed 2018/07. - - sclittle@chromium.org - bengr@chromium.org - - The total bytes before performing amortization across all DataUse objects - buffered for a single amortization run by the TrafficStatsAmortizer. This is - recorded even if TrafficStats byte counts are unavailable, but not recorded - if no DataUse objects have been buffered. - - - - - googleo@chromium.org - chrome-language@google.com - - Time taken for the TranslateAcceptLanguages to decide if a given language is - available as Accept-Languages. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the always translate option was selected in the - translate infobar. - - - - - groby@google.com - chrome-language@google.com - Tracks UI events related to the translate bubble. - - - - sclittle@google.com - megjablon@google.com - chrome-language@google.com - - The time spent capturing plain text from the DOM. Pre sub frame translation - support (this includes before M83), this is reported by - ChromeRenderViewObserver. If sub frame translation is enabled, this is - captured in the browser process and reported by ContentTranslateDriver. - - - - - - Removed as of 11/2017, since cld2 is deprecated. - - rkaplow@google.com - - Accuracy of the language detected by CLD2. Only recorded if the detection - returned a "known" result. - - - - - - Removed as of 11/2017, since cld2 is deprecated. - - rkaplow@google.com - Language of page detected by CLD2. - - - - frechette@chromium.org - chrome-language@google.com - - Language of the input page detected by CLD3. This information is logged on - every page load. - - - - - frechette@chromium.org - chrome-language@google.com - - Percentage of the bytes that are associated with the most popular language - on the input page. Only recorded if the detection returned a - "known" result. - - - - - mcrouse@chromium.org - chrome-language@google.com - - The time to evaluate the CLD3 language detection model for the top language. - This information is logged on every request. - - - - - anthonyvd@chromium.org - chrome-language@google.com - Various user actions performed in the translate infobar. - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the hashcode of the source language when always translate this - language option is clicked in the menu. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the hashcode of the language clicked on the more languages menu. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the hashcode of the source language when never translate this - language option is clicked in the menu. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the hashcode of the language clicked on the menu to indicate the - page is not in the selected language. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the hashcode of the language clicked on the infobar. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - Records the number of times a page is translated, every time the page is - translated. For instance on a page a) translation from A to B, we record - "1" b) from A to B - we record "1" and revert from B to - A - we record "2" c) from A to B - we record "1", then - translation to C - we record "2". d) from A to B - we record - "1", then translation to C - we record "2" and then - revert to A - we record "3". We increment the translation count: - a) every time the target language is changed. b) every time we revert to the - original language (user can only revert to original language and not - intermediate target languages). This essentially means 1 denotes >= 1 - translations, 2 is >=2 translations per page and so on. This will give us - a sense of how often people try out several translates on a page, or flip - back and forth. - - - - - kenjibaheux@google.com - chrome-language@google.com - - A page may provide a Content-Language HTTP header or a META tag. For each - page load, measures whether the Content-Language header exists and is valid. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the "Nope" (don't translate) or the infobar's - X button was clicked in the translate infobar. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the translate infobar was closed by clicking the X - button without the user translating the page. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the translate UI was closed without translating in the - way that the user doesn't deny translating explicityly, like pressing 'Nope' - button. This is counted on both the infobar and the bubble UI. We are - comparing this on infobar to that on bubble by A/B testing and expecting - that the user will click 'Nope' button on bubble less times than infobar. We - won't delete this histogram after the experiment. - - - - - yyushkina@google.com - anthonyvd@google.com - chrome-language@google.com - - The events (shown, saved, cancelled) happening in the Explicit Language Ask - prompt. - - - - - yyushkina@google.com - anthonyvd@google.com - chrome-language@google.com - - The languages that were added to the Accept Languages list from the Explicit - Language Ask prompt. - - - - - yyushkina@google.com - anthonyvd@google.com - chrome-language@google.com - - The languages that were removed from the Accept Languages list from the - Explicit Language Ask prompt. - - - - - - Removed as of 04/2020. No longer used for analysis. - - anthonyvd@chromium.org - yyushkina@chromium.org - chrome-language@google.com - - Whether or not the backoff threshold for triggering Translate on UI-language - content is reached when the translation process is initiated. - - - - - megjablon@google.com - chrome-language@google.com - - For Google navigations, the hrefTranslate hint may trigger a translation - automatically. If the hint is present on a Google navigation, record whether - or not automatic translation happened. If automatic translation was already - going to happen, then we use the auto translate target language. Also record - if this caused the target language to be different than the hrefTranslate - target language. - - - - - kenjibaheux@google.com - chrome-language@google.com - - A page may provide a lang attribute in html tag. For each page load, - measures whether the lang attribute exists and is valid. - - - - - anthonyvd@chromium.org - chrome-language@google.com - - The number of times the translate infobar was shown in the old translate UI - on Android. Only true is recorded. - - - - - - Removed as of 11/2013, and replaced by Translate.InitiationStatus.v2. - - chrome-language@google.com - kenjibaheux@google.com - - The reason why Chrome decided to perform the next action (e.g., to show - infobar, to translate a page without any prompting, and so on) when Chrome - Translate is ready to translate a page. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The reason why Chrome decided to perform the next action (e.g., to show - infobar, to translate a page without any prompting, and so on) when Chrome - Translate is ready to translate a page. - - - - - sclittle@chromium.org - megjablon@chromium.org - chrome-language@google.com - - The number of characters of page content used for language detection. - - - - - - Removed from code as of 04/2020. - - chrome-language@google.com - - This metric logs CLD3-detected languages for pages that specify a - conflicting English language in their markup. In these cases, we must decide - on a language source to favor. - - Bucket names are of the form "x,y", where x is the common English - language code specified in the page markup (or "other" if the - English language code is uncommon), and y is the CLD3-detected language. - - This histogram only logs detection conflicts. Hence, "matching" - buckets (e.g. "en,en", "en-AU,en") will never be - populated. - - - - - andrewhayden@chromium.org - chrome-language@google.com - - For each page load, records whether language detection occurs on time or - gets deferred. If deferred language detection later completes, this is also - recorded. This allows measuring the UX impact of using a non-static CLD data - source. - - - - - sclittle@chromium.org - megjablon@chromium.org - chrome-language@google.com - - Records the time from when a navigation finishes to when its page language - is determined. This includes the time to load the frame(s), capturing the - text content of the page, and running language classification on that - content. - - - - - frechette@chromium.org - chrome-language@google.com - - Log everytime the language settings page is shown. This can be either user - visits chrome://settings/languages or user visits the advanced languages - card in chrome://settings. With this stat, we will be able to understand how - well the language model is doing by looking into how the number changes over - time. In additiona to that, we are also interested in how many users ever - visit the languages settings card. - - - - - yyushkina@chromium.org - chrome-language@google.com - - For each page load, measures whether the provided HTML language (i.e. the - page lang attribute if it exists, otherwise the header Content-Language - value) matches the language determined by CLD. Beyond directly matching or - mismatching the HTML language, CLD can complement the HTML language. For - example, suppose the HTML language is 'zh' (general Chinese), a language - code that the Translate server does not support. In this case, CLD can - detect a subcode like '-TW' or '-CN', resulting in language codes 'zh-TW' - and 'zh-CN', which the Translate server supports. This is referred to as - "complementing a language subcode". - - - - - kenjibaheux@google.com - chrome-language@google.com - - Logs the user locale when the Translate feature is disabled by the user. - This is recorded each time a webpage is loaded and prefs for translation is - checked. This allows us to investigate the correlation between the user - locale and the usage rates of the Translate. - - - - - yyushkina@google.com - frechette@chromium.org - chrome-language@google.com - - Whether the 'Translate' app menu entry is shown to the user. Emitted when - the app menu (three dots) is shown and a translation could be performed. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the original language in the translate infobar has been - changed. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the target language in the translate infobar has been - changed. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the never translate option was selected in the translate - infobar. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the never translate site was selected in the translate - infobar. - - - - - - Removed 2/2018 - - chrome-language@google.com - joelhockey@chromium.org - - The time spent capturing plain text from the DOM. This is reported by - ChromeRenderViewObserver when a page is loaded completely. - - - - - kenjibaheux@google.com - chrome-language@google.com - Counts translation target page schemes. - - - - rogerm@google.com - chrome-language@google.com - - Tracks the outcome of attempts to download a Translate Ranker Model. - - - - - rogerm@google.com - chrome-language@google.com - - The date tamp (e.g., 20160916 -> 15 Sept 2016) which denotes the - TranslateRankerModel's version. - - - - - rogerm@google.com - chrome-language@google.com - - Whether the TranslateRanker accepts or denies to show the translation - prompt. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the TranslateRanker to use the translate ranker model to - calculate a score for the translation, in ms. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the Translate Ranker Model Loader to download its model from - the configured URL, in ms. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the Translate Ranker Model Loader to parse its model, in ms. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the Translate Ranker Model Loader to read its model from - local storage (cache), in ms. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the TranslateRanker to decide if a given translation should - be offered or not, in ms. This includes the time taken to extract the - relevant features upon which to base the decision, as well as the time taken - to calculate the result. - - - - - rogerm@google.com - chrome-language@google.com - - Time taken for the Translate Ranker Model Loader to write its model to local - storage, in ms. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the "report this error" of options menu is - selected in the translate infobar. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the show original button was clicked in the translate - infobar. - - - - - - Removed 5/2013 by Translate.UndisplayableLanguage - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the detected language is not supported by Translate - Element. - - - - - - Removed 7/2010. No longer tracked. - - chrome-language@google.com - kenjibaheux@google.com - - The number of times an infobar proposing to translate a page has been shown. - - - - - - Removed 06/2020. Duplicate of Translate.ShowErrorUI - - chrome-language@google.com - kenjibaheux@google.com - - Chrome Translate shows an error infobar when an error happens on translation - and the infobar message depends on what kind of error happens. This metric - counts how often each error message is shown. - - - - - kenjibaheux@google.com - chrome-language@google.com - - Chrome Translate shows an error UI (infobar or bubble) when an error happens - on translation and the UI message depends on what kind of error happens. - This metric counts how often each error message is shown. - - - - - kenjibaheux@google.com - chrome-language@google.com - - This metrics is logged whenever a page is loaded. The logged value is - "Mathced" when the CLD-detected language differs from the page - language code , and the two languages are such similar languages. In that - case, Chrome ignore the CLD-determined language and instead uses the page - language code. The page language code is decided by Content-Language and - HTML lang attribute. - - - - - yyushkina@google.com - chrome-language@google.com - - The number of requests sent to the Translate server, grouped by source - language. - - - - - yyushkina@google.com - chrome-language@google.com - - The number of requests sent to the Translate server, grouped by target - language. - - - - - megjablon@google.com - chrome-language@google.com - - Where the target language was determined from. Can be the most recent target - language, from the language model, the UI language, the user's accept - languages, or default to English. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The time from injecting scripts for Chrome Translate to being ready to - perform translation. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The time from injecting scripts for Chrome Translate to the finishing loads - of all depending libraries. - - - - - kenjibaheux@google.com - chrome-language@google.com - The time from starting translation to the completion. - - - - kenjibaheux@google.com - chrome-language@google.com - - The number of times the translate button was clicked in the translate - infobar. - - - - - sclittle@google.com - megjablon@google.com - chrome-language@google.com - - The number of times the translate button was clicked in the translate - infobar for a page that is likely an AMP Cache URL. - - - - - sclittle@google.com - megjablon@google.com - chrome-language@google.com - - The number of frames translated for a translated page (including the main - frame). This is recorded when sub frame translation is enabled. - - - - - sclittle@google.com - megjablon@google.com - chrome-language@google.com - - The error type for a failed sub frame translation (where the main frame was - successfully translated). This is recorded when sub frame translation is - enabled. - - - - - sclittle@google.com - megjablon@google.com - chrome-language@google.com - - The percentage of sub frames that translated successfully for a translated - page (where the main frame was successfully translated). This is recorded - when sub frame translation is enabled. - - - - - kenjibaheux@google.com - chrome-language@google.com - - Logs an undisplayable language included in the language list sent by the - Translate server. The Translate server sends the list each time the user - runs Chrome. This metrics tells us that there is a language which UI should - support but doesn't. - - - - - kenjibaheux@google.com - chrome-language@google.com - - Logs an unsupported source language detected during initiation of the - Translate feature. This is reported when the language detector successfully - detects the language of the webpage, but the language is not supported by - the translation server because it is too minor. This metric allows us to - assess how important the unsupported language is for Google translate. - - - - - kenjibaheux@google.com - chrome-language@google.com - - The time from a page content language being determined to user requesting - Chrome Translate. - - - - - peconn@chromium.org - peter@chromium.org - - Emits true if the user went to site settings from the dialog that is shown - after a Trusted Web Activity client app has had its data cleared. - - - - - peconn@chromium.org - peter@chromium.org - - Emits true if the user went to site settings from the dialog that is shown - after a Trusted Web Activity client app has been uninstalled. - - - - - peconn@chromium.org - peter@chromium.org - - Logs which kind of fallback for notification small icon was used for Trusted - Web Activity notification delegation. - - - - - eirage@chromium.org - peconn@chromium.org - - When a site running in Truested Web Activity is accessing geolocation, - records whether the last tracked focused Trusted Web Activity client app - enrolled location delegation. - - - - - eirage@chromium.org - peconn@chromium.org - - When a Trusted Web Activity client app's location permission is changed, - record the previous state and new stase. - - - - - eirage@chromium.org - peconn@chromium.org - - Records the boolean result (granted or not) from requesting a Trusted Web - Activity client app's location permission. - - - - - eirage@chromium.org - peconn@chromium.org - - Records an error code when we get a new location update or location error - from the Trusted Web Activity client app. Record - "LocationUpdateError.NONE" (value = 0) if there is no error and - the geoposition is valid. - - - - - eirage@chromium.org - peconn@chromium.org - - When Trusted Web Activity launches or navigates to a site that violate the - quality criteria, records the violation type. - - - - - peconn@chromium.org - peter@chromium.org - Recorded when data is shared via a Trusted Web Activity. - - - - peconn@chromium.org - peter@chromium.org - - Records whether or not a splash screen has been shown when launching a - Trusted Web Activity. - - - - - - Retired in M77 in favour of TrustedWebActivity.TimeInVerifiedOrigin.V2 which - uses a more appropriate timescale. - - peconn@chromium.org - peter@chromium.org - - Time spent in a verified origin until navigating to an unverified one or - pausing the Trusted Web Activity. - - - - - peconn@chromium.org - peter@chromium.org - - Time spent in a verified origin until navigating to an unverified one or - pausing the Trusted Web Activity. - - - - - - Retired in M77 in favour of TrustedWebActivity.TimeOutOfVerifiedOrigin.V2 - which uses a more appropriate timescale. - - peconn@chromium.org - peter@chromium.org - - Time spent out of verified origins until navigating back to a verified one - or pausing the Trusted Web Activity. - - - - - peconn@chromium.org - peter@chromium.org - - Time spent out of verified origins until navigating back to a verified one - or pausing the Trusted Web Activity. - - - - - - Replaced by Mobile.Splash.TranslucencyRemovalFailed. - - peconn@chromium.org - peter@chromium.org - - Records the cases when removing a Trusted Web Activity's translucency via a - reflective call fails. Only "true" is recorded. - - - - - - Removed 02/2016 in Issue 1741103002, and replaced by - Renderer4.CompositorWheelScrollUpdateThread and - Renderer4.CompositorTouchScrollUpdateThread. - - tdresser@chromium.org - Whether a scroll is executed on main thread. - - - - - Removed in M65. - - kylechar@chromium.org - - The amount of time the CompositorResizeLock was held in milliseconds. This - is a measure of jank as UI will not generate new frames as long as the lock - is held. - - - - - - Removed in M65. - - kylechar@chromium.org - - Tracks whether the CompositorResizeLock is being released due to timing out - or not. - - - - - bsep@chromium.org - - The device scales available on the system at startup. A system may report - more than one if it has multiple displays with varying device scales. Only - logged on Windows. - - - - - - Removed in M85. - - kylechar@chromium.org - - The amount of time it took for UI's CompositorFrame to activate due to a - surface synchronization event. This a measure of jank as UI will not - generate new frames as long synchronization is in progress. This metric is - similar to UI.CompositorResizeLock.Duration but measures the new - synchronization code path. - - - - - rkaplow@chromium.org - ukm-team@google.com - - The actual interval between log upload start and previous log upload - finished within the same process. A value of 0 indicates there was no - previous upload. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Emitted when UKM Service attempts to build and store a log. Emits true if it - was empty (no sources or entries) which means no log is written, false - otherwise. - - - - - bcwhite@chromium.org - rkaplow@chromium.org - ukm-team@google.com - - Logged in UpdateUkmAllowedForAllProfiles from the UkmConsentStateObserver - which is called when UkmConsentStateObserver starts observing a new profile - and every time a URL-keyed anonymized data collection state changes or a - sync service state changes. This records whether UKM is allowed for all - profiles. - - - - - bcwhite@chromium.org - rkaplow@chromium.org - ukm-team@google.com - - Logged in the UpdateProfileState call from the UkmConsentStateObserver. This - records if the UKM allowed change will trigger a purge of the local UKM - data. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of UKM entries that are dropped. Categorized by the cause of it being - dropped. - - - - - jwd@chromium.org - ukm-team@google.com - - The hashed name of the UKM entry being dropped. The hash is the same hash - sent in the UKM log but truncated to 31 bits with "event_hash & - 0x7fffffff". Recorded when adding an entry and the UKM recorder decides - it should be dropped. - - - - - yrsun@chromium.org - ukm-team@google.com - - The hashed name of the UKM entry being recorded. The hash is the same hash - sent in the UKM log but truncated to 31 bits with "event_hash & - 0x7fffffff". Recorded when an entry is added and accepted by the UKM - recorder. - - - - - - Removed 2/2018 by UKM.Entries.SerializedCount2. - - rkaplow@chromium.org - ukm-team@google.com - Number of serialized UKM entries when storing a UKM log. - - - - rkaplow@chromium.org - ukm-team@google.com - Number of serialized UKM entries when storing a UKM log. - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of serialized UKM entries that are of type PageLoad that have the - metric PaintTiming.NavigationToFirstContentfulPaint. This is recorded every - time a UKM log is stored. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Logged during UkmService initialization whether the init task or the initial - log timer completed first. The expectation is the vast majority of the time, - the init task should complete first. If metrics show otherwise, then it may - indicate there's a bug in the UkmService init sequence and that it should be - investigated. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Size in kilobytes (after compression) of an uploaded UKM log. Recorded after - a successful UKM upload. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Logs whether a log was not uploaded due to cellular log throttling logic. - Android only. - - - - - rkaplow@chromium.org - ukm-team@google.com - - HTTP response codes and network errors encountered by UKM when attempting to - upload logs to the server. - - - - - - Removed in favor of UKM.LogSize.OnSuccess - - asvitkine@chromium.org - holte@chromium.org - - Reports total upload length in bytes when the UKM service type is used. - - - - - jwd@chromium.org - rkaplow@chromium.org - ukm-team@google.com - - The client id was migrated from an Int64 pref to a UInt64 pref. Not migrated - is recorded when a valid UInt64 value is loaded from prefs. Migration - started in M75. - - - - - rkaplow@chromium.org - ukm-team@google.com - The status when loading UKM PersistedLogs from Prefs. - - - - rkaplow@chromium.org - ukm-team@google.com - - Recorded when a UKM client state (client_id, session_id) is reset. This - emits the reason the resetting was triggered. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of UKM sources that are dropped. Categorized by the cause of it being - dropped. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of unsent UKM sources that were kept in-memory to be potentially - transmitted in the next log. - - - - - - Removed 10/2018 by UKM.Sources.SerializedCount2. - - holte@chromium.org - rkaplow@chromium.org - Number of serialized UKM sources when storing a UKM log. - - - - rkaplow@chromium.org - ukm-team@google.com - Number of serialized UKM sources when storing a UKM log. - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of UKM sources that were not sent because they did not match a - navigation source URL. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of UKM sources that were not sent because they had no associated - entries. - - - - - - Removed 11/2018 for UKM.ConsentObserver.AllowedForAllProfiles. - - bcwhite@chromium.org - rkaplow@chromium.org - ukm-team@google.com - - Information about the determination by the UkmConsentStateObserver on why it - enabled or disabled UKM. - - - - - - Removed 11/2018 for UKM.ConsentObserver.Purge. - - bcwhite@chromium.org - rkaplow@chromium.org - ukm-team@google.com - - Logged in the UpdateSyncState call from the UkmConsentStateObserver. This - records if the UKM allowed change will trigger a purge of the local UKM - data. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Number of bytes in an excessively large log that was discarded while - persisting UKM logs to disk to retry during next chrome run. - - - - - rkaplow@chromium.org - ukm-team@google.com - - Counter for number of UKM unsent logs removed from persistent storage. - - - - - - Replaced by UKM.LogUpload.ResponseOrErrorCode - - holte@chromium.org - rkaplow@chromium.org - - For each upload to the UKM server, log the response received from the - server. - - - - - vincb@google.com - ukm-team@google.com - - The status of the retrieval of user demographics from sync that are reported - to UKM. Emitted each time UKM metrics are reported. - - - - - malaykeshav@chromium.org - - Records the time spent in uncompressing a gzipped animation file. - - - - - - Removed 2018/11, because the consent bump was removed. - - tangltom@chromium.org - msarda@chromium.org - - The action the user takes when the unified consent bump is shown. - - - - - - Removed 2018/11, because the consent bump was removed. - - droger@chromium.org - msarda@chromium.org - tangltom@chromium.org - - Boolean indicating whether the user is eligible for seeing the consent bump. - This metric is recorded at every startup when Unified Consent is enabled. - Note: There can be multiple entries per user. - - - - - - Removed 2018/11, because the consent bump was removed. - - tangltom@chromium.org - msarda@chromium.org - - The reason the consent bump isn't shown to the user. This is recorded at - startup during the migration to Unified Consent. - - - - - - - msarda@chromium.org - droger@chromium.org - - State of the user settings for making searches and browsing better, recorded - at startup. - - - - - - Removed 2018/11 because it's no longer necessary. - - droger@chromium.org - msarda@chromium.org - tangltom@chromium.org - - The reason the unified consent was revoked. This is recorded every time the - consent state changes from "unified consent given" to - "unified consent not given". - - - - - - Renamed as UnifiedConsent.MakeSearchesAndBrowsingBetter.OnStartup in 01/2020 - because today the UnifiedConsent service only manages the Make Searches and - Browsing better feature. - - msarda@chromium.org - droger@chromium.org - - State of the user settings for Sync and Google services, recorded at - startup. Multiple samples may be recorded at once, except for 'None' which - is recorded when no other bucket is used. - - - - - - - droger@chromium.org - msarda@chromium.org - - All *off* sync data types are recorded when the user confirmed the sync - setup after going through the advanced opt-in flow. - - - - - sorin@chromium.org - - The number of download jobs found in the Windows BITS queue. This value is - expected to be zero in most cases, or a small number otherwise. Large values - indicate a problem with the job creation or clean up code. The metric is - recorded before a new BITS job is created and inserted into BITS queue. - - - - - sorin@chromium.org - - True if a new BITS job was created to download the url, or false, if an - existing job was found in the BITS queue. The metric is recorded when the - component updater background downloader is asked to download a CRX. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The network connection type when the attempt begins. Possible values include - "Unknown", "Ethernet", "Wifi", - "Wimax", "Bluetooth", "Cellular", - "Tethered Ethernet", "Tethered Wifi". - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - A more detailed description of the last Payload transfer error when - downloading the payload. - - This is reported when an attempt ends with the "Payload Download - Error" result. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The download source used, possible values include "HTTPS Server", - "HTTP Server" and "HTTP Peer". - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes the update attempt took including the time the device - spent sleeping. - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes the update attempt took excluding the time the device - spent sleeping. - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - A more detailed description of the last internal error. The possible values - correspond to the ErrorCode enumeration in the update_engine source code. - - This is reported when an attempt ends with the InternalError result. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The attempt number which starts at 0 for the initial attempt and keeps - increasing for subsequent attempts. - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of payload mebibytes (1048576 bytes) actually download. - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The payload download speed, in kilobytes per second (1000 bytes/second). - This is calculated as the number of bytes downloaded divided by the duration - of the attempt (excluding time spent sleeping). - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The payload size, in mebibytes (1048576 bytes). - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The payload type, possible values include "Delta" (if Omaha - specified to download a delta payload); and "Full" (if Omaha - specified to download a full payload); and "ForcedFull" (if the - client specified that it would only accept a full payload). - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The result of the update attempt. - - This is reported when an update attempt ends. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes since the last attempt including the time the device - spent sleeping. - - This is reported when an update attempt ends but only if there was a - previous attempt for the same update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes since the last attempt excluding the time the device - spent sleeping. - - This is reported when an update attempt ends but only if there was a - previous attempt for the same update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The status of the certificate check done when downloading a payload over - HTTPS. Note that most downloads are done over HTTP. - - This is reported on every HTTPS connection to the payload download server. - Connection drops on the same payload may report different values. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The status of the certificate check done when querying Omaha for a new - version. - - This is reported on every update check. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - If unable to download a response from Omaha, a more detailed error code is - reported in this metric. - - This is reported on every update check resulting in "Download - error". - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - If there is an update available, this metric will track what the device does - with the information. Possible values include "Applying update", - "Deferring update", "Ignoring update", and "Backing - off". - - This is reported on update checks resulting in "Update available". - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The response from Omaha. Possible values include "No update - available", "Update available", "Download error", - "Response parsing error", and "Reboot pending". - - This is reported on every update check. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - First section of the Chrome OS target version set by device policy and sent - to Omaha if rollback is also allowed. This is a sparse histogram, since the - possible valid values are stable Chrome OS version prefixes (usually one per - milestone). - - Example value: 10323 (meaning M65 stable). - - This is reported on every update check if the TargetVersionPrefix device - policy is set and the value of the RollbackToTargetVersion device policy is - one of the values allowing rollback. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - First section of the Chrome OS target version set by device policy and sent - to Omaha. This is a sparse histogram, since the possible valid values are - stable Chrome OS version prefixes (usually one per milestone). - - Example value: 10323 (meaning M65 stable). - - This is reported on every update check if the TargetVersionPrefix device - policy is set. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes since the last check including the time the device - spent sleeping. - - This is reported on every update check except for the first one. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of minutes since the last check excluding the time the device - spent sleeping. - - This is reported on every update check except for the first one. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The age of the OS in days, defined as the age of the /etc/lsb-release file. - - This is reported on every update check but at most once a day. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - First section of the Chrome OS version to which an enterprise rollback - (rollback initiated by the admin of the device) has failed. This is a sparse - histogram, since the possible valid values are stable Chrome OS version - prefixes (usually one per milestone). - - Example value: 10323 (meaning M65 stable). - - This is reported after a rollback image has failed installing. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - First section of the Chrome OS version to which an enterprise rollback - (rollback initiated by the admin of the device) has succeeded. This is a - sparse histogram, since the possible valid values are stable Chrome OS - version prefixes (usually one per milestone). - - Example value: 10323 (meaning M65 stable). - - This is reported after a rollback image has been successfully installed. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The number of consecutive times a device has failed to boot an update that - successfully applied. - - This is reported every time the firmware fails to boot the slot with the - update and fell back to the slot it originally updated from. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The source used to provision the install-date-days value sent to Omaha with - every request. - - This is reported when OOBE (Out Of Box Experience) completes (M34 or later) - or when upgrading to a version with install-date-days support. - - This metric is specific to Chrome OS. - - - - - poromov@chromium.org - - Whether setting the MaxKernelKeyRollforward value in the TPM succeeded. - - This is reported every time an update check happens. This is a bool value. - - This metric is specific to Chrome OS. - - - - - poromov@chromium.org - - Maximum value the device can roll forward the minimum kernel key version - value in the TPM during the next boot. - - This value is set to infinity (0xfffffffe) for devices which doesn't allow - rollback. - - Otherwise, the value is the kernel key version of the earliest image to - which the device is allowed to roll back. - - This is reported every time an update check happens. This is a sparse value. - - This metric is specific to Chrome OS. - - - - - poromov@chromium.org - - Minimum kernel key version already set in the TPM. This value specifies - which images can be booted up with verified boot. - - This is reported every time an update check happens. This is a sparse value. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - Whether rollback worked. - - This is reported every time there's a rollback request. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of update attempts required to update the device. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of bytes downloaded in mebibytes (1048576 bytes) using all - available sources (e.g. HTTP, HTTPS, HTTP Peer). - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of bytes downloaded in mebibytes (1048576 bytes) using HTTP - from a local peer. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of bytes downloaded in mebibytes (1048576 bytes) using - HTTP. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of bytes downloaded in mebibytes (1048576 bytes) using - HTTPS. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The ratio between bytes downloaded and payload size minus 100. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The various download sources used - this is a combination of the values - "HTTPS Server", "HTTP Server" and "HTTP Peer". - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - The total number of days from when an update is first seen to when an update - is finished downloading (but before rebooting). This metric is recorded on - enterprise-enrolled devices that do not have the - DeviceAutoUpdateTimeRestrictions policy enabled. - - This metric is specific to Chrome OS. - - - - - mpolzer@google.com - managed-platforms@google.com - - The total number of days from when an update is first seen to when an update - is finished downloading (but before rebooting). This metric is recorded on - devices that have the DeviceAutoUpdateTimeRestrictions policy enabled. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The size of the payload, in mebibytes (1048576 bytes). - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The payload type ("Delta", "Full", - "ForcedFull") used. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of reboots during the update. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of minutes from when an update was detected until an update - (possibly another update) was applied. This includes the time waiting for - update checks and time the device spent sleeping. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of minutes from when an update was detected until an update - (possibly another update) was applied. This does not include the time - waiting for update checks and time the device spent sleeping. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of updates that were abandoned since the last successful - update. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The total number of times the URL was switched (from e.g. HTTPS to HTTP) - because of failures. - - This is reported on every successful update. - - This metric is specific to Chrome OS. - - - - - ahassani@chromium.org - chromeos-core-services@google.com - - The duration between when an update has successfully completed and the user - is presented with the "reboot arrow" and when the system has - booted into the new update. - - This is reported every time the device is rebooted after an update has been - applied. - - This metric is specific to Chrome OS. - - - - - ksspiers@chromium.org - nrpeter@chromium.org - - Measures the time elapsed from an update being visible to the browser and - the browser being restarted or quit. - - - - - spqchan@chromium.org - - Tracks the upgrade notification stage. This is recorded with every UMA log. - - - - - mpolzer@google.com - managed-platforms@google.com - - Tracks what is the reason we're doing a rollback instead of an update (going - to a more stable channel or admin-initiated enterprise rollback). We're - showing different notifications depending on the reason. - - Sent when the device finished installing the rollback image, shows the - notification and is waiting for reboot. - - This metric is specific to Chrome OS. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when Chrome is started, and - when the login prompt is again visible after a logout. This statistic is - only collected when preceeded by a logout. - - - - - satorux@chromium.org - hashimoto@chromium.org - - The system uptime on Chrome OS when the dbus-daemon process crashes, - resulting in a reboot. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS for setting up for a login after a - logout. More specifically, it is the time between when the Cryptohome is - unmounted (the last step in the logout process) and when the login prompt is - again visible after a logout. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS when performing a logout. More - specifically, it is the time between when a logout is initiated and when the - Cryptohome is unmounted, signaling the last step in the logout process. This - statistic is not collected when the logout is part of a restart or shutdown. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between initiating a logout and the - next time the login prompt is visible again. This statistic is not collected - if the machine is shutdown between the logout initiation and the prompt - becoming visible. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when a logout is initiated - and the UI has stopped (and Chrome has exited) during the logout process. - This statistic is not collected if the logout is part of a restart or - shutdown. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when all user-associated - processes have been terminated during the logout process and when Chrome is - started again to show the login screen. Since at least ChromeOS M62, - equivalent to Uptime.XTerminatedToChromeExecAfterLogout. - - - - - - Removed 05/2018 in Issue 721891 with removal of X11. Replaced by - Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in ChromeOS M69. - Equal to 0 since at least ChromeOS M62. - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when all user-associated - processes (including the X server) have been terminated during the logout - process. This statistic is not collected if the logout is part of a restart - or shutdown. - - - - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when the UI has stopped - (Chrome has exited), and when all other associated processes have been - terminated during the logout process. This statistic is not collected if the - logout is part of a restart or shutdown. - - - - - - Replaced by Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in - ChromeOS M69. Equivalent to the new name since at least ChromeOS M62. - - hajimehoshi@chromium.org - kouhei@chromium.org - - Measures the time elapsed on Chrome OS between when the X server has been - terminated from a previous logout and when Chrome is started again to show - the login screen. - - - - - - Served its purpose; deprecated 9/2018 in M71 (https://crbug.com/827173). - - grt@chromium.org - - The time it took to build and set the URL blacklist on the main thread - within URLBlacklistManager's constructor. - - - - - - Removed 10/2017. - - mmenke@chromium.org - - Size (in kilobytes) of response bodies retrieved as strings from URLFetcher. - - - - - pnoland@chromium.org - fgorski@chromium.org - - Android: count of Usage Stats events. Recorded as these events occur; e.g. - when a domain is associated with a token, or a site is suspended. - - - - - - This was added to assess possible impact of UserActivationV2, by comparing - pre- and post-launch stats. - - mustaq@chromium.org - - Outcomes (success/failure) of transient user activation availability check - attempts for each type of caller frame (null, ancestor, descedant, other). - - - - - - This was added to assess possible impact of UserActivationV2, by comparing - pre- and post-launch stats. - - mustaq@chromium.org - - Outcomes (success/failure) of user activation consumption attempts for each - type of caller frame (null, ancestor, descedant, other). - - - - - - Removed in M57. - - rsleevi@chromium.org - svaldez@chromium.org - - Distribution of Content-Disposition headers sent with x-x509-user-cert - content types. - - - - - - Removed on 2020-07 (crbug.com/975700). - - raleksandrov@google.com - cros-oac@google.com - - Distribution of the default images that users choose in Change Picture - dialog (Chrome OS). One sample is taken each time the user changes picture. - - - - - - Removed in M85. The OOBE user image screen is long gone. - - achuith@chromium.org - - Distribution of the default images chosen on user image screen during - out-of-the-box experience (Chrome OS). One sample is taken each time the - user confirms the choice by clicking OK button. - - - - - achuith@chromium.org - - Distribution of the default images that existing users login with (Chrome - OS). One sample is taken each time the user logs in. - - - - - - Removed on 2020-07 (crbug.com/1037348). - - raleksandrov@google.com - cros-oac@google.com - - Profile image download result for UserManager (either on behalf of the - Change Picture prefs page, OOBE or scheduled refresh after user login). - - - - - achuith@chromium.org - The time it took to download user's profile picture. - - - - - Removed in M85. The OOBE user image screen is long gone. - - achuith@chromium.org - - Time histogram of the "Choose Picture" OOBE screen display delay. - - - - - - Removed. Chrome can't listen to changes in the background, these are delayed - until the app becomes active again. Use UserInterfaceStyle.CurrentlyUsed - instead. - - javierrobles@chromium.org - rkgibson@google.com - bling-team@google.com - - [iOS] Used on iOS 13+ to report the changes to Light and Dark mode. This is - logged when the interface style changes and Chrome is active. Can be caused - by the system automatic switch or by the user manually changing the style. - - - - - javierrobles@chromium.org - rkgibson@google.com - bling-team@google.com - - [iOS] Used on iOS 13+ to report the usage of Light and Dark mode. This is - logged at startup and on each user interface style change. Can be caused by - the system automatic switch or by the user manually changing the style. - - - - - achuith@chromium.org - - The number of users of different types that log in to the system (Chrome - OS). - - - - - - - alemate@chromium.org - rsorokin@chromium.org - cros-oac@google.com - - The time between one regular user logging out and a different regular user - logging in (Chrome OS). Delays above thirty minutes or which span system - reboots or non-regular-user logins are not reported. - - - - - atwilson@chromium.org - - Whether the profile_ever_initialized() user attribute migration has - completed for the current user. - - - - - - - alemate@chromium.org - michaelpg@chromium.org - rsorokin@chromium.org - cros-oac@google.com - - This is logged when new user type reported by Gaia is different from the old - one (for existing user). - - - - - rsorokin@chromium.org - cros-oac@google.com - - The result of restoring account id on Chrome restart after crash on Chrome - OS. - - - - - - Removed on 2020-06 (crbug.com/975711). - - raleksandrov@google.com - cros-oac@google.com - - Whether the user pods were enabled during login, and what could disable - them. - - - - - - Removed 5/2017 in Issue 704922. Replaced by V8.ArrayBufferLargeAllocations. - - gdeepti@chromium.org - titzer@chromium.org - kschimpf@chromium.org - Number of bytes requested in an array buffer allocation. - - - - gdeepti@chromium.org - ecmziegler@chromium.org - - Number of bytes requested in array buffer allocations greater than one - megabyte. - - - - - gdeepti@chromium.org - ecmziegler@chromium.org - Array buffer sizes for which V8 failed to allocate memory. - - - - - Removed on 2019-06 (crbug.com/969997). - - mstarzinger@chromium.org - titzer@chromium.org - Size of asm.js module (in asm.js format). - - - - - Removed on 2019-06 (crbug.com/969997). - - mstarzinger@chromium.org - titzer@chromium.org - - Time to convert asm.js code to WebAssembly. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - clemensb@chromium.org - - Throughput of translation of asm.js code to WebAssembly in MB/s. - - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - TBD - - - - yangguo@chromium.org - - Reason code data has been rejected when attempting to deserialize. - - - - - yangguo@chromium.org - Cache size to source size ratio when caching compiled code. - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - TBD - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - Time spent generating native code for functions. - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - rmcilroy@chromium.org - - Fraction of the total generated code which was generated using the - Crankshaft optimizing compiler, after each GC in percent. - - - - - delphick@chromium.org - - Time spent collecting source positions to generate stack traces. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by V8.CompileMicroSeconds. - - hablich@chromium.org - yangguo@chromium.org - Time spent in V8 compiler (full codegen). - - - - yangguo@chromium.org - - Time spent compiling a script that may be subject to caching. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by V8.CompileDeserializeMicroSeconds. - - vogelheim@chromium.org - Time spent deseriailzing code, used by V8 code caching. - - - - vogelheim@chromium.org - - Time spent deseriailzing code, used by V8 code caching. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by V8.CompileEvalMicroSeconds. - - yangguo@chromium.org - Time spent in V8 compiler (full codegen) for eval. - - - - yangguo@chromium.org - - Time spent in V8 compiler (full codegen) for eval. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by V8.CompileTime.CacheBehaviour. - - kouhei@chromium.org - - V8 script compile function variant which was picked. This contains - information such as {if,why} v8 {code,parser} was - {produced,consumed,bypassed}. - - - - - - This histogram has been replaced by - V8.CompileTimeMicroSeconds.NoCache.InlineScript. - - yangguo@chromium.org - Time spent compiling an inline script. - - - - - This histogram has been replaced by V8.CompileLazyMicroSeconds. - - hablich@chromium.org - Time spent compiling functions lazily on first run. - - - - hablich@chromium.org - - Aggregated time spent compiling functions lazily during a single script - execution. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - yangguo@chromium.org - - Time spent in V8 compiler (full codegen) excluding parser. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by the subcategories of - V8.CompileTimeMicroSeconds.NoCache - - yangguo@chromium.org - - Time spent compiling a script that cannot be subject to caching. - - - - - - This histogram has been replaced by V8.CompileScriptMicroSeconds. - - yangguo@chromium.org - - Total time spent in compiling a script (incl. parsing/caching). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - The cache behaviour of compiling a V8 script, including whether we produced - or consumed a code cache, whether we hit V8's isolate's cache, and if we - didn't use the code cache, the reason why not. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing/caching). - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - rmcilroy@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) on a background - thread. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script when the 'compilation' is - deserializing it from the code cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing/caching) when the - compilation tried to deserialize it from the code cache, but failed. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing/caching) in the case - where the V8 isolate's compilation cache is hit. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) when the cache is too - cold to use. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) when the script is an - inline script. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) when we do not want - to cache it. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) when the script is - too small to be cached. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in compiling a script (incl. parsing) and serializing it - for the code cache. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Total time spent in finalizing a script that was streaming compiled. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - This histogram has been replaced by V8.CompileSerializeMicroSeconds. - - vogelheim@chromium.org - Time spent serializing code, used by V8 code caching. - - - - vogelheim@chromium.org - - Time spent serializing code, used by V8 code caching. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - yangguo@chromium.org - - Debugger feature used at least once per isolate, recorded on first use. - - - - - - This histogram is no longer present in V8 - - hablich@chromium.org - Time spent generating deferred code stubs. - - - - - This histogram has been removed. - - ulan@chromium.org - - Number of garbage collections that a detached global context survives, - recorded after each major garbage collection. Values greater than 7 indicate - a memory leak. - - - - - hablich@chromium.org - - The amount of JavaScript errors thrown by V8 per context. It does not count - custom errors and ignores catched errors thrown by V8. This is collected - after the context is detached. - - - - - - This histogram is no longer present in V8 - - hablich@chromium.org - - The maximum memory used to store V8 compiled code on a given process. - - - - - rmcilroy@chromium.org - - Time spent in JavaScript Execution, including runtime calls, callbacks, and - lazy compilation. - - - - - - Removed in Feb 2019. No longer tracked in V8. - - gab@chromium.org - - Latency (post-to-schedule) of each parallel task posted during V8 garbage - collection. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - - Time spent in background tasks doing marking in one GC cycle. It is recorded - after each GC. - - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - - Time spent in background tasks doing scavenging in one GC cycle. It is - recorded after each GC. - - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - - Time spent in background tasks doing sweeping in one GC cycle. It is - recorded after each GC. - - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - Time spent in mark-sweep phase of GC. - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in mark-sweep phase of GC in a background isolate. - - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in mark-sweep phase of GC in a foreground isolate. - - - - - - Removed in April 2020. No longer tracked. - - hpayer@chromium.org - Time spent doing a full GC during an IdleNotification. - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental latency-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the clearing phase of incremental latency-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the epilogue of incremental latency-optimized Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the evacuation phase of incremental latency-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the finish phase of incremental latency-optimized Mark-Compact - GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the marking phase of incremental latency-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the prologue of incremental latency-optimized Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the sweeping phase of incremental latency-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental latency-optimized - Mark-Compact GC in a background isolate. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental latency-optimized - Mark-Compact GC in a foreground isolate. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental memory-optimized - Mark-Compact GC. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental memory-optimized - Mark-Compact GC in a background isolate. - - - - - ulan@chromium.org - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in the final atomic pause of incremental memory-optimized - Mark-Compact GC in a foreground isolate. - - - - - - Removed in April 2020. No longer tracked. - - hpayer@chromium.org - Time spent in IdleNotifications. - - - - - Removed in August 2017. No longer tracked. - - hpayer@chromium.org - Idle time passed to V8 via IdleNotifications. - - - - - Removed in August 2017. No longer tracked. - - hpayer@chromium.org - - Milliseconds the idle time limit was overshot by the IdleNotification. - - - - - - Removed in August 2017. No longer tracked. - - hpayer@chromium.org - - Milliseconds the idle time limit was undershot by the IdleNotification. - - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - Time spent doing incremental marking steps during GC. - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - Time spent in finalizing incremental marking. - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - Reason an incremental marking was started in V8. - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - Time spent in starting incremental marking. - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - - The total time spent in incremental marking steps in one GC cycle. It is - only recorded if the time is non-zero. - - - - - - Removed in April 2020. No longer tracked. - - hpayer@chromium.org - Time spent in LowMemoryNotifications. - - - - mlippautz@chromium.org - v8-memory-sheriffs@google.com - - Marking throughput considering all durations of all marking phases on the - main thread and marked bytes within one V8 garbage collection cycle. - Reported once per garbage collection cycle. Only reported for platforms - supporting high resolution clocks and when more than 1MB of live objects - have been found. - - - - - mlippautz@chromium.org - v8-memory-sheriffs@google.com - - Sum of all durations of individual phases within one V8 mark-compact garbage - collection. Reported once per garbage collection. - - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - Reason a mark-compact garbage collection was started in V8. - - - - mlippautz@chromium.org - v8-memory-sheriffs@google.com - - Sum of all durations of all marking phases (incremental and non-incremental) - within one V8 garbage collection cycle. Reported once per garbage collection - at the end. - - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - Time spent in scavenging phase of GC. - - - - mlippautz@chromium.org - v8-memory-sheriffs@google.com - - Wall time spent in the main scavenging phase that copies over all reachable - objects during a V8 scavenge. - - - - - mlippautz@chromium.org - v8-memory-sheriffs@google.com - Time spent in scavenging the roots during a V8 scavenge. - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in scavenging phase of GC in a background isolate. - - - - - ulan@chromium.org - v8-memory-sheriffs@google.com - Reason a scavenge garbage collection was started in V8. - - - - hpayer@chromium.org - v8-memory-sheriffs@google.com - - Time spent in scavenging phase of GC in a foreground isolate. - - - - - - Removed in April 2020. No longer tracked. - - mlippautz@chromium.org - - Type of garbage collection strategy used to collect the young generation. - - - - - oth@chromium.org - Results from snapshot loading. - - - - oth@chromium.org - Results from opening V8 snapshot files. - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Liftoff (V8's baseline compiler for WebAssembly) bails out if it hits the - first unsupported feature in a function. The function is recompiled with - TurboFan then. This histogram records the bailout reason (or success) per - WebAssembly function compilation in Liftoff. - - - - - - This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. - - hpayer@chromium.org - - External memory fragmentation in the cell space after each GC in percent. - - - - - hpayer@chromium.org - - External memory fragmentation in the code space after each GC in percent. - - - - - hpayer@chromium.org - - External memory fragmentation in the large object space after each GC in - percent. - - - - - hpayer@chromium.org - - External memory fragmentation in the map space after each GC in percent. - - - - - - This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. - - hpayer@chromium.org - - External memory fragmentation in the old data space after each GC in - percent. - - - - - - This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. - - hpayer@chromium.org - - External memory fragmentation in the old pointer space after each GC in - percent. - - - - - hpayer@chromium.org - - External memory fragmentation in the old space after each GC in percent. - - - - - hpayer@chromium.org - - Total external memory fragmentation after each GC in percent. - - - - - - This histogram has been replaced by Memory.Experimental.Renderer2.V8. - - ulan@chromium.org - - The committed memory used by V8 in KB averaged over time, logged before each - GC. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the cell space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the code space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the lo space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the map space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the new space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the old data space after each GC in - percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the old pointer space after each GC in - percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - Fraction of the total heap used by the old space after each GC in percent. - - - - - - Removed as of 09/2017. - - hpayer@chromium.org - - The size of committed memory in the cell space after each GC in KB. - - - - - hpayer@chromium.org - - The size of committed memory in the code space after each GC in KB. - - - - - hpayer@chromium.org - - The size of committed memory in the map space after each GC in KB. - - - - - hpayer@chromium.org - - The maximum size of committed memory used by V8 after each GC in KB. - - - - - hpayer@chromium.org - - The total size of committed memory used by V8 after each GC in KB. - - - - - hpayer@chromium.org - - The total size of live memory used by V8 after each GC in KB. - - - - - - This histogram has been replaced by - Memory.Experimental.Renderer2.V8.AllocatedObjects. - - ulan@chromium.org - - The live memory used by V8 in KB averaged over time, logged before each GC. - - - - - - This histogram has been replaced by V8.ParseMicroSeconds. - - marja@chromium.org - Time spent in V8 parser. - - - - - This histogram has been replaced by V8.ParseLazyMicroSeconds. - - marja@chromium.org - - Time spent parsing functions when they are lazily compiled on first run. - - - - - - Removed. - - marja@chromium.org - - Time spent parsing functions when they are lazily compiled on first run. - - - - - - Removed. - - marja@chromium.org - Time spent in V8 parser. - - - - - This histogram has been replaced by V8.PreParseMicroSeconds. - - marja@chromium.org - Time spent preparsing source code. - - - - - Removed. - - marja@chromium.org - Time spent preparsing source code. - - - - jgruber@chromium.org - mvstanton@chromium.org - - The number of backtracks performed in a single regexp execution. - - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - Time spent on rewriting ASTs before compilation. - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - TBD - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - TBD - - - - - This histogram is no longer present in V8. - - yangguo@chromium.org - - The generation a compiled script was found in the compilation cache. - - - - - gdeepti@chromium.org - ulan@chromium.org - - Number of megabytes requested in shared array buffer allocations. - - - - - tebbi@chromium.org - mvstanton@chromium.org - - Number of ticks (in 1000s of ticks) from starting optimizing to installing - the code object. Recorded on each regular optimization of a function. - - Similar to V8.TurboFanOptimizeTotalTime, but instead of counting time, we - count a deterministic number of ticks sprinkled throughout the Turbofan - compiler. - - - - - bmeurer@chromium.org - mslekova@chromium.org - - Total time from starting optimizing to installing the code object. Recorded - on each regular, concurrent optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the execution phase of TurboFan optimization. Recorded on each - regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the finalization phase of TurboFan optimization. Recorded on - each regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the execution phase of TurboFan optimization for On Stack - Replacement (OSR). Recorded on each optimization for on-stack replacement of - a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the finalization phase of TurboFan optimization for On Stack - Replacement (OSR). Recorded on each optimization for on-stack replacement of - a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the preparation phase of TurboFan optimization for On Stack - Replacement (OSR). Recorded on each optimization for on-stack replacement of - a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Total time from starting optimizing for On Stack Replacement (OSR) to - installing the code object. Recorded on each optimization for on-stack - replacement of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - bmeurer@chromium.org - mslekova@chromium.org - - Total time from starting optimizing to installing the code object. Recorded - on each regular, non-concurrent optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Time spent in the preparation phase of TurboFan optimization. Recorded on - each regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Total time spent on a background thread during TurboFan optimization. - Recorded on each regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Total time spent on the main thread during TurboFan optimization. Recorded - on each regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - neis@chromium.org - mvstanton@chromium.org - - Total time from starting optimizing to installing the code object. Recorded - on each regular optimization of a function. - - This histogram only records metrics on machines with high-resolution clocks. - - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - Time spent analysing the usage of variables. - - - - - This histogram is no longer present in V8. - - hablich@chromium.org - TBD - - - - ecmziegler@chromium.org - adamk@chromium.org - ahaas@chromium.org - - The total amount of address space reserved by the backing stores of all live - WebAssembly.Memory backing stores in MiB. Recorded on each memory - reservation. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to execute a single WebAssembly code GC, measured from when it is - triggered until all isolates reported live code and all dead code was freed. - Recorded after each WebAssembly code GC if a high-resolution clock is - available. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to compile a WebAssembly function. Recorded on each compilation of a - single function, either synchronous, asynchronous, or lazily. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Peak memory used to compile a WebAssembly function. Recorded for each - TurboFan compilation of a WebAssembly function. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to asynchronously compile a WebAssembly module (using the - 'WebAssembly.compile' API). Recorded on each asynchronous WebAssembly - compilation, but only if a high-resolution clock is available. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to compile a WebAssembly module. Recorded on each synchronous - WebAssembly compilation. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to asynchronously compile a WebAssembly module using streaming - compilation (via the 'WebAssembly.compileStreaming' API). Recorded on each - streaming WebAssembly compilation, but only if a high-resolution clock is - available. Note that compilation speed is often limited by the network - speed, which is also reflected in this metric. - - - - - - Removed in M82 (crbug.com/1053286). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to decode a WebAssembly function. Recorded on each validation of a - WebAssembly function. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to decode a WebAssembly module. Recorded for each WebAssembly module - which is decoded for validation, compilation, or deserialization. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Peak memory used to decode a WebAssembly module. Recorded for each - WebAssembly module which is decoded for validation, compilation, or - deserialization. - - - - - - Removed 10/2019. No longer tracked. - - bbudge@chromium.org - clemensb@chromium.org - adamk@chromium.org - - Time to deserialize a WebAssembly module during streaming compilation (via - the 'WebAssembly.compileStreaming' API). Recorded on each streaming - WebAssembly deserialization from the code cache, but only if a - high-resolution clock is available. Note that compilation speed is often - limited by the network speed, which is also reflected in thie metric. - - - - - - Removed 03/2019. No longer tracked. - - titzer@chromium.org - adamk@chromium.org - - Time spent executing WebAssembly. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - bbudge@chromium.org - clemensb@chromium.org - adamk@chromium.org - - Time to asynchronously compile or deserialize a WebAssembly module during - streaming compilation (via the 'WebAssembly.compileStreaming' API). Recorded - on each streaming WebAssembly compilation or deserialization from the cache, - but only if a high-resolution clock is available. Note that compilation - speed is often limited by the network speed, which is also reflected in this - metric. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Size of a WebAssembly function in bytes. Recorded on each compilation of a - single function, either synchronous, asynchronous, or lazily. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Function count per WebAssembly module. Recorded for each WebAssembly module - which is decoded for validation, compilation, or deserialization. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to instantiate a WebAssembly module. Recorded on each instantiation of - a WebAssembly module. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time for lazy compilation of WebAssembly functions. This is recorded per - function for the functions that are lazily compiled. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Throughput of compilation of lazily compiled WebAssembly functions in KB/s - (size of function in wasm format divided by time to compile it). This is - recorded per function for functions that are lazily compiled. - - - - - ecmziegler@chromium.org - adamk@chromium.org - ahaas@chromium.org - - Number of 64KiB pages a WebAssembly module declares as its maximum - requirement. Recorded on each instantiation of a WebAssembly module. - - - - - ecmziegler@chromium.org - adamk@chromium.org - ahaas@chromium.org - - The result of attempts to allocate WebAssembly.Memory buffers. Recorded on - each attempt to allocate a WebAssembly.Memory buffer. - - - - - ecmziegler@chromium.org - adamk@chromium.org - ahaas@chromium.org - - Number of 64KiB pages a WebAssembly module declares as its minimum - requirement. Recorded on each instantiation of a WebAssembly module. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The amount of generated code in MiB for one WebAssembly module. Recorded - when baseline compilation finished. - - - - - - Removed in M82 (crbug.com/1053285). - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The amount of WebAssembly code freed by garbage collection, in MiB. Recorded - for each live module after each full GC. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The amount of committed code space in MiB used by individual WebAssembly - modules. Recorded for each live module after each full GC. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The percentage of WebAssembly code freed by garbage collection (ratio of - total freed code to total generated code so far). Recorded for each live - module after each full GC. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The amount of generated code in MiB for one WebAssembly module. Recorded - when top-tier compilation finished. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Number of code GCs triggered per WebAssembly module. Recorded after each - code GC. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - The number of code spaces (i.e. individual reservations) of a WebAssembly - module. Recorded on every code space allocation. - - - - - ecmziegler@chromium.org - adamk@chromium.org - ahaas@chromium.org - - Size of the wire bytes of a WebAssembly module. Recorded for each - WebAssembly module which is decoded for validation, compilation, or - deserialization. - - - - - clemensb@chromium.org - ecmziegler@chromium.org - - Number of WebAssembly native modules live in a Wasm engine (typically per - process). Recorded whenever a new native module is created. - - - - - clemensb@chromium.org - ecmziegler@chromium.org - - Number of WebAssembly native modules live in an isolate. Recorded whenever a - new native module is created. - - - - - ecmziegler@chromium.org - adamk@chromium.org - clemensb@chromium.org - - Time to tier-up a WebAssembly module, i.e. the time between baseline - compilation finishes and top-tier compilation finishes. Recorded whenever an - asynchronously compiled module finishes top-tier compilation, but only if a - high-resolution clock is available. - - - - - rmcelrath@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - The time interval between when a WebView-using app's copy of the variations - seed was written to its local app storage and when it was loaded for use. - This is different from Variations.SeedFreshness because it measures - freshness from when the app received its copy of the seed, not when the seed - was originally downloaded. Written every time the browser process - initializes, but not if there was an error reading the seed, or no seed - existed. - - - - - rmcelrath@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - The result of checking if a WebView-using app's copy of the variations seed - is still fresh, or if a new seed should be requested. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The result of verifying if the variations seed is expired, recorded before - trials are created from the seed. Expired seeds are treated as not existing. - - - - - - Removed 1/2013. No longer tracked. - - asvitkine@chromium.org - src/base/metrics/OWNERS - - A count of the number of times we hit the code where a field trial is - disabled because no entropy provider was provided. - - - - - - Removed 02/2020. Replaced by Variations.WebViewDownloadJobFetchTime2, which - has a higher maximum bucket. - - rmcelrath@chromium.org - src/android_webview/OWNERS - - The duration of the network request to downloads a new WebView variations - seed from the variations server to the central on-device service. - - - - - - Removed 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode. - - asvitkine@chromium.org - - The counts of network error codes encountered by VariationsService when an - attempt to fetch a variations seed from the server fails. - - - - - - Removed 2/2014. No longer tracked. - - asvitkine@chromium.org - - The latency of a VariationsService seed fetch that results in a not modified - response. - - - - - - Removed 2/2014. No longer tracked. - - asvitkine@chromium.org - - The latency of a VariationsService seed fetch that results in neither a - success nor not modified response. - - - - - - Removed 2/2014. No longer tracked. - - asvitkine@chromium.org - - The latency of a VariationsService seed fetch that results in a success - response. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The latency of connection to the variations server when fetching an initial - variations seed during Android Chrome first run. This is included in the - Variations.FirstRun.SeedFetchTime measurement. Only considers cases where an - HTTP 200 result was received. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The result of attempting to fetch an initial variations seed during Android - Chrome first run. Records both the HTTP code and various error values in one - enumeration. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The latency of fetching an initial variations seed during Android Chrome - first run. Only considers cases where an HTTP 200 result was received. - - - - - asvitkine@chromium.org - src/base/metrics/OWNERS - - Logs each event related to Android Chrome variations first run prefs to - debug crbug.com/1090968. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The result of attempting to import an initial variations seed during Android - Chrome first run. Logged from VariationsSeedStore::LoadSeed when seed prefs - do not exist. - - - - - - No longer logged - - jwd@chromium.org - - If the registry value for Google Update experiment labels contains - Variations experiments, and therefore needs to have them cleared. This will - be recorderd once per sessions, right before attempting to clear the value. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - How long it took to create the X-Client-Data header. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - caitlinfischer@google.com - src/base/metrics/OWNERS - - The owner of the top-level domain from which certain subframe-initiated HTTP - requests are made. It's logged after determining that (i) the request should - include variations headers, (ii) the request is from a subframe, and (iii) - TrustedParams are not present. It's logged before adding headers. It allows - us to verify whether non-render-thread-initiated requests, if any, lack - TrustedParams. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records number of experiment ids in the X-Client-Data header at the time the - header is constructed. - - - - - asvitkine@chromium.org - jwd@chromium.org - caitlinfischer@google.com - src/base/metrics/OWNERS - - Details about the request context in which an HTTP request is made. Logged - after determining that the request should include variations headers but - before adding the headers. - - - - - asvitkine@chromium.org - jwd@chromium.org - src/base/metrics/OWNERS - - The result of whether to append Variations headers to a request. Logged when - when determining (i) whether the URL to which the request is being sent - should have a variations header and (ii) whether--after a redirect--the - request to which a variations header was added should have the variations - header removed. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records how the country code saved in prefs used for filtering permanent - consistency studies compares to the country code in the variations seed. - This is recorded each time the saved country code is loaded from the pref. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The result of verifying the latest variations seed's signature, recorded - when the seed is loaded from Local State. Not recorded when running in safe - mode. - - - - - - Removed 9/2012. No longer tracked. - - asvitkine@chromium.org - - Whether or not the network was available when requested by the - VariationsService. - - - - - pastarmovj@chromium.org - ydago@chromium.org - src/base/metrics/OWNERS - - Records the restrictions on how experiment variations are applied on the - client. This is recorded at start up. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Number of previous requests to the variations server in the same session, - logged each time a new request is attempted to the variations server. For - example, the value of the 0th bucket indicates the number of initial - requests to the server that took place. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Counts the number of times the VariationsService is allowed or not allowed - to make a request due to the ResourceRequestAllowedNotifier. Useful for - debugging cases where variations seeds may not be getting fetched. - - - - - - Removed as of M85 / Jun 2020. - - rmcelrath@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - - Number of consecutive times WebView started up with a stale seed. Only - written by WebView, when its loaded seed is fresh after previously being - stale. Note that this means it won't be written for WebViews that are never - able to get a fresh seed, or ones that consistently have a fresh seed. - - - - - - Removed as of M66 / Jan 2018. Replaced by - Variations.SafeMode.FellBackToSafeMode2. - - isherman@chromium.org - - Whether or not the VariationsService /would/ fall back to Safe Mode, due to - either too many crashes or too many failures to fetch a new seed, given some - initial/unrefined heuristics. Recorded during Chrome startup, when the - VariationsService is created. - - This metric was only reported before Safe Mode was actually implemented, as - a sanity-check for the forthcoming implementation. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - Whether or not the VariationsService fell back to Safe Mode, due to either - too many crashes or too many failures to fetch a new seed. Recorded during - Chrome startup, immediately before field trials are created. Only recorded - if either a recent or a safe seed was loaded successfully. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - Records whether the safe variations seed was successfully read from local - state on startup. Records a detailed reason on read failure. Only recorded - when attempting to run in safe mode. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - The result of verifying the safe variations seed's signature, recorded when - the seed is loaded from Local State. Only recorded when attempting to run in - safe mode. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - Records the result of storing a safe variations seed (and all associated - metadata) to the seed store. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - The result of verifying the safe variations seed's signature, recorded when - the safe seed is stored to Local State. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - The number of consecutive crashes observed by the VariationsService, without - a single intervening successful seed fetch. Recorded during Chrome startup, - when the VariationsService is created. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - The number of consecutive failed attempts to fetch a new seed by the - VariationsService. Recorded during Chrome startup, when the - VariationsService is created. - - - - - jwd@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - Counts if a response from the variations server is the first response of the - day or not. This is counted when a new valid seed or a 304 is received. The - date line is computed in UTC and the times being compared are the server - time from the server response and the stored server time from the last - successful request. - - - - - - Removed as of 9/2015. - - gab@chromium.org - - Logged on startup when creating field trials from the variations seed if the - build time is ahead of or within 24 hours of the kVariationsSeedDate. Used - as an experiment to see whether the build time could be used to discard very - old seeds. - - - - - - Removed as of 9/2015. - - gab@chromium.org - - Logged on startup when creating field trials from the variations seed if the - build time is behind the kVariationsSeedDate by a day or more. Used as an - experiment to see whether the build time could be used to discard very old - seeds. - - - - - - Removed as of 9/2015. - - gab@chromium.org - - Logged on startup when creating field trials from the variations seed if the - system clock is ahead of or within 24 hours of the kVariationsSeedDate. Used - as an experiment to see whether the system clock could be used to discard - very old seeds. - - - - - - Removed as of 9/2015. - - gab@chromium.org - - Logged on startup when creating field trials from the variations seed if the - system clock is behind the kVariationsSeedDate by a day or more. Used as an - experiment to see whether the system clock could be used to discard very old - seeds. - - - - - - Removed in M61, and replaced by Variations.SeedLoadResult. This histogram - incorrectly conflated failures from loading the seed with failures while - attempting to store seeds with delta compression. - - asvitkine@chromium.org - - Records whether the variations seed was successfully read from local state - on startup. Records a detailed reason on read failure. - - - - - - Removed 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode. - - asvitkine@chromium.org - - The counts of HTTP response codes encountered by VariationsService when - attempting to fetch a variations seed from the server. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - HTTP response codes and network error encountered by VariationsService when - attempting to fetch a variations seed from the server over an HTTPS - connection. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - HTTP response codes and network error encountered by VariationsService when - attempting to fetch a variations seed from the server over an HTTP - connection. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The time interval between when the variations seed was downloaded and when - it was loaded for use. Not recorded for expired seeds, nor when the download - time is unknown (typically, for seeds imported via first run). - - - - - changwan@chromium.org - src/base/metrics/OWNERS - - Records the time spent blocking WebView startup to wait for the variations - seed. This is less than the entire time needed to load the seed, since - startup is only blocked if loading is not complete by the time the seed is - needed. This would ideally have a maximum value equal to the timeout in - VariationsSeedLoader, but there is no actual limit on how late that timeout - could fire. This is logged once per WebView startup, whether or not loading - the seed was successful. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records whether the latest variations seed was successfully read from local - state on startup. Records a detailed reason on read failure. Not recorded - when running in safe mode. - - - - - - Removed 2019-06. See results on https://crbug.com/936172#c8. - - changwan@chromium.org - - Records the time spent loading the variations seed in WebView, specifically, - the time to call VariationsUtils.readSeedFile(). This is logged once per - WebView startup, and is only logged if loading was successful. - - - - - - Removed 2019-06. See results on https://crbug.com/936172#c8. - - changwan@chromium.org - - Records how long we would block WebView startup to wait for the variations - seed if there were no timeout. This is measured from when we start blocking - until when the FutureTask which loads the seed finishes. The FutureTask may - finish before we block at all, in which case this will be 0. This is logged - once per WebView startup, whether or not loading was successful. - - - - - isherman@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS - - Records how long it takes to load and process variations seed. This metric - is recorded only when loading and processing of the seed is successful. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records the result of storing the variations seed that was received from the - server. Also logs the types of data received (gzip, delta, etc). - - - - - - Removed 11/2012. No longer tracked. - - asvitkine@chromium.org - - Whether or not the 1-Percent uniformity trial from the Variations server was - expired when loaded. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records the time taken to perform variations seed simulation. - - Recorded on every variation seed simulation, which follows a fetch. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records the result of variations seed simulation. Logs the number of - experiment groups in the "kill best effort" category that are - expected to change on a restart of the browser with the received seed. - - Recorded on every variation seed simulation, which follows a fetch. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records the result of variations seed simulation. Logs the number of - experiment groups in the "kill critical" category that are - expected to change on a restart of the browser with the received seed. - - Recorded on every variation seed simulation, which follows a fetch. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Records the result of variations seed simulation. Logs the number of - experiment groups in the "normal" category that are expected to - change on a restart of the browser with the received seed. - - Recorded on every variation seed simulation, which follows a fetch. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The size of the variations seed data, which may be a partial (delta) or - compressed (gzip) payload, see Variations.SeedStoreResult. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - On successful save of a delta-compressed variations seed, records the size - of the delta in KiB. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - On successful save of a delta-compressed variations seed, records the size - of the delta as a percentage of the decoded seed size. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - Records the size of the gzip-compressed variations seed in KiB. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - Records the size of the gzip-compressed variations seed as a percentage of - the decoded seed size. Note that variations seed could be first - delta-compressed and then gzip-compressed. In this case we record - gzip-compressed seed size as a percentage of the delta-compressed seed size. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - Records whether a country code was present when storing the variations seed. - - - - - - Removed 2019/07 - - asvitkine@chromium.org - - On successful save of a non-delta-compressed variations seed, records the - size of the received seed in KiB. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The result of verifying the variations seed signature, recorded when the - variations seed is stored to Local State after being retrieved from the - server. - - - - - asvitkine@chromium.org - src/base/metrics/OWNERS - - Records the number of UI strings overriden for each study that overrides - strings. Recorded at start up when each study is evaluated. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - The time since the previous attempt to fetch the variations seed within the - same session, with 0 indicating that this is the first attempt. Recorded - when a variations seed fetch is attempted by the VariationsService. - - - - - - Removed 1/2013. No longer tracked. - - asvitkine@chromium.org - - A count of the number of times we hit the code where the - UMA-Uniformity-Trial-1-Percent field trial is disabled as a result of the - expiration check. - - - - - - Removed 1/2013. No longer tracked. - - asvitkine@chromium.org - - Tracks whether the UMA-Uniformity-Trial-1-Percent field trial was not active - and which factors contributed to it. - - - - - asvitkine@chromium.org - rkaplow@chromium.org - src/base/metrics/OWNERS - - Log the user channel assigned at browser startup used for evaluating the - variations seeds. - - - - - rmcelrath@chromium.org - src/android_webview/OWNERS - - The result of a WebView seed download. Records both the HTTP code and - various error values in one enumeration. - - - - - rmcelrath@chromium.org - src/android_webview/OWNERS - - The duration of the network request to downloads a new WebView variations - seed from the variations server to the central on-device service. - - - - - rmcelrath@chromium.org - src/android_webview/OWNERS - - The time between the start of two consecutive WebView seed downloads by - WebView's service. This metric will not be written if seeds are never - downloaded. - - - - - rmcelrath@chromium.org - src/android_webview/OWNERS - - The delay between when a WebView seed download was scheduled by the service - with the JobScheduler and when it was executed. - - - - - binlu@google.com - - Records instances of navigator.vibrate. Includes whether or not it comes - with a user gesture, same-origin subframe or cross-origin subframe. - - - - - yoshiki@chromium.org - - Chrome OS Video Player: the results of the cast API extension load. This is - recorded after the initialization of the extension is finished. - - - - - yoshiki@chromium.org - - Chrome OS Video Player: the length of casted video (in seconds). - - - - - yoshiki@chromium.org - - Chrome OS Video Player: the number of cast devices. This is recorded when - the cast extension finishes the discovery. - - - - - yoshiki@chromium.org - - Chrome OS Video Player: the number of files being opened on launch. - - - - - yoshiki@chromium.org - - Chrome OS Video Player: type of playback (eg. local play, cast). This is - recorded when a video starts playing. - - - - - bokan@chromium.org - - Tracks the proportion of non-mobile optimized (i.e. zoom disabled or layout - width matches viewport) page views that had a user-initiated page scale - (e.g. pinch-zoom, double-tap). Recorded on navigation to a new page - on - Android only. - - - - - bokan@chromium.org - - Tracks the maximum scale factor that a user has scaled to over the lifetime - of the page. The scale is counted at pinch end (e.g. zooming to 300% and - back out to 150% in one gesture would count as 150%). Reported only on - non-mobile optimized pages (i.e. zoom disabled or layout width matches - viewport) which have had a page scale changing gesture. Recorded on - navigation to a new page - on Android only. - - - - - bokan@chromium.org - - The viewport meta tag type seen on each page load. Only recorded on Android. - - - - - bokan@chromium.org - - The screen width as a percentage of viewport width (i.e. zoom at which we - can see the whole page). Only recorded on Android and for viewport meta tags - with constant width. - - - - - wychen@chromium.org - dtrainor@chromium.org - The interval between ViewResourceAdapter#getBitmap calls. - - - - oka@chromium.org - - An integer representing a state transition from x to y in the form of x * - 1000 + y. If the transition is not expected, the value is negated. For - example an expected transition from SHOWING (= 2) to SHOWN (= 1) is denoted - as 2001, and an unexpected transition from SHOWING to SHOWING is denoted as - -2002. See KeyboardControllerState for the correspondence between the number - and the enum. - - - - - - Removed 2019/6 because it's equivalent to VirtualKeyboard. - ControllerStateTransition. - - oka@chromium.org - - Validity of a state transtion. This is equivalent to the positiveness of - VirtualKeyboard.ControllerStateTransition. - - - - - oka@chromium.org - Latency of the keyboard being loaded for the first time. - - - - Please list the metric's owners. Add more owner tags as needed. - - A count of various control events that can occur on the virtual keyboard, - such as showing and hiding. - - - - - - Removed 04/2016 as doesn't have data nor owner. - - Please list the metric's owners. Add more owner tags as needed. - - Counts the number of keys typed by the virtual keyboard between each - backspace. This metric provides a rough approximation of an error rate for - the virtual keyboard. - - - - - oka@chromium.org - - Records whenever an intermediate keyboard state has been active for longer - than a fixed timeout. - - - - - dcastagna@chromium.org - hoegsberg@chromium.org - - Overlay strategies used to promote Hardware Overlays, per frame. Recorded - every time a frame is rendered by the display compositor. - - - - - magchen@chromium.org - zmo@chromium.org - - Any root damage excluding overlay damage in the current frame? - - - - - magchen@chromium.org - zmo@chromium.org - - The root damage type excluding underlay damage in the current frame. - - - - - - This previously reported a latency metric for Viz on all platforms. This has - been replaced by improved tracing and Graphics.Smoothness metrics. Marked - obsolete in M87. - - jonross@chromium.org - - Records the delta from when a viz::LocalSurfaceId was allocated, to the time - where it is first embedded by the Viz Service. - - - - - samans@chromium.org - sadrul@chromium.org - viz-team-wat@google.com - - The time it took from when FrameSinkVideoCapturerImpl sent a request for an - I420 readback until the result comes back and ReadI420Planes successfully - finishes. - - - - - samans@chromium.org - sadrul@chromium.org - viz-team-wat@google.com - - Whether an I420 readback initiated by FrameSinkVideoCapturerImpl succeeded. - - - - - samans@chromium.org - sadrul@chromium.org - viz-team-wat@google.com - - The time it took from when FrameSinkVideoCapturerImpl sent a request for an - RGBA readback until the result comes back and ReadRGBAPlane successfully - finishes. - - - - - samans@chromium.org - sadrul@chromium.org - viz-team-wat@google.com - - Whether an RGBA readback initiated by FrameSinkVideoCapturerImpl succeeded. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - - Android: The source of a dismissed voice search, such as omnibox or NTP. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - - Android: The source of a failed voice search, such as omnibox or NTP. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - - Android: The source of a successful voice search, such as omnibox or NTP. - - - - - muyuanli@chromium.org - - Counts the number of requests to retrieve voice interaction context when no - user interaction is initiated. - - - - - - Previously recorded for CrOS, but is no longer used. Marked obsolete in M86. - - xiaohuic@chromium.org - - Records the time between a voice interaction session start and end. - - - - - wylieb@chromium.org - tedchoc@chromium.org - - Records the time it takes between the user clicking the mic and chrome - recieving the transcribed voice query. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - - Android: The source of a voice search start event, such as omnibox or NTP. - - - - - wylieb@chromium.org - tedchoc@chromium.org - - Android: The source of an incoming result that doesn't align with an - outgoing request from Chrome. - - - - - muyuanli@chromium.org - - Records the time between user interaction and the actual request arrival. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - - Android: Records the confidence value of a successful voice search as a - percentage. - - - - - wylieb@chromium.org - tedchoc@chromium.org - yusufo@chromium.org - Android: Records whether the voice search produced results. - - - - - Removed 02/2018 in issue 799074. - VR.Component.Assets.DurationUntilReady.OnRegisterComponent measures the - intended metric more accurately. - - tiborg@chromium.org - - Duration from starting Chrome until VR assets component is ready to use. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - Duration from entering a VR mode until the VR assets component is ready to - use. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - Duration from registering VR assets component until it is ready to use. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - Status of the VR assets component when entering a VR mode. - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - The component version and status of loading the VR assets. The value is - encoded as (XXX)(YYY)(SSS) where XXX is the major component version, YYY the - minor component version and SSS the status. See - //chrome/browser/vr/assets_load_status.h for possible status values. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - The version and update status of the VR assets component. The value is - encoded as (XXX)(YYY)(SSS) where XXX is the major version, YYY the minor - version and SSS the status. See - //chrome/browser/vr/assets_component_update_status.h for possible status - values. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - Recorded every time a user tries to enter the VR browser without the VR - feature module installed. Is success if the user could enter the VR browser - nonetheless. Is failure if entering the VR browser was blocked (on - smartphone VR) or started in 2D-in-VR mode (on standalones). - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - Network connection type when entering a VR mode. - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - - Network connection type when registering the VR component(s). - - - - - - Removed 02/2020 - - xr-dev@chromium.org - - Number of times voice search is started in a single VR session. Recorded - when a new disjoint session has begun or when the session has ended in a - non-continuable way. - - - - - - Removed 06/2020. - - xr-dev@chromium.org - - We must suppress monocularly rendered ui elements in VR. This records which - ui element suppressions are encountered in practice. - - - - - - Removed 06/2020. - - vollick@chromium.org - - We must exit VR mode when browsing in certain situations. This records which - situations are encountered in practice. - - - - - - Removed 06/2020. - - xr-dev@chromium.org - The end state of a voice search request in VR. - - - - - Removed 06/2020. - - xr-dev@chromium.org - - Chrome shows a prompt when the OS's record audio permission is needed for - voice search. The prompt gives user two choices: CANCEL or CONTINUE. This - records the user's selection. - - - - - - Removed as of 02/2019, VR DLAs are no longer supported. - - ymalik@chromium.org - - Whether we're auto-presenting the first time we enter WebVR mode. - - - - - - As of 5/18/2020 this appears to no longer be logged. - - alcooper@chromium.org - xr-dev@chromium.org - - The result of calls to VRDisplay::requestPresent(). Reported twice per - requestPresent() call, once to record the call, and once to record the - result. - - - - - ymalik@chromium.org - - Whether the user had been through the FRE when Chrome is launched in VR - mode. - - - - - - Removed 06/2020. - - alcooper@chromium.org - xr-dev@chromium.org - The version of the runtime being used for VR. - - - - - Removed 02/2020 - - alcooper@chromium.org - xr-dev@chromium.org - - Count of navigations while in a VR session. Logged when a new disjoint - session has begun, or when the session has ended in a non-continuable way. - - - - - alcooper@chromium.org - xr-dev@chromium.org - - The duration of the VR session. Logged when a new disjoint session has - begun, or when the session has ended in a non-continuable way. - - - - - - Removed as of 02/2019, VR DLAs are no longer supported. - - ymalik@chromium.org - - The duration of a single VR session initiated via a deep-linked WebVR app. - Logged when a new disjoint session has begun, or when the session has ended - in a non-continuable way. - - - - - alcooper@chromium.org - xr-dev@chromium.org - - Number of videos watched in a VR session. Logged when a new disjoint session - has begun, or when the session has ended in a non-continuable way. - - - - - alcooper@chromium.org - xr-dev@chromium.org - - The duration of a single session spent watching video in VR. Logged when a - new disjoint session has begun, or when the session has ended in a - non-continuable way. - - - - - alcooper@chromium.org - xr-dev@chromium.org - The type of headset being used for VR. - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's accept legal - document API call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's authenticate - instrument API call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's get full wallet API - call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's get wallet items - API call. - - - - - - Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's save address API - call. - - - - - - Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's save instrument API - call. - - - - - - Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's save instument and - address API call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's save to wallet API - call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's send status API - call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's unknown API calls. - - - - - - Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's update address API - call. - - - - - - Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. - - estade@chromium.org - - Measures the time taken by Google Online Wallet server's update instument - API call. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - - Counts the number of times each Wallet API failed due to being unable to - parse the response. - - - - - - requestAutocomplete was removed in M52. - - estade@chromium.org - HTTP response codes seen by Wallet client. - - - - - Removed 08/2016 because CertVerifier is not used for web view cert - verification. - - eugenebut@chromium.org - - [iOS] Reports certificate verification mismatch between SecTrust API and - CertVerifier. SecTrust API is used for making load/no-load decision and - CertVerifier is used for getting the reason of verification failure. It is - expected that mismatches will happen for those 2 approaches (e.g. SecTrust - API considers cert as good, but CertVerifier considers same cert as bad). - This metric helps to understand how common mismatches are. - - - - - eugenebut@chromium.org - gambard@chromium.org - - [iOS] Reports URL matches between the return value from the WebState's - GetLastCommittedURL and GetCurrentURL methods. It is expected the origins - will be equal to confirm that GetCurrentURL can now be replaced with - GetLastCommittedURL. This will be called each time WebStateImpl:: - GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an - old method of obtaining the url and trust level. The trust level was only - relevant with UIWebView, so this method is only called from code which has - not yet been updated since UIWebView was removed. - - - - - - Removed as of 9/2013, replaced by - Web.CurrentOriginEqualsLastCommittedOrigin. - - michaeldo@chromium.org - - [iOS] Reports URL matches between the return value from the WebState's - GetLastCommittedURL and GetCurrentURL methods. It is expected the values - will be equal to confirm that GetCurrentURL can now be replaced with - GetLastCommittedURL. This will be called each time WebStateImpl:: - GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an - old method of obtaining the url and trust level. The trust level was only - relevant with UIWebView, so this method is only called from code which has - not yet been updated since UIWebView was removed. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the available space that can be used when installing a WebAPK from - Google Play fails. The space recorded is the available space beyond the - system's minimum free space threshold, with a range between -1000 and 1000 - MB. Negative values mean that there is less free space available than the - system's minimum, by the given amount. - - - - - - Removed 2017-09. As of M64, this is no longer recorded. - - hanxi@chromium.org - ranj@chromium.org - yfriedman@chromium.org - - Records the available space that can be used when installing a WebAPK from - Google Play succeeds. The space recorded is the available space beyond the - system's minimum free space threshold, with a range between -1000 and 1000 - MB. Negative values mean that there is less free space available than the - system's minimum, by the given amount. - - - - - - Removed in Chrome M69. - - hanxi@chromium.org - yfriedman@chromium.org - - Records the available space that can be used when installing a WebAPK from - Google Play fails after freeing up cache and unimportant storage. The space - recorded is the available space beyond the system's minimum free space - threshold, with a range between -1000 and 1000 MB. Negative values mean that - there is less free space available than the system's minimum, by the given - amount. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the available space that can be used when installing a WebAPK from - Google Play fails after freeing up cache. The space recorded is the - available space beyond the system's minimum free space threshold, with a - range between -1000 and 1000 MB. Negative values mean that there is less - free space available than the system's minimum, by the given amount. - - - - - - Removed in Chrome M69. - - hanxi@chromium.org - ranj@chromium.org - yfriedman@chromium.org - - Records the available space that can be used when installing a WebAPK from - Google Play fails after freeing up unimportant storage. The space recorded - is the available space beyond the system's minimum free space threshold, - with a range between -1000 and 1000 MB. Negative values mean that there is - less free space available than the system's minimum, by the given amount. - - - - - - Removed 2020-04. - - hanxi@chromium.org - yfriedman@chromium.org - - Records the Chrome cache size when installing a WebAPK from Google Play - fails, with a range between 0 and 1000, rounded to the nearest 10MB. - - - - - - Removed in Chrome M69. - - hanxi@chromium.org - ranj@chromium.org - yfriedman@chromium.org - - Records the Chrome unimportant storage size when installing a WebAPK from - Google Play fails, with a range between 0 and 1000, rounded to the nearest - 10MB. - - - - - - Removed in Chrome M69. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - Records the amount of time that it takes to bind to the play install service - for WebAPK installs. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the error code when installing a WebAPK from Google Play fails. See - go/webapk-install-googleplayerrorcode. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records whether installing a WebAPK from Google Play succeeded. If not, - records the reason that the install failed. - - - - - - Deleted in M61. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - On web app and WebAPK installation, records whether a WebAPK could be - installed via the Google Play flow. If not, records why the WebAPK could not - be installed via the Google Play flow (and a web app was added to the - homescreen instead). Warning: This metric is recorded whenever a site is - added to the homescreeen as a web app, not just for sites with a WebAPK - compatible Web Manifest. - - - - - - Removed 2017-08. As of M62, this is no longer recorded. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or - the add to homescreen menu item. This stat tracks whether the installation - is triggered by an app banner or by the add to homescreen menu. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - How long it takes to install a WebAPK. The time is measured from the time - that the user initiates the install to the time that the Open button is - shown in the infobar. This metric is only recorded when install succeeds. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or - the add to homescreen menu item. This stat tracks WebAPK installation - events. - - - - - - No longer recorded as of M65. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or - the add to homescreen menu item. If the installation is via an app banner, - user could either accept to install or dismiss the infobar; while via the - add to homescreen menu, the installation will start automatically. This stat - tracks the ways that user accepts to install a WebAPK. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the amount of time which has elapsed from the "install infobar - showing" to the "install request being sent to Google Play". - This time includes the time that it takes to request the WebAPK token and - the time that it takes to compute the hashes for the launcher icon and the - badge icon. - - - - - - Removed 2020-04. - - hanxi@chromium.org - yfriedman@chromium.org - - Whether there is enough space to install a WebAPK. Recorded on each attempt - to install a WebAPK. - - - - - - Removed 2017-08. As of M62, this is no longer recorded. - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or - the add to homescreen menu item. If the user clicks the add to homescreen - menu, and a WebAPK has been installed before, an infobar with an open button - will show. The open button will also show on the infobar after a successful - installation. This stat tracks whether user clicks the open button on the - infobar or dismiss it. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the error codes when a WebAPK is launched with network failures. - - - - - - Removed 2018-01. Replaced by WebApk.LaunchInterval2 - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - Records the amount of time since the user last launched the WebAPK from the - homescreen. Not recorded on first launch. - - - - - - Removed 2020-01. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - Records the amount of time since the user last launched the WebAPK from the - homescreen. Not recorded on first launch. - - - - - - Removed 2020-04. - - hartmanng@chromium.org - peconn@chromium.org - pkotwicz@chromium.org - - Recorded each time that a child tab - e.g. a tab opened via window.open() - - is navigated. Records whether the navigation is within the scope of the - WebAPK's Web Manifest. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Recorded each time that a WebAPK is navigated. Records whether the - navigation is within the scope of the WebAPK's Web Manifest. Not recorded - for child tabs - e.g. tabs opened via window.open() - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - When a WebAPK receives a notification, log whether it has permission to - display that notification. - - - - - - Removed in Chrome M69. - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - When a user visits a PWA for which they have a WebAPK installed, the menu - item changes from 'Add to homescreen' to 'Open WebAPK'. This stat tracks - whether the opening of the WebAPK is successful when this menu item is - clicked. - - - - - - Removed 2017-11. This UMA logs extra requests. Replaced by - ChromePermissionDenied2. - - hanxi@chromium.org - pkotwicz@chromium.org - ranj@chromium.org - yfriedman@chromium.org - - The number of Android runtime permission requests that are denied for the - WebAPK because Chrome does not have access to that permission. - - - - - - Removed 2020-03. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - The number of Android runtime permission requests that are denied for the - WebAPK because Chrome does not have access to that permission. - - - - - - Removed 2020-03. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - Records the amount of requests of Android runtime permissions which haven't - been granted to Chrome when Chrome is running in WebAPK runtime. - - - - - - Removed 2018-08 in favour of WebApk.Session.TotalDuration2. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - The length of a WebAPK session (launch/foregrounding to backgrounding) in - milliseconds. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - The length of a WebAPK session (launch/foregrounding to backgrounding) in - milliseconds. - - - - - - Removed 2018-08 in favour of WebApk.ShellApkVersion2. - - hanxi@chromium.org - pkotwicz@chromium.org - yfriedman@chromium.org - - Records WebAPK "Shell APK version" when the WebAPK is launched. - The "Shell APK version" is documented in shell_apk_version.gni - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records WebAPK "Shell APK version" when the WebAPK is launched. - The "Shell APK version" is documented in shell_apk_version.gni - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Tracks the time to splash screen visible starting from the launch of the - WebAPK shell (rather than from the launch of Chrome) for new-style WebAPKs. - The WebAPK shell displays the splash screen for new-style WebAPKs. - - This is recorded iff: - This is a cold startup of Chrome. - Chrome has not - been sent to the background since launch. - There was no recents entry for - Chrome (Android replays intents if a recents entry exists), which otherwise - adds noise/long-tail to this histogram. - - - - - mheikal@chromium.org - yfriedman@chromium.org - - Tracks the time to splashscreen hidden starting from the launch of the - WebAPK shell (rather than from the launch of Chrome). The splashscreen is - hidden after the first visually non-empty paint. - - This is recorded iff: - This is a cold startup of Chrome. - Chrome has not - been sent to the background since launch. - There was no recents entry for - Chrome (android replays intents if a recents entry exists), which otherwise - adds noise/long-tail to this histogram. - - - - - mheikal@chromium.org - yfriedman@chromium.org - - Tracks the time to splashscreen visible starting from the launch of the - WebAPK shell (rather than from the launch of Chrome). The splashscreen is - shown during postInflationStartup. - - This is recorded iff: - This is a cold startup of Chrome. - Chrome has not - been sent to the background since launch. - There was no recents entry for - Chrome (android replays intents if a recents entry exists), which otherwise - adds noise/long-tail to this histogram. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - Records that a WebAPK was uninstalled. - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records whether updating a WebAPK from Google Play succeeded. If not, - records the reason that the update failed. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the number of zombie "WebAPK update request" files that - the update process failed to cleanup. Recorded for all WebAPKs whenever a - WebAPK or webapp is launched. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the number of times that a WebAPK update request was queued (i.e. - waiting for the WebAPK to be backgrounded) before being sent to the server. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records the time point when a request to update a WebAPK is sent to the - WebAPK Server. - - - - - hartmanng@chromium.org - - src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS - - - Records whether Chrome can bind to a WebAPK's "WebAPK service". - Recorded each time that Chrome attempts to bind to a WebAPK service. - - - - - dominickn@chromium.org - peconn@chromium.org - - Records the number of milliseconds that the add to homescreen dialog - required to check installability eligibility. - - - - - finnur@chromium.org - beverloo@chromium.org - - Keeps track of what verbiage was shown in the App menu versus what was - actually installed. - - - - - asamidoi@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - Records the result of the promotability check that decides if a PWA install - prompt appears depending on that the site has a service worker with offline - support. - - - - - asamidoi@chromium.org - shimazu@chromium.org - chrome-worker@google.com - - Records the time to complete the promotability check that decides if a PWA - install prompt appears depending on that the site has a service worker with - offline support. - - - - - calamity@chromium.org - mgiuca@chromium.org - loyso@chromium.org - - The type of engagement (navigation, user input, etc.) which led to an - accumulation in site engagement within a web app window or tab. Should be - collected for a subset of SiteEngagementService.EngagementType, which is - triggered for all browsing contexts. Recorded at the time of engagement - accumulation (e.g., when mouse is clicked). - - - - - - Removed 3/2019 because only counts PWAs. Superseded by the WebApp.Engagement - histogram with suffixes. - - calamity@chromium.org - mgiuca@chromium.org - - The type of engagement (navigation, user input, etc.) which led to an - accumulation in site engagement within a PWA app window. Should be collected - for a subset of SiteEngagementService.EngagementType, which is triggered for - all browsing contexts. Recorded at the time of engagement accumulation - (e.g., when mouse is clicked). - - - - - alancutter@chromium.org - mgiuca@chromium.org - loyso@chromium.org - - The HTTP status code class returned for each icon loaded during a WebApp's - creation. See corresponding - Extensions.BookmarkApp.Icon.HttpStatusCodeClassOnCreate histogram for legacy - extension-based system. Recorded when WebAppDataRetriever starts downloading - icons. - - - - - alancutter@chromium.org - mgiuca@chromium.org - loyso@chromium.org - - The HTTP status code class returned for each icon loaded when syncing a - WebApp. See Extensions.BookmarkApp.Icon.HttpStatusCodeClassOnSync histogram - for legacy extension-based system. Recorded when WebAppDataRetriever starts - downloading icons. - - - - - alancutter@chromium.org - raymes@chromium.org - loyso@chromium.org - - The HTTP status code class returned for each icon loaded when updating a - WebApp. Recorded when WebAppDataRetriever starts downloading icons. - - - - - - Removed 2019-11 and replaced by Webapp.Install.DisplayMode2, which correctly - records manifest display modes on desktop. - - peter@chromium.org - yfriedman@chromium.org - - Records the display mode (as defined in the Web App Manifest spec) at the - install time of a WebApp (including WebApks). - - - - - ericwilligers@chromium.org - peter@chromium.org - yfriedman@chromium.org - - Records the display mode (as defined in the Web App Manifest spec) at the - install time of a WebApp. Fixes a bug in the data collection for desktop web - apps. - - - - - dominickn@chromium.org - alancutter@chromium.org - - Records when a web app install bounced for different install sources. A - bounce is when the user uninstalls the web app within 1 hour of installing - it. - - - - - dominickn@chromium.org - loyso@chromium.org - calamity@chromium.org - - Records the mechanism and source from which a web app installation was - triggered, regardless of whether the installation was successful. - - - - - - Removed 2018-01 in favour of Webapp.Install.InstallEvent. - - mcgreevy@chromium.org - - Records the mechanism by which a web app installation was triggered, - regardless of whether the installation was successful. - - - - - - Expired in M77. - - dominickn@chromium.org - - Records whether or not the check that a site is or isn't a Progressive Web - App (PWA) completes before the add to homescreen dialog on Android forcibly - times out and falls back to generating an icon. - - - - - - Expired in M77. - - dominickn@chromium.org - - Records whether or not the check that a site is or isn't a Progressive Web - App (PWA) has completed when the user taps the add to homescreen menu item - on Android. - - - - - - Expired in M77. - - dominickn@chromium.org - - Records whether or not the check that a site is or isn't a Progressive Web - App (PWA) has completed when the user opens the menu on Android. - - - - - dmurph@chromium.org - desktop-pwa-team@google.com - - Records the reason that the WebApp install confirmation dialog is closed. - This dialog is shown when the user clicks on the 'install' icon in the - omnibox for websites that are installable. This metric is intended to give - data for an experiment to choose the best install icon. - - - - - - Replaced by Webapp.SystemApps.FreshInstallDuration in 09/2020, issue - https://crbug.com/1129275. - - calamity@chromium.org - ortuno@chromium.org - - Records the number of seconds taken to install system web apps, from when we - dispatch a call to install them, until we get all the installation results. - Recorded in milliseconds, from 1 millisecond to 3 minutes. - - - - - - - calamity@chromium.org - ortuno@chromium.org - Records the result code of Web App installs. - - - - - - calamity@chromium.org - ortuno@chromium.org - - Records why System Web App .crx extension is disabled during System Web App - installs. Certain properties of the profile might cause Extensions to be - disabled as soon as they are installed. For example, kiosk profile might set - policies to disable all Extensions, including System Web Apps which are - considered Extensions. - - - - - - - calamity@chromium.org - ortuno@chromium.org - - Records .crx extension error code when System Web App install fails. - - - - - davidbienvenu@chromium.org - jessemckenna@google.com - - The result of a Progressive Web App (PWA) launcher's attempt to launch - Chrome. Windows-only. - - - - - davidbienvenu@chromium.org - jessemckenna@google.com - - The result of updating a single Progressive Web App (PWA) launcher with the - latest version of chrome_pwa_launcher.exe. Windows-only. - - - - - alancutter@chromium.org - dxie@google.com - loyso@google.com - mgiuca@google.com - - The result of deploying a follow up migration after a migration bug - (https://crbug.com/1125020) that caused users' web apps to open in a browser - tab instead of a standalone window. This follow up migration only runs once - at startup for all Chrome profiles. If it fails it will retry until - successful on subsequent start ups, metrics are only recorded on success. - - - - - peter@chromium.org - hartmanng@chromium.org - - Records whether the top-level navigations in standalone Web Apps result in - presenting the web content or showing the error page. - - - - - alancutter@chromium.org - desktop-pwas-team@google.com - - Records how many preinstalled web app config files failed to parse as valid - JSON with valid fields. See external_web_app_utils.cc ParseConfig(). This is - recorded at start up. - - - - - alancutter@chromium.org - desktop-pwas-team@google.com - - Records how many preinstalled web apps configs were disabled for the device. - This is recorded at start up. - - - - - alancutter@chromium.org - desktop-pwas-team@google.com - - Records how many preinstalled web apps configs were enabled for the device. - This is recorded at start up. - - - - - phillis@chromium.org - dmurph@chromium.org - Records the result of shortcut creation for PWA. - - - - - Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer - needed or recorded. - - mlamouri@chromium.org - - Records the status of the splashscreen's background color (default or - custom). - - - - - - Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer - needed or recorded. - - mlamouri@chromium.org - Records the time during which the splashscreen was visible. - - - - - Removed 2020-04. - - pkotwicz@chromium.org - hartmanng@chromium.org - Records the signal that was used to hide the splashscreen. - - - - - Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer - needed or recorded. - - mlamouri@chromium.org - - Records the size of the icon used to construct the splashscreen in device - pixels (ie. real size divided by device pixel density). This is only - recording one dimension, the icon being square. - - - - - - Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer - needed or recorded. - - mlamouri@chromium.org - - Records the origin of the icon used to construct the splashscreen. - - - - - - Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer - needed or recorded. - - mlamouri@chromium.org - - Records the status of the splashscreen's theme color (default or custom). - - - - - - Removed 08/2020. Information no longer recorded. - - alancutter@chromium.org - loyso@chromium.org - - Records installation result code for sync initiated fallback installs in the - new USS-based web applications system. - - - - - alancutter@chromium.org - loyso@chromium.org - - Records uninstallation result for sync initiated uninstalls in the new - USS-based web applications system. - - - - - calamity@chromium.org - ortuno@chromium.org - - Records the time taken to perform a fresh install of all system web apps. It - measures the time from when we dispatch a call to install them, until we get - all the installation results. This intentionally excludes the scenario where - we don't request to install all the apps for consistency. Recorded in - milliseconds, from 1 millisecond to 3 minutes. - - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of uninstalling a WebApp when the user clicks on - "Uninstall" from the 3-dot menu of the respective WebApp window. - - - - - dmurph@chromium.org - desktop-pwas-team@google.com - - Records the result of uninstalling an app from the chrome://apps page. This - happens whena user right-clicks on a greyed out webapp icon in the - chrome://apps page and clicks "Uninstall". - - - - - benwells@chromium.org - dominickn@chromium.org - loyso@chromium.org - - Records the user response to the dialog shown when uninstalling a web app. - - - - - alancutter@chromium.org - loyso@chromium.org - raymes@chromium.org - - Records the result of web app manifest update checks during page - navigations. Note that "No app in scope" results are ignored due - to the expected several orders of magnitude higher volume than all other - update results. - - - - - qjw@chromium.org - ortuno@chromium.org - desktop-pwas-team@google.com - Records the result of WebAppUrlLoader::PrepareForLoad(). - - - - rtoy@chromium.org - hongchan@chromium.org - - The length (in frames) requested by createBuffer(). Recorded for every call - to createBuffer(). Probably many (tens or hundreds) per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The number of channels requested by createBuffer(). Recorded for every call - to createBuffer(). Probably many (tens or hundreds) per page. - - - - - - Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher - supported sample rates. - - rtoy@chromium.org - hongchan@chromium.org - - The sample rate (in Hz) requested by createBuffer(). Recorded for every call - to createBuffer(). Probably many (tens or hundreds) per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The sample rate (in Hz) requested by createBuffer(). Recorded for every call - to createBuffer(). Probably many (tens or hundreds) per page. - - - - - - Replaced by SampleRateRatio384kHz in Issue 644683 on 2016/10 due to higher - supported sample rates. - - rtoy@chromium.org - hongchan@chromium.org - - The ratio of the buffer sample rate from createBuffer() to the context - sample rate. This indicates if the buffer needs to be resampled. Recorded - for every call to createBuffer(). Probably many (tens or hundreds) per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The ratio of the buffer sample rate from createBuffer() to the context - sample rate. This indicates if the buffer needs to be resampled. Recorded - for every call to createBuffer(). Probably many (tens or hundreds) per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The hardware sample rate (in Hz) used by an AudioContext. Recorded for every - WebAudio AudioContext that is created; probably only one or two per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The maximum number of (hardware) channels available in an AudioContext. - Recorded for every WebAudio AudioContext that is created; probably only one - or two per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The sample rate requested by developer to be used as the sample rate when - constructing an AudioContext with an AudioContextOptions dictionary. This is - recorded for each AudioContext created, probably just one or two per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The ratio of the user-selected sample rate to the hardware sample rate of an - AudioContext. The ratio is represented as a percentage. This is recorded for - each AudioContext created, probably just one or two per page. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The callback buffer size (in audio frames) for WebAudio rendering between - the WebAudio graph and the audio device thread. This can differ from the - value recommended by the audio hardware due to internal constraints in - WebAudio. Recorded for every WebAudio AudioContext that is created. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The buffer size (in audio frames) for WebAudio rendering recommended by the - audio hardware. Recorded for every WebAudio AudioContext that is created. - - - - - - Removed 02/2018 in Issue 764396. Information no longer needed or recorded. - - rtoy@chromium.org - hongchan@chromium.org - - The number of times the AudioParam value setter was called that also - conflicts with an ongoing AudioParam automation. Updated when the realtime - AudioContext is closed. - - - - - - Removed 02/2018 in Issue 764396. Information no longer needed or recorded. - - rtoy@chromium.org - hongchan@chromium.org - - The percentage of number of calls to an AudioParam value setter that - conflicts with an ongoing AudioParam automation to the total number of calls - to the value setter. Updated once when an AudioContext is closed. - - - - - - Removed 02/2018 in Issue 764396. Information no longer needed or recorded. - - rtoy@chromium.org - hongchan@chromium.org - - The number of times the AudioParam value setter was called per tab. Updated - when the realtime AudioContext is closed. - - - - - mlamouri@google.com - media-dev@chromium.org - rtoy@chromium.org - hongchan@chromium.org - - The autoplay status of an AudioContext when destroyed. This include all - types of frames. In order to know the value only for main frames, the - .CrossOrigin values can be substracted. - - - - - mlamouri@google.com - media-dev@chromium.org - rtoy@chromium.org - hongchan@chromium.org - - The autoplay status of an AudioContext when destroyed in a cross-origin - frame. - - - - - mlamouri@google.com - media-dev@chromium.org - rtoy@chromium.org - hongchan@chromium.org - - Records how an AudioContext was unlocked (if it was). This is recorded when - the AudioContext is destroyed. - - - - - - Removed in Issue 774526 on 2017/10; statistics aren't needed anymore. - - rtoy@chromium.org - hongchan@chromium.org - - The Q value (in 0.25 dB steps) used for a highpass BiquadFilter. Recorded - each time the value is set for a highpass filter via the .value setter or - the automation methods linearRampToValueAtTime, exponentialValueAtTime, and - setValueAtTime. - - - - - - Removed in Issue 774526 on 2017/10; statistics aren't needed anymore. - - rtoy@chromium.org - hongchan@chromium.org - - The Q value (in 0.25 dB steps) used for a lowpass BiquadFilter. Recorded - each time the value is set for a lowpass filter via the .value setter or the - automation methods linearRampToValueAtTime, exponentialValueAtTime, and - setValueAtTime. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The type of the BiquadFilterNode. Recorded each time the type is set. This - recorded once (to lowpass) when a biquad filter is created and also recorded - whenever the filter type changes due to user action or programatically. It - is unlikely the type will change more than once. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The duration in millisec of impulse responses for a ConvolverNode. Recorded - each time the impulse response is set for a ConvolverNode. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The order of the WebAudio IIRFilterNode. The order is one less than the - number of feedback coefficients used in the denominator of the IIRFilter - transfer function. Recorded each time an IIRFilter is constructed. - - - - - rtoy@chromium.org - hongchan@chromium.org - - The number of channels specified for the offline audio context. Recorded for - every offline context created. Probably only a few per page, but could be - potentially much more (thousands). - - - - - rtoy@chromium.org - hongchan@chromium.org - - The length (in frames) specified for the offline audio context. Recorded for - every offline context created. Probably only a few per page, but could be - potentially much more (thousands). - - - - - - Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher - supported sample rates. - - rtoy@chromium.org - hongchan@chromium.org - - The sample rate (in Hz) specified for the offline audio context. Recorded - for every offline context created. Probably only a few per page, but could - be potentially much more (thousands). - - - - - rtoy@chromium.org - hongchan@chromium.org - - The sample rate (in Hz) specified for the offline audio context. Recorded - for every offline context created. Probably only a few per page, but could - be potentially much more (thousands). - - - - - rtoy@chromium.org - hongchan@chromium.org - - The panning model for the PannerNode. Recorded once with the default value - at creation and once again whenver it is changed. Once changed, it is - unlikely to be changed again. If there are any PannerNodes created at all, - then there is probably one for each source (AudioBufferSourceNode, - OscillatorNode, or other source). - - - - - rtoy@chromium.org - hongchan@chromium.org - - Captures if WebAudio caused glitches or not due to the FIFO underflow. It is - recorded when PushPullFIFO is destroyed. (e.g. navigating away from the - page.) - - - - - rtoy@chromium.org - hongchan@chromium.org - - Percentage of FIFO underflow happened due to the the missed deadline of - WebAudio rendering engine. It is recorded when PushPullFIFO is destroyed. - (e.g. navigating away from the page.) - - - - - - Removed 2016-09. As of M55, this is no longer recorded. - - mlamouri@chromium.org - - Records whether WebAudio had a user gesture requirement and whether it was - fulfilled. - - - - - agl@chromium.org - - Tracks events related to prompting users for permission to pass WebAuthn - attestation information back to origins. "Queried" means that the - embedder was queried for a decision. (Since such decisions can be resolved - by enterprise policy, that doesn't imply that a user saw a permissions - prompt in every case.) Then one of four things can happen: a timeout, a - positive or negative resolution, or the request is abandoned. The latter - case occurs when, for example, the tab is closed or the user navigates away. - - - - - agl@chromium.org - martinkr@google.com - - Records events that occur during caBLE v1 authenticator discovery so that - potential discovery failures can be identified. - - - - - - Superseded 02/2020 by WebAuthentication.CableV1DiscoveryEvent - - agl@chromium.org - - Records events that occur during the lifetime of a caBLE v1 getAssertion - operation so that any causes of drop-off can be identified. - - - - - kenrb@chromium.org - martinkr@google.com - - When a relying party is attempting to authenticate a user using the - WebAuthentication API, this metric reports the number of valid credentials - that the RP has registered for the user. - - - - - kenrb@chromium.org - martinkr@google.com - - Records the transport used for all WebAuthentication GetAssertion requests - sent to authenticators. This does not necessarily mean that there was a - success response from any given authenticator. - - - - - kenrb@chromium.org - martinkr@google.com - - Records the transport used when an authenticator responds with success to a - WebAuthentication GetAssertion request. - - - - - kenrb@chromium.org - martinkr@google.com - - Record at startup whether the current system has a platform authenticator - available; i.e. whether IsUVPAA JS call would return true or false. - - - - - kenrb@chromium.org - martinkr@google.com - - When a relying party is attempting to register a credential for a new user - using the WebAuthentication API, this metric reports the number of existing - credentials already registered in order to prevent re-registration. - - - - - kenrb@chromium.org - martinkr@google.com - - Records the transport used for all WebAuthentication MakeCredential requests - sent to authenticators. This does not necessarily mean that there was a - success response from any given authenticator. - - - - - kenrb@chromium.org - martinkr@google.com - - Records the transport used when an authenticator responds with success to a - WebAuthentication MakeCredential request. - - - - - kenrb@chromium.org - martinkr@google.com - - Records failures associated with verifying the relying party origin when - that relying party is attempting to make a credential or get an assertion - using the WebAuthentication API. Failures include when the relying party's - origin is opaque or non-secure, or when the caller-provided relying party ID - or app ID is not valid for this origin. - - - - - agl@chromium.org - - Tracks events related to prompting users for permission to pass U2F - attestation information back to origins. "Queried" means that the - embedder was queried for a decision. (Since such decisions can be resolved - by enterprise policy, that doesn't imply that a user saw a permissions - prompt in every case.) Then either a positive or negative result can happen. - However, note some complications: a negative will be recorded when the tab - is closed or the user navigates away, and a positive result will be recorded - when the user accepts the permission prompt but the request has already - timed out. - - - - - ajuma@chromium.org - gambard@chromium.org - - [iOS] Counts the number of time the backForwardList of the WebView gets out - of sync with the URL exposed by the WebView. This should not happen and is - probably an issue in WebKit. This is only recorded when there is an error. - - - - - ajuma@chromium.org - gambard@chromium.org - - [iOS] Records the action take when the backForwardList of the WebView is out - of sync with the URL exposed by the WebView when starting a new provisional - navigation. The URLs can get out of sync because of a bugs in WebKit. This - is only recorded when the URLs are out of sync. - - - - - eugenebut@chromium.org - gambard@chromium.org - - [iOS] Report cache hit/miss for WKWebView cert verification. - CRWWKNavigationHandler has a cache of pending cert verification results to - avoid extra verifications when presenting SSL interstitial. This metric - helps to understand how often this cache miss happens. - - - - - - Removed on 07/2019. - - eugenebut@chromium.org - - [iOS] Chrome for iOS crashes because NavigationManager does not have any - navigation items and visible navigation item is dereferenced - (crbug.com/565457). The assumption is that crash occurs if pending load was - stopped for a child window. This metric will prove or disprove that - assumption. - - - - - mrefaat@chromium.org - - [iOS] Measures the proportion of external URL requests that originate from a - subframe without any user interaction (e.g. an advertisement contains an - iframe directed at the App Store). - - - - - - Removed 2017-02. This metric disproved the assumption mentioned in the - summary and it is no longer needed. - - eugenebut@chromium.org - - Chrome for iOS crashes in |didCommitNavigation:| if Navigation Manager is - empty. It's unclear how the app can get into this state and one assumption - is that didStartProvisionalNavigation: does not add a pending navigation. - This metric is logged when didStartProvisionalNavigation: fails to add a - pending item. - - - - - - It is common for WKWebView to have certificateChain, which does not allow - constructing net::X509Certificate. Logging was removed on 2020-01-23. - - eugenebut@google.com - - Whether or not WKWebView has provided a valid -certificateChain when loaded - a page over a secure connection. - - - - - - This has been superseded by Blink.UseCounter.CSSProperties which does not - count multiple times per page load. See https://crbug.com/458925. - - ajuma@chromium.org - - Counts the number of times each CSS property is animated. There is no limit - on the number of times each property is counted per page view -- a property - that is animated multiple times during a single page view is counted each - time it animates. - - - - - - Removed 10/2018 with Blink.Canvas.IsComposited, - Blink.Canvas.ResourceProviderIsAccelerated, - Blink.Canvas.ResourceProviderType and Blink.Canvas.2DLayerBridgeIsDeferred - - zmin@chromium.org - fserb@chromium.org - - The usage of Canvas 2D Context API. Logged when the particular API is used. - - - - - wychen@chromium.org - gilmanmh@google.com - - The time spent on collecting the statistics of the document in the main - frame. These statistics would be used as features to classify whether the - page is suitable for DOM distiller. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. - - - - - yoichio@chromium.org - - Counts the number of times each document.execCommand is executed. This - doesn't count commands not supported by Blink. - - - - - yoichio@chromium.org - - Counts the number of times each Editor::Command::execute is called. This - doesn't count commands not supported by Blink. - - - - - - As of M57 this has been superseded by Blink.UseCounter.Features which fixes - a number of issues. See https://crbug.com/676837. - - rbyers@chromium.org - - Count of how many page loads use various features. The PageVisits bucket is - incremented for each page load, and the other buckets incremented at most - once per PageVisit via the WebCore::UseCounter class. - - - - - - As of M57 this has been superseded by Blink.UseCounter.CSSProperties which - fixes a number of issues. See https://crbug.com/676837. - - mikelawther@chromium.org - - Records usage of CSS properties used on a page, either statically or - dynamically, from the time the page is initialised to when it is closed or - navigated away from. Each property is counted at most once per page per - view. - - - - - rakina@chromium.org - altimin@chromium.org - - Records the number of find-in-page tasks executed for a find-in-page - request. Emitted when a find-in-page request is finished (it went through - the whole document) or when it got aborted. - - - - - rakina@chromium.org - altimin@chromium.org - - Records how long one find-in-page request (consisting multiple tasks) took - from the request start until the last find-in-page task for the request - finished. Emitted when a find-in-page request is finished (it went through - the whole document) or when it got aborted. - - - - - - Removed in M77 because we're not tracking this anymore. - - rakina@chromium.org - altimin@chromium.org - - Records how much time it takes for find-in-page scoping over the idle task - deadline. - - - - - rakina@chromium.org - altimin@chromium.org - - Records how long one find-in-page task took from invocation start to end. - Emitted when a find-in-page task finished running. - - - - - rakina@chromium.org - altimin@chromium.org - - Records the total task duration of all of the find-in-page tasks for one - find-in-page request. Nothe that this does not include the time spent in - between tasks. Emitted when a find-in-page request is finished (it went - through the whole document) or when it got aborted. - - - - - - Removed in September 2018 for a version that also tracks if the frame is an - ad frame. - - japhet@chromium.org - - Records instances of child frames navigating the top frame. Includes whether - or not the navigation would have been permitted if not for our special case - for 'framebusting', the practice of ensuring a given document is never - displayed in a frame. - - - - - csharrison@chromium.org - japhet@chromium.org - - The position of the URL in the framebust UI list (desktop only) when it is - clicked. Note that this UI surface is shared with the tab-under - intervention, so elements in the list could come from either features. This - metric will only be logged when a URL from the framebust (3p redirect) - intervention is clicked. - - - - - csharrison@chromium.org - japhet@chromium.org - - The (android only) outcome of a particular framebust infobar. Recorded when - the user either closes the infobar or declines the intervention by clicking - the link. - - - - - - Removed in March 2019. - - japhet@chromium.org - jkarlin@chromium.org - - Records instances of child frames navigating the top frame. Includes whether - or not the navigation would have been permitted if not for our special case - for 'framebusting', the practice of ensuring a given document is never - displayed in a frame. It also includes whether the frame that initiated the - navigation was an ad frame or not. - - - - - yoavweiss@chromium.org - csharrison@chromium.org - - Time in which non-AppCache requests have been delayed after being discovered - by the HTMLPreloadScanner, due to document element not being yet available, - which is required for AppCache support. Recorded per document. - - - - - yoavweiss@chromium.org - csharrison@chromium.org - - Time in which non-AppCache requests have been delayed after being discovered - by the HTMLPreloadScanner, due to document element not being yet available, - which is required for AppCache support. Recorded per document, but applies - only to main frames. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records actions that take place in IndexedDB. These stats are used for - normalization in formulas. See go/chrome-indexeddb-heartbeat - - - - - dmurph@chromium.org - pwnall@chromium.org - - Methods that encountered consistency errors. Such errors probably point to a - bug in our code. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the result of trying to delete an IndexedDB database, per the user - using the IDBFactory::DeleteDatabase API. - - - - - - As of chrome 26, use {Consistency, Read, Write}Error instead. - - dgrogan@chromium.org - - Count of internal IndexedDB errors (data corruption, I/O errors, etc) - encountered. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the result of the FIRST attempt at opening the backing store for - IndexedDB (i.e. retries are ignored). This is recorded when an API call - needs to open the backing store (if it isn't already opened). API calls that - can open the backing store are: IDBFactory::Open, GetDatabaseNames, - GetDatabaseInfo, and DeleteDatabase. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the time that it takes to open IndexedDB's backing store. This is - only recorded if the backing store was opened successfully on the first - attempt. - - - - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Count of the different success and failure modes when opening an IndexedDB - backing store - clean open, successful open with recovery, failed recovery, - etc. Includes all hosts. - - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Count of the different success and failure modes when opening an IndexedDB - backing store - clean open, successful open with recovery, failed recovery, - etc. Only for docs.google.com. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Length of leveldb directories that cause paths to not fit in the filesystem, - either because the individual component is too long or the overall path is - larger than MAX_PATH. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Methods that encountered leveldb errors while trying to read from disk. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Methods that encountered leveldb errors while trying to write to disk. - - - - - cmumford@chromium.org - The reason that a forced-close of a backing store occurred. - - - - dmurph@chromium.org - pwnall@chromium.org - - Number of outstanding transactions (running, blocked) in database when a new - transaction is created. - - - - - cmumford@chromium.org - - Count of the results when attempting to destroy a corrupt Indexed DB backing - store. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Recorded when there is an error during the force close of IndexedDB for an - origin. A force close can be triggered either from DevTools, or when there - is a disk error. Errors during force close are ignored, as the system is - already being torn down. This metric is the only record of these errors - happening. - - - - - - Removed as of July 2018. - - dgrogan@chromium.org - - Count total number of front end API calls of IndexedDB methods. - - - - - cmumford@chromium.org - - The time that it takes to close IndexedDB's LevelDB backing store. - - - - - - Removed 1/19. Metric never actually worked, as -1 / 1024 yields 0. - - dgrogan@chromium.org - - Count of how many times LevelDBDatabase got an error trying to check free - disk space. - - - - - - Removed 1/19. Use Quota.AvailableDiskSpace instead. - - dgrogan@chromium.org - - Amount of free disk space on the partition/volume/etc where LevelDB failed - to open. - - - - - - Removed 1/19. Use Quota.AvailableDiskSpace instead. - - dgrogan@chromium.org - - Amount of free disk space on the partition/volume/etc where LevelDB was - successfully opened. - - - - - cmumford@chromium.org - - The time that it takes to open IndexedDB's LevelDB backing store. - - - - - - Removed in M84. - - cmumford@chromium.org - chrome-owp-storage@google.com - - The time that it takes to write the data IndexedDB to the LevelDB backing - store for a put operation. - - - - - - Removed in M72. - - cmumford@chromium.org - - The time that it takes to commit an IndexedDB transaction to its LevelDB - backing store. - - - - - cmumford@chromium.org - - The time that it takes to write data to an IndexedDB's LevelDB backing - store. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Error classes returned by LevelDB when it failed to open a database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Errors (base::File::Error) encountered by a single LevelDBEnv method when - opening an IndexedDB instance. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Types of corruption that LevelDB encounters when opening a database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - LevelDBEnv methods that generated IO errors when opening a database. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE. - - dgrogan@chromium.org - - Errno errors encountered by a single LevelDBEnv method when opening an - IndexedDB instance. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE. - - dgrogan@chromium.org - - PlatformFileErrors encountered by a single LevelDBEnv method when opening an - IndexedDB instance. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Error classes returned by LevelDB when it failed to read a database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Errors (base::File::Error) encountered by a single LevelDBEnv method when - reading from an IndexedDB instance. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Types of corruption that LevelDB encounters when reading a database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - LevelDBEnv methods that generated IO errors when reading a database. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE. - - dgrogan@chromium.org - - Errno errors encountered by a single LevelDBEnv method when reading an - IndexedDB instance. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE. - - dgrogan@chromium.org - - PlatformFileErrors encountered by a single LevelDBEnv method when opening an - IndexedDB instance. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Error classes returned by LevelDB when it failed to write to a database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Errors (base::File::Error) encountered by a single LevelDBEnv method when - writing to an IndexedDB instance. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Types of corruption returned by LevelDB when it failed to write to a - database. - - - - - dmurph@chromium.org - pwnall@chromium.org - - LevelDBEnv methods that generated IO errors when writing to a database. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE. - - dgrogan@chromium.org - - Errno errors encountered by a single LevelDBEnv method when writing to an - IndexedDB instance. - - - - - - Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE. - - dgrogan@chromium.org - - PlatformFileErrors encountered by a single LevelDBEnv method when writing to - an IndexedDB instance. - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - The type of key (number, string, etc.) used for an index entry for a record - being newly stored or updated in an Indexed DB object store. For array keys, - the types of sub-keys are not recorded. - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - The type of key (number, string, etc.) used for a record being newly stored - or updated in an Indexed DB object store. For array keys, the types of - sub-keys are not recorded. - - - - - - Removed 2018-11. No longer needed. - - cmumford@chromium.org - - The delay between the receipt of the request to open an IndexedDB database - and the firing of the blocked event. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the full time it takes to open a database that isn't open yet (so - files are loaded from disk, metadata checked, etc). The measurement happens - when a website calls "indexedDB.open", and records the time it - takes from when this method is called to when the onsuccess event (or - onupgradeneeded event, in the case of a database upgrade) is dispatched. See - WebCore.IndexedDB.OpenTime.Warm for the time it takes an already-loaded - database to load. - - - - - - Removed 2018-11. No longer needed. - - cmumford@chromium.org - - The delay between the receipt of the request to open an IndexedDB database - and the firing of the error event. - - - - - - Removed 2018-11. No longer needed. - - cmumford@chromium.org - - The delay between the receipt of the request to open an IndexedDB database - and the firing of the success event. - - - - - - Removed 2018-11. No longer needed. - - cmumford@chromium.org - - The delay between the receipt of the request to open an IndexedDB database - and the firing of the upgradeneeded event. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the full time it takes to open an already-open database. The - measurement happens when a website calls "indexedDB.open", and - records the time it takes from when this method is called to when the - onsuccess event (or onupgradeneeded event, in the case of a database - upgrade) is dispatched. See WebCore.IndexedDB.OpenTime.Cold for the time it - takes to open a database that is not open yet. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The number of blobs being saved in an IndexedDB object store 'put' - operation. Recorded for every 'put' operation. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The total size of the blobs being saved in an IndexedDB object store 'put' - operation. Recorded for every 'put' operation, except when there are no - attached blobs or a blob has an unknown size. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The size of the IndexedDB key used in an IndexedDB object store 'put' - operation. Recorded for every 'put' operation. - - - - - - Replaced with WebCore.IndexedDB.PutValueSize2 on 6/2017 - - dmurph@chromium.org - - The size of the IndexedDB value used in an IndexedDB object store 'put' - operation. Recorded for every 'put' operation. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The size of the IndexedDB value used in an IndexedDB object store 'put' - operation. Recorded for every 'put' operation. - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - Records the 'keyPath' type (none, string, or array) during IDBObjectStore's - createIndex operation. See http://www.w3.org/TR/IndexedDB/ - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - Records the 'multiEntry' flag value during IDBObjectStore's createIndex - operation. See http://www.w3.org/TR/IndexedDB/ - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - Records the 'unique' flag value during IDBObjectStore's createIndex - operation. See http://www.w3.org/TR/IndexedDB/ - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - Records the 'autoIncrement' flag value during IDBDatabase's - createObjectStore operation. See http://www.w3.org/TR/IndexedDB/ - - - - - - Removed August 2019. Was added to measure use of features which not all - actively developed browser engines supported. No longer relevant. - - jsbell@chromium.org - - Records the 'keyPath' type (none, string, or array) during IDBDatabase's - createObjectStore operation. See http://www.w3.org/TR/IndexedDB/ - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records if a v2 schema has blob keys in the database, which means the - database is corrupt. These databases will eventually be wiped as corrupt. - Recorded when the IndexedDB backing store for an origin is first opened, - which happens when a IndexedDB database connection is opened or when - database names are fetched. Note: The backing store stays alive for - subsequent connections, and sticks around for a couple seconds after the - last connection is closed. See WebCore.IndexedDB.SchemaV2HasBlobs.Docs for - the Docs-only version. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records if a v2 schema has blob keys in the database, which means the - database is corrupt. These databases will eventually be wiped as corrupt. - Recorded when the IndexedDB backing store for an origin is first opened, - which happens when a IndexedDB database connection is opened or when - database names are fetched. Note: The backing store stays alive for - subsequent connections, and sticks around for a couple seconds after the - last connection is closed. Only for docs.google.com. Note that these samples - will also be recorded in WebCore.IndexedDB.SchemaV2HasBlobs. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the schema version of the IndexedDB database read from disk. - Recorded when the IndexedDB backing store for an origin is first opened, - which happens when a IndexedDB database connection is opened or when - database names are fetched. Note: The backing store stays alive for - subsequent connections, and sticks around for a couple seconds after the - last connection is closed. See WebCore.IndexedDB.SchemaVersion.Docs for the - Docs-only version. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the schema version of the IndexedDB database read from disk. - Recorded when the IndexedDB backing store for an origin is first opened, - which happens when a IndexedDB database connection is opened or when - database names are fetched. Note: The backing store stays alive for - subsequent connections, and sticks around for a couple seconds after the - last connection is closed. Only for docs.google.com. Note that these samples - will also be recorded in WebCore.IndexedDB.SchemaVersion. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the total size of tombstones deleted by the IndexedDB Tombstone - Sweeper. Recorded on the browser side (back end) when the sweeper has - completed scanning and it is in the 'deletion' mode. See - https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the time it takes for the IndexedDB Tombstone Sweeper to commit - tombstone deletions. Recorded on the browser side (back end) when the - sweeper has completed a round of sweeping and, it's in 'deletion' mode, and - it has tombstones to delete. See https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the time it takes for the IndexedDB Tombstone Sweeper to fully sweep - the indexes. Recorded on the browser side (back end) when the sweeper has - completed sweeping all indexes (so partial sweeps are not recorded) and it - is in 'deletion' mode. See https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records when an error occurs during deletion of index tombstones by the - IndexedDB Tombstone Sweeper. Recorded on the browser side (back end) when - the sweeper has completed a round of sweeping and, it's in 'deletion' mode, - and it has tombstones to delete. See https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper - has completed scanning. Records the percentage of the indexes the scanner - fully scanned before it was stopped. To reduce the number of buckets, the - recorded value is the percentage divided by 5. See https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Records the number of tombstones deleted by the IndexedDB Tombstone Sweeper. - Recorded on the browser side (back end) when the sweeper has completed - scanning and it is in 'deletion' mode. See https://goo.gl/coKwA7. - - - - - - Replaced with WebCore.IndexedDB.TombstoneSweeper.NumDeletedTombstones in - 07/2017. - - dmurph@chromium.org - - Records the number of tombstones encountered by the IndexedDB Tombstone - Sweeper. Recorded on the browser side (back end) when the sweeper has - completed scanning and it is in 'statistics' mode. See - https://goo.gl/coKwA7. - - - - - - Replaced with WebCore.IndexedDB.TombstoneSweeper.DeletionTotalTime.Complete - in 07/2017. - - dmurph@chromium.org - - Records the time it takes for the IndexedDB Tombstone Sweeper to fully scan - the indexes. Recorded on the browser side (back end) when the sweeper has - completed scanning all indexes (so partial scans are not recorded) and it is - in 'statistics' mode. See https://goo.gl/coKwA7. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper - encounters an error while sweeping. See https://goo.gl/coKwA7. - - - - - - Replaced with WebCore.IndexedDB.TombstoneSweeper.DeletedTombstonesSize in - 07/2017. - - dmurph@chromium.org - - Records the total size of tombstones encountered by the IndexedDB Tombstone - Sweeper. Recorded on the browser side (back end) when the sweeper has - completed scanning and it is in the 'statistics' mode. See - https://goo.gl/coKwA7. - - - - - - Replaced with WebCore.IndexedDB.Transaction.ReadOnly.SizeOnCommit2 on 6/2017 - - dmurph@chromium.org - - The total temporary size of an IndexedDB ReadOnly Transaction. Since this is - a readonly transaction, the size should only be >0 when the transaction - is removing tombstone index keys. Recorded on transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The total temporary size of an IndexedDB ReadOnly Transaction. Since this is - a readonly transaction, the size should only be >0 when the transaction - is removing tombstone index keys. Recorded on transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The time it takes for an IndexedDB ReadOnly Transaction to commit, starting - from when it starts executing tasks (when it is scheduled). Recorded on - transaction commit. - - - - - - Replaced with WebCore.IndexedDB.Transaction.ReadWrite.SizeOnCommit2 on - 6/2017 - - dmurph@chromium.org - - The total temporary size of an IndexedDB ReadWrite Transaction. This is the - memory that is temporarily stored before writing to disk. Recorded on - transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The total temporary size of an IndexedDB ReadWrite Transaction. This is the - memory that is temporarily stored before writing to disk. Recorded on - transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The time it takes for an IndexedDB ReadWrite Transaction to commit, starting - from when it starts executing tasks (when it is scheduled). Recorded on - transaction commit. - - - - - - Replaced with WebCore.IndexedDB.Transaction.VersionChange.SizeOnCommit2 on - 6/2017 - - dmurph@chromium.org - - The total temporary size of an IndexedDB VersionChange Transaction. This is - the memory that is temporarily stored before writing to disk. Version change - transactions happen when creating a database or updating a current database - schema. Recorded on transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The total temporary size of an IndexedDB VersionChange Transaction. This is - the memory that is temporarily stored before writing to disk. Version change - transactions happen when creating a database or updating a current database - schema. Recorded on transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - The time it takes for an IndexedDB VersionChange Transaction to commit, - starting from when it starts executing tasks (when it is scheduled). Version - change transactions happen when creating a database or updating a current - database schema. Recorded on transaction commit. - - - - - dmurph@chromium.org - pwnall@chromium.org - - Recorded on the browser side (back end) when an IndexedDB transaction is - aborted, specifically recording the reason for the abort. This can be - triggered by javascript code on the renderer, errors or force closes on the - backend, or by the transaction timeout timer. - - - - - - Removed, preloads are issued on the main thread now, so this is less useful. - - csharrison@chromium.org - - The delay between when the preload scanner discovers a resource on the - parser thread and when the preload request is issued on the main thread. - - - - - clamy@chromium.org - - The resulting action (e.g. load resource, use resource from in-memory - cache...) upon a resource request. - - - - - - Removed April 2017. - - clamy@chromium.org - - Number of dead resources found in the memory cache over the lifetime of the - ResourceFetcher. - - - - - - Removed April 2017. - - clamy@chromium.org - - Number of resources that needed to be loaded by the ResourceFetcher over its - lifetime. - - - - - clamy@chromium.org - - Whether the resource in the cache is being used by at least one client (live - resource) or not (dead resource) upon a cache hit. - - - - - - This metric has been not recorded at least since 2016/01. The displayed enum - labels might be unreliable because C++ enum values of blink::Resource::Type - have been changed over time. - - clamy@chromium.org - - The type of the resource (e.g. image, script...) upon a cache hit. - - - - - - Removed April 2017. - - clamy@chromium.org - - Number of dead resources that needed to be revalidated by the - ResourceFetcher over its lifetime. - - - - - - Removed November 2017. - - rmcilroy@chromium.org - - The amount of time allotted to a requestIdleCallback callback, i.e., the - difference between the time when it is called and when its deadline expires. - - - - - - Removed December 2017. - - rmcilroy@chromium.org - - The amount of time by which a requestIdleCallback callback overran its - deadline. Callbacks which don't overrun their deadline will report an - overrun of 0. - - - - - - Removed April 2020. - - shaseley@chromium.org - The callback type for every idle task that was run. - - - - - Removed April 2020. - - shaseley@chromium.org - - The amount of time an idle task was queued before running. This metric is - only recorded for idle tasks that run during idle periods, not for those - that run as a result of an expired timeout. - - - - - - Removed April 2020. - - shaseley@chromium.org - - The timeout value specified for each idle task that was run, regardless of - whether or not it was run due to its timeout expiring. A value of 0 - indicates that no timeout was specified. - - - - - - Removed April 2020. - - shaseley@chromium.org - - The timeout value for idle tasks that were run because their timeout - expired. - - - - - leszeks@chromium.org - v8-runtime@google.com - Reason for not streaming an async script. - - - - leszeks@chromium.org - v8-runtime@google.com - Whether an async script was streamed or not. - - - - leszeks@chromium.org - v8-runtime@google.com - Reason for not streaming a deferred script. - - - - leszeks@chromium.org - v8-runtime@google.com - Whether a deferred script was streamed or not. - - - - leszeks@chromium.org - v8-runtime@google.com - - Reason for not streaming an other (not async, deferred or parser blocking) - script. - - - - - leszeks@chromium.org - v8-runtime@google.com - - Whether an other (not async, deferred or parser blocking) script was - streamed or not. - - - - - - Removed as this data was needed for streaming investigations, no longer - needed. - - marja@chromium.org - - Whether a parsing blocking script was already preloaded from the net or the - cache by the time it was needed. - - - - - leszeks@chromium.org - v8-runtime@google.com - Reason for not streaming a parsing blocking script. - - - - leszeks@chromium.org - v8-runtime@google.com - Whether a parsing blocking script was streamed or not. - - - - - Removed as this data was needed for streaming investigations, no longer - needed. - - marja@chromium.org - - Time between the events "script is loaded" and "script is - compiled" for parsing blocking scripts. - - - - - - Removed in M85 as we haven't observed any related performance alerts, and no - team is actively monitoring it. - - xiaochengh@chromium.org - - The amount of time between consecutive spellcheck requests made by Blink, - with the exception that requests made simultaneously checking different - parts of the same editing host count as only one request. - - - - - - Temporary histogram replaced by Blink.UseCounter.CSSProperties. - - rbyers@chromium.org - - - - - Temporary histogram replaced by Blink.UseCounter.Features. - - rbyers@chromium.org - - - - - Temporary histogram replaced by Blink.UseCounter.SVGImage.CSSProperties. - - rbyers@chromium.org - - - - - Temporary histogram replaced by Blink.UseCounter.SVGImage.Features. - - rbyers@chromium.org - - - - - Removed 05/2013, we no longer have the code that uses this metric. - - Please list the metric's owners. Add more owner tags as needed. - - Duration of time taken to create a V8 Context for an isolated world. - - - - - - Removed 05/2013, we no longer have the code that uses this metric. - - Please list the metric's owners. Add more owner tags as needed. - - Duration of time taken to create a V8 Context for the main world. - - - - - - Deprecate 2017-06, as we've collected enough data to discuss. (see issue - 584616). - - yhirano@chromium.org - ricea@chromium.org - - Count the number of changes to WebSocket.binaryType after the connection - opened, per connection. Assignments that match the existing binaryType are - not counted. This is recorded after WebSocket close, whether explicit or due - to error or navigation. It is not recorded if the render process is - destroyed before the WebSocket is closed. - - - - - - Removed 2014-06 when we replaced the WebSocket implementation (see issue - 226931). - - yhirano@chromium.org - ricea@chromium.org - - Count the number of WebSocket handshake for each result. Use this histogram - as a baseline for investigating feature usage counters. - - - - - - Removed as of 2020-09 - - yhirano@chromium.org - ricea@chromium.org - - The sizes of binary WebSocket messages received, broken down by type. One - entry per message. Clamped to 100 MB. - - - - - - Removed as of 2020-09 - - yhirano@chromium.org - ricea@chromium.org - - The sizes of binary WebSocket messages sent, broken down by type. One entry - per message. Clamped to 100 MB. - - - - - - Removed 2014-06 when we replaced the WebSocket implementation (see issue - 226931). - - yhirano@chromium.org - ricea@chromium.org - - Count the number of WebSockets that accepted permessage-deflate extension - for each context take over mode. Used by the old Blink-based WebSocket - implementation. - - - - - - Removed as of 2020-02. - - yhirano@chromium.org - ricea@chromium.org - - Count the number of messages for each message type and set binary type. - - - - - yhirano@chromium.org - ricea@chromium.org - - Count the number of send() method calls on WebSockets for each argument - type. - - - - - - Removed as of 7/2014. This histogram was used to determine when it would be - ok to remove the deprecated XMLHttpRequest.send(ArrayBuffer) overload. The - support for ArrayBuffer was un-deprecated in the WHATWG spec for XHR, and - subsequently un-deprecated in Blink. - - costan@gmail.com - - Count the number of XHR.send() calls for each argument type to see when we - can deprecate the ArrayBuffer type support. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - A histogram tracking the time we spent showing blank text because a web font - wasn't available by the time we needed it. Measured once per @font-face that - ended up showing blank text. - - - - - hajimehoshi@chromium.org - kenjibaheux@chromium.org - kouhei@chromium.org - ksakamoto@chromium.org - - Recorded upon web fonts load. Counts the number of times web font is loaded - from cache (disk cache or memory cache), fetched over network, or served - from data URL. - - - - - kenjibaheux@chromium.org - xiaochengh@chromium.org - - The number of 'font-display: auto' web fonts whose display periods are - modified to 'swap' or 'failure' before a timeout to ensure a good LCP. This - is a diagnostic metric for feature AlignFontDisplayAutoTimeoutWithLCPGoal. - - - - - - Removed June 2019. - - bashi@chromium.org - kenjibaheux@chromium.org - The success or failure of web fonts CORS-enabled fetching. - - - - - Removed Jan 2020. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - Uncompressed font image size divided by the duration of time OTS takes to - decode the font image, in kilobytes per second. - - - - - - Removed 08/2019. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - Recorded upon an eviction of a cache entry for a font in Google Fonts. - Records the age of the cache entry. - - - - - - Removed 08/2019. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - Recorded upon a cache hit for a font in Google Fonts. Records the age of the - cache entry. - - - - - - Removed 08/2019. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - When a cache entry for a font in Google Fonts is evicted, records the reuse - count of the cache entry. - - - - - - Removed 08/2019. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - Recorded upon a cache hit for a font in Google Fonts. Records the reuse - count of the cache entry. - - - - - - Removed 08/2019 in favor of WebFont.HttpCacheStatus. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - Whether the font was in the cache or not. "Previously in the - cache" means there was an evicted entry for the font in the cache. - Recorded upon a disk cache query for a font in Google Fonts. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of under - 10KB. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 10KB-50KB. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 50KB-100KB. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 100KB-1MB. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of over - 1MB. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time taken for a webfont download that failed. Includes aborted - requests. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The value of font-display @font-face descriptor. Counted only when - explicitly specified in the @font-face rule. - - - - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - This metrics is logged when a page that use web fonts is loaded. The value - is whether we had to wait on at least one web font and ended up showing - blank text, or not. - - - - - yaoxia@chromium.org - shivanisha@chromium.org - - For each http cache transaction for a font in Google Fonts, record the cache - status. - - - - - - Removed 10/2017. Related field trial has finished rolling out. - - toyoshim@chromium.org - kenjibaheux@chromium.org - - For each WebFont load attempt, records whether User Agent Intervention was - triggered, and whether the request (would have) timed out or not. The - intervention takes adaptive behaviors to handle loading timeouts to improve - user experiences on slow networks. - - - - - - Removed 10/2017. Related field trial has finished rolling out. - - toyoshim@chromium.org - kenjibaheux@chromium.org - - Like InterventionResult, this records whether User Agent Intervention was - triggered, and whether the request (would have) timed out or not. But this - version records only when data actually comes from network, not from disk or - memory cache, and is not provided in a data URL format. - - - - - - Renamed to WebFont.StyleRecalcToDownloadLatency for clarity. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time from when the webfont was referenced by a calculated style for the - first time to the start of the font download. - - - - - ksakamoto@chromium.org - toyoshim@chromium.org - - The load limit state when the first disk-cache-only request fails by cache - miss, if WebFonts cache-aware timeout adaptation is enabled and applicable. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.0.Under10KB. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of under - 10KB. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.1.10KBTo50KB. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 10KB-50KB. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.2.50KBTo100KB. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 50KB-100KB. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.3.100KBTo1MB. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of - 100KB-1MB. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.4.Over1MB. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time it takes for a webfont download to finish, for webfonts of over - 1MB. - - - - - - Removed as of 8/2013, replaced by WebFont.DownloadTime.LoadError. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time taken for a webfont download that failed. Includes aborted - requests. - - - - - hajimehoshi@chromium.org - kenjibaheux@chromium.org - kouhei@chromium.org - ksakamoto@chromium.org - - Whether a locallly installed font is actually used when @font-face had local - sources. - - - - - - Removed Jan 2020. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The packaging format of the font file (e.g. SFNT, WOFF ...) upon a webfont - load. - - - - - - Removed 11/2013. No longer tracked. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time from when the webfont was referenced by a calculated style for the - first time to the start of the font download. Recorded at most once for each - FontResource object (not recorded if the font is retrieved from the memory - cache). - - - - - - Removed 11/2013. No longer tracked. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - For each webfont, this records (a) if the font was 'styled', i.e. referenced - by a calculated style for a RenderText before the font data was used, and - (b) if the font was actually used or not, i.e. the renderer requested the - font data or not. (A Font can be used without being styled, for example when - drawn by a Canvas 2D Context.) This is recorded upon a download request of a - webfont, or destruction of a FontResource object. Recorded at most once for - each FontResource object in the renderer's memory cahce. - - - - - - Removed as of 9/2013, replaced by - WebFont.Resource.StyleRecalcToDownloadLatency. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The time from when the webfont was referenced by a calculated style for the - first time to the start of the font download. - - - - - - Removed as of 9/2013, replaced by WebFont.Resource.UsageType. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - For each webfont, this records (a) if the font was 'styled', i.e. referenced - by a calculated style for a RenderText before the font data was used, and - (b) if the font was actually used or not, i.e. the renderer requested the - font data or not. (A Font can be used without being styled, for example when - drawn by a Canvas 2D Context.) This is recorded upon a download request of a - webfont, or destruction of a CSSFontFaceSource object. Recorded at most once - for each url() source of @font-face CSS rule. - - - - - - Removed June 2019. - - kenjibaheux@chromium.org - ksakamoto@chromium.org - - The number of webfonts used in a page. This is recorded when the first - layout is done, and so will not count webfonts dynamically loaded by - scripts. - - - - - zea@chromium.org - - Percentage of results that are present locally but are not returned by the - web history API call. Recorded every time a signed-in user visits the - chrome://history page and the results from the web history are received. - - - - - zea@chromium.org - - Whether getting the OAuth token was successful for a web history query. On - visits to the chrome://history page this token is obtained and then used to - get the user's synced web history. - - - - - zea@chromium.org - - HTTP Response code returned by the server when trying to fetch the OAuth - token for a web history query. - - - - - zea@chromium.org - - Whether the web history API call was successful. Every time a signed-in user - visits the chrome://history page this query is executed to get the user's - synced web history. If successful, the local and remote results are merged - and shown in the history page. - - - - - - Removed March 2020. - - msalama@chromium.org - chrome-signin-team@google.com - - Records the state of web and app activity everytime a request to query sWAA - is completed. The request is triggered when the user opens the history page, - sync setup settings page or clear browsing data dialog. Desktop only. - - - - - zea@chromium.org - - Time it took for the web history to reply. Recorded when the web history API - call triggered by visiting chrome://history receives the data, measuring how - much time it took for the server to reply. - - - - - droger@chromium.org - - Histogram for the format of decoded WebP images on iOS, as Chrome re-encodes - WebP images on that platform. - - - - - - Removed 5/2019 in issue bugs.webrtc.org/10563 due to the reporting component - (AEC2) being deprecated. - - hlundin@chromium.org - - Captures if the estimated delay between rendered and captured audio is out - of bounds which can cause the Echo Cancellation to fail. This is logged - roughly once every 5 seconds. The values are logged in four buckets - reflecting how well the Echo Cancellation likely performs based on the - estimated delay. - - - - - grunell@chromium.org - minyue@chromium.org - - The percentage of measurement periods during a capture stream's lifetime - when the echo canceler's filter is considered to have diverged at least - once. A diverged filter could mean that there was echo och ducking - experienced. The measurement period size is fixed and in the order of one - second. The first measurement period is larger, typically 2-3 seconds. - Capture streams with shorter lifetimes (i.e. no data available) are not - recorded here. - - - - - - Removed as of 12/2014, replaced by - WebRTC.ApplicationMaxConsecutiveBytesDiscard.v2. - - guoweis@chromium.org - - The maximum consecutive discarded bytes caused by not enough buffer - available in WebRTC's socket implementation. This happens when WebRTC - IpcPacketSocket's throttling mechanism kicks in. - - - - - guoweis@chromium.org - - The maximum consecutive discarded bytes caused by not enough buffer - available in WebRTC's socket implementation. This happens when WebRTC - IpcPacketSocket's throttling mechanism kicks in. The maximum bucket is - expanded from previous version to provide more insight when upper layer - feeds a lot of packets. - - - - - guoweis@chromium.org - - The percentage of packets discarded by WebRTC's socket layer due to - EWOULDBLOCKs when WebRTC IpcPacketSocket's throttling mechanism kicks in. - - - - - - Removed 4/2019 in issue bugs.webrtc.org/10563 due to the reporting component - (AEC2) being deprecated. - - hlundin@chromium.org - - The AEC in WebRTC will sometimes realign the far- and near-end signal - buffers to keep in sync with delay changes in the echo path. This metric - logs each such realignment, storing the delay change in ms, when the change - is triggered by a shift in the signal based delay estimation (a.k.a - delay-agnostic). - - - - - - Removed 4/2019 in issue bugs.webrtc.org/10563 due to the reporting component - (AEC2) being deprecated. - - hlundin@chromium.org - - The AEC in WebRTC will sometimes realign the far- and near-end signal - buffers to keep in sync with delay changes in the echo path. This metric - logs each such realignment, storing the delay change in ms, when the change - is triggered by a shift in system reported delay. - - - - - - Removed 11/2019 due to old AEC system (AEC2) being removed. - - hlundin@chromium.org - - The AEC in WebRTC keeps a buffer to mimic the audio buffers in the lower - layers. This histogram logs a sudden positive jump in buffer size. Since we - detect jumps in the capture thread, only positive values are feasible. Note - that the difference in milliseconds is logged and not the actual AEC system - delay value. Sampled every time the AEC system delay changes more than 50 - milliseconds. - - - - - aleloi@chromium.org - - Logs adaptive digital compression gain that is applied by AgcManagerDirect. - A log call is made once per second. The compression gain is applied to the - microphone signal at the end of the processing chain. - - - - - aleloi@chromium.org - - Logs adaptive digital compression gain that is applied by AgcManagerDirect. - A log call is made every time the gain changes. The compression gain is - applied to the microphone signal at the end of the processing chain. - - - - - aleloi@chromium.org - - Logs adaptive digital compression gain that is applied by - AdaptiveDigitalGainApplier in GainController2. A log call is made once per - second. The compression gain is applied to the microphone signal at the end - of the processing chain. - - - - - aleloi@chromium.org - - This histogram reports the noise level estimation done in GainController2. A - value is reported every second. The unit is inverted dBFS. The scale goes - from 0 (very loud noise) to 100 (very faint noise). - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Identity' region. In this region no attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in - GainController2. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Knee' region. In this region some attenuating gain is applied. - This metric is logged from the Fixed Digital limiter in GainController2. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Limiter' region. In this region some more attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in - GainController2. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Saturation' region. In this region much attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in - GainController2. - - - - - hlundin@chromium.org - - The automatic gain control (AGC) in WebRTC tries to adjust the microphone - gain to maintain a strong audio level, but without clipping (saturation). - The histogram will log a value every time input clipping is detected. The - value is a boolean, with "true" meaning that the gain was in fact - adjusted in response to the detected clipping, and "false" meaning - that adjustment was not allowed due to limiting boundaries in the algorithm. - - - - - hlundin@chromium.org - - The automatic gain control (AGC) in WebRTC tries to adjust the microphone - gain to maintain a strong audio level, but without clipping (saturation). - The histogram will log a new value every time the AGC changes the target - level. - - - - - hlundin@chromium.org - - This histogram reports the average RMS of the signal coming in to WebRTC's - Audio Processing Module, prior to any WebRTC processing. A new value is - reported every 10 seconds, and the average is over the latest interval. The - metric is negated dBFS, meaning that 0 is a full-scale signal, while 127 - corresponds to -127 dBFS (very faint). - - - - - hlundin@chromium.org - - This histogram reports the peak RMS of the signal coming in to WebRTC's - Audio Processing Module, prior to any WebRTC processing. A new value is - reported every 10 seconds, and the peak is the RMS of the strongest 10 ms - block over the latest interval. The metric is negated dBFS, meaning that 0 - is a full-scale signal, while 127 corresponds to -127 dBFS (very faint). - - - - - peah@chromium.org - - This histogram reports the average RMS of the signal in the output of - WebRTC's Audio Processing Module, after all audio WebRTC processing. A new - value is reported every 10 seconds, and the average is over the latest - interval. The metric is negated dBFS, meaning that 0 is a full-scale signal, - while 127 corresponds to -127 dBFS (very faint). - - - - - peah@chromium.org - - This histogram reports the peak RMS of the signal in the output of WebRTC's - Audio Processing Module, after all WebRTC audio processing. A new value is - reported every 10 seconds, and the peak is the RMS of the strongest 10 ms - block over the latest interval. The metric is negated dBFS, meaning that 0 - is a full-scale signal, while 127 corresponds to -127 dBFS (very faint). - - - - - hlundin@chromium.org - ivoc@chromium.org - - Measures the duration of each audio interruption event. An audio - interruption is defined as a loss concealment (a.k.a. expand) event that - lasts more than 150 milliseconds. The metric registers each of these events. - This gives an indication of the length and prevalence of severe network - events, which are likely to be detrimental to the audio quality. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Identity' region. In this region no attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in the Audio - Mixer. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Knee' region. In this region some attenuating gain is applied. - This metric is logged from the Fixed Digital limiter in the Audio Mixer. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Limiter' region. In this region some more attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in the Audio - Mixer. - - - - - aleloi@chromium.org - - The Fixed-Digital part of the AGC protects from saturation by reducing the - level of too loud signals. This metric shows how long the level estimate - stays in the 'Saturation' region. In this region much attenuating gain is - applied. This metric is logged from the Fixed Digital limiter in the Audio - Mixer. - - - - - aleloi@chromium.org - - Reports the sampling rate at which audio mixing is done. Lower rates result - in faster processing, higher rates can give higher quality. - - - - - aleloi@chromium.org - - Reports the number of active incoming streams in the WebRTC audio mixer. An - incoming stream is active if it is not muted. When multiple sterams are - active, adding them can result in saturation and limiting is needed. - - - - - aleloi@chromium.org - - Reports the number of streams in the WebRTC audio mixer. The mixer queries - all streams for audio and preferred sampling rate. The number of streams - affects mixing decisions. Whether to mix in floating points or use a limiter - depends on the number of incoming streams. - - - - - hlundin@chromium.org - - Measures the average waiting time in the buffer for each packet. The waiting - time is the time elapsed from the packet arrives until it is decoded. The - metric is calculated as the average over one minute, and is logged at the - end of each such interval. A well tuned target buffer level should lead to a - low value. - - - - - hlundin@chromium.org - - Measures the duration of each packet loss concealment (a.k.a. expand) event - that is not followed by a merge operation. The outage is measured in - milliseconds, with a range between 0 and 2000 ms. This gives an indication - of how well the jitter buffer's level adaptation is working. If the chosen - target level is too low, this value will increase. - - - - - hlundin@chromium.org - - Counts the number of delayed packet outage events per minute. The range is - between 0 and 100 (corresponds to more 1.6 events per second). See - WebRTC.Audio.DelayedPacketOutageEventMs for the definition of a delayed - packet outage event, and the interpretation of such events. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs a value indicating whether the WebRTC echo canceller - detects that there is active content in the render signal. A new value is - logged every 10 seconds and the logged value is averaged over this period. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the applied render buffer delay used in the WebRTC echo - canceller. A new value is logged every 10 seconds and the logged value - constitutes the current buffer delay at the time when the value is logged. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs a value every time the WebRTC echo canceller has - detected saturation in the capture signal. A new value is logged every 10 - seconds and the logged value indicates whether the capture signal has been - saturated during the last 10 seconds. - - - - - gustaf@chromium.org - peah@chromium.org - - This histogram logs whether clockdrift is detected in the WebRTC echo - canceller. A new value is logged every 10 seconds. - - - - - - Removed in M81 as the metric is no longer used for analysis. - - peah@chromium.org - - This histogram logs the level of the comfort noise in the WebRTC echo - canceller in the lower 4 kHz. A new value is logged every 10 seconds. - - - - - - Removed in M81 as the metric is no longer used for analysis. - - peah@chromium.org - - This histogram logs the level of the comfort noise in the WebRTC echo - canceller between 4 and 8 kHz. A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the frequency of echo path delay changes that are - detected by the delay estimator in the WebRTC echo canceller. A new value is - logged every 10 seconds and the logged value indicates how frequent delay - changes have been during the last 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the estimated echo path delay in 64 sample blocks as - seen by the delay estimator in the WebRTC echo canceller. A new value is - logged every 10 seconds and the logged value is the estimate of the delay of - the echo path at the time when the value is logged. - - - - - gustaf@chromium.org - peah@chromium.org - - This histogram logs the echo return loss achieved by the WebRTC echo - canceller as described in ITU G.168. When the echo canceller is being used, - one value is logged every 10 seconds per ongoing WebRTC call. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the echo return loss achieved by the WebRTC echo - canceller in the lower 4 kHz. A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the echo return loss achieved by the WebRTC echo - canceller between 4 and 8 kHz. A new value is logged every 10 seconds. - - - - - gustaf@chromium.org - peah@chromium.org - - This histogram logs the echo return loss enhancement achieved by the WebRTC - echo canceller as described in ITU G.168. When the echo canceller is being - used, one value is logged every 10 seconds per ongoing WebRTC call. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the echo return loss enhancement achieved by the WebRTC - echo canceller in the lower 4 kHz. A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the echo return loss enhancement achieved by the WebRTC - echo canceller between 4 and 8 kHz. A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the estimated echo path delay in 64 sample blocks as - seen by the linear filter delay in the WebRTC echo canceller. The value 0 - means that no delay could be estimated from the linear filter, otherwise the - logged delay corresponds to the actual delay + 1. A new value is logged - every 10 seconds and the logged value is the estimate of the filter delay at - the time when the value is logged. - - - - - peah@chromium.org - gustaf@chromium.org - - This histogram logs the observed maximum number of capture API calls in a - row in the unit of frames (10 ms). A new value is logged every 10 seconds. - - - - - peah@chromium.org - gustaf@chromium.org - - This histogram logs the observed maximum number of render API calls in a row - in the unit of frames (10 ms). A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the number of times per minute that the WebRTC echo - canceller detects a shift in the skew between the total number of render and - capture calls. The metric is reported once per minute and the report is done - also for the case of 0 detected skew shifts have been detected. The amount - of skew shifts per minute is capped to 20. The metric is reported separately - for each render process. The metric is only reported for render processes - where the WebRTC echo canceller is active in and there is both audio being - played out and captured simultaneously. The reporting is only done when the - browser is awake. - - - - - peah@chromium.org - gustaf@chromium.org - - This histogram logs the observed minimum number of capture API calls in a - row in the unit of frames (10 ms). A new value is logged every 10 seconds. - - - - - peah@chromium.org - gustaf@chromium.org - - This histogram logs the observed minimum number of render API calls in a row - in the unit of frames (10 ms). A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs a value every time the WebRTC echo canceller deems that - echo path is possible to model using any of the the echo canceller echo path - models. A new value is logged every 10 seconds and the logged value is the - feasibility assessment at the time when the value is logged. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the assessed reliability of the delay estimates produced - by the delay estimator in the WebRTC echo canceller. A new value is logged - every 10 seconds and the logged value is a meausure based on how often - during that period the delay estimate was reliable. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the frequency of overruns in the render buffer of the - WebRTC echo canceller. A new value is logged every 10 seconds and the logged - value is a meausure that indicates how often overruns occurred. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs the frequency of underruns in the render buffer of the - WebRTC echo canceller. A new value is logged every 10 seconds and the logged - value is a meausure that indicates how often underruns occurred. - - - - - - Removed in M81 as the metric is no longer used for analysis. - - peah@chromium.org - - This histogram logs the echo suppressor gain in the WebRTC echo canceller in - the lower 4 kHz. A new value is logged every 10 seconds. - - - - - - Removed in M81 as the metric is no longer used for analysis. - - peah@chromium.org - - This histogram logs the echo suppressor gain in the WebRTC echo canceller - between 4 and 8 kHz. A new value is logged every 10 seconds. - - - - - peah@chromium.org - saza@chromium.org - - This histogram logs a value every time the WebRTC echo canceller deems that - the linear filter in the echo canceller is sufficiently well adapted to be - usable. A new value is logged every 10 seconds and the logged value is the - assessment of whether the filter is usable at the time when the value is - logged. - - - - - aleloi@chromium.org - - Histogram of audio codec usage. Every sample corresponds to 5 seconds of - encoding with that codec. - - - - - hlundin@chromium.org - - Measures the expand rate for an incoming WebRTC audio stream. The expand - rate is the fraction of samples that are generated through loss-concealemnt - algorithms instead of being decoded from incoming media packets. The metric - is calculated as the percent over a 10 second internval, and is logged at - the end of each such interval. - - - - - minyue@chromium.org - - Frequency that audio packets hits the capacity of WebRTC jitter buffer. A - larger value indicates that the capacity is not big enough, and/or audio - packets are not processed quickly enough. The metric is recorded every - minute. - - - - - - Removed 11/2019 due to old AEC system (AEC2) being removed. - - hlundin@chromium.org - - Number of triggered WebRTC.Audio.AecSystemDelayJump during a call. This is - recorded when a WebRTC based call has ended. AecSystemDelayJump can be - triggered when, for example, the capture thread is stalled, which can harm - the AEC. NumOfAecSystemDelayJumps shows how often this occurs in general as - well as during a call. - - - - - - Removed 11/2019 due to old AEC system (AEC2) being removed. - - hlundin@chromium.org - - Number of triggered WebRTC.Audio.PlatformReportedStreamDelayJump during a - call. This is recorded when a WebRTC based call has ended. - PlatformReportedStreamDelayJump can be triggered when, for example, the - capture thread is stalled, which can harm the AEC. - NumOfPlatformReportedStreamDelayJumps shows how often this occurs in general - as well as during a call. - - - - - - Removed 11/2019 due to old AEC system (AEC2) being removed. - - hlundin@chromium.org - - The difference in stream delay reported to WebRTC by Chrome. Since we detect - jumps in the capture thread, only positive values are feasible. Note that - the difference in milliseconds is logged and not the actual stream delay - value. Sampled every time the stream delay changes more than 50 - milliseconds. - - - - - - Removed 01/2020 due to not being monitored in Chrome. - - hlundin@chromium.org - - The sum of the jitter buffer delay and the sound card's buffering delay for - the receiving side. That is, the sum of the metrics - WebRTC.Audio.ReceiverDeviceDelayMs and - WebRTC.Audio.ReceiverJitterBufferDelayMs. Sampled once every 10 ms when - WebRTC audio is playing. - - - - - hlundin@chromium.org - - The sound card's buffering delay for the receiving side. Sampled once every - 10 ms when WebRTC audio is playing. - - - - - hlundin@chromium.org - - The jitter buffer delay for the receiving side. Sampled once every 10 ms - when WebRTC audio is playing. - - - - - hlundin@chromium.org - ivoc@chromium.org - - The estimated likelihood percentage of echo as detected by the residual echo - detector. The residual echo detector can be used to detect cases where the - AEC (hardware or software) is not functioning properly. The detector can be - non-causal and operates on larger timescales with more delay than the - regular AEC. - - - - - hlundin@chromium.org - - Measures the audible expand rate for an incoming WebRTC audio stream. The - metric is very similar to WebRTC.Audio.ExpandRate, with the difference that - this metric only reports loss-concealement that generates audible samples. - The metric is calculated as the percent over a 10 second internval, and is - logged at the end of each such interval. - - - - - hlundin@chromium.org - - The target bitrate in kbps that the audio codec should try to produce on - average. Sampled every time the rate is updated. - - - - - hlundin@chromium.org - - The target jitter buffer delay for the receiving side. Sampled once every 10 - ms per WebRTC receive stream when WebRTC audio is playing. - - - - - - Removed from code 2014/2/25. - - Please list the metric's owners. Add more owner tags as needed. - Duration in milliseconds of WebRTC audio capture session. - - - - henrika@chromium.org - webrtc-audio@google.com - Audio input channel layout in WebRTC. - - - - - No longer exists in the code as of 2014/2/25. - - Please list the metric's owners. Add more owner tags as needed. - Size of WebRTC audio input buffers (in audio frames). - - - - - No longer exists in the code as of 2014/2/25. - - Please list the metric's owners. Add more owner tags as needed. - - Size of WebRTC audio input buffers (atypical values, in audio frames). - - - - - henrika@chromium.org - Audio input sample rate for WebRTC (in Hz). - - - - henrika@chromium.org - webrtc-audio@google.com - - Audio input sample rate for WebRTC (atypical values, in Hz). - - - - - - Removed from code on 2014/2/25. - - Please list the metric's owners. Add more owner tags as needed. - Audio output channel layout in WebRTC. - - - - - Removed from code Sep 2014. - - henrika@chromium.org - Size of WebRTC audio output buffers (in audio frames). - - - - - Removed from code Sep 2014. - - henrika@chromium.org - - Size of WebRTC audio output buffers (atypical values, in audio frames). - - - - - henrika@chromium.org - webrtc-audio@google.com - Audio output sample rate for WebRTC (in Hz). - - - - henrika@chromium.org - webrtc-audio@google.com - - Audio output sample rate for WebRTC (atypical values, in Hz). - - - - - - Removed from code 2014/2/25. - - Please list the metric's owners. Add more owner tags as needed. - Duration in milliseconds of WebRTC audio render session. - - - - - Removed as of Aug 2016, replaced by - Media.Audio.Render.GetSourceDataTime.WebRTC. - - henrika@chromium.org - - Measures the time spent in WebRtcAudioRenderer::SourceCallback. Sampled 10 - times per second. - - - - - holmer@chromium.org - The bandwidth estimate 2 seconds into a WebRTC call. - - - - holmer@chromium.org - - The number of video packets lost durig the first 2 seconds in a WebRTC call. - - - - - holmer@chromium.org - - The round-trip time as measured 2 seconds into a WebRTC call. - - - - - holmer@chromium.org - - The difference between the bandwidth estimate at 2 seconds and 20 seconds - into a WebRTC call, with a min at 0, which is supposed to capture the how - much the initial bandwidth estimate overshot the actual bandwidth available. - - - - - philipel@chromium.org - - The bitrate that will be probed, triggered by an update to the max - configured bitrate. - - - - - philipel@chromium.org - - The resulting bitrate probed, triggered by an update to the max configured - bitrate. - - - - - philipel@chromium.org - - A successful probing attempt for a given bitrate, triggered by an update to - the max configured bitrate. NOTE! This is not the resulting bitrate from a - probing attempt, see WebRTC.BWE.MidCallProbing.ProbedKbps. - - - - - jonasolsson@chromium.org - crodbro@chromium.org - - The size in bytes of the probe cluster. Counted for each cluster once all - its packets have been sent. - - - - - jonasolsson@chromium.org - crodbro@chromium.org - - The size in packets of the probe cluster. Counted for each cluster once all - its packets have been sent. - - - - - jonasolsson@chromium.org - crodbro@chromium.org - - The time from sending the first to the last packet of the probe cluster. - Counted for each cluster once all its packets have been sent. - - - - - jonasolsson@chromium.org - crodbro@chromium.org - - Counts the amount of probe clusters that timed out. Counted when the prober - is destroyed. - - - - - jonasolsson@chromium.org - crodbro@chromium.org - - Counts the amount of probe clusters that the bitrate prober created. Counted - when the prober is destroyed. - - - - - holmer@chromium.org - - The time it takes the estimated bandwidth to reach 1000 kbps from the first - RTCP packet received. Used to measure the bandwidth ramp-up time. - - - - - holmer@chromium.org - - The time it takes the estimated bandwidth to reach 2000 kbps from the first - RTCP packet received. Used to measure the bandwidth ramp-up time. - - - - - holmer@chromium.org - - The time it takes the estimated bandwidth to reach 500 kbps from the first - RTCP packet received. Used to measure the bandwidth ramp-up time. - - - - - holmer@chromium.org - - The bandwidth estimation used in WebRTC calls. Records whether the BWE is - running on the sender or the receiver and what BWE related RTP header - extensions are in use. - - - - - holmer@chromium.org - - Average audio bitrate received during a call, counted from first packet - received until Call instance is destroyed. Only mesured for calls that are - at least 10 seconds long. - - - - - holmer@chromium.org - - Average total bitrate received during a call (audio + video + RTCP), counted - from first packet received until Call instance is destroyed. Only mesured - for calls that are at least 10 seconds long. - - - - - holmer@chromium.org - - Average estimated send bitrate during a call, counted from first packet sent - until Call instance is destroyed. Only mesured for calls that are at least - 10 seconds long. - - - - - asapersson@chromium.org - - The lifetime of a call. Recorded when a Call instance is destroyed. - - - - - holmer@chromium.org - - Average pacer bitrate during a call, counted from first packet sent until - Call instance is destroyed. Only mesured for calls that are at least 10 - seconds long. - - - - - holmer@chromium.org - - Average RTCP bitrate received during a call, counted from first packet - received until Call instance is destroyed. Only mesured for calls that are - at least 10 seconds long. - - - - - saza@chromium.org - - The amount of time between the arrival of the first and last audio RTP - packets to pass through a Call object. This is logged when the Call object - is destroyed. This is only logged if audio RTP packets are at some point in - time received, and is a way to omit temporary objects that do not send any - actual media. - - - - - saza@chromium.org - - The amount of time between the arrival of the first and last video RTP - packets to pass through a Call object. This is logged when the Call object - is destroyed. This is only logged if video RTP packets are at some point in - time received, and is a way to omit temporary objects that do not send any - actual media. - - - - - - Removed 11/2018 due to little use and high implementation complexity. - - saza@chromium.org - - The amount of time between sending the first and the last audio RTP packets - through the audiostreams of a Call object. This is logged when the Call - object is destroyed. This is only logged if audio RTP packets are at some - point in time received, and is a way to omit temporary objects that do not - send any actual media. - - - - - holmer@chromium.org - - Average video bitrate received during a call, counted from first packet - received until Call instance is destroyed. Only mesured for calls that are - at least 10 seconds long. - - - - - perkj@chromium.org - - Counters on creation, opening, and a few main attributes of data channels. - - - - - perkj@chromium.org - - The maximum number of retransmissions that are attempted in unreliable mode. - It is set to the value used in the configuration when a RTCDataChannel is - created. - - - - - perkj@chromium.org - - The length of the time window during which transmissions and retransmissions - may occur in unreliable mode. It is set to the value used in the - configuration when a RTCDataChannel is created. - - - - - guidou@chromium.org - marinaciocea@chromium.org - armax@chromium.org - - Counters on creation of DesktopCaptureDevice and the first capture call. - - - - - zhihuang@chromium.org - - Counters on different types of TCP socket error code. Collected when we hit - the error code when writing. - - - - - zhihuang@chromium.org - - Counters on different types of UDP socket error code. Collected when we hit - the error code when writing. - - - - - reillyg@chromium.org - device-dev@chromium.org - - Records whether a user would potentially see a permission prompt for moving - the camera. It is recorded when showing a camera permission prompt - regardless of whether or not the site requested camera movement. - - - - - guoweis@chromium.org - - Counters on various types of NAT observed. This is logged once per session. - - - - - perkj@chromium.org - - Number of data channels created per PeerConnection. Sample added to the - histogram when the PeerConnection is destroyed. Note that this is done - purely on the renderer side, so no sample will be generated when the - renderer process is destroyed (as in the fast shutdown path for the - renderer) before the PeerConnection is destroyed. - - - - - hta@chromium.org - webrtc-dev@chromium.org - - Outcomes of adding ICE candidates to a PeerConnection. Used to check the - theory that failures in candidate addition are ignored by applications. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes which - "answerer step" the peer connection reached in its most successful - attempt. See blink::AnswererState for more information. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes the status - of the most successful attempt. See blink::CallSetupState for more - information. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes which - "answerer step" the peer connection reached in its most successful - attempt. See blink::OffererState for more information. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes which - "answerer step" the peer connection reached in its most successful - attempt. See blink::AnswererState for more information. This is the same as - "WebRTC.PeerConnection.CallSetupState.AnswererState" except it is - only reported for peer connections on pages where getUserMedia() has been - called. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes the status - of the most successful attempt. See blink::CallSetupState for more - information. This is the same as - "WebRTC.PeerConnection.CallSetupState.CallSetupState" except it is - only reported for peer connections on pages where getUserMedia() has been - called. - - - - - - These metrics were useful when Unified Plan was made the default SDP - semantics. They will again become useful when Plan B is becoming deprecated. - Until then, these are of little value and are temporarily disabled. - - hbos@chromium.org - hta@chromium.org - - Setting up a call involves a number of steps; this enum describes which - "answerer step" the peer connection reached in its most successful - attempt. See blink::OffererState for more information. This is the same as - "WebRTC.PeerConnection.CallSetupState.OffererState" except it is - only reported for peer connections on pages where getUserMedia() has been - called. - - - - - qingsi@google.com - jeroendb@google.com - - Counters of various ICE Endpoint types. These values are logged for the - first selected candidate pair of a PeerConnection. - - - - - qingsi@google.com - jeroendb@google.com - - Counters of ICE Connection states. These values are logged when the - PeerConnection gets into that state for the first time or after the ICE - restart. - - - - - zhihuang@chromium.org - - Records the error whenever the Dtls handshake fails. There are only two - types of errors, incompatitable cipher suite and unknown error, for now. - - - - - honghaiz@chromium.org - Records the reasons for ICE re-gathering. - - - - honghaiz@chromium.org - - Records the transport channel states when ICE restart happens. - - - - - qingsi@google.com - jeroendb@google.com - - Counters on IPv4 and IPv6 usage in PeerConnection. These values are logged - once per PeerConnection. - - - - - qingsi@google.com - jeroendb@google.com - - Whether the permission to collect the local IP addresses in WebRTC has been - requested and/or granted. This is collected the first time when networks - updated event is reported or if never reported, during the destruction phase - of a call. - - - - - qingsi@google.com - jeroendb@google.com - - Number of IPv4 network interfaces discovered in a PeerConnection Session. - - - - - qingsi@google.com - jeroendb@google.com - - Number of IPv4 local Candidates gathered in a PeerConnection Session once - the ICE address gathering process reaches the Completed status. To avoid - miscounting, this only includes the first m line's first component. - - - - - qingsi@google.com - jeroendb@google.com - - Number of IPv6 network interfaces discovered in a PeerConnection Session. - - - - - qingsi@google.com - jeroendb@google.com - - Number of IPv6 local Candidates gathered in a PeerConnection Session once - the ICE address gathering process reaches the Completed status. To avoid - miscounting, this only includes the first m line's first component. - - - - - hta@chromium.org - - What key exchange protocol (DTLS or SDES) is used to establish the crypto - keys for a PeerConnection's RTP transport. - - - - - hta@chromium.org - - What key exchange protocol (DTLS or SDES) is used to establish the crypto - keys for a PeerConnection's RTP transport, specified per media type. - - - - - kron@chromium.org - - What setting for the SDP attribute extmap-allow-mixed has been asked for by - the creator of a PeerConnection. This is specified to the constructor - through the dictionary property offerExtmapAllowMixed which can be set to - either true or false. A default value will be used if it's not specified. - - - - - pthatcher@chromium.org - - Whether RTCP-mux is used for the PeerConnection (both the local and remote - description enable RTCP-mux). Recorded after SetLocalDescription and - SetRemoteDescription are called, once per PeerConnection. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of createAnswer(). Using complex SDP without explicitly - specifying the sdpSemantics is considered unsafe in this context because - such usage is sensitive to the rollout of a different default SDP semantic. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of createOffer(). Using complex SDP without explicitly - specifying the sdpSemantics is considered unsafe in this context because - such usage is sensitive to the rollout of a different default SDP semantic. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of setLocalDescription(answer). Using complex SDP - without explicitly specifying the sdpSemantics is considered unsafe in this - context because such usage is sensitive to the rollout of a different - default SDP semantic. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of setLocalDescription(offer). Using complex SDP - without explicitly specifying the sdpSemantics is considered unsafe in this - context because such usage is sensitive to the rollout of a different - default SDP semantic. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of setRemoteDescription(answer). Using complex SDP - without explicitly specifying the sdpSemantics is considered unsafe in this - context because such usage is sensitive to the rollout of a different - default SDP semantic. - - - - - hbos@chromium.org - - The SDP usage category ("safe", "unsafe" or - "unknown") of setRemoteDescription(offer). Using complex SDP - without explicitly specifying the sdpSemantics is considered unsafe in this - context because such usage is sensitive to the rollout of a different - default SDP semantic. - - - - - steveanton@chromium.org - - What SDP format is received in the remote offer. The value "no - tracks" means that no audio or video tracks were received. The value - "simple" means that at most one audio and at most one video track - was received. The value "complex" means that more than one audio - or more than one video track was received, and how this was signaled is - indicated ("Plan B" meaning with a=ssrc lines within the same m= - section and "Unified Plan" meaning with a separate m= section). - - - - - hta@chromium.org - - What SDP semantic (Unified Plan or Plan B) was detected when completing - negotiation of a PeerConnection. This is recorded when accepting an SDP - Answer. The value "mixed" means that the accepted answer included - both types of marker in the SDP. The value "none" will happen when - the answerer sends no media. - - - - - hta@chromium.org - - What SDP semantic (Unified Plan, Plan B or "use default") has been - asked for by the creator of a PeerConnection. - - - - - - Removed on Dec 2016. This histogram is used to gauge the risk of making the - change for issue 6030. The decision has been made and this is not needed any - more. - - zhihuang@chromium.org - - Whether the application specified a value for RTCP-mux policy, and if so, - which value, "Require" or "Negotiate". Recorded after - parsing the configuration when creating the RTCPeerConnection. - - - - - amithi@chromium.org - - Was simulcast applied to the local description and with which API surface. - - - - - amithi@chromium.org - - Was simulcast applied to the remote description and with which API surface. - - - - - amithi@chromium.org - - Simulcast was disabled because it is not supported by the remote party. This - is a counter that can take on only a single value (1). - - - - - amithi@chromium.org - - Counts the number of send encodings given to PeerConnection::AddTransceiver. - This histogram will be used to understand if and how the API is used. - - - - - - - steveanton@chromium.org - - What error code is reported by libsrtp when failing to unprotect an incoming - SRTCP (secured media control) packet. - - - - - qingsi@google.com - jeroendb@google.com - - Counters on the type of SRTP crypto suites used by WebRTC. This is collected - whenever the transport signals the OnCompleted event. - - - - - - - steveanton@chromium.org - - What error code is reported by libsrtp when failing to unprotect an incoming - SRTP (secured media) packet. - - - - - qingsi@google.com - jeroendb@google.com - - Counters on the type of SSL cipher suites used by WebRTC. This is collected - whenever the transport signals the OnCompleted event. - - - - - eshr@google.com - hbos@chromium.org - - Measures computer thermal state, sampled every 60s when a PeerConnection is - open with a video sender. Most quick toggles between thermal states are thus - not sampled, but thermal states are generally stable so these toggles should - be rare. - - - - - qingsi@google.com - jeroendb@google.com - Time to setup a peer to peer call with PeerConnection. - - - - qingsi@google.com - jeroendb@google.com - - Time to receive the first SignalNetworksChanged from the request to start - updating network in PeerConnection. - - - - - hta@chromium.org - webrtc-dev@chromium.org - - Capsule history of a WebRTC PeerConnection, encoded as a sequence of bits - encapsulated in an integer. Only a few values will be deemed interesting, - but the interesting values may change over time. - - - - - perkj@chromium.org - - Durations of audio tracks received over a PeerConnection. The stopwatch - starts when the track first becomes connected, and ends when it is - disconnected or very soon thereafter. - - - - - perkj@chromium.org - - Durations of video tracks received over a PeerConnection. The stopwatch - starts when the track first becomes connected, and ends when it is - disconnected or very soon thereafter. - - - - - perkj@chromium.org - - Sizes of messages sent over reliable data channels. The size of an - individual message is added to the histogram as a sample immediately when a - message is sent. - - - - - jiayl@chromium.org - Time for capturing one frame in screen capturing. - - - - perkj@chromium.org - - Durations of audio tracks sent over a PeerConnection. The stopwatch starts - when the track first becomes connected, and ends when it is disconnected or - very soon thereafter. - - - - - perkj@chromium.org - - Durations of video tracks sent over a PeerConnection. The stopwatch starts - when the track first becomes connected, and ends when it is disconnected or - very soon thereafter. - - - - - qingsi@google.com - jeroendb@google.com - - For clients using a shared source port per STUN binding request toward the - specified servers, success rate for requests which received a response with - various intervals between requests. Only the first instance of renderers - will conduct the trial and log this result. The STUN binding requests are - grouped into multiple batches and the success rate is calculated for an - individual batch. - - - - - qingsi@google.com - jeroendb@google.com - - For clients using a shared source port per STUN binding request, average RTT - for requests which received a response with various intervals between - requests. Only the first instance of renderers will conduct the trial and - log this result. - - - - - qingsi@google.com - jeroendb@google.com - - For clients using a shared source port per STUN binding request, success - rate for requests which received a response with various intervals between - requests. Only the first instance of renderers will conduct the trial and - log this result. - - - - - qingsi@google.com - jeroendb@google.com - - The maximum of consecutive delayed bytes caused by EWOULDBLOCKs from system. - This happens when system can't send any packet synchronously at that moment. - - - - - qingsi@google.com - jeroendb@google.com - - The percentage of packets delayed due to ERR_IO_PENDING from system in a - WebRTC socket. This happens when system can't send any packet synchronously - at that moment. - - - - - qingsi@google.com - jeroendb@google.com - - The duration that it takes to send out a packet in system layer. This - includes both the queuing time (under the condition when socket returns - EWOULDBLOCK from system) as well as the time system takes to finish the - asynchronous send. For UDP, it's the time from P2PSocketHostUdp::Send to - P2PSocketHostUdp::HandleSendResult. Tcp part is to be implemented. - - - - - perkj@chromium.org - - Sizes of messages sent over unreliable data channels. The size of an - individual message is added to the histogram as a sample immediately when a - message is sent. - - - - - andresp@chromium.org - - The state of a UserMediaRequest when it gets destroyed before having a - result. - - Note: "Explicitly Cancelled" means - MediaStreamImpl::cancelUserMediaRequest was called and not necessarily that - the user cancelled. Those are likely tracked as UserMediaRequest with a - result of permission denied. - - - - - - Replaced by WebRTC.UserMediaRequest.Result2 in Feb 2018. - - andresp@chromium.org - - Counters for UserMediaRequests results such as failure reasons. - - - - - grunell@chromium.org - - Counters for UserMediaRequests results such as failure reasons. The standard - specification error names are in parenthesis. - - - - - - - asapersson@chromium.org - webrtc-video@google.com - - The average number of adaptation changes per minute for a sent video stream. - Recorded when a stream is removed. - - - - - - - holmer@chromium.org - - The average round-trip time of a WebRTC call in milliseconds. Recorded when - a stream is removed. - - - - - - - asapersson@chromium.org - - The absolute value of the sync offset between a rendered video frame and the - latest played audio frame is measured per video frame. The average offset - per received video stream is recorded when a stream is removed. - - - - - - Removed 08/27/2020. - - sprang@chromium.org - - Fraction of time the call was classified as bad because of any reason. - - - - - - Removed 08/27/2020. - - sprang@chromium.org - - Fraction of time the call was classified as bad because of low framerate. - - - - - - Removed 08/27/2020. - - sprang@chromium.org - - Fraction of time the call was classified as bad because of high framerate - variance. - - - - - - Removed 08/27/2020. - - sprang@chromium.org - - Fraction of time the call was classified as bad because of high qp. - - - - - - - asapersson@chromium.org - - Percentage of sent frames that are limited in resolution due to bandwidth - for a sent video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - webrtc-video@google.com - - For frames that are limited in resolution due to bandwidth, the average - number of disabled resolutions is recorded for a sent video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of received bits per second for a received video stream. Recorded - when a stream is removed. The total number of bytes is divided by the time - the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent bits per second for a sent video stream. Recorded when a - stream is removed. The total number of bytes is divided by the time the - video stream exists. - - - - - - Removed 03/28/2019. - - asapersson@chromium.org - - The number of complete frames received per second for a received video - stream. Recorded when a stream is removed. The total number of frames is - divided by the time the video stream exists. - - - - - - - asapersson@chromium.org - - Percentage of frames that are limited in resolution due to CPU for a sent - video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - Average current delay for a received video stream. This is the actual delay - imposed on frames (where the goal is to reach the target delay (see - WebRTC.Video.TargetDelayInMs)). Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The average QP (quantizer value) per frame for a received VP8 video stream. - Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of decoded frames per second for a received video stream. - Recorded when a stream is removed. The total number of frames is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The average decode time per frame for a received video stream. Recorded when - a stream is removed. - - - - - kron@chromium.org - - The decode time per frame for a received video stream. Continously updated - after each frame has been decoded. - - - - - - - asapersson@chromium.org - - Percentage of delayed frames to renderer for a received video stream. - Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The average delay of delayed frames to renderer for a received video stream. - Recorded when a stream is removed. - - - - - - Removed 03/28/2019. - - asapersson@chromium.org - - Percentage of discarded packets by the jitter buffer due to arriving too - late for a received video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by a capturer for a sent video stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by an encoder's internal rate limiter for a - sent video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped because encoder queue is full for a sent - video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a - sent video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by a WebRTC on the receive side because they - are incomplete or undecodable. - - - - - - Removed 03/28/2019. - - asapersson@chromium.org - - Percentage of duplicated packets in the jitter buffer for a received video - stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The average QP (quantizer value) per frame for a sent video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - webrtc-video@google.com - - Configured video codec for a sent video stream. Recorded when a - VideoSendStream is destroyed (for streams whose lifetime is longer than 10 - seconds). - - - - - - - asapersson@chromium.org - - The average encode time per frame for a sent video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - The average end-to-end delay per frame for a received video stream. Recorded - when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The maximum end-to-end delay per frame for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of received FEC bits per second for a received video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent FEC bits per second for a sent video stream. Recorded - when a stream is removed. The total number of bytes is divided by the time - the video stream exists. - - - - - - - asapersson@chromium.org - - The number of received RTCP FIR packets per minute for a sent video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent RTCP FIR packets per minute for a received video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - hbos@chromium.org - - The number of |H264DecoderImpl| events, such as an initialization or - decoding error, that have occurred. At most one Init and one Error is - reported per |H264DecoderImpl| instance. This is to avoid the same event - from being reported multiple times (e.g. if there is an error you might - re-initialize or get a decode error every frame which would otherwise - pollute the data). - - - - - - - hbos@chromium.org - - The number of |H264EncoderImpl| events, such as an initialization or - encoding error, that have occurred. At most one Init and one Error is - reported per |H264EncoderImpl| instance. This is to avoid the same event - from being reported multiple times (e.g. if there is an error you might - re-initialize or get an encode error every frame which would otherwise - pollute the data). - - - - - kron@chromium.org - webrtc-video@google.com - - The number of hardware decoded frames between fallbacks to software decoder - for a received video stream. - - - - - - - asapersson@chromium.org - - The number of incoming frames per second for a sent video stream. Recorded - when a stream is removed. The total number of frames is divided by the time - the video stream exists. - - - - - - - asapersson@chromium.org - - The average input height per frame (for incoming frames to video engine) for - a sent video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The average input width per frame (for incoming frames to video engine) for - a sent video stream. Recorded when a stream is removed. - - - - - ilnik@chromium.org - webrtc-video@google.com - - The 95th percentile of interframe delay for a received video stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average interframe delay for a received video stream. Recorded when a - stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The maximum interframe delay for a received video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - Average jitter buffer delay for a received video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - Permille of frames that are key frames for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - Permille of frames that are key frames for a sent video stream. Recorded - when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average duration of a freeze in video playback. Recorded when a received - stream is removed or content type changes. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average duration of a smooth video playback. Recorded when a received - stream is removed or content type changes. - - - - - - - asapersson@chromium.org - - The number of received media payload bits per second for a received video - stream. Recorded when a stream is removed. The total number of bytes is - divided by the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent media payload bits per second for a sent video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of received RTCP NACK packets per minute for a sent video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent RTCP NACK packets per minute for a received video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - ssilkin@chromium.org - - The number of video freezes per minute for a received video stream. Recorded - when a stream is removed or content type changes. - - - - - - - asapersson@chromium.org - - The number of times a video stream has been paused/resumed during a call. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average number of resolution down-switches per minute for a received - video stream. Recorded when a stream is removed or content type changes. - - - - - - - asapersson@chromium.org - - Average delay (network delay (rtt/2) + jitter delay + decode time + render - delay) for a received video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of received padding bits per second for a received video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent padding bits per second for a sent video stream. Recorded - when a stream is removed. The total number of bytes is divided by the time - the video stream exists. - - - - - - - asapersson@chromium.org - - Percentage of time that the video has been paused for a sent video stream. - Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of received RTCP PLI packets per minute for a sent video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent RTCP PLI packets per minute for a received video stream. - Recorded when a stream is removed. The total number of packets is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - For frames that are downscaled in resolution due to quality, the average - number of downscales is recorded for a sent video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - Percentage of sent frames that are downscaled in resolution due to quality - for a sent video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - Percentage of received FEC packets for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - The average received height per frame for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - Percentage of received packets lost for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - The average received width per frame for a received video stream. Recorded - when a stream is removed. - - - - - - - asapersson@chromium.org - - The lifetime of a video receive stream. Recorded when a VideoReceiveStream - instance is destroyed. - - - - - - - asapersson@chromium.org - - Percentage of recovered media packets from FEC packets for a received video - stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of sent frames to the renderer per second for a received video - stream. Recorded when a stream is removed. The total number of frames is - divided by the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of pixels (sqrt(width*height)) of sent frames to the renderer per - second for a received video stream. Recorded when a stream is removed. The - total number of pixels is divided by the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of retransmitted bits per second for a received video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of retransmitted bits per second for a sent video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The absolute value of the difference between the estimated frequency during - RTP timestamp to NTP time conversion and the actual value (i.e. 90 kHz) is - measured per received video frame. The max offset during 40 second intervals - is stored. The average of these stored offsets per received video stream is - recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The number of received bits over RTX per second for a received video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - asapersson@chromium.org - - The number of sent bits over RTX per second for a sent video stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - sprang@chromium.org - - Percentage of sent frames that are limited in resolution due to bandwidth - for a sent (screen content) video stream. Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - For frames that are limited in resolution due to bandwidth, the average - number of disabled resolutions is recorded for a sent (screen content) video - stream. Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - The number of sent bits per second for a sent screenshare stream. Recorded - when a stream is removed. The total number of bytes is divided by the time - the video stream exists. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average QP (quantizer value) per frame for a received VP8 screenshare - stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by a capturer for a sent screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by an encoder's internal rate limiter for a - sent screenshare stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped because encoder queue is full for a sent - screenshare stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a - sent screenshare stream. Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - The average encode time per frame for a sent (screen content) video stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average end-to-end delay per frame for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The maximum end-to-end delay per frame for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - The number of sent FEC bits per second for a sent screenshare stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - sprang@chromium.org - - The number of received RTCP FIR packets per minute for a sent screenshare - stream. Recorded when a stream is removed. The total number of packets is - divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - Ratio of sent frames to dropped frames at the encoder. The value is reported - when a stream is removed and is calculated as the total number frames sent - divided by the number of dropped frames. - - - - - - - sprang@chromium.org - - Ratio of sent frames to number of re-encoded frames (due to target bitrate - overshoot). The value is reported when a stream is removed and is calculated - as the total number frames sent divided by the number of re-encoded frames. - - - - - - - asapersson@chromium.org - - The number of incoming frames per second for a sent (screen content) video - stream. Recorded when a stream is removed. The total number of frames is - divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - The average input height per frame (for incoming frames to video engine) for - a sent (screen content) video stream. Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - The average input width per frame (for incoming frames to video engine) for - a sent (screen content) video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The 95th percentile of interframe delay for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average interframe delay for a received screenshare stream. Recorded - when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The maximum interframe delay for a received screenshare stream. Recorded - when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Permille of frames that are key frames for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - Permille of frames that are key frames for a sent (screen content) video - stream. Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - Stats for the lower layer (TL0) of a screenshare stream in conference mode. - - - - - - - sprang@chromium.org - - Stats for the higher layer (TL1) of a screenshare stream in conference mode. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average duration of a freeze in screenshare playback. Recorded then a - received stream is removed or content type changes. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average duration of a smooth video playback for screenshare stream. - Recorded when a received stream is removed or content type changes. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The number of received media payload bits per second for a received - screenshare stream. Recorded when a stream is removed. The total number of - bytes is divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - The number of sent media payload bits per second for a sent screenshare - stream. Recorded when a stream is removed. The total number of bytes is - divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - The number of received RTCP NACK packets per minute for a sent screenshare - stream. Recorded when a stream is removed. The total number of packets is - divided by the time the video stream exists. - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average number of resolution down-switches per minute for a receive - screenshare stream. Recorded when a stream is removed or content type - changes. - - - - - - - sprang@chromium.org - - The number of sent padding bits per second for a sent screenshare stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - sprang@chromium.org - - The number of received RTCP PLI packets per minute for a sent screenshare - stream. Recorded when a stream is removed. The total number of packets is - divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - For frames that are downscaled in resolution due to quality, the average - number of downscales is recorded for a sent (screen content) video stream. - Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - Percentage of sent frames that are downscaled in resolution due to quality - for a sent (screen content) video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average received height per frame for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Percentage of received packets lost for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The average received width per frame for a received screenshare stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The lifetime of a screenshare receive stream. Recorded when a - VideoReceiveStream instance is destroyed. - - - - - - - sprang@chromium.org - - The number of retransmitted bits per second for a sent screenshare stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - sprang@chromium.org - - The number of sent bits over RTX per second for a sent screenshare stream. - Recorded when a stream is removed. The total number of bytes is divided by - the time the video stream exists. - - - - - - - sprang@chromium.org - - The average delay (of average delays) of sent packets for a sent (screen - content) video stream. Recorded when a stream is removed. The delay is - measured from a frame is input to video engine until a packet is sent to the - network. For each sent packet, the average delay of all sent packets over - the last second is reported. The average of these reported delays is - recorded. - - - - - - - sprang@chromium.org - - The average delay (of max delays) of sent packets for a sent (screen - content) video stream. Recorded when a stream is removed. The delay is - measured from a frame is input to video engine until a packet is sent to the - network. For each sent packet, the maximum delay of all sent packets over - the last second is reported. The average of these reported delays is - recorded. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - The number of sent frames per second for a sent (screen content) video - stream. Recorded when a stream is removed. The total number of frames is - divided by the time the video stream exists. - - - - - - - sprang@chromium.org - - The average sent height per frame for a sent (screen content) video stream. - Recorded when a stream is removed. - - - - - - - sprang@chromium.org - - Percentage of sent packets lost for a sent screenshare stream. Recorded when - a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Ratio between Screenshare.SentFramesPerSecond and - Screenshare.InputFramesPerSecond in percents. Recorded when a stream is - removed. The total number of sent frames is divided by the total number of - input frames and multiplied by 100. - - - - - - - sprang@chromium.org - - The average sent width per frame for a sent (screen content) video stream. - Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Percentage of time the received screenshare stream playbacks low quality - blocky video. Recorded when a stream is removed or content type changes. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Percentage of time the received screenshare stream playbacks HD resolution. - Recorded when a stream is removed or content type changes. - - - - - - - sprang@chromium.org - - Percentage of unique RTCP NACK requests that are received in response to a - sent screenshare stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - The average send delay of sent packets for a sent video stream. Recorded - when a stream is removed. The delay is measured from a packet is sent to the - transport until leaving the socket. - - - - - - - asapersson@chromium.org - - The average delay (of average delays) of sent packets for a sent video - stream. Recorded when a stream is removed. The delay is measured from a - frame is input to video engine until a packet is sent to the network. For - each sent packet, the average delay of all sent packets over the last second - is reported. The average of these reported delays is recorded. - - - - - - - asapersson@chromium.org - - The average delay (of max delays) of sent packets for a sent video stream. - Recorded when a stream is removed. The delay is measured from a frame is - input to video engine until a packet is sent to the network. For each sent - packet, the maximum delay of all sent packets over the last second is - reported. The average of these reported delays is recorded. - - - - - - - asapersson@chromium.org - - The lifetime of a video send stream. Recorded when a VideoSendStream - instance is destroyed. - - - - - - - asapersson@chromium.org - - The number of sent frames per second for a sent video stream. Recorded when - a stream is removed. The total number of frames is divided by the time the - video stream exists. - - - - - - - asapersson@chromium.org - - The average sent height per frame for a sent video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - Percentage of sent packets lost for a sent video stream. Recorded when a - stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Ratio between SentFramesPerSecond and InputFramesPerSecond in percents. - Recorded when a stream is removed. The total number of sent frames is - divided by the total number of input frames and multiplied by 100. - - - - - - - asapersson@chromium.org - - The average sent width per frame for a sent video stream. Recorded when a - stream is removed. - - - - - - - asapersson@chromium.org - - Average target delay (jitter delay + decode time + render delay) for a - received video stream. Recorded when a stream is removed. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Percentage of time the receive video stream playbacks low quality blocky - video. Recorded when a stream is removed or content type changes. - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - Percentage of time the receive video stream playbacks HD resolution. - Recorded when a stream is removed or content type changes. - - - - - - - asapersson@chromium.org - - Percentage of unique RTCP NACK requests that are received in response to a - sent video stream. Recorded when a stream is removed. - - - - - - - asapersson@chromium.org - - Percentage of unique RTCP NACK requests that are sent in response to a - received video stream. Recorded when a stream is removed. - - - - - - - perkj@chromium.org - - Counts occurences of if the VP8 software decoder runs out of buffers due to - that they are not returned to the buffer pool. See http://crbug/652923 and - http://crbug/542522. - - - - - guidou@chromium.org - hbos@chromium.org - mcasas@chromium.org - emircan@chromium.org - armax@chromium.org - Counts number of calls to WebRTC APIs from JavaScript. - - - - guidou@chromium.org - armax@chromium.org - - Counts the number of calls to WebRTC APIs from JavaScript once per session. - A session is a crude estimate since its implemented as the lifetime of the - render process that called the WebRTC API. - - - - - - Removed as of r253828 (27 Feb 2014). - - tommi@chromium.org - - Counts number of calls to WebRTC APIs from JavaScript, once per origin per - renderer process. - - - - - jiayl@chromium.org - Time for capturing one frame in window capturing. - - - - eladalon@chromium.org - saeedj@google.com - manj@google.com - dmitriyg@google.com - - The result of calls to the API for the collection and uploading of WebRTC - event logs. - - - - - eladalon@chromium.org - saeedj@google.com - manj@google.com - dmitriyg@google.com - - NetError returned by the SimpleURLLoader object in charge of uploading a - WebRTC event log file. - - - - - eladalon@chromium.org - saeedj@google.com - manj@google.com - dmitriyg@google.com - - Tracks the uploading or discarding of WebRTC event logs that were previously - collected. - - - - - guidou@chromium.org - webrtc-dev@chromium.org - - Counts the number of WebRTC text log events per web application. Suffixed by - event. - - - - - guidou@chromium.org - webrtc-dev@chromium.org - - Network error codes for WebRTC text log upload failures. Recorded when an - upload attempt fails. - - - - - guidou@chromium.org - webrtc-dev@chromium.org - - Counts upload failures for WebRTC text log. Error codes for network errors - are logged in WebRtcTextLogging.UploadFailureNetErrorCode. Recorded when an - upload attempt fails. - - - - - mgiuca@chromium.org - - Counts the number of calls to navigator.share. Includes both successful and - failed shares. - - - - - mgiuca@chromium.org - - Records the outcome of calls to navigator.share. This will not count any - calls that never complete (e.g., if the page closes while the picker is - open). Therefore, DO NOT look at the raw percentages of this histogram; - instead, compare these numbers with the WebShare.ApiCount.Share total. - - NOTE: At the moment, if the user cancels the picker, its recording will be - delayed, and possibly never recorded (https://crbug.com/636274), so that - will account for a discrepancy between ShareOutcome and ApiCount.Share. - - - - - - Removed March 2020. - - ericwilligers@chromium.org - hartmanng@chromium.org - hzjian@chromium.org - yfriedman@chromium.org - - File types included in navigator.share() requests, where file content and - source URLs were not verified with Safe Browsing. - - - - - estark@chromium.org - dullweber@chromium.org - - Tracks actions with the website setting (a.k.a. page info / origin info) - bubble, such as opening it up or clicking on the Connection tab. - - - - - - Removed October 2016 in favor of Security.PageInfo.Action.HttpsUrl.Valid, - Security.PageInfo.Action.HttpsUrl.Dangerous, and - Security.PageInfo.Action.HttpsUrl.Downgraded. - - estark@chromium.org - - Tracks WebsiteSettings actions that take place on an HTTPS URL. This - completely disregards security status. - - - - - mxcai@chromium.org - dominickn@chromium.org - - Tracks actions with the "All Sites" page in website settings for - builds older than M82. - - - - - jarrydg@chromium.org - mxcai@chromium.org - - Tracks actions with the "All Sites" page in website settings - starting in M82. - - - - - miguelg@chromium.org - finnur@chromium.org - - Count of how often a specific content type (permission) is changed using the - content settings menu. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - miguelg@chromium.org - finnur@chromium.org - - Count of how often a specific content type (permission) is set to 'Allowed' - using the content settings menu. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - miguelg@chromium.org - finnur@chromium.org - - Count of how often a specific content type (permission) is set to 'Ask' - using the content settings menu. - - - - - miguelg@chromium.org - finnur@chromium.org - - Count of how often a specific content type (permission) is set to 'Blocked' - using the content settings menu. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - miguelg@chromium.org - finnur@chromium.org - - Count of how often a specific content type (permission) is reset to the - default value using the content settings menu. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - timloh@chromium.org - - Count of how often a specific content type (permission) is changed to the - session only value using the content settings menu. This option only exists - for cookies. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Count of how often a specific content type (permission) is changed using the - Origin Info dialog. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Count of how often a specific content type (permission) is set to 'Allowed' - using the Origin Info dialog. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - andypaicu@chromium.org - engedy@chromium.org - hkamila@chromium.org - - Count of how often a specific content type (permission) is set to 'Blocked' - using the Origin Info dialog. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - - Removed 12/2014 in Issue 433776, and replaced by - WebsiteSettings.OriginInfo.PermissionChanged. - - sashab@chromium.org - - Count of how often a specific content type (permission) is changed using the - Page Info UI. - - Note: The values of this metric collected for Chrome 49 (early 2016) are - innacurate and should not be trusted. crbug.com/589255. - - - - - - Removed 12/2018. We're no longer monitoring WebSQL performance. - - cmumford@chromium.org - - The time required to try (and fail) to open a Web SQL database. - - - - - - Removed 12/2018. We're no longer monitoring WebSQL performance. - - cmumford@chromium.org - The time required to successfully open a Web SQL database. - - - - - - dmurph@chromium.org - pwnall@chromium.org - - Counts the number of WebSQL databases opened for secure vs insecure origins. - - - - - jackhou@chromium.org - - The success or failure of all extension installs from the webstore. This - includes those initiated by sync. - - - - - - There is no remaining code that is emmiting this metric. It was removed at - an unknown time. - - joshwoodward@google.com - - Webstore Widget app: the reason why the suggest apps dialog was closed. - - - - - - There is no remaining code that is emmiting this metric. It was removed at - an unknown time. - - joshwoodward@google.com - - Webstore Widget app: whether the Webstore item user selected was - successfully installed or not. - - - - - - There is no remaining code that is emmiting this metric. It was removed at - an unknown time. - - joshwoodward@google.com - - Webstore Widget app: whether the initialization of the dialog succeeded or - not. - - - - - - There is no remaining code that is emmiting this metric. It was removed at - an unknown time. - - joshwoodward@google.com - - Webstore Widget app: time to load the widget contained in the app. Measured - between the moment window appears and the moment all the contents in the app - including the Chrome Webstore widget are ready. - - - - - dbeam@chromium.org - URLs for which Chrome creates WebUIControllers. - - - - dschuyler@chromium.org - tbuckley@chromium.org - bettes@chromium.org - - Paths within chrome://settings visited. For evaluating popularity and - priorities for chrome://settings GUI. Note that this metric used to include - paths that were part of OS settings, but starting with M-81, this metric - only records browser settings paths. - - - - - collinbaker@chromium.org - dfried@chromium.org - - The WebUI tab strip is a more touch-friendly tab strip used in place of - Chrome's native tab strip in some cases. It can be opened and closed. This - records how a user closed it. - - - - - johntlee@chromium.org - dpapad@chromium.org - - The WebUI tab strip is a more touch-friendly tab strip used in place of - Chrome's native tab strip in some cases. This records how a user closed a - tab within the WebUI tab strip. - - - - - collinbaker@chromium.org - dfried@chromium.org - - The WebUI tab strip is a more touch-friendly tab strip used in place of - Chrome's native tab strip in some cases. It can be opened and closed. This - records how a user opened it. - - - - - collinbaker@chromium.org - dfried@chromium.org - - The WebUI tab strip is a more touch-friendly tab strip used in place of - Chrome's native tab strip in some cases. It can be opened and closed. This - records how long it was open when closing. - - - - - robliao@chromium.org - johntlee@chromium.org - - WebUI Tabstrip: Time from activating a tab from WebUI to receiving an - activation notification in WebUI. - - - - - robliao@chromium.org - johntlee@chromium.org - - WebUI Tabstrip: Time needed to create all of the tab elements at launch. - - - - - robliao@chromium.org - johntlee@chromium.org - - WebUI Tabstrip: Time from requesting the tab data to receiving the data. - - - - - - Removed 2019-12 after expiration, while adding the similar - XHR.Sync.BlockingTime.MainThread and XHR.Sync.BlockingTime.WorkerThread. - - qinmin@chromium.org - cduvall@chromium.org - - Records the total duration the renderer spent on each sync XHR resource - request, including requests that time out. - - - - - - - reillyg@chromium.org - juncai@chromium.org - - Records the reason why the WebUSB device chooser was closed. - - - - - - Obsolete in M72 as initialization of WebUsbDetector no longer blocks the - main thread. - - reillyg@chromium.org - juncai@chromium.org - - Records the time spent initializing the WebUSB detector module. - - - - - - - reillyg@chromium.org - juncai@chromium.org - - Records the reason why the "WebUSB device detected" notification - was dismissed. - - - - - - - reillyg@chromium.org - juncai@chromium.org - - Records when the user revokes permission for an origin to connect to a USB - device using the WebUSB API. - - - - - changwan@chromium.org - ntfschr@chromium.org - src/android_webview/OWNERS - Records calls to WebView APIs in WebViewChromium. - - - - - Obsolete 04/04/2018 as it has been replaced by - Android.WebView.LoadDataWithBaseUrl.HistoryUrl. - - jamwalla@chromium.org - - Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/ - null, the same as the baseUrl parameter, or different from baseUrl. - - - - - tmartino@chromium.org - msarda@chromium.org - droger@chromium.org - chrome-signin-team@google.com - - Records the result of promoting sign-in via the Welcome page. - - - - - tmartino@chromium.org - - Records whether or not Chrome was the default browser when the user left the - Win10-specific Welcome page. - - - - - pmonette@chromium.org - tmartino@chromium.org - - Emits a "true" sample when the revamped WebUI-based welcome page - is added to the startup tabs list. This means that barring an error on - startup, it was shown to the user. This histogram can only be recorded - during first-run flow, when the EnableWelcomeWin10 experiment is enabled. - - - - - pmonette@chromium.org - tmartino@chromium.org - - Emits a "true" sample when the old external welcome page is added - to the startup tabs list. This means that barring an error on startup, it - was shown to the user. This histogram can only be recorded during first-run - flow, when the EnableWelcomeWin10 experiment is disabled. - - - - - pmonette@chromium.org - tmartino@chromium.org - - Records whether or not the check that verifies if Chrome is pinned to the - taskbar has timed out. This check is done when the welcome page is opened in - order to determine which instructions to display to the user. - - - - - tmartino@chromium.org - - Records whether or not Chrome was pinned to the taskbar when the user left - the Win10-specific Welcome page. - - - - - sahel@chromium.org - - Records whether or not a GSU event with wheel source is latched to the - current scrolling element. It is false for the first GSU event of every - scrolling sequence and true for the rest of the GSU events. - - - - - zturner@chromium.org - - Count of page loads in each of the 2 different environments (metro/desktop) - on Windows 8. - - - - - kuscher@chromium.org - - The number of app windows open when a load completes. This includes windows - opened by an app shortcut, or apps opened in a popup. This only counts v1 - apps. - - - - - - Removed 4/2013. No longer tracked. - - kuscher@chromium.org - - The number of panel windows open when a load completes. Panels are windows - docked to the bottom of the OS desktop, which are visible to the user even - while the user is interacting with other applications. - - - - - kuscher@chromium.org - - The number of popup windows open when a load completes. Popup windows only - have one content area (no multiple tabs) and a stripped down toolbar - consisting only of a read-only address bar. - - - - - kuscher@chromium.org - - The number of tabbed windows open when a load completes. A tabbed window is - a normal browser window which can have one or more tabs. - - - - - davidbienvenu@chromium.org - fdoray@chromium.org - - A top level window's occlusion state. Recorded each time the state changes. - - - - - forshaw@chromium.org - wfh@chromium.org - - Records if the APPID driver is running which indicates Applocker is enabled - and running. This does not guarantee that Applocker is configured to enforce - any rules. Reported once per browser session, on startup. - - - - - brucedawson@chromium.org - jessemckenna@google.com - - The result of prefetching chrome.dll on Windows, including whether a - fallback to slow prefetch took place, and why if so. - - - - - fdoray@chromium.org - - The amount of CPU time a call to ComputeNativeWindowOcclusionStatus() takes. - - - - - - Removed 01/2020 as it was causing dead lock issues. crbug.com/1043353. - - stanisc@chromium.org - - Time spent inside CreateThread() Windows API call creating a single thread. - - - - - grt@chromium.org - - The Windows error code relating to a failed attempt to operate on a file or - a directory. - - - - - - - wfh@chromium.org - brucedawson@chromium.org - - The Windows version (base::win::Version) as reported by GetVersionEx(). This - is queried shortly after startup. - - - - - brucedawson@chromium.org - gab@chromium.org - - The value of TimeTicks::IsHighResolution(). Reported once per browser - session, on startup. - - - - - - Removed 03/2020 after insight about OpenXPS has lead to more general - question of XPS availability (either type). - - awscreen@chromium.org - thestig@chromium.org - - If the version of Xpsprint.dll is sufficiently modern to support OpenXPS. - Reported once per browser session, on startup. - - - - - stanisc@chromium.org - - Percentage of elapsed time the high resolution timer is activated. The usage - is reported by each of Chrome processes individually (without aggregation) - and logged every 10 minutes. - - - - - rkc@chromium.org - rockot@chromium.org - - Whether Hyper-V is enabled on this machine. Logged shortly after startup. - This metric will only be logged on Windows 10+. - - - - - - Removed 06/2019 - - wfh@chromium.org - brucedawson@chromium.org - - A boolean used to indicate when the Windows version reported by - GetVersionEx() and the Windows version reported by VerQueryValue() on - kernel32 do not match. This is queried shortly after startup. - - - - - pmonette@chromium.org - - Whether connection error has happened for the UtilWin service. Every time a - connection is made to the service, a "false" value is reported to - provide a baseline. Every time a mojo connection error happens, a - "true" value is reported, which typically means the utility - process crashed. - - - - - - - markchang@google.com - pmonette@chromium.org - - Indicates whether Chrome is pinned to the Windows taskbar for the current - user. Recorded shortly after startup. - - - - - pmonette@chromium.org - - Indicates whether a connection error occured between the browser and the - shell handler process. This is usually caused by a crash in the utility - process. This is logged every time the pinned state is queried. - - - - - pmonette@chromium.org - chrdavis@microsoft.com - - Indicates whether Chrome is pinned to the Windows taskbar for the current - user. Recorded shortly after startup. This is different from - Windows.IsPinnedToTaskbar in that we do not check if the pin to taskbar verb - is available on the shortcut and only relies on the shortcut existing in the - User Pinned folder. - - - - - - - wfh@chromium.org - brucedawson@chromium.org - - The Windows version (base::win::Version) as reported by VeryQueryValue() on - kernel32.dll. This is queried shortly after startup. - - - - - chrisha@chromium.org - pmonette@chromium.org - - The result of reading the InspectionResultsCache from disk. The cache is - read once at startup when the ModuleInspector needs it. - - - - - chrisha@chromium.org - pmonette@chromium.org - - The result of writing the InspectionResultsCache to disk. This is done every - time the ModuleDatabase becomes idle. - - - - - davidbienvenu@chromium.org - fdoray@chromium.org - - The number of Chrome browser windows in a given visibility state. This is - computed using ComputeNativeWindowOcclusionStatus() and is recorded every 10 - minutes. - - - - - pmonette@chromium.org - - Indicates whether a connection error occured between the browser and the - shell handler process. This is usually caused by a crash in the utility - process. This is logged every time SelectFile() function is called and the - WinOOPSelectFileDialog feature is enabled. - - - - - - - wfh@chromium.org - brucedawson@chromium.org - - The 32-bit hash of the lower-case parent process basename (e.g. - explorer.exe) of the main Chrome executable. Reported once during startup as - part of install verification. - - - - - - - wfh@chromium.org - brucedawson@chromium.org - - A 32-bit value formed from combining the minor and patch level of the - currently running Windows operating system. E.g. "Windows 10 OS Version - 1809 (Build 17763.503)" would be 17763 (0x4563), combined with 503 - (0x1F7) = 0x456301F7. If either minor or patch level exceeds the value that - can fit in a 16-bit unsigned integer, then this histogram will report 0. - Reported once, shortly after browser startup. - - - - - grt@chromium.org - - The state of an item in the filesystem following an operation on it. - - - - - rkc@chromium.org - rockot@chromium.org - - The processor family type. Logged shortly after startup. The value is - specified in the SMBIOS specification, section 7.5.2: - https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf - This metric will only be logged on Windows 10+. - - - - - rkc@chromium.org - rockot@chromium.org - - Whether virtualization has been enabled in the system firmware. Logged - shortly after startup. This metric will only be logged on Windows 10+. - - - - - zturner@chromium.org - Count of browser launches from a Windows tablet pc. - - - - grt@chromium.org - etiennep@chromium.org - - The number of files failed to be deleted in a single directory by the - browser process's tmp file deleter on Windows. These are files that were - left behind on previous runs when third-party software interfered with - Chrome's ability to delete its own temporary files. No value is emitted for - a directory if no delete attempts are made. Otherwise, the fail count will - be zero or more. - - - - - grt@chromium.org - etiennep@chromium.org - - The number of files deleted in a single directory by the browser process's - tmp file deleter on Windows. These are files that were left behind on - previous runs when third-party software interfered with Chrome's ability to - delete its own temporary files. No value is emitted for a directory if no - delete attempts are made. Otherwise, the success count will be zero or more. - - - - - - Removed 04/2020. Necessary data was collected and a decision was made. See - https://crbug.com/920704 for details. - - brucedawson@chromium.org - jmadill@chromium.org - - The ucrtbase.dll version, converted to a base::win::Version enum. This is - queried shortly after startup. - - - - - - Removed 10/2016 as this is enabled by default so provides no useful data. - - wfh@chromium.org - - Count of browser launches where Win32k renderer lockdown is enabled. - - - - - noms@chromium.org - The type of category clicked in the Windows Jumplist - - - - - Obsolete 07/06/2017 as we are no long recording this metric. - - chengx@chromium.org - - The number of jumplist icons requested to create per jumplist update. It is - recorded whenever UpdateJumpList() is called. - - - - - - Obsolete 07/06/2017 as we are no long recording this metric. - - chengx@chromium.org - - Time spent in CreateIconFiles(). This method is called whenever there is a - jumplist update and the JumpListIcons folder is empty. - - - - - - Obsolete 07/06/2016 as we are no long recording this metric. - - chengx@chromium.org - Time spent in DeleteDirectoryContentAndLogRuntime(). - - - - - Obsolete 04/25/2017 as we are no long recording this metric. - - chengx@chromium.org - Time spent in DeleteDirectoryAndLogResults(). - - - - - Obsolete 04/25/2017 as we are no long recording this metric. - - chengx@chromium.org - - This metric records the detailed delete result of JumpListIcons directory. - - - - - - Obsolete 04/25/2017 as we are no long recording this metric. - - chengx@chromium.org - - This metric records the detailed delete result of JumpListIconsOld - directory. - - - - - - Obsolete 12/13/2016 as we are no long recording this metric. - - chengx@chromium.org - - This metric is recorded when folder JumpListIcons is moved (can be rename or - copy and delete) to JumpListIconsOld. This happens when tabs are closed, - mostly visited URLs get updated, etc. There are several key steps in this - folder move operation. Before the move operation, there is another step that - JumpListIconsOld folder is deleted. The status of these steps are put - together and recorded in this metric. The failure of any of these steps is - suspected to be related to a known issue. - - - - - - Obsolete 03/10/2017 as it is replaced by DetailedFolderResultsDeleteUpdated. - - chengx@chromium.org - - This metric is recorded when folders JumpListIcons and JumpListIconsOld get - updated. These two folders are updated when tabs are closed, mostly visited - URLs get updated, etc. These two folders are updated as follows 1) - JumpListIconsOld with its content get deleted; 2) if step 1 succeeds, - JumpListIcons is moved, 3) if any of the previous steps fails, JumpListIcons - is deleted, 4) A new JumpListIcons folder is created. The status of these 4 - file operations are put together and recorded in this metric. The failure of - any of these file operations is suspected to be related to a known issue. - - - - - - Obsolete 03/20/2017. New metrics named WinJumplist.DeleteStatusJumpListIcons - and WinJumplist.DeleteStatusJumpListIconsOld are used instead. - - chengx@chromium.org - - This metric is recorded when folders JumpListIcons and JumpListIconsOld get - updated. These two folders are updated when tabs are closed, mostly visited - URLs get updated, etc. These two folders are updated as follows 1) - JumpListIconsOld with its content get deleted; 2) if step 1 succeeds, - JumpListIcons is renamed to JumpListIconsOld, 3) if any of the previous - steps fails, JumpListIcons is deleted, 4) A new JumpListIcons folder is - created if deletion of JumpListIcons' content succeeds (only fail to delete - the directory is okay). The status of these 4 file operations are put - together and recorded in this metric. The failure of any of these file - operations is suspected to be related to a known issue. - - - - - - Obsolete 04/25/2017 as we are no long recording this metric. - - chengx@chromium.org - - This metric records whether the folder JumpListIcons exists; and if it does, - whether it is empty or non-empty. - - - - - - Obsolete 04/25/2017 as we are no long recording this metric. - - chengx@chromium.org - - This metric records whether the folder JumpListIconsOld exists; and if it - does, whether it is empty or non-empty. - - - - - - Obsolete 12/08/2016. DetailedFolderMoveResults is used for more detailed - analysis. - - chengx@chromium.org - - This metric is recorded when folder JumpListIcons is moved (can be rename or - copy and delete) to JumpListIconsOld. This happens when tabs are closed, - mostly visited URLs get updated, etc. There are 3 possible steps in this - folder move operation. Before the move operation, there is another step that - JumpListIconsOld folder is deleted. The status of these steps are put - together and recorded in this metric. The failure of any of these steps is - suspected to be related to a known issue listed below. - https://bugs.chromium.org/p/chromium/issues/detail?id=179576 - - - - - - Obsolete 12/13/2016, as we are now recording DetailedFolderResults. - - chengx@chromium.org - - This metric is recorded when folders JumpListIcons and JumpListIconsOld get - updated. These two folders are updated when tabs are closed, mostly visited - URLs get updated, etc. These two folders are updated as follows 1) - JumpListIconsOld with its content get deleted; 2) JumpListIcons is moved, 3) - A new JumpListIcons folder is created. The status of these three file - operations are put together and recorded in this metric. The failure of any - of these file operations is suspected to be related to a known issue. - - - - - - Obsolete 07/10/2017 as it's no longer needed. - - chengx@chromium.org - - The time interval between two adjacent update notifications if it's less - than 3500 ms. - - - - - - Obsolete 07/23/2017 as it's no longer needed. - - chengx@chromium.org - - The time interval between two adjacent update notifications. A zero value - indicates the interval is greater than 3500 ms. - - - - - - Obsolete 06/22/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in OnFaviconDataAvailable(). - - - - - Obsolete 07/23/2017 as it's no longer needed. - - chengx@chromium.org - - The ratio of the duration spent adding the most-visited category compared to - the duration spent adding the recently-closed category, multiplied by 10. - - - - - - Obsolete 06/22/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in StartLoadingFavicon(). - - - - - Obsolete 04/20/2017 as it's no longer accurate due to the code change. - - chengx@chromium.org - - Time spent in UpdateJumpList(). This method is called whenever there is a - jumplist update. - - - - - - Obsolete 07/26/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in JumpListUpdater::AddCustomCategory. - - - - - Obsolete 07/10/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in JumpListUpdater::AddTasks. - - - - - Obsolete 07/26/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in JumpListUpdater::BeginUpdate. - - - - - Obsolete 07/26/2017 as it's no longer needed. - - chengx@chromium.org - Time spent in JumpListUpdater::CommitUpdate. - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - Incremented each time the TimeTicks field trial runs on a machine with - multiple cores, but failed to change thread affinity. Broken down by Windows - version. - - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - The smallest non-zero delta reported by subsequent calls to - QueryPerformanceCounter. - - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - True if the CPU's timestamp counter ticks at a constant rate regardless of - CPU frequency. - - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times the TimeTicks field trial failed because - QueryPerformanceCounter ticked backwards. Broken down by Windows version. - - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times the TimeTicks field trial succeeded. Broken down by - Windows version. - - - - - - Removed 01/2017. - - Please list the metric's owners. Add more owner tags as needed. - - The number of times the TimeTicks field trial ran for comparison with - WinTimeTicks.VersionSuccess. Broken down by Windows version. - - - - - - Removed Jan 2020. - - hiroshige@chromium.org - nhiroki@chromium.org - - Type of worker top-level script's request URL's origin, relative to parent - execution context's origin, recorded on each successful classic dedicated - worker creation. - - - - - - Removed July 2019. - - kinuko@chromium.org - - Worker thread load, i.e. percentage of time spent on running tasks. This - metric is emitted at most once per kWorkerThreadLoadTrackerReportingInterval - sec per worker thread amortized. E.g. if a worker ran a single task for X - seconds and then went to idle for Y seconds before it shuts down, and - assuming the interval rate was 1 sec, we get X samples for 100% and Y - samples for 0%. - - - - - - Removed on 2018-02. - - nhiroki@chromium.org - The time taken for running a debugger task on WorkerThread. - - - - nhiroki@chromium.org - chrome-worker@google.com - Records the exit code of WorkerThread. - - - - - Removed July 2019. - - kinuko@chromium.org - - The amount of time a worker thread ran for. Starts recording when a worker - scheduler for the thread is created, and stops when the scheduler is shut - down. - - - - - - Removed on 2018-02. The sample count was overflowing. crbug.com/809672. - - nhiroki@chromium.org - The time taken for running a worker task on WorkerThread. - - - - ainslie@chromium.org - edwardjung@chromium.org - Number of times that each menu item is clicked. - - - - - Removed on 2020-04. Bucket sizes are not very useful for measuring jank. The - only user of AnimationFrameTimeHistogram. - - kkimlabs@chromium.org - - Frame times of the Android wrench menu opening animation. For example, if - the menu opening animation runs exactly at 60fps for a second, then each - frame time is 16ms, and a total of 60 values of 16ms are recorded. If the - animation is janky, we will see values greater than 16ms in the histogram. - - - - - rpop@chromium.org - - The number of times each tab or window restore option in the Recent Tabs - submenu is clicked. - - - - - ainslie@chromium.org - edwardjung@chromium.org - - The time a user takes to select a menu item after opening the menu. - - - - - kkimlabs@chromium.org - - Time difference between touch down and touch up on Android wrench button. - - - - - huangdarwin@chromium.org - src/ui/base/clipboard/OWNERS - - Counts how often the X11 server fails to register an atom. Recorded when - ::XInternAtom fails (returns None). Failure rates will inform whether we - implement error handling. https://crbug.com/1000919 - - - - - panicker@chromium.org - - Records occurence of async XHR during page dismissal state (unload, - beforeunload, pagehide etc). - - - - - foolip@chromium.org - - Records the time spent in sync XHR requests on the main thread. - - - - - foolip@chromium.org - - Records the time spent in sync XHR requests in a worker thread. - - - - - panicker@chromium.org - - Records occurence of sync XHR during page dismissal state (unload, - beforeunload, pagehide etc). - - - - - kdillon@chromium.org - panicker@chromium.org - - Records occurence of sync XHR requests during page dismissal state (unload, - beforeunload, pagehide etc) that were forbidden. - - - - - - Removed 03/2020 - - alcooper@chromium.org - xr-dev@chromium.org - - Indicates which VR APIs are installed. Recorded shortly after startup. - - - - - alcooper@chromium.org - mlamouri@google.com - xr-dev@chromium.org - - Indicates which XR runtime was used for a session. Recorded when the session - was successfully created. - - - - - - Removed 02/2020 - - alcooper@chromium.org - xr-dev@chromium.org - - The action that triggered the transition into Chrome in VR, either from 2D - or another VR app. - - - - - - Removed as of 06/2020. - - alcooper@chromium.org - mlamouri@chromium.org - xr-dev@chromium.org - - Records the actions of a user consent dialog which is displayed on - requesting an XR session. - - - - - - Removed as of 06/2020. - - alcooper@chromium.org - mlamouri@chromium.org - xr-dev@chromium.org - - Time the user takes to abort the consent flow by clicking on the - window-close system button of a session request consent dialog. - - - - - - Removed as of 06/2020. - - alcooper@chromium.org - mlamouri@chromium.org - xr-dev@chromium.org - - Time the user takes to click on the allow-and-enter-VR button on a session - request consent dialog. - - - - - - Removed as of 06/2020. - - alcooper@chromium.org - mlamouri@chromium.org - xr-dev@chromium.org - - Time the user takes to click on dont-allow button on a session request - consent dialog. - - - - - - Removed 02/2020 - - alcooper@chromium.org - xr-dev@chromium.org - - The action that triggered VR presentation, which is the display of web - content on a VR device. - - - - - alcooper@chromium.org - xr-dev@chromium.org - - Records which reference space was requested when a site calls - XRSession.requestReferenceSpace(). - - - - - alcooper@chromium.org - xr-dev@chromium.org - - Records which reference spaces are successfully created when the promise - returned by XRSession.requestReferenceSpace() is resolved. - - - - - - Removed July 2019. This was being tracked in case the assumptions about - feature availability based on platform version turned out to be incorrect, - but it appears that this is working as intended. The webxr-render-path flag - that could be used to override this at runtime was previously removed in - https://crrev.com/c/1487074. - - klausw@chromium.org - - Records the WebXR/WebVR render path used for presentation on presentation - start. The render path is affected by overrides and device capabilities. - - - - - hfung@chromium.org - - The number of results (either query or URL) from ZeroSuggest. This is set - every time a successful response from ZeroSuggest is received, which can be - every time the user focuses on the omnibox. - - - - - hfung@chromium.org - - The number of query results returned from ZeroSuggest. This is set every - time a successful response from ZeroSuggest is received, which can be every - time the user focuses on the omnibox. - - - - - hfung@chromium.org - - The number of URL results returned from ZeroSuggest. This is set every time - a successful response from ZeroSuggest is received, which can be every time - the user focuses on the omnibox. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed M80. Only affects one histogram, which is deprecated. - - msalama@chromium.org - msarda@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated January 2019 as we're transitioning to only using - SubresourceFilter data. - - - - - Deprecated January 2019 as we're transitioning to only using - SubresourceFilter data. - - - - - Deprecated January 2019, as these metrics only use subresource filter data - and metrics are being split out by visibility. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 09/2019. Replaced with NonAdFrames.Aggregate.Total2. - - - - - - - - - - - - Deprecated 08/20 in favor of AdFrames.PerFrame.PeakWindowedPercent2. - - - - - - Deprecated 08/20 in favor of AdFrames.PerFrame.PeakWindowStartTime2. - - - - - - Deprecated 06/19 in favor of AdFrames.PerFrame.PercentUsage2. - - - - - Deprecated 07/19 in favor of AdFrames.PerFrame.PeakWindowedPercent. - - - - - Deprecated 08/20 in favor of AdFrames.PerFrame.TotalUsage2. - - - - - - - - - - - - - - - - - - - - - - - Deprecated 08/20 in favor of Adframes.Aggregate.TotalUsage2. - - - - - - Deprecated 08/20 in favor of FullPage.PeakWindowedPercent2. - - - - - - Deprecated 08/20 in favor of FullPage.PeakWindowStartTime2. - - - - - - Deprecated 07/19 in favor of AdFrames.FullPage.PeakWindowedPercent. - - - - - Deprecated 08/20 in favor of FullPage.TotalUsage2. - - - - - - - - - - - - - Removed 01/2020, did not provide useful information on ad CPU performance. - - - - - Removed 01/2020, did not provide useful information on ad CPU performance. - - - - - - - - - - - - - - - - - - - - - - - Deprecated 09/2019. Replaced with Total2. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 01/2020. Replaced with PercentAdFrames suffix. - - - - - - Deprecated 09/2019. Replaced with PercentAds2 suffix. - - - - - - Deprecated 09/2019. Replaced with PercentAds2 suffix. - - - - - - Deprecated 09/2019. Replaced with PercentAds2 suffix. - - - - - - - Removed 01/2020. Replaced with PercentAdFrames suffix. - - - - - - - - - - - Deprecated 09/2019. Replaced with PercentNetwork2. - - - - - - - - - - - - - - - Deprecated 09/2019. Replaced with PercentSameOrigin2. - - - - - - Deprecated 09/2019. Replaced with SameOrigin2. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in favor of 'Download' - - - - - - - State does not exist - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Original code deleted in a refactoring. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 03/2018 with Mash AppList refactoring. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2016/03. The async set-as-default experiments are finished. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of at least 2013. Current autofill experiments rely on Finch - rather than a custom experimentation setup. - - - - - - - - - - - - - - - - - - - - - - - - - - - - sujiezhu@google.com - jsaul@google.com - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced 2019-04 by SignedInAndSyncFeatureEnabled and SyncPaused. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced with Autofill.WalletAddresses2 in 2018/12. - - - - - - Replaced with Autofill.WalletAddresses2 in 2018/12. - - - - - - - - - - - - - Removed in M84. - - - - - Removed in M84. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of May 2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 10/2018 with the addition of CssImage and Unknown. - - - - - - - - - - - - - Deprecated 11/2017 with removal of Display List Canvas 2D mode. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced with Blink.Canvas.ToBlob.CompleteEncodingDelay in 2017/12. - - - - - - - - - - - - - - - - Removed in Oct 2016 - - - - - Removed in Oct 2016 - - - - - Removed in Oct 2016 - - - - - - - Removed in Oct 2016 - - - - - Removed in Oct 2016 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Renamed to ImageFetcherClients on 04/2019. - - - - - This feature was deprecated in M74 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in M77. - - - - - Deprecated in M77. - - - - - - - - - - - Noticed unused 2019-10-09 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed January 2018, as the limit is independent of the backend type. - - - - - Removed January 2018, as the limit is independent of the backend type. - - - - - Removed January 2018, as the limit is independent of the backend type. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Experiments no longer active. - - - - - - - - - - - - - - - - - - - - - - - - Experiments no longer active. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - rsleevi@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 8/2013. This histogram only considered the leaf certificate - expiry date as a proxy for whether a certificate was in-scope for the BRs, - but did not consider the issuance date. As some CAs have issued long-lived - certs prior to the BRs, this disproportionately reported those certs as - being subject to the BRs, but non-compliant, when in reality they're not - subject. - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 01/2016. CertCacheTrial has been removed. - https://crbug.com/522312 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed and renamed to MobileStartup.ToolbarFirstDrawTime2 due to double - reporting bug (see https://crbug.com/857508). - - - - - No longer useful, deprecated in M82. - - - - - No longer useful, deprecated in M82 (see https://crbug.com/1053190). - - - - - Removed and renamed to MobileStartup.ToolbarFirstFocusTime2 due to double - reporting bug (see https://crbug.com/857508). - - - - - No longer useful, deprecated in M82. - - - - - - - - - - - - - - - - - - - - Removed Jan 2018 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - These were temporary metrics intended to understand whether high/low - resolution clocks adversely impact page load metrics. After collecting a few - months of data it was determined that clock resolution doesn't adversely - impact our metrics, and that these histograms were no longer needed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in 03/2020 because changes in the data are difficult to reason about - as the number of layers also tends to change at the same time. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 02/2020. Split into - SubmitCompositorFrameToPresentationCompositorFrame.StartDrawToSwapStart - and SubmitCompositorFrameToPresentationCompositorFrame.SwapStartToSwapEnd. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - Removed on 9/2019: metric is not monitored for the UI compositor. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced by SendBeginMainFrameToCommit.BeginMainSentToStarted of - CompositorLatency metrics. - - - - - - - - - - - - - - - - - - - - - These used an old bucketing scheme that that had too many buckets and were - an inefficient usage of UMA bandwidth. They have been replaced by new - metrics of the same name with a "2" appended to them. - - - - - - - - - - - - - - - - - - - - - Estimates don't need long term monitoring. - - - - - - - - - - - - - - - - - - - Estimates don't need long term monitoring. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 6/2019. No longer used. - - - - - - - - - - Removed 04/2020. No longer used. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed from code as of 05/2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated and removed from code as of 02/2017. - - - - - Deprecated and removed from code as of 02/2017. - - - - - - - - - - Removed 07/2019. - - - - - - - - Deprecated and removed from code as of 07/2018. - - - - - - - - - - - - - - - - - - - - - - Removed from code as of 04/2020. - - - - - - - - - - Removed from code as of 04/2020. - - - - - - - - - - - - - - - - - - - - - - - This feature was deprecated in M74 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 2020-01 - - - - - Deprecated as of 2020-01 - - - - - Deprecated as of 2020-01 - - - - - - - - - - - - - - - - Removed 9/2016. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Functionality removed in M77. - - - - - - - - - - Removed; refer to Experimental.Bytes.Network - - - - - - - - - - - - - - - - - - - - - - - - - Functionality removed in M77. - - - - - Functionality removed in M77. - - - - - Functionality removed in M77. - - - - - Functionality removed in M77. - - - - - Functionality removed in M77. - - - - - Functionality removed in M77. - - - - - - - - - - - - Obsoleted in March 2020. - - - - - - - Removed 04/2018. - - - - - - - - - - Removed 09/2016. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in Feb 2016. - - - - - - - - - - - - - - - - - - - Removed 2018/04. - - - - - - - - - Obsoleted March 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - tbansal@chromium.org - - - - - - - Obsoleted in March 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced by version without network-type breakdown in June, 2018. - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - Replaced by KB version in October, 2017. - - - - - - - - - - - - - - - - - - - Removed Oct 2018 - - - - - - - - - - - - - - Deprecated March 2017 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Marked obsolete 01/2020. Hasn't been recorded for some time. - - - - - - - - - - - - - - - - Removed as of 12/2013. Default pinned apps trial is finished. - - - - - - - - - - Removed August 2016 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - Deprecated April 2015 - - - - - - - - Deprecated October 2017 - - - - - - Deprecated April 2015 - - - - - - Deprecated October 2017 - - - - - - Deprecated April 2017 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 11/2018 in issue 894963. - - - - - - - - - - - - Removed 11/2018 in issue 894963. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated and removed from code as of 01/2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed after M72 since no longer needed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Affected histograms deprecated 09/2019. - - - - - - - - - - - - Affected histograms deprecated on 2019-06-17. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 08/2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 03/2018. We'd learned enough from this metric and it made - no sense to keep it around. - - - - - Deprecated as of 03/2018. We'd learned enough from this metric and it made - no sense to keep it around. - - - - - Deprecated as of 03/2018. We'd learned enough from this metric and it made - no sense to keep it around. - - - - - Deprecated as of 03/2018. We'd learned enough from this metric and it made - no sense to keep it around. - - - - - Deprecated as of 03/2018. We'd learned enough from this metric and it made - no sense to keep it around. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced by GenerateRequest. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - calamity@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in 2019-11. Equivalent values are tracked by - Apps.HomeLauncherTransition.AnimationSmoothness.* histograms. - - - - - Removed on 2019-07. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 01/2020 since the histogram indicators were stable. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - poromov@chromium.org - zmin@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - emaxx@chromium.org - igorcov@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 07/2020. Replaced with TotalLatencyToSwapBegin suffix - which measures what we actually intended to measure. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 08/2017. Replaced with ExpectedQueueingDurationThreshold. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated and removed from code as of 05/2015. - - - - - Deprecated and removed from code as of 05/2015. - - - - - Deprecated and removed from code as of 05/2015. - - - - - - - - - - - - - - - - - - Removed as of Jan 2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated and removed from code as of 04/2018. - - - - - - - - - - - - - - - Removed as of 12/2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 4/2019 in favor of ProtoDB.InitStatus.*. - - - - - Removed 4/2019 in favor of ProtoDB.LoadKeysSuccess.*. - - - - - - Removed 4/2019 in favor of ProtoDB.LoadEntriesSuccess.*. - - - - - - Removed 4/2019 in favor of ProtoDB.UpdateSuccess.*. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-09. - - - - - - - - - - - - - - - - - - - - Deprecated as of 12/2016. - - - - - Deprecated as of 12/2016. - - - - - Deprecated as of 9/2013. - - - - - - - - - - Deprecated as of 12/2016. - - - - - Deprecated as of 12/2016. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-04. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-06. - - - - - - - - - - - - - - - - Removed 2019-09. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2017-9. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - kmadhusu@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - vmiura@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - Expired in M75. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 05/17/2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 11/29/2016. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed by PageLoad.PaintTiming.NavigationToFirstContentfulPaint. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Renamed to RemoveFile 2020-01. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All relevant histograms have been marked as obsolete as of Sep 2016. - - macourteau@chromium.org - - - - - - - - - - - - - Removed as of 7/2015. - - - - - - - - - - - - - - - - - - - - - - - - - - lizeb@chromium.org - pasko@chromium.org - - - - - - - - - - - - - - Removed 10/2016. - - - - - - - - Removed 11/2016. - - - - - - - - - Removed 11/2016. - - - - - - - - - - - - - - - - Code removed long ago. - - pauljensen@chromium.org - - - - - - - - Removed 04/2020. See crrev.com/c/2129507 - - - - - - - - - - - - - - - - - - - - - - - - - - - Unused as of 03/2018 - - - - - - Replaced with IPH_ContextualSearchWebSearch. - - - - - - Replaced with IPH_ContextualSearchPromotePanelOpen. - - - - - - - Replaced with IPH_ContextualSearchPromoteTap. - - - - - - - This feature was deprecated in M74 - - - - - - - - - - - - - - - - - - - - This feature was deprecated in M79 - - - - - - This feature was deprecated in M79 - - - - - - - - - - - - - This feature was deprecated in M79 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This metric is now only recorded after the main message loop starts and no - longer distinguishes the first 30 seconds as "startup". - Startup.BrowserMessageLoopStartTime can be used for the startup phase - (before the loop is running) and Startup.FirstWebContents.NonEmptyPaint3 can - be used for the user-visible startup performance. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2017-10. - - - - - - - - - - - Removed 2020-01. - - - - - - - - - Removed 2017-10. - - - - - - - - - Removed 2020-01. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - cmumford@chromium.org - - - - Renamed to RemoveDir on 2020-01. - - - - - Renamed to RemoveFile on 2020-01. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated since 2019-10. - - - - - - - - - - Deprecated since 11/18. - - - - - - Deprecated since 08/18. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 08/2016. - - - - - - - - - - - Removed as of September 20, 2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2013-04 in favor of LevelDBEnvRetry. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - cmumford@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 12/2019. Recording suffixed version of - PageLoad.InteractiveTiming.FirstInputDelay4 instead. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed July 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removes as of 6/2020. We now get enough cache hit information from - Renderer4.SoftwareImageDecodeState* and don't need to divide it into tile - bins. - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 12/2017. The low memory margin is a per-platform constant. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TopCat model deprecated 2020-06. - - - - - - Removed 2020-02-01 because elapsed time should be measured by clients, if - they need it. - - - - - - - - Removed 2020-02-01 because elapsed time should be measured by clients, if - they need it. - - - - - - - - Removed 2020-02-01 because elapsed time should be measured by clients, if - they need it. - - - - - - - - - - - - - - - - - - - - Removed 2020-02-01 because elapsed time should be measured by clients, if - they need it. - - - - - Deprecated 07/2019, because we change to record total (shared+unshared) - memory rather than only private memory. Replaced by - MachineLearningService.TotalMemoryDeltaKb. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 5/15/2019. - - - - - - - - Removed as of 5/15/2019. - - - - - Removed as of 5/15/2019. - - - - - Removed as of 5/15/2019. - - - - - - - - - - - - - - - - - - Removed 06/2020. No longer needed. - - - - - - - - - Removed 06/2020. No longer needed. - - - - - - - - - - - - Removed 10/2019 in issue 1000058; no longer needed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed from code as of 07/2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in March 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed from code as of 08/2016. - - - - - - - - - Removed from code as of 08/2016. - - - - - - - - - - - - Deprecated and removed from code as of 05/2015. - - - - - - - - - - Removed from code as of 03/2018. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Replaced by the likely named entry. It had a misleading name as it also - has the before-unload time discounted. - - - - - - - - - - - - - - - - - - - - - - - Removed as of July 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of June 2017, in favor of - ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time_WorkerStartOccurred_NavigationPreloadEnabled. - - - - - - - - - Removed as of June 2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 07/2020. Not used in active investigations. - - mef@chromium.org - pauljensen@chromium.org - - - - - - - - - - - - - Removed 2020-06. - - - - - - - - - - - - - - - - - - - - - - Removed 02/2018. - - - - - - - - - - - - - - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - Deprecated and removed from code as of 10/2015. - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - csharrison@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - tbansal@chromium.org - - - - - - - tbansal@chromium.org - - - - - - - - - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed April 2019, replaced by - NewTabPage.SearchSuggestions.RequestLatencyV2. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Hasn't been used for a while, as of 2016-07. - - - - - - - - - - - - - Used for experiment but was never launched, as of 2019-07. - - - - - - Hasn't been used for a while, as of 2016-07. - - - - - Not used anymore as of 2016-07. - - - - - Has never been used. - - - - - Has never been used. - - - - - Has never been used. - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 06/2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed October 2017 (feature enabled by default). - - - - - - - - - - Removed in June 2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 01/2017. - - - - - Deprecated as of 01/2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - - - - - - - - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - Deprecated 01/2017. - - - - - Deprecated 01/2017. - - - - - - - - - - - - - - - - - - - - - - Obsoleted in Apr 2020. - - - - - - - Removed 01/2018. - - - - - - - - - - - - - Obsoleted in M81. - - - - - - - - - - Obsoleted in M81. - - - - - - - - - - Removed 01/2018. - - - - - - - - - - - - - Deprecated 08/2017. - - - - - Deprecated 08/2017. - - - - - Deprecated 08/2017. - - - - - Deprecated 08/2017. - - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - Deprecated 01/2018. - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2018-07 as the non bucketed metrics are enough for future reference. - - - - - - - - - - - - - Removed 2016-05 as the OffDomainInclusionDetector was removed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed March 2019 - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 12/2019 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 05/2020 in favor of recording on update and load of the - prediction model. - - - - - - - - - - - - - - - - Removed in M84. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Experiments no longer active. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in favor of PageLoadBackgrounded2. - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in favor of PaintTiming equivalent. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - deprecated in favor of PageLoad.AbortTiming.Background.* - - - - - - - - - - - - - - - - - - - Removed 5/2019 - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 5/2019 - - - - - - - - - - - - - - - Removed in favor of PageLoad.Clients.AMPCache2.*. - - - - - - - - - - - - Removed in favor of PageLoad.Clients.AMP.*. - - - - - - - - - - - - Removed September 2018 - - - - - - - - - - - Deprecated 05/2018. - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 10/2018 - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in August 2020 as the behavior is launched - - - - - - - - - - - - Deprecated in favor of Clients.FromGoogleSearch. - - - - - Deprecated in favor of Clients.FromGoogleSearch. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Functionality removed in M77. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 12/2018. - - - - - - Functionality removed in M77. - - - - - - - - - - - - - - - - - - - - - - Functionality removed in M86. - - - - - - - - - - - - - Renamed to Clients.Protocol.H11 - - - - - - - - - - - - - - - - - Removed at M53 in favor of LoadType.Reload. - - - - - - - - - - - Deprecated 12/2018. - - - - - - Functionality removed in M77. - - - - - - - - - - - Removed at M66. No longer recorded. - - - - - - - - - Removed at M66. No longer recorded. - - - - - - - - - - - - - - - - - - - - Deprecated on June 2018 (M69) in favor of Clients.NoServiceWorker2. - - - - - - Deprecated on June 2018 (M69) in favor of Clients.ServiceWorker2. - - - - - - - - - - - - - - - - - Deprecated in favor of PaintTiming equivalent. - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed May 2018 (M68) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed May 2018 (M68) - - - - - - - - - - - - - - - - - - - - - - - - - Removed May 2018 (M68) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in favor of - PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.Reload. - - - - - - - - - - - - - Deprecated in favor of UserGesture/BrowserInitiated. - - - - - Deprecated in favor of UserGesture/BrowserInitiated. - - - - - Deprecated in favor of UserGesture/BrowserInitiated. - - - - - - - - - - - Deprecated in favor of UserGesture. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 03/2016. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 03/2019. - - - - - - - - - - - Removed 03/2019. - - - - - - - - - - - - - - - - - - Replaced by SavedPasswordEntry+SyncPasswordEntry+NonSyncPasswordEntry in - M77. - - - - - - - Replaced by ProtectedPasswordEntry in M62. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 09/2020. Made decision in issue 1128111 to remove unused payment - sheet histograms. - - - - - Renamed to PaymentMethod. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed on 2020-06-19 as most permissions are no longer exposed to - insecure origins to begin with, and even those few that are recorded no - useful data any longer. - - - - - Removed on 2020-06-19 as most permissions are no longer exposed to - insecure origins to begin with, and even those few that are recorded no - useful data any longer. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in M82 as the experiment has been stopped. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 12/2017 in Issue 781644. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated March 2018 - - - - - - - Deprecated March 2018 - - - - - Deprecated March 2018 - - - - - - - - - - - - - Removed July 11 2017. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed August 2016 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - deprecated May 10 2012 - - - - - - - - - - - - - - - - - - - - - - - - Removed August 2016 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated October 2017 - - - - - - - Deprecated October 2017 - - - - - - Deprecated April 2017 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in M79. - - - - - - - - - - - - Functionality removed in 2018. - - - - - - Functionality removed in M86. - - - - - Removed in M84. - - - - - Functionality removed in M77. - - - - - - - Functionality removed in M86. - - - - - - - - - - - - - - - tengs@chromium.org - gzadina@google.com - - - - - - - - - - - - - - - - - - - - - - - - - Removed 03/2018. - - - - - Removed 03/2018. - - - - - Removed 03/2018. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use *.Custom.ServiceDiscardableManager instead. - - - - - Use *.Custom.ServiceDiscardableManager.AvgImageSize instead. - - - - - Use *.Custom.ServiceTransferCache instead. - - - - - Use *.Custom.ServiceTransferCache.AvgImageSize instead. - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2019-05 - - - - - - - - - - - - - Deprecated M81. - - - - - Deprecated 3/2019. - - - - - - - - - - Deprecated M81. - - - - - - - Removed 03/2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 8/2013. No longer tracked. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 04/2018. - - - - - - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - Deprecated 10/2015. - - - - - - - - Deprecated 04/2016. - - - - - - - - - - - - - - - - - - - - - - - - - dschinazi@chromium.org - src/net/quic/OWNERS - - - - - - - - - - - - - - - Obsolete as of M80. Only used for partial raster, which has shipped for a - long period of time / is not being tuned. - - - - - - - - - - - - - - - - - - Replaced by RasterTaskSchedulingDelayNoAtRasterDecodesType. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 01/2020. Data is not used. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 04/2018. No longer recorded. - - - - - - Deprecated as of 04/2018. No longer recorded. - - - - - Deprecated as of 04/2018. No longer recorded. - - - - - Deprecated as of June 2018. No longer recorded. This was also being - recorded when the page had a controller with no fetch event, which usually - means the service worker was not running. - - - - - - - - - - - - - - - - - - - - - Removed March 2019. - - - - - - - - - - - - - - - - - - Removed Febrary 2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in 10/2016. - - - - - - - - - - - - - - - This experiment was turned down, see https://crbug.com/703188. - - - - - - - - - - - - - - This experiment was turned down, see https://crbug.com/768325. - - - - - - - This experiment was turned down, see https://crbug.com/768325. - - - - - - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - - - - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - - - - - - - - - - - - - - - - Removed September 2016. No longer recorded. - - - - - - - - - - - - - - Removed 1/2016 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in M73. See https://crbug.com/916192 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 4/2015. - - - - - - - - - - Removed in or before M86. - - - - - - - - - Removed in or before M86. - - - - - - - - - - - - - - - - - - - - - - - - Removed in or before M86. See SafeBrowsing.Pref.SawInterstitial or - SafeBrowsing.Pref.Extended.* - - - - - - - - - - - - Removed June 2020. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 8/2019. Was used to better understand DLL prefetching. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated in 9/2016. - - - - - - - Removed in M79, not interesting to keep track of. - - - - - - - - - deprecated November 10 2012 crrev.com/167056 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - cthomp@chromium.org - estark@chromium.org - - - - EV_SECURE level was removed in May 2020. - - - - - HTTP_SHOW_WARNING level was removed in Sep 2019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - jeffreycohen@chromium.org - sebsg@chromium.org - tgupta@chromium.org - - - - - - - - - - - - The affected histogram is obsolete (5/20). - - jeffreycohen@chromium.org - sebsg@chromium.org - tgupta@chromium.org - - - - - - - - - - - - The affected histogram is obsolete. - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 5/2016 because geofencing got removed. - - - - - - - - - This experiment was turned down, see https://crbug.com/616502. - - - - - This experiment was turned down, see https://crbug.com/616502. - - - - - This experiment was turned down, see https://crbug.com/616502. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This experiment was turned down, see https://crbug.com/616502. - - - - - - - - - - - This experiment was turned down, see https://crbug.com/616502. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 07/2017. Replaced by ExistingUnreadyProcess and - ExistingReadyProcess. - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 07/2017. Replaced by StartWorkerExistingUnreadyProcess - and StartWorkerExistingReadyProcess. - - - - - - - - - - - - - Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Put and - ServiceWorkerCache.Cache.Delete. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.Cache.Renderer.DeleteOne. - - - - - Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Keys2 in - order to use a larger maximum value. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.Cache.Renderer.Keys. - - - - - Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Match2 in - order to use a larger maximum value. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.Cache.Renderer.Match.Hit. - - - - - Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.MatchAll2 - in order to use a larger maximum value. - - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.Cache.Renderer.PutOne and - ServiceWorkerCache.Cache.Renderer.PutMany. - - - - - - - - Removed as of 02/2019. Not replaced with any new histogram. - - - - - - - - - Removed as of 02/2019. Not replaced with any new histogram. - - - - - - - - - Removed as of 02/2019. Replaced by - ServiceWorkerCache.Cache.Renderer.MatchIgnoreSearch. - - - - - - - - - Removed as of 02/2019. Not replaced with any new histogram. - - - - - - - - wanderview@chromium.org - - - - - - - - - wanderview@chromium.org - - - - - - - - - - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.CacheStorage.Renderer.Delete. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.CacheStorage.Renderer.Has. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.CacheStorage.Renderer.Keys. - - - - - Deprecated as of 08/2018. Replaced by - ServiceWorkerCache.CacheStorage.Match2 in order to use a larger maximum - value. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.CacheStorage.Renderer.Match. - - - - - Deprecated as of 02/2019. Replaced by - ServiceWorkerCache.CacheStorage.Renderer.Open. - - - - - - - - Removed as of 02/2019. Not replaced with any new histogram. - - - - - - - - wanderview@chromium.org - - - - - - - - - - - - wanderview@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed June 2018 (M69). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 06/2019. - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - - - - - - - - - Removed in M82 as the experiment has been stopped. - - - - - - - - - - - Removed in M82 as the experiment has been stopped. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-01. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020-09 as the WebRTC experiment is shut down. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2018-03. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 12/2014. - - - - - - - - - - - - - - - - - - - - - - - - Removed in favor of Signin.Reconciler.Duration.UpTo3mins. - - - - - - - - - - - - - - - - Deprecated as of 2018-8. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 2019-03. - - - - - - - - - - - - Removed in June 2019 / M77. Some old data have been saved in a - Google-internal doc at - https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 - - - - - - - - - - - - Obsolete: mus+ash project was canceled, and these metrics are no longer - useful. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed on 04/2020. It is added to only Graphics.Smoothness metrics under - the name of SmoothnessSequenceTypes.Universal - - - - - - - - - - - Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - - - - - - - - - Removed on 9/2020. No longer needed after 'Universal' metric was - deprecated. - - - - - - - - - - Removed on 9/2019. Did not provide enough information about latency. - - - - - - - Removed in 9/2020, due to over penalize smoothness. - - - - - - - - - - Removed on 9/2020. No longer needed after 'Universal' metric was - deprecated. - - - - - - - - - - - - - - Removed on 9/2020. No longer needed after 'Universal' metric was - deprecated. - - - - - - - - - - - - - - - - - - - - - - - Removed as of 03/2015. - - - - - - - - - - - - - - - - - - - - - - - Deprecated 10/2018. Replaced by ESET suffix. - - - - - Deprecated 10/2018. Replaced by URZA suffix. - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 07/2014. - - willchan@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - costan@google.com - - - - - - - Deprecated as of 2016-1 (http://crrev.com/372327). - - - - - - - - - - - - - Deprecated July 11 2017. - - - - - - - - - - - Deprecated as of 2013-07. - - - - - - - - - - - - - - - - - - - - Removed 2018-02-06. - - costan@google.com - - - - - - - - - Removed 2011-06-01. - - - - - - - - - - - - - - - - - - - - Removed 10/2019. Since Startup.FirstWebContents.MainFrameLoad2 is no longer - tracked, the non-suffixed reason is always for - Startup.FirstWebContents.NonEmptyPaint2 and the suffix does not provide - additional information. - - - - - - - - - - - Obsolete as of Jan 2020. Was a diagnosis metric when warm/cold - distributions didn't look as expected but recording the suffix for every - startup metric was deemed overkill. Use Startup.Temperature and - Startup.BrowserMessageLoopStartHardFaultCount to diagnose discrepancies. - - - - - - - - - - - - - - - - - - - - - - - - Obsolete as of Jan 2020. - - - - - Obsolete as of Jan 2020. - - - - - - - - - - - - - - - - - - - - - - - Removed as of 10/2014. - - - - - - - - - - Removed as of Jan 2020. - - - - - - - - - Removed as of June 2017. - - - - - - - - - - - - - Removed as of June 2017. - - - - - - - - - - - Removed on 12/18. Metric wasn't used for anything and wasn't useful. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed May 2018 - - - - Deprecated 11/17, no longer used. - - - - - Deprecated 11/17, no longer used. - - - - - - - - - - - Obsolete as of April 2017 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in M77. - - - - - Replaced by Sync.SyncedHistoryFaviconAvailability in M77. - - - - - Deleted in M84. - - - - - Replaced by Sync.RequestGroupSizeForSyncedHistoryFavicons in M77. - - - - - - - - - - - - - - - - - - Deprecated 2/2017. - - - - - - - Deprecated 7/2018. - - - - - - - - - - - - Deprecated 4/2020. - - - - - - - - - - Deprecated 4/2018. - - - - - - Deprecated 4/2018. - - - - - - Removed 11/2019. - - - - - - - - - - - - - - - - - - - Deprecated in M53. - - - - - Deprecated in M53. - - - - - - - - - - - - This never got launched and is removed. - - - - - - - - - - - - - - - Deprecated 7/2018. Replaced by Sync.ModelTypeCount2. - - - - - Deprecated 8/2018. Replaced by Sync.ModelTypeCount3. - - - - - Deprecated 8/2018. Replaced by Sync.ModelTypeCount3. - - - - - - Deprecated 10/2018. Replaced by Sync.ModelTypeEntityChange3. - - - - - Deprecated 11/2018. Replaced by Sync.ModelTypeEntityChange3. - - - - - - - - - Deprecated 06/2019. Replaced by - Sync.NonReflectionUpdateFreshnessPossiblySkewed2. - - - - - - Deprecated 05/2019. - - - - - - Deprecated 05/2020. - - - - - - - Removed in M80. - - - - - Deprecated 2/2017. - - - - - - - - Deprecated 7/2018. - - - - - - - - - - - - - - - - - - Deprecated 4/2018. - - - - - - Deprecated 4/2018. - - - - - - - - - - - - - - - - - Deprecated in M53. - - - - - Deprecated in M53. - - - - - - - - - - This never got launched and is removed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - No longer logged. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 07/2020, base histogram no longer recorded on dektop. - - - - - Removed 07/2020, base histogram no longer recorded on dektop. - - - - - Removed 06/2017, never worked correctly. - - - - - Removed 06/2017, never worked correctly. - - - - - Removed 07/2020, base histogram no longer recorded on dektop. - - - - - - - - - - Unused as of 11/2019, sheet UI is no longer used. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 03/2019. All affected histograms are deprecated. - - - - - - - - - - - Removed 1/2018. Merged with TaskSchedulerTaskPriority into - TaskSchedulerTaskType to reduce suffixing. - - - - - Deprecated 4/2017. Units changed from milliseconds to microseconds. - - - - - Deprecated 4/2017. Units changed from milliseconds to microseconds. - - - - - Deprecated 4/2017. Units changed from milliseconds to microseconds. - - - - - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - - - - - - - - - - - - - - - - Removed 1/2018. Merged with TaskSchedulerMayBlock into TaskSchedulerTaskType - to reduce suffixing. - - - - - - - Deprecated 4/2017. Units changed from milliseconds to microseconds. - - - - - Deprecated 12/2016. Pool name removed from task latency histogram name. - - - - - Deprecated 12/2016. Pool name removed from task latency histogram name. - - - - - Deprecated 12/2016. Pool name removed from task latency histogram name. - - - - - Deprecated 12/2016. Pool name removed from task latency histogram name. - - - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - - - - - - - - - - - - - - - - - - - - Removed 4/2019. Prefix renamed to ThreadPool. - - - - Deprecated January 2019 as the pool no longer exists. - - - - - Deprecated 02/2017. Pool was renamed to BackgroundBlocking. - - - - - - Deprecated January 2019 as the pool no longer exists. - - - - - Deprecated 02/2017. Pool was renamed to ForegroundBlocking. - - - - - - Deprecated 01/2018. In favor of TaskSchedulerName suffix. - - - - - Deprecated 01/2018. In favor of TaskSchedulerName suffix. - - - - - Deprecated 01/2018. In favor of TaskSchedulerName suffix. - - - - - Deprecated 01/2018. In favor of TaskSchedulerName suffix. - - - - - Deprecated 01/2018. In favor of explicit .Browser suffix. - - - - - - - - - - - Deprecated 01/2018. In favor of explicit .Browser suffix. - - - - - - - - Deprecated 01/2018. In favor of explicit .Browser suffix. - - - - - - - - - - - Deprecated 12/2016. Pool name removed from task latency histogram name. - - - - - - - - - - - - - - Removed 2020 January. - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated 09/2019. Merged with BackgroundTaskPriority, because both - histograms effectively record the same thing since we merged pools. - - - - - - Deprecated 09/2019. Merged with UserBlockingTaskPriority, because both - histograms effectively record the same thing since we merged pools. - - - - - - Deprecated 09/2019. Merged with UserVisibleTaskPriority, because both - histograms effectively record the same thing since we merged pools. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2019-03. - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 11/2017 in Issue 650338. Using a DCHECK instead. - - - - - - - - - - - - - - - - - Deprecated as of 08/2015. Use Net.HttpJob.*Secure.NotQuic instead. - - - - - Deprecated as of 08/2015. Use Net.HttpJob.*Secure.Quic instead. - - - - - Deprecated as of 08/2018. No longer used. - - - - - - - Deprecated 10/2016, no longer used. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 2020/04. - - - - - - - - Removed 2018/07. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of July 2017, in favor of - NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and - NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed in favor of [LoadKeys, Clear] as of 2020-04-03. - - - - - - Removed in favor of [Clear] as of 2020-04-24. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed 06/2020. - - - - - - - - - - - - - - - - - - Removed 06/2020. - - - - - - - - - - Removed 06/2020. - - - - - - - - - Removed 02/2020 - - - - - Removed 02/2020 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 2020-02-11. - - - - - Deprecated as of 2020-02-11. - - - - - - - - - Deprecated as of 2019-12-24. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed Jan 2020. - - - - - - - - - toyoshim@chromium.org - - - - - - - - - - - - Removed 10/2017. Related field trial has finished rolling out. - - toyoshim@chromium.org - - - - - - - - - Removed 03/2020 in https://crbug.com/1053019. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ilnik@chromium.org - webrtc-video@google.com - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Removed as of 2020-09 - - - - - - - - - Removed as of 2020-09 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - tmartino@chromium.org - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenBookmark - instead. - - - - - - - - - - - - Deprecated as of 04/2017. Replaced by Bookmark Apps (CreateHostedApp). - - - - - - - - - - - - - - - - - - - - - - - - - - - Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenRecentTab - instead. - - - - - - - - - - - - - - - - - - - - - - + diff --git a/tools/metrics/histograms/histograms_index.txt b/tools/metrics/histograms/histograms_index.txt index fd812033385dadc6458d7c789299fd8f1b36aeb3..9acd5964b82ac55525a4b3f6f00bac2ddab2da60 100644 --- a/tools/metrics/histograms/histograms_index.txt +++ b/tools/metrics/histograms/histograms_index.txt @@ -1,5 +1,111 @@ tools/metrics/histograms/histograms.xml -tools/metrics/histograms/histograms_xml/Blink/histograms.xml -tools/metrics/histograms/histograms_xml/Fingerprint/histograms.xml -tools/metrics/histograms/histograms_xml/UMA/histograms.xml -tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml \ No newline at end of file +tools/metrics/histograms/histograms_xml/accessibility/histograms.xml +tools/metrics/histograms/histograms_xml/android/histograms.xml +tools/metrics/histograms/histograms_xml/apps/histograms.xml +tools/metrics/histograms/histograms_xml/arc/histograms.xml +tools/metrics/histograms/histograms_xml/ash/histograms.xml +tools/metrics/histograms/histograms_xml/assistant/histograms.xml +tools/metrics/histograms/histograms_xml/auth/histograms.xml +tools/metrics/histograms/histograms_xml/auto/histograms.xml +tools/metrics/histograms/histograms_xml/autofill/histograms.xml +tools/metrics/histograms/histograms_xml/back_forward_cache/histograms.xml +tools/metrics/histograms/histograms_xml/background/histograms.xml +tools/metrics/histograms/histograms_xml/blink/histograms.xml +tools/metrics/histograms/histograms_xml/bluetooth/histograms.xml +tools/metrics/histograms/histograms_xml/browser/histograms.xml +tools/metrics/histograms/histograms_xml/chrome/histograms.xml +tools/metrics/histograms/histograms_xml/cloud/histograms.xml +tools/metrics/histograms/histograms_xml/compositing/histograms.xml +tools/metrics/histograms/histograms_xml/content/histograms.xml +tools/metrics/histograms/histograms_xml/cookie/histograms.xml +tools/metrics/histograms/histograms_xml/cras/histograms.xml +tools/metrics/histograms/histograms_xml/cros/histograms.xml +tools/metrics/histograms/histograms_xml/crostini/histograms.xml +tools/metrics/histograms/histograms_xml/crypt/histograms.xml +tools/metrics/histograms/histograms_xml/cryptohome/histograms.xml +tools/metrics/histograms/histograms_xml/custom_tabs/histograms.xml +tools/metrics/histograms/histograms_xml/data_reduction_proxy/histograms.xml +tools/metrics/histograms/histograms_xml/dev/histograms.xml +tools/metrics/histograms/histograms_xml/diagnostics/histograms.xml +tools/metrics/histograms/histograms_xml/direct/histograms.xml +tools/metrics/histograms/histograms_xml/disk/histograms.xml +tools/metrics/histograms/histograms_xml/dom/histograms.xml +tools/metrics/histograms/histograms_xml/download/histograms.xml +tools/metrics/histograms/histograms_xml/enterprise/histograms.xml +tools/metrics/histograms/histograms_xml/event/histograms.xml +tools/metrics/histograms/histograms_xml/extension/histograms.xml +tools/metrics/histograms/histograms_xml/extensions/histograms.xml +tools/metrics/histograms/histograms_xml/file/histograms.xml +tools/metrics/histograms/histograms_xml/fingerprint/histograms.xml +tools/metrics/histograms/histograms_xml/gcm/histograms.xml +tools/metrics/histograms/histograms_xml/geolocation/histograms.xml +tools/metrics/histograms/histograms_xml/google/histograms.xml +tools/metrics/histograms/histograms_xml/gpu/histograms.xml +tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml +tools/metrics/histograms/histograms_xml/history/histograms.xml +tools/metrics/histograms/histograms_xml/image/histograms.xml +tools/metrics/histograms/histograms_xml/input/histograms.xml +tools/metrics/histograms/histograms_xml/installer/histograms.xml +tools/metrics/histograms/histograms_xml/instant/histograms.xml +tools/metrics/histograms/histograms_xml/interstitial/histograms.xml +tools/metrics/histograms/histograms_xml/ios/histograms.xml +tools/metrics/histograms/histograms_xml/local/histograms.xml +tools/metrics/histograms/histograms_xml/login/histograms.xml +tools/metrics/histograms/histograms_xml/media/histograms.xml +tools/metrics/histograms/histograms_xml/memory/histograms.xml +tools/metrics/histograms/histograms_xml/mobile/histograms.xml +tools/metrics/histograms/histograms_xml/multi_device/histograms.xml +tools/metrics/histograms/histograms_xml/na_cl/histograms.xml +tools/metrics/histograms/histograms_xml/navigation/histograms.xml +tools/metrics/histograms/histograms_xml/net/histograms.xml +tools/metrics/histograms/histograms_xml/network/histograms.xml +tools/metrics/histograms/histograms_xml/new_tab_page/histograms.xml +tools/metrics/histograms/histograms_xml/notifications/histograms.xml +tools/metrics/histograms/histograms_xml/offline/histograms.xml +tools/metrics/histograms/histograms_xml/omnibox/histograms.xml +tools/metrics/histograms/histograms_xml/oobe/histograms.xml +tools/metrics/histograms/histograms_xml/optimization/histograms.xml +tools/metrics/histograms/histograms_xml/others/histograms.xml +tools/metrics/histograms/histograms_xml/page/histograms.xml +tools/metrics/histograms/histograms_xml/password/histograms.xml +tools/metrics/histograms/histograms_xml/payment/histograms.xml +tools/metrics/histograms/histograms_xml/permissions/histograms.xml +tools/metrics/histograms/histograms_xml/platform/histograms.xml +tools/metrics/histograms/histograms_xml/plugin/histograms.xml +tools/metrics/histograms/histograms_xml/power/histograms.xml +tools/metrics/histograms/histograms_xml/print/histograms.xml +tools/metrics/histograms/histograms_xml/printing/histograms.xml +tools/metrics/histograms/histograms_xml/profile/histograms.xml +tools/metrics/histograms/histograms_xml/quickoffice/histograms.xml +tools/metrics/histograms/histograms_xml/quota/histograms.xml +tools/metrics/histograms/histograms_xml/renderer/histograms.xml +tools/metrics/histograms/histograms_xml/renderer4/histograms.xml +tools/metrics/histograms/histograms_xml/safe_browsing/histograms.xml +tools/metrics/histograms/histograms_xml/sb_client/histograms.xml +tools/metrics/histograms/histograms_xml/search/histograms.xml +tools/metrics/histograms/histograms_xml/security/histograms.xml +tools/metrics/histograms/histograms_xml/service/histograms.xml +tools/metrics/histograms/histograms_xml/session/histograms.xml +tools/metrics/histograms/histograms_xml/settings/histograms.xml +tools/metrics/histograms/histograms_xml/sharing/histograms.xml +tools/metrics/histograms/histograms_xml/signin/histograms.xml +tools/metrics/histograms/histograms_xml/simple/histograms.xml +tools/metrics/histograms/histograms_xml/smart/histograms.xml +tools/metrics/histograms/histograms_xml/software/histograms.xml +tools/metrics/histograms/histograms_xml/stability/histograms.xml +tools/metrics/histograms/histograms_xml/startup/histograms.xml +tools/metrics/histograms/histograms_xml/storage/histograms.xml +tools/metrics/histograms/histograms_xml/subresource/histograms.xml +tools/metrics/histograms/histograms_xml/sync/histograms.xml +tools/metrics/histograms/histograms_xml/tab/histograms.xml +tools/metrics/histograms/histograms_xml/translate/histograms.xml +tools/metrics/histograms/histograms_xml/ukm/histograms.xml +tools/metrics/histograms/histograms_xml/uma/histograms.xml +tools/metrics/histograms/histograms_xml/update_engine/histograms.xml +tools/metrics/histograms/histograms_xml/v8/histograms.xml +tools/metrics/histograms/histograms_xml/variations/histograms.xml +tools/metrics/histograms/histograms_xml/web_apk/histograms.xml +tools/metrics/histograms/histograms_xml/web_audio/histograms.xml +tools/metrics/histograms/histograms_xml/web_core/histograms.xml +tools/metrics/histograms/histograms_xml/web_rtc/histograms.xml +tools/metrics/histograms/histograms_xml/windows/histograms.xml \ No newline at end of file diff --git a/tools/metrics/histograms/histograms_xml/accessibility/histograms.xml b/tools/metrics/histograms/histograms_xml/accessibility/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..77c749ff897e75ecbf7433ef1818738944227b71 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/accessibility/histograms.xml @@ -0,0 +1,969 @@ + + + + + + + + + + dmazzoni@chromium.org + smcgruer@chromium.org + chrome-a11y-core@google.com + + Tracks whether animations are enabled on Android (e.g. if the animator + duration scale is non-zero.) The purpose is to inform the design of the + prefers-reduced-motion media feature; see http://crbug.com/722548. This is + logged once, 45 seconds after startup. + + This replaced Accessibility.Android.AnimationsEnabled because the older + histogram did not capture the default (e.g. no flag) case. + + + + + + + aleventhal@chromium.org + chrome-a11y-core@google.com + + Tracks whether a screen reader is enabled on Android (e.g. Talkback). This + is checked once, 45 seconds after startup. Note: prefer + Accessibility.Android.ScreenReader.EveryReport when querying for unique + users, as it is logged more frequently. + + + + + twellington@chromium.org + tedchoc@chromium.org + + Tracks whether the accessibility tab switcher is enabled when an + accessibility service (e.g. TalkBack or Switch Access) is enabled that would + typically cause the accessibility tab switcher to be used. Recorded when the + activity is resumed or accessibility services are turned on. + + + + + twellington@chromium.org + skym@chromium.org + + Records the current user font size pref when exiting accessibility settings + if the preference was changed. The font size ranges from 50% to 200% and can + be set in increments of 5%; the default is 100%. + + + + + twellington@chromium.org + skym@chromium.org + + Records the current user font size pref during deferred startup for + ChromeActivity. The font size ranges from 50% to 200% and can be set in + increments of 5%; the default is 100%. + + + + + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Tracks flags and capabilities of enabled accessibility services. Recorded + every time an Android web content view first creates a virtual view + hierarchy, indicating that some accessibility service is running. The number + of emits of this histogram won't be as useful as the unique user counts. The + primary purpose of this is to guide optimization by determining what + capabilities of accessibility services are widespread and which ones are + relatively rare. + + + + + dmazzoni@chromium.org + jkim@igalia.com + chrome-a11y-core@google.com + + Tracks usage of ATK APIs on Linux Desktop. Recorded when ATK APIs that were + supposed to trigger AX mode enabled is called. The feature to turn on AX + mode through ATK APIs is disabled for now; see http://crbug.com/1086506. + + + + + evliu@google.com + media-dev@chromium.org + + Whether custom caption settings were loaded from the user preferences. + Recorded when WebKit preferences are overridden. + + + + + evliu@google.com + media-dev@chromium.org + + Whether custom caption settings were loaded from the system preferences. + Recorded when WebKit preferences are overridden. + + + + + dtseng@chromium.org + chrome-a11y-core@google.com + + A user can control ChromeVox via a variety of gestures on the touch screen. + For example, swiping right with one finger causes ChromeVox to navigate to + the next object. Track all possible gestures here. + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS Accessibility Menu is set to be shown regardless of + the state of a11y features.(logged once 45 secs after startup). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + dtseng@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS Autoclick feature is on (logged once 45 secs after + startup). + + + + + katie@chromium.org + dtseng@chromium.org + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Recorded when a user has picked a new autoclick action type from the bubble + menu. + + + + + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS caret highlighting is on (logged once 45 secs after + startup). + + + + + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Set when a Chrome OS user has spoken feedback enabled, recorded once each + time ChromeVox starts up. True if the user has enabled "ChromeVox + Next", a new ChromeVox experience that became the default in Chrome 56 + (but can be toggled on or off by the user), false otherwise. + + + + + dmazzoni@chromium.org + katie@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS feature to colorize the cursor is enabled (logged once + 45 secs after startup). + + + + + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS cursor highlighting is on (logged once 45 secs after + startup). + + + + + anastasi@google.com + dtseng@chromium.org + chrome-a11y-core@google.com + + Whether the ChromeOS dictation feature is enabled (logged once 45 secs after + startup). + + + + + anastasi@google.com + dtseng@chromium.org + chrome-a11y-core@google.com + Records how users invoke Dictation. + + + + dmazzoni@chromium.org + katie@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS Docked Magnifier feature is on (logged once 45 secs + after startup). + + + + + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS focus highlighting is on (logged once 45 secs after + startup). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS High Contrast mode feature is on (logged once 45 secs + after startup). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS Large Cursor feature is on (logged once 45 secs after + startup). + + + + + yawano@chromium.org + lpalmaro@chromium.org + chrome-a11y-core@google.com + + Cursor size of the Chrome OS Large Cursor (logged once 45 secs after + startup). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS Screen Magnifier feature is on (logged once 45 secs + after startup). + + + + + dmazzoni@chromium.org + katie@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS select-to-speak is on (logged once 45 secs after + startup). + + + + + katie@chromium.org + chrome-a11y-core@google.com + + Whether Select-to-Speak had background shading enabled when activated. + + + + + katie@chromium.org + chrome-a11y-core@google.com + + A user may activate Select-to-Speak by holding down 'search' and clicking or + dragging a region with the mouse, or by highlighting an area and using + search + s to read just the highlighted area. Track the methods here. + + + + + katie@chromium.org + chrome-a11y-core@google.com + + A user has tapped a button in the tray to change Select-to-Speak's state. + The tap was interpreted by Select-to-Speak as a request to start selection, + to cancel speech, or to cancel selection, depending on Select-to-Speak's + internal state when the tap occured. This tracks when the button was tapped + and the event that it generated. + + + + + gzadina@google.com + tbarzic@chromium.org + + The value for shelf navigation buttons setting set by the user during OOBE. + The metric will be reported after the setting has been stable for 10 + seconds, or the OOBE screen in which the value can be set is closed (if the + setting changes multiple times in quick succession, only the final value + will be reported). + + + + + gzadina@google.com + tbarzic@chromium.org + + The value for shelf navigation buttons setting set by the user in Chrome OS + Settings page. The metric will be reported after the setting change has been + stable for 10 seconds, or the settings window in which the value is set gets + closed (if the setting changes multiple times in quick succession, only the + final value will be reported). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS Spoken Feedback feature is on (logged once 45 secs + after startup). Note: prefer Accessibility.CrosSpokenFeedback.EveryReport + when querying for unique users, as it is logged more frequently. + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + tengs@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome OS Sticky Keys feature is on (logged once 45 secs after + startup). + + + + + dmazzoni@chromium.org + anastasi@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS switch access is on (logged once 45 secs after + startup). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether the Chrome OS Virtual Keyboard feature is on (logged once 45 secs + after startup). + + + + + katie@chromium.org + dmazzoni@chromium.org + chrome-a11y-core@google.com + + Whether the Chrome accessibility image label setting is on (logged once 45 + secs after startup). + + + + + katie@chromium.org + dmazzoni@chromium.org + + Whether a user accepts or does not accept a modal dialog enabling the image + labels option. If the user does not accept it this does not track whether + they closed it with the negative button, the close button, or keyboard + escape. + + + + + katie@chromium.org + dmazzoni@chromium.org + chrome-a11y-core@google.com + + The language of a web page where image labels were requested, as detected by + Chrome (not necessarily what language the page claims to be in). + + + + + katie@chromium.org + dmazzoni@chromium.org + chrome-a11y-core@google.com + + The language that was requested for image descriptions, based on the page + language, the user's accept languages and top languages, and the server + languages. + + + + + gambard@chromium.org + rkgibson@google.com + + This metric is related to the Preferred Content Size chosen by the user. It + is only recorded once per session. This is hit if the chosen category is not + listed in the map defined in + /ios/chrome/browser/ui/util/dynamic_type_util.mm. In that case, we should + update the code by adding an entry for the new category in that map. This is + logged when the helper to returning the multiplier associated with the + current preferred content size is called. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + The number of nodes on this page for which language detection was attempted. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + The number of nodes on this page for which a detected language was + successfully assigned. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + The number of unique languages which were detected to be the most probable + language for at least one node on the page, regardless of whether a detected + language was assigned for that node. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + Of the nodes which had a detected language assigned, the percentage for + which the assigned language was the language detected as having the highest + probability. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + Of the nodes for which language detection was attempted, the percentage for + which a language was successfully assigned. + + + + + chrishall@chromium.org + aboxhall@chromium.org + dmazzoni@chromium.org + + Of the nodes for which a detected language was successfully assigned, the + percentage where the assigned language differs from the author-provided + language. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Whether the Live Caption feature is enabled. This is logged once, 45 seconds + after startup. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Whether the sample rate or channel count of a Live Caption audio stream + changed midstream. This is logged once per audio stream on the destruction + of the Cloud speech recognition client. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Whether the Live Caption feature flag is enabled. This is logged once at the + time of component registration. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Logged when there's a change in the lifetime of a Live Caption audio stream: + When a session started and captions began arriving from the service, when a + session ended because the audio stream finished, or when the session ended + because a user clicked the close button on the caption bubble. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Records when a user enables or disables the Live Caption feature from + chrome://settings. + + + + + katie@chromium.org + abigailbklein@google.com + evliu@google.com + chrome-a11y-core@google.com + + Whether the Live Caption feature is blocked because the website is on the + captioning blocklist. This is logged once per stream when the speech + recognition client is created. + + + + + dmazzoni@chromium.org + smcgruer@chromium.org + chrome-a11y-core@google.com + + Tracks whether the accessibilityDisplayShouldReduceMotion system property is + enabled. The purpose is to inform the design of the prefers-reduced-motion + media feature; see http://crbug.com/722548. This is logged once, 45 seconds + after startup. + + + + + ellyjones@chromium.org + chrome-a11y-core@google.com + + Whether the "reduce transparency" Mac system setting is enabled. + This is logged once, 45 seconds after startup. + + + + + + + aleventhal@chromium.org + chrome-a11y-core@google.com + + Tracks whether a screen reader is enabled on Mac (e.g. VoiceOver). This is + logged once, 45 seconds after startup. Note: prefer + Accessibility.Mac.ScreenReader.EveryReport when querying for unique users, + as it is logged more frequently. + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether Chrome has enabled accessibility support because the user passed the + --force-renderer-accessibility flag on the command-line (logged once 45 secs + after startup). + + + + + dmazzoni@chromium.org + aboxhall@chromium.org + chrome-a11y-core@google.com + + Whether individual accessibility mode flags are set. Tracked when each mode + flag is flipped from false to true. These flags are flipped automatically + when software communicates with Chrome via accessibility APIs. Flags can + only be flipped off by advanced users or for debugging using + chrome://accessibility/ - and that isn't tracked in this histogram. + + + + + + + lpalmaro@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + alemate@chromium.org + cros-oac@google.com + + Delay between login_prompt_visible and Chrome OS OOBE startup sound + playback. Depends on sound subsystem initialization time. + + + + + dmazzoni@chromium.org + janewman@microsoft.com + chrome-a11y-core@google.com + + Tracks time taken to execute the public Windows API that {API}. This is + recorded for all Windows users that call into our public APIs. + + + + + + + + + + + + + + + + + + + + + + + + + + amraboelkher@chromium.org + poromov@chromium.org + + Whether the Chrome OS Docked Magnifier shortcut is enabled. It's being + emitted when the Docked Magnifier shortcut is triggered. + + + + + amraboelkher@chromium.org + poromov@chromium.org + + Whether the Chrome OS High Contrast mode shortcut is enabled. It's being + emitted when the High Contrast shortcut is triggered. + + + + + amraboelkher@chromium.org + poromov@chromium.org + + Whether the Chrome OS Full-screen Magnifier mode shortcut is enabled. It's + being emitted when the Full-screen Magnifier shortcut is triggered. + + + + + amraboelkher@chromium.org + poromov@chromium.org + + Whether the Chrome OS Spoken Feedback shortcut is enabled. It's being + emitted when the Spoken Feedback shortcut is triggered. + + + + + evliu@google.com + media-dev@chromium.org + + Whether a VTT file contains an embedded style block. Recorded when a VTT + file is parsed. + + + + + dmazzoni@chromium.org + smcgruer@chromium.org + chrome-a11y-core@google.com + + Tracks whether the SPI_GETCLIENTAREAANIMATION system property is enabled. + The purpose is to inform the design of the prefers-reduced-motion media + feature; see http://crbug.com/722548. This is logged once, 45 seconds after + startup. + + + + + dmazzoni@chromium.org + nektar@chromium.org + chrome-a11y-core@google.com + Tracks usage of all public Windows accessibility APIs. + + + + dmazzoni@chromium.org + nektar@chromium.org + kbabbitt@microsoft.com + chrome-a11y-core@google.com + + Tracks properties requested via UI Automation GetPropertyValue(). + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + chrome-a11y-core@google.com + + Whether Windows system settings show that audio descriptions are enabled + (logged once 45 secs after startup). + + + + + dmazzoni@chromium.org + almaher@microsoft.com + weblayoutdev@microsoft.com + + Tracks which Windows high contrast theme is set in system settings (logged + once 45 secs after startup). AccessibilityHighContrastColorScheme::None + indicates that high contrast mode is not enabled. + + + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@chromium.org + chrome-a11y-core@google.com + + Whether the third-party JAWS screen reader is running (logged once 45 secs + after startup). Note: prefer Accessibility.WinJAWS.EveryReport when querying + for unique users, as it is logged more frequently. + + + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@chromium.org + chrome-a11y-core@google.com + + Whether the third-party NVDA screen reader is running (logged once 45 secs + after startup). Note: prefer Accessibility.WinNVDA.EveryReport when querying + for unique users, as it is logged more frequently. + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + + Whether Windows system settings show that a screen reader is running (logged + once 45 secs after startup). Note that this does not necessarily mean that + Chrome has detected a supported screen reader and has enabled its + accessibility mode. + + + + + + + aleventhal@chromium.org + + Whether the accessibility mode flag shows that a screen reader is running + (logged once 45 secs after startup). In this case, Chrome has detected + accessibility calls that would normally only occur from a screen reader. See + also the more specific metrics such as Accessibility.WinJAWS/WinNVDA. Note: + prefer Accessibility.WinScreenReader2.EveryReport when querying for unique + users, as it is logged more frequently. + + + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@chromium.org + chrome-a11y-core@google.com + + Whether Windows system settings show that Sticky Keys are enabled. + + + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@chromium.org + chrome-a11y-core@google.com + + Whether the third-party Supernova screen reader is running (logged once 45 + secs after startup). Note: prefer Accessibility.Supernova.EveryReport when + querying for unique users, as it is logged more frequently. + + + + + + + dmazzoni@chromium.org + kenjibaheux@google.com + aleventhal@chromium.org + chrome-a11y-core@google.com + + Whether the third-party ZoomText screen magnifier is running. Note: prefer + Accessibility.WinZoomText.EveryReport when querying for unique users, as it + is logged more frequently. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/android/histograms.xml b/tools/metrics/histograms/histograms_xml/android/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..b24cf30ca31fa934c96b45d548c0001fd80152ab --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/android/histograms.xml @@ -0,0 +1,2844 @@ + + + + + + + + + + peter@chromium.org + + Records whether notifications are enabled for Chrome, as the Android app, + every time metrics are logged. + + + + + mcarlen@chromium.org + + Reports the drop out reason of an Autofill Assistant script. It is recorded + when Autofill Assistant is shut down or terminated. The AA_START value is + used as a baseline and counts the number of attempted starts of Autofill + Assistant flows. The sum of all drop out reasons should be the same as the + number of attempted starts (i.e. AA_START). + + + + + mcarlen@chromium.org + autofill_assistant+watch@google.com + + Reports the installation status of the DFM, e.g. installation deferred, + foreground installation succeeded etc. The metric cannot currently + distinguish whether the deferred installation succeeded or not. + + + + + lsuder@chromium.org + mcarlen@chromium.org + + Reports the basic user interactions that can happen in regard on boarding. + It is recorded on Autofill Assistant startup and during the on boarding. + + + + + arbesser@google.com + mcarlen@chromium.org + + Reports whether autofill information was changed during an autofill + assistant payment request, or not. This is recorded every time the user sees + the autofill assistant payment request. + + + + + arbesser@google.com + mcarlen@chromium.org + + Reports whether the user selected a profile which does not contain separate + first and last name. This is recorded when the user confirms the payment + request screen in autofill assistant provided that 'name' was one of the + requested fields. + + + + + arbesser@google.com + mcarlen@chromium.org + + Reports on whether a billing postal code was required and whether the user + ultimately succeeded or not. Also reports if the user had to change their + profile or if the default profile already contained a billing postal code. + This histogram is reported either when the user taps the 'continue' button + of the autofill assistant payment request (and thus succeeds) or when + autofill assistant closes during the action (i.e., the user aborted). + + + + + arbesser@google.com + mcarlen@chromium.org + + Reports whether the autofill assistant payment request was successfully + completed (i.e., the continue button was tapped) or not, and whether the + payment request was initially pre-filled completely or not. This is recorded + every time the user sees the autofill assistant payment request. + + + + + ioanastefan@chromium.org + nator@chromium.org + knollr@chromium.org + + Records that an exact task has been created. Recorded when the task is + scheduled. + + + + + ioanastefan@chromium.org + nator@chromium.org + knollr@chromium.org + + Records the stored tasks migrated to the Protocol Buffer data format. The + metric is recorded when the migration to the new format is being done. The + migration is done at a restart / OS upgrade, if tasks stored in the old + format are found. + + + + + fgorski@chromium.org + nyquist@chromium.org + Records that a specific background task has been canceled. + + + + ioanastefan@chromium.org + nator@chromium.org + knollr@chromium.org + + Records that a specific task has been created with an expiration deadline. + Recorded when the task is scheduled. + + + + + ioanastefan@chromium.org + nator@chromium.org + knollr@chromium.org + + Records that a specific task has been created without the expiration feature + activated. Recorded when the task is scheduled. + + + + + ioanastefan@chromium.org + nator@chromium.org + knollr@chromium.org + + Records that a specific background task has expired. Recorded before the + task is to be started. + + + + + fgorski@chromium.org + nyquist@chromium.org + Records that a specific background task has loaded native. + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific background task has loaded native in Full Browser + Mode. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific background task has loaded native in Reduced Mode. + + + + + fgorski@chromium.org + nyquist@chromium.org + + Records that a specific background task has failed to be scheduled. + + + + + fgorski@chromium.org + nyquist@chromium.org + + Records that a specific background task has been successfully scheduled. + + + + + fgorski@chromium.org + nyquist@chromium.org + Records that a specific background task has been started. + + + + fgorski@chromium.org + nyquist@chromium.org + + Records that a specific background task has been stopped by Background Task + Scheduler before it was able to complete itself. + + + + + boliu@chromium.org + src/base/android/OWNERS + + When ChildProcessConnection fallback is enabled (Android 10+ for sandboxed + services), this is recorded after the timeout (10s) of every + ChildProcessConnection launch. Record whether fallback operation is + performed. + + + + + cduvall@chromium.org + boliu@chromium.org + + Measures time from {type} child process starts to right before main. Only + recorded on Android N+. + + + + + + + + + + + + peconn@chromium.org + src/base/metrics/OWNERS + + Recorded at the same time as "CustomTabs.Visible", this metric + should eventually replace that one. This additionally distinguishes between + Trusted Web Activities, WebAPKs and Webapps. + + As of M87, this histogram is logged on a log start, rather than log end to + tag more logs. + + + + + yfriedman@chromium.org + + Android: Count of requests to Chrome browser which are granted to other apps + to read/write user's bookmarks and history. Only records cases when the app + has permission according to Android's permission manager. + + + + + yfriedman@chromium.org + + Android: Count of requests to Chrome browser which are granted to other apps + to read/write user's bookmarks and history. Only records cases where the app + is a system app or signed by Google. + + + + + estevenson@chromium.org + agrieve@chromium.org + + The amount of time Chrome spends blocked on resource extraction. Generally, + extraction is completed in the background but in certain cases a main-thread + getResources() call may block on resource extraction. + + + + + estevenson@chromium.org + agrieve@chromium.org + + Describes the result of Android resource extraction, and is recorded once + per browser start as part of deferred startup (not at time of extraction). + + + + + estevenson@chromium.org + agrieve@chromium.org + + The amount of time spent on resource extraction, whether or not extraction + was performed in the background or foreground. + + + + + finnur@chromium.org + rayankans@chromium.org + + Measures whether the address selected from the contacts picker has derived + fields. Derived fields refer to the individual attributes of a full address, + such as city, country, region, or postcode. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the total number of contacts shown in the contacts picker. Measured + once when the Contacts Picker dialog is dismissed. + + + + + finnur@chromium.org + twellington@chromium.org + + Records which action the user takes in the ContactsPickerDialog. Measured + once when the Contacts Picker dialog is dismissed. + + + + + finnur@chromium.org + twellington@chromium.org + + The contact properties requested by the website (names, emails, telephone + numbers). Measured once when the Contacts Picker dialog is dismissed. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the total number of contacts selected in the contacts picker. + Measured once when the Contacts Picker dialog is dismissed. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the percentage of contacts selected in the contacts picker. + Measured once when the Contacts Picker dialog is dismissed. + + + + + wylieb@chromium.org + twellington@chromium.org + chrome-android-app@chromium.org + + Records if Chrome altered a google homepage/search request to include the + dark theme. Recorded only when navigating to google or google search. + Histogram total count will be the total number of requests to the google + hompage or google search. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Records the reason why dark theme is enabled when dark theme is visible to + user. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Records whether dark theme is enabled or not on cold start and when the + enabled state changes. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Records user theme preference of system default, light or dark theme on cold + start and when the theme preference changes. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + Records the current default browser state when the primer dialog prompting + users to change their default browser is shown. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + Records the current default browser state if the activity receives an intent + through the disambiguation sheet that is displayed in response to the + default browser promo. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + The final default browser state (outcome) after the user has been prompted + to set Chrome as the default when no browser is set as the default + initially. Recorded when the system UI prompting the user to change their + default is dismissed. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + The final default browser state (outcome) after the user has been prompted + to set Chrome as the default when another browser is set as the default + initially. Recorded when the system UI prompting the user to change their + default is dismissed. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + Records the default browser state when the Android Q+ role manager dialog is + shown. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + Records which button click led to the default browser promo dialog being + dismissed for dialogs shown when there is currently no default browser set. + + + + + lazzzis@google.com + twellington@chromium.org + pavely@chromium.org + + Records which button click led to the default browser promo dialog being + dismissed for dialogs shown when another browser is set as the default. + + + + + twellington@chromium.org + tedchoc@chromium.org + chrome-android-app@chromium.org + + Records the largest display dimension in dp during deferred startup. The + display size is not affected by Android N multi-window mode. Clamped at + 200dp to 1200dp. + + + + + twellington@chromium.org + tedchoc@chromium.org + chrome-android-app@chromium.org + + Records the smallest display dimension in dp during deferred startup. The + display size is not affected by Android N multi-window mode. Clamped at 0 to + 1000dp. + + + + + szermatt@chromium.org + autofill_assistant@google.com + + Counts calls to Activity.onPerformDirectAction made by the system on behalf + of the assist app and which action was performed, if any. Available starting + with Android Q. + + + + + shaktisahu@chromium.org + + Records the state of the download infobar when the user taps on the + infobar's close button. + + + + + shaktisahu@chromium.org + + Records various types of messages representing the state of the downloads as + they are shown on the download infobar. + + + + + hesen@chromium.org + clank-downloads@google.com + + Records various actions taken by the user on the rename dialog in download + home. + + + + + hesen@chromium.org + clank-downloads@google.com + + Records various error codes when users try to rename a download in a + download home, recorded when backend rename callback is compeleted. + + + + + shaktisahu@chromium.org + clank-downloads@google.com + Recorded when a download is cancelled from Java. + + + + dtrainor@chromium.org + clank-downloads@google.com + + Recorded when the user selects a filter from the Chrome download manager + navigation drawer. + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records instances where the foreground undergoes a lifecycle change (when + the foreground starts, changes pinned notification, or stops). + + + + + dtrainor@chromium.org + clank-downloads@google.com + + The number of non-incognito download items displayed when the download UI is + initialized. + + + + + dtrainor@chromium.org + clank-downloads@google.com + + The number of non-incognito download items displayed that are already viewed + by the user at any time, recorded when the download UI is initialized. + + + + + dtrainor@chromium.org + clank-downloads@google.com + Recorded when a download fails to open. + + + + dtrainor@chromium.org + clank-downloads@google.com + Recorded when a download is opened. + + + + dtrainor@chromium.org + clank-downloads@google.com + The count of Download Home list entry actions taken. + + + + dtrainor@chromium.org + clank-downloads@google.com + The count of Download Home top level menu actions taken. + + + + dtrainor@chromium.org + clank-downloads@google.com + + The number of items selected when performing a multi-delete action. + + + + + dtrainor@chromium.org + clank-downloads@google.com + + The number of items selected when performing a multi-share action. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records instances where a user interacts with a download notification (ie. + clicks on, pauses, resumes, cancels). + + + + + xingliu@chromium.org + clank-downloads@google.com + Records how users open audio download files on Android. + + + + xingliu@chromium.org + clank-downloads@google.com + + Records the entry point for users opening downloaded files on Android, that + are not audio nor video. + + + + + xingliu@chromium.org + clank-downloads@google.com + Records how users open video download files on Android. + + + + xingliu@chromium.org + clank-downloads@google.com + + + + Records instances of DownloadForegroundService stops. The number of expected + stops (stopped) and unexpected stops (task removed, low memory, etc) can be + compared to get a sense of how often the service crashes to see how it + handles restarts. For example, the number of times the service is stopped + because of low memory can be compared to the number of times the service has + been destroyed to see how frequently it occurs. Or, the number of start + sticky's will indicate how often the service is able to restart due to an + unexpected stop. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records instances of DownloadNotificationService stops. The number of + expected stops (stopped) and unexpected stops (task removed, low memory, + etc) can be compared to get a sense of how often the service crashes to see + how it handles restarts. For example, the number of times the service is + stopped because of low memory can be compared to the number of times the + service has been destroyed to see how frequently it occurs. Or, the number + of start sticky's will indicate how often the service is able to restart due + to an unexpected stop. + + + + + twellington@chromium.org + ianwen@chromium.org + clank-downloads@google.com + The number of downloads shared at the same time. + + + + twellington@chromium.org + ianwen@chromium.org + clank-downloads@google.com + + Recorded when downloads are shared through the download manager. A recorded + value of "All" indicates that multiple types of downloads were + shared. + + + + + twellington@chromium.org + ianwen@chromium.org + clank-downloads@google.com + The percentage of total storage downloads consume. + + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Records the required stretch of the smaller dimension before displaying an + image on download home. Measured in percentage. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records the entry point for users opening the download page on Android. + + + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Availability status for each dynamic feature module. Reported once per + Chrome start. This metric's purpose is to measure a feature module's install + penetration over time. + + + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Duration of successful installs for each dynamic feature module. Only + contains install durations for modules first requested *before* Chrome + started last and may therefore be installed from cache. Omits deep sleep + time. + + + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Install status counter for each dynamic feature module. Recorded during + on-demand and deferred installs. + + + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Install status for each dynamic feature module. Recorded after the + installation has finished. + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Length of time during startup used by module framework code. This is our + metric to improve and used to guard against regressions. + + + + + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org + + Duration of successful installs for each dynamic feature module. Only + contains install durations of modules first requested *after* Chrome started + last and are therefore unlikely to be installed from cache. Omits deep sleep + time. + + + + + drott@chromium.org + layout-dev@chromium.org + + Records the latency of looking up a local font from Android downloadable + fonts at the time of instantiating the font in the fonts backend in the + renderer. Includes time for error checking and attempting to create the font + from the retrieved blob, if there is one. Only records timings for + situations in which a font could not be instantiated. + + + + + drott@chromium.org + layout-dev@chromium.org + + Records the latency of looking up a local font from Android downloadable + fonts at the time of instantiating the font in the fonts backend in the + renderer. Includes time for error checking and attempting to create the font + from the retrieved blob, if there is one. Only records timings for + situations in which a font was successfully instantiated and returned. + + + + + chouinard@chromium.org + twellington@chromium.org + + Records the result of font fetch requests made to the GMS Core Android + downloadable font provider. The result may be success, or failure with a + reason. In the case of multiple failures, only the first one encountered is + reported. See implementation at AndroidFontLookupImpl. + + + + + chouinard@chromium.org + twellington@chromium.org + + Records the time taken to make a fetchFonts font request to GMS Core via the + Android downloadable font provider API. This metric may be used to determine + whether it's reasonable to execute this task on the IO thread rather than + posting to a background thread. + + + + + chouinard@chromium.org + twellington@chromium.org + + Records the time taken to respond to a request from the renderer to fetch a + specific font file from the GMS Core Android downloadable font provider. + + + + + sbirch@google.com + + Measures the amount of time spent in the getInstantAppIntent() API call when + the API was able to find an Instant App for the URL. This is recorded for + external intents coming into Chrome only and measures the delay before we + dispatch the intent to Instant Apps. + + + + + sbirch@google.com + tedchoc@chromium.org + + Measures the amount of time spent in the getInstantAppIntent() API call when + the API was not able to find an Instant App for the URL. This is recorded + for external intents coming into Chrome that get checked for their Instant + Apps eligibility, but end up being loaded in Chrome. It's critical to keep + this latency low for our startup performance. + + + + + sbirch@google.com + tedchoc@chromium.org + + For intents to load a web page in browser from Instant Apps, records where + the request to load came from. + + + + + sbirch@google.com + + Records events that occur when a user clicks on an intent:// URL that is + dispatched to instant apps. The intent:// URLs to the Instant Apps are + explicitly disabled unless they are launched from Google SERP, but we record + other attempts as well. + + + + + sbirch@google.com + tedchoc@chromium.org + + Records whether any given successful page load (for http and https schemes + only) could have been handled by an Instant App. + + + + + sbirch@google.com + tedchoc@chromium.org + + Measures the time from when we first received an eligible intent for Instant + Apps to the time we processed it in the case where the Instant Apps activity + had to invoke a fallback intent. This happens only on Android N and older. + + + + + sbirch@google.com + + Measures the amount of time spent triaging an incoming event to decide + whether it needs to be routed to Instant Apps. This is time from + ChromeLauncherActivity.onCreate() call to the time either startActivity() is + called or the request proceeds. This is a superset of + Android.InstantApps.ApiCallDurationWith[out]App. + + + + + sbirch@google.com + tedchoc@chromium.org + + Logs the reasons the banner is shown or hidden on an instant apps eligible + pages. Triggered every time asynchronous Instant Apps API indicates the + currently loaded page is instant apps eligible. Does not include Instant + Apps eligible pages loaded directly through the omnibox. + + + + + tedchoc@chromium.org + thildebr@chromium.org + + When an external application was launched as a result of a form submit, this + tracks whether there was a user gesture associated with the submit. + + + + + mthiesse@chromium.org + yfriedman@chromium.org + + When a site navigates to a URL that can be parsed as an Intent, record the + action of that Intent. + + + + + tedchoc@chromium.org + clank-team@google.com + + Signifies whether the last shared app information is retrieved successfully + or not. This is logged when configuring the direct sharing menu item. + + + + + rsesek@chromium.org + + Reports the kernel major and minor version from the utsname.release field. + The low 16 bits of each version are combined into a 32-bit integer. The + range is from [0x00020006,0x0004000a] to track kernel versions 2.6 through + 4.10. + + + + + perrier@chromium.org + megjablon@chromium.org + chrome-language@google.com + + Reports whether the Chrome UI language is the same as the Android system + lanaguage. Recorded once per top-level ChromeActivty start. + + + + + tiborg@chromium.org + heamy@chromium.org + chrome-language@google.com + + Reports whether Chrome was started in a language other than the system + language but we support the system language. That can happen if the user + changes the system language and the required language split cannot be + installed in time. + + + + + wnwen@chromium.org + + Whether VIEW intent sent explicitly to .Main activity was dispatched by + onCreate(). + + + + + wnwen@chromium.org + + Whether VIEW intent sent explicitly to .Main activity was dispatched by + onNewIntent(). + + + + + wnwen@chromium.org + + Sources (ExternalAppId) of undispatched VIEW intents sent explicitly to + .Main activity alias. + + + + + dmurph@chromium.org + + Recorded when the user presses a button in the 'Manage Space' screen for + Chrome. Note: the 'Clear App Data' option is likely incorrect, as the result + of that button disables UMA recording (as we factory reset the app). + + + + + dmurph@chromium.org + + Records the time it takes to delete all unimportant sites when the user + initiates the 'Clear Unimportant Sites' action in the 'Manage Space' screen + for Chrome. + + + + + dmurph@chromium.org + + Recorded when the user opens the 'Manage Space' screen for Chrome, after the + disk usage is calculated. The disk usage value represents the accumulated + disk usage by websites. + + + + + dmurph@chromium.org + + Recorded when the user opens the 'Manage Space' screen for Chrome, after the + disk usage is calculated. The disk usage value represents the accumulated + disk usage by websites that are not considered 'important'. + + + + + ssid@chromium.org + + The duration of each failed ActivityManager.getMyMemoryState() call made by + MemoryPressureMonitor. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ssid@chromium.org + + The duration of each successful ActivityManager.getMyMemoryState() call made + by MemoryPressureMonitor. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ssid@chromium.org + + Memory pressure notifications sent by Android through ComponentCallbacks2. + This metric was added 04/2018; for prior data for the browser process see + MemoryAndroid.NotificationBackground and + MemoryAndroid.NotificationForeground. + + + + + pavely@chromium.org + chrome-android-app@chromium.org + + Records the action taken on a security sensitive touch event in modal + dialog. As of M84 it is used for site premission dialogs. + + + + + tedchoc@chromium.org + clank-team@google.com + + The number of moderate bindings which were kept while Chrome process is in + the foreground. This is logged right before Chrome process goes into the + background. + + + + + + + twellington@chromium.org + tedchoc@chromium.org + chrome-android-app@chromium.org + + Records on every metrics upload whether the activity is running in Android N + multi-window mode or not. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + yfriedman@chromium.org + + Records that a specific background task has finished cleanly (i.e. no + unexpected exits because of chrome crash or OOM). This includes tasks that + have been stopped due to timeout. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific native background task started in Full Browser Mode + has finished cleanly. See Android.NativeBackgroundTask.TaskFinished for more + details. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific native background task started in Reduced Mode has + finished cleanly. It is possible that Full Browser has launched while the + task was running. See Android.NativeBackgroundTask.TaskFinished for more + details. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + yfriedman@chromium.org + + Records that a specific native background task has been started. This does + not consider tasks that are marked as DONE or RESCHEDULED before a call to + start native is made (regardless of whether native is already loaded). + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific native background task has been started in Full + Browser Mode. See Android.NativeBackgroundTask.TaskStarted for more details. + + + + + mheikal@chromium.org + hanxi@chromium.org + hnakashima@chromium.org + + Records that a specific native background task has been started in Reduced + Mode. See Android.NativeBackgroundTask.TaskStarted for more details. + + + + + mheikal@chromium.org + hnakashima@chromium.org + hanxi@chromium.org + + The number of times full-browser mode is requested to be loaded from native + code (running in reduced mode). + + + + + finkm@chromium.org + + Counts impressions of the NTP on Android. It also counts potential + impressions. A potential impression is a place where it would make sense to + open the NTP instead of the current view. E.g. the no-tab view is counted as + a potential impression since this view could be replaced with the NTP. For + better comparison regular impressions are also counted. The no-tab view + counting happens right after the user closed the last tab and the regular + impression counting happens at construction time of the NTP (=whenever a new + tab is opened). + + + + + chili@chromium.org + + State of a download or offline page request at user-initiated cancel. + + + + + ender@chromium.org + tedchoc@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Recorded every time AutocompleteController.java interacts with + autocomplete_controller_android.cc via an index reference to an item. + Indicates how often the match referenced by Java is different from the match + referenced by C++ at that position. + + + + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records time spent on positioning all suggestions on screen. This histogram + is recorded every time a new suggestion list is received. + + Values recorded here should generally aim to be small, likely below 2ms + range. Higher values are an indicator of a performance problem. + + Layout operation should take place just once when suggestion view is shown + for the first time. + + This metric is reported for all users and uses 100microsecond granularity. + + When comparing Durations measured here, also compare Total Counts for a + correct indication of how frequently views are laid out and how the overall + time spent performing layout operation changed. + + This histogram is related to Android.Omnibox.SuggestionView.Reused, + Android.Omnibox.SuggestionList.MeasureTime, + Android.Omnibox.SuggestionView.CreateTime. + + + + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records time spent on measuring all suggestions ahead of positioning them on + screen. This histogram is recorded every time a new suggestion list is + received. + + Values recorded here should generally aim to be small, likely below 2ms + range. Higher values are an indicator of a performance problem. + + Measure operation should take place just once when suggestion view is shown + for the first time. + + This metric is reported for all users and uses 100microsecond granularity. + + When comparing Durations measured here, also compare Total Counts for a + correct indication of how frequently views are measured and how the overall + time spent measuring views changed. + + This histogram is related to Android.Omnibox.SuggestionView.Reused, + Android.Omnibox.SuggestionList.LayoutTime, + Android.Omnibox.SuggestionView.CreateTime. + + + + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records time spent creating a single suggestion. + + Values recorded here should generally aim to be small, below 1ms range. + Higher values may be an indicator of a performance problem. + + This metric is reported for all users and uses 100microsecond granularity. + + When comparing Durations measured here, also compare Total Counts for a + correct indication of how frequently views are created and how the overall + time spent creating views changed. + + This histogram is related to Android.Omnibox.SuggestionList.LayoutTime, + Android.Omnibox.SuggestionList.MeasureTime, + Android.Omnibox.SuggestionView.Reused. + + + + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records number of times a suggestion was successfully reused. + + Values recorded here tell how efficiently View reuse algorithms operate and + how frequently these algorithms have managed to prevent unnecessary view + creation. Higher Reuse counts indicate better performance. + + When analysing this metric, consider checking also the Total Counts of + Android.Omnibox.SuggestionView.CreateTime metric for a better information + regarding how view creations and re-uses have changed: + + * If this metric increased while the Total Count of the CreateTime + decreased, the change has positive effect. + + * If this metric increased (or decreased) and there is a similar change in + Total Counts of CreateTime, then the effect is neutral. + + * If this metric decreased, while the Total Count increased, then the change + has a negative effect (fewer reuses, more time spent creating views) + + This histogram is related to Android.Omnibox.SuggestionList.LayoutTime, + Android.Omnibox.SuggestionList.MeasureTime, + Android.Omnibox.SuggestionView.CreateTime. + + + + + mdjones@chromium.org + twellington@chromium.org + amaralp@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + Records how the omnibox was focused. + + + + nyquist@chromium.org + yfriedman@chromium.org + + Records the size of the user's cache at startup on Android O and above. + + + + + nyquist@chromium.org + yfriedman@chromium.org + + At startup, records the space on disk taken by Chrome application including + APK resources, compiled libraries, and extracted native code. Only recorded + for Android O and above. + + + + + nyquist@chromium.org + yfriedman@chromium.org + + Records the size of the user's data directory at startup on Android O and + above. Does not include cache size. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time the BitmapScaler spent scaling a bitmap. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the total number of images served from the high-res cache during + the lifetime of the dialog. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the total number of images sent for decoding during the lifetime of + the dialog. + + + + + finnur@chromium.org + twellington@chromium.org + + The percentage of out-of-memory decoding failures, per batch of photos (not + videos) decoded. Intended to help identify if there are devices where + decoding fails 100% of the time. Be wary at looking at other numbers in the + histogram, as a value emitted at, say, 50% may represent one failure in a + two-item decoding or 50 failures in a hundred-item decoding. These are + qualitatively different experiences for a user. + + + + + finnur@chromium.org + twellington@chromium.org + + The percentage of file error decoding failures, per batch of videos (not + photos) decoded. Intended to help identify if there are devices where + decoding fails 100% of the time. Be wary at looking at other numbers in the + histogram, as a value emitted at, say, 50% may represent one failure in a + two-item decoding or 50 failures in a hundred-item decoding. These are + qualitatively different experiences for a user. + + + + + finnur@chromium.org + twellington@chromium.org + + The percentage of IO error decoding failures, per batch of videos (not + photos) decoded. Intended to help identify if there are devices where + decoding fails 100% of the time. Be wary at looking at other numbers in the + histogram, as a value emitted at, say, 50% may represent one failure in a + two-item decoding or 50 failures in a hundred-item decoding. These are + qualitatively different experiences for a user. + + + + + finnur@chromium.org + twellington@chromium.org + + The percentage of runtime error decoding failures, per batch of videos (not + photos) decoded. Intended to help identify if there are devices where + decoding fails 100% of the time. Be wary at looking at other numbers in the + histogram, as a value emitted at, say, 50% may represent one failure in a + two-item decoding or 50 failures in a hundred-item decoding. These are + qualitatively different experiences for a user. + + + + + finnur@chromium.org + twellington@chromium.org + + The percentage of unknown decoding error failures, per batch of videos (not + photos) decoded. Intended to help identify if there are devices where + decoding fails 100% of the time. Be wary at looking at other numbers in the + histogram, as a value emitted at, say, 50% may represent one failure in a + two-item decoding or 50 failures in a hundred-item decoding. These are + qualitatively different experiences for a user. + + + + + finnur@chromium.org + twellington@chromium.org + + Records which action the user takes in the PhotoPickerDialog. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the total number of files returned from the enumeration operation. + Measured once at the end of the enumeration operation. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the enumeration rate (files per tenths of a second). Measured once + at the end of the enumeration operation. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time the BitmapScaler spent enumerating files on + disk. Measured once at the end of the enumeration operation. + + + + + finnur@chromium.org + twellington@chromium.org + + Records whether the EXIF orientation directive is present and what it is set + to. Collected once per decoded image, but only on Android N and above (and + when no IO error occurs). + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the byte count of a decoded image. Only recorded on successful + decodes. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes the decoder to decode one image. Only + recorded on successful decodes. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes to process one image decode request + (not video) end to end (RPC and actual decoding of the bits by utility + process). Recorded whether or not the RPC/decode request was successful. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes to decode all the frames needed to show + the animation -- end to end (RPC and actual decoding of the bits by utility + process). Recorded whether or not the RPC/decode request was successful. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes to process one video frame request end + to end (RPC and actual decoding of the bits by utility process). Recorded + whether or not the RPC/decode request was successful. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes to upscale a bitmap from the low-res + cache. Recorded only when there a cache miss from the high-res bitmap but a + cache hit from the low-res (placeholder) bitmap. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the byte count of the first video thumbnail. Only recorded on + successful decodes. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes the decoder to decode all the frames + needed to display an animated thumbnail. Only recorded on successful + decodes. + + + + + finnur@chromium.org + twellington@chromium.org + + Measures the amount of time it takes the decoder to decode the first frame + of a video. Only recorded on successful decodes. + + + + + twellington@chromium.org + tedchoc@chromium.org + + Whether Google Play Services is installed on the device. Recorded during + deferred startup. + + + + + twellington@chromium.org + tedchoc@chromium.org + + The version code for Google Play Services if it is installed on the device, + or 0 if it is not. Recorded during deferred startup. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Measures the amount of time spent querying for whether a WebAPK is already + installed. + + + + + aberent@chromium.org + + Whether Chrome tried to restore its settings from a previous device or + installation, and what happened when it did. Only recorded on first run. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The type of the search engine chosen by the user in Search Engine Choice + flow. + + + + + wylieb@chromium.org + fgorski@chromium.org + + Counts occurences of various events related to Search Engine Choice feature. + + + + + wylieb@chromium.org + pavely@chromium.org + fgorski@chromium.org + + Counts occurences of various events related to Search Engine Choice V2 + feature. + + + + + wylieb@chromium.org + fgorski@chromium.org + + The type of the search engine used before Search Engine Choice flow was + presented. + + + + + peter@chromium.org + rsesek@chromium.org + + Reports the status of the seccomp-bpf sandbox in photo picker decoding + processes. Anything other than "Sandbox Engaged" indicates the + sandbox is not turned on. See https://crbug.com/477049. + + + + + rsesek@chromium.org + + Reports the status of the seccomp-bpf sandbox in renderer processes. + Anything other than "Sandbox Engaged" indicates the sandbox is not + turned on. See https://crbug.com/477049. + + + + + rsesek@chromium.org + + Reports the level of kernel support for the seccomp-bpf sandbox using the + seccomp system call. + + + + + finnur@chromium.org + peter@chromium.org + + Records the number of images selected in either the new Photo Picker or the + standard Android file picker. Note: Only recorded in situations determined + to warrant the new Photo Picker (not, for example, if mixed content, like + images and text files, was requested). + + + + + peter@chromium.org + finnur@chromium.org + + Records the scope of accepted content for a select file dialog when shown by + a Web developer. + + + + + yfriedman@chromium.org + wnwen@chromium.org + + Measures the amount of time due to a StrictMode violation from calling out + to Android activity manager. + + + + + wnwen@chromium.org + yfriedman@chromium.org + + Measures time spent during StrictMode-whitelisted code in + TabPersistentStore. + + + + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from fetching for + the thumbnail cache directory. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Recorded when a survey download is requested. If the client already has + successfully downloaded a survey, 'not requested' is recorded. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + The response code of the completed survey download request. + + + + twellington@chromium.org + chrome-android-app@chromium.org + + If the infobar was visible when it was closed and if it was closed directly + or not. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Whether or not the survey was successfully shown after its download. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + The result of the survey filtering process. Each enum represents a different + filter that caught the user. This is recorded on cold starts when we check + if a user qualifies for a survey. + + + + + ssid@chromium.org + + Measures whether Chrome low-end detection logic based on RAM size matches + the Android system utility value for isLowRamDevice(). This is recorded once + per browser start and may be recorded in the renderer if isLowEndDevice() + bit is checked. + + + + + wnwen@chromium.org + twellington@chromium.org + The number of bytes written for the tab metadata file. + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Records the status of a thumbnail query from the thumbnail disk storage. + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Measures the size of the thumbnail disk storage used. Recorded during + initialization. + + + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Measures the size of the bitmap cache used. Recorded whenever a bitmap is + added to the cache. + + + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Records the status of a thumbnail query from the thumbnail provider + in-memory cache. + + + + + hazems@chromium.org + src/android_webview/OWNERS + + Track if looking up Android app resource id using + android.content.res.Resources#getIdentifier succeeds in + AndroidProtocolHandler or if it falls back to reflection look up. + + + + + laisminchillo@chromium.org + src/android_webview/OWNERS + + Records calls to WebView APIs from AndroidX. Some AndroidX-originating calls + will plumb through the framework, for example, if methods that are available + in the framework are called from the equivalent method in AndroidX. + + + + + michaelbai@chromium.org + boliu@chromium.org + + Records if WebView was attached to a Android window in 30s since WebView was + created. Nothing will be recorded if WebView has already been destroyed. + + + + + michaelbai@chromium.org + boliu@chromium.org + + Records if WebView was attached to a Android window in 3m since WebView was + created. Nothing will be recorded if WebView has already been destroyed. + + + + + michaelbai@chromium.org + boliu@chromium.org + + Records if WebView was attached to a Android window in 5s since WebView was + created. Nothing will be recorded if WebView has already been destroyed. + + + + + michaelbai@chromium.org + boliu@chromium.org + + Records how long it took for WebView to be attached to a Android window + since WebView was created. If WebView is never attached to a window, nothing + will be recorded. + + + + + timvolodine@chromium.org + ntfschr@chromium.org + Records the invocation count of WebView callbacks. + + + + laisminchillo@chromium.org + src/android_webview/OWNERS + Records ClearProxyOverride calls. + + + + chlily@chromium.org + torne@chromium.org + + The value of the cookie's SameSite attribute, if any. This is logged once + per creation of a cookie via the CookieManager API. These cookies are double + counted (once from CookieManager, logged in this histogram, and once from + CanonicalCookie::Create, logged in Cookie.SameSiteAttributeValue). + + + + + chlily@chromium.org + torne@chromium.org + + If a cookie was SameSite=None, this records whether or not it was Secure. + Logged once per attempt to set a SameSite=None cookie via CookieManager API. + These cookies are double counted (once from CookieManager, logged in this + histogram, and once from CookieMonster::SetCanonicalCookie, logged in + Cookie.SameSiteNoneIsSecure). + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the number of times the developer UI app was launched. This only + ever logs the value "true" because we only care about the total + count. This is logged in the developer UI app during Activity#onCreate. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the state of crash collection, as seen by the developer UI. This is + recorded when launching the crash UI, but only if the UI is not already + showing an error message for another problem (ex. WebView package error). + This only logs the first state we detect: ex. if the user has enabled crash + reporting by opting in and also with the flag UI, this only logs the flag UI + case. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the user's interaction with crashes in the developer UI's crash + list. Specifically, this tracks how the user interacts with the "hide + crash", "upload this crash report" or the "file bug + report" buttons and possible subsequent dialogs. Since the latter two + buttons are connected (the user must upload a crash before they can file a + bug report), we track interaction with both in the same histogram. This is + recorded for each button press in the crash list and is not recorded if the + user does not interact with any crashes. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the number of crashes shown in the developer UI. This is logged each + time the crash UI is launched and each time its list is refreshed. The UI + currently limits the number of crashes at 20, so clients logging the maximum + may have more logs sitting on disk. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the time spent blocking WebView startup to check for developer mode + (see "Android.WebView.DevUi.DeveloperModeEnabled"). This is + recorded once during WebView startup, regardless of whether developer mode + is enabled. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records whether or not WebView is starting up in "developer mode." + This is a mode where the user has enabled debugging features through the + WebView developer UI. This is recorded once during startup. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the time spent blocking WebView startup to load flags from the + developer UI. This is recorded only once during WebView startup, and only if + we've already detected developer mode is enabled (see + "Android.WebView.DevUi.DeveloperModeEnabled"). + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + This is recorded each time a user toggles a flag in the developer UI + (changing a flag's state), and logs whether the user found this flag with + the search bar ("true" means there was a non-empty search query). + This is only recorded when the user toggles an individual flag through the + Spinner dialog, not when they press the "reset all flags" button. + + + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the user's navigation to a Fragment. "FromIntent" tracks + navigations triggered by an Intent (ex. navigating to HomeFragment on + launch) and "NavBar" tracks user interaction with the bottom + navigation bar. "AnyMethod" should be the sum of the other two. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the user's selection in the developer UI overflow menu or action + bar, recorded after each selection. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records how the developer UI launcher icon for Monochrome was toggled: was + it enabled or disabled? This can be recorded either from WebView's + non-embedded processes or Chrome's browser process whenever either changes + the icon state (nothing is logged if we don't need to change the icon + state). This is only recorded in Monochrome (Android Nougat, Oreo, and Pie), + since this logic is only relevant in that case. + + + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the time spent using a specific tool, from creation to destruction. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the number of flags we will toggle for this run of WebView. This is + recorded only once during WebView startup, and only if we've already + detected developer mode is enabled (see + "Android.WebView.DevUi.DeveloperModeEnabled"). If developer mode + is disabled, we will not toggle any flags through this mechanism. + + + + + michaelbai@chromium.org + boliu@chromium.org + + Records if WebView was ever attached to a window when WebView is destroyed. + If WebView is killed by platform, nothing will be recorded. + + + + + torne@chromium.org + src/android_webview/OWNERS + + Recorded when an app passes extra headers to + WebView.loadUrl(url,extra_headers). We check if the header names and values + are valid. + + + + + torne@chromium.org + src/android_webview/OWNERS + + Records the redirect type each time that a request is redirected, if that + request contains extra headers added by the + WebView.loadUrl(url,extra_headers) API. + + + + + vasilyt@chromium.org + boliu@chromium.org + + Tracks invalidate and frame submission status for WebView hardware draw. + Result is enum that represent three flags: did we called invalidate this + frame, did renderer submitted compositor frame and whether DrawParams from + Android HWUI changed. This is logged once per WebView draw functor call. + + + + + ntfschr@chromium.org + torne@chromium.org + src/android_webview/OWNERS + + Records the scheme for the baseUrl parameter to loadDataWithBaseURL. This + also records if this value is "empty", as determined by + TextUtils.isEmpty(). + + + + + jamwalla@chromium.org + + Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/ + null, the same as the baseUrl parameter, or different from baseUrl. + + + + + ntfschr@chromium.org + torne@chromium.org + src/android_webview/OWNERS + + Records the scheme for the URL loaded by a browser-initiated navigation. + Specifically, this is the scheme of the URL passed to loadUrl() (and its + overloads), postUrl(), and loadData (this is implicitly "data:"). + also records if this value is "empty", which means either null or + "about:blank". This intentionally excludes loadDataWithBaseURL(). + + + + + hazems@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + Records the time interval between when a histogram is recorded in a + non-embedded WebView process and when it's actually sent to the UMA API in + an embedded WebView. This is recorded during WebView startup for each + histogram retrieved and replayed successfully from WebView non-embedded + metrics service. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the number of histograms received from WebView's non-embedded + histogram service. This is recorded once during WebView startup, after + retrieving histograms from the service (if the proto can be parsed). + + + + + hazems@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + Records whether metrics parsing from file in non-embedded histogram service + was successful. It's recorded during service startup by adding it to records + list. It captures the most recent file parsing result for the last service + launch before the client connects to the service. + + + + + hazems@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + Recorded by the non-embedded histogram service if it's unable to return + histograms. This is always recorded when a client connects to retrieve + histograms. + + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records whether metrics transmission from the non-embedded histogram service + was successful. This is recorded once during WebView startup, after + retrieving histograms from the service. + + + + + timvolodine@chromium.org + tobiasjs@chromium.org + ntfschr@chromium.org + + The WebViewClient error code as returned by the onReceivedError callback + This is recorded regardless of whether the network service is enabled or + disabled. + + + + + timvolodine@chromium.org + tobiasjs@chromium.org + ntfschr@chromium.org + + The WebViewClient http resonse status code as returned by the + onReceivedHttpError callback This is recorded regardless of whether the + network service is enabled or disabled. + + + + + rmcelrath@chromium.org + src/android_webview/OWNERS + + Records how long WebView blocks startup to load prefs from disk. This is + recorded once per browser process startup. + + + + + ntfschr@chromium.org + timvolodine@chromium.org + + Records the action WebView took (if any) to "fix up" secure + cookies for backwards compatibility. + + + + + laisminchillo@chromium.org + src/android_webview/OWNERS + + Records whether bypass rules were present in SetProxyOverride calls. + + + + + laisminchillo@chromium.org + src/android_webview/OWNERS + + Records the type of scheme filter in SetProxyOverride calls. + + + + + laisminchillo@chromium.org + src/android_webview/OWNERS + Records the type of url in SetProxyOverride calls. + + + + timvolodine@chromium.org + ntfschr@chromium.org + + Whether the request was intercepted by the embedder of Android WebView, and + if so which url scheme was used. Intercepted request are requests for which + the shouldInterceptRequest() callback returned a non-null response. + + + + + timvolodine@chromium.org + tobiasjs@chromium.org + ntfschr@chromium.org + + Records the custom response status code for the intercepted requests where + input stream is null. In case status code is invalid (or has not been + specified by the app) a zero status code is recorded. This UMA is needed in + order to track specific usages of request interception where the behavior + with network service enabled is different from the old code path (for more + details see go/wv-ns-behavior-differences). This data is recorded regardless + of whether the network service is enabled or disabled. + + + + + changwan@chromium.org + src/android_webview/OWNERS + + How long it takes to initialize a WebViewChromiumFactoryProvider. This is + the first major phase of the WebViewChromium construction. + + + + + changwan@chromium.org + src/android_webview/OWNERS + + How long it takes to initialize a WebViewProvider, the first time that one + is initialized. WebViewProvider initialization is the second major phase of + WebViewChromium construction. The first initialization is recorded + separately because it is usually much slower than subsequent ones. + + + + + changwan@chromium.org + src/android_webview/OWNERS + + How long it takes to initialize a WebViewProvider, the first time that one + is initialized. WebViewProvider initialization is the second major phase of + WebViewChromium construction. When it is not the first time, it is faster + and thus recorded separately. + + + + + torne@chromium.org + src/android_webview/OWNERS + + How many attempts it took to acquire the WebView data directory lock. A + value of 0 indicates that we reached the max retry count and failed to + acquire the lock successfully at all. + + + + + torne@chromium.org + src/android_webview/OWNERS + + Records whether we already tried to initialize WebView in the current + process previously, upon entry to the initialization function. This should + never be true under normal circumstances and may indicate an application + catching an exception thrown by initialization and discarding it. + + + + + laisminchillo@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + Records whether the WebViewClient provided by the app is an instance of + WebViewClientCompat (and therefore exposes AndroidX callbacks). This is + recorded each time the app sets a new WebViewClient via + WebView#setWebViewClient(). + + + + + changwan@chromium.org + src/android_webview/OWNERS + + The version of the target SDK of the app WebView is running in. This is + recorded at WebView creation. + + + + + torne@chromium.org + src/android_webview/OWNERS + + Recorded when an app passes a custom user agent to + WebSettings.setUserAgentString. We check if the UA is valid, and if not we + try to interpret it in several ways and record which (if any) made sense. + + + + + idries@google.com + src/android_webview/OWNERS + + Records the global visibility state of WebView in seconds. The Visible + bucket counts total seconds that any WebView was visible (the view itself + was visible, and was attached to the view hierarchy of a visible window). + The NotVisble bucket counts time since WebView initialization for which no + WebView was considered visible, or no WebView existed. The total of these + two buckets reflects the amount of time covered by metrics collection. + + + + + idries@google.com + src/android_webview/OWNERS + + Records per-WebView visibility duration in seconds. The Visible bucket + counts the total time in seconds that each WebView was considered visible + (the view itself was visible, and was attached to the view hierarchy of a + visible window). If more than one WebView is considered visible, then each + WebView contributes independently. The NotVisible bucket counts the duration + that each WebView exists but not in a visible state. As with the Visible + bucket, each WebView contributes independently, and thus this bucket is not + incremented when no WebViews exist. + + + + + idries@google.com + src/android_webview/OWNERS + + Identical to Android.WebView.Visibility.Global except that the + OpenWebContentVisible bucket only records time that any WebView is visible + and displaying contents which originate from the 'Open Web' (in this context + that is taken to mean having an HTTP or HTTPS scheme). The + OpenWebContentNotVisible bucket records time when the WebView was not + visible or not displaying contents which originate from an HTTP or HTTPS + scheme. + + + + + idries@google.com + src/android_webview/OWNERS + + Identical to Android.WebView.Visibility.PerWebView except that the + OpenWebContentVisible bucket only records time that each WebView is visible + and displaying contents which originate from the 'Open Web' (in this context + that is taken to mean having an HTTP or HTTPS scheme). The + OpenWebContentNotVisible bucket records time when each WebView was not + visible or not displaying contents which originate from an HTTP or HTTPS + scheme. + + + + + wylieb@chromium.org + lzbylut@chromium.org + + Counts occurences of various events related to the Search Engine Logo + feature. When enabled, the feature will show the logo of the default search + engine in the omnibox. These events record the performance of fetching + non-Google logos. + + + + + azeemarshad@chromium.org + jonmann@chromium.org + better-together-dev@google.com + + Records effective final success/failure when trying to install Android + Messages for Web PWA. This is recorded once when any one of the installation + attempts succeed or when all attempts fails, irrespective of number of + retries. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Records message types for which all retry attempts failed when dispatching + to Android Messages for Web Service-Worker. This is recorded when using FCM + web push for background notificaitons. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Records message types for which a retry was attempted when dispatching to + Android Messages for Web Service-Worker. This is recorded when using FCM web + push for background notificaitons. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Records message types for which dispatching to Android Messages for Web + Service-Worker succeeded. This is recorded when using FCM web push for + background notificaitons. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Indicates the feature state of the Messages feature. This metric is emitted + to at the creation of the user session (when the user logs in), and when + feature state updates occur. + + + + + azeemarshad@chromium.org + jonmann@chromium.org + better-together-dev@google.com + + Records the number of installations attempted for Android Messages for Web + PWA before succeeding. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Records installation result code for every installation attempt for Android + Messages for Web PWA initiated through Multidevice setup or settings. This + metric also includes installation result for every failed retry. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Records success/failure for when Android Messages for Web PWA is + uninstalled. The PWA is uninstalled when the messages URL changes, resulting + in the PWA being uninstalled at the old URL and reinstalled at the new URL. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Tracks the duration of time for which the Android Messages for Web Service- + Worker is handling background connection. + + + + + azeemarshad@chromium.org + better-together-dev@google.com + + Tracks dispatch success/failure status of the start streaming message sent + to the Android Messages for Web Service-Worker. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/apps/histograms.xml b/tools/metrics/histograms/histograms_xml/apps/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..ef7905f34f656b745c8b4601b697a6a8c96018e9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/apps/histograms.xml @@ -0,0 +1,1727 @@ + + + + + + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of creating shortcuts for an Extension, specifically from + the user clicking on "Create Shortcut" on the chrome://apps page, + in the right click menu of the respective Extension icon. + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of creating shortcuts for a WebApp, specifically from the + user clicking on "Create Shortcut" on the chrome://apps page, in + the right click menu of the respective WebApp icon. + + + + + sashab@chromium.org + + The number of times the app info dialog is launched. This is gathered each + time the app info dialog is opened, from each of the places the dialog can + be opened from. + + + + + sashab@chromium.org + + The location of the app that the dialog was opened for. This is gathered + each time the app info dialog is opened. + + + + + sashab@chromium.org + + The type of the app that the dialog was opened for. This is gathered each + time the app info dialog is opened. + + + + + tapted@chromium.org + benwells@chromium.org + + The number of times v2 packaged apps are launched grouped by + extension_misc::AppLaunchBuckets. See also Extensions.AppLaunch. + + + + + pdyson@chromium.org + + The number of apps the were not able to be ranked by the Aggregated ML app + ranker (Top Cat). + + + + + pdyson@chromium.org + + The number of apps successfully ranked by the Aggregated ML app ranker (Top + Cat). + + + + + thanhdng@chromium.org + jiameng@chromium.org + + The type of errors that occur during the inference of Search Ranking + aggregated model. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending an answer card request and receiving the + notification that answer card has finished loading. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending an answer card request and receiving the + notification navigation has been finished with a valid answer card. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending a non-empty query to AppSearchProvider and + receiving results back. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending an empty query to AppSearchProvider and receiving + Zero State recommendation results back. + + + + + anasalazar@chromium.org + newcomer@chromium.org + + The different ways to add page in app list's apps grid. Logged when the page + is created. + + + + + + + anasalazar@chromium.org + tbarzic@chromium.org + + Relative smoothness of animations of entering or exiting the cardified state + in the apps grid. 100% represents ideally smooth 60 frames per second. 50% + represents only 30 frames per second is achieved during the animations. 0% + should not happen. This metric is recorded one time per apps grid page each + time we enter or exit cardified state in the apps grid. + + + + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + The number of results returned from a call to the Drive QuickAccess API. + Only reported if the API call did not error. + + + + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + Whether or not the results cache is empty. An empty cache means either poor + network conditions, the user opening zero-state very quickly, or an API + error. + + + + + tby@chromium.org + jiameng@chromium.org + + Whether or not the cache of Drive file results has already been warmed with + a request to ItemSuggest. Emitted each time we decide whether to warm the + cache, ie. each time Drive FS is mounted. + + + + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + Whether or not DriveFS is mounted on a call to + DriveQuickAccessProvider::Start or ::GetQuickAccessItems. + + + + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + The error code returned from a call to the Drive QuickAccess API. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The time between when GetQuickAccessItems was last called, and receiving + Drive QuickAccess results back. Only reported if the API call did not error. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The time between sending a zero state query and receiving file + recommendations back from the DriveQuickAccessProvider. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The time between when GetQuickAccessItems was last called, and the user + entering zero state search. + + + + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + Counts how many results from one call to the QuickAccess API exist in the + DriveFS mount and are OK for display. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending a non-empty query and receiving results back from + the extension which performs the file search. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending an non-empty query and receiving search results + back from OmniboxProvider which queries chrome AutocompelteController's + search providers to get the results. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The time between sending an empty query and receiving zero state + recommendations back from OmniboxProvider which queries chrome + ZeroStateProvider and gets recent queries back from Google Autocomplete + server. + + + + + jiameng@chromium.org + tby@chromium.org + + Various error states of the provider for OS settings in the cros launcher. + Emitted only in the case of an unexpected error, the bucket proportion is + not meaningful. + + + + + jiameng@chromium.org + tby@chromium.org + + The latency of a search in the OsSettingsProvider. Recorded each time a + search is completed, even if it returns no results. Not recorded if the + query is too short to perform a search at all. Chrome OS only. + + + + + thanhdng@chromium.org + jiameng@chromium.org + + The length of the query that resulted in an app launch from search box. This + metric only records non-empty queries. + + + + + thanhdng@chromium.org + jiameng@chromium.org + + The number of app launches from the search box with non-empty queries. + + + + + wrong@chromium.org + jiameng@chromium.org + + Whether or not the user has enabled Suggested Content in the launcher. This + is logged once per UMA upload, and only for any user that has the Suggested + Content toggle feature flag enabled. + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted when a suggestion chip is launched. Currently only 'true' is used, + but we may emit 'false' in future to track abandonment. + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted when a suggestion chip is launched, records the index (position in + the bar) of that chip. The left-most chip is index 0 and the maximum index + is 4. + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted when a suggestion chip is launched, records the type of that chip. + + + + + tby@chromium.org + jiameng@chromium.org + + Records error when processing user events into Apps.AppList.UserEvent.* + metrics. These are expected to be rare and bucket proportion is not + meaningful. + + + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted on a usage of the launcher, and records overall impressions, + launches, and abandons for a launcher UI view. The bucket proportion is not + meaningful for this metric, because impressions are a superset of launches + and abandons. Instead, the ratio between buckets can be used to calculate + accurate overall CTR. + + + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted after an impression, if the user then closes the launcher or moves + to a different view without launching any search result. This is emitted + once per abandon, per displayed result. Records the displayed result's type. + See Apps.AppList.UserEvent.TypeImpression for more details. + + This metric is completed by a histogram suffix describing which UI surface + the results are recorded from. + + + + + + + tby@chromium.org + jiameng@chromium.org + + When a set of results is displayed for 2 seconds and the user has probably + seen it, or the user interacted with the results and has definitely seen it, + we consider it an impression. + + Emitted once per impression for each displayed result. Records the type of + the displayed result, eg. native app or omnibox bookmark. + + The Apps.AppList.UserEvent.Type* metrics are directly comparable + per-result-type. So, for example, (launches / impressions) for a result type + gives an accurate CTR. + + This metric is completed by a histogram suffix describing which UI surface + the results are recorded from. + + + + + + + tby@chromium.org + jiameng@chromium.org + + Emitted after an impression, if the user launches a result. Records the type + of the launched result. See Apps.AppList.UserEvent.TypeImpression for more + details. + + This metric is completed by a histogram suffix describing which UI surface + the results are recorded from. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The time between sending a zero state query and receiving file + recommendations back from the ZeroStateFileProvider. + + + + + tby@chromium.org + edimitriadis@chromium.org + + Emitted when the ZeroStateFileProvider is created, records whether the + FileTasksNotifier creation succeeded for the given profile. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The type of item that was launched from a zero state launcher search result. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + Logs the result score received from the Drive Quick Access provider. The + original float score is scaled to range from 0 to 100 and its floor is + recorded. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + Logs the result score received from the Omnibox search provider. The + original float score is scaled to range from 0 to 100 and its floor is + recorded. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + Logs the result score received from the zero state file provider. The + original float score is scaled to range from 0 to 100 and its floor is + recorded. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + Whether an item was clicked from zero state search results, or if results + were displayed for some amount time but not clicked. These clicks and + impressions are used for calculating CTR metrics. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + Whether a set of search result impressions contains any Drive QuickAccess + file results. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The number of zero state impressions that contained at least one result of + the specified file type. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The position index of an item launched from zero state search results. + + + + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The number of item types included in each zero state impression set. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The decision of the user whether to remove a zero state search result. This + is gathered per click of a remove or cancel button of a search result + removal confirmation dialog. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The type of the action user performed on zero state search result. This is + gathered per click of a remove or append button of a search result. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The type of the app list suggestion that was opened by user in zero state. + + + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The number of apps launched from the launcher and shelf for each launcher + state. This is incremented each time an app is launched. Each bucket + represents where in the launcher or shelf the app was launched from. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The different ways to move an app in app list's apps grid. Logged when the + app moving succeeds. + + + + + charleszhao@chromium.org + pdyson@chromium.org + + The type of app clicked in the launcher on ChromeOS, recorded after the icon + is clicked, before it is launched. + + + + + newcomer@chromium.org + + Number of apps (including ones in folders) with Chrome badge, across all + Launcher pages. This is gathered per open-launcher event. + + + + + calamity@chromium.org + + The amount of time it takes to build the app list UI. This is logged each + time the app list is built from scratch. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The type of the default result opened by user by pressing ENTER key. + Launcher UI shows suggested apps, recent queries, etc when user activates + the search box, or shows matched apps (installed apps, play store app + results, etc.) and other results (query suggestions, web site, bookmark, + files, etc) when user types a query. It will set the focus on the first + result as the default. User can open the default result by simply pressing + ENTER key. This metrics logs the type of the default result (installed app, + play store result, query suggestion, etc) opened by user pressing ENTER key. + + + + + wutao@chromium.org + + Relative smoothness of animations of showing and hiding app list folder. + 100% represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user starts the folder + animation in the launcher. + + + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The folder name length in characters when an app list folder gets renamed. + Logged when the folder name is changed and the texfield is no longer in + focus. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The number of times folders are opened in the app list. This is logged when + the folder is clicked. + + + + + newcomer@chromium.org + mmourgos@chromium.org + + Elapsed time from the input event to hide the launcher UI. This is logged + each time the launcher is dismissed by pressing search key, clicking shelf + button, or focusing out side of the launcher. + + + + + wutao@chromium.org + + The internal app in apps grid was opened by the user. This is gathered per + click of an internal app. + + + + + wrong@chromium.org + jiameng@chromium.org + + Logs the length of user typed queries that result in launcher clicks. + Emitted each time the user opens a launcher search result after typing a + query. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The UMA histogram that logs the length of user typed queries app list + launcher issues to the search providers. + + + + + calamity@chromium.org + src/ash/app_list/OWNERS + + The page that the app list goes to. This is gathered every time the user + initiates a transition to another page in the launcher. + + + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The source used to switch pages in the app list's app grid. Logged when the + page switch succeeds. + + + + + newcomer@chromium.org + + Replaced with Apps.AppListPeekingToFullscreenSource on 9/2017. + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The source which transitions the app list from Peeking to Fullscreen. This + is logged when the transition method is used. + + + + + jennyz@chromium.org + newcomer@chromium.org + + The index of the app within all play store apps displayed when it is + launched. + + + + + hejq@chromium.org + The state of a Play Store app search request. + + + + jennyz@chromium.org + newcomer@chromium.org + + The number of the play store apps displayed to user for a query. + + + + + napper@chromium.org + robsc@chromium.org + + When a user opens an app recommendation result, this is the number of times + we showed the result before opening. Number of times shown is reset to 0 + every 30 days, and is held on device. + + + + + napper@chromium.org + robsc@chromium.org + + Response when parsing the recommended app list from Play Store for candidate + app list, recorded every time a response from the play store is parsed in + client. + + + + + napper@chromium.org + robsc@chromium.org + + Number of responses from server in Apps.AppListRecommendedResponse.count + when fetching appListRecommendded GetAppReinstallCandidates. + + + + + napper@chromium.org + robsc@chromium.org + + Milliseconds elapsed to fetch appListRecommended GetAppReinstallCandidates. + + + + + tby@chromium.org + jiameng@chromium.org + + The index of a clicked result in the search result box and the length of the + search query. The index is relative to the SearchResultListView, not the + overall position in the suggestion window. + + + + + thanhdng@chromium.org + jiameng@chromium.org + + This boolean records if the query that introduces a launch in the results + list is empty or not. This will be recorded every time the user clicks an + item in the launcher results list. + + + + + jennyz@chromium.org + jiameng@chromium.org + + The length of the query when the user abandons results of a queried search + or recommendations of zero state (zero length query) in launcher UI. + + + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The number of times the applist searchbox has been activated. This is split + by keystroke, mouse press, and gesture tap activations. This is gathered + each time the searchbox goes from inactive to active, not necessarily empty + to non-empty. + + + + + tapted@chromium.org + + The number of searches that are started in the app list. This is gathered + each time the app list search box transitions from empty to non-empty. + + + + + jennyz@chromium.org + newcomer@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + The type of app list search omnibox result that was opened by the user. This + is gathered per OmniboxResult opened in the app list's launcher suggestion + window. + + + + + + + calamity@chromium.org + + The length of the app list search query when a result is opened. This is + gathered per click of a search result. + + + + + wutao@chromium.org + + The app list search result of an internal app that was opened by the user. + This is gathered per click of a search result. + + + + + wutao@chromium.org + + The app list search result of an internal app that was shown to the user. + This is gathered per creation of a search result. Note: Typing a word with + multiple letters could trigger multiple creations of the search result. + + + + + calamity@chromium.org + src/ash/app_list/OWNERS + + The display type of the app list search result that was opened by the user. + This is gathered per click of a search result. + + + + + newcomer@chromium.org + The state of the app list when a search result was opened. + + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The type of app list search result that was opened by the user. This is + gathered per SearchResult opened. Only recorded for search results shown in + the search result page of the launcher (suggestion chips are not recorded). + + + + + newcomer@chromium.org + mmourgos@chromium.org + + Elapsed time from the input event to show the launcher UI. This is logged + each time the app list is shown by pressing search key, clicking shelf + button, or swiping from shelf. + + + + + newcomer@chromium.org + + The number of times the different sources for showing the app list are used. + This is logged when the app list is shown. Does not count the app list shown + when the last window is closed in tablet mode. This is not the total number + of times the app list is shown to the user; for that consult the user action + AppList_WindowFocused. + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The number of transitions from the different AppListStates. This is gathered + each time the launcher transitions from various states in + AppListView::SetState (Peeking, Half, Fullscreen All Apps, Fullscreen + Search, and Closed). Not all state transitions are collected because they + are not meaningful in measuring user activity. + + + + + newcomer@chromium.org + charleszhao@chromium.org + + The number of times suggested chips are launched at each suggested-apps + tile. An index i, ranged from 0 to kNumStartPageTiles - 1, is logged each + time a suggested chip is launched from i-th tile. + + + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The type of app list suggestion chip that was opened by the user. This is + gathered per SuggestionChip opened. + + + + + jackhou@chromium.org + + Counts which major milestone versions of app_mode_loader are sending + --app-shim-error. --app-shim-error is sent as a command line argument to + Chrome when app_mode_loader was unable to dyload the Chrome Framework and + call ChromeAppModeMain. For example, when Chrome updates from 32-bit to + 64-bit, an older shim will find the new framework version but fail to dyload + it. + + + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The total number of apps in folders ignoring OEM folders. This is logged + each time the app list is initialized. The + "FullscreenAppListDisabled" suffix has been deprecated. + + + + + ajlinker@chromium.org + dominickn@chromium.org + nancylingwang@chromium.org + + Records whether an application has bounced (been uninstalled in less than + seven days). Recorded when an application is uninstalled. + + + + + + + newcomer@chromium.org + mmourgos@chromium.org + + The number of times a certain command was executed by a context menu, split + by whether the context menu came from an app, or another part of the system + UI. + + + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The show source (touch, mouse, keyboard, etc) for a context menu. Split by + the component from which the context menu originated. + + + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The user journey time for a ContextMenu, defined as the time between + launching a context menu and the context menu's close callback being + activated. Not recorded whenever the context menu is not for an app icon on + the shelf. + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of creating shortcut image for web app on Linux. + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of creating shortcut for web app on Linux. + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of creating shortcut for web app on MacOS. + + + + + + + dominickn@chromium.org + nancylingwang@chromium.org + nigeltao@chromium.org + + Records when a user attempts to launch a particular Chrome OS app. + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of re-creating shortcut during file handler registration + process for PWA on Linux + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of file handler registration for PWA on Linux + + + + + phillis@chromium.org + cmumford@chromium.org + + Records the result of file handler registration for PWA on Windows + + + + + + + andrewxu@chromium.org + newcomer@chromium.org + + Relative smoothness of animations of launcher transitions in tablet mode. + 100% represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user triggers launcher + animation in tablet mode. + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of installing an app on the chrome://apps page. This + happens when a user drags a link to this page. + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of locally installed an app on the chrome://apps page, + which involves hooking up Os integration. Specifically, this records if the + shortcuts were created successfully. This happens whena user right-clicks on + a greyed out webapp icon in the chrome://apps page and clicks + "Install". + + + + + wrong@chromium.org + jiameng@chromium.org + + Whether or not the most recent Launcher search query differs from the + previous query in length by more than one character. Search queries are + issued incrementally as the user types, so this will approximately + differentiate between incremental and non-incremental search queries. + Emitted on each change to the launcher search query. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time needed to create a lock screen apps profile. This metric + is recorded only if the profile creation was successful. The lock screen + apps profile is created if the user has an app enabled on Chrome OS lock + screen, and is used as the context in which the app is launched on top of + the lock screen. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Boolean indicating whether the lock screen apps profile creation succeeded. + The lock screen apps profile is created if the user has an app enabled on + Chrome OS lock screen, and is used as the context in which the app is + launched on top of the lock screen. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The size of a data item stored in the lock screen data item storage using + chrome.lockScreen.data API as sent from the app - the item will be encrypted + before getting stored in the storage. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The size of an encrypted data item stored in the lock screen data item + storage using chrome.lockScreen.data API. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time it took to complete a lock screen data item storage + operation. Reported only on the operation failure. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time it took to complete a lock screen data item storage + operation. Reported only on the operation success. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The result of a lock screen data item storage operation returned through + chrome.lockScreen.data extension API. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The number of data items saved in the lock screen data item storage per app. + This is recorded on startup, when the app attempts to use the + chrome.lockScreen.data API. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Reported when a user attempts to launch a note taking app on the lock + screen. It reports the note taking app state in the lock screen apps profile + at the launch attempt time - for example, whether the app was enabled, or + whether the app had been terminated and an app reload was attempted. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time a lock screen enabled app window spent in a certain state + during the app window activity. The state to which the histogram refers to + is defined by the suffix. The metric is logged upon leaving the associated + state. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The note taking action availability state on the lock screen, recorded when + the user session is locked. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The state in which lock screen enabled note taking app was when the note + taking session ended. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount time a lock screen app had been launching when the app launch was + canceled. Logged if the lock screen app session ends before the lock screen + app window is shown. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Ordinal number of a note taking app launch request from a lock screen within + a lock screen session. If a note taking app is launched n times during a + single lock screen session, this histogram will be reported with values 1 + through n. The launch counter is reset on screen unlock. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The user action that launched note taking from the lock screen. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Reported when a note taking app is unloaded from the lock screen apps + profile while lock screen note taking is available. Reports the unload + reason type, which can be used to deduce whether the app can be reloaded in + the profile. The app unload event is not reported if the app is unloaded due + to lock screen note taking becoming unavailble (e.g. when the user unlocks + the screen). + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Amount of time needed to install a copy of a lock screen note taking app + into lock screen apps profile. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The reason the note taking on lock screen was ended (and lock screen app + window was closed). + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + Reported when a note taking app is terminated in the lock screen apps + profile. It reports the number of times the app was reloaded in the lock + screen apps profile during the current lock screen session (prior to the + termination). + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time needed to load a note taking app window contents on the + lock screen - i.e. the time passed from the user requesting an app launch to + the app window contents being loaded. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The amount of time needed to launch a note taking app window from the lock + screen - i.e. the time passed from the user requesting an app launch to the + app window appearing on the screen. + + + + + jiameng@chromium.org + thanhdng@chromium.org + tby@chromium.org + + Records number of clicks on search result for different display types in + zero-state. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The result of attempting to launch a default note-taking app on Chrome OS. + Only reported if the preferred app was unspecified or failed to launch. + + + + + dstockwell@chromium.org + tbuckley@chromium.org + + The result of attempting to launch the user-specified preferred note-taking + app, if any, on Chrome OS. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The number of folders that users have in their Launcher. Includes the OEM + folder. This metric is recorded every time the launcher is shown. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The number of pages that users have in the top level apps grid of their + Launcher. This metric is recorded every time the launcher is shown. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + The number of pages that are not full in the top level apps grid of + Launcher. This metric is recorded every time the launcher is shown. + + + + + + + newcomer@chromium.org + wutao@chromium.org + + Base name is deprecated as of 3/2019 in favor of + Apps.PaginationTransition.AnimationSmoothness.ClamshellMode and + Apps.PaginationTransition.AnimationSmoothness.TabletMode + + Relative smoothness of animations of launcher pagination transitions. 100% + represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user starts the pagination + transition animation of the launcher. + + + + + + + omrilio@chromium.org + newcomer@chromium.org + + Presentation time for the apps grid scrolling operation. This starts when + drag starts by gesture and ends before the patination animation starts. The + smoothness of the pagination animation is recorded in + Apps.PaginationTransition.AnimationSmoothness.{TabletMode|ClamshellMode}. + + + + + + + omrilio@chromium.org + newcomer@chromium.org + + Maximum latecy reported during one drag to scroll operation on apps grid. + + + + + dominickn@chromium.org + mxcai@chromium.org + + Recorded at the time a read/write operation happens for preferred app to + indicate whether the I/O succeeded or not. + + + + + dominickn@chromium.org + mxcai@chromium.org + + Recorded at the time a update operation happens for preferred apps to + indicate the type of update action. + + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Relative smoothness of animations of the scrollable shelf when scrolling. + 100% represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user scrolls over the + scrollable shelf. + + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Presentation time of the drag scroll in the scrollable shelf in + milliseconds. + + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Maximum latency of the presentation time of the drag scroll in the + scrollable shelf. + + + + + cmumford@chromium.org + rahsin@microsoft.com + + Records the result of shortcuts menu registration for PWA on Windows + + + + + cmumford@chromium.org + rahsin@microsoft.com + + Records the result of shortcuts menu unregistration for PWA on Windows + + + + + + + newcomer@chromium.org + + Relative smoothness of animations of peeking launcher state transitions. + 100% represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user switches states of the + launcher. + + + + + + + omrilio@chromium.org + newcomer@chromium.org + + Presentation time of the app launcher drag operation in milliseconds. + + + + + + + omrilio@chromium.org + newcomer@chromium.org + + Maximum latency of the presentation time of the app laucnher drag operation. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/arc/histograms.xml b/tools/metrics/histograms/histograms_xml/arc/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..784b66446493fbee902a72e473ad1019b38977c9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/arc/histograms.xml @@ -0,0 +1,1101 @@ + + + + + + + + + + hirokisato@chromium.org + sarakato@chromium.org + + Whether the ARC window is opened with TalkBack enabled or not. Counted when + a user opens a window or toggles the feature. Checked only when the spoken + feedback is enabled in Chrome OS. + + + + + dominickn@chromium.org + lgcheng@google.com + nancylingwang@chromium.org + + The adaptive Arc app icons are loaded from ArcAppIcon. Recorded whether the + icon is the adaptive icon when the icon is loaded. + + + + + dominickn@chromium.org + lgcheng@google.com + nancylingwang@chromium.org + + The adaptive Arc app icons are loaded from ArcAppIcon for default Arc apps. + Recorded whether the icon is the adaptive icon when the icon is loaded. + + + + + dominickn@chromium.org + lgcheng@google.com + nancylingwang@chromium.org + + The adaptive Arc app icons are loaded from Non ArcAppIcon. Recorded whether + the icon is the adaptive icon when the icon is loaded. + + + + + victorhsieh@chromium.org + tbuckley@chromium.org + + Record user's choice or error during ADB sideloading opt-in UI after reboot. + + + + + elijahtaylor@google.com + shihuis@google.com + The time elapsed for booting up the ARC instance. + + + + elijahtaylor@google.com + shihuis@google.com + + The number of ARC apps open at any given time. Collected every 5 minutes. + This indicates both how many users are engaging with apps and, when they do + engage, how many apps they are engaging with at a time. + + + + + robsc@chromium.org + napper@chromium.org + + Record a reason when an arc application completes installation successfully, + including policy based applications, default applications and user prompted + installations. + + + + + robsc@chromium.org + napper@chromium.org + + Record a count of an impression of FAR result. This is a count _any_ time + it's shown, even for a millisecond. + + + + + robsc@chromium.org + napper@chromium.org + + Record a count of an impression of FAR result. This is a count of heuristic + real impressions: a new showing after a while, a longer showing, etc. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + Record the time to build ARC app shortcut items on menu model. We get the + needed metadata from Android and decode icons in the utility process. It is + an asynchronous procedure so we need to know the longest waiting time. + + + + + elijahtaylor@google.com + shihuis@google.com + + Total number of ARC apps installed on a device measured at startup. Note: + This includes launchable apps that are installed by default, such as Play + Store and Settings, as well as any vendor specific apps. + + + + + robsc@chromium.org + napper@chromium.org + + Record a reason why an application was uninstalled when uninstall is + completed. + + + + + + + mhasank@google.com + arc-core@google.com + The status of account check before GMS Sign-in. + + + + + + mhasank@google.com + arc-core@google.com + + Elapsed time waiting for the account status check to be completed. This is + not recorded in case of account status check failure. + + + + + + + mhasank@google.com + arc-core@google.com + + Number of attempts done while waiting for the check-in task to be completed. + 0 means that device was already checked-in. This is recorded in case + check-in task is completed successfully. + + + + + + + mhasank@google.com + arc-core@google.com + + Elapsed time waiting for the check-in task to be completed. This is recorded + in case check-in task is completed successfully. + + + + + mhasank@google.com + arc-core@google.com + Contains the status of main account resolution. + + + + + + mhasank@google.com + arc-core@google.com + + Elapsed time waiting for network connection before starting other + authorization operations. + + + + + + + mhasank@google.com + arc-core@google.com + Elapsed time waiting for GMS sign-in to complete. + + + + elijahtaylor@google.com + shihuis@google.com + + The relative time of a boot progress event since the ARC starts. + + + + + elijahtaylor@google.com + xzhou@google.com + Code installation result for ARC boot continue. + + + + elijahtaylor@google.com + xzhou@google.com + + Total time needed to check the integrity of host generated code. If + signature checking fails, it also includes the time to regenerate and sign + the code. + + + + + elijahtaylor@google.com + xzhou@google.com + Host code relocation result. + + + + elijahtaylor@google.com + xzhou@google.com + Time needed to relocate boot*.art files. + + + + elijahtaylor@google.com + xzhou@google.com + Time needed to sign boot*.art files. + + + + elijahtaylor@google.com + xzhou@google.com + + Code verification result for host generated code for boot for login screen. + + + + + elijahtaylor@google.com + xzhou@google.com + Time needed to verify host generated code. + + + + sstan@google.com + bartfab@chromium.org + giovax@google.com + + Records the number of times ChromeOS Companion Library API called. Counter + adding when its Stub library receive the call from applications. + + + + + alexchau@google.com + emaxx@google.com + + Elapsed time from the policy update notification sent to ARC to the + corresponding successfully obtained compliance report from CloudDPS. + + + + + elijahtaylor@google.com + yusukes@google.com + + The number of ARC container lifetime events. One START event and up to one + non-START event are recorded per ARC session, which ends when the user opts + out from ARC or signs out. + + + + + elijahtaylor@google.com + yusukes@google.com + + The number of times ARC container crashes and automatically restarts in one + ARC session, which ends when the user opts out from ARC or signs out. + + + + + wvk@google.com + khmel@google.com + + Records the time that throttling was disabled due to a particular throttle + observer. The duration begins when a new throttle observer becomes active, + and measures until it becomes inactive or another throttle observer becomes + effective. + + + + + elijahtaylor@google.com + shihuis@google.com + + ARC use time. The use time is incremented in regular intervals while android + container is active. Reported at most once a day, at which point accumulated + time is reset (which means that sum of reported times for a OS version would + give an estimate of ARC usage time per OS version). + + + + + skau@chromium.org + vkuzkokov@google.com + + The number of pages sent to a native printer by ARC. Reported for every + print job originating in ARC container and sent to a CUPS printer. + + + + + hashimoto@google.com + shihuis@google.com + + Reason why a custom tab session ended. Recorded when a session ends. + + + + + hashimoto@google.com + Lifetime of each session. Recorded when a session ends. + + + + hashimoto@google.com + + Lifetime of each session. Recorded when a session is closed. + + + + + hashimoto@google.com + + Lifetime of each session. Recorded when a session ends because the tab was + forwarded to a normal tab. + + + + + maajid@google.com + shaochuan@google.com + shihuis@google.com + + Total of Arc.EngagementTime.Background and Arc.EngagementTime.Foreground. + Note that this differs from Arc.EngagementTime.Total in that this is the + ARC++ engagement time, while Arc.EngagementTime.Total is the CrOS total + engagement time on devices with ARC++ enabled. See Arc.EngagementTime.Total + for definition of engagement and further details. + + + + + maajid@google.com + shaochuan@google.com + shihuis@google.com + + Times when user is engaged and ARC++ apps are running in the background, but + the user isn't focusing on an ARC++ app window. See Arc.EngagementTime.Total + for definition of engagement and details. + + + + + maajid@google.com + shaochuan@google.com + shihuis@google.com + + Times when user is engaged and focuses on an ARC++ app window. See + Arc.EngagementTime.Total for definition of engagement and details. + + + + + maajid@google.com + shaochuan@google.com + shihuis@google.com + + Total CrOS user session time (from login to logout) excluding times when + user "disengages": screen is locked or dims down due to user idle. + Engagement time metrics, along with foreground and background time, are only + collected on users with ARC++ enabled. All four metrics are accumulated and + recorded to UMA once a day. For Total ARC++ engagement time, please see + Arc.EngagementTime.ArcTotal. + + + + + fukino@chromium.org + yusukes@chromium.org + + When a removable media is mounted, whether Android apps have full access to + the media. Users can allow full access in Settings. Changing the preference + in Settings is tracked by Arc.ExternalStorage.SetVisible. + + + + + fukino@chromium.org + yusukes@chromium.org + + When a user clicks a toggle switch in "External storage + preferences" screen, where the new value is ENABLED or not. + + + + + yusukes@google.com + khmel@google.com + + How long the user sees the spinning icon waiting for ARC container boot. + Zero when the container has already been up and running when the user + launches the ARC app. + + + + + yusukes@google.com + khmel@google.com + + Elapsed time from the when UI is shown after login to when the user + activates first ARC app. + + + + + alexchau@google.com + emaxx@google.com + + Elapsed time from the signing in process start to a successfully obtained + compliance report from CloudDPS. + + + + + alexchau@google.com + emaxx@google.com + + Elapsed time from ARC startup to a successfully obtained compliance report + from CloudDPS. This value is not reported during the first startup when + signing in happens. + + + + + khmel@google.com + lgcheng@google.com + + Elapsed time of first 5 compressed app icons is loaded from file system. + Recorded when the app icon loading completes. + + + + + khmel@google.com + lgcheng@google.com + + Elapsed time of other compressed app icons is loaded from file system. + Recorded when the app icon loading completes. + + + + + khmel@google.com + lgcheng@google.com + + Elapsed time of first 5 uncompressed app icons is loaded from file system. + Recorded when the app icon loading completes. + + + + + khmel@google.com + lgcheng@google.com + + Elapsed time of other uncompressed app icons is loaded from file system. + Recorded when the app icon loading completes. + + + + + yhanada@chromium.org + tetsui@chromium.org + + The number of IME apps installed. Collected at startup and when an IME app + is installed or uninstalled. + + + + + hashimoto@google.com + shihuis@google.com + + Types of things opened via ARC IntentHelperHost interface. Recorded when one + of the "open" methods of the interface is called. + + + + + elijahtaylor@google.com + shihuis@google.com + Cumulative count of low memory kills in one user session. + + + + cywang@google.com + elijahtaylor@google.com + shihuis@google.com + + When Chrome OS is in low memory state, TabManager kills some victims to free + memory. This value is the elapsed time between TabManager receiving the low + memory notification and the first kill. + + + + + elijahtaylor@google.com + shihuis@google.com + The memory size freed by each low memory kill event. + + + + elijahtaylor@google.com + shihuis@google.com + The elapsed time to last low memory kill event. + + + + elijahtaylor@google.com + levarum@google.com + + Native bridge used for ARC. Can be unknown and none. This is collected along + with Arc.State during every metrics recording interval, so it is in every + record uploaded to the server (despite crbug.com/929583 which was fixed in + M73). This is required because this value is used to categorize all other + data in the dashboard as collected with specific native bridge in use. Since + M74 this is also included in initial stability logs. + + + + + elijahtaylor@google.com + shihuis@google.com + Cumulative count of OOM kills in one user session. + + + + elijahtaylor@google.com + shihuis@google.com + Arc OptIn action taken by user. + + + + elijahtaylor@google.com + shihuis@google.com + Arc OptIn cancelation reason. + + + + elijahtaylor@google.com + khmel@google.com + Arc OptIn flow result. + + + + elijahtaylor@google.com + + Arc Silent Auth Code status. This status is set during the ARC OptIn flow. + + + + + khmel@google.com + + Arc Silent Auth Code status. This status is set during the ARC + Device/Primary Account reauthorization flow. + + + + + khmel@google.com + + Arc Silent Auth Code status. This status is set during the minting of an + auth code for a Secondary Account. It can be set for Secondary Account + signin or reauthorization. + + + + + + + jhorwich@google.com + khmel@google.com + State of PlayAutoInstall flow after the request. + + + + + + jhorwich@google.com + khmel@google.com + + Elapsed time from the when the PlayAutoInstall request was issued and + completed. + + + + + khmel@google.com + yusukes@google.com + + Elapsed time from the when the user launches the Play Store app and to when + the Play Store window is shown to the user. + + + + + jennyz@chromium.org + newcomer@chromium.org + + Time between a default play store result being activated by user pressing + ENTER key and being displayed. + + + + + hejq@chromium.org + + Time between sending an Play Store app discovery request and the storing + returned results. + + + + + jennyz@chromium.org + newcomer@chromium.org + + Time between a play store result being clicked and being displayed. + + + + + hejq@chromium.org + + The total number of returned apps of a Play Store app discovery query. + + + + + hejq@chromium.org + + The number of returned instant apps of a Play Store app discovery query. + + + + + hejq@chromium.org + + The number of returned uninstalled apps of a Play Store app discovery query. + + + + + + + yusukes@google.com + khmel@google.com + + Elapsed time from the when the user agrees ToS to when the Play Store window + is shown to the user. + + + + + bmgordon@chromium.org + jschettler@chromium.org + + Print preview events for ARC. Recorded when specific print preview events + occur (print preview requested, preview document created, etc.). + + + + + bmgordon@chromium.org + jschettler@chromium.org + + Time taken for ARC to render and generate a PDF for print preview. Includes + time to reflow the page back to normal, but not the time to reflow the page + to prepare for printing. + + + + + bmgordon@chromium.org + jschettler@chromium.org + + Time taken for ARC to render and generate a PDF for print preview divided by + the number of pages. Includes time to reflow the page back to normal, but + not the time to reflow the page to prepare for printing. + + + + + bmgordon@chromium.org + jschettler@chromium.org + + Count how frequently a set of pre-defined print preview errors occur for + ARC. + + + + + bmgordon@chromium.org + jschettler@chromium.org + Time taken for ARC to render a PDF for print preview. + + + + + + mhasank@google.com + arc-core@google.com + + The result (success or the reason of failure) of Cloud DPC provisioning. + Recorded when ARC++ provisioning flow completes. + + + + + + + alexchau@google.com + phweiss@google.com + + The result (success or the type of failure) of ARC provisioning. The base + value has been deprecated on 2016-09-15 in favour of per user type values. + + + + + + + alexchau@google.com + phweiss@google.com + + Elapsed time from the signing in process start to call to onSignInFailed. + + + + + + + alexchau@google.com + phweiss@google.com + + Elapsed time from the signing in process start to successful call to + onSignInComplete. + + + + + + + khmel@google.com + + The result (success or the type of failure) of ARC reauthorization. + + + + + + + khmel@google.com + skuhne@google.com + Standard deviation for commit time delta from ideal time. + + + + + + khmel@google.com + skuhne@google.com + Render frames per second. + + + + + + khmel@google.com + skuhne@google.com + Render quality with maximum 100%. + + + + niwa@google.com + yusukes@google.com + + The types of ARC SDK version upgrade. (e.g. Upgrade from N to P) Reported + when SDK version upgrade is detected during ARC boot. + + + + + sinhak@google.com + jhorwich@google.com + khmel@google.com + + The result (success or the type of failure) of ARC Secondary Account signin/ + reauthorization. + + + + + + + shaochuan@google.com + khmel@google.com + mmatena@google.com + + This is updated when the mojo connections to processes in detailing in + ArcMojoConnectionType are closed for reasons other than the ARC container + shutting down or crashing. + + + + + + + shaochuan@google.com + khmel@google.com + mmatena@google.com + + This is updated in case ARC++ stops for the reasons detailed in + ArcStopReason. For example, this is recorded in case of a graceful ARC++ + shutdown or if ARC++ crashes. + + + + + weifangsun@google.com + djacobo@google.com + + Exit code coming from ARC's share files feature. Used to observe stability + for the feature. + + + + + elijahtaylor@google.com + + The time it takes for ARC to shut down. This value is recorded on ARC + shutdown as the time is takes for the init process to exit after setting + 'sys.powerctl shutdown'. It is reported on the next ARC startup to avoid + sending data during shutdown. + + + + + elijahtaylor@google.com + ttylenda@google.com + + Whether ARC is enabled or not. Before M56 this was collected only on login + and when ARC was enabled or disabled. From M56 forward this is collected + during every metrics recording interval, so it is in every record uploaded + to the server (despite crbug.com/929583 which was fixed in M73). This is + required because this value is used to categorize all other data in the + dashboard as collected with ARC enabled or not. This is true even for users + who are running on ecryptfs and skipped Ext4 migration; even though ARC Apps + do not run until migration is complete on N or later systems. Since M74 this + is also included in initial stability logs. + + + + + + + elijahtaylor@google.com + shihuis@google.com + khmel@google.com + + Similar to "Arc.State" metric but has separation by user type. + + + + + giovax@chromium.org + arc-commercial@google.com + + The result (success or the type of failure) of ARC supervision transition + events. + + + + + giovax@chromium.org + arc-commercial@google.com + + Elapsed time for a successful supervision transition, during which the + supervision transition screen was displayed. + + + + + giovax@chromium.org + arc-commercial@google.com + + Whether supervision transition screen exited due to a successful transition. + + + + + elijahtaylor@google.com + khmel@google.com + Action of ARC++ Graphics Tracing tool. + + + + + + khmel@google.com + yusukes@google.com + + Elapsed time from the when ARC++ is started in already provisioned state to + when the ARC is available for the user. + + + + + + + khmel@google.com + yusukes@google.com + + Elapsed time from the when ARC++ is opted in from the user's session to when + the ARC is available for the user. + + + + + + + khmel@google.com + yusukes@google.com + + Elapsed time from the when ARC++ is opted in from OOBE to when the ARC is + available for the user. + + + + + jhorwich@chromium.org + elijahtaylor@chromium.org + shihuis@google.com + maajid@chromium.org + + Counts user interactions with ARC by type, such as ARC app launches via the + shelf or launcher. + + + + + + + mhasank@google.com + arc-core@google.com + + Elapsed time waiting for the check-in task to be completed. This is recorded + in case check-in task is completed successfully. + + + + + + + mhasank@google.com + arc-core@google.com + Elapsed time waiting for GMS sign-in to complete. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/ash/histograms.xml b/tools/metrics/histograms/histograms_xml/ash/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0ce87ee6113ffec6462a0ae7b2a50c8a9942a78a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/ash/histograms.xml @@ -0,0 +1,1843 @@ + + + + + + + + + + afakhry@chromium.org + + Showing the IME menu bubble has two accelerators: - Alt+Shift+K which is + deprecated. - Search+Shift+K which is new. This histogram shows the number + of times each accelerator (deprecated and new) is used. + + + + + zentaro@chromium.org + cros-peripherals@chromium.org + + Opening the task manager has two accelerators: - Shift+Esc which is + deprecated. - Search+Esc which is new. This histogram shows the number of + times each accelerator (deprecated and new) is used. + + + + + afakhry@chromium.org + + Toggling the high contrast display mode has two accelerators: - + Search+Shift+H which is deprecated. - Ctrl+Search+H which is new. This + histogram shows the number of times each accelerator (deprecated and new) is + used. + + + + + baileyberro@chromium.org + + Captures the result of a user using the rotation accelerator - + Ctrl+Shift+Refresh. This histogram shows how frequently users accidentally + hit the key combination. + + + + + amusbach@chromium.org + xdai@chromium.org + Captures usage of Alt+[ and Alt+]. + + + + kuscher@google.com + + The show type of the active window tracked over time by logging on a regular + basis (30 minutes). + + + + + cowmoo@google.com + xiaohuic@chromium.org + + Recorded whenever Ambient mode is entered from {TabletOrClamshell}. + AmbientUiMode indicates whether the user entered Ambient mode from the lock + screen or from screen idle. + + + + + + + + + wutao@chromium.org + xiaohuic@chromium.org + + Emitted when the ambient mode photo transition animation completes to report + the smoothness of this animation. 100% represents ideally smooth 60 frames + per second. + + + + + cowmoo@google.com + xiaohuic@chromium.org + + Among eligible users, whether the user has Ambient mode enabled. Recorded + once for every UMA upload. The set of eligible users includes all users with + profiles that can allow Ambient mode to be enabled. This is limited by + profile type, whether the user is primary, if the user has a supported + email, etc. + + + + + cowmoo@google.com + xiaohuic@chromium.org + + Among eligible users with ambient mode enabled, records the length of each + session. The metric is uploaded when ambient mode is ended. + + + + + + + + + cowmoo@google.com + xiaohuic@chromium.org + + Among eligible users with ambient mode enabled, records the source of + ambient mode photos. Recorded once for every UMA upload. + + + + + + + cowmoo@chromium.org + xiaohuic@chromium.org + + Relative smoothness of assistant related animations. 100% represents ideally + smooth 60 frames per second. + + + + + minch@chromium.org + tclaiborne@chromium.org + + End scenario type while swiping back from the left side of the window in + tablet mode. + + + + + minch@chromium.org + tclaiborne@chromium.org + + Start scenario type while swiping back from the left side of the window in + tablet mode. + + + + + minch@chromium.org + tclaiborne@chromium.org + + Underneath window type while swiping back from the left side of the window + in tablet mode. + + + + + + + yulunwu@chromium.org + tbarzic@chromium.org + + Tracks the reason contextual nudges for user gesture education are + dismissed. + + + + + + + yulunwu@chromium.org + tbarzic@chromium.org + + Tracks time between showing contextual nudge and gesture being performed. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + mukai@chromium.org + + Emitted when the virtual desks activation animation completes to report the + smoothness of this animation when running on the display on which the active + window resides (if any) or the display of the primary root window. 100% + represents ideally smooth 60 frames per second. + + + + + afakhry@chromium.org + sammiequon@chromium.org + tclaiborne@chromium.org + + When a four finger touchpad swipe has ended, an animation to the nearest + desk will occur. This histogram is emitted when that animation finishes. + 100% represents ideally smooth 60 frames per second. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + mukai@chromium.org + + Emitted when the virtual desks removal animation completes to report the + smoothness of this animation when running on the display on which the active + window resides (if any) or the display of the primary root window. 100% + represents ideally smooth 60 frames per second. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when there's a change in the virtual desks count whether due to desk + creation or removal. Specifies the number of available desks. It is not + emitted for the first-ever created default desk. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when the active desk is changed to specify the source of this + action, i.e. whether due to new-desk shortcut, desk removed, window + activated, switch-desk shortcut, or a press on the desk mini_view. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when a window is moved from the current active desk to another desk. + Specifies the source of this action, i.e. whether to window drag-and-drop, + or keyboard shortcut. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when a virtual desk is created to specify the source of this action, + i.e. whether from the new-desk button, keyboard shortcut, or due to desks + restore. It is not emitted for the first-ever created default desk. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The number of windows on the first desk. Emitted when a desk is removed, or + a window is moved to another desk. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The number of windows on the second desk. Emitted when a desk is removed, or + a window is moved to another desk. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The number of windows on the third desk. Emitted when a desk is removed, or + a window is moved to another desk. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The number of windows on the fourth desk. Emitted when a desk is removed, or + a window is moved to another desk. + + + + + afakhry@chromium.org + sammiequon@chromium.org + tclaiborne@chromium.org + + Presentation time in ms when a four finger swipe is being used to change + desks. One full swipe results in multiple emissions of this metric; once + everytime the fingers change location on the trackpad. Presentation time is + the time it takes from when the software recognizes the touchpad swipe to + when the next frame is displayed on the screen. + + + + + afakhry@chromium.org + sammiequon@chromium.org + tclaiborne@chromium.org + + The largest presentation time value in ms for a single four finger swipe to + change desks. One full swipe results in one emission of this metric; its the + largest value of Ash.Desks.PresentationTime.UpdateGesture which is emitted + multiple times during a single full swipe. Presentation time is the time it + takes from when the software recognizes the touchpad swipe to when the next + frame is displayed on the frame. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when a virtual desk is removed to specify the source of this remove + operation, i.e. whether from the close-desk button, or keyboard shortcut. + + + + + tbuckley@chromium.org + tclaiborne@chromium.org + + The number of seconds between task window activations triggered by users + clicking or tapping on a window, as recorded by the Desktop_SwitchTask user + action. Recorded on Chrome OS only. Task switches from other sources are + ignored and do not affect this metric. In other words, if a user performs + the following steps (1) click on task window 'A' (2) Alt+Tab to task 'Z'(3) + click on task window 'B', then this will result in a sample recorded for the + time delta between activating task window 'A'and 'B'. + + + + + jamescook@chromium.org + jessejames@chromium.org + cros-system-services@google.com + + The display zoom setting for the primary display, recorded on startup. + + + + + zentaro@chromium.org + cros-peripherals@google.com + + Emitted when the user chooses an option on the Display Change Dialog that is + shown when a user changes the resolution of an external display. + + + + + mcasas@chromium.org + dcastagna@chromium.org + + Whether a display has a "CTM" matrix properties that can be used + to set a color transform matrix. Recorded every time there is a display + configuration update. + + + + + mcasas@chromium.org + dcastagna@chromium.org + + This boolean keeps track if an ICC file was downloaded correctly (if true) + or a local file was reused instead. + + + + + mcasas@chromium.org + dcastagna@chromium.org + + This boolean keeps track if a Display update (i.e. when connecting a new + one) carried valid ColorSpace information. + + + + + mcasas@chromium.org + dcastagna@chromium.org + + Whether we could parse a valid product id from a display EDID. Recorded + every time there is a display configuration update. + + + + + kuscher@google.com + wutao@chromium.org + + User-initiated action taken that affects docked windows such as docking, + undocking, minimizing, restoring, closing or just dragging a docked window. + + + + + kuscher@google.com + wutao@chromium.org + + Source (mouse, touch, keyboard or unknown) of the user-initiated action for + docked windows. + + + + + kuscher@google.com + wutao@chromium.org + + Number of all docked windows or panels including hidden or minimized. + Recorded on every user action that interacts with docked windows. + + + + + kuscher@google.com + wutao@chromium.org + + Number of large (wider than dock maximum width) windows that had to be + shrunk to get docked among the visible docked windows. Recorded on every + user action that interacts with docked windows. + + + + + kuscher@google.com + wutao@chromium.org + + Number of docked visible panels. Recorded on every user action that + interacts with docked windows. + + + + + kuscher@google.com + wutao@chromium.org + + Number of visible docked windows or panels. Recorded on every user action + that interacts with docked windows. + + + + + kuscher@google.com + wutao@chromium.org + + Time elapsed between instances of docking, undocking or any other action + affecting docked state of a window. + + + + + kuscher@google.com + wutao@chromium.org + + Width of the docked area in pixels. Recorded every time it changes after a + user window resize operation is completed. + + + + + tbarzic@chromium.org + xdai@chromium.org + + Presentation time in ms when a window is dragged from the bottom of the + shelf. Recorded when the drag action is in progress. + + + + + tbarzic@chromium.org + xdai@chromium.org + + Maximum latency of the presentation time in ms when a window is dragged from + the bottom of the shelf. Recorded when the drag action is finished. + + + + + sammiequon@chromium.org + tbarzic@chromium.org + + Relative smoothness of animations when performing tablet mode homescreen + animations, recorded when the animation completes. 100% represents ideally + smooth 60 frames per second. + + + + + andrewxu@chromium.org + tbarzic@chromium.org + Gestures supported by the in-app hotseat. + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Tracks the animation smoothness for the ShelfWidget's animating background + during transitions of the hotseat to shown, extended, and hidden hotseat + states. Check Ash.HotseatWidgetAnimation.AnimationSmoothness for smoothness + of the HotseatWidget. + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Presentation time in ms of the hotseat when it changes between the hidden + and the extended state as a result of a drag action. Recorded when the drag + action is in progress. + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Maximum latency of the presentation time in ms of the hotseat when it + changes between the hidden and the extended state as a result of a drag + action. Recorded when the drag action is finished. + + + + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Tracks the animation smoothness for the bounds animation of the hotseat + widget's elements during transitions of the hotseat to shown, extended, and + hidden hotseat states. Check Ash.HotseatTransition.AnimationSmoothness for + smoothness of the shelf's animating background. + + + + + kuscher@google.com + + The type of the window which is put into immersive fullscreen. Immersive + fullscreen is entered via the F4 key. + + + + + oshima@chromium.org + mukai@chromium.org + + Time between when the size of a window changes during an interactive window + resize and the results are drawn (presented) on screen. This is recorded for + each movement of the mouse/pointer that results in a resize. + + + + + oshima@chromium.org + mukai@chromium.org + + Maximum time between when the size of a window changes during an interactive + window resize and the results are drawn (presented) on screen. This is + recorded for each movement of the mouse/pointer that results in a resize. + + + + + rsorokin@chromium.org + cros-oac@google.com + + The count of auth method switching actions in ChromeOS lock screen. + + + + + rsorokin@chromium.org + cros-oac@google.com + + The usage of different auth methods (PIN / Password / Smartlock / + Fingerprint) in ChromeOS lock screen clamshell mode. + + + + + rsorokin@chromium.org + cros-oac@google.com + + The usage of different auth methods (PIN / Password / Smartlock / + Fingerprint) in ChromeOS lock screen tablet mode. + + + + + tellier@google.com + cros-oac@google.com + + The number of incorrect passwords entered in Chrome OS login/lock screen + until the user gives up (user signs out the current session or shuts down + the device). + + + + + tellier@google.com + cros-oac@google.com + + The number of incorrect passwords entered in Chrome OS login/lock screen + until a successful attempt. + + + + + rsorokin@chromium.org + cros-oac@google.com + + The numbers of times that users click on the shelf buttons, trays and lock + screen note on the ChromeOS lock screen. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Whether the cryptohome migration banner was shown on the Chrome OS login + screen. + + + + + rsorokin@chromium.org + cros-oac@google.com + + The numbers of times that users click on the shelf buttons and trays on the + ChromeOS login screen. + + + + + raleksandrov@google.com + cros-oac@google.com + What shelf buttons or trays are clicked in the OOBE. + + + + rrsilva@google.com + cros-oac@google.com + + The result of the PIN auto submit 'Backfill' operation. Users updating to + M86 with an existing PIN will have their preference regarding auto submit + 'backfilled' to either enabled or disabled. + + + + + + + + + anasalazar@chromium.org + newcomer@chromium.org + + Relative smoothness of animations of the navigation widget's elements, which + are the widget itself and its child views. 100% represents ideally smooth 60 + frames per second. 50% represents only 30 frames per second is achieved + during the animations. Recorded every time an animation is triggered in the + Navigation Widget. We record this metric for each element separately. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + Emitted when the Auto Night Light notification is shown. + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when the user interacts with the Auto Night Light notification to + report the state of the notification as a result of this interaction. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The type of CRTC color transorm matrix support for the currently connected + displays. Emitted when cursor compositing status is refreshed, but only when + Night Light is on. The cursor compositing status is refreshed whenever there + is a change in Night Light status or color temperature. + + + + + afakhry@chromium.org + + The selected Night Light schedule type. Emitted when the user changes the + Night Light schedule type from the Display System Settings. + + + + + afakhry@chromium.org + + The ranges in which the selected values of the Night Light color temperature + reside. Emitted when the user drags the Night Light color temperature slider + to change its value from the Display System Settings. + + + + + jamescook@chromium.org + + An upper bound on the number of windows visible to the user on the primary + display. Determined by processing the windows in increasing z-order and + counting all non-minimized windows until a maximized or fullscreen window is + processed. This metric is logged periodically every 30 minutes. + + + + + + + omrilio@chromium.org + oshima@chromium.org + + Relative smoothness of animations when closing a window, recorded when the + animation completes. 100% represents ideally smooth 60 frames per second. + + + + + + + omrilio@chromium.org + oshima@chromium.org + + Relative smoothness of animations when entering overview mode, recorded when + the animation completes. 100% represents ideally smooth 60 frames per + second. + + + + + + + omrilio@chromium.org + oshima@chromium.org + + Relative smoothness of animations when exiting overview mode, recorded when + the animation completes. 100% represents ideally smooth 60 frames per + second. + + + + + sammiequon@chromium.org + tclaiborne@chromium.org + + Maximum latency of the presentation time for scrolling the overview grid in + overview mode for a scrolling session. + + + + + sammiequon@chromium.org + tclaiborne@chromium.org + + Presentation time for scrolling the overview grid in overview mode. Each + time the grid is updated by a scroll, the time it takes to update the new + visuals onto the screen is updated. + + + + + + + omrilio@chromium.org + oshima@chromium.org + Presentation time for dragging a window in overview mode. + + + + + + omrilio@chromium.org + oshima@chromium.org + + Maximum latency of the presentation time for dragging a window in overview + mode. + + + + + amusbach@chromium.org + xdai@chromium.org + + Recorded when a drag from overview (not from the top or shelf) is completed, + and when an overview item is closed by vertically swiping or flinging (even + if you fling without dragging). + + + + + zentaro@chromium.org + baileyberro@chromium.org + + The number of windows restored in multi-display scenario, such as due to + disconnecting and reconnecting display, enabling and disabling mirror mode, + entering and leaving dock mode. Zero is not recorded. + + + + + takise@chromium.org + linben@chromium.org + How long Android PIP was used for, upon ending the session. + + + + takise@chromium.org + linben@chromium.org + + Various individiual Picture-in-picture related events. See AshPipEvents. + + + + + takise@chromium.org + linben@chromium.org + + Area of a Picture-in-picture window when ending a free-resize, as a + percentage of the area it takes up on the display it is on. + + + + + takise@chromium.org + linben@chromium.org + + Initial area of a Picture-in-picture window when beginning a free-resize, as + a percentage of the area it takes up on the display it is on. + + + + + takise@chromium.org + linben@chromium.org + + The position that a Picture-in-picture window was moved to by a user drag. + + + + + zentaro@chromium.org + baileyberro@chromium.org + + Record the delay when power button and volume down key are both pressed, + which indicates user might want to use accelerator to take screenshot. This + will help us determine the best chord delay among metrics. + + + + + oshima@chromium.org + wutao@chromium.org + + Relative smoothness of animations when rotating screen. 100% represents + ideally smooth 60 frames per second. 50% represents only 30 frames per + second is achieved during the animations. 0% should not happen. This metric + is recorded exactly once when the user rotates the screen. + + + + + anasalazar@google.com + mmourgos@google.com + + Tracks the number of menu items that are enabled in a shelf item's secondary + menu. This metric is only recorded when a menu item is selected. + + + + + anasalazar@google.com + mmourgos@google.com + + Tracks the index of the selected menu item in a shelf item's secondary menu. + This metric is only recorded when a menu item is selected. + + + + + tbarzic@chromium.org + gzadina@google.com + + The reason shelf navigation buttons are shown in tablet mode. The buttons + are shown when the device is in tablet mode only if certain accessibility + settings are enabled. This histogram records which accessibility setting + caused the buttons to be shown. Shown when navigation buttons visibility + changes in tablet mode, and only if HideShelfControlsInTabletMode feature is + enabled. + + + + + anasalazar@google.com + mmourgos@google.com + + The number of icons in the shelf, not including the App Launcher icon. This + metric is recorded every 30 minutes. + + + + + anasalazar@google.com + mmourgos@google.com + + The number of pinned icons in the shelf, not including the App Launcher + icon. This metric is recorded every 30 minutes. + + + + + anasalazar@google.com + mmourgos@google.com + + The number of unpinned icons in the shelf. This metric is recorded every 30 + minutes. + + + + + tengs@chromium.org + gzadina@chromium.org + + The percentage of the screen area circled by the Assistant pen. Recorded + when the "closed shape" gesture is recognized. + + + + + tengs@chromium.org + gzadina@chromium.org + + The duration of an Assistant pen gesture. Recorded at the end of every + gesture. + + + + + tengs@chromium.org + gzadina@chromium.org + + The interval between subsequent Assistant pen gestures within a session. + Session is defined as the period while the Assistant tool is enabled. + Recorded at the end of each gesture except for the first one in the session. + The interval is computed excluding the gesture duration. + + + + + tengs@chromium.org + gzadina@chromium.org + + The number of Assistant pen gestures per session. Session is defined as the + period while the Assistant tool is enabled. Recorded at the end of the + session. + + + + + tengs@chromium.org + gzadina@chromium.org + + The number of recognized Assistant pen gestures per session. Session is + defined as the period while the Assistant tool is enabled. Recorded at the + end of the session. + + + + + tengs@chromium.org + gzadina@chromium.org + + The type of the Assistant pen gesture. Recorded at the end of each gesture. + + + + + tengs@chromium.org + gzadina@chromium.org + + The length of a recognized "horizontal stroke" Assistant pen + gesture. Recorded at the and of the gesture. + + + + + tengs@chromium.org + gzadina@chromium.org + + The amount of time spent in Palette Assistant mode. Recorded when the + Assistant mode is exited. + + + + + tengs@chromium.org + gzadina@chromium.org + + The amount of time spend in Palette Laser pointer mode. Recorded when the + Laser pointer mode is exited. + + + + + tengs@chromium.org + gzadina@chromium.org + + The amount of time spend in Palette Magnify mode. Recorded when the Magnify + mode is exited. + + + + + tengs@chromium.org + gzadina@chromium.org + + Tracks the number of times a palette mode is explicitly cancelled or + switched out of. + + + + + tengs@chromium.org + gzadina@chromium.org + + Recorded every time that the palette option has been selected from the + palette that has been opened manually (not via a stylus eject event). + + + + + tengs@chromium.org + gzadina@chromium.org + + Recorded every time that the palette option has been selected from the + palette that has been opened automatically (by a stylus eject event). + + + + + tengs@chromium.org + gzadina@chromium.org + + Recorded every time that the palette option has been selected by means other + that the palette menu (e.g. stylus barrel button or a keyboard accelerator). + + + + + tbuckley@chromium.org + + The number of seconds between contiguous task switch user actions triggered + by the Shelf buttons where the user activates a different user-predictable + task. Task switches from other sources are ignored and do not affect this + metric. In other words, if a user performs the following steps (1) launch + task 'A' from the Shelf (2) Alt+Tab to task 'Z' (3) launch task 'B' from the + Shelf, then this will result in a sample recorded for the time delta between + launching tasks 'A' and 'B'. + + + + + tbuckley@chromium.org + + Tracks the amount of time between a window being minimized by the shelf and + subsequently activated. In other words this metric is only recorded if a + shelf button pressed action causes a window to be minimized and the very + next shelf button pressed action causes the same window to be activated. + + + + + wrong@chromium.org + jiameng@chromium.org + + Whether or not the user had set up a night light schedule at the time of + night light event logging. + + + + + wrong@chromium.org + jiameng@chromium.org + + The number of Bluetooth devices available at the time of Bluetooth event + logging. + + + + + kuscher@google.com + + The current state of the shelf (alignment) tracked over time by logging on a + regular basis (30 minutes), this is used instead of log in or shelf usage to + track users that do not lock/unlock or log in frequently and use a small + number of browser instances or otherwise infrequently interact with the + shelf launcher. + + + + + + + kuscher@google.com + tbarzic@chromium.org + + The current state of the shelf (alignment) when the shelf launcher is used + to launch an app/window/etc, this is used instead of log in to give data on + users that do not lock/unlock or log in frequently. + + + + + andrewxu@chromium.org + newcomer@chromium.org + + Relative smoothness of animations of the shelf icons. 100% represents + ideally smooth 60 frames per second. Recorded when shelf icon animations are + completed, including icon move, icon fade-in and icon fade-out. + + + + + amusbach@chromium.org + xdai@chromium.org + + The amount of time that the user spent in multi-display split view mode, + meaning that split view is active on more than one display. The time is + measured from when the number of displays in split view becomes more than + one to when it drops back down to one. + + + + + xdai@chromium.org + + The amount of time that the user spent in split view mode. The time is + measured from the moment a window is snapped to one side of the screen to + when split view mode is ended. + + + + + sammiequon@chromium.org + xdai@chromium.org + + Relative smoothness of animation when releasing the split view divider, + recorded when the animation completes. 100% represents ideally smooth 60 + frames per second. + + + + + + + amusbach@chromium.org + xdai@chromium.org + omrilio@chromium.org + oshima@chromium.org + + Presentation time while resizing one or two split view windows. + + + + + + + amusbach@chromium.org + xdai@chromium.org + omrilio@chromium.org + oshima@chromium.org + + Maximum latency of the presentation time while resizing one or two split + view windows. + + + + + omrilio@chromium.org + + Maximum latency of the presentation timestamp while dragging a tab in tablet + mode. + + + + + omrilio@chromium.org + Presentation time while dragging a tab in tablet mode. + + + + omrilio@chromium.org + + Maximum latency of the presentation timestamp while dragging maximized + window in tablet mode. + + + + + omrilio@chromium.org + + Presentation time while dragging maximized window in tablet mode. + + + + + andrewxu@chromium.org + tbarzic@chromium.org + + Boolean indicating whether a swipe from hotseat on home screen resulted in a + transition to overview. + + + + + tengs@chromium.org + gzadina@chromium.org + + The visible rows displayed in the system menu's default view. Recorded each + time the menu is opened. + + + + + tengs@chromium.org + gzadina@chromium.org + + The height of the system menu divided by the height of the Ash desktop work + area; a value over 100% indicates that a portion of the system menu is not + visible to the user. Recorded each time the menu is opened. + + + + + tengs@chromium.org + gzadina@chromium.org + + The number of user-visible rows in the system menu's default view. Recorded + each time the menu is opened. + + + + + oshima@chromium.org + sammiequon@chromium.org + + Relative smoothness of animations when entering tablet mode, recorded when + the animation completes. 100% represents ideally smooth 60 frames per + second. + + + + + oshima@chromium.org + sammiequon@chromium.org + + Relative smoothness of animations when exiting tablet mode, recorded when + the animation completes. 100% represents ideally smooth 60 frames per + second. + + + + + tbuckley@google.com + + The number of seconds between contiguous task switch user actions triggered + by any of the other task switch actions that are tracked. (e.g., + Ash.Shelf.TimeBetweenNavigateToTaskSwitches, + Ash.Tab.TimeBetweenSwitchToExistingTabUserActions, + Ash.WindowCycleController.TimeBetweenTaskSwitches, + Ash.AppList.TimeBetweenTaskSwitches, + Ash.WindowSelector.TimeBetweenActiveWindowChanges, etc). Note the + Ash.AppList.TimeBetweenTaskSwitches and + Ash.Tab.TimeBetweenSwitchToExistingTabUserActions histograms were deprecated + and removed in 10/2016. + + + + + kuscher@google.com + rbyers@chromium.org + The distance between touch-move events. + + + + kuscher@google.com + + The interval between the end of a touch-sequence and the start of the next + touch-sequence. + + + + + oshima@chromium.org + + Chrome OS only. The computed angle between the lid and the keyboard panel. + These values are imprecise and may be tens of degrees off from reality. + Reported once per hour that the system is awake, and not reported if the + system doesn't have two accelerometers. + + + + + girard@chromium.org + + The length of time that TouchView is active, for each activation. + + + + + girard@chromium.org + The proportion of time spent in TouchView during a session. + + + + girard@chromium.org + The total time that TouchView is active during a session. + + + + girard@chromium.org + The length of time between TouchView activations. + + + + girard@chromium.org + + The total time that TouchView is not active during a session. + + + + + newcomer@chromium.org + tbuckley@chromium.org + + Tracks the success rate for wallpaper color extraction. Recorded each time + the wallpaper image changes for each extracted wallpaper prominent color. + + + + + xdai@chromium.org + + The custom wallpaper layout type. Recorded when the user sets a new custom + wallpaper or changes the existing custom wallpaper's layout. + + + + + xdai@chromium.org + + Recorded when a new wallpaper is set, either by the built-in Wallpaper + Picker App, or by a third party App. Note the wallpaper change triggered by + Sync file system event doesn't count. + + + + + kuscher@google.com + The wallpaper type. Recorded at user login. + + + + wutao@chromium.org + + Relative smoothness of cross fade animation when setting window bounds. 100% + represents ideally smooth 60 frames per second. 50% represents when only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when SetBoundsDirectCrossFade is + called, such as when window is maximized. + + + + + sammiequon@chromium.org + xdai@chromium.org + + When dragging a maximized window, the window will shrink to restore bounds. + Dragging the window back to the top of the screen will expand the window. + This histogram will be recorded to measure the smoothenss of the expand + animation. 100% represents ideally smooth 60 frames per second. 50% + represents when only 30 frames per second is achieved during the animations. + 0% should not happen. + + + + + sammiequon@chromium.org + xdai@chromium.org + + When dragging a maximized window, the window will shrink to restore bounds. + This histogram will be recorded to measure the smoothness of the shrink + animation. 100% represents ideally smooth 60 frames per second. 50% + represents when only 30 frames per second is achieved during the animations. + 0% should not happen. + + + + + sammiequon@chromium.org + tclaiborne@chromium.org + + Relative smoothness of hiding window animation. 100% represents ideally + smooth 60 frames per second. 50% represents when only 30 frames per second + is achieved during the animations. 0% should not happen. This metric is + recorded exactly once when AnimateHideWindowCommon is called, such as when + window is closed. + + + + + oshima@chromium.org + sammiequon@chromium.org + + Relative smoothness of snapping window animation. 100% represents ideally + smooth 60 frames per second. 50% represents when only 30 frames per second + is achieved during the animations. 0% should not happen. This metric is + recorded exactly once when a window is snapped to the left or right in + clamshell mode using the alt + [ or ] accelerator, but only if the size of + the window's bounds change. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + Emitted when the user ends window cycling via Alt-Tab, if and only if user + had 2 or more desks and a new window was activated, to report the distance + between the active desks before and after window cycling. A distance of 0 + means no desks switch occurred. + + + + + sammiequon@chromium.org + tclaiborne@chromium.org + xdai@chromium.org + + The number of windows in the Alt+Tab selector. Only recorded once when + cycling starts, not every time when Tab is pressed without releasing Alt. + + + + + sammiequon@chromium.org + tclaiborne@chromium.org + xdai@chromium.org + + The number of seconds between task switches triggered by the next window and + previous window accelerator keys (ie Alt+Tab, Alt+Shift+Tab). + + + + + yjliu@chromium.org + chromeos-wmp@google.com + + Relative smoothness of showing window animation when the window cycle view + moves the next window into position when alt + tab is pressed. 100% + represents ideally smooth 60 frames per second. 50% represents when only 30 + frames per second is achieved during the animations. 0% should not happen. + + + + + yjliu@chromium.org + chromeos-wmp@google.com + + Relative smoothness of showing window animation when the window cycle view + starts. 100% represents ideally smooth 60 frames per second. 50% represents + when only 30 frames per second is achieved during the animations. 0% should + not happen. + + + + + andrewxu@chromium.org + tbarzic@chromium.org + + The final state after window drag gesture that started from the system shelf + in tablet mode. + + + + + jdufault@chromium.org + + How long it took for the screen lock process to complete. This does not + include timeouts. + + + + + jdufault@chromium.org + + How long it took for the screen lock process to complete, for timeouts only. + + + + + flackr@chromium.org + + The number of times the arrow keys are pressed in overview mode per session, + i.e. between bringing up overview mode and ending it. This is only measured + for the sessions that end by selecting a window with the enter key. + + + + + flackr@chromium.org + kuscher@google.com + + The number of items (single windows or groups of windows such as panels) in + the overview mode, present at the start of each session. + + + + + flackr@chromium.org + + The number of items showing in overview mode at the moment when an item is + selected or when selection is canceled. Only recorded if the text filtering + textfield contains a non-empty string. + + + + + flackr@chromium.org + + The ratio between the arrow key presses and the number of overview items, + expressed as a percentage for a single session. + + + + + flackr@chromium.org + + The number of items closed from the window overview for a single session. + + + + + estade@chromium.org + tbuckley@chromium.org + + When a window is selected in overview mode, records that window's position + in the global MRU ordering. 1 represents the most-recently used window, 2 + represents the next most-recently used window, and so on. + + + + + flackr@chromium.org + + The length of the string entered into the text filtering textfield at the + moment when an item is selected or when selection is canceled. + + + + + flackr@chromium.org + + The number of times the text filtering textfield has had all of its text + removed within a single overview mode session. Measured from the time + overview mode is invoked to when an item is selected or when selection is + canceled. + + + + + tbuckley@chromium.org + + The amount of time between endings of overview mode sessions which were + caused by the user selecting a window which was not previously active. Only + recorded on the second and later times after startup that the user selected + a window which was not previously active. + + + + + flackr@chromium.org + kuscher@google.com + + The amount of time between uses of overview mode, recorded when overview + mode is entered. Only recorded on the second and later times after startup + that the user entered overview mode. + + + + + flackr@chromium.org + kuscher@google.com + + The amount of time spent in overview mode. Overview mode is engaged by + pressing the overview button. The time is measured from the moment the + windows begin animating to a thumbnail size preview to when a window is + selected or selection is canceled. + + + + + flackr@chromium.org + + The amount of time spent in overview mode when text filtering is used. The + time is measured from the moment the windows begin animating to a thumbnail + size preview to when a window is selected or selection is canceled. Only + recorded if the text filtering textfield contains a non-empty string. + + + + + yichenz@chromium.org + chromeos-wmp@google.com + + Presentation time in ms when a tab is dragged in clamshell mode. Each time + the tab is dragged within a display, the time it takes to present the new + frame on screen is recorded. + + + + + yichenz@chromium.org + chromeos-wmp@google.com + + Maximum presentation time recorded during the tab dragging session. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/assistant/histograms.xml b/tools/metrics/histograms/histograms_xml/assistant/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..ae35ce257f44da733868321e4e3d2a22af9ead08 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/assistant/histograms.xml @@ -0,0 +1,217 @@ + + + + + + + + + + xiaohuic@chromium.org + croissant-eng@chromium.org + + The number of times Assistant better onboarding buttons are clicked. + + + + + xiaohuic@chromium.org + croissant-eng@chromium.org + + The number of times Assistant better onboarding UI is shown. The UI has a + few different modes recorded in the enum. + + + + + xiaohuic@chromium.org + meilinw@chromium.org + + The number of times buttons on Assistant UI (e.g., minimize) are clicked. + + + + + updowndota@chromium.org + xiaohuic@chromium.org + + Among eligible users, whether the user has the Assistant context (related + info) enabled. Recorded once for every UMA upload. The set of eligible users + includes all users with profiles that can allow Assistant service to be + enabled (AssistantAllowedState is limited by locale, policy, etc). + + + + + meilinw@chromium.org + xiaohuic@chromium.org + + Counts the number of times Dsp hotword gets detected in each status, to help + capture the hotword false acceptance rate. + + + + + xiaohuic@chromium.org + meilinw@chromium.org + + Record the Assistant entry point where Assistant UI becomes visible. + + + + + xiaohuic@chromium.org + meilinw@chromium.org + + Record the Assistant exit point where Assistant UI becomes invisible. + + + + + updowndota@chromium.org + croissant-eng@chromium.org + + Counts the number of times user click the hotword enable notification to + open Assistant settings. + + + + + xiaohuic@chromium.org + croissant-eng@chromium.org + + Record the Assistant interaction resolution code. It indicates how the + Assistant server interpreted a particular query and decision on the state, + e.g. if the conversation is normal or timed out or ended with other errors. + + + + + updowndota@chromium.org + croissant-eng@chromium.org + + Amount of time between get settings request and response. The request will + be sent for each time the Assistant OptIn Flow is triggered to get string + texts from the server. + + + + + updowndota@chromium.org + croissant-eng@chromium.org + + Number of times that the loading timeout triggers. The loading timeout is + set by the Assistant OptIn Flow loading screen, which shows up during the + server string texts and webviews are pending. + + + + + updowndota@chromium.org + croissant-eng@chromium.org + Record the status of the Assistant opt-in flow. + + + + xiaohuic@chromium.org + meilinw@chromium.org + Number of queries fired for each entry point. + + + + xiaohuic@chromium.org + meilinw@chromium.org + The Assistant query response type. + + + + xiaohuic@chromium.org + meilinw@chromium.org + + The source of Assistant query (e.g. dialog plate text field, voice input). + Recorded when the query is committed. + + + + + xiaohuic@chromium.org + meilinw@chromium.org + + Among eligible users, whether the user has the Assistant service enabled. + Recorded once for every UMA upload. The set of eligible users includes all + users with profiles that can allow Assistant service to be enabled + (AssistantAllowedState is limited by locale, policy, etc). + + + + + xiaohuic@chromium.org + jeroendh@google.com + + Amount of time between when the Assistant service is launched, and when the + Assistant back-end signals it is ready to process queries. + + + + + updowndota@chromium.org + Amount of time spent in starting Assistant service. + + + + meilinw@chromium.org + xiaohuic@chromium.org + + For each attempt to set the hotword locale for a DSP device, counts whether + the attempt succeeded. + + + + + wylieb@chromium.org + fgorski@chromium.org + + (Android only) Reports user eligibility for the feature, but ignores if the + feature is enabled. The criteria includes: locale, agsa version and + available memory. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/auth/histograms.xml b/tools/metrics/histograms/histograms_xml/auth/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..e2b5b646f25ff64d0a8178ba8a04210f16c98f74 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/auth/histograms.xml @@ -0,0 +1,320 @@ + + + + + + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to authenticate a user to an Active Directory domain. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + Result from automatic background machine password renewal. + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from automatic background ticket-granting-ticket renewal. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result of an attempt to get an Active Directory user's Kerberos + ticket-granting-ticket and configuration data. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result of an attempt to get the status of an Active Directory user's + Kerberos ticket, password and account. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to join a machine to an Active Directory domain. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to fetch device policy from an Active Directory + domain and store it on disk. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to fetch user policy from an Active Directory domain + and store it on disk. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of times 'kinit' failed until the next try succeeded or the method + gave up because a maximum number of tries was exceeded. 'kinit' is run for + Active Directory enrolled devices during user authentication and device + policy fetch. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of times 'smbclient' failed until it the next try succeeded or the + method gave up because a maximum number of tries was exceeded. 'smbclient' + is run for Active Directory enrolled devices during policy fetch. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + The Kerberos encryption types used while succesfully authenticating an user. + This value comes from the DeviceKerberosEncryptionTypes policy. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + The Kerberos encryption types used while succesfully joining an Active + Directory domain. This value comes from the advanced settings of the + domainjoin screen. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of group policy objects attached to a specific user or machine on an + Active Directory domain. This value is recorded when user or device policy + is fetched from an Active Directory server. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to authenticate a user to an Active Directory domain. + The value is recorded no matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to get the Kerberos ticket-granting-ticket and + configuration data of an Active Directory user. The value is recorded no + matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to get status information of an Active Directory user. + The value is recorded no matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to join a machine to an Active Directory domain. Domain + join is part of the Active Directory enrollment process. The value is + recorded no matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to fetch device policy from an Active Directory domain + and store it on disk. The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to fetch user policy from an Active Directory domain + and store it on disk. The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'kinit' (request Kerberos ticket-granting- + ticket). TGTs are requested regularly for accessing services on Active + Directory domains. The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'klist' (print Kerberos ticket-granting-ticket + information). The command reveals a TGT's lifetime, which is used to + determine TGT status in GetUserStatus() called periodically by Chrome. The + value is recorded no matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'kpasswd' (change Active Directory password). + The command is used to change the machine account password. By default, it + is run every 30 days by the AuthPolicy daemon. The value is recorded no + matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'net ads gpo list' (list Active Directory group + policy objects). The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'net ads info' (query Active Directory + information). The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'net ads join' (join machine to an Active + Directory domain). The value is recorded no matter if the operation was + successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'net ads search' (query information about an + Active Directory account). The value is recorded no matter if the operation + was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'net ads workgroup' (query Active Directory + workgroup). The value is recorded no matter if the operation was successful + or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to call 'smbclient' (download policy from an Active + Directory domain). The value is recorded no matter if the operation was + successful or not. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/auto/histograms.xml b/tools/metrics/histograms/histograms_xml/auto/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..fcc0864a8c5e65f8ac5aa7def3cd7458987bbdd9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/auto/histograms.xml @@ -0,0 +1,570 @@ + + + + + + + + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. We also log the als-delta from the + previous log-lux (when brightness was last changed) to the current log-lux, + which includes both the sign of the als-delta and its absolute value. Chrome + OS only. + + + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. We also log the als-stddev in its + averaging period. We log it separately for the case when the associated + als-delta is positive and negative. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. This enum states the reason why the + model also thinks brightness should be changed. Chrome OS only. + + + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. We also log the number of model + iterations if we've set to use personal curve only. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. This enum states the reason why the + model doesn't think brightness should be changed. Chrome OS only. + + + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, we will ask the model whether it also + thinks brightness should be changed. We also log the als-stddev in its + averaging period. This metric records the als-stddev when the associated + als-delta is unknown. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether the ALS is enabled or the error otherwise. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + Reason for the model to change brightness. Chrome OS only. + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + The time between two consecutive auto brightness changes. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of model iterations when brightness is changed by a personal curve. + Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether the brightness monitor is enabled or the error otherwise. Chrome OS + only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on an Atlas + device with an ambient sensor that is supported by the auto screen + brightness model. Reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on an Eve device + with an ambient sensor that is supported by the auto screen brightness + model. Reported daily. The count is accumulated through the day, spanning + reboots, and sent once the system clock indicates that a full day or more + has passed since the last report. If the system is suspended or off for more + than a day, the current count will be reported immediately the next time the + system boots, but the skipped days will not be reported. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on a Kohaku + device with an ambient sensor that is supported by the auto screen + brightness model. Reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on a device + without an ambient sensor. Reported daily. The count is accumulated through + the day, spanning reboots, and sent once the system clock indicates that a + full day or more has passed since the last report. If the system is + suspended or off for more than a day, the current count will be reported + immediately the next time the system boots, but the skipped days will not be + reported. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on a Nocturne + device with an ambient sensor that is supported by the auto screen + brightness model. Reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on a device with + an ambient sensor that is supported by the auto screen brightness model. + Reported daily. The count is accumulated through the day, spanning reboots, + and sent once the system clock indicates that a full day or more has passed + since the last report. If the system is suspended or off for more than a + day, the current count will be reported immediately the next time the system + boots, but the skipped days will not be reported. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Number of times that a user has made brightness adjustments on a device with + an ambient sensor that is not supported by the auto screen brightness model. + Reported daily. The count is accumulated through the day, spanning reboots, + and sent once the system clock indicates that a full day or more has passed + since the last report. If the system is suspended or off for more than a + day, the current count will be reported immediately the next time the system + boots, but the skipped days will not be reported. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Type of error seen when handling data related to automatic screen brightness + adjustments. Only reported on Chrome OS. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + The elapsed time from a model brightness adjustment to the next user manual + brightness change. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + Whether the global curve is reset at initialization. + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + A monotone cubic spline curve may be invalid from input that used to + generate it. This metric records why it's invalid. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether there was no recorded ALS reading when brightness was changed. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Under the current implementation of brightness monitor, user brightness + request should be received before brightness change signal. Adapter operates + under this assumption. This metric logs an error if a brightness change + signal is received without a prior brightness request signal. Chrome OS + only. + + + + + jiameng@chromium.org + napper@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Personal model iteration count when modeller is initialized. Chrome OS only. + + + + + jiameng@chromium.org + napper@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + Status of the model loading from disk. Chrome OS only. + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether a new brightness exceeds the preset bound that defines reasonble + range of change. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether a training data is an outlier and should be discarded by the model + during training. Chrome OS only. + + + + + jiameng@chromium.org + napper@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When training data comes in, the model may or may not be updated. We measure + the error of the model as compared with the target value from training data. + This metric measures the error when model is not updated. Chrome OS only. + + + + + jiameng@chromium.org + napper@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When training data comes in, the model may or may not be updated. We measure + the error of the model as compared with the target value from training data. + This metric measures the error when model is updated. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether user brightness change is consistent with the model so that model is + not updated. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + The time elapsed between training start and a new curve saved to disk. Only + reported if a new curve was created and saved successfully to disk. Chrome + OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether a new curve was successfully saved to disk. Only reported if a new + curve was created during the training process. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, if the previous change was caused by + the model, then we log bucketized absolute brightness changes of the two + adjustments. This metric records changes if they are in the opposite + directions. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When there is an error in the automatic screen brightness parameters, this + records which kind of parameter is invalid. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + Whether the user's personal brightness curve is valid. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + When user changes brightness manually, if the previous change was caused by + the model, then we log bucketized absolute brightness changes of the two + adjustments. This metric records changes if they are in the same direction. + Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + The time elapsed to complete training after which a new curve was generated. + Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + The time elapsed to complete training after which no new curve was + generated. Chrome OS only. + + + + + jiameng@chromium.org + wrong@chromium.org + tby@chromium.org + thanhdng@chromium.org + + How user manual screen brightness adjustment changes the model. Chrome OS + only. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/autofill/histograms.xml b/tools/metrics/histograms/histograms_xml/autofill/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..efee2e641fa26a5cc07c9976552c6236bb7e7995 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/autofill/histograms.xml @@ -0,0 +1,1992 @@ + + + + + + + + + + jsaul@google.com + chrome-autofill@google.com + + Tracks whether Profile (Address) Autofill is enabled on page load for a page + containing forms. + + + + + jsaul@google.com + chrome-autofill@google.com + + Tracks whether Profile (Address) Autofill is enabled when Chrome launches. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of unverified autofill addresses deleted because they have not + been used for a long time, and are not used as billing addresses of valid + credit cards. Note the deletion only happens once per major version upgrade. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of address suggestions not shown in the Autofill popup because + they have not been used recently enough. Note that suppression only applies + when the user has not typed any text into the field. If any text is in the + field, all matching addresses are displayed, regardless of how recently they + have been used. + + + + + koerber@google.com + battre@chromium.org + + Each country can require different fields (ZIP code, state, city) to exist + for an address to be valid. This histogram logs which mandatory fields were + missing in a submitted address form. + + + + + koerber@google.com + battre@chromium.org + + Logs whether the individual requirements for importing an address profile + are met at form submission time. + + + + + koerber@google.com + battre@chromium.org + + Logs the overall status of a profile import attempt on form submission time. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of address suggestions shown in the Autofill popup. + + + + + schwering@google.com + chrome-autofill@google.com + + Records at submission time for each autofilled field with autocomplete != + off whether the user edited the autofilled field value or not. + + + + + schwering@google.com + chrome-autofill@google.com + + Records for each submitted form whether the user accepted the suggestion to + fill values and the triggering field has autocomplete != off. This is + counted as 'yes' if the user accepted such a suggestion at any time, + regardless whether other suggestions were ignored or whether the accepted + suggestion was reverted afterwards. + + + + + schwering@google.com + chrome-autofill@google.com + + Records at submission time for each autofilled field with autocomplete = off + whether the user edited the autofilled field value or not. + + + + + schwering@google.com + chrome-autofill@google.com + + Records for each submitted form whether the user accepted the suggestion to + fill values and the triggering field has autocomplete = off. This is counted + as 'yes' if the user accepted such a suggestion at any time, regardless + whether other suggestions were ignored or whether the accepted suggestion + was reverted afterwards. + + + + + michaelbai@chromium.org + Whether autocomplete is enabled. + + + + michaelbai@chromium.org + Whether an autocomplete query is created for a field. + + + + michaelbai@chromium.org + Whether there is any suggestions for an autocomplete query. + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + Tracks the time it takes to fetch the full PAN of a credit card once user + successfully authenticates using WebAuthn. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + Tracks the number of times Chrome made a GetDetailsForGetRealPan call. A + preflight call is only made when card suggestions are shown, and can only + happen when the user has server cards and is eligible for WebAuthn. + + As a percentage of the number of times card suggestions are shown, which is + tracked under Autofill.FormEvents.CreditCard, this metric provides an + estimate for the potential reach for the Autofill Better Auth project. + Moreover, this acts as a baseline value for other metrics in this project. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + Tracking the latency of a GetDetailsForGetRealPan call to Payments servers. + This duration should be comparable to that of Autofill.UnmaskPrompt.Duration + and should ideally stay under 500 ms in order for the user to autofill their + credit card without experiencing much friction. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + If the user is definitely opted-in to the new auth flow, Payments sends a + list of instrument IDs in the GDFGRP call, and Chrome makes the final call + on whether CVC or WebAuthn should be shown. Tracks which authentication + method was prompted. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + Tracks when a user completes each step in a card unmasking flow per + authentication type. This will provide a relative conversion rate for each + authentication type. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + Tracks when users opt-in either from the settings page or from a checkout + flow, making an UpdateAutofillUserPreference call. For each call to + payments, logs if the call was made in order to verify an existing + credential, to create a new credential, or to fetch a challenge. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + Logs the number of times the opt-in promo to use FIDO authentication for + card unmasking has been shown. Only applicable on Desktop. + + This is useful when compared to Autofill.BetterAuth.OptInPromoUserDecision, + to see what percentage of users are interacting with the dialog. Also, when + an opted-out user receives the preflight call before selecting a card (which + is recorded by the first bucket in + Autofill.BetterAuth.UserPerceivedLatencyOnCardSelection.OptedOut), then the + promo should eventually show if the user selects a masked card and + successfully authenticates through CVC. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + Tracks the user response to the opt-in promo for using FIDO authentication + for card unmasking. The user can either accept the promo and proceed to + perform user-verification, can decline the promo immediately, or first + accept the promo but then decline while the challenge is being fetched. Only + applicable on Desktop. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + Tracks the number of times UpdateAutofillUserPreference has been called with + the intention of opting out from FIDO authentication using the toggle switch + on the payments section on the settings page. + + This will be useful when compared to values in + Autofill.BetterAuth.OptInCalled to give an idea of what percentage of users + decide to opt-out. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + The GetDetailsForGetRealPan call is made when card suggestions are shown. + This metric tracks whether the response is received before or after a card + is chosen by the user. For an opted-in user, a late response would imply + perceived latency. For an opted-out user, a late response would imply that + opt-in may not have been offered. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + The GetDetailsForGetRealPan call is made when card suggestions are shown. + This metric logs the duration of the perceived latency when the response for + this call is received after a card is chosen by an opted-in user. After + waiting a set number of seconds without receiving a response, Chrome will + fall back to CVC authentication. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + The GetDetailsForGetRealPan call is made when card suggestions are shown. If + an opted-in user selects a card before the response is returned, latency is + perceived. Given that the user perceives latency, this metric logs whether + the request timed out and fell back to CVC or if the request was completed + and continued to WebAuthn. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + Tracks how long it takes to check that the user is verifiable through + WebAuthn's IsUserVerifiablePlatformAuthenticatorAvailable() call. This check + is done before deciding to make a GetDetailsForGetRealPan call to Payments. + + + + + jsaul@google.com + manasverma@google.com + autofill-auth-team@google.com + + + + This metric tracks the result of the WebAuthn prompt when the user attempts + to either opt-in for FIDO authentication or unmask a card using FIDO + authentication. + + + + + jsaul@google.com + siyua@chromium.org + payments-autofill-team@google.com + + Events tracking the usage of the cardholder name fix flow prompt. This + prompt is triggered whenever cardholder name must be explicitly requested + from the user in order to upload the card to Google Payments. + + + + + jsaul@google.com + siyua@chromium.org + payments-autofill-team@google.com + + + + Records the length of CVCs sent to Payments when making card unmask calls, + to help determine if blank or invalid length CVCs are being sent. + + + + + jsaul@google.com + siyua@chromium.org + payments-autofill-team@google.com + + Whether upload was offered upon detecting a form submission with credit card + data, a detailed reason if upload was offered even with some missing fields + and detailed reasons if it wasn't. + + + + + aneeshali@google.com + jsaul@google.com + + Detailed reasons why (or why not) card upload was enabled. When a user + submits a form, this check is triggered to decide whether to ask the user if + she wants to upload the card. + + + + + jsaul@google.com + chrome-autofill@google.com + + Tracks whether Credit Card Autofill is enabled on page load for a page + containing forms. + + + + + jsaul@google.com + chrome-autofill@google.com + + Tracks whether Credit Card Autofill is enabled when Chrome launches. + + + + + battre@chromium.org + chrome-autofill@google.com + + The relative frequency with which users accept, deny, or ignore the Autofill + credit card assisted filling infobar prompt. + + + + + battre@chromium.org + jsaul@google.com + chrome-autofill@google.com + + The relative frequency with which users accept, deny, or ignore the Autofill + credit card info bar prompt. + + + + + battre@chromium.org + jsaul@google.com + chrome-autofill@google.com + + The number of credit card deleted during a major version upgrade because + they have not been used recently enough and are expired. + + + + + battre@chromium.org + jsaul@google.com + chrome-autofill@google.com + + The number of credit card suggestions not shown in the Autofill popup + because they have not been used recently enough and are expired. Note that + suppression only applies when the user has not typed any text into the + field. If any text is in the field, all matching cards are displayed, + regardless of how recently they have been used and their expiration status. + + + + + siyua@chromium.org + jsaul@google.com + + Records when credit card upload provides feedback on its status to the user. + + + + + battre@chromium.org + chrome-autofill@google.com + + Logs the number of days that have passed since the credit card was last + used. + + + + + battre@chromium.org + chrome-autofill@google.com + + Logged at the time of autofill address use, this histogram captures the + number of days that have passed since the address was last used. I.e., the + distribution of time between uses of an "active" autofill address. + + + + + battre@chromium.org + chrome-autofill@google.com + + + + Logs the number of days that have passed since each credit card belonging to + a given Chrome Profile was last used. This is logged for each Autofill + credit card once per Chrome User Profile load. + + + + + battre@chromium.org + chrome-autofill@google.com + + This histogram captures the number of days that have passed since each + stored address profile belonging to a given Chrome Profile was last used. + This is logged for each Autofill address profile once per Chrome User + Profile load. + + + + + battre@chromium.org + chrome-autofill@google.com + + Measures the adoption of the HTML autocomplete type hint specification (see + http://is.gd/whatwg_autocomplete for more details). For each fillable form + detected, logs whether that form includes author-specified type hints. + + + + + koerber@google.com + battre@google.com + + Total number of fields at submission time that were autofilled and have or + have not been editing by the user afterwards. + + + + + koerber@google.com + battre@google.com + + Total number of fields at submission time of a specific type that were + autofilled and have or have not been editing by the user afterwards. + + + + + siashah@google.com + jsaul@google.com + payments-autofill-team@google.com + + Events tracking the usage of the expiration date fix flow prompt. This + prompt is triggered whenever expiration date must be explicitly requested + from the user in order to upload the card to Google Payments. + + + + + siashah@google.com + jsaul@google.com + payments-autofill-team@google.com + + The number of times the expiration date fix flow prompt is shown. + + + + + kolos@chromium.org + battre@chromium.org + chrome-autofill@google.com + Number of fields in a form that Autofill encounters. + + + + + + battre@chromium.org + chrome-autofill@google.com + + Predicted and actual form field type. This is a computed sparse histogram + where the value is ((predicted << 16)| actual). Predicted and actual + are taken from the autofill::ServerFieldType enumeration. + + + + + + + battre@chromium.org + chrome-autofill@google.com + + Aggregate Autofill field-type prediction outcomes. See + https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the + values. + + + + + + + battre@chromium.org + chrome-autofill@google.com + + Autofill field-type prediction outcomes, broken down by field type. See + https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the + values. + + + + + battre@chromium.org + chrome-autofill@google.com + + Time elapsed between the user's first interaction with a form and the form's + submission, for an autofilled form. + + + + + battre@chromium.org + chrome-autofill@google.com + + Time elapsed between the user's first interaction with a form and the form's + submission, for a non-autofilled form. + + + + + battre@chromium.org + chrome-autofill@google.com + + Time elapsed between form load and form submission, for an autofilled form. + + + + + battre@chromium.org + chrome-autofill@google.com + + Time elapsed between form load and form submission, for a non-autofilled + form. + + + + + battre@chromium.org + jsaul@google.com + + Autofill form events for address forms. These are recorded when the user + interacts with a form requesting an address. + +
+ Important caveat about submission metrics: - Submission using autofill data + is determined by simply evaluating if there was a fill operation in this + page. So, if the user filled with local data, completed erased or modified + the data after and then submitted, we would only emit one "Submitted + with server suggestion filled (once)"; - The submission segmentation + works by checking what kind of data was last filled for this type of form in + the page load. So, if a user initially filled with local data and after that + filled with server, we will only emit "Submitted with server suggestion + filled (once)". +
+ + + + jsaul@google.com + battre@chromium.org + + Autofill form events for credit card forms. These are recorded when the user + interacts with a form requesting a credit card. + +
+ Important caveat about submission metrics: - Submission using autofill data + is determined by simply evaluating if there was a fill operation in this + page. So, if the user filled with local data, completed erased or modified + the data after and then submitted, we would only emit one "Submitted + with server suggestion filled (once)"; - The submission segmentation + works by checking what kind of data was last filled for this type of form in + the page load. So, if a user initially filled with local data and after that + filled with server, we will only emit "Submitted with server suggestion + filled (once)". +
+ + + + estark@chromium.org + + Autofill form events for credit card forms on nonsecure pages. These are + recorded when the user interacts with a form requesting a credit card. + +
+ Important caveat about submission metrics: - Submission using autofill data + is determined by simply evaluating if there was a fill operation in this + page. So, if the user filled with local data, completed erased or modified + the data after and then submitted, we would only emit one "Submitted + with server suggestion filled (once)"; - The submission segmentation + works by checking what kind of data was last filled for this type of form in + the page load. So, if a user initially filled with local data and after that + filled with server, we will only emit "Submitted with server suggestion + filled (once)". +
+ + + + sujiezhu@google.com + jsaul@google.com + + Autofill form events for credit card forms. These are recorded when the user + interacts with a form requesting a credit card, a dropdown of suggestions is + shown and at least one of the suggestions has a server nickname available. + +
+ These metrics are used to measure the impact of the server card nickname + experiment. They are used to calculate the suggestion selection rate with + server nickname available. We will run the experiment on the same group of + user who has server cards with nicknames to compare the selection rate. For + enabled user, we will show nickname and log. For the other, we won't show + nickname in suggestion but we still log to this histogram. +
+ + + + sujiezhu@google.com + jsaul@google.com + + Time elapsed between when the first Autofill suggestion is shown and user + first chooses a card, for a credit card form, where the user has at least + one card with a server nickname available. Log only once per form. We will + run the experiment on the same group of user who have server cards with + nicknames to compare the selection duration. For enabled user, we will show + nickname and log. For the other, we won't show nickname in suggestion but we + still log to this histogram. + + + + + battre@chromium.org + chrome-autofill@google.com + The autofill state related to a submitted form. + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts whether users accepted any autofill suggestion that was shown to them + for a given form. + + This metric is only recorded if a suggestion for the given form type (see + histogram name) was shown at least once. This is recorded once per form. If + the user accepts one suggestion, this is reported as "User chose to + fill" once. It does not matter if the user clears the filled values nor + if the user accepts a different suggestion later. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts whether users interacted with a form of a certain type. + + Focusing a field is sufficient to consider a form as being interacted with. + The user does not need to type anything. Note that some forms may get + focused on page load. + + This metric is recorded once per form observed by Autofill, but only for + forms that Autofill classifies to be of the type indicated by the histogram + name. If a form changes dynamically, Autofill interprets the forms before + and after the change as two different forms and records two values. If a + form did not have features that classify it as a form of a certain type + (e.g. an address form or payment form), then nothing is recorded. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts whether a form was parsed/interpreted to be of the type indicated in + the histogram name. + + This metric is recorded once for each form observed by Autofill. If a form + changes dynamically, then Autofill treats the different versions of the form + as different forms. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts whether users submitted a form that was filled via autofill. + + This metric is recorded once for each form observed by Autofill but only for + forms that the user filled via Autofill. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts whether users were shown suggestions to fill the form, given that + they have already interacted with the form. + + This metric is recorded only for forms that users interacted with. It is + recorded only once per form, meaning that it does not matter how often the + user sees suggestions. If a form changes dynamically, then Autofill treats + the different versions of the form as different forms. + + + + + jsaul@google.com + battre@chromium.org + + Whether the user had opted-in to seeing their server cards in Wallet Sync + Transport mode. Recorded when showing the autofill dropdown for credit + cards. + + + + + battre@chromium.org + chrome-autofill@google.com + + Logs when a hidden or presentational field is autofilled. The hidden or + presentational fields are only autofilled for 'select' fields to support + synthetic fields. + + + + + battre@chromium.org + chrome-autofill@google.com + + Tracks whether or not autofill suppressed sending votes or calculating + quality metrics because the profile data was marked as invalid. Logged + during field-type validation if/when a field marked as invalid is found to + match the submitted data. + + + + + battre@chromium.org + chrome-autofill@google.com + + Tracks whether or not autofill suppressed offering an autofill suggestion + because the profile data was marked as invalid. Logged during autofill + suggestion generation when a suggestion is about to generated based on a + field marked as invalid. + + + + + jsaul@google.com + battre@chromium.org + chrome-autofill@google.com + + This includes Autofill.Address.IsEnabled.PageLoad and + Autofill.CreditCard.IsEnabled.PageLoad, and tracks whether either profile + Autofill or payment Autofill is enabled on page load for a page containing + forms. It helps deduce the overlap by showing what percentage of users have + one type of Autofill enabled but not the other. + + + + + jsaul@google.com + battre@chromium.org + chrome-autofill@google.com + + This includes Autofill.Address.IsEnabled.Startup and + Autofill.CreditCard.IsEnabled.Startup, and tracks whether either profile + Autofill or payment Autofill is enabled when Chrome launches. It helps + deduce the overlap by showing what percentage of users have one type of + Autofill enabled but not the other. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for submitted forms whether users accepted the suggestion to fill + values. This is counted as 'yes' if the user accepted such a suggestion at + any time, regardless whether other suggestions were ignored or whether the + accepted suggestion was reverted afterwards. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for submitted forms whether the user filled any fields via Autofill. + + If the user reverts the filling, the form is still counted as filled. + + This metric is different from Autofill.KeyMetrics.FillingAcceptance in the + sense that the latter is only recorded if the user has actually seen a + prompt to fill data. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for submitted and autofilled forms whether users edited at least one + filled value before submitting the form. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for submitted forms whether Chromium had any address or payments data + to fill. + + It does not matter whether the user actually requested to fill the data. It + does not matter either whether the data available for filling corresponded + to the submitted data. + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for filled (by Autofill) forms whether users submitted those forms. + + This is only recorded for forms that the user filled via Autofill. It does + not matter if the user reverted the filling afterwards. + + This is recorded once Autofill stops tracking the form (e.g. due to a + navigation or due to removal from the DOM). + + + + + battre@chromium.org + kolos@chromium.org + nepper@chromium.org + + Counts for not filled (by Autofill) forms whether users submitted those + forms. + + This is only recorded for forms into which the user typed anything but did + not fill anything. It does not matter if the user reverted what they typed. + + This is recorded once Autofill stops tracking the form (e.g. due to a + navigation or due to removal from the DOM). + + + + + siyua@chromium.org + jsaul@google.com + + Record events related to bubble showing. Logged when bubble is requested or + is actually shown to users. + + + + + siyua@chromium.org + jsaul@google.com + + Records whether and how the local card migration bubble was accepted or + closed. + + + + + siyua@chromium.org + jsaul@google.com + Record how bubble is closed by different user interactions. + + + + sujiezhu@google.com + siyua@chromium.org + jsaul@google.com + + Record the decisions made when determining if local card migration should be + offered. + + + + + siyua@chromium.org + jsaul@google.com + + Record duration of the local card migration dialog being visible to users. + + + + + siyua@chromium.org + jsaul@google.com + + Record events related to showing the local card migration dialog. + + + + + siyua@chromium.org + jsaul@google.com + + Record user interactions related to local card migration dialog. + + + + + siyua@chromium.org + jsaul@google.com + + Record the percentage of cards selected by the user in the migration dialog. + + + + + siyua@chromium.org + jsaul@google.com + + Records when local card migration prompts are shown and/or accepted. + + + + + manasverma@google.com + jsaul@google.com + + The frequency of user interactions with the Manage Cards prompt. + + + + + msarda@google.com + payments-autofill-team@google.com + + This metric is recorded when the bit that indicates the user is opted in to + wallet sync transport is migrated (part of the migration from using email to + using Gaia ID as the account identifier). + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of autofilled fields that were subsequently edited prior to the + form being submitted. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of Autofill profiles that have been considered for deduplication. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of Autofill profiles that have been removed during deduplication. + + + + + battre@chromium.org + chrome-autofill@google.com + + Records whether the number of fillable form elements matches the number of + fields in the form's description. Instances where this is recorded as False, + denote cases where autofill failed to preview/fill an autofill suggestion. + This can happen when a fields is filtered out of a formless form. + + + + + siyua@chromium.org + payments-autofill-team@google.com + + Tracks the number of autofill offers data a user has stored, measured at + Chrome profile launch time. + + + + + siyua@chromium.org + payments-autofill-team@google.com + + Tracks the number of the credit cards an autofill card linked offer data is + related to, measured at Chrome profile launch time. + + + + + siyua@chromium.org + payments-autofill-team@google.com + + Tracks the number of the merchants an autofill offer data is related to, + measured at Chrome profile launch time. + + + + + siyua@chromium.org + payments-autofill-team@google.com + + Tracks whether the offer data is valid or not, measured whenever offer data + is synced down via Sync. + + + + + marsin@google.com + koerber@google.com + + Tracks whether the visible page language was translated or not upon form + submission. + + + + + battre@chromium.org + chrome-autofill@google.com + + The profile action that took place when a form was submitted. + + + + + battre@chromium.org + src/components/autofill/OWNERS + + This metric is recorded when the autofill-use-improved-label-disambiguation + experiment is enabled and profile suggestions are available. This metric + measures how often suggestions were created with and without a formatter. + + + + + battre@chromium.org + chrome-autofill@google.com + + For credit card forms that are queried for Autofill, a ratio of how many are + within secure contexts (which includes mixed passive content). + + + + + battre@chromium.org + chrome-autofill@google.com + + The delay of a network request for a query due to exponential backoff. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of bytes that were sent in a query that subsequently failed. This + is to help determine the appropriate threshold at which autofill queries + should switch from GET to POST, and if there are certain sizes of queries + which are prone to failure. + + + + + battre@chromium.org + chrome-autofill@google.com + + The http response code or net error code returned on a query. + + + + + battre@chromium.org + chrome-autofill@google.com + The HTTP method used to query the autofill server. + + + + battre@chromium.org + chrome-autofill@google.com + The duration of a network request for a query. + + + + battre@chromium.org + chrome-autofill@google.com + + Was the autofill query response retrieved from the HTTP cache. + + + + + battre@chromium.org + chrome-autofill@google.com + + The quality of fields rationalization, putting rationalization result into + good/ok/bad categories. + + + + + jsaul@google.com + payments-autofill-team@google.com + + If the cardholder name fix flow is shown when credit card upload is offered, + records if the cardholder name textfield was prefilled with the name from + the user's Google Account. + + + + + jsaul@google.com + payments-autofill-team@google.com + + If the cardholder name fix flow is shown during credit card upload and the + user accepts upload, logs whether the final cardholder name was changed from + its prefilled value or not. + + + + + jsaul@google.com + payments-autofill-team@google.com + + Records the reason expiration date was explicitly requested from the user + during credit card save. + + + + + jsaul@google.com + siyua@chromium.org + + The relative frequency with which users accept or deny the Autofill save + credit card prompt. + + + + + jsaul@google.com + siyua@chromium.org + + The relative frequency with which the Autofill save credit card prompt is + shown or not. Logged when the flow is triggered and the prompt should be + shown. + + + + + jsaul@google.com + siyua@chromium.org + + The relative frequency with which users accept or deny the Autofill save + credit card prompt. Logged when users interacted with the prompt. + + + + + battre@chromium.org + chrome-autofill@google.com + Whether a credit card scan was completed or cancelled. + + + + battre@chromium.org + chrome-autofill@google.com + How long a credit card took to scan. + + + + battre@chromium.org + jsaul@chromium.org + chrome-autofill@google.com + Usage of the "Scan card" control item. + + + + jsaul@google.com + battre@chromium.org + chrome-autofill@google.com + + Logged when the user clicks on the server credit card link in the settings + page. + + + + + battre@chromium.org + chrome-autofill@google.com + The usefulness of Autofill server information. + + + + battre@chromium.org + chrome-autofill@google.com + + Tracks whether Autofill server had at least some prediction data for a given + form at query response time. + + + + + battre@chromium.org + chrome-autofill@google.com + + + + The number of credit cards a user has stored, measured at Chrome profile + launch time. + + + + + battre@chromium.org + chrome-autofill@google.com + + + + The number of disused credit cards a user has stored, measured at Chrome + profile launch time. This is only reported for users who have at least one + stored credit card. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of Autofill addresses a user has stored, measured at launch time. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of Autofill addresses a user has stored, measured when an + autofillable form is submitted. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of stored Autofill address profiles which have not been used in a + sufficiently long time for autofill to consider them disused. Measured once + per Chrome user profile launch. + + + + + jsaul@google.com + annelim@google.com + + Records when credit card save is not offered (either at all on mobile or by + simply not showing the bubble on desktop) due to the candidate card having + too many strikes. + + + + + jsaul@google.com + annelim@google.com + + Records when local card migration is not offered due to the candidate's + LocalCardMigration strike count reaching maximum strikes. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" a given card has, when a user + dismisses a prompt to save a new credit card. The strike count is + incremented each time the user dismisses the prompt. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" a user has, when a prompt for + local card migration is dismissed. The strike count is incremented each time + the user dismisses the prompt. + + + + + jsaul@google.com + annelim@google.com + + When a StrikeDatabase fails to initialize, records the number of consecutive + failed initialization attempts. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" a user has when local card + migration is accepted. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" a given card had when a user opted + to save the card to Chrome. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" a given card had when a user + successfully uploaded the card to Google Payments. + + + + + jsaul@google.com + annelim@google.com + + Records the number of "strikes" present in a StrikeDatabase entry + when a strike expires. + + + + + jsaul@google.com + payments-autofill-team@google.com + + Metric to measure credit card state when form is submitted, specifically if + it had a valid card number and/or expiration date. + + + + + jsaul@google.com + payments-autofill-team@google.com + + Metric to measure if a submitted card's expiration date matches the same + server card's expiration date (unmasked or not). Cards are considered to be + the same if they have the same card number (if unmasked) or if they have the + same network and last four digits (if masked). + + + + + kolos@chromium.org + jsaul@google.com + + Metric to measure if a submitted form contains any recognizable value + patterns (e.g., Unified Payment Interface Virtual Payment address (UPI + VPA)). Reported for every submitted non-empty visible field observed by + Autofill. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Records acceptance of autofill suggestions in regular and off-the-record + modes. + + + + + battre@chromium.org + chrome-autofill@google.com + + The index of the accepted Autofill suggestion in the popup. Due to + crbug.com/966411, the iOS data is incorrect. + + + + + battre@chromium.org + chrome-autofill@google.com + + The index of the accepted Autocomplete suggestion in the popup. Due to + crbug.com/966411, the iOS data is incorrect. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Records showing of autofill suggestions in regular and off-the-record modes. + + + + + kenjitoyama@chromium.org + battre@chromium.org + chrome-autofill@google.com + + Number of milliseconds passed between the start and end of + FormStructure::DetermineHeuristicTypes(). + + + + + kenjitoyama@chromium.org + battre@chromium.org + chrome-autofill@google.com + + Number of milliseconds passed between the start and end of parsing a single + form. + + + + + marsin@google.com + koerber@google.com + + The visible page language (best guess of the original or the translated + language, if translation was used) upon form submission. This is a sparse + histogram where the integer value represents the language code as described + by the ISO 639 standard. + + + + + jsaul@google.com + siyua@chromium.org + + Duration of the interaction with the UnmaskPrompt since it was shown until + it was closed. This prompt is triggered when a user selects a masked card in + an autofill dropdown. + + + + + jsaul@google.com + siyua@chromium.org + + Events tracking the usage of the unmasking prompt. This prompt is triggered + when a user selects a masked card in a autofill dropdown. + + + + + jsaul@google.com + siyua@chromium.org + + Duration of the GetRealPan API call. This API call is triggered by the + unmasking prompt when the user types information to verify their ownership + of the card being fetched. + + + + + jsaul@google.com + siyua@chromium.org + + Tracks the result of the GetRealPan API call. This API call is triggered by + the unmasking prompt when the user types information to verify their + ownership of the card being fetched. + + + + + jsaul@google.com + siyua@chromium.org + + Time the user waited before abandoning an unmasking operation. In such a + scenario, the user is cancelling a pending unmasking operation (possibly + because it is taking too long). The time measured here corresponds to the + time between the user clicking the "Verify" button and then + clicking "Cancel". + + + + + jsaul@google.com + siyua@chromium.org + + Duration between the user clicking the Verify button within the unmasking + prompt until we get a response back from the server. This prompt is + triggered when a user selects a masked card in an autofill dropdown. + + + + + battre@chromium.org + chrome-autofill@google.com + + Records incidents where an implicit (formless) form has elements filtered + out of it. This happens to unowned fields (directly embedded in the page + with no enclosing <form> tag) without autocomplete attributes if + formless forms are restricted to "checkout" pages. Logged when + parsing forms/fields. + + + + + + + battre@chromium.org + chrome-autofill@google.com + + The delay of a network request for an upload due to exponential backoff. + + + + + battre@chromium.org + chrome-autofill@google.com + + The number of bytes that were sent in an upload that subsequently failed. + This is to help determine if there are certain upload sizes which are prone + to failure. + + + + + + + battre@chromium.org + chrome-autofill@google.com + + The http response code or net error code returned on an upload. + + + + + battre@chromium.org + chrome-autofill@google.com + + Tracks whether or not the configuration fo metadata upload encoding is valid + or invalid. Note that if the configuration is invalid, the client will fall + back to a default configuration that sends 4 bits per byte (i.e., either the + even or odd bits encoding). + + + + + battre@chromium.org + chrome-autofill@google.com + + The metadata encoding scheme used by the client to encode rich uploads. + + + + + + + battre@chromium.org + chrome-autofill@google.com + The duration of a network request for an upload. + + + + + + jsaul@google.com + + Measures if a card for which upload was accepted is already stored as a + local card on the device or if it has not yet been seen. + + + + + + + battre@chromium.org + chrome-autofill@google.com + + Whether or not an upload was sent after having been triggered by a form + submission or proxy-form-submission. + + + + + + + jsaul@google.com + + Measures if a card for which upload was offered is already stored as a local + on the device or if it has not yet been seen. + + + + + jsaul@google.com + annelim@google.com + + Records the number of times that the cache for unmasked server cards has + been accessed for a given card. For example, if the cache is being accessed + and it has already been accessed for the card twice before, then + "3" is recorded. + + + + + battre@chromium.org + chrome-autofill@google.com + + Measures the frequency of various events in the Autofill user interaction + flow. By comparing frequencies, we can compute several interesting + "user happiness" metrics. + + + + + battre@chromium.org + chrome-autofill@google.com + + Tracks how the different wallet addresses are converted to local autofill + profiles. + + + + + yigu@chromium.org + battre@chromium.org + web-identity@google.com + + Records whether a frame has ever used autocomplete="one-time-code" + during its lifecycle. i.e. it's only recorded once per frame. In addition, + we only record it if the frame has parsed forms. + + + + + yigu@chromium.org + battre@chromium.org + web-identity@google.com + + Records whether a frame collects phone number based on the field + classification. It records once per frame only if it has parsed forms. + + Note that the field types may not be calculated if there are less than 3 + fields in the form unless an autocomplete attribute is provided. e.g. if the + form has only a single field regarding phone number without specifiying + autocomplete="phone", a sample with "false" will be + reported. + + + + + yigu@chromium.org + madjivp@chromium.org + web-identity@google.com + + Records whether a document collected phone number, and/or used WebOTP, + and/or used OneTimeCode (OTC) during its lifecycle. i.e. it's recorded in + the browser process when a document is destroyed. + + + + + michaelbai@chromium.org + src/android_webview/OWNERS + Records the state of an autofill session. + + + + michaelbai@chromium.org + src/android_webview/OWNERS + Whether the autofill is created by activity context. + + + + michaelbai@chromium.org + src/android_webview/OWNERS + + Whether the autofill service is enabled in Android platform. + + + + + michaelbai@chromium.org + src/android_webview/OWNERS + Records the source of form submission. + + + + michaelbai@chromium.org + src/android_webview/OWNERS + The time taken to display suggestion. + + + + michaelbai@chromium.org + src/android_webview/OWNERS + Whether the user changed autofilled field. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/back_forward_cache/histograms.xml b/tools/metrics/histograms/histograms_xml/back_forward_cache/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..f9fd5e8d25120c9039d3eb3a1ce53d219defc897 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/back_forward_cache/histograms.xml @@ -0,0 +1,420 @@ + + + + + + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Records the reason why the page is evicted from the back-forward cache but + after the document is restored. This happens when there is a race between + eviction and restoring. This also records when the page is restored to + calculate how often this eviction happens. + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, this records whether + the page was restored from the BackForwardCache or not. + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, this records what + blocklisted features were used when the page was loaded and prevented this + page from being stored in the back-forward cache. Multiple blocklisted + features can be recorded for the same page. + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history and the + BackForwardCache wasn't used because of the related browsing instances, this + records the reason why the browsing instance wasn't swapped. + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + carlscab@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + For history navigations, records the reasons passed to + BackForwardCache::DisableForRenderFrameHost calls. These reasons are + specified as strings, so this histograms contains their hashes computed as + base::HashMetricName. + + The metric is recorded when a history navigation commits and emits a sample + for each reason. Compare this with + BackForwardCache.HistoryNavigationOutcome, which contains the total number + of navigations which where not cached + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, record why it wasn't + restored from the cache. The page might not have entered the back-forward in + the first place based on the features used, or it might have been evicted + while being in the cache. + + This is recorded for all websites regardless whether back-forward cache is + enabled or not. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Records the reason why the page is evicted from the back-forward cache but + after the document is restored. This happens when there is a race between + eviction and restoring. This also records when the page is restored to + calculate how often this eviction happens. + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Records the time duration between the last time when the entry goes to the + back-forward cache and the time when the process is killed. + + + + + hbolaria@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Track number of times an unexpected IPC message is posted to frames in the + renderer process while they are frozen in the back-forward cache. IPC tasks + are denoted by md5 hash of the mojo bindings method name or message hash for + legacy IPCs. + + Recorded when an IPC task is posted to frames that have already been stored + in the back-forward cache, after a 15 second delay to account for completion + of all freezing-related operations. + + + + + hbolaria@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Duration between start of page being stored in the back-forward cache and + when the unexpected IPC call is received by a frame while in the cache. + + Recorded when an IPC task is posted to frames that have already been stored + in the back-forward cache, after a 15 second delay to account for completion + of all freezing-related operations. + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, this records whether + the page was restored from the BackForwardCache or not. + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, this records what + blocklisted features were used when the page was loaded and prevented this + page from being stored in the back-forward cache. Multiple blocklisted + features can be recorded for the same page. + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history and the + BackForwardCache wasn't used because of the related browsing instances, this + records the reason why the browsing instance wasn't swapped. + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + carlscab@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + For history navigations, records the reasons passed to + BackForwardCache::DisableForRenderFrameHost calls. These reasons are + specified as strings, so this histograms contains their hashes computed as + base::HashMetricName. + + The metric is recorded when a history navigation commits and emits a sample + for each reason. Compare this with + BackForwardCache.HistoryNavigationOutcome, which contains the total number + of navigations which where not cached + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + When navigating back to a page in the session history, record why it wasn't + restored from the cache. The page might not have entered the back-forward in + the first place based on the features used, or it might have been evicted + while being in the cache. + + This is recorded when back-forward cache is enabled for this navigation + (back-forward cache feature is enabled and the domain is in the scope of the + experiment). + + + + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Records whether a page restored from the back-forward cache has pageshow + handlers installed in its main frame. Recorded when the renderer resumes + page when restoring it from the back-forward cache. + + + + + rakina@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records whether a page where we did a same-site proactive BrowsingInstance + swap on (with the intention on storing it in the back-forward cache later) + is still eligible for back-forward cache when swapping out the old page + during navigation commit. Recorded when we have just finished committing the + new page on the renderer side, and during the commit of the new page in the + browser side. + + + + + rakina@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records whether we did a same-site proactive BrowsingInstance swap or not + for a same-site cross-document navigation. Recorded when we are committing + the navigation. + + + + + rakina@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records whether a page where we did a same-site proactive BrowsingInstance + swap on (with the intention on storing it in the back-forward cache later) + is no longer eligible for back-forward cache after the navigation committed + and the page has unload handlers that will run after commit, which is a + web-observable behavior change for same-site navigations. Recorded when we + have just finished committing the new page on the renderer side, and during + the commit of the new page in the browser side. + + + + + sreejakshetty@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records the number of reloads after a history navigation both for the cases + when page is served and not served from back-forward cache. + + This is recorded when navigation is committed, only for the domains which + are in the scope of back-forward cache experiment and they are of same + NavigationEntry (e.g. back and reload in different tab do not count). + + + + + sreejakshetty@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records the total number of history navigations along with the number of + reloads if the previous navigation was a history one. + + This is recorded when navigation is committed, only for the domains which + are in the scope of back-forward cache experiment. + + + + + sreejakshetty@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Duration between start of navigation restoring a document from back-forward + cache and the first paint. + + This is recorded when a history navigation is served from back-forward cache + but in a foreground tab. + + + + + rakina@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records occurences of certain actions triggered by script running on a page + after the pagehide event gets dispatched in the page, which might be + possible if we dispatch the pagehide event without unloading/freezing the + page (only happens when we're doing a same-site navigation and we did a + proactive BrowsingInstance swap but we're reusing the old page's process). + + Note: We will only track actions that might affect the user after we've + navigated away from the old page, such as modifications to storage, + navigations, or sending/receiving postMessage. + + Note 2: We will not track actions taken when the unload event is currently + in progress, which means the page is not actually stored in the back-forward + cache and the actions are expected to happen after pagehide. + + + + + carlscab@google.com + bfcache-dev@chromium.org + + Hash (base::HashMetricName) of a mojo interface name. + + A sample is recorded for every message the browser receives from a renderer + for a page that is in the back-forward cache. Logging can be disabled via + the back-forward cache feature parameter + "message_handling_when_cached". + + Renderers should not be sending messages back to the browser for pages that + are in the back-forward cache. Eventually we will be killing such renderers + (as we could assume that it is misbehaving because it got compromised). But + first we must make sure that we are not sending messages by mistake (i.e. + bugs in the renderer). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/background/histograms.xml b/tools/metrics/histograms/histograms_xml/background/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0fa81b609ad4a757ed2d506f53dbd28ebf8e3106 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/background/histograms.xml @@ -0,0 +1,481 @@ + + + + + + + + + + + + peter@chromium.org + rayankans@chromium.org + + Records the Service Worker status code that caused a Background Fetch API + event to fail dispatching whilst trying to dispatch an event on the active + Service Worker. + + + + + + + peter@chromium.org + rayankans@chromium.org + + Records the Service Worker status code that caused a Background Fetch API + event to fail dispatching whilst trying to find the Service Worker. + + + + + + + peter@chromium.org + rayankans@chromium.org + + Records the Service Worker status code that caused a Background Fetch API + event to fail dispatching whilst trying to start the active Service Worker. + + + + + + + peter@chromium.org + rayankans@chromium.org + + Records the result of dispatching one of the Background Fetch API events to + the Service Worker associated with the event. + + + + + peter@chromium.org + rayankans@chromium.org + + Records whether the fetch requests contains any duplicate URLs. This is + called after the provided requests are verified, but before the fetch is + started. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether the background fetch contains any requests with a body. + Called before the fetch is started. + + + + + rayankans@chromium.org + peter@chromium.org + + Records the number of Background Fetch registrations found on browser + start-up. This is called after the initialization database task runs + successfully. + + + + + + + rayankans@chromium.org + peter@chromium.org + + Records the duration of the mojo call for the exposed BackgroundFetchManager + APIs. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether match() or matchAll() was called from Document Scope. Called + when match() or matchAll() is invoked in the renderer process. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether match() or matchAll() was called when the background fetch + was incomplete. Called when match() or matchAll() is invoked in the renderer + process. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records the percent of requests for which updates are received in the + renderer process from the browser process. Called when the completion event + for a background fetch has finished processing. + + + + + + + rayankans@chromium.org + peter@chromium.org + Records the storage error when running a database task. + + + + atwilson@chromium.org + mvanouwerkerk@chromium.org + + The number of background applications (extensions) for a profile that were + loaded after the profile was registered with the BackgroundModeManager. + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + Logged if BackgroundModeManager is running and listening for pref changes, + and the pref does indeed change. The new value is logged. + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + Logged when an item in the system tray icon menu is clicked. + + + + + gab@chromium.org + mvanouwerkerk@chromium.org + + Logged during BackgroundModeManager's initialization. Indicates the + AutoLaunchState the current browser process was launched in. + + + + + gab@chromium.org + mvanouwerkerk@chromium.org + + Logged during BackgroundModeManager's initialization. Indicates the state of + the kBackgroundModeEnabled pref on startup. + + + + + peter@chromium.org + mvanouwerkerk@chromium.org + + The duration of a session before the browser got restarted in the background + by the BackgroundOptimizer to purge the memory. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the number of `sync` events which were fired in a batch. A batch is + defined as the set of `sync` events dispatched at the same time by the + BackgroundSyncManager. One-shots usually run individually (a batch of one), + unless the device was offline and multiple are waiting for the device to go + back online. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether the fired `sync` events upon completion orginated from a + background wakeup task or the foreground. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether a `sync` event succeeded or failed and whether the sync + event finished in the foreground or background. + +
+ A `sync` event finished in the foreground if the associated Service Worker + Registration has a client at the time that the event finished. +
+ + + + nator@chromium.org + rayankans@chromium.org + + Records whether a one-shot sync started firing in the foreground or + background. Called shortly before the event is fired. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether a periodic sync event succeeded or failed and whether the + sync event finished in the foreground or background. + +
+ A sync event finished in the foreground if the associated Service Worker + Registration has a client at the time that the event finished. +
+ + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether a periodic sync event started firing in the foreground or + background. Called shortly before the event is fired. + + + + + nator@chromium.org + rayankans@chromium.org + + Time taken to execute a batch of one-shot sync events. A batch is defined as + the set of sync events dispatched at the same time by the + BackgroundSyncManager. One-shots usually run individually (a batch of one), + unless the device was offline and multiple are waiting for the device to go + back online. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether Google Play Services is available to the Background Sync + system on Android, for scheduling future sync events when the browser is not + running. This will be logged at most once per run. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether the browser has sufficient permissions to create a + BackgroundSyncNetworkObserver object on Android, at the point when it tries + to create it. This should never be false, but is being tracked in order to + help resolve crbug.com/545473. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + Records time elapsed since the soonest expected wake-up time. Recorded + whenever a periodic Background Sync Chrome wake-up task is called after + loading the native parts of the browser. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the result of attempting to register a one-shot sync. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the result of attempting to register a one-shot sync in a situation + where the sync could fire immediately. + + + + + nator@chromium.org + rayankans@chromium.org + peter@chromium.org + + Records whether the dispatched sync event succeeded at the completion of the + one-shot Background Sync registration. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether a one-shot sync registration exactly duplicates an existing + registered sync. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the number of times a sync event was dispatched for a one-shot + Background Sync registration before it succeeded. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the result of attempting to register a periodic sync. This is called + at each successful registration. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether a periodic sync registration duplicates the tag of an + existing registered sync. Recorded upon each successful periodic Background + Sync registration. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the minInterval requested, in seconds, when a periodic sync is + successfully registered. + + + + + nator@chromium.org + platform-capabilities@chromium.org + + Records the result of attempting to unregister a periodic sync. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + If BackgroundSync uses BackgroundTaskScheduler to wake up Chrome, this + records the time elapsed since the soonest expected wake-up time. Recorded + whenever a BackgroundSync background task is called after loading the native + parts of the browser. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + If Chrome is woken up by the one shot Background Sync Background task, this + records whether any sync events were fired as a result. Recorded whenever + Chrome is woken up to process one-shot Background Sync registrations on + Android. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + If Chrome is woken up by the periodic Background Sync Background task,this + records whether any periodicsync events were fired as a result. Recorded + whenever Chrome is woken up to process periodic Background Sync + registrations on Android. + + + + + ssid@chromium.org + Records the reason for unwind failues in sampling profiler. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/Blink/histograms.xml b/tools/metrics/histograms/histograms_xml/blink/histograms.xml similarity index 99% rename from tools/metrics/histograms/histograms_xml/Blink/histograms.xml rename to tools/metrics/histograms/histograms_xml/blink/histograms.xml index 8421cb083477e18bd17b85076d82d5f149c08193..0539a3eef8c2b3658d7dc658daef6dae7ac4b6a8 100644 --- a/tools/metrics/histograms/histograms_xml/Blink/histograms.xml +++ b/tools/metrics/histograms/histograms_xml/blink/histograms.xml @@ -5,15 +5,12 @@ found in the LICENSE file. --> + + + + + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Disconnected GATT connection status codes. Used to better understand errors + seen in Android. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Failed GATT connection error codes. Used to better understand errors seen in + Android. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Successful GATT connection result codes. Used to better understand Android + results. + + + + + kenrb@chromium.org + kpaulhamus@chromium.org + + Determines the availability and capabilities of the Bluetooth driver. This + metric is logged on startup. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Records how long it takes for the user to select a device either after they + open the UI and Bluetooth is on, or after Bluetooth turns on while the UI is + open. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Records how long it takes for a failed pairing attempt, initiated from + Bluetooth Settings or System Tray, to finish. If the user needed to go + through an auth process during pairing, the time the user took to confirm + that is not included. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Records how long it takes for a successful pairing attempt, initiated from + Bluetooth Settings or System Tray, to finish. If the user needed to go + through an auth process during pairing, the time the user took to confirm + that is not included. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Records success or failure of a pairing attempt (initiated in the UI) to a + peripheral after the user taps that device in the list of discovered + peripherals in Bluetooth Settings or System Tray. + + Suffixed by Bluetooth transport type. View the base histogram to see results + for all transport types aggregated together, and suffixed histograms for the + results of just that particular transport type. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Breaks down why a pairing attempt to a peripheral failed (see + 'Bluetooth.ChromeOS.Pairing.Result'). + + Suffixed by Bluetooth transport type. View the base histogram to see results + for all transport types aggregated together, and suffixed histograms for the + results of just that particular transport type. + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + An enumerated histogram which captures the transport type of devices which + are paired with. Reports of transport types other than classic, BLE, or dual + should be considered concerning and investigated. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Records success or failure of a reconnection attempt to an already paired + peripheral after the user taps that device in the list of peripherals in + Bluetooth Settings or System Tray. Explicitly excludes automatic + reconnection attempts initiated by Chrome OS. + + Suffixed by Bluetooth UI surface. View the base histogram to see results for + all UI surfaces aggregated together, and suffixed histograms for the results + of just that particular UI surfaces. + + + + + + + hansberry@chromium.org + cros-system-services-networking@google.com + + Breaks down why a user-initiated reconnection attempt to a peripheral failed + (see 'Bluetooth.ChromeOS.UserInitiatedReconnectionAttempt.Result'). + + Suffixed by Bluetooth UI surface. View the base histogram to see results for + all UI surfaces aggregated together, and suffixed histograms for the results + of just that particular UI surfaces. + + + + + adlr@chromium.org + + Counts the number of simulataneously connected Bluetooth devices. Used to + direct testing efforts, and by our UI team to determine appropriate UI + sizes. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of calls to BluetoothAdapter::StartDiscoverySession. + Used to prioritize efforts to fix failures of this function. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of calls to BluetoothDiscoverySession::Stop. Used to + prioritize efforts to fix failures of this function. + + + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many times each macOS GATT error has occured. The results will + be used to determine how commun this errors are and if we need to provide + better error messages to the users. + + + + + adlr@chromium.org + + Records the method used to pair each Bluetooth Device. Used to direct our + testing efforts. + + + + + adlr@chromium.org + + Records the result of pairing each Bluetooth Device. Used to understand + whether we are having significant problems with Bluetooth pairing and seeing + errors more commonly than we should. + + + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + 'status' values returned by Android GATT event. + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of BluetoothBlocklist::Add parsing a non-empty string. + These strings will be updated dynamically by a server, and this histogram + provides feedback that parsing is functioning correctly on clients. + + False values are BAD, a blocklist is failing to be applied correctly. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to characteristic.readValue(). Used to know + what types of errors users are seeing. The results will be used to determine + how common these errors are and if we need to provide better error messages + to the users. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to characteristic.startNofications(). Used to + know what types of errors users are seeing. The results will be used to + determine how common these errors are and if we need to provide better error + messages to the users. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to characteristic.writeValue(). Used to know + what types of errors users are seeing. The results will be used to determine + how common these errors are and if we need to provide better error messages + to the users. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Counts how many times users interact with a regular chooser vs. an invalid + chooser. (A chooser is invalid when it's event handler becomes null.) + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of a device.gatt.connect() call. Used to understand what + errors developers are getting so we can target efforts toward the most + common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how long it takes for a connection attempt to fail. Use to let + developers know how to better wait for and handle connection errors. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how long it takes for a device to successfully connect. Use to let + developers know how long it should take to connect to a BLE device. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to descriptor.readValue(). Used to know what + types of errors users are seeing. The results will be used to determine how + common these errors are and if we need to provide better error messages to + the users. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to descriptor.writeValue(). Used to know what + types of errors users are seeing. The results will be used to determine how + common these errors are and if we need to provide better error messages to + the users. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the UUIDs used when getting a characteristic. The recorded value is + a 31-bit hash of the UUID. Used to know what types of characteristics to + target when building libraries that use the Web Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to getCharacteristic(). Used to understand + what errors developers are getting so we can target efforts toward the most + common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the UUIDs used when getting characteristics. The recorded value is a + 31-bit hash of the UUID. Used to know what types of characteristics to + target when building libraries that use the Web Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to getCharacteristics(). Used to understand + what errors developers are getting so we can target efforts toward the most + common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the UUIDs used when getting a descriptor. The recorded value is a + 31-bit hash of the UUID. Used to know what types of descriptors to target + when building libraries that use the Web Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to getDescriptor(). Used to understand what + errors developers are getting so we can target efforts toward the most + common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the UUIDs used when getting descriptors. The recorded value is a + 31-bit hash of the UUID. Used to know what types of descriptors to target + when building libraries that use the Web Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the outcome of a call to getDescriptors(). Used to understand what + errors developers are getting so we can target efforts toward the most + common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of a GATTServer.getPrimaryService() call. Used to + understand what errors developers are getting so we can target efforts + toward the most common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records what GATT Services are used when connected. The record value is a + 31-bit hash of the Service UUID. This will help us know if we should build + an API for specific services rather than a general Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of a GATTServer.getPrimaryServices() call. Used to + understand what errors developers are getting so we can target efforts + toward the most common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records what GATT Services are used when connected. The record value is a + 31-bit hash of the Service UUID. This will help us know if we should build + an API for specific services rather than a general Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many filters are used when scanning. These results will help us + better understand the uses of the API and make changes according to + developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records a 31-bit hash of the GATT Service UUIDs used when scanning. This + will help us know if we should build an API for specific services rather + than a general Bluetooth API. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many services are used in a filter. These results will help us + better understand the uses of the API and make changes according to + developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + juncai@chromium.org + + In the case of not accepting all devices, records the number of devices that + are in the chooser when a device is paired. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many optional services are used when scanning. These results + will help us better understand the uses of the API and make changes + according to developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records what optional services are used. The recorded value is a 31-bit hash + of the Service UUID. These results will help us better understand the uses + of the API and make changes according to developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the value of 'acceptAllDevices' in RequestDeviceOptions. These + results will help us better understand the uses of the API and make changes + according to developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of a navigator.bluetooth.requestDevice() call. Used to + understand what errors developers are getting so we can target efforts + toward the most common ones. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + juncai@chromium.org + + Raw RSSI values provided to chooser, before processing them for display in + the Web Bluetooth chooser. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + juncai@chromium.org + + Displayed RSSI levels, after processing and as displayed to users in the Web + Bluetooth chooser. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + juncai@chromium.org + + Records the duration scanning for devices is run, terminated by events such + as the chooser being closed with a selected device, cancelled, or the scan + duration timing out. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many services are used when scanning. This results will help us + better understand the uses of the API and make changes according to + developers' behavior. + + + + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records what services are used from either required or optional sets. The + recorded value is a 31-bit hash of the Service UUID. These results will help + us better understand the uses of the API and make changes according to + developers' behavior. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/browser/histograms.xml b/tools/metrics/histograms/histograms_xml/browser/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..b63d07d32a2c33179595d82e10039751200db736 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/browser/histograms.xml @@ -0,0 +1,799 @@ + + + + + + + + + + manukh@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + The time elapsed decoding an image using BitmapFetcher. + + + + manukh@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + The time elapsed fetching an image from a URL using BitmapFetcher. + + + + + lgrey@chromium.org + robliao@chromium.org + + Whether the user's system is in dark mode, light mode, or if this choice is + unavailable due to lack of system support. Updated every UMA upload. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the size of a compressed on-disk capture for the paint preview after + a proto is written to disk if compressed. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the number of frames captured by a paint preview if it succeeded. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records a boolean indicating whether a capture attempt was successful. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the total time spent capturing a paint preview of a page. This + includes capture and serialization of all frames and IPC time. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the size of an uncompressed on-disk capture for the paint preview + after a proto is written to disk if not compressed. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the compressed on-disk size of the capture if it succeeded for the + capture experiment. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the ratio of success to failure for the Paint Preview capture + experiment. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records if the paint preview compositor process started correctly. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the time it took to start the paint preview compositor process. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + Records when a link is clicked in the paint preview player. + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the time taken to from the request to start the compositor process + to the first bitmap being loaded. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the the reason for exiting the compositor process for the + TabbedPaintPreviewPlayer. Recorded when the compositor returns an error or + disconnects. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the the reason for exiting TabbedPaintPreviewPlayer. Recorded when + paint preview is removed. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records whether paint preview was drawn before the tab finished loading. + Recorded when tab has finished loading. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records whether a paint preview exists. Recorded when attempting to show a + preview on startup. This in conjuction with CompositorFailureReason gives + the total number of failures to show a paint preview. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the number of times that the upgrade snackbar was shown in a session + of TabbedPaintPreviewPlayer. Recorded when paint preview is removed. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the time taken to from actvity creation to the first bitmap being + shown. Recorded on first paint preview paint event. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the length of the time that a session of TabbedPaintPreviewPlayer + lasts. Recorded when paint preview is removed. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the total disk usage by the Paint Preview Tab Service at startup of + the profile keyed service. + + + + + gab@chromium.org + olivierli@chromium.org + + Similar to Browser.Responsiveness.IOJankyIntervalsPerMinute but sums janky + events across all foreground threads over the monitored minute rather than + considering each interval a boolean. This aims to cover a blind spot of + IOJankyIntervalsPerMinute as it cannot see an improvement where we unblock + 19/20 threads performing I/O. Not reported across system sleep. More details + @ https://bit.ly/chrome-io-jank-metric + + + + + gab@chromium.org + olivierli@chromium.org + + This metric is emitted every minute. It reports a number between 0 and 60 + which corresponds to the number of 1 second intervals during the monitored + minute to which a stalled foreground thread + ScopedBlockingCall(BlockingType::MAY_BLOCK) was attributed. A stalled call + is first attributed to the interval in which it began, and is attributed to + a number of intervals equal to the length of the call, rounded to the + nearest second. (Before http://crrev.com/c/2314873, the length was truncated + rather than rounded.) This aims to capture moments where the main thread is + responsive but the application is not (because things aren't loading). Not + reported across system sleep. More details @ + https://bit.ly/chrome-io-jank-metric + + + + + + + erikchen@chromium.org + tdresser@chromium.org + chrome-analysis-team@google.com + + This metric is emitted every 30 seconds [when there is user activity]. Each + 30 second duration is divided into 100ms intervals. This metric counts the + number of these intervals that were "janky". See + https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit + for more details. + + On desktop platforms, this metric measures native events, as well as tasks + posted to the UI and IO threads of the browser process. On Android, this + metric only measures tasks posted to the UI and IO threads. + + Update (October 27th 2019): The responsiveness::Watcher emitting this metric + previously started observation before the main message loop was running, + this resulted in the 99th percentile being mostly comprised of slow startups + (before the message loop gets to run). This was fixed and a fake-improvement + in the high percentiles is expected when the fix goes live. + + Update (M82 March 2020): Stopped recording background intervals on Android. + + Due to a bug, this metric does not measure long queueing time as jankiness. + It only measures jankiness as individual tasks taking a long time to run. + Given that it's a long-standing bug, this metric will not be modified. We + are testing a new metric + Browser.Responsiveness.JankyIntervalsPerThirtySeconds2 that correctly + accounts for queueing time. See + https://groups.google.com/a/google.com/forum/#!topic/chrome-scheduler/X32gKl6fW2A + for more details. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + erikchen@chromium.org + tdresser@chromium.org + fdoray@chromium.org + chrome-analysis-team@google.com + + This metric is emitted every 30 seconds after main message loop start, when + there is user activity. Each 30 second duration is divided into 100ms + intervals. This metric counts the number of these intervals that were + "janky". An interval is janky if during it the UI or IO thread + executes an "important" task that was queued more than 100 ms ago, + or a non-important task or a native event handler that started executing + more than 100 ms ago. See + https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit + for more details. + + Update (M82 March 2020): Stopped recording background intervals on Android. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + ejoe@google.com + jonross@chromium.org + + The time between input event timestamp for tab switch and when the + TabStripModel begins processing the switch. + + + + + sadrul@chromium.org + sky@chromium.org + + The time it takes for the browser to request a tab to be visible. Note that + this only measures the time from the browser deciding to make the tab + visible (after a click, or keyboard-shortcut to switch tabs), until the tab + is requested to become visible. The time it takes to actually make the tab + visible and show on screen is measured in a separate metric, in + RWH_TabSwitchPaintDuration. + + + + + + + fdoray@chromium.org + Whether a frame was presented after a tab switch event. + + + + + + fdoray@chromium.org + jonross@chromium.org + + The time between a tab switch input event timestamp and when the tab is + hidden, if no frame is presented in the meantime. + + + + + + + ejoe@google.com + jonross@chromium.org + + The time between the input event timestamp and the frame presentation time + on a tab switch. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Number of open guest windows at the same time. Recorded when a new guest + window is created. Please note that this metric double counts the lower + numbers, meaning that if user opens three windows (without closing any in + between), then buckets 1, 2, and 3 will all be incremented in turn. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Number of open incognito windows at the same time. Recorded when a new + incognito window is created. Please note that this metric double counts the + lower numbers, meaning that if user opens three windows (without closing any + in between), then buckets 1, 2, and 3 will all be incremented in turn. + + + + + dominickn@chromium.org + meacer@chromium.org + + Whether or not the user checked the option in the external protocol dialog + to remember their choice of opening or not opening the specified app. + Recorded each time the user interacts with the External Protocol Dialog, + when making a decision. + + + + + ericrobinson@chromium.org + johnidel@chromium.org + + Record the time spent in the background after RenderProcessHost + initialization of the process. Recorded when the RenderProcessHost for the + process is destroyed. + + + + + + + wfh@chromium.org + + Count of renderer process terminations due to a code integrity failure, + grouped by type. This is only reported on Windows. + + + + + wfh@chromium.org + Count of renderer process crashes grouped by type. + + + + wfh@chromium.org + Count of renderer process kills grouped by type. + + + + oshima@chromium.org + + Out of BrowserRenderProcessHost.ChildKills, numer of kills due to SIGKILL, + which is a strong signal of out of memory on Chrome OS, grouped by renderer + type. + + + + + + + wfh@chromium.org + + The launch error codes for failed renderer process launches. + + + + + + + wfh@chromium.org + Count of renderer process launch failures grouped by type. + + + + + + wfh@chromium.org + + Count of renderer process crashes that we miscounted because we took the + exit code too early. Grouped by type. + + + + + ericrobinson@chromium.org + csharrison@chromium.org + + Determines what combination of low and normal priority frames were attached + to a render process during its lifetime. Recorded when the host for the + render process is destroyed. + + + + + boliu@chromium.org + alexmos@chromium.org + + Recorded at most once per renderer process when it first becomes invisible + and has media stream. Record the frame depth of the process. Note this + metric is only meaningful when some form of OOPIF is enabled; otherwise + frame depth is always 0. + + + + + alexmos@chromium.org + lukasza@chromium.org + + Records what happens when an attempt is made to use a spare + RenderProcessHost - logs that either the attempt succeeded or why it failed. + + + + + ericrobinson@chromium.org + johnidel@chromium.org + + Record the lifetime of the RenderProcessHost after initialization of the + process. Recorded when the RenderProcessHost for the process is destroyed. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when we check whether a Trusted Web Activity client app can handle + Browsable Intents. It measures how long consulting the Android + PackageManager takes. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when any Android app is uninstalled or has its data cleared. This + measures how long it takes to read data from Preferences to determine + whether we need to act. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when an Android background service attempts to create a Tab. We + time how long the Android package manager queryIntentActivities call takes. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when a TrustedWebActivity is paused, recording the time since it + had been resumed. + + + + + peconn@chromium.org + peter@chromium.org + + The result of Digital Asset Link verification performed when starting a + Trusted Web Activity. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when Trusted Web Activity verification completes. Records how long + it takes the device to realise it is offline and fall back to the cached + result. + + + + + peconn@chromium.org + peter@chromium.org + + Triggered when Trusted Web Activity verification completes. Records how long + verification took when online. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records which browser the Legacy Browser Support feature is configured to + open (which defaults to IE). Recorded on browser startup, and when the value + changes. Only measured when Legacy Browser Support is enabled via the + BrowserSwitcher* policies. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records whether the "AppData/Local/Google/BrowserSwitcher" + directory was successfully created. Windows only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records whether a temp file in + "AppData/Local/Google/BrowserSwitcher" the directory was + successfully created. Windows only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records whether the temp file in + "AppData/Local/Google/BrowserSwitcher" directory was successfully + moved to its final destination ("cache.dat") after writing its + contents. Windows only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + On navigation and redirect, whether to switch browsers or not. Only measured + when Legacy Browser Support is enabled via the BrowserSwitcher* policies. + When this is true, Chrome attempts to launch an alternative browser + (typically IE) with the navigation URL. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + On navigation and redirect, records how long it took to compute a decision + (stay in Chrome/open in IE). Only measured when Legacy Browser Support is + enabled via the BrowserSwitcher* policies. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Number of rules that come from an external greylist XML file. Measured when + the sitelist is loaded during browser startup. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Number of rules that come from an external sitelist XML file. Measured when + the sitelist is loaded during browser startup. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Number of rules in the BrowserSwitcherUrlGreylist policy. Measured when the + policy is loaded. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Whether there is a wildcard ("*") rule in the + BrowserSwitcherUrlGreylist policy. Measured when the + BrowserSwitcherUrlGreylist policy gets updated. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Number of rules that come from Internet Explorer Enterprise Mode's sitelist. + Measured when the sitelist is loaded during browser startup. Windows only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records whether an attempt to launch an alternate browser failed or + succeeded. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Records how long it took to launch an alternate browser (regardless of + whether it failed or succeeded). Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Number of rules in the BrowserSwitcherUrlList policy. Measured when the + policy gets updated. Desktop Chrome only. + + + + + nicolaso@chromium.org + pastarmovj@chromium.org + + Whether there is a wildcard ("*") rule in the + BrowserSwitcherUrlList policy. Measured when the BrowserSwitcherUrlList + policy gets updated. Desktop Chrome only. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/chrome/histograms.xml b/tools/metrics/histograms/histograms_xml/chrome/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9ad152996054925c84a0a5f8dc413badeeff6628 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/chrome/histograms.xml @@ -0,0 +1,1325 @@ + + + + + + + + + + fdoray@chromium.org + gab@chromium.org + + Track set of Windows errors inside the meessage loop/pump system, where + system calls fail, and we try to gracefully recover. These errors should + really never happen, so we should be sure to look closer if they do. + + + + + gab@chromium.org + + The result of every rendez-vous reported once per browser process launch. + + + + + gab@chromium.org + aseren@yandex-team.ru + The reason of remote hang processes termination. + + + + gab@chromium.org + aseren@yandex-team.ru + + Used to send the result of interaction with remote process as histograms in + case when remote process influences on start. + + + + + gab@chromium.org + aseren@yandex-team.ru + + The error code of remote process termination on Posix in case when remote + process hung. + + + + + gab@chromium.org + aseren@yandex-team.ru + + The error code of remote process termination on Windows in case when remote + process hung. + + + + + gab@chromium.org + aseren@yandex-team.ru + + Time it takes from TerminateProcess call to the moment when we stop waiting + for remote process switches to signal state. + + + + + gab@chromium.org + aseren@yandex-team.ru + + The error code of wating for remote process termination on Windows. + + + + + gab@chromium.org + + Time it takes to grab the process singleton. Reported once per successful + attempt at obtaining the singleton. + + + + + gab@chromium.org + + Time it takes to return an error from the process singleton algorithm (nor + succeeding in obtaining it, nor in generating a rendez-vous). This does not + include time spent in the fast notification path (chrome_exe_main_win.cc). + + + + + gab@chromium.org + + Time it takes to find the process singleton owner and notify it. Reported + once per successful rendez-vous. This does not include time spent in the + fast notification path (chrome_exe_main_win.cc). + + + + + yichenz@chromium.org + chromeos-wmp@google.com + + Tracks the animation smoothness for the fade-in animation of tab hover card. + + + + + yichenz@chromium.org + chromeos-wmp@google.com + + Tracks the animation smoothness for the fade-out animation of tab hover + card. + + + + + yichenz@chromium.org + chromeos-wmp@google.com + + Tracks the animation smoothness of tab loading animation. A tracker starts + when the first tab loading animation starts and stops after the last one + stops for each browser window. The metric is emitted when the tracker stops. + + + + + gayane@chromium.org + yyushkina@chromium.org + + Records installed color id every time theme service is initialized from + prefs. Happens once per profile load. + + + + + chrisha@chromium.org + pmonette@chromium.org + + Records the NTSTATUS result that was returned when attempting to hook + NtMapViewOfSection during chrome_elf.dll initialization. Emitted + asynchronously shortly after startup. + + + + + chrisha@chromium.org + pmonette@chromium.org + + Records the number of attempts needed before third-party DLL blocking was + properly set up. This is logged immediately after a successful setup. Only + recorded on Windows. + + + + + chrisha@chromium.org + pmonette@chromium.org + + Records the successes and failures when running the third-party DLL blocking + setup code, taking into account the safety beacon. Used to determine how + often the third-party DLL blocking is disabled because it failed to + initialize properly twice in a row. Only recorded on Windows. + + + + + chrisha@chromium.org + pmonette@chromium.org + + Records the different status codes that are emitted by chrome_elf.dll while + initializing the NtMapViewOfSection hook used to blocked third-party DLLs. + Multiple status codes can be emitted per initialization since some of those + status codes represent non-fatal failures. E.g. Failure to clear the + previous failure codes. This also means that duplicates are possible. This + is recorded shortly after Chrome launches, since chrome_elf.dll doesn't have + access to the //base API. + + + + + lizeb@chromium.org + + For Custom Tabs generated by Chrome itself instead of external apps, this + shows the time between the intent arrival in the CCT and the first + navigation start. Recorded when the page has finished loading. + + + + + lizeb@chromium.org + + For Custom Tabs generated by Chrome itself instead of external apps, this + shows time between the intent arrival in the CCT and the first "page + loaded" event, if the navigation is successful. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Measures the model evaluation latency in the Chrome ML Service. This will be + recorded whenever a model evaluation call is invoked on a valid model, + regardless of whether the evaluation result is valid or not. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the model loading result status from the Chrome ML Service. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the decision model prediction result from the Chrome ML Service. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Measures the duration in which the Chrome ML Service is alive. This is + monitored by a service observer in the browser process, and should be + recorded correctly when the service exits either gracefully or unexpectedly. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + Records if the Chrome ML Service crashed. + + + + mcrouse@chromium.org + sophiechang@chromium.org + Records if the Chrome ML Service launched successfully. + + + + mcrouse@chromium.org + sophiechang@chromium.org + Records if the Chrome ML Service terminated normally. + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Whether the ML Service is already running when it is requested. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Measures the model validation latency in the Chrome ML Service. This is + recorded when the ML service receives a model and evaluates it, regardless + of whether the model turns out to be valid or not. + + + + + dominickn@chromium.org + melzhang@chromium.org + mxcai@chromium.org + + Records the response when the intent picker is shown to the user on Chrome + OS to allow them to open an external protocol in an app. + + + + + dominickn@chromium.org + melzhang@chromium.org + mxcai@chromium.org + + Records the response when users that are shown the intent picker accept + opening an external protocol in an app as well as whether the app is + persisted. + + + + + dominickn@chromium.org + melzhang@chromium.org + mxcai@chromium.org + + Records the response when users that are shown the intent picker reject + opening an external protocol in an app. + + + + + elijahtaylor@google.com + dominickn@chromium.org + shihuis@google.com + + Records the response when the intent picker is shown to the user on Chrome + OS to allow them to open a URL in an app. + + + + + elijahtaylor@google.com + dominickn@chromium.org + shihuis@google.com + + Records the app platform chosen (or Chrome if the user did not choose an + app) when the intent picker is shown to the user on Chrome OS. The + destination may be specified due to the user explicit selection or a + previously stored preference. + + + + + dominickn@chromium.org + nancylingwang@chromium.org + + Records whether a notification matches multiple apps, when there is one or + multiple web apps matching a web page nonpersistent notification. + + + + + ajlinker@chromium.org + dominickn@chromium.org + mxcai@chromium.org + + Records the type of app sending a link to the browser to be opened. + + + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the resolution of output stream that is configured by Chrome OS + camera service. + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the process time of ConfigureStreams() method in Chrome OS camera + service. + + This metric is reported for all users and will not cause abnormal + distribution since the metric is Chrome OS specified. + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the type of the error which triggers the Notify() method in Chrome + OS camera service. + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the camera facing of the camera session in Chrome OS camera service. + + + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the process time of the JDA (Jpeg Decode Accelerator) or JEA (Jpeg + Encode Accelerator) run on Chrome OS camera service. There are suffixes that + record the runner method (hardware/software), the runner type + (decode/encode). + + This metric is reported for all users and will not cause abnormal + distribution since the metric is Chrome OS specified. + + + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the resolution of the image that JDA/JEA process by Chrome OS camera + service. The resolution represents by the total pixels contained in the + image. There are suffixes that record the runner method (hardware/software), + the runner type (decode/encode). + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + + Records the process time of OpenDevice() method in Chrome OS camera service. + + This metric is reported for all users and will not cause abnormal + distribution since the metric is Chrome OS specified. + + + + + wtlee@chromium.org + chromeos-camera-eng@google.com + Records the session duration in Chrome OS camera service. + + + + miersh@google.com + pmarko@chromium.org + + The amount of time it took to sign one CSR by certificate provisioning + worker. + + + + + miersh@google.com + pmarko@chromium.org + + Number of times each event is reached during certificate provisioning flow. + + + + + miersh@google.com + pmarko@chromium.org + + The amount of time it took to generate one key pair by certificate + provisioning worker. + + + + + miersh@google.com + pmarko@chromium.org + + For final states (see the list in cert_provisioning::IsFinalState): number + of times certificate provisioning worker finished on every state. For other + states: number of times the worker failed on every state. + + + + + miersh@google.com + pmarko@chromium.org + + The amount of time it took to build one Verified Access response by + certificate provisioning worker. + + + + + aalexand@google.com + gmx@chromium.org + + A count of successes and various failure modes related to collecting and + processing profile data obtained via "perf events" on Chrome OS. + + + + + aalexand@google.com + cwp-team@google.com + + Record the collection status (success or failure) when the Chrome process + and thread types are collected as part of the ChromeOS perf profile + collection. + + + + + cywang@chromium.org + chinglinyu@chromium.org + + Records the status of collection attempts triggered by jankiness on Chrome + OS. + + + + + gmx@chromium.org + cwp-team@google.com + + A count of successes and various failure modes related to the parsing of + logical CPU frequencies on Chrome OS. Recorded when the browser process + starts. + + + + + aalexand@google.com + gmx@chromium.org + + Records the number of "perf events" reports included in an UMA + upload on Chrome OS. + + + + + tobyhuang@chromium.org + cros-families-eng@google.com + + Categorizes the current user for the Family Experiences team's metrics. A + Supervised User has a supervised primary account and no secondary accounts. + A Supervised Student has a supervised primary account and one or more K-12 + EDU secondary accounts, which is the only available option for a secondary + account in that scenario. A Student at Home has a K-12 EDU primary account + on an unmanaged ChromeOS device, regardless of the secondary account. Other + is for all other users that do not fall into any of the above categories. + + + + + wjmaclean@chromium.org + + Whether the GAIA Authenticator unexpectedly encountered a null contentWindow + value while handling WebView's onContentLoad event. This metric is only + enabled for AuthMode = DEFAULT, which indicates ChromeOS online login. This + is the only mode where the issue has been observed. Other modes not captured + here are OFFLINE (offline ChromeOS login) and DESKTOP (for online GAIA login + on desktop Chrome). + + + + + + + itspeter@chromium.org + stimim@chromium.org + chromeos-hw-checker@google.com + + Qualification status of each component types. This entry is generated by + hardware_verifier.conf at boot time. + + + + + itspeter@chromium.org + stimim@chromium.org + chromeos-hw-checker@google.com + Aggregated result of hardware verifier check. + + + + itspeter@chromium.org + stimim@chromium.org + chromeos-hw-checker@google.com + + The amount of time it takes to finish one hardware verification run. + + + + + itspeter@chromium.org + stimim@chromium.org + chromeos-hw-checker@google.com + The amount of time it takes to probe hardware components. + + + + + + jamescook@chromium.org + lacros-team@google.com + + Recorded as part of the metrics session data to identify the lacros-chrome + browser binary. + + + + + zeuthen@chromium.org + + The number of seconds of uptime since the last time the Chrome OS machine-id + was regenerated. This is reported every time the machine-id is regenerated + except for the first time since reboot. + + + + + zeuthen@chromium.org + + The reason why the Chrome OS machine-id was regenerated. This is reported + when the machine-id is re-generated. + + + + + xdai@chromium.org + + The memory pressure level in Chrome OS, which is recorded periodically (once + per second). This is used to show the relative frequency of the system being + in a critical vs relaxed memory pressure state. + + + + + yoshiki@chromium.org + omrilio@chromium.org + + The cause of the scroll event by the user on the message center. Only the + first event after the message center opens is recorded. For example, the + user opens the message center and scrolls by mouse then by key, only the + mouse event is recorded. If the user closes and reopens the message center + before the second event, both events are recorded. + + + + + omorsi@google.com + mgawad@google.com + + Tracks the final result of performing {Operation} operation on an {KeyType} + key in PlatformKeysService. + + + + + + + + + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + Whether platform verification subsystem features are available at the time a + platform verification request is made for content protection on Chrome OS. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The result of a platform verification attempt for content protection on + Chrome OS. + + + + + tengs@chromium.org + gzadina@google.com + + Record when the user toggles the integrated privacy screen on/off. See the + PrivacyScreenToggleUISurface enum for all UI surfaces for toggling the + feature. + + + + + mslus@chromium.org + emaxx@chromium.org + + Records every online login authenticated purely with GAIA or with SAML. + + + + + mslus@chromium.org + rsorokin@chromium.org + + Records how often users are guided through the SAML in-session password + change flow, and how often it is completed succesfully. + + + + + mslus@chromium.org + mohammedabdon@chromium.org + Records SAML provider when SAML login flow is used. + + + + miersh@google.com + pmarko@chromium.org + + Tracks results of calculating response for a challenge from Verified Access + server for remove attestation during SAML authentication. + + + + + mslus@chromium.org + emaxx@chromium.org + + The number of passwords that were scraped during a Chrome OS login via SAML. + This is set only when the Chrome Credentials Passing API is not used. + + + + + bartfab@chromium.org + + Whether one of the scraped passwords was successfully verified as the user's + password. This is set only when the Chrome Credentials Passing API is not + used. + + + + + khorimoto@chromium.org + cros-customization@google.com + + The amount of time between when the settings window becomes blurred and when + the user focuses it again. + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users interact with an element in the Chrome OS's Languages + browser settings page. + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users check/uncheck "Offer to translate pages in this + language" checkbox. + + + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users interact with a toggle in the Chrome OS's Languages + browser settings page. + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users interact with different element in the Chrome OS's + Languages OS settings page. + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users check/uncheck "Offer to translate pages in this + language" checkbox in OS Settings + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users visit a language settings support page for Chrome OS. + + + + + + + myy@chromium.org + essential-inputs-team@google.com + + Records when users interact with a toggle in the Chrome OS's Languages OS + settings page. + + + + + jamescook@chromium.org + cros-system-services@google.com + + The amount of time between the render frame host StartProvisionalLoad event + and the render frame DocumentOnLoadCompleted event for the Chrome OS + settings page. + + + + + jamescook@chromium.org + cros-system-services@google.com + + The amount of time between the render frame host StartProvisionalLoad and + DidFinishDocumentLoad events for the Chrome OS settings page. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The number of characters for queries used to fetch results from the Settings + Search Mojo API. + + + + + + + khorimoto@chromium.org + cros-customization@google.com + The number of clicks before changing a setting. + + + + + + khorimoto@chromium.org + cros-customization@google.com + The number of navigations before changing a setting. + + + + + + khorimoto@chromium.org + cros-customization@google.com + The number of searches before changing a setting. + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The number of search results fetched each time a successful search request + is made to the Settings Search Mojo API. + + + + + jamescook@chromium.org + cros-system-services@google.com + + Records whether the "try your Chrome OS settings" banner was shown + when the user opened a new Chrome browser settings tab and also records + interactions with the banner. + + + + + khorimoto@chromium.org + cros-customization@google.com + + Paths visited within chrome://os-settings. For evaluating popularity and + priorities for OS Settings UI. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The time fetching search results from the Settings Search Mojo API. Recorded + when getSearchHandler().search() completes. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The number of search requests made to the Settings Search Mojo API. For + search requests that succeeded with a response, the number of search + requests that had results which were discarded, and the number of search + requests that were shown to the user. Recorded when + getSearchHandler().search() completes. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The number of search requests made to the Settings Search Mojo API in one + session of the settings app. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + Section search results clicked by user in the OS settings search box. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + Setting search results clicked by user in the OS settings search box. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + Subpage search results clicked by user in the OS settings search box. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + Type of search results clicked by user in the OS settings search box. + + + + + + + khorimoto@chromium.org + cros-customization@google.com + + The time spent on the settings page before changing a setting. + + + + + khorimoto@chromium.org + hsuregan@chromium.org + cros-customization@google.com + + The user action taken when search results exist and are displayed. + + + + + khorimoto@chromium.org + cros-customization@google.com + + The amount of time between when a Chrome OS settings window is opened and + when it is closed. + + + + + dominickn@chromium.org + melzhang@chromium.org + + Records number of apps found for a given intent in the Sharesheet. + + + + + dominickn@chromium.org + melzhang@chromium.org + Records user action on sharesheet invocations. + + + + jamescook@chromium.org + cros-customization@google.com + + Tracks whether browser sync preferences were migrated to the new OS sync + feature (project SplitSettingsSync). Recorded once per session during login. + + + + + + + amehfooz@chromium.org + tengs@chromium.org + + Tracks the animation smoothness for the collapse / expand animation of the + system tray. + + + + + tengs@chromium.org + gzadina@google.com + + Tracks the number of blocked notifiers in the system tray after the user + blocks one or multiple notifiers. Note that this metric records the number + of blocked notifiers *after* the update. + + + + + tengs@chromium.org + gzadina@google.com + + Tracks the number of blocked notifiers in the system tray when it is opened. + + + + + tengs@chromium.org + amehfooz@chromium.org + + The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.) + in the system tray quick settings when it is opened, including pods that + overflow to other pages. See + ChromeOS.SystemTray.Tablet.FeaturePodCountOnOpen for the corresponding + histogram logged in tablet mode. + + + + + tengs@chromium.org + gzadina@google.com + + Records the first interaction the user has with the system tray, which can + be a click/tap on the quick settings or message center bubble. Note that + this interaction could be at any time after the user opens the tray (e.g. 30 + seconds later before the first click). + + + + + tengs@chromium.org + gzadina@google.com + + An enum value how system tray bubble is interacted e.g. by tap (touch + screen), or click (mouse, trackpad, etc.) Reported every time the region + inside system tray bubble is tapped or clicked. + + + + + tengs@chromium.org + gzadina@google.com + + If the value is true, SystemTray is expanded when it's opened. Otherwise, + it's closed when it's opened. + + + + + tengs@chromium.org + gzadina@google.com + + Records the number of notifications that are removed in a single clear all + action by the user. + + + + + yamaguchi@chromium.org + + Type of the support page which user opened by clicking the indicator of + managed device type in the unified system tray bubble. + + + + + tengs@chromium.org + gzadina@google.com + + The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in + the shelf status area whenever a pod appears/disappears. This histogram is + only logged when the device is not in tablet mode, otherwise + ChromeOS.SystemTray.Tablet.ShelfPodCount is logged. + + + + + tengs@chromium.org + amehfooz@chromium.org + + The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.) + in the system tray quick settings when it is opened, including pods that + overflow to other pages. This histogram is only logged when the device is in + tablet mode, otherwise ChromeOS.SystemTray.FeaturePodCountOnOpen is logged. + + + + + tengs@chromium.org + gzadina@google.com + + The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in + the shelf status area whenever a pod appears/disappears. This histogram is + only logged when the device is in tablet mode, otherwise + ChromeOS.SystemTray.ShelfPodCount is logged. + + + + + tengs@chromium.org + gzadina@google.com + + The amount of time a user took from clicking on the button in status area, + to clicking on an item in the system tray bubble. + + + + + tengs@chromium.org + gzadina@google.com + + An enum value how system tray bubble is expanded or collapsed. It can be + toggled by the button and touch gesture. + + + + + jorgelo@chromium.org + tnagel@chromium.org + + The number of files with URL extended attributes found in the users' home + directories. This is emitted once per boot. See crbug.com/919486 and + crbug.com/939386 for more details. + + + + + allenwebb@chromium.org + jorgelo@chromium.org + mnissler@chromium.org + Timing and number of USB devices attached. + + + + rsorokin@chromium.org + tellier@google.com + cros-oac@google.com + + The time spent before the web UI vesion of the multiprofile account picker + is ready. + + + + + tellier@google.com + rsorokin@chromium.org + cros-oac@google.com + + The time spent before the views-based version of the multiprofile account + picker is ready. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/cloud/histograms.xml b/tools/metrics/histograms/histograms_xml/cloud/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..ac6b2c2547d7df91563a7c203634c1ed9185429f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/cloud/histograms.xml @@ -0,0 +1,156 @@ + + + + + + + + + + thestig@chromium.org + Event counts in CloudPrintAuth. + + + + thestig@chromium.org + The number of printers available for registration. + + + + thestig@chromium.org + + The number of printers available for registration in Windows Service. + + + + + thestig@chromium.org + Event counts in PrinterJobHandler. + + + + thestig@chromium.org + The number of jobs successfully completed per hour. + + + + thestig@chromium.org + The number of jobs started per hour. + + + + thestig@chromium.org + Then number of job completion statuses. + + + + thestig@chromium.org + Event counts in PrintSystem. + + + + thestig@chromium.org + The amount of time needed to prepare job for spooling. + + + + thestig@chromium.org + The number of printers user has blacklisted. + + + + thestig@chromium.org + The number of printers user has whitelisted. + + + + thestig@chromium.org + The amount of time needed to finish print job. + + + + thestig@chromium.org + Event counts in ServiceProcessControl. + + + + thestig@chromium.org + Event counts in ServiceUtilityProcessHost. + + + + thestig@chromium.org + The amount of time needed to spool print job. + + + + thestig@chromium.org + The number of printers to unregister. + + + + thestig@chromium.org + The amount of data downloaded on cloud print request. + + + + thestig@chromium.org + The amount of time needed for cloud print request. + + + + thestig@chromium.org + Request counts to cloud print service. + + + + thestig@chromium.org + The number of retries used to complete cloud print request. + + + + thestig@chromium.org + The amount of data uploaded with cloud print request. + + + + thestig@chromium.org + Number of tries before successful ping. 99 means giving up. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/compositing/histograms.xml b/tools/metrics/histograms/histograms_xml/compositing/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..608174b484d013a97f68e20af20f83634f7e5803 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/compositing/histograms.xml @@ -0,0 +1,597 @@ + + + + + + + + + + flackr@chromium.org + animations-dev@chromium.org + + Time spent finding the closest matching layer to a given point whenever we + do hit testing on LayerTreeImpl (in a browser process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + schenney@chromium.org + animations-dev@chromium.org + + Time spent updating layers, in microseconds. Recorded when layers are + updated (in a browser process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Time spent updating layer draw properties, in microseconds. Recorded when a + LayerTreeImpl's draw properties are updated (in a browser process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of layers in the active tree for each compositor frame. This is + logged once per frame, before the frame is drawn (in a browser process). + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of PictureLayers in the active tree for each compositor frame. + This is logged once per frame, before the frame is drawn (in a browser + process). + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of render surfaces in the render surface layer list. Recorded + each time the render surface layer list is constructed (in a browser + process). + + + + + kylechar@chromium.org + sadrul@chromium.org + + Recorded for each OnBeginFrame() message that could potentially be sent to a + CompositorFrameSinkClient. The value indicates if the message was sent to + the client and why it was/wasn't sent. + + + + + wychen@chromium.org + + The turn around time taken for the async readback of pixels is measured + here. This should be marked as obsolete once some tests no longer rely on + this histogram. See crbug/1110961 for more details. + + + + + weiliangc@chromium.org + + Time spent drawing of composited layers by GLRenderer, in microseconds. This + is logged once per frame, when a frame should be drawn. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vasilyt@chromium.org + backer@chromium.org + + The area of the display damage that was added to current frame damage after + all adjustments, including FrameBufferDamage from buffer queue and render + pass filters. + + This metric is reported once per frame only on platforms/devices that + support partial swap and does not include "empty swap" (no frame + damage) case. + + + + + vasilyt@chromium.org + backer@chromium.org + + The area of the display that was damaged since previous draw to this frame + buffer. + + This metric is reported once per frame only on platforms/devices that + support partial swap and does not include "empty swap" (no frame + damage) case. + + + + + vasilyt@chromium.org + backer@chromium.org + + The area of the display that was damaged in current frame. + + This metric is reported only on platforms/devices that support partial swap + and does not include "empty swap" (no frame damage) case. + + + + + vasilyt@chromium.org + backer@chromium.org + + The total area of the display that will be redrawn this frame. + + This metric is reported only on platforms/devices that support partial swap + and does not include "empty swap" (no frame damage) case. + + + + + weiliangc@chromium.org + + Time spent drawing of composited layers by SoftwareRenderer, in + microseconds. This is logged once per frame, when a frame should be drawn. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + penghuang@chromium.org + backer@chromium.org + + Time spent drawing of composited layers by SkiaRenderer with Vulkan backend, + in microseconds. This is logged once per frame, when a frame should be + drawn. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yiyix@chromium.org + chromeos-gfx@chromium.org + + Time spent to remove invisible quads from the quad_list in CompositorFrame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yiyix@chromium.org + + It records the total drawing area skipped to show on screen as a result of + applying draw occlusion. This is logged once per frame, when the frame is + drawn. + + + + + yiyix@chromium.org + + It records the percentage of total area drawing skipped by draw occlusion of + the total area of damage rects in a compositor frame. This is logged once + per frame, when the frame is drawn. + + + + + backer@chromium.org + rjkroege@chromium.org + + This is logged once per frame, if the output surface provides timing + information. It measures the time from the display compositor starting a + draw on the Viz Compositor thread to issuing all related draw calls to the + driver on the Gpu Main thread. Only reported for platforms supporting high + resolution clocks. + + + + + samans@chromium.org + rjkroege@chromium.org + + Indicates whether DrmOverlayManager was able to find the overlay + configuration in its cache. Recorded when DrmOverlayManager is asked to + verify an overlay configuration. + + + + + samans@chromium.org + rjkroege@chromium.org + + The amount of memory allocated for the purpose of performing a pageflip + test. Recorded every time DRM thread is asked to validate an overlay + configuration. + + + + + backer@chromium.org + rjkroege@chromium.org + + This is logged once per frame. It is the number of renderer passes after + flattening all possible render passes. If the value is more than one, then + an intermediate rendering target must be used during the rendering of the + frame for each render pass greater than one. + + + + + samans@chromium.org + rjkroege@chromium.org + + Indicates whether the OverlayCandidate passed to + OverlayCandidateValidatorOzone is backed by a SharedImage (as opposed to a + legacy mailbox). Recorded for every candidate in every overlay configuration + passed to OverlayProcessorOzone. + + + + + samans@chromium.org + rjkroege@chromium.org + + Indicates whether the SharedImage corresponding to the OverlayCandidate was + found. Reported for every OverlayCandidate that is backed by a SharedImage. + + + + + vasilyt@chromium.org + backer@chromium.org + + This is logged once per frame, if the output surface provides timing + information. It measures delta between the time when display compositor + scheduled first draw task for the current frame on Viz Compositor thread and + the time when Gpu Thread started processing it. Only reported for platforms + supporting high resolution clocks. + + + + + ccameron@chromium.org + + The outcome of attempting to replace all renderer tiles with CALayers. + Either success, or the first reason why a DrawQuad couldn't be replaced by a + CALayer. + + + + + pdr@chromium.org + paint-dev@chromium.org + + The GPU memory allocated for tilings (in a renderer process), summed over + all picture layers. Emitted once per drawing. Nothing is recorded if there + are no picture layers. + + Tilings are used for decomposition of the layer's entire contents at a + picture screenspace resolution to do threaded rasterization. + + + + + flackr@chromium.org + animations-dev@chromium.org + + Time spent finding the closest matching layer to a given point whenever we + do hit testing on LayerTreeImpl (in a renderer process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + chrishtr@chromium.org + paint-dev@chromium.org + + Records whether layer draw properties updates were skipped due to the layer + being back-facing and not being double-sided, but were otherwise going to be + updated. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Time spent updating layers, in microseconds. Recorded when layers are + updated (in a renderer process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Time spent updating layer draw properties, in microseconds. Recorded when a + LayerTreeImpl's draw properties are updated (in a renderer process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + chrishtr@chromium.org + paint-dev@chromium.org + + Records whether a layer update was skipped due to the layer being + back-facing and not being double-sided, but was otherwise going to be + updated. + + + + + wangxianzhu@chromium.org + paint-dev@chromium.org + + Records the approximate kilo-pixels covered by text drawing operations by + LCD-text disallowed reasons. Hence the histogram value for each reason is + the approximate number of non-LCD kilo-pixels resulting from that reason. + Recorded when the renderer is idle, at minimum interval of the longer of 1 + minute and 500 begin frames for each local frame tree. + + + + + wangxianzhu@chromium.org + paint-dev@chromium.org + + Records the number of layers containing text by LCD-text disallowed reasons. + Recorded along with Compositing.Renderer.LCDTextDisallowedReasonKPixels. + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of layers in the active tree for each compositor frame. This is + logged once per frame, before the frame is drawn (in a renderer process). + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of PictureLayers in the active tree for each compositor frame. + This is logged once per frame, before the frame is drawn (in a renderer + process). + + + + + schenney@chromium.org + paint-dev@chromium.org + + The number of render surfaces in the render surface layer list. Recorded + each time the render surface layer list is constructed (in a renderer + process). + + + + + weiliangc@chromium.org + + Checkerboarded area, in number of pixels, that has recording but does not + have time to finish rastering yet. A sample is recorded everytime a frame is + drawn while a scroll is in progress. Tracking bug 535732. + + + + + weiliangc@chromium.org + + Checkerboarded area, in number of pixels, that has no recording to raster + from. A sample is recorded everytime a frame is drawn while a scroll is in + progress. Tracking bug 535732. + + + + + weiliangc@chromium.org + + Keeps track of number of incomplete tiles in a drawn compositor frame while + scrolling. This is a rough measurement of ugliness during user interaction. + Incomplete tiles are non ideal scaled. A sample is recorded everytime a + frame is drawn while a scroll is in progress. Tracking bug 381695. + + + + + weiliangc@chromium.org + + Keeps track of number of missing tiles in a drawn compositor frame while + scrolling. This is a rough measurement of ugliness during user interaction. + Incomplete tiles are checkerboard or solid color. A sample is recorded + everytime a frame is drawn while a scroll is in progress. Tracking bug + 381695. + + + + + sunnyps@chromium.org + graphics-dev@chromium.org + + Size of the in-use portion of the ResourcePool for CC layer tree. Recorded + each time resources are reclaimed after tile work completes. + + + + + weiliangc@chromium.org + + Time spent aggregating compositor frames from different surfaces in + microseconds. This is logged once per frame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vikassoni@chromium.org + khushalsagar@chromium.org + + Whether an aggregated frame contains video or not. This metric will be used + to analyze the percentage of displayed frame with video. This metric will be + extended in future to specify whether the video is inline or fullscreen. + + + + + jonross@chromium.org + kylechar@chromium.org + + The amount of time it took for a Surface with unresolved dependencies to + activate. Note that some activations may be triggered due to a deadline + hitting. That is tracked in the DeadlineHit histogram. + + + + + jonross@chromium.org + kylechar@chromium.org + + Tracks the number of alive surfaces after each garbage collection operation. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/content/histograms.xml b/tools/metrics/histograms/histograms_xml/content/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..c8e6fc8e894f57e7676e4c8e8046266406a1ab27 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/content/histograms.xml @@ -0,0 +1,1351 @@ + + + + + + + + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + + The time between a change in content and when the new capture is sent to the + browser process. + +
+ A specific content change is hard to track. This is roughly calculated as + the interval from the first content change after a prior capturing content + to the first content being sent after the next capture of content. +
+ + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + + The time taken to capture the on-screen content. + + Note that this metrics is only recorded on clients on which a + high-resolution clock is available. + + + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + + The time taken to get the bounding box of the batch of captured content. + + Note that this metrics is only recorded on clients on which a + high-resolution clock is available. + + + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + + The time taken to send the content to the browser process in batch. + + Note that this metrics is only recorded on clients on which a + high-resolution clock is available. + + + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + The total number of content captures sent for a document. + + + + michaelbai@chromium.org + src/third_party/blink/renderer/core/content_capture/OWNERS + + The time taken for the task to start after it's scheduled. + + Note: The time of task that was scheduled for the retry wasn't measured + because it is always 500ms. + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + Records the category of the content when registered. + + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + + Records the status of dispatching the `contentdelete` event in every phase + of dispatch. + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + Records the category of the entry clicked on by a user. + + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + Records the result of the database operation. + + + + rayankans@chromium.org + platform-capabilities@chromium.org + + Records how many entries were found when loaded by the browser. + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + + Records the category of an attempted registration that was blocked. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default autoplay setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default cookies setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + The default permission setting for idle detection at profile open. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default image setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default JavaScript setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default location setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default camera setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default microphone setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + The default MIDI permission setting on sysex (system exclusive) messages at + profile open. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default notification setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default plugins setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default popups setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default sound setting at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default subresource filter setting at profile open + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + The default permission setting for WebUSB at profile open. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + The default permission setting for Web Bluetooth at profile open. + + + + + engedy@chromium.org + + Records the number of times Flash permission is granted for a host. + + + + + + + lshang@chromium.org + dullweber@chromium.org + engedy@chromium.org + + The number of user defined content setting exceptions at browser start. + Suffixed with the name of content setting types. + + + + + alexmos@chromium.org + engedy@chromium.org + + Records the schemes of content setting exceptions at browser start. Each + exception provides one sample. + + + + + alexmos@chromium.org + engedy@chromium.org + + Records how often a content settings exception for the file: scheme has a + non-empty path. Recorded once per exception at browser start. + + + + + alexmos@chromium.org + engedy@chromium.org + + Count of how often a specific content type has a content settings exception + defined for a file: scheme with no path (i.e., wildcard path). Recorded once + per exception at browser start. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + alexmos@chromium.org + engedy@chromium.org + + Count of how often a specific content type has a content settings exception + defined for a file: scheme with a valid, non-empty path. Recorded once per + exception at browser start. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + raymes@chromium.org + + Count of how often a specific content setting is set for an embedded URL by + an extension. Only counts settings when the secondary pattern is different + to the primary pattern. Exactly one of this or + ContentSettings.ExtensionNonEmbeddedSettingSet will be emitted per call to + contentSettings.set(), if the arguments to the call are valid. + + + + + raymes@chromium.org + + Count of how often a specific content setting is set when only a single + pattern is specified. Exactly one of this or + ContentSettings.ExtensionEmbeddedSettingSet will be emitted per call to + contentSettings.set(), if the arguments to the call are valid. + + + + + calamity@chromium.org + src/chrome/browser/ui/page_action/OWNERS + + Counts which content setting buttons are pressed by the user. + + + + + battre@chromium.org + + The number of user defined hostname patterns for content settings at browser + start. + + + + + dominickn@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Number of times a given permission was requested by a website and the user + has the permission set to prompt (i.e. not blocked or allowed). + + Note this is probably not the metric you want - it does not correspond to + the total number of times websites request a permission. Also, because + specific permissions have code that can automatically block or grant + permissions based on things like incognito, installed extensions etc., this + does also not correspond to the number of times users are prompted to allow + permissions. + + For a better metric to track how often users are prompted, either use + ContentSettings.PermissionsActions*, or Permissions.Prompt.*. + + See https://crbug.com/638076 for more details. + + + + + dominickn@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Number of times a given permission was requested by an insecure origin and + the user has the permission set to prompt (i.e. not blocked or allowed). + + Note this is probably not the metric you want - it does not correspond to + the total number of times websites request a permission. Also, because + specific permissions have code that can automatically block or grant + permissions based on things like incognito, installed extensions etc., this + does also not correspond to the number of times users are prompted to allow + permissions. + + For a better metric to track how often users are prompted, use + ContentSettings.PermissionsActions*. + + See https://crbug.com/638076 for more details. + + + + + dominickn@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Number of times a given permission was requested by a secure origin and the + user has the permission set to prompt (i.e. not blocked or allowed). + + Note this is probably not the metric you want - it does not correspond to + the total number of times websites request a permission. Also, because + specific permissions have code that can automatically block or grant + permissions based on things like incognito, installed extensions etc., this + does also not correspond to the number of times users are prompted to allow + permissions. + + For a better metric to track how often users are prompted, use + ContentSettings.PermissionsActions*. + + See https://crbug.com/638076 for more details. + + + + + tommycli@chromium.org + + Tracks whether the plugin content blocked puzzle piece was shown in the + Omnibox, and how the user interacted with it. + + + + + charleszhao@chromium.org + + Tracks whether the popup content blocked puzzle piece was shown in the + Omnibox, and how the user interacted with it. + + + + + csharrison@chromium.org + + Counts of various events related to the popup blocker. Including blocked + popups and overridden (clicked through) popups. This is similar to the + ContentSettings.Popups but is at the per-popup layer rather than at the UI + layer. + + + + + csharrison@chromium.org + + The blocked popup list contains a list of links that Chrome has blocked via + the popup blocker. If a user clicks on the link, the popup is opened. This + metric records the position of the popup in the list that a user clicks + through. Currently it should only be recorded on desktop platforms, because + the mobile UI for popup blocking does not currently allow for specific + exceptions. + + + + + csharrison@chromium.org + + Measures the total duration a popup WebContents is visible / foregrounded, + until it is closed. + + + + + csharrison@chromium.org + + Measures the total duration a popup WebContents is visible / foregrounded, + until it is closed via some user gesture (like Ctrl-W). + + + + + csharrison@chromium.org + + Measures the total duration a popup WebContents is visible / foregrounded + for the duration of its first document load. This time is measured from the + first navigation commit to the time either the WebContents is destroyed or + when a new navigation commits. + + + + + csharrison@chromium.org + + The total number of popups blocked by the strong blocker for a given page + load. Logged when the page is navigated away from, or the tab is closed. + Only logged for pages which are triggered for strong popup blocking, aka + abusive experience enforcement. + + + + + csharrison@chromium.org + + Counts of various events related to the strong popup blocker (aka abusive + experience enforcement), that is triggered via safe browsing. + + + + + rogerm@chromium.org + feed@chromium.org + + Whether the feed was fetched with activity logging enabled. This is logged + on every feed fetch. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: count of app lifecycle events reported to the Feed library. + Recorded as these events occur; e.g. when Chrome is foregrounded, + backgrounded, or the user clears cached browsing data. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: number of rows present in a history deletion that's causing all + current suggestions to be deleted. Each row should correspond to a url that + is beign removed from history. Is not emitted when entire history is being + cleared. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + When an article on the NTP is opened by the user, records whether it is + available offline. When an article is available offline, it will have an + offline badge in the UI on the NTP. Opening the article occurs when the user + navigates from the NTP to the article itself, which can be either in the + current tab or a new tab. Note that this is independent of whether the + article is actually opened as an offline page or not. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Records whether an article on the NTP that is shown to the user was also + available offline. When an article is available offline, it will have an + offline badge in the UI. The initial offline status of the article is used + for this metric. While it is possible for the offline status to change while + the article is on screen, this metric will not be re-emitted. The criteria + for an article to be "shown" is for 2/3 of its vertical height to + be on screen for any amount of time. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Tracks the number of operations in a Feed mutation when database receive the + commit request. + + + + + + + vincb@google.com + feed@chromium.org + src/chrome/browser/android/feed/OWNERS + Actions related to the feed controls. + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Tracks the number of entries for the Feed storage after database perform get + all keys request. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The display status of the content suggestions when users open NTPs. + Whether content suggestions are disabled by policy (e.g. enterprise or + supervised users), enabled but collapsed, or enabled and expanded when a new + NTP is created. + + + + + petewil@chromium.org + harringtond@chromium.org + feed@chromium.org + + Tracks each instance of user engagement with the feed, by scrolling or + interacting with a card (opening the URL or using the menu). Note that each + event type reports samples very differently and buckets can't be directly + compared. We're mostly interested in unique user counts. We track every + interaction, and we report ENGAGED and ENGAGED_SIMPLE once per user visit. A + user visit is when the user scrolls or interacts with the NTP more than 5 + minutes after the previous visit. The SCROLLED engagement type represents a + single instance of the user scrolling, and is reported once per Feed visit. + The INTERACTED engagement type represents one instance of using the menu or + opening a feed article into its own tab. SCROLLED and INTERACTED are + reported for every occurrence, thus we could end up with more scrolled and + interected than ENGAGED or ENGAGED_SIMPLE samples. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The type of spinner when the content suggestion shows the loading + spinner. This is tracked based on if the spinner is shown, not how long it + is visible. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: How long the content suggestion loading spinner is shown when a + loading spinner finishes showing. This is tracked based on when the spinner + is enabled in the UI, not how long it is actually visible on screen. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: How long the content suggestion loading spinner is shown when a + spinner is destroyed without completing. This is tracked based on when the + spinner is enabled in the UI, not how long it is actually visible on screen. + + + + + harringtond@chromium.org + feed@chromium.org + + Android: Status of image fetches for the feed. Recorded for each image + fetch. Fetches happen when loading the feed or scrolling the feed. Fetched + images are cached, so subsequent loads may not fetch again. Feed v2 only. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The position of an interest header on the NTP that the user has indicated + they aren't interested in the story's source. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The position of an interest header on the NTP that the user has indicated + they aren't interested in the story's topic. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + The Feed library encountered an error at any time. + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The time it takes for the Feed to load all keys from the storage. + + + + + harringtond@chromium.org + feed@chromium.org + + Latencies for individual steps taken to load the feed. This is reported at + most once per Chrome execution, and only reported for a Feed load operation + that ends with the Feed showing up on the UI. All steps added together tally + to the total time taken. + + Feed v2 only. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Status of loading new feed data in the background. Feed v2 only. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Status of loading the initial Feed stream, which happens when a feed surface + is shown. Feed v2 only. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + This is the store-specific status for the initial load of the Feed stream. + This is provided along with ContentSuggestions.Feed.LoadStreamStatus.Initial + because store errors can be shadowed by fallback to network fetch. Feed v2 + only. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Status of loading additional Feed content onto the bottom of the stream. + Feed v2 only. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The time it takes for the Feed to load entries from the storage. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The amount of time fetching articles takes, regardless of success. This + includes the time it takes to get an auth token for signed in users. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: the size in kb of gzip-compressed requests sent by the Feed's + networking host. Recorded when a request is sent. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The integer status code of network requests made by the feed + library's networking host. This code includes both protocol(1xx-5xx) and + non-protocol(-xxx) errors. Recorded when a request completes. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: the uncompressed size in KB of responses received by the Feed's + networking host. Recorded when a successful response is received. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The HTTP response status for a network request made by the Feed component. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The amount of time it takes to get an access token for signed in users. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: failure reason when attempting to fetch an OAuth token for the + feed. Recorded when a token fetch completes. + + + + + frechette@chromium.org + feed@chromium.org + + Android: Whether the notice card for feed action reporting has been + fulfilled. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The number of urls that have offline status requested per call. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The number of milliseconds to round trip offline status for a set of URLs + from Offline Pages component. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The time it takes for the Feed to commit operations from the storage. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The number of milliseconds it takes for Feed content to be visible in the + UI. If content is not immediately available, this is conceptually the amount + of time a loading spinner is shown to the user. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The integer error code when Piet wants to report events that + occurred during Frame rendering. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Difference in age of content between feed and host. Recorded when the Feed + asks the scheduler how to behave when a NTP is opened. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The match status between Feed and the host when the scheduler's + ShouldSessionRequestData method is called. This occurs whenever the NTP is + opened, and tries to track if the Feed and host state agrees or disagrees. + If the device already has content, new requests are not necessarily required + for a reasonable user experience. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The match status between Feed and the host when the scheduler's + ShouldSessionRequestData method is called. This occurs whenever the NTP is + opened, and tries to track if the Feed and host state agrees or disagrees. + The type of request that could be outstanding is to fetch new or more news + articles, and when requests are outstanding new requests should not be + started. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The scheduler watches for various triggers, which cause it to decide if a + refresh is currently warranted or not. This histogram is emitted when a + trigger causes a refresh. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + When NTP is opened, the scheduler host tells the Feed library how to act, if + the existing content should be shown, immediately or with timeout, and if a + refresh request should be started. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + When the Feed scheduler receives a refresh request, the scheduler will + decide to refresh or not depending on the scheduler status. Recorded when + the Feed scheduler receives the request. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + When the previous last fetch attempt time is cleared, log the time since the + last fetch attempt. This typically occurs when suggestions are cleared. A + client that has never made a successful fetch (at least since it was last + cleared) will report the time since epoch. + + + + + carlosk@chromium.org + petewil@chromium.org + feed@chromium.org + Number of each type of feedback sent about the feed. + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + The reason for a server request from the Feed's prespective, when the + request is started. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How long it took from enqueuing the task to when it was run. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How long it took from the task starting to when it finished executing. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How long a user used the Feed in one day (local time midnight to midnight). + Reported at most once per day. Usage reported is typically from the previous + day, but could be from several days ago if the user is not active. Time is + calculated starting with the first Feed interaction, until the Feed surface + is closed, or the user is idle (no scrolling or other actions) for 30 + seconds. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How many top level features were in the continuation response, typically + clusters. Recorded when the fetch completes successfully. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How many tokens were in the continuation response, typically ways to fetch + more articles. Recorded when the fetch completes successfully. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + When a token fails to complete, how many failures this token has seen. + Record when the fetch fails. + + + + + iwells@chromium.org + harringtond@chromium.org + feed@chromium.org + + Result of attempting to upload a batch of one or more actions. + + + + + iwells@chromium.org + harringtond@chromium.org + feed@chromium.org + + Result of an UploadActionsTask run in which zero or more batches of user + actions are uploaded. See ContentSuggestions.Feed.UploadActionsBatchStatus + for the status of a particular batch upload. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Counts of user actions within the feed surface (Feed v2 only). + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Time between the UI requesting additional stream content and failure by + either a 15 second timeout or a surface closure. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Time between the UI requesting additional stream content and the content + being provided within 15 seconds. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + Reported when a user taps on a Feed card unless the page is not loaded + successfully within 20 seconds. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + The time between a user tapping on a Feed card and the page finishes loading + successfully. Only reported when loading takes less than 20 seconds. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + The time between a Feed surface opening and failing to provide the user + content. This is reported when either the surface is closed or a timeout of + 15 seconds expires. + + + + + harringtond@chromium.org + carlosk@chromium.org + feed@chromium.org + + The time between a Feed surface opening and the user viewing the first + content. If this takes more than 15 seconds, + ContentSuggestions.Feed.UserJourney.OpenFeed.FailureDuration is reported + instead. + + + + + harringtond@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: Time spent reading the page linked by an opened suggestion card. + This is a lower-bound time. Does not include time after Chrome is closed and + re-opened. Does not include time after the visited tab no longer has focus, + or after the tab is navigated. For the 'open in new tab' action, time starts + when the user switches to the new tab. If the user returns by tapping the + suggestion again, it will be recorded as another entry in this histogram. + + Feed v2 only. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The position of a clicked element in the stream not accounting for + header views. The top being 0. Position does not change after initial + layout. Specifically the position does not update if dismisses/removes are + performed. This is similar to NewTabPage.ContentSuggestions.Opened, but + records the specific elementType that was clicked. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The time since the content was made available on the device. This + could be the time for when this content was retrieved from the server or the + time the data was pushed to the device. Recorded when the user clicks the + element. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The position of a viewed element in the stream not accounting for + header views. The top being 0. Position does not change after initial + layout. Specifically the position does not update if dismisses/removes are + performed. This is similar to NewTabPage.ContentSuggestions.Shown, but + records the view after it has been on the screen for 500 milliseconds of + time instead of on predraw. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + Android: The time since the content was made available on the device. This + could be the time for when this content was retrieved from the server or the + time the data was pushed to the device. Recorded when the element has been + on the screen for 500 milliseconds. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How many top level features were in an initial article fetch, typically + clusters. Recorded when an article fetch completes and were previously in + zero state. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + + How many tokens were in an initial article fetch, typically ways to fetch + more articles. Recorded when an article fetch completes and were previously + in zero state. + + + + + carlosk@chromium.org + harringtond@chromium.org + feed@chromium.org + The reason the zero state (no articles) is shown to a user. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/cookie/histograms.xml b/tools/metrics/histograms/histograms_xml/cookie/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..3d907ebbd3ede516fb5e9f2286822bafbb43c63c --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/cookie/histograms.xml @@ -0,0 +1,397 @@ + + + + + + + + + + morlovich@chromium.org + + Whether or not updates to the backing store succeeded or failed, recorded + every update. + + + + + morlovich@chromium.org + + Recorded when a problem occurs trying to commit changes to the cookie store + back to disk, in the SQLite store. + + + + + estark@chromium.org + + Number of times a cookie was set with a name prefixed by + "__Secure-" or "__Host-" (prefixes reserved by + https://tools.ietf.org/html/draft-west-cookie-prefixes). + + + + + estark@chromium.org + + Number of times a cookie was set with a name prefixed by + "__Secure-" or "__Host-" that violate cookie prefix + rules. That is, a __Secure- cookie must be set over a secure connection with + the Secure attribute, and a __Host- cookie must be set over a secure + connection, with the Secure attribute, with no Domain attribute, and with a + Path attribute of "/". (As defined in + https://tools.ietf.org/html/draft-west-cookie-prefixes.) + + + + + bingler@chromium.org + chlily@chromium.org + + The scheme a cookie was set by and the scheme of the request that the cookie + was sent to. This is recorded once per cookie each time a URL request has + its headers set. + + + + + estark@chromium.org + + For each cookie added to the store, record whether its source URL has a + cryptographic scheme, broken down by Secure and not Secure. + + + + + chlily@chromium.org + tnagel@chromium.org + + Records the detection of a corrupted meta table. See http://crbug.com/111376 + . + + + + + chlily@chromium.org + morlovich@chromium.org + + Records a failure to recover a corrupted meta table. See + http://crbug.com/111376 . + + + + + battre@chromium.org + + Number of cookies in the store (recorded every 10 minutes of active browsing + time) + + + + + battre@chromium.org + Number of minutes until cookie expires when set. + + + + mkwst@chromium.org + + The size of each outgoing request's 'Cookie' header field's value, in bytes. + + + + + bingler@chromium.org + chlily@chromium.org + + The value of the effective samesite for cookies that will be included in a + request. Logged once per successful inclusion. + + + + + bingler@chromium.org + chlily@chromium.org + + The value of the effective samesite for cookies that will be accepted from a + response. Logged once per successful inclusion. + + + + + morlovich@chromium.org + chlily@chromium.org + + Whether killing the database because it was corrupted beyond repair + succeeded. + + + + + morlovich@chromium.org + + Recorded when a problem is recorded when loading the persistent cookie + store. + + + + + chlily@chromium.org + kaustubhag@chromium.org + + Records the number of distinct keys (eTLD+1's) that have experienced + eviction of a non-expired cookie due to reaching the max number of cookies + per key. This is not persisted across network service restarts, so it + represents the number of such eTLD+1's that have relatively recently added + new cookies that went over the limit (since the last browser restart, crash, + etc). Recorded every 10 minutes of active browsing time. + + + + + chlily@chromium.org + kaustubhag@chromium.org + + Records the number of distinct keys (eTLD+1's) that have any stored cookies + (which may or may not be expired). Recorded every 10 minutes of active + browsing time. + + + + + pwnall@chromium.org + + This histogram records the total duration of time during which at least one + web request was blocked waiting for the cookie store to load. If no requests + were affected, the value is 0. If two requests are simultaneously blocked + for 1 second, the value is 1 second. If two requests are consecutively + blocked for 1 second each, the value is two seconds. + + + + + pwnall@chromium.org + + The number of distinct Effective Top-Level Domains Plus One (ETLD+1, i.e., + google.com, bbc.co.uk) for which a priority cookie load occurred. + + + + + chlily@chromium.org + morlovich@chromium.org + + The same-site context of a request, i.e. the relationship between the + request and the navigational environment. Logged on every request to access + a cookie. + + + + + chlily@chromium.org + bingler@chromium.org + + The value of the cookie's SameSite attribute, if any. This is logged once + per created cookie, upon parsing of the SameSite attribute from a string. + + + + + bingler@chromium.org + kaustubhag@chromium.org + + The type of breaking same-site context downgrade a cookie is experiencing + along with the secureness of the origin that we're attempting to send the + cookie to. Logged once per included cookie or if the cookie was excluded + only due to insufficient same-site context. + + For more information on breaking context downgrades please see the comment + block above + net::CanonicalCookie::CookieInclusionStatus::WARN_STRICT_LAX_DOWNGRADE_STRICT_SAMESITE. + + + + + bingler@chromium.org + kaustubhag@chromium.org + + The type of breaking same-site context downgrade a cookie is experiencing + along with the secureness of the origin that is attempting to set the + cookie. Logged once per included cookie or if the cookie was excluded only + due to insufficient same-site context. + + For more information on breaking context downgrades please see the comment + block above + net::CanonicalCookie::CookieInclusionStatus::WARN_STRICT_LAX_DOWNGRADE_STRICT_SAMESITE. + + + + + chlily@chromium.org + morlovich@chromium.org + + If a cookie was SameSite=None, this records whether or not it was Secure. + Logged once per attempt to set a SameSite=None cookie. + + + + + chlily@chromium.org + morlovich@chromium.org + + If a cookie had an unspecified SameSite attribute, this records what mode it + was treated as, i.e. what the effective SameSite mode is. Logged once per + attempt to determine SameSite inclusion/exclusion for an + unspecified-SameSite cookie. + + + + + erikchen@chromium.org + + The number of session cookies deleted on startup. This metric is emitted + even if no cookies are deleted. This metric is not emitted if session + cookies are restored, rather than deleted on startup. + + + + + erikchen@chromium.org + + The amount of time required to delete session cookies on startup. This + metric is emitted even if no cookies are deleted. This metric is not emitted + if session cookies are restored, rather than deleted on startup. + + + + + nharper@chromium.org + + The amount of time (ms) between the cookie store load starting and + completing. + + + + + pwnall@chromium.org + + The amount of time (ms) to migrate a v9 cookie database to v10. + + + + + chlily@chromium.org + morlovich@chromium.org + + The amount of time (ms) to migrate a v10 cookie database to v11. Migration + occurs upon first startup of a browser version with v11 database code. + + + + + chlily@chromium.org + morlovich@chromium.org + + The amount of time (ms) to migrate a v11 cookie database to v12. Migration + occurs upon first startup of a browser version with v12 database code. + + + + + erikchen@chromium.org + The amount of time (ms) to migrate a v8 database to v9. + + + + nyquist@chromium.org + The amount of time (ms) to initialize the cookies database. + + + + pwnall@chromium.org + + This histogram records the wall-clock delay between a priority load task + being posted to the DB-thread and its execution. + + + + + erikchen@chromium.org + + This histogram records the the total amount of time spent fetching the + cookies associated with an eTLD+1 from disk, including time spent waiting in + task queues. + + + + + pwnall@chromium.org + + This histogram records the sum of the durations of all initial tasks loading + cookies from the database. + + + + + erikchen@chromium.org + + This histogram records the wall-clock delay between the Load task being + posted to the DB-thread and its execution. + + + + + mkwst@chromium.org + For each cookie added to the store, record it's type(s). + + + + + diff --git a/tools/metrics/histograms/histograms_xml/cras/histograms.xml b/tools/metrics/histograms/histograms_xml/cras/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..d8361cdad7a8539ecda93ba915052f227688969d --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/cras/histograms.xml @@ -0,0 +1,783 @@ + + + + + + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + For each audio thread running state, records the number of busyloops. + Busyloop means the audio thread doen't sleep during more than two loops, + which may make the system busy. Depending on the time of running state, the + records is seperated into three logs: ShortPeriod(shorter than 10 minutes), + MediumPeriod(between 10 and 60 minutes), LongPeriod (longer than 60 + minutes). + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + When each busyloop stops, records the length of it. The lengths exceeding + 1000 are recorded as 1000. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + It is used for logging input device usage of ChromeOS users. The count + indicates the number of each input device has been used and is recorded when + a device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + It is used for logging output device usage of ChromeOS users. The count + indicates the number of each input device has been used and is recorded when + a device is closed. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The volume of a device, which is recorded when closing a device. + + + + + enshuo@chromium.org + chromeos-audio@google.com + + For each HFP audio device record whether it supports battery indicator. + + + + + enshuo@chromium.org + chromeos-audio@google.com + + For each HFP battery level change event record if it comes from the command + defined by Apple's Spec or BT HFP spec. The count indicates how frequent + user might see this event and can help us decide which data source we prefer + to show if the headset supports both. + + + + + enshuo@chromium.org + chromeos-audio@google.com + + For each SCO connection record the returned event. The event indicates if + the setup of the connection is successful or not. + + + + + enshuo@chromium.org + chromeos-audio@google.com + + For each HFP audio device supporting WBS record how many packets are lost + per 1000 packets when the device is closed. This is for tracking how bad the + packet loss can be for WBS in real world. + + + + + hychao@chromium.org + chromeos-audio@google.com + + For each single connection of bluetooth HFP audio device record whether it + supports wideband-speech feature or not. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The highest hardware delay of input device in CRAS(ChromeOS audio server). + It is calculated by 1000 * highest_hw_level / largest_cb_level. The + highest_hw_level is the highest remaining frames in the device. The + largest_cb_level is the largest callback threshold of streams which have + attached to this device. The value is recorded when the device is removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The highest hardware delay of output device in CRAS(ChromeOS audio server). + It is calculated by 1000 * highest_hw_level / largest_cb_level. The + highest_hw_level is the highest remaining frames in the device. The + largest_cb_level is the largest callback threshold of streams which have + attached to this device. The value is recorded when the device is removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The highest hardware level of input device in CRAS(Chrome OS audio server). + The hardware level is the remaining frames in the device. For input device, + it can show the latency between capturing and actual reading. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The highest hardware level of output device in CRAS(Chrome OS audio server). + The hardware level is the remaining frames in the device. For output device, + it can show the latency between writing and actual playout. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device A2DP in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of fallback device in the abnormal situation. The runtime is the + duration between opening and closing a device. The value is recorded when + the device is closed. + + + + + hychao@chromium.org + chromeos-audio@google.com + + The runtime of input device Bluetooth narrowband in CRAS(ChromeOS audio + server). The runtime is the duration between opening and closing a device. + The value is recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of Bluetooth input device that doesn't fall to any other + category we defined. i.e HSP, narrowband or wideband. The runtime is the + duration between opening and closing a device. The value is recorded when + the device is closed. + + + + + hychao@chromium.org + chromeos-audio@google.com + + The runtime of input device Bluetooth wideband in CRAS(ChromeOS audio + server). The runtime is the duration between opening and closing a device. + The value is recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device InternalMic in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device HFP in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device Hotword in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device HSP in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device InternalMic in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device InternalMic in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device Mic in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of fallback device in the normal situation. The runtime is the + duration between opening and closing a device. The value is recorded when + the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device PostDspLoopback in CRAS(ChromeOS audio server). + The runtime is the duration between opening and closing a device. The value + is recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device PostMixLoopback in CRAS(ChromeOS audio server). + The runtime is the duration between opening and closing a device. The value + is recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device InternalMic in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of silent hotword device in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device Unknown in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input device USB in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of input stream in CRAS(ChromeOS audio server). The runtime is + the duration between creating and destroying a stream. The value is recorded + when the stream is destroyed. + + + + + hychao@chromium.org + chromeos-audio@google.com + + For each single connection of bluetooth HFP record the result of codec + negotiation, if supported. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The first time missed callbacks happened on input streams in CRAS (Chrome OS + audio server). In normal situation, audio thread should follow the callback + schedule to send frames to clients. However, sometimes it may miss schedule + because of some reasons. When the first time that audio thread misses + callback schedule, record how many seconds have passed since stream started + running. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The first time missed callbacks happened on output streams in CRAS (Chrome + OS audio server). In normal situation, audio thread should follow the + callback schedule to fetch frames from clients. However, sometimes it may + miss schedule because of some reasons. When the first time that audio thread + misses callback schedule, record how many seconds have passed since stream + started running. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The number of missed callbacks of input streams in a day after rescheduling. + It is calculated by number of the missed callbacks / runtime of the stream + after rescheduling. This value is recorded when the stream is removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The number of missed callbacks of output streams in a day after + rescheduling. It is calculated by number of the missed callbacks / runtime + of the stream after rescheduling. This value is recorded when the stream is + removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The number of missed callbacks of input streams in a day. It is calculated + by number of the missed callbacks / runtime of the stream. This value is + recorded when the stream is removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The number of missed callbacks of output streams in a day. It is calculated + by number of the missed callbacks / runtime of the stream. This value is + recorded when the stream is removed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The second time missed callbacks happened on input streams in CRAS (Chrome + OS audio server). When the second time audio thread misses callback + schedule, record how many seconds have passed since the first time. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The second time missed callbacks happened on output streams in CRAS (Chrome + OS audio server). When the second time audio thread misses callback + schedule, record how many seconds have passed since the first time. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device A2DP in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of fallback device in the abnormal situation. The runtime is the + duration between opening and closing a device. The value is recorded when + the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of Bluetooth output device in CRAS(ChromeOS audio server) that + doesn't belong to any category we defined. i.e A2DP, HFP or HSP. The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device Haptic in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device HDMI in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device Headphone in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device HFP in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device HSP in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device InternalSpeaker in CRAS(ChromeOS audio server). + The runtime is the duration between opening and closing a device. The value + is recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device Lineout in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of fallback device in the normal situation. The runtime is the + duration between opening and closing a device. The value is recorded when + the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device Unknown in CRAS(ChromeOS audio server). The + runtime is the duration between opening and closing a device. The value is + recorded when the device is closed. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output device USB in CRAS(ChromeOS audio server). The runtime + is the duration between opening and closing a device. The value is recorded + when the device is closed. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The runtime of output stream in CRAS(ChromeOS audio server). The runtime is + the duration between creating and destroying a stream. The value is recorded + when the stream is destroyed. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The callback threshold of stream in CRAS(Chrome OS audio server). It is the + number of frames when to request more from the client. This value is + recorded when the stream is created. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The client type of input stream in CRAS(Chrome OS audio server). This value + is recorded when the stream is created. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The client type of output stream in CRAS(Chrome OS audio server). This value + is recorded when the stream is created. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The bit map of effects to be enabled on this stream. This value is recorded + when the stream is created. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The flags of stream in CRAS(Chrome OS audio server). It is the special + handling for stream. This value is recorded when the stream is created. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The sampling format of stream in CRAS(Chrome OS audio server). This value is + recorded when the stream is created. + + + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The sampling rate of stream in CRAS(Chrome OS audio server). This value is + recorded when the stream is created. + + + + + hychao@chromium.org + chromeos-audio@google.com + + The longest additional time CRAS(Chrome OS audio server) ever waits for a + stream exceeding the timeout threshold. This value is recorded per stream + when it gets removed and used to investigate the audio glitch/skip problem + on Chrome OS. + + + + + yuhsuan@chromium.org + chromeos-audio@google.com + + The number of underruns happened on one audio device. Underrun here means + there are no samples in device buffer while device is playing. It is + recorded when device is closed by CRAS(Chrome OS audio server). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/cros/histograms.xml b/tools/metrics/histograms/histograms_xml/cros/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0f9b2660105dffde1b1bccd1d1a9c2931e6ff3cc --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/cros/histograms.xml @@ -0,0 +1,209 @@ + + + + + + + + + + charleszhao@chromium.org + tby@chromium.org + + This histogram is emitted each time when CrOSAction is recorded by the + CrOSActionRecorder. For each CrOSAction multiple values can be emitted, + corresponding to different events happened during the action processing by + CrOSActionRecorder. + + + + + fdegros@chromium.org + chromeos-files-app@google.com + + The type of archive file that Chrome OS cros-disks daemon is requested to + mount. + + + + + fdegros@chromium.org + chromeos-files-app@google.com + + The media type of removable device that Chrome OS cros-disks daemon is + requested to mount. + + + + + fdegros@chromium.org + chromeos-files-app@google.com + + The type of file system that Chrome OS cros-disks daemon is requested to + mount. + + + + + fdegros@chromium.org + chromeos-files-app@google.com + + The error code returned by ZIP mounting program fuse-zip, which is called + every time a user opens a ZIP archive in ChromeOS Files App. + + + + + fdegros@chromium.org + chromeos-files-app@google.com + + The error code returned by RAR mounting program rar2fs, which is called + every time a user opens a RAR archive in ChromeOS Files App. + + + + + austinct@chromium.org + + The error code of disk format signals received from the Chrome OS cros-disks + daemon. + + + + + austinct@chromium.org + + Time taken for the Chrome OS cros-disks daemon to perform a format + operation. + + + + + amistry@chromium.org + + The error code of disk mount signals received from the Chrome OS cros-disks + daemon. + + + + + amistry@chromium.org + + The {mount type}x{mount error code} received from the Chrome OS cros-disks + daemon. + + + + + amistry@chromium.org + + Time taken by the Chrome OS cros-disks daemon to perform a Mount operation. + + + + + amistry@chromium.org + + The error code of disk unmount operations returned from the Chrome OS + cros-disks daemon. + + + + + amistry@chromium.org + + Time taken by the Chrome OS cros-disks daemon to perform an Unmount + operation. + + + + + alemate@chromium.org + cros-oac@google.com + + Records the number of times when first-run dialog was shown. + + + + + alemate@chromium.org + cros-oac@google.com + + Index of furthest step that was reached during tutorial. Since order of + steps could change eventially and new steps could apear we use index here + instead of step name. + + + + + alemate@chromium.org + cros-oac@google.com + The total time that user spent on first-run tutorial. + + + + alemate@chromium.org + cros-oac@google.com + The time that user spent on some step of tutorial. + + + + alemate@chromium.org + cros-oac@google.com + Tracks the way how user left tutorial. + + + + alemate@chromium.org + cros-oac@google.com + + Records the number of times when first-run tutorial has been launched. + + + + + clumptini@google.com + tbuckley@chromium.org + + Records the reason why the "Cros USB device detected" notification + was dismissed. Recorded on notificiation close, after usb attached. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/crostini/histograms.xml b/tools/metrics/histograms/histograms_xml/crostini/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5a2344bcb548bef24a965ac86dbf1506d4c3c542 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/crostini/histograms.xml @@ -0,0 +1,449 @@ + + + + + + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time a Crostini app is launched, recording whether the app is + the built in terminal, a registered app, or an unknown app. + + + + + clumptini@google.com + tbuckley@chromium.org + + The result of attempting to launch a Crostini app (including Terminal). + + + + + clumptini@google.com + tbuckley@chromium.org + + Records the number of Crostini apps that surface in the launcher at login + time (not including the Terminal). This only logs if Crostini is enabled for + the current user. + + + + + clumptini@google.com + tbuckley@chromium.org + + The available disk space at the start of the crostini install flow, recorded + when installation was canceled. This is recorded any time the user cancels + the install before it finishes. This includes cases where e.g. they + previously tried installing and got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + + The available disk space at the start of the crostini install flow, recorded + when installation returned an error. This is recorded any time the user + tries to install install crostini and gets an error. This includes cases + where e.g. they previously tried installing and got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + + The available disk space at the start of the crostini install flow, recorded + when installation succeeded. This is recorded any time the user successfully + installs crostini. This includes cases where e.g. they previously tried + installing and got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + Result of crostini backup. + + + + clumptini@google.com + tbuckley@chromium.org + + log base 2 of compressed container backup size in bytes, rounded to the + nearest integer. Value is between 0 and 50, to give good granularity for + common sizes, while maintaining a range that can support very large sizes. + + + + + clumptini@google.com + tbuckley@chromium.org + + log base 2 of uncompressed container image size in bytes, rounded to the + nearest integer. Value is between 0 and 50, to give good granularity for + common sizes, while maintaining a range that can support very large sizes. + + + + + clumptini@google.com + tbuckley@chromium.org + + 100 * compressed size / container size. The conventional compression ratio + of input / output has not been used as the resulting value is unbounded. + + + + + clumptini@google.com + tbuckley@chromium.org + Time taken for failed backup. + + + + clumptini@google.com + tbuckley@chromium.org + Time taken for successful backup. + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time a Crostini container is launched, recording the OS + version running inside the container. + + + + + clumptini@google.com + tbuckley@chromium.org + + The percentage of the system CPU that crosvm processes used during the + 10-minute measuring period. This is recorded once every 10 minutes when + crosvm is running. + + + + + clumptini@google.com + tbuckley@chromium.org + + The number of crosvm processes that are running at the end of the 10-minute + interval. This is recorded once every 10 minutes when crosvm is running. + + + + + clumptini@google.com + tbuckley@chromium.org + + The percentage of the system memory that crosvm processes used at the end of + the 10-minute measuring period. This is recorded once every 10 minutes when + crosvm is running. + + + + + clumptini@google.com + davidmunro@google.com + + Records the result (e.g. succeeded) whenever an attempt to resize a Crostini + disk finishes. + + + + + clumptini@google.com + davidmunro@google.com + + Recorded each time a user tries resizing a Crostini disk to infer attempts + that started but never finished (e.g. code bug missing a timeout). This + won't exactly line up with the total of Crostini.DiskResizeResult due to how + metrics work (e.g. start one day and result the next) but should be close. + + + + + clumptini@google.com + davidmunro@google.com + + Records the type (e.g. sparse qcow2) of the user's disk. Emitted often, you + probably want to look at the unique user numbers of this metric. Certain + disk types are vulnerable to disk corruption in certain scenarios so this + metric tracks our progress in moving people off them and tells us if we need + to do additional work to migrate users off. + + + + + clumptini@google.com + tbuckley@chromium.org + + Filesystem corruption events in the crostini VM, recorded every time + corruption is observed to affect the state of the system. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the CrostiniRecoveryView is show, on detecting that a VM + is still running after a Chrome crash. + + + + + clumptini@google.com + tbuckley@chromium.org + + Emitted whenever a run of CrostiniRestarter is triggered except during the + initial install. + + + + + clumptini@google.com + tbuckley@chromium.org + + The result of a single run of CrostiniRestarter. This is recorded any time + the crostini restart flow is triggered, except during the initial install. + + + + + clumptini@google.com + tbuckley@chromium.org + Result of crostini restore. + + + + clumptini@google.com + tbuckley@chromium.org + Time taken for failed restore. + + + + clumptini@google.com + tbuckley@chromium.org + Time taken for successful restore. + + + + clumptini@google.com + tbuckley@chromium.org + victorhsieh@chromium.org + Record user's choice in Crostini Settings + + + + clumptini@google.com + tbuckley@chromium.org + + Emitted whenever a run of CrostiniRestarter is triggered during the initial + install. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user completes the Crostini setup UI, recording the + result of the setup. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user initiates the Crostini setup UI, recording the + UI surface that invoked the setup. + + + + + clumptini@google.com + tbuckley@chromium.org + + A record of post-startup failures in crostini components. Buckets are + recorded to whenever we become aware that the corresponding component has + failed. + + + + + joelhockey@chromium.org + tbuckley@chromium.org + + Record which settings in terminal are changed by users. This is captured + each time terminal is launched and fetches the current settings, and not + just when settings are changed, in order to give the best information about + the current state of active users. + + + + + clumptini@google.com + tbuckley@chromium.org + + The time from a user setting up their device, to the user enabling Crostini. + + + + + clumptini@google.com + tbuckley@chromium.org + + The time taken for the crostini installer to be canceled by the user. This + is recorded any time the user cancels the install before it finishes. This + includes cases where e.g. they previously tried installing and got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + + The time taken for the crostini installer to fail due to an error. This is + recorded any time the user tries to install install crostini and gets an + error. This includes cases where e.g. they previously tried installing and + got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + + The time taken for the crostini installer to finish successfully. This is + recorded any time the user successfully installs crostini. This includes + cases where e.g. they previously tried installing and got an error. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user completes the Crostini uninstall UI, recording + the result of the uninstall. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user initiates the Crostini uninstall UI, recording + the UI surface that initiated the uninstall. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time we display (or would display, see suffixes) a + notification that the user is trying to do something Crostini doesn't + support. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user sees the Crostini upgrade Notifiation, recording + the action that closded the notification. + + + + + clumptini@google.com + tbuckley@chromium.org + + A collection of events that can occur while upgrading the crostini + container, recorded as they occur. + + + + + clumptini@google.com + tbuckley@chromium.org + + Recorded each time the user sees the Crostini upgrade UI, recording the UI + surface that initiated the upgrade. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/crypt/histograms.xml b/tools/metrics/histograms/histograms_xml/crypt/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..cd0b5639895a0c83b52202407a093db3ad2d8b77 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/crypt/histograms.xml @@ -0,0 +1,966 @@ + + + + + + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether or not the device manufacturer name returned in the + hardware info is empty. Recored during the construction of a + ClientAppMetadata proto. + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether or not the device model name returned in the hardware info + is empty. Recored during the construction of a ClientAppMetadata proto. + + + + + khorimoto@chromium.org + better-together-dev@google.com + + Indicates the result of fetching an InstanceId token during the construction + of a ClientAppMetadata proto messages. + + + + + khorimoto@chromium.org + nohle@chromium.org + better-together-dev@google.com + + Counts the number of times the InstanceId token fetch got retried because it + did not match with the expected InstanceId. Logged during the construction + of a ClientAppMetadata proto message. + + + + + hansberry@chromium.org + better-together-dev@google.com + Indicates success of performing a DeviceSync. + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval performed during + initialization of the DeviceSync service. Recorded when the async callback + is invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval + performed during initialization of the DeviceSync service. Recorded when the + async callback is invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of GCM registration performed during + initialization of the DeviceSync service. Recorded when the async callback + is invoked. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of GCM registration performed during initialization of + the DeviceSync service. Recorded when the async callback is invoked. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the DeviceSync service initialization. + Recorded each time the DeviceSync service starts up, after initialization + succeeds. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Indicates that there was no issue retrieving supported and enabled software + features, or that there were enabled features which were not in the + supported feature set. See the histogram + "CryptAuth.DeviceSyncSoftwareFeaturesResult.Failures" for a + breakdown of failures by feature type. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Breaks down by feature type + "CryptAuth.DeviceSyncSoftwareFeaturesResult"'s count of enabled + features which were not in the supported feature set. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async GetDevicesActivityStatus API call to + CryptAuth during multi-device setup. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async GetDevicesActivityStatus API call + during multi-device setup. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async BatchNotifyGroupDevices API call to + CryptAuth. Recorded when the async callback is invoked or when the call + times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async BatchNotifyGroupDevices API call to + CryptAuth. Recorded when the async callback is invoked or when the call + times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async device metadata decryption during the + CryptAuth v2 DeviceSync flow. Records a success if the operation did not + timeout; a separate metric, + CryptAuth.DeviceSyncV2.DeviceSyncer.MetadataDecryptionSuccess, tracks + individual encryption failures.Recorded when the async callback is invoked + or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async group private key decryption during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async device metadata decryption during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async group private key decryption during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the group private key sent by CryptAuth matches the + existing group private key when they are expected to agree. Emitted during a + CryptAuth v2 DeviceSync if the group private key is not being rotated. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the local device metadata agrees with that sent by + CryptAuth in the SyncMetadata response. Emitted during the CryptAuth v2 + DeviceSync flow, after device metadata is decrypted. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not device metadata sent by CryptAuth in the SyncMetadata + response was able to be decrypted. Emitted during the CryptAuth v2 + DeviceSync flow for each device metadata packet. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not device metadata sent by CryptAuth in the SyncMetadata + response was able to be parsed from a decrypted serialized byte string into + a proto. Emitted during the CryptAuth v2 DeviceSync flow for each device + metadata packet. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async BatchGetFeatureStatuses API call during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the expected number of devices were sent in the + BatchGetFeatureStatuses response. Emitted when a BatchGetFeatureStatuses + response is received from the CryptAuth server. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async BatchGetFeatureStatuses API call + during the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not a device ID in the BatchGetFeatureStatuses response + has been seen already in the same response. Emitted for each device in the + BatchGetFeatureStatuses response. Emitted when a BatchGetFeatureStatuses + response is received from the CryptAuth server. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the feature type strings returned in the + BatchGetFeatureStatuses response are known feature types. Emitted for each + feature type for each device in the BatchGetFeatureStatuses response. + Emitted when a BatchGetFeatureStatuses response is received from the + CryptAuth server. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not a feature is marked as enabled even though it is + listed as unsupported. This should never happen. Emitted for all feature + types, for each device in the BatchGetFeatureStatuses response. Emitted when + a BatchGetFeatureStatuses response is received from the CryptAuth server. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not a device in the BatchGetFeatureStatuses response was + included in the BatchGetFeatureStatuses request. Emitted for each device in + the BatchGetFeatureStatuses response. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async BatchSetFeatureStatuses API call to + CryptAuth. Recorded when the async callback is invoked or when the call + times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async BatchSetFeatureStatuses API call to + CryptAuth. Recorded when the async callback is invoked or when the call + times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ShareGroupPrivateKey API call during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async group private key encryption during the + CryptAuth v2 DeviceSync flow. Records a success if the operation did not + timeout; a separate metric, + CryptAuth.DeviceSyncV2.GroupPrivateKeySharer.EncryptionSuccess, tracks + individual encryption failures. Recorded when the async callback is invoked + or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the group private key was able to be encrypted using + a device's encrypting key. Recorded during the ShareGroupPrivateKey phase of + the CryptAuth v2 DeviceSync flow. Recorded for each device with whom we + intend to share the group private key. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async group private key encryption during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ShareGroupPrivateKey API call during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not a device's key used to encrypt the group private key + is empty. If the key is empty, the group private key cannot be encrypted and + shared with the device. Recorded during the ShareGroupPrivateKey phase of + the CryptAuth v2 DeviceSync flow. Recorded for each device with whom we + intend to share the group private key. + + + + + nohle@chromium.org + better-together-dev@google.com + + The clients' reasons for making CryptAuth v2 DeviceSync requests. Recorded + when a DeviceSync is requested. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the first async SyncMetadata API call during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the second async SyncMetadata API call during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async group key creation during the CryptAuth v2 + DeviceSync flow. Recorded when the async callback is invoked or when the + call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async local device metadata encryption during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the first async SyncMetadata API call during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async group key creation during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async local device metadata encryption + during the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the second async SyncMetadata API call during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the device metadata packets sent by CryptAuth have + all of the necessary fields populated. Emitted for each device metadata + packet during the SyncMetadata phase of the CryptAuth v2 DeviceSync flow. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the device ID from a device metadata packet sent by + CryptAuth in the SyncMetadata response has the same ID as a packet from the + same response. Emitted for each device metadata packet during the + SyncMetadata phase of the CryptAuth v2 DeviceSync flow. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the number of devices returned by a v1 DeviceSync. Only recorded + when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and + v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices + are merged together, which occurs after either a v1 or v2 DeviceSync. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the number of devices returned by a v2 DeviceSync. Only recorded + when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and + v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices + are merged together, which occurs after either a v1 or v2 DeviceSync. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the percentage of devices returned by a v2 DeviceSync that replace + their v1 counterparts. This will only occur if the v2 device has a decrypted + public key that matches a v1 device. Only recorded when v1 and v2 DeviceSync + are running in parallel. Only recorded if a v1 and v2 DeviceSync has ever + previously occurred. Emitted when v1 and v2 devices are merged together, + which occurs after either a v1 or v2 DeviceSync. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the percentage of devices returned by a v2 DeviceSync that have a + decrypted user public key. Only recorded when v1 and v2 DeviceSync are + running in parallel. Only recorded if a v1 and v2 DeviceSync has ever + previously occurred. Emitted when v1 and v2 devices are merged together, + which occurs after either a v1 or v2 DeviceSync. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the ratio of the number of devices returned by a v2 DeviceSync to + the number returned by a v1 DeviceSync. Devices returned by a v2 DeviceSync + should be a subset of the devices returned by a v1 DeviceSync, barring any + race conditions. This ratio should be greater than or equal to + PercentageOfV1DevicesReplacedByV2Devices because a v2 device can only + replace its v1 counterpart if it has a decrypted public key. Only recorded + when v1 and v2 DeviceSync are running in parallel. Only recorded if a v1 and + v2 DeviceSync has ever previously occurred. Emitted when v1 and v2 devices + are merged together, which occurs after either a v1 or v2 DeviceSync. + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether or not any device data in the device registry changed as a + result of the CryptAuth v2 DeviceSync attempt. Recorded when a DeviceSync + attempt finishes. + + + + + nohle@chromium.org + better-together-dev@google.com + + The CryptAuth v2 DeviceSync attempt results broken down by result code. + Recorded when a DeviceSync attempt finishes. + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether the CryptAuth v2 DeviceSync attempt succeeded, failed, or + finished with non-fatal errors. Recorded when a DeviceSync attempt finishes. + + + + + nohle@chromium.org + better-together-dev@google.com + + The top-level result of the CryptAuth device enrollment process. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async EnrollKeys API call to CryptAuth during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async SyncKeys API call to CryptAuth during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async key creation call during the CryptAuth v2 + Enrollment flow. Recorded when the async callback is invoked or when the + call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async EnrollKeys API call to CryptAuth + during the CryptAuth v2 Enrollment flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async key creation call during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or + when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async SyncKeys API call to CryptAuth + during the CryptAuth v2 Enrollment flow. Recorded when the async callback is + invoked or when the call times out. + + + + + nohle@chromium.org + better-together-dev@google.com + + The clients' reasons for making CryptAuth v2 Enrollment requests. Recorded + when an enrollment is requested. + + + + + nohle@chromium.org + better-together-dev@google.com + + The CryptAuth v2 Enrollment attempt results broken down by result code. + Recorded when an enrollment attempt finishes. + + + + + nohle@chromium.org + better-together-dev@google.com + + The success or failure of CryptAuth v2 Enrollment requests. Recorded when an + enrollment attempt finishes. + + + + + nohle@chromium.org + better-together-dev@google.com + + The state--at system start time--of persisted user key pairs, generated + during CryptAuth v1 and/or v2 Enrollment: whether they exist and if they + agree. Recorded on CryptAuth v2 Enrollment manager construction. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records the multi-device feature type sent in a GCM message from CryptAuth + v2. Emitted when a GCM message with a feature type key/value pair is + received from CryptAuth. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the DeviceSync group name sent in a GCM message from + CryptAuth is valid. Currently the only valid group name is + "DeviceSync:BetterTogether". Emitted when a GCM message with a + DeviceSync group name key/value pair is received from CryptAuth. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the multi-device feature type sent in a GCM message + from CryptAuth v2 is recognized by the Chrome OS client. Emitted when a GCM + message with a feature type key/value pair is received from CryptAuth. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records whether or not the CryptAuth TargetService was specified in a GCM + message by both the CryptAuth v1 registration tickle type key/value pair as + well as the CryptAuth v2 target service key/value pair. Both key/value pairs + should not exist in same GCM message. Emitted when a GCM message is received + from CryptAuth. + + + + + nohle@chromium.org + better-together-dev@google.com + + The CryptAuth TargetService--Enrollment or DeviceSync--indicated by the + registration tickle type key/value pair of an incoming GCM message. The + registration tickle type is used in GCM messages sent by CryptAuth v1. + Emitted when a GCM message from CryptAuth is received. + + + + + nohle@chromium.org + better-together-dev@google.com + + The CryptAuth TargetService--Enrollment or DeviceSync--indicated by the + target service key/value pair of an incoming GCM message. This key/value + pair is used in GCM messages sent by CryptAuth v2. Emitted when a GCM + message from CryptAuth is received. + + + + + nohle@chromium.org + better-together-dev@google.com + + The time it takes the GCM driver to return the result of a GCM registration + request made by the CryptAuth GCM manager. CryptAuth registration with GCM + is only performed once, if successful, for a given user on a device as the + first step in CryptAuth v1 or v2 Enrollment. Recorded when the CryptAuth GCM + manager is notified by the GCM driver that the registration attempt + finished, successfully or not. The GCM driver might quietly retry failures + before notifying the CryptAuth GCM manager. The time recorded here + encompasses the possible retry attempts and delays from the GCM driver. + + + + + nohle@chromium.org + better-together-dev@google.com + + The result code from a GCM registration request made by the CryptAuth GCM + manager. CryptAuth registration with GCM is only performed once, if + successful, for a given user on a device as the first step in CryptAuth v1 + or v2 Enrollment. Recorded when the CryptAuth GCM manager is notified by the + GCM driver that the registration attempt finished, successfully or not. The + GCM driver might quietly retry failures before notifying the CryptAuth GCM + manager. This metric will not include results codes that were quietly + retried by the GCM driver. + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether or not the Instance ID used by the CryptAuth client + differs from the previously retrieved ID. Recorded while fetching client app + metadata if a previous ID has been set. + + + + + nohle@chromium.org + better-together-dev@google.com + + Indicates whether or not the Instance ID token used by the CryptAuth client + differs from the previously retrieved token. Recorded while fetching client + app metadata if a previous token has been set. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/cryptohome/histograms.xml b/tools/metrics/histograms/histograms_xml/cryptohome/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..70823b44d8431ff3b692da85d4b25286320185b3 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/cryptohome/histograms.xml @@ -0,0 +1,545 @@ + + + + + + + + + + zuan@chromium.org + cros-hwsec+uma@chromium.org + + Records the total running time of every async dbus calls of Cryptohome at + server side. + + + + + zuan@chromium.org + cros-hwsec+uma@chromium.org + + Records the total inqueue time of every async dbus calls of Cryptohome at + server side. Recorded when the first stage of this requests is served. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + Checksum status of critical persistent data used by Cryptohome. This status + is recorded every time the cryptohomed daemon reads a file. + + + + + slangley@chromium.org + wiefangsun@chromium.org + + In low disk space scenarios, Cryptohome erases whole user profiles. This is + a number of user profiles deleted during cleanup. Only reported when + non-zero. + + + + + apronin@chromium.org + louiscollard@chromium.org + zuan@chromium.org + cros-hwsec+uma@chromium.org + + Records when a deprecated API function in cryptohome is called, so we know + which exposed DBus API can be removed without side effect. + + + + + dspaid@chromium.org + + The status of the user home directory migration from ecryptfs to + ext4-crypto. This is logged once at the end of each migration. + + + + + kinaba@chromium.org + + The error code of file operation by which the user home directory migration + from ecryptfs to ext4-crypto has failed. This is logged once the migration + encounters a file I/O error. + + + + + kinaba@chromium.org + + The type of file operation at which the user home directory migration from + ecryptfs to ext4-crypto has failed. This is logged once the migration + encounters a file I/O error. + + + + + kinaba@chromium.org + + The category of the path where the user home directory migration from + ecryptfs to ext4-crypto has failed. This is logged once the migration + encounters a file I/O error. + + + + + dspaid@chromium.org + + The total amount of free disk space on the system when the user started the + migration from ecryptfs to ext4-crypto. This is only logged when the user + encounters an insufficient space error. + + + + + dspaid@chromium.org + + The total amount of free disk space on the system when the user received an + insufficient space error during the migration from ecryptfs to ext4-crypto. + This is only logged when the user encounters an insufficient space error. + + + + + dspaid@chromium.org + + The total number of bytes of xattr data that we are trying to store on a + file when we receive an insufficient space error. This includes both xattr + data already present on the file as well as the new xattr we are trying to + set. This is only logged during ecryptfs to ext4-crypto migration if we + receive an insufficient space error when setting a new extended attribute. + + + + + dspaid@chromium.org + + The status of the user home directory migration from ecryptfs to + ext4-crypto. This is logged once at the start of each migration. + + + + + hashimoto@chromium.org + + The total byte count (MB) of the data in a user's home directory which is + being migrated from ecryptfs to ext4-crypto. This is logged once when a new + migration starts. + + + + + hashimoto@chromium.org + + The total file count in a user's home directory which is being migrated from + ecryptfs to ext4-crypto. This is logged once when a new migration starts. + + + + + dspaid@chromium.org + pmarko@chromium.org + + The status of the user home directory minimal migration from ecryptfs to + ext4-crypto. This is logged once at the end of each minimal migration. + + + + + dspaid@chromium.org + pmarko@chromium.org + + The status of the user home directory minimal migration from ecryptfs to + ext4-crypto. This is logged once at the start of each minimal migration. + + + + + slangley@chromium.org + weifangsun@chromium.org + + In low disk space scenarios, Cryptohome erases caches while target amount of + free disk space is not reached. It starts from low priority categories. This + histogram reports which topmost priority was reached to fulfill a cleanup + request. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + Cryptohome errors. + + + + enlightened@chromium.org + tnagel@chromium.org + + Indicates whether Encrypted Vault Keyset Key (EVKK) is TPM wrapped. This is + reported when the Derive function inside scrypt auth block or TPM auth block + is called, which happends during cryptohome mount phase. + + + + + vsavu@chromium.org + weifangsun@chromium.org + + In low disk space scenarios, Cryptohome performs a lot of disk space + operations to erase data. This is the amount of space that was released by + the automatic cleanup. + + + + + slangley@chromium.org + weifangsun@chromium.org + + In low disk space scenarios, Cryptohome performs a lot of disk space + operations to erase data. This is a number of milliseconds taken to perform + a cleanup. Reported only if longer than 5 ms. Increased maximum and number + of buckets compared to FreeDiskSpaceTotalTime. + + + + + slangley@chromium.org + weifangsun@chromium.org + + This is an amount of Google Drive cache (MB) which was evicted by cryptohome + due to shortage of remaining disk space. Reported only if something was + deleted (greater than zero). + + + + + dspaid@chromium.org + + The encryption type used for a user's cryptohome directory. This is logged + each time the cryptohome is mounted. + + + + + + + pmalani@chromium.org + apronin@chromium.org + mnissler@chromium.org + allenwebb@chromium.org + cros-hwsec+uma@chromium.org + + Events related to Low Entropy (LE) credential management. These are logged + every time an operation involving a LE credential is performed. + + + + + alemate@chromium.org + rsorokin@chromium.org + cros-oac@google.com + + This is the status of cryptohome migration to GaiaId. Every time user logs + in current migration status is recorded. + + + + + fukino@chromium.org + + The amount of consumed battery level during cryptohome encryption migration. + This is logged when the battery level decreases during migration, and the + data is used to check if the minimum battery level required to start + migration is appropriate. + + + + + fukino@chromium.org + + The first screen in the encryption migration UI, which is shown when a user + attempts to log in to the system and old encryption (eCryptfs) is detected. + + + + + fukino@chromium.org + + The result of encryption migration from eCryptfs to Ext4 dircrypto. The + recorded result is what the migration UI in Chrome side is notified from + cryptohomed. + + + + + fukino@chromium.org + + The result of the removal of user's cryptohome. When the migration UI is + notified that the migration failed, the UI tries to remove the user's + cryptohome to make sure that the user can create clean crytohome directory + in the next sign-in. + + + + + fukino@chromium.org + + User's choice when the system is ready to migrate encryption. The user can + start migration or skip it. It is used to know how many users have skipped + migration. + + + + + fukino@chromium.org + + How many times each screen in migration UI is shown to the user. A screen is + recorded as a visible screen when the screen is kept displayed at least for + a second. + + + + + betuls@chromium.org + jorgelo@chromium.org + + The result of a cryptohome out-of-process mount cleanup. Recorded once per + logout. + + + + + betuls@chromium.org + jorgelo@chromium.org + + The result of a cryptohome out-of-process mount operation. Recorded once per + login attempt. + + + + + zuan@chromium.org + cros-hwsec+uma@chromium.org + + How many tasks runs in parallel typically in the mount thread of cryptohome. + Recorded when a requests comes in. Counts of 1 will not reported. + + + + + vsavu@chromium.org + slangley@chromium.org + weifangsun@chromium.org + + The amount of time (s) between disk cleanup runs. If there is sufficient + disk space, nothing is reported. The first cleanup run after boot is not + reported. + + + + + kerrnel@chromium.org + mnissler@chromium.org + + The amount of time (ms) for Chrome OS cryptohome daemon to verify the user's + password during an unlock operation. + + + + + dspaid@chromium.org + + The amount of time (ms) for the user's home directory to be migrated from + ecryptfs to ext4-crypto. If the migration is interrupted and subsequently + resumed (such as due to power loss) then no value is recorded for either + attempt. + + + + + dspaid@chromium.org + + The amount of time (ms) for the user's home directory to be migrated from + ecryptfs to ext4-crypto if the minimal migration method was used. If the + minimal migration is interrupted and subsequently resumed (such as due to + power loss) then no value is recorded for either attempt. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome daemon to initialize the + PKCS#11. Initializations under 1 second represent checks on a previously + initialized PKCS#11, and should be discarded for analysis. + + + + + jorgelo@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time for Chrome OS cryptohome to mount the encrypted home + directory. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome to mount the encrypted + guest home directory asynchronously. + + + + + jorgelo@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time for Chrome OS cryptohome to mount the encrypted guest + home directory. + + + + + jorgelo@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time cryptohome spends actively performing mounts when + creating an ephemeral user data directory. Does not include any process or + async dispatch overhead. + + + + + betuls@chromium.org + jorgelo@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time cryptohome spends performing the mounts for the user's + encrypted home directory. Does not include any process or async dispatch + overhead. + + + + + jorgelo@chromium.org + betuls@chromium.org + + The amount of time (ms) cryptohome spends terminating and reaping the + out-of-process mounter, which includes the time spent by the mounter itself + tearing down the user home directory. + + + + + jorgelo@chromium.org + betuls@chromium.org + + The amount of time (ms) cryptohome spends running the out-of-process + mounter, until the user home directory is finalized. + + + + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome daemon to take ownership of + the TPM. + + + + + afakhry@chromium.org + + The errors resulting from interacting with the Trusted Platform Module (TPM) + device. + + + + + zuan@chromium.org + cros-hwsec+uma@chromium.org + + Records the time duration of every dbus outgoing calls issued from the + client of Crypthome in Chrome side. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/custom_tabs/histograms.xml b/tools/metrics/histograms/histograms_xml/custom_tabs/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0d146203b8e6de2fdadfcf242c5f498851e9128f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/custom_tabs/histograms.xml @@ -0,0 +1,307 @@ + + + + + + + + + + ranj@chromium.org + yfriedman@chromium.org + + + + Records the time duration in CustomTab Activity from onStart/onResume to + onStop/onPause, if that activity is opened by Webapp/WebApk/Trusted Web + Activity. + + + + + yusufo@chromium.org + + Android: AppId declared by the launching application in EXTRA_APPLICATION_ID + in a custom tab. This histogram is used as a means to count the total + instances of custom tabs created meanwhile binning them across launching + apps that have identified themselves. Starting with M84 this is is also + recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + peconn@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/browserservices/OWNERS + + + Records whether the CustomTab/TrustedWebActivity "navigate to landing + page" algorithm for child tabs - e.g. tabs opened via window.open() - + produces the same behaviour (closes the current tab) as the webapp + "close current tab" algorithm. Recorded when the user clicks the + CustomTab/TrustedWebActivity close button on a child tab. Starting with M84 + this is is also recorded for webapps/WebAPKs. Filter the platform for just + CCT/TWA data. + + + + + peconn@chromium.org + peter@chromium.org + + Android: Recorded whenever user closes the custom tab by hitting the close + button or back to return to the caller app. Keeps track of the connection + status and whether the app was using a KeepAlive connection. Recorded only + for AGSA. Starting with M84 this is is also recorded for webapps/WebAPKs. + Filter the platform for just CCT/TWA data. + + + + + peconn@chromium.org + peter@chromium.org + + Android: Recorded whenever user closes the custom tab by hitting the close + button or back to return to the caller app. Keeps track of the connection + status and whether the app was using a KeepAlive connection. Recorded for + all apps other than AGSA. Starting with M84 this is is also recorded for + webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + cct-team@google.com + + Time between the start of a detached resource request and its completion + (failure or success). Android only. Starting with M84 this is is also + recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + cct-team@google.com + + Reports the final status of the detached request, including success. + Recorded once per detached resource request. Android only. Starting with M84 + this is is also recorded for webapps/WebAPKs. Filter the platform for just + CCT/TWA data. + + + + + lizeb@chromium.org + cct-team@google.com + + Number of redirects followed by a detached resource request until success or + failure. Android only. Starting with M84 this is is also recorded for + webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + + Time between the intent arrival to a Custom Tab and the first navigation + commit. Recorded for every custom tabs intent when the page has finished + loading. + + + + + lizeb@chromium.org + + Time between the intent arrival to a Custom Tab and the navigation start. + Recorded when the page has finished loading. Non-"Herb" mode. + + + + + lizeb@chromium.org + + Time between the intent arrival in Chrome and the first "page + loaded" event, if the navigation is successful. Non-"Herb" + mode. + + + + + lizeb@chromium.org + + Android only. Which flavors of mayLaunchUrl() were used before a tab launch. + Can be low and/or high confidence. Recorded at the same time as + CustomTabs.WarmupStateOnLaunch for the buckets "Session, No Warmup, + Warmup called from another UID", "Session, No Warmup" and + "Session, Warmup". + + + + + lizeb@chromium.org + cct-team@google.com + + Recorded only on Android. Whether a parallel request was requested by the + calling application, and if so its initial status. Recorded once per handled + intent, when the request is initiated. Starting with M84 this is is also + recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + + For Custom Tabs, records whether mayLaunchUrl() has been called, and if so, + whether the call was later matched by a URL launch. + + + + + lizeb@chromium.org + + When a URL prediction succeeds, time in ms between the prediction and the + actual launch. + + + + + alexilin@chromium.org + + Time between the start of a detached resource request for resource prefetch + and its completion (failure or success). Android only. + + + + + alexilin@chromium.org + + Reports the final status of the detached request for resource prefetch, + including success. Recorded once per resource prefetch request. Android + only. + + + + + lizeb@chromium.org + mthiesse@chromium.org + + Android: When a spare WebContents is created from Custom Tabs, record + creation, and whether it was used by CCT, stolen by another Chrome Activity, + killed or destroyed. Creation is recorded to get the "abandoned" + case, that is when Chrome is killed before the renderer. Starting with M84 + this is is also recorded for webapps/WebAPKs. Filter the platform for just + CCT/TWA data. + + + + + lizeb@chromium.org + + Android: When a spare WebContents is created from Custom Tabs, record how + long is took before the render process was killed. Starting with M84 this is + is also recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA + data. + + + + + lizeb@chromium.org + + Recorded only for Android. How a speculation was started or why it was + disallowed. This is recorded when a speculation of any kind is requested, + with either a "Speculation allowed" value, or a reason why it was + not allowed. If the speculation is allowed and is attempted to be started, + the status on start will be counted in addition: one of + "Prefetch", "Prerender", "Background Tab" or + "Prerender not started". The last case is when a prerender is + abandoned during start. Starting with M84 this is is also recorded for + webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + + Recorded only for Android. Recorded when a speculation is requesting to swap + into a visible tab. Starting with M84 this is is also recorded for + webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + + + yusufo@chromium.org + src/base/metrics/OWNERS + + Recorded only for Android. Records on every metrics upload whether the + currently visible tab is a custom tab. The custom tab is launched by a + client app with customized UI. Some metrics like page load time will behave + differently for these tabs since it will be possible to warm up the browser + process and prepare resources for specific urls ahead of time via a service + connection. This histogram can be used to cluster these metric differently. + + As of M87, this histogram is logged on a log start, rather than log end to + tag more logs. + + + + + lizeb@chromium.org + + Recorded only on Android. Reports whether warmup() has been called when a + Custom Tabs Intent is received from an application, and if so, whether the + call could be matched with a session. Starting with M84 this is is also + recorded for webapps/WebAPKs. Filter the platform for just CCT/TWA data. + + + + + lizeb@chromium.org + + Android: When a CustomTabActivity creates its Tab, whether we use a + prerendered WebContents, a spare renderer or create a new WebContents. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/data_reduction_proxy/histograms.xml b/tools/metrics/histograms/histograms_xml/data_reduction_proxy/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..67b3ce5ced30f59d8d07ae42746c7cc0b46162dc --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/data_reduction_proxy/histograms.xml @@ -0,0 +1,438 @@ + + + + + + + + + + bengr@chromium.org + tbansal@chromium.org + + Counts the response bytes that did not go through the data reduction proxy + as the result of a bypass event. + + + + + bengr@chromium.org + tbansal@chromium.org + + Counts the response bytes that went through the data reduction proxy and + were not bypassed. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Total number of authentication required responses received from the Data + Reduction Proxy. + + An "Unexpired" value is recorded every time a new client config is + fetched and parsed successfully. An "Expired" value is recorded + every time Chrome receives an authentication failure from the data saver + proxy. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The time delta between connectStart and connectEnd of the client config + request. This is recorded only on successful requests when connectStart and + connectEnd were non-null. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The number of failed attempts when retrieving the configuration from the + Data Reduction Proxy API before a successful attempt took place. + + Recorded every time a new client config is fetched and parsed successfully. + If the device has a valid connection type but no Internet connectivity, this + count will keep increasing. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Time from when the Data Reduction Proxy configuration request starts until + it completes. + + Recorded every time a new client config is fetched and parsed successfully. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Count per HttpResponseCode when attempting to retrieve the Data Reduction + Proxy configuration from the Data Reduction Proxy API. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The time delta between requestStart and requestEnd of the client config + request. This is recorded only on successful requests. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Upper bound on the count of HTTP requests that did or did not go through the + data saver proxy. + + An HTTP request may not go through data saver proxy if the config was + unavailable, due to local bypass rules, or due to server side bypasses. If + data saver is turned on, this metric is recorded every time proxy is + resolved for an HTTP request. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Upper bound on the count of main frame requests that did or did not go + through the data saver proxy. + + A main frame request may not go through data saver proxy if the config was + unavailable, due to local bypass rules, or due to server side bypasses. If + data saver is turned on, this metric is recorded every time proxy is + resolved for an HTTP request. + + + + + rajendrant@chromium.org + tbansal@chromium.org + + Records the number of days since data reduction proxy was last enabled by + the user. Recorded only if the data reduction proxy was last enabled since + this metric was added to Chromium (M-56). Recorded at Chrome startup if data + reduction proxy is already enabled, and when the user enables the data + reduction proxy. + + + + + robertogden@chromium.org + bengr@chromium.org + + When the data savings are cleared because the user deletes their browsing + history, record how many buckets were deleted. See also + DataReductionProxy.SavingsCleared.Reason/User action - cleared browsing + history. + + + + + rajendrant@chromium.org + tbansal@chromium.org + + Samples of user interactions with the Data Saver settings menu across all + platforms (android, IOS, desktop extension). Data is collected whenever user + toggles the ON/OFF switch in the settings menu for reducing data usage. + + For desktop, Off-to-On/On-to-Off histogram count will increment when the + data saver extension is installed/uninstalled respectively as well. + + + + + kundaji@chromium.org + + Time taken to load historical data usage from Level DB into memory. This UMA + is reported each time the method to load historical data usage is called, + which happens when user views data usage history. + + + + + rajendrant@chromium.org + bengr@chromium.org + + Records the aggregate data use of services for the last week. Different + conditions are added as suffixes to this histogram. Recorded when Chrome is + started, so this does not include the current session. The aggregation + happens when requests complete. The current week calculation is based on + week starting from the Epoch day(Thursday, January 1, 1970), and every 7 + days is treated as a week. + + + + + rajendrant@chromium.org + bengr@chromium.org + + Records the aggregate data use for the last week. This is the downstream + data use of all user-initiated traffic. Recorded when Chrome is started, so + this does not include the current session. The aggregation happens when + requests complete. The current week calculation is based on week starting + from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated + as a week. + + + + + kundaji@chromium.org + Status of calling Open() on Data Reduction Proxy LevelDB. + + + + kundaji@chromium.org + Size of Data Reduction Proxy LevelDB measured at startup. + + + + sclittle@chromium.org + src/components/data_reduction_proxy/OWNERS + + Records the result of migrating the Data Reduction Proxy away from being + configured via a proxy preference, including cases when no migration action + was taken. + + + + + rajendrant@chromium.org + tbansal@chromium.org + + Whether the save-data savings JSON retrieved from field trial was parsed as + a dictionary. Recorded on startup. + + + + + robertogden@chromium.org + bengr@chromium.org + + Records why the data reduction savings were cleared. See also + DataReductionProxy.DeleteBrowsingHistory.NumBuckets. + + + + + bengr@chromium.org + tbansal@chromium.org + + Logs the data savings in MB of the data reduction proxy snackbar promo that + was shown. The snackbar promo shows the user the amount of data Chrome has + saved them using Data Saver. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the negative data savings percentage at Chrome startup for data + saver enabled users who have browsed a reasonable amount (at least 10MB + since data saver was enabled). + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the data savings percentage at Chrome startup for data saver enabled + users who have browsed a reasonable amount (at least 10MB since data saver + was enabled). Negative savings are not recorded. + + + + + rajendrant@chromium.org + tbansal@chromium.org + + Samples of the state of the data reduction proxy on Chrome startup. The + proxy will either be unavailable (the feature hasn't been rolled out to this + user yet), not enabled (the feature is available but the user doesn't have + it turned on), or enabled (the feature is enabled and turned on). + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the aggregate data use of services for the current week. Different + conditions are added as suffixes to this histogram. Recorded when Chrome is + started, so this does not include the current session. The aggregation + happens when requests complete. The current week calculation is based on + week starting from the Epoch day(Thursday, January 1, 1970), and every 7 + days is treated as a week. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the aggregate data use for the current week. This is the downstream + data use of all user-initiated traffic. Recorded when Chrome is started, so + this does not include the current session. The aggregation happens when + requests complete. The current week calculation is based on week starting + from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated + as a week. + + + + + bengr@chromium.org + mcrouse@chromium.org + + Samples of user interactions with the Data Reduction Proxy promos, First Run + Experience, main menu footer, and settings menu. All samples are mutually + exclusive. These samples include: + + The user interactions with the First Run Experience. On Android when the + user sees the FRE card, the Data Reduction Proxy defaults to ON. The user + can disable the proxy via a switch on the card. The state of the proxy is + sampled when the First Run Experience is completed and only reported if the + Data Reduction Proxy card was shown. + + The user interactions with the second run promo. On Android, there are two + actions that dismiss this promo (enable or dismiss). This is sampled when + the promo leaves view. + + The user interactions with the Infobar promo. On Android, there are two + actions that dismiss the promo (enable, dismiss). This is sampled when the + promo leaves view. + + The user interactions with the Snackbar promo. The user can either ignore + the promo or click the action to the settings menu. From the settings menu, + the user may enable or disable the proxy. + + The user interactions with the main menu footer. The user can click the + footer to enter the settings menu. From the settings menu, the user may + enable or disable the proxy. + + Any other user interaction with the ON/OFF switch in the settings menu for + reducing data usage. Only the setting changes between entering the reducing + data usage setting menu and leaving the menu will be sampled regardless of + how many times they toggle the ON/OFF switch. Other samples that report + ON/OFF settings menu changes are not also reported here. + + The views of and user interactions with the site breakdown in the settings + menu. The site breakdown can be sorted by data saved descending or data used + descending, and expanded to view more sites. The Data Reduction statistics + can also be reset. + + + + + rajendrant@chromium.org + robertogden@chromium.org + src/components/data_reduction_proxy/OWNERS + + The total original content size displayed to the user. Computed over the + last 30 days. Recorded when the user views the data savings in the UI. + + + + + rajendrant@chromium.org + robertogden@chromium.org + src/components/data_reduction_proxy/OWNERS + + The difference between the total data savings as displayed to the user and + the sum of the data savings for all hosts in the data use breakdown. + Calculated as a percentage of `abs(summedSavingsTotal - + displayedSavingsTotal) / (summedSavingsTotal + displayedSavingsTotal)`. + Recorded when the user views the data savings in the UI. + + + + + rajendrant@chromium.org + robertogden@chromium.org + src/components/data_reduction_proxy/OWNERS + + The total data saved displayed to the user. Computed over the last 30 days. + Recorded when the user views the data savings in the UI. + + + + + rajendrant@chromium.org + robertogden@chromium.org + src/components/data_reduction_proxy/OWNERS + + The difference between the total data usage as displayed to the user and the + sum of the data usage for all hosts in the data use breakdown. Calculated as + a percentage of `abs(summedUsageTotal - displayedUsageTotal) / + (summedUsageTotal + displayedUsageTotal)`. Recorded when the user views the + data savings in the UI. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/dev/histograms.xml b/tools/metrics/histograms/histograms_xml/dev/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..a42c1d2e6c62fee5df4524086cfa148d4a23d625 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/dev/histograms.xml @@ -0,0 +1,278 @@ + + + + + + + + + + alph@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + Specified DevTools action has been taken. + + + + yangguo@chromium.org + rayankans@chromium.org + bmeurer@chromium.org + + The result of clearing all stored events for a Background Service feature. + This is called if a developer clicks on a delete button in a Background + Service DevTools panel. + + + + + rayankans@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + + The result of loading all stored events for a Background Service feature. + This is called when the a Bakground Service DevTools panel is opened. + + + + + rayankans@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + + The result of logging a Background Service event. An event is logged if + `Recording` mode is on and a relevant Background Service event is taking + place. + + + + + yangguo@chromium.org + bmeurer@chromium.org + rayankans@chromium.org + + Records the Background Service for which `Recording` mode was enabled. This + is called if the developer toggles the record button in the relevant + Bakground Service DevTools panel. + + + + + yangguo@chromium.org + mathias@chromium.org + alexrudenko@chromium.org + + Records which color contrast threshold was fixed by the user in the Color + Picker. + + + + + changhaohan@chromium.org + yangguo@chromium.org + mathias@chromium.org + + Records state changes for DevTools computed style grouping toggled from the + Computed pane. + + + + + yangguo@chromium.org + brgoddar@microsoft.com + leo.lee@microsoft.com + + DevTools settings for CSS grid recorded on launch of the DevTools. + + + + + yangguo@chromium.org + soxia@microsoft.com + leo.lee@microsoft.com + + Records the usage of dual screen device emulation: a dual screen or fold + device is selected for emulation; the span button is hit; or the platform + support of dual screen is utilized. + + + + + yangguo@chromium.org + brgoddar@microsoft.com + shanejc@microsoft.com + + Fired when a devtools experiment is disabled from the experiments tab. + + + + + yangguo@chromium.org + brgoddar@microsoft.com + shanejc@microsoft.com + + Fired when a devtools experiment is enabled from the experiments tab. + + + + + yangguo@chromium.org + brgoddar@microsoft.com + shanejc@microsoft.com + + Fires for each experiment that is enabled at the time of Devtools Launch. + + + + + changhaohan@chromium.org + yangguo@chromium.org + mathias@chromium.org + + Records which UI element is being used to open Grid overlays. + + + + + yangguo@chromium.org + patrick.brosset@microsoft.com + leo.lee@microsoft.com + + Number of simultaneous persistent CSS grid overlays in DevTools, recorded + after each change. + + + + + alph@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + + Time to load Developer Tools when user clicks Inspect Element in the context + menu. + + + + + yangguo@chromium.org + jegarc@microsoft.com + + Records which type of issue is expanded in the issues panel. + + + + + yangguo@chromium.org + bmeurer@chromium.org + + Records which UI element is being used to open the Issues Panel. + + + + + yangguo@chromium.org + jegarc@microsoft.com + + Records which resource from what issue category is opened in the issue + panel. + + + + + yangguo@chromium.org + jalyn@microsoft.com + leo.lee@microsoft.com + + Recorded when the user changes which keyboard shortcut presets they are + using in the DevTools. + + + + + yangguo@chromium.org + jalyn@microsoft.com + leo.lee@microsoft.com + + Recorded when a DevTools keyboard shortcut has been processed and + successfully executed its action. + + + + + + + yangguo@chromium.org + bmeurer@chromium.org + + Measures the time until a given tool is interactive during a cold start of + the DevTools. + + + + + yangguo@chromium.org + joselea@microsoft.com + shanejc@microsoft.com + Specified DevTools panel was closed. + + + + alph@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + Specified DevTools panel was shown. + + + + alph@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + Specified DevTools setting was changed. + + + + changhaohan@chromium.org + yangguo@chromium.org + bmeurer@chromium.org + Specified DevTools sidebar pane was shown. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/diagnostics/histograms.xml b/tools/metrics/histograms/histograms_xml/diagnostics/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..41b741839d87efda191b06cb23aab866cf3e9952 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/diagnostics/histograms.xml @@ -0,0 +1,429 @@ + + + + + + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the DiskSpace recovery step that runs + on recovery startups. The recovery step attempts to guarantee the DiskSpace + test, which checks that the disk space in the volume where the user data + directory normally lives is not dangerously low, would pass on the next + startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the JSONBookmarks recovery step that + runs on recovery startups. The recovery step attempts to guarantee the + JSONBookmarks test, which makes sure that the JSON-encoded Bookmarks file is + properly formed, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the JSONLocalState recovery step that + runs on recovery startups. The recovery step attempts to guarantee the + JSONLocalState test, which makes sure that the JSON-encoded Local State file + is properly formed, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the JSONPreferences recovery step + that runs on recovery startups. The recovery step attempts to guarantee the + JSONPreferences test, which makes sure that the JSON-encoded Preferences + file is properly formed, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the PathDictionaries recovery step + that runs on recovery startups. The recovery step attempts to guarantee the + PathDictionaries test, which makes sure that the path to the Dictionaries + directory exists and has the right permissions, would pass on the next + startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the PathLocalState recovery step that + runs on recovery startups. The recovery step attempts to guarantee the + PathLocalState test, which makes sure that the path to the Local State file + exists and has the right permissions, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the PathResources recovery step that + runs on recovery startups. The recovery step attempts to guarantee the + PathResources test, which makes sure that the path to the Resources + directory exists and has the right permissions, would pass on the next + startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the PathUserData recovery step that + runs on recovery startups. The recovery step attempts to guarantee the + PathUserData test, which makes sure that the path to the User Data directory + exists and has the right permissions, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityCookie recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityCookie test, which checks the integrity of the Cookie + database, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker + recovery step that runs on recovery startups. The recovery step attempts to + guarantee the SQLiteIntegrityDatabaseTracker test, which checks the + integrity of the Database Tracker database, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityFavicons recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityFavicons test, which checks the integrity of the Favicons + database, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityHistory recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityHistory test, which checks the integrity of the History + database, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityNSSCert recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityNSSCert test, which checks the integrity of the NSS + Certificate database, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityNSSKey recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityNSSKey test, which checks the integrity of the NSS Key + database, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityTopSites recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityTopSites test, which checks the integrity of the TopSites + database, would pass on the next startup. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityWebData recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityWebData test, which checks the integrity of the Web Data + database, would pass on the next startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Count of the number of times diagnostics recovery is invoked or not, and how + it was invoked. A sample is added to this histogram once for each startup of + Chrome. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the DiskSpace test + that runs on recovery startups. The DiskSpace test checks that the disk + space in the volume where the user data directory normally lives is not + dangerously low. + + + + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the JSONBookmarks + test that runs on recovery startups. The JSONBookmarks test checks to make + sure that the JSON encoded bookmarks file is properly formed. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the JSONLocalState + test that runs on recovery startups. The JSONLocalState test checks to make + sure that the JSON encoded Local State file is properly formed. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the JSONPreferences + test that runs on recovery startups. The JSONPreferences test checks to make + sure that the Preferences file is properly formed. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the PathDictionaries + test that runs on recovery startups. The PathDictionaries test checks makes + sure that the path to the Dictionaries folder exists and has the right + permissions. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the PathLocalState + test that runs on recovery startups. The PathLocalState test checks makes + sure that the path to the Local State folder exists and has the right + permissions. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the PathResources + test that runs on recovery startups. The PathResources test checks makes + sure that the path to the Resources folder exists and has the right + permissions. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of diagnostics for the PathUserData test + that runs on recovery startups. The PathUserData test checks makes sure that + the path to the User Data folder exists and has the right permissions. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityCookie test that + runs on recovery startups. The test checks the integrity of the Cookie + database. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker + test that runs on recovery startups. The test checks the integrity of the + Database Tracker database. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityFavicons test that + runs on recovery startups. The test checks the integrity of the Favicons + database. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityHistory test that + runs on recovery startups. The test checks the integrity of the History + database. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityNSSCert test that + runs on recovery startups. The test checks the integrity of the NSS + Certificate database. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityNSSKey test that + runs on recovery startups. The test checks the integrity of the NSS Key + database. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityTopSites test that + runs on recovery startups. The test checks the integrity of the TopSites + database. + + + + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityWebData test that + runs on recovery startups. The test checks the integrity of the Web Data + database. + + + + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + shess@chromium.org + + Histogram comparing the various types of diagnostic test failures when + diagnostic tests are run. Note that some types of test failures cause the + rest of the tests to be skipped. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/direct/histograms.xml b/tools/metrics/histograms/histograms_xml/direct/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..77841d823ef33c769d495c4155fcf693f224fde9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/direct/histograms.xml @@ -0,0 +1,287 @@ + + + + + + + + + + drott@chromium.org + etienneb@chromium.org + + The number of iterations that was required to initialize Direct Write. This + metric is taken by the browser process at startup. The value -1 is reported + when the initialization failed. The fallback path using GDI is used instead + of DWrite. + + + + + drott@chromium.org + layout-dev@chromium.org + Records the error returned from CreateFontFace. + + + + drott@chromium.org + layout-dev@chromium.org + + When scanning fonts for meta data as part of local matching, record the + ratio of empty per-family results to all per-family results as percentage. + Recorded in DWriteFontTableBuilder at the time of finishing scanning the + font files for their name meta information. A value of 100% means, all + per-family scan tasks came back empty. A value of 0% means, all per-family + tasks yielded at least one font file. Used for diagnosing + https://crbug.com/1009402. + + + + + drott@chromium.org + layout-dev@chromium.org + Records how many font families are in the fallback cache. + + + + drott@chromium.org + layout-dev@chromium.org + + Measures the effectiveness of the font fallback proxy. This tracks if we + were able to find a suitable font to render the character, and whether an + IPC was necessary. + + + + + drott@chromium.org + + The number of font families as seen by the font proxy in the renderer. + + + + + drott@chromium.org + layout-dev@chromium.org + + Number of font families on the system as retrieved from DWrite API (usually + less than to number of font files reported in + DirectWrite.Fonts.Proxy.NumFontFiles as a family can contain multiple font + files). Recorded in DWriteFontTableBuilder at the time of starting scanning + the font files for their name meta information. Used for diagnosing + https://crbug.com/1009402. + + + + + drott@chromium.org + layout-dev@chromium.org + + The errors encountered by the DirectWrite font proxy while loading fonts. + + + + + drott@chromium.org + layout-dev@chromium.org + Records the error returned from GetSystemFontCollection. + + + + drott@chromium.org + layout-dev@chromium.org + + Indexing speed in font files per second while building the local font unique + name lookup table. Recorded after building the lookup table in + DWriteFontLookupTableBuilder. + + + + + drott@chromium.org + layout-dev@chromium.org + + The number of last resort fallback fonts found on the system as seen by the + browser. + + + + + drott@chromium.org + layout-dev@chromium.org + + The number of font files found for a last resort fallback font. + + + + + drott@chromium.org + layout-dev@chromium.org + + The codepath that was used to load a font family. This is logged in the + browser every time a renderer attempts to load a font family, once per font + file. + + + + + drott@chromium.org + layout-dev@chromium.org + + The outcome of attempting to load a font family in the renderer (success vs + failure and number of families). This is logged in the renderer once per + family that is loaded. + + + + + drott@chromium.org + layout-dev@chromium.org + + The time taken to load a font family, excluding glyph data. This is logged + in the renderer once per family that is loaded. + + + + + drott@chromium.org + layout-dev@chromium.org + + Time it takes to build the font unique name lookup table. Recorded at the + initial build of this table, after which it is kept for the lifetime of the + browser process. The start time is recorded when the actual task of starting + to scan fonts has started. + + + + + drott@chromium.org + layout-dev@chromium.org + + Measures whether the font table lookup structure was loaded from disk cache + or had to be rebuilt due to changes in installed fonts, DWrite version or + Chrome version. Recorded when DWriteFontLookupTableBuilder starts to prepare + the lookup table. + + + + + drott@chromium.org + layout-dev@chromium.org + + Measures whether the font table lookup structure was successfully persisted + to disk after having been constructed. Recorded when + DWriteFontLookupTableBuilder finalizes the lookup table. + + + + + drott@chromium.org + layout-dev@chromium.org + + Time it takes from scheduling the preparation of the font lookup table until + it is ready, independent of whether it is read from cache or built by + scanning fonts. Start time is recorded when the call is made to prepare the + table. Duration and this histogram's value is recorded either when it is + done reading from cache or when the table construction is ready. This metric + includes a scheduling delay from when the task to read from cache or build + is scheduled, untils its execution, while + DirectWrite.Fonts.Proxy.LookupTableBuildTime does not include this + scheduling delay and measures only from when the first font scanning task is + started. + + + + + drott@chromium.org + layout-dev@chromium.org + + Size of the font unique name lookup table in kilobytes. Recorded at the + initial build of this table, after which it is kept for the lifetime of the + browser process. + + + + + drott@chromium.org + layout-dev@chromium.org + + Errors, if any, encountered by the DirectWrite font proxy message filter. + + + + + drott@chromium.org + layout-dev@chromium.org + + When scanning fonts for meta data as part of local matching, record the most + frequent failure of why no meta data was gathered for a font family. + Recorded in DWriteFontTableBuilder at the time of finishing scanning the + font files for their name meta information. Values are Windows HRESULT error + codes, including custom values for implementation specific failure cases. + Used for diagnosing https://crbug.com/1009402. + + + + + drott@chromium.org + layout-dev@chromium.org + + Number of font files which were encountered during scanning for locally + installed font and building the unique font name lookup table. Recorded in + DWriteFontTableBuilder while after the building the lookup table. Kept for + the lifetime of the browser process after that. + + + + + drott@chromium.org + layout-dev@chromium.org + + Shows whether the font lookup table construction timed out. Recorded when + DWriteFontLookupTableBuilder finalizes the lookup table. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/disk/histograms.xml b/tools/metrics/histograms/histograms_xml/disk/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5cc0b78c0629e8cf40b9e9fb7f1e487dbd880170 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/disk/histograms.xml @@ -0,0 +1,1773 @@ + + + + + + + + + + rvargas@chromium.org + + The time for an async IO operation to complete. This covers content Writes + and Reads, measured from the cache thread. + + + + + rvargas@chromium.org + The synchronous portion of an async read. + + + + rvargas@chromium.org + The synchronous portion of an async write. + + + + rvargas@chromium.org + + The average number of open disk cache entries at any given time. + + + + + rvargas@chromium.org + The total size of all the internal buffers. + + + + rvargas@chromium.org + + The number of KB accessed from the cache in a 30 seconds interval. + + + + + rvargas@chromium.org + The time spent creating a new entry on the cache. + + + + rvargas@chromium.org + The age of the last entry on the queue of deleted entries. + + + + rvargas@chromium.org + + The size of the data portion of a given entry by the time it is deleted. + + + + + rvargas@chromium.org + The percentage of the deleted entries. + + + + rvargas@chromium.org + Number of external files that we were unable to delete. + + + + rvargas@chromium.org + + The size of the HTML headers of a given entry by the time it is deleted. + + + + + rvargas@chromium.org + The number of entries currently stored on the cache. + + + + rvargas@chromium.org + + The number of entries currently stored on the cache, after it is full. + + + + + rvargas@chromium.org + + The number of entries accessed by the cache in a 30 seconds interval. + + + + + rvargas@chromium.org + + The average size of an entry. It is only measured after the cache is full, + so evictions are taking place. + + + + + rvargas@chromium.org + Critical error ids. + + + + rvargas@chromium.org + + The age of the cache (in hours) by the time we reach the size limit. + + + + + rvargas@chromium.org + + The number of hours required to fill up the cache, as measured by the cache + being running. + + + + + rvargas@chromium.org + + The average number of KB accessed from the cache in a 30 seconds interval, + by the time we reach the cache size limit. + + + + + rvargas@chromium.org + + The average number of entries accessed by the cache in a 30 seconds + interval, by the time we reach the cache size limit. + + + + + rvargas@chromium.org + + The average size of an entry by the time we reach the cache size limit. + + + + + rvargas@chromium.org + + The percentage of the entries that are highly reused, by the time we fill up + the cache. + + + + + rvargas@chromium.org + + The hit ratio by the time we fill up the cache. Of course, we started with + an empty cache. + + + + + rvargas@chromium.org + + The percentage of the cache used by entries of more than 512 KB, by the time + we reach the cache size limit. + + + + + rvargas@chromium.org + + The percentage of the entries that have been reused a few times, by the time + we fill up the cache. + + + + + rvargas@chromium.org + + The percentage of the entries that have never been reused, by the time we + fill up the cache. + + + + + rvargas@chromium.org + + The percentage of re-created deleted entries versus entries that we really + don't know about. + + + + + rvargas@chromium.org + The time spent reading the LRU-related portion of an entry. + + + + rvargas@chromium.org + + The age of the last entry on the queue of highly used entries. + + + + + rvargas@chromium.org + The percentage of the entries that are highly reused. + + + + rvargas@chromium.org + + The current hit ratio. It is only measured after the cache is full, so + evictions are taking place, and data from the fill-up period is not + considered. + + + + + rvargas@chromium.org + + The hit ratio for each size. To calculate the hit ratio of caches of a + certain size, take the ratio of a bin in this histogram to the same bin in + DiskCache.0.Size2. + + + + + rvargas@chromium.org + + The hit ratio for each total time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.0.TotalTime. + + + + + rvargas@chromium.org + + The hit ratio for each use time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.0.UseTime. + + + + + rvargas@chromium.org + + Percentage of the index table that is currently used (the cache is full). + + + + + rvargas@chromium.org + The size of each key. + + + + rvargas@chromium.org + + Percentage of the cache used by entries of more than 512 KB. It is only + measured after the cache is full, so evictions are taking place. + + + + + rvargas@chromium.org + + The time to load the main entry data from disk, with a "loaded" + system. + + + + + rvargas@chromium.org + + The age of the last entry on the queue of entries reused a few times. + + + + + rvargas@chromium.org + + The percentage of the entries that have been reused a few times. + + + + + rvargas@chromium.org + + The maximum number of simultaneously open disk cache entries. + + + + + rvargas@chromium.org + The maximum size of the cache. + + + + rvargas@chromium.org + + The age of the next entry to be evicted that has never been reused. + + + + + rvargas@chromium.org + The percentage of the entries that have never been reused. + + + + rvargas@chromium.org + The number of open entry references at any given moment. +
+ Closely related to AverageOpenEntries, but this one is not the average per + client but instead a direct histogram updated every 30 secs. +
+ + + + rvargas@chromium.org + + The time spent opening an entry already on the cache (cache hit). + + + + + rvargas@chromium.org + The number of pending IO operations (Async IO). + + + + rvargas@chromium.org + The time spent reading from an entry. + + + + rvargas@chromium.org + + The percentage of re-created deleted entries versus entries that we really + don't know about. + + + + + rvargas@chromium.org + The reason for not sending a full report. + + + + rvargas@chromium.org + The current size of the cache. + + + + rvargas@chromium.org + The time spent reading from an sparse entry. + + + + rvargas@chromium.org + The time spent writing to an sparse entry. + + + + rvargas@chromium.org + The time spent deleting the cache. (Clear browsing data). + + + + rvargas@chromium.org + The time spent deleting the cache. (Clear browsing data). + + + + rvargas@chromium.org + + The number of times that this cache has been deleted by the user. + + + + + rvargas@chromium.org + + The number of times that the user has deleted new entries from this cache. + + + + + rvargas@chromium.org + The number of times that ga.js was evicted. + + + + rvargas@chromium.org + + The number of fatal errors detected for this cache (so we delete + everything). + + + + + rvargas@chromium.org + + The total time it takes to perform a payload IO operation (AKA, directed to + an entry). This is measured from the IO thread. + + + + + rvargas@chromium.org + Number of hours that the cache has been used. + + + + rvargas@chromium.org + + The number of hours that the cache has been in use, for users that still + have available space. + + + + + rvargas@chromium.org + The time spent removing deleted entries from the cache. + + + + rvargas@chromium.org + The time spent removing old entries from the cache. + + + + rvargas@chromium.org + The time spent removing old entries from the cache. + + + + rvargas@chromium.org + + The time spent evicting entries from the cache (moving them to the deleted + list). + + + + + rvargas@chromium.org + + The time that an entry lives in the cache without being accessed until it is + finally purged. + + + + + rvargas@chromium.org + + The number of entries that are deleted on a single iteration. + + + + + rvargas@chromium.org + + The number of entries that are evicted on a single iteration. + + + + + rvargas@chromium.org + + The number of entries that are evicted (moved to the deleted list) on a + single iteration. + + + + + rvargas@chromium.org + The number of entries that are evicted per hour of use. + + + + rvargas@chromium.org + + The time spent moving an entry to the front of the LRU list. + + + + + rvargas@chromium.org + + The percentage of the allowed disk space that we are currently using. + + + + + rvargas@chromium.org + + Number of hours that the cache has been used since last week. + + + + + rvargas@chromium.org + The time spent writing to an entry. + + + + rvargas@chromium.org + + The time for an async IO operation to complete. This covers content Writes + and Reads, measured from the cache thread. Media-specific cache. + + + + + rvargas@chromium.org + + The synchronous portion of an async read. Media-specific cache. + + + + + rvargas@chromium.org + + The synchronous portion of an async write. Media-specific cache. + + + + + rvargas@chromium.org + + The average number of open disk cache entries at any given time. + Media-specific cache. + + + + + rvargas@chromium.org + + The total size of all the internal buffers. Media-specific cache. + + + + + rvargas@chromium.org + + The number of KB accessed from the cache in a 30 seconds interval. + Media-specific cache. + + + + + rvargas@chromium.org + + The time spent creating a new entry on the cache. Media-specific cache. + + + + + rvargas@chromium.org + + The size of the data portion of a given entry by the time it is deleted. + Media-specific cache. + + + + + rvargas@chromium.org + + Number of external files that we were unable to delete. Media-specific + cache. + + + + + rvargas@chromium.org + + The size of the HTML headers of a given entry by the time it is deleted. + Media-specific cache. + + + + + rvargas@chromium.org + + The number of entries currently stored on the cache. Media-specific cache. + + + + + rvargas@chromium.org + + The number of entries currently stored on the cache, after it is full. + Media-specific cache. + + + + + rvargas@chromium.org + + The number of entries accessed by the cache in a 30 seconds interval. + Media-specific cache. + + + + + rvargas@chromium.org + + The average size of an entry. It is only measured after the cache is full, + so evictions are taking place. Media-specific cache. + + + + + rvargas@chromium.org + Critical error ids. Media-specific cache. + + + + rvargas@chromium.org + + The age of the cache (in hours) by the time we reach the size limit. + Media-specific cache. + + + + + rvargas@chromium.org + + The number of hours required to fill up the cache, as measured by the cache + being running. Media-specific cache. + + + + + rvargas@chromium.org + + The average number of KB accessed from the cache in a 30 seconds interval, + by the time we reach the cache size limit. Media-specific cache. + + + + + rvargas@chromium.org + + The average number of entries accessed by the cache in a 30 seconds + interval, by the time we reach the cache size limit. Media-specific cache. + + + + + rvargas@chromium.org + + The average size of an entry by the time we reach the cache size limit. + Media-specific cache. + + + + + rvargas@chromium.org + + The hit ratio by the time we fill up the cache. Of course, we started with + an empty cache. Media-specific cache. + + + + + rvargas@chromium.org + + The percentage of the cache used by entries of more than 512 KB, by the time + we reach the cache size limit. Media-specific cache. + + + + + rvargas@chromium.org + + The time spent reading the LRU-related portion of an entry. Media-specific + cache. + + + + + rvargas@chromium.org + + The current hit ratio. It is only measured after the cache is full, so + evictions are taking place, and data from the fill-up period is not + considered. Media-specific cache. + + + + + rvargas@chromium.org + + The hit ratio for each size. To calculate the hit ratio of caches of a + certain size, take the ratio of a bin in this histogram to the same bin in + DiskCache.2.Size2. Media-specific cache. + + + + + rvargas@chromium.org + + The hit ratio for each total time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.2.TotalTime. Media-specific cache. + + + + + rvargas@chromium.org + + The hit ratio for each use time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.2.UseTime. Media-specific cache. + + + + + rvargas@chromium.org + + Percentage of the index table that is currently used (the cache is full). + Media-specific cache. + + + + + rvargas@chromium.org + The size of each key. Media-specific cache. + + + + rvargas@chromium.org + + Percentage of the cache used by entries of more than 512 KB. It is only + measured after the cache is full, so evictions are taking place. + Media-specific cache. + + + + + rvargas@chromium.org + + The time to load the main entry data from disk, with a "loaded" + system. Media-specific cache. + + + + + rvargas@chromium.org + + The maximum number of simultaneously open disk cache entries. Media-specific + cache. + + + + + rvargas@chromium.org + The maximum size of the cache. Media-specific cache. + + + + rvargas@chromium.org + + The number of open entry references at any given moment. Closely related to + AverageOpenEntries, but this one is not the average per client but instead a + direct histogram updated every 30 secs. Media-specific cache. + + + + + rvargas@chromium.org + + The time spent opening an entry already on the cache (cache hit). + Media-specific cache. + + + + + rvargas@chromium.org + + The number of pending IO operations (Async IO). Media-specific cache. + + + + + rvargas@chromium.org + The time spent reading from an entry. Media-specific cache. + + + + rvargas@chromium.org + + The percentage of re-created deleted entries versus entries that we really + don't know about. Media-specific cache. + + + + + rvargas@chromium.org + + The reason for not sending a full report. Media-specific cache. + + + + + rvargas@chromium.org + The current size of the cache. Media-specific cache. + + + + rvargas@chromium.org + + The time spent deleting the cache. (Clear browsing data). Media-specific + cache. + + + + + rvargas@chromium.org + + The time spent deleting the cache. (Clear browsing data). Media-specific + cache. + + + + + rvargas@chromium.org + + The total time it takes to perform a payload IO operation (AKA, directed to + an entry). This is measured from the IO thread. Media-specific cache. + + + + + rvargas@chromium.org + + Number of hours that the cache has been used. Media-specific cache. + + + + + rvargas@chromium.org + + The time spent removing deleted entries from the cache. Media-specific + cache. + + + + + rvargas@chromium.org + + The time spent removing old entries from the cache. Media-specific cache. + + + + + rvargas@chromium.org + + The time spent removing old entries from the cache. Media-specific cache. + + + + + rvargas@chromium.org + + The time spent evicting entries from the cache (moving them to the deleted + list). Media-specific cache. + + + + + rvargas@chromium.org + + The time that an entry lives in the cache without being accessed until it is + finally purged. Media-specific cache. + + + + + rvargas@chromium.org + + The number of entries that are deleted on a single iteration. Media-specific + cache. + + + + + rvargas@chromium.org + + The number of entries that are evicted on a single iteration. Media-specific + cache. + + + + + rvargas@chromium.org + + The number of entries that are evicted (moved to the deleted list) on a + single iteration. Media-specific cache. + + + + + rvargas@chromium.org + + The number of entries that are evicted per hour of use. Media-specific + cache. + + + + + rvargas@chromium.org + + The time spent moving an entry to the front of the LRU list. Media-specific + cache. + + + + + rvargas@chromium.org + + The percentage of the allowed disk space that we are currently using. + Media-specific cache. + + + + + rvargas@chromium.org + + Number of hours that the cache has been used since last week. Media-specific + cache. + + + + + rvargas@chromium.org + The time spent writing to an entry. Media-specific cache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time for an async IO operation to complete. This covers content Writes + and Reads, measured from the cache thread. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The synchronous portion of an async read. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The synchronous portion of an async write. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of open disk cache entries at any given time. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The total size of all the internal buffers. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of KB accessed from the cache in a 30 seconds interval. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The time spent creating a new entry on the cache. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The size of the data portion of a given entry by the time it is deleted. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of external files that we were unable to delete. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries currently stored on the cache. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries currently stored on the cache, after it is full. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries accessed by the cache in a 30 seconds interval. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average size of an entry. It is only measured after the cache is full, + so evictions are taking place. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + Critical error ids. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The age of the cache (in hours) by the time we reach the size limit. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of hours required to fill up the cache, as measured by the cache + being running. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of KB accessed from the cache in a 30 seconds interval, + by the time we reach the cache size limit. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of entries accessed by the cache in a 30 seconds + interval, by the time we reach the cache size limit. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average size of an entry by the time we reach the cache size limit. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio by the time we fill up the cache. Of course, we started with + an empty cache. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of the cache used by entries of more than 512 KB, by the time + we reach the cache size limit. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent reading the LRU-related portion of an entry. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The current hit ratio. It is only measured after the cache is full, so + evictions are taking place, and data from the fill-up period is not + considered. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each size. To calculate the hit ratio of caches of a + certain size, take the ratio of a bin in this histogram to the same bin in + DiskCache.3.Size2. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each total time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.3.TotalTime. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each use time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.3.UseTime. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Percentage of the index table that is currently used (the cache is full). + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The size of each key. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + Percentage of the cache used by entries of more than 512 KB. It is only + measured after the cache is full, so evictions are taking place. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time to load the main entry data from disk, with a "loaded" + system. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The maximum number of simultaneously open disk cache entries. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The maximum size of the cache. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent opening an entry already on the cache (cache hit). AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The number of pending IO operations (Async IO). AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The time spent reading from an entry. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of re-created deleted entries versus entries that we really + don't know about. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The reason for not sending a full report. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The current size of the cache. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The total time it takes to perform a payload IO operation (AKA, directed to + an entry). This is measured from the IO thread. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + Number of hours that the cache has been used. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent removing deleted entries from the cache. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent removing old entries from the cache. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent evicting entries from the cache (moving them to the deleted + list). AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time that an entry lives in the cache without being accessed until it is + finally purged. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are deleted on a single iteration. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are evicted on a single iteration. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are evicted (moved to the deleted list) on a + single iteration. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are evicted per hour of use. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent moving an entry to the front of the LRU list. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of the allowed disk space that we are currently using. + AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of hours that the cache has been used since last week. AppCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The time spent writing to an entry. AppCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time for an async IO operation to complete. This covers content Writes + and Reads, measured from the cache thread. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The synchronous portion of an async read. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The synchronous portion of an async write. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of open disk cache entries at any given time. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The total size of all the internal buffers. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of KB accessed from the cache in a 30 seconds interval. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent creating a new entry on the cache. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The size of the data portion of a given entry by the time it is deleted. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of external files that we were unable to delete. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The size of the HTML headers of a given entry by the time it is deleted. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries currently stored on the cache. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries currently stored on the cache, after it is full. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries accessed by the cache in a 30 seconds interval. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average size of an entry. It is only measured after the cache is full, + so evictions are taking place. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + Critical error ids. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The age of the cache (in hours) by the time we reach the size limit. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of hours required to fill up the cache, as measured by the cache + being running. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of KB accessed from the cache in a 30 seconds interval, + by the time we reach the cache size limit. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average number of entries accessed by the cache in a 30 seconds + interval, by the time we reach the cache size limit. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The average size of an entry by the time we reach the cache size limit. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio by the time we fill up the cache. Of course, we started with + an empty cache. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of the cache used by entries of more than 512 KB, by the time + we reach the cache size limit. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent reading the LRU-related portion of an entry. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The current hit ratio. It is only measured after the cache is full, so + evictions are taking place, and data from the fill-up period is not + considered. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each size. To calculate the hit ratio of caches of a + certain size, take the ratio of a bin in this histogram to the same bin in + DiskCache.4.Size2. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each total time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.4.TotalTime. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The hit ratio for each use time. To calculate the hit ratio of caches of a + certain age, take the ratio of a bin in this histogram to the same bin in + DiskCache.4.UseTime. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Percentage of the index table that is currently used (the cache is full). + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The size of each key. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + Percentage of the cache used by entries of more than 512 KB. It is only + measured after the cache is full, so evictions are taking place. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time to load the main entry data from disk, with a "loaded" + system. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The maximum number of simultaneously open disk cache entries. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The maximum size of the cache. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent opening an entry already on the cache (cache hit). + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of pending IO operations (Async IO). ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The time spent reading from an entry. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The reason for not sending a full report. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The current size of the cache. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The total time it takes to perform a payload IO operation (AKA, directed to + an entry). This is measured from the IO thread. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + Number of hours that the cache has been used. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent removing old entries from the cache. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time that an entry lives in the cache without being accessed until it is + finally purged. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are evicted on a single iteration. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of entries that are evicted per hour of use. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time spent moving an entry to the front of the LRU list. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of the allowed disk space that we are currently using. + ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of hours that the cache has been used since last week. ShaderCache. + + + + + Please list the metric's owners. Add more owner tags as needed. + The time spent writing to an entry. ShaderCache. + + + + Please list the metric's owners. Add more owner tags as needed. + The percentage of use for blocks of type 0 (links). + + + + Please list the metric's owners. Add more owner tags as needed. + The percentage of use for blocks of type 1 (256 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + The percentage of use for blocks of type 2 (1024 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + The percentage of use for blocks of type 3 (4096 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + The number of used blocks of type 0 (links). + + + + Please list the metric's owners. Add more owner tags as needed. + The number of used blocks of type 1 (256 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + The number of used blocks of type 2 (1024 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + The number of used blocks of type 3 (4096 bytes). + + + + Please list the metric's owners. Add more owner tags as needed. + Number of block-files that we were unable to delete. + + + + Please list the metric's owners. Add more owner tags as needed. + The experiment group for this user. + + + + dmikurube@chromium.org + The size distribution of data stored on the cache. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/dom/histograms.xml b/tools/metrics/histograms/histograms_xml/dom/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5620123fd352caf717fe5d535536535b54cbc3a2 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/dom/histograms.xml @@ -0,0 +1,251 @@ + + + + + + + + + + wychen@chromium.org + + The reason to reject distillability at PageDistillableAfterParsing time. + + + + + wychen@chromium.org + + Score of distillability from AdaBoost model, non-mobile-friendly only. The + score shown here is multiplied by 100. + + + + + wychen@chromium.org + + Score of distillability from AdaBoost model, non-mobile-friendly only. The + score shown here is multiplied by 100. + + + + + mdjones@chromium.org + + "Used" is recorded when the user clicks the infobar to enter + Reader Mode. "Not Used" is recorded when the user clicks the close + button. If there's no user action, nothing is recorded. + + + + + wychen@chromium.org + + Score of long article from AdaBoost model, distillable and + non-mobile-friendly only. The score shown here is multiplied by 100. + + + + + wychen@chromium.org + + Score of long article from AdaBoost model, distillable and + non-mobile-friendly only. The score shown here is multiplied by 100. + + + + + wychen@chromium.org + + Records the "Distillable Type" (mobile-friendly not distillable, + mobile-friendly distillable, non-mobile-friendly not distillable, + non-mobile-friendly distillable) for each analyzed page after loading. + + + + + wychen@chromium.org + + Records the "Distillable Type" (mobile-friendly not distillable, + mobile-friendly distillable, non-mobile-friendly not distillable, + non-mobile-friendly distillable) for each analyzed page after parsing. + + + + + kuan@chromium.org + Records whether a page has distilled data. + + + + katie@chromium.org + gilmanmh@google.com + chrome-a11y-core@google.com + The method a user used to enter reader mode on an article. + + + + katie@chromium.org + gilmanmh@google.com + chrome-a11y-core@google.com + + The method a user used to exit reader mode and return to the original + article. + + + + + mdjones@chromium.org + + Records if the panel became visible at any point after a page was navigated. + + + + + mdjones@chromium.org + + Records the number of words in a distilled page. This only records the first + page of a multi-page article. + + + + + nyquist@chromium.org + + Records the number of words in a distilled page. For articles with multiple + pages, each page is counted separately. + + + + + katie@chromium.org + chrome-a11y-core@chromium.org + + Records the amount of active time a user spent on a distillable page before + switching that page to Reader Mode. Active time is time that the article was + visible, not total time the page was open: the timer is paused when the page + is not visible. This is not recorded when the user opens a distillable page + but does not switch to Reader Mode from that page (via the omnibox icon or + menu option). + + + + + katie@chromium.org + chrome-a11y-core@chromium.org + + Records the amount of active time a user spent on a Reader Mode page. Active + time is the time the Reader Mode page was visible, not the total time the + page was open: the timer is paused when the page is not visible. This is + recorded regardless of how a user enters the page: e.g. using the + forward/back buttons, entering the URL directly, or coming from a + distillable page all start the timer equally. + + + + + yfriedman@chromium.org + + Time spent in DomDistiller's identification of text content. + + + + + yfriedman@chromium.org + Complete time spent in DomDistiller's processing of a page. + + + + wychen@chromium.org + + Time spent in DistillPageImpl(), mostly ExecuteJavaScript(), including + compilation and execution. + + + + + yfriedman@chromium.org + + Time spent in creating DomDistiller's internal representation of the HTML + document. + + + + + yfriedman@chromium.org + + Time spent in DomDistiller's final processing of article content/formatting. + + + + + yfriedman@chromium.org + + Time spent in DomDistiller's processing of article metadata. + + + + + wychen@chromium.org + + Time spent in ExecuteJavaScript() in DomDistiller. It includes JavaScript + code transmission through IPC, parsing, compilation, execution, and + returning the JSON back through IPC. + + + + + wychen@chromium.org + + Records the time from the Reader Mode panel opening to the viewer loaded. + + + + + mdjones@chromium.org + + Records the amount of time a user spent on a Reader Mode Page. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/download/histograms.xml b/tools/metrics/histograms/histograms_xml/download/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..ac9404975a4b0bdf14a453b2a092d8a86f47e574 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/download/histograms.xml @@ -0,0 +1,979 @@ + + + + + + + + + + dtrainor@chromium.org + Downloads extension API function calls. + + + + dtrainor@chromium.org + + Time taken to invoke IAttachmentExecute::Save() excluding the time taken to + instantiate CLSID_AttachmentServices. + + + + + dtrainor@chromium.org + + Overall bandwidth seen for the download. Note that this is measured at the + point at which the file is written, and so will not take into account the + time costs of activities that occur after file write is completed (e.g. safe + browsing scanning). + + + + + xingliu@chromium.org + clank-downloads@google.com + Records why the download is canceled. + + + + xingliu@chromium.org + Types of audio files that are downloaded. + + + + + + dtrainor@chromium.org + Types of images that are downloaded. + + + + xingliu@chromium.org + Types of text files that are downloaded. + + + + + + xingliu@chromium.org + Types of video files that are downloaded. + + + + + + xingliu@chromium.org + + Various individual counts in the download system; see DownloadCountType for + details. + + + + + dtrainor@chromium.org + + Various individual counts in the download system, for example the number of + downloads blocked by throttling from the DownloadRequestLimiter. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@chromium.org + + User chose to save a download which was marked DANGEROUS_FILE. Grouped by + the type of file. + + + + + xingliu@chromium.org + + Records whether the download database is available when database startup + completes, before starting any pending downloads. If the database is + available, it will provide the next download id. Or no download history will + be persisted. + + + + + xingliu@chromium.org + + How long users keep downloaded audio files on disk. Recorded when the + downloaded file is deleted. + + + + + xingliu@chromium.org + + How long users keep downloaded video files on disk. Recorded when the + downloaded file is deleted. + + + + + dtrainor@chromium.org + User actions in chrome://downloads + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records when user is shown the download danger prompt while attempting to + recover a blocked download from chrome://downloads, grouped by the type of + file. + + + + + qinmin@chromium.org + dtrainor@chromium.org + + Records the delay of creating non-incognito download manager after the + download system is initialized. + + + + + qinmin@chromium.org + dtrainor@chromium.org + + Records the approximate memory usage from non-incognito download manager, + after all downloads are loaded. + + + + + + + dtrainor@chromium.org + The size of successfully completed downloads. + + + + qinmin@chromium.org + dtrainor@chromium.org + + The total number of download IDs that are duplicate in the in-progress + downloads DB, capped at 10. + + + + + + + xingliu@chromium.org + The count of HTTP Response codes for download requests. + + + + meacer@chromium.org + jdeblasio@chromium.org + + Records the type of the window.opener origin when a download is initiated in + a tab by that tab's opener (crbug.com/121259). + + + + + qinmin@chromium.org + + Various individual counts related to in-progress download DB. + + + + + jdeblasio@chromium.org + estark@chromium.org + cthomp@chromium.org + + Records file extension of download to support analysis for mixed content + file download blocking. + + + + + jdeblasio@chromium.org + estark@chromium.org + cthomp@chromium.org + + Records security state of downloads to support analysis for mixed content + file download blocking. + + + + + jdeblasio@chromium.org + estark@chromium.org + cthomp@chromium.org + + Records mime-type of download to support analysis for mixed content file + download blocking. This is a temporary metric for investigating differences + in metrics. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + The reason that a download was interrupted. + + + + mahmadi@chromium.org + + Logged at different stages of downloading a USDZ MIME type AR model on iOS. + + + + + eugenebut@chromium.org + + The action that a user takes on a file after it has been successfully + downloaded on iOS. + + + + + eugenebut@chromium.org + mrefaat@chromium.org + + Positive net error codes that happens in the case of download content fetch + failure. + + + + + eugenebut@chromium.org + stkhapugin@chromium.org + + HTTP status code returned when file download completes on iOS. + + + + + eugenebut@chromium.org + + Logged when the download is completed (successfully or not) or in-progress + download was cancelled because of the app termination. This histogram + includes information whether the download was successful and whether or not + the download task was running while the app was active. + + + + + eugenebut@chromium.org + Result when a user attempts to download a file on iOS. + + + + ewannpv@chromium.org + eugenebut@chromium.org + + Result when a user attempts to present the download UI on iOS. Looged when + download is created. + + + + + ewannpv@chromium.org + eugenebut@chromium.org + + Result when the download UI is prexsented on iOS. Values indicate if Google + Drive is installed and whether or not Install Google Drive promo was shown. + Logged when download is updated. + + + + + eugenebut@chromium.org + + MIME type of a download response. Logged when the download UI was offered by + the browser to the user. + + + + + eugenebut@chromium.org + + Result when a user attempts to download a PassKit file on iOS. + + + + + eugenebut@chromium.org + sdefresne@chromium.org + + The user discarded in-progress download and replaced with the new one. Only + recorded after the user interacts with a dialog offering the choice between + replacing an in-progress download versus downloading separately to a new + filename. + + + + + eugenebut@chromium.org + sdefresne@chromium.org + Result of an attempt to present Add Passes dialog on iOS. + + + + mahmadi@chromium.org + + Result of an attempt to present a USDZ MIME type AR model on iOS. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records events for download later feature in download core code. + + + + + xingliu@chromium.org + clank-downloads@google.com + + The size of downloads when the user tries to download at a scheduled time. + Recorded when the positive button in download later dialog is clicked. + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The user selection in the download later dialog. Recorded when the user + starts a download, or clicking the change button on download infobar and + download home UI. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records events for download later feature in download Android UI. + + + + + + + dtrainor@chromium.org + qinmin@chromium.org + xingliu@chromium.org + Records events for local media metadata parsing. + + + + + + dtrainor@chromium.org + qinmin@chromium.org + xingliu@chromium.org + + Records events when using media parser to analyze local media files. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + Network connection type when a download is completed. + + + + + + dtrainor@chromium.org + xingliu@chromium.org + Network connection type when starting a new download. + + + + + + dtrainor@chromium.org + chrome-analysis-team@google.com + + Invocation count for methods of opening a download. For some file types, + Chrome defaults to opening the file in the browser instead of invoking the + system handler. The user has the option of overriding this behavior. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + dtrainor@chromium.org + The number of unopened downloads, when one is opened. + + + + xingliu@chromium.org + + When parallel downloading feature is enabled, a download may be created as + parallel download or fall back to normal download based on various factors. + Records the total number of parallel and non-parallel downloads created when + parallel downloading feature is enabled. Also records the reason why a + parallel download falls back to normal download. The reasons are not + mutually exclusive. + + + + + qinmin@chromium.org + xingliu@chromium.org + + Records the received failure reason after sending a parallel download + request. + + + + + xingliu@chromium.org + + Records if the byte stream reader of a subsequent request is successfully + added to the download sink. + + + + + xingliu@chromium.org + + The total number of requests sent for a parallel download, including the + initial request. + + + + + xingliu@chromium.org + clank-downloads@google.com + The download time for a parallelizable download. + + + + xingliu@chromium.org + clank-downloads@google.com + The download size of a parallelizable download. + + + + qinmin@chromium.org + + For parallelizable download, average disk bandwidth seen for different + settings. If a download was ever paused, this is not recorded. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The download path generation behavior which happens before download path + validation in download target determination process. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The download path validation result before the final download target is + determined. + + + + + pmonette@chromium.org + alewoolf@microsoft.com + + Whether a connection error has happened for the QuarantineService. + + + + + calamity@chromium.org + dbeam@chromium.org + + Records the time taken to load the downloads Web UI and render (at least) a + screen full of items. This is roughly equivalent to 'time to first + meaningful paint' for the downloads page. + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Records whenever max auto-resumption limit was reached for a download. + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Records the last interrupt reason for this download when the download + reaches auto-resumption limit. + + + + + shaktisahu@chromium.org + clank-downloads@google.com + Records the last interrupt reason for this download. + + + + shaktisahu@chromium.org + clank-downloads@google.com + Records whether a resumption was due to user. + + + + qinmin@chromium.org + xingliu@chromium.org + + Records the interrupt reason when download is restarting from the beginning + during resumption. + + + + + dtrainor@chromium.org + + Events (e.g. Started, Cancelled, Finished, Write to Completed file, Write to + Failed file) occuring within the state machine of a SavePackage operation. + + + + + + + xingliu@chromium.org + clank-downloads@google.com + Records a failed database operation. + + + + + + xingliu@chromium.org + clank-downloads@google.com + Records a successful database operation. + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The total number of database records used by download service, and the + number of records in each entry state. + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The interrupt reason for failed downloads in download service. + + + + + dtrainor@chromium.org + xingliu@chromium.org + An action the download service took on an active download. + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records how many attempts have taken place at the time of a retry for a + download in the Download Service. This differs from + Download.Service.Entry.ResumptionCount, which records resumptions not + complete restarts. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The number of files that have been deleted by external application or the + user, when performing clean up tasks in download service. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The number of failed file deletion attempts, when performing clean up tasks + in download service. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The number of files successfully deleted, when performing clean up tasks in + download service. + + + + + + + xingliu@chromium.org + + The error code when failed to create the download directory. + + + + + xingliu@chromium.org + + The percentage of free disk space to total disk space. Recorded during + initialization of the file monitor. + + + + + + + xingliu@chromium.org + + The lifestime of a download file, which begins from the download completion + to the file being deleted by the clean up task. + + + + + + + xingliu@chromium.org + The time to complete the download in download service. + + + + xingliu@chromium.org + The completion type for downloads in download service. + + + + + + shaktisahu@chromium.org + + The reason for suspending a download right after the upload data is received + from the client. Every pause will result in two entries in the histogram: + ANY and a more specific reason. + + + + + + + shaktisahu@chromium.org + + The reason for pausing an in-progress download. Every pause will result in + two entries in the histogram: ANY and a more specific reason. + + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + Records the API calls on download service. + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + The start up result of the download service. + + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The platform background tasks used by download service will invoke native + functions after being scheduled. The tasks may be aborted or canceled. This + metric records the status of background tasks when native functions are + invoked. + + + + + shaktisahu@chromium.org + + Records if the entry has been deleted for some reason while we are waiting + for the client to respond with the upload data. + + + + + + + shaktisahu@chromium.org + clank-downloads@google.com + + The download service uses a single code path for both downloading and + uploading data. This metric records whether a given request includes upload + data. It is recorded upon starting a download or upload, immediately after + the client indicates whether the request includes upload data. + + + + + sdy@chromium.org + + Events related to dragging a completed download from the shelf, which + represents dragging a reference to the downloaded file. + + + + + dtrainor@chromium.org + + User saw the confirm prompt to save a download which was marked dangerous. + Grouped by the type of danger. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@chromium.org + + A download warning was shown in the shelf. Note that some downloads may not + be shown on the shelf, e.g., if chrome://downloads is already open when the + download completes, or if an extension is using the downloads API. Grouped + by the type of danger. + + + + + + + xingliu@chromium.org + clank-downloads@google.com + + The initiation source (if initiated within the above-content layer of + chrome) for a download. + + + + + shaktisahu@chromium.org + Content types of the downloads. + + + + shaktisahu@chromium.org + clank-downloads@google.com + + Content types of the downloads that are started in non-incognito profile. + + + + + drubery@chromium.org + chrome-safebrowsing-team@chromium.org + + User chose to save a download which was marked dangerous. Grouped by the + type of danger. + + + + + + + dtrainor@chromium.org + qinmin@chromium.org + xingliu@chromium.org + Records events for local video thumbnail retrieval. + + + + dtrainor@chromium.org + qinmin@chromium.org + Records the OS error code when moving a file on windows. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/enterprise/histograms.xml b/tools/metrics/histograms/histograms_xml/enterprise/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..953f78d8940cf06c3498362936a0eea67f97e899 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/enterprise/histograms.xml @@ -0,0 +1,1684 @@ + + + + + + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + The way device is joined to the Active Directory domain. This will be + recorded during successful enterprise enrollment and domain join. + + + + + twellington@google.com + tedchcoc@chromium.org + + Records the time it takes to retrieve applicaton restrictions from the + system. Android only. + + + + + twellington@google.com + tedchcoc@chromium.org + + Records the time it takes to retrieve applicaton restrictions from the + system when the retrieved Bundle is empty. Android only. + + + + + twellington@google.com + tedchcoc@chromium.org + + Records the time it takes to retrieve applicaton restrictions from the + system when the retrieved Bundle is not empty. Android only. + + + + + + + igorcov@chromium.org + vsavu@chromium.org + + Consistency between TPM lock state and absence/presence of install + attributes at boot. + + + + + + + pmarko@chromium.org + igorcov@chromium.org + + Duration of the bucket download part of the auto-enrollment protocol. + + + + + + + pmarko@chromium.org + igorcov@chromium.org + + Time since the user logged in until the auto-enrollment protocol completed. + 0 is sampled when the protocol is done by the time the user logs in. + + + + + + + amraboelkher@google.com + mpolzer@google.com + + Duration of the hash dance to determine enrollment state of the device. Only + recorded if the hash dance finished successfully. + + + + + amraboelkher@google.com + mpolzer@google.com + + Comparison of hash dance and private set membership results used to + determine the initial enrollment state of the device. + + + + + amraboelkher@google.com + mpolzer@google.com + + The status of a private set membership request. This request is used to + determine the initial enrollment state of the device. + + + + + amraboelkher@google.com + mpolzer@google.com + + Duration of the private set membership request to determine enrollment state + of the device. Only recorded if it finished successfully. + + + + + + + pmarko@chromium.org + igorcov@chromium.org + Total duration time of the auto-enrollment protocol. + + + + + + pmarko@chromium.org + igorcov@chromium.org + + Network error code (if applicable) for auto-enrollment requests. + + + + + + + pmarko@chromium.org + igorcov@chromium.org + URL fetcher status for auto-enrollment requests. + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting CBCM policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events measuring effectiveness of refreshing CBCM policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + + + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting status of executed CBCM remote commands. The metric + includes only signed CBCM remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting status of executed CBCM remote commands. The metric + includes only unsigned CBCM remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting received CBCM remote commands. The metric includes + signed CBCM remote commands, both valid and invalid. Valid remote command is + counted by its type. Invalid remote command is counted by a reason why it is + considered invalid (e.g. unknown type or duplication). + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting received CBCM remote commands. The metric includes + unsigned CBCM remote commands, both valid and invalid. Valid remote command + is counted by its type. Invalid remote command is counted by a reason why it + is considered invalid (e.g. unknown type or duplication). + + + + + anthonyvd@google.com + cbe-eng@google.com + + Events for counting CBCM remote commands invalidations received with and + without payloads. Invalidations indicate that there is a remote command to + execute. Payloads provide context about the remote commands update, but may + be absent if dropped by the invalidation service. + + + + + zmin@chromium.org + src/chrome/browser/enterprise/reporting/OWNERS + + Recorded when cloud extension request pending list is updated. Note that + when multiple requests are added or removed together, there will be only one + event recorded. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + The proto size of the basic Chrome browser cloud management reporting + request. When a report is separated into multiple requests, all of them + contain the basic request. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + The number of request for one Chrome browser cloud management report. A + report is separated into multiple requests when it's too large. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + The proto size of each Chrome browser cloud management reporting request. It + includes the requests which are more than 5MB and discarded. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + The upload result for each cloud reporting request. Note that there may be + multiple requests per report. Also, one request may creates multiple data + point due to retry. + + + + + + + grt@chromium.org + src/chrome/browser/enterprise/reporting/OWNERS + + The trigger detected by the ReportScheduler responsible that led to an + attempt to upload an enterprise report. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device local account policy invalidations received with + and without payloads. Invalidations indicate that a policy has been updated + and should be refreshed. Payloads provide context about the policy update, + but may be absent if dropped by the invalidation service. + + As opposed to current histogram, Enterprise.DevicePolicyInvalidations2 + counts only events of device policy invalidations. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing device local account policy + when invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. + + As opposed to current histogram, Enterprise.DevicePolicyRefresh3 counts only + events of refreshing device policies. + + + + + + + emaxx@chromium.org + poromov@chromium.org + + Result of the device ID validation in the device policy blob. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. + + As opposed to current histogram, + Enterprise.DeviceLocalAccountPolicyInvalidations2 counts only events of + device local account policy invalidations. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. + + As opposed to current histogram, Enterprise.DeviceLocalAccountPolicyRefresh3 + counts only events of refreshing device local account policies. + + + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting status of executed device remote commands. The metric + includes only signed device remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting status of executed device remote commands. The metric + includes only unsigned device remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting received device remote commands. The metric includes + signed device remote commands, both valid and invalid. Valid remote command + is counted by its type. Invalid remote command is counted by a reason why it + is considered invalid (e.g. unknown type or duplication). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting received device remote commands. The metric includes + unsigned device remote commands, both valid and invalid. Valid remote + command is counted by its type. Invalid remote command is counted by a + reason why it is considered invalid (e.g. unknown type or duplication). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device remote commands invalidations received with and + without payloads. Invalidations indicate that there is a remote command to + execute. Payloads provide context about the remote commands update, but may + be absent if dropped by the invalidation service. + + Metric is similar to Enterprise.DevicePolicyInvalidations2. Device local + account scope does not exist for remote commands so there is no metric for + remote commands similar to + Enterprise.DeviceLocalAccountPolicyInvalidations2. + + + + + poromov@chromium.org + managed-devices@google.com + + Recorded every time policy file is missing or corrupted on Chrome OS. Should + be compared to Enterprise.DeviceSettings.UpdatedStatus as happens only if + status is STORE_NO_POLICY and device being not managed. + + + + + poromov@chromium.org + managed-devices@google.com + + Recorded every time as DeviceSettingsProvider updates its current state. + Used to compare rate of Enterprise.DeviceSettings.MissingPolicyMitigated + event. + + + + + poromov@chromium.org + managed-devices@google.com + + Number of retries the client did to execute a DeviceManagementServer + request. It's recorded after the request has been completed, either + successfully after 0 or more retries, with a failure (too many retries or + non-retriable error) or with a server error. + + + + + + + igorcov@chromium.org + vsavu@chromium.org + + Whether loading of device policy from file on an enterprise-enrolled + (checked against install_attributes.pb) Chrome OS device yields an + enterprise policy with a DM token. Filled once during session startup, after + first successful device policy read. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to device enrollment on new installs of Chrome OS devices. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to attestation-based enrollment (Zero-Touch) of Chrome OS + devices. + + + + + antrim@chromium.org + raleksandrov@google.com + cros-oac@google.com + + Events related to Chrome OS enterprise enrollment automated by OOBE + configuration. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to forced re-enrollment (FRE) of Chrome OS devices. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to attestation-based re-enrollment (Auto RE) of Chrome OS + devices. + + + + + raleksandrov@google.com + pmarko@chromium.org + cros-oac@google.com + + Events related to forced initial enrollment of Chrome OS devices during the + first startup of a device. + + + + + raleksandrov@google.com + pmarko@chromium.org + cros-oac@google.com + + Events related to attestation-based initial enrollment (Zero-Touch) of + Chrome OS devices during the first startup of a device. + + + + + raleksandrov@google.com + pmarko@chromium.org + cros-oac@google.com + + Events related to manual fallback from attestation-based initial enrollment + (Zero-Touch) of Chrome OS devices during the first startup of a device. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to manual fallback from attestation-based re-enrollment (Auto + RE) of Chrome OS devices. + + + + + raleksandrov@google.com + cros-oac@google.com + + Events related to Chrome OS enterprise enrollment recovery. Note that this + only covers cases in which prior to recovery, the "private owner" + of the device had UMA stats enabled. + + + + + raleksandrov@google.com + cros-oac@google.com + + Elapsed time from *after* GAIA login until enrollment was cancelled. + + + + + raleksandrov@google.com + cros-oac@google.com + + Elapsed time from *after* GAIA login until enrollment failed. + + + + + raleksandrov@google.com + cros-oac@google.com + + Elapsed time from *after* GAIA login until enrollment succeeded. + + + + + emaxx@chromium.org + poromov@chromium.org + rsorokin@chromium.org + + Chrome OS only. Whether the successful locking of install attributes reused + the previously existing locked attributes, or a fresh lock has being held. + + + + + anthonyvd@google.com + chrome-enterprise-team-core@google.com + + Events for counting CBCM policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. Subset of + "Enterprise.CBCMPolicyInvalidations". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + anthonyvd@google.com + chrome-enterprise-team-core@google.com + + Events measuring effectiveness of refreshing CBCM policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + Subset of "Enterprise.CBCMPolicyRefresh". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device local account policy invalidations received with + and without payloads. Invalidations indicate that a policy has been updated + and should be refreshed. Payloads provide context about the policy update, + but may be absent if dropped by the invalidation service. Subset of + "Enterprise.DeviceLocalAccountPolicyInvalidations2". Gets recorded + only when FCMInvalidationService is used as InvalidationService. + + As opposed to current histogram, + Enterprise.FCMInvalidationService.DevicePolicyInvalidations2 counts only + events of device policy invalidations. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing device local account policy + when invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. Subset of + "Enterprise.DeviceLocalAccountPolicyRefresh3". Gets recorded only + when FCMInvalidationService is used as InvalidationService. + + As opposed to current histogram, + Enterprise.FCMInvalidationService.DevicePolicyRefresh3 counts only events of + refreshing device policies. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. Subset of + "Enterprise.DevicePolicyInvalidations2". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + As opposed to current histogram, + Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyInvalidations2 + counts only events of device local account policy invalidations. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. Subset of "Enterprise.DevicePolicyRefresh3". + Gets recorded only when FCMInvalidationService is used as + InvalidationService. + + As opposed to current histogram, + Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyRefresh3 counts + only events of refreshing device local account policies. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting user policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. Subset of + "Enterprise.PolicyInvalidations". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Tracks the result of registration for policy invalidations. It will fail + when duplicate invalidation names are used for different policies due to + http://b/119860379. Subset of + "Enterprise.PolicyInvalidationsRegistrationResult". Gets recorded + only when FCMInvalidationService is used as InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + Subset of "Enterprise.PolicyRefresh2". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + wenyufu@chromium.org + twellington@chromium.org + + Records the time it takes to retrieve applicaton restrictions from the + system using an AsyncTask. Recording during first run experience on Android + only. + + + + + skym@chromium.org + twellington@chromium.org + wenyufu@chromium.org + + Records the time it takes to retrieve applicaton restrictions from the + system using an AsyncTask. Recording during first run experience on Android + only. Has a bigger range (0-3 minutes) than the non-Medium version. + + + + + igorcov@chromium.org + poromov@chromium.org + + Result of a single attempt to signal a device heartbeat, which is used for + monitoring the device connectivity. By default heartbeats per a single + device are sent every 2 minutes. + + + + + pmarko@chromium.org + igorcov@chromium.org + + Chrome OS only. Encodes if initial enrollment should be done, and if not, + why. This histogram is recorded when the Auto Enrollment Check screen is + reached in the Chrome OS Out Of The Box Experience (OOBE) sequence and the + device has not been enrolled or in consumer mode before, i.e. when the + 'check_enrollment' and 'ActivateDate' VPD keys are not present. + + + + + emaxx@chromium.org + igorcov@chromium.org + vsavu@chromium.org + + Chrome OS only. Result of checking if device policy files are valid when + reading the device policy data. + + + + + mnissler@chromium.org + + Number of policies loaded at startup on iOS, and when a change is detected + at runtime. + + + + + emaxx@chromium.org + igorcov@chromium.org + + Chrome OS only. The result of D-Bus call to lock device to single user. + Estimated that till version M86 we should get enough stats to understand if + there are big problems with the D-Bus call. + + + + + rogerta@chromium.org + zmin@chromium.org + + Time since the enrollment request was made until an error is returned from + the server. + + + + + rogerta@chromium.org + zmin@chromium.org + + Time since the enrollment request was made until a successful enrollment + response is returned from the server. + + + + + rogerta@chromium.org + zmin@chromium.org + The result of machine level user cloud policy enrollment. + + + + rogerta@chromium.org + zmin@chromium.org + + Records whether the machine level user cloud policy enrollment dialog is + shown to the user and the action they took. + + + + + rogerta@chromium.org + zmin@chromium.org + + The length of time the machine level user cloud policy enrollment dialog was + visible to the user. + + + + + domfc@chromium.org + zmin@chromium.org + + Records whether a browser unenrollment was completed succcessfully by + writing an invalid DM token to storage or not. + + + + + domfc@chromium.org + webprotect-team@google.com + + Records the size (in bytes) of data that might have been scanned by the + OnBulkDataEntry Enterprise Connector. Is is logged once per user action that + would trigger this Connector. + + + + + mnissler@chromium.org + Result of the OpenNetworkConfiguration policy validation. + + + + mnissler@chromium.org + + A set of enterprise policy rules that are in use. This is recorded every 24 + hours and at startup, if the last recording was earlier than a day before. + + + + + ydago@chromium.org + + A set of enterprise policy rules that are ignored because they do not share + the highest priority from their policy atomic group. This is recorded at + startup, then every 24 hours. If chrome is not running at the 24 hours mark, + this will be recorded at the next startup. + + + + + ydago@chromium.org + + A set of policy atomic groups that have at least one policy disabled because + of its source. This is recorded at startup, then every 24 hours. If chrome + is not running at the 24 hours mark, this will be recorded at the next + startup. + + + + + atwilson@chromium.org + + Boolean tracking whether there is a valid policy signing key on disk. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting user policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. + + + + + asumaneev@google.com + managed-platforms@google.com + + Tracks the result of registration for policy invalidations. It will fail + when duplicate invalidation names are used for different policies due to + http://b/119860379. + + + + + mnissler@chromium.org + + Time since startup of the cloud policy code until the policy invalidation + service first reported its online status. + + + + + atwilson@chromium.org + Tracking the results of policy key verification. + + + + mnissler@chromium.org + + Load status from the policy loaders which pull policy settings from the + underlying platform, such as Windows Group Policy. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + + + + + rbock@google.com + igorcov@chromium.org + Time since last device policy fetch. + + + + zmin@chromium.org + pastarmovj@chromium.org + Time since last machine level user policy fetch. + + + + rbock@google.com + igorcov@chromium.org + Time since last user policy fetch. + + + + poromov@chromium.org + Tracking the results of policy user verification. + + + + isandrk@chromium.org + sduraisamy@chromium.org + + Extensions (and apps) are quite restricted in public sessions for security + and privacy concerns - some permissions are blocked which means the + extension itself is blocked (prevented from loading). This histogram counts + requested permissions on extension installation in public sessions (both + installed and blocked extensions). + + + + + marcgrimme@chromium.org + managed-devices@google.com + + A public session starts when a user signs in using the policy configured + public account. It stops when the user signs out. Session length is the + duration between the start and stop events. It is recorded during signing + out and reported on the next chrome run. This metric tracks the recorded + session length rounded down to the nearest 10-minute bucket and capped at 24 + hours. + + + + + rogerta@chromium.org + + Number of retries the client did to execute a real-time reporting upload + request. It's recorded after the request has been completed, either + successfully after 0 or more retries, with a failure (too many retries or + non-retriable error) or with a server error. + + + + + marcgrimme@chromium.org + managed-devices@google.com + + A regular user session starts when a user signs in using his/her user + account. It stops when the user signs out. Session length is the duration + between the start and stop events. It is recorded during signing out and + reported on the next chrome run. This metric tracks the recorded session + length on an enrolled device rouned down to the nearest 10-minute bucket and + capped at 24 hours. + + + + + antrim@chromium.org + + When an enterprise admin attempts to establish a remote session to a device + running in kiosk mode, the command will fail if device is not considered + idle. This histogram is emitted when that happens. + + + + + antrim@chromium.org + + When an enterprise admin attempts to establish a remote session to a device + running in kiosk mode, it is possible to override usual idleness check and + connect anyway. + + + + + asumaneev@google.com + managed-platforms@google.com + + Tracks whether remote commands invalidator registered for corresponding + invalidations. In case of success the invalidator is able to receive + incoming invalidations. + + Metric is similar to Enterprise.PolicyInvalidationsRegistrationResult. + + + + + + + emaxx@chromium.org + igorcov@chromium.org + + On Chrome OS, the response obtained to retrieve policy request. + + + + + ayaelattar@chromium.org + poromov@chromium.org + + Shows which system features are set to be disabled by + SystemFeaturesDisableList policy. Recorded when the policy preference is + updated with a new system feature. No-op updates aren't counted. + + + + + poromov@chromium.org + Result of a single attempt to upload system logs. + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting device policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. Subset of + "Enterprise.DevicePolicyInvalidations". Gets recorded only when + TiclInvalidationService is used as InvalidationService; + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. Subset of "Enterprise.DevicePolicyRefresh2". + Gets recorded only when TiclInvalidationService is used as + InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting user policy invalidations received with and without + payloads. Invalidations indicate that a policy has been updated and should + be refreshed. Payloads provide context about the policy update, but may be + absent if dropped by the invalidation service. Subset of + "Enterprise.PolicyInvalidations". Recorded only when + TiclInvalidationService was used as InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Tracks the result of registration for policy invalidations. It will fail + when duplicate invalidation names are used for different policies due to + http://b/119860379. Subset of + "Enterprise.PolicyInvalidationsRegistrationResult". Gets recorded + only when TiclInvalidationService is used as InvalidationService. + + + + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + Subset of "Enterprise.PolicyRefresh2". Recorded only when + TiclInvalidationService was used as InvalidationService. + + + + + bmalcolm@chromium.org + managed-devices@google.com + + Number of retries the client did to execute an UploadJob. It's recorded + after the request has been completed, either successfully after 0 or more + retries, with a failure because of too many retries or if the UploadJob is + interrupted (destroyed before it could succeed or fail). + + + + + atwilson@chromium.org + + Result of the attempted policy load during profile initialization. + + + + + atwilson@chromium.org + + Result of validating the policy that has just been loaded from disk. + + + + + atwilson@chromium.org + + Result of validating the policy sent down from the server, before writing to + disk. + + + + + agawronska@chromium.org + michaelpg@chromium.org + Failure reason for OAuth token fetch for child user. + + + + mnissler@chromium.org + Initialization delay due to loading the user policy cache. + + + + mnissler@chromium.org + Policy client error during initial policy fetch. + + + + mnissler@chromium.org + Delay for registering the client with the policy server. + + + + mnissler@chromium.org + Delay for minting an OAuth2 acccess token. + + + + mnissler@chromium.org + Delay for fetching policy from the policy server. + + + + mnissler@chromium.org + Total delay for the initial policy fetch. + + + + igorcov@chromium.org + asumaneev@google.com + Service error during OAuth2 access token fetch. + + + + mnissler@chromium.org + Network error during OAuth2 access token fetch. + + + + hendrich@chromium.org + managed-devices@google.com + Re-registration results after failed policy fetch. + + + + emaxx@chromium.org + + Session abort due to a fatal error of Chrome OS user policy initialization. + + + + + mnissler@chromium.org + Source of policy validation errors on Chrome OS. + + + + mnissler@chromium.org + + Validation result when loading user policy from the policy store. + + + + + mnissler@chromium.org + + Validation result when writing user policy to the policy store. + + + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting status of executed user remote commands. The metric + includes only signed user remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting status of executed user remote commands. The metric + includes only unsigned user remote commands. Reports a final status of + finished remote command (e.g. success, failure or termination). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting received user remote commands. The metric includes + signed user remote commands, both valid and invalid. Valid remote command is + counted by its type. Invalid remote command is counted by a reason why it is + considered invalid (e.g. unknown type or duplication). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting received user remote commands. The metric includes + unsigned user remote commands, both valid and invalid. Valid remote command + is counted by its type. Invalid remote command is counted by a reason why it + is considered invalid (e.g. unknown type or duplication). + + + + + asumaneev@google.com + managed-platforms@google.com + + Events for counting user remote commands invalidations received with and + without payloads. Invalidations indicate that there is a remote command to + execute. Payloads provide context about the remote commands update, but may + be absent if dropped by the invalidation service. + + Metric is similar to Enterprise.PolicyInvalidations. + + + + + xiyuan@chromium.org + sduraisamy@chromium.org + Tracks the sign-in events on an enrolled device. + + + + atwilson@chromium.org + + Choice the user made when presented with enterprise signin dialog. + + + + + igorcov@chromium.org + tnagel@chromium.org + + The status code (exit code or signal) from sanity check of RW_VPD read and + matching the contents with data from dump_vpd_log (Chrome OS). + + + + + igorcov@chromium.org + tnagel@chromium.org + + The status code (exit code or signal) from VPD update operation (Chrome OS). + + + + + mnissler@chromium.org + + Delay incurred by the token fetching step of the wildcard login check. + + + + + mnissler@chromium.org + Total delay incurred by the wildcard login check. + + + + mnissler@chromium.org + + Delay incurred by the user info fetching step of the wildcard login check. + + + + + pastarmovj@chromium.org + rogerta@chromium.org + + Whether the machine is part of an AD domain. This check is performed once at + start-up on Windows. + + + + + olsen@chromium.org + + A set of policy rules that failed validation due to unparsable JSON, or JSON + that did not match the schema. This validation happens on start-up and when + the policy has changed. + + + + + pastarmovj@chromium.org + + A set of policy rules that were ignored due to integrity violations while + parsing the policy data which happens on start-up and when the policy has + changed. + + + + + pastarmovj@chromium.org + zmin@chomium.org + + The number of disabled policy entries on Windows due to integrity violations + while parsing the policy data which happens on start-up and when the policy + has changed. + + + + + mad@chromium.org + + Whether the machine is joined to an AD domain. This check is performed once + at start-up on Windows. + + + + + rogerta@chromium.org + + Whether the machine is considered an enterprise user. An enterprise user is + either in a domain or is managed via MDM. This check is performed once at + start-up on Windows. + + + + + twellington@google.com + tedchcoc@chromium.org + + On Android (OS version Lollipop+): Whether the device has a "device + owner" app installed. This check is performed once on application + start-up. + + + + + mad@chromium.org + + Whether the full machine name is the same as the short one, identifying a + local machine. This check is performed once at start-up on Windows. + + + + + mad@chromium.org + + Whether the currently logged in user is a local user or not, based on its + SAM compatible user name and machine name. This check is performed once at + start-up on Windows. + + + + + rogerta@chromium.org + pastarmovj@chromium.org + + On Windows: Whether the machine is managed via MDM. On macOS: Whether Chrome + found a file of managed policies to follow. On Android (OS version + Lollipop+): Whether the device has a profile owner app. This check is + performed once on application start-up. + + + + + twellington@google.com + tedchcoc@chromium.org + + Records the time it takes to calculate whether there is a profile owner app + on the device. Android only. + + + + + avi@chromium.org + pastarmovj@chromium.org + + On the Mac: Whether the current user has an enterprise identity in Open + Directory. This check is performed once at start-up. + + + + + avi@chromium.org + pastarmovj@chromium.org + + On the Mac: Whether the machine is joined to a domain. This check is + performed once at start-up. + + + + + avi@chromium.org + pastarmovj@chromium.org + + On the Mac: Whether the machine is managed via MDM, with data obtained via a + new method (profiles) that is only available in 10.13.4 or later. This check + is performed once at start-up. + + + + + avi@chromium.org + pastarmovj@chromium.org + + On the Mac: Whether the machine is managed via MDM, with data obtained via + an old method (system_profiler). This check is performed once at start-up. + + + + + rogerta@chromium.org + + Whether we could obtain the address of the NetGetJoinInformation function. + This check is performed once at start-up on Windows. + + + + + pastarmovj@chromium.org + rogerta@chomium.org + + The rough Windows suite we are running on. This check is performed once at + start-up on Windows. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/event/histograms.xml b/tools/metrics/histograms/histograms_xml/event/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..8c8b56ef6e045b0e65f3ff5a4048bc0e2e4862b2 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/event/histograms.xml @@ -0,0 +1,1622 @@ + + + + + + + + + + tdresser@chromium.org + + Time between initiation of any input event and the renderer receiving and + starting to process it. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + + mustaq@chromium.org + nzolghadr@chromium.org + + Tracks the number of Android MotionEvents with ACTION_DOWN or + ACTION_POINTER_DOWN or ACTION_BUTTON_PRESS for each ToolType (unknown, + finger, mouse or stylus). + + Team: input-dev@chromium.org. + + + + + yigu@chromium.org + event-targeting@chromium.org + + Tracks how many clients were queried (asynchronously) to determine the + target for an input event. + + + + + yigu@chromium.org + + Tracks how long it takes for a client to respond to an asynchronous request + to find a target for an input event. + + Team: event-targeting@chromium.org. + + + + + nzolghadr@chromium.org + + Whether click target was affected by DOM manipulation or not. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + + Whether click target was affected by interactive element being in the + ancestor path. + + Team: input-dev@chromium.org. + + + + + tbuckley@chromium.org + + The number of down events received per destination, input and form factor + combination. + + Input is down events generated by mouse/touch/stylus. Form factor is down + events generated by clamshell/touchviewLandscape/touchviewPortrait. + Destination: Every down event that is targeted to each destination will be + counted including those that don't have an effect. For example: Tapping on a + disabled button inside the browser frame will be treated as down events on + browser window. + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + For each 10 second window, reports the fraction of the time there was no + user input. We consider there to be no user input if we haven't received any + events for > 50ms. + + + + + wjmaclean@chromium.org + + Record whether we unexpectedly encounter an empty gesture queue while + routing gesture events to frames' renderers: true => empty queue, false + => non-empty queue. + + + + + wjmaclean@chromium.org + kenrb@chromium.org + + The size of the TouchEventAckQueue, recorded each time we process an event + ack (the queue usually, but not always, decreases in size during ack + processing). Ideally this queue will operate at length close to zero, + depending on how long it takes for events to travel to a renderer and be + processed and an ack sent back. As the size increases it indicates decreased + responsiveness of renderers with respect to touch events. One purpose of + this metric is to develop a sense of normal queue sizes for different + platforms. Initially we expect queue length to be less than 20 most of the + time, but this is a guess. + + + + + kuscher@google.com + + The gesture-events recognized and dispatched by the browser gesture + recognizer. This replaces Ash.GestureCreated, which did not record events on + Android and Windows. + + Team: input-dev@chromium.org. + + + + + dtapuska@chromium.org + + For each hit test, records whether it was a hit or miss, and why. + + Team: input-dev@chromium.org. + + + + + dtapuska@chromium.org + + For hit tests that are validated, records whether it was correct or not, and + why. + + Team: input-dev@chromium.org. + + + + + dtapuska@chromium.org + + For hit tests that are invalid, records the score (a series of bits + indicating what was matched and what wasn't). + + Team: input-dev@chromium.org. + + + + + eirage@chromium.org + axantoine@google.com + + Overshoot distance in pixels between a predicted scroll position and the + corresponding interpolated real scroll position that occurred at the + prediction time. + + Team: input-dev@chromium.org. + + + + + eirage@chromium.org + axantoine@google.com + + Euclidean distance in pixels between two successive variations of touch + scroll deltas which are the difference between a predicted scroll position + and its corresponding interpolated real position that occurred at prediction + time. + + Team: input-dev@chromium.org. + + + + + eirage@chromium.org + axantoine@google.com + + Undershoot distance in pixels between a predicted scroll position and the + corresponding interpolated real scroll position that occurred at the + prediction time. + + Team: input-dev@chromium.org. + + + + + eirage@chromium.org + axantoine@google.com + + Euclidean distance in pixels between two successive variations of touch + scroll deltas which are the difference between a predicted scroll position + and the interpolated real position that occurred at frame time. + + Team: input-dev@chromium.org. + + + + + eirage@chromium.org + axantoine@google.com + + Boolean that indicates whether the prediction is in the same direction as + the real trajectory at the same prediction time. True means the direction is + not the same (wrong direction). + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the OS receiving a keyboard event and the resulting GPU frame + swap. If no swap was induced by the event, no recording is made. Only + recorded for key presses. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between the OS receiving a mouse event and the resulting GPU frame + swap. If no swap was induced by the event, no recording is made. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between the OS receiving a touchpad pinch event and the resulting GPU + frame swap. If no swap was induced by the event, no recording is made. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between the OS receiving a touchpad pinch event and the resulting GPU + frame swap. If no swap was induced by the event, no recording is made. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between the OS receiving a touchpad pinch event and RenderWidgetHost + sending event to render. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Duration of a non-resurive hitTest operation. The hit test is non-recursive + when the AllowChildFrameContent flag is clear. See also + Event.Latency.HitTestRecusrive. + + Team: paint-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Duration of a recursive hitTest operation. The hit test is recursive when + the AllowChildFrameContent flag is set. See also Event.Latency.HitTest. + + Team: paint-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between input event received by OS and sent to Chrome. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sullivan@chromium.org + input-dev@chromium.org + + For Mac, a version of Event.Latency.OS that has the positive values it would + contain if ValidateEventTimeClock() were not called on the timestamps. + + This metric is intended to debug http://crbug.com/1039833, where very high + numbers are seen for PageLoad.InputDelay3. The units of this metric are the + same as PageLoad.InputDelay3 for consistency while debugging. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between initial creation of a wheel event and the generated + ScrollUpdate gesture event is handled on main/impl thread (specified by + suffix). If no swap was induced by the ScrollUpdate gesture event, no + recording is made. Unlike Event.Latency.ScrollUpdate.Wheel.TimeToHandled2 + this metric includes the first GSU of every scrolling sequence as well. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between initial creation of a wheel event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. Unlike + Event.Latency.ScrollUpdate.Wheel.TimeToScrollUpdateSwapBegin2 this metric + includes the first GSU of every scrolling sequence as well. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the display compositor receives the notification of the first + ScrollUpdate gesture event in a given scroll gesture event sequence with + scrollbar source induced renderer swap and GPU starts to swap. The name + contains BrowserNotified for consistency with the existing + ScrollBegin/ScrollUpdate metrics - historically the display compositor lived + in the browser process. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between gpu starts to swap the first ScrollUpdate gesture event in a + given scroll gesture event sequence with scrollbar source induced frame and + the swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the first ScrollUpdate gesture event in a given scroll gesture + event sequence with scrollbar source, is handled on main/impl thread + (specified by suffix) and before renderer starts to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the renderer starts to swap a frame (generates compositor + frame) induced by the first ScrollUpdate gesture event in a given scroll + gesture event sequence with scrollbar source, and display compositor + receives the submitted compositor frame. The name contains BrowserNotified + for consistency with the existing ScrollBegin/ScrollUpdate metrics - + historically the display compositor lived in the browser process. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between initial creation of a scrollbar event and the first generated + ScrollUpdate gesture event in a given scroll gesture event sequence is + handled on main/impl thread (specified by suffix). If no swap was induced by + the ScrollUpdate gesture event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + speed-metrics-dev@chromium.org + + Time between initial creation of an input event that resulted in a scrollbar + scroll and the start of the frame swap on the GPU service caused by the + generated ScrollUpdate gesture event if that ScrollUpdate is the first such + event in a given scroll gesture event sequence. If no swap was induced by + the event, no recording is made. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + + Time between initial creation of a wheel/touch event and start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. If no + swap was induced by the event, no recording is made. + + Team: input-dev@chromium.org. + + + + + sadrul@chromium.org + chrome-gpu-metrics@google.com + + Records whether the browser top-controls (i.e. omnibox, toolbar) moved + because of the scroll-begin event (i.e. the first scroll-update event of + that sequence). + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures an average distance that represents how the page sticks to the + finger when user scrolls. Only reports touch scrolling. See + https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ + + This is the lag caused by the Gesture Scroll Begin Event. In each touch + interaction there is a GSB followed by multiple Gesture Scroll Updates, + which are separately logged by Event.Latency.ScrollUpdate.Touch.AverageLag. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.org + input-dev@chromium.org + + Measures an average distance that represents how the page sticks to the + finger when user scrolls. Only reports touch scrolling. See + https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ + + This is the lag caused by the Gesture Scroll Begin Event. In each touch + interaction there is a GSB followed by multiple Gesture Scroll Updates, + which are separately logged by + Event.Latency.ScrollUpdate.Touch.AverageLagPresentation. + + The difference between AverageLag and AverageLagPresentation is that the + former uses the Gpu Swap Begin Time as an approximation for the time the + frame is visible on the screen, while the latter uses the Presentation Time. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + Time between the browser receives the notification of the first ScrollUpdate + gesture event in a given scroll gesture event sequence with touch source + induced renderer swap and GPU starts to swap. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + Time between gpu starts to swap the first ScrollUpdate gesture event in a + given scroll gesture event sequence with touch source induced frame and the + swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the first ScrollBegin gesture event in a given scroll gesture + event sequence with touch source, is handled on main/impl thread (specified + by suffix) and before renderer starts to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the renderer starts to swap a frame induced by the first + ScrollUpdate gesture event in a given scroll gesture event sequence with + touch source, and browser receives the swap notification. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between initial creation of a touch event and the first generated + ScrollBegin gesture event in a given scroll gesture event sequence is + handled on main/impl thread (specified by suffix). If no swap was induced by + the ScrollUpdate gesture event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + speed-metrics-dev@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between the browser receives the notification of the first ScrollUpdate + gesture event in a given scroll gesture event sequence with wheel source + induced renderer swap and GPU starts to swap. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between gpu starts to swap the first ScrollUpdate gesture event in a + given scroll gesture event sequence with wheel source induced frame and the + swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the first ScrollUpdate gesture event in a given scroll gesture + event sequence with wheel source, is handled on main/impl thread (specified + by suffix) and before renderer starts to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the renderer starts to swap a frame induced by the first + ScrollUpdate gesture event in a given scroll gesture event sequence with + wheel source, and browser receives the swap notification. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between initial creation of a wheel event and the first generated + ScrollUpdate gesture event in a given scroll gesture event sequence is + handled on main/impl thread (specified by suffix). If no swap was induced by + the ScrollBegin gesture event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between initial creation of a wheel event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghad@chromium.org + + Time between the browser receives the notification of a ScrollUpdate gesture + generated from a touchscreen fling induced renderer swap and GPU starts to + swap. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between gpu starts to swap a ScrollUpdate gesture event generated from + a touchscreen fling induced frame and the swap finishes. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + + Time between a ScrollUpdate gesture event generated from a touchscreen + fling, is handled on main/impl thread (specified by suffix) and before + renderer starts to swap. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + input-dev@chromium.org + + Time between the renderer starts to swap a frame induced by a ScrollUpdate + gesture event generated from a touchscreen fling, and browser receives the + swap notification. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + + Time between initial creation of a ScrollUpdate gesture event generated from + a touchscreen fling is handled on main/impl thread (specified by suffix). If + no swap was induced by the ScrollUpdate gesture event, no recording is made. + + Team: input-dev@chromium.org. + + + + + nozlghadr@chromium.org + + Time between initial creation of a ScrollUpdate gesture event generated from + a touchscreen fling and the start of the frame swap on the GPU service + caused by the generated ScrollUpdate gesture event. If no swap was induced + by the event, no recording is made. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the display compositor receives the notification of the first + ScrollUpdate gesture event in a given scroll gesture event sequence with + scrollbar source induced renderer swap and GPU starts to swap. The name + contains BrowserNotified for consistency with the existing + ScrollBegin/ScrollUpdate metrics - historically the display compositor lived + in the browser process. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between gpu starts to swap a ScrollUpdate gesture event with scrollbar + source induced frame and the swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the ScrollUpdate gesture event with scrollbar source, is + handled on main/impl thread (specified by suffix) and before renderer starts + to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between the renderer starts to swap a frame (generates compositor + frame) induced by the first ScrollUpdate gesture event in a given scroll + gesture event sequence with scrollbar source, and display compositor + receives the submitted compositor frame. The name contains BrowserNotified + for consistency with the existing ScrollBegin/ScrollUpdate metrics - + historically the display compositor lived in the browser process. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + + Time between initial creation of an input event that results in a scrollbar + scroll and the generated ScrollUpdate gesture event is handled on main/impl + thread (specified by suffix). If no swap was induced by the ScrollUpdate + gesture event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + dlibby@microsoft.com + input-dev@chromium.org + speed-metrics-dev@chromium.org + + Time between initial creation of a scrollbar event and start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event. + If no swap was induced by the event, no recording is made. The first GSU of + every scrolling sequence is excluded from this metric. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nzolghadr@chromium.org + + Time between initial creation of a wheel/touch event and start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event. + If no swap was induced by the event, no recording is made. The first GSU of + every scrolling sequence is excluded from this metric. + + Team: input-dev@chromium.org. + + + + + sadrul@chromium.org + chrome-gpu-metrics@google.com + + Records whether the browser top-controls (i.e. omnibox, toolbar) moved + because of the scroll-update event (other than the first update event in the + sequence). + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures an average distance that represents how the page sticks to the + finger when user scrolls. Only reports touch scrolling. See + https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ + + This is the lag caused by the Gesture Scroll Updates occourring in the + lifetime of a scroll interaction. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures the negative impact on the AverageLag metric that is attributable + to scroll prediction. This value has the same units as + Event.Latency.ScrollUpdate.Touch.AverageLag but is a difference between that + value and what it would have been if prediction was disabled. + + PredictionNegative is logged when prediction caused an increase in perceived + lag (i.e. the rendered position was on average further from the actual + location of the finger) for a given interaction/interval. The duration of + the interaction/interval is either 1s, or the time from when the user starts + scrolling to lifting the finger, whichever is smaller. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures the positive impact on the AverageLag metric that is attributable + to scroll prediction. This value has the same units as + Event.Latency.ScrollUpdate.Touch.AverageLag but is a difference between that + value and what it would have been if prediction was disabled. + + PredictionPostive is logged when prediction caused a decrease in perceived + lag (i.e. the rendered position was on average closer to the actual location + of the finger) for a given interaction/interval. The duration of the + interaction/interval is either 1s, or the time from when the user starts + scrolling to lifting the finger, whichever is smaller. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures an average distance that represents how the page sticks to the + finger when user scrolls. Only reports touch scrolling. See + https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ + + This is the lag caused by the Gesture Scroll Updates occurring in the + lifetime of a scroll interaction. + + The difference between AverageLag and AverageLagPresentation is that the + former uses the Gpu Swap Begin Time as an approximation for the time the + frame is visible on the screen, while the latter uses the Presentation Time. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures the negative impact on the AverageLagPresentation metric that is + attributable to scroll prediction. This value has the same units as + Event.Latency.ScrollUpdate.Touch.AverageLagPresentation but is a difference + between that value and what it would have been if prediction was disabled. + + PredictionNegative is logged when prediction caused an increase in perceived + lag (i.e. the rendered position was on average further from the actual + location of the finger) for a given interaction/interval. The duration of + the interaction/interval is either 1s, or the time from when the user starts + scrolling to lifting the finger, whichever is smaller. + + The difference between AverageLag and AverageLagPresentation is that the + former uses the Gpu Swap Begin Time as an approximation for the time the + frame is visible on the screen, while the latter uses the Presentation Time. + + Team: input-dev@chromium.org. + + + + + flackr@chromium.org + joalmei@microsoft.com + input-dev@chromium.org + + Measures the positive impact on the AverageLagPresentation metric that is + attributable to scroll prediction. This value has the same units as + Event.Latency.ScrollUpdate.Touch.AverageLagPresentation but is a difference + between that value and what it would have been if prediction was disabled. + + PredictionPostive is logged when prediction caused a decrease in perceived + lag (i.e. the rendered position was on average closer to the actual location + of the finger) for a given interaction/interval. The duration of the + interaction/interval is either 1s, or the time from when the user starts + scrolling to lifting the finger, whichever is smaller. + + The difference between AverageLag and AverageLagPresentation is that the + former uses the Gpu Swap Begin Time as an approximation for the time the + frame is visible on the screen, while the latter uses the Presentation Time. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + Time between the browser receives the notification of a ScrollUpdate gesture + event with touch source induced renderer swap and GPU starts to swap. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between gpu starts to swap a ScrollUpdate gesture event with touch + source induced frame and the swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between the ScrollUpdate gesture event with touch source, is handled on + main/impl thread (specified by suffix) and before renderer starts to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between the renderer starts to swap a frame induced by ScrollUpdate + gesture event with touch source, and browser receives the swap notification. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + Time between initial creation of a touch event and the generated + ScrollUpdate gesture event is handled on main/impl thread (specified by + suffix). If no swap was induced by the ScrollUpdate gesture event, no + recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + + tdresser@chromium.org + input-dev@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + Time between initial creation of a touch event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between the browser receives the notification of a ScrollUpdate gesture + event with wheel source induced renderer swap and GPU starts to swap. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Time between gpu starts to swap a ScrollUpdate gesture event with wheel + source induced frame and the swap finishes. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between the ScrollUpdate gesture event with wheel source, is handled on + main/impl thread (specified by suffix) and before renderer starts to swap. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + input@chromium.org + + Time between the renderer starts to swap a frame induced by ScrollUpdate + gesture event with wheel source, and browser receives the swap notification. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + Time between initial creation of a wheel event and the generated + ScrollUpdate gesture event is handled on main/impl thread (specified by + suffix). If no swap was induced by the ScrollUpdate gesture event, no + recording is made. The first GSU of every scrolling sequence is excluded + from this metric. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tdresser@chromium.org + + Time between initial creation of a wheel event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + tommckee@chromium.org + speed-metrics-dev@chromium.org + + When tracking input event latency, we expect to associate some number of + latency records (instances of ui::LatencyInfo) with a CompositorFrame. Each + record is associated to a particular navigation through its ukm::SourceId + property. This histogram tracks how often the records of an individual frame + have varying or invalid source ids. See crbug.com/1062764. + + + + + dtapuska@chromium.org + + The result of handling of MouseWheel, TouchStart, TouchMove, TouchEnd events + in the renderer. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + + On non-mobile sites, gesture taps are delayed to prevent double taps from + sending a click event. This stat counts the number of taps that are delayed + by the double-tap delay versus those that are sent immediately on mobile + sites. + + Team: input-dev@chromium.org. + + + + + charliea@chromium.org + nzolghadr@chromium.org + + Whether a given touch event is filtered by the passthrough touch event queue + or not. If the event was filtered, a reason is given. Potential reasons for + filtering include the page not having any registered touch handlers and the + renderer process not responding to previous touch events. + + Team: input-dev@chromium.org + + + + + kuscher@google.com + rbyers@chromium.org + + The gesture-events recognized and dispatched for UI components owned by the + browser. This histogram was created as part of separating gesture events + between the browser and Ash (crbug.com/826476). The enums are extracted from + Ash.GestureTarget. + + + + + tdresser@chromium.org + input-dev@chromium.org + + On non-mobile-optimized (desktop) sites, whether the ack response from the + renderer for any event in a contiguous touch sequence exceeds the + desktop-specific timeout threshold. + + Team: input-dev@chromium.org. + + + + + tdresser@chromium.org + input-dev@chromium.org + + On mobile-optimized sites, whether the ack response from the renderer for + any event in a contiguous touch sequence exceeds the mobile-specific timeout + threshold. + + Team: input-dev@chromium.org. + + + + + kuscher@google.com + tdresser@chromium.org + + The duration of a touch-sequence. Only measured for single finger gestures. + This replaces Ash.TouchDuration2, which did not record events on Android and + Windows. + + Team: input-dev@chromium.org. + + + + + kuscher@google.com + tdresser@chromium.org + + The maximum euclidean distance in dips (device independent pixel) which a + touch point has travelled away from its starting point. Only measured for + single finger gestures. This replaces Ash.TouchMaxDistance, which did not + record events on Android and Windows. + + Team: input-dev@chromium.org. + + + + + nzolghadr@chromium.org + + Duration of touch selection sequence which finished with the user selecting + one of the text manipulation actions, such as copy, cut, or paste. The + duration is measured from the moment the text selection handles are shown, + and until the action is executed. + + + + + nzolghadr@chromium.org + + Whether the touch selection sequence ended with the user selecting one of + the text manipulation actions, such as copy, cut, or paste. after startup). + Sequences ending with such action are considered successful. + + + + + nzolghadr@chromium.org + + Duration of touch selection sequence which involved dragging a text + selection handle. The duration is measured from the moment the text + selection handles are shown, and until they are dismissed. + + + + + amaralp@chromium.org + + Percentage of touch handle height that would be clipped by the viewport in + the best case of flipping or not flipping. + + + + + amaralp@chromium.org + + Percentage of touch handle height that would be clipped by the viewport if + the handle was not vertically flipped. + + + + + amaralp@chromium.org + + The difference between the metrics |BottomHandleClippingPercentage| and + |BestVerticalClippingPercentage|. Measures how useful vertical flipping is. + + + + + amaralp@chromium.org + + Percentage of left touch handle width that would be clipped by the viewport + without flipping. + + + + + amaralp@chromium.org + + Percentage of right touch handle width that would be clipped by the viewport + without flipping. + + + + + amaralp@chromium.org + + Whether flipping the handle vertically would result in less clipping. + + + + + yigu@chromium.org + + Tracks the reasons why sychronous hit testing could not be done for each hit + test requests processd by HitTestQuery. + + Team: event-targeting@chromium.org. + + + + + zandershah@google.com + event-targeting@chromium.org + + Tracks the result of AsyncLayerTreeFrameSink calls to + HitTestRegionList::IsEqual. + + + + + mohsen@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages an event goes through from when it is + generated on the browser side until it ends up generating a frame that is + eventually presented to the user. If the frame is dropped, nothing is + reported. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/extension/histograms.xml b/tools/metrics/histograms/histograms_xml/extension/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..4e3293224df83a80d9870fbf1ed3dfd4672b27b4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/extension/histograms.xml @@ -0,0 +1,293 @@ + + + + + + + + + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create + iframes to add to the page. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that were blacklisted when already installed, + grouped by Extension::Location. Logged when ExtensionService blackists and + unloads an installed extension. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that have been blocked from installing grouped by + Extension::Location. Logged when ExtensionService refuses to install a + blacklisted extension. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that have been silently installed in a blacklisted + state, grouped by Extension::Location. Logged when ExtensionService installs + a blacklisted extension without blocking it (ExtensionBlacklist.BlockCRX + would be logged otherwise). Typically this will be when a user has a + blacklisted extension synced. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that were unblacklisted when installed, grouped by + Extension::Location. Logged when ExtensionService unblacklists and loads a + blacklisted extension. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken by the user when seeing the bubble, logged right after the + action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The total number of extensions found to be loaded under Developer Mode, + logged when the devmode bubble is shown (once per startup per profile, if + any devmode extension is found). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The total number of extensions found to be wiped by SideloadWipeout, logged + when the wipeout bubble is shown, which is once per startup per profile. + + + + + + + lazyboy@chromium.org + extensions-core@chromium.org + + The time taken to create the computed_hashes.json file for an extension. + This happens once for each extension after we get signed values of the + expected root node of a tree hashes for each file from the webstore; we then + compute the individual block level hashes of the actual files and cache them + in computed_hashes.json (assuming we don't detect any mismatches). + + + + + lazyboy@chromium.org + extensions-core@chromium.org + + The time taken to initialize the ContentHashReader for an extension resource + load. (The work done is to read in the verified contents and computed hashes + data, and compare them to make sure they agree.) + + + + + lazyboy@chromium.org + + The time taken in computation (hashing actual bytes read and comparing + against expected computed hashes values) during an extension resource load. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + The result of the verifier trying to get a new signature. + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The result of initialization for the extension install verifier. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken by the user when seeing the bubble, notifing them of an + extension overriding their new tab page. Logged right after the action is + taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken by the user when seeing the bubble, notifing them of an + extension overriding their homepage. Logged right after the action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken by the user when seeing the bubble, notifing them of an + extension overriding their search engine. Logged right after the action is + taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken by the user when seeing the bubble, notifing them of an + extension overriding their startup page. Logged right after the action is + taken. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Records whether adding a new/updated extension to the install verifier + succeeded. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The outcome of a call to ExtensionService::VerifyAllExtensions, whether it + was called for bootstrapping or another reason (extension + installed/uninstalled, etc.). + + + + + Please list the metric's owners. Add more owner tags as needed. + + When loading the chrome://extensions page, this records whether we decided + to do a verification check against the server (because the user had one or + more extensions disabled due to verification failure). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of icons the Browser Actions Container knows about (visible or in + the overflow bucket). Does not count icons that have been permanently hidden + by the user. Measured once per startup per (non-incognito) profile. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of visible icons in the Browser Actions Container (visible as in + number of icons not in the overflow bucket). 0 means all icons are in the + overflow bucket. MAX_INT means the toolbar is always showing all icons. + Measured once per startup per (non-incognito) profile but only for those + profiles that have one or more browser actions showing in the toolbar. + + + + + lazyboy@chromium.org + The time taken to complete an extension url request. + + + + lazyboy@chromium.org + + When fetching a chrome-extension:// URL, this indicates the first byte + position we read from. This will be greater than 0 in cases such as XHR's + with a Range header, but will normally be 0 in the typical case of reading + the entire file. This helps identify how frequently partial file reads are + taking place. + + + + + lazyboy@chromium.org + + The total number of bytes read for a chrome-extension:// URL, logged when + the job is finished (either successfully or not). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/extensions/histograms.xml b/tools/metrics/histograms/histograms_xml/extensions/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..52cdf118caed7a04fcd5570bf331b0dc41971668 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/extensions/histograms.xml @@ -0,0 +1,3498 @@ + + + + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The cause for the failure in the setIcon() extension API function. This is + temporary logging to help track down the cause of a crash. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions on a page that wanted to execute a script, required + explicit user consent, and were denied permission. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions on a page that wanted to execute a script, required + explicit user consent, and were granted permission. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time it takes to generate the JavaScript API bindings for a + particular extension API. This includes the time from when a JavaScript + context tries to access the API, triggering the lazy initializion, to the + time when the API object is returned. This is only recorded if the binding + is successfully generated. See also Extensions.DidCreateScriptContext_*. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time it takes to create the JavaScript binding object using + the binding.js module. This is a strict subset of + Extensions.ApiBindingGenerationTime, which includes this work and more. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + dbertoni@chromium.org + + Reports whether a tab was updated to a javascript:-scheme URL from the + extensions tabs.update API. Reported once per call to tabs.update(). + + + + + benwells@chromium.org + dominickn@chromium.org + tapted@chromium.org + + The number of times v1 apps are launched grouped by + extension_misc::AppLaunchBuckets. See also Apps.AppLaunch for v2 apps. + + + + + benwells@chromium.org + cylee@chromium.org + + The number of times apps are launched grouped by + extensions::AppLaunchSource. + + + + + lazyboy@chromium.org + + A platform app ended up in a regular tab either by the app page or its + background page. Note that this happens unexpectedly right now and we wish + to track its usage before removing the supporting code. + + + + + benwells@chromium.org + tapted@chromium.org + + The number of apps loaded at startup time grouped by Extension::Location. + + + + + benwells@chromium.org + tapted@chromium.org + + The actions taken in the NTP apps promo grouped by + extension_misc::AppsPromoBuckets. + + + + + benwells@chromium.org + tapted@chromium.org + + The number of apps launched grouped by extensions::LaunchType. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The extension install location of an extension that Chrome attempted to add, + but failed because it would downgrade the version. Tracking for + https://crbug.com/810799. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The extension item type of an extension that Chrome attempted to add, but + failed because it would downgrade the version. Tracking for + https://crbug.com/810799. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time taken for an extension's persistent background page to load its + initial URL. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The type (if any) of background page the extension has. Recorded for + installed extensions on startup. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of times each Extension function call sends a bad message, + killing the renderer. This may indicate a bug in that API's implementation + on the renderer. Note a similar, aggregate metric is BadMessageTerminate_EFD + which counts the number of bad messages that are sent overall. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The reason a valid ExtensionSyncData could not be parsed from a SyncData + received from sync. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The elapsed time to create a new full instance of an extension API's + bindings using native bindings. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The elapsed time to update the bindings for a new or existing v8::Context. + The suffix indicates which type of context the bindings are for. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benwells@chromium.org + dominickn@chromium.org + Records the container used for a bookmark app launch. + + + + benwells@chromium.org + dominickn@chromium.org + mgiuca@chromium.org + ortuno@chromium.org + + The number of times Bookmark Apps are launched, grouped by + extensions::AppLaunchSource. The equivalent histogram on Android is called + Launch.HomeScreenSource. + + + + + rkaplow@chromium.org + + The amount of time that elapsed during + ExtensionService::CheckForExternalUpdates. + + + + + archanasimha@chromium.org + extensions-core@chromium.org + + Records every time the user clicks on the extensions checkup middle slot + promo link. The user is served the promo if they are part of the + ExtensionsCheckup experiment and have at least one non default installed + extension. The promo should appear every time the user opens the NTP. The + enum value represents the focus of the message displayed in the promo, which + is determined by the experiment group the user is in. This metric should be + compared with Extensions.Checkup.NtpPromoShown. + + + + + archanasimha@chromium.org + extensions-core@chromium.org + + Records every time the user is served the extensions checkup middle slot + promo on the NTP. The user is served the promo if they are part of the + ExtensionsCheckup experiment and have at least one non default installed + extension. The promo should appear every time the user opens the NTP. The + enum value represents the focus of the message displayed in the promo, which + is determined by the experiment group the user is in. This metric should be + compared with Extensions.Checkup.NtpPromoClicked. + + + + + archanasimha@chromium.org + extensions-core@chromium.org + + The amount of time passed from when the chrome://extensions page has + finished loading till it is closed. We record the time elapsed once the + WebUI has been destroyed. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + The amount of elapsed time taken to initialize the ChromeExtensionsClient. + Recorded once per client initialization, which happens once per instance of + Chrome. This is a new stat that has microsecond resolution. + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + How long a successful initialization of computed_hashes.json file takes. + Recorded when content verification needs to retrieve block hashes. + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether or not computed_hashes.json file read and parse succeeded. Recorded + when content verification needs to retrieve block hashes. + + + + + burunduk@chromium.org + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether or not computed_hashes.json file was successfully generated and + written during extension installation. Recorded during installation of an + extension if hashes computing was requested for this specifix extension. + Hashes computing on installation is used for off-store policy-based + extensions since we need them to be checked against corruption and cannot + use Chrome Web Store for source of hashes. + + + + + burunduk@chromium.org + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time taken to successfully create the computed_hashes.json file for an + extension upon installation. The histogram is collected with + &Extensions.ContentVerification.ComputeHashesOnInstallResult& (in + case of success). + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether or not fetching verified_contents.json succeeded. Recorded when the + file wasn't available locally and we needed to fetch it from network. + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + + Time spent by ContentVerifier for a request to create a ContentHash + instance. Recorded during an extension load completion or during an on + demand content verification that was triggered by ContentVerifyJob. + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether or not initializing verified_contents.json succeeded. Recorded + during an extension load completion or during an on demand content + verification that was triggered by ContentVerifyJob. + + + + + lazyboy@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + How long a successful initialization of verified_contents.json file takes. + Recorded if Extensions.ContentVerification.VerifiedContentsInitResult = true + was recorded. + + + + + + + rdevlin.cronin@chromium.org + karandeepb@chromium.org + + Records the action taken by the user from the extension icon context menu. + + + + + lazyboy@chromium.org + extensions-core@chromium.org + + Fired each time an extension was detected to be corrupted (contents not + matching an expected content hash from the webstore) and was disabled. + + + + + lazyboy@chromium.org + rockot@chromium.org + extensions-core@chromium.org + + The reason why an extension was detected to be corrupted. Recorded each time + an extension is disabled due to corruption detection. + + + + + + + lazyboy@chromium.org + extensions-core@chromium.org + + Logged once at startup, this is the value of a counter that is incremented + anytime we disable a corrupted extension because its content didn't match an + expected content hash. + + + + + lazyboy@chromium.org + extensions-core@chromium.org + + Simiar to Extensions.CorruptExtensionBecameDisabled, but fires when we're in + a bootstrapping mode and would have disabled an extension. + + + + + burunduk@chromium.org + lazyboy@chromium.org + poromov@chromium.org + extensions-core@chromium.org + + Fires when we suspect corruption in an enterprise policy forced install + extension and begin the process of reinstalling it, saving reason of such + suspection. Compare to CorruptPolicyExtensionResolved to judge success rate. + Note that if extension was not reinstalled in the session when corruption + was found, it will be detected again (possible several times, every session + start will trigger a detection until the extension will be fixed), but as + CORRUPTION_DETECTED_IN_PRIOR_SESSION. + + + + + burunduk@chromium.org + lazyboy@chromium.org + extensions-core@chromium.org + managed-devices@google.com + + Fires when we've successfully resinstalled a corrupt enterprise policy + force-installed extension, with a value indicating how long it took + end-to-end to complete the reinstall (including download time). + + + + + cmumford@chromium.org + + The result of an attempt to recover from an attempt to open a database that + failed as a result of corruption. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + The result of an open attempt to an Extensions database. + + + + cmumford@chromium.org + + The result of an attempt to delete a corrupted value from a database. + + + + + + + karandeepb@chromium.org + + Number of calls to the declarative API extension functions. This includes + the declarativeContent and declarativeWebRequest APIs. Emitted when the + extension function is called. + + + + + kelvinjiang@chromium.org + extensions-core@chromium.org + + Number of times a declarative content action is created within an extension. + Emitted when a new declarative content action is created. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Measures the time taken to load a single indexed ruleset in the browser + process for an extension. This includes reading the indexed ruleset file and + verifying it. Emitted whenever a single extension ruleset is loaded. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Time taken to evaluate the before-request action for a network request for a + single extension ruleset. Emitted for each network request that is visible + to the extension. This is only emitted for users with high resolution + clocks. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Time taken to evaluate the action to take for the network request as per the + Declarative Net Request API. This includes the time taken to evaluate all + the extension rulesets. Emitted for non-sensitive network requests seen by + the Extension System when there is at least one active extension ruleset. + This is only emitted for users with high resolution clocks. + + + + + karandeepb@chromium.org + lazyboy@chromium.org + + Time taken to index and persist to disk, the deserialized json rules + provided by an extension manifest for the Declarative Net Request API. This + is emitted whenever a packaged extension with a declarative ruleset is + installed or updated. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Logs whether a regex rule wasn't indexed since it exceeded the per-rule + memory limit. Emitted for every regex rule an extension adds. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Records the result of loading an extension ruleset for the Declarative Net + Request API. Emitted whenever a single extension ruleset is loaded. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + The number of enabled indexed declarative rules provided by an extension + manifest for the Declarative Net Request API. This is emitted whenever a + packaged extension with a declarative ruleset is installed or updated. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + The number of indexed declarative rules provided by an extension manifest + for the Declarative Net Request API. This also includes rules from disabled + rulesets. This is emitted whenever a packaged extension with a declarative + ruleset is installed or updated. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Indicates the result of reading the dynamic JSON rules for an extension from + the disk. Logged whenever an extension calls the getDynamicRules extension + function or when it updates the dynamic rules through a call to + addDynamicRules or removeDynamicRules. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the request header added by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnBeforeSendHeaders stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the request header modified by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnBeforeSendHeaders stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the request header removed by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnBeforeSendHeaders stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the response header added by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnHeadersReceived stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the response header modified by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnHeadersReceived stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + Records the response header removed by extensions using the + DeclarativeNetRequest API. Recorded for each network request during the + OnHeadersReceived stage. Multiple samples can be recorded per request. + + + + + karandeepb@chromium.org + lazyboy@chromium.org + + Indicates whether reindexing of a Declarative Net Request ruleset was + successful. Called whenever a JSON ruleset for an extension is reindexed, + e.g. on ruleset corruption. Note: this is emitted for both static and + dynamic rulesets. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Indicates the result of an extension function call to add or remove dynamic + rules. Logged every time an extension calls the addDynamicRules or + removeDynamicRules extension function. + + + + + Please list the metric's owners. Add more owner tags as needed. + Time spent until rules storage delegate gets ready. + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether an icon specified in the declarativeContent.SetIcon API is + considered visible by our icon analysis code. This stat is emitted when we + create the underlying object that sets the icon when the declarative rule is + applied. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether an icon specified in the declarativeContent.SetIcon API is + considered visible by our icon analysis code. This stat is emitted when we + create the underlying object that sets the icon when the declarative rule is + applied. + + This replaces the previous stat, DeclarativeSetIconWasVisibleRendered, due + to a change to our analysis algorithm. The new algorithm renders the icon + against the toolbar background color and determines how visible the + resulting pixels are. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per blessed + extension context (chrome-extension://... origins within Extension + processes, like background pages, options pages, popups). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per blessed web page + context (hosted apps). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per content script + context. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per content script + context. This histogram measures the time to install Extension Javascript + bindings in a context for a platform app enabled on the Chrome OS lock + screen. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per unblessed + extension context (chrome-extension://... origins hosted in iframes). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings in an unknown type + of context (this should never happen other than in bizarre circumstances). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per web page context + (just the chrome.app, chrome.webstore, and possibly chrome.runtime APIs). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records + the time taken to install Extension JavaScript bindings per WebUI context + (chrome://extensions and so forth). + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Records the time taken to install Extension JavaScript bindings per service + worker context. + + + + + + + rdevlin.cronin@chromium.org + + The number of extensions that are disabled at browser startup. + + + + + + + rdevlin.cronin@chromium.org + + The number of extensions that are disabled at browser startup due to + permissions increases. + + + + + catmullings@chromium.org + + User response to the dialog shown when an extension is disabled due to an + update requiring more permissions. A count is recorded when the user takes + an action on the dialog (re-enable or remove the extension) or ignores the + dialog. + + + + + catmullings@chromium.org + + User response to the dialog shown when an extension is disabled due to it + having been installed remotely. A count is recorded when the user takes an + action on the dialog (re-enable or remove the extension) or ignores the + dialog. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The count of disabled extensions at startup grouped by disble reason from + disable_reason::DisableReason. When an extension is disabled, it can be for + one or more reasons (although typically just one), so the sum of these may + be greater than 'Extensions.Disabled' which is a count of the number of + unique extensions that are disabled. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether a call to set a dynamic icon in the toolbar passed an icon + considered visible by our icon analysis code. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether a call to set a dynamic icon in the toolbar passed an icon + considered visible by our icon analysis code. + + This replaces the previous stat, DynamicExtensionActionIconWasVisible, due + to a change to our analysis algorithm. The new algorithm renders the icon + against the toolbar background color and determines how visible the + resulting pixels are. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + If opening the CRX file for unpacking fails, this integer is the error code + given by the OS. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions with event pages that have no registered event + listeners at profile startup. (This may indicate something has gone wrong; + such event pages will never get started.) + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time between an extension's event page loading its first URL and the + event page later shutting down. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + The time an extension's event page has spent unloaded. + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time taken for an extension's event page to load its initial URL. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Recorded every time an event is dispatched to an extension. + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded every time an event is dispatched to a *component* extension. + Otherwise identical to Extensions.Events.Dispatched. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded every time an event is dispatched to an extension with a persistent + background page. The event may or may not have been dispatched to the + background page itself, for example it may have been dispatched to its + popup. When this metric is recorded, Extensions.Events.Dispatch will also be + recorded. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded every time an event is dispatched to an extension with an event + page that was already running (i.e. at some point had been woken from its + suspended state, see Extensions.Events.DispatchWithSuspendedEventPage). The + event may or may not have been dispatched to the event page itself, for + example it may have been dispatched to its popup. When this metric is + recorded, Extensions.Events.Dispatch will also be recorded. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded every time an event is dispatched to an extension with an event + page that was suspended. This implies that firing this event woke up the + event page. The event may or may not have been dispatched to the event page + itself, for example it may have been dispatched to its popup, but regardless + it will wake the event page. When this metric is recorded, + Extensions.Events.Dispatch will also be recorded. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Recorded when an extension is already disabled and a new disable reason is + added to the extension. The new disable reason is retrieved from the update + service data key reasons during an update check for extensions. + + + + + burunduk@chromium.org + snijhara@google.com + managed-devices@google.com + + Number of cached extensions on disk. Reported on Chrome OS during user + session start. + + + + + burunduk@chromium.org + snijhara@google.com + managed-devices@google.com + + Total size of .crx files in cache on disk. Reported on Chrome OS during user + session start. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + The update service data key reasons that the update service encounters + during an update check session using update client when disabling an + extension. + + + + + + + rdevlin.cronin@chromium.org + + Emitted when an extension is downloaded by the user (including webstore + installs). + + + + + + + rdevlin.cronin@chromium.org + + The install location for a given extension. Recorded once per enabled + extension on profile initialization. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Recorded when an extension that was previously only disabled remotely is + re-enabled remotely during an update service session. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Length of the Extensions dir path inside the profile directory. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken for the ExtensionService to initialize, including the time it + takes to load the extensions for the service's profile and parse their + manifests. This happens during startup and also any time a new profile is + loaded. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken for the ExtensionService to notify all ready listeners that the + extension system is now ready. This happens as part of the total + initialization time of ExtensionService, measured in + Extensions.ExtensionServiceInitTime. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + An extension has been uninstalled. + + + + Please list the metric's owners. Add more owner tags as needed. + + Records what happens to extensions that are sideloaded, grouped by the + ExternalExtensionEvent enum. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of sideloaded apps/extensions loaded on startup grouped by + enabled/disabled state. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of extensions referenced in the external extensions source at path + chrome::DIR_EXTERNAL_EXTENSIONS. + + + + + archanasimha@chromium.org + extensions-core@chromium.org + + Records when an extension with the chrome://favicon host permission makes a + network level request for a favicon resource. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time that elapsed during extensions::FeatureProvider::Static. + Only measured while in the browser process. + + + + + rdevlin.cronin@chromium.org + + The number of extensions (and friends) that could have been given access to + the file:// scheme, and were, for users that have at least one extension + that could have been given access. This excludes anything that doesn't show + up in chrome://extensions (platform apps, hosted apps, component + extensions), policy-installed extensions, and unpacked extensions. See also + Extensions.FileAccessNotAllowed. + + + + + rdevlin.cronin@chromium.org + + The number of extensions (and friends) that could have been given access to + the file:// scheme, but weren't, for users that have at least one extension + that could have been given access. This excludes anything that doesn't show + up in chrome://extensions (platform apps, hosted apps, component + extensions), policy-installed extensions, and unpacked extensions. See also + Extensions.FileAccessAllowed. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + Number of enterprise policy forced extensions that are blacklisted and thus + not loaded after 5 minutes if at least one of policy forced extensions is + not yet enabled. + + + + + swapnilgupta@google.com + burunduk@chromium.org + poromov@chromium.org + + Status of cache entry about enterprise policy forced extension. Recorded for + each forced extension. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The last known intermediate stage of extension when the extension + installation stage if CREATED if failure reason was not recorded + (installation of an extension was neither yet finished nor failed). Recorded + for each forced extension that failed to install after 5 minutes. Recorded + together with "Extensions.ForceInstalledTimedOutCount" histogram, + but for every extension not installed at the moment. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The last known downloading stage of extension downloading process if failure + reason was not recorded and installing stage is DOWNLOADING, so it's + specification of Extensions.ForceInstalledStage. Recorded for each forced + extension that failed to install after 5 minutes. Recorded together with + "Extensions.ForceInstalledTimedOutCount" histogram, but for every + extension not installed at the moment. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Status of cache entry about enterprise policy forced extension which failed + to install. Recorded for each forced extension that failed to install after + 5 minutes. Recorded together with + "Extensions.ForceInstalledTimedOutCount" histogram, but for every + extension not installed at the moment. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Detailed reason why CRX installation failed for enterprise policy forced + extensions. Recorded for each forced extension that failed to install after + 5 minutes with Extensions.{OffStore,Webstore}_ForceInstalledFailureReason3 + equal to CRX_INSTALL_ERROR_*. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The detailed reason why enterprise policy forced extensions had failed to + install because fetched update manifest was invalid due to app status error. + Recorded for each forced extension that failed to install after 5 minutes + with Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID and + Extensions.ForceInstalledFailureManifestInvalidErrorDetail2 equal to + BAD_APP_STATUS. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The detailed reason why enterprise policy forced extensions had failed to + install because fetched update manifest was invalid. Recorded for each + forced extension that failed to install after 5 minutes with + Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID. + + Replaced Extensions.ForceInstalledFailureManifestInvalidErrorDetail due to + addition of new error BAD_APP_STATUS, and some of the errors that were + MISSING_UPDATE_CHECK_TAG would now be reported as BAD_APP_STATUS. + + + + + snijhara@google.com + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The info field in the update manifest fetched from the server for enterprise + policy forced extensions. Recorded for each forced extension for which the + server responds with no updates and an empty CRX fetch url. Recorded for + each forced extension that failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + CRX_FETCH_URL_EMPTY. + + + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The reason why enterprise policy forced extensions were not installed. + Recorded for each forced extension that failed to install after 5 minutes. + Recorded together with "Extensions.ForceInstalledTimedOutCount" + histogram, but for every extension not installed at the moment. + + Replaced Extensions.ForceInstalledFailureReason2 because of reporting + MANIFEST_INVALID instead of MANIFEST_FETCH_FAILED in case parsing update + manifest failed with different reasons for the extensions. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The reason why enterprise policy forced extensions had failed to unpack. + Recorded for each forced extension that failed to install after 5 minutes + with Extensions.ForceInstalledFailureReason3 equal to + CRX_INSTALL_ERROR_SANDBOXED_UNPACKER_FAILURE. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The type of session in case enterprise policy forced extensions were not + installed. Recorded for each force installed extension which failed to + install after 5 minutes. Supported only on ChromeOS and recorded only if + there is an active user. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Number of fetch retries made when CRX fetch failed for enterprise policy + forced extensions. Recorded for each forced extension that failed to install + after 5 minutes with + Extensions.{OffStore,Webstore}_ForceInstalledFailureReason3 equal to + CRX_FETCH_FAILED. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + HTTP error code for the last retry attempt when CRX fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + CRX_FETCH_FAILED and a HTTP response code was received. HTTP response code + is received only if there was no network error. Replaced + Extensions.ForceInstalledHttpErrorCode because error codes are now reported + only when network error code is HTTP_RESPONSE_CODE_FAILURE. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The amount of time elapsed during installation of enterprise policy forced + extensions. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Number of fetch retries made when Manifest fetch failed for enterprise + policy forced extensions. Recorded for each forced extension that failed to + install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + MANIFEST_FETCH_FAILED. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + HTTP error code for the last retry attempt when Manifest fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + MANIFEST_FETCH_FAILED and a HTTP response code was received. HTTP response + code is received only if there was no network error. Replaced + Extensions.ForceInstalledManifestFetchFailedHttpErrorCode because error + codes are now reported only when network error code is + HTTP_RESPONSE_CODE_FAILURE. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Network error code for the last retry attempt when Manifest fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + MANIFEST_FETCH_FAILED. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Network error code for the last retry attempt when CRX fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + CRX_FETCH_FAILED. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + Records the disable reason for the enterpise policy forced extensions. + Recorded for each forced extension that installed but failed to load after 5 + minutes. If the extension is not disabled, it records + DisableReason::DISABLE_NONE. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Records whether there was a possible non-misconfiguration failure for the + enterprise policy forced extensions. Records true if in a session at least + one forced extension failed to install after 5 minutes with a + non-misconfiguration failure and false when all the forced extensions which + failed to install after 5 minutes failed due to some misconfiguration. + Recorded together with "Extensions.ForceInstalledTimedOutCount" + histogram. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The last known stage of extension installation process if failure reason was + not recorded (installation of an extension was neither yet finished nor + failed). Recorded for each forced extension that failed to install after 5 + minutes. Recorded together with + "Extensions.ForceInstalledTimedOutCount" histogram, but for every + extension not installed at the moment. + + Replaced Extensions.ForceInstalledStage because the stages that were used + for used for investigation of CREATED stage are moved to a new enum. + + + + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The amount of time elapsed during different stage of the installation + process for the enterprise policy forced extensions. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Number of enterprise policy forced extensions that are not installed after 5 + minutes if at least one of policy forced extensions is not yet enabled. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Number of enterprise policy forced extensions that are not loaded after 5 + minutes timeout, while might be already installed. + + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + Total amount of extensions in force installed list. Gets recorded on profile + open (which happens on every startup and when user logs in) and tries to + load extensions. Number of records should correspond to the sum of records + in "Extensions.ForceInstalledLoadTime" and records in + "Extensions.ForceInstalledTimedOutAndNotInstalledCount". + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of apps/extensions loaded on startup with an inconsistent "from + webstore" state. This means an item that is flagged as from_webstore, + but with either a non-webstore update_url or an external install location. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when a component extension calls an extension API. Recorded once + per function call. See also Extensions.Functions.WebUICalls and + Extensions.Functions.ExtensionCalls. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when a non-component extension calls an extension API. Recorded + once per function call. See also Extensions.Functions.WebUICalls and + Extensions.Functions.ComponentExtensionCalls. + + + + + lazyboy@chromium.org + dbertoni@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when an extension service worker calls an extension API. Note that + the function would also be included in either + Extensions.Functions.ExtensionCalls or + Extensions.Functions.ComponentExtensionCalls histogram. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when an extension function call fails and finishes execution. The + suffix indicates the exact bucket the function is in. See also + Extensions.Functions.FailedTotalExecutionTime. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The total amount of time it took to execute an extension function that + failed from the time the extension function is called to the time the + function responds. Note that since some extension functions are inherently + slow (anything that requires user interaction, for instance), this is not a + definitive source for function performance. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time it takes to handle a response for an extension API + request. Recorded on the renderer side once we receive the response IPC from + the browser and have deserialized the arguments and passed them to the JS + context. Only recorded if the response is successfully handled. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time it takes to start an extension API request. Recorded on + the renderer side after we perform JS pre-processing, but includes all + serialization and dispatching. Only recorded if the request is successfully + dispatched. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when an extension function call succeeds and finishes execution. + The suffix indicates the exact bucket the function is in. See also + Extensions.Functions.SucceededTotalExecutionTime. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The total amount of time it took to execute an extension function that + succeeded from the time the extension function is called to the time the + function responds. Note that since some extension functions are inherently + slow (anything that requires user interaction, for instance), this is not a + definitive source for function performance. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The synchronous amount of time an extension function takes. Note that many + extension functions run asynchronously; see also + Extensions.Functions.[Succeeded|Failed]TotalExecutionTime. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Recorded when a WebUI context calls an extension API. Recorded once per + function call. See also Extensions.Functions.ComponentExtensionCalls and + Extensions.Functions.ExtensionCalls. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records requests to use resources from Google Docs Offline + extension, along with whether the extension has been available or not and + the request has been done from incognito mode or not. Note that this request + is double counted for the imports. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it is + automatically disabled due to a permission increase (e.g., after an + extension upgrade). To find places where this histogram may be emitted, look + for calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument AutoDisable. For Sync users, this may be reported for each device, + depending on whether the Sync update or the extension auto-update happen + first. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it was + installed. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument Install. For Sync users, this is reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when installation + was aborted (e.g. because the parent window of the confirmation dialog went + away), not including installation errors and user cancels. To find places + where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + InstallAbort. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when installation + was canceled. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument InstallCancel. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it was + loaded (which happens at profile open or extension install). To find places + where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument Load. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it was + re-enabled from a confirmation prompt. To find places where this histogram + may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + ReEnable. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when the + re-enable prompt was aborted (e.g. because the parent window of the + confirmation dialog went away), not including installation errors and manual + user cancels. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument ReEnableAbort. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when the + re-enable was canceled from the confirmation prompt. To find places where + this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + ReEnableCancel. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it was + uninstalled. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument Uninstall. For Sync users, this is reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when it was + installed through the web store. To find places where this histogram may be + emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + WebStoreInstall. Contrary to the more-general HasPermissions_Install3 + histogram, this one is NOT reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when installation + from the web store was canceled. To find places where this histogram may be + emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + WebStoreInstallCancel. + + + + + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + The number of enabled extensions with a homepage override specified in their + manifest. Recorded once per profile at profile initialization. + + + + + benwells@chromium.org + dominickn@chromium.org + + Records the container used for a hosted app launch. The definition of + 'launch' for the purposes of this histogram is different to that used for + the launch type histograms. This definition is less inclusive, for example + it does not include navigations to the hosted app due to normal browsing, + which the other definition does include. This definition could be thought of + more as explicit launches via a launch surface such as the app launcher, + chrome://apps, or a shortcut. + + + + + + + rdevlin.cronin@chromium.org + + The number of extensions (and friends) that could have been allowed in + incognito, and were, for users that have at least one extension that could + have been allowed. This excludes anything that doesn't show up in + chrome://extensions (platform apps, hosted apps, component extensions), + policy-installed extensions, and unpacked extensions. See also + Extensions.IncognitoNotAllowed. + + + + + rdevlin.cronin@chromium.org + + The number of extensions (and friends) that could have been allowed in + incognito, but weren't, for users that have at least one extension that + could have been allowed. This excludes anything that doesn't show up in + chrome://extensions (platform apps, hosted apps, component extensions), + policy-installed extensions, and unpacked extensions. See also + Extensions.IncognitoAllowed. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time that elapsed during the GetExtensions call within + ExtensionPrefs::InitPrefStore. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The amount of time for a CSS file to be injected into a page. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken to execute all scripts for one location within an extension. + Recorded every time content scripts injected by extensions are executed. + Unlike Extensions.InjectScriptTime, this includes execution time of + asynchronously injected scripts. + + + + + + + rdevlin.cronin@chromium.org + + Number of blocking scripts injected at document end by extensions. + + + + + + + rdevlin.cronin@chromium.org + Number of scripts injected at document end by extensions. + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken to inject all scripts at document end by extensions. Not reported + if scripts are executed asynchronously. + + + + + + + rdevlin.cronin@chromium.org + + Number of blocking scripts injected at document idle by extensions. + + + + + + + rdevlin.cronin@chromium.org + Number of scripts injected at document idle by extensions. + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken to inject all scripts at document idle by extensions. Not + reported if scripts are executed asynchronously. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Number of blocking scripts injected at document start by extensions. + + + + + + + rdevlin.cronin@chromium.org + Number of css files injected by extensions. + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Number of scripts injected at document start by extensions. + + + + + + rdevlin.cronin@chromium.org + + Time taken to inject css/scripts at document start by extensions. Not + reported if scripts are executed asynchronously. + + + + + kelvinjiang@chromium.org + extensions-core@chromium.org + + Time from first display of the extension installation prompt until the user + aborts the installation through clicking the cancel button or dismissing the + dialog. + + + + + kelvinjiang@chromium.org + extensions-core@chromium.org + + Time from first display of the extension installation prompt until the user + accepts the installation. Will always be greater than 500ms as the install + option is enabled after that time has elapsed. + + + + + meacer@chromium.org + rdevlin.cronin@chromium.org + + Type of the extension install prompt displayed when an extension + installation is triggered. Replaced Extensions.InstallPrompt.Type 2019-07. + + + + + meacer@chromium.org + + Actions on the show details link grouped by action type when the install + prompt trial is running. + + + + + meacer@chromium.org + + Actions on the show permissions link grouped by action type when the install + prompt trial is running. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Installs grouped by the location property in prefs. + + + + + + rdevlin.cronin@chromium.org + Installs grouped by Extension::HistogramType. + + + + peter@chromium.org + + The number of options provided to the GetToken request. Recorded when the + extension has made a call to chrome.instanceID.getToken(). + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + The amount of elapsed time taken to render an icon against a specified + background color and determine whether it would be visible to the user. + Recorded every time the analysis code is called. + + + + + + + rdevlin.cronin@chromium.org + The number of extensions and themes loaded at profile open. + + + + + + rdevlin.cronin@chromium.org + + Time taken to load all component extensions at profile open. This happens as + part of the total initialization time of ExtensionService, measured in + Extensions.ExtensionServiceInitTime. + + + + + + + rdevlin.cronin@chromium.org + + Time taken to load all non-component extensions at profile open and record + metrics. This happens as part of the total initialization time of + ExtensionService, measured in Extensions.ExtensionServiceInitTime. + + + + + + + rdevlin.cronin@chromium.org + The number of apps loaded by each user at profile open. + + + + + + rdevlin.cronin@chromium.org + + The number of externally managed apps loaded by each user at profile open. + + + + + + + rdevlin.cronin@chromium.org + + The number of user-installed apps loaded by each user at profile open. + + + + + + + rdevlin.cronin@chromium.org + + The number of browser action extensions loaded at profile open. + + + + + calamity@chromium.org + + The creation flags of all extensions loaded at profile open grouped by + Extension::InitFromValueFlags. + + + + + + + rdevlin.cronin@chromium.org + The number of extensions loaded at profile open. + + + + + + rdevlin.cronin@chromium.org + + The number of externally managed extensions loaded at profile open. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of user-installed extensions loaded at profile open. + + + + + + + rdevlin.cronin@chromium.org + + The number of externally managed extensions and apps loaded at profile open. + + + + + + + rdevlin.cronin@chromium.org + + The number of hosted apps loaded by each user at profile open. + + + + + + + rdevlin.cronin@chromium.org + + The number of extensions that had neither a page nor browser action + specified in their manifest. Recorded at profile open. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of enabled extensions or apps the user has installed that do not + update from the Chrome Web Store. Recorded during profile initialization. + + + + + + + rdevlin.cronin@chromium.org + + The number of legacy packaged apps loaded by each user at profile open. + + + + + + + rdevlin.cronin@chromium.org + The number of platform apps loaded at profile open. + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + The number of themes loaded at profile open. + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions loaded at profile open grouped by + Extension::HistogramType. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of converted user scripts loaded at profile open. + + + + + isandrk@chromium.org + jhastings@chromium.org + + Records requests to enter or exit locked fullscreen mode through extension + APIs. Used only on Chrome OS. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of times chrome retried to download an extension update manifest with + a url on a google.com domain, before eventually giving up. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of times chrome retried to download an extension update manifest with + a url on a non google.com domain, before eventually giving up. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of times chrome retried to download an extension update manifest with + a url on a google.com domain, before eventually succeeding. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of times chrome retried to download an extension update manifest with + a url on a non google.com domain, before eventually succeeding. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether an icon that's specified in the manifest is considered + visible by our icon analysis code. This stat is only for packed extensions, + which we check dynamically when the icon is requested. The stat is emitted + the first time the default icon is requested, since we cache the icon that's + selected. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether an icon that's specified in the manifest is considered + visible by our icon analysis code. This stat is only for packed extensions, + which we check dynamically when the icon is requested. The stat is emitted + the first time the default icon is requested, since we cache the icon that's + selected. + + This replaces the previous stat, ManifestIconSetIconWasVisibleForPacked, due + to a change to our analysis algorithm. The new algorithm renders the icon + against the toolbar background color and determines how visible the + resulting pixels are. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether loading an icon declarated in the extension's manifest icon + set is considered visible by our icon analysis code. This stat is only for + unpacked extensions, which we check at load time. + + + + + dbertoni@chromium.org + extensions-core@chromium.org + + Reports whether loading an icon declarated in the extension's manifest icon + set is considered visible by our icon analysis code. This stat is only for + unpacked extensions, which we check at load time. + + This replaces the previous stat, ManifestIconSetIconWasVisibleForUnpacked, + due to a change to our analysis algorithm. The new algorithm renders the + icon against the toolbar background color and determines how visible the + resulting pixels are. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of extension loads on startup where it is necessary to reload the + mainfest because the locale has changed. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of extension loads on startup where it is not necessary to reload the + extension's manifest. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of extension loads on startup where it is necessary to reload the + manifest because the extension is unpacked. + + + + + + + rdevlin.cronin@chromium.org + The manifest version of each loaded extension. + + + + rdevlin.cronin@chromium.org + + The number of ports created in a given script context at a specific time. + Recorded once at the destruction of the script context (when no more ports + could be created) if and only if at least one port was created in the + context. Only includes ports to extension contexts (i.e., not ports created + to tabs or native apps). + + + + + rdevlin.cronin@chromium.org + + The total amount of time between when an extension opens a new channel and + when it receives the global port id from the browser and can begin sending + messages. + + + + + rdevlin.cronin@chromium.org + + The amount of synchronous time taken for the renderer to request an + extension message port id from the browser when a new channel is first + opened by an extension. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The size, in bytes, of a message sent from an extension using one of the + messaging APIs (e.g. chrome.runtime.sendMessage). All message sizes are + logged, but messages over 64 MB in size aren't sent. + + + + + rdevlin.cronin@chromium.org + + The amount of time for the renderer to inform the browser process of a new + port being created with a certain id. This replaces the flow for + Extensions.Messaging.GetPortId[A]SyncTime. + + + + + ekaramad@chromium.org + wjmaclean@chromium.org + + Reports the creation of MimeHandlerViews and usage of postMessage for cross + and same origin resources. + + + + + battre@chromium.org + karandeepb@chromium.org + extensions-core@chromium.org + Time that network requests were blocked due to extensions. + + + + battre@chromium.org + karandeepb@chromium.org + extensions-core@chromium.org + + Percentage of total lifetime a network request was blocked due to an + extension. + + + + + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + The number of enabled extensions with a New Tab Page override specified in + their manifest. Recorded once per profile at profile initialization. + + + + + + + rdevlin.cronin@chromium.org + + The number of apps/extensions with a non-webstore update_url loaded at + startup time grouped by Extension::Location. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Number of non-WebStore extensions on startup that override the new tab page. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it is automatically disabled + due to a permission increase (e.g., after an extension upgrade). To find + places where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + AutoDisable. For Sync users, this may be reported for each device, depending + on whether the Sync update or the extension auto-update happen first. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it was installed. To find + places where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + Install. For Sync users, this is reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when installation was aborted (e.g. + because the parent window of the confirmation dialog went away), not + including installation errors and user cancels. To find places where this + histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + InstallAbort. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when installation was canceled. To + find places where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + InstallCancel. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it was loaded (which happens at + profile open or extension install). To find places where this histogram may + be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument Load. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it was re-enabled from a + confirmation prompt. To find places where this histogram may be emitted, + look for calls to ExtensionService::RecordPermissionMessagesHistogram with + the argument ReEnable. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when the re-enable prompt was + aborted (e.g. because the parent window of the confirmation dialog went + away), not including installation errors and manual user cancels. To find + places where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + ReEnableAbort. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when the re-enable was canceled from + the confirmation prompt. To find places where this histogram may be emitted, + look for calls to ExtensionService::RecordPermissionMessagesHistogram with + the argument ReEnableCancel. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it was uninstalled. To find + places where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + Uninstall. For Sync users, this is reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when it was installed through the + web store. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument WebStoreInstall. Contrary to the more-general Permissions_Install3 + histogram, this one is NOT reported for each device. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when installation from the web store + was aborted (e.g. because the parent window of the confirmation dialog went + away), not including installation errors and user cancels. To find places + where this histogram may be emitted, look for calls to + ExtensionService::RecordPermissionMessagesHistogram with the argument + WebStoreInstallAbort. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when installation from the web store + was canceled. To find places where this histogram may be emitted, look for + calls to ExtensionService::RecordPermissionMessagesHistogram with the + argument WebStoreInstallCancel. + + + + + rdevlin.cronin@chromium.org + + The time taken between a user clicking on a button to open a popup, and the + popup finishing loading its initial URL. This is a good way to measure the + UI responsiveness of extension popups. It will be strictly larger than + Extensions.PopupLoadTime2, which only measures the time it takes to load - + there may be a delay between clicking and starting to load, for example, if + the popup's host got caught in a queue. + + + + + rdevlin.cronin@chromium.org + + The time taken for an extension popup to load its initial URL. This may not + include the time taken for an extension process to start, if the extension + already has a background page running. It does not necessarily correlate + with the amount of time since the popup was *clicked* either, since there + may be a delay between the user clicking and the loading started. + Extensions.PopupCreateTime measures this instead. + + + + + tnagel@chromium.org + chrome-privacy-core@chromium.org + + The number of extensions reported in chrome://management ui with powerful + permissions. This number is recorded every time the user opens + chrome://management ui. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time taken to start up persistent background pages for extensions in + ExtensionProcessManager when the extension system notifies that it is ready. + This version of the histogram does not include cases where the background + page startup is deferred, which would have been logged as ~0ms startup in + Extensions.ProcessManagerStartupHostsTime. + + + + + rdevlin.cronin@chromium.org + treib@chromium.org + + Whether the DISABLE_PERMISSIONS_INCREASE disable reason was removed from an + extension while checking for a permissions increase. Recorded during startup + and on reload and update, for each extension that has the + DISABLE_PERMISSIONS_INCREASE reason. + + + + + lazyboy@chromium.org + + The difference in seconds between an extension resource's last modification + time and its extension base directory's creation time. Recorded on each + extension resource request if the difference is non-negative (i.e., the + resource's last modification time is more recent than the directory's + creation time.) For cases where the directory creation date is more recent, + see Extensions.ResourceLastModifiedNegativeDelta instead. + + + + + lazyboy@chromium.org + + The absolute difference in seconds between an extension resource's last + modification time and extension base directory's creation time. Recorded on + each extension resource request if the difference is negative (i.e., the + directory's creation time is more recent than the resource's last + modification time.) For cases where the resource modification time is more + recent, see Extensions.ResourceLastModifiedDelta instead. + + + + + + + rdevlin.cronin@chromium.org + karandeepb@chromium.org + + Whether an extension had host permissions withheld as a result of the + RuntimeHostPermissions feature. Recorded once per extension at profile + initialization if and only if the RuntimeHostPermissions feature is enabled + and the extension requests any host permissions (i.e., could be affected by + the feature). + + + + + + + rdevlin.cronin@chromium.org + karandeepb@chromium.org + + The number of hosts an extension has been granted explicit access to that it + also requested (note that if the user granted unrequested hosts, those will + not be included in this count). Recorded once per extension at profile + initialization if and only if the RuntimeHostPermissions feature is enabled + and the extension has had host permissions withheld. See also + Extensions.RuntimeHostPermissions.ExtensionHasWithheldHosts. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The reason an extension failed to unpack, recorded when a failure occurs. + + + + + achuith@chromium.org + + Whether a CRX file hash sum was the same as in an updater manifest. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Count the number of times a sandboxed CRX unpack succeeds. + + + + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + The number of enabled extensions with a search engine override specified in + their manifest. Recorded once per profile at profile initialization. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken on the settings overridden dialog that was shown to alert + the user of an extension overriding the New Tab Page, when the dialog shown + is the version that asks the user if they want to go back to Google's New + Tab Page. Recorded once per instance of the dialog being shown, after the + action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken on the settings overridden dialog that was shown to alert + the user of an extension overriding the default search provider, when the + dialog shown is the version that asks the user if they want to go back to + Google search. Recorded once per instance of the dialog being shown, after + the action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken on the settings overridden dialog that was shown to alert + the user of an extension overriding the default search provider, when the + dialog shown is the version that asks the user if they want to go back to a + previous search engine that isn't Google. Recorded once per instance of the + dialog being shown, after the action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken on the settings overridden dialog that was shown to alert + the user of an extension overriding the New Tab Page, when the dialog shown + is the generic version. Recorded once per instance of the dialog being + shown, after the action is taken. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action taken on the settings overridden dialog that was shown to alert + the user of an extension overriding the default search provider, when the + dialog shown is the generic version. Recorded once per instance of the + dialog being shown, after the action is taken. + + + + + rdevlin.cronin@chromium.org + kelvinjiang@chromium.org + + The number of enabled extensions with startup page overrides specified in + their manifest. Recorded once per profile at profile initialization. + + + + + rdevlin.cronin@chromium.org + + The amount of synchronous time spent retrieving an extension's message + bundle (the collection of its i18n resources) from the browser. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The duration by which a network request was delayed while waiting for + extension user script load. Recorded once per request that is delayed, at + the time the resource resumes loading. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The source that triggered an extension action. Recorded once per invocation + of an extension action. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that the user has pinned on the toolbar. Recorded + once per profile during initialization if the user has at least one + extension with an action in the toolbar. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The percentage of extensions that the user has pinned to the toolbar (i.e., + this will be 100 if the user has every extension pinned). Recorded once per + profile during initialization if the user has at least one extension with an + action in the toolbar. + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The action that was taken from an extension uninstall dialog. Recorded once + per dialog shown. Only recorded if all possible actions (including report + abuse) were available on the dialog. + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The source for the extension uninstall. This is only recorded if an + uninstall dialog is shown to the user (i.e., it is not recorded for internal + "cleanups"). + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Uninstalls grouped by Extension::HistogramType. + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of legacy packaged apps and hosted apps that were checked during + an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of extensions that were checked during an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of crx's with a Google-hosted update URL that were checked during + an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of crx's with no update URL checked during an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of crx's with a non-Google update URL that were checked during an + update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of packaged apps that were checked during an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of themes that were checked during an update check. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of extensions that were updated at browser startup. + + + + + Please list the metric's owners. Add more owner tags as needed. + Updates grouped by the location property in prefs. + + + + Please list the metric's owners. Add more owner tags as needed. + Updates grouped by Extension::HistogramType. + + + + apotapchuk@chromium.org + anqing@chromium.org + + Tracks the usage of different MIME type handlers used to view files. It is + recorded when the browser intercepts navigation with one of the type + handlers. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records any flags that were registered in the extraInfoSpec of a webRequest + listener, as well as the total number of listeners registered. Recorded each + time a new listener is registered. + + + + + yhirano@chromium.org + kinuko@chromium.org + + Whether and how keepalive requests are blocked. There is a similar histgoram + Net.KeepaliveRequest.BlockStatus. See there for the difference between the + two histograms. + + + + + rockot@chromium.org + + For every network request visible to the Web Request API, this indicates + whether any registered declarative rules or event listeners observed the + onBeforeSendHeaders event. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M69. + + + + + rockot@chromium.org + + For every network request visible to the Web Request API, this indicates + whether any registered declarative rules or event listeners observed the + onHeadersReceived event. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M69. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the request header added by extensions using the WebRequest API. + Recorded for each network request during the OnBeforeSendHeaders stage. + Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the request header modified by extensions using the WebRequest API. + Recorded for each network request during the OnBeforeSendHeaders stage. + Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the request header removed by extensions using the WebRequest API. + Recorded for each network request during the OnBeforeSendHeaders stage. + Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the response header added by extensions using the WebRequest API. + This is logged for the cumulative delta across all the web request + extensions. Recorded for each network request during the OnHeadersReceived + stage. Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the response header modified by extensions using the WebRequest API. + This is logged for the cumulative delta across all the web request + extensions. Recorded for each network request during the OnHeadersReceived + stage. Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Records the response header removed by extensions using the WebRequest API. + This is logged for the cumulative delta across all the web request + extensions. Recorded for each network request during the OnHeadersReceived + stage. Multiple samples can be recorded per request. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + The total time a network request took when at least one Web Request listener + was registered at the start of the request, and a listener was blocked on + the request. Measures from onBeforeRequest to onCompleted/onErrorOccurred, + and does not include canceled or redirected requests. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + The total time a network request took when at least one Web Request listener + with 'extraHeaders' in the extraInfoSpec was registered at the start of the + request. Measures from onBeforeRequest to onCompleted/onErrorOccurred, and + does not include canceled or redirected requests. + + + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + The total time a network request took when at least one Web Request listener + was registered at the start of the request. Measures from onBeforeRequest to + onCompleted/onErrorOccurred, and does not include canceled or redirected + requests. + + + + + + + karandeepb@chromium.org + + Counts the number of times an action is requested by extensions as part of + the Web Request API. For a given web request stage, multiple actions may be + logged. + + + + + karandeepb@chromium.org + extensions-core@chromium.org + + Number of enabled extensions which have requested the + "webRequestBlocking" permission. Includes all kinds of extensions, + including component and unpacked extensions. Recorded during profile + initialization. + + + + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Number of enabled extensions which have requested the "webRequest" + permission. Includes all kinds of extensions, including component and + unpacked extensions. Recorded during profile initialization. + + + + + Please list the metric's owners. Add more owner tags as needed. + The reason a webstore download was interrupted. + + + + Please list the metric's owners. Add more owner tags as needed. + + The number of KBytes received for a webstore download before it was + interrupted. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The total expected size in KBytes of an interrupted webstore download. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Tracks whether the total size of an interrupted webstore download was known. + + + + + dpapad@chromium.org + dbeam@chromium.org + + The amount of time between starting the provisional load and fully loading + the document in the main frame of the chrome://extensions page. This + corresponds to the WebContentsObserver::DocumentLoadedInFrame method. + + + + + dpapad@chromium.org + dbeam@chromium.org + + The amount of time between starting the provisional load and having + completed the onload handler in the main frame of the chrome://extensions + page. This corresponds to the + WebContentsObserver::DocumentOnLoadCompletedInMainFrame method. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/file/histograms.xml b/tools/metrics/histograms/histograms_xml/file/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0b626ed32aa477c4d712ded56153818ba7488dce --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/file/histograms.xml @@ -0,0 +1,813 @@ + + + + + + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: Counts the number of directory-changed events, + bucketed by the RootType of the directory newly displayed. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: number of Computers a user has available in the + Files app. Computed every time the File Browser is opened (including file + picker dialogs). NOTE: This data is biased towards users that use the Files + App more often. + + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS File Browser opening mode. + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: time to scan a directory. Measured on every File + Browser directory change. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Tracks whether download destination is set to a Google Drive folder when the + download destination is changed by the user in the settings page. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Tracks whether download destination is set to a Google Drive folder on + startup. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The size of the space consumed by a users files in "My Files" + folder and it's children, calculated as a percentage of the total disk + space. Caluclated on user login. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The total size of all of the users files stored in the "My Files" + folder and it's children. Caluclated on user login. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: number of files and directories in the Downloads + directory (not including the contents of nested directories). Computed every + time the File Browser current directory changes to Downloads. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The time taken to calculate the hash of a file, only recorded if the time + exceeds a local threshold that is currenty 5 seconds. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The time taken to search for a file using it's hash value, only recorded if + the time exceeds a local threshold that is currently 1 second. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The type of file system provider that has been mounted. This metric is + emmitted on mounting of the filesystem. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: this is recorded when the user adds a folder + shortcut. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: number of saved folder shorcuts. This is recorded + when the Files app is launched. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: this is recorded when the user clicks or selects a + folder shortcut and is navigated to the target folder. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: this is recorded when the user removes a folder + shortcut. + + + + + austinct@chromium.org + + Chrome OS File Browser: this records the filesystem selected when formatting + an external drive. + + + + + slangley@chromium.org + + Chrome OS Files App: Whether an external media device was removed during the + upload process. + + + + + slangley@chromium.org + + Chrome OS Files App: Whether the media import process was cancelled. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The time taken to execute launcher search for drive files. Recorded when the + complete result set is returned from drive. + + + + + slangley@chromium.org + weifangsun@chromium.org + + The time taken to execute launcher search for local files. Recorded when the + complete result set has been calculated for files on the local disk. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser is an built-in extension without a background page. + Its main.html file is loaded every time the user opens a File Browser tab or + a file chooser dialog. The file is fairly large and the initialization is + pretty expensive. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: The locations (root types) of non-top-level entries + when they are expanded or collapsed (expand icon clicked) in the directory + tree. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: The locations (root types) of top-level entries (root + entries) when they are expanded or collapsed (expand icon clicked) in the + directory tree. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: The locations (root types) of non-top-level entries + when they are clicked in the directory tree. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: The locations (root types) of top-level entries (root + entries) when they are clicked in the directory tree. + + + + + slangley@chromium.org + + Chrome OS Files App: Whether the media import (Photos/Video) from external + media was cancelled. + + + + + slangley@chromium.org + + Chrome OS Files App: Count of duplicate media (Photos/Videos) files that + were skipped during a single upload session. + + + + + slangley@chromium.org + + Chrome OS Files App: Number of errors that occured during an upload session. + + + + + slangley@chromium.org + + Chrome OS Files App: Count of individual media (Photos/Videos) uploaded from + a single upload session. + + + + + slangley@chromium.org + + Chrome OS Files App: Size of the media (Photos/Videos) uploaded from a + single upload session. + + + + + slangley@chromium.org + + Chrome OS Files App: Whether the media import (Photos/Video) from external + media was started. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: The commands selected in the menu by the files app. + + + + + fukino@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: Notification types what were shown to the user. + + + + + fukino@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: User actions responding to a notification. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The locations (root types) of files which are opened + by the file picker. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Editor: time to display an image. Measured from the moment + the user selected the image till the moment it is displayed (not counting + the low resolution preview). + + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS Photo Editor: the type of the file opened. + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS Photo Editor: the way the image has been loaded. + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS Photo Editor: time to load an image from a file. + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Editor: the result of a file save operation. + + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS Photo Editor: time to save an image to a file. + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Editor: size of an image file in megabytes. Measured on + every image load. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Editor: size of an image in megapixels. Measured on every + image load. + + + + + slangley@chromium.org + weifangsun@chromium.org + Chrome OS Photo Editor: the button which the user clicked. + + + + slangley@chromium.org + weifangsun@chromium.org + + File dialog type (e.g. Full page, Save as file) when quick view is launched. + + + + + slangley@chromium.org + weifangsun@chromium.org + File types that were tried to be opened with quick view. + + + + slangley@chromium.org + weifangsun@chromium.org + File types that were selected when quick view is launched. + + + + slangley@chromium.org + weifangsun@chromium.org + The volume type where quick view is opened. + + + + slangley@chromium.org + weifangsun@chromium.org + How quick view was opened. + + + + slangley@chromium.org + weifangsun@chromium.org + + Time to load a recently modified file list from Media Views. It is triggered + when the user opens or reloads Recent view in the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Time to load a recently modified file list from Crostini. It is triggered + when the user opens or reloads Recent view in the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Time to load a recently modified file list from Downloads. It is triggered + when the user opens or reloads Recent view in the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Time to load a recently modified file list from Drive. It is triggered when + the user opens or reloads Recent view in the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Time to load a recently modified file list from all sources. It is triggered + when the user opens or reloads Recent view in the Files app. + + + + + lucmult@chromium.org + majewski@chromium.org + Chrome OS File Browser: the source of file sharing action. + + + + lucmult@chromium.org + majewski@chromium.org + + Chrome OS File Browser: The number of files shared via a single Share + action. + + + + + lucmult@chromium.org + majewski@chromium.org + + Chrome OS File Browser: The type of the file shared via Share action. + Recorded for each file being shared by a share action + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: the reason why the suggest apps dialog was closed. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: whether the Webstore item user selected was + successfully installed or not. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: whether the initialization of the dialog succeeded + or not. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: time to load the suggest apps dialog. Measured + between the moment window appears and the moment all the contents in the + dialog including the Chrome Webstore widget are ready. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: number of Team Drives a user has available in the + Files app. Computed every time the File Browser is opened (including file + picker dialogs). NOTE: This data is biased towards users that use the Files + App more often. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Files App: Recorded when the Grid View/List View toggle menu icon + is selected. + + + + + slangley@chromium.org + weifangsun@chromium.org + + File types that were tried to be viewed through browser. This is recorded + when the user tries to view a file from the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + File types that were tried to be viewed through browser while the user is + offline. This is recorded when the user tries to view a file from the Files + app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + File types that were tried to be viewed through browser while the user is + online. This is recorded when the user tries to view a file from the Files + app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The locations (root types) of files which are opened + in stand-alone mode. This does not include files opened in file picker mode. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The locations (root types) of files which are opened + in stand-alone mode while the user is offline. This does not include files + opened in file picker mode. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The locations (root types) of files which are opened + in stand-alone mode while the user is online. This does not include files + opened in file picker mode. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The type of the handler to be used to open files. + This is recorded when the user tries to view a file from the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The type of the handler to be used to open files + when the user is offline. This is recorded when the user tries to view a + file from the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: The type of the handler to be used to open files + when the user is online. This is recorded when the user tries to view a file + from the Files app. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: counts the number of times volumes are mounted for + each volume type. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: counts the number of times ZIP file was opened or + created, categorized by component extensions and its operation types. + + + + + mek@chromium.org + + For each FileReaderSync instance records the type of the web worker that + created the instance. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + The result of FileSystemDirectoryDatabase initialization. + + + + tzik@chromium.org + The result of FileSystemDirectoryDatabase repair. + + + + tzik@chromium.org + + The success or the cause of failure for each call to OpenFileSystem(). + + + + + tzik@chromium.org + The result of opening a filesystem. + + + + tzik@chromium.org + The result of opening a non-throttled filesystem. + + + + + + dmurph@chromium.org + pwnall@chromium.org + The result of FileSystemOriginDatabase initialization. + + + + tzik@chromium.org + + Number of origins that have persistent filesystem. Measured when the Quota + system queries the filesystem subsystem about its entire usage, which + usually happens when one of the storage subsystem methods is called for the + first time. + + + + + tzik@chromium.org + + Number of origins that have temporary filesystem. Measured when the Quota + system queries the filesystem subsystem about its entire usage, which + usually happens when one of the storage subsystem methods is called for the + first time. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/Fingerprint/histograms.xml b/tools/metrics/histograms/histograms_xml/fingerprint/histograms.xml similarity index 97% rename from tools/metrics/histograms/histograms_xml/Fingerprint/histograms.xml rename to tools/metrics/histograms/histograms_xml/fingerprint/histograms.xml index 8045ed3b63fe1e238ff7d4850c5d71fd86d8a9c6..24e5f3def437e737c9512db238b7cfba4026d431 100644 --- a/tools/metrics/histograms/histograms_xml/Fingerprint/histograms.xml +++ b/tools/metrics/histograms/histograms_xml/fingerprint/histograms.xml @@ -1,5 +1,5 @@ @@ -11,9 +11,6 @@ along with a detailed description for each histogram. For best practices on writing histogram descriptions, see https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md -For brief details on how to modify this file to add your description, see -https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/one-pager.md - Please send CLs to chromium-metrics-reviews@google.com rather than to specific individuals. These CLs will be automatically reassigned to a reviewer within about 5 minutes. This approach helps the metrics team to load-balance incoming diff --git a/tools/metrics/histograms/histograms_xml/gcm/histograms.xml b/tools/metrics/histograms/histograms_xml/gcm/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..4007f74fd72dc24f2409173e77a85e367fae6575 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/gcm/histograms.xml @@ -0,0 +1,465 @@ + + + + + + + + + + peter@chromium.org + knollr@chromium.org + + Records that a message has been received from a delivery channel powered by + the GCM account mappings. + + + + + peter@chromium.org + zea@chromium.org + Status code of the outcome of a GCM checkin request. + + + + peter@chromium.org + knollr@chromium.org + + Network error code for a GCM checkin request that failed because of a + network error. + + + + + zea@chromium.org + URL response and error codes from GCM disconnect events. + + + + zea@chromium.org + Number of connections made to each specific MCS endpoint. + + + + zea@chromium.org + URL response and error codes from GCM connection attempts. + + + + peter@chromium.org + zea@chromium.org + + The time between the initiation of a connection and the successful + completion of it. + + + + + zea@chromium.org + Reasons for GCM connection resets. + + + + zea@chromium.org + + GCM connection success rate. Does not take into account login success. See + GCM.ConnectionFailureErrorCode for a breakdown of connection failure + reasons. + + + + + zea@chromium.org + + Time (from login until reset) that a GCM connection was active. + + + + + peter@chromium.org + zea@chromium.org + + Success rate of writing new keying material to the GCM key store. + + + + + + + peter@chromium.org + zea@chromium.org + + Result of decryption on a received GCM message, which includes unencrypted + messages, successfully decrypted messages and decryption failures. + + + + + peter@chromium.org + alexchau@chromium.org + + Result of encryption of outgoing GCM message, which includes successfully + encrypted messages and encryption failures. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + Result of upgrading GCM Key Store Database from deprecated format to current + format. We upgrade the GCM Key store when it first initialized, if it + contains any EncryptionData object with a KeyPair in it, and then record + whether the upgrade was successful in this metric. + + + + + peter@chromium.org + zea@chromium.org + + Success rate of reading keying material from the GCM key store. + + + + + peter@chromium.org + zea@chromium.org + + Success rate of initializing the LevelDB back-end of the GCM key store. + + + + + peter@chromium.org + zea@chromium.org + + Success rate of loading existing keying material in the GCM key store. + + + + + peter@chromium.org + zea@chromium.org + + Success rate of removing keying material from the GCM key store. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + peter@chromium.org + The result of a database open attempt by the GCM store. + + + + peter@chromium.org + zea@chromium.org + + Number of DATA_MESSAGE messages received from Google Cloud Messaging for + which a matching registration exists. Recorded when processing the received + message. Prior to M56 this also counted received DELETED_MESSAGES messages + (whether or not a registration existed). + + + + + peter@chromium.org + + Records whether a non-empty collapse_key token is set for each received + DATA_MESSAGE message from Google Cloud Messaging for which a matching + registration exists. Recorded while processing the received message. + + + + + peter@chromium.org + + For every DELETED_MESSAGES message received from Google Cloud Messaging + (whether or not a matching registration exists), this records the provided + count of how many messages were simultaneously deleted, or zero if the count + is unknown. + + + + + peter@chromium.org + mamir@chromium.org + + Whether a received GCM message could be delivered to an app handler. + Recorded for each received GCM message that didn't have encryption issues. + + + + + zea@chromium.org + + If a heartbeat was missed, the time delta by which it was missed (in system + time, not ticks). + + + + + peter@chromium.org + + Number of SEND_ERROR messages received from Google Cloud Messaging. Recorded + when processing the received message. + + + + + jianli@chromium.org + Status code of loading from the persistent GCM store. + + + + zea@chromium.org + + Number of applications hitting GCM per-app outstanding message limits at + startup time. + + + + + peter@chromium.org + + Number of connection events which have not been sent to GCM. This is + recorded only at the time of shutdown to capture the events which are being + lost due to shutdown. Because this is recorded at shutdown, this is not + guaranteed to be complete and should be treated as a best effort record. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + Reports the status of cached GCM registration. This is recorded when a new + registration request is considered on the GCM client. + + + + + peter@chromium.org + + Number of registration requests sent to Google Cloud Messaging. Recorded + immediately after the request has started. + + + + + peter@chromium.org + platform-capabilities@chromium.org + + Net error code from a GCM registration attempt. Recorded when URL loading + completes. + + + + + peter@chromium.org + + Status code of the outcome of a GCM registration request. The Unknown error + case was split up in M56 (merged mid-beta to M55) to separate out the + Response parsing failed, Internal server error, Quota exceeded, and Device + has too many registrations cases. + + + + + jianli@chromium.org + Number of sender IDs specified in a registration request. + + + + msarda@chromium.org + chrome-signin-team@google.com + + Number of times that account mapping entries are deleted from or kept in the + GCM store database while loading them in memory. Used during the account ID + migration from email to Gaia ID. + + + + + zea@chromium.org + + Reports the problem encountered when resetting the GCM store. + + + + + zea@chromium.org + + Number of unacknowledged incoming messages restored from the persistent + store at startup. + + + + + zea@chromium.org + + Number of pending outgoing messages restored from the persistent store at + startup. + + + + + peter@chromium.org + + Number of registrations restored from the persistent store at startup. + + + + + peter@chromium.org + + Result of sending an upstream message through Google Cloud Messaging. + Recorded when the message has either been queued, sent, or has been dropped + because it expired or an error happened. + + + + + alexchau@chromium.org + peter@chromium.org + + Size of web push messages payload. Recorded right before the message is + sent. + + + + + alexchau@chromium.org + peter@chromium.org + + Result of sending web push messages. Recorded when the message has either + been sent, or has been dropped because an error happened. + + + + + alexchau@chromium.org + peter@chromium.org + + Result code from sending web push messages. Logs net::Error if it's not + net::OK. Logs net::OK if response header is not present. Otherwise, logs + HTTP status code returned. Recorded when received response after message has + been sent. + + + + + zea@chromium.org + + Success indicates successfully destroying the GCM persistent store. Failure + indicates a failure destroying the persistence store. GCM store will be + destroyed when the profile has been signed out. + + + + + zea@chromium.org + Size of the GCM persistent store in kilobytes at startup. + + + + zea@chromium.org + + Success indicates successfully updating the GCM persistent store on message + update. Failure indicates a failure updating the persistence store. + + + + + zea@chromium.org + Time elapsed from machine suspend until resume. + + + + peter@chromium.org + zea@chromium.org + Status code of the outcome of a GCM unregistration request. + + + + jianli@chromium.org + + Indicates whether the user was signed in when GCM started up. + + + + + knollr@chromium.org + peter@chromium.org + + Device state when receiving a web push message. Indicates if the message was + sent with a high priority and if the device was in idle mode. Recorded when + a web push message got received. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/geolocation/histograms.xml b/tools/metrics/histograms/histograms_xml/geolocation/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..8b3bbd6d8242a7981faa5084fd7da8b3136673d4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/geolocation/histograms.xml @@ -0,0 +1,239 @@ + + + + + + + + + + mattreynolds@chromium.org + device-dev@chromium.org + + Records the action performed by an existing user when prompted to authorize + the use of location by Chrome. + + + + + mattreynolds@chromium.org + device-dev@chromium.org + + Records the action performed by a new user when prompted to authorize the + use of location by Chrome. + + + + + kcarattini@chromium.org + dominickn@chromium.org + + For Geolocation requests from the omnibox on Android, the time since the + location was most recently acquired. If no location has been acquired, the + maximum bucket is incremented. + + + + + kcarattini@chromium.org + dominickn@chromium.org + + Counts Geolocation requests for omnibox searches sliced by various + permission combinations. The location mode abbreviations indicate one of: + High Accuracy, Battery Saving, GPS On or Location Mode Off. + + + + + kcarattini@chromium.org + dominickn@chromium.org + + For Geolocation requests from the omnibox on Android, the time since the + location was first acquired. If no location has been acquired, the minimum + bucket is incremented. + + + + + kiyun@google.com + mvanouwerkerk@chromium.org + newt@chromium.org + + Reason why the X-Geo header was or was not included in a Google search from + the omnibox. + + + + + mattreynolds@chromium.org + device-dev@chromium.org + Error code for the geoposition sent to the renderers. + + + + mattreynolds@chromium.org + device-dev@chromium.org + + The number of WiFi access points used to determine geolocation. + + + + + mattreynolds@chromium.org + device-dev@chromium.org + Events in NetworkLocationRequest. + + + + mattreynolds@chromium.org + device-dev@chromium.org + Http response codes in NetworkLocationRequest. + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + For each query into the position cache used by the network location + provider, records whether a position was returned from the cache. + + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + For each query into the position cache used by the network location + provider, records the number of items in the cache. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the backoff level when the Location Settings Dialog is accepted by + the user. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the backoff level when the Location Settings Dialog is rejected by + the user. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the backoff level when the Location Settings Dialog is shown to the + user. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the backoff level when the Location Settings Dialog is suppressed + due to backoff. + + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + Counts Geolocation request timeout values, bucketing by timeout duration. + This is recorded for all requests upon creation, see + Geolocation.TimeoutExpired for timeouts that actually expired. + + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + Counts Geolocation request timeout expirations, bucketing by timeout + duration. This means no position was received within the allowed time from + the browser process due to e.g. a slow network or an unresponsive system + location provider. + + + + + benwells@chromium.org + + Records the action the user took after the geolocation disclosure has been + displayed. + + + + + benwells@chromium.org + + Records how long the search geolocation disclosure infobar was visible for. + + + + + benwells@chromium.org + + Records the geolocation default search engine setting after the search + geolocation disclosure has been shown and won't be shown again. This metric + is only recorded once per client. + + + + + benwells@chromium.org + + Records the geolocation default search engine setting immediately before the + search geolocation disclosure has been shown. This metric is only recorded + once per client. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/google/histograms.xml b/tools/metrics/histograms/histograms_xml/google/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..cee60bca0bfeeb13df9b806c37b44450c4bffe9c --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/google/histograms.xml @@ -0,0 +1,220 @@ + + + + + + + + + + grt@chromium.org + The HRESULT for a failed on-demand update check. + + + + shaktisahu@chromium.org + + (Android-only) The amount of internal memory storage that is free on the + file system and available to the applications when the InfoBar or update + menu item is shown. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Records the instances where Play update API returned the + current install status of inline updates. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Records the instances where Play update API returned the + current availability of inline updates. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Records the instances where Play update API calls failed. + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Records the instances where Play update API notified us of an + install error during an update. This is keyed on the specific state so we + can tell which states are seeing which errors. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) The UI component that triggered an inline update to finish + and install. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) The UI component that triggered an inline update to retry. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) The UI component that triggered an inline update to start. + + + + + nikunjb@chromium.org + chrome-metrics-team@google.com + + Store the hash of update cohort name as reported by Chrome Updater on + Windows. Recorded at the start of metrics service. + + + + + grt@chromium.org + + The exit code from Chrome's installer following a failed on-demand update + check. All values reported for this histogram fall in the + GOOGLE_UPDATE_ERROR_UPDATING bucket of the GoogleUpdate.UpdateErrorCode + histogram and the GOOPDATEINSTALL_E_INSTALLER_FAILED bucket of the + GoogleUpdate.ErrorHresult histogram. + + + + + twellington@chromium.org + + (Android-only) Records whether Chrome was updated after the update menu item + was clicked. + + + + + twellington@chromium.org + + (Android-only) Records whether the update menu item was clicked when the app + menu was opened. + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Whether or not an update was successful when looking at the + Chrome version on the next session where there is no update in progress. + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Whether or not an update was successful within a specific + server-configured window of time (e.g. an update may not occur right after + the user attempts to start it, but if they update sometime in the next X + days, we can possibly attribute it to the update flow we started). An + example window value could be on the order of days (e.g. 2 days since an + update started). + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) Whether or not an update was being tracked as 'in progress' + when another update was started. + + + + + dtrainor@chromium.org + nyquist@chromium.org + + (Android-only) The state of any in-progress updates when the process first + starts and queries for it. + + + + + grt@chromium.org + + An unrecognized CurrentState value received from Google Update while polling + for the status of an on-demand update check. + + + + + grt@chromium.org + The error code for a failed on-demand update check. + + + + grt@chromium.org + The result of an on-demand update check. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/gpu/histograms.xml b/tools/metrics/histograms/histograms_xml/gpu/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..284667d3914c8a01b6513687f896f95127af848a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/gpu/histograms.xml @@ -0,0 +1,1304 @@ + + + + + + + + + + vmiura@chromium.org + + Refresh rate of the display in Hz. This is recorded every time we present a + frame. + + + + + cwallez@chromium.org + + The sum of the size of the CPU-side memory allocations of Buffer11's copies + (vs. GPU memory allocations). These allocations are used when modifying the + buffer data on the CPU or when transfering to GPU memory via DMA. + + + + + jmadill@chromium.org + + An extended Windows error code returned from D3D11CreateDevice on error. Can + be almost any valid HRESULT or DXGI error code, which are listed at + https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx. + + + + + jmadill@chromium.org + + The maxmium supported (or currently requested) Direct3D feature level in + D3D11 ANGLE. We support as low as 9.3, and as high as 11.1, though Chrome + should only use 10.0+ for D3D11. Gives an indication of how new a user's + video card is, what features it supports, and it's general speed tier. + + + + + jonahr@google.com + angle-team@google.com + + The result from initializing a D3D11 device in ANGLE. Can be success, or one + of several error codes which indicate different reasons for failing. + + + + + jmadill@chromium.org + + The result from initializing a D3D9 device in ANGLE. Can be success, or one + of several error codes which indicate different reasons for failing. + + + + + jonahr@google.com + angle-team@google.com + + The time ANGLE spends calling the D3D shader compiler. Tracks total time we + spend compiling shaders on startup and during Chrome's lifetime. + + + + + jonahr@google.com + angle-team@google.com + + Time ANGLE spends in eglInitialize, where it spins up a Renderer. This can + gives us insight into how much time we're spending initializing the GPU. + + + + + jmadill@chromium.org + + The time to load a gpu program from the program cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + jmadill@chromium.org + + The time to link a gpu program. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + jmadill@chromium.org + + If a successfully linked program was found in the GPU program cache during a + program link call, and if the hit was originally loaded from disk. + + + + + jonahr@google.com + angle-team@google.com + + Records if the call to load a cached binary was successful. This can + legitimately fail if the driver wants chrome to re-link and re-cache the gpu + program. + + + + + jmadill@chromium.org + + The size of program binaries loaded into the gpu program cache. + + + + + jmadill@chromium.org + + Windows computers running Windows 8+, or running Windows 7 with a platform + update, support the newer version of DXGI. This update also indicates the + computer is capable of running Direct3D 11.1 if the hardware supports it. + + + + + forshaw@chromium.org + wfh@chromium.org + + On Windows 10 version RS1 and above the GPU can be sandboxed using an + AppContainer. This is recorded every time the GPU sandbox is initialized and + enabling the AppContainer is requested, such as through a command line + option. The recorded value can indicate that the AppContainer was disabled + due to an incompatible configuration or the GPU process had previously + crashed resulting in the AppContainer being forcefully disabled. + + + + + forshaw@chromium.org + wfh@chromium.org + + On Windows 10 version RS1 and above the GPU can be sandboxed using an + AppContainer. This indicates the status when initializing the sandbox + profile during process creation. + + + + + vmiura@chromium.org + + The number of surfaces that the GPU process was rendering to right before + exiting. This should be equal to the number of tabs (both visible and + hidden) rendering via the compositor. + + + + + vmiura@chromium.org + + Counts number of browser invocations for which a GPU feature is + allowed/blacklisted/disabled. + + + + + vmiura@chromium.org + + Counts number of browser invocations for which a GPU feature is + allowed/blacklisted/disabled in various Windows sub-versions. + + + + + vmiura@chromium.org + + Counts number of browser invocations for which a disabled blacklist entry is + matched. + + + + + vmiura@chromium.org + + Counts number of browser invocations for which the GPU process is blocked + due to a blacklist entry match. + + + + + vmiura@chromium.org + + The time that the GPU process spends collecting driver information during + startup. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + kylechar@chromium.org + + Records what compositing mode (software, GL, etc.) Chrome is using every + five minutes. This is the default compositing mode that most windows will + use. There are some window types (eg. menus on some platforms) that always + use software compositing and ignore the default. + + + + + sievers@chromium.org + + The reason a GPU command buffer context of a given type was lost. + + + + + ericrk@chromium.org + The amount of memory used by a GL Context. + + + + vmiura@chromium.org + Whether D3D11 supports B8G8R8A8 format for render targets. + + + + vmiura@chromium.org + Whether D3D11 supports B8G8R8A8 format for 2D textures. + + + + sadrul@chromium.org + zmo@chromium.org + + Records the highest D3D_FEATURE_LEVEL available, collected in the info + collection GPU process, once per UMA ping. This is Windows platform only. + + + + + vmiura@chromium.org + magchen@chromium.org + + The maximum D3D12 feature level supported in the gpu drivers. It is recorded + 15 seconds after the browser launch. + + + + + jmadill@chromium.org + + ANGLE's currently active D3D shader model version. Logged once every startup + of the GPU process, on Windows only. Note that Shader Models 2 and 3 map to + D3D9 with ANGLE, and 4+ map to D3D11 ANGLE. + + + + + sunnyps@chromium.org + zmo@chromium.org + + If the system approves a swap chain's custom present duration request, this + is the approved custom present duration. If the swap chain's custom present + duration request is not approved, this is zero. + + + + + sunnyps@chromium.org + zmo@chromium.org + + How the Desktop Window Manager presented Chrome's DirectComposition layers + to the screen. + + + + + zmo@chromium.org + graphics-dev@chromium.org + + How the Desktop Window Manager presented Chrome's main DirectComposition + layer to the screen. + + + + + zmo@chromium.org + rafael.cintron@microsoft.com + + HRESULT return value of IDXGIFactory2::CreateSwapChainForComposition. + + + + + magchen@chromium.org + zmo@chromium.org + + HRESULT return value of ID3D11VideoDevice::CreateVideoProcessorEnumerator in + Direct Composition InitializeVideoProcessor. + + + + + sunnyps@chromium.org + zmo@chromium.org + + Recorded for each texture quad (on overlay processing) the reason it was or + wasn't put in an overlay. + + + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded for each quad (on overlay processing) with protected video type the + reason it was or wasn't put in an overlay. + + + + + magchen@chromium.org + zmo@chromium.org + + HRESULT return value of IDCompositionDevice2::CreateSurface. + + + + + sunnyps@chromium.org + zmo@chromium.org + + Result of calling CreateDecodeSwapChainForCompositionSurfaceHandle. Recorded + when decode swap chain is created. + + + + + sunnyps@chromium.org + zmo@chromium.org + + The reason decode swap chain wasn't used to present a video frame. Recorded + on each present. See also GPU.DirectComposition.VideoPresentationMode. + + + + + sunnyps@chromium.org + zmo@chromium.org + + How many frames since the last time the layer color format was changed. + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded for each video quad during the video playback whether it is an + underlay or an overlay + + + + + sunnyps@chromium.org + zmo@chromium.org + + Number of presented frames for which presentation queries haven't completed. + Recorded on each vblank. + + + + + sunnyps@chromium.org + zmo@chromium.org + + Which overlay format was chosen for YUV overlays. Recorded once per GPU + process launch only if hardware overlays are supported. + + + + + sunnyps@chromium.org + zmo@chromium.org + True if Chrome will try to use DirectComposition overlays. + + + + sunnyps@chromium.org + zmo@chromium.org + Whether or not a frame displays an overlay. + + + + + + sunnyps@chromium.org + zmo@chromium.org + + Whether creating swap chain for overlay format succeeded. Recorded once per + swap chain creation. + + + + + + + magchen@chromium.org + zmo@chromium.org + + Whether creating swap chain for protected video succeeded. Recorded once per + swap chain creation. + + + + + sunnyps@chromium.org + zmo@chromium.org + + What format was used for each overlay swap chain on each swap buffers. + + + + + magchen@chromium.org + zmo@chromium.org + + HRESULT return value of ID3D11Device::CreateTexture2D in Direct Composition + UploadVideoImages for creating a copy texture. + + + + + magchen@chromium.org + zmo@chromium.org + + HRESULT return value of ID3D11Device::CreateTexture2D in Direct Composition + UploadVideoImages for creating a staging texture. + + + + + magchen@chromium.org + zmo@chromium.org + + HRESULT return value of ID3D11VideoDevice::CreateVideoProcessor in Direct + Composition InitializeVideoProcessor. + + + + + sunnyps@chromium.org + zmo@chromium.org + + What code path was used to present a video frame. Recorded on each present. + + + + + jonahr@google.com + angle-team@google.com + + The time we spend in GLES2DecoderImpl::DoLinkProgram. Related to how much + time we spend compiling shaders during startup. + + + + + + + vmiura@chromium.org + kbr@chromium.org + zmo@chromium.org + + For every entry in the gpu driver bug list that is hit on a machine, this + records the id. Entry 0 is the total number of times that data is recorded. + It should be recorded whenever new GPU information is received: on startup, + whenever a GPU process launches, and whenever the active GPU changes. + + + + + jbauman@chromium.org + The display type used to ask for an EGLDisplay. + + + + zmo@chromium.org + vmiura@chromium.org + The error states generated by OpenGL calls. + + + + reveman@chromium.org + + Whether GLFence support is available. Recorded each time a new context group + is initialized and extensions are detected. + + + + + magchen@chromium.org + zmo@chromium.org + + Records the OpenGL implementation mode. Recorded during GPU process + initilization. + + + + + vasilyt@chromium.org + backer@chromium.org + + This metric recorded only with --enable-gpu-blocked-time flag. This is + logged once per frame if the output surface provides timing information. It + measures the time Gpu Main thread was blocked (difference between wall time + and cpu time) during tasks execution for currect frame. Only reported when + there is single surface swap in the same vsync interval. Only reported for + platforms supporting high resolution clocks. + + + + + magchen@chromium.org + zmo@chromium.org + + The wait time between the IPC message sent from the GPU channel host and the + event sync from the GPU process. If the wait time takes longer than 120 + seconds, 120 seconds will be recoreded. + + + + + magchen@chromium.org + zmo@chromium.org + + The time between the GPU process starts and the GPU Info is collected at GPU + process startup and recorded in browser process when this piece info is sent + back to browser process. The range is between 200ms and 5s. + + + + + wnwen@chromium.org + + Breakdown of exit status for gpu processes. Only recorded on Android. + + + + + jbauman@chromium.org + + Counts for the exit codes returned by the GPU process when it terminated. + + + + + vmiura@chromium.org + + Whether the GPU process successfully initialized or failed and then exitted + normally. + + + + + vmiura@chromium.org + + Startup time of the GPU process as measured by the GPU process host. + + + + + rjkroege@chromium.org + msisov@igalia.com + + The reason a GPU process is terminated. It works only when + TERMINATION_STATUS_PROCESS_WAS_KILLED TerminationStatus is set. The goal of + this histogram is to get spikes of the above mentioned case when + Ozone/Wayland terminates the GPU process due to invalid data it received if + any. + + + + + vmiura@chromium.org + + Counts for each time the GPU Process Host detects the process dies. + + + + + sadrul@chromium.org + zmo@chromium.org + + Records whether the system has a discrete GPU, collected in the info + collection GPU process, once per UMA ping. This is Windows platform only. + + + + + jonahr@google.com + angle-team@google.com + + The time that the GPU process spends in initializing the GL surface, and + collecting graphics information. Records times up to three minutes. + + + + + sadrul@chromium.org + zmo@chromium.org + + Records the highest Intel GPU generation of the system using the GPU info + collected at GPU process startup time, once per UMA ping. + + + + + sunnyps@chromium.org + zmo@chromium.org + + Records user device's GPU series type. Only recorded on Windows platform at + GPU process launch time. Only meaningful with Intel GPUs. + + + + + ccameron@chromium.org + + The time that it took to update the CALayer tree and commit the transaction. + This is often affected by IOSurface paging. + + + + + ccameron@chromium.org + + The time that it took for a call to IOSurfaceCreate to complete. + + + + + ccameron@chromium.org + + The time that it took for a call to glFlush to complete. This is often + affected by IOSurface paging. + + + + + ccameron@chromium.org + + The time that it took for a call to CGLTexImageIOSurface2D to complete. + + + + + senorblanco@chromium.org + + The maximum number of multisampled anti-aliasing (MSAA) samples per pixel + that the user's GPU can render. + + + + + khushalsagar@chromium.org + + During OutOfProcess(Oop) raster, the renderer generates and sends the + requisite glyph data for rasterizing a tile with the serialized paint + commands. If the data for any glyph is missing, the GPU process attempts to + use a fallback glyph from the cache. This records each time we encounter a + cache miss on the GPU and whether we could use a fallback. + + + + + hubbe@chromium.org + media-dev@chromium.org + + Records the output color space of the monitor as reported by Windows. + Recorded once for each monitor when the gpu process starts. If monitor + enumeration fails, this metric will not be provided. + + + + + hubbe@chromium.org + media-dev@chromium.org + + Records if any connected monitor is HDR capable. Recorded when the gpu + process starts. Only recorded on Windows as of M-61. If monitor enumeration + fails, this metric will not be provided. + + + + + jonahr@google.com + angle-team@google.com + + The time we spend in GLES2DecoderPassthroughImpl::DoLinkProgram. Related to + how much time we spend compiling shaders during startup. + + + + + vmiura@chromium.org + + Recorded once for every GPU process launch and crash when GPU process is + started for the display compositor with software compositing. Crash buckets + are based on crash count for disabling features. No hardware acceleration + and no SwiftShader WebGL will be run. + + + + + vmiura@chromium.org + + Recorded once for every GPU process launch and crash when GPU process is + started for hardware accelerated GPU compositing and/or WebGL. Crash buckets + are based on crash count for disabling features. With OOP-D enabled the + display compositor also runs in the GPU process. + + + + + vmiura@chromium.org + + Recorded once for every GPU process launch and crash when GPU process is + started for SwiftShader WebGL. Crash buckets are based on crash count for + disabling features. With OOP-D enabled the display compositor with software + compositing will also run as part of the GPU process. + + + + + vmiura@chromium.org + + The time to load a gpu program from the program cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + + The time to link a gpu program. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + jonahr@google.com + angle-team@google.com + + If a successfully linked program was found in the GPU program cache during a + program link call. + + + + + vmiura@chromium.org + + The time to check the program cache that we've already compiled the shader. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + + The time to compile a shader. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + zmo@chromium.org + graphics-dev@chromium.org + + Whether or not a {FORMAT_TYPE} fbo is complete and renderable. + + + + + + + + + + + + + + + + vmiura@chromium.org + wfh@chromium.org + + Whether or not the GPU sandbox properly initialized. Failures are typically + platform- and driver-specific (e.g. driver creating threads on Linux). + + + + + kylechar@chromium.org + chrome-gpu-metrics@google.com + + Records the wall time taken for each GPU scheduler task to run. The time + delta starts when the GPU scheduler pops the task off the task queue and + finishes when the task has completed. Only recorded for clients with high + resolution clocks. + + + + + vmiura@chromium.org + + Counts activation and deactivation of accelerated compositing. + + + + + ericrk@chromium.org + + Whether or not the shader prefix loaded from disk matched the expected + prefix for the data and system configuration. False indicates either disk + corruption or a system configuration change, and should be rare. + + + + + penghuang@chromium.org + backer@chromium.org + + Whether or not the content of a SharedImage is consumed. False indicates the + content of a SharedImage is never used due to destroying the SharedImage or + writing new content to it before using it. + + + + + samans@chromium.org + viz-team-wat@google.com + + Time it took to acquire the lock in SharedImageManager. Recorded only when + the manager is thread-safe. Ignores clients with no high-resolution clock. + + + + + sadrul@chromium.org + zmo@chromium.org + + Collects whether Chrome uses software renderer or hardware GPU 20 seconds + after Chrome starts, and records this value once per UMA ping. This value is + not re-collected at each recording time because GPU process could crash for + various reasons and fall back to software rendering. This value is intended + to reflect device capabilities rather than the current state. + + + + + vmiura@chromium.org + + Records whether a client was selected for the Stage3D on XP field trial or + not. + + + + + vmiura@chromium.org + magchen@chromium.org + + This metric shows whether the GPU supports D3D12. It is recorded 120 seconds + after the browser launch. + + + + + vikassoni@chromium.org + + Counts the error code which is returned when AImageReader api call + acquireLatestImageAsync fails. + + + + + vasilyt@chromium.org + backer@chromium.org + + This is logged once per frame if the output surface provides timing + information. It measures the time of SwapBuffers call. Only reported when + there is single surface swap in the same vsync interval. Only reported for + platforms supporting high resolution clocks. + + + + + reveman@chromium.org + + Whether RG texture support is available. Recorded each time a new context + group is initialized and extensions are detected. + + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + + The amount of time required to create an external VkSemaphore. Only reported + for platforms supporting high resolution clocks. + + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + + The amount of time required to get a file handle from a VkSemaphore. Only + reported for platforms supporting high resolution clocks. + + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + The number of semaphores imported into GL per frame. + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + + The amount of time required to import a VkSemaphore from a file handle. Only + reported for platforms supporting high resolution clocks. + + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + + The amount of time required to import a VkSemaphore into GL. Only reported + for platforms supporting high resolution clocks. + + + + + backer@chromium.org + penghuang@chromium.org + vasilyt@chromium.org + + The number of vkQueueSubmit() calls per SwapBuffers. It is recorded when + SwapBuffers() call is completed or skipped. + + + + + stanisc@chromium.org + + Whether WaitForVBlank operation has been successful or failed with one of + the errors prompting a backup delay based v-sync mechanism. Recorded each + time a new GPU v-sync signal is generated. + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded for each time the GPU watchdog thread starts, crashes and ends. + This includes data from both watchdog V1 and V2. + + + + + + + magchen@chromium.org + zmo@chromium.org + + The number of extra timeouts the GPU main thread needs to make any progress + after the first watchdog timeout. + + + + + magchen@chromium.org + zmo@chromium.org + + Records the number of the watchdog timeout functions being entered at each + timeout after allowing the GPU to finish the current job with extra thread + time. If the user decides to quite Chrome, the recorded count would decrease + at the next timeout. + + + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded timeout events when the GPU watchdog V2 enters OnWatchdogTimeout. + + + + + + + magchen@chromium.org + zmo@chromium.org + + Record the wait time in OnWatchdogTimeout() for the GPU main thread to make + any progress. + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded every second in a 60-second loop that the watchdog was still + running after allowing the GPU to complete the current job within 60 + seconds. If any of the users decided to quit Chrome, the recorded count + would decrease at the next second. + + + + + magchen@chromium.org + zmo@chromium.org + + Recorded the time the GPU main thread makes any progress after allowing the + GPU to complete the current job within 60 seconds. + + + + + vmiura@chromium.org + + Counts of context initialization that succeed or fail based on combinations + of attributes requiring canRecoverFromContextLoss and devices that report + can_lose_context. Failing Init is desired when a device can not guarantee it + won't fail for a user that can not handle failures, e.g. DX9 on WinXP used + by Canvas2D' + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) gaming graphics score. It is in + the range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 + represents a failure to get the score. This is collected each time Chrome is + launched. + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) gaming graphics score, scaled by + 10x. It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 + represents a failure to get the score. This is collected each time Chrome is + launched. + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) graphics score. It is in the + range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a + failure to get the score. This is collected each time Chrome is launched. + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) graphics score, scaled by 10x. + It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 + represents a failure to get the score. This is collected each time Chrome is + launched. + + + + + vmiura@chromium.org + + A boolean representing whether or not we succeeded in getting the system's + WinSAT scores. This is collected each time Chrome is launched. + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) overall system score. This is + the minimum of all the individual subscores. It is in the range 1.0-5.9 on + Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a failure to get + the score. This is collected each time Chrome is launched. + + + + + vmiura@chromium.org + + The WinSAT (Windows System Assessment Tool) overall system score, scaled by + 10x. This is the minimum of all the individual subscores. It is in the range + 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 represents a failure to + get the score. This is collected each time Chrome is launched. + + + + + vmiura@chromium.org + + The amount of time it takes to read the WinSAT results. This is collected + each time Chrome is launched. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml b/tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml index 83db96622d3c7e2b3769dfb9389a905d3cf595db..408df4b147a7eae7af8dff8f6d26351e08c45e53 100644 --- a/tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml +++ b/tools/metrics/histograms/histograms_xml/histogram_suffixes_list.xml @@ -1,19 +1,16 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Marked obsolete 01/2020. Hasn't been recorded for some time. + + + + + + + + + + + + + + + + Removed as of 12/2013. Default pinned apps trial is finished. + + + + + + + + + + Removed August 2016 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + Deprecated April 2015 + + + + + + + + Deprecated October 2017 + + + + + + Deprecated April 2015 + + + + + + Deprecated October 2017 + + + + + + Deprecated April 2017 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 11/2018 in issue 894963. + + + + + + + + + + + + Removed 11/2018 in issue 894963. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated and removed from code as of 01/2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed after M72 since no longer needed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Affected histograms deprecated 09/2019. + + + + + + + + + + + + Affected histograms deprecated on 2019-06-17. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 08/2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 03/2018. We'd learned enough from this metric and it made + no sense to keep it around. + + + + + Deprecated as of 03/2018. We'd learned enough from this metric and it made + no sense to keep it around. + + + + + Deprecated as of 03/2018. We'd learned enough from this metric and it made + no sense to keep it around. + + + + + Deprecated as of 03/2018. We'd learned enough from this metric and it made + no sense to keep it around. + + + + + Deprecated as of 03/2018. We'd learned enough from this metric and it made + no sense to keep it around. + + + + + + + + + + + + + + + + + + + + + + + + + + + + Replaced by GenerateRequest. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + calamity@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in 2019-11. Equivalent values are tracked by + Apps.HomeLauncherTransition.AnimationSmoothness.* histograms. + + + + + Removed on 2019-07. + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 01/2020 since the histogram indicators were stable. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + poromov@chromium.org + zmin@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + emaxx@chromium.org + igorcov@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 07/2020. Replaced with TotalLatencyToSwapBegin suffix + which measures what we actually intended to measure. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 08/2017. Replaced with ExpectedQueueingDurationThreshold. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated and removed from code as of 05/2015. + + + + + Deprecated and removed from code as of 05/2015. + + + + + Deprecated and removed from code as of 05/2015. + + + + + + + + + + + + + + + + + + Removed as of Jan 2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated and removed from code as of 04/2018. + + + + + + + + + + + + + + + Removed as of 12/2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 4/2019 in favor of ProtoDB.InitStatus.*. + + + + + Removed 4/2019 in favor of ProtoDB.LoadKeysSuccess.*. + + + + + + Removed 4/2019 in favor of ProtoDB.LoadEntriesSuccess.*. + + + + + + Removed 4/2019 in favor of ProtoDB.UpdateSuccess.*. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-09. + + + + + + + + + + + + + + + + + + + + Deprecated as of 12/2016. + + + + + Deprecated as of 12/2016. + + + + + Deprecated as of 9/2013. + + + + + + + + + + Deprecated as of 12/2016. + + + + + Deprecated as of 12/2016. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-04. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-06. + + + + + + + + + + + + + + + + Removed 2019-09. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2017-9. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + kmadhusu@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + vmiura@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + Expired in M75. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 05/17/2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 11/29/2016. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed by PageLoad.PaintTiming.NavigationToFirstContentfulPaint. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Renamed to RemoveFile 2020-01. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + All relevant histograms have been marked as obsolete as of Sep 2016. + + macourteau@chromium.org + + + + + + + + + + + + + Removed as of 7/2015. + + + + + + + + + + + + + + + + + + + + + + + + + + lizeb@chromium.org + pasko@chromium.org + + + + + + + + + + + + + + Removed 10/2016. + + + + + + + + Removed 11/2016. + + + + + + + + + Removed 11/2016. + + + + + + + + + + + + + + + + Code removed long ago. + + pauljensen@chromium.org + + + + + + + + Removed 04/2020. See crrev.com/c/2129507 + + + + + + + + + + + + + + + + + + + + + + + + + + + Unused as of 03/2018 + + + + + + Replaced with IPH_ContextualSearchWebSearch. + + + + + + Replaced with IPH_ContextualSearchPromotePanelOpen. + + + + + + + Replaced with IPH_ContextualSearchPromoteTap. + + + + + + + This feature was deprecated in M74 + + + + + + + + + + + + + + + + + + + + This feature was deprecated in M79 + + + + + + This feature was deprecated in M79 + + + + + + + + + + + + + This feature was deprecated in M79 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This metric is now only recorded after the main message loop starts and no + longer distinguishes the first 30 seconds as "startup". + Startup.BrowserMessageLoopStartTime can be used for the startup phase + (before the loop is running) and Startup.FirstWebContents.NonEmptyPaint3 can + be used for the user-visible startup performance. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2017-10. + + + + + + + + + + + Removed 2020-01. + + + + + + + + + Removed 2017-10. + + + + + + + + + Removed 2020-01. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + cmumford@chromium.org + + + + Renamed to RemoveDir on 2020-01. + + + + + Renamed to RemoveFile on 2020-01. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated since 2019-10. + + + + + + + + + + Deprecated since 11/18. + + + + + + Deprecated since 08/18. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 08/2016. + + + + + + + + + + + Removed as of September 20, 2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2013-04 in favor of LevelDBEnvRetry. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + cmumford@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 12/2019. Recording suffixed version of + PageLoad.InteractiveTiming.FirstInputDelay4 instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed July 2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removes as of 6/2020. We now get enough cache hit information from + Renderer4.SoftwareImageDecodeState* and don't need to divide it into tile + bins. + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 12/2017. The low memory margin is a per-platform constant. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TopCat model deprecated 2020-06. + + + + + + Removed 2020-02-01 because elapsed time should be measured by clients, if + they need it. + + + + + + + + Removed 2020-02-01 because elapsed time should be measured by clients, if + they need it. + + + + + + + + Removed 2020-02-01 because elapsed time should be measured by clients, if + they need it. + + + + + + + + + + + + + + + + + + + + Removed 2020-02-01 because elapsed time should be measured by clients, if + they need it. + + + + + Deprecated 07/2019, because we change to record total (shared+unshared) + memory rather than only private memory. Replaced by + MachineLearningService.TotalMemoryDeltaKb. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 5/15/2019. + + + + + + + + Removed as of 5/15/2019. + + + + + Removed as of 5/15/2019. + + + + + Removed as of 5/15/2019. + + + + + + + + + + + + + + + + + + Removed 06/2020. No longer needed. + + + + + + + + + Removed 06/2020. No longer needed. + + + + + + + + + + + + Removed 10/2019 in issue 1000058; no longer needed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed from code as of 07/2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in March 2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed from code as of 08/2016. + + + + + + + + + Removed from code as of 08/2016. + + + + + + + + + + + + Deprecated and removed from code as of 05/2015. + + + + + + + + + + Removed from code as of 03/2018. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Replaced by the likely named entry. It had a misleading name as it also + has the before-unload time discounted. + + + + + + + + + + + + + + + + + + + + + + + Removed as of July 2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of June 2017, in favor of + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time_WorkerStartOccurred_NavigationPreloadEnabled. + + + + + + + + + Removed as of June 2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + + + + + + + + + + + + + Removed 2020-06. + + + + + + + + + + + + + + + + + + + + + + Removed 02/2018. + + + + + + + + + + + + + + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + Deprecated and removed from code as of 10/2015. + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + csharrison@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + tbansal@chromium.org + + + + + + + tbansal@chromium.org + + + + + + + + + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed April 2019, replaced by + NewTabPage.SearchSuggestions.RequestLatencyV2. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Hasn't been used for a while, as of 2016-07. + + + + + + + + + + + + + Used for experiment but was never launched, as of 2019-07. + + + + + + Hasn't been used for a while, as of 2016-07. + + + + + Not used anymore as of 2016-07. + + + + + Has never been used. + + + + + Has never been used. + + + + + Has never been used. + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 06/2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed October 2017 (feature enabled by default). + + + + + + + + + + Removed in June 2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 01/2017. + + + + + Deprecated as of 01/2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + + + + + + + + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + Deprecated 01/2017. + + + + + Deprecated 01/2017. + + + + + + + + + + + + + + + + + + + + + + Obsoleted in Apr 2020. + + + + + + + Removed 01/2018. + + + + + + + + + + + + + Obsoleted in M81. + + + + + + + + + + Obsoleted in M81. + + + + + + + + + + Removed 01/2018. + + + + + + + + + + + + + Deprecated 08/2017. + + + + + Deprecated 08/2017. + + + + + Deprecated 08/2017. + + + + + Deprecated 08/2017. + + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + Deprecated 01/2018. + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2018-07 as the non bucketed metrics are enough for future reference. + + + + + + + + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed March 2019 + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 12/2019 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 05/2020 in favor of recording on update and load of the + prediction model. + + + + + + + + + + + + + + + + Removed in M84. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Experiments no longer active. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in favor of PageLoadBackgrounded2. + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated in favor of PaintTiming equivalent. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated in favor of PageLoad.AbortTiming.Background.* + + + + + + + + + + + + + + + + + + + Removed 5/2019 + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 5/2019 + + + + + + + + + + + + + + + Removed in favor of PageLoad.Clients.AMPCache2.*. + + + + + + + + + + + + Removed in favor of PageLoad.Clients.AMP.*. + + + + + + + + + + + + Removed September 2018 + + + + + + + + + + + Deprecated 05/2018. + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 10/2018 + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in August 2020 as the behavior is launched + + + + + + + + + + + + Deprecated in favor of Clients.FromGoogleSearch. + + + + + Deprecated in favor of Clients.FromGoogleSearch. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Functionality removed in M77. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 12/2018. + + + + + + Functionality removed in M77. + + + + + + + + + + + + + + + + + + + + + + Functionality removed in M86. + + + + + + + + + + + + + Renamed to Clients.Protocol.H11 + + + + + + + + + + + + + + + + + Removed at M53 in favor of LoadType.Reload. + + + + + + + + + + + Deprecated 12/2018. + + + + + + Functionality removed in M77. + + + + + + + + + + + Removed at M66. No longer recorded. + + + + + + + + + Removed at M66. No longer recorded. + + + + + + + + + + + + + + + + + + + + Deprecated on June 2018 (M69) in favor of Clients.NoServiceWorker2. + + + + + + Deprecated on June 2018 (M69) in favor of Clients.ServiceWorker2. + + + + + + + + + + + + + + + + + Deprecated in favor of PaintTiming equivalent. + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed May 2018 (M68) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed May 2018 (M68) + + + + + + + + + + + + + + + + + + + + + + + + + Removed May 2018 (M68) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated in favor of + PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.Reload. + + + + + + + + + + + + + Deprecated in favor of UserGesture/BrowserInitiated. + + + + + Deprecated in favor of UserGesture/BrowserInitiated. + + + + + Deprecated in favor of UserGesture/BrowserInitiated. + + + + + + + + + + + Deprecated in favor of UserGesture. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 03/2016. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 03/2019. + + + + + + + + + + + Removed 03/2019. + + + + + + + + + + + + + + + + + + Replaced by SavedPasswordEntry+SyncPasswordEntry+NonSyncPasswordEntry in + M77. + + + + + + + Replaced by ProtectedPasswordEntry in M62. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 09/2020. Made decision in issue 1128111 to remove unused payment + sheet histograms. + + + + + Renamed to PaymentMethod. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed on 2020-06-19 as most permissions are no longer exposed to + insecure origins to begin with, and even those few that are recorded no + useful data any longer. + + + + + Removed on 2020-06-19 as most permissions are no longer exposed to + insecure origins to begin with, and even those few that are recorded no + useful data any longer. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2/2017 for Issue 689315 which indicated they weren't being used. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in M82 as the experiment has been stopped. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 12/2017 in Issue 781644. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated March 2018 + + + + + + + Deprecated March 2018 + + + + + Deprecated March 2018 + + + + + + + + + + + + + Removed July 11 2017. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed August 2016 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated May 10 2012 + + + + + + + + + + + + + + + + + + + + + + + + Removed August 2016 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated October 2017 + + + + + + + Deprecated October 2017 + + + + + + Deprecated April 2017 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in M79. + + + + + + + + + + + + Functionality removed in 2018. + + + + + + Functionality removed in M86. + + + + + Removed in M84. + + + + + Functionality removed in M77. + + + + + + + Functionality removed in M86. + + + + + + + + + + + + + + + tengs@chromium.org + gzadina@google.com + + + + + + + + + + + + + + + + + + + + + + + + + Removed 03/2018. + + + + + Removed 03/2018. + + + + + Removed 03/2018. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Use *.Custom.ServiceDiscardableManager instead. + + + + + Use *.Custom.ServiceDiscardableManager.AvgImageSize instead. + + + + + Use *.Custom.ServiceTransferCache instead. + + + + + Use *.Custom.ServiceTransferCache.AvgImageSize instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2019-05 + + + + + + + + + + + + + Deprecated M81. + + + + + Deprecated 3/2019. + + + + + + + + + + Deprecated M81. + + + + + + + Removed 03/2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 8/2013. No longer tracked. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 04/2018. + + + + + + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + Deprecated 10/2015. + + + + + + + + Deprecated 04/2016. + + + + + + + + + + + + + + + + + + + + + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + + + + + + + + + + + + + + Obsolete as of M80. Only used for partial raster, which has shipped for a + long period of time / is not being tuned. + + + + + + + + + + + + + + + + + + Replaced by RasterTaskSchedulingDelayNoAtRasterDecodesType. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 01/2020. Data is not used. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 04/2018. No longer recorded. + + + + + + Deprecated as of 04/2018. No longer recorded. + + + + + Deprecated as of 04/2018. No longer recorded. + + + + + Deprecated as of June 2018. No longer recorded. This was also being + recorded when the page had a controller with no fetch event, which usually + means the service worker was not running. + + + + + + + + + + + + + + + + + + + + + Removed March 2019. + + + + + + + + + + + + + + + + + + Removed Febrary 2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated in 10/2016. + + + + + + + + + + + + + + + This experiment was turned down, see https://crbug.com/703188. + + + + + + + + + + + + + + This experiment was turned down, see https://crbug.com/768325. + + + + + + + This experiment was turned down, see https://crbug.com/768325. + + + + + + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + + + + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + + + + + + + + + + + + + + + + Removed September 2016. No longer recorded. + + + + + + + + + + + + + + Removed 1/2016 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in M73. See https://crbug.com/916192 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 4/2015. + + + + + + + + + + Removed in or before M86. + + + + + + + + + Removed in or before M86. + + + + + + + + + + + + + + + + + + + + + + + + Removed in or before M86. See SafeBrowsing.Pref.SawInterstitial or + SafeBrowsing.Pref.Extended.* + + + + + + + + + + + + Removed June 2020. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 8/2019. Was used to better understand DLL prefetching. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated in 9/2016. + + + + + + + Removed in M79, not interesting to keep track of. + + + + + + + + + deprecated November 10 2012 crrev.com/167056 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + cthomp@chromium.org + estark@chromium.org + + + + EV_SECURE level was removed in May 2020. + + + + + HTTP_SHOW_WARNING level was removed in Sep 2019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + jeffreycohen@chromium.org + sebsg@chromium.org + tgupta@chromium.org + + + + + + + + + + + + The affected histogram is obsolete (5/20). + + jeffreycohen@chromium.org + sebsg@chromium.org + tgupta@chromium.org + + + + + + + + + + + + The affected histogram is obsolete. + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 5/2016 because geofencing got removed. + + + + + + + + + This experiment was turned down, see https://crbug.com/616502. + + + + + This experiment was turned down, see https://crbug.com/616502. + + + + + This experiment was turned down, see https://crbug.com/616502. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + This experiment was turned down, see https://crbug.com/616502. + + + + + + + + + + + This experiment was turned down, see https://crbug.com/616502. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 07/2017. Replaced by ExistingUnreadyProcess and + ExistingReadyProcess. + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 07/2017. Replaced by StartWorkerExistingUnreadyProcess + and StartWorkerExistingReadyProcess. + + + + + + + + + + + + + Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Put and + ServiceWorkerCache.Cache.Delete. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.Cache.Renderer.DeleteOne. + + + + + Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Keys2 in + order to use a larger maximum value. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.Cache.Renderer.Keys. + + + + + Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.Match2 in + order to use a larger maximum value. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.Cache.Renderer.Match.Hit. + + + + + Deprecated as of 08/2018. Replaced by ServiceWorkerCache.Cache.MatchAll2 + in order to use a larger maximum value. + + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.Cache.Renderer.PutOne and + ServiceWorkerCache.Cache.Renderer.PutMany. + + + + + + + + Removed as of 02/2019. Not replaced with any new histogram. + + + + + + + + + Removed as of 02/2019. Not replaced with any new histogram. + + + + + + + + + Removed as of 02/2019. Replaced by + ServiceWorkerCache.Cache.Renderer.MatchIgnoreSearch. + + + + + + + + + Removed as of 02/2019. Not replaced with any new histogram. + + + + + + + + wanderview@chromium.org + + + + + + + + + wanderview@chromium.org + + + + + + + + + + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.CacheStorage.Renderer.Delete. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.CacheStorage.Renderer.Has. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.CacheStorage.Renderer.Keys. + + + + + Deprecated as of 08/2018. Replaced by + ServiceWorkerCache.CacheStorage.Match2 in order to use a larger maximum + value. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.CacheStorage.Renderer.Match. + + + + + Deprecated as of 02/2019. Replaced by + ServiceWorkerCache.CacheStorage.Renderer.Open. + + + + + + + + Removed as of 02/2019. Not replaced with any new histogram. + + + + + + + + wanderview@chromium.org + + + + + + + + + + + + wanderview@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed June 2018 (M69). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 06/2019. + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + + + + + + + + + Removed in M82 as the experiment has been stopped. + + + + + + + + + + + Removed in M82 as the experiment has been stopped. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-01. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2018-03. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 12/2014. + + + + + + + + + + + + + + + + + + + + + + + + Removed in favor of Signin.Reconciler.Duration.UpTo3mins. + + + + + + + + + + + + + + + + Deprecated as of 2018-8. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 2019-03. + + + + + + + + + + + + Removed in June 2019 / M77. Some old data have been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + + + + + + + + + + + Obsolete: mus+ash project was canceled, and these metrics are no longer + useful. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed on 04/2020. It is added to only Graphics.Smoothness metrics under + the name of SmoothnessSequenceTypes.Universal + + + + + + + + + + + Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. + + + + + Removed on 9/2019. Did not provide enough information about latency. + + + + + + + + + + + + + Removed on 9/2020. No longer needed after 'Universal' metric was + deprecated. + + + + + + + + + + Removed on 9/2019. Did not provide enough information about latency. + + + + + + + Removed in 9/2020, due to over penalize smoothness. + + + + + + + + + + Removed on 9/2020. No longer needed after 'Universal' metric was + deprecated. + + + + + + + + + + + + + + Removed on 9/2020. No longer needed after 'Universal' metric was + deprecated. + + + + + + + + + + + + + + + + + + + + + + + Removed as of 03/2015. + + + + + + + + + + + + + + + + + + + + + + + Deprecated 10/2018. Replaced by ESET suffix. + + + + + Deprecated 10/2018. Replaced by URZA suffix. + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 07/2014. + + willchan@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + costan@google.com + + + + + + + Deprecated as of 2016-1 (http://crrev.com/372327). + + + + + + + + + + + + + Deprecated July 11 2017. + + + + + + + + + + + Deprecated as of 2013-07. + + + + + + + + + + + + + + + + + + + + Removed 2018-02-06. + + costan@google.com + + + + + + + + + Removed 2011-06-01. + + + + + + + + + + + + + + + + + + + + Removed 10/2019. Since Startup.FirstWebContents.MainFrameLoad2 is no longer + tracked, the non-suffixed reason is always for + Startup.FirstWebContents.NonEmptyPaint2 and the suffix does not provide + additional information. + + + + + + + + + + + Obsolete as of Jan 2020. Was a diagnosis metric when warm/cold + distributions didn't look as expected but recording the suffix for every + startup metric was deemed overkill. Use Startup.Temperature and + Startup.BrowserMessageLoopStartHardFaultCount to diagnose discrepancies. + + + + + + + + + + + + + + + + + + + + + + + + Obsolete as of Jan 2020. + + + + + Obsolete as of Jan 2020. + + + + + + + + + + + + + + + + + + + + + + + Removed as of 10/2014. + + + + + + + + + + Removed as of Jan 2020. + + + + + + + + + Removed as of June 2017. + + + + + + + + + + + + + Removed as of June 2017. + + + + + + + + + + + Removed on 12/18. Metric wasn't used for anything and wasn't useful. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed May 2018 + + + + Deprecated 11/17, no longer used. + + + + + Deprecated 11/17, no longer used. + + + + + + + + + + + Obsolete as of April 2017 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in M77. + + + + + Replaced by Sync.SyncedHistoryFaviconAvailability in M77. + + + + + Deleted in M84. + + + + + Replaced by Sync.RequestGroupSizeForSyncedHistoryFavicons in M77. + + + + + + + + + + + + + + + + + + Deprecated 2/2017. + + + + + + + Deprecated 7/2018. + + + + + + + + + + + + Deprecated 4/2020. + + + + + + + + + + Deprecated 4/2018. + + + + + + Deprecated 4/2018. + + + + + + Removed 11/2019. + + + + + + + + + + + + + + + + + + + Deprecated in M53. + + + + + Deprecated in M53. + + + + + + + + + + + + This never got launched and is removed. + + + + + + + + + + + + + + + Deprecated 7/2018. Replaced by Sync.ModelTypeCount2. + + + + + Deprecated 8/2018. Replaced by Sync.ModelTypeCount3. + + + + + Deprecated 8/2018. Replaced by Sync.ModelTypeCount3. + + + + + + Deprecated 10/2018. Replaced by Sync.ModelTypeEntityChange3. + + + + + Deprecated 11/2018. Replaced by Sync.ModelTypeEntityChange3. + + + + + + + + + Deprecated 06/2019. Replaced by + Sync.NonReflectionUpdateFreshnessPossiblySkewed2. + + + + + + Deprecated 05/2019. + + + + + + Deprecated 05/2020. + + + + + + + Removed in M80. + + + + + Deprecated 2/2017. + + + + + + + + Deprecated 7/2018. + + + + + + + + + + + + + + + + + + Deprecated 4/2018. + + + + + + Deprecated 4/2018. + + + + + + + + + + + + + + + + + Deprecated in M53. + + + + + Deprecated in M53. + + + + + + + + + + This never got launched and is removed. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + No longer logged. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 07/2020, base histogram no longer recorded on dektop. + + + + + Removed 07/2020, base histogram no longer recorded on dektop. + + + + + Removed 06/2017, never worked correctly. + + + + + Removed 06/2017, never worked correctly. + + + + + Removed 07/2020, base histogram no longer recorded on dektop. + + + + + + + + + + Unused as of 11/2019, sheet UI is no longer used. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 03/2019. All affected histograms are deprecated. + + + + + + + + + + + Removed 1/2018. Merged with TaskSchedulerTaskPriority into + TaskSchedulerTaskType to reduce suffixing. + + + + + Deprecated 4/2017. Units changed from milliseconds to microseconds. + + + + + Deprecated 4/2017. Units changed from milliseconds to microseconds. + + + + + Deprecated 4/2017. Units changed from milliseconds to microseconds. + + + + + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + + + + + + + + + + + + + + + + Removed 1/2018. Merged with TaskSchedulerMayBlock into TaskSchedulerTaskType + to reduce suffixing. + + + + + + + Deprecated 4/2017. Units changed from milliseconds to microseconds. + + + + + Deprecated 12/2016. Pool name removed from task latency histogram name. + + + + + Deprecated 12/2016. Pool name removed from task latency histogram name. + + + + + Deprecated 12/2016. Pool name removed from task latency histogram name. + + + + + Deprecated 12/2016. Pool name removed from task latency histogram name. + + + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + + + + + + + + + + + + + + + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + + + Deprecated January 2019 as the pool no longer exists. + + + + + Deprecated 02/2017. Pool was renamed to BackgroundBlocking. + + + + + + Deprecated January 2019 as the pool no longer exists. + + + + + Deprecated 02/2017. Pool was renamed to ForegroundBlocking. + + + + + + Deprecated 01/2018. In favor of TaskSchedulerName suffix. + + + + + Deprecated 01/2018. In favor of TaskSchedulerName suffix. + + + + + Deprecated 01/2018. In favor of TaskSchedulerName suffix. + + + + + Deprecated 01/2018. In favor of TaskSchedulerName suffix. + + + + + Deprecated 01/2018. In favor of explicit .Browser suffix. + + + + + + + + + + + Deprecated 01/2018. In favor of explicit .Browser suffix. + + + + + + + + Deprecated 01/2018. In favor of explicit .Browser suffix. + + + + + + + + + + + Deprecated 12/2016. Pool name removed from task latency histogram name. + + + + + + + + + + + + + + Removed 2020 January. + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated 09/2019. Merged with BackgroundTaskPriority, because both + histograms effectively record the same thing since we merged pools. + + + + + + Deprecated 09/2019. Merged with UserBlockingTaskPriority, because both + histograms effectively record the same thing since we merged pools. + + + + + + Deprecated 09/2019. Merged with UserVisibleTaskPriority, because both + histograms effectively record the same thing since we merged pools. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2019-03. + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 11/2017 in Issue 650338. Using a DCHECK instead. + + + + + + + + + + + + + + + + + Deprecated as of 08/2015. Use Net.HttpJob.*Secure.NotQuic instead. + + + + + Deprecated as of 08/2015. Use Net.HttpJob.*Secure.Quic instead. + + + + + Deprecated as of 08/2018. No longer used. + + + + + + + Deprecated 10/2016, no longer used. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 2020/04. + + + + + + + + Removed 2018/07. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of July 2017, in favor of + NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and + NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed in favor of [LoadKeys, Clear] as of 2020-04-03. + + + + + + Removed in favor of [Clear] as of 2020-04-24. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed 06/2020. + + + + + + + + + + + + + + + + + + Removed 06/2020. + + + + + + + + + + Removed 06/2020. + + + + + + + + + Removed 02/2020 + + + + + Removed 02/2020 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 2020-02-11. + + + + + Deprecated as of 2020-02-11. + + + + + + + + + Deprecated as of 2019-12-24. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed Jan 2020. + + + + + + + + + toyoshim@chromium.org + + + + + + + + + + + + Removed 10/2017. Related field trial has finished rolling out. + + toyoshim@chromium.org + + + + + + + + + Removed 03/2020 in https://crbug.com/1053019. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Removed as of 2020-09 + + + + + + + + + Removed as of 2020-09 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + tmartino@chromium.org + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenBookmark + instead. + + + + + + + + + + + + Deprecated as of 04/2017. Replaced by Bookmark Apps (CreateHostedApp). + + + + + + + + + + + + + + + + + + + + + + + + + + + Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenRecentTab + instead. + + + + + + + + + + + + + + + + + + + - \ No newline at end of file + diff --git a/tools/metrics/histograms/histograms_xml/history/histograms.xml b/tools/metrics/histograms/histograms_xml/history/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..3f8e2448a378f68ce3e1ba86ccc19073363cb3a0 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/history/histograms.xml @@ -0,0 +1,930 @@ + + + + + + + + + + sky@chromium.org + sdefresne@chromium.org + + Logged whenever history database initialization fails. The frequency of + logging will tell you the total failure rate. True indicate that we think + the database is non-recoverable and it will be deleted. It should be + re-created the next time Chrome is started. False indicates we think the + error is temporary (like out of disk space or file locked). Chrome will run + with no history database and nothing will be done to try to fix the error. + See History.InitializationFailureStep for which particular step of history + initialization failed. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + The time that passed while performing a browsing data deletion with an + origin filter. The deletion might be for all time or specific time range. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + The time that passed while performing a full browsing data deletion. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + The time that passed while performing a browsing data deletion for a set of + origins. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + Record tasks from BrowsingDataRemoverImpl that took more than 180s to + finish. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + Record tasks from ChromeBrowsingDataRemoverDelegate that took more than 180s + to finish. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + Record tasks from StoragePartition that took more than 180s to finish. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + The time that passed while performing a browsing data deletion for a + restricted amount of time (e.g. "Last hour") without an origin + filter. + + + + + dullweber@chromium.org + msramek@chromium.org + + Records tasks from ChromeBrowsingDataRemoverDelegate that did not complete + successfully, i.e. where some data that was supposed to be deleted was left + behind. + + + + + msramek@chromium.org + + Whether a notice about other forms of browsing history was shown in the + footer of the Clear Browsing Data dialog. This is recorded every time the + dialog is opened. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + Recorded when the user presses the 'clear' button when presented with the + list of important sites they might want to exclude from clearing browsing + data. We record the number of sites the user deselected, or protected, from + clearing. The default has all sites selected. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + Recorded when the user presses the 'clear' button when presented with the + list of important sites they might want to exclude from clearing browsing + data. We record the percent of sites the user deselected, or protected, from + clearing. The default has all sites selected, which is 0%. Note: To reduce + the number of empty buckets, the percent is divided by 5. + + + + + dmurph@chromium.org + + Recorded when the user presses the 'clear' button in the clear browsing + dialog. We record 'true' if the important sites dialog is shown. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Recorded when the user presses the 'clear' button when presented with the + list of installed apps they might want to exclude from clearing browsing + data. This histogram will be true if the user choose to exclude at least one + installed app from clearing. The default has all apps selected, in which + case this enum would be false. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Recorded when the user presses the 'clear' button when presented with the + list of installed apps they might want to exclude from clearing browsing + data. We record the number of apps the user deselected, or protected, from + clearing. The default has all apps selected. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Recorded when the user presses the 'clear' button when presented with the + list of installed apps they might want to exclude from clearing browsing + data. We record the percent of apps the user deselected, or protected, from + clearing. The default has all apps selected, which is 0%. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + Recorded when we successfuly fetched important sites in the clear browsing + data screen. This is the number of sites that we think are important to the + user. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Recorded when we successfuly fetched installed apps in the clear browsing + data screen. This is the number of apps that we think are important to the + user and allow the users to exclude from clearing browsing data. + + + + + msramek@chromium.org + + Recorded when the user deletes their passwords in the ClearBrowsingData + dialog. Counts how many other data types were selected for deletion. + + + + + msramek@chromium.org + + Whether a dialog with a notice about other forms of browsing history was + shown after the user deleted data from the Clear Browsing Data dialog. + + + + + + + dullweber@chromium.org + msramek@chromium.org + + The number of tasks that are in the task queue when the BrowsingDataRemover + is destroyed. + + + + + dullweber@chromium.org + msramek@chromium.org + + Time spent in Clear Browsing Data dialog. From opening the dialog until data + is cleared. This does not record users who exit the dialog without clearing. + + + + + + + msramek@chromium.org + + Recorded when the user deletes their browsing data. Shows whether cookies + and/or cache were among the selected data types. + + + + + + + msramek@chromium.org + + Recorded when the user deletes their browsing data manually from the + ClearBrowsingData dialog. Shows whether cookies and/or cache were among the + selected data types. + + + + + dullweber@chromium.org + msramek@chromium.org + + Recorded when the user deletes their browsing data. Shows which tab was used + to perform the deletion. + + + + + shess@chromium.org + + Time spent on advanced History DB metrics calculation (weekly and monthly + URL, host, and category counts). Advanced metrics are logged on + initialization of the History DB on 0.3% of starts. + + + + + shess@chromium.org + + Time spent on basic History DB metrics calculation (file size and table + counts). Basic metrics are logged on initialization of the History DB on 1% + of starts. + + + + + shess@chromium.org + + Size of History DB file. Duplicate of Profile.HistorySize and + Sqlite.SizeKB.History. Logged on initialization of the History DB on 1% of + starts. + + + + + dimich@chromium.org + + Time spent on computing the monthly count of hosts visited. Reported every + time computation is performed, which in turn is done approximately weekly. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Count of "History Index *" databases deleted. These databases + stored the full-text-search data for history, which was removed at r213442, + this histogram tracks cleanup. + + + + + mpearson@chromium.org + mjzhang@chromium.org + chrome-analysis-team@google.com + + Number of unique domains visited by the user within a calendar day in user's + local timezone. For each profile, reported at profile open (which usually + happens at startup) for each unreported day (up to 7 days) prior to the + current date, and also reported once every 24 hours thereafter for the + latest unreported day, while the profile remains open. If no domains are + visited in a given day, a count of 0 will be reported for that day. + + Note: for users syncing between multiple devices, this count may include + some URLs/domains that weren't visited on this device. In other words, some + domains may be counted for multiple client_ids even though they were only + visited once, on one device. However, at this time (Feb 2020), only URLs + navigated to via the omnibox ("typed URLs") are synced, not all + visited URLs. There are no plans to change this behavior. As such, because + the mis-counting only occurs for users who are syncing across multiple + devices and only for a subset of visited URLs, the effect of double-counting + is likely to be small. + + + + + mpearson@chromium.org + mjzhang@chromium.org + chrome-analysis-team@google.com + + Number of unique domains visited by the user within a 28 calendar day period + in user's local timezone. For each profile, reported at profile open (which + usually happens at startup) for each unreported 28-day period (up to 7 + periods) ending on the current day, current day - 1, current day - 2, etc. + Also reported once every 24 hours thereafter for the latest unreported + period, while the profile remains open. If no domains are visited during a + 28-day period, a count of 0 will be reported for that period. + + Note: for users syncing between multiple devices, this count may include + some URLs/domains that weren't visited on this device. In other words, some + domains may be counted for multiple client_ids even though they were only + visited once, on one device. However, at this time (Feb 2020), only URLs + navigated to via the omnibox ("typed URLs") are synced, not all + visited URLs. There are no plans to change this behavior. As such, because + the mis-counting only occurs for users who are syncing across multiple + devices and only for a subset of visited URLs, the effect of double-counting + is likely to be small. + + + + + mpearson@chromium.org + mjzhang@chromium.org + chrome-analysis-team@google.com + + Number of unique domains visited by the user within a 7 calendar day period + in user's local timezone. For each profile, reported at profile open (which + usually happens at startup) for each unreported 7-day period (up to 7 + periods) ending on the current day, current day - 1, current day - 2, etc. + Also reported once every 24 hours thereafter for the latest unreported + period, while the profile remains open. If no domains are visited during a + 7-day period, a count 0 will be reported for that period. + + Note: for users syncing between multiple devices, this count may include + some URLs/domains that weren't visited on this device. In other words, some + domains may be counted for multiple client_ids even though they were only + visited once, on one device. However, at this time (Feb 2020), only URLs + navigated to via the omnibox ("typed URLs") are synced, not all + visited URLs. There are no plans to change this behavior. As such, because + the mis-counting only occurs for users who are syncing across multiple + devices and only for a subset of visited URLs, the effect of double-counting + is likely to be small. + + + + + mpearson@chromium.org + mjzhang@chromium.org + chrome-analysis-team@google.com + + Time spent on a scheduled computation task of domain visit counts. Each such + task computes a number of (at least 1 and up to 7) sets of domain counts, + where each set includes 3 results, for a 1-day, 7-day and 28-day period + respectively. Note that for each computation task, only one query time is + reported which covers the entire duration of the task. A task is scheduled + once at startup and every 24 hours thereafter while the browser remains + open. + + + + + calamity@chromium.org + + The percentage of time taken in ExpireHistoryBackend::ExpireVisits for + calculating the redirect parent. + + + + + calamity@chromium.org + + The time taken to expire a list of visits. This is not scaled to the number + of visits deleted, but gives an idea of how long a single request to + ExpireHistoryBackend::ExpireVisits takes. + + + + + rogerm@chromium.org + + The wall-clock time taken to gather favicon database metrics. Metrics are + logged on initialization of the Favicon DB on 1% of starts. + + + + + rogerm@chromium.org + + Size of the Favicons database in MB. This is calculated as the number of + pages consumed by the database multiplied by the page size. Logged on + initialization of the Favicon DB on 1% of starts. + + + + + yiyaoliu@chromium.org + + The count of differences between cached top sites and up-to-date top sites + when function TopSitesImpl::SetTopSites is firstly called at startup. + + + + + yiyaoliu@chromium.org + + The amount of time for function + history::TopSitesBackend::UpdateTopSitesOnDBThread to execute when this + function is called during startup. Excludes the case where local + TopSitesDatabase db_ is unavailable, i.e. where the update doesn't really + happen. + + + + + Please list the metric's owners. Add more owner tags as needed. + Time to check the thumbnail database for an url's favicon. + + + + calamity@chromium.org + src/chrome/browser/resources/history/OWNERS + + The page of the History page shown to the user. Logged each time the user + loads the History page or switches pages. + + + + + sky@chromium.org + sdefresne@chromium.org + + The phase of history initialization that failed. This histogram is only + logged on database initialization failure. + History.AttemptedToFixProfileError will tell how often initialization fails + overall. + + + + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + sky@chromium.org + mpearson@chromium.org + + The number of typed URLs in the history database that are read into the + "in memory" history database. This in memory copy of the typed + URLs is used for synchronous inline autocomplete on the UI thread, while the + larger slower service is run off of disk on a background thread. Recorded on + profile open. + + + + + sky@chromium.org + mpearson@chromium.org + + Number of items in in-memory keyword_search_terms table. Recorded on profile + open. + + + + + sky@chromium.org + mpearson@chromium.org + + Number of items in in-memory urls table. Recorded on profile open. + + + + + sky@chromium.org + mpearson@chromium.org + + The time it takes to read the typed URLs from the main history database into + the "in memory" history database. This in memory copy of the typed + URLs is used for synchronous inline autocomplete on the UI thread, while the + larger slower service is run off of disk on a background thread. Recorded on + profile open. + + + + + mpearson@chromium.org + chrome-omnibox-team@google.com + + Number of history items in the in-memory url index. Recorded on profile open + when restoring from a cache file and again shortly after profile open when + rebuilding the in-memory url index from history. + + + + + mpearson@chromium.org + ssid@chromium.org + + Time to rebuild in-memory url index from main history database. Recorded + once shortly after profile open. + + + + + sky@chromium.org + sdefresne@chromium.org + + History database version from which history migration failed. If there are + higher than normal migration failures, this histogram will indicate which + migration step failed. + + + + + mpearson@chromium.org + sky@chromium.org + + Unique hostnames in History database urls table with last-visit times in the + last 30 days. Metrics are logged on initialization of the History DB on 0.3% + of starts. See also ExploreSites.MonthlyHostCount metric which is similar + but is reported on a elapsed time basis to help avoid bias toward more + active users. + + + + + mpearson@chromium.org + sky@chromium.org + + Unique URLs in History database urls table with last-visit times in the last + 30 days. Metrics are logged on initialization of the History DB on 0.3% of + starts. + + + + + mpearson@chromium.org + sky@chromium.org + + Number of rows in History visits table with visit times in the last 30 days. + Metrics are logged on initialization of the History DB on 1% of starts. + + + + + rogerm@chromium.org + + The total number of favicon bitmaps (of all sizes) cached in a user's + Favicon database. A given favicon URL may be associated with multiple + bitmaps (of different sizes). Logged on initialization of the Favicon DB on + 1% of starts. + + + + + rogerm@chromium.org + + The number of page URL (e.g., http://www.google.com) to favicon URL (e.g., + http://www.google.com/favicon.ico) mappings stored in a user's Favicon + database. Logged on initialization of the Favicon DB on 1% of starts. + + + + + rogerm@chromium.org + + The total number of favicon URLs (e.g. http://www.google.com/favicon.ico) + tracked in a user's Favicon database. This metric tracks knowledge of a + favicon URL not whether there are cached bitmaps for that favicon URL. See + History.NumFaviconBitmapsInDB for that. Logged on initialization of the + Favicon DB on 1% of starts. + + + + + rogerm@chromium.org + + The total number of large (>= 64 pixels wide) favicons being tracked in a + user's Favicon database. This is a subset of History.NumFaviconBitmapsInDB, + which includes all sizes in its count. Logged on initialization of the + Favicon DB on 1% of starts. + + + + + rogerm@chromium.org + + The total number of touch icons being tracked in a user's Favicon database. + This is a subset of History.NumFaviconsInDB, which includes all icon types + in its count. Logged on initialization of the Favicon DB on 1% of starts. + + + + + chengx@chromium.org + + The amount of time for function HistoryBackend::QueryMostVisitedURLs to + execute. Excludes the case where local HistoryDatabase db_ is unavailable, + i.e. where the query doesn't really happen. + + + + + calamity@chromium.org + dbeam@chromium.org + + Records the time taken to load the history Web UI and render (at least) a + screen full of items. This is roughly equivalent to 'time to first + meaningful paint' for the history page. + + + + + msramek@chromium.org + + Whether the notice about other forms of browsing history was shown in the + header of the History page when the header was displayed. The header is + refreshed with every history query. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Size of the recovered TopSites database relative to the original corrupt + database. Recovery is VACUUM-like, so the resulting database should always + be smaller. Substantial 100% results would indicate empty databases being + recovered, substantial low% results would indicate very little data being + recovered. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Rows recovered from [thumbnails] table in TopSites recovery. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The TopSites recovery code is written conservatively, with successful + recovery committed and any failure leading to rollback. This tracks the + outcomes to determine which cases are high-frequency enough to warrant + adding additional code to handle them (versus simply deleting the data). + + + + + mpearson@chromium.org + sky@chromium.org + + Number of rows in urls table in History DB. Metrics are logged on + initialization of the History DB on 1% of starts. + + + + + mpearson@chromium.org + sky@chromium.org + + Number of rows in visits table in History DB. Metrics are logged on + initialization of the History DB on 1% of starts. + + + + + mpearson@chromium.org + sky@chromium.org + + Unique hostnames in History database urls table with last-visit times in the + last 7 days. Metrics are logged on initialization of the History DB on 0.3% + of starts. + + + + + mpearson@chromium.org + sky@chromium.org + + Unique URLs in History database urls table with last-visit times in the last + 7 days. Metrics are logged on initialization of the History DB on 0.3% of + starts. + + + + + mpearson@chromium.org + sky@chromium.org + + Number of rows in History visits table with visit times in the last 7 days. + Metrics are logged on initialization of the History DB on 1% of starts. + + + + + msramek@chromium.org + dullweber@chromium.org + + Recorded each time an entry on the history page is clicked. Measures the age + in days (defined as 24 hour periods, not using local time) of that entry. + Values are ROUNDED UP, i.e. "1" means at most one day old etc. + + + + + msramek@chromium.org + dullweber@chromium.org + + Subset of the HistoryPage.ClickAgeInDays histogram, with better bucket + resolution at lower numbers. + + + + + rpop@google.com + + Number of entries that the clicked entry is older than in History page. Last + bucket is any entry of that value or higher. + + + + + rpop@google.com + + Subset of the Click Position histogram. Contains only the first smaller + subset of entries on the page. Number of entries that the clicked entry is + older than in History page. Last bucket is entries of that value or higher. + + + + + + + rpop@google.com + chrome-analysis-team@google.com + + Histogram for usage of the section in the history page that allows the user + to access tabs from other devices. + + OtherSessionsActions.OPENED_LINK_VIA_CONTEXT_MENU was added for M-76. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + markchang@chromium.org + + The number of tabs created in each window when a user executes "Open + all" menu item from a session menu in the "Tabs from other + devices" section of the history page. + + + + + markchang@chromium.org + + Total number of tabs opened when a user executes "Open all" menu + item from a session menu in the "Tabs from other devices" section + of the history page. + + + + + markchang@chromium.org + + Total number of windows opened when a user executes "Open all" + menu item from a session menu in the "Tabs from other devices" + section of the history page. + + + + + rpop@google.com + + Number of entries that the deleted entry is older than in History page. Last + bucket is any entry of that value or higher. Confirmed removal is not + guaranteed, just an initiation of 'Remove selected items'. + + + + + rpop@google.com + + Subset of Remove Entry Position histogram. Contains only the first smaller + subset of entries on the page. Number of entries that the deleted entry is + older than in History page. Last bucket is any entry of that value or + higher. Confirmed removal is not guaranteed, just an initiation of 'Remove + selected items'. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/image/histograms.xml b/tools/metrics/histograms/histograms_xml/image/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5cc1c04746904b4d57592f0e296043a37698aaef --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/image/histograms.xml @@ -0,0 +1,375 @@ + + + + + + + + + + Please list the metric's owners. Add more owner tags as needed. + + Time it takes to do high-quality image resampling for images that are + resized. Non-resized images and ones our heuristic decides can be done + "badly" are not counted. + + + + + amoylan@chromium.org + martis@chromium.org + + For each image processed by the image annotation service, records whether or + not results for the image already existed in the client-side cache. A hit + means that image data was not transmitted to the image annotation server. + + + + + dmazzoni@chromium.org + amoylan@chromium.org + martis@chromium.org + + For each request made by a client feature to the image annotation service, + reports the final status of the service response. + + + + + + + amoylan@chromium.org + martis@chromium.org + + For each annotation of the given type returned by the image annotation + server, records the confidence (as a percentage) produced by the ML model + for the annotation. + + + + + amoylan@chromium.org + martis@chromium.org + + For each annotation backend run by the image annotation server, records the + gRPC status reported. + + + + + + + amoylan@chromium.org + martis@chromium.org + + For each annotation of the given type returned by the image annotation + server, records whether or not the text of the annotation was empty. This is + sometimes valid, e.g. for text extraction (OCR) on an image that does not + contain any text. + + + + + amoylan@chromium.org + martis@chromium.org + + For each image sent from a client feature to the image annotation service, + reports the image's final size (in kilobytes) after resizing and reencoding. + + + + + amoylan@chromium.org + martis@chromium.org + + For each annotation backend run by the image annotation server, records + whether or not the backend is recognised by this version of Chrome. + + + + + amoylan@chromium.org + martis@chromium.org + + For each image request sent to the image annotation server, records whether + or not the description backend is included among the requested backends. + + The description backend will not be included when the image is known to + violate the description model policy (i.e. be too small or have too-high an + aspect ratio). + + + + + dmazzoni@chromium.org + amoylan@chromium.org + martis@chromium.org + + For each non-empty response sent from the image annotation server, records + whether or not JSON data were successfully parsed from the response body. + + + + + amoylan@chromium.org + martis@chromium.org + + For each pixel fetch request sent from the image annotation service to a + client feature, records whether or not encoded pixel data were successfully + returned to the service. + + + + + amoylan@chromium.org + martis@chromium.org + + For each HTTP response from the image annotation server, reports the + associated HTTP code. + + + + + amoylan@chromium.org + martis@chromium.org + + For each HTTP response from the image annotation server, reports the time + elapsed (in milliseconds) since the corresponding request was sent. + + + + + amoylan@chromium.org + martis@chromium.org + + For each HTTP request sent to the image annotation server, reports the net + error (or OK status) of the request. + + + + + amoylan@chromium.org + martis@chromium.org + + For each HTTP request sent to the image annotation server, reports the size + of the request. Measured in kilobytes, since a request can contain the pixel + data of multiple images. + + + + + amoylan@chromium.org + martis@chromium.org + + For each HTTP response from the image annotation server, reports the + response size in bytes. + + + + + amoylan@chromium.org + martis@chromium.org + + For each image sent from a client feature to the image annotation service, + reports the image's original (i.e. pre-scaling) area in pixels. Images with + pixel count above a certain threshold will be resized prior to transmission. + + + + + + + amoylan@chromium.org + martis@chromium.org + + For each annotation backend run by the image annotation server, records the + gRPC status reported. + + + + + + + fgorski@chromium.org + wylieb@chromium.org + xingliu@chromium.org + + The total number of metadata entries in the image fetcher cache metadata + database for a given cache strategy. Recorded during cache eviction process. + + + + + + + fgorski@chromium.org + wylieb@chromium.org + xingliu@chromium.org + + The total size of the cache for a given cache strategy. Recorded during + cache eviction process. + + + + + fgorski@chromium.org + wylieb@chromium.org + + Events that track the lifecycle and performance of the cached_image_fetcher. + The events reported include: success/failure conditions, various recoverable + errors and a couple of dead-end errors. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the cache + in native. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the cache + in Java. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from native + code. Only recorded on successful loads. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the network + after a cache hit. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the + network. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes to load an image's metadata from the metadata store. + + + + + fgorski@chromium.org + wylieb@chromium.org + + Android: The integer status code of network requests made by the image data + fetcher. This code includes both protocol(1xx-5xx) and non-protocol(-xxx) + errors. Recorded when a request completes. + + + + + fgorski@chromium.org + wylieb@chromium.org + + The time since the last LRU eviction from the image cache. Recorded when two + LRU evictions occur within closure proximity to one another. Will be used to + determine if LRU eviction is happening too frequently. + + + + + tapted@chromium.org + chromeos-files-app@google.com + + For each image load request that requested caching, records whether or not + it was found in the client-side cache. A hit means the request was not + forwarded to the ImageLoader extension. + + + + + tapted@chromium.org + chromeos-files-app@google.com + + Returns the percentage of the client-side cache that is used for loading + images, before they are sent to the ImageLoader extension. Expressed as a + percentage of ImageLoaderClient.CACHE_MEMORY_LIMIT (e.g. 20MB). + + + + + tapted@chromium.org + chromeos-files-app@google.com + + For each image load request records whether or not it requested caching. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/input/histograms.xml b/tools/metrics/histograms/histograms_xml/input/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..1dcfd79ca214a5d0b09222c7da3f34565c87ee9a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/input/histograms.xml @@ -0,0 +1,749 @@ + + + + + + + + + + myy@chromium.org + essential-inputs-team@google.com + + The number of active input methods. Recorded when the user logs in to Chrome + OS or each cold start of Chrome on Android. The active input methods are + selected by user in the language settings page on Chrome OS and in system + language settings on Android. + + + + + myy@google.com + essential-inputs-team@google.com + + Tracks when assistive autocorrect is performed by a text input client. + Recorded when autocorrect is triggered by users with the feature enabled + using a text input client that's being tracked. + + + + + jopalmer@google.com + essential-inputs-team@google.com + + Tracks time between when autocorrect occurs and user clicks to undo the + autocorrect. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The number of times each assistive action is triggered. Recorded when + assistive actions are triggered. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The number of times each assistive action could be triggered according to + the surrounding text but was not triggered because the user turned off the + feature. Recorded when the surrounding text could trigger assistive actions + but the corresponding feature was disabled. + + + + + myy@google.com + essential-inputs-team@google.com + + The reason for emoji suggestions not being shown to users. Recorded when the + surrounding text could trigger emoji suggestions but the feature was + disabled. Only the first applicable reason in IMEAssistiveDisabledReason + enum is recorded per occurrence. + + + + + myy@google.com + essential-inputs-team@google.com + + The reason for personal information suggestions not being shown to users. + Recorded when the surrounding text could trigger personal information + suggestions but the feature was disabled. Only the first applicable reason + in IMEAssistiveDisabledReason enum is recorded per occurrence. + + + + + myy@google.com + essential-inputs-team@google.com + + The number of times an emoji suggest addition is accepted at a given index. + Recorded when an user accepts an emoji suggestion appeared after typing an + emoji-triggered word. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The number of times each assistive action could be triggered according to + the surrounding text. This includes cases in InputMethod.Assistive.Coverage, + and also includes cases when the feature is turned off or there is + insufficient data. Recorded when the surrounding text could trigger + assistive actions. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The number of times each assistive action is accepted. Recorded when + assistive actions are accepted by the users. + + + + + myy@google.com + essential-inputs-team@google.com + + The duration from when emoji suggestions show up to when users accept a + suggestion. Recorded when users accept the suggestion. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The duration from when personal info suggestions show up to when users + accept a suggestion. Recorded when users accept the suggestion. + + + + + myy@google.com + essential-inputs-team@google.com + + The duration from when emoji suggestions show up to when users dismiss a + suggestion. Recorded when users dismiss the suggestion. + + + + + jiwan@google.com + essential-inputs-team@google.com + + The duration from when personal info suggestions show up to when users + dismiss a suggestion. Recorded when users dismiss the suggestion. + + + + + myy@google.com + essential-inputs-team@google.com + + The user's preference for emoji suggestions. Recorded when + AssistiveSuggester is initialised. "Enabled" is logged as the + default value if the user didn't explicitly set it. + + + + + myy@google.com + essential-inputs-team@google.com + + The user's preference for personal information suggestions. Recorded when + AssistiveSuggester is initialised. "Enabled" is logged as the + default value if the user didn't explicitly set it. + + + + + shend@chromium.org + essential-inputs-team@google.com + The auto-correction level for suggestion engine. + + + + shend@chromium.org + essential-inputs-team@google.com + + The breakdown of input method usage by input method category. Recorded when + the system changes the current input method. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The suggestion index (1-based) of the suggestion list item which user + chooses to commit. + + + + + shuchen@chromium.org + + The suggestion accuracy type which the user chooses to commit. + + + + + shuchen@chromium.org + The number of characters committed with composition text. + + + + lanwei@chromium.org + siliu@microsoft.com + + Whether the composition is composed by IMM32-based input method processor + when TSF is disabled on Windows. Recorded when user starts new composition. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Types of actions performed by the user during handwriting, recorded when the + user performs a gesture action. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + The index of the selected suggestion from the handwriting alternative + suggestion menu. This metric is recorded when the handwriting text + highlighted is multiple words, and the selected suggestion is a single word. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + The index of the selected suggestion from the handwriting alternative + suggestion menu. The metric is recorded when the suggestion is selected. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + The index of the selected suggestion from the handwriting alternative + suggestion menu. This metric is recorded when the handwriting text + highlighted is a single word, and the selected suggestion is mutliple words. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Number of characters written in a 10 second interval, recorded every 10s + while the handwriting keyboard is active. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Number of characters written in a 5 second interval, recorded every 5s while + the handwriting keyboard is active. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Number of characters written in a 60 second interval, recorded every 60s + while the handwriting keyboard is active. + + + + + shuchen@chromium.org + + The breakdown of input method usage by input method IDs. Recorded when the + user presses keys on physical or on-screen keyboard. + + + + + azurewei@chromium.org + shuchen@chromium.org + + Whether the opt-in IME menu in the shelf has been activated. + + + + + azurewei@chromium.org + shuchen@chromium.org + + The number of times users click emoji, handwriting or voice button in opt-in + IME menu. + + + + + shuchen@chromium.org + The trigger type of input method switches by user. + + + + shend@chromium.org + essential-inputs-team@google.com + Time taken by the engine to handle a key event. + + + + aurimas@chromium.org + + Whether the currently selected keyboard language matches the system + language. Recorded once with every cold start of Chrome for Android. + + + + + shend@chromium.org + essential-inputs-team@google.com + The result of the user pressing the mode change key. + + + + googleo@chromium.org + shuchen@chromium.org + + The time taken to activate a new IME via IME Mojo service in the IME + extension. It's from when the IME extension sends out an request to activate + a new IME until the new IME is resolved in the IME service and its Mojo + interface is bound to the IME extension. + + + + + shend@chromium.org + essential-inputs-team@google.com + The events of Mojo service in the IME Extension. + + + + shend@chromium.org + essential-inputs-team@google.com + + The time taken to process a rulebased request via the IME Mojo service + inside the IME extension. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The time taken to initialize the IME Mojo service in the IME extension. It's + from the IME extension starts loading a private Mojo bundle for making a + request to connect a IME service until the connection between the extension + and the IME Mojo service is built. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The suggestion index (1-based) of the suggestion list item which user + chooses to commit for physical keyboard autocorrect. + + + + + shuchen@chromium.org + + The suggestion accuracy type which the user chooses to commit for physical + keyboard autocorrect. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The number of times the backspace key was pressed on the virtual keyboard, + while the virtual keyboard was alive. Recorded when the virtual keyboard is + closed. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The layout type of the virtual keyboard, recorded when backspace is pressed. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that counts the number of times the cursor was moved to + the previous word by swiping backwards on the selection track. The count is + initialized when the user starts swiping from any side of the virtual + keyboard, incremented based on how far they swipe backwards on the selection + track, and recorded when they release their finger. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Counts the length of text typed by the virtual keyboard between each + backspace. This metric provides a rough approximation of an error rate for + the virtual keyboard. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The total number of characters committed. Recorded when the virtual keyboard + is closed. + + + + + keithlee@google.com + essential-inputs-team@google.com + + The character per minute ratio recoded during a typing session. + + + + + keithlee@google.com + essential-inputs-team@google.com + + The total number of characters committed during a typing session. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that counts the number of times each virtual keyboard + display mode is used. Recorded when the virtual keyboard is opened or a user + changes the keyboard mode from UI in the virtual keyboard. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that counts events from the decoder triggered by the + virtual keyboard. + + + + + shend@chromium.org + essential-inputs-team@google.com + How long the virtual keyboard was visible. + + + + shend@chromium.org + essential-inputs-team@google.com + How emojis were inserted. + + + + shend@chromium.org + essential-inputs-team@google.com + Errors from the virtual keyboard extension + + + + shend@chromium.org + essential-inputs-team@google.com + + Whether an input field was focused by a stylus or not. Recorded when an + input field is focused. + + + + + shend@chromium.org + essential-inputs-team@google.com + Text input events related to gesture typing. + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + What kind of commit method was used when text was committed to an input from + the handwriting input method in the virtual keyboard. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + What type of container was the virtual keyboard in when text was committed + from the handwriting input method. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + How wide was the keyboard container when text was committed from the + handwriting input method. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The on-screen keyboard initialization latency in milliseconds. + + + + + jopalmer@chromium.org + essential-inputs-team@google.com + + Time to show the on-screen keyboard in milliseconds. Similar to + InputMethod.VirtualKeyboard.KeyboardShown but with a larger maximum to + capture more of the distribution. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The layout of the on-screen keyboard. Logged when the specific layout is + shown. + + + + + dvallet@google.com + essential-inputs-team@google.com + + The count of layout switching actions while virtual keyboard is alive. + Recorded when the virtual keyboard window is hidden or destroyed. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that counts the number of times the cursor was moved to + the next word by swiping forward on the selection track. The count is + initialized when the user starts swiping from any side of the virtual + keyboard, incremented based on how far they swipe forwards on the selection + track, and recorded when they release their finger. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The layout of the virtual keyboard that is shown when the user focuses on an + input field with a stylus. Recorded when the layout is shown after a focus. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + The width of the virtual keyboard window, in pixels, when the floating + keyboard is initialized. This is recorded only once on startup, when the + virtual keyboard is initialized in floating mode. + + + + + curtismcmullan@chromium.org + essential-inputs-team@google.com + + The width of the virtual keyboard window, in pixels, after a user has + completed resizing the virtual keyboard. This is recorded when the user + lifts their finger at the end of a drag that initiates a resize. + + + + + keithlee@google.com + essential-inputs-team@google.com + The duration in seconds of a typing session. + + + + shend@chromium.org + essential-inputs-team@google.com + + The count of user actions to switch keyboard mode (floating, docked). + Recorded when the user clicks in the docked/floating keyboard menu option. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The number of times the virtual keyboard was tapped while the virtual + keyboard was alive. Recorded when the virtual keyboard is closed. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that tracks the total number of words that were deleted + by swiping forward on the deletion track. The count is initialized when the + user starts swiping on the backspace key, incremented based on how far they + swipe forwards on the deletion track, and recorded when they release their + finger. + + + + + shend@chromium.org + essential-inputs-team@google.com + + The number of words typed per minute. Recorded when the virtual keyboard is + closed. + + + + + shend@chromium.org + essential-inputs-team@google.com + + Chrome OS histogram that tracks the total number of words that were restored + by swiping backwards on the deletion track. The count is initialized when + the user starts swiping on the backspace key, incremented based on how far + they swipe backwards on the deletion track, and recorded when they release + their finger. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/installer/histograms.xml b/tools/metrics/histograms/histograms_xml/installer/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..c639d5c9ea6fd4f74d2ca7dd78088e3c9694602c --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/installer/histograms.xml @@ -0,0 +1,246 @@ + + + + + + + + + + zeuthen@chromium.org + + The number of update attempts until the update has been applied. This is + reported every time the device has completed an update. + + + + + zeuthen@chromium.org + Errors from update_engine process when running in dev mode. + + + + zeuthen@chromium.org + + The overhead in downloading extra bytes due to errors/interruptions. + Expressed as a percentage of the bytes that are actually needed to be + downloaded for the update to be successful. + + + + + zeuthen@chromium.org + + The combinations of protocol and source server that were used to complete a + successful update. + + + + + zeuthen@chromium.org + + The number of update attempts with a full update payload until the update + has been applied. This is reported on every update attempt. + + + + + zeuthen@chromium.org + + The source used to provision the install-date-days value sent to Omaha with + every request. This is reported when OOBE completes (M34 or later) or when + upgrading to a version with install-date-days support. + + + + + zeuthen@chromium.org + + Errors from update_engine process when running in normal mode. + + + + + zeuthen@chromium.org + + The age of the OS, defined as the age of the /etc/lsb-release file. This is + reported on every update check but at most once a day. + + + + + zeuthen@chromium.org + + The number of update attempts until the update has been applied. This is + reported on every update attempt. + + + + + zeuthen@chromium.org + + The type of update payload used to update the device. The difference between + "Full" and "Forced Full" is that in the latter, the + request sent to Omaha included a directive saying that a delta payload + wasn't accepted. A "Full" payload is one where a delta payload was + accepted but Omaha provided a full payload. This is reported every time the + device has completed an update. + + + + + zeuthen@chromium.org + + The number of times a Chrome OS device has been powerwashed (factory reset) + without subsequently going through recovery and/or changing the dev mode + switch. Reported once after each powerwash. + + + + + zeuthen@chromium.org + + The number of consecutive times a device has failed to boot an update that + successfully applied. This metric is reported every time the firmware fails + to boot the slot with the update and fell back to the slot it originally + updated from. + + + + + kimjae@chromium.org + chromeos-core-services@google.com + + The reason for entering recovery mode immediately prior to a recovery. + + This is reported on reboot after a successful recovery. + + This metric is specific to Chrome OS. + + + + + zeuthen@chromium.org + + Number of MBs downloaded from during an update that completed successfully. + + + + + zeuthen@chromium.org + + Wall-clock duration between when an update has successfully completed (and + the user is presented with the "reboot arrow") and when the system + has booted into the new update. This is reported every time the device is + rebooted after an update has been applied. + + + + + zeuthen@chromium.org + + Total number of MBs downloaded since the last successful update. This also + includes all the bytes downloaded during any prior failed attempts. + + + + + zeuthen@chromium.org + + Absolute wall-clock time duration it took for the update to complete from + the time an update first began. It includes not just the time the device was + up, but also includes the time the device spent sleeping. + + + + + zeuthen@chromium.org + + Uptime duration it took for the update to complete from the time an update + first began. It does not include the time the device spent sleeping, but it + does include the uptime spent in waiting for the hourly update checks to + happen. + + + + + zeuthen@chromium.org + + Number of times the device was rebooted by the user since an update began + and until it completed successfully. + + + + + zeuthen@chromium.org + + The number of update attempts that didn't complete because a newer update + was detected during the update operation. This is reported every time the + device has completed an update. + + + + + zeuthen@chromium.org + + The number of consecutive different abandoned update payloads since the last + successful update. This is reported every time an update payload is + abandoned because a newer update payload is available. + + + + + zeuthen@chromium.org + + The time in seconds it took to update a Chrome OS system -- from completing + an update check to reboot pending. + + + + + zeuthen@chromium.org + + Number of times the download URLs were switched due to failures. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/instant/histograms.xml b/tools/metrics/histograms/histograms_xml/instant/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5afe6b1407c79960efc313fc865f7f9a555b9a97 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/instant/histograms.xml @@ -0,0 +1,374 @@ + + + + + + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a breakdown of how many times each possible Bluetooth advertisement + registration result occurs. + + The bucket "Unknown result" indicates that the Bluetooth platform + returned an unknown error code; if it has any counts, the client code should + be changed to account for the new error code. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a breakdown of how many times each possible Bluetooth advertisement + unregistration result occurs. + + The bucket "Unknown result" indicates that the Bluetooth platform + returned an unknown error code; if it has any counts, the client code should + be changed to account for the new error code. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides the success rate of starting a Bluetooth discovery session. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides the success rate of stopping a Bluetooth discovery session. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a top-level breakdown of the times a connection to a host has + failed. + + An "unknown error" is caused by the host returning an + "unknown error" response code. Tethering timing out and client + connection error are both broken down further in + InstantTethering.ConnectionToHostResult.Failure.TetheringTimeout and + InstantTethering.ConnectionToHostResult.Failure.ClientConnection, + respectively. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Breaks down the reasons why the client failed to connect to the hotspot, and + the number of times they occurred. + + Note that a client connection can be canceled by a user either via pressing + the Disconnect button or beginning a connection attempt to another host. The + "internal error" case is a general bucket that captures client + errors we don't expect to be significant failure causes. + + This histogram breaks down the "client connection error" count of + InstantTethering.ConnectionToHostResult.Failure. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Captures the number of times of whether or not first-time setup was required + when tethering timed out. + + Starting tethering on the host works like so: if first-time setup is + required on the host, a first-time setup UI is shown on the host; once the + user interacts with it, the provisioning app is called. If first-time setup + is not required, then the provisioning app is directly called. To be clear: + the provisioning app is always run. + + There are two possible ways for tethering to time out: either the + provisioning app flaked (crashed or hung, and never called back to Instant + Tethering), or the user never interacted with the first-time setup UI flow + (assuming first-time setup was required). + + Because it's very unlikely for the provisioning app to flake, we can read + the "was first-time setup" count as almost always indicative of + the user not interacting with the first-time setup UI. We expect the + "was not first-time setup" count to be low (because, as mentioned, + it's very unlikely for the provisioning app to flake). + + This histogram breaks down the "tethering timed out" count of + InstantTethering.ConnectionToHostResult.Failure. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a breakdown of the times a connection to a host was either + unsuccessful due to provisioning failure (the carrier disallows tethering) + or "other" (this is captured under + InstantTethering.ConnectionToHostResult.SuccessRate.Background). + + This metric captures the rough percentage of connections which are + unsuccessful due to provisioning failure. It is separate from + InstantTethering.ConnectionToHostResult.SuccessRate.Background and the + metrics related to it because provisioning failure is neither truly a + success nor an error. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Captures the count of successful and failed connection attempts. + + This metric counts the top-level user action from beginning to connect, all + the way through success or failure of the connection (excluding any + programmatic retries within the connection attempt). + + This metric provides an immediate understanding of the Instant Tethering + connection success rate. The counts of failure are broken down in + InstantTethering.ConnectionToHostResult.Failure. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Breaks down the state of Instant Tethering during user sessions. All states, + except for 'Enabled', indicate that the feature was not active. This + histogram is emitted to each time a condition affecting Instant Tethering's + state, e.g. the user enabling or disabling the feature, or Bluetooth + becoming enabled or disabled. + + Note: The "Screen locked" bucket is obsolete, and should not have + any reports. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of a batch of host scans. A batch is defined as a series of one + or host scans separated by no more than one minute. + + For example, if a scan occurs then stops and does not start back up again, + the metric logged would be the amount of time taken for that scan. However, + if a scan finishes and a new scan starts up again less than a minute after + the previous scan finished, the metric logged would be the time difference + between the start of the first scan and the finish of the second scan. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a breakdown of the results of each host scan. This metric is + recorded after each host scan. + + Comparing the number of times no hosts were found against the other buckets + can help determine how often a host scan is useful. + + The sum of the buckets capturing that a notification was shown can be used + as a baseline of comparison against + InstantTethering.ConnectionToHostResult.ProvisioningFailureRate to roughly + measure engagement with the notification. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between the start and end of a Tether connection. + Timing starts when the device connects to the Wi-Fi hotspot and ends when + the device becomes disconnected from the Wi-Fi hotspot. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Captures the count of successful and failed attempts to send a + 'KeepAliveTickle' message to the phone. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Indicates the feature state of the Instant Tethering feature. This metric is + emitted to at the creation of the user session (when the user logs in), and + when feature state updates occur. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Counts the number of interactions a user has with each of the Instant + Tethering notifications. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when a client authenticates with a host, and + receives a ConnectTetheringResponse. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time it takes for the client to connect to the host, from + the moment the user taps 'Connect', until the client connects to the host's + hotspot. This does not include timeouts. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time it takes for the client to connect to the provided + hotspot after receiving a ConnectTetheringResponse. This does not include + timeouts. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time it takes for the client to send off a + DisconnectTetheringRequest. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when a client authenticates with a host, and + receives a KeepAliveTickleResponse. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when a client authenticates with a host, and + receives a TetherAvailabilityResponse. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides a breakdown of how each Tether session ended. A session begins when + a device is first connected to a host's hotspot, and ends when the device is + no longer connected to the hotspot. This metric is recorded at the end of + each session. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides the count of the number of users who have the Instant Tethering + toggle enabled vs. disabled on startup. This metric is logged each time a + user logs into a Chromebook. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Provides the count of the number of times users have enabled or disabled the + user preference for Mobile data. This metric is logged each time the value + is toggled. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/interstitial/histograms.xml b/tools/metrics/histograms/histograms_xml/interstitial/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..a64e3b64e1ee9a11c6edc47f2790edf77f810399 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/interstitial/histograms.xml @@ -0,0 +1,260 @@ + + + + + + + + + + meacer@chromium.org + + User action when the user is shown a captive portal error page. + + + + + estark@chromium.org + carlosil@chromium.org + + User decision when presented with a security interstitial. As of M44, + subresource interstitials were split into their own entries. As of M52, + social_engineering_ads* and social_engineering_landing* interstitial reasons + are split into their own entries from phishing*. + + + + + felt@chromium.org + carlosil@chromium.org + + User decision when presented with a security interstitial, on a site that + the user had previously visited. As of M44, subresource interstitials were + split into their own entries. As of M52, social_engineering_ads* and + social_engineering_landing* interstitial reasons are split into their own + entries from phishing*. + + + + + estark@chromium.org + carlosil@chromium.org + + User interactions with a security interstitial. As of M44, subresource + interstitials were split into their own entries. As of M52, + social_engineering_ads* and social_engineering_landing* interstitial reasons + are split into their own entries from phishing*. + + + + + meacer@chromium.org + + Record possible states of captive portals. This histogram is emitted + (possibly multiple times to different buckets) whenever a ssl interstitial + page is displayed and captive portal detection is enabled. The captive + portal technique forces a client on a network to see a special web page + (usually for authentication purposes) before using the internet normally. + + + + + estark@chromium.org + carlosil@chromium.org + + Possible non-attack causes of the non-overridable SSL interstitial. Many + errors are not reported in this histogram and new errors may be added over + time, therefore one should not look at the breakdown of this histogram (one + bucket divided by the sum) because that will be inaccurate. Instead, one + should look at each bucket count divided by the count of the ssl errors of + that type. E.g. WWW mismatch is recorded only when the ssl error is + CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW + mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the + histogram interstitial.ssl_error_type. + + + + + estark@chromium.org + carlosil@chromium.org + + Possible non-attack causes of the overridable SSL interstitial. Many errors + are not reported in this histogram and new errors may be added over time, + therefore one should not look at the breakdown of this histogram (one bucket + divided by the sum) because that will be inaccurate. Instead, one should + look at each bucket count divided by the count of the ssl errors of that + type. E.g. WWW mismatch is recorded only when the ssl error is + CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW + mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the + histogram interstitial.ssl_error_type. + + + + + mab@chromium.org + + State of the system clock, as inferred from the build timestamp, when an SSL + CERT_INVALID_DATE error is seen. + + + + + estark@chromium.org + mab@chromium.org + + State of the system clock, relative to network time, when an SSL + CERT_INVALID_DATE error is seen. + + + + + felt@chromium.org + carlosil@chromium.org + + The histogram shows the connection types associated with SSL warnings. E.g., + do more warnings occur on WiFi? + + + + + carlosil@chromium.org + + Specifies when a user enters the page info menu whether or not the user + pressed the SSL decisions revoke button. This is logged when the page info + UI is closed, only if the button was visible in the page info. + + + + + carlosil@chromium.org + + Records when a user visits a site after clicking through a certificate + warning. + + + + + meacer@chromium.org + carlosil@chromium.org + estark@chromium.org + The type of action that the SSL error handler takes. + + + + estark@chromium.org + + When handling a certificate date error, Chrome (under certain Variations + Service experiments) will delay displaying the warning interstitial for up + to 3 seconds while querying a network time service. This histogram records + the amount of time for which the interstitial was delayed on this check. The + histogram is recorded even when a time query is not sent (for example, + because Chrome already had an up-to-date network timestamp that it could + use, or because the client is not in the experimental group that enables + network time queries). + + + + + estark@chromium.org + carlosil@chromium.org + + The type of SSL error that the user encounters. This is recorded for all SSL + warnings, regardless of whether they are overridable. + + + + + estark@chromium.org + + Recorded when a non-overridable SSL interstitial is shown. The value is true + if the user has seen the same error multiple times (in which case a special + message is added to the interstitial). + + + + + estark@chromium.org + + Recorded when a non-overridable SSL interstitial is shown for a Certificate + Transparency error. The value is true if the user has seen the same error + multiple times (in which case a special message is added to the + interstitial). + + + + + estark@chromium.org + + Recorded when an overridable SSL interstitial is shown. The value is true if + the user has seen the same error multiple times (in which case a special + message is added to the interstitial). + + + + + estark@chromium.org + + Recorded when an overridable SSL interstitial is shown for a Certificate + Transparency error. The value is true if the user has seen the same error + multiple times (in which case a special message is added to the + interstitial). + + + + + estark@chromium.org + + Recorded whenever the user sees or proceeds through an SSL interstitial for + an error that the user has seen multiple times (in which case a special + message is added to the interstitial). + + + + + estark@chromium.org + + Recorded whenever the user sees or proceeds through an SSL interstitial for + a Certificate Transparency error that the user has seen multiple times (in + which case a special message is added to the interstitial). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/ios/histograms.xml b/tools/metrics/histograms/histograms_xml/ios/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..65db2a1e24a38bc844637d47cf98e20c6c9fa24a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/ios/histograms.xml @@ -0,0 +1,822 @@ + + + + + + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + When a navigation is committed, it should have a non-null NavigationContext. + This histogram counts the frequency of this invariant holding at the time + when a new navigation is committed. It is used to verify the effectiveness + of code fixes because this issue is not currently reproducible in testing + (http://crbug.com/864769). True means a non-null NavigationContext is + present. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + When a navigation is committed, the web view URL is expected to match that + of the current back-forward item. WKWebView seems to break this assumption + at times. This histogram counts the frequency of this invariant violation at + the time when a new navigation is committed. True means the URL matches the + current back-forward item. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The number of times the Content Extension was displayed since last Chrome + foregrounding. Reported when Chrome is put in foregrounded. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The index of the URL selected by the user in the Content Extension. + + + + + rkgibson@google.com + gambard@chromium.org + + When the content rule list provider updates its lists, this can succeed or + fail. Failure occurs when the rule lists are updated again before the first + update finishes. + + + + + mrefaat@chromium.org + bling-team@google.com + + Recorded to indicate whether the GetCookiesForURL call found cookies or not + when called on a specific system cookie store implementation. Most of the + cookies fetching on iOS Chromium is done by the WKWebView and doesn't + involve calling GetCookiesForURL. The method is only called when a request + is made by the UrlRequestFetcher for cases that are not handled by WKWebView + (eg. Downloads, Auto Suggestions and NTP tiles). + + + + + mrefaat@chromium.org + bling-team@google.com + + The system cookie store type used when GetCookiesForURL method is called. + Most of the cookies fetching on iOS Chromium is done by the WKWebView and + doesn't involve calling GetCookiesForURL. The method is only called when a + request is made by the UrlRequestFetcher for cases that are not handled by + WKWebView (eg. Downloads, Auto Suggestions and NTP tiles). + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user copied a Password since + last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user copied a URL since last + Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user copied a Username since + last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension was displayed since last Chrome + foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension password util failed to look up + for a password since last Chrome foregrounding. Reported when Chrome is put + in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension pasword util was queried with a + nil argument since last Chrome foregrounding. Reported when Chrome is put in + foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user selected for a Password + since last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension selected a Password without + user intervention since last Chrome foregrounding. Reported when Chrome is + put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension needed user reauthentication + since last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user searched for a Password + since last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + djean@chromium.org + + Recorded when a request to replace identities in ASCredentialIdentityStore + fails. + + + + + javierrobles@chromium.org + djean@chromium.org + + The number of times the Credential Extension user unobfuscated a Password + since last Chrome foregrounding. Reported when Chrome is put in foreground. + + + + + justincohen@chromium.org + eugenebut@chromium.org + + Recorded when app is running in the background and posted a background task. + This time is obtained by calling UIApplication.backgroundTimeRemaining. When + backgroundTimeRemaining reaches 0 and there is at least one running + background task, then iOS terminates the app instead of suspending it. The + lower recorded value is, the higher chances that posted task will keep + running when backgroundTimeRemaining reaches 0, causing the app termination. + When app is relaunched after termination the app starts cold which is slower + and does not fully restore the prior UI state, so terminations are worse + than suspensions. + + + + + justincohen@chromium.org + gambard@chromium.org + + Workaround for a WKWebView bug where WKNavigations can leak, leaving a + permanent pending URL, thus breaking the omnibox. While it is possible for + navigations to finish out-of-order, it's an edge case that should be handled + gracefully, as last committed will appear in the omnibox instead of the + pending URL. This metric records whether there are old navigations to clean + up each time a navigation finishes. See crbug.com/1010765 for details. + + + + + thegreenfrog@chromium.org + rohitrao@chromium.org + + The action taken by the user in response to the default browser promo. + + + + + kkhorimoto@chromium.org + michaeldo@chromium.org + Tracks the way JavaScript dialogs are closed on iOS. + + + + jif@chromium.org + + The type of content that the user is dragging into Chrome. Because a drag + can contain multiple types of objects, multiple DragContent values may be + recorded for a single drag event. + + + + + edchin@chromium.org + justincohen@chromium.org + + Tracks the result of snapshotting when the user enters the tab switcher. + Recorded whenever the user enters the tab switcher. + + + + + danyao@chromium.org + + When a navigation is finished, it should have a non-null NavigationContext. + This histogram counts the frequency of this invariant holding at the time + when a new navigation is finished. It is used to verify the effectiveness of + code fixes because this issue is not currently reproducible in testing + (http://crbug.com/864769). True means a non-null NavigationContext is + present. + + + + + danyao@chromium.org + + When a navigation is finished, it should have a non-null NavigationItem. + This histogram counts the frequency of this invariant holding at the time + when a new navigation is finished. It is used to verify the effectiveness of + code fixes because this issue is not currently reproducible in testing + (http://crbug.com/864769). True means a non-null NavigationItem is present. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + When a navigation is finished, the web view URL is expected to match that of + the current back-forward item. WKWebView seems to break this assumption at + times. This histogram counts the frequency of this invariant violation at + the time when a new navigation is finished. True means the URL matches the + current back-forward item. + + + + + javierrobles@chromium.org + eugenebut@chromium.org + + Reports exceptions when trying to send a form input accessory action to the + virtual keyboard. + + + + + erikchen@chromium.org + + This event is recorded each time a Handoff is received by Chrome on iOS. The + enumeration indicates the source of the Handoff. + + + + + pkl@chromium.org + + Tracks the reason for why the In Product Help bubble was dismissed. + + + + + thegreenfrog@chromium.org + rohitrao@chromium.org + + As of iOS14, users will be able to set a default browser other than Safari. + When Chrome is the default browser, it will receive all URL opens, which is + likely to change certain stability metrics. Thus, it will be good to filter + those metrics by default browser status. This metrics records whether the + user was deemed to have set Chrome as the device's default browser. This + metric will be logged with ever histogram upload. + + + + + rkgibson@google.com + gambard@chromium.org + + IOS Content Blocking uses special injected Javascript to block access to + things like cookies and local storage. Future changes to iOS/WebKit could + cause these blocks to break. This logs that occurrence. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The time during which main thread was not responding. 0 if application was + killed before recovering. Logged after an action posted on the main thread + is not executed immediately. The histogram is sent when the task is finally + executed or on next application startup. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The durations of time in which the app is too busy to handle user + interaction responsively. Logged when a MXMetricPayload is received (one per + day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The amount of time taken to resume the app from the background. Logged when + a MXMetricPayload is received (one per day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The average amount of memory in use by the app when it's suspended. Logged + when a MXMetricPayload is received (one per day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The reason for the application termination in background. Logged when a + MXMetricPayload is received (one per day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The total time the app is in the background. Logged when a MXMetricPayload + is received (one per day). Note: The date the data is reported is later than + the day it account for. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The reason for the application termination in background. Logged when a + MXMetricPayload is received (one per day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The total time the app is in the foreground. Logged when a MXMetricPayload + is received (one per day). Note: The date the data is reported is later than + the day it account for. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The largest amount of memory used by the app. Logged when a MXMetricPayload + is received (one per day). + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The amount of time taken to launch the app. Logged when a MXMetricPayload is + received (one per day). + + + + + marq@chromium.org + djean@chromium.org + + The source of "Open in new Window" user requests. Recorded when a + newly created window is added to a session. + + + + + javierrobles@chromium.org + eugenebut@chromium.org + + NSString API: stringByReplacingCharactersInRange:withString: was invoked + with a nil argument. + + + + + gambard@chromium.org + + The type of NTP impressions on iOS, split by type of suggestions shown + (local vs remote vs remote_collapsed). + + + + + mrefaat@chromium.org + bling-team@google.com + + The result of the download operation done when the user taps "open + in" button to open a file by a different application. + + + + + ewannpv@chromium.org + gambard@chromium.org + bling-team@google.com + + The MIME type of the previwed file when the "Open In" toolbar is + presented. + + + + + danyao@chromium.org + The number of navigation started events by navigation type. + + + + danyao@chromium.org + + The "true" value of this boolean histogram counts the number of + page loading started events. The "false" value will never be seen. + + + + + edchin@chromium.org + justincohen@chromium.org + + Tracks the result of snapshotting when the page has been loaded. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + Measures the time from the end of user input in the omnibox to when the page + is fully loaded. Only measures page loads initiated by user typing a URL or + selecting a suggested entry from the URL bar. + + + + + javierrobles@chromium.org + bling-team@google.com + + Tracks the results and attempts of reauthentication when using password + Autofill suggestions. + + + + + javierrobles@chromium.org + bling-team@google.com + + Tracks the results and attempts of reauthentication when using a password in + Manual Fallback. + + + + + mrefaat@chromium.org + bling-team@google.com + + The user reaction to the prompt that appears when a website tries to open an + external application repeatedly. + + + + + eugenebut@chromium.org + justincohen@chromium.org + + [iOS] The number of items Navigation Manager was requested to restore. 100 + is logged when the number of navigation items is greater than 100. This is + just a requested count and actual number of restored items can be smaller. + Restoration is triggered in the following cases (the list is not + exhaustive): app cold start, remote tab was open, cookie were cleared, + recently closed tab was restored. + + + + + eugenebut@chromium.org + justincohen@chromium.org + + [iOS] Time spent on restoring committed Navigation Manager's items. Recorded + once per restoration, as a cumulative time across all items. Restoration is + triggered in the following cases (the list is not exhaustive): app cold + start, remote tab was open, cookies were cleared, recently closed tab was + restored. This metric will be used for monitoring session restoration + performance which relies on system's WKWebView. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + The action selected by the user in the Search Extension. + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The number of times the Search Extension was displayed since last Chrome + foregrounding. Reported when Chrome is put in foreground. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The number of items received simultaneously in Chrome from the IOS share + extension. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + Type of the item received from the iOS share extension. + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The delay in milliseconds between the item creation in the extension and its + processing in Chrome. + + + + + javierrobles@chromium.org + olivierrobin@chromium.org + + The source application that sent the external command to Chrome. + + + + + pkl@chromium.org + + The latency in milliseconds between the start of the Share Page operation + and when the UI is ready to be presented. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + The Spotlight Action pressed by the user. + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + Tracks the availability of the Spotlight indexation on the device. It is + logged once at each cold start. Note: Spotlight may be available on the + device but disabled by the user. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + Time spent in Spotlight initial indexation of bookmarks. + + + + eugenebut@chromium.org + olivierrobin@chromium.org + Number of bookmarks indexed during initial indexation. + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This event is recorded each time a Chrome Spotlight entry is selected by the + user. The enumeration indicates the nature of the Spotlight entry. + + + + + mrefaat@chromium.org + eugenebut@chromium.org + + The result of StoreKit handling for a specific iTunes URL. Not Handled will + be logged when the LinksHandler didn't handle a specific URL on purpose (not + supported), and Failure will be logged when a URL that should have been + handled wasn't handled. + + + + + mrefaat@chromium.org + bling-team@google.org + + Whether the StoreKit loaded the required iTunes product successfully or not. + + + + + marq@chromium.org + + The UI interaction by which the user changed the visible page in the tab + switcher. + + + + + gambard@chromium.org + justincohen@chromium.org + + A boolean that is used to indicate that the URL property of the WKWebView + has changed to a nil or empty URL. Recorded on the KVO of the URL of the + WKWebView. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + Measures the number of main frame navigations in slim navigation manager + that are affected by a WKWebView bug that corrupts back/forward history + (http://crbug.com/887497). This is recorded during WKWebView's + decidePolicyForNavigationAction callback. True means the bug is triggered. + False means the bug is not triggered. + + + + + danyao@chromium.org + + WKWebView should notify navigation commit before navigation finish, but + exceptions have been observed. This histogram counts the frequency of this + invariant violation at the time when a new navigation is finished. True + means navigation finish callback happened before navigation commit. + + + + + kkhorimoto@chromium.org + pkl@chromium.org + + Records the user actions related to the WKWebView 3D touch link preview API. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/local/histograms.xml b/tools/metrics/histograms/histograms_xml/local/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..58e03c08123292d966ac8935460d58dd73f5a556 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/local/histograms.xml @@ -0,0 +1,338 @@ + + + + + + + + + + + + + + + + + uthakore@chromium.org + invernizzi@chromium.org + + Number of requests made by a private page to resources besides itself. + + + + + uthakore@chromium.org + invernizzi@chromium.org + + Number of requests made by a public page to resources with reserved IP + addresses. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Type of backend requested from the Local Search Service. It is reported once + at the initialization of an Index. Chrome OS only. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Number of times the local search service has been requested to perform a + search on a device. Reported daily. The count is accumulated through the + day, spanning reboots, and sent once the system clock indicates that a full + day or more has passed since the last report. If the system is suspended or + off for more than a day, the current count will be reported the next time + the system boots, but the skipped days will not be reported. Chrome OS only. + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Reasons why local search daily metrics were reported. Chrome OS only. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Number of documents in the corpus. Recorded each time the index is updated + (documents added, updated or removed) and if the index is not empty. Chrome + OS only. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Number of results for each successful search. Chrome OS only. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Search request response status for Cros Settings. Chrome OS only. + + + + + + + jiameng@chromium.org + tby@chromium.org + thanhdng@chromium.org + wrong@chromium.org + + Time taken to find search results. Only recorded if search response status + is success, i.e. neither index nor query is empty. Chrome OS only. + + + + + ssid@chromium.org + + Total size of the HTML5 LocalStorage browser-side cache purged in KB when + memory pressure signal was triggered or cache size hit the limits. + + + + + ssid@chromium.org + + Total size of the HTML5 LocalStorage databases in KB in the browser-side + cache recorded each time a new database is opened in memory. + + + + + mek@chromium.org + dmurph@chromium.org + + Size of the HTML5 LocalStorage DB in KB in the renderer-side cache using + Mojo implementation. + + + + + mek@chromium.org + dmurph@chromium.org + + Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using + Mojo implementation. + + + + + mek@chromium.org + dmurph@chromium.org + + Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using + Mojo implementation, split by size. {LocalStorageSizes} + + + + + + ssid@chromium.org + + The renderer side cache hit rate metrics for new HTML5 LocalStorage DB + opened. + + + + + mek@chromium.org + dmurph@chromium.org + + Size of the HTML5 LocalStorage DB in KB in the renderer-side cache. + + + + + mek@chromium.org + + Total size of the HTML5 LocalStorage browser-side cache purged in KB when + memory pressure signal was triggered or cache size hit the limits. + + + + + mek@chromium.org + + Total size of the HTML5 LocalStorage databases in KB in the browser-side + cache. Recorded each time a new database is opened in memory. + + + + + mek@chromium.org + + The result of an attempt to commit localstorage data to the database. + + + + + mek@chromium.org + + The result of a failed attempt to open a LevelDB database for LocalStorage. + + + + + mek@chromium.org + + The result of a failed attempt to open a LevelDB database for LocalStorage + on disk. + + + + + mek@chromium.org + + The result of a failed attempt to open a LevelDB database for LocalStorage + in memory. + + + + + mek@chromium.org + + The result of attempting to delete the LocalStorage database. + + + + + mek@chromium.org + + The reason opening a directory for the LevelDB database that backs + LocalStorage failed. + + + + + mek@chromium.org + + The reason loading an initial snapshot of the localstorage data for an + origin failed. + + + + + mek@chromium.org + + Whether or not any fixes needed to be made to localstorage data, as a result + of bugs in the migration code in M61/M62. Recorded every time the browser + loads an initial snapshot of the localstorage data for an origin. + + + + + mek@chromium.org + dullweber@chromium.org + + Recorded when the database connection is closed unexpectedly. + + + + + mek@chromium.org + + The reason opening the LevelDB database that backs LocalStorage failed. + + + + + + + mek@chromium.org + + The result of opening the LevelDB database that backs LocalStorage. + + + + + mek@chromium.org + + The reason reading the schema version of the LocalStorage database failed. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/login/histograms.xml b/tools/metrics/histograms/histograms_xml/login/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..a03f31d8551d07f9f1481d49d02a8319d4fce01c --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/login/histograms.xml @@ -0,0 +1,275 @@ + + + + + + + + + + mhasank@google.com + arc-core@google.com + + Tracks the time to backup ARC bug report when starting ARC fails. + + + + + xiyuan@chromium.org + + Tracks the browser process shutdown time from when SIGTERM is sent to the + browser process to when the browser process group exits (or gets killed by + SIGABRT). + + + + + cmasone@chromium.org + sumit@chromium.org + + Chrome OS histogram tracking, per consumer sign-in, whether the device owner + is allowing arbitrary accounts to be used on the device, or only those on a + specific whitelist. + + + + + + + alemate@chromium.org + rsorokin@chromium.org + + A set of chrome flags that triggered browser restart on Chrome OS after user + sign in. Chrome needs to be restarted if the device owner set of flags is + different from the user flags. Which means that there is a flag difference + which led to this restart. This difference is reported by this metric. + + + + + achuith@chromium.org + Chrome OS login failure reason. + + + + achuith@chromium.org + omrilio@chromium.org + + Chrome OS histogram that keeps track of the days since the least frequently + used account signed in. Reported on every boot and once a day after that. + + + + + betuls@chromium.org + jorgelo@chromium.org + chromeos-security-core@google.com + + Mount Namespace creation success status. Reported every time user signs in. + + + + + alemate@chromium.org + Records whether a new user's priority prefs sync timed out. + + + + alemate@chromium.org + + Time spent waiting for priority preferences to sync after new user sign in. + The operation will time out after 10s. + + + + + glevin@chromium.org + + On offline login failure, records whether it is for an existing user. + + + + + glevin@chromium.org + + On offline login success, records number of attempts, including success. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Tracks the reason why a user was sent through the GAIA re-auth flow which + caused the local password change. + + + + + xiyuan@chromium.org + omrilio@chromium.org + + Records the UI flow after a possible password change is detected. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Tracks the reason why a user was sent through the GAIA re-auth flow which + did not cause the local password change. + + + + + cmasone@chromium.org + The state of Chrome OS owner key and device policy files. + + + + rsorokin@chromium.org + achuith@chromium.org + cros-oac@google.com + + Time from first display of the login prompt until the user completes signing + in. + + + + + elijahtaylor@google.com + yusukes@chromium.org + rsorokin@chromium.org + cros-oac@google.com + + Time from first display of the login prompt until the existing user + completes signing in. + + + + + iby@chromium.org + + Tracks whether a ChromeOS user was logged out because Chrome repeatedly + crashed. + + + + + mnissler@chromium.org + Result of a state key generation operation. + + + + achuith@chromium.org + Chrome OS login success reason. + + + + glevin@chromium.org + + Time between sending a request to, and receiving a reply from, GAIA token + endpoint to validate TokenInfo. + + + + + raleksandrov@google.com + antrim@chromium.org + rsorokin@chromium.org + cros-oac@google.com + + Time between sending a request to, and receiving a reply from, GAIA token + endpoint to obtain TokenInfo. + + + + + alemate@chromium.org + achuith@chromium.org + + Chrome OS histogram that keeps track of number of users who have logged in + in the last 28 days. Reported on every boot and once a day after that. + + + + + alemate@chromium.org + achuith@chromium.org + + Chrome OS histogram that keeps track of number of users who have logged in + in the last day. Reported on every boot and once a day after that. + + + + + alemate@chromium.org + achuith@chromium.org + + Chrome OS histogram that keeps track of number of users who have logged in + in the last 7 days. Reported on every boot and once a day after that. + + + + + alemate@chromium.org + achuith@chromium.org + + Chrome OS histogram that keeps track of percentage of local users who have + logged in in the last 7 days. Reported on every boot and once a day after + that. + + + + + cmasone@chromium.org + + Chrome OS histogram that keeps track of the way a user logs in and whether + Chrome OS is running normal or developer mode. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/media/histograms.xml b/tools/metrics/histograms/histograms_xml/media/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..6ea5808fc7ecd6a4495e7081020c329fca520f8e --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/media/histograms.xml @@ -0,0 +1,4743 @@ + + + + + + + + + + vikassoni@chromium.org + Error codes to handle AImage and AImageReader api calls. + + + + mlamouri@chromium.org + media-dev@chromium.org + + Android-specific metric. The time between the moment the backgrounded video + playback is started (meaning the user just resumed the backgrounded video + allowing playback) and the moment it stops being background playback by the + current playing video either going foreground or being paused by the user. + Note: on Android, videos are suspended when backgrounded. + + + + + tguilbert@chromium.org + media-dev@chromium.org + Android: Whether MediaPlayer exited without errors. + + + + sandersd@chromium.org + media-dev@chromium.org + + Wall time of MediaPlayer playbacks. Each count represents one second of + media playback. Multiple MediaPlayer instances can together accumulate watch + time faster than real time. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Records when an audible tab is closed and we now only have one audible tab + open. + + + + + mlamouri@google.com + media-dev@chromium.org + + Records how long more than one tab is audible at the same time. The + concurrent tabs might change during this period. The time recorded starts + when the browser goes from one to two audbile tabs and stops when it is back + below two. + + + + + mlamouri@google.com + media-dev@chromium.org + + Records how many tabs were audible when a new tab started to be audible. + + + + + mlamouri@google.com + media-dev@chromium.org + + Records how many tabs are audible at the same time during the session. It is + recording the maximum audible tab count everytime it increases. In other + words, a session with N concurrent audible tabs will record entries from 1 + through N exactly once. + + + + + henrika@chromium.org + media-dev@chromium.org + + Size (in audio frames) of native I/O buffers that is set by the audio + manager when calling AUAudioInputStream::Open(). I.e., it is the actual + buffer size and it can differ from the one that the client requested. Only + sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + henrika@chromium.org + media-dev@chromium.org + + Stored in combination with Media.Audio.RenderFailsWhenBufferSizeChangesMac. + It is set to true if calls to AudioUnitRender has ever worked, i.e., we did + not start to see kAudioUnitErr_CannotDoInCurrentContext error messages + directly from start but there has been at least on successful call to + AudioUnitRender. + + + + + mlamouri@chromium.org + media-dev@chromium.org + Records the autoplay source of audios. + + + + guidou@chromium.org + olka@chromium.org + + Whether missing callbacks where detected during audio capture. Logged when + AudioInputDevice is stopped. + + + + + guidou@chromium.org + armax@chromium.org + + The number of captured audio frames that is provided by the operating system + in each callback. Typically, Chrome will want to use a 10 ms buffer (e.g. + 480 frames for a sample rate of 48 kHz), but the OS may decide to capture + e.g. 256 frames of audio at a time. If the desired frame size is used, the + emitted value is special-cased to be 0. This histogram then shows how + frequent it is that the desired number of frames is used and if not, the + number of frames used in practice. The number of frames per callback is + normally constant or very rarely changed throughout the lifetime of the + audio stream. The first value that differs from the desired value is stored + and logged when an audio input stream is closed. Any further differences + during the lifetime will be ignored. + + + + + guidou@chromium.org + olka@chromium.org + + The number of glitches that were detected at the OS level while an audio + stream was active. A glitch is detected if the OS has to skip providing a + set of frames. This value is logged when an audio input stream is closed. + + + + + guidou@chromium.org + olka@chromium.org + + A boolean that reflects whether or not an error was reported during audio + capture for a high latency stream. + + + + + guidou@chromium.org + olka@chromium.org + + This histogram measures the duration of every input stream, as seen from the + renderer. It counts from when it has been successfully started, until it is + stopped. Streams that fail to start are not logged. + + + + + guidou@chromium.org + olka@chromium.org + + The length in milliseconds of the largest audio glitch that was detected at + the OS level. This value is logged when an audio input stream that has + suffered glitches is closed. + + + + + guidou@chromium.org + olka@chromium.org + + The combined length in milliseconds of audio glitches that was detected at + the OS level. This is useful to know in particular for audio processing such + as echo cancellation. This value is logged when an audio input stream that + has suffered glitches is closed. + + + + + guidou@chromium.org + olka@chromium.org + + A boolean that reflects whether or not an error was reported during audio + capture for a low latency stream. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The time from the first microphone access failure due to blocked system + permission before the last browser restart to startup after browser restart. + Logged once at browser startup if the system permission then is allowed. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The time from the last microphone access failure due to blocked system + permission before the last browser restart to startup after browser restart. + Logged once at browser startup if the system permission then is allowed. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for microphone. Logged once at browser + startup. For more information on the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for microphone. Logged once at browser + startup if there was a failure accessing the microphone due to blocked + system permission before the last browser restart. For more information on + the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for microphone at the time of a user media + request. Logged when the system permission is checked. If the permission is + "not determined" this is logged, permission is requested, and the + resulting permission (from the user response) is also logged. For more + information on the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + guidou@chromium.org + olka@chromium.org + + When AudioInputDevice is stopped, this stat is recorded with whether an + error callback was ever received over IPC, and in that case whether the + error occurred during or after stream creation. + + + + + maxmorin@chromium.org + + A boolean that reflects whether or not an error was reported during audio + capture for a virtual stream. + + + + + tommi@chromium.org + guidou@chromium.org + olka@chromium.org + + Error codes from IAudioClient::Initialize() in + WASAPIAudioInputStream::InitializeAudioEngine on Windows. + + + + + guidou@chromium.org + olka@chromium.org + + Errors from IAudioClient::Initialize() in + WASAPIAudioInputStream::InitializeAudioEngine on Windows that are related to + the audio format. Each error is split by whether format conversion was used + or not. + + + + + gudiou@chromium.org + olka@chromium.org + + Success/error cases for opening an audio input stream on Windows. + + + + + guidou@chromium.org + armax@chromium.org + + Tracks support and initialization success/failure of the CoreAudio dispatch + override hotfix. Logged during initialization of AudioManagerMac. The fix is + not supported on macOS earlier than version 10.10. + + + + + guidou@chromium.org + armax@chromium.org + + Logged whenever the CoreAudio dispatch override hotfix needs to look up the + calling function using dladdr(). Once ResumeIO and PauseIO have been + identified, no more lookups should be performed during the session. + + + + + henrika@chromium.org + + Indicates if the size of the audio unit's IO buffer was changed when + starting an input audio stream. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + henrika@chromium.org + webrtc-audio@google.com + + Indicates if audio capturing did start after stream startup was requested. + Sampled once, a few seconds after a stream has been asked to start. + + + + + henrika@chromium.org + media-dev@chromium.org + + Indicates if the volume level of the audio session is set to zero when the + input audio session starts. Sampled once when the stream starts but only on + Windows platforms. See http://crbug.com/1014443. + + + + + henrika@chromium.org + media-dev@chromium.org + + The number of logical processors/cores available on the Mac OSX device. Only + sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Time delta between the moment output device authorization request is + received by the browser and the moment its processessing is finished (and + reply is to be sent back to the renderer if IPC is not closed yet). + + + + + henrika@chromium.org + webrtc-audio@google.com + + The number of physical processors/cores available on the Mac OSX device. + Only sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + armax@chromium.org + guidou@chromium.org + + The time, in milliseconds, between when a block of audio is read from the + soundcard and when it's presented to the audio processor. Used in + calculating the total system delay for the audio processor. + + + + + armax@chromium.org + guidou@chromium.org + + The variance of the capture delay in milliseconds (see + Media.Audio.Processing.CaptureDelayMs). Logged once every second and + calculated over the past second of data. + + + + + armax@chromium.org + guidou@chromium.org + + The time, in milliseconds, between when a block of audio is presented to the + audio processor and the time it's played out on the soundcard. Used in + calculating the total system delay for the audio processor. + + + + + armax@chromium.org + guidou@chromium.org + + The variance of the render delay in milliseconds (see + Media.Audio.Processing.RenderDelayMs). Logged once every second and + calculated over the past second of data. + + + + + armax@chromium.org + guidou@chromium.org + + The estimated total audio system delay presented to the audio processor. The + sum of the individual capture and render delays at similar points in time. + + + + + armax@chromium.org + guidou@chromium.org + + The variance of the total delay in milliseconds (see + Media.Audio.Processing.TotalDelayMs). Logged once every second and + calculated over the past second of data. + + + + + guidou@chromium.org + olka@chromium.org + + The number of frames audio is actually rendered at if the number is + different from the desired number of frames. If the desired frame size is + used, this value will be 0. Typically, Chrome will want to use a 10ms buffer + (e.g. 480 frames for a sample rate of 48kHz), but we might have to render + audio 256 frames at a time. This histogram gives us an indication as to how + frequent that is and what buffer sizes are used in practice. This value is + logged when an audio output stream is stopped. + + + + + guidou@chromium.org + armax@chromium.org + + The time spent to get audio data from the source. For WebRTC, it's the time + spent in WebRtcAudioRenderer::SourceCallback. Logged every function call, + which is every 10 ms. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + guidou@chromium.org + armax@chromium.org + + The maximum time spent to get audio data from the source during a session. + For WebRTC, it's the time spent in WebRtcAudioRenderer::SourceCallback. A + session is between Start() and Stop() of WebRtcAudioRenderer. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + guidou@chromium.org + olka@chromium.org + + The number of glitches that were detected at the OS level while an audio + stream was active. A glitch is detected if the OS has to skip rendering a + set of frames. This value is logged when an audio output stream is stopped. + + + + + guidou@chromium.org + olka@chromium.org + + The length in milliseconds of the largest glitch that was detected at the OS + level. This value is logged when an audio output stream that has suffered + glitches is stopped. + + + + + guidou@chromium.org + olka@chromium.org + + The combined length in milliseconds of audio glitches. This is useful to + know in particular for audio processing such as echo cancellation. This + value is logged when an audio output stream that has suffered glitches is + stopped. + + + + + maxmorin@chromium.org + + Similar to Media.Audio.OutputDeviceAuthorizationTime, this histogram + measures the time required for device authorization, but it is measured on + the renderer side when AudioOutputDevice calls RequestDeviceAuthorization on + the IO thread until it receives OnDeviceAuthorized, also on the IO thread. + Note that an authorization timeout will cause OnDeviceAuthorized to be + called, so for platforms that use a timeout, very few times will be above + the timeout value. + + + + + guidou@chromium.org + olka@chromium.org + + Whether audio output device timed out waiting for authorization reply from + the browser side. + + + + + armax@chromium.org + dalecurtis@chromium.org + guidou@chromium.org + olka@chromium.org + + Device status received in response to device authorization request. + + + + + maxmorin@chromium.org + + This histogram measures the duration of every output stream, as seen from + the renderer. It counts from when it has been successfully started, until it + is stopped. Streams that fail to start are not logged. + + + + + guidou@chromium.org + olka@chromium.org + + Whether a cached sink was used to get audio output device information, or a + new sink was created for that. + + + + + guidou@chromium.org + olka@chromium.org + + When a new sink is created to get output device information, it is cached. + This metric shows if such a sink is later reused for audio output (can + happen no more than once) or deleted unused after timeout expires. Logged + when one of the abovementioned events takes place. + + + + + guidou@chromium.org + olka@chromium.org + + Whether a sink was created through the sink cache or directly. + + + + + maxmorin@chromium.org + + When AudioOutputDevice is stopped, this stat is recorded with whether an + error callback was ever received over IPC, and in that case whether the + error occurred during or after stream creation. + + + + + henrika@chromium.org + media-dev@chromium.org + + True if a call to AudioUnitRender failed with an error code of + kAudioUnitErr_CannotDoInCurrentContext (-10863) and the call was preceded + with a change in the native I/O buffer size. This value is logged while + input audio is active but it should be a very rare event. + + + + + henrika@chromium.org + media-dev@chromium.org + + Size (in audio frames) the client has asked for when creating an + AUAudioInputStream object. It might not be able to fulfill this request. The + actual size is given by Media.Audio.ActualInputBufferFrameSizeMac. Only + sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + + + + olka@chromium.org + maxmorin@chromium.org + + Device status received during TrackAudioRenderer initialization. This is a + specific case of Media.Audio.Render.OutputDeviceStatus histogram. + + + + + + + + + olka@chromium.org + maxmorin@chromium.org + + Device status received by TrackAudioRenderer when switching the output + device. This is a specific case of Media.Audio.Render.OutputDeviceStatus + histogram. + + + + + + + + + olka@chromium.org + maxmorin@chromium.org + + Device status received during WebRTCAudioRenderer initialization. This is a + specific case of Media.Audio.Render.OutputDeviceStatus histogram. + + + + + + + + + olka@chromium.org + maxmorin@chromium.org + + Device status received by WebRTCAudioRenderer when switching the output + device. This is a specific case of Media.Audio.Render.OutputDeviceStatus + histogram. + + + + + dalecurtis@chromium.org + Bits per channel of HTML5 audio sample data. + + + + guidou@chromium.org + olka@chromium.org + + Whether there is input audio glitches due to dropped input audio data or + not. Sampled when a low-latency input audio stream is destructed. + + + + + guidou@chromium.org + olka@chromium.org + + The percentage of input audio data that was dropped at the browser/renderer + boundary due to for example buffer overflow in the writer side buffer or in + the socket. Reported at the destruction of low-latency audio input stream. + + + + + gudou@chromium.org + olka@chromium.org + + The percentage of input audio data blocks that had to be buffered because + there was not room in the shared memory ring buffer on the browser/renderer + boundary. This happens if the reading side hasn't read data in time. + Reported at the destruction of low-latency audio input stream. + + + + + + + dalecurtis@chromium.org + Audio codec used in HTML5 media. + + + + dalecurtis@chromium.org + media-dev@chromium.org + Audio codec profile used in HTML5 media for AAC playback. + + + + henrika@chromium.org + webrtc-audio@google.com + + Error codes that AudioUnitRender() returns in AUAudioInputStream on Mac. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + Measures the time taken for AudioInputController:: + + + + guidou@chromium.org + olka@chromium.org + + Every 15 seconds during the lifetime of an audio input stream, the sound + level is measured, see AudioInputController::CheckAudioPower(). If the level + is below a certain threshold, it's considered "silence". Otherwise + it's considered "audio". This metric shows whether there was only + silence, only audio, or both, during the lifetime of a stream. If logged + before the first measurement, i.e. if the lifetime is less than 15 seconds, + "no measurement" is reported. If there is no audio data provided + by the OS during the lifetime of the stream, for example because of a bug, + measurements will not be performed and "no measurement" is + reported. + + + + + guidou@chromium.org + olka@chromium.org + + A boolean that reflects whether or not an error was reported during audio + rendering, reported after a stream has stopped, if it was started. + + + + + + + + + olka@chromium.org + guidou@chromium.org + armax@chromium.org + + Time interval from the output stream controller construction to its + destruction. + + + + + guidou@chromium.org + olka@chromium.org + + Whether an AudioOutputController succeeded in creating and opening an output + stream proxy. Only logged for the initial creation, subsequent re-creations + due to device change events are logged in the + Media.AudioOutputController.ProxyStreamCreationResultForDeviceChange + histogram. + + + + + guidou@chromium.org + olka@chromium.org + + Whether an AudioOutputController succeeded in creating and opening an output + stream proxy after receiving a default device change event. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Time spent waiting in AudioOutputController::WaitTillDataReady() if the data + was not initially available. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Whether playback started successfully after stream startup was requested. + + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Whether a low latency stream to be rendered through the resampler was opened + successfully or which type of fallback stream was used instead. In case a + fake fallback stream is used it means audio rendered through the resampler + will be muted. In case fallback fails entirely, renderer callback error will + be signalled. + + + + + marinaciocea@chromium.org + + This histogram is the 3nd potential failure step in + CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram + is input for + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult + histogram. + + + + + marinaciocea@chromium.org + + This histogram is the 1st potential failure step in + CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram + is input for + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult + histogram. + + + + + marinaciocea@chromium.org + + This histogram is the 2nd potential failure step in + CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram + is input for + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult + histogram. + + + + + marinaciocea@chromium.org + + This histogram is the last potential failure step in + CoreAudioUtil::GetPreferredAudioParameters. + + + + + marinaciocea@chromium.org + + This histogram is the 4nd potential failure step in + CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram + is input for + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult + histogram. + + + + + olka@chromium.org + + Records format used by AudioManager to create audio output stream proxy. If + a fake stream is created it results in muted audio playback. + + On Windows, the failure reasons that can lead to fake stream creation are + tracked with the following histograms: + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceEnumeratorResult + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult + Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult + + + + + henrika@chromium.org + olka@chromium.org + + Captures if render-side audio glitches are detected or not. Sampled when a + low-latency output audio stream is destructed. + + + + + armax@chromium.org + dalecurtis@chromium.org + guidou@chromium.org + olka@chromium.org + + Status of audio sink used by AudioRendererImpl. If not OK, a NullAudioSink + will be used for audio output instead. This is logged for every call to + AudioRendererImpl::Initialize, which generally occurs once per active audio + session (i.e., between a play and pause). If audio track changes are ever + enabled, it may additionally be called for every audio track change. + + + + + dalecurtis@chromium.org + olka@chromium.org + + Percentage of AudioSyncReader::Read() calls where the renderer missed its + realtime deadline. + + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + How long it take for the audio manager instance to be created by the audio + service, in case the audio service owns the audio manager. + + + + + marinaciocea@chromium.org + maxmorin@chromium.org + olka@chromium.org + + The time interval when the audio service has connections, computed from the + moment the first bind request is received to the moment when the last + connection is closed. + + + + + marinaciocea@chromium.org + maxmorin@chromium.org + olka@chromium.org + + The time interval when the audio service has no connections, computed from + the moment the last connection is closed until quit closure is called or a + new bind request is received. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + State of the audio thread. A value of "started" is emitted once + the hang monitor has been initialized. If the thread is detected as hung + later, a value of "hung" is emitted. If the hung thread later + recovers a value of "recovered" is emitted. + + + + + liberato@chromium.org + videostack-eng@chromium.org + + Record a count for each frame sent to the client by AVDA, separated by what + type of frame it is: Non Overlay, secure overlay, etc. + + + + + liberato@chromium.org + videostack-eng@chromium.org + + Record a count for each frame sent to the client by AVDA. True counts + indicate that the frame was an overlay (SurfaceView). False counts are for + Non Overlay frames. This will be deprecated in favor of + Media.AVDA.FrameInformation in M63. + + + + + chcunningham@chromium.org + mlamouri@google.com + media-dev@chromium.org + + Time spent between receiving a decodingInfo() call and resolving it. It only + record successful calls and ignores audio-only. + + + + + chcunningham@chromium.org + mlamouri@google.com + media-dev@chromium.org + + Time spent between receiving a decodingInfo() call and resolving it. It only + record successful calls and ignores audio-only. This is a subset of + Media.Capabilities.DecodingInfo.RequestTime.Video that only takes into + account clear content. + + + + + chcunningham@chromium.org + mlamouri@google.com + media-dev@chromium.org + + Time spent between receiving a decodingInfo() call and resolving it. It only + record successful calls and ignores audio-only. This is a subset of + Media.Capabilities.DecodingInfo.RequestTime.Video that only takes into + account encrypted content. + + + + + vikassoni@chromium.org + liberato@chromium.org + + Whether we exceeded the timeout in CodecBufferWaitCoordinator:: + WaitForFrameAvailable and will proceed without a frame ready. + + + + + vikassoni@chromium.org + liberato@chromium.org + + Time spent waiting for a frame to become available in a Non Overlay + (TextureOwner mode) so that MediaCodec can render it. This time is recorded + before the frame is rendered. + + + + + cassew@google.com + media-dev@chromium.org + + Duration of decoder selection during config changes, measured from first + call to 'DecoderSelector::SelectDecoder' to + 'DecoderSelector::FinalizeSelection'. The HW/SW suffix indicates the type of + the decoder that was ultimately selected. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + Records events related to click through rate (CTR) calculation. + + The CTR can be calculated by computing "Interacted" / + "Displayed". "Interacted", for buttons, means that they + were clicked. For sliders, it will reflect any change in the internal state + and includes other events in addition to clicks. "Displayed" means + that the control element was meant to be displayed in the controls. It does + not mean that the user have seen the element so is not to be confused with + visibility. Furthermore, because the controls UI changes while loading, + "Displayed" is only computed when metadata are available unless + preloading was disabled on the element or the browser. + + + + + mlamouri@chromium.org + + Record whether the default media controls of an audio element were shown and + why every time they could be shown. Note that audio elements that were not + insterted to the DOM and do not have a controls attribute are not taken into + account. + + + + + mlamouri@chromium.org + + Record whether the default media controls of a video element were shown and + why every time they could be shown. + + + + + dalecurtis@chromium.org + + The state of the user selected virtual beamforming audio device on CrOS. + It's logged whenever the format of the audio input stream is queried, which + at least happens on stream startup, but could happen at other times as well. + + + + + liberato@chromium.org + tmathmeyer@chromium.org + + This enum allows us to count D3D11VideoDecoder specific crashes and + initialization failures. This is recorded whenever the decoder is + initialized or destroyed. + + + + + liberato@chromium.org + sandersd@chromium.org + tmathmeyer@chromium.org + + This enum measures whether or not d3d11 is supported and if not, what the + reason is. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Audio codec used in HTML5 media. Reporting corrected in M51 to include all + detected audio codecs, not just those up to and including the first one + supported. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + Audio codec used in HTML5 media for a local file playback. + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Container used for HTML5 media. Views that include pre-M34 data will + categorize dash (38) and smooth streaming (39) in the "Other" + bucket. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + Container used for HTML5 media for a local file playback. + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Video codec used in HTML5 media. Reporting corrected in M51 to include all + detected video codecs, not just those up to and including the first one + supported. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + Video codec used in HTML5 media for a local file playback. + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Count of dropped frames between pipeline start and stop. Media pipeline + starts/stops when an HTML5 video is loaded/unloaded respectively in the + browser. + + + + + liberato@chromium.org + sandersd@chromium.org + + This enum measures how often each of the various DXVAVDA PictureBuffer + display mechanisms are used. Each count represents the mechanism selected at + the end of DXVA::Initialize; i.e., there is one count per decoder. + + + + + liberato@chromium.org + tmathmeyer@chromium.org + sandersd@chromium.org + + Records how many times the DXVA VDA successfully initializes a D3D11 device + vs. D3D9 device. + + + + + sandersd@chromium.org + media-dev@chromium.org + Result of EME promises that were handled by Chromium code. + + + + xhwang@chromium.org + media-dev@chromium.org + + Size in KB of the last file successfully read by the CDM through CDM FileIO + before a specific error happens. This is reported only when the error + happens, which should be rare. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Size in KB of the first file successfully read by the CDM through CDM + FileIO. This is recorded once per CDM instance. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The actual time spent by the CDM accessing a file. This is only recorded for + successful operations. + + + + + xhwang@chromium.org + media-dev@chromium.org + + The status of CDM host verification. This is reported per CDM load. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Chromium could support multiple versions of CDM interface. This metric + records the CDM interface version that the CDM created by Chromium uses. + This is recorded once per CDM instance. + + + + + xhwang@chromium.org + media-dev@chromium.org + + The error code of a library CDM load failure. Only reported on Windows. + + + + + xhwang@chromium.org + media-dev@chromium.org + The result from an attempt to load a library CDM. + + + + xhwang@chromium.org + media-dev@chromium.org + The time spent to load a library CDM. + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether the CDM instance is created successfully. Reported each time a CDM + instance creation is attempted, usually as a result of Javascript call of + createMediaKeys(). + + + + + xhwang@chromium.org + media-dev@chromium.org + The time it takes to create the CDM instance. + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether EME encrypted event has been fired. Every time a WebMediaPlayerImpl + object is created a "false" value is reported to provide a + baseline. Every time an encrypted event is fired, a "true" value + will be reported. Note that it is possible to have multiple encrypted events + during the lifetime of a WebMediaPlayerImpl object. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether encrypted media is enabled when requestMediaKeySystemAccess() is + called. User can enable and disable encrypted media in content settings. + Recorded when requestMediaKeySystemAccess() is called but will be reported + at most once per renderer process. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The encryption scheme used by the audio stream in an HTML5 video. Reported + when metadata is available if the initial config is encrypted. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The encryption scheme used by the video stream in an HTML5 video. Reported + when metadata is available if the initial config is encrypted. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether a given WebMediaPlayer instance, with a CDM attached, is played in + an incognito window or in Chrome OS guest mode. Players that never started + playback are excluded. Recorded once at time of player destruction. + + + + + xhwang@chromium.org + media-dev@chromium.org + System code count associated with key status. + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether the CDM is available for the key system or not. In normal cases, + this is reported once per render process if the EME API is used. In rare + cases it could be reported more than once if the CDM is not available and + then is component updated. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Reported at most once during browser process shutdown the max number of + concurrent CDM processes at any time during the lifetime of that browser + process. Will NOT be reported if no CDM process has ever been created. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether MediaCrypto is available on a MediaDrm-based CDM. Reported once per + MediaDrmBridge creation. In normal cases it should always be available. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The status of every attempt to obtain a pre-provisioned origin ID to be used + by MediaDrm. This will only be reported for applications that use + MediaDrmOriginIdManager. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The number of pre-provisioned origin IDs available shortly after startup on + devices that do not support per-application provisioning. + + + + + jrummell@chromium.org + media-dev@chromium.org + + The number of pre-provisioned origin IDs available shortly after startup on + devices that support per-application provisioning. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether MediaDrmBridge supports the key system. Reported once per + MediaDrmBridge creation. In normal cases it should always be supported. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether connection error has happened for MojoCdm. Every time a MojoCdm + object is created a "false" value is reported to provide a + baseline. Every time a mojo connection error happened, a "true" + value will be reported, which typically means a remote CDM process crash. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Output protection query status and result. One query and one positive (no + unprotected external links) result (if any) are reported per CDM instance. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Key system support query status and result, as reported by + RequestMediaKeySystemAccess. Each value will be reported at most once per + renderer process. + + + + + xhwang@chromium.org + media-dev@chromium.org + System code count in promise rejection. + + + + xhwang@chromium.org + media-dev@chromium.org + The time it takes to resolve a EME promise. + + + + jrummell@chromium.org + media-dev@chromium.org + + The net error or HTTP response code of provisioning requests made by + UrlProvisionFetcher on Android and Cast devices. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Whether the robustness level of any video capability in the supported + configuration passed into requestMediaKeySystemAccess() is empty. This is + specific to the Widevine key system. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when the Media Engagement Preloaded List is checked whether a + string is present on that list. If the check was successful then the result + of the check is recorded in this histogram. If the check was not successful + then the reason for the check failing is recorded. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when data is loaded into the Media Engagement Preloaded List. If + the load is successful then "loaded" is recorded to this + histogram. If the load was not successful then the reason why is recorded to + this histogram. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The media engagement score recorded at the time of playback. It is converted + to a percentage so should be divided by 100 to get the actual score. It is + only recorded for playback that is either lacking an audio track or not + muted. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when the Media Engagement service doesn't determine a player to be + significant. If a player is not significant the reasons why will be + individually recorded to this histogram each time except for the first time + which is recorded to a different histogram. + + The significant state of a player is reevaluated any time the state of the + player changes (e.g. muted, playing/paused). If the player was not + considered signficiant and still is not then we will record the reasons why + in this histogram. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when the Media Engagement service doesn't determine a player to be + significant. If a player is not significant the reasons why will be + individually recorded to this histogram the first time only. + + The significant state of a player is reevaluated any time the state of the + player changes (e.g. muted, playing/paused). If the player was not + considered signficiant and still is not then we will record the reasons why + in this histogram. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when the Media Engagement service no longer determines a player to + be significant. If a player is no longer significant, the reasons why will + be individually recorded to this histogram. + + The significant state of a player is re-evaluted any time the state of the + player changes (e.g. muted, playing/paused). If the player was previously + considered significant and is no longer considered that we will record the + reasons why in this histogram. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Whether Chrome had to fallback to the high latency audio path or not. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when a Media Feed is loaded from the database. If there was an + error reading from the database then the result will include the reason. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when a Media Feed item is loaded from the database. If there was an + error reading from the database then the result will include the reason. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Records the size of the fetched feed when a Media Feed is periodically + fetched in the background. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when a Media Feed Item is checked against Safe Search. This happens + automatically when Chrome fetches the feed so long as the user has opted + into Safe Search checking. + + + + + steimel@chromium.org + media-dev@chromium.org + + Records if the Global Media Controls device selector was available. Recorded + once per notification either when the device selector was shown or when the + notification disappears. + + + + + steimel@chromium.org + media-dev@chromium.org + + Records if the Global Media Controls device selector was opened. Recorded + once per notification either when the device selector was opened or when the + notification disappears. This histogram is only recorded if the device + selector was available. + + + + + steimel@chromium.org + media-dev@chromium.org + + Recorded each time a media session is dismissed or removed from the Global + Media Controls. Records the reason why it happened (e.g. user clicked the + dismiss button or playback stopped). + + + + + steimel@chromium.org + media-dev@chromium.org + + Recorded each time a paused media session is interacted with (e.g. playing + the media or clicking on the notification to go back to the tab). Records + the time passed since it was last interacted with (or since when it was + paused if this is the first post-pause interaction). + + + + + steimel@chromium.org + media-dev@chromium.org + + Recorded each time the Global Media Controls Device picker dialog is opened + and is populated with devices. Records the number of device options + displayed, possibly including the default fallback device. + + + + + steimel@chromium.org + media-dev@chromium.org + + Recorded each time the Global Media Controls dialog is opened. True if this + was repeat usage of the dialog (e.g. if it's not the first time the dialog + has been opened this session). + + + + + steimel@chromium.org + media-dev@chromium.org + + The focused state of the WebContents associated with the MediaSession that + the user is interacting with via the Global Media Controls. Recorded when + the user presses an action on the Global Media Controls dialog (e.g. play). + + + + + dcastagna@chromium.org + + Records when a context provider is acquired in media, and when it's released + because a context loss has been detected. + + + + + acourbot@chromium.org + chromeos-video-eng@google.com + + Counts of status values returned from calls to + GpuArcVideoDecodeAccelerator::Initialize(). + + + + + dcastagna@chromium.org + mcasas@chromium.org + + GpuMemoryBufferVideoFramePool is called with an unsupported VideoFrame pixel + format. Emitted on VideoFrame arrival. + + + + + vikassoni@chromium.org + liberato@chromium.org + + The error code returned when GetSharedContextState() fails or MakeCurrent() + on the SharedContextState fails. + + + + + + + dalecurtis@chromium.org + Channel count of the hardware audio device. + + + + + + dalecurtis@chromium.org + Channel layout of the hardware audio device. + + + + + + dalecurtis@chromium.org + Samples per second of the hardware audio device. + + + + steimel@chromium.org + media-dev@chromium.org + + Records media key presses that are handled by the + HardwareKeyMediaController. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Whether a given WebMediaPlayer instance, after preload, started playback; + recorded once at time of player destruction. + + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Whether capture started successfully after a high-latency input stream + startup was requested. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The size of the Media History database. Recorded once on startup. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when Media History is initialized when the browser is started. This + is not recorded in incognito mode or if "save browsing history" is + disabled. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when Media History is recreated when the browser is started and the + Media History database has been corrupted to the point where we need to + delete it and start again. This is not recorded in incognito mode or if + "save browsing history" is disabled. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when Media History records a playback to the database. Playbacks + are recorded when the player is destroyed and are are recorded on a + per-player level and might be called multiple times on a single page. + Playbacks are not recorded in incognito mode or if "save browsing + history" is disabled. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when Media History records a sessions to the database. Sessions are + recorded once per WebContents on navigation if there was playback on the + page. Playbacks are not recorded in incognito mode or if "save browsing + history" is disabled. + + + + + cassew@google.com + media-dev@chromium.org + + Duration of initial decoder selection. Measured from first call to + 'DecoderSelector::SelectDecoder' to 'DecoderSelector::FinalizeSelection'. + The HW/SW suffix indicates the type of the decoder that was ultimately + selected. + + + + + tommi@chromium.org + webrtc-audio@google.com + + Error codes that we encounter while setting up an AUAudioInputStream on Mac. + + + + + henrika@chromium.org + webrtc-audio@google.com + + Duration in milliseconds of low-latency audio input streams. Sampled when + the stream is closed by the AudioInputController. + + + + + maxmorin@chromium.org + + Duration in milliseconds of low-latency audio input streams which never got + any callbacks. + + + + + steimel@chromium.org + beccahughes@chromium.org + media-dev@chromium.org + + Recorded each time the Kaleidoscope First Run Experience is shown when + either the tab is closed or the FRE is completed. Records how far into the + FRE the user got before exiting (or completing). + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded each time the Kaleidoscope module is loaded on the New Tab Page + with whether the data was loaded from the server or whether it hit the + cache. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded each time the Kaleidoscope module is loaded on the New Tab Page + with the time it takes to fetch the data from the server. + + + + + + + liberato@chromium.org + chcunningham@chromium.org + + Confusion matrix for UMA-reported regresssion tasks for media local learning + experiments. Each bucket is interpreted as follows: + + TrueNegative - prediction was negative, observation was negative. + FalseNegative - prediction was negative, observation was positive. + FalsePositive - prediction was positive, observation was negative. + TruePositive - prediction was positive, observation was positive. + + For those observations for which we could not make a prediction due to data + sparsity, the "no-prediction" buckets indicate whether the + observation was positive or negative. + + + + + + + liberato@chromium.org + chcunningham@chromium.org + + Confusion matrices, split out by the feature index used to train the model. + Each confusion matrix has 6 entries: + + TrueNegative - prediction was negative, observation was negative. + FalseNegative - prediction was negative, observation was positive. + FalsePositive - prediction was positive, observation was negative. + TruePositive - prediction was positive, observation was positive. + No-prediction Negative - no prediction made, observation was negative. + No-prediction Positive - no prediction made, observation was positive. + + The confusion matrix entry will also be labelled with a bucket number, which + for this histogram represents the index of the feature that was used. The + feature index matches |LearningTask::feature_descriptions| for the + appropriate task. + + + + + + + liberato@chromium.org + chcunningham@chromium.org + + Confusion matrices, split out by the total amount of training data used to + train the model. Each confusion matrix has 6 entries: + + TrueNegative - prediction was negative, observation was negative. + FalseNegative - prediction was negative, observation was positive. + FalsePositive - prediction was positive, observation was negative. + TruePositive - prediction was positive, observation was positive. + No-prediction Negative - no prediction made, observation was negative. + No-prediction Positive - no prediction made, observation was positive. + + The bucket number mentioned in the enum label indicates how much weight the + training set had. To convert from bucket number to an actual weight range, + one must know the particular settings in the corresponding LearningTask. + + Please see |LearningTask::max_reporting_weight| and + |LearningTask::num_reporting_weight_buckets| for the the appropriate task. + + + + + dalecurtis@chromium.org + + Audio IO layer used by the Linux OS, sampled once at startup of the browser. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Load type of HTML5 media, such as URL, MediaSource and MediaStream. + + + + + Please list the metric's owners. Add more owner tags as needed. + + State of the WebRtc local renderer, sampled once during the lifetime of a + local renderer. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The reason why the lock screen media controls were hidden if they were + previously shown. Recorded when the controls are destroyed by the lock + screen (e.g. unlock, switch user, shutdown). + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Whether the lock screen media controls were shown and if they will not be + shown the reason why. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The action (e.g. pause) that a user clicked on the lock screen media + controls. + + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Whether capture started successfully after a low-latency input stream + startup was requested. + + + + + liberato@chromium.org + sandersd@chromium.org + tguilbert@chromium.org + + The time between MediaCodec::dequeueOutputBuffer() and the dispatch of the + corresponding VideoFrame from MediaCodecVideoDecoder. + + + + + dalecurtis@chromium.org + + The total watch time (see Media.WatchTime) of a given playback divided by + the number of rebuffering events that occured during that playback. + + + + + jrummell@chromium.org + media-dev@chromium.org + + Whether the content type provided to HTMLMediaElement would parse with + ParsedContentType or not. + + + + + mlamouri@google.com + media-dev@chromium.org + + Recorded when an HTMLMediaElement play() promise is rejected (handled or + not) with the type of rejection. + + + + + steimel@chromium.org + media-dev@chromium.org + + Whether or not the MediaKeysListener was able to successfully register a hot + key. Failure typically indicates that the hotkey was already registered by a + different application. + + + + + mcasas@chromium.org + wtlee@chromium.org + The errors HW video encode encounters in MediaRecorder. + + + + mcasas@chromium.org + wtlee@chromium.org + Whether HW video encode is used in MediaRecorder. + + + + henrika@chromium.org + webrtc-audio@google.com + + Heuristically detects if the user has muted the microphone or not. Measured + approximately four times per minute. + + + + + toyoshim@chromium.org + midi-dev@chromium.org + + Reports whether any data was sent or received by a MidiManager. Recorded + once per MidiManager instantiation, upon destruction. MidiManager is + instantiated when the first Web MIDI client starts a session, and destroyed + when the last client ends the session. + + + + + toyoshim@chromium.org + midi-dev@chromium.org + Reports sysex message size. + + + + toyoshim@chromium.org + midi-dev@chromium.org + + The MidiManager instance use count, but this is not intended to understand + the real API usage because this can be counted by feature scanning scripts + that are often used for footprinting. You may want to track SendReceiveUsage + to monitor only instances that actually send or receive MIDI messages. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Records the number of active MojoVideoDecoderService instances that are + alive each time an instance becomes active. An instance is active if + Decode() has been called at least once. This provides an estimate of the + concurrent hardware resource requirements. + + + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + Delay between a DecodeBuffer (and encoded chunk) input and a decoded + VideoFrame being produced by the remote MojoVideoDecoder. Output once per + successful decode. + + + + + eugene@chromium.org + liberato@chromium.org + + Total number of instances of MojoVideoDecoder used by a page (i.e. render + frame) when an instance of MojoVideoDecoder encountered a decoding error or + a crash during the first 150 frames of a video stream. + + + + + eugene@chromium.org + liberato@chromium.org + + Total number of instances of MojoVideoDecoder used by a page (i.e. render + frame) when an instance of MojoVideoDecoder successfuly decode the first 150 + frames of a video stream. + + + + + + + wolenetz@chromium.org + media-dev@chromium.org + + Audio codec used in Media Source Extensions playback. Set when MediaSource + addSourceBuffer() is successfully called during playback. Also set twice + during a successful SourceBuffer changeType() operation. See issue 535738 + for reworking MSE codec histograms to record on each successfully parsed + initialization segment (possibly filtered to record only when actual new + codec configurations are parsed). + + + + + wolenetz@chromium.org + sandersd@chromium.org + media-dev@chromium.org + + Duration of config changes that include codec changes, measured from before + decoder flush until after the first output frame is returned. The HW/SW + suffix indicates the type of the decoder that was ultimately selected. + + + + + wolenetz@chromium.org + media-dev@chromium.org + + Amount of time taken to destroy one ChunkDemuxer object, not including + initial background task scheduling delay. + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Tracks if ShakaPackager metadata was detected in the MP4 'moov' atom during + MSE based media playback. Recorded for every 'moov' atom, which is expected + once per asset. Multiple assets may be played within the same MSE session. + + + + + wolenetz@chromium.org + media-dev@chromium.org + + For each MediaSource instance, records the type of thread that created the + instance. + + + + + wolenetz@chromium.org + sandersd@chromium.org + + Reports the number of consecutive empty samples in a sequence within a track + run. There can be zero or more such sequences in a track run, and each + sequence is reported separately. This metric is expected to inform a + heuristic to realistically bound the parsing complexity of track runs that + may contain empty samples. See https://crbug.com/907268. + + + + + wolenetz@chromium.org + sandersd@chromium.org + + Reports the number of empty samples within a track run. This metric is + expected to inform a heuristic to realistically bound the parsing complexity + of track runs that may contain empty samples. See https://crbug.com/907268. + + + + + wolenetz@chromium.org + sandersd@chromium.org + + Reports the size of each sample parsed. This metric is expected to inform a + heuristic to realistically bound the parsing complexity of track runs that + may contain empty or huge samples. See https://crbug.com/907268. + + + + + wolenetz@chromium.org + sandersd@chromium.org + + Reports the number of samples in each track run. This metric is expected to + inform a heuristic to realistically bound the parsing complexity of track + runs that may contain huge numbers of samples. See https://crbug.com/907268. + + + + + + + wolenetz@chromium.org + media-dev@chromium.org + + Video codec used in Media Source Extensions playback. Set when MediaSource + addSourceBuffer() is successfully called during playback. Also set twice + during a successful SourceBuffer changeType() operation. See issue 535738 + for reworking MSE codec histograms to record on each successfully parsed + initialization segment (possibly filtered to record only when actual new + codec configurations are parsed). + + + + + + + wolenetz@chromium.org + media-dev@chromium.org + + Video codec used in Media Source Extensions playback if the media container + is MP4. Set when MediaSource addSourceBuffer() is successfully called during + playback. Also set twice during a successful SourceBuffer changeType() + operation. See issue 535738 for reworking MSE codec histograms to record on + each successfully parsed initialization segment (possibly filtered to record + only when actual new codec configurations are parsed). + + + + + + + wolenetz@chromium.org + media-dev@chromium.org + + Video codec used in Media Source Extensions playback if the media container + is WebM. Set when MediaSource addSourceBuffer() is successfully called + during playback. Also set twice during a successful SourceBuffer + changeType() operation. See issue 535738 for reworking MSE codec histograms + to record on each successfully parsed initialization segment (possibly + filtered to record only when actual new codec configurations are parsed). + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Whether the media notification (including ones for Cast sessions) is + displaying artwork. This is recorded when the artwork is updated by the + underlying media session. + + + + + takumif@chromium.org + openscreen-eng@google.com + media-dev@chromium.org + + Whether the Cast media notification is displaying artwork. This is recorded + a few seconds after a notification is shown for the first time, which is + different from when Media.Notification.ArtworkPresent is recorded. + + + + + takumif@chromium.org + openscreen-eng@google.com + media-dev@chromium.org + + The number of Cast media notifications that are currently being displayed. + This is recorded when a media notification starts being displayed. + + + + + takumif@chromium.org + openscreen-eng@google.com + media-dev@chromium.org + + Whether the Cast media notification is displaying certain types of metadata. + This is recorded a few seconds after a notification is shown for the first + time, which is different from when Media.Notification.MetadataPresent is + recorded. + + + + + takumif@chromium.org + openscreen-eng@google.com + media-dev@chromium.org + + The action (e.g. pause) that a user clicked on a Cast media notification + (including ones for Cast sessions). + + + + + mlamouri@chromium.org + media-dev@chromium.org + + The type of media notification the user clicked to go back to Chrome. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The number of media notifications that are currently being displayed + (including ones for Cast sessions). This is recorded when a media + notification starts being displayed. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + Whether the media notification (including ones for Cast sessions) is + displaying certain types of metadata. This is recorded when the metadata is + updated by the underlying media session. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The source of the underlying media session (e.g. ARC, web, Cast) that + displayed the media notification. This is recorded when a notification is + available to be shown. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The action (e.g. pause) that a user clicked on a media notification + (including ones for Cast sessions). + + + + + guidou@chromium.org + olka@chromium.org + + Duration of an audio output stream. Measured in AudioOutputController from + when a stream is started until it is stopped. A stream is stopped when it is + paused, closed (i.e. destructed), or when a device change event causes it to + be restarted. + + + + + mlamouri@google.com + media-dev@chromium.org + + Whether Pepper players have played sound through its lifetime. + + + + + ihf@chromium.org + posciak@chromium.org + Counts of video decode errors reported to plugin. + + + + sandersd@chromium.org + dalecurtis@chromium.org + + Counts every output picture emitted to a PPAPI client, categorized by size + and decoder type. Flash will only use platform decoders, but NaCl clients + can use either decoder type. + + + + + ihf@chromium.org + posciak@chromium.org + + Number of PictureBuffers/textures requested per hardware decoder creation. + This value varies by platform and video. A user visible video may trigger + multiple decoder creations (sometimes every 5 seconds) but would normally + not hold more than 2 sets of buffers at any given time in memory. + + + + + ihf@chromium.org + posciak@chromium.org + + Vertical video resolution rounded to the nearest bucket. (Corresponds + roughly to the number in 720p.) + + + + + prabhur@chromium.org + dalecurtis@chromium.org + + Status of the media pipeline at the end of its lifecycle suffixed by stream + and video decoder type. + + + + + xhwang@chromium.org + media-dev@chromium.org + + Status of the media pipeline starting process (including demuxer and + renderer initialization). If the media pipeline is destroyed during the + starting process nothing will be reported, but this should relatively rare. + + + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + Time for the platform-specific (set of) video decode acceleration command(s) + to be executed. Output once per decode request submit. + + + + + liberato@chromium.org + videostack-eng@chromium.org + + Total battery (0-100 percent) consumed by playback. When divided by + Media.PlaybackPower.ElapsedTime, this provides the average rate of battery + drain for that category of playback. Units are (total) percent. This is + recorded when an entire percent (or more) is consumed during playback. Since + devices have different battery sizes, methods of measuring battery, and + different power consumption rates, it's a good idea to filter by a specific + device type and OS version before trying to interpret these results. The + magnitude of these numbers, alone, is also likely hard to use, for this + reason. Instead, consider comparing A/B experiments to see if they get + larger or smaller. Playbacks under one msec are ignored. + + + + + liberato@chromium.org + videostack-eng@chromium.org + + Total time, in msec, elapsed while consuming the battery described by + Media.PlaybackPower.BatteryDelta. See that histogram for details. Recorded + when one or more percent of battery is consumed during playback. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Indicates the number of rebuffers a given watch time session had. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Tracks whether a web page allows content to be remoted. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Measured audio content transfer bitrate while remoting content. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Audio channel layout used while remoting content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Audio codec used while remoting content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Audio sampling rate while remoting audio content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Audio sampling rate while remoting audio content (atypical values, in Hz). + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Measures the duration of each remoting session. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Tracks the trigger for starting a remoting session. + + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Tracks the trigger for stopping a remoting session. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Measures the duration of each remoting session shorter than 15 seconds. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Measures how long, from the start of a remoting session, until content began + playing out on the remote device. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Measures how long, from the start of a remoting session, until a message was + received from the remote device indicating initialization succeeded. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Tracks whether audio or video or both are remoted. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Aspect ratio of video while remoting content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + + Measured video content transfer bitrate while remoting content. + + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Video codec used while remoting content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Video codec profile used while remoting content. + + + + miu@chromium.org + jophba@chromium.org + openscreen-eng@google.com + Video width while remoting content. + + + + posciak@chromium.org + Counts of video decode errors reported to RTCVideoDecoder. + + + + + + mcasas@chromium.org + sprang@chromium.org + chromeos-gfx@chromium.org + + Indicates whether we were successful in initializing hardware video decoder + for use in the RTC pipeline. + + + + + kron@chromium.org + webrtc-video@google.com + + Initialization latency of the hardware video decoder that is used in the RTC + pipeline. + + + + + + + mcasas@chromium.org + sprang@chromium.org + chromeos-gfx@chromium.org + Video codec profile used in RTC video decoder. + + + + kron@chromium.org + webrtc-video@google.com + + Reinitialization latency of the hardware video decoder that is used in the + RTC pipeline. + + + + + + + mcasas@chromium.org + sprang@chromium.org + chromeos-gfx@chromium.org + + Indicates whether we were successful in initializing hardware video encoder + for use in the RTC pipeline. + + + + + + + mcasas@chromium.org + sprang@chromium.org + chromeos-gfx@chromium.org + Video codec profile used in RTC video encoder. + + + + emircan@chromium.org + + Indicates whether we were successful in preserving timestamps in hardware + video encoder session. It is tracked during the session and logged after it + ends. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + Time during which a media session has been active, in other words, the time + between an activation and deactivation, without counting time while it was + suspended. If a session is activated after being deactivated, there will be + two entries. For example, if a user plays a song but is interrupted by a + phone call, it will only account for the song playing time. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + The number of times the user paused playback of a media session using other + means than the pause button on the page. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + The number of times the user started playback of a media session using other + means than the play button on the page. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + Indicate whether the native requestAudioFocus() call was successful. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + The number of times the user stopped a media session using other means than + the pause button on the page. + + + + + mlamouri@chromium.org + media-dev@chromium.org + + The number of times a media session is suspended and why it has been + suspended. + + + + + beccahughes@chromium.org + media-dev@chromium.org + + The number of times user interacts with MediaSession sorted by action type. + + + + + steimel@chromium.org + media-dev@chromium.org + + The focused state of the WebContents associated with the MediaSession that + the user is interacting with. Recorded when the user interacts with a + MediaSession (e.g. by pressing the play/pause key on their keyboard). + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Video codec used in plain src= (not MSE) HTML5 media if the media container + is MP4. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Video codec used in plain src= (not MSE) HTML5 media if the media container + is WebM. + + + + + + + mlamouri@google.com + media-dev@chromium.org + + The duration of the user gesture (how long their finger is down), recorded + at the end of each drag gesture. This histogram is split according to the + width of the slider track in CSS px - see histogram name suffix. + + + + + + + mlamouri@google.com + media-dev@chromium.org + + The net distance the media scrubber moved, recorded at the end of each drag + gesture, as a percentage of the width of the slider track. This histogram is + split according to the width of the slider track in CSS px - see histogram + name suffix. + + + + + + + mlamouri@google.com + media-dev@chromium.org + + The sum of absolute distances the media scrubber incrementally moved, + recorded at the end of each drag gesture, each measured as the change in + media current time. If the scrubber was dragged back and forth before being + released, this will be larger than the value recorded for + Media.Timeline.DragTimeDelta (and may even be larger than the media + duration), otherwise it will be the same as DragTimeDelta. This histogram is + split according to the width of the slider track in CSS px - see histogram + name suffix. + + + + + + + mlamouri@google.com + media-dev@chromium.org + + The net distance the media scrubber moved, recorded at the end of each drag + gesture, measured as the change in media current time. This histogram is + split according to the width of the slider track in CSS px - see histogram + name suffix. + + + + + + + mlamouri@google.com + media-dev@chromium.org + + The type of user gesture, recorded at the end of each input sequence. For + example holding down the right arrow key with the scrubber focused will only + be logged as a single event. This histogram is split according to the width + of the slider track in CSS px - see histogram name suffix. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Time in milliseconds from when WebMediaPlayerImpl starts loading until the + first video frame has been shown. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Time in milliseconds from when WebMediaPlayerImpl starts loading until + metadata is known. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Time in milliseconds from when WebMediaPlayer starts loading until it has + buffered enough to start playback. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + scherkus@chromium.org + Size of HTML5 media (when known), in MB. + + + + + + + + dalecurtis@chromium.org + + The amount of time taken to leave the underflow state (i.e. resume playback) + for playbacks. This doesn't report initial zero samples, which was + previously used to compensate for playbacks that don't rebuffer. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + URL scheme used with HTML5 media; only recorded for src=URL playbacks and + not for Media Source Extensions playbacks. Each URL provides one sample. + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + The codec-specific delegate in VaapiVideoDecoder has returned an error from + Decode(). This could be a parse error, or a VA error itself. + + + + + mcasas@chromium.org + chromeos-gfx-video@google.com + + Whether the creation of VaapiWrapper succeeded or not inside + VaapiVideoDecoder. + + + + + mcasas@chromium.org + chromeos-gfx-video@google.com + + Whether the call to VaapiWrapper's VADisplayState::Initialize() succeeded or + not. + + + + + andrescj@chromium.org + chromeos-gfx@chromium.org + + The response given to the client by VaapiJpegDecodeAccelerator for a decode + request. This is recorded when the decode succeeds or fails. The recorded + value corresponds to a MjpegDecodeAccelerator::Error. + + + + + wtlee@chromium.org + chromeos-gfx@chromium.org + + Result codes reported by jpeg encode using VA-API hardware jpeg encoder. + + + + + mcasas@chromium.org + chromeos-gfx-video@google.com + + Whether the creation of VaapiWrapper succeeded or not inside VaVDA. + + + + + mlamouri@google.com + media-dev@chromium.org + + Records the autoplay source of videos. This includes + Media.Video.Autoplay.Muted. + + + + + mlamouri@google.com + media-dev@chromium.org + Records the autoplay source of muted videos. + + + + mlamouri@google.com + media-dev@chromium.org + + Records muted video started playing with play() become visible at some + point. The UMA for false is not complete since it is recorded in a + destructor which is garbage-collected. Please subtract + Media.Video.Autoplay.Muted "play() method" count with the true + count of this histogram to obtain the real false count. + + + + + mlamouri@google.com + media-dev@chromium.org + + Records the offscreen playing duration of a muted video autoplaying from + play() method. + + + + + mlamouri@google.com + media-dev@chromium.org + + Status of the unmute action on a video that autoplayed because it was muted. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The time from the first camera access failure due to blocked system + permission before the last browser restart to startup after browser restart. + Logged once at browser startup if the system permission then is allowed. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The time from the last camera access failure due to blocked system + permission before the last browser restart to startup after browser restart. + Logged once at browser startup if the system permission then is allowed. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for camera. Logged once at browser startup. + For more information on the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for camera. Logged once at browser startup + if there was a failure accessing the camera due to blocked system permission + before the last browser restart. For more information on the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + grunell@chromium.org + engedy@chromium.org + hkamila@chromium.org + + The Mac system permission state for camera at the time of a user media + request. Logged when the system permission is checked. If the permission is + "not determined" this is logged, permission is requested, and the + resulting permission (from the user response) is also logged. For more + information on the values, see + https://developer.apple.com/documentation/avfoundation/avauthorizationstatus. + + + + + eugene@chromium.org + videostack-eng@chromium.org + + Video playback roughness for a 100s interval. Suffixed by the framerate. + + + + + mcasas@chromium.org + + Video Capture Device captured aspect ratio, as a rounded integer multiplied + by 100. The collection is made in the VideoCaptureController upon reception + of the first frame. + + + + + mcasas@chromium.org + + Counts appearances of Blacklisted Video Capture devices during enumeration. + This collection happens during first enumeration in the appropriate + platforms' VideoCaptureDeviceFactory. + + + + + guidou@chromium.org + armax@chromium.org + + Time it takes from the moment that a VideoCaptureController is requested to + start to the moment the first video frame arrives at + VideoCaptureController::OnFrameReadyInBuffer(). + + + + + mcasas@chromium.org + guidou@chromium.org + armax@chromium.org + + Breaks down the events counted in Media.VideoCaptureManager.Event bucket + "Stopping video capture due to error" by the origin of the error. + This allows narrowing down what is causing errors. An event for this + histogram is emitted once for each time a client disconnects from a video + capture session because the session has reported an error. + + + + + mcasas@chromium.org + guidou@chromium.org + armax@chromium.org + + An event for this histogram is emitted once for each time a video frame is + dropped on the way from a capture source, e.g. a webcam, to a corresponding + media::VideoCaptureController instance running in the Browser process. If + more than + |VideoCaptureController::max_consecutive_frame_drop_for_same_reason_count()| + frames are dropped consecutively for the same reason, no more events for the + same reason will be counted for that session until either a frame is + delivered successfully or the reason for the frame dropping changes. + + + + + mcasas@chromium.org + guidou@chromium.org + armax@chromium.org + + Video Capture Device frame rate requested by VideoCaptureManager on + AllocateAndStart(). The collection is made in the VideoCaptureController + upon reception of the first frame. + + + + + mcasas@chromium.org + + Video Capture Device captured frame height in pixels. The collection is made + in the VideoCaptureController upon reception of the first frame. + + + + + chfremer@chromium.org + + Indicates how many times Chrome has asked AVFoundation to enumerate devices + since the process start when zero devices are returned. This event is only + emitted for the first time that zero devices are returned since the process + start. This is used in the context of investigating http://crbug.com/582931. + + + + + perkj@chromium.org + + MacBook hardware version used when Chrome cannot enumerate a video device. + This is used for tracking http://crbug.com/582931. + + + + + perkj@chromium.org + + Number of video capture devices detected by Chrome during device + enumeration. Zero devices indicate a problem since all MacBooks should have + a built-in camera. This is used for tracking http://crbug.com/582931. + + + + + chfremer@chromium.org + + Counts events that are emitted in the context of attempting to mitigate the + issue of no cameras being found on Macbooks by restarting the video capture + service and retrying to obtain device infos, see http://crbug.com/582931. + + + + + chfremer@chromium.org + + An event for this histogram is emitted when a video capture session drops + more than + |VideoCaptureController::max_consecutive_frame_drop_for_same_reason_count()| + consecutive video frames for the same reason. After this event is emitted + once, no additional events are emitted for consecutively dropped frames for + the same reason until the count is reset by either a frame being delivered + successfully or a frame being dropped for a different reason. See also + Media.VideoCapture.FrameDrop. + + + + + mcasas@chromium.org + + Video Capture Device captured frame width in pixels. The collection is made + in the VideoCaptureController upon reception of the first frame. + + + + + chfremer@chromium.org + + Indicates which video capture backend is used on Windows. A count is + recorded each time a new VideoCaptureDeviceFactoryWin instance is created. + + + + + chfremer@chromium.org + + Counts number of times taking a still image on Windows fails/succeeds. + + + + + chfremer@chromium.org + + Counts how many retries are needed for calls to MediaFoundation function + GetAvailableDeviceMediaType before getting a result different from + MF_E_INVALIDREQUEST or giving up. + + + + + guidou@chromium.org + armax@chromium.org + + Counts how many retries are needed for calls to MediaFoundation function + GetDeviceStreamCategory before getting a result different from + MF_E_INVALIDREQUEST or giving up. + + + + + guidou@chromium.org + armax@chromium.org + + Counts how many retries are needed for calls to MediaFoundation function + GetDeviceStreamCount before getting a result different from + MF_E_INVALIDREQUEST or giving up. + + + + + henryhsu@chromium.org + + Indicates whether we were successful in initializing hardware jpeg decoder + for attempts to VideoCaptureGpuJpegDecoder::Initialize(). + + + + + mcasas@chromium.org + Measures the time taken for VideoCaptureManager:: + + + + chfremer@chromium.org + mcasas@chromium.org + + Counts video capture event, such as start and stop capture. Note that the + ideal case is 50% start events and 50% normal stop events. + + + + + chfremer@chromium.org + + Measures the duration from the time the Browser connected to the video + capture service to the time it closed the connection. Entries are only + logged if the service was used for creating an actual capture session as + opposed to enumerating devices only. + + + + + chfremer@chromium.org + + Measures the duration from the time the Browser connected to the video + capture service to the time it closed the connection. Entries are only + logged if the service was used for enumerating devices only, but not for + creating an actual capture session. + + + + + chfremer@chromium.org + + Measures the duration from the time the Browser connected to the video + capture service to the time the connection was lost. + + + + + chfremer@chromium.org + + Measures the duration from the time the Browser last closed or lost + connection to the video capture service to the time it reconnects. This + duration only gets logged for reconnects after usage of the service for + capture (as opposed to enumeration-only usage). + + + + + chfremer@chromium.org + + Measures the duration from the time the Browser last closed or lost + connection to the video capture service to the time it reconnects. This + duration only gets logged for reconnects after enumeration-only usage of the + service. + + + + + chfremer@chromium.org + + Counts video capture service events, such as startup, shutdown, and + connection lost. + + + + + + + dalecurtis@chromium.org + Video codec used in HTML5 media. + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Whether Chrome had to fall back to a secondary video decoder after the + primary decoder failed reinitialization. + + + + + + + + + chcunningham@chromium.org + media-dev@chromium.org + + Indicates whether we were successful performing some database operation. See + suffix VideoDecodeStatsDBOperations. + + + + + + + + + chcunningham@chromium.org + media-dev@chromium.org + + Indicates duration of time performing some database operation. + + + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + Delay between a VideoFrame being decoded and it being consumed by the OS + presentation API (on ChromeOS, this includes the display controller too). + + + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + Delay between a VideoFrame being decoded and it being handed over to the + CompositorFrameSink, essentially capturing the buffering in the Renderer. + This value is strictly included in Media.VideoFrameSubmitter + + + + + xhwang@chromium.org + media-dev@chromium.org + + The height of the first video frame in an HTML5 video. Reported when the + first video frame is available. + + + + + mlamouri@google.com + peconn@chromium.org + media-dev@chromium.org + + Every time a video persistence session could be triggered, it records the + result of the attempt. + + + + + mlamouri@google.com + media-dev@chromium.org + + Record the type of controls a persisted video is using. This is recorded + every time a video enters persistence mode + + + + + mlamouri@google.com + peconn@chromium.org + media-dev@chromium.org + + Records the length during which a video was in a persistent state. It is + recorded once per video persistence session. + + + + + mlamouri@google.com + peconn@chromium.org + media-dev@chromium.org + + Records the reason why a video persistence session has ended. + + + + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Indicates how many cadence changes have occurred during playback, a zero + value is emitted at the beginning of playback. Subsequent values are emitted + during video rendering for each cadence change (up to a maximum of 10). + + + + + xhwang@chromium.org + media-dev@chromium.org + + Indicates whether video is rendering in low delay mode. It's recorded when a + video starts playing. + + + + + dalecurtis@chromium.org + Metadata rotation in mp4 videos. Emitted during demuxing. + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Whether capture started successfully after a high-latency input stream + startup was requested. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Whether a VTDecompressionSession is internally using hardware accelerated + decoding. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Count of VideoToolbox initialization failure reasons. Successful + initializations are counted as a special failure type. The sum of successes + and failures gives a lower bound on the number of attempted initializations. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Count of VTVDA session failure reasons. Successful initializations are + counted as a special failure type. Since only successfully initialized + session can fail, failures rates are computed as a simple ratio. + + + + + dalecurtis@chromium.org + + Watch time is defined as the amount of elapsed media time for audio+video + media aggregated per player instance. A minimum of 7 seconds of unmuted, + foreground media must be watched to start watch time monitoring. Watch time + is checked on a regular basis and reported to UMA upon one of the stop + events mentioned below or at player destruction if none occur prior. + + Any one of paused, hidden, or muted is sufficient to stop watch time metric + reports. Each of these has a hysteresis where if the state change is undone + within some time, the watch time will be counted as uninterrupted. + + Power events (on/off battery power) have a similar hysteresis, but unlike + the aforementioned properties, will not stop metric collection. + + Each seek event will result in a new watch time metric being started and the + old metric finalized as accurately as possible. + + + + + sandersd@chromium.org + tguilbert@chromium.org + + When an HLS manifest is found during loading (on Android only), and the + response is CORS cross-origin, this histogram records whether the response + included an Access-Control-Allow-Origin header. Such requests are likely to + be supported by fetch() if the mode is correctly configured. + + + + + sandersd@chromium.org + tguilbert@chromium.org + + When an HLS manifest is found during loading (on Android only), records + whether the request was CORS cross-origin. These are cases that could not be + implemented using fetch(). Note: subresources referenced by the manifest are + not considered; they may have different origins or CORS configurations. + + + + + sandersd@chromium.org + tguilbert@chromium.org + + When an HLS manifest is found during loading (on Android only), records + whether the request would be mixed content. These are cases that could not + be implemented using fetch(). Note: subresources referenced by the manifest + are not considered; they may have different origins. + + + + + sandersd@chromium.org + media-dev@chromium.org + + Wall time of WebMediaPlayer playbacks. Each count represents one second of + media playback. Multiple WebMediaPlayer instances can together accumulate + watch time faster than real time. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to pre-buffer A/V data before the actual playback for the + YouTube application. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to buffer A/V data after an underrun for the YouTube + application. + + + + + mcasas@chromium.org + chromeos-gfx@chromium.org + + Error codes reported by libva (via VaapiWrapper) while being used from the + specified client name. {VaapiClientName} + + + + + + + + + + + + + + + + + vandebo@chromium.org + If a media scan was cancelled, the duration (in ms) it ran. + + + + vandebo@chromium.org + + The number of directories with media files found during a scan. + + + + + vandebo@chromium.org + + Duration in milliseconds taken to do a media scan that ran to completion. + + + + + vandebo@chromium.org + + The percentage of galleries accepted (not deselected) from the scan result + dialog. + + + + + vandebo@chromium.org + + The number of galleries added or updated in preferences after a scan. + + + + + vandebo@chromium.org + Various usage counts for media galleries. + + + + steimel@chromium.org + media-dev@chromium.org + + True if the MediaLauncherActivity was successfully able to open the file. + Recorded when the MediaLauncherActivity starts the CustomTabActivity. + + + + + steimel@chromium.org + media-dev@chromium.org + + The type of media that a user is opening via the MediaLauncherActivity. + + + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + Round trip time for a Cast app availability request. Can be suffixed with + Success or Failure. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Whether opening Cast channel succeeds or not. Recorded when all opening + channel attempts (including retry attempts) finish. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Errors encountered on a Cast channel. Recorded when a Cast channel fails to + open, or when an opened channel fails to respond to keepalive ping request + and times out. + + + + + btolsch@chromium.org + openscreen-eng@google.com + + The number of Cast devices available from the device cache at the time of a + new network connection. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + The number of connected Cast devices. Recorded when browser finishes + discovering Cast devices. Recording happens roughly once per hour. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + The number of known Cast devices. Recorded when browser finishes discovering + Cast devices. Recording happens roughly once per hour. + + + + + btolsch@chromium.org + openscreen-eng@google.com + The source of discovery for a newly-created Cast sink. + + + + muyaoxu@google.com + openscreen-eng@google.com + + The types of apps supported by the sender page. Recorded when requesting the + receiver to launch a new session. + + + + + muyaoxu@google.com + openscreen-eng@google.com + + The type of app that the receiver device choose to launch. Recorded when + receiving a receiver status response to the launch request. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken to fail to open a cast channel. Recorded when + one opening channel attempt fails. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken to successfully open a cast channel. Recorded + when one opening channel attempt succeeds. + + + + + takumif@chromium.org + muyaoxu@google.com + openscreen-eng@google.com + + Records whether audio is played on the receiver device. If not, then on the + sender side. Recorded when a new site-initiated mirroring session is + started. + + + + + takumif@chromium.org + openscreen-eng@google.com + Total time to launch a Cast Streaming mirror session. + + + + takumif@chromium.org + openscreen-eng@google.com + + Total length of a Cast Streaming mirror session of any type, including the + time spent in media remoting. + + + + + rwkeane@google.com + openscreen-eng@google.com + Total length of a Cast Streaming File mirror session. + + + + rwkeane@google.com + openscreen-eng@google.com + + Total length of a Cast Streaming Offscreen Tab mirror session. + + + + + rwkeane@google.com + openscreen-eng@google.com + Total length of a Cast Streaming Screen mirror session. + + + + rwkeane@google.com + openscreen-eng@google.com + + Total length of a Cast Streaming mirror session of type Tab and NOT of types + offscreen tab or local file. This includes the time spent in media remoting. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Whenever a Cast Streaming session fails to start, record the error + associated with the event. This is recorded only for the extension Cast MRP. + See MediaRouter.CastStreaming.Start.Failure.Native for the native MRP. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Whenever a Cast Streaming session fails to start, record the error + associated with the event. This is recorded only for the native Cast MRP. + See MediaRouter.CastStreaming.Start.Failure for the extension MRP. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Whenever a Cast Streaming session is successfully started, record if it was + for a Tab or Desktop mirroring session. + + + + + rwkeane@chromium.org + openscreen-eng@google.com + + Whenever a resource is loaded from the Media Router Component Extension, + this metric gets logged. The value for this metric is always true. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The pref value to enable the cloud services. Recorded whenever the Cast + dialog is opened. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The pref value to enable the cloud services. Recorded whenever the browser + is initialized for a regular (not incognito or guest) profile. + + + + + mfoltz@chromium.org + takumif@chromium.org + openscreen-eng@google.com + + The number of available DIAL devices. Recorded when browser finishes + discovering DIAL devices. Recording happens roughly once per hour. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The result of a DIAL CreateRoute request. Recorded when the user requests to + create a media route to a DIAL device. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The result of a DIAL app info request. Recorded when an app info request is + issued to a DIAL device. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The number of known DIAL devices. Recorded when browser finishes discovering + DIAL devices. Recording happens roughly once per hour. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The result of parsing a Cast SDK message in the DIAL media route provider. + Recorded when the DIAL media route prover finishes parsing a Cast SDK + message sent from a Cast-enabled webpage. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + Error encountered while parsing DIAL device description XML text. Recorded + when utility process returns an invalid DIAL device description object to + browser. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The result of a DIAL TerminateRoute request. Recorded the user requests to + terminate a DIAL media route. + + + + + takumif@chromium.org + openscreen-eng@google.com + Location the user clicked to open the Media Router dialog. + + + + takumif@chromium.org + openscreen-eng@google.com + + Records errors encountered by the Mirroring Service. If an error occurs + while media remoting, the service attempts to revert to mirroring. Otherwise + mirroring is terminated. + + + + + btolsch@chromium.org + openscreen-eng@google.com + + Network connection type reported by DiscoveryNetworkMonitor whenever it + detects a change in the set of networks connected to the host device which + may affect local discovery. + + + + + btolsch@chromium.org + openscreen-eng@google.com + + Time between network change events reported by DiscoveryNetworkMonitor. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + The type of Presentation URL used in a PresentationRequest by a web page. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Logged when the Media Router starts a presentation according to the type of + presentation URL and the type of media sink. + + + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + Result of a request to a MediaRouteProvider to create a route. + CreateRoute.Result (without a suffix) is recorded for the extension or an + unknown MRP. + + + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + Result of a request to a MediaRouteProvider to join a route. + JoinRoute.Result (without a suffix) is recorded for the extension or an + unknown MRP. + + + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + + Result of a request to a MediaRouteProvider to terminate a route. + TerminateRoute.Result (without a suffix) is recorded for the extension or an + unknown MRP. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Records how the major version of the Media Router component extension + compares to the major version of the browser. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Reason that the Media Router woke the Media Route Provider event page. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Records the outcome of waking the Media Router component's event page. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The number of times a Media Router create route response succeeds or fails. + This breaks down the different failure types in to separate buckets. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The type of the Media Sink that media is being Cast to. Recorded each time + the user selects a Media Sink to start Casting. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The source of a Media Router session. This is recorded to keep track of what + kind of media is being streamed. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The file format of a local media Media Router session. This is recorded when + a casting session begins to keep track of what kind of media is being + streamed. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The file size of a local media Media Router session. This is recorded when a + casting session begins to keep track of what kind of media is being + streamed, specifically, whether it is a clip or a song, or a full length + film or podcast. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken from the user opening the Media Router dialog + to the user closing the dialog. This is only recorded if closing the dialog + is the first action the user takes. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken from the Media Router dialog showing the sink + list and being populated with at least one device to the user selecting a + device immediately after to create a new route. + + + + + takumif@chromium.org + openscreen-eng@google.com + The index of the sink that was selected in the sink list. + + + + takumif@chromium.org + openscreen-eng@google.com + + The number of times a session was successfully started versus failed. + + + + + takumif@chromium.org + openscreen-eng@google.com + The number of times a user stops different types of routes. + + + + takumif@chromium.org + openscreen-eng@google.com + + Counts the number of devices known and populated to the Media Router dialog + three seconds after the dialog loads. Always expected to be non-negative. + + + + + takumif@chromium.org + openscreen-eng@google.com + + This records how the Cast dialog was opened and what Cast mode was used + whenever a Cast session starts. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Whether the Cast toolbar icon is in its ephemeral state (shown only when the + feature is active), or is pinned to the toolbar by user pref / admin policy. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken from the user click to open the Media Router + dialog to initializing the dialog with data. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Duration in milliseconds taken from a user click to open the Media Router + dialog to the initial paint. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The first action taken by the user after opening the Media Router dialog. + + + + + takumif@chromium.org + openscreen-eng@google.com + + Whether the Cast toolbar icon is in its ephemeral state (shown only when the + feature is active), or is pinned to the toolbar by user pref / admin policy. + Recorded whenever the browser is initialized for a regular (not incognito or + guest) profile. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The number of times the user selects a specific cast source type. + + + + + takumif@chromium.org + openscreen-eng@google.com + + The number of Media Sinks available for Casting a Presentation API URL to + local screens. Recorded at most once an hour, when the Wired Display Media + Route Provider reports an update on the sink count. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/memory/histograms.xml b/tools/metrics/histograms/histograms_xml/memory/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..f294da49938f797badc9b39cabc5da47ebcb71bc --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/memory/histograms.xml @@ -0,0 +1,2280 @@ + + + + + + + + + + + + marinaciocea@chromium.org + maxmorin@chromium.org + olka@chromium.org + + A rough estimate of the private memory footprint of the audio service + process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + olka@chromium.org + guidou@chromium.org + + An amount of private memory of the audio service process placed in swap + (VmSwap). + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + fdoray@chromium.org + + The size of the resident memory in a audio service process. This is + influenced by factors we control (e.g. memory that is not accessed can be + swapped) and factors we don't control (e.g. an unrelated process using a lot + of memory can force memory in our process to be swapped). Recorded once on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + olka@chromium.org + guidou@chromium.org + + A rough estimate of the shared memory footprint of the audio service + process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + A rough estimate of the private memory footprint of the browser process + while an Android background task is running. Recorded once per background + task, with a random delay of 0s to 60s after it starts. Available only on + Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + An amount of private memory the browser process placed in swap (VmSwap) by + the browser process while an Android background task is running in Full + Browser Mode. Recorded once per background task, with a random delay of 0s + to 60s after it starts. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + The size of the resident memory in a browser process while an Android + background task is running. Recorded once per background task, with a random + delay of 0s to 60s after it starts. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + A rough estimate of the shared memory footprint of the browser process while + an Android background task is running. Recorded once per background task, + with a random delay of 0s to 60s after it starts. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + A rough estimate of the private memory footprint of the browser process + while the Android Offline Prefetch Android background task is running. + Recorded once per background task, with a random delay of 0s to 60s after it + starts. The same value is recorded into + Memory.BackgroundTask.Browser.PrivateMemoryFootprint, which aggregates all + task types. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + An amount of private memory the browser process placed in swap (VmSwap) by + the browser process while the Android Offline Prefetch Android background + task is running in Full Browser Mode. Recorded once per background task, + with a random delay of 0s to 60s after it starts. The same value is recorded + into Memory.BackgroundTask.Browser.PrivateSwapFootprint, which aggregates + all task types. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + The size of the resident memory in a browser process while the Android + Offline Prefetch Android background task is running. Recorded once per + background task, with a random delay of 0s to 60s after it starts. The same + value is recorded into Memory.BackgroundTask.Browser.ResidentSet, which + aggregates all task types. Available only on Android. + + + + + + + hanxi@chromium.org + hnakashima@chromium.org + + A rough estimate of the shared memory footprint of the browser process while + the Android Offline Prefetch background task is running. Recorded once per + background task, with a random delay of 0s to 60s after it starts. The same + value is recorded into Memory.BackgroundTask.Browser.SharedMemoryFootprint, + which aggregates all task types. Available only on Android. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + TBD. + + + + + + erikchen@chromium.org + chrome-analysis-team@google.com + + This metric is only recorded on iOS. This measures the sum of + PrivateMemoryFootprint and SharedMemoryFootprint, which is possible because + iOS is single-process. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint + but only recorded when UIApplication.sharedApplication.applicationState is + UIApplicationStateActive. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This metric is only recorded on iOS when + UIApplication.sharedApplication.applicationState is + UIApplicationStateActive. True if the sum of PrivateMemoryFootprint and + SharedMemoryFootprint is greater than 200MB. According to Apple, apps on + iPhone 6 and older devices get terminated by the OS if memory usage crosses + 200MB watermark, so it's important to keep the memory usage under 200MB. + "true" value may not show up on iPhone 6 and older devices if iOS + is strict about the advertised watermark. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint + but only recorded when UIApplication.sharedApplication.applicationState is + UIApplicationStateBackground. According to Apple, apps get terminated by the + OS if memory usage in background crosses 50MB watermark, so it's important + to keep the memory usage under 50MB. The timing of this metric will line up + so that it rarely occurs when the app is in the background. With a small + data set, the metrics might be biased in ways that we can't think of right + now. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint + but only recorded when UIApplication.sharedApplication.applicationState is + UIApplicationStateInactive. The timing of this metric will line up so that + it rarely occurs when the app is inactive. With a small data set, the + metrics might be biased in ways that we can't think of right now. + + + + + rkgibson@google.com + eugenebut@chromium.org + + Investigation into crbug.com/1102494 shows that OverscrollActionsController + is allocating thousands of objects in it's -initWithScrollView:. This is + likely because thousands of OverscrollActionsControllers are being + initialized. The theory is that there are users that have many many tabs, + causing many OverscrollActionsControllers to be allocated. This histogram + tests that theory by logging how many live OverscrollActionsControllers + there are. This is recorded every time histograms are uploaded. + + + + + rkgibson@google.com + eugenebut@chromium.org + + Investigation into crbug.com/1102494 shows that OverscrollActionsController + is allocating thousands of objects in it's -initWithScrollView:. This is + likely because thousands of OverscrollActionsControllers are being + initialized. The theory is that there are users that have many many tabs, + causing many OverscrollActionsControllers to be allocated. This histogram + tests that theory by logging how many open tabs there are. This is recorded + every time histograms are uploaded. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + This metric is only recorded on iOS. Same as Memory.Browser.MemoryFootprint + but recorded right after the app transitions into background. According to + Apple, apps get terminated by the OS if memory usage in background crosses + 50MiB watermark so it's important to keep the memory usage under 50MiB. + + + + + + + erikchen@chromium.org + chrome-analysis-team@google.com + + A rough estimate of the private memory footprint of the browser process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + erikchen@chromium.org + ssid@chromium.org + + An amount of private memory of the browser process placed in swap (VmSwap). + Available on Android, Linux and ChromeOS. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + fdoray@chromium.org + + The size of the resident memory in the browser process. This is influenced + by factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + erikchen@chromium.org + + A rough estimate of the shared memory footprint of the browser process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + TBD. + + + + thiabaud@google.com + lizeb@chromium.org + + Freelist size used by ClientDiscardableMemoryManager in the foreground only. + Recorded during |OnMemoryDump|. + + + + + thiabaud@google.com + lizeb@chromium.org + + Boolean metric which tracks whether or not discardable memory had already + been discarded when an attempt is made to lock it. + + + + + thiabaud@google.com + lizeb@chromium.org + + Effective memory used by ClientDiscardableMemoryManager in the foreground + only. Recorded during |OnMemoryDump|. + + + + + thiabaud@google.com + lizeb@chromium.org + + Virtual memory used by ClientDiscardableMemoryManager in the foreground + only. Recorded during |OnMemoryDump|. + + + + + reveman@chromium.org + thiabaud@google.com + + The discardable memory allocation size in KB. Recorded each time a new + discardable memory instance is created. + + + + + ericrk@chromium.org + + The size of the EGL_ANDROID_blob_cache cache file on disk. Recorded once per + Chrome launch, after the first page has loaded. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The browser process's memory usage reported by the memory instrumentation + service in MB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The browser process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The browser process's memory usage reported by the memory instrumentation + service in KB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The browser process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + ssid@chromium.org + erikchen@chromium.org + + Records how many failed process dumps there were for a given global dump + completed by the memory instrumentation service + (resource_coordinator/memory_instrumentation/coordinator_impl.h). This is + recorded once each time a global dump request is completed. + + + + + ssid@chromium.org + erikchen@chromium.org + + Records how long it took the memory instrumentation service + (resource_coordinator/memory_instrumentation/coordinator_impl.h) from + starting working on a global memory dump request until complating that + request. This does not include queuing time (requests are handled serially). + This is recorded once each time a request is completed. + + + + + ssid@chromium.org + erikchen@chromium.org + + Number of global memory dump requests queued in by the memory + instrumentation service + (resource_coordinator/memory_instrumentation/coordinator_impl.h). This + includes the request currently being worked on if any. This is recorded once + each time a new request is queued. This happens at least once per UMA ping + to in order to compute Memory.Experimental.Renderer2, + Memory.Experimental.Browser2 etc. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The extension process's memory usage reported by the memory instrumentation + service in MB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The extension process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The extension process's memory usage reported by the memory instrumentation + service in KB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The extension process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + erikchen@chromium.org + + The physical footprint of the GPU process on macOS. Other measurements fail + to correctly account for OpenGL memory usage. This metric also has flaws and + is not intended for permanent use. It's an emergency measure added to help + debug https://crbug.com/713854. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The gpu process's memory usage reported by the memory instrumentation + service in MB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The gpu process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The gpu process's memory usage reported by the memory instrumentation + service in KB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The gpu process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The time taken by the call to the various memory pressure handlers in + GpuChannelManager::HandleMemoryPressure. + + + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The network service process's memory usage reported by the memory + instrumentation service in MiB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The network service process's memory usage reported by the memory + instrumentation service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The network service process's memory usage reported by the memory + instrumentation service in KiB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The network service process's memory usage reported by the memory + instrumentation service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of blink usage after 10 seconds of intervention. This reports + positive numbers when reduced. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of blink usage after 20 seconds of intervention. This reports + positive numbers when reduced. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of blink usage after 30 seconds of intervention. This reports + positive numbers when reduced. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of renderer pmf after 10 seconds of intervention. This + reports positive numbers when reduced. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of renderer pmf after 20 seconds of intervention. This + reports positive numbers when reduced. + + + + + yuzus@chromium.org + keishi@chromium.org + + Reduced amount of renderer pmf after 30 seconds of intervention. This + reports positive numbers when reduced. + + + + + yuzus@chromium.org + + The renderer process's memory usage reported every second when OOM + intervention is enabled. + + + + + ssid@chromium.org + + The renderer process' Blink memory usage, as sum of V8, PartitionAlloc and + BlinkGC allocations, when a foreground OOM occurs. This was last recorded + metric by renderer a few seconds before getting killed. + + + + + yuzus@chromium.org + + The renderer process's PMF size reported every second when OOM intervention + is enabled. + + + + + ssid@chromium.org + bashi@chromium.org + + The renderer process' private memory footprint when a foreground OOM occurs. + This was last recorded metric by renderer a few seconds before getting + killed. + + + + + yuzus@chromium.org + + The renderer process's swap size reported every second when OOM intervention + is enabled. + + + + + ssid@chromium.org + bashi@chromium.org + + The renderer process' swap size when a foreground OOM occurs. This was last + recorded metric by renderer a few seconds before getting killed. + + + + + yuzus@chromium.org + keishi@chromium.org + + Records the time since last main frame navigation start on the renderer + process when high memory usage is detected. Record only when navigation + happened at least once. + + + + + ssid@chromium.org + haraken@chromium.org + + Records the time since last main frame navigation start on the renderer + process when it OOMs in foreground visible state. Record 0 if no navigation + was started. + + + + + yuzus@chromium.org + keishi@chromium.org + + Records the time since starting monitor on renderer when high memory usage + is detected. + + + + + yuzus@chromium.org + + The renderer process's virtual memory usage reported every second when OOM + intervention is enabled. + + + + + ssid@chromium.org + bashi@chromium.org + + The renderer process' virtual memory usage, when a foreground OOM occurs. + This was last recorded metric by renderer a few seconds before getting + killed. + + + + + keishi@chromium.org + yuzus@chromium.org + V8 memory usage 10 seconds after intervention. + + + + keishi@chromium.org + yuzus@chromium.org + V8 memory usage 20 seconds after intervention. + + + + keishi@chromium.org + yuzus@chromium.org + V8 memory usage 30 seconds after intervention. + + + + keishi@chromium.org + yuzus@chromium.org + V8 memory usage right before intervention. + + + + + + keishi@chromium.org + + The renderer process's memory usage at the specific timing, i.e. after a + page load and 5/10/15minutes after backgrounded. + + + + + tasak@google.com + bartekn@google.com + + The highest private memory footprint of a renderer process in (X mins after + the first page navigation, Y mins after the first page navigation]. (X, Y] + is (0, 2], (2, 4], (4, 8], and (8, 16]. The metric is recorded at the Y's + timing. + + + + + keishi@chromium.org + + The number of loads in a main frame during the lifetime of a render process + (excludes extensions). Emitted when the processes quits. + + + + + tasak@google.com + bartekn@google.com + + The peak RSS size(VmHMW) of a render process when the highest private memory + footprint is observed after the first navigation start. + + + + + keishi@chromium.org + + The uptime of a render process in time ticks (excludes extensions). Emitted + when the processes quits. + + + + + tasak@google.com + bartekn@google.com + + The number of webpages when the highest private memory footprint of renderer + process is observed after the first navigation start. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The renderer process's memory usage reported by the memory instrumentation + service in MB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The renderer process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The renderer process's memory usage reported by the memory instrumentation + service in KB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The renderer process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + sebmarchand@chromium.org + + The swap thrashing level, which is recorded periodically. This shows the + cumulative number of seconds that systems spend in each of the swap + thrashing states. Only available on Windows. + + + + + sebmarchand@chromium.org + + The number of swap-thrashing level state changes for each possible pairwise + state change. Only available on Windows. + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the private memory footprint of all processes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + keishi@chromium.org + tasak@chromium.org + + The renderer process' private memory footprint 10 seconds after a memory + pressure signal is generated. + + + + + keishi@chromium.org + tasak@chromium.org + + The renderer process' private memory footprint right before a memory + pressure signal is generated. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The utility process's memory usage reported by the memory instrumentation + service in MB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The utility process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + The utility process's memory usage reported by the memory instrumentation + service in KB. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The utility process's memory usage reported by the memory instrumentation + service in bytes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the private memory footprint of the extension process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + fdoray@chromium.org + + The size of the resident memory in an extension process. This is influenced + by factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of the extension process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The number of glyph pages present in the renderer when it commits a load. + Since this is per-sub-process, you can get the average number of glyph pages + in the system by multiplying this number with the average number of + renderers. Note that this typically won't count the glyph pages added as a + result of the load that just committed, since layout will happen after the + commit. There are 512 bytes per glyph page, but this number also very + closely approximates the number of glyph width map pages in the same + renderer. The only difference is that if you have font fallback, it will + make a new glyph page and no width page, but in most common cases there is + no fallback). Width pages are 1K each (256 floats), so you could think of + this value as being the number of "1.5K units related to glyphs per + renderer per page load". + + + + + + + + + + + jonross@chromium.org + graphics-dev@chromium.org + sadrul@chromium.org + + The maximum amount of memory of the GPU process allocated by a particular + source during a user interaction (e.g. tab-switch, page-load, scroll etc.). + See Memory.GPU.PeakMemoryUsage. + + + + + + + jonross@chromium.org + sadrul@chromium.org + graphics-dev@chromium.org + + The maximum amount of memory of the GPU process during a particular + interaction (e.g. tab-switch, page-load, scroll etc.). + + + + + + + erikchen@chromium.org + ssid@chromium.org + chrome-analysis-team@google.com + + A rough estimate of the private memory footprint of the gpu process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + erikchen@chromium.org + ssid@chromium.org + + An amount of private memory of the GPU process placed in swap (VmSwap). + Available on Android, Linux and ChromeOS. + + + + + + + fdoray@chromium.org + + The size of the resident memory in the GPU process. This is influenced by + factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of the gpu process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + hajimehoshi@chromium.org + erikchen@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + System-wide graphics driver memory consumption. Recorded on Chrome OS for + platforms where it is exposed by the kernel (for example, Intel i915 and + Exynos Mali). Recorded once per UMA ping. + + + + + alph@chromium.org + erikchen@chromium.org + + Browser process memory allocated with malloc when UMA heap profile is taken. + + + + + msalama@google.com + lizeb@chromium.org + + The size of the resident memory for the native library code across all + processes. This metric is computed by parsing proc/self/pagemap and counting + native library pages that are mapped and present in RAM for at least one + Chrome process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + lizeb@chromium.org + pasko@chromium.org + + Result of an attempt to read /proc/self/pagemap when determining the amount + of resident memory mapped by the current process. Reading the file is + performed as part of computing the + Memory.NativeLibrary.MappedAndResidentMemoryFootprint2 histogram. Available + only on Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + lizeb@chromium.org + + The size of the native library code which was ordered, yet is not resident + in memory, across all processes. This metric is computed by parsing + proc/self/pagemap and counting native library pages that are mapped and + present in RAM for at least one Chrome process. Available only on Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + lizeb@chromium.org + + The size of the native library code which is outside the ordered section, + yet is resident in memory, across all processes. This metric is computed by + parsing proc/self/pagemap and counting native library pages that are mapped + and present in RAM for at least one Chrome process. Available only on + Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the private memory footprint of the network service + process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + An amount of private memory of the network service process placed in swap + (VmSwap). Available on Android, Linux and ChromeOS. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Note: Histogram data may be missing for mid-2020 due to expiry. + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + The size of the resident memory in a network service process. This is + influenced by factors we control (e.g. memory that is not accessed can be + swapped) and factors we don't control (e.g. an unrelated process using a lot + of memory can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + mmenke@chromium.org + morlovich@chromium.org + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of the network service + process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Note: Histogram data may be missing for mid-2020 due to expiry. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide memory allocation right after a renderer was killed by + oom-killer, roughly equivalent to the sum of memory allocated with malloc() + in userspace plus graphics driver memory. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide file-backed memory plus free memory right after a renderer was + killed by oom-killer, which should be smaller than or close to what the + kernel uses to trigger low-memory notifications for tab discards. If this is + higher than the kernel's threshold for tab discards, renderers may be killed + due to reasons other than out-of-memory. + + + + + oshima@chromium.org + alemate@chromium.org + + Graphics driver (GEM object) memory right after a renderer was killed by + oom-killer. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide shared memory right after a renderer was killed by oom-killer. + Used primarily for shared buffers in the graphics system. Tracked because + it's a historical source of leaks on Chrome OS. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide memory allocation right after a renderer was killed by + oom-killer, roughly equivalent to the sum of memory allocated with malloc() + in userspace plus graphics driver memory. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide file-backed memory plus free memory right after a renderer was + killed by oom-killer, which should be smaller than or close to what the + kernel uses to trigger low-memory notifications for tab discards. If this is + higher than the kernel's threshold for tab discards, renderers may be killed + due to reasons other than out-of-memory. + + + + + oshima@chromium.org + alemate@chromium.org + + Graphics driver (GEM object) memory right after a renderer was killed by + oom-killer. + + + + + oshima@chromium.org + alemate@chromium.org + + System-wide shared memory right after a renderer was killed by oom-killer. + Used primarily for shared buffers in the graphics system. Tracked because + it's a historical source of leaks on Chrome OS. + + + + + + + dcastagna@chromium.org + ssid@chromium.org + + The total number of open file descriptors opened per process. Recorded once + per UMA ping. + + + + + + + dcastagna@chromium.org + ssid@chromium.org + + The limit of open file descriptors that can be opened per process. Recorded + once per UMA ping. + + + + + lizeb@chromium.org + + Total size of compressed ParkableStrings, in KB. Recorded at the same time + as "Memory.ParkableString.TotalSizeKb". + + + + + lizeb@chromium.org + + Time to compress a ParkableString, in us. Note: This metric drops reports on + clients with low-resolution clocks, which means these reports will be biased + against a portion of the population on Windows. See + Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + lizeb@chromium.org + + Size of a compressed ParkableString, recorded at compression time. + + + + + lizeb@chromium.org + + Size of a compressed ParkableString, recorded at compression time. + + + + + lizeb@chromium.org + pasko@chromium.org + + Average compression ratio, 100 * compressed_size / initial_size, for all + compressed ParkableStrings. Recorded at the same time as + "Memory.ParkableString.TotalSizeKb.5min". + + + + + lizeb@chromium.org + + Time to decompress a ParkableString, in us. Note: This metric drops reports + on clients with low-resolution clocks, which means these reports will be + biased against a portion of the population on Windows. See + Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + lizeb@chromium.org + + Original size of a compressed ParkableString, recorded at decompression + time. + + + + + lizeb@chromium.org + + Original size of a compressed ParkableString, recorded at decompression + time. + + + + + lizeb@chromium.org + pasko@chromium.org + + Whether the disk allocator is usable. Recorded at the same time as + "Memory.ParkableString.TotalSizeKb.5min". The disk may not be + usable for several reasons, including the profile being an Incognito one, + permssions error, or disk write error. + + + + + lizeb@chromium.org + pasko@chromium.org + + Total main thread time used by ParkableStrings for reading over the first 5 + minutes of a renderer lifetime. Starting time is from the first + ParkableString being added. + + + + + lizeb@chromium.org + pasko@chromium.org + + Total time used by ParkableStrings for writing to disk over the first 5 + minutes of a renderer lifetime. Starting time is from the first + ParkableString being added. + + + + + lizeb@chromium.org + pasko@chromium.org + + Total main thread time used by ParkableStrings over the first 5 minutes of a + renderer lifetime. Starting time is from the first ParkableString being + added. + + + + + lizeb@chromium.org + pasko@chromium.org + + Sum of memory saved by compression and disk discarding, in KB. Recorded at + the same time as "Memory.ParkableString.TotalSizeKb.5min", when + disk discarding is enabled. + + + + + lizeb@chromium.org + pasko@chromium.org + + Total disk footprint used by ParkableStrings including allocator waste, in + KB. Recorded once, 5 minutes after the first ParkableString is added to a + renderer, at the same time as + "Memory.ParkableString.MemorySavings.5min". + + + + + lizeb@chromium.org + pasko@chromium.org + + Total size of ParkableStrings discarded to disk, excluding allocator waste, + in KB. Recorded once, 5 minutes after the first ParkableString is added to a + renderer, at the same time as + "Memory.ParkableString.MemorySavings.5min". + + + + + lizeb@chromium.org + pasko@chromium.org + + Total thread time used by ParkableStrings for parking over the first 5 + minutes of a renderer lifetime. Starting time is from the first + ParkableString being added. + + + + + lizeb@chromium.org + pasko@chromium.org + + Time to read a ParkableString from disk, in us. Note: This metric drops + reports on clients with low-resolution clocks, which means these reports + will be biased against a portion of the population on Windows. See + Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + lizeb@chromium.org + pasko@chromium.org + Size read from disk for a ParkableString. + + + + lizeb@chromium.org + pasko@chromium.org + Read throughput from disk for a ParkableString. + + + + lizeb@chromium.org + pasko@chromium.org + + Sum of memory saved by compression, in KB. Recorded at the same time as + "Memory.ParkableString.TotalSizeKb". + + + + + lizeb@chromium.org + pasko@chromium.org + + Sum of memory saved by compression, in KB. Recorded at the same time as + "Memory.ParkableString.TotalSizeKb.5min". + + + + + lizeb@chromium.org + pasko@chromium.org + + Total size of ParkableStrings assuming no compression, in KB. Recorded once, + 5 minutes after the first ParkableString is added to a renderer, at the same + time as "Memory.ParkableString.MainThreadTime.5min". + + + + + lizeb@chromium.org + pasko@chromium.org + + Time to write a ParkableString to disk, in us. Note: This metric drops + reports on clients with low-resolution clocks, which means these reports + will be biased against a portion of the population on Windows. See + Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + lizeb@chromium.org + pasko@chromium.org + Size of an on-disk ParkableString, recorded at write time. + + + + lizeb@chromium.org + pasko@chromium.org + Throughput of a ParkableString disk write. + + + + chrisha@chromium.org + + The memory pressure level, which is recorded periodically. This shows the + cumulative number of seconds that systems spend in each of the memory + pressure states. + + + + + chrisha@chromium.org + + The number of pressure level state changes for each possible pairwise state + change. + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The time spent in each of the memory pressure state. Recorded when + transitioning from a memory pressure state to the other and when exiting + memory pressure. + + + + + creis@chromium.org + nasko@chromium.org + + The count of all active processes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + pasko@chromium.org + leszeks@chromium.org + + The state of CachedMetadata on every attempt to use it for a script + resource. Used for experiment in http://crbug.com/1045052. + + + + + hajimehoshi@chromium.org + + The esitimated memory size which would be reduced when reusing disk cache is + implemented. If it is 100% sure that the encoded data is in disk cache, the + same data in memory can be dropped to reduce memory usage. This is rencorded + when an ImageResource is pruned. See crbug/664437. + + + + + + + erikchen@chromium.org + ssid@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + A rough estimate of the private memory footprint of the renderer process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + + + + + + fdoray@chromium.org + + The size of the resident memory in a renderer process. This is influenced by + factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of the renderer process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + creis@chromium.org + nasko@chromium.org + + The count of active renderer processes. Excludes renderers hosting + chrome-extension:// and/or chrome:// URLs. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Computed based on OS data. + + WARNINGS: Not reliable on Android, see https://crbug.com/875400. Ignores + processes that do not host a widget, see https://crbug.com/949977#c36. + Consider using Memory.RenderProcessHost.Count.* instead. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + nasko@chromium.org + + The count of all renderer processes. Covers all renderer processes, + including ones hosting web content (i.e. http(s):// and/or file://), + extensions (i.e. chrome-extension://) and WebUI (i.e. chrome://). + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Computed based on count of RenderProcessHost objects, even if 1) they have + not been launched yet (e.g. during session restore) or 2) they are dead + (e.g. killed by the browser process or the OS). + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + nasko@chromium.org + + The count of active renderer processes. Recorded once per UMA ping. Covers + all renderer processes, including ones hosting web content (i.e. http(s):// + and/or file://), extensions (i.e. chrome-extension://) and WebUI (i.e. + chrome://). + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Computed based on count of RenderProcessHost objects that are + IsInitializedAndNotDead (i.e. have been launched and not terminated yet). + + + + + reveman@chromium.org + + The amount of free space in temporary directory for shared memory files. + Recorded each time a new discardable memory manager instance is created. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each worker process. Each worker process provides one + sample. Recorded once per process per UMA ping if the system has swapped. + + + + + + + erikchen@chromium.org + ssid@chromium.org + chrome-analysis-team@google.com + + A rough estimate of the private memory footprint of all processes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + tommckee@chromium.org + + A rough estimate of the private memory footprint of all renderer processes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + + + fdoray@chromium.org + + The size of the resident memory in all processes. This is influenced by + factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Note: This metric is a simple sum of the resident set of all processes and + this cause some double accounting for the shared portion of the working set. + As a result this metric doesn't give an exact representation of how much + physical memory is used by Chrome. + + + + + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of all processes. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + sadrul@chromium.org + zmo@chromium.org + + Records the system commit limit (number of total pages) x page size, + collected in the info collection GPU process, once per UMA ping. This is + Windows platform only. + + + + + + + jam@chromium.org + + A rough estimate of the private memory footprint of the utility process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + jam@chromium.org + + An amount of private memory of the utility process placed in swap (VmSwap). + Available on Android, Linux and ChromeOS. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Note: Histogram data may be missing for mid-2020 due to expiry. + + + + + + + fdoray@chromium.org + + The size of the resident memory in a utility process. This is influenced by + factors we control (e.g. memory that is not accessed can be swapped) and + factors we don't control (e.g. an unrelated process using a lot of memory + can force memory in our process to be swapped). Recorded on + Windows/Linux/ChromeOS/Android. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + + + + jam@chromium.org + erikchen@chromium.org + ssid@chromium.org + + A rough estimate of the shared memory footprint of the utility process. + + Recorded at Poisson sampled time intervals with a mean of 5 minutes on + Android and 30 minutes on other platforms. + + Note: Histogram data may be missing between M77 to M87 due to expiry. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each worker process. Each worker process + provides one sample. Recorded once per process per UMA ping. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Value of getMemoryClass() recorded once upon startup. This is an integer, + device-specific constant correlated with the amount of memory available on + Android device. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Reasons behind evictions of individual tabs, recorded upon each tab + eviction. + + + + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Number of loaded (memory-resident) tabs when LowMemory notification is + delivered. + + + + + ssid@chromium.org + + Whether Chrome is running in low ram mode. This histogram is reported on + every upload by Android devices. A device is considered low-RAM if it has + 512MiB of RAM or lower (see SysUtils.detectLowEndDevice()). + + Note: The low-RAM determination has changed in M-49, it used to be given + directly by the Android OS. + + + + + marq@chromium.org + + The number of memory warnings during a given foreground session. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/mobile/histograms.xml b/tools/metrics/histograms/histograms_xml/mobile/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9a9b520d5f6d4aa04d0eb3f49800d153d3c822f4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/mobile/histograms.xml @@ -0,0 +1,1118 @@ + + + + + + + + + + + + + + + gangwu@chromium.org + twellington@chromium.org + + The time it takes for the user to abandon the app menu after it's shown by + pressing back or touching outside the menu. This is only logged if the menu + is abandoned. See Mobile.AppMenu.TimeToTakeAction.SelectedItem for the cases + where it is closed as a result of user interaction with the menu. Android + only. + + + + + gangwu@chromium.org + twellington@chromium.org + + The time it takes for the user to select an item. This is only logged if the + menu is closed as a result of the user clicking a menu item. See + Mobile.AppMenu.TimeToTakeAction.Abandoned for the cases where it is + abandoned by the user. Android only. + + + + + pkl@chromium.org + tedchoc@chromium.org + + The result of the operation to retrieve the page's canonical URL. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Bookmark + entries. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Bookmark + folders. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which context menu was shown. To drill down into a specific context + menu's usage, take a look at its actions' histogram (the format for actions + histograms is Mobile.ContextMenu.*.Actions). Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for History + entries. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Most Visited + entries. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Reading List + entries. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Recent Tabs + entries. To view how often this context menu was shown, take a look at this + other histogram: Mobile.ContextMenu.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + gambard@chromium.org + + Tracks which action was selected in the context menu shown for Recent Tabs + headers/devices. To view how often this context menu was shown, take a look + at this other histogram: Mobile.ContextMenu.EntryPoints. Currently only on + iOS. + + + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + Android: The number of browsers installed on the device. Logged when a new + session is started. + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + Android: Whether or not the device has a default browser and whether or not + it is a system installed browser. Logged when a new session is started. + + + + + + + + + dtrainor@chromium.org + nyquist@chromium.org + + Android: The number of system installed browsers. Logged when a new session + is started. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the time between tapping the target and source language in a legacy + infobar. If only one of either is tapped, nothing is logged. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the time an unused legacy infobar persists on screen. This is logged + when the infobar is closed. + + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records the state of a badge when it was tapped. + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records the reason why a Banner was dismissed. + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records Infobar Banner events. + + + + sczs@chromium.org + thegreenfrog@google.com + + Records the time an Infobar (Messages) Banner is visible on screen. Used to + know how long it takes a user to act on the banner before it gets + auto-dismissed. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Tracks the number of multiple Infobars being presented at the same time. + This will be recorded everytime an Infobar is presented. + + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the time between the Infobar Delegate is created, and the user + accepts a Confirm Infobar action. + + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the events related to Confirm Infobars (e.g. Presented, Accepted, + Dismissed,etc.) + + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records generic Infobar Modal events. + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records a tap on an Infobar overflow menu row. + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records the reason why a Password Modal was dismissed. + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records Password specific Infobar Modal events. + + + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records the context when a Password Modal was presented. + + + + sczs@chromium.org + thegreenfrog@chromium.org + Records Save Card specific Infobar Modal events. + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the context when an iOS user taps on a Translate Banner Action + Button. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records when an iOS user initiates an Translate specific Infobar Modal + event. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records the context when an iOS user initiates a Translate Modal + presentation. + + + + + sczs@chromium.org + edchin@chromium.org + + Records the total number of tabs opened when Open all was selected from + other devices in Recent Tabs. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for a bookmark entry. To view how often this sharing scenario was triggered, + take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks which sharing entry point was triggered. To view the outcome of these + sharing scenarios, take a look at their actions' histogram (the format is + Mobile.Share.*.Actions). Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for a history entry. To view how often this sharing scenario was triggered, + take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for a most visited tile. To view how often this sharing scenario was + triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for the generated QR code image. To view how often this sharing scenario was + triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for a reading list entry. To view how often this sharing scenario was + triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + for a recent tab entry. To view how often this sharing scenario was + triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + seblalancette@chromium.org + chrome-sharing-core@google.com + + Tracks the sharing actions executed when the sharing scenario was initiated + from the tab's share button. To view how often this sharing scenario was + triggered, take a look at: Mobile.Share.EntryPoints. Currently only on iOS. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records which Android notifications users interact with. Recorded when an + user taps the button in a notification, for any Chrome-generated + notification on Android that includes a button tap-target. + + + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records the duration in minutes from the time when the system notification + is shown to the time that the user clicked on an action button on the + Android notification. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Android: Represents the number of system notifications that were blocked and + could not be shown by type. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Android: Represents the type of notification that was last shown before the + user disabled notification permissions on Chrome. This is only logged the + first time we attempt to show a notification and fail. + + + + + + + peter@chromium.org + xingliu@chromium.org + + Android: Represents the number of system notifications by type that we + attempted to show but were blocked, due to their notification channel being + blocked. Only applies to devices on Android O and above. + + + + + + + xingliu@chromium.org + chrome-analysis-team@google.com + + Records the type of notification when the user clicks the body of Android + notification. This does not include clicks on notification action buttons. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records the duration in minutes from the time when the system notification + is shown to the time that the user clicked the notification on Android. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records the type of notification when the user dismisses the Android + notification. + + + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records the duration in minutes from the time when the system notification + is shown to the time that the user dismissed the notification on Android. + + + + + knollr@chromium.org + xingliu@chromium.org + + Android: Represents the number of system notifications failed to be notified + by Android NotificationManager API. Recorded when the notification is shown + on Android. + + + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Android: Represents the number of system notifications that will be + successfully shown to the user by type. + + + + + sczs@chromium.org + thegreenfrog@chromium.org + + Records a histogram for an infobar (both legacy and Messages) that the user + did not interact with throughout its lifetime. + + + + + hnakashima@chromium.org + hanxi@chromium.org + yfriedman@chromium.org + + Android: Records events for downloads started from the background, that is, + while the browser process is not running. Used to measure completion rate of + these downloads. + + + + + qinmin@chromium.org + xingliu@chromium.org + + Android: Records the target determination result for downloads started in + the background, that is, while the browser process is not running. + + + + + qinmin@chromium.org + + Android: Records various counts related to the save image context menu + option. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Android: Records whether download later dialog will be shown to the user. + Recorded when the download later preference is initialized in native. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Android: Records whether download dialog will be shown to the user. Recorded + when the download preference is initialized in native. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records the directory type when the user selects the download directory + through download location dialog. May be recorded even when the user didn't + download anything. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records whether the user accepted or dismissed the dialog to select a + download location. + + + + + xingliu@chromium.org + clank-downloads@google.com + + Records the download location dialog type when the dialog is shown to the + user. + + + + + xingliu@chromium.org + dtrainor@chromium.org + qinmin@chromium.org + + Records the directory type shown when a user opens download location dialog + or download location setting. This is recorded when the directory provider + generates a list of available directories. + + + + + xingliu@chromium.org + clank-downloads@google.com + Records the directory type when download is completed. + + + + xingliu@chromium.org + clank-downloads@google.com + + Records the directory type when the user selects the download directory + through download preference. May be recorded even when the user didn't + download anything. + + + + + qinmin@chromium.org + + Android: Records the number of resumptions for a download by resumption + type. For all resumption types, this is recorded when a download is + finished, completed or cancelled. For automatic resumptions, it is also + recorded when user manually resumes the download to clear the auto retry + count. + + + + + qinmin@chromium.org + + Android: Records various counts when requesting the storage permission. + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: Records the time it takes from object initialization to the + enterprise policy check completing. This check is often skipped when its + result becomes irrelevant. Histogram has suffixes depending if the timing + was faster or slower than inflation. + + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: Records the time it takes from object initialization to the device + ownership check completing. Histogram has suffixes depending if the timing + was faster or slower than inflation. + + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: Records how long it takes to load the enterprise CCT/ToS fragment. + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: The amount of time spent fetching child account status during the + FRE. Not applicable for light weight FRE. + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: Enterprise FRE cannot fully show the first page until the + appRestrictions call returns. This suffixed histogram measures when fragment + inflation was slower or faster than the appRestrictions call, and wether the + UI had to wait. Note this is recorded for all clients, not just enterprise. + Not applicable for light weight FRE. + + + + + skym@chromium.org + wenyufu@chromium.org + + Android: This suffixed histogram represents the amount of time from when the + FRE intent was initially constructed, until some event in the future occurs. + Not applicable for light weight FRE. + + + + + bsazonov@chromium.org + msarda@chromium.org + droger@chromium.org + gogerald@chromium.org + chrome-signin-team@google.com + + Android: Records which states of the "first run experience" have + been reached. Each bucket represents a state and recorded everytime the + state changed. Pages can be double counted if the user goes backwards in the + flow. + + + + + aruslan@chromium.org + + Android: How the user left the sign-in part of the "first run + experience" activity (M-38+). + + + + + qinmin@chromium.org + + Android: Records the duration that a fullscreen video is played after device + rotates from portrait to landscape mode for the first time, and before it + exits fullscreen. If there is no device rotation or if the video starts with + landscape mode, it is not recorded. If there are mutiple rotations between + portrait and landscape mode, only one record is emitted and it is equal to + the time period from the first rotation to the moment when the video exits + fullscreen. + + + + + qinmin@chromium.org + + Android: Records the duration that a fullscreen video is played in landscape + mode. If a video starts playing in landscape mode, and then it is switched + back and forth between landscape and portrait mode, only the time period + before the first switch is accounted. If a video starts playing in portrait + mode, it is not recorded. + + + + + qinmin@chromium.org + + Android: Records whether a fullscreen video is switched from landscape to + portrait mode at any point during playback. + + + + + qinmin@chromium.org + + Android: Records the device orientation when a video enters fullscreen. The + value is true if device orientation is portrait, or false otherwise. The + video doesn't necessarily needs to be in a playing state. + + + + + qinmin@chromium.org + + Android: Records the duration that a fullscreen video is played in portrait + mode. If a video starts playing in portrait mode, and then it is switched + back and forth between landscape and portrait mode, only the time period + before the first switch is accounted. If a video starts playing in landscape + mode, it is not recorded. + + + + + qinmin@chromium.org + + Android: Records whether a fullscreen video is switched from portrait to + landscape mode at any point during playback. + + + + + qinmin@chromium.org + + Android: Records whether a video has a larger height than width when it + enters the fullscreen mode. + + + + + peconn@chromium.org + peter@chromium.org + + Recorded when Chrome on Android is launched to an internal Chrome scheme + (chrome://, chrome-native://, about://) by a first party app (not Chrome). + This metric is to be used to determine whether any first party app uses the + feature, and whether we can remove it. + + + + + + + tedchoc@chromium.org + + Android: Count of page loads started by intents from external apps. In M87 + the reporting of this histogram was updated to exclude intents sent from + Chrome itself. + + + + + gangwu@chromium.org + jdonnelly@chromium.org + + Recorded when user long presses and pastes clipboard content into omnibox. + The value indicates the estimated age of the clipboard. + + Intended to be compared to Omnibox.ClipboardSuggestionShownAge. + + + + + stkhapugin@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Recorded when the omnibox popup is closed. Indicates the duration it was + open. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + + When a user presses an omnibox suggestion based on the content of the + clipboard, this histograms records how long ago Chrome detected a change in + the clipboard. + + Intended to be compared to Omnibox.ClipboardSuggestionShownAge. + + If Chrome never detected a change to the clipboard, no clipboard suggestion + is shown, meaning this histogram will never be emitted to. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times the signin promo is implicitly dismissed (by closing + the bookmark manager) per impression. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times one of the "sign in" buttons (any of the + signed-out "Sign in to Chrome" button, the "Continue as + |name|" button, or the "Not |email|?" button) is clicked per + impression. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times the explicit "X"-to-close button is clicked + per impression. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times the signin promo is implicitly dismissed (by closing + the settings view) per impression. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times one of the "sign in" buttons (any of the + signed-out "Sign in to Chrome" button, the "Continue as + |name|" button, or the "Not |email|?" button) is clicked per + impression. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts how many times the explicit "X"-to-close button is clicked + per impression. + + + + + tedchoc@chromium.org + twellington@chromium.org + + Android only. + + The number of times the tabbed mode of Chrome is launched within a given 24 + hour window. Recall that custom tabs is not considered tabbed mode. A + "launch" here is defined as anytime the tabbed mode is made + visible (foregrounded), but all Chrome activities must be completely hidden + before we'll count an additional launch. It includes all kinds of intents, + such as MAIN and VIEW. By ensuring all Chrome activities are hidden, we + avoid overcounting by going to Settings and returning to Chrome. + + This launch definition includes some items one might not expect: (i) click a + link in Chrome that opens in another app, then click back. (ii) have Chrome + in the foreground, then the screen times out (goes blank) or engages the + lock screen, then wake up/unlock the device. (iii) switch to + "Recents", then re-select Chrome. In all these cases, Chrome has + gone to the background so returning to it counts as another launch. + + The value reported reflects activity over a 24-hour window in the past, + possibly the distant past. Reporting is controlled by storing an initial + launch timestamp and counting all "launches" as a count until a + new launch happens after the 24hr window has elapsed (at this point, a new + 24hr window is started). The count is reported at the start of the next 24hr + window, so this is a retroactive count. For example, if a user uses Chrome + in one day two months ago, then doesn't use Chrome at all, then when Chrome + launches today it'll report the value during that 24-hour window. + + + + + tedchoc@chromium.org + twellington@chromium.org + yfriedman@chromium.org + + Android: The time it takes from creating an intent for ChromeActivity to + activity creation. This includes activity creation time spent in the + framework. + + + + + tedchoc@chromium.org + twellington@chromium.org + + The type of launching Chrome mobile app, e.g launch by hitting icon. + + Only recorded for tabbed mode launches of Chrome. Recall that custom tabs is + not considered tabbed mode. + + + + + pasko@chromium.org + + Android: The time spent performing toolbar layout inflation. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/multi_device/histograms.xml b/tools/metrics/histograms/histograms_xml/multi_device/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..bdefa7dc2a0c8b2db2d825d0e0a47bb596b4df68 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/multi_device/histograms.xml @@ -0,0 +1,299 @@ + + + + + + + + + + vecore@google.com + better-together-dev@google.com + + Indicates the feature state of the Better Together Suite feature. This + metric is emitted to at the creation of the user session (when the user logs + in), and when feature state updates occur. + + + + + vecore@google.com + better-together-dev@google.com + Result of trying to find eligible devices. + + + + vecore@google.com + better-together-dev@google.com + + Breaks down the percentages of reasons when failure occurs on + FindEligibleDevices. + + + + + vecore@google.com + better-together-dev@google.com + Result for when ForceEnrollmentNow is called. + + + + vecore@google.com + better-together-dev@google.com + Result for when ForceSyncNow is called. + + + + vecore@google.com + better-together-dev@google.com + + Breaks down which features failed when attempted to disable. + + + + + vecore@google.com + better-together-dev@google.com + Breaks down which features failed when attempted to enable. + + + + vecore@google.com + better-together-dev@google.com + Result of enabling and disabling features for devices. + + + + vecore@google.com + better-together-dev@google.com + + Breaks down the percentages of reasons when failure occurs on + SetSoftwareFeatureState. + + + + + vecore@google.com + better-together-dev@google.com + + Compares when the Forget Host Button is pressed and when setup completes. + + + + + vecore@google.com + better-together-dev@google.com + + Provides a count of how many times each page of the MultiDevice setup flow + was reached. This allows analysis of user dropoff between subsequent pages. + + The formula "Success page" / "Start page" provides the + overall "success rate" of the MultiDevice setup flow, at a quick + glance. + + The sum of each bucket's count is not meaningful. + + + + + vecore@google.com + better-together-dev@google.com + + A histogram measuring the success rate of authenticating a BLE channel once + a GATT connection has been established. This metric measures the effective + rate; i.e., a failure followed by a successful retry is counted as a + success. + + + + + vecore@google.com + better-together-dev@google.com + + A time histogram measuring the time from the moment a GATT connection is + made to the remote device, to the moment that an authenticated channel is + established with the remote device. + + In this context, "background" refers to the BLE advertising scheme + under which the remote device is persistently advertising "in the + background" at low power. + + + + + vecore@google.com + better-together-dev@google.com + + A time histogram measuring the time from the moment a background + advertisement is received, to the moment that a GATT connection is made to + the remote device. + + In this context, "background" refers to the BLE advertising scheme + under which the remote device is persistently advertising "in the + background" at low power. + + + + + vecore@google.com + better-together-dev@google.com + + A time histogram measuring the time it takes to create a secure connection + to a remote device, from the moment a SecureChannelService client asks for a + new connection (start scanning), to the moment that an authenticated channel + is established with the remote device. + + In this context, "background" refers to the BLE advertising scheme + under which the remote device is persistently advertising "in the + background" at low power. + + + + + vecore@google.com + better-together-dev@google.com + + A time histogram measuring the time it from the moment SecureChannelService + starts scanning for a background advertisement, to the moment that it + establishes a GATT connection to the remote device. + + In this context, "background" refers to the BLE advertising scheme + under which the remote device is persistently advertising "in the + background" at low power. + + + + + vecore@google.com + better-together-dev@google.com + + A time histogram measuring the time it from the moment SecureChannelService + starts scanning for a background advertisement, to the moment that it + receives an advertisement from the expected remote device. + + In this context, "background" refers to the BLE advertising scheme + under which the remote device is persistently advertising "in the + background" at low power. + + + + + vecore@google.com + better-together-dev@google.com + + A histogram measuring the success rate of authenticating a BLE channel once + an advertisement has been received. This metric measures the effective rate; + i.e., a failure followed by a successful retry is counted as a success. + + + + + vecore@google.com + better-together-dev@google.com + + A histogram measuring the success rate of creating a GATT connection once an + advertisement has been received. This metric measures the effective rate; + i.e., a failure followed by a successful retry is counted as a success. + + + + + vecore@google.com + better-together-dev@google.com + + Breaks down percentages of host statuses. This metric is emitted to at the + creation of the user session (when the user logs in), and when host status + updates occur. + + + + + nohle@chromium.org + better-together-dev@google.com + + Records if a multi-device host device has all of the crypto data necessary + for secure communication via Bluetooth. This will be false if v2 DeviceSync + data is not yet decrypted, for instance. Emitted when checking if a host is + verified. This occurs only if there is an existing host, and the check + occurs during start-up, when the host changes, or when new devices are + synced from CryptAuth. + + + + + vecore@google.com + better-together-dev@google.com + + Compares when the Verify Host Button is pressed to when setup completes. + + + + + cvandermerwe@google.com + better-together-dev@google.com + + Indicates the feature state of the Wifi Sync V2 feature. This metric is + emitted to at the creation of the user session (when the user logs in), and + when feature state updates occur. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/na_cl/histograms.xml b/tools/metrics/histograms/histograms_xml/na_cl/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..1b28a5c4b70bd057ddc313f5153c317c1285e993 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/na_cl/histograms.xml @@ -0,0 +1,478 @@ + + + + + + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + Type of NaCl/PNaCl application/extension. Recorded at plugin creation time + after the permission check. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + When the browser started, what happened with the NaCl helper process? + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + When a NaCl application process was created, what had happened with the NaCl + helper process when the browser was started? + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The OS/Architecture of a nexe that was loaded. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The status code returned when trying to load a manifest inside an installed + app. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The status code returned when trying to load a manifest from a source other + than an installed app. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The status code returned when trying to load a NaCl executable inside an + installed app. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The status code returned when trying to load a NaCl executable from a source + other than an installed app. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The error code returned by NaCl's Chrome plugin. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The error code returned by NaCl's Chrome plugin, but only for installed + apps. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The error code returned by NaCl's Chrome plugin, but excluding installed + apps. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The error code returned by NaCl's sel_ldr. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The error code returned by NaCl's sel_ldr, but only for installed apps. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The error code returned by NaCl's sel_ldr, but excluding installed apps. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + Was the manifest specified as a data URI rather than a .nmf file? + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The time a NaCl module ran before it crashed. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The time a NaCl module ran without crashing, at shutdown. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The optimization level set for the initial Portable Native Client + translation from bitcode to native code. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + Did the Portable Native Client translation cache find an executable + translated from bitcode? + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The rate for compiling a Portable Native Client bitcode file to an object + file in Kilobytes per second. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to compile a Portable Native Client bitcode file to an + object file. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to link a Portable Native Client generated object file into + a Native Client executable. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to load and validate the Portable Native Client compiler. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to load and validate the Portable Native Client linker. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The percentage of a Portable Native Client application that is compiled by + the time the application is fully downloaded (compile and download happen in + parallel). + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The rate for completely translating a Portable Native Client bitcode file + into a Native Client executable and caching the result in Kilobytes per + second. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The total time it took to completely translate a Portable Native Client + bitcode file into a Native Client executable, and cache the result. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The time it took the NaCl module to shut down. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The size of the manifest file. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The size of the main .nexe file downloaded for a Native Client module. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The size of the main .pexe bitcode file downloaded for a Portable Native + Client module. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The size of the main .pexe bitcode file divided by the size of the .nexe + that is the result of translating the bitcode file, times 100. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The size of the main .nexe file that is the result of translating a Portable + Native Client .pexe bitcode file. This reflects the amount of cache + consumed. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + The time it took to load the NaCl module into sel_ldr. + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to load the NaCl module into sel_ldr. Normalized by the + size of the .nexe, in megabytes. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to download the manifset file for a Native Client module. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took between the Native Client plugin initialization and when + proxied execution of the NaCl module begins. This is the general startup + overhead of running as a NaCl module vs a trusted PPAPI plugin. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took between the Native Client plugin initialization and when + proxied execution of the NaCl module begins. This is the general startup + overhead of running as a NaCl module vs a trusted PPAPI plugin. Normalized + by the size of the .nexe, in megabytes. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to download the main .nexe for a Native Client module. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took to download the main .nexe for a Native Client module. + Normalized by the size of the .nexe, in megabytes. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took between the Native Client plugin initialization and when + the NaCl module is ready to be used. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + The time it took between the Native Client plugin initialization and when + the NaCl module is ready to be used. Normalized by the size of the .nexe, in + megabytes. + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + Did a validation cache query find a previously known validation result? + + + + + dschuff@chromium.org + adamk@chromium.org + bbudge@chromium.org + + Was the validation cache updated with a new validation result? + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/navigation/histograms.xml b/tools/metrics/histograms/histograms_xml/navigation/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..fd57b81774d022d669653417bb08b9d082402d80 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/navigation/histograms.xml @@ -0,0 +1,679 @@ + + + + + + + + + + shivanisha@chromium.org + csharrison@chromium.org + + This metric logs true if all the previous entries are marked to be skipped + on back/forward button via the history manipulation intervention. This is + logged when back button is pressed (see crbug.com/907167). The goal of the + intervention is to intervene against pages that manipulate browser history + such that the user is not able to use the back button to go to the previous + site they interacted with. + + + + + shivanisha@chromium.org + csharrison@chromium.org + + This metric counts the number of entries the history manipulation + intervention would have skipped when the user presses the back button (see + crbug.com/907167). The goal of the intervention is to intervene against + pages that manipulate browser history such that the user is not able to use + the back button to go to the previous site they interacted with. + + + + + clamy@chromium.org + The cache flags set on back-forward navigations. + + + + shivanisha@chromium.org + csharrison@chromium.org + + This metric counts the number of entries the history manipulation + intervention would have skipped when the user presses the forward button + (see crbug.com/907167). The goal of the intervention is to intervene against + pages that manipulate browser history such that the user is not able to use + the back button to go to the previous site they interacted with. + + + + + shivanisha@chromium.org + csharrison@chromium.org + + This metric logs true if the existing entry being navigated to is marked to + be skipped on back/forward UI. This is logged at the start of navigation + initiated using long-press back/forward button. + + + + + shivanisha@chromium.org + csharrison@chromium.org + + Whether an entry in the back-forward list is marked to be skipped on + subsequent back/forward button clicks as part of the history manipulation + intervention. This is logged when the entry is navigated away from. The goal + is to intervene against pages that manipulate browser history such that the + user is not able to use the back button to go to the previous site they + interacted with. + + + + + clamy@chromium.org + Whether the back-forward navigation was served from cache. + + + + msramek@chromium.org + + Recorded when a navigation is deferred while clearing site data. Indicates + how much time the clearing took. + + + + + msramek@chromium.org + + The parameters of the Clear-Site-Data header. Recorded when the header is + successfully parsed. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logs the error code for each navigation commit timeout. This will be used to + debug http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logs whether this was a main frame navigation for each navigation commit + timeout. This will be used to debug http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logged with the status of the renderer process for each navigation commit + timeout. This will be used to debug http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logged with the status of the network service for each navigation commit + timeout. This will be used to debug http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logged with the time since the last network service crash if available for + each navigation commit timeout. This will be used to debug + http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logs the time it takes to make a round trip call to the network service for + each navigation commit timeout. This will be used to debug + http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Logged with the navigation URL scheme for each navigation commit timeout. + This will be used to debug http://crbug.com/934317. + + + + + csharrison@chromium.org + yaoxia@chromium.org + + When a navigation results in a download, logs the download policy applied to + that navigation. This is logged once per download and when multiple policies + exist, an arbitrary one will be chosen. + + + + + csharrison@chromium.org + yaoxia@chromium.org + + When a navigation results in a download, for each download policy applied to + that navigation, logs the policy. + + + + + estark@chromium.org + security-enamel@chromium.org + + The amount of time that an HTTP page was in the foreground. Recorded on + every page close/transition. + + + + + estark@chromium.org + security-enamel@chromium.org + + The amount of time that an HTTPS page was in the foreground. Recorded on + every page close/transition. + + + + + estark@chromium.org + security-enamel@chromium.org + + The percentage of time that HTTPS pages were in the foreground, as compared + to total foreground time. Recorded whenever user metrics are uploaded. + + + + + + + mpearson@chromium.org + amaralp@chromium.org + chrome-analysis-team@google.com + + Emitted every time a user uses a Home button to go to their home page. + Records whether the page is chrome-internal (most likely the New Tab Page or + about:blank) or not (most likely an actual web site). For the purpose of + this histogram, about:, chrome: and chrome-native: are considered + chrome-internal; everything else is not. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + ajuma@chromium.org + eugenebut@chromium.org + + Logged when NavigationContext is null inside -[WKNavigationDelegate + webView:didFailProvisionalNavigation]. If Chrome stopped logging this metric + it means that it is now safe to remove workaround for + https://bugs.webkit.org/show_bug.cgi?id=198794. + + + + + alexmos@chromium.org + lukasza@chromium.org + + Whether the navigation commits in a process that is locked to an origin. + Logged at ready-to-commit time for every navigation excluding same-document + navigations and errors. + + + + + alexmos@chromium.org + lukasza@chromium.org + + Whether the navigation commits in a process that is locked to an origin. + Logged at ready-to-commit time for every navigation that commits with a HTTP + or HTTPS URL scheme, excluding same-document navigations and errors. + + + + + arthursonzogni@chromium.org + clamy@chromium.org + nasko@chromium.org + + Whether a main frame navigation led to a change of BrowsingInstance or not. + + + + + clamy@chromium.org + nasko@chromium.org + Whether the navigation led to a change of process or not. + + + + arthursonzogni@chromium.org + clamy@chromium.org + nasko@chromium.org + + Whether the navigation led to a change of SiteInstance or not. + + + + + + + boliu@chromium.org + alexmos@chromium.org + src/base/android/OWNERS + + The type of the source of a load from LoadIfNecessary. Recorded when + LoadIfNecessary starts a page load. For example, on Android, + kRequestedByClient is recorded when user switch back to a tab with a dead + renderer, which causes the tab to reload. + + + + + michaelpg@chromium.org + yilkal@chromium.org + cros-families-eng@google.com + + The number of frames that are present in a WebContents. Recorded once when + the main frame finishes loading. + + + + + michaelpg@chromium.org + yilkal@chromium.org + cros-families-eng@google.com + + The maximum number of loaded frames that are present in a WebContents. + Recorded once when the main frame is moving away from current page. This can + be when the WebContents is being destroyed or when it starts loading new + content. + + + + + meacer@chromium.org + security-enamel@chromium.org + + Site engagement level of the URL of the top frame of a navigation. Only + counts HTTP or HTTPS URLs and ignores downloads. + + + + + meacer@chromium.org + security-enamel@chromium.org + + Site engagement level of the URL of the top frame of a form submission. This + is a subset of Navigation.MainFrame.SiteEngagementLevel. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Whether the main-frame navigation was to a URL with an RTL domain name. This + is only recorded for finished navigations and not attempts. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Whether the main-frame navigation was to a URL with an RTL domain name, + recorded for each main-frame avigation that replaces a document object. This + is not reported for reference fragment navigations, pushState/replaceState + or same page history navigation. This is only recorded for finished + navigations and not attempts. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + The browser profile type for each main-frame navigation, recorded after + navigation completion, including NTP. + + + + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation. This is only recorded + for finished navigations and not attempts. + + + + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation that replaces a + document object. This is not reported for reference fragment navigations, + pushState/replaceState or same page history navigation. This is only + recorded for finished navigations and not attempts. + + + + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation that replaces a + document object while in incognito. This is not reported for reference + fragment navigations, pushState/replaceState or same page history + navigation. This is only recorded for finished navigations and not attempts. + + + + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation while in incognito. + This is only recorded for finished navigations and not attempts. + + + + + jam@chromium.org + kinuko@chromium.org + + The sum of all the times spent posting tasks between the UI and IO threads + inside NavigationURLLoaderImpl. Recorded when each frame navigation gets the + response. + + Note: This metric drops reports on clients with low-resolution clocks, which + means these reports will be biased against a portion of the population on + Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + clamy@chromium.org + nasko@chromium.org + + Overhead time spent handling the OnBeforeUnload event from the browser + standpoint. More precisely, it is the total time between dispatch and + acknowledgment of the BeforeUnload event on the browser side, minus the + actual time spent executing the BeforeUnload handlers on the renderer side. + + + + + falken@chromium.org + chrome-loading@google.com + + Time between the two messages OnReceiveResponse and + OnStartLoadingResponseBody as observed by the browser process during a + navigation by NavigationURLLoader::URLLoaderRequestController. The idea is + to see whether there is a performance cost in having two separate messages, + as the plan is to combine them into one. + + + + + clamy@chromium.org + nasko@chromium.org + + The time needed to commit a navigation once it is ready to commit. This is + the time between ReadyToCommit and DidFinishNavigation (for a navigation + that commits). + + + + + alexmos@chromium.org + lukasza@chromium.org + + Whether the navigation commits in a SiteInstance that requires a dedicated + process. Logged at ready-to-commit time for every navigation excluding + same-document navigations and errors. + + + + + alexmos@chromium.org + lukasza@chromium.org + + Whether the navigation commits in a SiteInstance that requires a dedicated + process. Logged at ready-to-commit time for every navigation that commits + with a HTTP or HTTPS URL scheme, excluding same-document navigations and + errors. + + + + + jam@chromium.org + + True counts the events when a https URL commits with a SSL certificate. + False is when the certificate is missing. This should be at 100%, anything + less is probably a bug. + + + + + nasko@chromium.org + csharrison@chromium.org + + The time delta between the start of a navigation and the time it is + committed. + + + + + clamy@chromium.org + nasko@chromium.org + + The time delta between the start of a navigation and the time it is ready to + commit. + + + + + carlosk@chromium.org + + Time between the start of a browser-started navigation request and the + reception of a corresponding ResourceRequest in the network stack. + + + + + estark@chromium.org + + When the navigation URL loader receives an OnComplete message from the + network service that contains certificate chains, this histogram records the + size in KB of those pickled certificate chains. This histogram is recorded + by the navigation URLLoader for navigations that fetch from network, for + every request which contains an SSLInfo in its OnComplete notification. + + + + + estark@chromium.org + + Whether the network service's OnComplete message to the navigation URL + loader contains an SSLInfo, which should only be present for main-frame + requests with certificate errors. This histogram is recorded for every + request completion by the navigation URL loader that fetches from network. + + + + + tbansal@chromium.org + + Tracks action taken by navigation predictor. Recorded at the time of page + load. + + + + + tbansal@chromium.org + ryansturm@chromium.org + + Reports data about the clicked link with regards to whether it was + prerendered by the Navigation Predictor. Recorded when the page is navigated + away from. + + + + + tbansal@chromium.org + ryansturm@chromium.org + + Reports data about the clicked link with regards to whether it was + prerendered by the Navigation Predictor. Recorded when the page is navigated + away from. + + + + + tbansal@chromium.org + ryansturm@chromium.org + + Reports data about the clicked link with regards to whether it was + prerendered by the Navigation Predictor. Recorded when the page is navigated + away from. + + + + + sophiechang@chromium.org + tbansal@chromium.org + + Count of likely URLs for the next navigation as reported by an external + Android app via mayLaunchUrl() Android API. Recorded at the time the + prediction was received by Chrome. + + + + + tbansal@chromium.org + ryansturm@chromium.org + + Set to true if the IP address of the origin of the main frame URL is + publically routable. Recorded everytime a preconnect attempt is made by the + navigation predictor. + + + + + ryansturm@chromium.org + tbansal@chromium.org + + Reports data about the clicked link with regards to whether it was + prerendered by the Navigation Predictor. Recorded when the user clicks a + link. + + + + + meacer@chromium.org + security-enamel@chromium.org + + Tracks events when the currently navigated domain name is a lookalike to one + of the top 10K domains or a domain that the user interacted with, resulting + in a navigation suggestion interstitial. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/net/histograms.xml b/tools/metrics/histograms/histograms_xml/net/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..b0e7439fb806bbb91651ac68f65d91e9451926e5 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/net/histograms.xml @@ -0,0 +1,4743 @@ + + + + + + + + + + dschinazi@chromium.org + src/net/OWNERS + + Breakdown of the locations when SetBrokenAlternateProtocol is called. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Breakdown of how requests which could potentially make use of an alternate + protocol use or don't use the protocol. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Breakdown of how requests which could potentially make use of an alternate + protocol use or don't use the protocol, for connections to Google servers. + + + + + tbansal@chromium.org + dschinazi@chromium.org + src/net/OWNERS + + Positive net error codes that failed alternative protocol requests end with. + Recorded only when an alternative job fails, and the main job succeeds. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Information about the AlternativeService used for each request. + + + + + estark@chromium.org + + The net error code returned after attempting an AIA fetch on Android. + Recorded once per intermediate that Chrome attempts to fetch via AIA on + Android. + + + + + martinkr@google.com + + Whether certificate validation was disabled for a set of public keys because + the --ignore-certificate-errors-spki-list switch was set on startup. + + + + + martinkr@google.com + + Whether certificate validation was disabled because the + --ignore-certificate-errors switch was set on startup. + + + + + estark@chromium.org + + This histogram is recorded every time Chrome successfully verifies a + certificate that chains to a private root. A value of true indicates that + the certificate contains the TLS Feature Extension, and false indicates that + it doesn't. + + + + + estark@chromium.org + + This histogram is recorded every time Chrome successfully verifies a + certificate that chains to a private root and the certificate contains the + TLS Feature Extension. A value of true indicates that the connection had an + OCSP response stapled, and a value of false indicates that it did not. + + + + + + + rsleevi@chromium.org + + The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust + anchor encountered in a successfully-verified certificate chain, during an + HTTP URL request. The associated root certificate can be looked up using + https://crt.sh/?spkisha256= . + + + + + + + rsleevi@chromium.org + + The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust + anchor encountered in a successfully-verified certificate chain, during + verification time. The associated root certificate can be looked up using + https://crt.sh/?spkisha256= . + + + + + + + rsleevi@chromium.org + + This histogram is recorded every time Chrome successfully validates a + certificate, but cannot determine a public trust anchor from the verified + chain. A value of true indicates that the trust anchor list is out of date, + as the OS believes a public trust anchor is being used, but the built-in + list does not know about this trust anchor, while a value of false indicates + that a public trust anchor was not used, thus there is no evidence that the + list is out of date. This histogram is temporary until the transition to a + unified root store (in source), at which point, the OS store will no longer + be consulted for known roots. + + + + + estark@chromium.org + + Whether or not certificate verification was successful after attempting AIA + fetching on Android. Recorded once per certificate verification on Android + that resulted in an untrusted-root error without AIA fetching. + + + + + + + estark@chromium.org + + The compliance of each connection with the Certificate Transparency policy, + recorded once on connection setup unless CT evaluation has been disabled for + that connection or the certificate is invalid. Connections can be compliant, + or they can be non-compliant for one of several reasons (not enough Signed + Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old + so CT compliance wasn't checked). Not recorded for certificates that chain + to locally-installed roots. + + + + + + + estark@chromium.org + + The compliance of each connection with the Certificate Transparency policy, + for connections for which CT compliance is required for the connection to + succeed. (For example, CT compliance is required for certain Certificate + Authorities, or a site can opt in to having CT be required.) Recorded once + on connection setup for applicable connections unless CT evaluation has been + disabled for that connection or the certificate is otherwise invalid. Not + recorded for certificates that chain to locally-installed roots. + + + + + estark@chromium.org + + The compliance of each HTTP request with the Certificate Transparency + policy, for requests on connections for which CT compliance is required for + the connection to succeed. (For example, CT compliance is required for + certain Certificate Authorities, or a site can opt in to having CT be + required.) Recorded once on request completion for requests on applicable + connections, unless CT evaluation has been disabled for that connection or + the certificate is otherwise invalid. Not recorded when the request's + certificate chains to a locally-installed root. + + + + + + + estark@chromium.org + + The state of compliance with Certificate Transparency presence requirements + for each EV certificate. Recorded once on QUIC connection setup when the + connection uses an EV certificate unless CT evaluation has been disabled for + that connection or the certificate is invalid. Not recorded for certificates + that chain to locally-installed roots. + + + + + estark@chromium.org + + The compliance of each HTTP request with the Certificate Transparency + policy, recorded once on request completion unless CT evaluation has been + disabled for that request's connection or the certificate is otherwise + invalid. A request's connection can be compliant, or it can be non-compliant + for one of several reasons (not enough Signed Certificate Timestamps [SCTs], + not diverse enough SCTs, or the build was old so CT compliance wasn't + checked). Not recorded when the request's certificate chains to a + locally-installed root. + + + + + estark@chromium.org + rsleevi@chromium.org + + Time to verify a single SCT (Signed Certificate Timestamps) when setting up + a TLS connection. Recorded each time a single SCT is verified. Includes not + just the signature verification but also other operations that are involved + in verifying an SCT, such as notifying observers and looking up the log that + issued the SCT. + + + + + estark@chromium.org + rsleevi@chromium.org + + Time to verify the SCTs (Signed Certificate Timestamps) when setting up a + TLS connection. Recorded on each connection setup where at least one SCT is + verified. + + + + + estark@chromium.org + rsleevi@chromium.org + + The origin breakdown of Signed Certificate Timestamps (SCTs). Emitted once + for every SCT when first validated, which means 0 or more times during every + SSL connection establishment. + + + + + estark@chromium.org + rsleevi@chromium.org + + Breakdown of Signed Certificate Timestamps (SCTs) validation status. Emitted + once for every SCT when first validated, which means 0 or more times during + every SSL connection establishment. + + + + + mattm@chromium.org + rsleevi@chromium.org + + Whether Name normalization was used in successfully validated certificate + chains, only recorded for chains ending in privately trusted roots. Suffixed + by the CertVerifyProc implementation. + + + + + mattm@chromium.org + rsleevi@chromium.org + + When using the builtin cert verifier, records the number of iterations taken + during path building for each attempted verification. + + + + + + + mattm@chromium.org + rsleevi@chromium.org + + The actual amount of time spent verifying a certificate using the underlying + cryptographic APIs. Because parallel verifications for the same certificate + may be coalesced, histograms such as Net.SSLCertVerificationTime may be + skewed, due to later verifications taking less overall time. This records + the overall time spent verifying the first job to capture initialization + costs. + + + + + + + rsleevi@chromium.org + mattm@chromium.org + + The actual amount of time spent verifying a certificate using the underlying + cryptographic APIs. Because parallel verifications for the same certificate + may be coalesced, histograms such as Net.SSLCertVerificationTime may be + skewed, due to later verifications taking less overall time. This records + the overall time spent verifying a single request, regardless of how many + parallel requests are being served by the verification. + + + + + mattm@chromium.org + rsleevi@chromium.org + + If the CertDualVerificationTrial is enabled, each certificate verification + associated with a (non-incognito) profile which is opted-in to SBER2(Scout) + will record the outcome of comparing the primary verifier and secondary + verifier results. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Application protocol used for main frame resources. Logged by the renderer + only for request that accessed the network and have received response + headers. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Application protocol used for subresources (resources other than main + frame). Logged by the renderer only for request that accessed the network + and have received response headers. + + + + + mef@chromium.org + pauljensen@chromium.org + + For each CONTENT_DECODING_FAILED, record the filter that failed. + + + + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of CORS error types on the original network requests. This + reports whenever CORS checks detect an error on the original network + requests. + + + + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of CORS access check results. This reports whenever CORS + AccessCheck runs. + + + + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the key size in the CORS preflight cache. This counts + each key size when a new entry is added to the cache. + + + + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the CORS preflight cache query results. This counts on + each cache query. + + + + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of CORS error types on preflight requests. This reports + whenever CORS checks detect an error on the original network requests. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The number of broken alternative services loaded from the prefs file on + startup. Alternative services allow an origin server to specify additional + means of interacting with it on the network. A broken alternative service is + one whose most recent connection attempt failed and whose retry timeout + period has not yet expired. Recorded when broken alternative services are + loaded from the prefs file on startup. + + + + + zhongyi@chromium.org + dschinazi@chromium.org + src/net/quic/OWNERS + + This counts the number of server configs persisted in prefs file. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The number of recently broken alternative services loaded from the prefs + file on startup. Alternative services allow an origin server to specify + additional means of interacting with it on the network. A recently broken + alternative service is one whose most recent connection attempt failed. + Recorded when broken alternative services are loaded from the prefs file on + startup. + + + + + yhirano@chromium.org + kinuko@chromium.org + src/net/OWNERS + + The maximum number of data pipes used for network::URLLoader in the network + service in every 20 minutes. + + + + + yhirano@chromium.org + kinuko@chromium.org + src/net/OWNERS + + The minimum number of data pipes used for network::URLLoader in the network + service in every 20 minutes. + + + + + yhirano@chromium.org + kinuko@chromium.org + src/net/OWNERS + + The maximum number of data pipes used for network::WebSocket in the network + service in every 20 minutes. + + + + + yhirano@chromium.org + kinuko@chromium.org + src/net/OWNERS + + The minimum number of data pipes used for network::WebSocket in the network + service in every 20 minutes. + + + + + ericorth@chromium.org + doh-core@google.com + + Records details of the secure DNS mode used to configure the host resolver + at construction of the network service. + + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of specific error codes returned by DnsTask. Only counts failures + that took less than 10ms, which are probably local failures. + + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of specific error codes returned by DnsTask. Only counts failures + that took at least 10ms, which are probably remote failures or connectivity + problems. + + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of specific error codes returned by DnsTask if a subsequent ProcTask + succeeded. + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of time taken by DnsTask (the grouping of all individual DNS + queries for a single instance of resolving a name) in resolutions that + succeeded. + + + + + ericorth@chromium.org + src/net/OWNERS + + Enumeration of the logic path used (e.g. different protocols) for each + started DnsAttempt (the representation of an individual network request to a + DNS server). + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by an insecure DnsTransaction to fail. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by an insecure DnsTransaction to succeed. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Counts of specific error codes returned by secure DnsTransactions to a DoH + server that is unavailable or has unknown availability. These transactions + may be probe queries or queries issued in the secure DNS mode. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTransaction to a DoH server that is + unavailable or has unknown availability to fail. These transactions may be + probe queries or queries issued in the secure DNS mode. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTransaction to a DoH server that is + unavailable or has unknown availability to succeed. These transactions may + be probe queries or queries issued in the secure DNS mode. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Counts of specific error codes returned by secure DnsTransactions to an + available DoH server. A DoH server is available if a probe has been + successfully completed and fewer than a threshold amount of failures have + occurred. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTransaction to an available DoH server + to fail. A DoH server is available if a probe has been successfully + completed and fewer than a threshold amount of failures have occurred. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTransaction to an available DoH server + to succeed. A DoH server is available if a probe has been successfully + completed and fewer than a threshold amount of failures have occurred. + + + + + ericorth@chromium.org + src/net/OWNERS + + Ratio (scaled up by 10) between the time taken by a successful secure + DnsTransaction attempt and the current dynamically-determined base timeout + in use for the DoH server that accomplished the resolve. Only recorded when + the DoH server is already known to be "available" (successful + probe request and failure thresholds not exceeded). + + + + + ericorth@chromium.org + src/net/OWNERS + + Enumerated status of whether a DNS over UDP response ID matched the expected + query ID and whether a mismatched ID is recognized as a recently-queried + one. Logged for every DNS over UDP response received with a parsable ID. + + + + + ericorth@chromium.org + src/net/OWNERS + + Time between receiving a mismatched DNS ID (when a DNS response contains an + ID that does not match the ID sent in the query) via UDP and the oldest + known use of the same ID in a query. Logged for every DNS over UDP response + receivied with a mismatched DNS ID. + + + + + ericorth@chromium.org + src/net/OWNERS + + Enumerated status of the reason why the built-in DNS resolver has detected a + "low entropy" situation for DNS over UDP and has switched to DNS + over TCP. + + + + + ericorth@chromium.org + src/net/OWNERS + + Number of recent uses found of a local port number used for DNS over UDP. + Logged for every DNS over UDP query sent. + + + + + ericorth@chromium.org + src/net/OWNERS + + Time between use of a local port number for DNS over UDP and the most recent + DNS over UDP use of the same port. Logged for every DNS over UDP query sent + with at least 1 recognized previous use of the local port. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Records which RCODE the DNS server specified when it responded to our + INTEGRITY query. If the query timed out before getting a response, + "TimedOut" is recorded instead of an RCODE value. Histograms are + emitted at the completion of a DnsTask's final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Indicates whether the result of an INTEGRITY query was intact (true) or + mangled (false). Only recorded when DnsRcode indicates NoError. Histograms + are emitted at the completion of a DnsTask's final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Records a sample of one when we receive an INTEGRITY record and an error + RCODE at the same time. Histograms are emitted at the completion of a + DnsTask's final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Counts the number of records received when we get any INTEGRITY record + (Intact or Mangled) for a non-experimental domain. Any INTEGRITY record in + the response would be a surprise! Histograms are emitted at the completion + of a DnsTask's final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Records how many ms the DNS server took to respond to an INTEGRITY query. + Histograms are emitted at the completion of a DnsTask's final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Records how many ms the DNS server took to respond to any query other than + an INTEGRITY query. Histograms are emitted at the completion of a DnsTask's + final transaction. + + + + + + + dmcardle@chromium.org + ericorth@chromium.org + + Records a ratio indicating the relative INTEGRITY resolve time compared to + the slower A or AAAA resolve time, where A/AAAA/INTEGRITY belong to the same + DnsTask. Multiply this value by 10 to obtain a percentage P. The INTEGRITY + query completed in roughly P% of the slower A/AAAA resolve time. Values + smaller than 10 indicate that INTEGRITY query was faster than A/AAAA. Values + larger than 10 indicate that the INTEGRITY query was slower than A/AAAA. + Histograms are emitted at the completion of a DnsTask's final transaction. + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of time taken by an insecure DnsTask in resolutions that failed. + + + + + dmcardle@chromium.org + ericorth@chromium.org + + The duration of time DnsTransactions spend waiting to be started by a + DnsTask, aggregated by HostResolverManager::Job. This metric is only + recorded when the Job failed. + + + + + dmcardle@chromium.org + ericorth@chromium.org + + The duration of time a DnsTransaction spends waiting to be started by a + DnsTask. The dominant factor is likely the time spent waiting for other + DnsTransactions to complete, i.e. waiting for DnsTask::StartNextTransaction + to be invoked by the dispatcher. If there were no limit on the number of + concurrent DNS queries, we would expect this metric to be near zero. + + + + + dmcardle@chromium.org + ericorth@chromium.org + + The duration of time DnsTransactions spend waiting to be started by a + DnsTask, aggregated by HostResolverManager::Job. This metric is only + recorded when the Job succeeded. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a probe attempt to fail. The time is measured + since the probe sequence was initiated due to a DNS config change. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a probe attempt to succeed. The time is measured + since the probe sequence was initiated due to a DNS config change. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a probe attempt to fail. The time is measured + since the probe sequence was initiated due to a network change. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a probe attempt to succeed. The time is measured + since the probe sequence was initiated due to a network change. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of HostResolver requests from Start() until completion. Includes + requests resolved synchronously using fast local sources, e.g. from cache, + recorded as 0. Excludes speculative requests. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of HostResolver requests from Start() until completion. Excludes + speculative requests and requests resolved using fast local sources, e.g. + from cache. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + Whether a HostResolverManager::Job (the basic internal unit of work for + non-local host resolutions, potentially merging redundant requests from + Chrome) succeeded or failed, and whether it was speculative. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + For DNS resolutions that failed after less than 10 ms, which are probably + local failures, what error code the jobs failed with. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + For DNS resolutions that failed after at least 10 ms, which are probably + remote failures or connectivity problems, what error code the jobs failed + with. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of time taken by HostResolverManager::Job (the basic internal unit + of work for non-local host resolutions, potentially merging redundant + requests from Chrome) in resolutions that failed. This is the time to + resolve a hostname from start to finish. Excludes jobs where all requests + are speculative. + + + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of time taken by HostResolverManager::Job (the basic internal unit + of work for non-local host resolutions, potentially merging redundant + requests from Chrome) in resolutions that succeeded. This is the time to + resolve a hostname from start to finish. Excludes jobs where all requests + are speculative. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by HostResolverManager::Job (the basic internal unit + of work for non-local host resolutions, potentially merging redundant + requests from Chrome) in resolutions for in AUTOMATIC secure DNS mode. + Excludes jobs where all requests are speculative. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by HostResolverManager::Job (the basic internal unit + of work for non-local host resolutions, potentially merging redundant + requests from Chrome) in resolutions for in OFF secure DNS mode. Excludes + jobs where all requests are speculative. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by HostResolverManager::Job (the basic internal unit + of work for non-local host resolutions, potentially merging redundant + requests from Chrome) in resolutions for in SECURE secure DNS mode. Excludes + jobs where all requests are speculative. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTask in resolutions that failed that + were issued in AUTOMATIC mode. Excludes time spent in the subsequent + fallback. + + + + + ericorth@chromium.org + doh-core@google.com + + Duration of time taken by a secure DnsTask in resolutions that failed that + were issued in SECURE mode. + + + + + ericorth@chromium.org + doh-core@google.com + + Counts of specific error codes returned by insecure DnsTasks after a secure + DnsTask failed. + + + + + ericorth@chromium.org + doh-core@google.com + + Counts of specific error codes returned by a ProcTask after a secure DnsTask + failed. Only records instances where there was no intermediary insecure + DnsTask. + + + + + + + ericorth@chromium.org + doh-core@google.com + + Provider in a user-initiated dropdown change event that occured when this + provider was one of the dropown options. + + + + + ericorth@chromium.org + doh-core@google.com + + Records the outcome of a DoH probe attempt on the first valid entry in the + custom text field. + + + + + ericorth@chromium.org + doh-core@google.com + + Records the outcome of a formatting validation attempt on the custom text + field. + + + + + ericorth@chromium.org + doh-core@google.com + + True if upgrade to DoH from a DoT hostname was attempted and succeeded. + False if it was attempted and failed. + + + + + ericorth@chromium.org + doh-core@google.com + + True if there was at least one public nameserver during an attempt to + upgrade to DoH from insecure DNS. False if there were no public nameservers + during an attempt to upgrade to DoH from insecure DNS. + + + + + ericorth@chromium.org + doh-core@google.com + + True if upgrade to DoH was not attempted because the DoH config was already + specified. False if upgrade to DoH was not attempted for some other reason. + + + + + ericorth@chromium.org + doh-core@google.com + + True if upgrade to DoH was not attempted because of unhandled options in the + system config. False if upgrade to DoH was not attempted for some other + reason. Emitted each time the DnsConfig is updated. + + + + + ericorth@chromium.org + doh-core@google.com + + True if upgrade to DoH from insecure DNS was attempted and succeeded. False + if it was attempted and failed. + + + + + mmenke@chromium.org + + The time measured before starting DNS lookup until after the connection is + complete. + + + + + csharrison@chromium.org + + The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time + histograms are being uploaded. + + + + + csharrison@chromium.org + + The bucket proportion of the ABORTED bucket in Net.ErrorCodesForMainFrame3 + at the time histograms are being uploaded. + + + + + + + mmenke@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" for + https://www.google.com (it does not for example count the error codes for + subresoures on a page). It excludes main frame navigations that are + converted to downloads (unless they fail / are aborted before it's known + that they would be a download), and requests handled externally (like mailto + links). + + + + + skonig@chromium.org + hbengali@chromium.org + + Net error codes that requests for images end with, including net::OK and + net:ERR_ABORTED. + + + + + + + mmenke@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" (it + does not for example count the error codes for subresoures on a page). It + excludes main frame navigations that are converted to downloads (unless they + fail / are aborted before it's known that they would be a download), and + requests handled externally (like mailto links). + + + + + + + mmenke@chromium.org + + Net error codes that requests for "subresources" end with, + including net::OK and net::ERR_ABORTED. + + + + + svaldez@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" for + endpoints used in the initial TLS 1.3 deployment. Subresources or main frame + navigations to other origins are not included. + + + + + edwardjung@chromium.org + src/net/OWNERS + + Counts of various events that can occur on the network error page. Note that + this histogram enum buckets are not mutually exclusive and so a single error + page load might report samples into multiple ones. Each bucket has + descriptions that further explain the context of their samples. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Counts of the type of offline content suggestions clicked on the network + error page. Reported upon click. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Counts of the type of offline content suggestions shown on the network error + page. Multiple suggestions can be shown at the same time. Reported when the + suggestions are presented. + + + + + mmenke@chromium.org + estark@chromium.org + + The number of entries loaded from the Expect-CT database when Chrome starts + up. + + + + + estark@chromium.org + + Sites can send an Expect-CT header to Chrome to indicate that they intend + their sites to comply with Chrome's Certificate Transparency policy. This + histogram is recorded whenever an Expect-CT header is processed on a + connection. True indicates that the header parsed successfully, and false + indicates that there was a parse failure. + + + + + estark@chromium.org + + Sites can send an Expect-CT header to Chrome to indicate that they intend + their sites to comply with Chrome's Certificate Transparency policy. This + histogram is recorded on connection setup, whenever Chrome connects to an + Expect-CT site using a publicly trusted root. The histogram records the CT + policy compliance status of the connection. + + + + + estark@chromium.org + + Sites can send an Expect-CT header to Chrome to indicate that they intend + their sites to comply with Chrome's Certificate Transparency policy. This + histogram is recorded whenever an Expect-CT header is successfully parsed on + a connection that chains to a publicly trusted root. The histogram records + the CT policy compliance status of the connection on which the header was + received. + + + + + yoichio@chromium.org + ricea@chromium.org + yhirano@chromium.org + + Protocol used to fetch upload streaming with allowHTTP1ForStreamingUpload: + true property. This is recorded per fetch attempt regardless of result. + + + + + yoichio@chromium.org + ricea@chromium.org + yhirano@chromium.org + + Protocol used to fetch upload streaming with allowHTTP1ForStreamingUpload: + false property. This is recorded per fetch attempt regardless of result. + + + + + tervay@google.com + asanka@chromium.org + + Each bucket is the result of whether or not the initiated FTP transaction. + Successful transactions are recorded as either authenticated or + unauthenticated. + + + + + davidben@chromium.org + + Records, on startup, for ARM devices running Android, whether the CPU is + known to have a broken NEON unit. See https://crbug.com/341598. + + + + + asanka@chromium.org + mmenke@chromium.org + + Per-authentication-scheme counts of authentication attempts and rejections. + + + + + asanka@chromium.org + mmenke@chromium.org + + Whether NTLMv2 was enabled for an authentication handshake. For a given data + set the number of samples here is expected to be equivalent to the + "NTLM Start" count in the "Net.HttpAuthCount" histogram. + Note that NTLMv2 being enabled makes the client behavior equivalent to + setting LmCompatibilityLevel to 3 or higher. + + + + + meacer@chromium.org + Type of the HTTP auth prompt displayed. + + + + asanka@chromium.org + mmenke@chromium.org + + Per-authentication-scheme counts of authentication targets, such as secure + servers or proxies. + + + + + Please list the metric's owners. Add more owner tags as needed. + Length of time that a received resource will be cacheable. + + + + bengr@chromium.org + + The difference between the size specified in the X-Original-Content-Length + header and the size of the response body. Only includes resources that have + the X-Original-Content-Length header. + + + + + + + bengr@chromium.org + + Size of the response body. This is the actual number of bytes received, + which usually agrees with but is not necessarily the same as the size + specified by the Content-Length header. Replaces Net.HttpContentLength, + recording non-DRP Http traffic as "Http.Direct" instead of + "Http.Other". + + + + + jkarlin@chromium.org + + Total prefilter (e.g., before decompression) bytes read for an HttpJob + request. + + + + + + + mmenke@chromium.org + + Time it takes to complete an HttpJob, from starting the transaction until we + are done reading. + + + + + + + mmenke@chromium.org + + Time it takes to complete an HttpJob, from starting the transaction until we + are done reading, for jobs served from the cache. + + + + + + + mmenke@chromium.org + + Time it takes to complete an HttpJob, from starting the transaction until + the job is killed. Note that we didn't detect the end of the data for this + job. + + + + + + + mmenke@chromium.org + + Time it takes to complete an HttpJob, from starting the transaction until we + are done reading, for jobs not served from the cache. + + + + + + + mmenke@chromium.org + + Time it takes to complete an HttpJob, from starting the transaction until we + are done reading, for jobs when we read until no more data is available. + + + + + + + bengr@chromium.org + + Net.HttpOriginalContentLength with non-data reduction proxy traffic properly + labeled with the "Direct" suffix. + + Size specified in the X-Original-Content-Length header. If this header is + not present in the response, the size of the response body is used. Replaces + Net.HttpOriginalContentLength, breaking down traffic by Direct, ViaDRP, + Bypassed, and Other. + + + + + bengr@chromium.org + + Size specified in the X-Original-Content-Length header. Only includes + resources that have the X-Original-Content-Length header. + + + + + eroman@chromium.org + tbansal@chromium.org + + Time taken to establish the connection to the HTTP proxy. Note that the + histogram expired briefly for M-86 and M-87 non-stable versions. Exact + counts during that period may not be meaningful. + + + + + + + mmenke@chromium.org + The count of HTTP Response codes encountered. + + + + zhongyi@chromium.org + mmenke@chromium.org + + The total number of ServerInfo structs written to the network service's + prefs file, recorded each time the HttpServerProperties are serialized to + update the copy stored on disk. + + + + + + + mmenke@chromium.org + + Time from when an HTTP request is issued to when the first byte is + processed. + + + + + yhirano@chromium.org + kinuko@chromium.org + + Whether and how keepalive requests are blocked. There is a similar histgoram + "Extensions.WebRequest.KeepaliveRequestState": This histogram + supports platforms where extensions are not supported. + "Extensions.WebRequest.KeepaliveRequestState" includes requests + rejected by WebRequest.onBeforeRequest() which are not counted in this + histogram. + + + + + yhirano@chromium.org + panicker@chromium.org + + The size of the request headers for each request with keepalive specified. + + + + + yhirano@chromium.org + kinuko@chromium.org + The end state of keepalive request. + + + + yhirano@chromium.org + panicker@chromium.org + + The sum of the size of the request headers and destination URL for each + request with keepalive specified. + + + + + yhirano@chromium.org + panicker@chromium.org + + The size of the destination URL for each request with keepalive specified. + + + + + yhirano@chromium.org + + The peak number of concurrent outstanding requests with keepalive specified. + This histogram is reported whenever the peak number is updated. For example, + if the inflight number of requests were 0 => 1 => 2 => 1 => 2 + => 3 => 2, then 0, 1, 2, and 3 would be reported. + + + + + yhirano@chromium.org + + The peak number of concurrent outstanding requests with keepalive specified + per render process. + + + + + yhirano@chromium.org + + The peak number of concurrent outstanding requests with keepalive specified + per render process. This histogram is reported whenever the peak number is + updated. For example, if the inflight number of requests were 0 => 1 + => 2 => 1 => 2 => 3 => 2, then 0, 1, 2, and 3 would be + reported. + + + + + jkarlin@chromium.org + + The distribution of storable vs "cache-control: no-store" + main-frame resources. + + Counted after response headers have completed and before the content has + completed. Redirects are counted. All HTTP cache transactions are counted, + not just those that require the network. + + + + + morlovich@chromium.org + wicarr@microsoft.com + webmedia@microsoft.com + + Records decision points on whether response-side media content will be + cached or not. This is determined after receiving the HTTP response headers + and before attempting to write the the cache. + + + + + davidben@chromium.org + + Records, on startup, for ARM devices running Android, whether the kernel is + missing AT_HWCAP2 from the ELF auxv and /proc/cpuinfo reports support for + ARMv8 features. Those features should also be reported in AT_HWCAP2. This is + to measure the workaround in https://crbug.com/boringssl/46. + + + + + mef@chromium.org + pauljensen@chromium.org + + This is logged when SCDynamicStoreCreate fails in + network_config_watcher_mac.cc. + + + + + mef@chromium.org + pauljensen@chromium.org + + This is logged when SCDynamicStoreCreateRunLoopSource fails in + network_config_watcher_mac.cc. + + + + + mef@chromium.org + pauljensen@chromium.org + + This is logged when retrying SCDynamicStore has stopped after either + receiving a success or hitting the maximum number of retries in + network_config_watcher_mac.cc. The 0 bucket is where no retry is performed, + and the maximal bucket is where all retries have failed. + + + + + horo@chromium.org + ksakamoto@chromium.org + kinuko@chromium.org + + When Network Error Logging observes a completed request of signed exchange + that might generate a report, what happens to it. NEL observes all requests, + both successful and unsuccessful. It sends reports for successful and + unsuccessful requests at specified sampling rates so that error rates can be + calculated. Insecure requests are discarded for having an insecure origin + regardless of existence of a policy for the origin. + + + + + pauljensen@chromium.org + + On Windows, NetworkChangeNotifierWin calls NotifyAddrChange, which can fail + for unknown reasons. This records the number of times it fails in a row + before a successful call. If it never succeeds, or takes over 100 tries, a + value of 100 is recorded. See http://crbug.com/69198 + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of QUIC sessions when the QuicStreamFactory is destroyed. + + + + + jkarlin@chromium.org + + Bytes read for requests that were served from a cache entry whose + unused_since_prefetch bit is true. + + + + + jkarlin@chromium.org + + Number of bytes read from the network on behalf of prefetch requests. This + is prefilter, so before any decompression. + +
+ This applies to requests with RESOURCE_TYPE_PREFETCH. +
+ + + + eroman@chromium.org + + The time taken from requesting a PAC script to receiving the first byte of + the response body on successful fetches. This does not include time spent + doing proxy auto-discovery, or failed attempts at retrieving PAC scripts. If + the response body was empty, this measures the total time to fetch the + (empty) response body. + + + + + eroman@chromium.org + + The time taken to successfully fetch a PAC script. This does not include + time spent doing proxy auto-discovery, or failed attempts at retrieving PAC + scripts. + + + + + estark@chromium.org + + A validated certificate chain may be subject to additional pinning + requirements on a per-domain basis. When pinning requirements are violated, + Chrome attempts to send a report about the incident. This records the net + error code when sending a pinning violation report fails. + + + + + agl@chromium.org + + A validated certificate chain may be subject to additional + "pinning" requirements on a per-domain basis. This records the + fraction of successful matches between a certificate chain and a pin list. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Information about the value of the Vary response header in HTTP/2 pushed + streams. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of active QUIC sessions before we activate a new QUIC session. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Tracks the number of QUIC alt-svc advertisements parsed by Chrome in Google + format vs in IETF format. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The reject reasons for QUIC's CHLO (client hello) message from server + + + + + wub@chromium.org + src/net/quic/OWNERS + + The write result returned by the packet writer when the connection attempts + to write a packet. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of active sessions that are degrading on network changes. The + suffix specifies the network change. Emitted when there are more than one + active sessions. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + The number of active QUIC sessions when a network change is detected. The + suffix specifies the network change. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of all sessions that detectes path degradation until a network + change happens, including both active sessions and closed sessions. The + suffix specifies the network change. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + The total number of sessions that reports path degradation before a network + change happens, including both still active sessions and closed sessions. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + The number of total sessions that has been tracked since the first + speculative error, including both active and closed sessions. Only recorded + if non-zero. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + The number of total sessions that has been closed due to + QUIC_PACKET_WRITE_ERROR before first path degradation detection. + + The histogram is emitted when session path degrading is detected for the + first time on the current network and there was a session closed with a + speculative signal (QUIC_PACKET_WRITE_ERROR). + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The percentage of active sessions that are degrading on network changes. The + suffix specifies the network change. Emitted when there are at least two + active sessions. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The percentage of all sessions that detectes path degradation until a + network change happens, including both active sessions and closed sessions. + Always emit 0 when there is no session reporting path degrading to speculate + a connectivity failure on the current network. The suffix specifies the + network change. + + The histogram is emitted when a network change happens which could affect + the current default network, which includes the default network being + changed, alternate networks being connected. It, however, doesn't emit when + disconnecting an alternate network because that does not affect the current + default network. + + + + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + When a packet write error is detected by the session, if path degradation + has been detected already on the same session. + + The histogram is emitted when a session encounters a QUIC_PACKET_WRITE_ERROR + and is soon to be closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Tracks failure reasons to read/load/write of QuicServerInfo to and from disk + cache. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The reason a QUIC packet could not be processed, logged for each dropped + packet. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of QUIC packets received by a QUIC connection whose handshake was + not confirmed when that connection is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The state of a QUIC connection's crypto hanshake as it progresses from + starting to confirmation or failure. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The compression percentage, logged for each sent HPACK compressed header + frame. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + For each indexed representation decoded, records the time since the + corresponding entry was added to the dynamic table. This data is being + collected to help analyze a proposed solution to HPACK induced head of line + blocking. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The decompression percentage, logged for each received HPACK compressed + header frame. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + For each indexed representation encoded, records the time since the + corresponding entry was added to the dynamic table. This data is being + collected to help analyze a proposed solution to HPACK induced head of line + blocking. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Time from when QUIC detects performance degradation on the current network + to when QUIC notices a new network is connected. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Time from when QUIC detects performance degradation on the current network + to when QUIC notices the current network is disconnected. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The time from QUIC detecting network performance degradation to an + alternative network becoming default. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The time from network disconnection to an alternative network becoming + default. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of client hello messages sent. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of times ServerConfigUpdateMessages ignored. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The state of the QUIC server information when it's loaded from the disk + cache. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of pending stream requests aborted when the session is closed. + Pending streams are those which could not be created immediately because + there were too many active streams. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The number of active streams when the quic session decides to go away on + path degrading. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if the result of reading a packet from the network was ERR_IO_PENDING. + Recorded for each packet when Read() returns. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of BLOCKED frames recevied by a QuicSession when the session is + closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of BLOCKED frames sent by a QuicSession when the session is + closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code returned to a QUIC session from the CertVerifier when + a certification verification is attempted. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Time spent verifying a certificate when racing cert veriifcation with host + resolution. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The final maximum packet size of the connection used by the client before + the session is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code which resulted in all sessions being closed. + + + + + wub@chromium.org + src/net/quic/OWNERS + + For a QUIC session that is closed by a public reset, this boolean shows + whether it is a public reset sent from a Google server or not. + + + + + wub@chromium.org + fayang@chromium.org + src/net/quic/OWNERS + + For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is + the number of packets it received before it is closed. + + + + + wub@chromium.org + fayang@chromium.org + src/net/quic/OWNERS + + For a QUIC session that is closed by QUIC_TOO_MANY_RTOS at client, this is + the number of packets it sent before it is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if the QUIC session is closed during the call to InitializeSession, + logged for each session just after InitializeSession is called. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code which resulted in the session being closed. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + When a new stream frame is added to a QUIC packet, record whether it's + coalesced with the existing stream frames. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Samples of the number of round-trips needed by a QUIC connection before a + request could be sent by the client. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if a QUIC connection connected successfully after having been broken. + Only emitted after a QUIC connection attempt to a server that was previous + marked as broken. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error which caused a QUIC connection to be closed before the + hanshake was confirmed, in the case where no packets were received. This + provides a breakdown of the entires in + Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value + is BLACK_HOLE. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error which caused a QUIC connection to be closed before the + hanshake was confirmed, in the case where at least 1 packet was received. + This provides a breakdown of the entires in + Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value + is UNKNOWN. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + The reason a QUIC handshake failed. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of streams open when a QUIC session crypto handshake timed out. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of streams open when a QUIC session timed out. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of total streams created when a QUIC session crypto handshake + timed out. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the Google QUIC connection being + closed by the client. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the Google QUIC connection being + closed by the client to a server ending in .google.com. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the Google QUIC connection being + closed by the server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the Google QUIC connection being + closed by the server with a name ending in .google.com. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server with a name ending in .google.com. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server, when the GQUIC error was missing. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server with a name ending in .google.com, when the GQUIC + error was missing. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC transport error code in a CONNECTION_CLOSE frame received from the + server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server with a name ending in .google.com. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC transport error code in a CONNECTION_CLOSE frame received from the + server, when the GQUIC error was missing. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC application transport error code in a CONNECTION_CLOSE frame + received from the server with a name ending in .google.com, when the GQUIC + error was missing. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The duration of a QUIC connection starting from 1-RTT key available to + connection close. + + + + + fayang@chromium.org + src/net/quic/OWNERS + Duration of connections received PUBLIC_RESET. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Whether QUIC session's connection is flow control blocked when a PING + message is sent to server. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + True if an active session already exists for a given Ip during connection. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The result of a QUIC connection migration attempt. The suffix specifies the + cause of connection migration. + + + + + fayang@chromium.org + zhongyi@chromium.org + src/net/quic/OWNERS + + The result of connectivity probing according to different migration causes. + Recorded for every connectivity probing when attempting connection + migrations. + + + + + renjietang@chromium.org + zhongyi@chromium.org + src/net/quic/OWNERS + + Logs the state of the connection from stale host when fresh dns resolution + is completed. This histogram is only valid when race_stale_dns_on_connection + experiment is enabled. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The IP Address family of this connection, as reported by the server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + The IP Address family of this connection, as seen locally. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Samples of the number of round-trips needed by a QUIC connection before a + request could be sent by the client, when handshake confirmation was + required. (The operating system randomly selected a source port for the + connection.) + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Count of errors during attempts to create a QUIC session (before even using + the session). + + + + + fayang@chromium.org + src/net/quic/OWNERS + + Times of retransmission time out of connections with successful handshake. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + Times of crypto retransmission timeout of connections with failed handshake. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The number of draining streams when the quic session decides to go away on + path degrading. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of duplicate packets recevied by a QuicSession when the session + is closed. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + The elapsed time between starting the crypto handshake and installing the + first encryption key that can carry application data (either 0-RTT or + 1-RTT). + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + Record where exactly packet serialization fails for investigation. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the TCP cubic sender's CWND when the session is closed. + + + + + renjietang@chromium.org + zhongyi@chromium.org + src/net/quic/OWNERS + + The time for a fresh DNS resolution from DoResolveHost to having a fresh DNS + result. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + This measures the time gap between the most recent write error and the + network disconnection. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Whether QuicGoAwayFrame is received from server for connection migration due + to client's port change. Logged when a QuicGoAwayFrame with error code + QUIC_ERROR_MIGRATING_PORT is received. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The elapsed time between starting the crypto handshake, and receiving + confirmation from the server. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The handshake status when the session attempts to migrate the connection + according to different migration causes. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The handshake status when the session attempts to port migration on path + degrading. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Whether path degrading has been detected by the time a QUIC connection is + closed due to handshake timeout. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Header compression ratio as percentage for received headers using HPACK. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Header compression ratio as percentage for sent headers using HPACK. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Header compression ratio as percentage for received headers using QPACK. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Header compression ratio as percentage for sent headers using QPACK. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The elapsed time between the end of resolving the DNS name of the server for + a QUIC connection, and receiving crypto handshake confirmation from the + server. Logged after crypto handshake is confirmed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number packets recevied by a QuicSession with an incorrect connection id + when the sesesion is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The source for the initial RTT estimate recorded when a QUIC session is + created. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + Time from handshake completion to last packet was sent for connections + received PUBLIC_RESET. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + A bitfield representing the last sent packet content before connection + receives PUBLIC_RESET. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + Max consecutive retransmission timeout before making forward progress. + + + + + fayang@chromium.org + src/net/quic/OWNERS + + Max consecutive retransmission timeout before making forward progress when + blackhole has been detected. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The maximum packet sequence number reordering observed by a QUIC connection. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ratio of the maximum reordering time of a QUIC packet to the min rtt. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ratio of the maximum reordering time of a QUIC packet to the min rtt, + only for those sessions with a min rtt larger than 100 ms. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The minimum RTT observed during the life of a QUIC connection. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of MTU probes sent by the client during the session. Logged when + the connection is destroyed. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The number of active streams when idle timeout is detected and connection is + being closed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Number of connection migrations exercised before the connection receives a + public reset. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of QUIC streams opened when a new QUIC stream is created. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of pending stream requests when a new stream request is added to + the pending list. Pending streams are those which could not be created + immediately because there were too many active streams. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The number of pings a QUIC connection sends during its lifetime. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The number of streams waiting to write when idle timeout is detected and + connection is being closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The total number of streams created by the client when the session is + closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of missing packets between the current received packet and the + previously largest received packet sequence number, when the current + received packet had a lower sequence number than the previously received + packet sequence number. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times the current received packet had a lower sequence number + than the previously received packet sequence number, and the size of the + current packet is larger than the size of the previous packet. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times the current received packet had a lower sequence number + than the previously received packet sequence number. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of missing packets between the current received packet and the + previously largest received packet sequence number. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of missing packets between the last received packet before a PING + frame sent and the first packet received after PING sent. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of missing packets between the current received packet and the + previously largest received packet sequence number, as reported by the + remote end of the connection. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ratio of the number of missing packets, to the maximum packet sequence + number received, for QUIC connections longer than 21 packets received via + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of packets retransmitted per 1000. Only sessions with + packets_sent >= 100 are included. Recorded in session destructor. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The time taken to Write() a QUIC packet to the socket. Recorded for each + packet when it is sent. The suffix specifies if the write completed + synchonously or asynchronously. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The wait time of the pending stream when it is finally serviced. Pending + streams are those which could not be created immediately because there were + too many active streams. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The platform notification received by QUIC when network change happens. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + The result of a QUIC port migration attempt. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if the QUIC session prefers to use AES GCM because of hardware support. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Number of retries to send connectivity probing packet on new path until + success. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The wait time to receive a matched probing response to mark connectivity + probing as successful. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + When a public reset packet is received, whether the client IP address and + port number in it differ from the client IP address and port number in the + ServerHello handshake message. In the comparison, the first address is the + one in ServerHello and the second address is the one in public reset. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of push streams received when the session is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of pushed and used streams when the session is closed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of bytes that is pushed but not used when the session is closed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of bytes that is pushed when the session is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ordinality of a header list within a connection during the encoding of + which unacknowledged dynamic table entries could not be referenced due to + the limit on the number of blocked streams. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ordinality of a header list within a connection during the encoding of + which at least one dynamic table insertion was blocked. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ordinality of a header list within a connection during the encoding of + which no dynamic table insertion was blocked. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ordinality of a header list within a connection during the encoding of + which the limit on the number of blocked streams did not prevent referencing + unacknowledged dynamic table entries. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + Version of the QUIC protocol used for this connection. + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code returned when attempting to read from a QUIC + connection. The suffix specifies the condition/source of the read error. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The network error code returned when attempting to read on the current + network from a QUIC connection after handshake has been confirmed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the SETTINGS_QPACK_BLOCKED_STREAMS parameter received on an + HTTP/3 connection, if any. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of SETTINGS parameters received on an HTTP/3 connection, + incremented by one (the SETTINGS frame can be empty). + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the SETTINGS_MAX_HEADER_LIST_SIZE parameter received on an + HTTP/3 connection, if any. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the SETTINGS_QPACK_MAX_TABLE_CAPACITY parameter received on an + HTTP/3 connection, if any. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of reserved SETTINGS parameters (that is, with identifier in the + form 0x1f * N + 0x21 for a non-negative integer value of N) received on an + HTTP/3 connection, incremented by one (there might be zero reserved + identifiers). Defined at + https://quicwg.org/base-drafts/draft-ietf-quic-http.html#name-defined-settings-parameters. + These should not be treated specially on the receive side, because they are + sent to exercise the requirement that unknown identifiers are ignored. Here + an exception is made for logging only, to understand what kind of + identifiers are received. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if the QUIC REJ message received from the server contains a proof. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The length in bytes of a QUIC REJ message received from the server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of consecutive times a packet was retried after a write error, + using exponential backoff. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in a stream being reset by the client. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in a stream being reset by the server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of request for secure resources over QUIC sessions. True if the + session is secure, false if it is not. + + + + + zhongyi@google.com + src/net/quic/OWNERS + + When a SHLO handshake message is received, whether the client IP address and + port number in it differ from the local client IP address and port number. + In the comparison, the first address is the one in SHLO and the second + address is the client IP address. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The size in bytes of an encrypted QUIC packet sent to the peer at the + specified encryption level. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The largest packet which the client received from the server during the + session. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The final smoothed RTT observed during the life of a QUIC connection. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + True if fresh host lists contains stale host used in racing connection. + + + + + renjietang@chromium.org + zhongyi@chromium.org + src/net/quic/OWNERS + + The time a QUIC connection from invalid stale dns result takes to do Crypto + handshake. This starts on DoConnect and ends when the connection finishes. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + True if the stale host is used in racing connection. + + + + renjietang@chromium.org + src/net/quic/OWNERS + + Records when a STATELESS_RESET is received after a connectivity probing is + cancelled. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + When probing is cancelled, records whether a STATELESS_RESET is received. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the stream (and connection) being + closed by the client after the handshake was confirmed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the stream (and connection) being + closed by the client after the handshake was confirmed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Whether any of QUIC session's streams are flow control blocked when a PING + message is sent to server. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of stream frames received which were duplicates, out of every + 1000 stream frames received. Only for QUIC sessions which received at least + 100 packets. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The percentage of stream frames received which were duplicates. Only for + QUIC sessions which received at least 100 packets. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The percentage of stream frames received which were duplicates. Only for + QUIC sessions which received fewer than 100 packets. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of stream frames received which were duplicates, out of every + 1000 stream frames received. Only for QUIC sessions which received fewer + than 100 packets. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + If a QUIC connection timed out with open streams, this contains a count of + consecutive RTOs. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + If a QUIC connection timed out with open streams, this contains a count of + consecutive TLPs. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + If a QUIC connection timed out with open streams, this will be true when the + connection has unacked packets. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + If a QUIC connection timed out locally with open streams, this contains the + local port number for the connection. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + The time a QuicStreamFactory Job takes from host rersolution to connection + confirmation. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if more than 100 streams are open when a new stream is activated. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + When a QUIC packet is sent at initial encryption that is smaller than the + minimum size, this records the size difference (minimum_size - + observed_size). + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of undecryptable packets recevied by a QuicSession when the + sesesion is closed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The location in quic_client_session.cc where a session is unexpectedly not + going away. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The location in quic_client_session.cc where there were unexpected + observers. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The location in quic_client_session.cc where there were unexpected open + streams. + + + + + renjietang@chromium.org + zhongyi@chromium.org + src/net/quic/OWNERS + + The time a QUIC connection that will be confirmed takes for Crypto + handshake. The event starts on DoConnect, and ends when the connection + finishes. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Time spent verifying the signature and certificate chain. This is logged + whenever QUIC verifies the certificate chain and signature during crypto + handshake. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code returned when attempting to write to a QUIC + connection. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The network error code returned when attempting to write to a QUIC + connection after the handshake has been confirmed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The most recent network error code when attempting to write to a QUIC + connection when the network gets disconnected. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + The reason QUIC packet writer needed to allocate a new buffer, rather than + the expected case of reusing its existing one. + + + + + nharper@chromium.org + src/net/quic/OWNERS + + Indicates whether a QUIC handshake attempted or used 0-RTT on the + connection, and if 0-RTT was not used, it provides reasons why. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + Indicates whether a QUIC handshake attempted or used 0-RTT on the + connection, and if 0-RTT was not used, it provides reasons why. Only records + connections with Google hosted servers. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + + Indicates whether a QUIC handshake attempted or used 0-RTT on the + connection, and if 0-RTT was not used, it provides reasons why. Only records + connections with non-Google servers. + + + + + renjietang@chromium.org + src/net/quic/OWNERS + Whether 0-RTT was successfully used in the connection. + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Records if a new connection on the alternate network is attempted when a + connection fails before handshake is confirmed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Connection type of the default network when the connection fails with + handshake not confirmed. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + A count of how often a user hits 1, 2, 3, 4 and 5 bad packet loss events for + port 443. Recorded whenever QUIC has bad packet loss (high packet loss on + multiple consecutive connections). + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Status of the connection on the non-default network when it finishes. A + connection may stay on the non-default network during the initial setup when + the platform's default network changes. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Records, for initial socket created for each new QUIC connection, whether + the bound network matched the default network tracked by QuicStreamFactory. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Rrecords reasons QUIC is disabled (for all ports), if sufficent recent + connections experience: public reset post crypto handshake, or timeouts with + streams open. QUIC is disabled until the next reboot of Chrome. Logged + during session close. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Connection type of the alternate network when a connection is about to be + attempted when the original connection fails on the default network with + handshake not confirmed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Status of the connection which is created for migration before handshake is + confirmed. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + The network error code returned when the retried connection on the alternate + network before handshake fails. + + + + + zhongyi@chromium.org + src/net/quic/OWNERS + + Captures whether the default network has been changed when the new + connection succeeds on the "alternate" network. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Captures the maximum number of public resets post handshake that occurred + within a window of recent connections (default 20). Will help inform the + choice of threshold to disable QUIC for clients that experience pathalogical + errors. Logged during session close. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Recorded whenever QUIC is disabled for a port due to repeated lossy + connections (high packet loss on multiple consecutive connections). QUIC is + disabled until next reboot of Chrome. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + Captures the maximum number of connection timeouts with streams open that + occurred within a window of recent connections (default 20). Will help + inform the choice of threshold to disable QUIC for clients that experience + pathalogical errors. Logged during session close. + + + + + vasilvv@chromium.org + src/net/quic/OWNERS + + The Google QUIC error code which resulted in the QuicTransport connection + being closed by the client. + + + + + vasilvv@chromium.org + src/net/quic/OWNERS + + The Google QUIC error code which resulted in the QuicTransport connection + being closed by the server. + + + + + vasilvv@chromium.org + src/net/quic/OWNERS + + The error code for cases when QuicTransport failed to establish a + connection. + + + + + vasilvv@chromium.org + src/net/quic/OWNERS + The code for QuicTransport errors. + + + + vasilvv@chromium.org + src/net/quic/OWNERS + + The state at which establishing a QuicTransport connection has failed. + + + + + vasilvv@chromium.org + src/net/quic/OWNERS + + The state at which the QuicTransportClient has been marked as failed. + + + + + csharrison@chromium.org + rsleevi@chromium.org + + The total number of redirects encountered during processing a URLRequest. + This includes redirects generated by servers (for example, 302 Found) and + redirects generated internally (for example, HSTS redirects or error pages). + + + + + eustas@chromium.org + + True for redirect responses with unadvertised "Content-Encoding". + False for valid redirect responses. See http://crbug.com/714514 + + + + + chlily@chromium.org + juliatuttle@chromium.org + + The outcome of Reporting trying to deliver a report, recorded when the + report is finally erased from memory. + + + + + clamy@chromium.org + + When starting a cross-site navigation, the time between reading the headers + and body of the response. + + + + + morlovich@chromium.org + chlily@chromium.org + + Logged on any document.cookie or CookieStore API operation. True if the + browser-side site_for_cookies and the render-provided value match. + + + + + morlovich@chromium.org + chlily@chromium.org + + Logged on any document.cookie or CookieStore API operation. True if the + browser-side top_frame_origin and the render-provided value match. + + + + + chlily@chromium.org + morlovich@chromium.org + + The site engagement level of a frame that triggers the + CookieInsecureAndSameSiteNone warning, whether the cookie was actually + blocked or not. Recorded every time one or more cookies triggers the + warning. + + + + + chlily@chromium.org + morlovich@chromium.org + + The site engagement level of a frame that triggers the CookieNoSameSite + warning, whether the cookie was actually blocked or not. Recorded every time + one or more cookies triggers the warning. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The size of a socket's receive buffer when the attempt to change it via + setsockopt failed. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The size of a socket's send buffer when the attempt to change it via + setsockopt failed. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The counts of the flow control state of each frame (with stream and session + flow control on). + + + + + dschinazi@chromium.org + src/net/OWNERS + + The percent compression achieved when compressing HEADERS frames. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The compression percentage in received HPACK compressed header frames. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Status of checking if a SPDY domain can handle a IP match. If a match is + found, we successfully used the IP Pooling. If a match is not found, we + could have used IP Pooling, except the TLS Cert didn't match the IP-pooled + domain. + + + + + dschinazi@chromium.org + src/net/OWNERS + + This histogram is recorded exactly once for every PUSH_PROMISE frame + received on an HTTP/2 connection, and tracks the fate of the pushed stream. + + + + + dschinazi@chromium.org + src/net/OWNERS + + HTTP status codes received in HTTP/2 HEADERS frames. If a stream contains + one or more informational (1xx) response preceeding the main response, each + status code is logged separately. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Net error codes when SpdySession was closed, doesn't inlcuding net::OK. + + + + + dschinazi@chromium.org + src/net/OWNERS + Socket connected status in SpdySession::CreateStream. + + + + zhongyi@chromium.org + src/net/OWNERS + + The number of bytes that is pushed but not used when the session is closed. + + + + + zhongyi@chromium.org + dschinazi@chromium.org + src/net/OWNERS + + The number of bytes that is pushed when the session is closed. + + + + + dschinazi@chromium.org + src/net/OWNERS + + Whether the server has advertised support for WebSockets over HTTP/2. + + + + + dschinazi@chromium.org + src/net/OWNERS + The type of SPDY Protocol error encountered. + + + + dschinazi@chromium.org + src/net/OWNERS + + WARNING: r181910 added an enum value in the middle, so don't trust the + counts for values 9 and above for Chrome builds after that revision. + + The type of SPDY Protocol error encountered when talking to a google.com + server. + + + + + dschinazi@chromium.org + src/net/OWNERS + The type of SPDY Session used when looking up a session. + + + + dschinazi@chromium.org + src/net/OWNERS + + Whether SpdySession::Get{Peer,Local}Address was called when the connection + had no socket. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The number of pushed, but abandoned streams over a single session. + + + + + dschinazi@chromium.org + src/net/OWNERS + The number of streams issued over a single session. + + + + dschinazi@chromium.org + src/net/OWNERS + + The number of pushed, and used streams over a single session. + + + + + dschinazi@chromium.org + src/net/OWNERS + The number of push streams received over a single session. + + + + + + agl@chromium.org + rsleevi@chromium.org + + The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS + connection in the socket pool where Connect() succeeds. + + + + + + + agl@chromium.org + + Counts of specific error codes returned when opening an SSL connection. + + + + + svaldez@chromium.org + + Counts of specific error codes returned when opening an SSL connection for + an endpoint we are using in the initial TLS 1.3 deployment. + + + + + + + agl@chromium.org + Time from when the Connect() starts until it completes. + + + + svaldez@chromium.org + + Time from when the Connect() starts until it completes for a set of domains + that we are using in the initial TLS 1.3 deployment. + + + + + + + agl@chromium.org + rsleevi@chromium.org + sigbjorn@opera.com + + The curve used for key exchange for ECDHE. Recorded for each SSL/TLS + connection in the socket pool where Connect() succeeds. + + + + + rsleevi@chromium.org + Time to complete a certificate verification (success case). + + + + rsleevi@chromium.org + Time to complete a certificate verification (error case). + + + + davidben@chromium.org + src/net/OWNERS + + For each successful TLS handshake, what kind of handshake was used. This + metric distinguishes TLS 1.2 (or earlier) and TLS 1.3 as they have very + different resumption and round-trip behaviors. It also distinguishes full + handshakes, resumption, 0-RTT, and False Start. + + + + + davidben@chromium.org + svaldez@chromium.org + src/net/OWNERS + + Indicates whether a TLS 1.3 connection with 0-RTT enabled ended up using + 0-RTT or not, and why; this includes reasons such as the server declining to + resume the connection and the client not having enough tickets available. + + + + + cthomp@chromium.org + + Counts when the SSLKEYLOGFILE environment variable or --ssl-key-log-file + command-line flag are set, and when they enable the SSLKeyLogger feature. + + + + + davidben@chromium.org + src/net/OWNERS + + For each TLS connection, whether it needed the legacy crypto fallback and a + classification as to why. See https://crbug.com/658905 and + https://crbug.com/691888. Note some connections are reported as sending + SHA-1 certificates because, although SHA-1 is no longer accepted in + certificates, servers may send unused certificates in the handshake. Some + such servers additionally match their certificate chains against the + ClientHello. These servers require the client advertise legacy algorithms + despite not actually using them. + + + + + dschinazi@chromium.org + src/net/OWNERS + + For each TLS handshake, whether ALPN was negotiated; and if so, the + negotiated protocol. + + + + + davidben@chromium.org + + For each TLS connection which uses a unknown root, an RSA key, and TLS 1.2 + or below, what the result of checking the RSA key usage would have been. + + + + + + + davidben@chromium.org + src/net/OWNERS + + For each SSL connection with a full handshake using a DHE- or ECDHE-based + key exchange, the signature algorithm used to authenticate the peer. In TLS + 1.2, this is the signature on the ServerKeyExchange message. (Note: Although + the ECDSA values specify a curve, the curve is only enforced in TLS 1.3.) + + + + + + + davidben@chromium.org + + The SSL/TLS version that was negotiated. Recorded for each SSL/TLS + connection in the socket pool where Connect() succeeds. + + + + + davidben@chromium.org + rsleevi@chromium.org + + The SSL/TLS version that was negotiated to a Google host. Recorded for each + appplicable SSL/TLS connection in the socket pool where Connect() succeeds. + Google servers all support TLS 1.2, so any occurrences of TLS 1.0 or TLS 1.1 + indicate an outdated insecure TLS MITM proxy, such as some antivirus + configurations. TLS 1.0 and 1.1 are deprecated, so record these to see how + prevalent they are. See https://crbug.com/896013. + + + + + + + mmenke@chromium.org + + Time from when the Connect() starts until it completes. Only times under 10 + minutes are logged. + + + + + mgersh@chromium.org + + Time from when the Connect() starts until it completes when the network + address only contains IPv4 addresses. Only times under 10 minutes are + logged. + + + + + mgersh@chromium.org + + Time from when the Connect() starts until it completes when the IPv4 + fallback connection won the race against IPv6. Only times under 10 minutes + are logged. + + + + + mgersh@chromium.org + + Time from when the Connect() starts until it completes when we race an IPv6 + connection against an IPv4 connection with a 300ms delay. Only times under + 10 minutes are logged. + + + + + mgersh@chromium.org + + Time from when the Connect() starts until it completes when the network + address only contains IPv6 addresses. Only times under 10 minutes are + logged. + + + + + eroman@chromium.org + src/net/OWNERS + + Time taken when failed to establish a TCP connection to an individual + endpoint. This includes the case when the attempt was aborted by a higher + layer (likely because it took too long). + + + + + eroman@chromium.org + src/net/OWNERS + + Time taken to successfully establish a TCP connection to an individual + endpoint. + + + + + eroman@chromium.org + src/net/OWNERS + + Time taken when failed to establish a TCP connection to an individual + endpoint, expressed as a multiple of the transport RTT. This includes the + case when the attempt was aborted by a higher layer (likely because it took + too long). This may have fewer samples than Net.TcpConnectAttempt.Latency.* + in cases where the network quality estimation was unknown. + + + + + eroman@chromium.org + src/net/OWNERS + + Time taken to successfully establish a TCP connection to an individual + endpoint, expressed as a multiple of the transport RTT. This may have fewer + samples than Net.TcpConnectAttempt.Latency.* in cases where the network + quality estimation was unknown. + + + + + bmcquade@chromium.org + + The kernel's estimated TCP round trip time. Recorded for each TCP socket, at + the time it is disconnected. + + + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + The //net status codes for resource requests that had started Trust Tokens + operations. This captures the reasons why requests with Trust Tokens + operations fail and might help debug a surfeit of "TypeError: failed to + fetch" observed in live testing. + + + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + Time taken to execute a Trust Tokens operation's outbound Begin half (see + network::TrustTokenRequestHelper). + + + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + Time time to taken a Trust Tokens operation's inbound Finalize half (see + network::TrustTokenRequestHelper). + + + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + Time between finishing a Trust Tokens Tokens operation's outbound Begin half + and beginning its inbound Finalize half (see + network::TrustTokenRequestHelper). + + + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + Time elapsed from the beginning of a Trust Tokens operation's outbound Begin + half to the end of its inbound Finalize half (see + network::TrustTokenRequestHelper), when the operation succeeded overall. + + + + + davidvc@chromium.org + privacy-sandbox-dev@chromium.org + + For a Trust Tokens operation associated with a subresource request, stores + whether the browser believed the frame had the Feature Policy feature + necessary for executing the operation. + + + + + mgersh@chromium.org + Chromium error code from call to RandomBind() UDP socket. + + + + dschinazi@chromium.org + src/net/OWNERS + The time spent in closesocket call in UDPSocketWin::Close. + + + + + + davidvc@chromium.org + kaustubhag@chromium.org + + Records for each URLRequest whether its referrer contains more information + than just its origin (this is the case exactly when it has at least one + character apart from a leading slash in its path, e.g. http://example.com/a + but not http://example.com/ nor http://example.com). + + + + + + + davidvc@chromium.org + kaustubhag@chromium.org + + Records the distribution of referrer policies provided with outgoing + URLRequests, and whether or not the requests were cross-origin. + + + + + estark@chromium.org + + Records the usage of the Referrer-Policy header on redirect responses. This + histogram is recorded on each HTTP redirect response, with the value true if + a Referrer-Policy header was present and false otherwise. + + + + + ricea@chromium.org + yhirano@chromium.org + yoichio@chromium.org + + Records the status code with which WebSockets are closed. Logged once for + every successfully opened WebSocket. Includes codes "No Status + Rcvd" and "Abnormal Closure" which are never sent over the + wire but generated internally. See RFC6455 section 7.4.1 for the meanings of + the codes. Newer codes are documented at + https://www.iana.org/assignments/websocket/websocket.xhtml#close-code-number. + Codes that have not been standardised are bucketed to save storage space. + Used to determine if changes in framing change the error rate. + + + + + + + yhirano@chromium.org + ricea@chromium.org + + Positive net error codes that WebSockets end with, including OK and ABORTED. + + + + + + + yhirano@chromium.org + ricea@chromium.org + src/net/OWNERS + + Results of WebSocket handshakes, including information whether the handshake + happened over HTTP/2. Use this histogram as a baseline for investigating + feature usage counters. + + + + + + + yhirano@chromium.org + ricea@chromium.org + All HTTP status codes seen during WebSocket handshakes. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/network/histograms.xml b/tools/metrics/histograms/histograms_xml/network/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..cfa01c2accd32d4173ea2718333b50d9eaf7713f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/network/histograms.xml @@ -0,0 +1,2290 @@ + + + + + + + + + + stevenjb@chromium.org + benchan@chromium.org + The time the Gobi modem takes to complete activation. + + + + stevenjb@chromium.org + benchan@chromium.org + + The time the Gobi modem takes to connect to the cellular network. + + + + + stevenjb@chromium.org + benchan@chromium.org + + The time the Gobi modem takes to disconnect from the cellular network. + + + + + stevenjb@chromium.org + benchan@chromium.org + Number of attempts taken to install Gobi firmware. + + + + stevenjb@chromium.org + benchan@chromium.org + The time it takes to install Gobi firmware. + + + + stevenjb@chromium.org + benchan@chromium.org + + The time the Gobi modem takes to register on the cellular network. + + + + + stevenjb@chromium.org + benchan@chromium.org + Errors experienced during Gobi device powerup. + + + + azeemarshad@chromium.org + cros-system-services-networking@google.com + + Tracks the Cellular network activation state when the primary user logs-in + to the device. + + + + + azeemarshad@chromium.org + cros-system-services-networking@google.com + + Tracks when cellular network is connected and when cellular network is + disconnected without explicit user action. + + + + + azeemarshad@chromium.org + cros-system-services-networking@google.com + + Tracks the amount fo time taken between when cellular device starts and + finishes connecting. + + + + + azeemarshad@chromium.org + cros-system-services-networking@google.com + + Tracks the number of times a cellular network is connected as the only + network, or with other network or not connected at all. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of cellular network + flakes. A network flake occurs when the signal strength goes below detection + level for a short duration. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the total amount of time spent + from the start of the first auto-connect request until when the cellular + modem successfully connects to the network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of auto-connect + tries that were attempted before the cellular modem successfully connected + to the network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the presence of a Cellular device in + the system. A sample is emitted once every 3 minutes. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks whether the cellular network was + disconnected due to an error or was explicitly disconnected by the user. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS cellular network metric that tracks the number of drops based on + the network technology. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the length of a lease for a + cellular network at the time it expired without the DHCP client being able + to renew it. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the presence of complete IPv6 + configuration at the time when cellular connection is established. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the types of IP configuration used for + establishing cellular connections. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS cellular network metric that tracks the number of out-of-credits + detected based on the cause that triggered the out-of-credits. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of portal detection + attempts per pass for a cellular network. This includes failure, timeout and + successful attempts. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the total number of portal + detection attempts performed for a cellular network between the Connected + and Online state. This includes failure, timeout and successful attempts. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the result of portal detections + for a cellular network. + + + + + kuabhs@chromium.org + cros-network-metrics@google.com + + Chrome OS connection manager service errors for cellular interface. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the signal strength (0-100) of the + cellular modem before it dropped from the network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the time spent using cellular to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to join a cellular + network and configure Layer 3 state. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to connect a cellular + modem. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to disable a cellular + modem. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to enable a cellular + modem. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to initialize a + cellular modem. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that a + cellular network is online after configuring Layer 3 state. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that a + cellular network is in a captive portal after configuring Layer 3 state. + + + + + matthewmwang@chromium.org + hugobenichi@chromium.org + + Chrome OS network performance metric sampling the time to determine that a + cellular network is in a captive portal with a valid redirect URL after + configuring Layer 3 state. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to scan a cellular + network and register a modem. + + + + + stevenjb@chromium.org + benchan@chromium.org + + Chrome OS network metric that tracks the connectivity issue diagnosed by the + ConnectionDiagnostics class in Shill. This metric is logged each time a + ConnectionDiagnostics object completes its diagnostics actions and reports + the results to its caller. + + + + + stevenjb@chromium.org + benchan@chromium.org + + Chrome OS cellular network metric that tracks the number of corrupted + profiles encountered by Shill. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS device time on line in the previous 24-hour sample period. + "On line" means shill believes the device is on the internet. The + shill state is sampled every 5 minutes. The start of each 24-hour period is + the end of the previous period, unless the device is inactive at that time + (suspended or off), in which case it is the time of the next + resume/power-on. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS fraction of daily cumulative time on a cellular connection when + both cellular and WiFi adaptors are available. Each sample is the ratio of + the corresponding DailyChosenTimeOnLine.{Cellular,Any} samples. Reported + only when both a cellular and a WiFi adaptor are present (independently of + whether they would both be able to connect). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS fraction of daily cumulative time on a WiFi connection when both + cellular and WiFi adaptors are available. Each sample is the ratio of the + corresponding DailyChosenTimeOnLine.{Cellular,Any} samples. Reported only + when both a cellular and a WiFi adaptor are present (independently of + whether they would both be able to connect). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS daily cumulative time on line when both cellular and WiFi adaptors + are available. Reported only when both kinds of adaptor are present + (independently of whether they would both be able to connect). Each sample + contains the total on-line time in the 24-hour slot following the previous + sample. The time granularity is 5 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS daily cumulative time on a cellular connection when both cellular + and WiFi adaptors are available. Reported only when both kinds of adaptor + are present (independently of whether they would both be able to connect). + Each sample contains the total on-line time in the 24-hour slot following + the previous sample. The time granularity is 5 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS daily cumulative time on a WiFi connection when both cellular and + WiFi adaptors are available. Reported only when both kinds of adaptor are + present (independently of whether they would both be able to connect). Each + sample contains the total on-line time in the 24-hour slot following the + previous sample. The time granularity is 5 minutes. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of dark resume + actions that successfully complete or fail when shill suspends. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes dark resume actions to complete when shill suspends. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of times a dark resume scan is + retried in a single dark resume. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks whether dark resume scan retries led to + the system suspending from dark resume in a connected state. This metric is + only recorded in dark resumes when at least one dark resume scan retry was + launched. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the connection status of + the device. A sample is emitted once every 3 minutes. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the network device removed events for + each device type. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the MTU value proposed by the + DHCP server. A sample is emitted each time the DHCP client completes + negotiation with a server. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the current state of the DHCP + client. A sample is emitted each time the DHCP client state changes. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the number of DHCP option failures + encountered by Shill for each network technology. This indicates that Shill + is using minimal DHCP options due to suspected MTU issues on the return path + from the DHCP server back to the client. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the presence of an Ethernet device in + the system. A sample is emitted once every 3 minutes. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks whether the Ethernet network was + disconnected due to an error or was explicitly disconnected by the user. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the length of a lease for + an Ethernet network at the time it expired without the DHCP client being + able to renew it. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of LinkMonitor + broadcast errors that were accrued on an Ethernet network at the time that + the link was declaired to be failed. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS metric that signals the type of failure the LinkMonitor + encountered which caused it to stop monitoring an Ethernet network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of milliseconds + between an ARP request and a received reply on an Ethernet network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of seconds from + the start of the LinkMonitor until failure on an Ethernet network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of LinkMonitor + unicast errors that were accrued on an Ethernet network at the time that the + link was declaired to be failed. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of portal detection + attempts per pass for an Ethernet network. This includes failure, timeout + and successful attempts. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the total number of portal + detection attempts performed for an Ethernet network between the Connected + and Online state. This includes failure, timeout and successful attempts. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the result of portal detections + for an Ethernet network. + + + + + kuabhs@chromium.org + cros-network-metrics@google.com + + Chrome OS connection manager service errors for ethernet interface. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the time spent using Ethernet to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to join a wired + Ethernet network and configure Layer 3 state (typically acquire a DHCP + lease). + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to initialize an + Ethernet device. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that an + Ethernet network is online after configuring Layer 3 state. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that an + Ethernet network is in a captive portal after configuring Layer 3 state. + + + + + matthewmwang@chromium.org + hugobenichi@chromium.org + + Chrome OS network performance metric sampling the time to determine that an + Ethernet network is in a captive portal with a valid redirect URL after + configuring Layer 3 state. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS fraction of monthly cumulative time on a cellular connection when + both cellular and WiFi adaptors are available. Each sample is the ratio of + the corresponding MonthlyChosenTimeOnLine.{Cellular,Any} samples. Reported + only when both a cellular and a WiFi adaptor are present (independently of + whether they would both be able to connect). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS fraction of monthly cumulative time on a WiFi connection when both + cellular and WiFi adaptors are available. Each sample is the ratio of the + corresponding MonthlyChosenTimeOnLine.{Cellular,Any} samples. Reported only + when both a cellular and a WiFi adaptor are present (independently of + whether they would both be able to connect). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS monthly cumulative time on line when both cellular and WiFi + adaptors are available. Reported only when both kinds of adaptor are present + (independently of whether they would both be able to connect). Each sample + contains the total on-line time in the 30-day slot following the previous + sample. The time granularity is 5 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS monthly cumulative time on a cellular connection when both + cellular and WiFi adaptors are available. Reported only when both kinds of + adaptor are present (independently of whether they would both be able to + connect). Each sample contains the total on-line time in the 30-day slot + following the previous sample. The time granularity is 5 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS monthly cumulative time on a WiFi connection when both cellular + and WiFi adaptors are available. Reported only when both kinds of adaptor + are present (independently of whether they would both be able to connect). + Each sample contains the total on-line time in the 30-day slot following the + previous sample. The time granularity is 5 minutes. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric recording portal detection results of both the HTTP + and HTTPS probes. This is recorded every time a portal detection trial + finishes. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the MTU value provided by the + upstream PPP peer. A sample is emitted each time the client successfully + negotiates an MTU value via PPP. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS connection manager service errors across all technologies. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of services that are connected + to the currently connected network. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of suspend actions + that successfully complete or fail when shill suspends. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes suspend actions to complete when shill suspends. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of termination + actions that successfully complete or fail when shill terminates. Previously + deprecated in 10/2012 and brought back in 10/2014. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes termination actions to complete when shill terminates. + + + + + stevenjb@chromium.org + benchan@chromium.org + cros-network-metrics@google.com + + Chrome OS network stability metric sampling the time in seconds between the + networking going online to going offline. Offline events due to device + shutdown or suspend are ignored (along with the online time before that + offline event). + + + + + stevenjb@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the number of user-initiated events. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled on each successful VPN connection + that tracks the VPN connection type. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled on each successful VPN connection + that tracks the remote authentication method. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the time spent using VPN to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). A sample is emitted + every time the system transitions from primary connectivity through a VPN to + some other type of connectivity. The value of the sample is the time delta + in seconds from the instant the system transitioned to VPN connectivity. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on a VPN network (typically acquire a DHCP lease). + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that a + VPN connection is online after configuring Layer 3 state. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled on each successful VPN connection + that tracks the user authentication method. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of Wireless Access Points that + support the 802.11k standard, sampled on successful connections to an AP. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of Wireless Access Points that + support the 802.11r standard, sampled on successful connections to an AP. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of Wireless Access Points that + support the 802.11v BSS Max Idle Period feature, sampled on successful + connections to an AP. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of Wireless Access Points that + support the 802.11v BSS Transition feature, sampled on successful + connections to an AP. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of Wireless Access Points that + support the 802.11v DMS feature, sampled on successful connections to an AP. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled when an AP switches channels. Shows + the old frequency band and the new frequency band. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Reason code reported when the AP disconnects + a WiFi connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Broad category of reason AP disconnected a + WiFi connection. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Status code reported when an 802.11 + association fails. Note that not all disconnects are caused by an assoc + failure, and so this metric shold not be correlated with the DisconnectType + metrics. + + + + + akhouderchah@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Status code reported when an 802.11 + authentication fails. Note that not all disconnects are caused by an auth + failure, and so this metric should not be correlated with the DisconnectType + metrics. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of wifi services available for + auto-connect when auto-connect is initiated for wifi device. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of BSSes (endpoints) available + for the currently connecting wifi service. + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric recording BSS Transition Management statuses. This + is recorded every time a BSS Transition Management request is received from + a wireless access point. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. The channel used for each successful WiFi + connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Reason code reported when the client + disconnects a WiFi connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. Broad category of reason client disconnected + a WiFi connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks whether any unmatched scan results are + received during dark resume cycles. An unmatched scan result is a set of + scan results received by shill in response to a scan request that was not + sent directly by shill in the same dark resume cycle. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the wake reason for dark resume. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the presence of a WiFi device in the + system. A sample is emitted once every 3 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks whether an 802.11 wireless + network was disconnected due to an error or was explicitly disconnected by + the user. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled on each successful 802.1x wireless + connection that tracks the configured inner authentication method. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric sampled on each successful 802.1x wireless + connection that tracks the configured outer authentication method. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the length of a lease for a + WiFi network at the time it expired without the DHCP client being able to + renew it. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the result of the fallback + DNS test. The fallback DNS test is performed when portal detection failed + due to DNS failure. + + + + + tnagel@chromium.org + cros-network-metrics@google.com + cros-privacy-core@google.com + + Chrome OS network metric tracking WiFi networks configured with hidden SSID. + The metric includes networks from system and user profile and it's recorded + each time a user configuration profile is loaded, such as when a user logs + in. The fraction of non-zero buckets should roughly correspond to the + fraction of devices that are trying to connect to hidden SSIDs at any given + point in time. + + + + + kglund@google.com + cros-network-metrics@google.com + + Chrome OS network metric that tracks the Hotspot 2.0 support of access + points that devices connect to. Results are recorded every time a device + connects to an access point. The metric records either the HS20 version the + AP supports, or that the AP does not support HS20. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the presence of complete IPv6 + configuration at the time when WiFi connection is established. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of LinkMonitor + broadcast errors that were accrued on an 802.11 wireless network at the time + that the link was declared to be failed. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS metric that signals the type of failure the LinkMonitor + encountered which caused it to stop monitoring an 802.11 wireless network. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of milliseconds + between an ARP request and a received reply on an 802.11 wireless network. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of seconds from + the start of the LinkMonitor until failure on an 802.11 wireless network. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the number of LinkMonitor + unicast errors that were accrued on an 802.11 wireless network at the time + that the link was declaired to be failed. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks the types of IP configuration used for + establishing WiFi connections. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the network problems + encountered by TrafficMonitor after WiFi connection is established. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. The channel type used for each successful + WiFi connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of portal detection + attempts per pass for an 802.11 wireless network. This includes failure, + timeout and successful attempts. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the total number of portal + detection attempts performed for an 802.11 wireless network between the + Connected and Online state. This includes failure, timeout and successful + attempts. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the result of portal detections + for an 802.11 wireless network. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks which country the WiFi regulatory + domain is set to. Recorded every time a WiFi regulatory domain change is + triggered or determined initially (Shill startup). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of 802.11 wireless + networks known by the connection manager at the time a configuration profile + has been loaded. A configuration profile is loaded at each system startup, + and when a user logs in. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of 802.11 wireless networks + configured from the system configuration profile. This metric is sampled + each time a user configuration profile is loaded, such as when a user logs + in. + + It might be surprising to have a system configuration profile metric sampled + when a user configuration profile is loaded. But this ensures that we have + equal numbers of samples for system and user configuration profiles. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the number of 802.11 wireless networks + configured from a user configuration profile. This metric is sampled each + time a user configuration profile is loaded, such as when a user logs in. + + + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric recording roam successes or failures. This is + recorded every time a client succeeds or fails to roam from one wireless + access point to another. + + + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric recording roam time in milliseconds. This is + recorded every time a successful roam from one wireless access point to + another occurs. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric describing, for a WiFi scan attempt, what + scan method is used and whether it ends in a connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric describing, for a WiFi scan attempt, how many + milliseconds were spent waiting to talk to the kernel/drivers. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric. The security setting for each successful + WiFi connection. + + + + + kuabhs@chromium.org + cros-network-metrics@google.com + + Chrome OS connection manager service errors for wifi interface. + + + + + + + matthewmwang@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric recording session length in milliseconds. This is + recorded every time an uninterrupted session with a wireless access point is + terminated. + + + + + silberst@google.com + cros-network-metrics@google.com + + Chrome OS network metric indicating the negative of the dBm received signal + strength recorded at the time of a WiFi disconnect. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric indicating the negative of the dBm received signal + strength recorded at the time a successful WiFi connection started. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric indicating the maximal length of any stopped + mac80211 transmit queue. The metric is reported when a queue-status check + determines that at least one transmit queue is stopped, and has more than a + threshold number of frames queued. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric indicating the reason that mac80211 transmit queues + were stopped. The metric is reported when a queue-status check determines + that at least one queue is stopped, and has more than a threshold number of + frames queued. + + One measurement is reported per stop reason, per queue-status check. Reasons + that apply to multiple queues are reported only once per queue-status check. + Reasons that only apply to queues that have a below-threshold number of + frames are skipped. + + Note that, because we may report multiple stop reasons for a single + queue-status check, this histogram is not suitable for determining the + number of times a queue-status check found that the queues were stopped. To + determine that number, use the count of + Network.Shill.WiFi.StoppedTxQueueLength reports. + + + + + briannorris@chromium.org + chromeos-kernel-wifi@google.com + cros-network-metrics@google.com + + Number of attempts required for a WiFi device to be established with WPA + supplicant (shill retries on failure). This metric is reported either on + success, reporting the number of attempts performed; or after repeated + failures (currently 6), we give up and report an artificial maximum (10). + + Thus, a value of 10 means we aborted after repeated failures. Values of 1 to + 6 represent successful connections on the first to sixth try. Values of 7 to + 9 (which should not occur) represent successful connections after seven or + more attempts (success reports are capped at 9). + + + + + semenzato@chromium.org + briannorris@chromium.org + cros-network-metrics@google.com + + Time spent in suspended state, on a resume, for the case when wake on wifi + is disabled (WoWOff), and after resume, the NIC is found to be already + connected. + + + + + semenzato@chromium.org + briannorris@chromium.org + cros-network-metrics@google.com + + Time spent in suspended state, on a resume, for the case when wake on wifi + is enabled (WoWOff), and after resume, the NIC is found to be disconnected. + + + + + semenzato@chromium.org + briannorris@chromium.org + cros-network-metrics@google.com + + Time spent in suspended state, on a resume, for the case when wake on wifi + is enabled (WoWOn), and after resume, the NIC is found to be already + connected. + + + + + semenzato@chromium.org + briannorris@chromium.org + cros-network-metrics@google.com + + Time spent in suspended state, on a resume, for the case when wake on wifi + is enabled (WoWOn), and after resume, the NIC is found to be disconnected. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the time spent using WiFi to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time from the resume event + to the time when an 802.11 wireless network has configured its Layer 3 + state. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on an 802.11 wireless network (typically acquire a DHCP lease). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to connect to a WiFi + Basic Service Set (which consists of the access point and associated + stations on a particular WiFi channel for a specific network). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to initialize an + 802.11 wireless device. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to join (associate + plus authenticate) an 802.11 wireless network. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that an + 802.11 wireless network is online after configuring Layer 3 state. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that an + 802.11 wireless network is in a captive portal after configuring Layer 3 + state. + + + + + matthewmwang@chromium.org + hugobenichi@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to determine that an + 802.11 wireless network is in a captive portal with a valid redirect URL + after configuring Layer 3 state. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time to scan WiFi until a + connection is found. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric sampling the time between the beginning + of a WiFi scan (if the scan includes both a progressive scan and a full + scan, the TimeToScanAndConnect starts with the first scan of the series) and + the completion of a successful connection. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the transmit bitrate in + Mbps for the wifi device when it is connected to a network. The bitrate is + reported once every minute after the wifi connection is established. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric sampling the signal strength (0-100) of the wifi + network when it becomes unreliable (experiencing multiple link failures in a + short period of time). + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the reasons of failed + user-initiated WiFi connection attempts. The result of the user-initiated + WiFi connection attempts are being tracked by + Network.Shill.WiFi.UserInitiatedConnectionResult. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network performance metric that tracks the result of + user-initiated WiFi connection attempts. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the number of times NIC wake on + WiFi settings verification succeeds or fails in shill. This metric is + recorded every time wake on WiFi settings are requested and verified after + the NIC is programmed with wake on WiFi settings. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks the wake on WiFi features that + are enabled in shill. Recorded once every 10 minutes. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks whether wake on WiFi was disabled + during a period of system suspension because of too many dark resume wakes. + This metric is only recorded for system suspends where wake on WiFi + functionality has been programmed into the NIC. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network metric that tracks whether a wake reason was received + during dark resume before executing WakeOnWiFi::OnDarkResume. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network usage metric that tracks the WiFi connection status after + waking from suspend, both when wake on WiFi is enabled and disabled. + Recorded 1 second after waking from suspend. + + + + + yzshen@chromium.org + + How much, in bytes, of the response body has been read from network by a + URLLoader before it pauses reading, when it receives a + PauseReadingBodyFromNet() call. If there are multiple calls to + PauseReadingBodyFromNet(), only a single value is recorded for the last + call. This histogram is recorded by URLLoader implementations that fetch + from network. When SafeBrowsing indicates that a resource may be unsafe and + therefore a more time-consuming check is required to classify it, reading + response body from network is paused in order to reduce the chance of + writing unsafe contents into cache. This histogram is useful to evaluate how + much data is cached during this window. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Chrome OS network usage metric. The channel used for each successful WiFi + connection. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Chrome OS network usage metric. The channel type used for each successful + WiFi connection. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Network metric reporting the average round trip time to the WiFi gateway. + Recorded at least once per day. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Chrome OS network usage metric. The security setting for each successful + WiFi connection. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the failure reason for all connection attempts, + manual or automatic, to Wi-Fi networks which were added from Chrome Sync. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the result of all connection attempts, manual + or automatic, to Wi-Fi networks which were added from Chrome Sync. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the failure reason for manual connection + attempts to Wi-Fi networks which were added from Chrome Sync. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the result of manual connection attempts to + Wi-Fi networks which were added from Chrome Sync. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the total number of Wi-Fi networks which are + stored in Chrome Sync for the active user. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the failure reason for update attempts to + synced Wi-Fi networks. This includes create/modify/remove operations. Each + retry is counted seperately. + + + + + jonmann@chromium.org + better-together-dev@google.com + + Chrome OS metric that tracks the result of update attempts to synced Wi-Fi + networks. This includes create/modify/remove operations. failures are only + recorded after all retries have been exhausted. + + + + + mmenke@chromium.org + + Whether a request going through the network service has one of a number of + concerning headers added by the caller when the request is redirected. + Entries are only recorded when headers are actually added during a redirect. + We want to figure out if we can ban any of these headers from being set + outside the network service. For comparison with + NetworkService.ConcerningRequestHeader.HeaderAddedOnRedirect. + + + + + mmenke@chromium.org + + Tracks how often each of a number of concerning headers are added by the + caller when a network service request is redirected. We want to figure out + if we can ban any of these headers from being set outside the network + service. To get meaningful percentages of requests, need to compare with + NetworkService.ConcerningRequestHeader.AddedOnRedirect. + + + + + mmenke@chromium.org + + Tracks how often each of a number of concerning headers are set by the + caller when a network service request is started. We want to figure out if + we can ban any of these headers from being set outside the network service. + To get meaningful percentages of requests, need to compare with + NetworkService.ConcerningRequestHeader.PresentOnStart. + + + + + mmenke@chromium.org + + Whether a request going through the network service has one of a number of + concerning headers set by the caller when the request starts. We want to + figure out if we can ban any of these headers from being set outside the + network service. For comparison with + NetworkService.ConcerningRequestHeader.HeadersPresentOnStart. + + + + + mkwst@chromium.org + yhirano@chromium.org + + Records the result of the Cross-Origin Resource Policy check, with + cross-origin-embedder-policy-report-only involvement. + + + + + mkwst@chromium.org + yhirano@chromium.org + + Records the result of the Cross-Origin Resource Policy check. + + + + + qingsi@chromium.org + jeroendb@chromium.org + + Errors that the mDNS responder service encounters during its lifetime. These + may be system errors in mDNS socket creation and IO, or user-induced by + invalid IP addresses. + + + + + jam@chromium.org + + How long the browser waits for the network process to exit at shutdown. + + + + + cduvall@chromium.org + cmumford@chromium.org + + How long it takes the network service to respond to the first mojo call. + This will be used to debug http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + How long it takes the network service to respond to the first mojo call + after a network service crash. This will be used to debug + http://crbug.com/934317. + + + + + cduvall@chromium.org + cmumford@chromium.org + + How long it takes the network service to respond to the first mojo call on + startup. This will be used to debug http://crbug.com/934317. + + + + + lukasza@chromium.org + creis@chromium.org + jam@chromium.org + + Whether the request origin (i.e. + network::ResourceRequest::request_initiator) matches the origin that the + browser process expected when creating the URLLoaderFactory (i.e. whether it + matches URLLoaderFactoryParams::request_initiator_origin_lock). + + Recorded when a request is started (i.e. at the time of constructing + network::URLLoader). + + + + + jam@chromium.org + juncai@chromium.org + mmenke@chromium.org + + Whether the Origin header is the same as the request origin in the + URLLoaderFactory when it creates a URLLoader. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker observes a tick clock and a wall clock to determine + whether a timestamp retrieved from the network in the past can be used to + compute a current timestamp. When the tick clock and wall clock diverge from + each other, the NetworkTimeTracker must discard the network timestamp + because it has no way to compute a reliable current timestamp. Whenever the + NetworkTimeTracker discards a network timestamp due to the tick and wall + clocks diverging, this histogram records the difference of the tick clock's + delta minus the wall clock's delta since the network timestamp was + retrieved. For cases where the the tick clock delta is bigger than the wall + clock delta, see NetworkTimeTracker.ClockDivergence.Positive. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker observes a tick clock and a wall clock to determine + whether a timestamp retrieved from the network in the past can be used to + compute a current timestamp. When the tick clock and wall clock diverge from + each other, the NetworkTimeTracker must discard the network timestamp + because it has no way to compute a reliable current timestamp. Whenever the + NetworkTimeTracker discards a network timestamp due to the tick and wall + clocks diverging, this histogram records the difference of the tick clock's + delta minus the wall clock's delta since the network timestamp was + retrieved. For cases where the the wall clock delta is bigger than the tick + clock delta, see NetworkTimeTracker.ClockDivergence.Negative. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker makes periodic queries to obtain a secure timestamp over + the network. This histogram records the delta between each secure timestamp + and the previous one, to measure how often time queries are made. The first + time query is not recorded, because there is no previous query from which to + compute a delta. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker makes periodic queries to obtain a secure timestamp over + the network. This histogram records the latency of each time query. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker makes periodic queries to obtain a secure timestamp over + the network. This histogram records the request's net error code whenever a + secure timestamp fetch results in a network error or a non-200 HTTP status + code. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker makes periodic queries to obtain a secure timestamp over + the network. Whenever one of these requests results in a successful 200 + status code, this histogram records true if the response parsed and + validated successfully, and false otherwise. + + + + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker observes a tick clock and a wall clock to determine + whether a timestamp retrieved from the network in the past can be used to + compute a current timestamp. When the NetworkTimeTracker observes that the + wall clock ran backwards, the NetworkTimeTracker must discard the network + timestamp because it has no way to compute a reliable current timestamp. + Whenever the NetworkTimeTracker discards a network timestamp due to the wall + clock running backwards, this histogram records the magnitude of the + difference of the current wall clock time minus the wall clock time when the + network timestamp was retrieved. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/new_tab_page/histograms.xml b/tools/metrics/histograms/histograms_xml/new_tab_page/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..1809a1f7de264083d28c7b7759b5c9f284cc0121 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/new_tab_page/histograms.xml @@ -0,0 +1,1342 @@ + + + + + + + + + + twellington@chromium.org + finkm@chromium.org + + Actions taken from the new tab page on Android. These actions may navigate + away from the NTP (e.g. searching in the omnibox or opening a bookmark), but + can also happen without navigating away from the NTP (e.g. opening a content + suggestion in a new tab). + + + + + justincohen@chromium.org + gambard@chromium.org + + Actions taken by users from the new tab page on iOS. These actions may + navigate away from the NTP (e.g. searching in the omnibox or opening a + bookmark), but can also happen without navigating away from the NTP (e.g. + opening a bookmark in a new tab). + + + + + Please list the metric's owners. Add more owner tags as needed. + + Histogram for the source of app page drags. For any succesful drop onto an + apps pane of the NTP, this logs where the drag originated. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The time it took until a request from the New Tab Page for Backdrop + Collections was served. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The time it took until a request from the New Tab Page for Backdrop Images + was served. + + + + + ramyan@chromium.org + yyushkina@chromium.org + + The time it took until a request from the New Tab Page for the next Backdrop + Image in a collection was served. The duration is measured from time the + client invokes the service call, to the time it receives the callback. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: Whether article suggestions on New Tab Page are set visible by user + on startup and when the visibility is changed. + + + + + skym@chromium.org + carlosk@chromium.org + Android: Loading of Zine was artifically delayed + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The type of trigger that caused a background fetch of NTP content + suggestions from a suggestion server. Every background fetch is recorded. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: A category of content suggestions that was dismissed (by swiping + away its empty state card). + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The number of suggestion cards that were available at the time an + NTP was opened. Only visible categories (i.e. which can be seen by the user + on this NTP) are recorded, including empty ones. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The number of prefetched suggestion cards that were available in + Articles category if it was visible at the time an NTP was opened and the + user was offline. Analogous to + NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible, except that this + metric is reported after all URL prefetched asynchronous checks finish. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The position of a suggestion card on the NTP that is dismissed, + typically by swiping it away. The suggestion had a URL that was NOT visited + before. We track the position the card had in the list when it was first + seen by the user. This tracked position can be different from the position + observed by the user, e.g. when the user dismissed some suggestions from the + list or requested more that got inserted in the middle of the feed. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The position of a suggestion card on the NTP that is dismissed, + typically by swiping it away. The suggestion had a URL that was visited + before. We track the position the card had in the list when it was first + seen by the user. This tracked position can be different from the position + observed by the user, e.g. when the user dismissed some suggestions from the + list or requested more that got inserted in the middle of the feed. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The position of a suggestion card whose long-press menu was opened, + analogous to NewTabPage.ContentSuggestions.Opened. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The age of a suggestion card on the NTP whose long-press menu was + opened, analogous to NewTabPage.ContentSuggestions.OpenedAge. + + + + + tschumann@chromium.org + + Android: The relevance score of a suggestion card on the NTP whose + long-press menu was opened, analogous to + NewTabPage.ContentSuggestions.OpenedScoreNormalized. Scores (which are + typically floats within (0,1]) get reported as discrete integers within + [1,10]. For instance, the discrete value 1 represents score values from + (0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly + high scores. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The position of a "More" suggestion card that was clicked + on the NTP. A card is considered shown when at least 2/3 of its height is + visible on the screen. We track the position the card had in the list when + it was first seen by the user. This tracked position can be different from + the position observed by the user, e.g. when the user dismissed some + suggestions from the list or requested more that got inserted in the middle + of the feed. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The position of a "More" suggestion card that was shown + on the NTP. A card is considered shown when at least 2/3 of its height is + visible on the screen. For each card, at most one impression is recorded per + NTP instance. We track the position the card had in the list when it was + first seen by the user. This tracked position can be different from the + position observed by the user, e.g. when the user dismissed some suggestions + from the list or requested more that got inserted in the middle of the feed. + + + + + vitaliii@chromium.org + + Android: The new index of a category on the NTP after it has been moved up + due to a click. The index of a category, which has been overtaken, is not + recorded here. This tracked index can be different from the position + observed by the user, e.g. empty categories are not shown. This metric + ignores all other order changes (e.g. dismissing a category or clearing + history). + + + + + zea@chromium.org + + Android: The number of actions taken on displayed notifications, either + user-initiated (tapping to open or swiping to dismiss), or automatic (hiding + due to a change in circumstances). + + + + + zea@chromium.org + + Android: The number of times a user opted out, keyed by method: IMPLICIT + (user ignored enough notifications consecutively that we think they're not + interested), or EXPLICIT (via explicit setting). + + + + + zea@chromium.org + + Android: The number of notifications that were shown, keyed by category. One + bucket counts the server-provided ARTICLES category; the other counts + everything else. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: How an article linked from a suggestion card on the NTP was opened + (e.g. plain click, open in new tab, open in incognito). + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The position of the suggestion card on the NTP, that is clicked + through to the host website of the content. We track the position the card + had in the list when it was first seen by the user. This tracked position + can be different from the position observed by the user, e.g. when the user + dismissed some suggestions from the list or requested more that got inserted + in the middle of the feed. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The position of the prefetched suggestion card on the NTP, that is + clicked through to the host website of the content, when the user is + offline. Analogous to NewTabPage.ContentSuggestions.Opened. That is we track + the position the card had in the list when it was first seen by the user. + This tracked position can be different from the position observed by the + user, e.g. when the user dismissed some suggestions from the list or + requested more that got inserted in the middle of the feed. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The age of a suggestion card on the NTP that is clicked through to + the host website of the content. The age is measured from the moment the + content has been published. + + + + + vitaliii@chromium.org + + Android: The index of a category on the NTP, whose suggestion card is + clicked through to the host website of the content. This tracked index can + be different from the position observed by the user, e.g. for the user a + category may be at the top of the NTP, but with index 1, because they + dismissed the one that was previously at the top. + + + + + tschumann@chromium.org + + Android: The score of a suggestion card on the NTP that is clicked through + to the host website of the content. The recorded score is from the moment + the suggestion was fetched, it could have changed since. Scores (which are + typically floats within (0,1]) get reported as discrete integers within + [1,10]. For instance, the discrete value 1 represents score values from + (0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly + high scores. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Whether content suggestions from the remote service are enabled. It is + recored at startup. Note: This histogram is not specific to the New Tab + Page. + + + + + vitaliii@chromium.org + + Android: The number of suggestion sections that were shown at the time an + NTP was opened. All shown sections (including empty ones) are counted. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The position of a suggestion card that was shown on the NTP. A card + is considered shown when at least 2/3 of its height is visible on the + screen. For each card, at most one impression is recorded per NTP instance. + We track the position the card had in the list when it was first seen by the + user. This tracked position can be different from the position observed by + the user, e.g. when the user dismissed some suggestions from the list or + requested more that got inserted in the middle of the feed. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The position of a prefetched suggestion card that was shown on the + NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is + a card is considered shown when at least 2/3 of its height is visible on the + screen. For each card, at most one impression is recorded per NTP instance. + We track the position the card had in the list when it was first seen by the + user. This tracked position can be different from the position observed by + the user, e.g. when the user dismissed some suggestions from the list or + requested more that got inserted in the middle of the feed. This metric is + reported not immediately after the impression, but once the request to + Offline Page model to check the URL finishes. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The age of a suggestion card that was shown on the NTP. A card is + considered shown when at least 2/3 of its height is visible on the screen. + For each card, at most one impression is recorded per NTP instance. + + + + + tschumann@chromium.org + + Android: The score of a suggestion card that was shown on the NTP. A card is + considered shown when at least 2/3 of its height is visible on the screen. + For each card, at most one impression is recorded per NTP instance. Scores + (which are typically floats within (0,1]) get reported as discrete integers + within [1,10]. For instance, the discrete value 1 represents score values + from (0.0, 0.1]. The discrete value 11 is the overflow bucket for + unexpectedly high scores. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the displayed content suggestions was fetched. + Recorded when the user looks at content suggestions on the NTP. The metric + is only recorded for suggestions of the Articles for you section. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the last fetch, recorded upon the first on-shown + fetch trigger. The first on-shown trigger does not necessarily cause a fetch + (if it comes before the end of the respective scheduling interval). This + metric is recorded at most once after each fetch (and additionaly at most + once after each startup of Chrome before the next fetch). This is used to + understand how changing scheduling intervals will impact traffic of + background fetches. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the last fetch, recorded upon the first startup + fetch trigger. The first startup trigger does not necessarily cause a fetch + (if it comes before the end of the respective scheduling interval). This + metric is recorded at most once after each fetch (and additionaly at most + once after each startup of Chrome before the next fetch). This is used to + understand how changing scheduling intervals will impact traffic of + background fetches. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the last fetch, recorded upon a persistent fetch. + This is used to understand what are the real persistent fetching intervals + in the wild. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the last fetch, recorded upon a soft fetch. This is + used to understand what are the real soft fetching intervals in the wild. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time since the last fetch, recorded upon a startup fetch. This + is used to understand what are the real soft fetching intervals in the wild. + + + + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + Android: The time of day (in the local timezone) when the user used content + suggestions. Recorded for example when the user scrolls to the articles + suggestions or opens an article suggestions. + + + + + freedjm@chromium.org + feed@chromium.org + + Android: Time spent reading the page linked by an opened suggestion card. + Exit conditions include the tab not being in the foreground or starting a + new navigation. + + + + + tmartino@chromium.org + chrome-creation@google.com + + Tracks the outcome of Probabilistic Cryptid Rendering (succeeded, failed, or + was disabled because preconditions were not met). + + + + + + + dbeam@chromium.org + yyushkina@chromium.org + chrome-analysis-team@google.com + + Customization actions performed by the user on the New Tab Page; logged as + each interaction occurs. This may indicate popularity of a particular + customization type. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + Captures the actions performed when configuring a 'Chrome background' image + on the New Tab Page. Since most actions are sequential, this may indicate + steps in the configuration process where users drop off. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The New Tab Page features that have been customized by the user; logged per + NTP load. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The New Tab Page shortcut settings that can be customized by the user, + including shortcut type (i.e. most visited vs custom links) and visibility; + logged per NTP load. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Captures the actions performed when uploading a local image as the + background on the New Tab Page. Since most actions are sequential, this may + indicate steps in the configuration process where users drop off. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Captures the actions performed when configuring shortcuts on the New Tab + Page. + + + + + jkrcal@chromium.org + + Android: Percentage of how much in browsing is the UI language of Chrome + used compared to overall use of the two top languages that are reported to + Chrome content suggestion server. + + + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Histogram of the time, in milliseconds, it took for the NTP to load all of + its tiles since navigation start. + + + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-analysis-team@google.com + chrome-desktop-ntp@google.com + + The number of clicks on the static/call-to-action/animated logo on the NTP. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Outcome of downloading search provider's logos. It measures whether + download/parsing is successful, revalidation and parsing work properly, etc. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The amount of time it took to download the static logo. This includes + requests where there was no logo, or where an existing logo was revalidated + (so no new image data was downloaded), but it does not include failed + requests. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + A logo image (static or CTA) was downloaded. Recorded only when the image + was downloaded and decoded without errors. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The number of static logos and animated logos shown to users. Note that the + base version of this histogram is recorded both for logos from the cache and + for fresh logos, so it can be recorded twice per NTP impression. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The amount of time between opening an NTP and the logo appearing. Only + recorded when there is a logo, and only recorded once per NTP. + + + + + fserb@chromium.org + zmin@chromium.org + + Record the network status when a new tab page is opened. True if user is + online and false for offline. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Histogram of the time, in milliseconds since navigation start, it took until + the modules showed up on the NTP. + + + + + + + justincohen@chromium.org + mastiz@chromium.org + tiborg@chromium.org + yyushkina@chromium.org + chrome-analysis-team@google.com + chrome-desktop-ntp@google.com + + Histogram for user clicks of the most visited tile. The value is equal to + the index of the tile. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The age of the data at click time, that is, the elapsed time since the + suggestion was generated by a ranking algorithm. + + + + + treib@chromium.org + + The time from the New Tab page being shown until the user to clicked on a + most visited tile. Only recorded if the user clicked on a tile, as opposed + to e.g. searching via the omnibox. Only measured on Android. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The number of tiles that are on the NTP, no matter if they are thumbnails, + gray tiles, or external tiles. Recorded before reloading the suggestions, + navigating to a URL, switching tabs, changing the active window or closing + the tab/shutting down Chrome. The sum of this histogram does not have to + equal to the total count of tile impressions (such as the total count in + NewTabPage.TileType). The reason is that not all tiles have to be impressed + initially (e.g., the second row of tiles may be initially out of sight on + iOS). + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The time it took until a request from the New Tab page for the OneGoogleBar + script was served. Recorded only on the local NTP. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Histogram of the time, in milliseconds since navigation start, it took until + the OneGoogleBar showed up on the NTP. Recorded only on the local NTP. + + + + + wenyufu@chromium.org + twellington@chromium.org + + Records events related to the homepage promo card on the new tab page. + Recorded for Android only. + + + + + wenyufu@chromium.org + twellington@chromium.org + + The number of times that the homepage promo was shown to the user before + they took action. Recorded when the user accepts the homepage promo. + Recorded for Android only. + + + + + wenyufu@chromium.org + twellington@chromium.org + + The number of times that the homepage promo was shown to the user before it + was manually dismissed. Recorded when the user dismisses the promo. Recorded + for Android only. + + + + + + + dbeam@chromium.org + yyushkina@chromium.org + chrome-analysis-team@google.com + + Emitted each time a promo linked is clicked on the local NTP. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + mahmadi@chromium.org + chrome-desktop-ntp@google.com + + Logs how many times various promo browser commands are executed. Triggered + when a supported and enabled promo browser command is sent via the New Tab + Page promos and is executed by the PromoBrowserCommandHandler. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The time it took until a request from the New Tab page for the middle slot + promo script was served. Recorded on the local and WebUI NTP. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Histogram of the time, in milliseconds since navigation start, it took until + a middle slot promo showed up on the NTP. Recorded on the local and WebUI + NTP. + + + + + mahmadi@chromium.org + tommycli@chromium.org + chrome-desktop-ntp@google.com + + Records the time taken between a keystroke being typed in the NTP realbox + and the time when we're ready to render the results in the DOM. If there are + multiple keystrokes before the results are rendered, logs the time since the + earliest one. This is most comparable to Omnibox's + Omnibox.CharTypedToRepaintLatency.ToPaint as it does not take into account + the time the DOM change task spends in the message loop nor its duration. + + + + + jkrcal@chromium.org + + Records how many background requests of the given type the browser tried to + perform each day where the type is specified by the _suffix of the + histogram. The histogram is emitted only after midnight of the given day + passes - right before the first following request (which can be several days + later if the user does not use Chrome in the meantime). The histogram counts + requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count + can easily exceed the daily quota. + + + + + jkrcal@chromium.org + + Records how many interactive requests of the given type the browser tried to + perform each day where the type is specified by the _suffix of the + histogram. The histogram is emitted only after midnight of the given day + passes - right before the first following request (which can be several days + later if the user does not use Chrome in the meantime). The histogram counts + requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count + can easily exceed the daily quota. + + + + + jkrcal@chromium.org + + Records the status w.r.t. the quota for all requests of the given type. The + type of request is specified by the _suffix of the histogram. + + + + + fgorski@chromium.org + ender@google.com + yyushkina@chromium.org + + The time until the search box became available on the NTP in a cold start. + It's a cold start if the native library is not already loaded and + initialized at the time the activity is created. Only measured on Android. + + + + + fgorski@chromium.org + ender@google.com + yyushkina@chromium.org + + The time until the search box became available on the NTP in a warm start. + It's a warm start if the native library is already loaded and initialized at + the time the activity is created. This might happen if for example a service + was already running. Only measured on Android. + + + + + + + dbeam@chromium.org + yyushkina@chromium.org + chrome-analysis-team@google.com + + The index of the search suggestion tile that was clicked on the local NTP. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The time it took until a request from the New Tab page for the search + suggestions script was served. Recorded only on the local NTP. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + Whether a request was made for search suggestions on NTP load; and if a + request was not made, the reason why. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The number of search suggestion tiles that were shown on the local NTP. + + + + + treib@chromium.org + + Android: The time it took to load the database of persisted content + suggestions. Recorded only when the database is loaded successfully. + + + + + treib@chromium.org + + Android: The state of the RemoteSuggestionsProvider. Recorded when the state + changes, typically once at startup and rarely afterwards, e.g. on database + errors. + + + + + mastiz@chromium.org + + Response or error codes encountered when attempting to fetch snippets. + + + + + mastiz@chromium.org + + Result of attempting a fetch, logged once per issued trigger. + + + + + mastiz@chromium.org + + Time spent fetching snippets. Only recorded for fetch attempts that resulted + in an actual network request. + + + + + finkm@chromium.org + + Records the time of the day in minutes when a snippets background fetch was + initiated. Counts minutes since midnight UTC. + + + + + finkm@chromium.org + + Records the time of the day in minutes when a snippets background fetch was + initiated. Counts minutes since midnight local time. + + + + + maybelle@chromium.org + + Whether we discarded any of the snippets after fetching them due to having + incomplete metadata. + + + + + treib@chromium.org + + Android: The number of snippet articles available to show on the NTP, logged + once every time the list is updated. + + + + + mastiz@chromium.org + + Android: The number of valid snippet articles fetched from the server, + logged every time a fetch finishes successfully. + + + + + mastiz@chromium.org + + Android: The number of snippet articles discarded by the user, logged every + time the list is updated resulting in an empty list (all articles + discarded). + + + + + treib@chromium.org + + The number of snippets that we discard per fetch due to having incomplete + data. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Histogram for impressions on the various most visited tiles. The value is + equal to the index of the thumbnail. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + The age of the data at impression time, that is, the elapsed time since the + suggestion was generated by a ranking algorithm. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The favicon type that was chosen to represent a most visited tile displayed + on the new tab page, logged at impression time. Note that these values don't + involve an actual icon being displayed because a scrabble time might have + been displayed instead (see NewTabPage.TileType). + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The favicon type that was chosen to represent a most visited tile displayed + on the new tab page, logged when a tile is clicked. Note that these values + don't involve an actual icon being displayed (see + NewTabPage.TileTypeClicked). + + + + + treib@chromium.org + + The number of times a tile was available offline, per tile index - compare + to the NewTabPage.SuggestionsImpression.* histograms. This is recorded when + the NTP finishes loading. Only measured on Android. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Records the source of the title for each most visited tiled displayed when + an NTP is opened, e.g. a short_name from a manifest, or the page title. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Records the source for the name a most visited tile showed when the user + clicked it, e.g. a URL, or the page title. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The visual type of each most visited tile displayed on the new tab page, + e.g. actual thumbnail or placeholder thumbnail. This is recorded for each + most visited item when the NTP is opened. + + + + + dbeam@chromium.org + yyushkina@chromium.org + + The visual type of the most visited item that the user clicked on, e.g. + actual thumbnail or placeholder thumbnail. + + + + + freedjm@chromium.org + feed@chromium.org + + The time spent on the new tab page as measured from when it was loaded or + last brought to the foreground until it was navigated away from or hidden. + Only measured on Android. + + + + + freedjm@chromium.org + feed@chromium.org + + The time from when a new tab page is created until the first pre-draw call + on the root view containing the search provider logo (if available), fake + search box, most visited tiles, articles etc. More specifically, this is the + time between NewTabPage's constructor and the first pre-draw pass on this + root view. This typically means that the fixed UI elements are shown to the + user, but the articles below are not filled in yet. + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Records the status of the New Tab page URL when an NTP is opened. + + + + + jkrcal@chromium.org + + Android: The estimated average number of hours between two successive times + when a new tab page is opened. Recorded after each opening of a NTP (and + after updating the model used for the estimate). + + + + + jkrcal@chromium.org + + Android: The estimated average number of hours between two successive times + when the list of content suggestions on a new tab page is shown (i.e. when + the user scrolls below the fold). Recorded after each time the suggestions + are shown (and after updating the model used for the estimate). + + + + + freedjm@chromium.org + feed@chromium.org + + Android: The estimated average number of hours between two successive times + when the user opens a content suggestion or clicks on the "More" + button. Recorded after each time a suggestion or a More button is clicked + (and after updating the model used for the estimate). + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Actions taken by users of Voice Search on the local New Tab Page on Desktop. + These actions may navigate away from the NTP (e.g. submitting a speech + query), but can also happen without navigating away from the NTP (e.g. + initiating or retrying Voice Search). + + + + + tiborg@chromium.org + yyushkina@chromium.org + chrome-desktop-ntp@google.com + + Errors that occur during Voice Search use on the local New Tab Page on + Desktop. These may be user-induced (e.g. the user's utterance could not be + recognized - no match), or resulting from external circumstances (e.g. + offline, lack of microphone permission). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/notifications/histograms.xml b/tools/metrics/histograms/histograms_xml/notifications/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..952472eadb571e49e5a12062220a1f961ed9ee06 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/notifications/histograms.xml @@ -0,0 +1,812 @@ + + + + + + + + + + dewittj@chromium.org + + The actions taken on notifications, recorded every time they happen. This + histogram will record every single event that happens separately. + + + + + peter@chromium.org + + Records the delay between scheduling a job with the JobScheduler (with a + desired latency of 0ms, in response to a notification click) and receiving + the onStartJob callback. Only measured on Android N and above. + + + + + peter@chromium.org + + Recorded when the Sites channel (which we hope to deprecate) is used as a + fallback, when a site-specific notification channel is expected to exist but + does not. Note, we only log when the sites channel is *used*, not when it is + not used. + + + + + dtrainor@chromium.org + xingliu@chromium.org + + Records the events when the announcement notification is shown, clicked, or + closed. + + + + + + + peter@chromium.org + + Records whether notifications are enabled for Chrome, as the Android app, + for each Web Notification that is being shown to the user. + + + + + peter@chromium.org + + The size, in bytes, of the author-provided data associated with a Web + Notification. Recorded when a persistent Web Notification is being shown by + the developer. + + + + + hesen@chromium.org + xingliu@chromium.org + + + + Various events when Chrome interacts with Chime notification platform. + Recorded when Chrome registers to Chime service, receives notifications, and + the user interacts with the notification. + + + + + hesen@chromium.org + xingliu@chromium.org + + + + Records the result of Chime notification platform registration. Each device + may have multiple accounts registered. The registration happens right after + opening Chrome. + + + + + tengs@chromium.org + gzadina@google.com + + Records the notification type when a notification interaction occurs. See + suffixes for all event types. ChromeOS only. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of deleting all notification data for given + origins. This happens when notification permissions are revoked for a site. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of deleting notification data from the Web + Notification database that share their tag (replacement identifier) with a + notification that's about to be shown. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of deleting notification data from the Web + Notification database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of deleting all notification data associated + with a Service Worker registration ID. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of destroying the Web Notification database + altogether. + + + + + knollr@chromium.org + peter@chromium.org + adelm@google.com + + Records the age of the oldest notification for an origin. Logged after + handling a push event for that origin. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of opening the Web Notification database + after it has been destroyed in response to data corruption. + + + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of opening the Web Notification database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of reading data of all notifications + associated with a Service Worker from the Web Notification database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of reading resources for a notification from + the Web Notification database. This happens when a previously scheduled + notification has triggered. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of reading resources for a notification from + the Web Notification database. This happens when a scheduled notification is + read from the database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of reading data of a single notification + from the Web Notification database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of writing data for a notification to the + Web Notification database. + + + + + knollr@chromium.org + peter@chromium.org + + Records the result status codes of updating the triggered flag for a + notification in the Web Notification database. This happens after fetching + data and resources for a triggered notification, just before displaying it. + + + + + + + thomasanderson@chromium.org + + Whether the notification server supports the capability in question. (Linux + only) Logged when the proxy to /org/Freedesktop/Notifications is set up + successfully, which happens at most once on startup. + + + + + thomasanderson@chromium.org + + The status code for initializing NotificationPlatformBridgeLinux. (Linux + only) Logged on each start up. + + + + + finnur@chromium.org + + The execute status of a ComServerModule class instance. Logged whenever a + notification_helper process is launched by Windows. + + + + + chengx@chromium.org + finnur@chromium.org + + The primary execute status of NotificationActivator::Activate. Logged + whenever a notification_helper process is launched by Windows. + + + + + chengx@chromium.org + finnur@chromium.org + + The secondary execute status of NotificationActivator::Activate. Logged + whenever a notification_helper process is launched by Windows. + + + + + finnur@chromium.org + + The runtime of the notification_helper server process. This process is + created when a notification is activated from the Windows Action Center. + Once created, this process does some COM class registration work, so that + Windows can call certain APIs to handle the notification activation. Upon + finishing the API calls, Windows signals this process to exit. + + + + + tengs@chromium.org + + The number of times a notification was added for the various types of + sources. + + + + + knollr@chromium.org + peter@chromium.org + + The number of notifications that got deleted from the NotificationDatabase + after the notification permissions got revoked. + + + + + dewittj@chromium.org + + The actions taken on notifications, recorded once per notification, when it + is closed. This differs from the Notifications.Actions histogram in that + multiple events of the same type on a single notification will only record a + single UMA event. + + + + + peter@chromium.org + + The number of action buttons the developer provided for a persistent Web + Notification. Logged whenever showNotification is called. + + + + + peter@chromium.org + deepak.m1@samsung.com + + Recorded delivery status for persistent notification clicks to a Service + Worker when handling a click on a persistent WebNotification has finished. + + + + + peter@chromium.org + knollr@chromium.org + + Records delivery status for persistent notification close events sent to a + Service Worker when the event has been handled. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the various events when running the background task in notification + scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the number of notifications shown in each background task run. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the hour (0-23) when the notification scheduler background task + starts. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the initialization result of icon database for the notification + scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the database operation result (except initialization) of icon + database for the notification scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the number of records of icon database for the notification + scheduling system when the icon database is initialized. + + + + + + + xingliu@chromium.org + hesen@chromium.org + + Records events for inline helpful/unhelpful action buttons on the + notification when the buttons are shown or clicked. + + + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the number of impression records in impression db right after the + impression database is initialized. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records various events in impression history tracker in notification + scheduling system when the user interacts with the notification. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the initialization result of impression database for the + notification scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the database operation result (except initialization) of impression + database for the notification scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the number of records of impression database for the notification + scheduling system when the impression database is initialized. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the initialization result of notification database for the + notification scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the database operation result (except initialization) of + notification database for the notification scheduling system. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the number of records of notification database for the notification + scheduling system when the notification database is initialized. + + + + + + + xingliu@chromium.org + hesen@chromium.org + + Records life cycle events for a scheduled notification, when notification is + scheduled, shown or encountering any error. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the result of png icon converter decoding process in icon store for + the notification scheduling system. It will be logged typically when + scheduling system trying to display the notification to the client - the + icon store will load entries, and decode icons to PNG format for delivery. + + + + + xingliu@chromium.org + hesen@chromium.org + + Records the result of png icon converter encoding process in icon store for + the notification scheduling system. It will be logged typically when the + client scheduled notification with icons - the icon store will then encode + icons to string and store them in protodb. + + + + + + + xingliu@chromium.org + dtrainor@chromium.org + + Records the type of user action when the user interacts with notification + sent from notification scheduler system. + + + + + knollr@chromium.org + peter@chromium.org + + Delay between the expected and actual display time of a notification. + Recorded just before displaying a notification with a show trigger. + + + + + + + peter@chromium.org + knollr@chromium.org + thomasanderson@chromium.org + + Indicates if Chrome is using system notifications or the Chrome notification + center. Logged on each start up. + + + + + finnur@chromium.org + peter@chromium.org + chengx@chromium.org + + The status of Activation requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever an activation from a notification occurs. + + + + + finnur@chromium.org + peter@chromium.org + + The status of Close requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever a notification is closed. + + + + + finnur@chromium.org + peter@chromium.org + + The HRESULT returned by the Windows Action Center, when trying to create a + toast manager fails. This provides a more detailed error in the cases the + histogram Notifications.Windows.DisplayStatus reported + CREATE_TOAST_NOTIFIER_WITH_ID_FAILED. + + + + + finnur@chromium.org + peter@chromium.org + + The HRESULT returned by the Windows Action Center, when showing a + notification fails. + + + + + finnur@chromium.org + peter@chromium.org + + The status of Display requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever a notification is displayed. For a more detailed + error about CREATE_TOAST_NOTIFIER_WITH_ID_FAILED and SHOWING_TOAST_FAILED, + see Notification.Windows histograms CreateToastManagerErrorCode and + ShowFailedErrorCode (respectively). + + + + + finnur@chromium.org + peter@chromium.org + + The status of decoding launch ids while processing a GetDisplayed requests + in NotificationPlatformBridgeWin (Windows only). Logged whenever a request + to retrieve all displayed notifications comes in. + + + + + finnur@chromium.org + peter@chromium.org + + The status of GetDisplayedStatus requests in NotificationPlatformBridgeWin + (Windows only). Logged whenever a request to retrieve all displayed + notifications comes in. + + + + + finnur@chromium.org + peter@chromium.org + + The status of GetNotificationLaunchId requests in + NotificationPlatformBridgeWin (Windows only). Logged whenever a request to + decode the GetNotificationLaunchId comes in. + + + + + finnur@chromium.org + peter@chromium.org + + The policy value provided by get_Setting in NotificationPlatformBridgeWin + (Windows only). Logged whenever a request to show a notification comes in. + + + + + finnur@chromium.org + peter@chromium.org + + The return value of get_Setting calls in NotificationPlatformBridgeWin + (Windows only). Logged whenever a request to show a notification comes in. + + + + + finnur@chromium.org + peter@chromium.org + + The status of HandleEvent requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever a notification event is being handled. + + + + + finnur@chromium.org + peter@chromium.org + + The status of History requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever history is requested for notifications. + + + + + chengx@chromium.org + finnur@chromium.org + + Used to indicate the status of decoding an input launch id string (Windows + only). Logged whenever a notification event is being handled. + + + + + chengx@chromium.org + peter@chromium.org + + The status of OnFailed requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever a failed event is handled. + + + + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + The status of SetReadyCallback requests in NotificationPlatformBridgeWin + (Windows only). Logged once at startup. + + + + + finnur@chromium.org + peter@chromium.org + + The HRESULT returned by the Windows Action Center, when trying to create a + toast manager fails. This provides a more detailed error in the cases the + histogram Notifications.Windows.DisplayStatus reported SHOWING_TOAST_FAILED. + + + + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + Used to indicate the status of start menu shortcut (Windows only). Logged + whenever a notification display attempt is made. + + + + + peter@chromium.org + rsesek@chromium.org + + Mac only. Records the different events of a Notification XPC connection. + These are recorded by monitoring the different error callbacks provided by + the XPC connection object. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/obsolete_histograms.xml b/tools/metrics/histograms/histograms_xml/obsolete_histograms.xml index 7e3a5044e3c047c52e15b3bd58ca8c0d5c15f597..21dab9159d443da3aadb5d5f210de6c1dfddd854 100644 --- a/tools/metrics/histograms/histograms_xml/obsolete_histograms.xml +++ b/tools/metrics/histograms/histograms_xml/obsolete_histograms.xml @@ -5,15 +5,12 @@ found in the LICENSE file. --> - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. + katie@chromium.org + dmazzoni@chromium.org + + For every image on a page with screen reader accessibility mode enabled, + this histogram will be used to understand minimum dimension of the image, + i.e. either the width or height in px. - + - Replaced with Blink.Canvas.ToBlob.CompleteEncodingDelay in 2017/12. + Removed 06/2020 as this is stable and doesn't need to be tracked closely. - fserb@chromium.org - aaronhk@chromium.org + + + katie@chromium.org + dmazzoni@chromium.org - This metric measures the total time spent on encoding all the rows of an - image (jpeg or png), excluding the waiting time of next idle periods. This - is part of a canvas.toBlob API call. Encoding occurs during one or more idle - periods on the main thread. + For every image on a page with screen reader accessibility mode enabled, + this histogram will be used to understand the size ratio of the image. This + is the smaller dimension divided by the larger dimension. - + - Replaced with Blink.Canvas.ToBlob.ScaledDuration in 10/2018. + Removed 12/2016 in Issue 672205 with the addition of Accessibility.ModeFlag. - fserb@chromium.org - aaronhk@chromium.org + dmazzoni@chromium.org + kenjibaheux@google.com - Time spent on 2D canvas toBlob API call. - - In addition, metric values from OffscreenCanvas.convertToBlob API call are - also gathered into this histogram, because the logic flow is exactly the - same as canvas.toBlob. It's worth to note that the values can come from idle - tasks on either main or worker thread. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. + Whether Chrome has enabled accessibility support because it detects + supported assistive technology running, or due to being manually enabled via + a command-line flag (logged once 45 secs after startup). - + - Replaced with Blink.Canvas.ToDataURLScaledDuration in 10/2018. + System Access To Go is a discontinued product. - fserb@chromium.org + dmazzoni@chromium.org + kenjibaheux@google.com - Time spent on 2D canvas toDataURL API call. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. + Whether the third-party System Access To Go screen reader is running (logged + once 45 secs after startup). - + - Removed on 2018-05-04. + Removed in M84 as part of https://crrev.com/c/2131912 The legacy code path + and API being checked by this UMA stat no longer exist. - khushalsagar@chromium.org + sinhak@chromium.org - The number of images which could have been checkered (async decoded) for a - performance gain, split by the DOM element type on which they were used. - This is recorded each time an image for an element created by the page is - loaded, either from the network or the local cache. The browser heuristics - define an image to be checkerable if it is expected to have a long decode - duration. Since these images may be on the rendering critical path, decoding - them asychronously from painting other content can provide better - performance be reducing overall content checkerboarding. + Tracks the usage of the legacy Primary Account setting flow vs the new flow + through Account Manager. This is recorded only once per session, at login + time. - + - No useful signal. Deprecated 7/2019. + Removed 05/2017 in favor of ActivityTracker.Collect.Status. - brianosman@chromium.org - mcasas@google.com - ccameron@chromium.org - Gamut properties of image color space. + manzagop@chromium.org + + Number of unclean shutdowns, as derived from the stability instrumentation. + Logged each time stability file collection is performed. + - + - Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + Removed 05/2017 in favor of ActivityTracker.Collect.Status. - ccameron@chromium.org + manzagop@chromium.org - Whether or not the output color space ICC profile was able to produce raw - transfer function tables. + Number of unclean shutdowns that can potentially be attributed to system + instability. This should be smaller or equal to UncleanShutdownCount. Logged + each time stability file collection is performed. - + - No useful signal. Deprecated 2020-03-03. + Removed 05/2017 in favor of ActivityTracker.CollectCrash.Event. - brianosman@chromium.org - mcasas@google.com - ccameron@chromium.org + manzagop@chromium.org - The result of analyzing the destiation color space's ICC profile. + Success of the attempt to open the debug file for deletion. Logged each time + a debug file is opened for deletion during collection from the crash + handler. - + - Linear fit found to be always inaccurate on 2017-02-28. + Removed 05/2017 in favor of ActivityTracker.Record.Event. - ccameron@chromium.org + manzagop@chromium.org - The L-infinity error (in 8-bit values) of the numerical approximation of - table-based ICC profile transfer functions, when falling back to a linear - approximation. + Status of internal activity tracking initialization. Logged once, during the + activity tracking initialization. - + - Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + Setup time is <=10ms for 90% with 0.1% taking >500ms. Removed 2019/06. - ccameron@chromium.org + siggi@chromium.org - Whether or not to-XYZD50 matrix was extracted from the output color space - ICC profile. + Time spent setting up the stability debugging instrumentation. Logged once, + during setup of the stability debugging instrumentation. - + - Nonlinear fit code moved to skcms on 2018-04-25. + Gaussian distribution around 22 with 0.1% being >=100. Removed 2019/06. - ccameron@chromium.org + bcwhite@chromium.org - Whether or not the nonlinear least squares fit of the table-based ICC - profile transfer function for a single channel converged. + The number of threads being tracked for activities such as waiting for a + lock/event, a thread to join, or a task to run. Analysis of this data can + reveal why a thread will not exit. This value is updated every time a new + thread gets an activity tracked for the first time so will show one count + for every permanent thread but multiple counts for a thread than exits and + is replaced. - + - Nonlinear fit code moved to skcms on 2018-04-25. + Never occurred. Removed 2019/06. - ccameron@chromium.org + bcwhite@chromium.org - The L-infinity error (in 8-bit values) of the numerical approximation of - table-based ICC profile transfer functions for a single channel, when the - nonlinear approximation converged. + The limit on the number of thread trackers that could be allocated from the + persistent memory segment. Trackers beyond this number were allocated from + the heap and thus were not available for analysis. This value is updated on + every "memory full" failure. - + - Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + Removed April 2019 - ccameron@chromium.org + csharrison@chromium.org + jkarlin@chromium.org - Whether or not the output color space ICC profile has a numerical transfer - function. + For a given ad request, logs information related to whether it is isolated + from the top-level context. Logged per ad subresource request. - + - TMax found to almost always be 1 on 2017-02-28. + Removed April 2019 - ccameron@chromium.org + csharrison@chromium.org + jkarlin@chromium.org - One minus the maximum value of table-based ICC profile transfer functions as - an 8-bit fixed-point value. This histogram is temporary, to see if we can - bake in the assumption that it will almost always be 255. + For a given request, logs information related to whether it is marked as an + ad, and whether it is secure (e.g. https). Logged per subresource request. - + - TMin found to almost always be 0 on 2017-02-28. + Removed 10/2019 in issue 1000058; no longer needed. - ccameron@chromium.org + johnidel@chromium.org - The minimum value of table-based ICC profile transfer functions as an 8-bit - fixed-point value. This histogram is temporary, to see if we can bake in the - assumption that it will almost always be 0. + Total number of bytes buffered over the lifetime of a WebMediaPlayer inside + of an adframe. Suffixed by type of playback. - + - No useful signal. Deprecated 7/2019. + Removed 07/2019 in favor of Ads.ResourceUsage.Size.Cache2. - brianosman@chromium.org - mcasas@google.com - ccameron@chromium.org - Gamma properties of image color space. + johnidel@chromium.org + jkarlin@chromium.org + + For a given resource fetched from the disk cache, logs the encoded body + length of the resource, even if the resource request was canceled or + incomplete. Recorded when the resource request is complete, or when the page + is destroyed/navigated for incomplete resources. + - + - Obsolete as of http://crrev.com/794384 and M86. + Removed 10/2018. Replaced with + Ads.ResourceUsage.Size.Network.Mainframe.AdResource and + Ads.ResourceUsage.Size.Cache.Mainframe.AdResource. - schenney@chromium.org - paint-dev@chromium.org + jkarlin@chromium.org + johnidel@chromium.org - Time spent updating compositing in the Blink document lifecycle. This is the - legacy compositing approach. BlinkGenPropertyTrees launches part of the new - compositing approach and will use both this and - Blink.CompositingCommit.UpdateTime. - - Note: As of M70, this histogram has stopped recording metrics on machines - with low-resolution clocks. - - TODO(crbug.com/1100711): This is being replaced soon by CompositingInputs + - CompositingAssignments (== Compositing). + For a given ad resource in the main frame, logs the network bytes received + for the resource, even if the resource request was canceled or incomplete. - + - Removed as of 01/20/2020. + Removed 10/2018. Replaced with + Ads.ResourceUsage.Size.Network.Mainframe.VanillaResource and + Ads.ResourceUsage.Size.Cache.Mainframe.VanillaResource. - kinuko@chromium.org - dcheng@chromium.org + jkarlin@chromium.org + johnidel@chromium.org - Microseconds per sync IPC call to set cookies. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. + For a given non-ad resource in the main frame, logs the network bytes + received for the resource, even if the resource request was canceled or + incomplete. - + - Removed as of 01/20/2020. + Removed 10/2018. Replaced with Ads.ResourceUsage.Size.Cache.Mime and + Ads.ResourceUsage.Size.Network.Mime. - kinuko@chromium.org - dcheng@chromium.org + johnidel@chromium.org + jkarlin@chromium.org - Microseconds per sync IPC call to fetch cookies. - - Warning: This metric may include reports from clients with low-resolution - clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports - will cause this metric to have an abnormal distribution. When considering - revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the - solution. + Size of resources tagged as ads, identified by the response header mime + type. This includes resources that did not complete loading. Recorded when + the resource request is completed. For incomplete requests, recorded when + the page is destroyed/navigated. - + - Removed as of 11/29/2016. + Removed 10/2018. Replaced with + Ads.ResourceUsage.Size.Network.Subframe.AdResource and + Ads.ResourceUsage.Size.Cache.Subframe.AdResource. - ryansturm@chromium.org - bengr@google.com + jkarlin@chromium.org + johnidel@chromium.org - The original canvas dimensions were sufficient to determine image size. This - is logged once per image header decode, which happens typically twice per - image on the page. + For a given ad resource in a subframe, logs the network bytes received for + the resource, even if the resource request was canceled or incomplete. - + - Removed as of 11/29/2016. + Removed 10/2018. Replaced with + Ads.ResourceUsage.Size.Network.Subframe.VanillaResource and + Ads.ResourceUsage.Size.Cache.Subframe.VanillaResource. - ryansturm@chromium.org - bengr@google.com + jkarlin@chromium.org + johnidel@chromium.org - How many bytes of the file were read before an image width and height were - determined. This is logged once per image header decode, which happens - typically twice per image on the page. + For a given non-ad resource in a subframe, logs the network bytes received + for the resource, even if the resource request was canceled or incomplete. - + - Removed as of 08/23/2018. Replaced by Blink.DecodedImage.JpegDensity.* + Removed 05/2020. - deymo@google.com - compression-dev@google.com + chelu@chromium.org + tbansal@chromium.org - The compressed image density measured in 0.01 bits per pixel. This is logged - once per image load after the whole image is loaded and only for JPEGs with - at least 100 pixels on each dimension. + The rank of the clicked anchor element in terms of area. This histogram is + recorded when the anchor element is clicked. - + - Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + Removed 05/2020. - deymo@google.com - compression-dev@google.com + chelu@chromium.org + tbansal@chromium.org - The compressed image density measured in 0.01 bits per pixel. This is logged - once per image load after the whole image is loaded and only for JPEGs with - at least 1000 pixels on the smallest dimension (width or height). + The interval between consecutive clicks of anchor elements. This histogram + is recorded when an anchor element is clicked except the first click in the + current document. - + - Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + Removed 05/2020. - deymo@google.com - compression-dev@google.com + chelu@chromium.org + tbansal@chromium.org - The compressed image density measured in 0.01 bits per pixel. This is logged - once per image load after the whole image is loaded and only for JPEGs with - at least 100 pixels on the smallest dimension (width or height) but less - than 400 pixels on the smallest dimension. + The duration between page load and the first click of an anchor element. If + the first click happens before page load, then the sample is recorded in + bucket 0. This histogram is recorded when an anchor element is clicked for + the first time in the current document. - + - Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + Removed 07/2018. Replaced with + AnchorElementMetrics.Clicked.HrefEngagementScore2. - deymo@google.com - compression-dev@google.com + chelu@chromium.org + tbansal@chromium.org - The compressed image density measured in 0.01 bits per pixel. This is logged - once per image load after the whole image is loaded and only for JPEGs with - at least 400 pixels on the smallest dimension (width or height) but less - than 1000 pixels on the smallest dimension. + The target link (href) engagement score of an anchor element. The score is + retrieved from the site engagement service. Currently all scores reported + are set to 0. This will soon change. This histogram is recorded when the + anchor element is clicked. - + - Removed as of 11/29/2016. + Obsoleted in M79. - ryansturm@chromium.org - bengr@google.com + chelu@chromium.org + tbansal@chromium.org - How much the canvas width needed to be expanded as a result of the first - frame's width and x-offset being larger than the initial canvas width. This - is logged once per image header decode, which happens typically twice per - image on the page. + The site engagement score of the target link (href) of an anchor element. + The score is retrieved from the site engagement service. This histogram is + recorded when the anchor element is clicked, and the score is larger than 0. - + - Removed as of 11/29/2016. + Removed 05/2020. - ryansturm@chromium.org - bengr@google.com + chelu@chromium.org + tbansal@chromium.org - How much the canvas height needed to be expanded as a result of the first - frame's height and y-offset being larger than the initial canvas height. - This is logged once per image header decode, which happens typically twice - per image on the page. + The calculated navigation score of the target link (href) of an anchor + element. The score is retrieved from the site engagement service. This + histogram is recorded when the anchor element is clicked and the score has + already been calculated when the document is loaded. - + - Removed 01/2018. + Removed 05/2020. - bokan@chromium.org + chelu@chromium.org + tbansal@chromium.org - Time it takes to execute all the `resize` event listeners on a page when a - resize event is fired. Tracked only for the main frame. + The rank of the navigation score of the target link (href) of an anchor + element. This histogram is recorded when the anchor element is clicked and + the score has already been calculated when the document is loaded. - + - UserActivationV2 made UserGestureTokens obselete, so the merge stats is now - irrelevant. + Removed 05/2020. - jyasskin@chromium.org - domenic@google.com + chelu@chromium.org + tbansal@chromium.org - How many times two user gesture tokens were merged by UserGestureIndicator, - and whether each token had an active gesture. One of the new token's - gestures, if any, is moved to the old token. + The ratio times 100 between the number of anchor elements that contains + images and the total number of anchor elements. This histogram is recorded + when the anchor element is clicked and it contains images. - + - Replaced with separate ImplCompositorCommit and WaitForCommit metrics and - removed in M84. + Removed 05/2020. - schenney@chromium.org - paint-dev@chromium.org - - + chelu@chromium.org + tbansal@chromium.org - The percentage of time between a BeginMainFrame and paint results commit in - Blink that is used for committing the layer tree to the impl thread. + The ratio times 100 between the number of anchor elements that contains + images and the total number of anchor elements. This histogram is recorded + when the anchor element is clicked and it does not contain images. - + - Replaced with separate Style and Layout metrics and removed in M81. + Removed 05/2020. - schenney@chromium.org - paint-dev@chromium.org - + chelu@chromium.org + tbansal@chromium.org + + The ratio times 100 between the number of anchor elements that is inside an + iframe and the total number of anchor elements. This histogram is recorded + when the anchor element is clicked and it is inside an iframe. + + + + + Removed 05/2020. + + chelu@chromium.org + tbansal@chromium.org - The percentage of time between a BeginMainFrame and paint results commit in - Blink that is used for computing Style and Layout. + The ratio times 100 between the number of anchor elements that is inside an + iframe and the total number of anchor elements. This histogram is recorded + when the anchor element is clicked and it is not inside an iframe. - + - Removed 08/2017 as it is integrated into media controller. + Removed 05/2020. - qinmin@chromium.org + chelu@chromium.org + tbansal@chromium.org - Records how the download button on the MediaDocument is used. + The ratio between the height of the root document and the height of the + viewport times 100. This histogram is recorded when the anchor element is + clicked. - + - Removed 11/2016 in Issue 666370 with the deprecation of Autoplay experiment. + Removed 05/2020. - oysteine@chromium.org + chelu@chromium.org + tbansal@chromium.org - Records user observation and interaction with Media HTML elements that - feature autoplay, either script-controlled or through the attribute. + The ratio times 100 between the number of anchor elements whose href have + the same host as the document and the total number of anchor elements. This + histogram is recorded when the anchor element is clicked and href of the + anchor element has a different host than the document. - + - Not very useful for identifying performance issues. + Removed 05/2020. - paint-dev@chromium.org + chelu@chromium.org + tbansal@chromium.org - Percentage of display items that are put into the index because of - out-of-order display item matching. Higher value means lower performance - beause of the cost of out-of-order matching and indexing. Recorded when we - finish updating paint in the Blink document lifecycle. + The ratio times 100 between the number of anchor elements whose href have + the same host as the document and the total number of anchor elements. This + histogram is recorded when the anchor element is clicked and href of the + anchor element has the same host as the document. - + - Not very useful for identifying performance issues. + Removed 05/2020. - paint-dev@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total number of display items (including cached and repainted) in the - painted result. Recorded when we finish updating paint in the Blink document - lifecycle. + The ratio times 100 between the number of anchor elements whose href is + incremented by one from the url of the document and the total number of + anchor elements. This histogram is recorded when the anchor element is + clicked and its href is not incremented by one from the url of the document. - + - Not very useful for identifying performance issues. + Removed 05/2020. - paint-dev@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total number of paint chunks in the painted result. Recorded when we finish - updating paint in the Blink document lifecycle. + The ratio times 100 between the number of anchor elements whose href is + incremented by one from the url of the document and the total number of + anchor elements. This histogram is recorded when the anchor element is + clicked and its href is incremented by one from the url of the document. - + - Not very useful for identifying performance issues. + Removed 05/2020. - paint-dev@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total number of subsequences (including cached and repainted) in the painted - result. Recorded when we finish updating paint in the Blink document - lifecycle. + True if the anchor element contains an image element, false if it is not. - + - SlimmingPaintInvalidation is enabled by default, so this histogram is no - longer being logged. Was removed in 02-2018. + Obsoleted in M79. - paint-dev@chromium.org + chelu@chromium.org + tbansal@chromium.org - Time spent updating paint invalidation in the Blink document lifecycle. Not - available when SlimmingPaintInvalidation or SlimmingPaintV2 is enabled. + The site engagement score of the document URL. The score is retrieved from + the site engagement service. - + - Replaced with separate ImplCompositorCommit and WaitForCommit metrics and - removed in M84. + Obsoleted in M79. - + chelu@chromium.org + tbansal@chromium.org + + The site engagement score of the target link (href) of an anchor element. + The score is retrieved from the site engagement service. + + - - - - - schenney@chromium.org - paint-dev@chromium.org + + + Obsoleted in M79. + + chelu@chromium.org + tbansal@chromium.org - Time spent commiting the layer tree to the impl thread in a main frame - update. - - Note: This histogram does not record metrics on machines with low-resolution - clocks. + The site engagement score of the target link (href) of an anchor element. + The score is retrieved from the site engagement service. This histogram is + recorded when href is an external link. - + - Removed as of 02/2020. + Removed 05/2020. - dtapuska@chromium.org - kenjibaheux@google.com - Count of resources attempted Stale Revalidation. + tbansal@chromium.org + + True if the anchor element was inside an iframe tagged as an ad iframe. + - + - Removed as of 8/2018. + Removed 05/2020. - - - toyoshim@chromium.org - ksakamoto@chromium.org - Count received data size in bytes for each resource. + chelu@chromium.org + tbansal@chromium.org + + True if the anchor element is within an iframe, false if it is not. + - + - Removed as of 02/2020. + Removed 05/2020. - toyoshim@chromium.org - altimin@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total decoded size of resources associated with frames of a particular type. - Recorded when a fetch has been completed. - - Each bucket of the histogram cointains the total size of all requests - associated with frames with a particular frame status in kilobytes. + True if the target URL of the anchor element and the URL of the root + document only differ by one number, and the number in the target URL equals + the number in the the URL of the root document plus one. - + - Removed as of 6/2019. + Removed 05/2020. - - - ksakamoto@chromium.org - toyoshim@chromium.org + chelu@chromium.org + tbansal@chromium.org - The largest number of outstanding resource requests issued by a frame until - the network 2-quiet (no more than 2 active network requests for 1 seconds). + The ratio times 100 between the clickable region area of an anchor element, + and the viewport area. - + - Removed as of 02/2020. + Removed 05/2020. - toyoshim@chromium.org - ksakamoto@chromium.org + chelu@chromium.org + tbansal@chromium.org - Count resource request circumstance, e.g. from the main frame vs sub-frames, - or in throttled state vs in not-throttled state, on each resource load - completion. + The ratio times 100 between the distance from the center of the clickable + region of an anchor element to the top edge of the visible region, and the + viewport height. - + - Removed as of 6/2019. + Removed 05/2020. - toyoshim@chromium.org - ksakamoto@chromium.org + chelu@chromium.org + tbansal@chromium.org - Count how many times the scheduler has changed throttling status from the - frame creation until network activity quiets. + The ratio times 100 between the distance from the bottom of the clickable + region of an anchor element to the bottom edge of the root frame, and the + viewport height. - + - Removed as of 6/2019. + Removed 05/2020. - - - toyoshim@chromium.org - altimin@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total received data size in bytes to load resources from the frame creation - until network activity quiets. + The ratio times 100 between the distance from the top of the clickable + region of an anchor element to the top edge of the root frame, and the + viewport height. - + - Removed as of 6/2019. + Removed 05/2020. - - - toyoshim@chromium.org - ksakamoto@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total number of resource requests completed from the frame creation until - network activity quiets. + The ratio times 100 between the distance from the top of the clickable + region of an anchor element to the top edge of the visible region, and the + viewport height. - + - Removed as of 6/2019. + Removed 05/2020. - - - toyoshim@chromium.org - altimin@chromium.org + chelu@chromium.org + tbansal@chromium.org - Total traffic data in bytes transferred over networks to load resources from - the frame creation until network activity quiets. + The ratio times 100 between the visible clickable region area of an anchor + element, and the viewport area. - + - Removed as of 8/2018. + Removed 05/2020. - - - toyoshim@chromium.org - ksakamoto@chromium.org + chelu@chromium.org + tbansal@chromium.org - Count traffic data size in bytes transferred over networks to load each - resource. + The highest navigation score of the anchor elements sent to the browser + process on a page load. This histogram is recorded when the webpage is + loaded. Normalized to a value between 0.0 and 100.0. - + - Removed 01/2016 and replaced by Blink.RestoredCachedStyleSheet2 + Removed 05/2020. - kouhei@chromium.org + chelu@chromium.org + tbansal@chromium.org - On each link stylesheet tag resolve, record whether a Blink MemoryCached - StyleSheetContents was reused. + The number of anchor element metrics sent to the browser process on a page + load. This histogram is recorded when the webpage is loaded. - + - Removed 04/2017. + Removed 2020-01 - kouhei@chromium.org + twellington@chromium.org - On each link stylesheet tag resolve, record which cache Blink hit. + What caused ChromeTabbedActivity#onStop() to be called, which indicates that + Chrome is sent to the background. - + - Used to justify distribution of serialized data in the wild, but unlikely to - be useful to track long-term. + Removed 2020-01 - platform-architecture-dev@chromium.org + twellington@chromium.org - Number of DOM wrappers serialized as part of an object passed to - postMessage, IndexedDB, or another API that serializes script values. + What happened when the user hit the system back button in + ChromeTabbedActivity. - + - Used to justify distribution of serialized data in the wild, but unlikely to - be useful to track long-term. + Removed 2019-01: New releases of Chrome+Android+ARM rely on NEON support. - platform-architecture-dev@chromium.org + fdegans@chromium.org - Number of JavaScript objects (other than DOM wrappers) serialized as part of - an object passed to postMessage, IndexedDB, or another API that serializes - script values. + Reports the FPU capabilities of the Android ARM device. This is recorded + once per browser session during startup. - + - Used to justify distribution of serialized data in the wild, but unlikely to - be useful to track long-term. + Removed 08/2017. Made decision in issue 736066 with already acquired data. + So this is no longer needed. - platform-architecture-dev@chromium.org + boliu@chromium.org - Number of primitive values (numbers, strings, etc.) serialized as part of an - object passed to postMessage, IndexedDB, or another API that serializes - script values. + Measure time from bindService call to onServiceConnected. This is part of + launching child services on Android that's under Android's control. Recorded + in the first onServiceConnected of a connection. - + - Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + Removed 08/2017. Made decision in issue 736066 with already acquired data. + So this is no longer needed. - hiroshige@chromium.org + boliu@chromium.org - Number of failed SharedBuffer::lock() calls for each resource type. - https://crbug.com/603791 + Boolean histogram that records whether bindServiced timed out. Timeout is + recorded in a delayed task, and success is recorded in onServiceConnected + callback. - + - Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + Unused as of 7/2019 - hiroshige@chromium.org + mdjones@chromium.org + twellington@chromium.org + The duration the Chrome Home bottom sheet was open. + + + + + Unused as of 7/2019 + + mdjones@chromium.org + twellington@chromium.org + The reason the bottom sheet was opened. + + + + + Removed 03/2018. Chrome Home is being deprecated. + + mdjones@chromium.org + twellington@chromium.org - Number of successful SharedBuffer::lock() calls for each resource type. - https://crbug.com/603791 + Records the reciprocal of the velocity of a swipe that did not result in the + bottom sheet opening. This value is recorded in microseconds per dp traveled + and is only recorded if the "chrome-home-swipe-logic" experiment + is set to "velocity". - + - Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + Removed 03/2018. Chrome Home is being deprecated. - hiroshige@chromium.org + mdjones@chromium.org + twellington@chromium.org - Number of SharedBuffer::unlock() calls for each resource type. - https://crbug.com/603791 + Records the reciprocal of the velocity of a swipe that resulted in the + bottom sheet opening and the user navigating to a URL or a different sheet + content. This value is recorded in microseconds per dp traveled. - + - Removed 9/2019 since the concept of timeouts have been removed. - https://crbug.com/1000376 + Removed 03/2018. Chrome Home is being deprecated. - goto@chromium.org - reillyg@chromium.org - ayui@chromium.org + mdjones@chromium.org + twellington@chromium.org - Records the timeout value specified when the API is called regardless of - whether or not the call actually timed out. The value of 0 indicates that no - value was specified. + Records the reciprocal of the velocity of a swipe that resulted in the + bottom sheet opening but the user taking no action (i.e. the next action is + the sheet closing). This value is recorded in microseconds per dp traveled. - + - Removed 9/2019 since the concept of timeouts have been removed. - https://crbug.com/1000376 + Removed 03/2018. Chrome Home is being deprecated. - goto@chromium.org - reillyg@chromium.org - ayui@chromium.org + mdjones@chromium.org + twellington@chromium.org - Records the duration from when the API is called to when the user gets timed - out of the SMS verification flow because no SMS was received within the - specified timeout window. + Records the reciprocal velocity of a swipe that resulted in the bottom sheet + opening. This value is recorded in microseconds per dp traveled and is only + recorded if the "chrome-home-swipe-logic" experiment is set to + "velocity". - + - Replaced with separate Style and Layout metrics and removed in M81. + Removed 01/2018 with the removal of the first version of Chrome Home. - - - - - - - schenney@chromium.org - layout-dev@chromium.org + mdjones@chromium.org + twellington@chromium.org - Time spent updating style and layout in the Blink document lifecycle. - - Note: As of M70, this histogram has stopped recording metrics on machines - with low-resolution clocks. + The result of showing the Chrome Home promo when launched from the overflow + menu. This action can only be performed if Chrome Home is enabled. - + - Renamed to Blink.UseCounter.AnimatedCSSProperties in 03/2018, M69. The old - blink UseCounter is flawed in OOPIF, so moved to the browser side instead. + Removed 01/2018 with the removal of the first version of Chrome Home. - chasej@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org - Records usage of animated CSS properties used across all frames in a page, - either statically or dynamically, from the time the page is initialised to - when it is closed or navigated away from. Each property is counted at most - once per page view except kTotalPagesMeasuredCSSSampleId which represents a - page load (enum value of 1) and is counted exactly once per page view. + The result of showing the Chrome Home promo when launched from the NTP. This + action can only be performed if Chrome Home is disabled. - + - Renamed to Blink.UseCounter.CSSProperties in 03/2018, M69. The old blink - UseCounter is flawed in OOPIF, so moved to the browser side instead. + Removed 01/2018 with the removal of the first version of Chrome Home. - chasej@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org - Records usage of CSS properties used across all frames in a page, either - statically or dynamically, from the time the page is initialised to when it - is closed or navigated away from. Each property is counted at most once per - page per view except kTotalPagesMeasuredCSSSampleId which represents a page - load (enum value of 1) and is counted exactly once per page view. + The result of showing the Chrome Home promo when launched from startup. This + action can only be performed if Chrome Home is disabled. - + - Feature moved from feature policy to document policy in M82. Histogram and - recording code removed for feature policy. Histogram and recording code will - be added for document policy. + Removed 01/2018 with the removal of the first version of Chrome Home. - iclelland@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org + The reason the Chrome Home promo was shown. + + + + + Removed 04/2018. Replaced with Android.Survey.DownloadResponseCode. + + danielpark@chromium.org + The response code of the completed survey download request. + + + + + Removed 04/2018. Replaced with Android.Survey.InfoBarClosingState. + + danielpark@chromium.org - Logs downscaling ratio in percentage for images enforced by feature policy - oversized-images policy going into origin trials in M75. If an image's - downscaling ratio is 1, it will be represented as 10 percent, if an image's - downscaling ratio is 5, it will be represented as 50 percents. Recorded when - oversized-images policy is enforced and the image is about to be painted. + If the infobar was visible when it was closed and if it was closed directly + or not. - + - Feature moved from feature policy to document policy in M82. Histogram and - recording code removed for feature policy. Histogram and recording code will - be added for document policy. + Removed 04/2018. Replaced with Android.Survey.ShowSurvey. - iclelland@chromium.org - feature-control@chromium.org + danielpark@chromium.org - Counts ImageFileFormats (lossy, lossless, webp animation, others) of images - enforced by feature policy unoptimized-images policy going into origin - trials in M75. Recorded when images finish decoding the mime type. + Whether or not the survey was successfully shown after its download. - + - Feature moved from feature policy to document policy in M82. Histogram and - recording code removed for feature policy. Histogram and recording code will - be added for document policy. + Removed 04/2018. Replaced with Android.Survey.SurveyFilteringResults. - iclelland@chromium.org - feature-control@chromium.org + danielpark@chromium.org - Logs compression ratio in percentage with 1KB overhead for lossless type - images enforced by feature policy unoptimized-lossless-images policy going - into origin trials in M75. If an image's compression ratio is 0.1, it will - be represented as 1 percent, if an image's compression ratio is 5, it will - be represented as 50 percents. Recorded when unoptimized-lossless-images - policy is enforced and the image finishes decoding its mime type. + The result of the survey filtering process. Each enum represents a different + filter that caught the user. This is recorded on cold starts when we check + if a user qualifies for a survey. - + - Feature moved from feature policy to document policy in M82. Histogram and - recording code removed for feature policy. Histogram and recording code will - be added for document policy. + Unused as of 7/2019 - iclelland@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org - Logs compression ratio with 1KB overhead for lossy type images enforced by - feature policy unoptimized-lossy-images policy going into origin trials in - M75. If an image's compression ratio is 0.1, it will be represented as 1 - percent, if an image's compression ratio is 5, it will be represented as 50 - percents. Recorded when unoptimized-lossy-images policy is enforced and the - image finishes decoding its mime type. + The time between the last time the Chrome Home bottom sheet was closed and + the next time it was opened. - + - Feature moved from feature policy to document policy in M82. Histogram and - recording code removed for feature policy. Histogram and recording code will - be added for document policy. + Unused as of 7/2019 - iclelland@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org - Logs compression ratio with 10KB overhead for lossless type images enforced - by feature policy unoptimized-lossless-images-strict policy going into - origin trials in M75. If an image's compression ratio is 0.1, it will be - represented as 1 percent, if an image's compression ratio is 5, it will be - represented as 50 percents. Recorded when unoptimized-lossless-images-strict - policy is enforced and the image finishes decoding its mime type. + The time between app creation and the first open of the Chrome Home bottom + sheet for this run of Chrome. - + - Replaced by Blink.UseCounter.Features in M67. See crbug.com/849695. + Unused as of 7/2019 - chasej@chromium.org - feature-control@chromium.org + mdjones@chromium.org + twellington@chromium.org - Count of how many page loads use various features. The PageVisits bucket is - incremented for each page load, and the other buckets incremented at most - once per PageVisit via the blink::UseCounter class. + Records whether or not the user preference for Chrome Home is set to + enabled. This is recorded whenever the browser is restarted and the state of + Chrome Home is first checked. This metric is only recorded if the user's + preference is set. -
- This histogram recorded values in the renderer process. With the addition of - OOPIF, the counts could be inaccurate due to multiple renderer processes for - a page. It was replaced by an implementation that records values in the - browser process. -
- + - Renamed to Blink.UseCounter.Features in 03/2018, M67. The old blink - UseCounter is flawed in OOPIF, so moved to the browser side (this) instead. + Removed 12/2018. CustomFeedback never shipped to 100% and is no longer + planned for launch. - chasej@chromium.org - feature-control@chromium.org + jwanda@chromium.org - Count of how many page loads use various features across all frames in a - page. The PageVisits bucket is incremented for each page load, and the other - buckets incremented at most once per PageVisit via the WebCore::UseCounter - class. This counter lives in browser process. + Recorded when the user selects a category button when in the Custom Feedback + UI. - + - Removed in 06/2018, M69 since the histogram is not really useful. See - https://crbug.com/804645. + Removed 12/2018. CustomFeedback never shipped to 100% and is no longer + planned for launch. - chasej@chromium.org - feature-control@chromium.org + jwanda@chromium.org - Like Blink.UseCounter.AnimatedCSSProperties but specifically for the case of - CSS properties used inside of an SVG image. + Recorded when a user selects an option related to their problem within the + Custom Feedback UI. -
- Warning: This histogram represents pre-renderer metrics and so is flawed - under OOPIF. - - This histogram counts usage of animated CSS properties only. Refer to - Blink.UseCounter.SVGImage.CSSProperties for details. -
- + - Removed in 06/2018, M69 since the histogram is not really useful. See - https://crbug.com/804645. + Removed Jan 2020. - chasej@chromium.org - feature-control@chromium.org + shaktisahu@chromium.org + clank-downloads@google.com - Like Blink.UseCounter.CSSProperties but specifically for the case of CSS - properties used inside of an SVG image. + Records the number of chips being shown on download home. Recorded during + initialization and also during any list change. -
- Warning: This histogram represents pre-renderer metrics and so is flawed - under OOPIF. + - The 'Total pages measured' bucket is incremented each time a new SVG image - is created. Note that the same SVG image can be used across multiple tabs in - a single renderer but this counts as a single usage. See - http://crbug.com/236262. -
+ + + Removed October 2019. The feature was dropped during implementation review. + + dtrainor@chromium.org + shaktisahu@chromium.org + clank-downloads@google.com + Recorded when a menu action is taken on the images section. - + - Removed in 05/2019, M76. Every SVGImage has it's own Page instance and - multiple web pages can share the usage of a single SVGImage. Previously - Blink.UseCounter.Features was recorded on the Blink side per Page; metrics - from SVGImage needed to be recorded in a separate histogram. Now that - metrics are recorded on the browser side, feature usage from SVGImage is - measured via page load metrics, on Blink.UseCounter.Features, once per page - load. This histogram is no longer needed. + Removed July 2019. The relaunch rarely happens. + xingliu@chromium.org + clank-downloads@google.com - Like Blink.UseCounter.Features except specifically for the case of SVG - Images. + Records instances when a notification is being launched for the first time + or relaunched due to the need to dissociate the notification from the + foreground (only on API less than 24). -
- Warning: This histogram represents pre-renderer metrics and so is flawed - under OOPIF. - - Count of how many SVG images use various features. The PageVisits bucket is - incremented each time a new SVG image is created. Note that the same SVG - image can be used across multiple tabs in a single renderer but this counts - as a single usage. See http://crbug.com/236262. -
- + - Removed 06/2017 in Issues 455099 and 681769 (M61). + Removed July 2019. - hiroshige@chromium.org + xingliu@chromium.org + clank-downloads@google.com - The count of XMLHttpRequest.setRequestHeader() calls where header values are - invalid/valid but affected by normalization/valid in RFC 7230. - https://crbug.com/455099. + Records the number of notifications that are already existing (presumably + displayed) when a new notification is being launched to help understand the + frequency of multiple downloads with downloads as a foreground service + disabled. - + - See BlinkGC.TimeForAtomicPhaseMarking. + Removed July 2019. - mlippautz@chromium.org - oilpan-reviews@chromium.org + xingliu@chromium.org + clank-downloads@google.com - Duration of finishing marking the transitive closure of objects during the - final Blink garbage collection pause. Recorded at the end of each garbage - collection. + Records the number of notifications that are already existing (presumably + displayed) when a new notification is being launched to help understand the + frequency of multiple downloads with downloads as a foreground service + enabled. - + - Removed 06/2018. The sample taken here was a mix of marking, sweeping and - compaction. Replaced by BlinkGC.AtomicPhaseMarking for the marking phase and - BlinkGC.TimeForTotalCollectGarbage for the overal time. + Deprecated Jan 2020. - haraken@chromium.org + twellington@chromium.org + clank-downloads@google.com - Duration of time taken to run Heap::collectGarbage(). Recorded at the end of - each garbage collection. + The extension type for non-incognito download items that match the + "other" filter type. Recorded when the download UI is initialized. - + - Removed as of 07/2019. Use Memory.Renderer.* and - Memory.Experimental.Renderer2.* instead. + Deprecated Jan 2020. - haraken@chromium.org + twellington@chromium.org + clank-downloads@google.com - The committed memory size in Blink GC. The value is reported when we see the - highest memory usage we've ever seen in the renderer process. + The extension type for downloads that match the "other" filter + type. Recorded when a download fails to open. - + - Removed 07/2019. Replaced by BlinkGC.TimeForCompleteSweep. + Deprecated Jan 2020. - haraken@chromium.org - Duration of time taken to run ThreadState::completeSweep(). + twellington@chromium.org + clank-downloads@google.com + + The extension type for downloads that match the "other" filter + type. Recorded when a download is opened. + - + - Removed at 2014 Jan. + Deprecated Jan 2020. - haraken@chromium.org + twellington@chromium.org + clank-downloads@google.com - Duration of time taken to run ThreadState::performPendingSweep(). + The extension type for downloads that match the "other" filter + type. Recorded when downloads are shared through the download manager. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed 06/2016 with code removal of download home V1 to follow. - mlippautz@chromium.org - oilpan-reviews@chromium.org + shaktisahu@chromium.org + clank-downloads@google.com - Duration of finishing marking the transitive closure of objects during the - final Blink garbage collection pause. Only recorded when incremental marking - finalization took at least 40ms. + Recorded when the user clicks the info button on download home to toggle the + storage info. The state recorded is after the visibility is toggled. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed on Jan 2020. - mlippautz@chromium.org - oilpan-reviews@chromium.org + xingliu@chromium.org + clank-downloads@google.com - Duration of time taken to run eager sweep finalizers finalizers. Only - recorded when incremental marking finalization took at least 40ms. + The duration between when an audio file is downloaded and when the file is + opened, only recorded when the user opens the file in download home UI. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed on Jan 2020. - mlippautz@chromium.org - oilpan-reviews@chromium.org + xingliu@chromium.org + clank-downloads@google.com - Duration of time for incremental marking finalization. Only recorded when - incremental marking finalization took at least 40ms. + The duration between when a video file is downloaded and when the file is + opened, only recorded when the user opens the file in download home UI. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed 2019-09 in favour of + Android.FeatureModules.CachedAwakeInstallDuration. - mlippautz@chromium.org - oilpan-reviews@chromium.org + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org - Duration of time taken to invoke pre finalizers. Only recorded when - incremental marking finalization took at least 40ms. + Duration of successful installs for each dynamic feature module. Only + contains install durations for modules first requested *before* Chrome + started last and may therefore be installed from cache. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed 2019-09 in favour of + Android.FeatureModules.UncachedAwakeInstallDuration. - mlippautz@chromium.org - oilpan-reviews@chromium.org + + + agrieve@chromium.org + fredmello@chromium.org + tiborg@chromium.org + wnwen@chromium.org - Duration of time taken for weak processing. Only recorded when incremental - marking finalization took at least 40ms. + Duration of successful installs for each dynamic feature module. Only + contains install durations of modules first requested *after* Chrome started + last and are therefore unlikely to be installed from cache. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed 7/2019. No longer tracked. - mlippautz@chromium.org - oilpan-reviews@chromium.org + twellington@chromium.org - Duration of time taken to visit cross thread persistents. Only recorded when - incremental marking finalization took at least 40ms. + The number of selected items the user opened in new tabs from the native + Android history page. - + - Removed 07/2019. Data gathering finished with the result that slow marking - finalization was mostly caused by visiting DOM wrappers or premature - finalization. + Removed 7/2019. No longer tracked. - mlippautz@chromium.org - oilpan-reviews@chromium.org + twellington@chromium.org - Duration of time taken to visit DOM wrappers. Only recorded when incremental - marking finalization took at least 40ms. + The number of selected items the user removed from the native Android + history page. - + - Removed 07/2019. Coalescing is not used anymore. + Not being recorded as of 2017. - haraken@chromium.org - hpayer@chromium.org + mariakhomenko@chromium.org - Duration of memory coalesce operation in the Blink GC. Reported once per - coalesce operation. + Measures the amount of time spent in the getInstantAppIntent() API call. - + - As of 02/2017, the code to stop Blink threads was removed. + Removed in M86. No longer tracked. - haraken@chromium.org + peconn@chromium.org - Duration of time taken to stop all Blink threads before starting a GC. + Records the usage of the Browser.EXTRA_HEADERS field for Intents that Chrome + receives, breaking down by type of header and by whether the launching app + was first or third party. - + - As of 07/2019, this metric is replaced by BlinkGC.TimeForSweepingSum. + Removed in M86. No longer tracked. - haraken@chromium.org - Accumulated time taken to sweep all objects. + jochen@chromium.org + peconn@chromium.org + + Records hashes of header names used in the Browser.EXTRA_HEADERS fields for + Intents that Chrome receives that aren't on the CORS header safelist. This + can be used to match against known types of headers to measure their + frequencies. + - + - As of 02/2017, the code for thread-local weak processing was removed. + Removed 7/2019. No longer tracked. - haraken@chromium.org - Duration of time taken to run thread-local weak processing. + twellington@chromium.org + tedchoc@chromium.org + + Renaming the old tab metadata file failed during multi-instance migration. + Only true is recorded. + - + - Removed in M45. + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + The new tab metadata file already existed when multi-instance migration was + attempted. Only true is recorded. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + Records whether the screen width is below 600dp when the activity is in + Android N multi-window mode. True if the screen width is less than 600dp and + false if is greater than or equal to 600dp. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + Records the screen height in dp when the activity is in Android N + multi-window mode. Clamped at 200dp to 1200dp. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + Records the screen width in dp when the activity is in Android N + multi-window mode. Clamped at 200dp to 1200dp. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + Records the screen width in dp when the activity is in Android N + multi-window mode and the width is below 600dp. + + + + + + Removed in July 2019. See https://crbug.com/975556. + + michaelbai@chromium.org + + The return value of NativeLibraryPreloader.loadLibrary() in browser process, + is recorded once per browser process start. + + + + + + Removed in July 2019. See https://crbug.com/975556. + + michaelbai@chromium.org + + The return value of NativeLibraryPreloader.loadLibrary() in renderer + process, is recorded once per renderer process start. + + + + + + Removed from the code in July 2019. See https://crbug.com/975701. + + jeffreycohen@chromium.org + ewald@chromium.org + + At startup, records whether the Chrome application has been granted the read + storage permission on Android. + + + + + + Removed in July, 2020 + + twellington@chromium.org + chrome-android-app@chromium.org + + Records the number of other devices listed in recent tabs page when recent + tabs page is loaded. + + + + + + Removed in July, 2020 + + twellington@chromium.org + chrome-android-app@chromium.org + + Records the number of recently-closed tabs shown in recent tabs page when + recent tabs page is loaded. + + + + + + Removed in July, 2020 + + twellington@chromium.org + chrome-android-app@chromium.org + + Records the total number of tabs listed in recent tabs page (sum of all tab + from other devices plus recently-closed tabs) when recent tabs page is + loaded. + + + + + + Removed from the code in July 2019. See https://crbug.com/975749. + + rsesek@chromium.org + + Reports the level of kernel support for the seccomp-bpf sandbox using + prctl(PR_SET_SECCOMP). + + + + + + Removed from code June 2019. See https://crbug.com/577190 for context. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from checking for + whether play services is available. + + + + + + Removed July 2019 (http://crbug.com/984291). + + estevenson@chromium.org + wnwen@chromium.org + + Measures the amount of time due to a StrictMode violation from checking for + whether a package is Google signed. + + + + + + Removed 05/2016 in Issue 582539 with the removal of document mode. + + hartmanng@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from fetching the + DocumentMode shared preferences file. + + + + + + Removed 05/2016 in Issue 582539 with the removal of document mode. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from document mode + loading its prioritized tab's state. + + + + + + Removed from code June 2019. See https://crbug.com/508615 for context. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from fetching and + possibly creating the downloads directory. + + + + + + Removed from code June 2019. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from custom + notification builder through date formatting. + + + + + + Removed from code June 2019. + + wnwen@chromium.org + + Measures the amount of time due to a StrictMode violation from snippet UI + through date formatting. + + + + + + Removed from code June 2019. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from looking up a + webapp's MAC on startup. + + + + + + Removed from code June 2019. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from fetching for + creating the webapp directory. + + + + + + Removed from code June 2019. + + wnwen@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from reading and + saving webapp state. + + + + + + Removed from code July 2019. + + hartmanng@chromium.org + yfriedman@chromium.org + + Measures the amount of time due to a StrictMode violation from fetching the + Webapp shared preferences file. + + + + + + Removed 2020-04. + + tedchoc@chromium.org + + The distribution of results when running ExternalNavigationHandler, this + shows how often we send intents to be handled by other applications. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + + The number of bytes read for the other tab state's metadata file when + merging tab states in Android N+. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + + The number of normal and incognito tabs merged (for Android N+ + multi-instance). This will be logged for both cold-start and non-cold-start + merging assuming that the native library is loaded. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + + Measures the amount of time it takes to restore state for each merged tab + (for Android N+ multi-instance). This will only be logged for non-cold-start + merging, because restoring merged tabs is not distingushed from restoring + regular tabs on cold start. + + + + + + Removed May 2020 because this only captures sessions up to 10 seconds long. + Use Android.WebView.DevUi.SessionDuration2 instead, which captures sessions + up to an hour. + + + + ntfschr@chromium.org + hazems@chromium.org + src/android_webview/OWNERS + + Records the time spent using a specific tool, from creation to destruction. + + + + + + Replaced by Android.WebView.ExtraHeadersRedirect 2020-07 + + torne@chromium.org + src/android_webview/OWNERS + + Record when extra headers are added to requests by AwURLLoaderThrottle and + whether they were kept or removed during redirects. + + + + + + Removed in M79. Obtained required data from M78. + + boliu@chromium.org + ericrk@chromium.org + + Record in a functor draw whether stencil test is enabled by Android HWUI. + This is recorded every frame. Note some OS versions never use stencil so + worth checking result split by OS version. + + + + + + Removed 2019/10/11. This histogram was never well understood and the + underlying feature has been shipped for some time anyway. + + smcgruer@chromium.org + + Records if a data url passed to loadUrl had a '#' character. This is to be + used in the effort to deprecate the incorrect treatment of '#' characters in + data URIs; see http://crbug.com/823666#c30. + + + + + + Removed in April 2020. The backfill logic is deemed no longer necessary to + keep around. + + ntfschr@chromium.org + src/android_webview/OWNERS + + Records whether WebView needed to backfill the install date pref with + Android frameworks APIs. Recorded once during startup (metrics service + initializtion). + + + + + + Removed in April 2020. Network Service has launched, and we don't intend to + follow up on this metric. + + ntfschr@chromium.org + timvolodine@chromium.org + + Records information about the specified MIME types for app-provided content + loaded in Android WebView. At the moment, this focuses on + shouldInterceptRequest, ContentProvider-supplied content, and app + assets/resources (where we expect the app to use proper file extensions to + indicate MIME type), and is recorded as part of the process of loading each + resource. This may apply to any type of resource (frame HTML, subresource, + etc.). + + + + + + Removed 09/2020. These are no longer being tracked. + + laisminchillo@chromium.org + timvolodine@chromium.org + + The WebViewClient SSL error code as received by onReceivedSslError. + + + + + + Removed 04/2020. These metrics are tracked generally for SafeBrowsing, and + WebView no longer needs specializations. + + laisminchillo@chromium.org + timvolodine@chromium.org + + Records the WebViewClient safe browsing threat type as returned by + onSafeBrowsingHit callback. + + + + + + Removed in M73. Bundles have shipped. + + tiborg@chromium.org + yfriedman@chromium.org + + Result of applying a workaround to fix a crash on Android O if the WebView + provider is a split APK (see crbug.com/889954 for more details). + + + + + + Removed from code July 2018. Variations in WebView has launched. + + changwan@chromium.org + + Indicates whether variations is enabled. We want to know how enabling + variations affects metrics, but we can't enable variations as a variations + study, since variations can't enable/disable itself. Instead, WebView + hard-codes a random variable for enabling variations, and reports the result + in this histogram. + + + + + + Removed as of 06/2020. Mostly tracked with Snackbar.Shown. + + dtrainor@chromium.org + + When a user closes a tab an undo toast will popup on certain devices giving + the user the chance to undo closing that tab. This stat tracks how the user + interacts with that UI and what actions they take. A cold start means that + the undo bar wasn't showing when it was triggered to show again. A warm + start means that it was. Warm starts can happen when the user closes + multiple tabs close together. When the undo bar is dismissed, all closes + that were queued up to be undone are committed. This can happen either by a + timeout or by an action by the user to move to another part of the UI. + + + + + + Removed as of 01/2019. Replaced with + Animation.AnimationWorklet.MutateDuration. + + majidvp@chromium.org + animations-dev@chromium.org + + The time it takes for AnimationWorkletGlobalScope to produce a mutation + update. This includes all V8 script execution cost. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + AppCache check response result code. + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + Time elapsed between a completion task being queued and run. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + The amount of time taken to run a completion task on the IO thread. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + Tracks the number of times corruption is detected in the sql database. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + AppCache initialization result code. + + + + + Removed 2018-03-20. No longer tracked. + + mek@chromium.org + + How long URLRequests to be retrieved from the appcache are delayed. + + + + + + Removed 2018-03-20. No longer tracked. + + mek@chromium.org + + How long URLRequests that result in a synthesized error are delayed. + + + + + + Removed 2018-03-20. No longer tracked. + + mek@chromium.org + + How long URLRequests to be retrieved over the network are delayed. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + Counts the number of appcached page loads for secure vs insecure origins. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + Tracks the success rate of retrieving a main resource from the appcache. + + + + + + Removed 01/2020. Feature has been removed. + + pwnall@chromium.org + mek@chromium.org + + The proportion of manifests that use patterns in valid FALLBACK: entries. + Only tracks manifests that were successfully parsed. + + + + + + Removed 01/2020. Feature has been removed. + + pwnall@chromium.org + mek@chromium.org + + The proportion of manifests that use patterns in valid NETWORK: entries. + Only tracks manifests that were successfully parsed. + + + + + + Removed 01/2020. Feature has been removed. + + pwnall@chromium.org + mek@chromium.org + + The proportion of manifests that use patterns in any valid entries. Only + tracks manifests that were successfully parsed. + + + + + + Removed as of 5/2019. No longer needed. + + cmp@chromium.org + pwnall@chromium.org + + The proportion of ParseManifest calls that are triggered using a valid vs an + invalid manifest URL. + + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + Identifies where a missing manifest was detected occured. + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + + Logged on each occurrence of there being no record for the manifest file in + the entries table. + + + + + + Removed on 2019-06-17. No longer tracked. + + mek@chromium.org + + Tracks the success rate of retrieving a sub resource from the appcache. + + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + + Time elapsed between a background task being queued and run. + + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + The amount of time taken to run a background task. + + + + + Removed on 2020-08-20. No longer tracked. + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times while handling a 304 response a cached response + has a Vary header while the incoming 304 response doesn't. + + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + AppCache update job result code. + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + Percent completion at point of failure of an update job. + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + + Whether the resource causing the failure was from a different origin. + + + + + + Removed 2019-06-17. No longer tracked. + + mek@chromium.org + + Whether any progresss had been made in the 5 minutes preceeding failure. + + + + + + Removed 11/2017 in issue 600915 with the removal of app list on platforms + other than Chrome OS. + + mad@chromium.org + Interactions with the App Launcher promo dialog. + + + + + Removed October 2019, replaced by + Apps.AppList.ZeroStateResultsList.LaunchedItemPositionV2, which uses + different bucketing. + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The position index of an item launched from zero state search results. + + + + + + Removed October 2019, replaced by + Apps.AppList.ZeroStateResultsList.NumImpressionTypesV2, which uses different + bucketing. + + wrong@chromium.org + tby@chromium.org + jiameng@chromium.org + + The number of item types included in each zero state impression set. + + + + + + Removed June 2019, replaced by + Apps.AppList.ZeroStateSearchResultRemovalDecision. + + jennyz@chromium.org + newcomer@chromium.org + + The decision of the user whether to remove a zero state search result. This + is gathered per click of a remove or cancel button of a search result + removal confirmation dialog. + + + + + + Removed as of 04/2019 in favor Apps.AppListAppLaunchedV2. + + newcomer@chromium.org + + The number of apps launched from the launcher. This is logged each time an + app is launched. The bucket denotes whether the app is suggested. + + + + + + Removed as of 04/2019 in favor Apps.AppListAppLaunchedV2. + + newcomer@chromium.org + + The number of apps launched from the fullscreen launcher. This is logged + each time an app is launched. The bucket denotes whether the app is + suggested. + + + + + + App list doesn't support doodles anymore. + + calamity@chromium.org + + The number of user interactions with the app list doodle. This is logged + once per action. + + + + + + Removed January 2020, this was a debugging metric that was too expensive to + keep in the code. + + Results on beta were: 60% present and shown, 5% present and not shown, and + 35% absent. + + tby@chromium.org + wrong@chromium.org + jiameng@chromium.org + + Emitted when the launcher updates the displayed zero-state search results. + Records whether a) a Drive QuickAccess result was displayed, b) a DQA result + was present in the candidate results list but wasn't one of the top 5 so was + not displayed, or c) no DQA results were in the results list. + + + + + + Removed 03/2018 with Mash AppList refactoring. + + tapted@chromium.org + + The trigger that caused the app list to be enabled. Recorded when the user + first shows the app list. If not shown after one hour, will be recorded + then. If Chrome was not running at the one-hour mark, will be recorded + during the next Chrome startup. + + + + + + Removed January 2020, the app list launch recorded has been removed. + + tby@chromium.org + charleszhao@chromium.org + + Reports error states of the app list launch recorder system. + + + + + + Removed 2020-05. Not needed any longer. + + calamity@chromium.org + + The minimum number of arrow keys a user would need to press to navigate to + the opened search result. This is gathered per click of a search result. + + + + + + Removed March 2019. Replaced with Apps.AppListSearchResultOpenTypeV2. + + tapted@chromium.org + + The type of app list search result that was opened by the user. This is + gathered per SearchResult opened. Only recorded for search results shown in + the search result page of the launcher, except for M-62 where suggestion + chips were recorded as search results (https://crbug.com/919550). M-62 + should be filtered out when viewing this histogram to ignore the metrics + caused by the above mentioned bug. + + + + + + Removed 04/2020. The related app ranking experiments have finished. + + tby@chromium.org + jiameng@chromium.org + + The index of a clicked result in the search result app tiles and the length + of the search query. The index is relative to the SearchTileItemListView, + not the overall position in the suggestion window. + + + + + + Removed 2018-03. + + tapted@chromium.org + + Time between enabling the app list, and a user explicitly choosing to show + it. If the app list is not shown after one hour, an entry in the last bucket + is recorded. If the user installs a second packaged app within one hour, or + if the app list was not enabled by installing a packaged app from the Web + Store, no time value is recorded - only Apps.AppListHowEnabled. + + + + + + Removed 07/2016 in Issue 600915 with the removal of the app list on Windows. + + tapted@chromium.org + + The amount of time spent in warmup (in WarmupForProfile call). This will + tell us how long warmup blocks the UI. + + + + + + Removed 08/2020. File handler registration is done through shortcuts + creation, replaced by WebApp.Shortcuts.Creation.Result. + + phillis@chromium.org + cmumford@chromium.org + + Records the result of file handler registration for PWA on MacOS + + + + + + Obsolete - tracks actions in UI that did not launch. + + tbarzic@chromium.org + tbuckley@chromium.org + + The action the user took on the lock screen UI shown when lock screen app + window is in background, shown under the lock screen. + + + + + + There was only one valid value starting in M69 and code to record the values + was removed in M85. + + stevenjb@chromium.org + + The type of app window opened (through the chrome.app.window API). + + + + + + Removed 06/2019. Replaced by Arc.CustomTabs.SessionLifetime2.All to extend + the max value. + + hashimoto@google.com + shihuis@google.com + Lifetime of each session. Recorded when a session ends. + + + + + Removed 06/2019. Replaced by Arc.CustomTabs.SessionLifetime2.Closed to + extend the max value. + + hashimoto@google.com + shihuis@google.com + + Lifetime of each session. Recorded when a session is closed. + + + + + + Removed 06/2019. Replaced by + Arc.CustomTabs.SessionLifetime2.ForwardedToNormalTab to extend the max + value. + + hashimoto@google.com + shihuis@google.com + + Lifetime of each session. Recorded when a session ends because the tab was + forwarded to a normal tab. + + + + + + Removed April 2018 and replaced by ChromeOS.Apps.IntentPickerAction. + + elijahtaylor@google.com + shihuis@google.com + ARC intent handler action taken by user. + + + + + Removed April 2018 and replaced by + ChromeOS.Apps.IntentPickerDestinationPlatform. + + elijahtaylor@google.com + shihuis@google.com + + ARC intent handler destination platform. The destination may be specified + due to the user explicit selection or a previously stored preference. + + + + + + Removed 09/2020 for Issue 1124182. + + elijahtaylor@google.com + shihuis@google.com + + The oom_badness score of a OOM killed process as reported by kernel. + + + + + + Removed 09/2020 for Issue 1124182. + + elijahtaylor@google.com + shihuis@google.com + The elapsed time since last OOM kill event. + + + + + Renamed to Arc.LowMemoryKiller.FreedSize on 2016/03/24. + + elijahtaylor@google.com + The memory size freed by each low memory kill event. + + + + + Renamed to Arc.LowMemoryKiller.TimeDelta on 2016/03/24. + + elijahtaylor@google.com + The elapsed time to last low memory kill event. + + + + + Removed Jan 2020 for R82. + + zentaro@chromium.org + cros-peripherals@chromium.org + + The lock screen action has two accelerators: - Ctrl+Shift+L which is + deprecated. - Search+L which is new. This histogram shows the number of + times each accelerator (deprecated and new) is used. + + + + + + Removed 01/2017 for Issue 672905. + + afakhry@chromium.org + + The switch to the next IME action has two accelerators: - Shift+Alt which is + deprecated. - Ctrl+Shift+Space which is new. This histogram shows the number + of times each accelerator (deprecated and new) is used. + + + + + + Removed 02/2017 due to lack of usage. + + kuscher@google.com + rbyers@chromium.org + + Number of active touch-points when a new touch-point is added. + + + + + + Removed 10/2016 for Issue 616581. + + tbuckley@chromium.org + + The amount of time between selecting an item from the Ash app list. Not + recorded on the first time an item is selected from the app list after + startup. + + + + + + Removed from code as of 04/2020. + + + + yulunwu@chromium.org + tbarzic@chromium.org + + Tracks usage of the contextual nudge for the user gesture education. + + + + + + Removed 03/2020, and replaced by Ash.Desks.DesksCount2. This was broken as + it did report desks count during the creation of the first-ever created desk + after boot. + + afakhry@chromium.org + + Emitted when there's a change in the virtual desks count whether due to desk + creation or removal. Specifies the number of available desks. + + + + + + Removed 03/2020, and replaced by Ash.Desks.NewDesk2. This was broken as it + did report the creation of the first-ever created default desk after boot as + being created by the new-desk button. + + afakhry@chromium.org + + Emitted when a virtual desk is created to specify the source of this action, + i.e. whether from the new-desk button, keyboard shortcut. + + + + + + Removed 10/2017, replaced by Ash.DisplayColorManager.IccFileDownloaded + + mcasas@chromium.org + dcastagna@chromium.org + + This boolean keeps track if a request for an ICC for a specific product id + has been successful or not. + + + + + + Removed 08/2014 in Issue 352654, and replaced by Event.GestureCreated. + + kuscher@google.com + rbyers@chromium.org + + The gesture-events recognized and dispatched by the browser gesture + recognizer. + + + + + + Removed on 01/2020, no longer useful. + + kuscher@google.com + rbyers@chromium.org + + The gesture-events recognized and dispatched for UI components owned by Ash. + For browser gestures, see Event.Touch.GestureType. + + + + + + Removed 27/05/2020, the histogram has been revised as we do not count pod + switching anymore and the metric was not recorded on shutdown. New + histogram: Ash.Login.Lock.NbPasswordAttempts.UntilFailure + + kerrnel@google.com + + The number of incorrect password entered in ChromeOS login/lock screen until + the user gives up (switch pods or user sign out the current session or + shutdown the device). + + + + + + Removed 27/05/2020, the histogram has been revised as we did not count + successful authentification on login screen and successful authentification + on lock screen wasn't recorded due to a bug. New histogram: + Ash.Login.Lock.NbPasswordAttempts.UntilSuccess + + kerrnel@google.com + + The number of incorrect password entered in ChromeOS login/lock screen until + a successful attempt. + + + + + + Removed 05/2019; no longer need to track this. + + sky@chromium.org + + The delta between when chrome main starts to when the Chrome OS system UI + (ash) is visible to the user (specifically the first time pixels are lit up + on the primary display showing the Chrome OS system UI). + + + + + + Removed 02/2017 due to lack of usage. + + kuscher@google.com + rbyers@chromium.org + The duration of mostly stationary long-duration touches. + + + + + Removed 10/2016 for Issue 616581. + + tbuckley@chromium.org + + The number of seconds between tab switches triggered by a user gesture (e.g. + Ctrl+T, Ctrl+1, tapping or clicking the tab strip, etc). + + + + + + Removed 12/2013 in r239809, and replaced by Ash.TouchDuration2. + + kuscher@google.com + The duration of a touch-sequence. + + + + + Removed 08/2014 in Issue 352654, and replaced by Event.TouchDuration. + + kuscher@google.com + rbyers@chromium.org + The duration of a touch-sequence. + + + + + Removed 08/2014 in Issue 352654, and replaced by Event.TouchMaxDistance. + + kuscher@google.com + rbyers@chromium.org + + The maximum euclidean distance in dips which a touch point has travelled + away from its starting point. Only measured for single finger gestures. + + + + + + Removed 02/2017 due to lack of usage. + + kuscher@google.com + rbyers@chromium.org + The interval between touch-move events. + + + + + Removed 07/2018 due to lack of usage. + + kuscher@google.com + The position of the touch-events along the X axis. + + + + + Removed 07/2018 due to lack of usage. + + kuscher@google.com + The position of the touch-events along the Y axis. + + + + + Removed 07/2018 due to lack of usage. + + kuscher@google.com + The radius of a touch event. + + + + + Removed 02/2017 due to lack of usage. + + kuscher@google.com + rbyers@chromium.org + + The number of rapid touch-starts that happened within a short interval. + Logged once for each such burst group. + + + + + + Removed as of 2/2018. Currently there is only one type of Wallpaper App. + + xdai@chromium.org + + The Wallpaper App that the user is using right now on Chrome OS. It's the + app that is used when the user right clicks on desktop and selects "Set + wallpaper" or when the user selects "Set wallpaper" from + chrome://settings page. This is recorded at user login. + + + + + + Removed as of 8/2018. + + tbuckley@chromium.org + + The time taken to extract colors from wallpapers. Recorded each time the + wallpaper image changes. It may contain multiple colors extracted. + + + + + + Removed as of 8/2018. + + tbuckley@chromium.org + + The time taken to extract colors from 'expensive' wallpapers. Recorded each + time the wallpaper image changes and the color extraction is expected to be + expensive, e.g. image size > 100 pixels. This includes time spent + switching threads. It may contain multiple colors extracted. + + + + + + Removed as of 6/2017. + + tbuckley@chromium.org + + Tracks the success rate for wallpaper color extraction. Recorded each time + the wallpaper image changes. + + + + + + Removed as of 11/2012. Use of indices has been removed. + + kuscher@google.com + + The wallpaper index if one of the default wallpapers has been selected. + Recorded at user login. Currently only for the old wallpaper picker UI. + + + + + + Removed as of 04/2017 in favor of Ash.Wallpaper.ColorExtraction.Durations + and Ash.Wallpaper.ColorExtraction.UserDelay. + + tbuckley@chromium.org + + The time taken to extract colors from wallpapers. Recorded each time the + wallpaper image changes. NOTE, this measure also included the time spent + jumping between threads, thus it was deprecated in favor of + Ash.Wallpaper.ColorExtraction.Durations. + + + + + + Removed as of 8/2018. + + tbuckley@chromium.org + + The time taken to resize wallpapers. Recorded once each time the wallpaper + changes (e.g. initial wallpaper loading at boot, switching user avatar at + login screen, switching between logged in users, user selects new wallpaper, + etc). + + + + + + Removed as of 07/2019. + + wutao@chromium.org + tbuckley@google.com + + The amount of time the Alt key is held after pressing Alt+Tab to begin + cycling through windows. + + + + + + Removed as of 07/2019. + + wutao@chromium.org + tbuckley@google.com + + When a window is selected after pressing Alt+Tab, records that window's + position in the global MRU ordering. 1 represents the most-recently used + window, 2 represents the next most-recently used window, and so on. Recorded + when Alt+Tab cycling stops, i.e., when Alt key is released. + + + + + + Removed 01/2020 in Issue 989794 since we are now using focus rings instead + of a highlight. The focus rings have no animations. + + yjliu@chromium.org + chromeos-wmp@google.com + + Relative smoothness of showing window animation when the highlight moves to + the next window in the window cycle view when alt + tab is pressed. 100% + represents ideally smooth 60 frames per second. 50% represents when only 30 + frames per second is achieved during the animations. 0% should not happen. + + + + + + Removed 03/2019 in favor of Ash.Overview.AnimationSmoothness.Close.Clamshell + and Ash.Overview.AnimationSmoothness.Close.Tablet + + estade@chromium.org + + Relative smoothness of animations when closing a window in overview mode. + 100% represents ideally smooth 60 frames per second. + + + + + + Removed 03/2019 in favor of Ash.Overview.AnimationSmoothness.Enter.Clamshell + and Ash.Overview.AnimationSmoothness.Enter.Tablet + + estade@chromium.org + + Relative smoothness of animations when entering overview mode. 100% + represents ideally smooth 60 frames per second. + + + + + + Removed 03/2019 in favor of + Ash.Overview.AnimationSmoothness.Exit.ClamshellMode and + Ash.Overview.AnimationSmoothness.Exit.TabletMode + + estade@chromium.org + + Relative smoothness of animations when exiting overview mode. 100% + represents ideally smooth 60 frames per second. + + + + + + Removed as of 06/2014. No longer relevant since alt-tab switching was + separated from WindowSelector. + + flackr@chromium.org + kuscher@google.com + + The amount of time the Alt key is held after pressing Alt+Tab to begin + cycling through windows. + + + + + + Removed as of 01/2020. + + wutao@chromium.org + + Relative animation smoothness of resizing assistant container window. 100% + represents ideally smooth 60 frames per second. 50% represents when only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded when the container window resizing is finished. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a click on a proactive suggestions card by the user. This histogram + is recorded for every click event while derivative metrics are recorded for + splicing by category, index, and veId only when those respective attributes + are known. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for a proactive suggestions card that was clicked + by the user. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records the index for a proactive suggestions card within its list that was + clicked by the user. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records the VE ID for a proactive suggestions card that was clicked by the + user. + + + + + + Removed 11/2018 because a need was discovered for a non-boolean value. + Superseded by Accessibility.Android.AnimationsEnabled2. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records an attempt to show a proactive suggestion to the user for the first + time. + + + + + + Associated with an experimental feature which was removed in M85. + + + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for an attempt to show a proactive suggestion to + the user for the first time. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a result of having shown a proactive suggestion to the user for the + first time. + + + + + + Associated with an experimental feature which was removed in M85. + + + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user for the first time. + + + + + + Removed 11/2018 because a need was discovered for a non-boolean value. + Superseded by Accessibility.Android.AnimationsEnabled2. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a result for a proactive suggestions server request. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for a proactive suggestions server request that + resulted in error. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for a proactive suggestions server request that + resulted in a successful response containing content. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for a proactive suggestions server request that + resulted in a successful response that did not contain content. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records an attempt to reshow a proactive suggestion to the user that has + already been seen. + + + + + + Associated with an experimental feature which was removed in M85. + + + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for an attempt to reshow a proactive suggestion + to the user that has already been seen. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a result of having reshown a proactive suggestion to the user that + has already been seen. + + + + + + Associated with an experimental feature which was removed in M85. + + + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having reshown a proactive suggestion to the + user that has already been seen. + + + + + + Replaced in M80 by Assistant.ProactiveSuggestions.FirstShowAttempt and + Assistant.ProactiveSuggestions.ReshowAttempt. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records an attempt to show a proactive suggestion to the user. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowAttempt.AbortedByDuplicateSuppression.ByCategory + and + Assistant.ProactiveSuggestions.ReshowAttempt.AbortedByDuplicateSupression.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for an attempt to show a proactive suggestion to + the user that was aborted due to duplicate suppression. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowAttempt.Success.ByCategory and + Assistant.ProactiveSuggestions.ReshowAttempt.Success.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for an attempt to show a proactive suggestion to + the user that was successful. + + + + + + Replaced in M80 by Assistant.ProactiveSuggestions.FirstShowResult and + Assistant.ProactiveSuggestions.ReshowResult. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a result of having shown a proactive suggestion to the user. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowResult.Click.ByCategory and + Assistant.ProactiveSuggestions.ReshowResult.Click.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user that resulted in a click. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowResult.CloseByContextChange.ByCategory. + and + Assistant.ProactiveSuggestions.ReshowResult.CloseByContextChange.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user that resulted in being closed due to a change in context. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowResult.CloseByTimeout.ByCategory and + Assistant.ProactiveSuggestions.ReshowResult.CloseByTimeout.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user that resulted in being closed due to timeout. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowResult.CloseByUser.ByCategory and + Assistant.ProactiveSuggestions.ReshowResult.CloseByUser.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user that resulted in being closed by the user. + + + + + + Replaced in M80 by + Assistant.ProactiveSuggestions.FirstShowResult.Teleport.ByCategory and + Assistant.ProactiveSuggestions.ReshowResult.Teleport.ByCategory. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for having shown a proactive suggestion to the + user that resulted in teleportation directly to a single result. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records an impression of a proactive suggestions view seen by the user. This + histogram is recorded for every impression event while derivative metrics + are recorded for splicing by category and veId only when those respective + attributes are known. Note that this histogram is primarily used with + Assistant.ProactiveSuggestions.CardClick to give an idea of CTR. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records a content category for a proactive suggestions view that was seen by + the user. Note that this histogram is primarily used with + Assistant.ProactiveSuggestions.CardClick.ByCategory to give an idea of CTR. + + + + + + Associated with an experimental feature which was removed in M85. + + xiaohuic@chromium.org + dmblack@google.com + croissant-eng@chromium.org + + Records the VE ID for a proactive suggestions view that was seen by the + user. Note that this histogram is primarily used with + Assistant.ProactiveSuggestions.CardClick.ByVeId to give an idea of CTR. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of DnsAttempts before DnsTransaction completes with failure. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of DnsAttempts before DnsTransaction completes successfully. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + Whether DnsConfig was parsed successfully. + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + Whether the first valid DnsConfig included a rogue nameserver. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Counts of specific error codes returned by DnsTask if a subsequent ProcTask + succeeded, at the end of a streak of failures after which the DnsClient was + disabled. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + TRUE counts the events when a valid DnsConfig is received and used to enable + DnsClient, while FALSE counts the events when DnsClient is disabled after a + series of successful fallbacks from DnsTask to ProcTask. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time spent by ProcTask in failing fallback resolutions. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time spent by ProcTask in successful fallback resolutions. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Whether there was a valid DNS configuration at the start of a job which + eventually completed successfully. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + The size of the HOSTS file observed before each attempt to parse it. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). Includes only Jobs which had + priority HIGHEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). Includes only Jobs which had + priority IDLE when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). Includes only Jobs which had + priority LOW when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). Includes only Jobs which had + priority LOWEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (using DnsClient). Includes only Jobs which had + priority MEDIUM when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). Includes only Jobs which had priority HIGHEST + when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). Includes only Jobs which had priority IDLE when + started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). Includes only Jobs which had priority LOW when + started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). Includes only Jobs which had priority LOWEST when + started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (using DnsClient). Includes only Jobs which had priority MEDIUM when + started. + + + + + + Removed as of 4/2016. + + mgersh@chromium.org + + Type of nameservers in the DNS config, recorded each time the config is read + by the DNSConfigService. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Counts of results of parsing addresses out of DNS responses in successful + DnsTransactions. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The source of the async DNS preference's default. Logged at startup, when + the IO thread is created. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The source of the async DNS preference's value. Logged at startup, when the + IO thread is created. + + + + + + Removed as of 12/2018. + + robpercival@chromium.org + + The DNS response rcode + (https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6). + Logged when a DnsTransaction finishes an attempt at a DNS record lookup. It + may make multiple attempts - the rcode of each attempt will be logged. No + logging will occur for attempts that do not obtain a response from a DNS + server. + + Only DNS record lookups performed by the internal DNS resolver + ("AsyncDNS") will have their rcode logged. Lookups performed by + the system resolver will not have their rcode logged. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskError. + + mgersh@chromium.org + + Counts of specific error codes returned by DnsTask if a subsequent ProcTask + succeeded. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskFail. + + mgersh@chromium.org + + Duration of time taken by DnsTask in resolutions that failed. Excludes time + spent in the subsequent fallback. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + Counts of the overall results of using asynchronous DNS in HostResolverImpl. + This only includes jobs started with valid DNS configuration and excludes + synchronous resolutions (as IP literals, from cache, and from HOSTS). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. + + mgersh@chromium.org + + Duration of time taken by DnsTask in resolutions that succeeded. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. + + mgersh@chromium.org + + Same as AsyncDNS.ResolveSuccess, but limited to pure IPv4 lookups. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. + + mgersh@chromium.org + + Same as AsyncDNS.ResolveSuccess, but limited to pure IPv6 lookups. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess. + + mgersh@chromium.org + + Same as AsyncDNS.ResolveSuccess, but limited to IPv4/IPv6 lookups. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Index in DnsConfig of the failing server, recorded at the time of failure. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of server failures after network change before first success in the + DnsSession. Recorded at the time of first success. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of server failures after success until the end of the session. Server + has reported success at some point during the session. Recorded at the end + of the DnsSession. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of server failures before success. This is NOT the first success in + the DnsSession. Recorded at the time of success. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Count of server failures without success until the end of the session. + Server has never reported success during the DnsSession. Recorded at the end + of the DnsSession. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The current server is "good" and does not have to be skipped. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in failing calls to AddressSorter in dual-stack + resolutions using DnsTask. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in successful calls to AddressSorter in dual-stack + resolutions using DnsTask. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + The number of names from the search name list consumed during a successful + transaction (QTYPE A only). + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + The number of names left on the search name list at the end of a successful + transaction (QTYPE A only). + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + The number of names on the search name list at the start of a transaction + (QTYPE A only). + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by DnsTCPAttempt in failed attempts. Excludes + timeouts. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by DnsTCPAttempt in successful attempts. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Difference between RTT and timeout calculated using Histogram algorithm. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Difference between timeout calculated using Histogram algorithm and RTT. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Difference between RTT and timeout calculated using Jacobson algorithm. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Difference between timeout calculated using Jacobson algorithm and RTT. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time that would be spent waiting for lost request using + Histogram algorithm. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time that would be spent waiting for lost request using Jacobson + algorithm. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.TotalTime. + + mgersh@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Excludes speculative requests. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.TotalTime_speculative. + + mgersh@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Speculative requests only. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in failing DnsTransactions. This includes server + failures, timeouts and NXDOMAIN results. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in successful DnsTransactions. This includes all + NOERROR answers, even if they indicate the name has no addresses or they + cannot be parsed. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Same as AsyncDNS.TransactionSuccess but limited to A query type. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Same as AsyncDNS.TransactionSuccess but limited to AAAA query type. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + TTL of the resolved addresses, as in the response received from the server. + For results served from local cache, the TTL is from the original response. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by DnsUDPAttempt in failed attempts. Excludes + timeouts. + + + + + + Removed as of 12/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by DnsUDPAttempt in successful attempts. Includes + responses arriving after timeout, if multiple attempts are allowed. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the frequency of user interactions with the Autocheckout bubble, + which prompts users to invoke Autocheckout on supported websites. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the frequency of final states reached in Autocheckout buy flow. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + The state of the Autocheckout dialog when it was dismissed. + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user submitted the Autocheckout + dialog and when the Autocheckout flow, or filling process, concluded. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user submitted the Autocheckout + dialog and when the Autocheckout flow concluded, in cases where the flow + failed. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user submitted the Autocheckout + dialog and when the Autocheckout flow concluded, in cases where the flow + succeeded. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + The initial state of a user that's interacting with a freshly shown + Autocheckout dialog. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + User interactions with the Autofill popup shown while filling an + Autocheckout dialog. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the frequency of security warnings and errors in the Autocheckout + dialog. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the duration for which an Autocheckout dialog was shown. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the duration for which an Autocheckout dialog was shown, in cases + where the user ended up canceling out of the dialog. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the duration for which an Autocheckout dialog was shown, in cases + where the user ended up accepting the dialog. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures how users are interacting with the Autocheckout dialog UI. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the duration of time it takes for the Autocheckout UI to be + actionable by the user after it is shown. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the frequency of errors in communicating with the Google Online + Wallet server. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the frequency of required user actions returned by the Google + Online Wallet server. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures time taken to download the Autocheckout whitelist file. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures time taken to download the Autocheckout whitelist file in case the + download was failed. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Measures time taken to download the Autocheckout whitelist file in case the + download was succeeded. + + + + + + Removed as of 2/2016. + + jinsukkim@chromium.org + + Whether the text encoding auto detection logic was attempted for a web page. + The logic is triggered when the parser fails to find the encoding method + from other signals such as http header, meta tag, BOM, etc. + + If the logic successfully detects a new encoding method which is different + from the default one, the result is reported through + AutodetectEncoding.Detected with the encoding method (see below). Otherwise + - i.e. detection logic somehow fails to work for the page or the detected + one is same as the default - no result is reported. + + + + + + Removed as of 2/2016. + + jinsukkim@chromium.org + + The number of web pages whose encoding method is found by the auto detection + logic. Grouped by the encoding methods defined in EncodingMethod. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + Whether an attempt to access the Mac AddressBook was skipped because doing + so would incorrectly cause the appearance of the permissions dialog. This + happens when Chrome auto-update changes the binary on disk before the first + AddressBook access attempt. + + + + + + Removed as of 8/2015. + + isherman@chromium.org + + Whether the Mac AddressBook was available on an attempt to read data from + it. + + + + + + Removed as of 8/2015. + + isherman@chromium.org + + Whether the Mac AddressBook was available on the *first* attempt to read + data from it. This is only recorded once per Chrome profile. + + + + + + Removed as of 6/2015, replaced by Autofill.ProfileActionOnFormSubmitted. + + sebsg@chromium.org + + Whether a new Autofill profile was created automatically. In the + "false" case, an existing profile was used (and possibly updated). + + + + + + Removed after M78. + + jsaul@google.com + siyua@chromium.org + payments-autofill-team@google.com + + Tracks whether UKM logging is enabled for the page in the Autofill. + + + + + + Removed as of 2/2016, replaced by Autofill.CardUploadDecisionMetric. + + jdonnelly@chromium.org + + Whether upload was offered upon detecting a form submission with credit card + data and a reason if it wasn't. + + + + + + Removed as of 5/2017, replaced by Autofill.CardUploadDecisionMetric. + + jdonnelly@chromium.org + + Whether upload was offered upon detecting a form submission with credit card + data and a detailed reason if it wasn't. + + + + + + Removed as of 3/2011, replaced by Autofill.CreditCardInfoBar. + + Please list the metric's owners. Add more owner tags as needed. + The Autofill credit card info bar was accepted. + + + + + Removed as of 3/2011, replaced by Autofill.CreditCardInfoBar. + + Please list the metric's owners. Add more owner tags as needed. + The Autofill credit card info bar was denied. + + + + + Was replaced by the AutofillDoNotUploadSaveUnsupportedCards feature in M75. + Removed 2019/07. + + jsaul@google.com + + When a credit card is not allowed to be offered upload save due to its + network, logs what the card network was. + + + + + + Removed as of 06/2019. + + jsaul@google.com + sebsg@chromium.org + + Logs the number of days between most recent use without modification and the + penultimate use of the profile when submitting a credit card form. + + + + + + Removed 06/2020 after sufficient data was collected, to cleanup the code + base. + + schwering@google.com + chrome-autofill@google.com + + Records how forms change dynamically: whether the form signature changed, a + field's signature changed, or a field was newly created. The reference + period starts when Autofill parses the form for the first time, and ends + when a navigation is committed or the frame is destructed. + +
+ Every form is observed for dynamic changes from the time it was first parsed + by Autofill until either a navigation has been committed or the frame is + destructed or the form's observation had to be flushed prematurely (the form + observations are managed in an LRU cache of maximum size 32, with least + recently parsed forms being discarded first). At the end of the lifetime, a + three-bit number is sent: the lowest bit is 1 iff a field was changed during + the form's lifetime (its signature changed); the second bit is 1 iff a field + was added (its renderer ID is new to the form); the highest bit is 1 iff the + form was changed (its signature changed). +
+ + + + + Removed as of 02/2020. + + jsaul@google.com + siyua@chromium.org + + Autofill form events for credit card forms. These are recorded when the user + interacts with a form requesting a credit card, a dropdown of suggestions is + shown and at least one of the suggestions has a bank name. Form events are + logged at most once per page load. + +
+ These metrics are used to measure the impact of the bank name experiment. + They are used to calculate the CTR of the autofill UI with bank names + available. Not all credit cards will have bank names even if we launch the + experiment. With these metrics we can run the experiment on 2 groups. For + one group, we will show bank names if available. For the other, we won't + shown. +
+ + + + + Removed as of 06/2019. + + jsaul@google.com + sebsg@chromium.org + + Whether user modified an address profile shortly before submitting a credit + card form. + + + + + + Removed after M77. + + mathp@chromium.org + + Tracks whether Autofill was able to create the ICU collator successfully. + + + + + + Obsolete after M77. + + mahmadi@chromium.org + + [iOS] Measures the frequency of button presses on the iOS Autofill keyboard + accessory view when VoiceOver is off. + + + + + + Obsolete after M85. + + mahmadi@chromium.org + + [iOS] Measures the frequency of button presses on the iOS Autofill keyboard + accessory view when VoiceOver is on. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + When Chrome tries to access the user's Address Book, OSX presents a blocking + dialog which disrupts the user experience. A new Chrome feature has been + introduced wherein Chrome only shows this blocking dialog if the user + explicitly asked Chrome to access the user's Address Book. If a form's field + looks like it might support Autofill suggestions from the user's Address + Book and there are no other suggestions, Chrome shows an Autofill entry that + prompts the user to give Chrome access to the user's Address Book. This + histogram tracks the frequency that this Autofill entry is presented, and + the frequency that this Autofill entry is selected. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + This metric is emitted each time the user accepts an Autofill suggestion. It + records whether the result is from the Address Book. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + The amount of time spent accessing the OSX Address Book the first time after + Chrome was launched. If this time is larger than ~100ms, this it is likely + that the user was shown a blocking, modal dialog. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + After a Chrome is given access to the Mac Address Book, whether the Address + Book contained a Me card. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + When Chrome is given access to the Me Card of the Address Book, whether the + card has an address that contained a street number and either a city or zip + code. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + When Chrome is given access to the Me Card of the Address Book, whether the + card has an email. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + When Chrome is given access to the Me Card of the Address Book, whether the + card has a name. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + When Chrome is given access to the Me Card of the Address Book, whether the + card has a phone number. + + + + + + Removed as of 8/2015. + + erikchen@chromium.org + + The number of times that the access Address Book prompt has been shown when + the user selects the prompt. + + + + + + Removed as of 12/2019. The comparison found that Chrome and Payments + correctly matched 99.9% of the time. + + jsaul@google.com + payments-autofill-team@google.com + + This metric is recorded when two credit cards are compared using + CreditCard::HasSameNumberAs and one of the cards in the comparison is + masked. The metric measures whether there is a match between a masked card's + network and the network of the card with which the masked card is being + compared. + + + + + + Removed 10/2015. + + dvadym@chromium.org + gcasto@chromium.org + + Tracks the increased load on the Autofill server if the restriction on + querying for password forms with fewer than 3 fields were omitted. + + + + + + Removed as of 1/2016, autofill payload compression was removed. + + mathp@chromium.org + + Compression ratio of the query and upload payload that are sent to the + Autofill server. The payload is compressed using gzip. + + + + + + Removed as of 9/2018, replaced by + Autofill.PaymentsCustomerDataBillingIdStatus. + + mathp@chromium.org + + When PaymentsCustomerData is used to send a request to Google Payments, we + log the validity state of the billing customer ID. + + + + + + Removed as of August 2019. + + mathp@chromium.org + + When PaymentsCustomerData is used to send a request to Google Payments, we + log the validity state of the billing customer ID. + + + + + + Removed as of 3/2011, replaced by Autofill.StoredProfileCount. + + Please list the metric's owners. Add more owner tags as needed. + The number of Autofill address profiles a user has. + + + + + Removed as of 3/2011, replaced by Autofill.Quality. + + Please list the metric's owners. Add more owner tags as needed. + The quality of the AutoFill implementation. + + + + + Removed as of 2/2014 (M35), replaced by Autofill.UserHappiness. + + isherman@chromium.org + The quality of the Autofill implementation. + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.Aggregate.Heuristic. + + isherman@chromium.org + The quality of Autofill's heuristic field type detection. + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.ByFieldType.Heuristic. + + isherman@chromium.org + + The quality of Autofill's heuristic field type detection, broken down by the + specific field type. Fields with multiple possible types (based on the + stored Autofill data) are logged as having ambiguous type. + + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.Aggregate.Overall. + + isherman@chromium.org + The overall quality of the Autofill field type predictions. + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.ByFieldType.Overall. + + isherman@chromium.org + + The overall quality of the Autofill field type predictions, broken down by + the specific field type. Fields with multiple possible types (based on the + stored Autofill data) are logged as having ambiguous type. + + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.Aggregate.Server. + + isherman@chromium.org + The quality of the Autofill server's field type detection. + + + + + Removed as of 6/2017, replaced by + Autofill.FieldPredictionQuality.ByFieldType.Server. + + isherman@chromium.org + + The quality of the Autofill server's field type detection, broken down by + the specific field type. Fields with multiple possible types (based on the + stored Autofill data) are logged as having ambiguous type. + + + + + + Removed as of 8/2018, replaced by Autofill.Query.HttpResponseOrErrorCode. + + rogerm@chromium.org + The HTTP response code returned on a query. + + + + + Were added as part of Issue 851295; no longer necessary. Removed 2019/07. + + sebsg@chromium.org + The number of full server cards that were reset. + + + + + Removed as of 10/2018 (M72). + + sebsg@chromium.org + The number of full server cards that would have been reset. + + + + + Were added as part of Issue 851295; no longer necessary. Removed 2019/07. + + sebsg@chromium.org + + Records whether a sync service in a not active state is passed to Autofill + OnSyncServiceInitialized. + + + + + + Were added as part of Issue 851295; no longer necessary. Removed 2019/07. + + sebsg@chromium.org + + Records whether a null sync service is passed to Autofill + OnSyncServiceInitialized. + + + + + + Removed as of 04/2019 (M76). No longer necessary since we don't mask data + for USS Autofill Wallet anymore. + + sebsg@chromium.org + + Records the sync service state when OnStateChanged is called. + + + + + + Removed as of 05/2019. Was a temporary metric to gauge the impact of + http://crbug.com/892299. + + jsaul@google.com + sebsg@chromium.org + mahmadi@chromium.org + + + + Records if the PersonalDataManager was notified to attempt saving of a card. + + + + + + Deprecated after M85. + + battre@chromium.org + + + + Records if a card was saved from a form that had split name fields. + + + + + + Deprecated after M85. + + battre@chromium.org + + + + Records if a card was offered to be saved from a form that had split name + fields. + + + + + + Removed as of 6/2011, replaced by Autofill.ServerExperimentId.Query. + + isherman@chromium.org + + The experiment ID received in response to an Autofill server query. + + + + + + Removed as of 2/2014 (M35). + + isherman@chromium.org + + The experiment ID received in response to an Autofill server query. + + + + + + Removed as of 2/2014 (M35). + + isherman@chromium.org + + The experiment ID received at the time of an Autofill upload. + + + + + + Removed as of 3/2011, replaced by Autofill.ServerQueryResponse. + + Please list the metric's owners. Add more owner tags as needed. + The usefulness of AutoFill server information. + + + + + Removed in favor of Autofill.StoredCreditCardCount.Local. + + mathp@chromium.org + + The number of local credit cards a user has stored, measured at Chrome + profile launch time. + + + + + + Removed in favor of Autofill.StoredCreditCardCount.Server. + + mathp@chromium.org + + The number of server credit cards a user has stored, measured at Chrome + profile launch time. + + + + + + Removed as of 01/2019, as it never occurs. + + rogerm@chromium.org + + The delay of a network request for which the download manager seems to have + lost the request type due to exponential backoff. This should never be + logged. + + + + + + Removed as of 01/2019, as it never occurs. + + rogerm@chromium.org + + The number of bytes that were sent in a request for which the download + manager seems to have lost the request type. This should never be logged. + + + + + + Removed as of 8/2018, replaced by Autofill.Unknown.HttpResponseOrErrorCode. + + rogerm@chromium.org + + The HTTP response code returned on a request for which the download manager + seems to have lost the request type. This should never be logged. + + + + + + Removed as of 01/2019, as it never occurs. + + rogerm@chromium.org + + The http response code or net error code returned on a request for which the + download manager seems to have lost the request type. This should never be + logged. + + + + + + Removed as of 01/2019, as it never occurs. + + rogerm@chromium.org + + The duration of a network request for which the download manager seems to + have lost the request type. This should never be logged. + + + + + + Removed as of 8/2018, replaced by Autofill.Upload.HttpResponseOrErrorCode. + + rogerm@chromium.org + The HTTP response code returned on an upload. + + + + + Removed as of 12/2018, replaced by Autofill.WalletAddresses2. + + + + sebsg@chromium.org + jkrcal@chromium.org + + The number of Wallet addresses that were added to Chrome or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. Recorded only if both the user had previously non-empty + data set locally and the new data set is also non-empty (to rule out initial + sync and wiping out data). This metric has a flaw that the Directory + implementation (unlike the USS implementation) records the metric also on + every startup and the resulting histograms are hard to compare. + + + + + + Removed as of 05/2019. + + + + sebsg@chromium.org + jkrcal@chromium.org + + The number of Wallet addresses that were added to Chrome or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. Recorded only if both the user had previously non-empty + data set locally and the new data set is also non-empty (to rule out initial + sync and wiping out data). + + + + + + Removed as of 11/2018, replaced by Autofill.WalletAddresses.Added. + + sebsg@chromium.org + treib@chromium.org + + The number of Wallet addresses that were added to Chrome via Sync. Recorded + when receiving an AUTOFILL_WALLET_DATA update from the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 11/2018, replaced by Autofill.WalletAddresses.AddedOrRemoved. + + sebsg@chromium.org + treib@chromium.org + + The total number of Wallet addresses that were added to or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 11/2018, replaced by Autofill.WalletAddresses.Removed. + + sebsg@chromium.org + treib@chromium.org + + The number of Wallet addresses that were removed from Chrome via Sync. + Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 12/2018, replaced by Autofill.WalletCards2. + + + + sebsg@chromium.org + jkrcal@chromium.org + + The number of Wallet credit cards that were added to Chrome or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. Recorded only if both the user had previously non-empty + data set locally and the new data set is also non-empty (to rule out initial + sync and wiping out data). This metric has a flaw that the Directory + implementation (unlike the USS implementation) records the metric also on + every startup and the resulting histograms are hard to compare. + + + + + + Removed as of 05/2019. + + + + sebsg@chromium.org + jkrcal@chromium.org + + The number of Wallet credit cards that were added to Chrome or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. Recorded only if both the user had previously non-empty + data set locally and the new data set is also non-empty (to rule out initial + sync and wiping out data). + + + + + + Removed as of 11/2018, replaced by Autofill.WalletCards.Added. + + sebsg@chromium.org + treib@chromium.org + + The number of Wallet credit cards that were added to Chrome via Sync. + Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 11/2018, replaced by Autofill.WalletCards.AddedOrRemoved. + + sebsg@chromium.org + treib@chromium.org + + The total number of Wallet credit cards that were added to or removed from + Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from + the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 11/2018, replaced by Autofill.WalletCards.Removed. + + sebsg@chromium.org + treib@chromium.org + + The number of Wallet credit cards that were removed from Chrome via Sync. + Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server. + +
+ Can probably be removed around Q1 2019, after project Dice has rolled out. +
+ + + + + Removed as of 04/2019 because most measurements were in the last bucket, + replaced by Autofill.WalletUseDateInMinutes.Address. + + jkrcal@chromium.org + treib@chromium.org + + The time since last use date of a wallet address, as known by sync. Recorded + for each wallet address on startup. + + + + + + Removed as of 04/2019 because most measurements were in the last bucket, + replaced by Autofill.WalletUseDateInMinutes.Card. + + jkrcal@chromium.org + treib@chromium.org + + The time since last use date of a wallet card, as known by sync. Recorded + for each wallet card on startup. + + + + + + Removed as of 2019-08. + + jkrcal@chromium.org + treib@chromium.org + + The time since last use date of a wallet address, as known by sync. Recorded + for each wallet address on startup. + + + + + + Removed as of 2019-08. + + jkrcal@chromium.org + treib@chromium.org + + The time since last use date of a wallet card, as known by sync. Recorded + for each wallet card on startup. + + + + + + Removed 12/2019. No longer tracked. + + gayane@chromium.org + + Time that it takes to calculate all the theme properties for autogenerated + themes in ms. + + + + + + Removed as of 11/2018. It has been replaced by DailyUserAdjustment. + + jiameng@chromium.org + Type of user manual screen brightness adjustment. + + + + + Replaced by Availability.Prober.TimeUntilFailure2. + + robertogden@chromium.org + tbansal@chromium.org + + Records the amount of time spent working on a single probe attempt to get to + a failed state. Recorded every time a probe fails. + + + + + + Replaced by Availability.Prober.TimeUntilSuccess2. + + robertogden@chromium.org + tbansal@chromium.org + + Records the amount of time spent working on a single probe attempt to get to + a successful state. Recorded every time a probe succeeds. + + + + + + Deprecated 09/2020 in favor of ActionAfterPagehide2 which excludes actions + taken when the unload event is in progress. + + rakina@chromium.org + altimin@chromium.org + bfcache-dev@chromium.org + + Records occurences of certain actions triggered by script running on a page + after the pagehide event gets dispatched in the page, which might be + possible if we dispatch the pagehide event without unloading/freezing the + page (only happens when we're doing a same-site navigation and we did a + proactive BrowsingInstance swap but we're reusing the old page's process). + Note: we will only track actions that might affect the user after we've + navigated away from the old page, such as modifications to storage, + navigations, or sending/receiving postMessage. + + + + + + Removed 10/2018 since DB tasks record this more accurately. + + peter@chromium.org + rayankans@chromium.org + + Records the error after the Background Fetch Data Manager creates a + registration. + + + + + + Removed 10/2018 since DB tasks record this more accurately. + + peter@chromium.org + rayankans@chromium.org + + Records the error after the Background Fetch Data Manager deletes a + registration. + + + + + + Removed 10/2018 since DB tasks record this more accurately. + + peter@chromium.org + rayankans@chromium.org + + Records the error after the Background Fetch Data Manager marks a + registration for deletion. This is called when the Scheduler Controller is + finished. + + + + + + As of 10/2015 this has been replaced by + BackgroundSync.Event.OneShotResultPattern. + + iclelland@chromium.org + Records whether a one-shot sync event succeeded or failed. + + + + + As of 10/2015 this has been replaced by + BackgroundSync.Event.PeriodicResultPattern. + + iclelland@chromium.org + Records whether a periodic sync event succeeded or failed. + + + + + Removed as of 09/2019. + + nator@chromium.org + rayankans@chromium.org + + Records the result of attempting to cancel a future browser launch using the + GCM Network Manager on Android. + + + + + + Removed as of 09/2019. + + nator@chromium.org + rayankans@chromium.org + + Records the result of attempting to schedule a future browser launch using + the GCM Network Manager on Android. + + + + + + Removed as of 03/2019. + + rayankans@chromium.org + + Whether the Background Sync dispatch conditions changed between scheduling + the operation and dispatching the event. This is collected right before the + event is dispatched. + + + + + + Stopped recording as of 2/2016. + + iclelland@chromium.org + + Records the result of attempting to unregister a one-shot sync. + + + + + + Removed 6/3/2020. No longer needed. + + phillis@chromium.org + cmumford@chromium.org + The result from updating the app badge on Windows. + + + + + The blacklist is deprecated in favor of third-party DLL blocking. + + csharp@chromium.org + + Records the name hashes of all the dlls that are blocked from the browser + process. + + + + + + Removed at 2015 July. + + csharp@chromium.org + + Counts the number of times a renderer process is started with the browser + blacklist patch. This should never be hit. + + + + + + Replaced by ChromeElf.Beacon.RetryAttemptsBeforeSuccess after the old + blacklist was deprecated. + + csharp@chromium.org + proberge@google.com + + Records the number of attempts needed before the blacklist is properly set + up. This is logged immediately after a successful setup. + + + + + + Replaced by ChromeElf.Beacon.SetupStatus after the old blacklist was + deprecated. + + csharp@chromium.org + + Records the successes and failures when running the browser blacklist setup + code. Used to determine if the blacklist is working as intended during + startup (since the blacklist runs before crash reporting is set up). This + only occurs on Windows. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent to create a v8::Context instance during a page loading in the + main-frame window. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent to create a v8::Context instance during a page loading in a + non-main-frame window, e.g. iframe. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent initializing LocalWindowProxy during a page loading in main + windows. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent initializing RemoteWindowProxy during a page loading in main + frame of OOPIF. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 03/2017. This metric was split into two metrics depending if + it figures time for local window proxies or remote ones. + + peria@chromium.org + + Time spent initializing WindowProxy during a page loading in main windows. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent initializing LocalWindowProxy during a page loading in non-main + windows, e.g. iframe. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 04/2019 with the removal of field trial experiment settings. + + peria@chromium.org + + Time spent initializing RemoteWindowProxy during a page loading in OOPIF. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 03/2017. This metric was split into two metrics depending if + it figures time for local window proxies or remote ones. + + peria@chromium.org + + Time spent initializing WindowProxy during a page loading in non-main + windows, e.g. iframe. + + + + + + Removed as of 10/2016. This metric was split into two metrics depending if + it figures time for main windows. + + peria@chromium.org + Time spent initializing WindowProxy during a page loading. + + + + + Removed as of 08/2018 (M70) with the removal of the Budget API. + + peter@chromium.org + + Whenever the Budget API framework receives a query for the current budget, + this records the total budget available to the origin, which is an internal + Chrome value for the amount of background processing an origin can do + without visibly alerting the user. Scale for the budget is 0 to 100. Care + should be taken when drawing conclusions from this metric, as budget is + based on both engagement and usage, so could vary significantly based on + user behaviour and origin. + + + + + + Removed as of 08/2018 (M70) with the removal of the Budget API. + + peter@chromium.org + + Whenever the Budget API framework receives a request to reserve budget for a + future background operation, this records whether the reserve request + succeeded or not. + + + + + + Removed as the deferral path is always used now - 11/2019. + + aaronhk@chromium.org + fserb@chromium.org + + Records if a 2D Layer Bridge is using deferred rendering when it is + destroyed. Emitted in Canvas2DLayerBridge::~Canvas2DLayerBridge. + + + + + + Replaced with Blink.Canvas.DrawImage.Duration in 10/2018. + + fserb@chromium.org + + Time spent on 2D canvas drawImage API call. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced with Blink.Canvas.GetImageDataScaledDuration in 10/2018. + + fserb@chromium.org + + Time spent on 2D canvas getImageData API call. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Canvas doesn't disable deferral anymore since July 2019. + + fserb@chromium.org + aaronhk@chromium.org + + The reasons why a GPU accelerated canvas stopped deferring its rendering + operations. + + + + + + Removed in 10/2018. Offscreen Canvas no longer needs commits. + + fserb@chromium.org + xidachen@chromium.org + + Wall clock durations of OffscreenCanvas.commit() calls. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced with Blink.Canvas.PutImageDataScaledDuration in 10/2018. + + fserb@chromium.org + + Time spent on 2D canvas putImageData API call. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced with Blink.Canvas.ToBlob.CompleteEncodingDelay in 2017/12. + + fserb@chromium.org + aaronhk@chromium.org + + This metric measures the total time spent on encoding all the rows of an + image (jpeg or png), excluding the waiting time of next idle periods. This + is part of a canvas.toBlob API call. Encoding occurs during one or more idle + periods on the main thread. + + + + + + Replaced with Blink.Canvas.ToBlob.ScaledDuration in 10/2018. + + fserb@chromium.org + aaronhk@chromium.org + + Time spent on 2D canvas toBlob API call. + + In addition, metric values from OffscreenCanvas.convertToBlob API call are + also gathered into this histogram, because the logic flow is exactly the + same as canvas.toBlob. It's worth to note that the values can come from idle + tasks on either main or worker thread. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced with Blink.Canvas.ToDataURLScaledDuration in 10/2018. + + fserb@chromium.org + + Time spent on 2D canvas toDataURL API call. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed on 2018-05-04. + + khushalsagar@chromium.org + + The number of images which could have been checkered (async decoded) for a + performance gain, split by the DOM element type on which they were used. + This is recorded each time an image for an element created by the page is + loaded, either from the network or the local cache. The browser heuristics + define an image to be checkerable if it is expected to have a long decode + duration. Since these images may be on the rendering critical path, decoding + them asychronously from painting other content can provide better + performance be reducing overall content checkerboarding. + + + + + + No useful signal. Deprecated 7/2019. + + brianosman@chromium.org + mcasas@google.com + ccameron@chromium.org + Gamut properties of image color space. + + + + + Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + + ccameron@chromium.org + + Whether or not the output color space ICC profile was able to produce raw + transfer function tables. + + + + + + No useful signal. Deprecated 2020-03-03. + + brianosman@chromium.org + mcasas@google.com + ccameron@chromium.org + + The result of analyzing the destiation color space's ICC profile. + + + + + + Linear fit found to be always inaccurate on 2017-02-28. + + ccameron@chromium.org + + The L-infinity error (in 8-bit values) of the numerical approximation of + table-based ICC profile transfer functions, when falling back to a linear + approximation. + + + + + + Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + + ccameron@chromium.org + + Whether or not to-XYZD50 matrix was extracted from the output color space + ICC profile. + + + + + + Nonlinear fit code moved to skcms on 2018-04-25. + + ccameron@chromium.org + + Whether or not the nonlinear least squares fit of the table-based ICC + profile transfer function for a single channel converged. + + + + + + Nonlinear fit code moved to skcms on 2018-04-25. + + ccameron@chromium.org + + The L-infinity error (in 8-bit values) of the numerical approximation of + table-based ICC profile transfer functions for a single channel, when the + nonlinear approximation converged. + + + + + + Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28. + + ccameron@chromium.org + + Whether or not the output color space ICC profile has a numerical transfer + function. + + + + + + TMax found to almost always be 1 on 2017-02-28. + + ccameron@chromium.org + + One minus the maximum value of table-based ICC profile transfer functions as + an 8-bit fixed-point value. This histogram is temporary, to see if we can + bake in the assumption that it will almost always be 255. + + + + + + TMin found to almost always be 0 on 2017-02-28. + + ccameron@chromium.org + + The minimum value of table-based ICC profile transfer functions as an 8-bit + fixed-point value. This histogram is temporary, to see if we can bake in the + assumption that it will almost always be 0. + + + + + + No useful signal. Deprecated 7/2019. + + brianosman@chromium.org + mcasas@google.com + ccameron@chromium.org + Gamma properties of image color space. + + + + + Obsolete as of http://crrev.com/794384 and M86. + + schenney@chromium.org + paint-dev@chromium.org + + Time spent updating compositing in the Blink document lifecycle. This is the + legacy compositing approach. BlinkGenPropertyTrees launches part of the new + compositing approach and will use both this and + Blink.CompositingCommit.UpdateTime. + + Note: As of M70, this histogram has stopped recording metrics on machines + with low-resolution clocks. + + TODO(crbug.com/1100711): This is being replaced soon by CompositingInputs + + CompositingAssignments (== Compositing). + + + + + + Removed as of 01/20/2020. + + kinuko@chromium.org + dcheng@chromium.org + + Microseconds per sync IPC call to set cookies. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 01/20/2020. + + kinuko@chromium.org + dcheng@chromium.org + + Microseconds per sync IPC call to fetch cookies. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed as of 11/29/2016. + + ryansturm@chromium.org + bengr@google.com + + The original canvas dimensions were sufficient to determine image size. This + is logged once per image header decode, which happens typically twice per + image on the page. + + + + + + Removed as of 11/29/2016. + + ryansturm@chromium.org + bengr@google.com + + How many bytes of the file were read before an image width and height were + determined. This is logged once per image header decode, which happens + typically twice per image on the page. + + + + + + Removed as of 08/23/2018. Replaced by Blink.DecodedImage.JpegDensity.* + + deymo@google.com + compression-dev@google.com + + The compressed image density measured in 0.01 bits per pixel. This is logged + once per image load after the whole image is loaded and only for JPEGs with + at least 100 pixels on each dimension. + + + + + + Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + + deymo@google.com + compression-dev@google.com + + The compressed image density measured in 0.01 bits per pixel. This is logged + once per image load after the whole image is loaded and only for JPEGs with + at least 1000 pixels on the smallest dimension (width or height). + + + + + + Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + + deymo@google.com + compression-dev@google.com + + The compressed image density measured in 0.01 bits per pixel. This is logged + once per image load after the whole image is loaded and only for JPEGs with + at least 100 pixels on the smallest dimension (width or height) but less + than 400 pixels on the smallest dimension. + + + + + + Removed in M79. Replaced by Blink.DecodedImage.JpegDensity.KiBWeighted. + + deymo@google.com + compression-dev@google.com + + The compressed image density measured in 0.01 bits per pixel. This is logged + once per image load after the whole image is loaded and only for JPEGs with + at least 400 pixels on the smallest dimension (width or height) but less + than 1000 pixels on the smallest dimension. + + + + + + Removed as of 11/29/2016. + + ryansturm@chromium.org + bengr@google.com + + How much the canvas width needed to be expanded as a result of the first + frame's width and x-offset being larger than the initial canvas width. This + is logged once per image header decode, which happens typically twice per + image on the page. + + + + + + Removed as of 11/29/2016. + + ryansturm@chromium.org + bengr@google.com + + How much the canvas height needed to be expanded as a result of the first + frame's height and y-offset being larger than the initial canvas height. + This is logged once per image header decode, which happens typically twice + per image on the page. + + + + + + Removed 01/2018. + + bokan@chromium.org + + Time it takes to execute all the `resize` event listeners on a page when a + resize event is fired. Tracked only for the main frame. + + + + + + UserActivationV2 made UserGestureTokens obselete, so the merge stats is now + irrelevant. + + jyasskin@chromium.org + domenic@google.com + + How many times two user gesture tokens were merged by UserGestureIndicator, + and whether each token had an active gesture. One of the new token's + gestures, if any, is moved to the old token. + + + + + + Replaced with separate ImplCompositorCommit and WaitForCommit metrics and + removed in M84. + + schenney@chromium.org + paint-dev@chromium.org + + + + The percentage of time between a BeginMainFrame and paint results commit in + Blink that is used for committing the layer tree to the impl thread. + + + + + + Replaced with separate Style and Layout metrics and removed in M81. + + schenney@chromium.org + paint-dev@chromium.org + + + + The percentage of time between a BeginMainFrame and paint results commit in + Blink that is used for computing Style and Layout. + + + + + + Removed 08/2017 as it is integrated into media controller. + + qinmin@chromium.org + + Records how the download button on the MediaDocument is used. + + + + + + Removed 11/2016 in Issue 666370 with the deprecation of Autoplay experiment. + + oysteine@chromium.org + + Records user observation and interaction with Media HTML elements that + feature autoplay, either script-controlled or through the attribute. + + + + + + Not very useful for identifying performance issues. + + paint-dev@chromium.org + + Percentage of display items that are put into the index because of + out-of-order display item matching. Higher value means lower performance + beause of the cost of out-of-order matching and indexing. Recorded when we + finish updating paint in the Blink document lifecycle. + + + + + + Not very useful for identifying performance issues. + + paint-dev@chromium.org + + Total number of display items (including cached and repainted) in the + painted result. Recorded when we finish updating paint in the Blink document + lifecycle. + + + + + + Not very useful for identifying performance issues. + + paint-dev@chromium.org + + Total number of paint chunks in the painted result. Recorded when we finish + updating paint in the Blink document lifecycle. + + + + + + Not very useful for identifying performance issues. + + paint-dev@chromium.org + + Total number of subsequences (including cached and repainted) in the painted + result. Recorded when we finish updating paint in the Blink document + lifecycle. + + + + + + SlimmingPaintInvalidation is enabled by default, so this histogram is no + longer being logged. Was removed in 02-2018. + + paint-dev@chromium.org + + Time spent updating paint invalidation in the Blink document lifecycle. Not + available when SlimmingPaintInvalidation or SlimmingPaintV2 is enabled. + + + + + + Replaced with separate ImplCompositorCommit and WaitForCommit metrics and + removed in M84. + + + + + + + + schenney@chromium.org + paint-dev@chromium.org + + Time spent commiting the layer tree to the impl thread in a main frame + update. + + Note: This histogram does not record metrics on machines with low-resolution + clocks. + + + + + + Removed as of 02/2020. + + dtapuska@chromium.org + kenjibaheux@google.com + Count of resources attempted Stale Revalidation. + + + + + Removed as of 8/2018. + + + + toyoshim@chromium.org + ksakamoto@chromium.org + Count received data size in bytes for each resource. + + + + + Removed as of 02/2020. + + toyoshim@chromium.org + altimin@chromium.org + + Total decoded size of resources associated with frames of a particular type. + Recorded when a fetch has been completed. + + Each bucket of the histogram cointains the total size of all requests + associated with frames with a particular frame status in kilobytes. + + + + + + Removed as of 6/2019. + + + + ksakamoto@chromium.org + toyoshim@chromium.org + + The largest number of outstanding resource requests issued by a frame until + the network 2-quiet (no more than 2 active network requests for 1 seconds). + + + + + + Removed as of 02/2020. + + toyoshim@chromium.org + ksakamoto@chromium.org + + Count resource request circumstance, e.g. from the main frame vs sub-frames, + or in throttled state vs in not-throttled state, on each resource load + completion. + + + + + + Removed as of 6/2019. + + toyoshim@chromium.org + ksakamoto@chromium.org + + Count how many times the scheduler has changed throttling status from the + frame creation until network activity quiets. + + + + + + Removed as of 6/2019. + + + + toyoshim@chromium.org + altimin@chromium.org + + Total received data size in bytes to load resources from the frame creation + until network activity quiets. + + + + + + Removed as of 6/2019. + + + + toyoshim@chromium.org + ksakamoto@chromium.org + + Total number of resource requests completed from the frame creation until + network activity quiets. + + + + + + Removed as of 6/2019. + + + + toyoshim@chromium.org + altimin@chromium.org + + Total traffic data in bytes transferred over networks to load resources from + the frame creation until network activity quiets. + + + + + + Removed as of 8/2018. + + + + toyoshim@chromium.org + ksakamoto@chromium.org + + Count traffic data size in bytes transferred over networks to load each + resource. + + + + + + Removed 01/2016 and replaced by Blink.RestoredCachedStyleSheet2 + + kouhei@chromium.org + + On each link stylesheet tag resolve, record whether a Blink MemoryCached + StyleSheetContents was reused. + + + + + + Removed 04/2017. + + kouhei@chromium.org + + On each link stylesheet tag resolve, record which cache Blink hit. + + + + + + Used to justify distribution of serialized data in the wild, but unlikely to + be useful to track long-term. + + platform-architecture-dev@chromium.org + + Number of DOM wrappers serialized as part of an object passed to + postMessage, IndexedDB, or another API that serializes script values. + + + + + + Used to justify distribution of serialized data in the wild, but unlikely to + be useful to track long-term. + + platform-architecture-dev@chromium.org + + Number of JavaScript objects (other than DOM wrappers) serialized as part of + an object passed to postMessage, IndexedDB, or another API that serializes + script values. + + + + + + Used to justify distribution of serialized data in the wild, but unlikely to + be useful to track long-term. + + platform-architecture-dev@chromium.org + + Number of primitive values (numbers, strings, etc.) serialized as part of an + object passed to postMessage, IndexedDB, or another API that serializes + script values. + + + + + + Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + + hiroshige@chromium.org + + Number of failed SharedBuffer::lock() calls for each resource type. + https://crbug.com/603791 + + + + + + Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + + hiroshige@chromium.org + + Number of successful SharedBuffer::lock() calls for each resource type. + https://crbug.com/603791 + + + + + + Removed 08/2016 since SharedBuffer::unlock() was successfully removed. + + hiroshige@chromium.org + + Number of SharedBuffer::unlock() calls for each resource type. + https://crbug.com/603791 + + + + + + Removed 9/2019 since the concept of timeouts have been removed. + https://crbug.com/1000376 + + goto@chromium.org + reillyg@chromium.org + ayui@chromium.org + + Records the timeout value specified when the API is called regardless of + whether or not the call actually timed out. The value of 0 indicates that no + value was specified. + + + + + + Removed 9/2019 since the concept of timeouts have been removed. + https://crbug.com/1000376 + + goto@chromium.org + reillyg@chromium.org + ayui@chromium.org + + Records the duration from when the API is called to when the user gets timed + out of the SMS verification flow because no SMS was received within the + specified timeout window. + + + + + + Replaced with separate Style and Layout metrics and removed in M81. + + + + + + + + schenney@chromium.org + layout-dev@chromium.org + + Time spent updating style and layout in the Blink document lifecycle. + + Note: As of M70, this histogram has stopped recording metrics on machines + with low-resolution clocks. + + + + + + Renamed to Blink.UseCounter.AnimatedCSSProperties in 03/2018, M69. The old + blink UseCounter is flawed in OOPIF, so moved to the browser side instead. + + chasej@chromium.org + feature-control@chromium.org + + Records usage of animated CSS properties used across all frames in a page, + either statically or dynamically, from the time the page is initialised to + when it is closed or navigated away from. Each property is counted at most + once per page view except kTotalPagesMeasuredCSSSampleId which represents a + page load (enum value of 1) and is counted exactly once per page view. + + + + + + Renamed to Blink.UseCounter.CSSProperties in 03/2018, M69. The old blink + UseCounter is flawed in OOPIF, so moved to the browser side instead. + + chasej@chromium.org + feature-control@chromium.org + + Records usage of CSS properties used across all frames in a page, either + statically or dynamically, from the time the page is initialised to when it + is closed or navigated away from. Each property is counted at most once per + page per view except kTotalPagesMeasuredCSSSampleId which represents a page + load (enum value of 1) and is counted exactly once per page view. + + + + + + Feature moved from feature policy to document policy in M82. Histogram and + recording code removed for feature policy. Histogram and recording code will + be added for document policy. + + iclelland@chromium.org + feature-control@chromium.org + + Logs downscaling ratio in percentage for images enforced by feature policy + oversized-images policy going into origin trials in M75. If an image's + downscaling ratio is 1, it will be represented as 10 percent, if an image's + downscaling ratio is 5, it will be represented as 50 percents. Recorded when + oversized-images policy is enforced and the image is about to be painted. + + + + + + Feature moved from feature policy to document policy in M82. Histogram and + recording code removed for feature policy. Histogram and recording code will + be added for document policy. + + iclelland@chromium.org + feature-control@chromium.org + + Counts ImageFileFormats (lossy, lossless, webp animation, others) of images + enforced by feature policy unoptimized-images policy going into origin + trials in M75. Recorded when images finish decoding the mime type. + + + + + + Feature moved from feature policy to document policy in M82. Histogram and + recording code removed for feature policy. Histogram and recording code will + be added for document policy. + + iclelland@chromium.org + feature-control@chromium.org + + Logs compression ratio in percentage with 1KB overhead for lossless type + images enforced by feature policy unoptimized-lossless-images policy going + into origin trials in M75. If an image's compression ratio is 0.1, it will + be represented as 1 percent, if an image's compression ratio is 5, it will + be represented as 50 percents. Recorded when unoptimized-lossless-images + policy is enforced and the image finishes decoding its mime type. + + + + + + Feature moved from feature policy to document policy in M82. Histogram and + recording code removed for feature policy. Histogram and recording code will + be added for document policy. + + iclelland@chromium.org + feature-control@chromium.org + + Logs compression ratio with 1KB overhead for lossy type images enforced by + feature policy unoptimized-lossy-images policy going into origin trials in + M75. If an image's compression ratio is 0.1, it will be represented as 1 + percent, if an image's compression ratio is 5, it will be represented as 50 + percents. Recorded when unoptimized-lossy-images policy is enforced and the + image finishes decoding its mime type. + + + + + + Feature moved from feature policy to document policy in M82. Histogram and + recording code removed for feature policy. Histogram and recording code will + be added for document policy. + + iclelland@chromium.org + feature-control@chromium.org + + Logs compression ratio with 10KB overhead for lossless type images enforced + by feature policy unoptimized-lossless-images-strict policy going into + origin trials in M75. If an image's compression ratio is 0.1, it will be + represented as 1 percent, if an image's compression ratio is 5, it will be + represented as 50 percents. Recorded when unoptimized-lossless-images-strict + policy is enforced and the image finishes decoding its mime type. + + + + + + Replaced by Blink.UseCounter.Features in M67. See crbug.com/849695. + + chasej@chromium.org + feature-control@chromium.org + + Count of how many page loads use various features. The PageVisits bucket is + incremented for each page load, and the other buckets incremented at most + once per PageVisit via the blink::UseCounter class. + +
+ This histogram recorded values in the renderer process. With the addition of + OOPIF, the counts could be inaccurate due to multiple renderer processes for + a page. It was replaced by an implementation that records values in the + browser process. +
+ + + + + Renamed to Blink.UseCounter.Features in 03/2018, M67. The old blink + UseCounter is flawed in OOPIF, so moved to the browser side (this) instead. + + chasej@chromium.org + feature-control@chromium.org + + Count of how many page loads use various features across all frames in a + page. The PageVisits bucket is incremented for each page load, and the other + buckets incremented at most once per PageVisit via the WebCore::UseCounter + class. This counter lives in browser process. + + + + + + Removed in 06/2018, M69 since the histogram is not really useful. See + https://crbug.com/804645. + + chasej@chromium.org + feature-control@chromium.org + + Like Blink.UseCounter.AnimatedCSSProperties but specifically for the case of + CSS properties used inside of an SVG image. + +
+ Warning: This histogram represents pre-renderer metrics and so is flawed + under OOPIF. + + This histogram counts usage of animated CSS properties only. Refer to + Blink.UseCounter.SVGImage.CSSProperties for details. +
+ + + + + Removed in 06/2018, M69 since the histogram is not really useful. See + https://crbug.com/804645. + + chasej@chromium.org + feature-control@chromium.org + + Like Blink.UseCounter.CSSProperties but specifically for the case of CSS + properties used inside of an SVG image. + +
+ Warning: This histogram represents pre-renderer metrics and so is flawed + under OOPIF. + + The 'Total pages measured' bucket is incremented each time a new SVG image + is created. Note that the same SVG image can be used across multiple tabs in + a single renderer but this counts as a single usage. See + http://crbug.com/236262. +
+ + + + + Removed in 05/2019, M76. Every SVGImage has it's own Page instance and + multiple web pages can share the usage of a single SVGImage. Previously + Blink.UseCounter.Features was recorded on the Blink side per Page; metrics + from SVGImage needed to be recorded in a separate histogram. Now that + metrics are recorded on the browser side, feature usage from SVGImage is + measured via page load metrics, on Blink.UseCounter.Features, once per page + load. This histogram is no longer needed. + + + Like Blink.UseCounter.Features except specifically for the case of SVG + Images. + +
+ Warning: This histogram represents pre-renderer metrics and so is flawed + under OOPIF. + + Count of how many SVG images use various features. The PageVisits bucket is + incremented each time a new SVG image is created. Note that the same SVG + image can be used across multiple tabs in a single renderer but this counts + as a single usage. See http://crbug.com/236262. +
+ + + + + Removed 06/2017 in Issues 455099 and 681769 (M61). + + hiroshige@chromium.org + + The count of XMLHttpRequest.setRequestHeader() calls where header values are + invalid/valid but affected by normalization/valid in RFC 7230. + https://crbug.com/455099. + + + + + + See BlinkGC.TimeForAtomicPhaseMarking. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of finishing marking the transitive closure of objects during the + final Blink garbage collection pause. Recorded at the end of each garbage + collection. + + + + + + Removed 06/2018. The sample taken here was a mix of marking, sweeping and + compaction. Replaced by BlinkGC.AtomicPhaseMarking for the marking phase and + BlinkGC.TimeForTotalCollectGarbage for the overal time. + + haraken@chromium.org + + Duration of time taken to run Heap::collectGarbage(). Recorded at the end of + each garbage collection. + + + + + + Removed as of 07/2019. Use Memory.Renderer.* and + Memory.Experimental.Renderer2.* instead. + + haraken@chromium.org + + The committed memory size in Blink GC. The value is reported when we see the + highest memory usage we've ever seen in the renderer process. + + + + + + Removed 07/2019. Replaced by BlinkGC.TimeForCompleteSweep. + + haraken@chromium.org + Duration of time taken to run ThreadState::completeSweep(). + + + + + Removed at 2014 Jan. + + haraken@chromium.org + + Duration of time taken to run ThreadState::performPendingSweep(). + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of finishing marking the transitive closure of objects during the + final Blink garbage collection pause. Only recorded when incremental marking + finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time taken to run eager sweep finalizers finalizers. Only + recorded when incremental marking finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time for incremental marking finalization. Only recorded when + incremental marking finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time taken to invoke pre finalizers. Only recorded when + incremental marking finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time taken for weak processing. Only recorded when incremental + marking finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time taken to visit cross thread persistents. Only recorded when + incremental marking finalization took at least 40ms. + + + + + + Removed 07/2019. Data gathering finished with the result that slow marking + finalization was mostly caused by visiting DOM wrappers or premature + finalization. + + mlippautz@chromium.org + oilpan-reviews@chromium.org + + Duration of time taken to visit DOM wrappers. Only recorded when incremental + marking finalization took at least 40ms. + + + + + + Removed 07/2019. Coalescing is not used anymore. + + haraken@chromium.org + hpayer@chromium.org + + Duration of memory coalesce operation in the Blink GC. Reported once per + coalesce operation. + + + + + + As of 02/2017, the code to stop Blink threads was removed. + + haraken@chromium.org + + Duration of time taken to stop all Blink threads before starting a GC. + + + + + + As of 07/2019, this metric is replaced by BlinkGC.TimeForSweepingSum. + + haraken@chromium.org + Accumulated time taken to sweep all objects. + + + + + As of 02/2017, the code for thread-local weak processing was removed. + + haraken@chromium.org + Duration of time taken to run thread-local weak processing. + + + + + Obsolete as of 05/2019. + + ulan@chromium.org + + Records how a bloated renderer was handled in the browser process. + + + + + + Obsolete as of 05/2019. + + ulan@chromium.org + + Records how a bloated renderer was handled in the resource coordinator + service. + + + + + + Obsolete as of 05/2019. + + ulan@chromium.org + + Records how a bloated V8 heap was handled in the renderer process. It is + emitted the first time V8 heap reaches the heap limit and invokes the + NearHeapLimitCallback. Subsequent invocations of the callback are ignored. + Thus it is emitted once per renderer process run. + + + + + + Removed as of 04/2019, and replaced by Bluetooth.Availability.v2. This + metric was double-reporting on an error condition. + + kenrb@chromium.org + kpaulhamus@chromium.org + + Determines the availability and capabilities of the Bluetooth driver. This + metric is logged on startup. + + + + + + As of 08/2015 this has been replaced by + Bluetooth.Web.Characteristic.ReadValue and + Bluetooth.Web.Characteristic.WriteValue. + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records how many times each GATT Error has occured. The results will be used + to determine how common this errors are and if we need to provide better + error messages to the users. + + + + + + Removed 08/2015 and replaced by Bluetooth.Web.RequestDevice.Outcome. + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of a navigator.bluetooth.requestDevice() call. Used to + understand what errors developers are getting so we can target efforts + toward the most common ones. Multiple outcomes may result for a given + RequestDevice, such as rescan multiple times and then select a device. + + + + + + Removed as of 11/2016, replaced by + Bluetooth.Web.Blocklist.ParsedNonEmptyString. + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Records the result of BluetoothBlacklist::Add parsing a non-empty string. + These strings will be updated dynamically by a server, and this histogram + provides feedback that parsing is functioning correctly on clients. + + False values are BAD, a blacklist is failing to be applied correctly. + + + + + + Removed as of 3/2017. Replaced by using blink IDL annotation MeasureAs which + appear in Blink.UseCounter.Features. + + odejesush@chromium.org + ortuno@chromium.org + reillyg@chromium.org + + Counts the number of times each call to a WebBluetooth function is done. + + + + + + Replaced 08/2018 by BlueZ.ChipLost2 for more suspend/resume filtering even + when the Bluetooth adapter is turned off. + + sonnysasaka@chromium.org + + This is specific to Chrome OS. Records a duration of a Bluetooth adapter + being lost caused by hardware disconnection. This helps us better understand + the Bluetooth controller drop issue in the field. + + + + + + Removed as of May 2020. + + calamity@chromium.org + johntlee@chromium.org + + Logs when a keyboard shortcut triggers a command in the bookmark manager. + + Revised in M-76 when the "Open (double click/enter)" bucket was + split into two separate buckets, one for bookmarks and one for folders. + + + + + + Removed as of July 2020. + + jhimawan@google.com + twellington@google.com + + Logs the number of drag actions that are performed in one session (defined + as the time between a user's opening a folder and closing said folder). + + + + + + Removed as of July 2020. + + jhimawan@google.com + twellington@google.com + + Logs the number of uses of the Move Up / Down buttons in one session + (defined as the time between a user's opening a folder and closing said + folder). + + + + + + Removed as of 05/2020. + + mamir@chromium.org + mastiz@chromium.org + + The number of bookmarks a user has saved with an empty title (strictly + speaking, i.e. does not count whitespace-only titles), including folders and + excluding the root. Recorded when bookmarks are loaded into storage from + disk if there is at least one node with an empty title. + + + + + + Removed as of 05/2020. + + mamir@chromium.org + + The size of the file used to persist bookmarks. It's recorded every time the + file is loaded in memory. + + + + + + Removed as of 6/2019. This histogram is no longer necessary. + + yfriedman@chromium.org + + Logs the depth of the bookmark in the bookmark tree hierarchy every time a + bookmark is launched. Depth indicates how many levels below a permanent + bookmark folder the bookmark was found in (e.g. a bookmark immediately in + the bookmark bar has depth 1). + + + + + + Removed as of 1/2016. + + kkimlabs@chromium.org + + Logs how user is opening a bookmark on Android. For example, user can long + press and select "Open in a new tab" or "Open in incognito + tab". + + + + + + Replaced 08/2016 by BootTime.Total2 with larger range and more buckets. + + bccheng@chromium.org + semenzato@chromium.org + Time from power on to login panel ready (Chrome OS). + + + + + Removed in M76. + + eustas@chromium.org + Indicates whether the gzip-like header was detected. + + + + + Removed 05/2020. Was not substantially different from results in the GPU + process. + + ccameron@chromium.org + graphics-dev@chromium.org + + Compiling a MTLLibrary will sometimes hang forever. When initializing the + browser process, a test shader is compiled to see if the MTLCompilerService + is responding or not. This records the time that it took for the compile to + succeeded, up to 1 minute. After 1 minute, a timeout sentinel value of 3 + minutes is reported. + + + + + + Removed 05/2020. Did not reveal interesting results. + + ccameron@chromium.org + graphics-dev@chromium.org + + Compiling a MTLLibrary will sometimes hang forever. When initializing the + browser process, a test shader is compiled to see if the MTLCompilerService + is responding or not. This records the time that it took for the compile + method to finish (not including the time for the compile itself to finish), + up to 1 minute. After 1 minute, a timeout sentinel value of 3 minutes is + reported. + + + + + + Removed in M77 with the removal of Browser Actions. + + peconn@chromium.org + + The number of tabs currently opened when users tap "Open in new Chrome + tab" from Browser Actions context menu. This includes the new tab + created from the tap. + + + + + + Removed in M77 with the removal of Browser Actions. + + peconn@chromium.org + + The option that the user selected from a Browser Actions context menu. + + + + + + Removed 09/2017. This histogram has been replaced with + ExternalProtocol.HandleState. + + dominickn@chromium.org + + Whether or not the user checked the option in the external protocol dialog + to remember their choice of opening or not opening the specified app. + Recorded each time the user interacts with the External Protocol Dialog + (either accepting or cancelling/dismissing). + + + + + + Removed June 2019. + + horo@chromium.org + + How long a render process is kept alive by additional customers such as + shared workers and service workers. + + + + + + Removed June 2019. + + panicker@chromium.org + + How long fetch is alive which in turn keeps the render process alive. + TODO(panicker): Remove after investigation of crbug/823482, likely in M68. + + + + + + Removed June 2019. + + panicker@chromium.org + + How long service worker is alive which in turn keeps the render process + alive. TODO(panicker): Remove after investigation of crbug/823482, likely in + M68. + + + + + + Removed June 2019. + + panicker@chromium.org + + How long shared worker is alive which in turn keeps the render process + alive. TODO(panicker): Remove after investigation of crbug/823482, likely in + M68. + + + + + + Removed June 2019. + + alexmos@chromium.org + panicker@chromium.org + + How long the renderer process is kept alive by a subframe unload handler. + TODO(panicker): Remove after investigation of crbug/823482. + + + + + + Removed Feb 2020. + + wfh@chromium.org + + Number of times BrowserRenderProcessHost::OnChannelError was called. + + + + + + Retired in M77 in favour of BrowserServices.TwaOpenTime.V2 which uses a more + appropriate timescale. + + peconn@chromium.org + peter@chromium.org + + Triggered when a TrustedWebActivity is paused, recording the time since it + had been resumed. + + + + + + Obsolete since 01/2020: mus+ash project was canceled, and these metrics are + no longer useful. + + sadrul@chromium.org + mustash-team@google.com + + Duration of an interactive resize from start to end. Measured only on + Windows. + + + + + + Obsolete since 01/2020: mus+ash project was canceled, and these metrics are + no longer useful. + + sadrul@chromium.org + + Size changed between two consecutive steps during browser-window resize. + Measured only on Windows. + + + + + + Obsolete since 01/2020: mus+ash project was canceled, and these metrics are + no longer useful. + + sadrul@chromium.org + + Number of intermediate resize-steps taken to complete the resize from start + to end. Measured only on Windows. + + + + + + Obsolete since 01/2020: mus+ash project was canceled, and these metrics are + no longer useful. + + sadrul@chromium.org + + Time-interval between two consecutive steps during browser-window resize. An + interactive resize can have many number of small steps. This measures the + interval between two steps. 'Duration' measures the interval between the + first and last steps. Measured only on Windows. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was closed because the user accepted it. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + + An open bubble was closed because the user didn't accept it. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was closed because of a focus change. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was forced to close. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was dismissed because a frame was destroyed. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + + An open bubble was dismissed because fullscreen was toggled. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + + An open bubble was dismissed because the page was navigated. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was closed because a tab was detached. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + An open bubble was closed because a tab was switched. + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + + An open bubble was dismissed by the user without making a decission. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + + Log the amount of time any bubble was visible. Only bubbles that are shown + will have a visible time. + + + + + + No longer used; generating code removed in M81. + + hcarmona@chromium.org + A bubble was given to the bubble manager but not shown. + + + + + Renamed to ImageFetcher.Events on 04/2019. + + fgorski@chromium.org + wylieb@chromium.org + + Events that track the lifecycle and performance of the cached_image_fetcher. + The events reported include: success/failure conditions, various recoverable + errors and a couple of dead-end errors. + + + + + + Renamed to ImageFetcher.ImageLoadFromCacheTime on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the cache + in native. + + + + + + Renamed to ImageFetcher.ImageLoadFromCacheTimeJava on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the cache + in Java. + + + + + + Renamed to ImageFetcher.ImageLoadFromNativeTimeJava on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from native + code. Only recorded on successful loads. + + + + + + Renamed to ImageFetcher.ImageLoadFromNetworkAfterCacheHit on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the network + after a cache hit. + + + + + + Renamed to ImageFetcher.ImageLoadFromNetworkTime on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes for cached_image_fetcher to load an image from the + network. + + + + + + Renamed to ImageFetcher.LoadImageMetadata on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time it takes to load an image's metadata from the metadata store. + + + + + + Renamed to ImageFetcher.TimeSinceLastCacheLRUEviction on 06/2019. + + fgorski@chromium.org + wylieb@chromium.org + + The time since the last LRU eviction from the image cache. Recorded when two + LRU evictions occur within closure proximity to one another. Will be used to + determine if LRU eviction is happening too frequently. + + + + + + Replaced with Blink.Canvas.ContextType in 10/2018. + + fserb@chromium.org + kbr@chromium.org + + Records the context type names used to create canvas rendering contexts. + + + + + + Replaced with Blink.Canvas.CreateImageBitmapSource in 10/2018. + + fserb@chromium.org + zakerinasab@chromium.org + + The source from which an ImageBitmap is created by a createImageBitmap call. + + + + + + Removed 11/2017 with removal of Display List Canvas 2D mode. + + fserb@chromium.org + + The reasons why a canvas initially set to display list mode had to fall back + to direct rasterization mode. + + + + + + Replaced with Blink.Canvas.GPUAccelerated2DCanvasDisableDeferralReason in + 10/2018. + + fserb@chromium.org + + The reasons why a GPU accelerated canvas stopped deferring its rendering + operations. + + + + + + Replaced with Blink.Canvas.HibernationEvents in 10/2018. + + fserb@chromium.org + aaronhk@chromium.org + + Records the occurrence of events related to 2D canvas GPU resource + hibernation. + + + + + + Removed 10/2018 with Blink.OffscreenCanvas histograms + + xidachen@chromium.org + fserb@chromium.org + + The type of code path that OffscreenCanvas's commit API goes through. + + + + + + The experiment finishes and removed in 03/2020 + + yiyix@chromium.org + fserb@chromium.org + + measure the percentage of Canvas is dirty before each repaint by using + cc::Rect. Note that we record this metrics for all canvas that has an area + of more than 65k pixel^2 (256x256). + + + + + + The experiment finishes and removed in 03/2020 + + yiyix@chromium.org + fserb@chromium.org + + measure the percentage of Canvas is dirty before each repaint by using + cc::Region. Note that we record this metrics for all canvas that has an area + of more than 65k pixel^2 (256x256). + + + + + + Replaced with Blink.Canvas.RequestedImageMimeTypes in 10/2018. + + aaronhk@chromium.org + + Records the occurence of image file formats passed into toDataURL and toBlob + functions in canvas. + + + + + + Removed 2019/08, this metrics doesn't reflect the measurement speed because + it is dependent on the length of text. + + yiyix@chromium.org + fserb@chromium.org + + Time spent in microseconds to perform calls to measure TextMetrics for + Canvas2d. It's measured each time TextMetrics is called. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 08/2016 with removal of Chrome Crash Service component. + + scottmg@chromium.org + + Tracks the component updater steps for the Chrome Crash Service. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + Count of displayed and not displayed due to errors notifications about + captive portal. + + + + + + Retired in M85. + + pmarko@chromium.org + cros-networking@google.com + cros-oac@google.com + + Count of clicked, closed and ignored captive portal notifications. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + Duration of the captive portal detection process for a particular network at + OOBE. Detection duration is recorded each time portal detection is completed + for an active network. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + The result of captive portal detection attempts performed at OOBE. Detection + result is recorded when portal detection is completed for an active network + and when it differs from the previous result for the same network. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + The result of captive portal detection attempts at OOBE if it diverges from + network manager results. Detection result is recorded each time portal + detection is completed for an active network. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + Number of milliseconds passed between consecutive reports for the same + network about portal and online states. + + + + + + Retired in M85. + + pmarko@chromium.org + cros-networking@google.com + cros-oac@google.com + + Number of milliseconds between start of request to gstatic.com/generate_204 + and receipt of response with redirect to captive portal login page. + + + + + + Retired in M85. + + pmarko@chromium.org + cros-networking@google.com + + Duration of the captive portal detection process for a particular network in + user session. Detection duration is recorded each time portal detection is + completed for an active network. + + + + + + Retired in M85. + + pmarko@chromium.org + michaeldo@chromium.org + cros-networking@google.com + cros-oac@google.com + + The result of captive portal detection attempts performed in user session. + Detection result is recorded when portal detection is completed for an + active network and when it differs from the previous result for the same + network. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + The result of captive portal detection attempts in session if it diverges + from network manager results. Detection result is recorded each time portal + detection is completed for an active network. + + + + + + Retired in M85. + + rsorokin@chromium.org + cros-networking@google.com + cros-oac@google.com + + Number of milliseconds passed between consecutive reports for the same + network about portal and online states. + + + + + + Retired in M86. + + michaeldo@chromium.org + cros-networking@google.com + + The result of captive portal detection attempts performed in user session. + Detection result is recorded when portal detection is completed for a failed + secure connection. + + + + + + Retired in M86. + + michaeldo@chromium.org + cros-networking@google.com + + The result of captive portal detection attempts performed in user session. + Detection result is recorded when portal detection is completed for a + request which timed out or hadn't yet replied within eight seconds. + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + Records the number of times the cast button was shown to the user. The value + will be true if the button is enabled, and false if the button is disabled. + Note that depending on the current UX, it's possible that we hide the button + entirely if it's disabled, so it's possible for the false values to be 0. + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + Records the number of times the cast button was shown to the user when the + video is fullscreened. The value will only be recorded on entering + fullscreen. The value will be true if the button is enabled, and false if + the button is disabled. Note that depending on the current UX,it's possible + that we hide the button entirely if it's disabled, so it's possible for the + false values to be 0. + + + + + + Removed 04/2014, and replaced by Cast.Sender.CastPlayerResult. + + maybelle@chromium.org + miguelg@chromium.org + + Records the result of a request to play remotely. The value will be true if + the playback succeeded, and false if there was an error. + + + + + + Removed July 2017 in favor of Media.Controls.CTR.CastOverlayButton. + + mlamouri@chromium.org + media-dev@chromium.org + + Records events and user interactions related to the Cast overlay shown on + video elements. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The count of cellular device activation failures (Chrome OS). + + + + + + Removed 07/2020 because the histogram is neither logged nor owned. + + Please list the metric's owners. Add more owner tags as needed. + The count of cellular device activation tries (Chrome OS). + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The count of cellular reconnect failures during activation (Chrome OS). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The count of cellular device reconnect tries during activation (Chrome OS). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The count of successful cellular plan established (Chrome OS). + + + + + + Removed 07/2020 because it is unowned and did not appear to be needed. + + Please list the metric's owners. Add more owner tags as needed. + + The count of initiated cellular device setup starts (Chrome OS). + + + + + + Removed logging on 07/2020; the histogram is unowned and has been marked as + obsolete since 04/2016. + + Please list the metric's owners. Add more owner tags as needed. + The count of failed cellular plan setup tries (Chrome OS). + + + + + Removed logging on 07/2020; the histogram is unowned and has been marked as + obsolete since 04/2016. + + Please list the metric's owners. Add more owner tags as needed. + The count of failed cellular plan purchases (Chrome OS). + + + + + Removed logging on 07/2020; the histogram is unowned and has been marked as + obsolete since 04/2016. + + Please list the metric's owners. Add more owner tags as needed. + + The count of successfully completed cellular plan purchases (Chrome OS). + + + + + + Removed as of 8/2013. This histogram only considered the leaf certificate + expiry date as a proxy for whether a certificate was in-scope for the BRs, + but did not consider the issuance date. As some CAs have issued long-lived + certs prior to the BRs, this disproportionately reported those certs as + being subject to the BRs, but non-compliant, when in reality they're not + subject. + + Please list the metric's owners. Add more owner tags as needed. + + Information about the certificate algorithms and sizes in use on the web, to + examine compliance with the CA/Browser Forum requirements and security best + practice. + + + + + + Removed 3/2013. Renamed to ChildProcess.Crashed2. + + Please list the metric's owners. Add more owner tags as needed. + Count of child process crashes grouped by process type. + + + + + Removed as of 10/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process crashes that we miscounted because we took the exit + code too early. Grouped by process type. + + + + + + Removed 10/2011. Renamed to ChildProcess.Crashed. + + Please list the metric's owners. Add more owner tags as needed. + Count of child process crashes grouped by process type. + + + + + Removed 10/2011. Renamed to ChildProcess.CrashedWasAlive. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process crashes that we miscounted because we took the exit + code too early. Grouped by process type. + + + + + + Removed as of 10/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process crashes for which we were not able to understand the + exit code, grouped by process type. + + + + + + Removed 3/2013. Renamed to ChildProcess.Disconnected2. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process abnormal channel disconnects grouped by process type. + + + + + + Removed 3/2013. Renamed to ChildProcess.DisconnectedAlive2. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process abnormal channel disconnects that are not classified + and reported because we took the exit code too early. Grouped by process + type. + + + + + + Removed 3/2017. + + clamy@chromium.org + + What the browser was waiting for from the renderer when it was reported as + hung. + + + + + + Removed 4/2019. + + cmumford@chromium.org + + What the browser was waiting for from the renderer when it was reported as + hung. + + + + + + Removed 6/2019. + + wfh@chromium.org + + Whether the browser command line had the switch --no-startup-window when a + child process crashed due to invalid sandbox state. Recorded when a child + process crashes if the exit code from the child process is + RESULT_CODE_INVALID_SANDBOX_STATE. + + + + + + Removed 3/2013. Renamed to ChildProcess.Killed2. + + Please list the metric's owners. Add more owner tags as needed. + Count of child process kills grouped by process type. + + + + + Removed as of 10/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process kills that we miscounted because we took the exit + code too early. Grouped by process type. + + + + + + Removed 10/2011. Renamed to ChildProcess.Killed. + + Please list the metric's owners. Add more owner tags as needed. + Count of child process kills grouped by process type. + + + + + Removed 10/2011. Renamed to ChildProcess.KilledWasAlive. + + Please list the metric's owners. Add more owner tags as needed. + + Count of child process kills that we miscounted because we took the exit + code too early. Grouped by process type. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates how many times each particular type of Activity was in the + foreground when a UMA session was terminated abnormally. UMA sessions last + as long as Chrome remains in the foreground. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates how many times each particular type of Activity was brought to the + foreground when a UMA session was active (i.e. launched at some point). UMA + sessions last as long as Chrome remains in the foreground. + + + + + + Removed 12/2019. + + manzagop@chromium.org + + Indicates the execution phase the browser was in when the browser crashed. + + + + + + Removed as of 11/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates the execution phase the browser was in when browser didn't exit + cleanly. + + + + + + Removed as of 04/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The total number of times the browser process has attempted to generate a + crash dump. This should be the sum of Chrome.BrowserDumpsWithCrash and + Chrome.BrowserDumpsWithNoCrash. + + + + + + Removed as of 04/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times the browser process has attempted to generate a crash + dump because of an actual browser crash. + + + + + + Removed as of 04/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times the browser process has attempted to generate a crash + dump in a non-crashing (i.e., reporting only) context. + + + + + + Removed in 07/2020 because the histogram is unused. + + isherman@chromium.org + src/base/metrics/OWNERS + + The number of command line switches that were present at the start of a + chrome session. + + + + + + Removed in 07/2020 because the histogram is unused. + + isherman@chromium.org + src/base/metrics/OWNERS + + The number of command line switches that were present at the start of a + chrome session, excluding App Mode and User Data Directory switches. + + + + + + Removed as of 12/2017. + + gab@chromium.org + aseren@yandex-team.ru + + The error code of remote process termination on Windows in case when remote + process hung. This histogram has been replaced by + Chrome.ProcessSingleton.TerminateProcessErrorCode.Windows histogram. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user not in the search engine dialog + experiment. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user in the search engine dialog + experiment. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user in slot 1 of a randomized + search engine dialog. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user in slot 2 of a randomized + search engine dialog. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user in slot 3 of a randomized + search engine dialog. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + The default search engine selected by a user in slot 4 of a randomized + search engine dialog. + + + + + + Removed 6/2017. No longer tracked. + + asvitkine@chromium.org + + Records when a page load happens, based on the same logic as the PageLoad + user action. + + + + + + Removed 12/2019. No longer tracked. + + gayane@chromium.org + yyushkina@chromium.org + + Records applied color id every time its applied from Colors menu. + + + + + + Removed 12/2019. No longer tracked. + + gayane@chromium.org + yyushkina@chromium.org + + Records whether color/theme changes were confirmed or reverted by + ChromeColorsService. + + + + + + Removed 12/2019. No longer tracked. + + gayane@chromium.org + yyushkina@chromium.org + + Records the reason color/theme changes were reverted by ChromeColorsService. + + + + + + Removed 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*. + + lizeb@chromium.org + + Time between the intent arrival in a Chrome generated custom tab and the + first navigation commit, if the navigation is successful. Similar in + principle to Startup.FirstCommitNavigationTime. + + + + + + Removed 2017-08 in favor of + ChromeGeneratedCustomTab.IntentToFirstNavigationStartTime. + + lizeb@chromium.org + + In "Herb" mode shows the time between the intent arrival in a + Chrome generated custom tab and the first navigation start (note: not the + navigation commit, as the name suggests). Recorded when the page has + finished loading. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The actions to enable or disable services sending synced notifications. + Synced Notification Sending services can be individually disabled by the + user in the Chrome Notification center settings dialog. + + + + + + Removed 01/2020 in Issue 1036859 with the removal of the heap collection + code. + + aalexand@google.com + gmx@chromium.org + + A count of successes and various failure modes related to the collection and + processing of Chrome heap sample profiles on Chrome OS. + + + + + + Removed 01/2020 in Issue 1036859 with the removal of the heap collection + code. + + aalexand@google.com + gmx@chromium.org + + Records the number of "heap" reports included in an UMA upload on + Chrome OS. + + + + + + Removed 10/2017 and replaced by Platform.DetachableBase.PairResult. + + kitching@google.com + Result of a Chrome OS detachable base pair operation. + + + + + Removed 10/2017 and replaced by Platform.DetachableBase.ROUpdateMetric. + + kitching@google.com + Result of a Chrome OS detachable base RO firmware update. + + + + + Removed 10/2017 and replaced by Platform.DetachableBase.RWUpdateMetric. + + kitching@google.com + Result of a Chrome OS detachable base RW firmware update. + + + + + Removed 8/2017. + + xiaowenx@chromium.org + mukai@chromium.org + + The name of the current color calibration of the display on Chrome OS. This + value is sent when the color calibration is changed by the user. + + + + + + Removed in 2020/06 as the histogram is no longer in use. The instrumentation + code is long gone. The iframe flow is not used since 2015. + + achuith@chromium.org + + Whether a user signed in using the new WebView-based GAIA flow. This value + is sent after the GAIA screen has completed user authentication. + + + + + + Removed in 2019/08 as the histogram is no longer in use. (crbug/975047) + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The result of a certificate expiry check during a platform verification + attempt for content protection on Chrome OS. + + + + + + Removed as of 10/2019. Replaced with ChromeOS.SAML.APILogin that correctly + records various login flows. + + bartfab@chromium.org + + Whether a Chrome OS login via SAML used the principals API. This is recorded + during login on Chrome OS if SAML is being used for authentication. + + + + + + Removed as of 10/2019. Replaced with ChromeOS.SAML.Scraping.PasswordCountAll + that fixes the main case of a single scraped password. + + bartfab@chromium.org + + The number of passwords that were scraped during a Chrome OS login via SAML. + This is set only when the principals API is not used. + + + + + + Removed as of 05/2020 (crbug/1072514). + + jamescook@chromium.org + cros-system-services@google.com + + Records whether the "try your Chrome browser settings" banner was + shown when the user opened a new Chrome OS settings window and also records + interactions with the banner. + + + + + + Removed as of 06/2019. + + digit@chromium.org + pasko@chromium.org + lizeb@chromium.org + + Whether relro sharing was attempted for the browser process, and if + attempted, whether it succeeded. + + + + + + Removed 10/2014 in Issue 419010, and replaced by + ChromiumAndroidLinker.BrowserStates. + + simonb@chromium.org + Is low memory device. + + + + + Removed as of 06/2019. + + petrcermak@chromium.org + + Whether the device supports loading a library directly from the APK file. + The functionality is checked and reported during every Chromium browser + process start up. + + + + + + Removed 10/2014 in Issue 419010, and replaced by + ChromiumAndroidLinker.RendererStates. + + simonb@chromium.org + Load at fixed address failed. + + + + + Removed 2020-02 as part of crbug.com/1021156. + + lizeb@chromium.org + pasko@chromium.org + + Status of each attempt to load the native library with a custom linker. + Recorded after each attempt to load. Not recorded when all attempts fail in + a process. + + + + + + Removed 2019-07 in crbug.com/981599. + + agrieve@chromium.org + yfriedman@chromium.org + + The total number of times Chrome uses relinker fallback to extract and load + native libraries. + + + + + + Removed as of 06/2019. + + simonb@chromium.org + + Whether relro sharing was attempted for a renderer process, and if + attempted, whether it succeeded. + + + + + + Removed 07/2020 because this unowned histogram is no longer being used and + has expired. + + Please list the metric's owners. Add more owner tags as needed. + + The length of time between a dangerous download appearing on the downloads + shelf, and the "Discard" button being clicked. + + + + + + Removed 07/2020 because this unowned histogram is no longer being used and + has expired. + + Please list the metric's owners. Add more owner tags as needed. + + The length of time between a dangerous download appearing on the downloads + shelf, and the "Dismiss" button being clicked. Deprecated since + M54. + + + + + + Removed 07/2020 because this unowned histogram is no longer being used and + has expired. + + Please list the metric's owners. Add more owner tags as needed. + + The length of time between the external protocol dialog being shown and the + "Launch Application" button being clicked. + + + + + + Removed 07/2020 because this unowned histogram is no longer being used and + has expired. + + Please list the metric's owners. Add more owner tags as needed. + + The length of time between a download appearing on the download shelf, and + the user opening it by clicking the item or pressing return. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Time between "Report and Discard" button being shown and it being + clicked. + + + + + + Removed M86 since what it's measuring no longer happens. + + yoavweiss@chromium.org + tbansal@chromium.org + mkwst@chromium.org + + Count of client hints that were received by the render process. Recorded + approximately at the time of the renderer startup. + + + + + + Launched briefly in M-59 dev, then refactoring made obsolete. + + mpearson@chromium.org + + Whether Android's Clipboard.java successfully constructed a hasher to hash + clipboard entries. Recorded on construction of the class, which happens only + on startup. + + + + + + Removed as of 4/2013, experiment confirmed correctness of our patch. + + Please list the metric's owners. Add more owner tags as needed. + + Counts how often the user writes or reads from the clipboard and whether the + write was from an incognito window or not. + + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + The amount of time between capabilities updates. + + + + + Removed 12/2015. http://crbug.com/466644 + + thestig@chromium.org + + Temporarily histogram with size of IPC sockets in default location. + + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + + The amount of time used to fail to collect printer capabilities. + + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + The amount of time used to collect printer capabilities. + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + + The amount of time the utility process runs before disconnect. + + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + The amount of time used to fail to generate metafile. + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + The amount of time used to generate metafile. + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + + The amount of time used to fail to collect printer capabilities. + + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + The amount of time used to collect printer capabilities. + + + + + Removed 02/2017. http://crbug.com/643570 + + thestig@chromium.org + Xmpp timeout option value provided by server. + + + + + Removed in July 2019 + + weili@chromium.org + + Tracks the status of PDF document composition and generation conducted in + PDF compositor service. + + + + + + Removed in July 2019 + + weili@chromium.org + + Tracks the status of PDF page composition and generation conducted in PDF + compositor service. + + + + + + Removed 05/2019 because it no longer reports. To be superseded by a + measurement related to percentage of cache/discardable memory used by image + caching. + + vmpstr@chromium.org + + The maximum number of images that were cached in the browser over the + lifetime of the image decode cache. This is recorded at the image cache + destruction. It is further split up by Software and Gpu rasterization. + + + + + + Removed 06/2019 because the research it was used for is complete. + + ccameron@chromium.org + + The total number of quads in all render passes in a CompositorFrame. This is + logged as the CompositorFrame is submitted to its surface. + + + + + + Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when display list recording source is updated (in a + browser process). + + + + + + Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a display list, in microseconds. + Recorded when display list is updated (in a browser process). + + + + + + Removed 10/2018. This metric didn't end up being useful. + + kylechar@chromium.org + + How often the layer compositor successfully submitted content to the display + compositor, or what caused an abort. This is reported fairly late in the + pipeline, during the final stages of submitting content. + + + + + + Removed September, 2020. Memory.GPU.PeakMemoryUsage.PageLoad can be used to + track overall GPU memory usage. + + pdr@chromium.org + paint-dev@chromium.org + + The GPU memory allocated for tilings (in a browser process), summed over all + picture layers. Emitted once per drawing. Nothing is recorded if there are + no picture layers. + + Tilings are used for decomposition of the layer's entire contents at a + picture screenspace resolution to do threaded rasterization. + + + + + + Has not produced data for over a year prior to removal in 03/2020. + + paint-dev@chromium.org + + Total estimated memory used by SkPictures in the layer tree, in kilobytes. + Recorded once per frame, before the frame is drawn (in a browser process). + + + + + + Obsolete since 2015. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when picture pile is updated (in a browser process). + + + + + + Obsolete since 2015. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a picture pile, in microseconds. + Recorded when picture pile is updated (in a browser process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 11/2016. Increased the max tracking range to accomendate GPU raster, + and will require new baskets. + + paint-dev@chromium.org + + Rasterized area, in pixels, divided by rasterization time, in milliseconds, + of a compositor rasterization task. Recorded after the task finishes (in a + browser process). + + + + + + Removed 04/2019. Was unused. + + paint-dev@chromium.org + + Rasterized area, in pixels, divided by rasterization time, in milliseconds, + of a compositor rasterization task. Recorded after the task finishes (in a + browser process). + + + + + + Removed 04/2019. Was unused. + + paint-dev@chromium.org + + Time spent completing a compositor rasterization task, in microseconds. + Recorded after the task finishes (in a browser process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 02/2016. We'd learned as much as we could from this metric and it + made no sense to keep it around. + + vollick@chromium.org + + Tracks the number of missing tiles that had some image content in the + browser process. + + + + + + Removed 02/2016. We'd learned as much as we could from this metric and it + made no sense to keep it around. + + vollick@chromium.org + + Tracks the number of missing tiles that did not have any image content in + the browser process. + + + + + + Expired 2020-03-01. + + kylechar@chromium.org + + The result of submitting a CompositorFrame to a CompositorFrameSink. + ACCEPTED means the frame was accepted by the CompositorFrameSink. + COPY_OUTPUT_REQUESTS_NOT_ALLOWED means an unprivileged client attempted to + readback a texture. SURFACE_INVARIANTS_VIOLATION means size or device scale + factor changed but a new viz::LocalSurfaceId was not allocated. + + + + + + Made obsolete 04/2016. Logging removed 08/2020. + + Please list the metric's owners. Add more owner tags as needed. + + The time taken for the sync readback of pixels is measured here. + + + + + + Removed 02/2018, replaced by similar metric + Compositing.Display.Draw.Occlusion.Drawing.Area.Saved2. + + yiyix@chromium.org + + It records the total drawing area skipped to show on screen as a result of + applying draw occlusion. This is logged once per frame, when the frame is + drawn. + + + + + + Removed 06/2019 because the research it was used for is complete. + + ccameron@chromium.org + + This is logged once per frame, when the frame is drawn. The total number of + quads in all render passes in the CompositorFrame that is produced by + surface aggregation. + + + + + + Removed 03/2018. We'd learned enough from this metric and it made no sense + to keep it around. + + yiyix@chromium.org + + This is logged once per frame, when the frame is drawn. Captures area of all + draw quads that need to go through no scale and no translation transforms. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when display list recording source is updated. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a display list, in microseconds. + Recorded when display list is updated. + + + + + + Removed 05/2017 in Issue 710306. Histogram was used temporarily for tracking + a potential performance regression. + + paint-dev@chromium.org + + Time spent finding the closest matching layer to a given point, in + microseconds. Recorded each time we do hit testing on LayerTreeImpl. + + + + + + Expired M81 + + kylechar@chromium.org + + The amount of time it took for a main frame with unresolved dependencies to + activate. Note that some activations may be triggered due to a deadline + hitting. + + + + + + Removed 04/2016, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + dneto@chromium.org + + The number of layers in the active tree for each compositor frame. This is + logged once per frame, before the frame is drawn. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Total estimated memory used by SkPictures in the layer tree, in kilobytes. + Recorded once per frame, before the frame is drawn. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when picture pile is updated. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a picture pile, in microseconds. + Recorded when picture pile is updated. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Rasterized area, in pixels, divided by rasterization time, in milliseconds, + of a compositor rasterization task. Recorded after the task finishes. + + + + + + Removed 09/2015, replaced by similar metrics under Compositing.Renderer and + Compositing.Browser, depending on which process it occurs in. + + paint-dev@chromium.org + + Time spent completing a compositor rasterization task, in microseconds. + Recorded after the task finishes. + + + + + + Removed 05/2019 because it no longer reports. To be superseded by a + measurement related to percentage of cache/discardable memory used by image + caching. + + vmpstr@chromium.org + + The maximum number of images that were cached in the renderer over the + lifetime of the image decode cache. This is recorded at the image cache + destruction. It is further split up by Software and Gpu rasterization. + + + + + + Removed 01/2020. + + khushalsagar@chromium.org + + The outcome for whether an image could be sucessfully deferred for + asynchronous decode in the renderer compositor. If not, the reason for using + a synchronous decode. An image which is decoded asynchronously will be + checkerboarded on the rasterized tiles until the decode is finished, as + opposed to synchronous decodes where the tile rasterization is blocked on + the image decode completing. + + + + + + Removed 06/2019 because the research it was used for is complete. + + ccameron@chromium.org + + The total number of quads in all render passes in a CompositorFrame. This is + logged as the CompositorFrame is submitted to its surface. + + + + + + Removed September 2020 because the research it was used for is complete. + + pdr@chromium.org + dlibby@microsoft.com + paint-dev@chromium.org + + Records instances of directly composited images that did not need to + recalculate raster scale in response to scale changes. The boolean value + indicates whether will-change:transform is set or a scale transforms is + animating. This metric will be used to determine the impact on raster CPU + usage if we were to scope the directly composited images feature. + + + + + + Removed September 2020 because the research it was used for is complete. + + pdr@chromium.org + dlibby@microsoft.com + paint-dev@chromium.org + + Records whether or not a PictureLayerImpl that has a single drawImage paint + operation is able to apply directly composited image optimization. See + PictureLayerImpl::ShouldDirectlyCompositeImage for more details. + + + + + + Removed September 2020 because the research it was used for is complete. + + pdr@chromium.org + dlibby@microsoft.com + paint-dev@chromium.org + + Records the number of tile pixels added when directly composited image is + applied to a layer. If the raster scale is greater than it otherwise would + be, the difference in pixels used for tiling the layer is logged in this + histogram. + + + + + + Removed September 2020 because the research it was used for is complete. + + pdr@chromium.org + dlibby@microsoft.com + paint-dev@chromium.org + + Records whether or not the chosen raster scale for a directly composited + image matches the ideal raster scale. In cases where the scale does not + match (i.e. false values for this histogram), either TileAreaAdded or + TileAreaSaved will be logged to provide an indication on the effects on + memory usage. + + + + + + Removed September 2020 because the research it was used for is complete. + + pdr@chromium.org + dlibby@microsoft.com + paint-dev@chromium.org + + Records the number of tile pixels saved when directly composited image is + applied to a layer. If the raster scale is lower than it otherwise would be, + the difference in pixels used for tiling the layer is logged in this + histogram. + + + + + + Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when display list recording source is updated (in a + renderer process). + + + + + + Removed 05/2016. See Blink.Paint.UpdateTime as a related alternate metric. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a display list, in microseconds. + Recorded when display list is updated (in a renderer process). + + + + + + Removed 10/2018. This metric didn't end up being useful. + + kylechar@chromium.org + + How often the layer compositor successfully submitted content to the display + compositor, or what caused an abort. This is reported fairly late in the + pipeline, during the final stages of submitting content. + + + + + + Replaced by Compositing.Renderer.LCDTextDisallowedReason* on 2020-05-08. + + wangxianzhu@chromium.org + paint-dev@chromium.org + + Records the percentage of approximate number of pixels covered by text + drawing operations that are LCD-text eligible, in that of all text drawing + operations. This is recorded when the renderer is idle, at minimum interval + of the longer of 1 minute and 500 begin frames for each local frame tree. + Note that LCD-text eligible text may rasterize in non-LCD-text mode when + e.g. LCD-text is not supported by the font or LCD-text doesn't appreciably + improve quality. + + + + + + Removed in 03/2020 because changes in the data are difficult to reason about + as the number of layers also tends to change at the same time. + + + + paint-dev@chromium.org + + The number of PictureLayers in the active tree for each compositor frame + that have both text drawing operations and do not permit lcd text. This is + logged once per frame, before the frame is drawn (in a renderer process). + Suffixed with the count of number of picture layers with text. + + + + + + Removal in 03/2020 because it is not very useful. + + paint-dev@chromium.org + + Total estimated memory used by SkPictures in the layer tree, in kilobytes. + Recorded once per frame, before the frame is drawn (in a renderer process). + + + + + + Obsolete since 2015. + + paint-dev@chromium.org + + Area of invalidated content, in pixels, divided by update (i.e. record), in + milliseconds. Recorded when picture pile is updated (in a renderer process). + + + + + + Obsolete since 2015. + + paint-dev@chromium.org + + Time spent updating (i.e. recording) a picture pile, in microseconds. + Recorded when picture pile is updated (in a renderer process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 11/2016. Increased the max tracking range to accomendate GPU raster, + and will require new baskets. + + paint-dev@chromium.org + + Rasterized area, in pixels, divided by rasterization time, in milliseconds, + of a compositor rasterization task. Recorded after the task finishes (in a + renderer process). + + + + + + Removed 04/2019. Was unused. + + paint-dev@chromium.org + + Rasterized area, in pixels, divided by rasterization time, in milliseconds, + of a compositor rasterization task. Recorded after the task finishes (in a + renderer process). + + + + + + Removed 04/2019. Was unused. + + paint-dev@chromium.org + + Time spent completing a compositor rasterization task, in microseconds. + Recorded after the task finishes (in a renderer process). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 02/2016. We'd learned as much as we could from this metric and it + made no sense to keep it around. + + vollick@chromium.org + + Tracks the number of missing tiles that had some image content in the + renderer process. + + + + + + Removed 02/2016. We'd learned as much as we could from this metric and it + made no sense to keep it around. + + vollick@chromium.org + + Tracks the number of missing tiles that did not have any image content in + the renderer process. + + + + + + Removed as being no longer useful to track. + + enne@chromium.org + chrishtr@chromium.org + + Percent of layers drawn that frame that are mask layers. A sample is + recorded on the first draw per commit. + + + + + + Removed as being no longer useful to track. + + enne@chromium.org + chrishtr@chromium.org + + Total visible area of layers drawn that frame that are mask layers and also + are simple rounded corner masks. A sample is recorded on the first draw per + commit. + + + + + + Removed as being no longer useful to track. + + enne@chromium.org + chrishtr@chromium.org + + Percent of visible area of layers drawn that frame that are mask layers and + also are simple rounded corner masks. A sample is recorded on the first draw + per commit. + + + + + + Removed as being no longer useful to track. + + enne@chromium.org + chrishtr@chromium.org + + Percent of layers drawn that frame that are mask layers and also are simple + rounded corner masks. A sample is recorded on the first draw per commit. + + + + + + Removed 10/2018. This metric didn't end up being useful. + + akaba@chromium.org + kylechar@chromium.org + + The distance between the latest inflight surface and the primary surface. + This is logged for each call to HandleSurfaceQuad(). + + + + + + Removed 07/2018 in issue 865597 in order to avoid spurious error messages on + Viz process crash. + + kylechar@chromium.org + + The number of SurfaceDrawQuads where the surface doesn't exist. This is + logged for each call to Aggregate(). + + + + + + Removed 07/2018 in issue 865597 in order to avoid spurious error messages on + Viz process crash. + + kylechar@chromium.org + + The number of SurfaceDrawQuads where the surface exists but doesn't have an + active CompositorFrame. This is logged for each call to Aggregate(). + + + + + + Removed 10/2018. This metric didn't end up being useful. + + kylechar@chromium.org + + The number of SurfaceDrawQuads where the primary SurfaceId does not have a + corresponding active CompositorFrame and so the fallback surface is used + instead. This is logged for each call to Aggregate(). + + + + + + Removed 10/2018. This metric didn't end up being useful. + + kylechar@chromium.org + + The number of SurfaceDrawQuads where the surface exists and has an active + CompositorFrame. This is logged for each call to Aggregate(). + + + + + + Removed as of 10/2018. This metric didn't end up being useful. + + kylechar@chromium.org + + Tracks whether an activation of a surface was due to due to a deadline or + the resolution of dependencies. + + + + + + Removed as of 2018/09/10 in favor of + Compositing.CompositorFrameSinkSupport.SubmitResult. + + kylechar@chromium.org + + The number of times a renderer in this browser session has violated a + surface synchronization invariant. This manifests as a skipped frame. + Ideally this metric should always report 0, but realistically there are + races in the system and this tracks the frequency that we hit these races. + + + + + + Removed 2018/01/24. + + kylechar@chromium.org + + The number of temporary references that have existed for at least 10 seconds + and are most likely orphaned. This is logged every 10 seconds. + + + + + + Expired M81. + + kylechar@chromium.org + Tracks the reason for removing a temporary reference. + + + + + Expired M81. + + kylechar@chromium.org + + Tracks the number of temporary references after each garbage collection + operation. + + + + + + Obsolete after 03/2019. For temporary debugging of CompositorImpl hangs. + + ericrk@chromium.org + + Tracks the amount of time it takes to synchronously tear down the display + when the CompositorImpl becomes invisible or is destroyed. Recorded after + display teardown completes in CompositorImpl:: + TearDownDisplayAndUnregisterRootFrameSink. + + + + + + Removed on 01/2020. MissedFrame changed to DroppedFrame for more clarity. + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages in the pipeline as a single frame goes + through the various stages in the compositor. This is reported for frames + that the user did not see: this includes frames that are dropped in various + stages inside chromium, or even frames that went through all stages in + chromium, but ultimately was not presented to the user. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed on 9/2019. Did not provide enough information about latency. + + sadrul@chromium.org + graphics-dev@chromium.org + + The latency increase of an abnormally long activation stage on the + multithread thread compositor pipeline when the frame is missed. + + These latency increases are determined by comparing the stage duration to + the times from past non-missed frames. These times are also reported to + "CompositorLatency.MissedFrame.<StageName>" + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Whether or not the network connectivity info, i.e. validated, is provided by + the system. We will use it if it is available from the system. Otherwise, we + will do our own http probes to find it out. This UMA will not be recorded if + a flag in about:flags is set to bypass this logic to always favor the check + by http probes. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + The HTTP response code returned from a HTTP probe for the purpose of + checking network connectivity. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + The result from a HTTP probe for the purpose of checking network + connectivity. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + The total duration measuring all the HTTP probes and backoff time taken when + the network connectivity is successfully validated. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Records type of url, default or fallback URL, resulting in successful + connectivity validation. + + + + + + Removed 04/2020. No longer used. + + ebeach@google.com + HTTP latency seen by the Connectivity Diagnostics. +
+ HTTP latency is computed using the chrome.socket API to make an HTTP GET + request to the /generate_204 page of three randomly generated Google + hostnames (*-ccd-testing-v4.metric.gstatic.com). The time taken from issuing + the HTTP request to receiving a response is clocked in JavaScript and the + arithmetic mean of the three times is used as the HTTP latency. +
+ + + + + Removed 04/2020. No longer used. + + ebeach@google.com + + Connectivity Diagnostics App: Outcome of the connectivity tests. + + + + + + Removed 04/2020. No longer used. + + ebeach@google.com + + Connectivity Diagnostics App: Amount of time taken to run each of the + connectivity tests. + + + + + + Expired + + michaelbai@chromium.org + The estimated time taken to capture one on-screen content. + + + + + Removed 07/2014 since it is not referenced anywhere in the code. + + toyoshim@chromium.org + The default handler setting at profile open. + + + + + Support for keygen was removed. + + svaldez@chromium.org + + The default setting for using key generation in forms at profile open. + + + + + + This setting was deprecated in r322364 and replaced with separate settings + for camera and microphone. See + ContentSettings.DefaultMediaStreamCameraSetting and + ContentSettings.DefaultMediaStreamMicSetting. + + toyoshim@chromium.org + msramek@chromium.org + The default MediaStream setting at profile open. + + + + + Removed on 2020-07-07. This histogram is no longer recorded. + + toyoshim@chromium.org + The default mouse cursor setting at profile open. + + + + + Removed on 2020-07-07. This histogram is no longer recorded. + + miguelg@chromium.org + + The default permission setting for push messages at profile open. + + + + + + Removed 2015-10-05 in Issue 433475. Histogram was used temorarily for + diagnosing crash causes. + + scheib@chromium.org + + Numer of results of parsing WebsiteSettingsHandler::last_setting_ success or + failure in WebsiteSettingsHandler methods. + + + + + + Removed 2020-01-06. Histogram had already expired and metrics are no longer + required after the mixed content shield removal. + + estark@chromium.org + + Tracks whether the mixed content shield was shown, and how the user + interacted with it. + + + + + + Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.Allow + + battre@chromium.org + + The number of user defined cookies setting exceptions for allowing cookies + at browser start. + + + + + + Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.Block + + battre@chromium.org + + The number of user defined cookies setting exceptions for blocking cookies + at browser start. + + + + + + Removed Oct 2018 in favor of ContentSettings.Exceptions.cookies.SessionOnly + + battre@chromium.org + + The number of user defined cookies setting exceptions for 'clearing cookies + on browser exit' at browser start. + + + + + + Removed 11/2015 in favor of Permissions.Action.* + + miguelg@chromium.org + + Tracks whether a permission was granted, rejected, etc. The suffix of the + histogram indicates which particular permission. + + + + + + Removed 11/2015 in favor of Permissions.Action.InsecureOrigin.* + + miguelg@chromium.org + + Tracks whether a permission was granted, rejected, etc on an insecure + origin. The suffix of the histogram indicates which particular permission. + + + + + + Removed 11/2015 in favor of Permissions.Action.SecureOrigin.* + + miguelg@chromium.org + + Tracks whether a permission was granted, rejected, etc on a secure origin. + The suffix of the histogram indicates which particular permission. + + + + + + Removed in favor of ContentSettings.Popups.FirstDocumentEngagementTime2. + + csharrison@chromium.org + + Measures the total duration a popup WebContents is visible / foregrounded + for the duration of its first document load. This time is measured from the + first navigation commit to the time either the WebContents is destroyed or + when a new navigation commits. + + + + + + Removed in favor of + SubresourceFilter.PageLoad.Activation.RedirectPosition2.Enforcement + + csharrison@chromium.org + ericrobinson@chromium.org + + For pages that trigger Safe Browsing triggered popup blocker (in warn or + enforce modes), records the position in the redirect chain for the page the + activation was triggered by. If SubresourceFilterConsiderRedirects is + disabled, then always returns "Only navigation". + + + + + + Removed in favor of ContentSuggestions.Feed.AppLifecycle.Events. + + pnoland@chromium.org + fgorski@chromium.org + + Android: count of app lifecycle events reported to the Feed library. + Recorded as these events occur; e.g. when Chrome is foregrounded, + backgrounded, or the user clears cached browsing data. + + + + + + Removed in favor of CachedImageFetcher.Events. + + wylieb@chromium.org + + Android: Represents success/failure of Feed image loading. Recorded upon + each individual image retrieved from the feed_image_cache. Feed v1 only. + + + + + + Removed in favor of CachedImageFetcher.Events. + + wylieb@chromium.org + + Android: The time it takes for Feed to load an image from the cache. + + + + + + Removed in favor of CachedImageFetcher.Events. + + wylieb@chromium.org + + Android: The time it takes for Feed to load an image from the network. + + + + + + Removed 4/2019 in favor of ProtoDB.InitStatus.*. + + gangwu@chromium.org + fgorski@chromium.org + + Tracks the Feed storage success rate during initial storage. + + + + + + Removed 4/2019 in favor of ProtoDB.LoadKeysSuccess.*. + + gangwu@chromium.org + fgorski@chromium.org + Tracks the Feed storage success rate during load keys. + + + + + Removed 4/2019 in favor of ProtoDB.LoadEntriesSuccess.*. + + gangwu@chromium.org + fgorski@chromium.org + Tracks the Feed storage success rate during load entries. + + + + + This implementation is incorrect and we are now using + NewTabPage.ActionAndroid2 instead. Marked obsolete in 01-2020 + + carlosk@chromium.org + freedjm@chromium.org + feed@chromium.org + + The position of a card in the feed from which the user has opened the Manage + Interests page. Recorded when the Manage Interest item is clicked in the + card menu. + + + + + + Removed in favor of ContentSuggestions.Feed.Network.RequestStatusCode. + + pnoland@chromium.org + + Android: The integer status code of network requests made by the feed + library's networking host. This code includes both protocol(1xx-5xx) and + non-protocol(-xxx) errors. Recorded when a request completes. + + + + + + Removed 4/2019 in favor of ProtoDB.UpdateSuccess.*. + + gangwu@chromium.org + fgorski@chromium.org + + Tracks the Feed storage success rate during commit operations. + + + + + + Removed in favor of + ContentSuggestions.Feed.Network.RequestSizeKB.Compressed. + + pnoland@chromium.org + + Android: the size in kb of gzip-compressed requests sent by the Feed's + networking host. Recorded when a request is sent. + + + + + + Removed in favor of ContentSuggestions.Feed.Network.ResponseSizeKB. + + pnoland@chromium.org + + Android: the uncompressed size in KB of responses received by the Feed's + networking host. Recorded when a successful response is received. + + + + + + Removed in favor of ContentSuggestions.Feed.TokenCompleted.ContentCount2. + Removed 03/2019. http://crbug.com/943838 + + skym@chromium.org + gangwu@chromium.org + + How many top level features were in the continuation response, typically + clusters. Recorded when the fetch completes successfully. + + + + + + Removed in favor of ContentSuggestions.Feed.Network.TokenFetchStatus. + + pnoland@chromium.org + + Android: failure reason when attempting to fetch an OAuth token for the + feed. Recorded when an artcile fetch completes. + + + + + + Removed in favor of ContentSuggestions.FetchPendingSpinner.VisibleDuration. + + dgn@chromium.org + ntp-dev+metrics@chromium.org + + Android: How long the content suggestion placeholder is shown. This is + tracked based on when the placeholder is enabled in the UI, not how long it + is actually visible on screen. Depending on the screen size, the used value + could be bigger. + + + + + + Removed in favor of + ContentSuggestions.Feed.FetchPendingSpinner.VisibleDuration. + + dgn@chromium.org + ntp-dev+metrics@chromium.org + + Android: How long the content suggestion loading spinner is shown. This is + tracked based on when the spinner is enabled in the UI, not how long it is + actually visible on screen. Depending on the screen size, the used value + could be bigger. + + + + + + Removed 06/2019. iFrame Context Menu feature shipped. + + michaeldo@chromium.org + + How long it takes to fetch the details of the DOM element the user is + selecting for the context menu. On iOS, JavaScript must be run in order to + get the details of the DOM element. If the element is not inside the main + frame, latency could be added due to the communication between frames. Only + logged on iOS. + + + + + + Removed from code as of 5/2019. WARNING: The code emitting this histogram + was broken on desktop, and logged many items that should not have been + logged at all into bucket 0. The values for bucket 0 are wrong and should + not be relied upon. The replacements are ContextMenu.SelectedOptionDesktop, + ContextMenu.SelectedOptionAndroid, and ContextMenu.SelectedOptionIOS. + + lzbylut@google.com + + The option that the user selected from a context menu. This mis-logged and + thus was removed. + + + + + + Removed 06/2019. iFrame Context Menu feature shipped. + + michaeldo@chromium.org + + Logged when an unexpected FindElementResultHandler message was received by + the application. An unexpected message may be sent by a malicious frame. + Only logged on iOS. + + + + + + This feature was deprecated in M74 + + twellington@chromium.org + + Android: Whether contextual suggestions are enabled. Recorded when the + enabled state changes. Note that this may be recorded multiple times per + session. + + + + + + This feature was deprecated in M74 + + donnd@chromium.org + fgorski@chromium.org + twellington@chromium.org + + Records each event handled by the Contextual Suggestions backend. Recorded + when the event is sent to the backend, typically when a UI or network action + is registered. Implemented for Android. + + + + + + This feature was deprecated in M74 + + pnoland@chromium.org + + Android: The net::Error status code of contextual suggestion fetches. + Recorded when a fetch completes. + + + + + + This feature was deprecated in M74 + + pnoland@chromium.org + fgorski@chromium.org + + Android: the amount of time taken elapsed between a contextual suggestion + fetch starting and ending. Recorded when a fetch is completed. + + + + + + This feature was deprecated in M74 + + pnoland@chromium.org + + Android: The size of the serialized and base64-encoded proto sent to the + server when fetching contextual suggestions. Recorded when a fetch is + + + + + + This feature was deprecated in M74 + + pnoland@chromium.org + + Android: The http status code of contextual suggestion fetches. Recorded + when a fetch completes. + + + + + + This feature was deprecated in M75 + + pnoland@chromium.org + + Android: The number of bytes in the response received when a contextual + suggestions fetch completes. Recorded when the response is received. + + + + + + This feature was deprecated in M74 + + pnoland@chromium.org + + Android: The size of the response body received when a contextual + suggestions fetch completes. Recorded when the response is received. + + + + + + This feature was deprecated in M74 + + fgorski@chromium.org + wylieb@chromium.org + + Android: The length of a visit on a page. Reported for HTTP and HTTPS pages + provided there was something visible printed to the screen. Selecting a tab + or loading a new URL in current tab starts timing a visit. Switching to a + different tab, closing the tab or loading a new URL finishes timing and + reports the time if the page did a visually non-empty paint or finished + loading. Bucketed by short/medium/long. + + + + + + This feature was deprecated in M74 + + fgorski@chromium.org + wylieb@chromium.org + + Android: The length of a visit on a page. Reported for HTTP and HTTPS pages + provided there was something visible printed to the screen. Selecting a tab + or loading a new URL in current tab starts timing a visit. Switching to a + different tab, closing the tab or loading a new URL finishes timing and + reports the time if the page did a visually non-empty paint or finished + loading. + + + + + + This feature was deprecated in M74 + + twellington@chromium.org + + Android: Whether the user preference for contextual suggestions is enabled. + Recorded on cold start and when the user has changed the preference state. + Note that this may be recorded multiple times per session. + + + + + + Removed 01/2019, no longer needed + + twellington@chromium.org + + Android: Whether the contextual suggestions results are returned to the + UI-layer while the user is in overview mode. + + + + + + This feature was deprecated in M74 + + twellington@chromium.org + + Android: The position of the clicked contextual suggestion card within its + cluster. + + + + + + This feature was deprecated in M74 + + twellington@chromium.org + + Android: The position of the clicked contextual suggestion card within the + entire list of suggestions. + + + + + + Removed 2015-08-17 as part of cookie histogram cleanup + (https://crbug.com/521135). + + Please list the metric's owners. Add more owner tags as needed. + Intervals between access time updates for each cookie. + + + + + Removed 2019-10-23 as part of cookie histogram cleanup + (https://crbug.com/993120). + + mkwst@chromium.org + + Record when at attempt is made to delete an equivalent cookie on a set + cookie operation and when such a cookie is found and deleted. Also measure + when strict secure cookie rules affect this outcome and prevent a cookie + from being deleted. + + + + + + Removed 2017-07-14 as it demonstrated that making cookie parsing rules + stricter was not feasible. See https://crbug.com/638117. + + ricea@chromium.org + + Indicates whether a cookie initialised from a Set-Cookie header value was + valid or not. This is only logged after cookies containing control + characters have already been rejected, so "Invalid" here means + that the cookie contains quotes, commas, backslashes or top-bit-set + characters. + + + + + + Removed as of March 9, 2020. + + dmikurube@chromium.org + + The size, on disk, of the cookie database as it is being loaded. + + + + + + Removed Jul 2017 for lack of use. + + nharper@chromium.org + + For each cookie removed from the store, the reason it was removed. + + + + + + Removed 2015-08-17 as part of cookie histogram cleanup + (https://crbug.com/521135). + + Please list the metric's owners. Add more owner tags as needed. + + For each domain, number of cookies in that domain (recorded every 10 minutes + of active browsing time). + + + + + + Removed 2015-08-17 as part of cookie histogram cleanup + (https://crbug.com/521135). + + Please list the metric's owners. Add more owner tags as needed. + + For every top level domain, number of subdomains in that top level domain + (recorded every 10 minutes of active browsing time). + + + + + + Removed 2015-08-17 as part of cookie histogram cleanup + (https://crbug.com/521135). + + Please list the metric's owners. Add more owner tags as needed. + + For every top level domain, number of cookies in that domain (recorded every + 10 minutes of active browsing time). + + + + + + Removed Jul 2017 for lack of use. + + nharper@chromium.org + + For each evicted (not expired) cookie, the amount of time since it was last + used + + + + + + Removed Feb 2019 as further data collection is no longer necessary. + + rockot@google.com + + The length of time between when the network stack receives a request for a + cookie list and when it actually responds to the request or abandons it (for + e.g. a closed renderer). + + + + + + Removed June 2020. No longer needed because results are expected to be + stable. + + chlily@chromium.org + morlovich@chromium.org + + The age in milliseconds of a cookie that activates the Lax-allow-unsafe + intervention. Emitted whenever a cookie is included in a request with an + unsafe HTTP method, where the cookie has an unspecified SameSite attribute + and is only included because it is new enough to fall under the age + threshold for allowing Lax-allow-unsafe. + + + + + + Removed 2019-10-31 as part of cookie histogram cleanup + (https://crbug.com/993120). + + tnagel@chromium.org + + Degree of protection against cookie theft. Recorded for each cookie when + setting the `Cookie` header for a request. + + + + + + Removed 2019-07-03. Cookie.Count measures similar things with different + timing. + + morlovich@chromium.org + + This histogram records the total number of cookies loaded from disk, + including any cookies that are discarded during loading (for whatever + reason). + + + + + + Removed as of 9/2013. Experiment to measure control characters in cookies is + finished. + + Please list the metric's owners. Add more owner tags as needed. + + When parsing a cookie, indicates if control characters were present in any + of the cookie values and if any of the cookie values were invalid. + Specifically, checks that all of the parsed values are valid according to + the valid token definition in Section 2.2 of RFC2616 which specifies a token + must have no separators (i.e. no characters from the following string, + ignoring the starting and ending single quote: '()<>@,;:\"/[]?={} + \t') and no control characters. + + + + + + Removed as of 8/2015. + + huangs@chromium.org + + The duration in seconds between a cookie getting evicted (due to the number + of cookies exceeding a domain limit), and subsequently reinstated. + + + + + + Removed Apr 2020 as this metric doesn't capture the correct information. + https://crbug.com/1066231 + + bingler@chromium.org + kaustubhag@chromium.org + + The value of the SameSiteCookieContext if a Lax or Strict cookie is being + sent http-to-https or https-to-http for the site-for-cookies to the request. + Logged once per cookie sent with the above conditions. + + + + + + Removed Apr 2020 as this metric doesn't capture the correct information. + https://crbug.com/1066231 + + bingler@chromium.org + kaustubhag@chromium.org + + The value of the SameSiteCookieContext if a Lax or Strict cookie is being + set http-to-https or https-to-http for the site-for-cookies from the + response. Logged once per cookie sent with the above conditions. + + + + + + Removed June 2020. No longer needed because results are expected to be + stable. + + chlily@chromium.org + morlovich@chromium.org + + The age in milliseconds of a cookie that would have activated the + Lax-allow-unsafe intervention except for the fact that it is too old. + Emitted whenever a cookie is excluded from being sent on a request with an + unsafe method, where the cookie has an unspecified SameSite attribute and is + too old to fall under the age threshold to allow Lax-allow-unsafe. + + + + + + Removed as of 9/2013. Experiment to measure control characters in cookies is + finished. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates whether a cookie attribute pair was set with both a valid key and + a valid attribute value or not. For the key, this implies that it was a + valid token as defined in Section 2.2 of RFC2616 which specifies a token + must have no separators (i.e. no characters from the following string, + ignoring the starting and ending single quote: '()<>@,;:\"/[]?={} + \t') and no control characters. For the value, this implies that it + contained no control characters and no semicolon. + + + + + + Removed as of 9/2013. Experiment to measure control characters in cookies is + finished. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates whether a cookie name was set with a valid token. A valid token is + defined in Section 2.2 of RFC2616 which specifies a token must have no + separators (i.e. no characters from the following string, ignoring the + starting and ending single quote: '()<>@,;:\"/[]?={} \t') and no + control characters. + + + + + + Removed as of 9/2013. Experiment to measure control characters in cookies is + finished. + + Please list the metric's owners. Add more owner tags as needed. + + Indicates whether a cookie value was valid or invalid when there was an + attempt to set it, where a valid value is defined in RFC 6265 as ASCII + characters excluding controls, whitspace, comma, semicolon, and backslash. + + + + + + Removed as of 9/2015. The associated experiment was flawed. + + erikchen@chromium.org + + The number of session cookies deleted on shutdown. This metric is emitted + even if no cookies are deleted. + + + + + + Removed as of 9/2015. The associated experiment was flawed. + + erikchen@chromium.org + + The amount of time required to delete session cookies on shutdown. This + metric is emitted even if no cookies are deleted. + + + + + + Removed as of 04/2015. The migration has finished for most users. + + The amount of time (ms) to migrate a v4 database to v5. + + + + + Removed as of 04/2015. The migration has finished for most users. + + The amount of time (ms) to migrate a v5 database to v6. + + + + + Removed as of 04/2015. The migration has finished for most users. + + The amount of time (ms) to migrate a v6 database to v7. + + + + + Removed as of 04/2015. The migration has finished for most users. + + The amount of time (ms) to migrate a v7 database to v8. + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time (ms) to get cookies for each URL request. + + + + + + Removed as part of histogram expiry. See discussion in crbug.com/975202. + + nyquist@chromium.org + + The amount of time (ms) to read and parse the domain map from the cookies + database. + + + + + + Removed as part of histogram expiry. See discussion in crbug.com/975202. + + nyquist@chromium.org + + The amount of time (ms) to read the domain map from the cookies database. + + + + + + Removed as part of histogram expiry. See discussion in crbug.com/975202. + + nyquist@chromium.org + + The amount of time (ms) to parse the domains already loaded from the cookies + database and put them in the domain map. + + + + + + Removed 2019-10-31 as part of cookie histogram cleanup + (https://crbug.com/993120). + + mkwst@chromium.org + tnagel@chromium.org + + Records the age (in days) of {Age} cookie delivered along with a request. + Recorded when setting the `Cookie` header for a given request. + {CookieConnectionType} {CookieSiteAffinity} + + + + + + + + + + + + + + + + + + Removed as of 04/2016 as CrashPad does not implement this. + + siggi@chromium.org + + Reports the result of an attempt to report a crash dump via Breakpad. + Success indicates only that the out-of-process crash reporter succesfully + generated a dump. The success or failure of the eventual upload is not + measured. This stability metric is logged from the first Chrome launch + post-dump. + + + + + + Removed as of 04/2016 as CrashPad does not implement this. + + siggi@chromium.org + + Reports the result of an attempt to report a dump via Breakpad without + crashing. Success indicates only that the out-of-process crash reporter + succesfully generated a dump. The success or failure of the eventual upload + is not measured. This stability metric is logged from the first Chrome + launch post-dump. + + + + + + Removed as of 03/2018 when Chrome for iOS stopped uploading crash dumps in + the background. + + olivierrobin@chromium.org + pkl@chromium.org + + Time delta between when the crash took place and when the crash was uploaded + by the app as a background task. Only logged on iOS. + + + + + + 07/2020: Investigation complete. + + iby@chromium.org + cros-telemetry@google.com + + Which crash handler (Breakpad or Crashpad) is handling + ProducerClient::InitSharedMemoryIfNeeded()'s attempt to do a + DumpWithoutCrashing. Investigating why Breakpad never seems to generate + InitSharedMemoryIfNeeded reports on some ChromeOS devices. + + + + + + 06/2020: Removed in favor of + CrashReport.DumpWithoutCrashingResult.FromInitSharedMemoryIfNeeded2. + + iby@chromium.org + cros-telemetry@google.com + + Did the attempt to dump without crashing in + ProducerClient::InitSharedMemoryIfNeeded() succeed or fail? Investigating + why Breakpad never seems to generate InitSharedMemoryIfNeeded reports on + some ChromeOS devices. + + + + + + 07/2020: Investigation complete. + + iby@chromium.org + cros-telemetry@google.com + + Did the attempt to dump without crashing in + ProducerClient::InitSharedMemoryIfNeeded() succeed or fail? Investigating + why Breakpad never seems to generate InitSharedMemoryIfNeeded reports on + some ChromeOS devices. + + + + + + Removed as of 03/2018 when Chrome for iOS stopped uploading crash dumps in + the background. + + olivierrobin@chromium.org + pkl@chromium.org + + The number of crash reports present when the app wakes up as a background + task to upload crash reports. Only logged on iOS. + + + + + + Removed 01/2017 in Issue 680162 with the removal of Kasko. + + siggi@chromium.org + + Counts crash reports that the Kasko crash reporter fails to upload and hands + off to Chrome. Kasko stores the failed reports in a location specified by + Chrome. Chrome records this metric when it detects new minidump files in + that location. Currently the reports are discarded, but they could + eventually be uploaded via the Chrome network stack. + + + + + + Removed as of 12/2013. Default pinned apps trial is finished. + + Please list the metric's owners. Add more owner tags as needed. + Chrome OS shelf clicks. + + + + + Removed 10/2019 because it was never used. + + sidereal@google.com + nverne@chromium.org + + The maximum space allowed for a VM disk image, as set at install time. This + is recorded each time a disk image is successfully created. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval needed for the + device activity getter. Recorded when the async callback is invoked or when + the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval needed + for the device activity getter. Recorded when the async callback is invoked + or when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the ClientAppMetadataFetch during the + CryptAuth v2 DeviceSync flow. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval for the + CryptAuth device notifier. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval for the + CryptAuth device notifier. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2020-01-02 because metric was never used. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ShareGroupPrivateKey API call during + the CryptAuth v2 DeviceSync flow. Recorded when the async callback is + invoked or when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval for the + CryptAuth feature status setter. Recorded when the async callback is invoked + or when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval for the + CryptAuth feature status setter. Recorded when the async callback is invoked + or when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async ClientAppMetadata retrieval during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2019-12-11 in favor of + CryptAuth.EnrollmentV2.GcmRegistration.Success because the timeout was + removed. + + nohle@chromium.org + better-together-dev@google.com + + Records the result of the async GCM registration call during the CryptAuth + v2 Enrollment flow. Recorded when the async callback is invoked or when the + call times out. + + + + + + Removed 2019-09-12 in favor of + CryptAuth.EnrollmentV2.ExecutionTime.ClientAppMetadataFetch2 because too + many results were reaching the max time limit. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval during + the CryptAuth v2 Enrollment flow. Recorded when the async callback is + invoked or when the call times out. + + + + + + Removed 2020-07-29. ClientAppMetadata now fetched in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async ClientAppMetadata retrieval during + the CryptAuth v2 Enrollment flow. Recorded when the async callback is + invoked or when the call times out. + + + + + + Removed 2019-12-11 in favor of + CryptAuth.EnrollmentV2.GcmRegistration.AttemptTime because too many results + were reaching the max time limit. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async GCM registration call during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked or + when the call times out. + + + + + + Removed 2020-07-29. GCM registration now occurs in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the execution time of the async GCM registration call during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked. + + + + + + Removed 2020-07-29. GCM registration now occurs in DeviceSync service. + + nohle@chromium.org + better-together-dev@google.com + + Records the success or failure of the async GCM registration call during the + CryptAuth v2 Enrollment flow. Recorded when the async callback is invoked. + + + + + + Removed 05/2018 in favor of Cryptohome.GCache.FreedDiskSpaceInMb. Reports + zero in 99% of hits. + + oka@chromium.org + + The amount of drive cache (MB) which was evicted by cryptohome due to + shortage of remaining disk space. + + + + + + Replaced by Cryptohome.FreeDiskSpaceTotalTime2 in M81. + + slangley@chromium.org + weifangsun@chromium.org + + Being replaced by Cryptohome.FreeDiskSpaceTotalTime2 + + In low disk space scenarios, Cryptohome performs a lot of disk space + operations to erase data. This is a number of milliseconds taken to perform + a cleanup. Reported only if longer than 5 ms. + + + + + + Retired in M81. + + vsavu@google.com + igorcov@chromium.org + + Records the result of using the install_attributes.pb cache. This is logged + at each device boot. + + + + + + Retired in M81. + + vsavu@google.com + igorcov@chromium.org + + Records the result of validating install_attributes.pb. This is logged at + each device boot. + + + + + + Removed 07/2019 as it is not used since crrev.com/c/1393048 + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home + directory asynchronously. + + + + + + Removed 06/2020 as it is not used since crrev.com/c/1183895 (8/2018). + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome to mount the encrypted + guest home directory synchronously. + + + + + + Removed 06/2020 as it hasn't been reported since around crrev.com/185598 + (~2014) and has been completely removed in crrev.com/c/1183895 (6/2020). + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home + directory synchronously. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Time to create an activity delegate for a custom tabs dynamic module. + Android only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Time to create the package context for a custom tabs dynamic module. Android + only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Possible reasons for destroying a custom tabs dynamic module. Android only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + amalova@chromium.org + + Time to initialize the entry point class for a custom tabs dynamic module. + Android only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Time to load the entry point class for a custom tabs dynamic module. Android + only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Time to instantiate the entry point class for a custom tabs dynamic module. + Android only. + + + + + + Removed in February 2020 + + mvanouwerkerk@chromium.org + + Possible results when loading a custom tabs dynamic module. Android only. + + + + + + Removed in October 2019 + + msalama@google.com + lizeb@chromium.org + mvanouwerkerk@chromium.org + + The proportional set size (PSS) of code pages occupied by a custom tabs + dynamic module. Recorded before the module destruction. Android only. + + + + + + Removed in October 2019 + + msalama@google.com + lizeb@chromium.org + mvanouwerkerk@chromium.org + + The proportional set size (PSS) of code pages occupied by a custom tabs + dynamic module. Recorded when a module is loaded. Android only. + + + + + + Removed in October 2019 + + msalama@google.com + lizeb@chromium.org + mvanouwerkerk@chromium.org + + The resident set size (RSS) of code pages occupied by a custom tabs dynamic + module. Recorded before the module destruction. Android only. + + + + + + Removed in October 2019 + + msalama@google.com + lizeb@chromium.org + mvanouwerkerk@chromium.org + + The resident set size (RSS) of code pages occupied by a custom tabs dynamic + module. Recorded when a module is loaded. Android only. + + + + + + Finished experiment and replaced by CustomTabs.Visible in September 2020 + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Experimental version of CustomTabs.Visible that is logged on a log start, + rather than log end, to check if this results in more logs being tagged. + Starting with M84 this is is also recorded for webapps/WebAPKs. Filter the + platform for just CCT/TWA data. + + + + + + Removed 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*. + + lizeb@chromium.org + + Time between the intent arrival in Chrome and the first navigation commit, + if the navigation is successful. Similar in principle to + Startup.FirstCommitNavigationTime. + + + + + + Removed 2017-08 in favor of CustomTabs.IntentToFirstNavigationStartTime. + + lizeb@chromium.org + + Time between the intent arrival to a Custom Tab and the navigation start + (note: not the navigation commit, as the name suggests). Recorded when the + page has finished loading. Non-"Herb" mode. + + + + + + Removed 4/2018 when prerender was removed from Custom Tabs. + + lizeb@chromium.org + + Android: When there is a prerender for a session with non-default + parameters, whether the prerender was matched when navigating. + + + + + + Removed 4/2018 when prerender was removed from Custom Tabs. + + lizeb@chromium.org + + Android: When prerendering a URL for Custom Tabs, whether the client session + uses the default parameters. + + + + + + Replaced by CustomTabs.SpareWebContents.Status2 as of 03/2019. + + lizeb@chromium.org + + Android: When a spare WebContents is created from Custom Tabs, record + creation, and whether it was used, killed or destroyed. Creation is recorded + to get the "abandoned" case, that is when Chrome is killed before + the renderer. + + + + + + Replaced by DataReductionProxy.LoFi.Accuracy. + + bengr@chromium.org + tbansal@chromium.org + + Counts the accuracy of estimated network quality when using Lo-Fi. Counters + are incremented when a main frame URL request is handled by Data Reduction + Proxy and session was in Auto Lo-Fi enabled field trial. + + + + + + Removed as of 8/2017, per server-directed preview decision. + + tbansal@chromium.org + + Counts the changes in the state of Lo-Fi request header (q=low) being added + to the Chrome proxy request header. Counters are incremented when a main + frame URL request is handled by Data Reduction Proxy and session was in Auto + Lo-Fi enabled field trial. + + + + + + Obsoleted April 2020. + + bengr@chromium.org + marq@chromium.org + tbansal@chromium.org + + Counts various events that trigger Chrome to block the fallback + configuration of the data reduction proxy. + + + + + + Obsoleted April 2020. + + bengr@chromium.org + marq@chromium.org + tbansal@chromium.org + + Counts various events that trigger Chrome to block the primary configuration + of the data reduction proxy. + + + + + + Removed as of 6/2014, replaced by DataReductionProxy.BypassTypeFallback. + + bengr@chromium.org + marq@chromium.org + + Counts various events that trigger Chrome to bypass the fallback + configuration of the data reduction proxy. + + + + + + Removed as of 6/2014, replaced by DataReductionProxy.BypassTypePrimary. + + bengr@chromium.org + marq@chromium.org + + Counts various events that trigger Chrome to bypass the primary + configuration of the data reduction proxy. + + + + + + Removed as of March 2020. + + bengr@chromium.org + + Positive net error code that caused the fallback data reduction proxy to be + bypassed and put on the proxy retry list. Called after a failure to connect + or resolve a host name. + + + + + + Removed as of March 2020. + + bengr@chromium.org + + Positive net error code that caused the primary data reduction proxy to be + bypassed and put on the proxy retry list. Called after a failure to connect + or resolve a host name. + + + + + + Obsoleted April 2020. + + bengr@chromium.org + marq@chromium.org + tbansal@chromium.org + + Counts various events that trigger Chrome to bypass the fallback + configuration of the data reduction proxy. + + + + + + Obsoleted April 2020. + + bengr@chromium.org + marq@chromium.org + tbansal@chromium.org + + Counts various events that trigger Chrome to bypass the primary + configuration of the data reduction proxy. + + + + + + Removed 2018/04. + + tbansal@chromium.org + bengr@chromium.org + + Records if the platform detected that a captive portal is present on the + current network. Recorded at the time of Chrome startup and on IP change + event. Recorded only for users that have data saver enabled. + + + + + + Removed in Feb. 2016 + + bengr@chromium.org + + Size of the response body. This is the actual number of bytes received, + which usually agrees with but is not necessarily the same as the size + specified by the Content-Length header. Only recorded if the request is sent + while a simulated Data Reduction Proxy configuration fetch is taking place. + + + + + + Removed in Feb. 2016 + + bengr@chromium.org + + The difference between the size specified in the X-Original-Content-Length + header and the size of the response body. Only recorded if the request is + sent while a simulated Data Reduction Proxy configuration fetch is taking + place. Only positive values are logged, so if X-Original-Content-Length is + not specified or if it equals or exceeds the content length, it is not + logged. + + + + + + Removed in Feb. 2016 + + bengr@chromium.org + + Size specified in the X-Original-Content-Length header. If this header is + not present in the response, the size of the response body is used. Only + recorded if the request is sent while a simulated Data Reduction Proxy + configuration fetch is taking place. + + + + + + Obsoleted March 2020. + + robertogden@chromium.org + tbansal@chromium.org + + On receiving an authentication failure from the data reduction proxy, + records whether the session key used in the request matches the current + session key. + + Recorded every time Chrome receives an authentication failure from the data + saver proxy. + + + + + + Obsoleted March 2020. + + robertogden@chromium.org + tbansal@chromium.org + + Time from when the request starts to the time when the auth failure is + received from the data saver proxy. + + Recorded every time an auth failure is received from the data saver proxy. + + + + + + Removed 2018/04. + + tbansal@chromium.org + bengr@chromium.org + + Records whether the persisted client config for data saver proxies read from + the disk at the time of Chrome startup was expired or not. Recorded once at + the time of Chrome startup. + + + + + + Removed in October 2018 + + robertogden@chromium.org + + Records whether the client config client sent variation headers in the + config request. + + + + + + Obsoleted in M-79. + + tbansal@chromium.org + bengr@chromium.org + + Records the number of days since the data reduction savings were cleared + because the system clock moved back by more than 1 day. Recorded at Chrome + startup if data reduction proxy is enabled, and if the data reduction proxy + savings were cleared in some previous Chrome session. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + For each carrier, the total number of HTTP responses that have been checked + for tampering. This assumes the data reduction proxy injected fingerprints + have not been tampered with. Only the data reduction proxy responses with + 200 OK response code are checked. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + For each carrier, the total number of HTTPS responses that have been checked + for tampering. This assumes the data reduction proxy injected fingerprints + have not been tampered with. Only the data reduction proxy responses with + 200 OK response code are checked. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + For each carrier, the total number of HTTP responses that passed the tamper + detection. This assumes the data reduction proxy injected fingerprints have + not been tampered with. Only the data reduction proxy responses with 200 OK + response code are checked. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + For each carrier, the total number of HTTPs responses that passed the tamper + detection. This assumes the data reduction proxy injected fingerprints have + not been tampered with. Only the data reduction proxy responses with 200 OK + response code are checked. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + The total number of HTTP responses that some part (specified by suffix name) + have been tampered with. This assumes the data reduction proxy injected + fingerprints have not been tampered with. Only the data reduction proxy + responses with 200 OK response code are checked. + + + + + + Removed in June 2017 + + xingx@chromium.org + bolian@chromium.org + bengr@chromium.org + + The total number of HTTPS responses that some part (specified by suffix + name) have been tampered with. This assumes the data reduction proxy + injected fingerprints have not been tampered with. Only the data reduction + proxy responses with 200 OK response code are checked. + + + + + + Obsoleted March 2020. + + tbansal@chromium.org + + Net error codes observed when invalid response headers were received from + data reduction proxy. + + + + + + Removed as of 8/2017, per server-directed preview decision. + + bengr@chromium.org + tbansal@chromium.org + + Records the accuracy of estimated network quality when using Lo-Fi. Network + quality predicted at the time of navigation start is compared with the + network quality observed during the specified time interval following the + start of the navigation. This metric is recorded only when the session is in + Lo-Fi enabled field trial. + + + + + + Obsolete as of October 2017. + + bengr@chromium.org + megjablon@chromium.org + + Counts of Lo-Fi implicit opt out actions. If the user chooses to "Load + image" for k pages in a session, LoFi is disabled for the remainder of + that session. If Lo-Fi is disabled for j consecutive sessions, Lo-Fi is + disabled for that user until the next implicit opt out epoch, which may be + in a later session, or never. k and j default to 3 and are assigned via the + DataReductionProxyLoFi field trial. + + + + + + Removed as of October 2017 per transition to blacklist. + + bengr@chromium.org + megjablon@chromium.org + + Tracks Lo-Fi usage at the granularity of browser sessions. Counts for each + session if Lo-Fi was used or not. In the case where Lo-Fi was not used, + records if it was because the network quality was always good or because the + user had implicitly opted out. The session where a user permanently opts out + is counted in the Lo-Fi used bucket. + + + + + + Functionality removed in M77. + + bengr@chromium.org + tbansal@chromium.org + + Counts of pageloads that received or requested, but did not receive, various + Lo-Fi lite page transformations. Recorded when a lite page is requested or + received through Data compression proxy. + + + + + + Removed as of 9/2016, replaced by Previews.ContextMenuAction.LoFi. + + bengr@chromium.org + megjablon@chromium.org + + User interactions with the Lo-Fi snackbar and context menu option. These + include: + + Displays and clicks on the "Load images" snackbar. Displays and + clicks on the "Load image" and "Load images"context menu + options. Count of pages where the user has clicked "Load image" at + least once. + + + + + + Removed 2018/04. + + bengr@chromium.org + sclittle@chromium.org + + Counts the response bytes of responses that Chrome expected to come through + a data reduction proxy and have the data reduction proxy via header, but + where the data reduction proxy via header was missing. Note that this does + not include responses that were bypassed. + + + + + + Obsoleted March 2020. + + bengr@chromium.org + sclittle@chromium.org + + Counts the different HTTP response codes of responses that Chrome expected + to come through a data reduction proxy and have the data reduction proxy via + header, but where the data reduction proxy via header was missing. + + + + + + Obsoleted in March 2020. + + bengr@chromium.org + tbansal@chromium.org + + Counts the number of times various events occur when the data reduction + proxy is enabled and the IP address of the client changes. + + + + + + Obsoleted in April 2020 + + tbansal@chromium.org + + Records if the network properties of a network were found in the cache or + not. Recorded every time there is a change in the connection type. + + + + + + Removed in M79. + + ryansturm@chromium.org + + Counts the number of times that pageload metrics were queued to be attempted + or not queued based on the reporting fraction. Recorded once per pageload. + + + + + + Removed in M79. + + ryansturm@chromium.org + + Counts various actions related to crash detection in the pingback client. + This is recorded only when a renderer crash occurs on a Data Reduction Proxy + page load. + + + + + + Removed in M79. + + ryansturm@chromium.org + + Counts the number of times that a batched pingback request succeeded or + failed at being sent to the server. Recorded everytime a pingback request is + attempted. + + + + + + Obsoleted in March 2020. + + bengr@chromium.org + marq@chromium.org + + Counts various outcomes of requesting the data reduction proxy's probe URL. + + + + + + Obsoleted in March 2020. + + bengr@chromium.org + tbansal@chromium.org + + Reports the type of network error when the data reduction proxy probe fails + due to a network error. + + + + + + Removed as of 3/2015, replaced by DataReductionProxy.UIAction. + + bengr@chromium.org + marq@chromium.org + + Samples which method was used by the user to dismiss the proxy promo. This + is sampled when the promo leaves view, with the sampled value depending on + which of four possible controls the user used. + + + + + + Obsolete as of 10/2018. + + dougarnett@chromium.org + + Records the sending of accepted transform headers to the data reduction + proxy and also receiving transforms and policies from the data reduction + proxy. Recorded on a per page request basis and also on a per image resource + request basis for empty-image transforms. Headers for both types of requests + (pages and resources) are recorded here for convenience in viewing in a + single histogram. In general, the separate groups of request/receive buckets + for either page or resource types can be compared. + + + + + + Obsolete as of 10/2018. + + dougarnett@chromium.org + + Records the reason that a page request is not accepting proxy server + transforms. Recorded on a per page request basis. + + + + + + Obsoleted March 2020. + + tbansal@chromium.org + bengr@chromium.org + + Records the scheme of the data reduction proxy server. Recorded for every + request that is fetched successfully through a data reduction proxy server. + + + + + + Removed in 5/2017, since the experiment to use default QUIC alternative + proxy was deprecated. + + tbansal@chromium.org + bengr@chromium.org + + Status of the availability of valid alternative data reduction proxy + servers. This metric is recorded only when data reduction proxy delegate is + queried for the value of the supported alternative proxy server. + + + + + + As of M66 this has been superceded by Net.AlternativeProxyFailed. + + tbansal@chromium.org + + Number of times an alternative QUIC proxy was marked as broken. + + + + + + Obsoleted March 2020. + + tbansal@chromium.org + + Records the result of the attempt to use a data reduction proxy that + supports QUIC. The metric is logged for every request for which the resolved + proxy is a data reduction HTTPS proxy. + + + + + + Removed in 2/2016, since it didn't get recorded for many kinds of error + codes when it should have been recorded, and + Net.HttpRequestCompletionErrorCodes is a good enough replacement when + filtering for clients with the Data Reduction Proxy enabled. + + sclittle@chromium.org + bengr@chromium.org + + Reports the different network errors that requests that try to use the data + reduction proxy are completing with, including OK and ABORTED. + + + + + + Removed in 2/2016, since it didn't get recorded for many kinds of error + codes when it should have been recorded, and + Net.HttpRequestCompletionErrorCodes is a good enough replacement when + filtering for clients with the Data Reduction Proxy enabled. + + sclittle@chromium.org + bengr@chromium.org + + Reports the different network errors that main frame resource requests that + try to use the data reduction proxy are completing with, including OK and + ABORTED. + + + + + + Removed 2018/04. + + tbansal@chromium.org + bengr@chromium.org + + Content type of the resource determined by data reduction proxy. Used for + determining the data reduction proxy that should be used for fetching the + resource. Logged once per resource for only the resources that are eligible + for fetching by data reduction proxies. + + + + + + Obsoleted March 2020. + + sclittle@chromium.org + bengr@chromium.org + + Reports the state of the proxy server field in the response seen by the Data + Reduction Proxy bypass logic. + + + + + + Replaced by DataReductionProxy.SavingsCleared.Reason in M68. + + tbansal@chromium.org + bengr@chromium.org + + Records if the data reduction savings were cleared because the system clock + moved back by more than 1 day. Recorded at Chrome startup if the data + reduction proxy is enabled. + + + + + + Obsoleted in March 2020. + + bengr@chromium.org + + Time from when the Data Reduction Proxy secure proxy check starts until it + completes. + + + + + + Removed as of 3/2015, replaced by DataReductionProxy.UIAction. + + bengr@chromium.org + marq@chromium.org + + Samples of user interactions with the ON/OFF switch in the settings menu for + reducing data usage. Only the setting changes between entering the reducing + data usage setting menu and leaving the menu will be sampled. So if a user + enters the menu with OFF and leaves it with OFF, it is counted as one OFF to + OFF conversion regardless of how many times they toggle the ON/OFF switch. + + + + + + Obsoleted March 2020. + + tbansal@chromium.org + bengr@chromium.org + + Count of the number of requests that were successfully fetched via data + reduction proxy. The bucket represents the index of the data reduction proxy + in the data reduction proxy list. + + + + + + Obsoleted March 2020. + + tbansal@chromium.org + bengr@chromium.org + + Count of the number of main frame requests that were successfully fetched + via data reduction proxy. The bucket represents the index of the data + reduction proxy in the data reduction proxy list. + + + + + + Removed 2018/04. + + tbansal@chromium.org + bengr@chromium.org + + Records the time duration between the data saver initialization and the + first HTTP request that is resolved through the data saver proxy. On IP + address changes, time duration between the IP address change event and the + next subsequent HTTP request that resolves through the data saver proxy is + recorded. + + + + + + Removed March 2018. Percent no longer displayed. + + tbansal@chromium.org + + The percentage of data savings displayed to users. Computed over the last 30 + days. Recorded when the user views the data savings in the UI. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + Records the result of an attempt to fetch the warmup URL. + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Records the total number of warmup URL (i.e., the probe URL) fetch attempts + that were made before the warmup URL was successfully fetched. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Number of times the data reduction proxy warm up URL was fetched. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + Whether the warm up URL was fetched succesfully. + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Whether the response headers of the warm up URL had Chrome Proxy via header. + Recorded only when non-null response headers were available when the fetch + of warm up URL concludes. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + HTTP response code of the warm up URL. Set to 1 when HTTP response headers + were unavailable. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Net error codes observed when the fetch of the warm up URL concludes. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Proxy scheme of the proxy server via which the warm up URL was fetched. + Recorded only when non-null response headers were available when the fetch + of warm up URL concludes. + + + + + + Obsoleted in March 2020. + + tbansal@chromium.org + + Whether the warmup (or probe) URL was successfully fetched over a data saver + proxy. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The number of invalid matching rules fetched from the platform external data + use observer. A sample is recorded everytime fetch done callback is called. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The number of valid matching rules fetched from the platform external data + use observer. A sample is recorded everytime fetch done callback is called. + + + + + + Removed 2018/07. + + rajendrant@chromium.org + bengr@chromium.org + + Records the sequence number of the page load within a data usage tracking + session. Logged for each navigation in the tracking session. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The time taken in milliseconds to fetch the matching rules for the first + time from the platform external data use observer. This measures the + duration from the start time of Chromium to the time the rules are returned + asynchronously. A sample is recorded when the first fetch done callback is + called. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The time taken in milliseconds to submit the data use reports to the + platform external data use observer. This measures the duration from the + time of report submission to the time report submission done asynchronous + callback is received. A sample is recorded everytime report submission done + callback is received. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The time taken in milliseconds for a regular expression to parse an URL. A + sample is recorded evertime regular expression parsing is done for an URL. + + + + + + Removed 2018/07. + + bengr@chromium.org + tbansal@chromium.org + + Count of bytes in the data use reports that were intended to be submitted to + the platform external data use observer. + + + + + + Removed 2018/07. + + bengr@chromium.org + tbansal@chromium.org + Result of data usage report submission. + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The duration from the start time of a tab entry's latest data usage tracking + session, till when the entry is expired and removed from the tab model. This + is for tab entries that are still actively tracking data usage for a + Chromium tab. + + Tab model maintains the tab entries, each pertaining to tracking sessions of + a single Chromium tab. These entries are considered expired after some + duration and can be removed from the tab model after that. The sample is + taken when an expired tab entry still tracking data usage is removed from + the tab model. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The duration from the end time of a tab entry's latest data usage tracking + session, till when the entry is expired and removed from the tab model. This + is for tab entries that are not actively tracking data usage for a Chromium + tab. + + Tab model maintains the tab entries, each pertaining to tracking sessions of + a single Chromium tab. These entries are considered expired after some + duration and can be removed from the tab model after that. The sample is + taken when an expired inactive tab entry is removed from the tab model. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The duration from the end time of a data usage tracking session, till when + the tracking session is removed from the tab model. This is for old tracking + sessions that are not actively tracking data usage. + + Tab model maintains a limited number of tracking sessions per Chromium tab. + When this limit is reached oldest inactive tracking sessions are removed. + The sample is taken when an old inactive tracking session of a tab is + removed from the tab model. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The lifetime of a data usage tracking session of a Chromium tab, maintained + by the tab model. This is the duration between the time tracking started due + to an entry event and ended with an exit event. The sample is taken when the + data usage tracking session ends. + + + + + + Removed 2018/07. + + bengr@chromium.org + rajendrant@chromium.org + + The duration from the end time (start time, if still active) of a tab + entry's latest data usage tracking session, till when the entry is removed + from the tab model. This is for tab entries that are not expired yet, and + removed from the tab model. + + Tab model maintains a limited number of entries, each pertaining to tracking + sessions of a single Chromium tab. When this limit is reached even after + removing expired tab entries, then oldest unexpired tab entries are removed. + The sample is taken when an unexpired tab entry is removed from the tab + model. + + + + + + Removed 2018/07. + + rajendrant@chromium.org + bengr@chromium.org + + The reason for ending the data usage tracking session. Logged when the + tracking session ends. + + + + + + Removed 2018/07. + + rajendrant@chromium.org + bengr@chromium.org + + The reason for starting the data usage tracking session. Logged when the + tracking session was started. + + + + + + Removed 2018/07. + + bengr@chromium.org + megjablon@chromium.org + + Samples of user interactions with the Data Use snackbar and dialog. These + samples include: + + Displays of the snackbar that indicates the start of data use tracking and + clicks on its "More" button. Displays of snackbar that indicates + the end of data use tracking and clicks on its "More" button. + Displays of the dialog that indicates the end of data use tracking and the + user interactions with it, which include: clicking "Continue", + clicking "Cancel", clicking "Learn more", and opting out + of seeing the dialog. If the user opts out of seeing the dialog, they will + see the snackbar that indicates the end of data use tracking from then on. + + + + + + Replaced by KB version in October, 2017. + + rajendrant@chromium.org + bengr@chromium.org + + The total background data use of Chrome's services broken down by service + name. It is logged only in Android when the URLRequest of a service + completes. + + + + + + Replaced by DataUse.AllServicesKB.* version in June, 2018. + + rajendrant@chromium.org + bengr@chromium.org + + The total background data use of Chrome's services broken down by service + name. It is logged only in Android when the URLRequest of a service + completes. + + + + + + Removed 2018/05. Bytes are logged to DataUse.ContentType.ServicesKB. + + rajendrant@chromium.org + bengr@chromium.org + + Data use of Chrome services traffic by different content types. Recorded + when network bytes are received by Chrome. + + + + + + Removed since not needed. + + rajendrant@chromium.org + bengr@chromium.org + + Data use of Chrome services traffic by different content types. Recorded in + KB when network bytes are received by Chrome. + + + + + + Removed 2017/04. Bytes are logged to DataUse.ContentType.UserTrafficKB. + + rajendrant@chromium.org + bengr@chromium.org + + Data use of user traffic by different content types. Recorded when network + bytes are received by Chrome. + + + + + + Removed 10/2017. + + bengr@chromium.org + + The request and response size of the messages exchanged by a service. It is + logged when the URLRequest of a service is completed. The service name is + added as a suffix to this histogram name. + + + + + + Replaced by DataUse.AllServicesKB.* version in June, 2018. + + bengr@chromium.org + + The request and response size of the messages exchanged by all the services. + Whenever a URLRequest of a service is completed, the number of exchanged + bytes is logged in this histogram. The buckets in this histogram are + services, so it makes it possible to compare the use of different services + in different conditions. Different conditions are added as suffixes to this + histogram. If the OS is not Android all the requests are considered + foreground. + + + + + + Removed 2018/05. Bytes are logged to DataUse.PageTransition.UserTrafficKB. + + rajendrant@chromium.org + bengr@chromium.org + + Data use of user traffic by different core page transition types. Recorded + when the URL request finishes. + + + + + + Removed 10/2017. + + bengr@chromium.org + + Number of downloaded bytes of different data types in Sync service for + received updates. It is updated when an update message is received from sync + server. + + + + + + Removed 10/2017. + + bengr@chromium.org + + Number of downloaded entities of different data types in Sync service for + received updates. It is updated when an update message is received from sync + server. + + + + + + Removed 10/2017. + + bengr@chromium.org + + Number of downloaded bytes of ProgressMarker of different data types in Sync + service for received updates. It is updated when an update message is + received from sync server. + + + + + + Removed 10/2017. + + bengr@chromium.org + + Number of uploaded bytes of different data types in Sync service for sent + commits. Updated when a commit message is sent to sync server. + + + + + + Removed 10/2017. + + bengr@chromium.org + + Number of uploaded entities of different data types in Sync service for sent + commits. Updated when a commit message is sent to sync server. + + + + + + Removed in M74 and replaced by DataUse.AllServicesKB. + + bengr@chromium.org + + The total data use of Chrome's services. There is no ResourceRequestInfo + attached to these requests. If the OS is not Android all the requests are + considered foreground. + + + + + + Removed 2015/11. Renamed to DefaultBrowser.SetDefaultAsyncDuration. + + pmonette@chromium.org + + How long it took to set Chrome as the default browser asynchronously in + Windows 10+. The duration is recorded only on Success, Failure, Abandoned + and Retry result codes. + + + + + + Removed 2015/11. Renamed to DefaultBrowser.SetDefaultResult. + + pmonette@chromium.org + + The count of how many times users were successfully able to set Chrome as + the default browser asynchronously in Windows 10+. + + + + + + Removed 2016/03. The async set-as-default experiments are finished. + + pmonette@chromium.org + + How long it took to set Chrome as the default browser asynchronously in + Windows 10+. The duration is recorded only on Success, Failure, Abandoned, + Retry and NoErrorsNotDefault result codes. + + + + + + Removed 2016/03. + + pmonette@chromium.org + + The outcome of an attempt to set Chrome as the user's default browser. + + + + + + Removed 2015/11. The same information is available as the value Failure in + DefaultBrowser.SetDefaultResult. + + gab@chromium.org + + In the make-default infobar, the user explicitly declined to set Chrome as + default. Or, on OSes requiring the SetAsDefaultUI, the user explicitly chose + another browser as default from the interactive UI. TODO(gab): Split the + interactive signal into a separate histogram. + + + + + + Removed 2015/11. Renamed to DefaultBrowser.InfoBar.UserInteraction. + + gab@chromium.org + + The user ignored the make-default infobar (it was eventually dismissed along + with its associated web content without the user interacting with it). + + + + + + Removed 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There is + no longer a distinction between interactive or not. + + gab@chromium.org + + In the make-default infobar, the user clicked a button making Chrome the + default. + + + + + + Removed 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There is + no longer a distinction between interactive or not. + + gab@chromium.org + + Same as SetAsDefault, but in Win8+ (resulting in interactive UI instead of + automatic takeover). Successes == these reports minus reports for + DefaultBrowserWarning.SetAsDefaultUIFailed and some + DefaultBrowserWarning.DontSetAsDefault. TODO(gab): Improve reporting here. + + + + + + Removed 2015/11. The same information is available as the value Failure in + DefaultBrowser.SetDefaultResult. + + gab@chromium.org + + The user dismissed the interactive SetAsDefaultUI without making an explicit + choice (or the UI failed to come up for another reason). + + + + + + Removed 2016/03. + + pmonette@chromium.org + + The outcome of an attempt to set Chrome as the user's default client for a + protocol. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The actual delay added to main frame navigations by DelayNavigationThrottle. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The absolute delta between the specified and actual delays added to main + frame navigations by DelayNavigationThrottle. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The specified delay added to main frame navigations by + DelayNavigationThrottle. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + The dimissal reason of the desktop to iOS promotion entry point. + DismissalReason will be prefixed by the entry point promotion name that the + user interacted with. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + The type of the desktop to iOS promotion that was shown to the user. This + will be logged every time the user sees the desktop to iOS promotion. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + [IOS] For users who sign-in on Chrome for iOS, log the type of the desktop + iOS promotions that was shown to the user. Only recorded if the user has + seen at least one desktop iOS promotion in the last 7 days and is signing + into chrome on iOS. The last promotion entry point that sent an SMS (if any) + is logged as DesktopIOSPromotion.SMSSent.IOSSigninReason; all other + promotions that the user has seen are logged as + DesktopIOSPromotion.NoSMS.IOSSigninReason. + + + + + + Removed 11/2018 in issue 894963. + + justincohen@chromium.org + + Whether getting the OAuth token was successful for a desktop to iOS + promotion query. + + + + + + Removed 11/2018 in issue 894963. + + justincohen@chromium.org + + HTTP Response code returned by the server when trying to fetch the OAuth + token for a desktop ios promotion query. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + Whether the SMS service api called from the desktop to iOS promotion + returned a phone number or failed. This phone number is presented to the + user so they know that Chrome will send the SMS to this number. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + Whether the SMS service api initiated SMS sending successfully from the + desktop to iOS promotion. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + [IOS] The difference between the client time of triggering the SMS action on + a specific entry point promotion on desktop and client time of signing in + Chrome iOS app. This will only be logged if at least one promotion was shown + to the user on the last 7 days and if at least one SMS was sent. If multiple + SMSs were sent (at any time), it uses the time from the most recently sent + one. If the is negative due to bad clock on one of the clients it will be + logged as 0. SMSToSigninTime will be prefixed by the entry point promotion + name that was responsible for the SMS sending. + + + + + + Removed 11/2018 in issue 894963. + + mrefaat@chromium.org + + [IOS] For users who sign-in on Chrome for iOS, log which variation of the + desktop iOS promotions was shown to the user. The variation number is a + unique identifier that is set for each group on the DesktopIOSPromotion + study, and will be only recorded if the user has seen at least one desktop + iOS promotion in the last 7 days and is signing into Chrome on iOS. The last + variation that sent an SMS (if any) is logged as + DesktopIOSPromotion.SMSSent.VariationSigninReason. If no SMS was sent, then + the last variation the user has seen is logged as + DesktopIOSPromotion.NoSMS.VariationSigninReason. + + + + + + Removed 08/2020 because the set of settings has changed. Superseded by + DevTools.CSSGridSettings2. + + yangguo@chromium.org + brgoddar@microsoft.com + leo.lee@microsoft.com + + DevTools settings for CSS grid recorded on launch of the DevTools. + + + + + + Removed in July 2020, M86. This histogram was fired multiple times per + setting change and is unusable. Replaced with DevTools.CSSGridSettings. + + yangguo@chromium.org + brgoddar@microsoft.com + leo.lee@microsoft.com + + Recorded when a DevTools CSS Grid overlay display setting is changed. + Actually fires once for each overlay target active when the setting is + changed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityAppCache recovery + step that runs on recovery startups. The recovery step attempts to guarantee + the SQLiteIntegrityAppCache test, which checks the integrity of the App + Cache database, would pass on the next startup. + + + + + + Removed as of Jun 2014: we no longer have an archived database. + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityArchivedHistory + recovery step that runs on recovery startups. The recovery step attempts to + guarantee the SQLiteIntegrityArchivedHistory test, which checks the + integrity of the Archived History database, would pass on the next startup. + + + + + + Removed 05/2016 in Issue 617226; has not been valid for many years. + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityThumbnails + recovery step that runs on recovery startups. The recovery step attempts to + guarantee the SQLiteIntegrityThumbnails test, which checks the integrity of + the Thumbnails database, would pass on the next startup. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + TBD - Not run automatically yet, so this is just a placeholder for future + metrics collection. Any samples collected here represent users running + diagnostics manually. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityAppCache test that + runs on recovery startups. The test checks the integrity of the App Cache + database. + + + + + + Removed as of Jun 2014: we no longer have an archived database. + + Please list the metric's owners. Add more owner tags as needed. + + Shows the success and failure rates of the SQLiteIntegrityArchivedHistory + test that runs on recovery startups. The test checks the integrity of the + Archived History database. + + + + + + Removed 05/2016 in Issue 617226; has not been valid for many years. + + shess@chromium.org + + Shows the success and failure rates of the SQLiteIntegrityThumbnails test + that runs on recovery startups. The test checks the integrity of the + Thumbnails database. + + + + + + Removed, use Dialog.DialogDelegate.Create. + + pdyson@chromium.org + + Counts the number times dialog boxes are created using DialogDelegate. + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + + Reports size of font cache file. This is reported every time we rebuild font + cache. + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + layout-dev@chromium.org + + Reports the total number of fonts that will be ignored while building static + font cache due to size limitation. During cache building phase if our logic + suggests that we need to put more than 70% of font file contents into cache + file then we don't cache that particular font file. These ignored font files + are directly picked up from system fonts folder during Direct Write cache + building process. Our end goal is to minimize costly open and close + operations on font files in system folder. + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + + Reports the total number of fonts that will be ignored while loading a + custom font collection. With current criteria fonts that are not in + system-font location will be ignored. + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + + Reports the total number of fonts to be loaded through a custom font + collection. This actually reports total font entries from registry excluding + font entries that point to non-system location. + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + + Measures the total time spent in loading a custom font collection in + non-cache-file mode. We load system fonts as a custom font collection to + avoid any interaction with windows font cache service from sandboxed + renderer process. Please note that windows font cache services is different + from our cache file approach (later referred here as cache-file mode). + + + + + + Removed 04/2016, as the code path containing this metric was deprecated in + favor of DWriteFontProxyImpl. + + drott@chromium.org + + Measures the total time spent in loading a custom font collection in + cache-file mode. We load system fonts as a custom font collection to avoid + any interaction with windows font cache service from sandboxed renderer + process. Please note that windows font cache services is different from our + cache file approach (later referred here as cache-file mode) + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Whether an extension has been wiped out. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How many external extensions get wiped out as a result of the Sideload + Wipeout one-time initiative. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Whether any extension got wiped out as a result of the Sideload Wipeout + one-time initiative. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The user selection in the Sideload Wipeout bubble, grouped by the + UmaWipeoutHistogramOptions enum. + + + + + + Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs + are discarded too often. + + fdoray@chromium.org + + Number of tabs that are not pending load or discarded when an urgent discard + request is received. + + + + + + Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs + are discarded too often. + + fdoray@chromium.org + + Time between two consecutive urgent discard requests. Urgent discards are + undesirable; it is better to reduce memory usage before the system is in a + bad state. + + + + + + Removed 08/2019. Use Discarding.ReloadsPer10Minutes to assess whether tabs + are discarded too often. + + fdoray@chromium.org + + Time between Chrome startup and the first urgent discard request. Urgent + discards are undesirable; it is better to reduce memory usage before the + system is in a bad state. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Records information about DiskBasedCertCache operations with respect to + certificate chain positions. Zero indicates that a certificate is root, one + indicates that it is the first intermediate certificate, etc. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Records the outcome of requests to retrieve certificates from the disk + cache. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Whether or not the leaf certificate of a certificate chain was successfuly + read from the disk cache. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Whether or not the leaf certificate of a certificate chain was successfully + written to the disk cache. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Measures the wall clock time spent reading a certificate chain. The starting + time is when the read command is issued, and the ending time is when all of + the certificates in the chain have been read into memory. + + + + + + Removed as of 01/2016. CertCacheTrial has been removed. + https://crbug.com/522312 + + brandonsalmon@chromium.org + + Measures the wall clock time spent writing a certificate chain to disk. The + starting time is when the write command is issued, and the ending time is + when all the certificates in the chain have been written to disk. + + + + + + Removed 2019-07-05 + + morlovich@chromium.org + The age of the cache's files (wall time). + + + + + Removed. See MaxSize2. + + rvargas@chromium.org + The maximum size of the cache. + + + + + Removed. See Size2 + + rvargas@chromium.org + The current size of the cache. + + + + + Removed 2019-07-05 + + morlovich@chromium.org + + The age of the cache's files (wall time). Media-specific cache. + + + + + + Removed. See MaxSize2. + + rvargas@chromium.org + The maximum size of the cache. Media-specific cache. + + + + + Removed. See Size2. + + rvargas@chromium.org + The current size of the cache. Media-specific cache. + + + + + Removed 2019-07-05 + + morlovich@chromium.org + The age of the cache's files (wall time). AppCache. + + + + + Removed. See MaxSize2. + + Please list the metric's owners. Add more owner tags as needed. + The maximum size of the cache. AppCache. + + + + + Removed 2019-07-05 + + morlovich@chromium.org + The age of the cache's files (wall time). ShaderCache. + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + The number of entries currently stored on the cache. + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + + The current hit ratio. It is only measured after the cache is full, so + evictions are taking place, and data from the fill-up period is not + considered. + + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + + Percentage of the cache used by entries of more than 512 KB. It is only + measured after the cache is full, so evictions are taking place. + + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + The maximum size of the cache. + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + The current size of the cache. + + + + + Removed 2019-07-05 + + morlovich@chromium.org + The size distribution of data stored in the HTTP cache. + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + + The total time it takes to perform a payload IO operation, for the regular + disk cache. + + + + + + Removed. + + Please list the metric's owners. Add more owner tags as needed. + + The time that an entry lives in the cache without being accessed until it is + finally purged. + + + + + + Removed after M72 since no longer needed. + + + + sadrul@chromium.org + sunnyps@chromium.org + + The reason for the DisplayScheduler to abort a draw operation. + + + + + + Removed as of 6/2018. + + mgersh@chromium.org + + The attempt which completed after the job was already cancelled. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + The attempt which completed after the job was already cancelled OR the + attempt that has finished after host resolution was already completed by an + earlier attempt. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in OS resolutions for actual navigations. These + attempts which completed after the job was already canceled OR after the job + was already completed by an earlier attempt. Note that cached resolutions + may provide low (0ms?) resolution times. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + The attempt that has not resolved the host successfully. + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + The attempt that resolved the host first and the resolution was not + successful. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + The attempt that resolved the host first and the resolution was successful. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + The attempt that has resolved the host successfully. + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken in OS resolutions that succeeded and were requested + for actual navigations. These attempts which completed after the job was + already canceled OR after the job was already completed by an earlier + attempt. Note that cached resolutions may provide low (0ms?) resolution + times. + + + + + + Removed as of 6/2018. + + mgersh@chromium.org + + This histogram shows the time saved by having spawned an extra attempt, when + the first attempt didn't finish before retry attempt. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The time left to expiration of an entry when it is removed while compacting + the HostCache. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The time since expiration of an entry when it is removed while compacting + the HostCache. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The time since expiration of an entry when it is removed on lookup. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + Error status when an empty address list was found in OnLookupComplete(). + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + The reason for erasing a DNS entry from the host cache. + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When erasing a stale (expired or old-network) DNS entry from the host cache, + how long past the expiration time it is. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When erasing a stale (expired or old-network) DNS entry from the host cache + how many network changes happened between setting and erasing it. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When erasing a stale (expired or old-network) DNS entry from the host cache + how many hits it received while stale. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When erasing a valid DNS entry from the host cache, for how much longer it + would have remained valid. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + The outcome of looking up a DNS entry in the host cache. + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When looking up a stale DNS entry in the host cache, how long past the + expiration time it is. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When looking up a stale DNS entry in the host cache, how many network + changes happened between setting it and looking it up. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + Number of HostCache entries persisted to disk, measured at restore time. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + Whether the persisted HostCache entries were restored successfully. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + The outcome of setting a DNS entry in the host cache. + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When updating a stale (expired or old-network) DNS entry in the host cache, + and both results are successful, how the address list differs between the + old and new entries. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When updating a stale (expired or old-network) DNS entry in the host cache, + how long past the expiration time the old entry was. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + When updating a stale (expired or old-nework) DNS entry in the host cache, + how many network changes happened between setting the old entry and setting + the new entry. + + + + + + Removed as of 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + The number of hits received to an updated stale DNS entry in the host cache + while it was stale. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + When either a pre-resolution was not done recently enough to provide + benefit, or the corresponding pre-resolution is still pending, this + histogram shows the duration of time used to resolve a hostname as not + existing during a failed attempt to navigate to (GET) a URL. In newer + versions, if the hostname has never been found as a link during a page scan, + and it has a referring URL, then it is added to referrer list data structure + (hoping we'll do better next time). + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + When either a pre-resolution was not done recently enough to provide + benefit, or the corresponding pre-resolution is still pending, this + histogram shows the duration of the duration of time used to resolve a + hostname to navigate to (GET) a URL. In newer versions, if the hostname has + never been found as a link during a page scan, and it has a referring URL, + then it is added to referrer list data structure (hoping we'll do better + next time). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). Includes only Jobs which had priority HIGHEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). Includes only Jobs which had priority IDLE when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). Includes only Jobs which had priority LOW when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). Includes only Jobs which had priority LOWEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTime. + + mgersh@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started (a getaddrinfo call was dispatched to the thread + pool). Includes only Jobs which had priority MEDIUM when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). Includes + only Jobs which had priority HIGHEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). Includes + only Jobs which had priority IDLE when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). Includes + only Jobs which had priority LOW when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). Includes + only Jobs which had priority LOWEST when started. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange. + + mgersh@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started (a getaddrinfo call was dispatched to the thread pool). Includes + only Jobs which had priority MEDIUM when started. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time used (most recently) to pre-resolve a hostname, when + the prefetched resolution was apparently evicted from the cache. The + included samples only list pre-resolution times when the later + navigations/fetches took in excess of 15ms. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time used (most recently) to pre-resolve a hostname, when + the prefetched resolution was apparently evicted from the cache. The + included samples only list pre-resolution times when the later + navigations/fetches took in excess of 15ms. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + Replaced by DNS.PrefetchFoundNameL. + + + + + Removed 2/2010, and replaced by DNS.PrefetchResolution + + mgersh@chromium.org + + The duration of time used by the DNS pre-resolving threads to resolve a host + name via the network. Any resolutions that are faster than 15ms are + considered to be local cache hits, not requiring network access, and are not + included in this histogram. This histogram is most useful for estimating the + typical cost of a name resolution, but it also estimates the total number of + network-based resolutions induced by this feature. Not all these resolutions + prove helpful (i.e., the user does not always actually visit the resolved + hostnames). + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + Replaced by DNS.PrefetchNegativeHitL. + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time saved due to DNS pre-resolving in the "name not + found" case. Time "savings" shown in the histogram are + defined to be the difference between the DNS pre-resolution duration, and + the DNS resolution duration seen during a navigation. These cache hits only + list events where the DNS pre-resolve duration for a host was in excess of + 15ms (i.e., the network was consulted), and the actual DNS resolution (when + a user attempted to navigate to a link with the same host name) took less + than 15ms (i.e., the network was not consulted), which means the gain was a + result of a "cache hit" in the OS cache. For some users with LANs, + all negative results (even when the DNS cache might otherwise help) take + about 2.5 seconds (due to timeouts for netbios broadcasts), and hence no + savings are possible (or shown) for such users in this category. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + Replaced by DNS.PrefetchPositiveHitL. + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time saved due to DNS pre-resolving in the "name was + found" case, and induced by either a page scan for a link or an omnibox + entry by the user. Time "savings" shown in the histogram are + defined to be the difference between the DNS pre-resolution duration, and + the DNS resolution duration seen during a navigation. These cache hits only + list events where the DNS pre-resolve duration for a host was in excess of + 15ms (i.e., the network was consulted), and the actual DNS resolution (when + a user attempted to navigate to a link with the same host name) took less + than 15ms (i.e., the network was not consulted), which means the gain was a + result of a "cache hit" in the OS cache. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time spent by a proposed resolution waiting in the queue to + be resolved. This number is in addition to any DNS resolution time that may + come later. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + The duration of time saved due to DNS pre-resolving in the "name was + found" case, and induced by predicting (using referrer lists) that a + resolution was needed. Time "savings" shown in the histogram are + defined to be the difference between the DNS pre-resolution duration, and + the DNS resolution duration seen during a navigation. These cache hits only + list events where the DNS pre-resolve duration for a host was in excess of + 15ms (i.e., the network was consulted), and the actual DNS resolution (when + a user attempted to navigate to a link with the same host name) took less + than 15ms (i.e., the network was not consulted), which means the gain was a + result of a "cache hit" in the OS cache. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + When, due to congestion avoidance, a queued pre-resolution is abandoned + (recycled) without actually being resolved, this histograms records the age + in the queue of that entry. Only times over 2 seconds are recorded in this + histogram. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + When, due to congestion avoidance, a queued pre-resolution is abandoned + (recycled) without actually being resolved, this histograms records the age + in the queue of that entry. Only times less than or equal to 2 seconds are + recorded in this histogram. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ResolveCategory. + + mgersh@chromium.org + + Counts of successes and failures of OS resolutions in various categories. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. + + mgersh@chromium.org + + Duration of time taken in OS resolutions for actual navigations. Note that + cached OS resolutions may provide low (0ms?) resolution times. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. + + mgersh@chromium.org + Same as DNS.ResolveFail, but limited to pure IPv4 lookups. + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. + + mgersh@chromium.org + Same as DNS.ResolveFail, but limited to pure IPv6 lookups. + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. + + mgersh@chromium.org + Same as DNS.ResolveFail, but limited to IPv4/IPv6 lookups. + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskFail. + + mgersh@chromium.org + + Duration of time taken in speculative OS resolutions. Note that cached OS + resolutions may provide low (0ms?) resolution times. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. + + mgersh@chromium.org + + Duration of time taken in speculative OS resolution that succeeded. Note + that cached resolutions may provide low (0ms?) resolution times. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. + + mgersh@chromium.org + + Duration of time taken in OS resolutions that succeeded and were requested + for actual navigations. Note that cached resolutions may provide low (0ms?) + resolution times. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. + + mgersh@chromium.org + + Same as DNS.ResolveSuccess, but limited to pure IPv4 lookups. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. + + mgersh@chromium.org + + Same as DNS.ResolveSuccess, but limited to pure IPv6 lookups. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess. + + mgersh@chromium.org + + Same as DNS.ResolveSuccess, but limited to IPv4/IPv6 lookups. + + + + + + Removed as of 5/2013. + + mgersh@chromium.org + + Counts of hits and misses in the DNS cache and DNS jobs pool of wasted + HostResolverImpl::Jobs that could be avoided by always resolving using + AF_UNSPEC. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver returns, a stale cached + result was available, and the network responded before or exactly at the + stale delay, how much earlier it responded. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver returns, a stale cached + result was available, and the network responded after the stale delay, how + much later it responded. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver returns or is canceled, + the outcome of the request. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver has no stale cached result + available, the number of host cache entries that were restored from prefs. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver has no stale cached result + available, the number of entries in the host cache. + + + + + + Removed 2020-06 + + pauljensen@chromium.org + mef@chromium.org + + When a DNS request made through StaleHostResolver had a stale cached result + and both the stale and network results were successful, the difference + between the old and new address lists. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.TotalTime. + + mgersh@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Excludes speculative requests. + + + + + + Removed as of 9/2017. Replaced by Net.DNS.TotalTime_speculative. + + mgersh@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Speculative requests only. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + In some cases, such as when content arrives with embedded references to + other servers, the prefetch system can't (or doesn't) attempt to pre-resolve + the hostnames. As an example, a visit to www.cnn.com will fetch content with + references to about 12 additional hostnames, none of which are currently + anticipated. Such resolutions are termed "Unexpected Resolutions," + and the durations associated with those DNS resolutions are shown below. + Future features may attempt to learn (from prior experience locally, or from + server provided hints), what secondary hostname resolutions should be done + when a primary resolution (or navigation) takes place. This histogram shows + what the potential savings are that "remain on the table" until we + employ some of these more advanced features. + + + + + + Removed as of 9/2017. + + mgersh@chromium.org + + In some cases, such as when content arrives with embedded references to + other servers, or when a page (such as one in SSL) preclude scanning and + prefetching, the prefetch system can't (or doesn't) attempt to pre-resolve + the hostnames. As an example, a visit to www.cnn.com will fetch content with + references to about 12 additional hostnames, none of which might be + anticipated. Similarly, clicking on a link in an SSL page won't be + anticipated (since scanning in not allowed by default). Such resolutions are + termed "Unexpected Resolutions," and the durations associated with + those navigation induced DNS resolutions are shown below. If a referring URL + is available for the navigation, the relationship to the referring URL was + recorded, and future navigations to the referring hostname would have + induced a pre-resolution of hostname that caused an entry below. Such any + entry may facilitate future listing in the ReferredPositiveHit histogram. + + + + + + Renamed 7/2013 to DnsProbe.ProbeDuration. + + mgersh@chromium.org + Time between starting and finishing DNS probe. + + + + + Removed 7/2013. + + mgersh@chromium.org + + Time between starting and finishing DNS probe when NCN says we're offline. + + + + + + Removed 7/2013. + + mgersh@chromium.org + + Result of DNS probes sent by the probe service when NCN says we're offline. + + + + + + Removed 7/2013. + + mgersh@chromium.org + + Time between starting and finishing DNS probe when NCN says we're online. + + + + + + Removed 7/2013. + + mgersh@chromium.org + + Result of DNS probes sent by the probe service when NCN says we're online. + + + + + + Renamed 7/2013 to DnsProbe.ProbeResult. (Also switched to the full + DnsProbe.ProbeStatus enum.) + + mgersh@chromium.org + Result of DNS probes sent by the probe service. + + + + + Removed 7/2013. + + mgersh@chromium.org + Elapsed time of DNS probes that return PROBE_BAD_CONFIG. + + + + + Removed 7/2013. + + mgersh@chromium.org + + Whether the only nameserver in the system DNS config was 127.0.0.1 when the + probe result was BAD_CONFIG. + + + + + + Removed 7/2013. + + mgersh@chromium.org + + The result of the system probe job when the overall probe result was + BAD_CONFIG. + + + + + + Removed 7/2013. + + mgersh@chromium.org + + The number of nameservers in the system DNS config when the probe result was + BAD_CONFIG. + + + + + + Removed 7/2013. + + mgersh@chromium.org + Elapsed time of DNS probes that return PROBE_NO_INTERNET. + + + + + Removed 7/2013. + + mgersh@chromium.org + Elapsed time of DNS probes that return PROBE_NXDOMAIN. + + + + + Removed 7/2013. + + mgersh@chromium.org + Elapsed time of DNS probes that return PROBE_UNKNOWN. + + + + + Replaced 2/2019 with DnsProbe.ProbeDuration2, which uses TimeTicks instead + of Time. + + pauljensen@chromium.org + mef@chromium.org + Wall time between starting and finishing DNS probe. + + + + + Removed 9/2016. + + mariakhomenko@chromium.org + + Recorded only for Android. Records on every metrics upload whether document + mode is enabled. + + + + + + Removed May 2020. + + pstew@chromium.org + + Chrome OS document scan metric that tracks whether a document scan call to + the image conversion process succeeded. + + + + + + Removed July 2020. + + fletcherw@chromium.org + bmgordon@chromium.org + + Chrome OS document scan metric that tracks whether an attempt to scan + succeeded. + + + + + + Removed July 2019. + + nharper@chromium.org + + Tracks whether the "Origin Bound Certs" file exists in a profile. + Logged each time the network context params are created for a profile, which + should happen approximately once per session for a profile. + + + + + + Removed January 2018. + + mattm@chromium.org + Number of certs loaded from domain bound cert database. + + + + + Feature was removed (crbug.com/875053). + + nharper@chromium.org + + The status of loading the Channel ID database from disk. This histogram + records why the database failed to load, or that it loaded successfully. + + + + + + Removed January 2018. + + mattm@chromium.org + Time spent loading domain bound cert database. + + + + + Removed 4/2017. + + mattm@chromium.org + + The size, on disk, of the domain bound cert database as it is being loaded. + + + + + + Feature was removed (crbug.com/875053). + + nharper@chromium.org + + The version number of the Channel ID database (before any migrations are + run). + + + + + + Removed 4/2017. + + mattm@chromium.org + Time spent generating a domain bound cert. + + + + + Removed 4/2017. + + mattm@chromium.org + + Combined time for GetDomainBoundCert retrieval (both synchronous and + asynchronous). + + + + + + Removed 4/2017. + + mattm@chromium.org + + Time for asynchronous retrieval (from the GetDomainBoundCert call until + completion callback is called). + + + + + + Removed 4/2017. + + mattm@chromium.org + Time for synchronous GetDomainBoundCert cert retrieval. + + + + + Removed January 2018. + + mattm@chromium.org + Result of GetDomainBoundCert function. + + + + + Feature was removed (crbug.com/875053). + + mattm@chromium.org + + Whether the domain-bound certs sqlite database was killed succesfully when + an unrecoverable error was detected. + + + + + + Removed January 2018. + + mattm@chromium.org + + Counts of SSL client sockets broken down by support for Domain Bound + Certificates TLS extension. Counts only connections with full handshakes, + resumed sessions are not counted. + + + + + + Removed 4/2017. + + mattm@chromium.org + + Longest time spent by requests waiting for load of domain bound cert + database. + + + + + + Removed 4/2017. + + mattm@chromium.org + + Number of requests that waited for load of domain bound cert database. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The time between successive Domain Reliability beacons being queued in the + same context. (Can be arbitrarily long if no beacons are queued in a while.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The time between successive Domain Reliability beacons being queued across + all contexts. (Can be arbitrarily long if no beacons are queued in a while.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + Whether a beacon added to a Domain Reliability context was saved to be + uploaded to the collector. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + Whether adding a beacon to a Domain Reliability context caused it to evict + an older beacon to stay within memory limits. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The Chrome error code included in a beacon saved to be uploaded to the + collector. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The Chrome error code included in a beacon with a non-empty server_ip field + saved to be uploaded to the collector. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The upload depth included in a beacon saved to be uploaded to the collector. + (Zero means the beacon was not about a report upload; n+1 means the beacon + was about a report with upload depth n.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + When Domain Reliability receives a valid NEL configuration header for an + origin with Domain Reliability active, whether or not it needed to recreate + the origin's context to apply a changed config. + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The index of the collector that a Domain Reliability upload was sent to. + (Later collectors are only used when earlier collectors have failed.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + After an upload to a collector finishes (successfully or not), the delay + before the scheduler can send another upload to that collector. (If recent + uploads were successful, this will be 0; if not, it will be based on the + BackoffEntry and any Retry-After header received.) + + + + + + Removed 11/2019 for cleanup. https://crbug.com/807144 + + juliatuttle@chromium.org + + The elapsed time between starting and finishing a Domain Reliability upload. + + + + + + Removed 11/2014; see UploadCollectorIndex + + juliatuttle@chromium.org + + Whether a Domain Reliability upload was sent to a collector other than the + first one listed in the config. (This only happens when an upload to the + first collector fails.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The time between successive Domain Reliability uploads being started in the + same context. (Can be arbitrarily long if no beacons are reported in a + while.) + + + + + + Removed November 2017. + + juliatuttle@chromium.org + + The time between successive Domain Reliability uploads being started across + all contexts. (Can be arbitrarily long if no beacons are reported in a + while.) + + + + + + Removed 11/2019 for cleanup. https://crbug.com/807144 + + juliatuttle@chromium.org + + The time from the first beacon in a Domain Reliability upload being recorded + and that upload completing successfully. (Note that if some beacons are + never uploaded successfully, they will not feature in this histogram at + all.) + + + + + + Removed 11/2019 for cleanup. https://crbug.com/807144 + + juliatuttle@chromium.org + + The network error code (or OK if none) returned by the URLFetcher when a + Domain Reliability report is uploaded. + + + + + + Removed 11/2019 for cleanup. https://crbug.com/807144 + + juliatuttle@chromium.org + + The HTTP response code returned by the Domain Reliability collector when a + report is uploaded. + + + + + + Removed 11/2019 for cleanup. https://crbug.com/807144 + + juliatuttle@chromium.org + Whether a Domain Reliability upload succeeded. + + + + + UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. + + mdjones@chromium.org + + Records if the close button was used before or after opening and viewing + Reader Mode content. + + + + + + Removed 04/2020 because the code to collect this metric has not been called + in months. + + nyquist@chromium.org + + Whether the perceived quality of the distillation of a web page was good. + + + + + + PageDistillableAfterLoading and PageDistillableAfterParsing provide more + details since 02/2016. + + cjhopman@chromium.org + + Records the "Distillable Type" (not distillable, mobile-friendly + distillable, non-mobile-friendly distillable, etc) for each analyzed page. + + + + + + Not collected anymore. + + cjhopman@chromium.org + + Records the "Distillable Type" (not distillable, mobile-friendly + distillable, non-mobile-friendly distillable, etc) for each distilled page. + + + + + + UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. + + wychen@chromium.org + + Records the time from a swipe-up gesture on ReaderModePanel to the first + paint of the empty template. + + + + + + UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017. + + mdjones@chromium.org + + Records the amount of time between the Reader Mode panel opening and it + closing or returning to the peeking state. + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.clear() or sessionStorage.clear(). + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.getItem() or sessionStorage.getItem(). + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.key() or sessionStorage.key(). + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.length() or sessionStorage.length(). + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.removeItem() or + sessionStorage.removeItem(). + + + + + + Removed 2012. + + michaeln@chromium.org + + Duration to execute localStorage.setItem() or sessionStorage.setItem(). + + + + + + Removed from code 2017-08. + + treib@chromium.org + Outcome of downloading the Doodle config. + + + + + Removed from code 2017-08. + + treib@chromium.org + + The time it took to download the Doodle config. Recorded only if the + download succeeded and the received data was parsed without errors. + + + + + + Removed in 08/2018. + + dtrainor@chromium.org + The length of downloads for serves that accept byte ranges. + + + + + Removed in 08/2018. + + dtrainor@chromium.org + + The length of downloads for serves that do not specify whether the accept + ranges, or have invalid ranges specified. + + + + + + Removed in 08/2018. + + dtrainor@chromium.org + + The length of downloads for serves that do not accept ranges. + + + + + + Removed January 2017. + + dtrainor@chromium.org + The actual bandwidth (per read) of a download. + + + + + Removed in 08/2018. + + dtrainor@chromium.org + + Result of invoking (or attempting to invoke) Windows Attachment Services API + via IAttachmentExecute::Save(). + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Disk bandwidth (defined as total bytes divided by the amount of time blocked + on write or close on the file descriptor) seen for a single download. + + + + + + Removed January 2017. + + dtrainor@chromium.org + + The percentage of the potential bandwidth actually used (per read) of a + download. An entry of 100% implies that Chrome was the limiting factor in + download speed. + + + + + + Removed April 2017. + + qinmin@chromium.org + + For parallel downloading, average disk bandwidth seen when only 1 stream is + actively downloading the content. Other streams may have already finished, + or have not been created yet. If a download was ever paused, this is not + recorded. + + + + + + Removed April 2017. + + qinmin@chromium.org + + For parallel downloading, average disk bandwidth seen when parallel streams + are downloading the content. If a download was ever paused, this is not + recorded. + + + + + + Removed 02/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Records the number of cancelled download that are cleaned up from the + history, after loading all the downloads from the history DB on startup. + + + + + + Removed 1/2017. + + dtrainor@chromium.org + + The number of downloads in history at the time it is cleared. + + + + + + Deprecated 04/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Network connection information about the download, recorded after the + network response is received. + + + + + + Deprecated 02/2020. + + dtrainor@chromium.org + + Content-Disposition header features. The presence of a Content-Disposition + header, use of 'filename' and 'filename*' parameters, and string encoding + schemes are counted for each unthrottled download. The total number + downloads is Download.Counts[5] (Initiated and Unthrottled). + + + + + + Deprecated 02/2020. + + qinmin@chromium.org + + File size calculated from the content-length header of successfully + completed Parallelizable downloads. + + + + + + Removed 03/2017, and replaced by Download.Start.ContentType. + + dtrainor@chromium.org + Content types that are downloaded. + + + + + Removed in 01/2020. + + dtrainor@chromium.org + felt@chromium.org + + User chose to save a download which was marked dangerous. Grouped by the + type of danger. + + + + + + Removed in 01/2020. + + dtrainor@chromium.org + felt@chromium.org + + User chose to save a download which was marked DANGEROUS_FILE. Grouped by + the type of file. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + felt@chromium.org + + A download which was marked DANGEROUS_FILE was discarded without the user + directly choosing, because the browser was closed. Grouped by the file + extension. + + + + + + Removed in M77 since the data was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates why a download is marked as DANGEROUS_FILE. Grouped by reason, + such as Safe Browsing (SB) service is not available, and SB returns UNKOWN + or SAFE verdict. The sum of all reasons should roughly equal to the + DANGEROUS_FILE bucket count in Download.DownloadWarningShown. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + felt@chromium.org + + User chose to discard a download which was marked DANGEROUS_FILE. Grouped by + the file extension. + + + + + + Removed in 08/2018. + + asanka@chromium.org + Time taken to create a single download in the history DB. + + + + + Removed in 08/2018. + + asanka@chromium.org + Time taken to query all downloads from history DB. + + + + + Removed in 08/2018. + + asanka@chromium.org + Time taken to update a single download in the history DB. + + + + + Removed in 07/2019. + + qinmin@chromium.org + + Whether a download can be found for a download slice in the DB. This + histogram is recorded for each download slice row every time the database is + loaded. + + + + + + Removed in 08/2018. + + asanka@chromium.org + Reason for dropping a record read in from the DB. + + + + + Removed in 08/2018. + + asanka@chromium.org + Number of downloads removed from the history at once. + + + + + Removed 2/2017 + + dtrainor@chromium.org + + How long it took to delete a batch of downloads from history. + + + + + + Removed 2/2017 + + dtrainor@chromium.org + + How long it took to delete some downloads from history, per download. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + felt@chromium.org + + A download which was marked dangerous was discarded without the user + directly choosing, because the browser was closed. Grouped by the type of + danger. + + + + + + Removed 1/2017. + + dtrainor@chromium.org + + The percentage of the available disk bandwidth that was used by the + download. 100% indicates that the disk bandwidth was the limiting factor for + the download. + + + + + + Replaced 03/2020 by Download.ShowedDownloadWarning due to this one expiring. + + dtrainor@chromium.org + + A download warning was shown in the shelf. Note that some downloads may not + be shown on the shelf, e.g., if chrome://downloads is already open when the + download completes, or if an extension is using the downloads API. Grouped + by the type of danger. + + + + + + Removed in 09/2020. + + qinmin@chromium.org + + Estimated time saved on a download when parallel downloading is enabled. To + estimate this, the time spent on a download is classified into two + categories. The fist category has only one stream active, while other + streams are either finished, not started, or failed. And the second category + has multiple streams active. By calculating the average bandwidth during the + first category, a rough estimation on the time it will save is obtained by + assuming all the bytes downloaded during the second category are downloaded + by only one stream. If a download is ever paused, this is not recorded. + + + + + + Removed in 07/2019. + + qinmin@chromium.org + + Similar to Download.EstimatedTimeSavedWithParallelDownload, but this + estimates the time wasted on a download when parallel downloading is + enabled. + + + + + + Removed in 06/2020. + + dtrainor@chromium.org + + Whether the user enables dangerous download feedback reporting after viewing + the opt-in dialog. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + How the user interacts with the file chooser when doing a "Save + As" for non-full-page saves. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The amount of time in milliseconds the file thread blocks for each set of + buffers drained from the incoming pipe (ms). + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The number of buffers in a call to DownloadManager::UpdateDownload. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The time between a download completing and the file being opened for the + first time. + + + + + + Removed 11/2018. + + yaoxia@chromium.org + + The type of frame in which a download occurs and whether the download + involves a transient user gesture. It is only recorded for downloads + originated from navigations or from HTML anchor download attributes. + + + + + + Removed in 04/2020. + + dtrainor@chromium.org + + The number of items in the History database, at the time a new download is + recorded. + + + + + + Removed in 04/2020. + + dtrainor@chromium.org + + The number of items in the History database, at the time a new download is + recorded. Higher maximum, more buckets than Download.HistorySize. + + + + + + Checked on 06/2020 and no longer logged. + + dtrainor@chromium.org + + Positive net error code that caused a download to be interrupted at the + *end* of a download (when the number of bytes is known). This is only + triggered when the total content size is known before any bytes are + transferred, such as when a Content-Length header is supplied. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + + The reason that a download was interrupted at the *end* of a download (when + the number of bytes is known). This is only triggered when the total content + size is known before any bytes are transferred, such as when a + Content-Length header is supplied. + + + + + + Removed in 02/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Records the number of interrupted download that are cleaned up from the + history, after loading all the downloads from the history DB on startup. + + + + + + Checked on 06/2020 and no longer logged. + + dtrainor@chromium.org + + Positive net error code that caused a download to be interrupted. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + + The total number of bytes minus the received number of bytes at the time + that a download is interrupted. This is only triggered when the total + content size is known before any bytes are transferred, such as when a + Content-Length header is supplied. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + + The number of kilobytes received for a download at the time it is + interrupted. + + + + + + Deprecated 02/2020. + + dtrainor@chromium.org + + The reported total size in kilobytes for a download at the time it is + interrupted. This is essentially the size reported by the Content-Length + header. If no size is specified up-front, it is not recorded in the + histogram. For example, a download transferred with chunked encoding will + not be recorded. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + + The excessive number of bytes which have been received at the time that a + download is interrupted. This is only triggered when the total content size + is known before any bytes are transferred, such as when a Content-Length + header is supplied. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + True if the size of an interrupted download is unknown, false if it is + known. + + + + + + Removed in 12/2019 replaced by IOSDownloadFileUIGoogleDrive's histogram. + + eugenebut@chromium.org + pkl@chromium.org + + Logged when the download was successfully completed. Bool value indicates + whether or not Install Google Drive promo was shown to the user. + + + + + + Removed as of 01/2019. + + yaoxia@chromium.org + + Whether the main frame download involves a transient user gesture. It is + only recorded for downloads originated from navigations or from HTML anchor + download attributes. + + + + + + Removed as of 03/2019. + + yaoxia@chromium.org + + For a download that occurs in top frame, record whether the frame is + sandboxed and whether the download involves a transient user gesture. It is + only recorded for downloads originated from navigations or from HTML anchor + download attributes. + + + + + + Removed as of 08/2019. + + dtrainor@chromium.org + felt@chromium.org + + A download has been marked as malicious. Grouped by the type of danger. Each + download can only be recorded once; it will be labeled with the first type + of danger spotted. + + + + + + Removed in 04/2019 after network service is enabled by default. Use + Download.MapErrorNetworkFailed.NetworkService instead. + + dtrainor@chromium.org + + Network error that produced a DOWNLOAD_INTERRUPT_REASON_NETWORK_FAILED + result in DownloadResourceHandler::OnResponseCompleted(). + + + + + + Removed as of 08/2020. + + dtrainor@chromium.org + qinmin@chromium.org + + Network error that produced a DOWNLOAD_INTERRUPT_REASON_NETWORK_FAILED + result in DownloadResourceHandler::OnResponseCompleted(). Recorded when + running with the network service enabled. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Windows error that produced a DOWNLOAD_INTERRUPT_REASON_ACCESS_DENIED result + in MapShFileOperationCodes(). + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_FAILED result + in MapShFileOperationCodes(). + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_TRANSIENT_ERROR + result in MapShFileOperationCodes(). + + + + + + Removed July 2019. + + xingliu@chromium.org + + Records the duration to successfully complete the media file parsing. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Percentage of DownloadItem::Observer::OnDownloadUpdated events that + signified a change in the extension API representation of the download. + + + + + + Deprecated 02/2020. + + dtrainor@chromium.org + + The time between a download completing and the file being opened. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Changes observed when a response is received for a full download resumption + request. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Changes observed when a response is received for a partial (byte-range) + download resumption request. + + + + + + Removed 08/2020 + + dtrainor@chromium.org + + The core page transition type for navigation initiated downloads. Not + recorded for programmatic downloads. This metric is recorded when the + response headers were received and processed for a download. The number of + samples here should correspond to Download.Counts[8] (Started) - + (programmatic downloads that don't have a page transition type). + + + + + + Removed August 2018. + + xingliu@chromium.org + + Records the ratio of parallel streams bandwidth to single stream bandwidth + in parallel download. + + + + + + Removed in 07/2019. + + qinmin@chromium.org + + Records the remaining download time when building parallel requests. + + + + + + Removed August 2018. + + xingliu@chromium.org + + Records the ratio of the actual total time of the download to the total time + without parallel streams. The total time without parallel streams is + calculated as the size of the file divided by the single stream bandwidth. + + + + + + Removed January 2017. + + dtrainor@chromium.org + + The maximum bandwidth (per read) that Chrome could have provided for the + download. If the actual bandwidth equals the potential bandwidth, that means + that Chrome was the limiting factor for download bandwidth. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The percentage of the lifetime of the DownloadResourceHandler for which it + was blocked by downstream flow control. 0% indicates that the network + bandwidth was the limiting factor for the download. + + + + + + Removed in 08/2019. + + qinmin@chromium.org + xingliu@chromium.org + + Records the interrupt reason after download is resumed after a content + length mismatch error. + + + + + + Removed in 04/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Records whether strong validators are present when download completes. + + + + + + Removed in 09/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Records counts related to download restarting from the beginning during + resumption. + + + + + + Removed in 04/2020. + + qinmin@chromium.org + xingliu@chromium.org + + Records whether strong validators are present when download is resumed. + + + + + + Deprecated 05/2020. + + + + dtrainor@chromium.org + mheikal@chromium.org + hanxi@chromium.org + + The number of times full browser mode is requested to be loaded by a + DeferredClientWrapper. This is recorded when a DeferredClientWrapper needs + to inflate the underlying client while the browser is running in reduced + mode. DeferredClientWrapper inflates the underlying client for any + non-trivial method call on DeferredClientWrapper. + + + + + + Deprecated 02/2020. + + dtrainor@chromium.org + + Records how many resumptions have taken place at the time of resumption for + a download in the Download Service. This differs from + Download.Service.Entry.RetryCount, which records restarts. + + + + + + Removed as of 01/2020. + + shaktisahu@chromium.org + + The number of times download service tried to delete the download file + before successfully deleting it. + + + + + + Removed 08/2020 + + xingliu@chromium.org + + The percentage of disk space used by download service files. Recorded during + initialization of the file monitor. + + + + + + Removed 08/2020 + + + + xingliu@chromium.org + + Records if the final file path has been renamed by low level download + library after the download is successfully completed. + + + + + + Removed as of 08/2019. + + + + xingliu@chromium.org + + The file size of completed download, including failed downloads. + + + + + + Removed in 09/2019. + + dtrainor@chromium.org + xingliu@chromium.org + + Records if a completed download service entry was sent to a client with a + hash or not. + + + + + + Removed 08/2020 + + xingliu@chromium.org + + The state that the entry transitions to when recovery operation happens. + + + + + + Removed in 06/2019 in Issue 975678. + + xingliu@chromium.org + The battery requirement of the download request. + + + + + Removed in 06/2019 in Issue 975678. + + xingliu@chromium.org + The network requirement of the download request. + + + + + Removed in 06/2019 in Issue 975678. + + xingliu@chromium.org + The priority of the download request. + + + + + Removed 08/2020 + + + + xingliu@chromium.org + The start response of download attempts. + + + + + Download client api no longer expects a repsponse from the client when a + download is started. + + + + xingliu@chromium.org + The start result of download attempts. + + + + + Removed in 08/2018. + + asanka@chromium.org + + The number of download items in progress on the shelf when it closes + automatically. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The number of download items in progress on the shelf when the user closes + it. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The number of download items on the shelf when it closes automatically. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + The number of download items on the shelf when the user closes it. + + + + + + Removed 1/2018, integrated into Download.Counts.DOWNLOAD_TRIGGERED_COUNT + + xingliu@chromium.org + + The initiation source (if initiated within the content layer of chrome) for + a download. + + + + + + Removed in 04/2020. Superseded by mixed download metrics under + Download.InsecureBlocking. + + cthomp@chromium.org + estark@chromium.org + + The content type of a download, for downloads where the final resolved URL + or any redirect before the final URL are insecure. To normalize these + numbers, divide the counts by the counts of Download.Start.ContentType (to + measure the proportion for each content type downloaded insecurely) or by + the sum of Download.Start.ContentType (to measure the proportion of a + particular insecure download content type over all downloads). + + + + + + Removed in 04/2020. Superseded by mixed download metrics under + Download.InsecureBlocking. + + cthomp@chromium.org + estark@chromium.org + + The content type of a download, for downloads where the final resolved URL + and all redirects before the final URL are secure. To normalize these + numbers, divide the counts by the counts of Download.Start.ContentType (to + measure the proportion for each content type downloaded securely) or by the + sum of Download.Start.ContentType (to measure the proportion of a particular + secure download content type over all downloads). + + + + + + Removed as of 03/2019. + + yaoxia@chromium.org + + For a download that occurs in subframe, record whether the frame is + sandboxed, whether the origin is same to the top frame, whether it's an ad + subframe, and whether the download involves a transient user gesture. It is + only recorded for downloads originated from navigations or from HTML anchor + download attributes. + + + + + + Removed in M77 since the data was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The connection security state of a download, indicating whether its final + resolved url and the redirects before final url are secure. + + + + + + Removed in 08/2018. + + asanka@chromium.org + Time between the start of a download and its completion. + + + + + Removed in 08/2018. + + asanka@chromium.org + + Time elapsed until a retried download file rename operation failed for the + last time after the initial rename failed. + + + + + + Removed in 08/2018. + + asanka@chromium.org + + Time elapsed until a retried download file rename operation succeeded after + the initial rename failed. + + + + + + Removed in 07/2019. + + dtrainor@chromium.org + felt@chromium.org + + User chose to discard a download which was marked dangerous. Grouped by the + type of danger. + + + + + + Removed 1/2017 + + dtrainor@chromium.org + + The number of iterations for the write loop in BaseFile::AppendDataTofile(). + + + + + + Removed 1/2017 + + dtrainor@chromium.org + The write size for calls to BaseFile::AppendDataTofile(). + + + + + Removed 2/2018 + + digit@chromium.org + + The time to succesfully download and install the DownloadableStrings + component on Android. + + + + + + Removed 2/2018 + + digit@chromium.org + + The mobile country code (MCC) of the device's SIM card, if available (in the + [200..999] range), or 0 for "undetermined". This is collected on + Chrome startup. For devices with several SIM cards, this only reports the + code of the SIM card in use during startup. + + + + + + Removed 2/2018 + + digit@chromium.org + + The status code returned after trying to install and update the + DownloadableStrings component. + + + + + + Removed 2/2018 + + digit@chromium.org + + The timeout reported by the component updater when trying to install the + DownloadableStrings component fails with a specific error. + + + + + + Obsolete 07/2019 as DriveFS implementation obsoletes this metric. + + hirono@chromium.org + Respose code of batch upload request. + + + + + Removed 8/2013. + + joshwoodward@google.com + Status of drive cache metadata database open. + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Time spent to load the delta change list information from the server. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Time spent to load the list of files in a single directory from Google Drive + server. + + + + + + This was a temporary histogram for bug http://crbug.com/229650 that has been + closed. + + mtomasz@chromium.org + + Sizes of files being downloaded from Drive. Temporary histogram for + gathering data for http://crbug.com/229650. + + + + + + Removed 12/2013 due to the UMA stat bucket layout change. We'll use + Drive.FullFeedLoadTime instead. + + joshwoodward@google.com + + Time spent to load the entire file system information from the server + + + + + + Removed 10/2012. + + joshwoodward@google.com + + Provides breakdown of specific formats for hosted documents. Recorded when + feed is loaded from the server. + + + + + + Removed 10/2012. + + joshwoodward@google.com + + Provides breakdown of specific file formats for regular files. Recorded when + feed is loaded from the server. + + + + + + Obsolete 02/2019 as DriveFS implementation obsoletes this metric. + + mtomasz@chromium.org + + Error codes returned by the Drive API for files list requests executed via + the FilesListRequestRunner class. + + + + + + Obsolete 02/2019 as DriveFS implementation obsoletes this metric. + + mtomasz@chromium.org + + Maximum number of results for each files list request using the Drive API. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Time spent to load the entire file system information from the server + + + + + + Deperecated 12/2013 since it did not record meaningful information. + Drive.DirectoryFeedLoadTime should be checked for measuring the time until + the user sees the first response of file lists. + + joshwoodward@google.com + + Time spent to load the initial part of the file system information from the + server + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + Result of drive resource metadata database initialization. + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Result of attempt to open existing drive resource metadata database. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Reason of drive resource metadata database validity check failure. Recorded + when the validity check fails during Drive metadata initialization triggered + by profile initialization. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Version number of drive resource metadata DB found on the disk before + checking whether it should be upgraded. Recorded during Drive metadata + initialization triggered by profile initialization. + + + + + + Obsolete 08/2019. Most migrations are complete, we no longer need this. + + dats@chromium.org + sammc@chromium.org + + Records the number of dirty (unsynced) files migrated from legacy Drive to + DriveFs. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Number of files recovered from Drive cache directory. Recorded when file + recovery takes place after metadata DB corruption is found during metadata + DB initialization. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive + is first accessed. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Number of regualr files on Drive. Logged when Drive is first accessed. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Number of total files (regualr files + hosted documents) on Drive. Logged + when Drive is first accessed. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Time spent to perform an incremental search for auto completion of files on + Drive. This time is collected for every partial query the user types for + auto completion. For instance, if the user types "faq", + incremental searches are performed for "f", "fa", and + "faq" respectively. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + Total file count contained in a drive batch upload request. + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + Total file size contained in a drive batch upload request. + + + + + This was a temporary histogram for bug http://crbug.com/229650 that has been + closed. + + mtomasz@chromium.org + + Number of jobs which have to be completed before a newly added download or + download from or to Drive is requested. Temporary histogram for gathering + data for http://crbug.com/229650. + + + + + + Obsolete 04/2019 as DriveFS implementation obsoletes this metric. + + slangley@chromium.org + weifangsun@chromium.org + + Upload protocol for each file. e.g. Batch upload including 5 files triggers + the metric 5 times. + + + + + + This was a temporary histogram for bug http://crbug.com/229650 that has been + closed. + + mtomasz@chromium.org + + Sizes of files being uploaded to Drive. Temporary histogram for gathering + data for http://crbug.com/229650. + + + + + + Converted to DCHECK in 08/2020. If EDID property is unset, blob is always + NULL. + + andrescj@chromium.org + mcasas@chromium.org + chromeos-gfx@google.com + + True when an EDID blob is detected and is empty. This UMA is recorded + whenever we attempt to parse the EDID from a display. + + + + + + Removed as of 03/2018. + + joshwoodward@google.com + isherman@chromium.org + + When Easy Unlock attempts to authenticate the secure connection between a + Chromebook (or other Chrome device) and an Android phone, whether the + authentication succeeded. + + + + + + Removed as of 11/2018. + + tengs@chromium.org + hansberry@chromium.org + + Measures the time delta in milliseconds since the last zero RSSI value was + read to when the user successfully unlocks or signs in using Smart Lock. + +
+ A zero RSSI value is special because both Bluetooth devices in a connection + attempt to maintain by adjusting their transmit power levels. This time + delta can be used as a possible heuristic to determine that the phone is + close to the local device. + + If no RSSI was read, then an overflow value will be recorded. +
+ + + + + Removed as of 11/2018. + + tengs@chromium.org + hansberry@chromium.org + + Measures the difference between the current transmit power and the maximum + transmit power of the local device when the user successfully unlocks or + signs in using Smart Lock. + +
+ Devices connected using classic Bluetooth adjust their transmit power + dynamically to optimize power and signal strength. The difference between + the current transmit power and maximum transmit power can be used as a + heurstic to determine if the phone is close to the local device. + + According to the Bluetooth specs, there are three classes of devices, with a + maximum transmit power of 20, 4, and 0 dBm respectively. + + If no transmit power was read, then a sentinel value of 127 will be + recorded. +
+ + + + + Removed as of 02/2017. + + bcwhite@chromium.org + + Reports the type of Bluetooth adapter present in the device. + +
+ Statistics about what Bluetooth capabilities are available will determine + how the EasyUnlock feature gets developed and deployed across platforms. + + This value is logged only once during the lifetime of the Chrome process, + shortly after it starts up. If a Bluetooth USB adapter is inserted after + that point, the change will not be registered until Chrome restarts. +
+ + + + + Removed as of 01/2020. + + hansberry@chromium.org + Button clicked in EasyUnlock app during setup process. + + + + + Removed 02/2015. Replaced by EasyUnlock.Setup.PromoNotificationEvent. + + joshwoodward@google.com + tbarzic@chromium.org + + Tracks events related to notifications used by EasyUnlock feature. For + example a specific EasyUnlock notification being shown or clicked. + + + + + + Removed as of 01/2020. + + hansberry@chromium.org + + The number of eligible devices that the CryptAuth server returns during the + Smart Lock setup flow. + +
+ Note that a single user might report multiple values, for example if they + try to complete the setup flow with a device in airplane mode, and then try + again taking the device out of airplane mode. +
+ + + + + Removed as of 01/2020. + + hansberry@chromium.org + + The number of ineligible devices that the CryptAuth server returns during + the Smart Lock setup flow. + +
+ Note that a single user might report multiple values, for example if they + try to complete the setup flow with a device in airplane mode, and then try + again taking the device out of airplane mode. +
+ + + + + Removed as of 01/2020. + + hansberry@chromium.org + + Whether the user's phone has a secure screen lock installed. Recorded during + Smart Lock setup, when the user's phone first connects to the Chromebook. + + + + + + Removed as of 01/2020. + + hansberry@chromium.org + + Whether the user's phone has a trust agent -- e.g. Smart Lock for Android -- + enabled. Recorded during Smart Lock (for Chrome) setup, when the user's + phone first connects to the Chromebook. + +
+ Note that this histogram tracks whether the setting under Settings ~> + Security ~> Trust agents ~> Smart Lock (Google) (or any other trust + agent) is enabled. The Smart Lock trust agent is enabled by default for + users who have ascure lock screen. This metric does _not_ measure whether + users have any Smart Lock trustlets enabled. +
+ + + + + Removed as of 01/2020. + + hansberry@chromium.org + + Records the most actionable reason why none of a user's devices were + eligible as unlock keys for Smart Lock. This is recorded during the Smart + Lock setup flow, only if the CryptAuth server returns no eligible devices + for the user. + +
+ To be precise, this metric tracks the _least_ actionable _reason_ why the + _most_ actionable _device_ is not eligible as an unlock key. For example, + suppose that the user has 10 ineligible devices returned. This metric tries + to identify the most likely candidate device for use as a Smart Lock key, + and then records the most confounding reason why that device is still not + eligible to be used as an unlock key. +
+ + + + + Removed as of 03/2018. + + hansberry@chromium.org + jhawkins@chromium.org + + Records events at each step of the Setup process, when the Setup flow is + initiated without the promotion notification. + + + + + + Removed as of 03/2018. + + hansberry@chromium.org + jhawkins@chromium.org + + Records events at each step of the Setup process, when the Setup flow is + initiated via the promotion notification. + + + + + + Removed as of 01/2020. + + hansberry@chromium.org + + Measures user interactions with the Smart Lock promo notification. + +
+ Due to technical limitations of the implementation, it is hard to track + precisely which users opened the setup app as a result of interacting with + the promo notification. This metric measures setup app interactions from all + users who click on the promo notification, and subsequently launch the setup + app. +
+ + + + + Removed as of 03/2018. + + joshwoodward@google.com + tbarzic@chromium.org + + The state of EasyUnlock setup when the app window was closed by user. + + + + + + Removed 02/2015; replaced by EasyUnlock.AuthEvent.SignIn. + + hansberry@chromium.org + + Measures the use of Easy sign-in: records whether an Easy sign-in login + succeeded or failed; or if a password fallback was used, the reason why. + Recorded upon a login attempt for users who have the Easy sign-in feature + enabled. + + + + + + Removed as of 01/2020. + + hansberry@chromium.org + + Records when the Easy Unlock trial run is launched, and when the user + attempts to click on the lock icon during the trial run. + +
+ If a user clicks on the lock icon more than once, then the "clicked + lock icon" event counter will be incremented more than once as well. + Hence, the "user count" data shows how many users ever clicked on + the lock icon during the trial run. From the raw (non-"user + count") data, we can also see whether users click on the icon multiple + times. +
+ + + + + Removed 02/2015; replaced by EasyUnlock.AuthEvent.Unlock. + + joshwoodward@google.com + tbarzic@chromium.org + Screen unlock events detected while EasyUnlock was enabled. + + + + + Removed 03/2016; replaced by + EmbeddedWorkerInstance.Start.SendStartWorker_ExistingProcess and + EmbeddedWorkerInstance.Start.TimeToURLJob_ExistingProcess. + + ksakamoto@chromium.org + + The time taken to allocate a process to start the EmbeddedWorkerInstance. + Recorded when an existing process was used. + + + + + + Removed 03/2016; replaced by + EmbeddedWorkerInstance.Start.SendStartWorker_NewProcess and + EmbeddedWorkerInstance.Start.TimeToURLJob_NewProcess. + + ksakamoto@chromium.org + + The time taken to allocate a process to start the EmbeddedWorkerInstance. + Recorded when a new process was created. + + + + + + Removed as of 05/2015. Replaced by + EmbeddedWorkerInstance.NewProcessAllocation and + EmbeddedWorkerInstance.ExistingProcessAllocation. + + horo@chromium.org + + The time taken to allocate a process to start the EmbeddedWorkerInstance. + + + + + + Removed as of June 2020. If you find it's useful and add the metric again, + please consider using an enum of StartSituation instead of a boolean. + + falken@chromium.org + chrome-worker@google.com + + Whether a new renderer process was created for the EmbeddedWorkerInstance or + existing one was used. Only recorded for installed workers. + + + + + + Removed as of 03/2016. Replaced by + EmbeddedWorkerInstance.Start.TimeToEvaluateScript. + + horo@chromium.org + + The time taken to evaluate the script to start the EmbeddedWorkerInstance. + + + + + + Removed as of 03/2016. Replaced by + EmbeddedWorkerInstance.Start.TimeToLoad_Network. + + horo@chromium.org + + The time taken to load the script file for the EmbeddedWorkerInstance with + network access. + + + + + + Removed as of 03/2016. Replaced by + EmbeddedWorkerInstance.Start.TimeToLoad_HttpCache and + EmbeddedWorkerInstance.Start.TimeToLoad_InstalledScript. + + horo@chromium.org + + The time taken to load the script file for the EmbeddedWorkerInstance + without network access. + + + + + + Removed June 2018 (M69). Replaced with + ServiceWorker.StartTiming.SentStartWorkerToReceivedStartWorker. + + falken@chromium.org + + The time between the browser sending a "start a service worker" + message to the renderer, and the renderer receiving it. This may include + renderer startup time. Only recorded if the high-resolution system clock was + used and deemed consistent across proceses, and the time was non-negative + (see EmbeddedWorkerInstance.Start.StartMessageLatency.Type). Only recorded + for installed workers. Recorded upon successful startup. + + + + + + Removed June 2018 (M69). Replaced with + ServiceWorker.StartTiming.ClockConsistency. + + falken@chromium.org + + See EmbeddedWorkerInstance.Start.StartMessageLatency. Describes the outcome + of taking the measurement and whether StartMessageLatency was recorded. + + + + + + Removed July 2018 (M69). Replaced with + ServiceWorker.StartTiming.ScriptEvaluationStartToScriptEvaluationEnd. + + falken@chromium.org + + The time taken for initial evaluation of the service worker script. + Specifically, the time between ACK from the renderer that the thread started + and ACK that the script evaluation finished. Only recorded for installed + workers. + + + + + + Removed June 2018 (M69). This depended on the URLRequestJob code path, which + won't be taken with S13nServiceWorker/NetworkService. If we want this again, + it can be logged from ServiceWorkerScriptLoader or in Blink directly using + Resource Timing. + + falken@chromium.org + + The time taken to load a new (not installed) service worker, when it came + from the HTTP cache. + + + + + + Removed June 2018 (M69). This path is no longer taken since service worker + installed script manager is used for installed scripts. + + falken@chromium.org + The time taken to load an installed service worker. + + + + + Removed June 2018 (M69), see note in + EmbeddedWorkerInstance.Start.TimeToLoad.HttpCache. + + falken@chromium.org + + The time taken to load a new (not installed) service worker, when it came + from the network. + + + + + + Removed July 2018 (M69). Replaced with + ServiceWorker.StartTiming.StartToSentStartWorker. + + falken@chromium.org + + The time taken between deciding to start a worker and sending the start + worker IPC. Only recorded for installed workers. + + + + + + Removed July 2018 (M69). Replaced with + ServiceWorker.StartTiming.ReceivedStartWorkerToScriptEvaluationStart. + + falken@chromium.org + + The time taken to start the service worker thread. Specifically, the time + between ACK from the renderer that load finished and ACK that the thread + started. Does not include script evaluation time. Only recorded for + installed workers. + + + + + + Removed June 2018 (M69). This path is no longer taken since service worker + installed script manager is used for installed scripts. + + falken@chromium.org + + The round-trip time between asking the renderer process to start a worker + and receiving the corresponding resource request. Only recorded for + installed workers. + + + + + + Removed June 2018 (M69). + + falken@chromium.org + + Indicates if Blink was not initialized by the time the browser sent a + "start a service worker" message to the renderer. If this is true, + receiving the message had to wait until after Blink initialization finished. + Blink initialization is considered the time RenderThreadImpl::Init sets up + the Mojo interface for receiving the "start a service worker" + message. Only recorded for installed workers. Recorded upon successful + startup. + + + + + + Removed June 2018 (M69). + + falken@chromium.org + + Recorded when EmbeddedWorkerInstance.Start.WaitedForRendererSetup is true. + The time between when the "start a service worker" was sent by the + browser, and Blink initialization finishing. The start time is recorded by + the browser process, and the end time by the renderer process, so process + clock skew could possibly affect the result. + + + + + + Removed 4/2016 after we no longer show "all bookamrks" in bookmark + manager. + + ianwen@chromium.org + Number of bookmarks the user has. Android only. + + + + + Removed 3/2015 along with the enhanced bookmarks sync experiment. + + noyau@chromium.org + yefim@chromium.org + + Captures the state the enhanced bookmark experiment is in. Recorded on + startup. To be removed once the enhanced bookmark experiment is finished. + see crbug/323423. + + + + + + Removed 9/2015 after list view became the only view mode. + + ianwen@chromium.org + + Record which Enhanced Bookmark UI mode users are in. This will be recorded + everytime the user opens the bookmark manager UI. + + + + + + Code removed in M46. + + aberent@chromium.org + + Android Only - Time to load the App Restrictions from the O.S.. + + + + + + Code removed in M46. + + aberent@chromium.org + + Android Only - Whether Chrome was able to read and decode the + AppRestrictions policy cache on startup. + + + + + + Removed 06/2020 because enough data had been gathered. + + zmin@chromium.org + pastarmovj@chromium.org + + The number of profiles that miss at least one report and may not be able to + catch the next round due to browser shutdown. The metric is recorded during + browser shutdown process. + + + + + + Removed 03/2020 in order to separate device and device local account. + Superseded by Enterprise.DevicePolicyInvalidations2 and + Enterprise.DeviceLocalAccountPolicyInvalidations2. + + asumaneev@google.com + managed-platforms@google.com + + Events for counting both device and device local account policies + invalidations received with and without payloads. Invalidations indicate + that a policy has been updated and should be refreshed. Payloads provide + context about the policy update, but may be absent if dropped by the + invalidation service. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.DevicePolicyRefresh2. + + bartfab@chromium.org + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. + + + + + + Removed 03/2020 in order to separate device and device local account. + Superseded by Enterprise.DevicePolicyRefresh3 and + Enterprise.DeviceLocalAccountPolicyRefresh3. + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing both device and device local + account policies when invalidations are received from a service. For each + refresh, indicates whether the policy changed, and whether the policy was + invalidated at the time of the refresh. + + + + + + Removed 03/2019, since no code reports it anymore. + + mnissler@chromium.org + + Events related to fetching, saving and loading DM server tokens. These are + used to retrieve cloud policies. + + + + + + Removed 03/2019, since the issues has been long fixed. + + atwilson@chromium.org + + Temporary metric tracking which regex caused an icu::RegexMatcher + initialization failure, to help figure out the cause of + http://crbug.com/365351 which we can't repro locally. + + + + + + Removed 03/2019, since the issues has been long fixed. + + atwilson@chromium.org + + Temporary metric tracking the type of an icu::RegexMatcher initialization + failure, to help figure out the cause of http://crbug.com/365351 which we + can't repro locally. + + + + + + Removed 03/2019, since the issues has been long fixed. + + atwilson@chromium.org + + Temporary metric tracking the success of icu::RegexMatcher IcuMatcher + initialization, to help figure out the cause of http://crbug.com/365351. + + + + + + Removed 03/2020 in order to separate device and device local account. + Superseded by Enterprise.FCMInvalidationService.DevicePolicyInvalidations2 + and + Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyInvalidations2. + + asumaneev@google.com + managed-platforms@google.com + + Events for counting both device and device local account policies + invalidations received with and without payloads. Invalidations indicate + that a policy has been updated and should be refreshed. Payloads provide + context about the policy update, but may be absent if dropped by the + invalidation service. Subset of + "Enterprise.DevicePolicyInvalidations". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.FCMInvalidationService.DevicePolicyRefresh2. + + askaraitzhan@google.com + isandrk@chromium.org + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. Subset of "Enterprise.DevicePolicyRefresh". + Gets recorded only when FCMInvalidationService is used as + InvalidationService. + + + + + + Removed 03/2020 in order to separate device and device local account. + Superseded by Enterprise.FCMInvalidationService.DevicePolicyRefresh3 and + Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyRefresh3. + + asumaneev@google.com + managed-platforms@google.com + + Events measuring effectiveness of refreshing both device and device local + account policies when invalidations are received from a service. For each + refresh, indicates whether the policy changed, and whether the policy was + invalidated at the time of the refresh. Subset of + "Enterprise.DevicePolicyRefresh2". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.FCMInvalidationService.PolicyRefresh2. + + askaraitzhan@google.com + isandrk@chromium.org + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + Subset of "Enterprise.PolicyRefresh". Gets recorded only when + FCMInvalidationService is used as InvalidationService. + + + + + + Removed 10/2019, since no code reports it anymore. Superseded by + Enterprise.InvalidDevicePolicyFilesStatus. + + emaxx@chromium.org + igorcov@chromium.org + + Chrome OS only. Number of policy files that turned out to be invalid when + reading the device policy data. In success scenario the latest policy file + read is successful and has valid data submitting zero for this statistic. + + + + + + Remove in M82. Because we decide not to handle user level enrollment + separately. + + zmin@chromium.org + + Records whether the Chrome install is system level or user level when trying + to enroll into the machine level user cloud policy on Windows. This is + intended to count the number of enrollments for each install type. + + + + + + Removed 03/2019, since no code reports it anymore. + + mnissler@chromium.org + + Events related to fetching, saving and loading user policies, and also + device policies on Chrome OS. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.PolicyRefresh2. + + mnissler@chromium.org + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + + + + + + Removed 01/2020 since the histogram indicators were stable. + + nikitapodguzov@chromium.org + The time to perform operations on the ResourceCache object. + + + + + Removed 01/2020 because SCHEMA_ALLOW_INVALID strategy was removed. + + poromov@chromium.org + hendrich@chromium.org + + Signals whether mismatched value was ignored while validating while using + SCHEMA_ALLOW_INVALID strategy. The strategy is used only for + ManagedBookmarks policy and is considered for deprecation. Recorded when + policy is validated using SCHEMA_ALLOW_INVALID strategy. + + + + + + Removed and removed from code as of 01/2016. + + pbond@chromium.org + + Events for counting sensitive data occurrences in system logs to upload. + (Email addresses, IP addresses, SSIDs, URLs). The lines with this data will + be removed before upload. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.TiclInvalidationService.DevicePolicyRefresh2. + + askaraitzhan@google.com + isandrk@chromium.org + + Events measuring effectiveness of refreshing device policy when + invalidations are received from a service. For each refresh, indicates + whether the policy changed, and whether the policy was invalidated at the + time of the refresh. Subset of "Enterprise.DevicePolicyRefresh". + Gets recorded only when TiclInvalidationService is used as + InvalidationService. + + + + + + Removed 10/2019 because was recorded incorrectly. Superseded by + Enterprise.TiclInvalidationService.PolicyRefresh2. + + askaraitzhan@google.com + isandrk@chromium.org + + Events measuring effectiveness of refreshing user policy when invalidations + are received from a service. For each refresh, indicates whether the policy + changed, and whether the policy was invalidated at the time of the refresh. + Subset of "Enterprise.PolicyRefresh". Recorded only when + TiclInvalidationService was used as InvalidationService. + + + + + + Removed 07/2016 in Issue 621270. + + mnissler@chromium.org + pastarmovj@chromium.org + + Whether we were able to contact the AD Domain Controller. This check is + performed once at start-up on Windows. + + + + + + Removed 07/2016 in Issue 621270. + + mnissler@chromium.org + pastarmovj@chromium.org + + Enum of possible things that can fail while checking for enterprise env. + This check is performed once at start-up on Windows. + + + + + + Removed M85, obsoleted by IsFullyManaged2 because recording frequency + changed from once per session to once per app start. Note that the summary + of this histogram incorrectly stated otherwise. + + twellington@google.com + tedchcoc@chromium.org + + On Android (OS version M+): Whether the device has a "device + owner" app installed. This check is performed once at start-up. + + + + + + Removed M85, obsoleted by IsManaged2 because recording frequency changed on + Android from once per session to once per app start. + + rogerta@chromium.org + pastarmovj@chromium.org + + On Windows: Whether the machine is managed via MDM. On macOS: Whether Chrome + found a file of managed policies to follow. On Android (up to M84: OS + version M+, M85+: OS version Lollipop+): Whether the device has a profile + owner app. This check is performed once at start-up. Note that this data is + bogus before M81 on the Mac. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + On non-mobile sites, gesture taps are delayed to prevent double taps from + sending a click event. This stat tracks the user's first action within 5 + seconds after a double tap gesture when the gesture tap delay is disabled. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + On non-mobile sites, gesture taps are delayed to prevent double taps from + sending a click event. This stat tracks the user's first action within 5 + seconds after a double tap gesture when gesture tap events are delayed. + + Team: input-dev@chromium.org. + + + + + + Removed as of 01/2020. The feature has been launched. + + yigu@chromium.org + + Tracks how long an event has to wait in the queue while a previous event is + being targeted asynchronously. + + Team: event-targeting@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + input-dev@chromium.org + Number of Mouse events coalesced. + + + + + Removed in 06/2020. + + tdresser@chromium.org + input-dev@chromium.org + Number of Touch events coalesced. + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between the first and last events in a coalesced mouse events group. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between the first and last events in a coalesced touch events group. + + Team: input-dev@chromium.org. + + + + + + Removed 01/2019 due to lack of usage. + + eirage@chromium.org + + Number of continuous gesture events (GestureScrollUpdate, + GesturePinchUpdate) coalesced inside the compositor thread event queue per + event. This field is recorded just before the event is processed on the + compositor thread. + + Team: input-dev@chromium.org. + + + + + + Removed 01/2019 due to lack of usage. + + eirage@chromium.org + + Time between the first event in a coalesced continuous gesture events group + (GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the + compositor thread. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 01/2019 due to lack of usage. + + eirage@chromium.org + + Time between the last event in a coalesced continuous gesture events group + (GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the + compositor thread. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 01/2019 due to lack of usage. + + eirage@chromium.org + + Time between when a non-continuous gesture event (GestureScrollStart/End, + GesturePinchStart/End) was placed into the queue and when it was processed + on the compositor thread. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 01/2018 in favor of + Event.DownEventCount.PerInputFormFactorDestinationCombination. + + xiaoyinh@chromium.org + tbuckley@chromium.org + + The number of down events received per destination. Every down event that is + targeted to each destination will be counted, including those that don't + have an effect. For example: Tapping on a disabled button inside the browser + frame will be treated as down events on browser window. + + + + + + Removed 01/2018 in favor of + Event.DownEventCount.PerInputFormFactorDestinationCombination. + + xiaoyinh@chromium.org + tbuckley@chromium.org + + Counts the number of down events generated by clamshell/touchview. + + + + + + Removed 01/2018 in favor of + Event.DownEventCount.PerInputFormFactorDestinationCombination. + + xiaoyinh@chromium.org + tbuckley@chromium.org + + Counts the number of down events generated by Mouse/Touch/Stylus. + + + + + + Removed 02/2019 in favor of + Event.DownEventCount.PerInputFormFactorDestinationCombination2. + + tbuckley@chromium.org + + The number of down events received per input, form factor, and destination + combination. + + Input is down events generated by mouse/touch/stylus. Form factor is down + events generated by clamshell/touchviewLandscape/touchviewPortrait. + Destination: Every down event that is targeted to each destination will be + counted including those that don't have an effect. For example: Tapping on a + disabled button inside the browser frame will be treated as down events on + browser window. + + + + + + Removed 06/2020 as being expired. + + dcheng@chromium.org + sadrul@chromium.org + + Reports whether chrome accepts or rejects a drag and drop operation. + + During a drag and drop operation, there are many 'drag update' events that + happen for each mouse-move event. For each such drag-update event, chrome + reports whether it is able to accept the drop event or not. + + + + + + Removed 06/2020 as being expired. + + nzolghadr@chromium.org + + Counts the number of times the user cancelled a drag and drop operation. + + + + + + Removed 06/2020 as being expired. + + nzolghadr@chromium.org + + Counts the number of times the user completed a drag and drop operation. + + + + + + Removed 06/2020 as being expired. + + nzolghadr@chromium.org + + Counts the number of times a drag and drop operation originating outside of + a Chrome window successfuly drops. + + + + + + Removed 06/2020 as being expired. + + nzolghadr@chromium.org + + Counts the number of times the user started a drag and drop operation. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Emitted after a renderer process main-thread fling curve animation + terminates, for any reason, reporting the average animation frequency + (animations/second) of the fling instance over its lifetime. This is + computed as the number of fling animation ticks divided by the fling + animation duration. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Emitted after a renderer process impl-thread fling curve animation + terminates, for any reason, reporting the average animation frequency + (animations/second) of the fling instance over its lifetime. This is + computed as the number of fling animation ticks divided by the fling + animation duration. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019. + + + + eirage@chromium.org + + Records the euclidean distance from a mouse event's position to the + predicted position at the event time when prediction is available. + Prediction is available after the predictor selected by feature flag gets a + few continuous mouse events. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019. + + + + eirage@chromium.org + + Records the euclidean distance from a ScrollUpdate event's absolute scroll + position (count by accumulated delta) to the predicted scrolling position at + the event time when prediction is available. Prediction is available after + the predictor selected by feature flag gets a few continuous + GestureScrollUpdate events. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019. Replaced by + Event.InputEventPrediction.Scroll.OverPrediction. + + + + eirage@chromium.org + + Records y direction distance from a ScrollUpdate event's absolute scroll + position (count by accumulated delta) to the predicted scrolling position at + the event time when prediction is available and also the predicted result is + 'OverPredict'. Over predict means the absolute value of predicted scroll + delta is larger than the real delta in the same time period. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019. Replaced by + Event.InputEventPrediction.Scroll.UnderPrediction. + + + + eirage@chromium.org + + Records y direction distance from a ScrollUpdate event's absolute scroll + position (count by accumulated delta) to the predicted scrolling position at + the event time when prediction is available and also the predicted result is + 'UnderPredict'. Under predict means the absolute value of predicted scroll + delta is smaller than the real delta in the same time period. + GestureScrollUpdate events. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019. + + + + eirage@chromium.org + + Records the euclidean distance from a touch event's position to the + predicted position at the event time when prediction is available. + Prediction is available after the predictor selected by feature flag gets a + few continuous touches with same ids. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + input-dev@chromium.org + + Time between the renderer main thread receiving a keyboard event and acking + it, for events which were not preventDefaulted. Only recorded for key + presses. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + input-dev@chromium.org + + Time between the renderer main thread receiving a keyboard event and acking + it, for events which were preventDefaulted. Only recorded for key presses. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchend event and acking + it, for events which were not preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchend event and acking + it, for events which were preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchmove event and acking + it, for events which were not preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchmove event and acking + it, for events which were preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchstart event and + acking it, for events which were not preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between the renderer main thread receiving a touchstart event and + acking it, for events which were preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of all input events and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of input event and browser processing. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between key events sent from RWH to renderer and acked by renderer. + Only monitors key presses. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between key events received by Chrome and sent from RWH to renderer. + Only monitors key presses. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between touch events sent from RWH to renderer and acked by renderer. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between touch events received by Chrome and sent from RWH to renderer. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + ccameron@chromium.org + + Time between wheel events sent from RWH to renderer and acked by renderer. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + ccameron@chromium.org + + Time between wheel events received by Chrome and sent from RWH to renderer. + + Team: input-dev@chromium.org. + + + + + + This histogram never has negative values, so it was removed 06/2020. + + sullivan@chromium.org + input-dev@chromium.org + + For Mac, a version of Event.Latency.OS that has the negative values it would + contain if ValidateEventTimeClock() were not called on the timestamps. + + This metric is intended to debug http://crbug.com/1039833, where very high + numbers are seen for PageLoad.InputDelay3. The units of this metric are the + same as PageLoad.InputDelay3 for consistency while debugging. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + input-dev@chromium.org + + Time between sending a keyboard event to the renderer main thread and when + the renderer begins to process that event, for events which were not + preventDefaulted. Only recorded for key presses. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a keyboard event to the renderer main thread and when + the renderer begins to process that event, for events which were + preventDefaulted. Only recorded for key presses. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchend event to the renderer main thread and when + the renderer begins to process that event, for events which were not + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchend event to the renderer main thread and when + the renderer begins to process that event, for events which were + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchmove event to the renderer main thread and when + the renderer begins to process that event, for events which were not + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchmove event to the renderer main thread and when + the renderer begins to process that event, for events which were + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchstart event to the renderer main thread and when + the renderer begins to process that event, for events which were not + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed in 06/2020. + + tdresser@chromium.org + + Time between sending a touchstart event to the renderer main thread and when + the renderer begins to process that event, for events which were + preventDefaulted. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between initiation of all input events and renderer processing. This is + soon to be replaced by Event.Latency.Renderer2.* + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between input event creation and the renderer receiving and starting to + process the event. For touch events on Windows, we measure from when the + event reaches Chrome, whereas on other platforms we use the timestamp from + the kernel. On Windows, this metric is only reported when |IsHighResolution| + is true, which will introduce some sampling bias. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between input event creation and the renderer impl thread receiving and + starting to process the event. For touch events on Windows, we measure from + when the event reaches Chrome, whereas on other platforms we use the + timestamp from the kernel. On Windows, this metric is only reported when + |IsHighResolution| is true, which will introduce some sampling bias. + + Team: input-dev@chromium.org. + + + + + + Removed 12/2013 and replaced by Event.Latency.RendererImpl.GestureScroll2 + + rbyers@chromium.org + + Time between initial creation of touch event and when the resulting + ScrollGesture reaches Impl thread. Maximum is 200ms. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between touch event creation and when the resulting GestureScroll + reaches the Impl thread. Maximum is 1000ms. On Windows, we measure from when + the touch event reaches Chrome, whereas on other platforms we use the + timestamp from the kernel. On Windows, this metric is only reported when + |IsHighResolution| is true, which will introduce some sampling bias. This + supersedes the Event.Latency.RendererImpl.GestureScroll metric. + + Team: input-dev@chromium.org. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68. + + nzolghadr@chromium.org + + Time between initial creation of a wheel/touch event and start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. If no + swap was induced by the event, no recording is made. + + Team: input-dev@chromium.org. + + + + + + Removed 04/2020 due to lack of usage. + + eirage@chromium.org + axantoine@google.com + + Time between the initiation of the last ScrollBegin event received and its + handling in a frame by the scroll predictor (i.e. rAF time). + + Team: input-dev@chromium.org. + + Warning: Only recorded in a touch context. + + + + + + Removed 10/2019 due to lack of usage. + + eirage@chromium.org + axantoine@google.com + + Time between the handling of the last ScrollBegin event received in the + frame (i.e. rAF time) and the end of the swap of that frame on the gpu. + + Team: input-dev@chromium.org. + + Warning: Only recorded in a touch context. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. This is + going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a + rebucketing change made this metric lose its usefulness in Chirp + infrastructure. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a wheel event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. This is + going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a + rebucketing change made this metric lose its usefulness in Chirp + infrastructure. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a wheel event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + sahel@chromium.org + + Time between initial creation of a ScrollUpdate gesture event generated from + a touchscreen fling and the start of the frame swap on the GPU service + caused by the generated ScrollUpdate gesture event. If no swap was induced + by the event, no recording is made. This is going to be replaced by + *.TimeToScrollUpdateSwapBegin3 version since a rebucketing change made this + metric lose its usefulness in Chirp infrastructure. + + Team: input-dev@chromium.org. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + sahel@chromium.org + + Time between initial creation of a ScrollUpdate gesture event generated from + a touchscreen fling and the start of the frame swap on the GPU service + caused by the generated ScrollUpdate gesture event. If no swap was induced + by the event, no recording is made. + + Team: input-dev@chromium.org. + + + + + + To be replaced by + Event.Latency.ScrollUpdate.Touch.BrowserNotifiedToBeforeGpuSwap2, + Event.Latency.ScrollUpdate.Wheel.BrowserNotifiedToBeforeGpuSwap2 in M56. + https://crbug.com/649754 + + rbyers@chromium.org + + Time between the browser receives the notification of a ScrollUpdate gesture + event induced renderer swap and GPU starts to swap. + + + + + + To be replaced by Event.Latency.ScrollUpdate.Touch.GpuSwap2, + Event.Latency.ScrollUpdate.wheel.GpuSwap2 in M56. https://crbug.com/649754 + + rbyers@chromium.org + + Time between gpu starts to swap a ScrollUpdate gesture event induced frame + and the swap finishes. + + + + + + To be replaced by Event.Latency.ScrollUpdate.Touch.HandledToRendererSwap2, + Event.Latency.ScrollUpdate.Wheel.HandledToRendererSwap2 in M56. + https://crbug.com/649754 + + rbyers@chromium.org + + Time between the ScrollUpdate gesture event is handled on main/impl thread + (specified by suffix) and before renderer starts to swap. + + + + + + To be replaced by + Event.Latency.ScrollUpdate.Touch.RendererSwapToBrowserNotified2, + Event.Latency.ScrollUpdate.Wheel.RendererSwapToBrowserNotified2 in M56. + https://crbug.com/649754 + + rbyers@chromium.org + + Time between the renderer starts to swap a frame induced by ScrollUpdate + gesture event and browser receives the swap notification. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68. + + nzolghadr@chromium.org + + Time between initial creation of a wheel/touch event and start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event. + If no swap was induced by the event, no recording is made. The first GSU of + every scrolling sequence is excluded from this metric. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019 due to lack of usage. + + eirage@chromium.org + axantoine@google.com + + Time between the initiation of the last ScrollUpdate event received and its + handling in a frame by the scroll predictor (i.e. rAF time). + + Team: input-dev@chromium.org. + + Warning: Only recorded in a touch context. + + + + + + Removed 04/2020 due to lack of usage. + + eirage@chromium.org + axantoine@google.com + + Time between the handling of the last ScrollUpdate event received in the + frame (i.e. rAF time) and the end of the swap of that frame on the gpu. + + Team: input-dev@chromium.org. + + Warning: Only recorded in a touch context. + + + + + + Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + To be replaced by + Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2 in M57. + https://crbug.com/669618 + + Team: input-dev@chromium.org. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a touch event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. This is going to be + replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing + change made this metric lose its usefulness in Chirp infrastructure. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a touch event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + To be replaced by Event.Latency.ScrollUpdate.Touch.TimeToHandled2 in M56. + https://crbug.com/649754 + + rbyers@chromium.org + + Time between initial creation of a touch event and the generated + ScrollUpdate gesture event is handled on main/impl thread (specified by + suffix). If no swap was induced by the ScrollUpdate gesture event, no + recording is made. + + + + + + Replaced by Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a wheel event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + To be replaced by + Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2 in M57. + https://crbug.com/669618 + + Team: input-dev@chromium.org. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a wheel event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. This is going to be + replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing + change made this metric lose its usefulness in Chirp infrastructure. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68. + + tdresser@chromium.org + + Time between initial creation of a wheel event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. The first GSU of every + scrolling sequence is excluded from this metric. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by + Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + + + + + Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a touch event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. + + + + + + Replaced by Event.Latency.TouchToFirstScrollUpdateSwapBegin. + crbug.com/478845 + + rbyers@chromium.org + + Time between initial creation of a touch event and the frame swap caused by + by the generated ScrollUpdate gesture event if that ScrollUpdate is the + first such in a given scroll gesture event sequence. If no swap was induced + by the event, no recording is made. + + + + + + Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a touch event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + To be replaced by + Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2 in M56. + https://crbug.com/649754 + + Team: input-dev@chromium.org. + + + + + + Replaced by Event.Latency.TouchToScrollUpdateSwapBegin. crbug.com/478845 + + tdresser@chromium.org + + Time between initial creation of a touch event and the frame swap caused by + by the generated ScrollUpdate gesture event. If no swap was induced by the + event, no recording is made. + + + + + + Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a touch event and start of the frame swap + on the GPU service caused by the generated ScrollUpdate gesture event. If no + swap was induced by the event, no recording is made. + + To be replaced by + Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2 in M56. + https://crbug.com/649754 + + Team: input-dev@chromium.org. + + + + + + Replaced by + Event.Latency.ScrollUpdate.Wheel.TimeToFirstScrollUpdateSwapBegin2. + + tdresser@chromium.org + + Time between initial creation of a wheel event and the start of the frame + swap on the GPU service caused by the generated ScrollUpdate gesture event + if that ScrollUpdate is the first such event in a given scroll gesture event + sequence. If no swap was induced by the event, no recording is made. + + + + + + Removed 08/2016, and replaced by Linux.X11.ServerRTT. + + thomasanderson@chromium.org + Time to request a timestamp from the X server. + + + + + Removed 03/2018 due to lack of usage. + + dtapuska@chromium.org + + Number of continuous events (touchmove, mousemove, mousewheel) coalesced + inside the main thread event queue per event. This field is recorded just + before the event is processed on the main thread. + + Team: input-dev@chromium.org. + + + + + + Removed 01/2018 due to lack of usage. + + dtapuska@chromium.org + + Time between when a continuous event (touchmove, mousemove, mousewheel) was + placed into the queue (or coalesced with another event) and when it was + processed on the main thread. + + Team: input-dev@chromium.org. + + + + + + Removed 01/2018 due to lack of usage. + + dtapuska@chromium.org + + Time between when a continuous event (touchmove, mousemove, mousewheel) was + placed into the queue and when it was processed on the main thread. + + Team: input-dev@chromium.org. + + + + + + Expired 2019-07. + + dtapuska@chromium.org + + Whether the Begin Main Frame was not received and the queue generated a + flush queue after a given timeout. + + Team: input-dev@chromium.org. + + + + + + Removed 01/2018 due to lack of usage. + + dtapuska@chromium.org + + Time between when a non-continuous event (not touchmove, mousemove, + mousewheel) was placed into the queue and when it was processed on the main + thread. + + Team: input-dev@chromium.org. + + + + + + Expired 2019-07. + + dtapuska@chromium.org + + Counts the number of event listener invocations that were forced to be + passive due to interventions and whether the invocation of the listener + called prevent default or not. + + Team: input-dev@chromium.org. + + + + + + Removed 08/2016 in Issue 595327, and replaced by + Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling. + + dtapuska@chromium.org + + Time between when a forced non-blocking event was generated and the event + processed. This histogram tracks the benefit of forcing non-blocking events + listeners. + + + + + + Expired 2019-07. + + dtapuska@chromium.org + + Time between when a touchstart or first touchmove event per scroll was + generated and the event processed, for events which were forced non-blocking + since they occurred during fling. This histogram tracks the benefit of + forcing events non-blocking during fling. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 04/2018 due to cancellation of experiment. + + tdresser@chromium.org + + Time between when a touchstart or first touchmove event per scroll was + generated and the event processed, for events which were forced non-blocking + since they occurred while the main thread was unresponsive. This histogram + tracks the benefit of forcing events non-blocking when the main thread is + unresponsive. + + Team: input-dev@chromium.org. + + + + + + Removed as of M80 due to the lack of usage. + + dtapuska@chromium.org + + Time between when a cancelable event was generated and the event processed + yet no action was executed for the event. This histogram tracks the + potential benefit of using passive events listeners. + + Team: input-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 10/2019 due to the completion of the experiment. + + nzolghadr@chromium.org + sarsha@microsoft.com + + On Windows, reports negative time delta between pointer input timestamps + based on TimeNow and the timestamp reported via + PointerInfo.PerformanceCount. This negative time delta is w.r.t to + PerformanceCount. See also + Pen.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Positive. + + + + + + Removed 10/2019 due to the completion of the experiment. + + nzolghadr@chromium.org + sarsha@microsoft.com + + On Windows, reports positive time delta between pointer input timestamps + based on TimeNow and the timestamp reported via + PointerInfo.PerformanceCount. This positive time delta is w.r.t to + PerformanceCount. See also + Pen.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Negative. + + + + + + Removed 06/2017 due to lack of usage. + + dtapuska@chromium.org + + Whether the input IPC messages were discarded before being fully processed + in RenderView's IPC message handler. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2017 due to the completion of the experiment. + + yigu@chromium.org + + Record the area of a scroller upon page load. This is intended to help us + measure the distribution of scrollers with different sizes. Combined with + the other two metrics which measure the size of scrollers on scroll, we may + have a better idea of not compositing small scrollers. + + Team: input-dev@chromium.org, animations-dev@chromium.org. + + + + + + Removed 10/2017 due to the completion of the experiment. + + yigu@chromium.org + + Record the area of a scroller upon ScrollBegin. This is intended to help us + measure the frequencies of different sizes of scrollers getting scrolled. + For those small scrollers that users may rarely scroll, there is no need to + composite them even if we are able to do so. + + Team: input-dev@chromium.org, animations-dev@chromium.org. + + + + + + Removed as of 10/2019 due to no further need of data. + + nzolghadr@chromium.org + dlibby@microsoft.com + + Time (ms) between the pointer down event and when a subsequent pointer move + is recognized as a scroll. + + Team: input-dev@chromium.org + + + + + + Removed as of 1/2018 in issue 650338 (http://crbug.com/650338). Using a + DCHECK instead. + + majidvp@chromium.org + caseq@chromium.org + + Whether the timestamps on input events produced by the windowing system + appear to be sharing the same time base as TimeTicks, modulo possible + roll-over. + + Team: input-dev@chromium.org. + + + + + + Removed 10/2019 due to the completion of the experiment. + + nzolghadr@chromium.org + sarsha@microsoft.com + + On Windows, reports negative time delta between pointer input timestamps + based on TimeNow and the timestamp reported via + PointerInfo.PerformanceCount. This negative time delta is w.r.t to + PerformanceCount. See also + Touch.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Positive. + + + + + + Removed 10/2019 due to the completion of the experiment. + + nzolghadr@chromium.org + sarsha@microsoft.com + + On Windows, reports positive time delta between pointer input timestamps + based on TimeNow and the timestamp reported via + PointerInfo.PerformanceCount. This positive time delta is w.r.t to + PerformanceCount. See also + Touch.InputEventTimeStamp.DeltaBetweenTimeNowAndPerformanceCount.Negative. + + + + + + Removed 05/2016, and replaced by Event.Touch.TargetAndDispatchResult2. + + dtapuska@chromium.org + + An enumeration identifying 3 properties: 1) a classification of the event + target whether it is a root scroll listener (window, document, body) or not; + 2) the result of the dispatch; 3) whether the document was scrollable or + not. + + + + + + Expired 2019-07 + + dtapuska@chromium.org + + An enumeration identifying 4 properties: 1) a classification of the current + target whether it is a root scroll listener (window, document, body) or not; + 2) the result of the dispatch or whether it was previously canceled 3) + whether the document was scrollable or not 4) what phase the listener was + encountered at. This metric is logged during the dispatch of the touch + events. It will only be reported for main frame events that block scrolling, + have only one touch point and current targets that fired an event listener + at that phase. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2019 due to no longer needed. + + eirage@chromium.org + + Records the euclidean distance in dips from a gesture event's original tap + center to its adjusted touch point. 0 if not adjusted. This only records + GestureTap events and GestureLongPress events. + + Team: input-dev@chromium.org. + + + + + + Removed 03/2018 due to no longer needed. + + eirage@chromium.org + + Records if doing touch adjustment on touchstart have same hit test node as + doing touch adjustment on GestureTap. If not, record if one is descendant of + the other. Others means neither of the nodes are descendant of the other. + This only records GestureTap events. + + Team: input-dev@chromium.org. + + + + + + Removed 02/2018 and replaced by Event.Touch.TouchAdjustment.AdjustedNode. + + eirage@chromium.org + + Records if doing touch adjustment on touchstart have same hit test node as + doing touch adjustment on GestureTap. True for same node, false for + different node. This only records GestureTap events. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart events and + the first touchmove events per scroll. Only recorded after the page is fully + loaded. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart events and + the first touchmove events per scroll. Only recorded before the page is + fully loaded. + + Team: input-dev@chromium.org. + + + + + + Removed 08/2016 in Issue 595327, and replaced by + Event.Touch.TouchDispositionsDuringFling2. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart events. Only + recorded while there is an active fling animation. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart and first + touchmove events per scroll. Only recorded while there is an active fling + animation. + + Team: input-dev@chromium.org. + + + + + + Removed 08/2016 in Issue 595327, and replaced by + Event.Touch.TouchDispositionsOutsideFling2. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart events. Only + recorded while there is no active fling animation. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Records the disposition (handled or not handled) of touchstart and first + touchmove events per scroll events. Only recorded while there is no active + fling animation. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between when a touch event was generated and the event was processed. + Recorded only for touchstart events and the first touchmove events per + scroll that occur after the page is fully loaded. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between when a touch event was generated and the event was processed. + Recorded only for touchstart events and the first touchmove events per + scroll that occur before the page is fully loaded. This histogram tracks the + benefit of forcing passive event listeners before the page is fully loaded. + + Team: input-dev@chromium.org. + + + + + + Removed 06/2017 due to lack of usage. + + tdresser@chromium.org + + Time between when a touch event was generated and the event was processed. + Recorded only for touchstart events and the first touchmove events per + scroll when there was no active fling animation. + + Team: input-dev@chromium.org. + + + + + + Removed 08/2016 in Issue 595327, and replaced by + Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling. + + tdresser@chromium.org + + Time between when a touchstart event was generated and the event was + processed. Recorded only when there was an active fling animation. This + histogram tracks the benefit of forcing passive event listeners during + fling. + + + + + + Removed 08/2016 in Issue 595327, and replaced by + Event.Touch.TouchLatencyOutsideFling. + + tdresser@chromium.org + + Time between when a touchstart event was generated and the event was + processed. Recorded only when there was no active fling animation. + + + + + + Removed as of 07/2018. Replaced with Event.VizHitTest.AggregateTimeUs. + + riajiang@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestAggregator to aggregate hit-test data + received from all clients. + + + + + + Removed as of 01/2020. The feature has been launched. + + yigu@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestAggregator to aggregate hit-test data + received from all clients, in microseconds. + + + + + + Removed as of 01/2020. The feature has been launched. + + yigu@chromium.org + event-targeting@chromium.org + + Total number of hit-test regions Viz received from all clients. + + + + + + Removed as of 07/2018. Replaced with Event.VizHitTest.TargetTimeUs. + + riajiang@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestQuery to find a target on a given + location. + + + + + + Removed as of 01/2020. The feature has been launched. + + yigu@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestQuery to find a target on a given + location, in microseconds. + + + + + + Removed as of 07/2018. Replaced with Event.VizHitTest.TransformTimeUs. + + riajiang@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestQuery to transform a location to a given + target's coordinate space. + + + + + + Removed as of 01/2020. The feature has been launched. + + yigu@chromium.org + event-targeting@chromium.org + + Tracks how long it takes for HitTestQuery to transform a location to a given + target's coordinate space, in microseconds. + + + + + + Removed as of 11/2019. The verification path is removed. + + yigu@chromium.org + + This tracks how often the cc layer based hit testing fast path result + matches or doesn't match the asynchronous blink hit test result. + + Team: event-targeting@chromium.org. + + + + + + Removed with M77 and replaced by ExploreSites.SiteTilesClickIndex2. + + dewittj@chromium.org + petewil@chromium.org + + The total index of the selected tile on the ExploreSites page. This measures + how far down from the top it is, counting all the other tiles in cards above + it. This assumes 8 tiles per category, and might skip some valid indices if + fewer tiles are displayed in a category. + + + + + + Removed with M46. + + felt@chromium.org + rdevlin.cronin@chromium.org + + For each pageload, the number of extensions that inject at least one new ad. + + + + + + Removed with M46. + + felt@chromium.org + rdevlin.cronin@chromium.org + + For each pageload, the number of extensions that performed an action that + heuristically looks like injecting an ad, but could not be confirmed. + + + + + + Removed with M46. + + felt@chromium.org + rdevlin.cronin@chromium.org + + For each pageload, the number of extensions that performed an action that + heuristically looks like replacing an ad, but could not be confirmed. + + + + + + Removed with M46. + + felt@chromium.org + rdevlin.cronin@chromium.org + + For each pageload, the number of extensions that remove at least one ad. + + + + + + Removed with M46. + + felt@chromium.org + rdevlin.cronin@chromium.org + + For each pageload, the number of extensions that replace at least one ad. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that inject a content script. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create divs to add to the + page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create 'embed' elements to + add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create iframes to add to + the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create inputs to add to the + page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create links to add to the + page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create 'object' elements to + add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that create script tags to add + to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that use document.write. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that inject a + content script. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create divs + to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create + 'embed' elements to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create + inputs to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create links + to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create + 'object' elements to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that create + script tags to add to the page. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that use + document.write. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that set + innerHTML. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that invoke DOM + methods. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that set the + value of DOM properties via assignments. + + + + + + Removed with M46. + + felt@chromium.org + + For each www.google.com pageload, the number of extensions that read from + the DOM. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that set innerHTML. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that invoke DOM methods. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that set the value of DOM + properties via assignments. + + + + + + Removed with M46. + + felt@chromium.org + + For each pageload, the number of extensions that read from the DOM. + + + + + + Stopped recording in 2019-07. Data was no longer required. + + finnur@chromium.org + + The action taken by the user when seeing the bubble, logged right after the + action is taken. + + + + + + Replaced with ExtensionInstalledLoader.ForceDisabled2. + + Please list the metric's owners. Add more owner tags as needed. + + Counts whether we force-disabled an installed extension at startup because a + policy provider indicated it must remain disabled. + + + + + + Expired 2018-08-30 + + rdevlin.cronin@chromium.org + + Counts whether we force-disabled an installed extension at startup because + it failed ManagementPolicy::MustRemainDisabled check. This checks both + UserMayLoad and MustRemainDisabled methods on a policy provider. + + + + + + Code removed 2020-04. + + N/A. Never properly tracked. + + + + + Code removed 2020-04. + + N/A. Never properly tracked. + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + This is a count of the number of ids that we asked to be signed which the + server response indicated were not in the webstore. + + + + + + Code removed 2020-04. + + N/A. Never properly tracked. + + + + + Code removed 2020-04. + + N/A. Never properly tracked. + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + A count of the number of server requests since Chrome started running, + recorded each time we do a request. NOTE: when interpreting these values, + keep in mind that a user who did 5 server requests during one run of Chrome + will log this histogram 5 times with values 1, 2, 3, 4, and 5. + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether the server result received by the extensions install signer was + valid or invalid. + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + This records the number of seconds since the last time we've done a request + to the server (only during this run of the browser). + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Records how many seconds the browser has been running at the time a request + to the server is made to get a new install signature. + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Logged during InstallVerifier::Init, to indicate the actual enforcement + status used (usually determined by the ExtensionInstallVerifier field trial + experiment, but possibly modified by command line flags). + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Logged during InstallVerifier::Init to indicate the enforcement status as + determined by the ExtensionInstallVerifier field trial experiment. + + + + + + Code removed 2020-04. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The outcome for each call to InstallVerifier::MustRemainDisabled. + + + + + + Code removed 2015-10. + + rdevlin.cronin@chromium.org + + The number of extensions per page that injected an ad and could have been + stopped if the user had declined script injection. This is related to the + ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or + navigation. Only recorded if there was at least one ad injection detected. + + + + + + Removed 2/2014. + + rdevlin.cronin@chromium.org + + The number of extensions which would display an Active Script Running + indiciation to the user. Recorded at page close. + + + + + + Code removed 2015-10. + + rdevlin.cronin@chromium.org + + The number of extensions per page that injected an ad and that could not + have been stopped through script injection permission. This is related to + the ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or + navigation. Only recorded if there was at least one ad injection detected. + + + + + + Code removed 2015-08. + + felt@chromium.org + rdevlin.cronin@chromium.org + The type of ad that was injected. + + + + + Code removed long ago. + + felt@chromium.org + rdevlin.cronin@chromium.org + + The install location of an ad-injecting extension. Recorded upon page close + for any extension that injected ads on that page. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + tjudkins@chromium.org + extensions-core@chromium.org + + Reports whether a URL navigated to by an extension through the extensions + API has the devtools scheme. Reported once per call to tabs.update(), + tabs.create() or browser.openTab(). Also reported from windows.create() and + will be reported once for each url passed to that function. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Captures the results of URL resolution when relative urls are used in the + tabs/windows api. + + + + + + Removed as of 12/2014, replaced by Apps.HostedAppLaunchContainer. + + benwells@chromium.org + tapted@chromium.org + + The number of times apps are launched grouped by + extensions::LaunchContainer. + + + + + + Expired + + rdevlin.cronin@chromium.org + + Time taken to load BackgroundContents for apps at startup when the extension + system notifies that it is ready. + + + + + + Replaced by Extensions.BackgroundPageLoadTime2. + + rdevlin.cronin@chromium.org + The time for an extension's background page to load. + + + + + Removed in M73 after collecting the data necessary. + + ortuno@chromium.org + reillyg@chromium.org + + Records the UUID of the service to which a Chrome App opens a socket + connection. The recorded value is a 31-bit hash of the UUID. These results + will help us better understand the uses of the API and make changes + according to developers' behavior. + + + + + + Removed in M73 after collecting the data necessary. + + ortuno@chromium.org + reillyg@chromium.org + + Records the UUID of a service created by a Chrome App listening for L2CAP + connections. The recorded value is a 31-bit hash of the UUID. These results + will help us better understand the uses of the API and make changes + according to developers' behavior. + + + + + + Removed in M73 after collecting the data necessary. + + ortuno@chromium.org + reillyg@chromium.org + + Records the UUID of a service created by a Chrome App listening for RFCOMM + connections. The recorded value is a 31-bit hash of the UUID. These results + will help us better understand the uses of the API and make changes + according to developers' behavior. + + + + + + Removed 2019/05 as PWA link capturing has been removed. + + mgiuca@chromium.org + ortuno@chromium.org + + Time it takes to retrieve the app for the current URL during a navigation. + + + + + + Removed 2019/05 as PWA link capturing has been removed. + + mgiuca@chromium.org + ortuno@chromium.org + + Time it takes to retrieve the app associated with the window during a + navigation. + + + + + + Removed 2019/05 as PWA link capturing has been removed. + + mgiuca@chromium.org + ortuno@chromium.org + + Time it takes to retrieve the app for the target url during a navigation. + + + + + + Removed 2018/11 in favor of WebApp.Icon.HttpStatusCodeClassOnCreate. + + alancutter@chromium.org + mgiuca@chromium.org + + The HTTP status code class returned for each icon loaded during a + BookmarkApp's creation. + + + + + + Removed 2019/05 in favor of WebApp.Icon.HttpStatusCodeClassOnSync. + + alancutter@chromium.org + mgiuca@chromium.org + + The HTTP status code class returned for each icon loaded when syncing a + BookmarkApp. + + + + + + Removed 2019/05 as PWA link capturing has been removed. + + mgiuca@chromium.org + ortuno@chromium.org + + Number of times navigations into and out of Bookmark Apps are processed, + grouped by their result. + + + + + + Removed 2019/05 as PWA link capturing has been removed. + + mgiuca@chromium.org + ortuno@chromium.org + + The time between the last navigation in the context and us opening a new app + window in response to a new navigation. If it is very small, the context + probably redirected immediately, which is a bad user experience. + + + + + + Logging code has been removed in M77. Some historical data may be found at + (Google-internal, sorry) + https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY + + lukasza@chromium.org + + When an extension violates browsing instance boundaries, this metric records + the extension type. + + This is a temporary metric - probably okay to remove it in M66, after we've + gathered sufficient UMA data in M65. See also https://crbug.com/786411. + + + + + + Logging code has been removed in M77. Some historical data may be found at + (Google-internal, sorry) + https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY + + lukasza@chromium.org + + When an extension violates browsing instance boundaries, this metric records + whether either the source or the target frame was of the extension view type + of VIEW_TYPE_BACKGROUND_CONTENTS. + + This is a temporary metric - probably okay to remove it in M66, after we've + gathered sufficient UMA data in M65. See also https://crbug.com/786411. + + + + + + Logging code has been removed in M77. Some historical data may be found at + (Google-internal, sorry) + https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY + + lukasza@chromium.org + + When an extension violates browsing instance boundaries, this metric records + the extension view type of the source frame. + + This is a temporary metric - probably okay to remove it in M66, after we've + gathered sufficient UMA data in M65. See also https://crbug.com/786411. + + + + + + Logging code has been removed in M77. Some historical data may be found at + (Google-internal, sorry) + https://docs.google.com/document/d/11O-73Hs0avk1xkkULn5HoxtY0gvzz3Ff5I3GFvMI_cY + + lukasza@chromium.org + + When an extension violates browsing instance boundaries, this metric records + the extension view type of the found frame. + + This metric should help confirm or deny the theory that violating browsing + instance boundaries is only needed for looking up background contents / + pages (of VIEW_TYPE_BACKGROUND_CONTENTS type). + + This is a temporary metric - probably okay to remove it in M66, after we've + gathered sufficient UMA data in M65. See also https://crbug.com/786411. + + + + + + Replaced by Extensions.ChromeExtensionsClientInitTime2. + + dbertoni@chromium.org + extensions-core@chromium.org + + The amount of elapsed time taken to initialize the ChromeExtensionsClient. + Recorded once per client initialization, which happens once per instance of + Chrome. + + + + + + Removed 11/2018. Renamed to Extensions.CorruptPolicyExtensionDetected2. + + asargent@chromium.org + + Fires when we detect corruption in an enterprise policy forced install + extension and begin the process of reinstalling it. Compare to + CorruptPolicyExtensionResolved to judge success rate. + + + + + + Removed 01/2020. Replaced by Extensions.CorruptPolicyExtensionDetected3. + + burunduk@chromium.org + lazyboy@chromium.org + poromov@chromium.org + extensions-core@chromium.org + + Fires when we detect corruption in an enterprise policy forced install + extension and begin the process of reinstalling it. Compare to + CorruptPolicyExtensionResolved to judge success rate. + + + + + + Removed 9/2016 by fix for Issue 447040. + + asargent@chromium.org + + Fires when we detect corruption in an enterprise policy forced install + extension. See http://crbug.com/447040 for more background on why we don't + yet disable these. A useful comparison can be made between this value and + the number of policy forced extensions loaded at startup, which is logged in + the EXTERNAL_POLICY_DOWNLOAD bucket of the Extensions.ExtensionLocation + histogram. + + + + + + Removed as of 06/2020. + + waffles@chromium.org + extensions-core@chromium.org + Net error results from URLFetcher. + + + + + Expired. + + waffles@chromium.org + extensions-core@chromium.org + + Number of times chrome retried to download an extension with a url on a + google.com domain, before eventually giving up. + + + + + + Expired. + + waffles@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Number of times chrome retried to download an extension with a url on a non + google.com domain, before eventually giving up. + + + + + + Removed 2020-02. + + waffles@chromium.org + extensions-core@chromium.org + + Number of times chrome retried to download an extension with a url on a + google.com domain, before eventually succeeding. + + + + + + Removed 2020-02. + + waffles@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Number of times chrome retried to download an extension with a url on a non + google.com domain, before eventually succeeding. + + + + + + Removed 2020-02. + + waffles@chromium.org + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Length of the path to the directory under which an extension is installed. + This directory is in the user's profile. + + + + + + Shipped only in M48. Superceded by Extensions.Database.Database.Restore and + Extensions.Database.Value.Restore. + + cmumford@chromium.org + + The result of an attempt to recover from an attempt to open a database that + failed as a result of corruption. + + + + + + Removed Jan 2020 to increase resolution to microseconds. Replaced with + Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension2. + + karandeepb@chromium.org + extensions-core@chromium.org + + Time taken to evaluate the before-request action for a network request for a + single extension ruleset. Emitted for each network request that is visible + to the extension. + + + + + + Removed Dec 2018. Replaced with + Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions2. + + karandeepb@chromium.org + + Time taken to evaluate whether a network request should be blocked or + redirected as per the Declarative Net Request API. This includes the time + taken to evaluate all the extension rulesets. Emitted for non-sensitive + network requests seen by the Extension System. + + + + + + Removed Jan 2020 to increase resolution to microseconds. Replaced with + Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions3. + + karandeepb@chromium.org + extensions-core@chromium.org + + Time taken to evaluate whether a network request should be blocked or + redirected as per the Declarative Net Request API. This includes the time + taken to evaluate all the extension rulesets. Emitted for non-sensitive + network requests seen by the Extension System when there is at least one + active extension ruleset. + + + + + + Removed March 2019. + + karandeepb@chromium.org + + Time taken to index the deserialized json rules provided by an extension + manifest for the Declarative Net Request API. This is emitted whenever an + extension's json ruleset is successfully indexed. This may happen when a + packed extension is installed, an unpacked extension is loaded, an + extension's ruleset is re-indexed due to corruption, etc. + + + + + + Removed April 2020. Replaced with + Extensions.DeclarativeNetRequest.ManifestRulesCount2. + + karandeepb@chromium.org + lazyboy@chromium.org + + The number of indexed declarative rules provided by an extension manifest + for the Declarative Net Request API. This is emitted whenever a packaged + extension with a declarative ruleset is installed or updated. + + + + + + Removed Jan 2020. The addAllowedPages API was removed. + + karandeepb@chromium.org + lazyboy@chromium.org + + Describes the different cases pertaining to initiator checks used by the + Declarative Net Request Page Whitelisting API. Emitted whenever an extension + ruleset is evaluated for a main frame sub-resource request. + + + + + + Removed May 2018. Replaced with + Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions + + karandeepb@chromium.org + + Time taken to evaluate whether a network request should be blocked as per + the Declarative Net Request API. This includes the time taken to evaluate + all the extension rulesets. Emitted whenever a non-sensitive network request + is seen by the Extension System. + + + + + + Removed December 2019. Replaced with + Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension + + karandeepb@chromium.org + + Time taken to evaluate whether a network request should be blocked for a + single extension ruleset. Emitted for each network request that is visible + to the extension. + + + + + + Removed December 2019. Replaced with + Extensions.DeclarativeNetRequest.EvaluateBeforeRequestTime.SingleExtension + + karandeepb@chromium.org + + Time taken to evaluate whether a network request should be redirected for a + single extension ruleset. Emitted for network requests visible to the + extension. + + + + + + Removed May 2018. Replaced with + Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions + + karandeepb@chromium.org + + Time taken to evaluate whether a network request should be redirected as per + the Declarative Net Request API. This includes the time taken to evaluate + all the extension rulesets. Emitted for non-sensitive network requests seen + by the Extension System. + + + + + + Removed 09/2020. + + karandeepb@chromium.org + mmenke@chromium.org + + The type of each WebRequestConditionAttribute created as part of the + declarativeWebRequest API. + + + + + + Removed July 2019. + + karandeepb@chromium.org + + Whether a network request from a guest webview has any declarative web + request rules that need to be evaluated. Emitted whenever a network request + from a guest webview is received at the network layer. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Number of extensions referenced in the depricated external extensions source + at path chrome::DIR_DEPRICATED_EXTERNAL_EXTENSIONS. + + + + + + There is no such thing as an extension dialog. + + Please list the metric's owners. Add more owner tags as needed. + The time for a dialog-hosted extension to load. + + + + + Expired 2018-08 + + rdevlin.cronin@chromium.org + + Records the Chrome channel when JavaScript exceptions are not gracefully + dealt with, and suppressed by C++ instead. These are exceptions generated + (or simply not caught and gracefully recovered) in our own internal + JavaScript, not from JavaScript code written by developers (that which is + typically hosted in CRX files). This should be 0 for unstable channels like + canary and dev, because we try *not* to suppress errors and instead kill the + renderer and generate a crash report. However, at times we need to suppress + even those. Note that this histogram is intended to be tracked over time, + per channel, to observe crash rates. Comparisons between + stable/beta/dev/canary are unlikely to be meaningful. + + + + + + Removed 03/2017 because miscounting IGNORE histogram entry. This error is + fixed with DisabledUIUserResponse2. + + rdevlin.cronin@chromium.org + + User response to the dialog shown when an extension is disabled due to an + update requiring more permissions. + + + + + + Removed 03/2017 because miscounting IGNORE histogram entry. This error is + fixed with DisabledUIUserResponseRemoteInstall2. + + mek@chromium.org + + User response to the dialog shown when an extension is disabled due to it + having been installed remotely. + + + + + + Removed 2019-06. + + rdevlin.cronin@chromium.org + + The state of the toolbar icon for the docs offline extension (visible in the + toolbar, overflowed in the menu, or the extension is disabled). Recorded + once per startup per (non-incognito) profile. + + + + + + Obsolete since the enhanced bookmarks manager is no longer using an event + page. + + wittman@chromium.org + + The number of event listeners the Enhanced Bookmarks Manager has, measured + at profile startup. A value of 0 implies that Chrome has a general bug with + event page management, since the bookmarks manager should always have at + least one event listener - but a bug with event page management that affects + the bookmarks manager is particularly dire. + + + + + + Replaced by Extensions.EventPageActiveTime2. + + rdevlin.cronin@chromium.org + The time an extension's event page has spent loaded. + + + + + Replaced by Extensions.EventPageLoadTime2. + + rdevlin.cronin@chromium.org + The time for an extension's event page to load. + + + + + Removed 21-Jan-2020. + + mfoltz@chromium.org + + Recorded every time an event is dispatched to a *component* extension with a + suspended event page. Otherwise identical to + Extensions.Events.DispatchWithSuspendedEventPage. + + + + + + Removed 2019-05. + + rdevlin.cronin@chromium.org + + The amount of time taken to create a single extension object. This includes + parsing all the different extension manifest keys and initializating the + associated manifest data. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M77. + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + True if the cache of the extension frame map was hit during access on the IO + thread. + + + + + + Removed in M77. + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + True if the lookup for a frame in the extension frame map succeeded after a + cache miss. + + + + + + Removed 2019-11 + + rdevlin.cronin@chromium.org + + The maximum number of ExtensionHosts (primarily background/event pages) that + were actively loading at any one time, within the first minute of Chrome + startup. Emitted exactly one minute after startup. + + + + + + Removed 2019-11 + + rdevlin.cronin@chromium.org + + The maximum number of ExtensionHosts (primarily background/event pages) in + the queue awaiting being loaded (via an ExtensionHostQueue), within the + first minute of Chrome startup. Emitted exactly one minute after startup. + + + + + + Removed 2019-11 + + rdevlin.cronin@chromium.org + + The total number of ExtensionHosts that completed loading in the first + minute of Chrome startup. Emitted exactly one minute after startup. + + + + + + Removed 2019-11 + + rdevlin.cronin@chromium.org + + The total number of ExtensionHosts (primarily background/event pages) that + were added to a queue to start loading, within the first minute of Chrome + startup. These may or may not end up starting, let alone finishing, + depending on the queue behavior. Emitted exactly one minute after startup. + + + + + + Removed 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during ExtensionManagement::Refresh. + + + + + + Removed 4/2016. ExtensionRendererState was replaced with ExtensionFrameMap. + + rdevlin.cronin@chromium.org + + True if the cache for the ExtensionRendererState was hit during a lookup. + + + + + + Expired. + + waffles@chromium.org + + Records the error codes of the extension updater update check errors. These + events are triggered only when the extension updater gets an error for the + first time (before any retry) in the update check phase for a google.com + domain. + + + + + + Expired. + + waffles@chromium.org + + Records the error codes of the extension updater update check errors. These + events are triggered only when the extension updater gets an error for the + first time (before any retry) in the update check phase for a non google.com + domain. + + + + + + Expired. + + waffles@chromium.org + + The number of extensions that are checked for update. This number is emitted + right before the extensions are split between the current extension updater + and the unified extension updater (if used). + + + + + + Expired. + + waffles@chromium.org + + The number of extensions that are passed over to the extension updater for + update check. Triggered when the extension updater starts doing update + check. + + + + + + Expired. + + waffles@chromium.org + + The number of extensions that have updates in an update check session. + Triggered when the extension updater found an update for an extension. + + + + + + Removed 2020-02. + + waffles@chromium.org + + Records the update results of extensions in an extension updater session, + grouped by ExtensionUpdaterUpdateResult. + + + + + + Expired 2018-08. + + rdevlin.cronin@chromium.org + + Whether or not the uninstallation of an external extension succeeded. + Triggered when the external install warning is shown to the user and the + user selects to remove the extension. + + + + + + Expired after M77. + + xiaohuic@chromium.org + + Record the time taken to physically move the extention files from temporary + location to the final installation directory. It includes the time to flush + the file system if ExtensionUseSafeInstallation field trial is enabled. This + is recorded once per extension install/update. + + + + + + Removed 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the FontSettingsEventRouter + construction. + + + + + + Removed 07/2020, replaced by + Extensions.ForceInstalledFailureManifestInvalidErrorDetail2. + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The detailed reason why enterprise policy forced extensions had failed to + install because fetched update manifest was invalid. Recorded for each + forced extension that failed to install after 5 minutes with + Extensions.ForceInstalledFailureReason2 equal to MANIFEST_INVALID. + + + + + + Removed 12/2019, replaced by Extensions.ForceInstalledFailureReason3. + + askaraitzhan@google.com + burunduk@chromium.org + poromov@chromium.org + rdevlin.cronin@chromium.org + + The reason why enterprise policy forced extensions were not installed. + Recorded for each forced extension that failed to install after 5 minutes. + Recorded together with "Extensions.ForceInstalledTimedOutCount" + histogram, but for every extension not installed at the moment. + + + + + + Removed 04/2020, replaced by Extensions.ForceInstalledFailureReason3. + + + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The reason why enterprise policy forced extensions were not installed. + Recorded for each forced extension that failed to install after 5 minutes. + Recorded together with "Extensions.ForceInstalledTimedOutCount" + histogram, but for every extension not installed at the moment. + + Replaced Extensions.ForceInstalledFailureReason because of splitting + CRX_FETCH_FAILED options into three dirrerent failures. + + + + + + Removed 2020-08-28 because it is verified from the collected statistics that + we always receive "no update" status in case of + CRX_FETCH_URL_EMPTY. + + swapnilgupta@google.com + burunduk@chromium.org + managed-devices@google.com + + The update check status details for enterprise policy forced extensions when + update manifest is fetched from server. Recorded for each forced extension + that failed to install after 5 minutes. + + + + + + Removed 2020-08-28, replaced by Extensions.ForceInstalledHttpErrorCode2. + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + HTTP error code for the last retry attempt when CRX fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + CRX_FETCH_FAILED and a HTTP response code was received. HTTP response code + is received only if there was no network error. + + + + + + Removed 2020-08-28, replaced by + Extensions.ForceInstalledManifestFetchFailedHttpErrorCode2. + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + HTTP error code for the last retry attempt when Manifest fetch failed for + enterprise policy forced extensions. Recorded for each forced extension that + failed to install after 5 minutes with + Extensions.{OffStore,WebStore}_ForceInstalledFailureReason3 equal to + MANIFEST_FETCH_FAILED and a HTTP response code was received. HTTP response + code is received only if there was no network error. + + + + + + Removed 09/2020, replaced by Extensions.ForceInstalledStage2. + + burunduk@chromium.org + swapnilgupta@google.com + managed-devices@google.com + + The last known stage of extension installation process if failure reason was + not recorded (installation of an extension was neither yet finished nor + failed). Recorded for each forced extension that failed to install after 5 + minutes. Recorded together with + "Extensions.ForceInstalledTimedOutCount" histogram, but for every + extension not installed at the moment. + + + + + + Replaced by Extensions.Functions.ComponentExtensionCalls, + Extensions.Functions.ExtensionCalls, and Extensions.Functions.WebUICalls + 2019-05. + + rdevlin.cronin@chromium.org + Number of calls to extension functions. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + What happens when the extensions system tries to get a temp dir to unpack + in? + + + + + + Code removed 2020-06. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Whether there were any permissions present in an extension when installation + from the web store was aborted (e.g. because the parent window of the + confirmation dialog went away), not including installation errors and user + cancels. To find places where this histogram may be emitted, look for calls + to ExtensionService::RecordPermissionMessagesHistogram with the argument + WebStoreInstallAbort. + + + + + + Expired 2018-08 + + rdevlin.cronin@chromium.org + + The usage (in kilobytes) of persistent storage in a hosted app with the + unlimitedStorage permission. This is logged each time the storage is used*, + so this also serves as a cap of the number of calls that would fail if the + app did not have the unlimited storage permission. *Capped at once per 30 + seconds so as to not impact performance. + + + + + + Expired 2018-08 + + rdevlin.cronin@chromium.org + + The percentage of "normal" (that is, not unlimited) quota that a + hosted app with unlimited storage is currently using. This is logged each + time the storage is used*, so the number of times the app would use greater + than 100% of the default storage can serve as a cap for the number of calls + that would fail if the app did not have the unlimitedStorage permission. + *Capped at once per 30 seconds so as to not impact performance. + + + + + + Expired 2018-08-30 + + rdevlin.cronin@chromium.org + + The usage (in kilobytes) of a hosted app with the unlimitedStorage api + permission, recorded once per run per app the first time we load storage for + the hosted app. This is separate from the other metrics on hosted app + unlimited storage usage because it is logged once per extension per run. + + + + + + Removed 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during + ExtensionPrefs::InitExtensionControlledPrefs. + + + + + + Removed 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during ExtensionPrefs::InitPrefStore. + + + + + + Removed 03/2017 in favor of Extensions.InjectedScriptExecutionTime. + + rdevlin.cronin@chromium.org + Time taken to inject all scripts by extensions. + + + + + Obsolete as of 2019-05 as it can be derived by comparing the aggregate + counts of Extensions.InstallPrompt.TimeToInstall and + Extensions.InstallPrompt.TimeToInstall. + + meacer@chromium.org + + Whether the user accepted or aborted an extension installation. + + + + + + Stopped recording 2019-07. The previous enum was garbled. + + meacer@chromium.org + + Type of the extension install prompt displayed when an extension + installation is triggered. + + + + + + Removed as of 2019-11. Replaced by Extensions.LoadAllTime2. + + rdevlin.cronin@chromium.org + + Time taken to load all non-component extensions at profile open. This + happens as part of the total initialization time of ExtensionService, + measured in Extensions.ExtensionServiceInitTime. + + + + + + Removed as of 4/2015. Replaced by ManagedUsers.Whitelist.Count. + + asargent@chromium.org + + The number of content-pack extensions loaded at profile open. + + + + + + Removed June 2019. + + ksakamoto@chromium.org + + The amount of time taken to inject content scripts. If multiple scripts are + injected within a single task, this records the time taken to execute all + the scripts. + + This metric only logs tasks longer than 50 milliseconds. This threshold + aligns with the definition of "long task" in Long Tasks API + (https://w3c.github.io/longtasks/). + + Note that this histogram itself doesn't tell you what percentage of content + scripts are greater than 50 ms. See Extensions.Inject{Start,End,Idle}_Time + and Extensions.InjectedScriptExecutionTime.* for the overall distribution. + + + + + + Removed January 2020. + + rdevlin.cronin@chromium.org + nharper@chromium.org + + The behavior for including the TLS channel ID in the information sent with + extension messaging. Recorded once per opened channel. + + + + + + Removed June 2019. + + battre@chromium.org + + Time that network requests were blocked due to relevant rule registries + loading. + + + + + + Never used. Added to source 06/2012. Removed from source and added here + 09/2016. + + + Delay of network requests due to waiting for extension declarativeWebRequest + rules to be loaded from disk at startup. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_AutoDisable2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it is automatically disabled + due to a permission increase (e.g., after an extension upgrade). + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_AutoDisable3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it is automatically disabled + due to a permission increase (e.g., after an extension upgrade). + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_Install2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was installed. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_Install3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was installed. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_InstallAbort2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation was aborted, not + including installation errors and user cancels. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_InstallAbort3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation was aborted, not + including installation errors and user cancels. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_InstallCancel2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation was canceled. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_InstallCancel3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation was canceled. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_Load2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + The permissions present in an extension when it was loaded. + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_Load3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + The permissions present in an extension when it was loaded. + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_ReEnable2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was re-enabled from a + confirmation prompt. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_ReEnable3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was re-enabled from a + confirmation prompt. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_ReEnableAbort2. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when the re-enable prompt was + aborted, not including installation errors and manual user cancels. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_ReEnableAbort3. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The permissions present in an extension when the re-enable prompt was + aborted, not including installation errors and manual user cancels. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_ReEnableCancel2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when the re-enable was canceled from + the confirmation prompt. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_ReEnableCancel3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when the re-enable was canceled from + the confirmation prompt. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_Uninstall2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was uninstalled. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_Uninstall3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was uninstalled. + + + + + + Removed as of 5/2014, replaced by Extensions.Permissions_WebStoreInstall2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was installed through the + web store. + + + + + + Removed as of 6/2015, replaced by Extensions.Permissions_WebStoreInstall3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when it was installed through the + web store. + + + + + + Removed as of 5/2014, replaced by + Extensions.Permissions_WebStoreInstallAbort2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation from the web store + was aborted, not including installation errors and user cancels. + + + + + + Removed as of 6/2015, replaced by + Extensions.Permissions_WebStoreInstallAbort3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation from the web store + was aborted, not including installation errors and user cancels. + + + + + + Removed as of 5/2014, replaced by + Extensions.Permissions_WebStoreInstallCancel2. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation from the web store + was canceled. + + + + + + Removed as of 6/2015, replaced by + Extensions.Permissions_WebStoreInstallCancel3. + + rdevlin.cronin@chromium.org + rpaquay@chromium.org + + The permissions present in an extension when installation from the web store + was canceled. + + + + + + Replaced by Extensions.PopupLoadTime2. + + rdevlin.cronin@chromium.org + The time for an Extension's popup to load. + + + + + Replaced by Extensions.ProcessManagerStartupHostsTime2 - 12/2019 + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The time taken to start up persistent background pages for extensions in + ExtensionProcessManager when the extension system notifies that it is ready. + + + + + + Stopped recording 2019-07. Data no longer needed. + + extensions-core@chromium.org + + The initialization latency (in milliseconds) introduced to each extension + resource request by querying the directory timestamp. + + + + + + Can be inferred from SandboxUnpackFailureReason. + + extensions-core@chromium.org + + Count the number of times a sandboxed extension unpack fails. + + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Time taken to unpack an extension, when the unpack fails. + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Length of the initial path to the CRX to be unpacked. + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Length of the normalized (link/junction free) path to the temporary copy of + a CRX made during unpacking. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which a CRX file is unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files 1MB to 2MB are unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files 2MB to 5MB are unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files 50kB to 1MB are unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files 5MB to 10 MB are unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files larger than 10MB are unpacked in Kilobytes per + second. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + + Rate at which CRX files under 50 KB are unpacked in Kilobytes per second. + + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Count the number of times a sandboxed CRX unpack succeeds, but we can't get + the file size. + + + + + + Code removed 2020-04. + + extensions-core@chromium.org + Size of the .crx file, in KB, when the unpack succeeds. + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Time taken to unpack an extension, when the unpack succeeds. + + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + Length of the path of the temporary copy of a CRX made during unpacking. + + + + + + Code removed 2020-04. No longer being monitored. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + Length of the path under which a CRX is unpacked. + + + + + Removed in September, 2016 + + + Emitted when QuotaExceededError was called due to an extension using too + many bytes for a given setting. The number has no natural numerator + (normalizing factor) and thus is not particularly useful. + + + + + + Removed in September, 2016 + + + Emitted when QuotaExceededError was called due to an extension using too + many keys. The number has no natural numerator (normalizing factor) and thus + is not particularly useful. + + + + + + Removed in September, 2016 + + + Emitted when QuotaExceededError was called due to an extension using too + many bytes. The number has no natural numerator (normalizing factor) and + thus is not particularly useful. + + + + + + Removed in July 2019. + + alexmos@chromium.org + + When the web-accessible resource check in + ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this + records the reason for the failure. This check is performed on navigations + that utilize the OpenURL path as well as on transfers. + + + + + + Removed in July 2019. + + alexmos@chromium.org + + When the web-accessible resource check in + ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this + records the scheme of the SiteInstance that initiated the blocked load. This + check is performed on navigations that utilize the OpenURL path as well as + on transfers. + + + + + + This has not been recorded since at least mid-2013. + + asargent@chromium.org + The time one extension delays network requests at startup. + + + + + This has not been recorded since at least mid-2013. + + rdevlin.cronin@chromium.org + + The total time extensions delay network requests at startup. + + + + + + Removed 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during StorageFrontend::Init. + + + + + + Expired 2018-08. + + rdevlin.cronin@chromium.org + + The total number of network requests that were delayed by extension user + script load. Recorded once each time network requests may have been delayed + by user script load (i.e., once at the end of each batch of script loads). + + + + + + Removed June 2019. + + ksakamoto@chromium.org + + Time elapsed between two asynchronously-injected content script runs. + + + + + + Replaced by Extensions.Toolbar.PinnedExtensionCount2 in 2020/05. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of extensions that the user has pinned on the toolbar. Recorded + once per profile during initialization. + + + + + + Replaced by Extensions.Toolbar.PinnedExtensionPercentage2 in 2020/05. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The percentage of extensions that the user has pinned to the toolbar (i.e., + this will be 100 if the user has every extension pinned). Recorded once per + profile during initialization. + + + + + + Replaced by Extensions.Toolbar.PinnedExtensionPercentage3 in 2020/05. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The percentage of extensions that the user has pinned to the toolbar (i.e., + this will be 100 if the user has every extension pinned). Recorded once per + profile during initialization if the user has at least one extension with an + action in the toolbar. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Time taken to load a toolstrip. + + + + + Removed 2020-02. + + waffles@chromium.org + + Records the error codes of the unified extension updater download errors. + These events are triggered when the extension updater fails to download the + extension update package of an extension, which can happen only after the + updater has successfuly determined that there is an update for the + extension. + + + + + + Expired. + + waffles@chromium.org + + The number of extensions that are passed over to the unified extension + updater for update check. Triggered when the new extension updater starts + doing update check. + + + + + + Removed 2020-02. + + waffles@chromium.org + + Records the error codes of the unified extension updater update check + errors. These events are triggered only when the new extension updater gets + an error in the update check phase. + + + + + + Removed 2020-02. + + waffles@chromium.org + + Records the update results of extensions in an unified extension updater + session, grouped by ExtensionUpdaterUpdateResult. + + + + + + Removed 2020-02. + + waffles@chromium.org + + The update service errors that the update service encouters during an update + check session using update client. + + + + + + Stopped recording 2019-07. + + extensions-core@chromium.org + + Count failing CRX installs, grouped by the way an extension can be + installed. + + + + + + Code removed 2020-06. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The install source of an extension that failed to unpack correctly. Emitted + each time an extension fails to unpack from the CrxInstaller. + + + + + + Stopped recording 2019-07. + + extensions-core@chromium.org + + Count successful CRX installs, grouped by the cause of the install. + + + + + + Code removed 2020-06. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The install source of an extension that succeeded in unpacking correctly. + Emitted each time an extension successfully unpacks from the CrxInstaller. + + + + + + Removed 2019-01. + + waffles@chromium.org + Time in minutes between update checks. + + + + + Removed 3/2018 in https://crbug.com/357781 with the removal of the + extensions-update-frequency command line flag. + + catmullings@chromium.org + + Logs whether or not the extensions-update-frequency command line flag is + used. Recorded at profile creation if extensions autoupdate is enabled. + + + + + + Expired. + + waffles@chromium.org + + Counts the number of entries with the same extension ID found in the update + manifest of an update check request. When the update manifest does not + contain any update entry for an extension ID in the update check request, + the count will be 0. + + + + + + Expired. + + waffles@chromium.org + + The number of prodversionmin attributes appearing in an update manifest of + an update check request. + + + + + + Removed 10/2013. + + Please list the metric's owners. Add more owner tags as needed. + + What happened when the extension updater tried to write a file? + + + + + + Removed November 2018. Replaced with Extensions.WebRequest.InitiatorAccess2. + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Describes the different cases pertaining to host permissions check for the + initiator URL of a network request. This is emitted whenever an extension is + found to have access to a request url, when checked by the WebRequest API. + + + + + + Removed April 2019. + + karandeepb@chromium.org + rdevlin.cronin@chromium.org + + Describes the different cases pertaining to host permissions check for the + initiator URL of a network request. This is emitted whenever an extension is + found to have access to a request url for the WebRequest or Declarative Net + Request API. + + + + + + Removed 11/2018 as this is no longer needed. + + rockot@chromium.org + + Tracks whether any interesting response header modifications were made for + each request seen by the Web Request API. Logged for every network request + as long as one or more enabled extensions is using a declarative or blocking + filter to process onHeadersReceived events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M69. + + + + + + Removed May 2019. + + cduvall@chromium.org + karandeepb@chromium.org + + Whether the set-cookie response header was changed by an extension using the + Web Request API. Logged for every network request as long as one or more + enabled extensions is using a declarative or blocking filter to process + onHeadersReceived events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M73. + + + + + + Removed May 2019. + + cduvall@chromium.org + karandeepb@chromium.org + + Whether the set-cookie response header was removed by an extension using the + Web Request API. Logged for every network request as long as one or more + enabled extensions is using a declarative or blocking filter to process + onHeadersReceived events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M73. + + + + + + Removed 11/2018 as this is no longer needed. + + rockot@chromium.org + + Whether either or both of the special Accept-Language or User-Agent request + headers were removed by an extension using the Web Request API. Logged for + every network request as long as one or more enabled extensions is using a + declarative or blocking filter to process onBeforeSendHeaders events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M69. + + + + + + Removed April 2019. + + cduvall@chromium.org + karandeepb@chromium.org + + Whether Accept-Language, Accept-Encoding, User-Agent, Cookie, Referer, or + mulitple of these request headers were changed by an extension using the Web + Request API. Logged for every network request as long as one or more enabled + extensions is using a declarative or blocking filter to process + onBeforeSendHeaders events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M73. + + + + + + Removed April 2019. + + cduvall@chromium.org + karandeepb@chromium.org + + Whether Accept-Language, Accept-Encoding, User-Agent, Cookie, Referer, or + mulitple of these request headers were removed by an extension using the Web + Request API. Logged for every network request as long as one or more enabled + extensions is using a declarative or blocking filter to process + onBeforeSendHeaders events. + + This histogram is temporary, for investigating https://crbug.com/827582. It + can probably be removed by M73. + + + + + + Removed as of Jan 2019. + + yhirano@chromium.org + + Whether cookies on a websocket connection are modified in + OnBeforeSendHeaders. + + This histogram is temporary, for investigating https://crbug.com/827582. + + + + + + Removed as of Jan 2019. + + yhirano@chromium.org + + Whether cookies on a websocket connection are modified in OnHeadersReceived. + + This histogram is temporary, for investigating https://crbug.com/827582. + + + + + + Removed as of Jan 2019. + + yhirano@chromium.org + ricea@chromium.org + + Whether certain headers are modified in OnBeforeSendHeaders. + + + + + + Removed as of Jan 2019. + + yhirano@chromium.org + + Tracks request headers modifications on a websocket connection in + OnBeforeSendHeaders. + + This histogram is temporary, for investigating https://crbug.com/827582. + + + + + + Removed as of Jan 2019. + + yhirano@chromium.org + + Whether response headers on a websocket connection are modified in + OnHeadersReceived. + + This histogram is temporary, for investigating https://crbug.com/827582. + + + + + + Removed as of 11/2017. No longer relevant after refactoring. + + rdevlin.cronin@chromium.org + + Whether or not the render frame lookup for a given webRequest event + succeeded. + + + + + + Expired after M77. + + xiaohuic@chromium.org + + The time spent to download the crx file from the webstore to local disk. + This is recorded once per successful download. + + + + + + Removed as of 09/2018, with the removal of the "Zip Unpacker" + component extension. + + yamaguchi@google.com + + Records the reason why the ZIP unpacker extension was disabled when the + service attempted to re-enable the extension upon startup. Each entry + indicates that the extension was disabled unintentionally and a fix was + attempted. + + + + + + Stopped recording 2019-07. + + finnur@chromium.org + + The number of Browser Action icons the user has elected to permanently hide + (as opposed to putting them in the overflow bucket). Measured once per + startup per (non-incognito) profile. + + + + + + Removed at 07/2019 because refactored DataPipeProducer does not provide the + net::Error code any more, and it reaches the planned expiry milestone. + + extensions-core@chromium.org + + The error code for failures of incremental reads of a file stream for a + chrome-extension:// URL. (See also ExtensionUrlRequest.OnReadCompleteResult + for the success case). + + + + + + Removed at 07/2019 because refactored DataPipeProducer does not provide the + reported value, and this metric was already broken, reporting always 0. + + lazyboy@chromium.org + extensions-core@chromium.org + + The result of an incremental read of a file stream for a chrome-extension:// + URL, representing a byte count. Logged in success cases (see also + ExtensionUrlRequest.OnReadCompleteError). + + + + + + Removed as of 12/2017. + + fhorschig@chromium.org + + Records the number of favicon link tags on a page once the page has finished + loading. The count includes the automatically added favicon.ico entry. + + + + + + Removed as of 12/2017. + + fhorschig@chromium.org + + Records the number of favicon link tags with a non empty sizes attribute + once the page has finished loading. + + + + + + Removed as of 12/2017. + + fhorschig@chromium.org + + Records the number of apple-touch-icon and apple-touch-icon-precomposed link + tags once the page has finished loading. + + + + + + Removed as of 12/2017. + + fhorschig@chromium.org + + Records the number of icons requested until the best-fitting candidate was + found or there were no candidates left to check. More than 15 attempts are + unlikely and will be stored in overflow bucket 16. Less than 1 attempt means + an error happened; these cases are in bucket 0. + + + + + + Removed as of 12/2017. + + fhorschig@chromium.org + + Records whether a download succeeded, failed or was skipped because it has + failed previously. + + + + + + Removed 2020-02. + + treib@chromium.org + melandory@chromium.org + + Recorded whenever the GCM client announces that some FCM messages were + deleted. Note that this does not record the number of deleted messages. + + + + + + Replaced in 2019-12 by FCMInvalidations.TokenStateOnRegistrationRequest2. + This first version did not record the "Token was cleared" bucket. + + melandory@chromium.org + treib@chromium.org + + Records the outcome of instance ID token requests (i.e. whether the token + changed). Such requests are made when invalidations are first enabled (e.g. + on sign-in), and then periodically every 24 hours. + + + + + + Removed in favor of ContentSuggestions.Feed.Offline.GetStatusCount. + + skym@chromium.org + + The number of urls that have offline status requested per call. + + + + + + Removed in favor of ContentSuggestions.Feed.Offline.GetStatusDuration. + + skym@chromium.org + + The number of milliseconds to round trip offline status for a set of URLs + from Offline Pages component. + + + + + + Removed in favor of ContentSuggestions.Feed.Scheduler.RefreshTrigger. + + skym@chromium.org + + The scheduler watches for various triggers, which cause it to decide if a + refresh is currently warranted or not. This histogram is emitted when a + trigger causes a refresh. + + + + + + Removed in favor of ContentSuggestions.Feed.Scheduler.RequestBehavior. + + skym@chromium.org + + When NTP is opened, the scheduler host tells the Feed library how to act, if + the existing content should be shown, immediately or with timeout, and if a + refresh request should be started. + + + + + + Depcreated as of 08/2019. Replaced by + Feedback.HappinessTrackingSurvey.BubbleUsage. + + jeffreycohen@chromium.org + cyflee@chromium.org + + Reports on the responses to showing Happiness Tracking Surveys (HaTS) to a + subset of users. Records each time HaTS is shown. + + + + + + Was removed from the code at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser - Specific actions taken by user such initiating + cloud import, canceling import, selecting a directory, or opting-in to + Drive>Photos sync. + + + + + + Removed 2020-09. + + joelhockey@chromium.org + tbuckley@chromium.org + Dialog shown when using crostini app to open a file. + + + + + Removed 2020-09. + + joelhockey@chromium.org + tbuckley@chromium.org + + The depth from volume root of the path being shared. This is equivalent to + how many '/' are in the path. E.g. 'Downloads' or 'My Drive' has depth 0. + 'Downloads/foo/bar' has depth 2. + + + + + + The bug which the UMA was investigating got fixed. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: time from the SuspendDone event to the DiskRemoved + event. The UMA is added temporarily for crbug.com/433734. + + + + + + The bug which the UMA was investigating got fixed. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: time from the DiskRemoved event to the Suspend + event. The UMA is added temporarily for crbug.com/433734. + + + + + + Removed 2020-09. + + joelhockey@chromium.org + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS File Browser: time to start and mount the crostini container in + order to show Linux Files. + + + + + + Removed 4/2013, and replaced by FileBrowser.ViewingFileType. + + slangley@chromium.org + weifangsun@chromium.org + File types that were tried to be opened through browser. + + + + + Code seems to have been removed at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Import flow: action chosen in the Action Choice dialog for + the external device. + + + + + + Code seems to have been removed at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Import flow: the number of photos imported. Measured on + every successfull import operation. + + + + + + Code seems to have been removed at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Import flow: the percent of photos imported among all the + photos on the device. Measured on every successfull import operation. + + + + + + Code seems to have been removed at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Import flow: time to load the action dialog. Measured + between the moment window appears and the moment user see all available + actions for the device. + + + + + + Code seems to have been removed at an unknown time. + + slangley@chromium.org + weifangsun@chromium.org + + Chrome OS Photo Import flow: time to scan the external device. + + + + + + Removed July 2019. + + alexmos@chromium.org + + Logged when we fail the permission validation of the filesystem URL origin, + from ChildProcessSecurityPolicy::HasPermissionsForFileSystemFile. This is + not expected to happen in normal operation. + + + + + + Removed from code March 2019. + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the email interstitial of the onboarding + process. We record that the page was seen and what action the user took. + + + + + + Removed from code April 2019. + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the Email Providers new user experience. + We record the number of times the page is seen, how they interacted with the + page (i.e. interacting with presented options and button clicks), and + through what method they leave the page (i.e. confirm, cancel, neither). The + new user experience should only be shown once to new profiles. Hence, the + leaving method should be recorded at most once. + + + + + + Removed from code April 2019. + + hcarmona@chromium.org + scottchen@chromium.org + + Records what email provider was selected as part of the Email Providers New + User Experience. Histogram is only recorded when a user confirms adding an + email provider. + + + + + + Removed 2020-04. + + tedchoc@chromium.org + + The amount of time (in minutes) that the app was in the background before + the user started it (via an ACTION_MAIN intent) and performed a user action + that describes the intent of resuming the app. Only recorded if the action + took place within the first 10 seconds of starting Chrome. The actions are + further described in the FirstUserActionTypes suffix. + + + + + + Removed 2019-09. Enough data has been collected for investigation of + https://crbug.com/876306 + + droger@chromium.org + msarda@chromium.org + + + + Reports the network error code for requests to the ListAccounts Gaia + endpoint. There are suffixes for individual tries (0 is the initial request, + and 1-8 are retries). + + + + + + Removed 2019-09. Enough data has been collected for investigation of + https://crbug.com/876306 + + droger@chromium.org + msarda@chromium.org + + Reported when a request to the ListAccounts Gaia endpoint fails to complete + for network reasons (i.e. when the error is not OK). This histogram can be + used in conjunction with + "Gaia.AuthFetcher.ListAccounts.ProcessUptime.Success" in order to + compute the failure rate of ListAccounts depending on the process uptime + (measured as a base::TimeDelta between the start of the process and the + start of the request). + + + + + + Removed 2019-09. Enough data has been collected for investigation of + https://crbug.com/876306 + + droger@chromium.org + msarda@chromium.org + + Reported when a request to the ListAccounts Gaia endpoint completes without + network error (i.e. when the network error is OK). This histogram can be + used in conjunction with + "Gaia.AuthFetcher.ListAccounts.ProcessUptime.Error" in order to + compute the failure rate of ListAccounts depending on the process uptime + (measured as a base::TimeDelta between the start of the process and the + start of the request). + + + + + + Removed 2019-09. Enough data has been collected for investigation of + https://crbug.com/876306 + + droger@chromium.org + msarda@chromium.org + + Reported when a request to the ListAccounts Gaia endpoint fails to complete + for network reasons (i.e. when the network error is not OK). This histogram + can be used in conjunction with + "Gaia.AuthFetcher.ListAccounts.SystemUptime.Success" in order to + compute the failure rate of ListAccounts depending on the system uptime + (measured as a base::TimeDelta between the start of the system and the start + of the request). + + + + + + Removed 2019-09. Enough data has been collected for investigation of + https://crbug.com/876306 + + droger@chromium.org + msarda@chromium.org + + Reported when a request to the ListAccounts Gaia endpoint completes without + network error (i.e. when the network error is OK). This histogram can be + used in conjunction with + "Gaia.AuthFetcher.ListAccounts.SystemUptime.Error" in order to + compute the failure rate of ListAccounts depending on the system uptime + (measured as a base::TimeDelta between the start of the system and the start + of the request). + + + + + + No longer recorded as of M86. + + msarda@chromium.org + droger@chromium.org + chrome-signin-team@google.com + + Number of successful requests preceding a bad request for an OAuth2 refresh + token. + + + + + + Removed as of 01/2018. Use Gamepad.KnownGamepadConnectedWithId instead. + + mattreynolds@chromium.org + + Records an enumeration value that can be used to identify the connected + device from a list of known gamepads. Reported when a device with a vendor + and product ID matching a known gaming input device is detected during + Gamepad API enumeration. + + + + + + Removed as of 01/2016. The error has been fixed by GCM. (crbug/580367) + + khushalsagar@chromium.org + Result of a message received by the GcmReceiver on Android. + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of times when gcm.unregister API is called. + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Length of time taken to complete a GCM checkin request successfully. If the + checkin is retried multiple times, the length of time is counted for the + last successful retry. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of retries before a GCM checkin succeeds. + + + + + Removed as of 03/2018 (M67). + + zea@chromium.org + Whether the GCM connection was made via a proxy or not. + + + + + Removed in September 2020 as the data was no longer being used. + + peter@chromium.org + + Interval between two successive received data message bursts. + + + + + + No longer used starting with Chrome 61 as the check was removed. + + peter@chromium.org + + Records whether a matching registration was found for each received + DATA_MESSAGE message from Google Cloud Messaging. Recorded while processing + the received message. Prior to M56 this also counted received + DELETED_MESSAGES messages. + + + + + + Removed in June 2019. + + peter@chromium.org + + The time between the successful completion of the connection and the arrival + of the first data message. + + + + + + Removed in April 2020. + + tschumann@chromium.org + treib@chromium.org + + Reports the client-started state when the GCM driver requested a read of the + instance id although the client was not ready. If != Success, the client is + likely leaking a registration. + + + + + + Removed in 2020-06. + + + + tschumann@chromium.org + treib@chromium.org + + Result of the outcome of persisting a change in the GCMStore. This histogram + is to meausure the frequency of such events and assess their severity. For + example, failing to write when calling AddInstanceIDData() likely results in + leaked FCM registrations. + + + + + + Removed as of 2/2015. + + zea@chromium.org + + Success indicates successfully loading an initialized persistent GCM store + at startup time. Failure indicates a failure loading the store. + + + + + + Removed as of 3/2014. + + zea@chromium.org + + Number of GCM users associated with this client at startup time. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Category of TTL specified in the outgoing message: 0, less than or equal to + 1 minute, less than or equal to 1 hour and etc. + + + + + + Removed in September 2020 as the data was no longer being used. + + peter@chromium.org + Number of messages in a received GCM data message burst. + + + + + Removed in June 2019. + + peter@chromium.org + + Interval between messages within a received GCM data message burst. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Length of time taken to complete a GCM registration request successfully. If + the registration is retried multiple times, the length of time is counted + for the last successful retry. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of retries before a GCM registration succeeds. + + + + + Removed in M56 in favor of GCM.ResetStoreError + + jianli@chromium.org + + Reports the problem encountered when resetting the GCM store. + + + + + + Removed Sep 2020. No longer used. + + alexchau@chromium.org + peter@chromium.org + + Categorized response body when 403: Forbidden is received from sending web + push messages. Recorded when received response after message has been sent. + All platforms. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Length of time taken to complete a GCM unregistration request successfully. + If the unregistration is retried multiple times, the length of time is + counted for the last successful retry. + + + + + + Removed 7/2019. No longer used. + + peter@chromium.org + + Number of unregistration requests sent to Google Cloud Messaging. Recorded + immediately after the request has started. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of retries before a GCM unregistration succeeds. + + + + + Removed 2020-02. + + pavely@chromium.org + + Status of parsing incoming invalidations message from GCM channel. + + + + + + Removed 2020-02. + + pavely@chromium.org + + Status of sending outgoing invalidations message through GCM. + + + + + + Removed 9/2012, and replaced by Drive.EntireFeedLoadTime + + Please list the metric's owners. Add more owner tags as needed. + + Time spent to load the entire file system information from the server + + + + + + Removed 9/2012, and replaced by Drive.EntryKind + + Please list the metric's owners. Add more owner tags as needed. + + Provides breakdown of specific formats for hosted documents. Recorded when + feed is loaded from the server. + + + + + + Removed 9/2012, and replaced by Drive.InitialFeedLoadTime + + Please list the metric's owners. Add more owner tags as needed. + + Time spent to load the initial part of the file system information from the + server + + + + + + Removed 9/2012, and replaced by Drive.NumberOfHostedDocuments + + Please list the metric's owners. Add more owner tags as needed. + + Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive + is first accessed. + + + + + + Removed 9/2012, and replaced by Drive.NumberOfRegularFiles + + Please list the metric's owners. Add more owner tags as needed. + + Number of regualr files on Drive. Logged when Drive is first accessed. + + + + + + Removed 9/2012, and replaced by Drive.NumberOfTotalFiles + + Please list the metric's owners. Add more owner tags as needed. + + Number of total files (regualr files + hosted documents) on Drive. Logged + when Drive is first accessed. + + + + + + Removed 01/2020 because the metric is not needed anymore. See + https://crbug.com/1036861 for discussion on this metric. + + mattreynolds@chromium.org + device-dev@chromium.org + + Whether high accuracy geolocation information was requested. + + + + + + Removed 9/2014, and replaced by + ContentSettings.PermissionActions_Geolocation. + + mvanouwerkerk@chromium.org + Events in GeolocationInfoBarDelegate. + + + + + Removed 9/2014, and replaced by + ContentSettings.PermissionActions_Geolocation. + + mvanouwerkerk@chromium.org + Events in GeolocationInfoBarDelegateAndroid. + + + + + Removed 2017/11. Use PostDisclosureDSESetting instead. + + benwells@chromium.org + + Records the geolocation content setting for the default search engine's + origin after the search geolocation disclosure has been shown and won't be + shown again. This metric is only recorded once per client. + + + + + + Removed 2017/01. Replaced by PostDisclosureContentSetting. + + benwells@chromium.org + + Records the geolocation permission for the default search engine's origin + after the search geolocation disclosure has been shown and won't be shown + again. This metric is only recorded once per client. + + + + + + Removed 2017/11. Use PreDisclosureDSESetting instead. + + benwells@chromium.org + + Records the geolocation content setting for the default search engine's + origin immediately before the search geolocation disclosure has been shown. + This metric is only recorded once per client. + + + + + + Removed 2017/01. Replaced by PreDisclosureContentSetting. + + benwells@chromium.org + + Records the geolocation permission for the default search engine's origin + immediately before the search geolocation disclosure has been shown. This + metric is only recorded once per client. + + + + + + Removed 2020/02. Replaced by Cancelled. + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gestures that were abandoned before they were completed. + Implemented for Android. + + + + + + Removed 2020/02. + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gesture was made beyond a threshold that, upon release, would + trigger navigation. Users can swipe back below the threshold but this event + will still be logged. Implemented for Android. + + + + + + Removed 2020/02. Replaced by Activated. + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gestures initiated by the user. Note that not all overscroll + gestures triggered are completed (e.g. the overscroll gesture is aborted if + user swipes back to the edge before releasing the finger). Implemented for + Android. + + + + + + Removed in r454917 03/2017. + + robliao@chromium.org + skare@chromium.org + Types of cards which received an index 0 button click. + + + + + Removed in r454917 03/2017. + + robliao@chromium.org + skare@chromium.org + Types of cards which received an index 1 button click. + + + + + Removed in r454917 03/2017. + + robliao@chromium.org + skare@chromium.org + Types of cards which received a notification click. + + + + + Removed in r454917 03/2017. + + robliao@chromium.org + skare@chromium.org + Events in Google Now component extension. + + + + + Removed in r455117 03/2017. + + robliao@chromium.org + skare@chromium.org + + Count of the number of Google Now notifications visible when the message + center/notification center is shown. + + + + + + Removed from code June 2019. See https://crbug.com/490710 for context. + + wnwen@chromium.org + + ConnectionResult error codes resulting from attempts to check whether or not + Google Play Services is available. Most of these checks are done lazily, + when a user accesses a feature that uses Google Play Services. Added for + http://crbug.com/490710. + + + + + + Removed from code June 2019. See https://crbug.com/490710 for context. + + wnwen@chromium.org + + Types of action taken in response to Google Play Services user-recoverable + errors. Added for http://crbug.com/490710. + + + + + + Removed 2015/08. + + kmadhusu@chromium.org + + Counts number of Google searches from various access points in the browser. + WARNING: Do not use this histogram as it currently fails to classify a large + percentage of Omnibox searches correctly - http://crbug.com/421631. + + + + + + Removed 09/2018; see https://crbug.com/871490. + + gab@chromium.org + + The effective update policy for Chrome on Windows. Recorded once per startup + (following a 45 seconds delay). + + + + + + Removed 12/2015 in Issue 566085. + + yfriedman@chromium.org + dfalcantara@chromium.org + + (Android-only) Records what action the user took (if any) on the InfoBar + indicating that a new version of Chrome is available. + + + + + + Removed 6/2020. + + yfriedman@chromium.org + dfalcantara@chromium.org + khushalsagar@chromium.org + + (Android-only) The amount of internal memory storage available on the user's + device when the InfoBar or update menu item is shown. Deprecating soon in + M64. + + + + + + Removed 12/2015 in Issue 566085. + + yfriedman@chromium.org + dfalcantara@chromium.org + + (Android-only) The amount of time which the InfoBar indicating a new version + is available is visible. + + + + + + Removed 08/2020 + + xingliu@chromium.org + + (Android-only) Records events when try to launch the update work flow via an + update notification. + + + + + + Removed 09/2018; see https://crbug.com/871490. + + grt@chromium.org + + True if the effective update policy for Chrome on Windows is the result of + an app-specific override; false if it is the default for all apps. Recorded + once per startup (following a 45 seconds delay). + + + + + + Removed sometime around M77. + + jmadill@chromium.org + + The time that elapses for the initial call to D3D11CreateDevice on D3D11 + ANGLE. A pure system call, with no ANGLE or Chromium code, called once every + GPU process startup. + + + + + + Removed sometime around M77. + + jmadill@chromium.org + + Time ANGLE spends initializing various shaders and internal classes. This is + time that isn't purely loading system DLLs and calling OS methods. It might + be work we can optimize or defer until later. + + + + + + Removed sometime around M77. + + jmadill@chromium.org + + Time ANGLE spends loading system DLLs, such as the D3D compiler DLL, and the + D3D11 and DXGI DLLs. Probably unavoidable startup costs, though very useful + to keep track of. + + + + + + Removed sometime around M55. + + vmiura@chromium.org + + The amount of GPU memory that was currently allocated as of just before the + GPU process' exit. + + + + + + Removed sometime around M55. + + vmiura@chromium.org + + The maximum amount of GPU memory that had ever been allocated during the GPU + process' lifetime, as of just before the GPU process' exit. + + + + + + Removed sometime around M55. + + vmiura@chromium.org + + The GPU memory manager's limit on the amount of GPU memory that can be + allocated as of just before the GPU process' exit. + + + + + + Removed sometime around M55. + + vmiura@chromium.org + + The number of windows that the GPU memory manager believed to exist as of + just before the GPU process' exit. + + + + + + Replaced by GPU.BlacklistFeatureTestResultsWindows2 in M67. + + vmiura@chromium.org + + Counts number of browser invocations for which a GPU feature is + allowed/blacklisted/disabled in various Windows sub-versions. + + + + + + Removed in M77. + + kbr@chromium.org + + Indicates whether WebGL / Pepper3D were blocked, and if so, for all domains, + or only a single one. This statistic is gathered every time an attempt is + made to create a 3D context. + + + + + + Removed 01/2017. + + ericrk@chromium.org + + The amount of time spent in GLES2DecoderImpl::CheckFramebufferValid. + + + + + + Removed 07/2018: not useful anymore. + + vmiura@chromium.org + + The time that the browser process takes to create the compositor from its + point of view. One of these is created for each top-level window (browser + frame, menus, etc.). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + As of 02/26/2020 this has been superceded by GPU.D3D11FeatureLevel. + + vmiura@chromium.org + The highest D3D11 feature level available. + + + + + Removed 11/2016. + + ericrk@chromium.org + + The amount of time spent destroying programs during ProgramManager::Destroy. + + + + + + Removed 11/2016. + + ericrk@chromium.org + + The number of progams destroyed during ProgramManager::Destroy. + + + + + + Removed 11/2016. + + ericrk@chromium.org + + The number of programs destroyed per millisecond during + ProgramManager::Destroy. Only logged if both the number of programs and the + elapsed time are greater than zero. + + + + + + Removed 11/2018. Replaced by GPU.DirectComposition.DCLayerResult2.Clear. + + jbauman@chromium.org + + Recorded for each quad (on overlay processing) the reason it was or wasn't + put in an overlay. + + + + + + Removed 08/2019. Replaced by GPU.DirectComposition.DCLayerResult.Video + + + + magchen@chromium.org + zmo@chromium.org + + Recorded for each quad (on overlay processing) with protected video type the + reason it was or wasn't put in an overlay. + + + + + + Removed 3/2019. This either succeeds or fails with DXGI_STATUS_OCCLUDED + infrequently which we also handle. + + sunnyps@chromium.org + zmo@chromium.org + + Result of calling Present on decode swap chain. Recorded on each present. + + + + + + Removed 3/2019. Creating the surface never fails. + + sunnyps@chromium.org + zmo@chromium.org + + Result of calling CreateSurfaceFromHandle. Recorded when decode swap chain + is created. + + + + + + Removed 4/2019. Replaced by GPU.DirectComposition.VideoPresentationMode. + + sunnyps@chromium.org + zmo@chromium.org + + Whether zero copy decode swap chain was used to present video frame instead + of video processor blit with flip swap chain. Recorded on each present. + + + + + + No longer needed. Data has been collected. + + magchen@chromium.org + zmo@chromium.org + + Recorded for each overlay frame during the video playback whether the + workaround that reduces the swap chain size to fit the screen is active. + + + + + + Removed 4/2019. Replaced by GPU.DirectComposition.OverlayFullScreenTypes. + + magchen@chromium.org + zmo@chromium.org + + Recorded for each overlay/underlay quad during the video playback whether + the video is played in full screen mode + + + + + + Removed 10/2018. Replaced by GPU.DirectComposition.OverlayFormatUsed2. + + sunnyps@chromium.org + Which overlay format was chosen for YUV overlays. + + + + + Removed 5/2019. Replaced by GPU.DirectComposition.OverlayFormatUsed3. + + sunnyps@chromium.org + zmo@chromium.org + + Which overlay format was chosen for YUV overlays. Recorded once per GPU + process launch only if hardware overlays are supported. + + + + + + Removed 03/2020. Data has been collected. + + magchen@chromium.org + zmo@chromium.org + + The overlay size types in comparison to the full screen size. Recorded for + each overlay quad during the video playback. + + + + + + Removed 04/2019. Rec 709 is almost always supported. + + magchen@chromium.org + sunnyps@chromium.org + zmo@chromium.org + + Whether or not Rec709 color space is supported on NV12 supported machines. + Recorded during the GPU process initialization. + + + + + + Replaced by format specific histograms under OverlaySupportFlags2. + + sunnyps@chromium.org + + These are the flags explaining how well overlays are supported on the + current display. The is recorded for every connected display when creating a + DirectComposition view context. + + + + + + Removed 04/2019. BGRA is never supported, NV12 always supports scaling, and + YUY2 supports scaling in 75% cases. + + + + sunnyps@chromium.org + zmo@chromium.org + + Flags that indicate if overlays are supported, and if additional features + such as scaling are supported for some common pixel formats. + + + + + + Removed 08/2018. Replaced by SwapBuffersResult which is emitted on both + success and failure. + + sunnyps@chromium.org + Emitted on direct composition surface swap buffers failure. + + + + + Removed 05/2018. GetLastError returns error for last successful or failed + win32 call so this doesn't work as expected. + + sunnyps@chromium.org + Last error when presentation using DirectComposition fails. + + + + + Removed 04/2019. SwapBuffers rarely fails. + + sunnyps@chromium.org + zmo@chromium.org + Whether or not swap buffers succeeded. + + + + + Removed 04/2019 because of using histogram macros instead of functions. + Replaced by SwapChainCreationResult2. + + + + sunnyps@chromium.org + zmo@chromium.org + + Whether creating swap chain for overlay format succeeded. Recorded once per + swap chain creation. + + + + + + Removed 10/2018. Replaced by GPU.DirectComposition.SwapChainFormatUsed. + + jbauman@chromium.org + What type of swapchain was actually created for an overlay. + + + + + Removed 5/2019. Replaced by GPU.DirectComposition.SwapChainFormatUsed3. + + sunnyps@chromium.org + zmo@chromium.org + + What format was used for each overlay swap chain on each swap buffers. + + + + + + Removed 04/2019. ResizeBuffers rarely fails. + + sunnyps@chromium.org + zmo@chromium.org + + Result of ResizeBuffers call. Recorded once per swap chain resize. + + + + + + Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.DisplayCompositor. + + mohsen@chromium.org + + Counts of the number of gpu process crashes when it only has display + compositor (no hardware acceleration and software compositing). + + + + + + Removed 2/2017. The values hadn't been updated since it was created, and the + code gathering the installation status has been removed in Chrome CL + 2679773002. + + vmiura@chromium.org + + Whether a version of DisplayLink is installed that crashes the GPU process. + This information is collected at statup. It applies only to Windows. See + http://crbug.com/177611. + + + + + + Expired in M75. + + kylechar@chromium.org + + The duration from when a request to establish a GPU channel arrives in + viz::GpuClient and to when the response for the request is sent. + + + + + + Removed November 27, 2019. See GPU.GpuBlockedBetweenSwapsUs2. + + vasilyt@chromium.org + backer@chromium.org + + This is logged once per frame if the output surface provides timing + information. It measures the time Gpu Main thread was blocked (difference + between wall time and cpu time) during tasks execution for currect frame. + Only reported when there is single surface swap in the same vsync interval. + Only reported for platforms supporting high resolution clocks. + + + + + + Removed 10/2019. Moved to GPU.GPUChannelHostWaitTime.Max120Seconds. + + magchen@chromium.org + zmo@chromium.org + + The wait time between the IPC message sent from the GPU channel host and the + event sync from the GPU process. If the wait time takes longer than 60 + seconds, 60 seconds will be recoreded. + + + + + + Removed 01/2020. + + kylechar@chromium.org + + Records how long the browser UI thread spent blocked for a sync IPC sent + using GpuChannelHost to see if it's contributing to jank. + + + + + + Renamed to GPU.IntelGpuSeriesType 03/2020 + + sunnyps@chromium.org + zmo@chromium.org + + Records user device's GPU generation. Only recorded on Windows platform at + GPU process launch time. Currently only meaningful with Intel GPUs. + + + + + + Removed 01/2020. Moved to GPU.GPUInitializationTime.V2. + + magchen@chromium.org + zmo@chromium.org + + The time between the GPU process starts and the GPU Info is collected in Viz + GPU service. If GPU initilization takes longer than 60 seconds, 60 seconds + will be recoreded. + + + + + + Removed 08/2016. + + vmiura@chromium.org + + Counts enumerating the initial cause for the GPU Process to be launched. + + + + + + Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.HardwareAccelerated. + + vmiura@chromium.org + + Counts of the number of process launches and crashes (when running on h/w). + + + + + + This histogram is no longer recorded. Use GPU.GLImplementation == + kGLImplementationSwiftShaderGL to check if the gpu process is launched with + software rendering. + + vmiura@chromium.org + + A boolean indicating whether the gpu process that was launched uses software + or hardware 3d rendering. + + + + + + Removed April 2018. Replaced by GPU.GPUProcessTerminationStatus2. + + vmiura@chromium.org + + Counts for each time the GPU Process Host detects the process dies. + + + + + + Removed August 2020. Replaced by Memory.GPU.PeakMemoryAllocationSource. + + enne@chromium.org + khushalsagar@chromium.org + + Kilobytes of memory used by Skia in the gpu process. This is recorded after + every block of commands in the raster decoder. + + + + + + Removed 10/2013. + + vmiura@chromium.org + + Records whether a client was selected for the force compositing mode field + trial or not. + + + + + + Removed 4/2015. + + vmiura@chromium.org + + The time that the GPU process spends in initializing the GL surface, and + collecting graphics information. + + + + + + It is not planned to use this approach to determine if Metal is to be used. + + ccameron@chromium.org + graphics-dev@chromium.org + + Compiling a MTLLibrary will sometimes hang forever. When initializing Metal, + a test shader is compiled to see if the MTLCompilerService is responding or + not. This records the success or failure of this test compile, once at + initialization. + + + + + + Removed 05/2020. Did not reveal interesting results. + + ccameron@chromium.org + graphics-dev@chromium.org + + Compiling a MTLLibrary will sometimes hang forever. When initializing the + gpu process, a test shader is compiled to see if the MTLCompilerService is + is responding or not. This records the time that it took for the compile + method to finish (not including the time for the compile itself to finish), + up to 1 minute. After 1 minute, a timeout sentinel value of 3 minutes is + reported. + + + + + + This did not substantially improve the situation and was removed. + + ccameron@chromium.org + graphics-dev@chromium.org + + Creating a new MTLLibrary will automatically retry if its callback is not + invoked within a short timeframe. This records the attempt number whose + callback was executed first. Recorded after every call to -[MTLDeviceProxy + newLibraryWithSource:] completes. + + + + + + This did not substantially improve the situation and was removed. + + ccameron@chromium.org + graphics-dev@chromium.org + + Creating a new MTLRenderPipelineState will automatically retry if its + callback is not invoked within a short timeframe. This records the attempt + number whose callback was executed first. Recorded after every call to + -[MTLDeviceProxy newRenderPipelineStateWithDescriptor:] completes. + + + + + + Removed 06/2019. + + khushalsagar@chromium.org + + This records the number of bytes required to serialize a paint op for OOP + rasterization. The metric is recorded each time an op is serialized with a + size > 512k bytes. + + + + + + Removed 07/2020. No longer used. + + hubbe@chromium.org + media-dev@chromium.org + + Records the display maximum lumens as reported by Windows. Recorded once for + each monitor when the gpu process starts. If monitor enumeration fails, this + metric will not be provided. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ericrk@chromium.org + + Whether we succeeded in compressing program data. Expected to always be + true. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ericrk@chromium.org + + The time to compress a program's binary data during insertion into the + program cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ericrk@chromium.org + + The percentage of raw size that a program binary takes after compression. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ericrk@chromium.org + + Whether we succeeded in decompressing program data. Failure indicates disk + or memory corruption. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ericrk@chromium.org + + The time to decompress a program's binary data during retrieval from the + program cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + vmiura@chromium.org + + Records if the call to glProgramBinary was successful. This can legitimately + fail if the driver wants chrome to re-link and re-cache the gpu program. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + ssid@chromium.org + + Amount of memory released from the program cache on memory pressure. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + vmiura@chromium.org + + Records the total in-memory cache size, before a program is cached. Can be + used with GPU.ProgramCache.MemorySizeBeforeKb to find the maximum cache size + distribution. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + vmiura@chromium.org + + Records the total in-memory cache size, after a program is cached. Can be + used with GPU.ProgramCache.MemorySizeAfterKb to find the maximum cache size + distribution. + + + + + + Not used after M77. ProgramCache not actively being tuned. + + vmiura@chromium.org + + The size of program binaries loaded into the gpu program cache. + + + + + + Never used. + + vmiura@chromium.org + + Counts of the number of gpu process crashes when the software rasterizer is + enabled. + + + + + + Removed 06/2020. Data has been collected on Windows. + + vmiura@chromium.org + magchen@chromium.org + + This metric shows whether the GPU supports Vulkan. It is recorded 15 seconds + after the browser launch. + + + + + + Removed 12/2012. Moved to GPU.AtExitSurfaceCount. + + vmiura@chromium.org + + The number of surfaces that the GPU process was rendering to right before + exiting. This should be equal to the number of tabs (both visible and + hidden) rendering via the compositor. + + + + + + Removed 05/2018. Moved to GPU.ProcessLifetimeEvents.SwiftShader. + + capn@chromium.org + + Counts of the number of process launches and crashes (when running on s/w). + + + + + + Removed 06/2020. Both LUMINANCE_F16 and R16_EXT must be supported for now. + + hubbe@chromium.org + rijubrata.bhaumik@intel.com + media-dev@chromium.org + + Whether LUMINANCE_F16 and/or R16_EXT texture support is available. Recorded + each time a new context group is initialized and extensions are detected. + + + + + + Removed 04/2018. Infobar has been removed. + + vmiura@chromium.org + Counts user actions when a 3D API info bar is raised. + + + + + Removed 06/2020. Data has been collected on Windows. + + vmiura@chromium.org + magchen@chromium.org + + Whether the Vulkan extension VK_KHR_external_memory_win32 is supported in + the GPU drivers. It is recorded 15 seconds after the browser launch. + + + + + + Removed 06/2020. Data has been collected on Windows. + + vmiura@chromium.org + magchen@chromium.org + + Whether the Vulkan extension VK_KHR_external_semaphore_win32 is supported in + the GPU drivers. It is recorded 15 seconds after the browser launch. + + + + + + Removed 06/2020. Data has been collected on Windows. + + vmiura@chromium.org + magchen@chromium.org + + Whether the Vulkan extension VK_KHR_win32_keyed_mutex is supported in the + GPU drivers. It is recorded 15 seconds after the browser launch. + + + + + + Removed 06/2020. Data has been collected on Windows. + + vmiura@chromium.org + magchen@chromium.org + + The maximum Vulkan API version supported in the gpu drivers. It is recorded + 15 seconds after the browser launch. + + + + + + No longer used after GPU watchdog V2 is enabled by default in M82. It's the + same as the default histogram GPU.WatchdogThread.Event. + + magchen@chromium.org + zmo@chromium.org + + Recorded for each time the GPU watchdog V2 thread starts, crashes and ends. + + + + + + GPU watchdog V1 is disabled in M82. Please see + GPU.WatchdogThread.ExtraThreadTime for the result of V2. + + magchen@chromium.org + zmo@chromium.org + + The time the GPU main thread needs to make any progress after the first + watchdog timeout. + + + + + + GPU watchdog V1 is disabled in M82. Please see GPU.WatchdogThread.Timeout + for the result of V2. + + magchen@chromium.org + zmo@chromium.org + + Recorded timeout events when the GPU watchdog V2 enters OnWatchdogTimeout. + + + + + + GPU watchdog V1 is disabled in M82. Please see GPU.WatchdogThread.WaitTime + for the result of V2. + + magchen@chromium.org + zmo@chromium.org + + Record the wait time in OnWatchdogTimeout() for the GPU main thread to make + any progress. + + + + + + As of 2020-02-12, this is deprecated in favor of + Graphics.Smoothness.PercentDroppedFrames. + + sadrul@chromium.org + graphics-dev@chromium.org + + + + + As of 2020-02-12, this is deprecated in favor of + Graphics.Smoothness.PercentDroppedFrames.AllAnimations. + + sadrul@chromium.org + ericrk@chromium.org + + + + + As of 2020-02-12, this is deprecated in favor of + Graphics.Smoothness.PercentDroppedFrames.AllInteractions. + + sadrul@chromium.org + ericrk@chromium.org + + As of 2020-02-12, this is deprecated in favor of + Graphics.Smoothness.PercentDroppedFrames.AllInteractions. + + + + + + As of 2020-02-12, this is deprecated in favor of + Graphics.Smoothness.PercentDroppedFrames.AllSequence. + + sadrul@chromium.org + ericrk@chromium.org + + + + + Removed 07/2020; currently unowned, and histogram gathering was causing + crashes. + + vtsyrklevich@chromium.org + dynamic-tools@google.com + + Reports how many allocations it took for malloc GWP-ASan to OOM. Reported + the first time the allocator fails to consecutively allocate + GuardedPageAllocator::kOutOfMemoryCount allocations in a row. + + + + + + Removed 07/2020; currently unowned, and histogram gathering was causing + crashes. + + vtsyrklevich@chromium.org + dynamic-tools@google.com + + Reports how many allocations it took for PartitionAlloc GWP-ASan to OOM. + Reported the first time the allocator fails to consecutively allocate + GuardedPageAllocator::kOutOfMemoryCount allocations in a row. + + + + + + Removed 1/2020 - but the data exists in system_profile under + hardware.app_drive and hardware.user_data_app_drive + + dbeam@chromium.org + + Whether a drive has a seek penalty (i.e. is a spinning disk). Emitted 0-2 + times shortly after startup when constructing the initial UMA log. + + + + + + Removed 1/2020 - but the data exists in system_profile under + hardware.app_drive and hardware.user_data_app_drive + + dbeam@chromium.org + + Whether it was possible to determine if a drive has a seek penalty. This can + fail for various reasons (device drivers don't offer this information, the + drive is still mounting, lack of access, etc.). Emitted twice shortly after + startup when constructing the initial UMA log. + + Seek penalty detection is disabled on XP/Vista as of 9/24/2015 because it + crashes too much. http://crbug.com/514822 + + + + + + Removed 1/2020 - but the data exists in system_profile under + hardware.app_drive and hardware.user_data_app_drive + + dbeam@chromium.org + + The amount of time it takes to determine whether a drive has a seek penalty. + Emitted twice shortly after startup when constructing the initial UMA log. + + + + + + Removed in M83 after all code for the old enumeration method had been + removed. + + charliea@chromium.org + + On Windows and Mac, we're implementing new methods to enumerate serial + devices that provide us more information about the actual devices. This + metric measures the difference between the number of devices that the new + and old enumeration methods find. Once this metric gives us confidence that + the new and old methods are at parity, we can cut out the old method + altogether. + + + + + + Removed 3/2019. + + ryansturm@chromium.org + bengr@chromium.org + + Records that the capping heavy pages InfoBar was allowed or the specific + reason that the feature was blacklisted from heavy page capping. Recorded + when the triggering threshold is met for users with capping heavy pages + enabled. Reasons are ordered in the same order they are checked. + + + + + + Removed 3/2019. + + ryansturm@chromium.org + bengr@chromium.org + + Records the details of user interaction with the heavy page capping InfoBar. + + + + + + Removed 3/2019. + + ryansturm@chromium.org + + Records the data savings due to heavy page capping. This is recorded when + the page is being terminated. This is not recorded when the tab is + backgrounded, so android fast shutdown may result in this metric not being + recorded. This is only recorded for page loads that were still paused when + the page was terminated. + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a browser for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. Each type of inconsistency is a bit, and all bits found + in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency MAY appear time and + again as the same corrupt histogram is examined for each potenital UMA + upload. + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a browser for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. Each type of inconsistency is a bit, and all bits found + in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency will only appear at + most one time for each histogram in a single process (i.e., duplicate + corruption in a single histogram is not noted in this chart.) + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a child process for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. Each type of inconsistency is a bit, and all bits found + in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency MAY appear time and + again as the same corrupt histogram is examined for each potenital UMA + upload. + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a child process for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. Each type of inconsistency is a bit, and all bits found + in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency will only appear at + most one time for each histogram in a single process (i.e., duplicate + corruption in a single histogram is not noted in this chart.) + + + + + + Removed 7/2012. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a renderer for transmission to the browser. Inconsistent data is NOT + transmitted to the browser. Each type of inconsistency is a bit, and all + bits found in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency MAY appear time and + again as the same corrupt histogram is examined for each potenital UMA + upload. + + + + + + Removed 7/2012. + + asvitkine@chromium.org + + The number of inconsistency events found when examining a single histogram's + data in a renderer for transmission to the browser. Inconsistent data is NOT + transmitted to the browser. Each type of inconsistency is a bit, and all + bits found in one histogram examination are added together to summarize the + inconsistent event. Note that the same inconsistency will only appear at + most one time for each histogram in a single renderer process (i.e., + duplicate corruption in a single histogram is not noted in this chart.) + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of extra samples counted in the redundant_count in a histogram + that were not found by summing the samples in the buckets. + + + + + + Removed 7/2017. + + asvitkine@chromium.org + + The number of missing samples in the redundant_count in a histogram that + were found by summing the samples in the buckets. + + + + + + Removed 7/2012. + + asvitkine@chromium.org + + The amount of discrepancy found when examining a single histogram's data in + a renderer process for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. + + + + + + Removed May 2020, replaced with more detailed histograms: + History.ClearBrowsingData.Duration.TimeRangeDeletion, + History.ClearBrowsingData.Duration.OriginDeletion, + History.ClearBrowsingData.Duration.FilteredDeletion. + + dullweber@chromium.org + msramek@chromium.org + + The time that passed while performing a browsing data deletion for a + restricted amount of time (e.g. "Last hour") or with an origin + filter. + + + + + + Removed 02/2020 since the histogram indicators were stable. + + dullweber@chromium.org + msramek@chromium.org + + Track whether the SpannableString is applied correctly in + ClearBrowsingDataCheckbox.java. (crbug.com/783866) + + + + + + No longer tracked as of March 2017. + + rpop@google.com + + Size of the recovered Favicons database relative to the original corrupt + database. Recovery is VACUUM-like, so the resulting database should always + be smaller. Substantial 100% results would indicate empty databases being + recovered, substantial low% results would indicate very little data being + recovered. + + + + + + No longer tracked as of March 2017. + + rpop@google.com + + Rows recovered from [favicon_bitmaps] table in Favicons recovery. + + + + + + No longer tracked as of March 2017. + + rpop@google.com + Rows recovered from [favicons] table in Favicons recovery. + + + + + No longer tracked as of March 2017. + + rpop@google.com + + Rows recovered from [icon_mapping] table in Favicons recovery. + + + + + + No longer tracked as of March 2017. + + rpop@google.com + + Track results of SQLite database recovery code in thumbnail_database.cc. + + + + + + Removed as of 02/2020. The vast majority of the time this is under 50ms. + + rkaplow@chromium.org + + The amount of time that elapsed during HistoryService::Init. + + + + + + Removed July 2020 as not deemed necessary. + + sky@chromium.org + mpearson@chromium.org + + Time to load in-memory keyword_search_terms table from disk. Recorded on + profile open. + + + + + + Removed July 2020 as not deemed necessary. + + sky@chromium.org + mpearson@chromium.org + + Time to load in-memory urls table from disk urls table. Recorded on profile + open. + + + + + + No longer needed. Removed Aug 2019 as part of crbug.com/969934 cleanup. + + gab@chromium.org + + The sum of the visit_count fields for all URLs in the "in memory" + history database. This corresponds to the number of times the user has + visited the typed URLs in the last 30 days (excluding page reloads, since + the history database does not increment the visit_count in that case). + Recorded on profile open. + + + + + + Removed August 2020. + + mpearson@chromium.org + + Size of on-disk cache for in-memory url index. Recorded on profile open when + restoring from a cache file. + + + + + + Removed August 2020. + + mpearson@chromium.org + + Number of items in the in-memory url index char_word_map_. Recorded on + profile open when restoring from a cache file and again shortly after + profile open when rebuilding the in-memory url index from history. + + + + + + Removed July 2020. + + mpearson@chromium.org + ssid@chromium.org + + Time to restore the in-memory url index from disk cache. Recorded on profile + open. + + + + + + Removed July 2020. + + mpearson@chromium.org + ssid@chromium.org + + Time to write in-memory url index to disk cache. Recorded once shortly after + profile open (after rebuilding the in-memory url index from history) and + again upon (clean) shutdown. + + + + + + Removed August 2020. + + mpearson@chromium.org + + Number of items in in-memory url index word_map_. Recorded on profile open + when restoring from a cache file and again shortly after profile open when + rebuilding the in-memory url index from history. + + + + + + Removed as of 11/2018, not used in production since 2/2018. + + twifkak@chromium.org + bengr@chromium.org + + Page visits to each of a user's top 50 hosts. The bucket is the 1-based rank + of the host. Visits to all other hosts go into the 51st bucket. + Android-only. Only counts the last URL in a redirect chain and does not + include reloads. The list of top hosts is computed approximately nightly. + This means that a given day will likely include a recalculation of top + hosts, and therefore a given bucket may represent two different hosts at + different times of day. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Page visits to each of a user's top 50 sites. Visits to all other sites go + into the 51st bucket. Only count the page visit if it came from user + browsing and only count it once when cycling through a redirect chain. + + + + + + Removed because only the execution time at startup is of interest. See + histogram History.UpdateTopSitesOnDBThread_Startup_Time. + + yiyaoliu@chromium.org + + The amount of time for function + history::TopSitesBackend::UpdateTopSitesOnDBThread to execute. Excludes the + case where local TopSitesDatabase db_ is unavailable, i.e. where the update + doesn't really happen. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + rlp@chromium.org + + The state of the hotword audio logging preference. This value is emitted + each time the hotword availability is requested by the extension if the user + is also opted in to hotword voice search. This check typically happens each + time a hotword search is initiated. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + rlp@chromium.org + + The state of the hotword preference. This value is emitted during + HotwordService initialization which happens during Profile initialization. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + rlp@chromium.org + + Whether the external component hotword extension exists (i.e., not pending + download, disabled, etc.). This value is emitted each time the hotword + availability is requested by the extension which typically happens each time + a hotword search is initiated. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + rlp@chromium.org + + Errors reported by the hotword service when determining if hotwording is + available. Non-errors are also reported so that errors can be seen as a + percentage of total requests. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + amistry@chromium.org + rlp@chromium.org + somast@chromium.org + + Success or error when attempting to open a MediaStream for the microphone. + At most one success or error will be logged for an attempt to open a stream. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + amistry@chromium.org + rlp@chromium.org + somast@chromium.org + + Timeout occured while waiting for a message from the NaCl hotword detector + plugin. This value is the message that was expected to be received from the + plugin. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + amistry@chromium.org + rlp@chromium.org + somast@chromium.org + + Success or error when attempting to load the NaCl hotword detector plugin. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + amistry@chromium.org + rlp@chromium.org + somast@chromium.org + + Location of hotword trigger. Emitted every time the hotword is triggered by + the user saying 'Ok Google'. + + + + + + Removed as of 10/2017. Feature removed with crbug/761426. + + amistry@chromium.org + rlp@chromium.org + somast@chromium.org + + Language, switched to by the user, that triggered a hotword shared module + reinstall. + + + + + + Removed as of 02/2020. + + yhirano@chromium.org + lukasza@chromium.org + + Logs the type of requests made by HTML imports with wrong fetcher. + + + + + + Removed as of 3/2015. + + ricea@chromium.org + + The time spent performing an asynchronous revalidation that was triggered by + a Cache-Control: stale-while-revalidate directive. This is recorded when the + asynchronous revalidation completes, either after the response was + completely read or an error occurred. One entry is recorded for each + asynchronous revalidation that is performed. + + + + + + stale-while-revalidate implementation removed for now, see + https://crbug.com/700568. + + ricea@chromium.org + + Count of the number of external (ie. from Blink) conditionalized requests, + and whether or not those requests could have been served from the browser + cache. + + + + + + Removed in favor of HttpCache.NetworkIsolationKeyPresent2. + + jkarlin@chromium.org + shivanisha@chromium.org + + Records whether a cache request has a network isolation key set or not, + which is used for double-keying. + + + + + + Removed 4/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Result of a main page HttpCacheTransaction if offline mode had been enabled. + + + + + + Removed 2019-07-03. + + morlovich@chromium.org + + For http cache transactions in which a network request was sent, the + percentage of total request time that elapsed before sending the request + over the network; this is the time spent accessing the disk cache. + + + + + + Removed in M77. One day Android results: 25.00% 1033 50.00% 4945 75.00% + 42023 95.00% Infinity + + jkarlin@chromium.org + + For each http cache transaction for which a cache entry exists but it cannot + be used because the entry's age is beyond its freshness: counts how many + freshness periods have elapsed since the entry was last used (x1000). + + + + + + Removed in M77. One day percentiles on Android: 25.00% 16146 50.00% 101342 + 75.00% 372632 95.00% Infinity + + jkarlin@chromium.org + + For each http cache transaction for which a validation attempt is made due + to a stale entry and is updated (e.g., 200), records the age of the entry in + seconds. + + + + + + Removed in M77. One day percentiles on Android: 25.00% 246.3 50.00% 1353 + 75.00% 9142 95.00% 147572 99.00% Infinity + + jkarlin@chromium.org + + For each http cache transaction for which a validation attempt is made due + to a stale entry and is updated (e.g., 200), records the age of the entry as + percentage of freshness period. + + + + + + Removed in M77. One day percentiles on Android: 25.00% 10791 50.00% 70285 + 75.00% 223571 95.00% Infinity + + jkarlin@chromium.org + + For each http cache transaction for which a validation attempt is made due + to a stale entry and is validated (304), records the age of the entry in + seconds. + + + + + + Removed in M77. One day percentiles on Android: 25.00% 169.5 50.00% 476.3 + 75.00% 2451 95.00% 43218 99.00% 474791 99.50% Infinity + + jkarlin@chromium.org + + For each http cache transaction for which a validation attempt is made due + to a stale entry and is validated (304), records the age of the entry as + percentage of freshness period. + + + + + + Removed 07/2019 and replaced by HttpCache.NetworkIsolationKeyPresent. + + jkarlin@chromium.org + shivanisha@chromium.org + + Records whether a cache request has a top frame origin set or not, which is + used for double-keying. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + The type of Vary header for a given GET response. + + + + + Removed 06/19. + + vasilii@chromium.org + hurims@gmail.com + + Whether or not the password checkbox is checked when importing a profile of + Firefox. Note that canceled imports could be counted also. + + + + + + Removed 07/2020. + + vasilii@chromium.org + hurims@gmail.com + + The number of passwords that are imported from Firefox. This is recorded + when importing a profile of Firefox with the password checkbox checked. Note + that the reported number of password could be slightly bigger than the + actual number of imported passwords because some incomplete or blacklisted + passwords that are dropped while importing might be included in the reported + value. + + + + + + Removed and removed BookmarkBarView + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time from install time to time that user opens import dialog + from BookmarkBarView. + + + + + + Removed and removed BookmarkBarView + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time from install time to time that user opens import dialog + from NTP floating BookmarkBarView. + + + + + + Removed and replaced by Import.ShowDialog.FromBookmarkBarView + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time from install time to time that user opens import dialog + from BookmarkBarView. + + + + + + Removed and replaced by Import.ShowDialog.FromFloatingBookmarkBarView + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time from install time to time that user opens import dialog + from NTP floating BookmarkBarView. + + + + + + Replaced by ImportantFile.FileDeleteNoRetryError, + ImportantFile.FileDeleteRetryExceededError, and + ImportantFile.FileDeleteRetrySuccessCount in M84. + + grt@chromium.org + xaerox@yandex-team.ru + + File error happened upon temporary file deletion at ImportantFileWriter. + + + + + + Removed in M84. + + xaerox@yandex-team.ru + + File error happened upon opening temporary file at ImportantFileWriter. + + + + + + Removed in 2019-11. + + mamir@chromium.org + + Time used to atomically write string into a file using ImportantFileWriter. + + + + + + Removed 11/2014 (crbug.com/347507). Replaced by + InertialSensor.DeviceOrientationSensorAndroid. + + timvolodine@chromium.org + + Whether the Sensor.TYPE_ROTATION_VECTOR was available at the start of Device + Orientation. + + + + + + Removed 03/2015, and replaced by InputMethod.Commit.Type2. + + shuchen@chromium.org + + The suggestion accuracy type which the user chooses to commit. + + + + + + This is deprecated since M46, InputMethod.ID2 is used since then. + + shuchen@chromium.org + + The breakdown of input method usage by input method IDs. Recorded when the + user presses keys on physical or on-screen keyboard. + + + + + + Removed as of Jan 2020. + + changwan@chromium.org + The result of registering proxy view to InputMethodManager. + + + + + Superseded by Installer.Recovery.Reason in 8/2017. + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of times the device has been recovered. + + This is reported on reboot after a successful recovery. Cleared only when + switching to dev mode or on factory reset. + + This metric is specific to Chrome OS. + + + + + + Removed 4/2015. It appears the code at some point changed to use the + histogram name 'ExtensionInstallSigner.InvalidCount' and we forgot to update + this histogram name. + + Please list the metric's owners. Add more owner tags as needed. + + This is a count of the number of ids that we asked to be signed which the + server response indicated were not in the webstore. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallSigner.ResultWasValid. + + Please list the metric's owners. Add more owner tags as needed. + + The extensions install signer got a well-formed result from the server but + the signature check on it failed. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.GetSignatureResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier tried to get a new signature and received a + response but it wasn't properly signed. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.GetSignatureResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier tried to get a new signature but was unable + to (network error contacting the server, response from server was malformed, + etc.). + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.GetSignatureResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier got a new signature from the server that was + valid. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.InitResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier found a valid signature at startup, and this + is a count of the number of signed ids it contained. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.InitResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier found a signature in the prefs at startup, + and it parsed properly, but it was invalid (some ids may have been + added/removed, could not verify it was signed with the correct private key, + etc.). + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.InitResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier did not find any signature in the prefs at + startup. + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.InitResult. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier found a signature in the prefs at startup, + but it wasn't parseable (missing/wrong format of required keys, etc.). + + + + + + Removed 1/2014 (crbug.com/333934). Replaced by + ExtensionInstallVerifier.MustRemainDisabled. + + Please list the metric's owners. Add more owner tags as needed. + + The extension install verifier would have disabled an extension but is not + in enforcement mode. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Length of time taken to complete the DeleteToken request successfully. If + the request is retried multiple times, the length of time is counted for the + last successful retry. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of retries before DeleteToken succeeds. + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + + Whether the Instance ID API is enabled. Checked when a chrome.instanceID + function is called. + + + + + + Removed in 2020-06. + + tschumann@chromium.org + treib@chromium.org + + Counts the events when the GCM integration generates and registers a new + instance ID with FCM. This histogram acts as a pure counter and only emits + 'true' values. The goal of the histogram is to detect potential instance ID + leaks. It's best interpreted in relation to the reported number of + syncing/sync-transport users. + + + + + + Removed 7/2019. No longer used. + + jianli@chromium.org + Number of retries before GetToken succeeds. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Records various events of interest in the InstantController. E.g. When URLs + are blacklisted. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How often an Instant preview is committed onto a different tab than it was + created from. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time between the first Omnibox interaction and when the Instant preview + shows. If the instant preview was already showing when the user interacted + with the omnibox, this histogram is not recorded. + + + + + + Removed as of 07/2019, see crbug.com/975798. + + kmilka@chromium.org + ramyan@chromium.org + + Records a histogram for how often the Cacheable NTP fails to load. + + + + + + Depcreated as of 10/2013. No longer relevant since the HTML overlay was + abandoned. + + Please list the metric's owners. Add more owner tags as needed. + + Records the cause for falling back to a local overlay at the time of + fallback. + + + + + + Removed as of 10/2013. This histogram is no longer relevant since the HTML + overlay went away. + + Please list the metric's owners. Add more owner tags as needed. + + Records a histogram for instant extended (Local NTP and Online NTP) and + non-extended navigations. + + + + + + Removed as of 11/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Records, on startup, whether the user has chosen to opt-in to or opt-out of + InstantExtended via chrome://flags. + + + + + + Removed 2013-06. As of m30 use InstantExtended.NewOptInState. + + Please list the metric's owners. Add more owner tags as needed. + + Records, on startup, whether the user has chosen to opt-in to or opt-out of + InstantExtended via chrome://flags. + + + + + + Removed 2013-07. Please see InstantExtended.PercentageMatchV2_QuerytoQuery + instead. + + Please list the metric's owners. Add more owner tags as needed. + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a search query to another search query. + + + + + + Removed 2013-07. Please see InstantExtended.PercentageMatchV2_QuerytoURL + instead. + + Please list the metric's owners. Add more owner tags as needed. + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a search query to a url. Example: Accidental search for + google.con, then navigation to google.com. + + + + + + Removed 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoQuery + instead. + + Please list the metric's owners. Add more owner tags as needed. + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a url to a search query. + + + + + + Removed 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoURL + instead. + + Please list the metric's owners. Add more owner tags as needed. + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a url to another url. + + + + + + Removed in August 2016 with the removal of query in the omnibox code. + + mpearson@chromium.org + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a search query to another search query. + + + + + + Removed in August 2016 with the removal of query in the omnibox code. + + mpearson@chromium.org + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a search query to a url. Example: Accidental search for + google.con, then navigation to google.com. + + + + + + Removed in September 2016 because (i) this measurement was somewhat wrong, + (ii) it's difficult to understand the data, and (iii) there are better ways + to answer the same question. The measurement is somewhat wrong because + reloads, link drops, and pasting URLs and pressing enter are all incorrectly + logged to the URLtoQuery histogram, not the URLtoURL histogram. Futhermore, + this histogram is difficult to analyze because it's not broken up by input + length. Short URLs can by random chance have a sizable percentage match with + a query. Finally, there are better source for data like this; ask mpearson + for details. + + mpearson@chromium.org + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a url to a search query. + + + + + + Removed in September 2016 because (i) this measurement was somewhat wrong, + and (ii) there are better ways to answer the same question. The measurement + is somewhat wrong because reloads, link drops, and pasting URLs and pressing + enter are all incorrectly logged to the URLtoQuery histogram, not the + URLtoURL histogram. Furthermore, there are better source for data like this; + ask mpearson for details. + + mpearson@chromium.org + + Records the number of matching characters at the start of the user's text as + a percentage of average length between the old and new text when the user + navigates from a url to another url. + + + + + + Removed 2013-06. This preference has not been exposed or used for months, + and we do not plan to use it in the future. + + Please list the metric's owners. Add more owner tags as needed. + + Records, on startup, the value of the "Allow your search engine to + provide Instant result" preference setting for the first profile + loaded. + + + + + + Removed as of 7/2015. + + ksimbili@chromium.org + + Records the scroll state on the preview page when instant search clicks + feature is triggered. + + + + + + Removed as of 7/2015. + + ksimbili@chromium.org + + Records the reason that triggered the page swap when instant search clicks + feature is triggered. + + + + + + Removed as of 7/2015. + + ksimbili@chromium.org + + The time spent by the user in preview page before swapping to original or + navigating out of preview page. + + + + + + Removed as of 7/2015. + + ksimbili@chromium.org + + The time it took for swap to trigger for all swaps. The is the time between + preview page load start to preview page swap with the original page. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + Captures the count of successful and failed connection attempts. + + This metric counts the top-level user action from beginning to connect, all + the way through success or failure of the connection (excluding any + programmatic retries within the connection attempt). + + This metric provides an immediate understanding of the Instant Tethering + connection success rate. The counts of failure are broken down in + InstantTethering.ConnectionToHostResult.Failure. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + Captures the effective count of successful and failed GATT connection + attempts, including retries. This means that if a GATT connection attempt + fails but then succeeds on a future retry, this is counted as a single + success. In the context of this metric, a failure represents a GATT failure + in all retry attempts. + + An individual attempt is considered successful if a GATT connection was + created and authenticated successfully (i.e., the connection was ready for + Instant Tethering to exchange protocol messages). + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + Captures the effective count of successful and failed GATT connection + attempts, including retries. This means that if a GATT connection attempt + fails but then succeeds on a future retry, this is counted as a single + success. In the context of this metric, a failure represents a GATT failure + in all retry attempts. + + An individual attempt is considered successful if a GATT connection was + created and authenticated successfully (i.e., the connection was ready for + Instant Tethering to exchange protocol messages). + + This metric is the background advertisement analog of + InstantTethering.GattConnectionAttempt.EffectiveSuccessRateWithRetries. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + Captures the count of successful and failed GATT connection attempts. + + An attempt is considered successful if a GATT connection was created and + authenticated successfully (i.e., the connection was ready for Instant + Tethering to exchange protocol messages). + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + Captures the count of successful and failed GATT connection attempts. + + An attempt is considered successful if a GATT connection was created and + authenticated successfully (i.e., the connection was ready for Instant + Tethering to exchange protocol messages). + + This metric is the background advertisement analog of + InstantTethering.GattConnectionAttempt.SuccessRate. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client begins to scan and advertise, and + connects to a host (before authentication). + + This histogram only considers the time from when the client *sends* an + advertisement, and not when the client *receives* an advertisement. See + InstantTethering.Performance.StartScanToReceiveAdvertisementDuration and + InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration for + histograms that consider when the client receives an advertisement. + + This histogram is the foreground advertisement analog of + InstantTethering.Performance.StartScanToConnectionDuration.Background. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client connects to a host, and + authenticates with that host. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client connects to a host, and + authenticates with that host. + + This histogram is the background advertisement analog of + InstantTethering.Performance.ConnectionToAuthenticationDuration. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time it takes for the client to connect to the host, from + the moment the user taps 'Connect', until the client connects to the host's + hotspot. This does not include timeouts. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client received a foreground + advertisement from a host, and connected to that host (before + authentication). + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client received a background + advertisement from a host, and connected to that host (before + authentication). + + This histogram is the background advertisement analog of + InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client begins to scan, and connects to a + host (before authentication). + + This histogram is the background advertisement analog of + InstantTethering.Performance.AdvertisementToConnectionDuration. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client begins to scan and advertise, and + receives a foreground advertisement from a host. + + + + + + Removed 2019/02 in favor of MultiDevice.* equivalent. + + hansberry@chromium.org + + The duration of time between when a client begins to scan, and receives a + background advertisement from a host. + + This histogram is the background advertisement analog of + InstantTethering.Performance.AdvertisementToConnectionDuration. + + + + + + Removed on 8/1/13. + + felt@chromium.org + + The time between the SSL interstitial display and the user decision, which + may be either accept or deny. This is only recorded for overridable SSL + warnings with a CERT_AUTHORITY_INVALID warning. Timing begins when user + first focuses on the page. + + + + + + Removed on 8/1/13. + + felt@chromium.org + + The time between the SSL interstitial display and the user decision, which + may be either accept or deny. This is only recorded for overridable SSL + warnings with a CERT_COMMON_NAME_INVALID warning. Timing begins when user + first focuses on the page. + + + + + + Removed on 8/1/13. + + felt@chromium.org + + The time between the SSL interstitial display and the user decision, which + may be either accept or deny. This is only recorded for overridable SSL + warnings with a CERT_DATE_INVALID warning. Timing begins when user first + focuses on the page. + + + + + + Replaced by interstitial.ssl_overridable.* and + interstitial.ssl_nonoverridable.* in Jan 2015 (M42). + + felt@chromium.org + + User action when the user is shown a SSL interstitial. SHOW_ALL and MORE + refer to the total number of SSL errors; all of the other numbers pertain to + the number of actions related to SSL errors that are overridable. The counts + do not sum to 100%; SHOW_ALL is a superset of SHOW_OVERRIDABLE, which in + turn will be a supserset of the PROCEED/DONT_PROCEED variables. + SHOW_UNDERSTAND is only being used by an experimental field trial. The + interstitials due to captive portals are now recorded in the + "SSLCaptivePortal". + + + + + + Removed August 2016. Replaced with interstitial.ssl.clockstate.network2, + which records reasons why network time might be unavailable. + + mab@chromium.org + + State of the system clock, relative to network time, when an SSL + CERT_INVALID_DATE error is seen. + + + + + + Removed October 2016. Due to a bug, data in this histogram is mislabelled + and should be disregarded. Replaced with + interstitial.ssl.clockstate.network3. + + estark@chromium.org + mab@chromium.org + + State of the system clock, relative to network time, when an SSL + CERT_INVALID_DATE error is seen. + + + + + + Removed September 13 2017. + + jww@chromium.org + + Specifies when a user enters the page info menu whether or not the user + pressed the SSL decisions revoke button. This can only by done if the user + is in the "Remember Certificate Error Decisions" experiment. This + is logged when the page info UI is closed. Replaced by + .did_user_revoke_decisions2 to keep data separate after changing + functionality to only log when button was visible. + + + + + + Removed Dec 2017 (M65). + + jww@chromium.org + + Records when a user has made a decision to proceed on a nonoverridable SSL + interstitial. Also records whether a prior decision had been made but the + decision expired. + + + + + + Removed Dec 2017 (M65). + + jww@chromium.org + + Records when a user has made a decision to proceed on an overridable SSL + interstitial. Also records whether a prior decision had been made but the + decision expired. + + + + + + Removed Nov 2017 (M64). + + jww@chromium.org + + Emitted when a good certificate is seen, specifying whether the user already + gave an exception for a bad certificate for the same host. + + + + + + Removed December 2017 (M65). + + jam@chromium.org + + Whether the resource type for a request that succeeded with a good cert and + revoked a certificate exception is for a frame (as opposed to subresource). + + + + + + Removed Jan 2015 (M42). + + felt@chromium.org + + The likelihood of a |CERT_AUTHORITY_INVALID| error being an attack. + + + + + + Removed Jan 2015 (M42). + + felt@chromium.org + + The likelihood of a |CERT_COMMON_NAME_INVALID| error being an attack. + + + + + + Removed Jan 2015 (M42). + + felt@chromium.org + + The likelihood of a |CERT_DATE_INVALID| error being an attack. + + + + + + Removed on 8/1/13. + + felt@chromium.org + + The time between the SSL interstitial display and the user decision, when + the user accepts the SSL warning. This is only recorded for overridable SSL + warnings. Timing begins when user first focuses on the page. + + + + + + Removed 2018-11. + + estark@chromium.org + + When encountering a certificate error, Chrome looks for the well-known + Superfish certificate in the certificate chain and records this histogram as + true if the Superfish certificate is present and false otherwise. The + Superfish certificate is an indication that the user is vulnerable to + man-in-the-middle attacks because of software installed on their computer. + + + + + + Removed on 8/1/13. + + felt@chromium.org + + The time between the SSL interstitial display and the user decision, when + the user rejects the SSL warning. This is only recorded for overridable SSL + warnings. Timing begins when user first focuses on the page. + + + + + + Histogram for the deprecated implementation. + + pavely@chromium.org + melandory@chromium.org + Network channel used for invalidations. + + + + + Removed 2018-01. As of M65 use Mobile.CanonicalURLResult. + + gchatz@chromium.org + + The result of the operation to retrieve the page's canonical URL. + + + + + + Removed 09/2020. + + eugenebut@chromium.org + michaeldo@chromium.org + + Recorded when the iOS JavaScript Console logging is manually enabled or + manually disabled. + + + + + + Removed 2018-12. + + pkl@chromium.org + + Counts the times when a mailto: URL is tapped by user and whether the URL + has been rewritten for an available native Mail client app or not. + + + + + + Removed 2017-11. + + danyao@chromium.org + + Counts different types of navigation and loading events that are relevant to + counting page loads. + + + + + + Removed 2019-07. + + eugenebut@chromium.org + marq@chromium.org + + Recorded when the user quits the app. True if ChromeBrowserProvider is a + non-null pointer. Chrome for iOS has frequent crashes during shutdown caused + by dereferencing null or dangling ChromeBrowserProvider pointer + (crbug.com/983504). ChromeBrowserProvider can only be null if iOS did not + call application:didFinishLaunchingWithOptions: callback. This metric should + help to understand if ChromeBrowserProvider can even be null after app is + launched. + + + + + + Removed 2019-01. + + edchin@chromium.org + + Tracks the result of snapshotting when the user enters the tab switcher. + Recorded whenever the user enters the tab switcher. + + + + + + Removed 2019-04. + + edchin@chromium.org + marq@chromium.org + + WebStateList should be guaranteed to be non-nil during a + WebStateListObserver callback. This histogram counts the frequency of this + invariant holding when webStateList:DidDetachWebState: is invoked in + TabGridMediator. Violations of this invariant is the cause of real-world + crashes (https://crbug.com/877792), which were not currently reproducible in + testing. This histogram is used to retain visibility of the severity of this + issue, while preventing the crashes with a no-op. + + + + + + Removed 2019-04. + + edchin@chromium.org + marq@chromium.org + + WebStateList should be guaranteed to be non-nil during a + WebStateListObserver callback. This histogram counts the frequency of this + invariant holding when GetActiveTabID() is invoked in TabGridMediator. + Violations of this invariant is the cause of real-world crashes + (https://crbug.com/877792), which were not currently reproducible in + testing. This histogram is used to retain visibility of the severity of this + issue, while preventing the crashes with a no-op. + + + + + + Removed 2020-03. + + mrsuyi@chromium.org + eugenebut@chromium.org + + On iOS9, didStartProvisionalNavigation may be called with empty URL. However + in didCommitNavigation the URL will be about:blank. This historgram checks + if this still happens in later iOS versions, and records it when it happens. + + + + + + Removed 2020-01. + + avi@chromium.org + + The count of the number of characters in JavaScript dialog messages. + + + + + + Removed 2018-06. + + avi@chromium.org + + The count of the number of characters in JavaScript dialog messages that + were suppressed by the user. Compare with + JSDialogs.CountOfJSDialogMessageCharacters. + + + + + + Removed 2018-06. + + avi@chromium.org + + The count of the number of characters in JavaScript dialog messages. + + + + + + Removed 2018-06. + + avi@chromium.org + + The count of the number of newlines in JavaScript dialog messages. (This + does not count breaks inserted by the UI toolkit in wrapping the messages.) + + + + + + Removed 2016-02. + + avi@chromium.org + + The count of the number of characters in onbeforeunload messages. + + + + + + Removed 2016-02. + + avi@chromium.org + + The count of the number of newlines in onbeforeunload messages. (This does + not count breaks inserted by the UI toolkit in wrapping the messages.) + + + + + + Removed 2020-01. + + avi@chromium.org + The cause of dismissal of JavaScript dialogs. + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between closing a Javascript dialog and opening + another, to track very frequent dialogs. + + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between opening a Javascript dialog and opening + another, to track very frequent dialogs. + + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between opening a Javascript dialog and closing + it, to track very short-lived dialogs. + + + + + + Removed 2020-01. + + avi@chromium.org + + For dialogs, whether or not they were spawned by a tab that was foremost. + + + + + + Removed 2017-10. + + avi@chromium.org + + The site engagement values of sites showing onbeforeunload dialogs. Logged + once per dialog, whether shown or suppressed. + + + + + + Removed 2016-10. Site engagement needed to be measured in small buckets + anyway so it was never high-resolution enough for use. + + avi@chromium.org + + The site engagement values of sites showing dialogs. Logged once per dialog, + whether shown or suppressed. + + + + + + Removed 07/2016 in crbug.com/631204 with KeyboardUmaEventFilter removal. + + girard@chromium.org + + The time between keystrokes in Aura text fields. The only keystrokes that + are measured are ones that produce a printable character and are not over 5 + seconds apart. + + + + + + Removed 2019-07. Search key shortcut analysis is done. + + xiaohuic@chromium.org + zalcorn@chromium.org + + The time between a user pressing the Chrome OS "Search" key and + the second key being pressed down to active a shortcut. e.g. Search + L + would record the time between Search key down and L key down. If the user + pressed multiple keys after Search, we only record the first key down. + + + + + + Removed 2019-06. Shortcut viewer has been in production for many milestones + and its performance is adequate. + + jamescook@chromium.org + msw@chromium.org + wutao@chromium.org + + Time delay to make the visual update in response to a search-query. Note + that this does *not* include the initial delay to trigger the update after + the initial keystroke to change the search-query string. + + + + + + Removed 2019-06. Shortcut viewer has been in production for many milestones + and its performance is adequate. + + jamescook@chromium.org + msw@chromium.org + wutao@chromium.org + + Time delay for the visual update to be visible on screen in response to a + search-query. Note that this does *not* include the initial delay to trigger + the update after the initial keystroke to change the search-query string. + + + + + + Removed 2019-07 -- Replaced by + KeyboardAccessory.GeneratedPasswordDialogChoice*. + + ioanap@chromium.org + vasilii@chromium.org + + Android only. Records the interaction with the password generation dialog. + + + + + + Removed in 2019-07. + + brunoad@chromium.org + maroun@chromium.org + michaelpg@chromium.org + + Records usage of methods in KioskNextHome Mojo bridge. Recorded on every + method invocation. + + + + + + Removed in 2019-07. + + brunoad@chromium.org + maroun@chromium.org + michaelpg@chromium.org + + Records the result (success or failure) of every call from KioskNextHome + bridge to get the Android id. + + + + + + Removed in 2019-07. + + brunoad@chromium.org + maroun@chromium.org + michaelpg@chromium.org + + Records the result (success or error reason) of every call from + KioskNextHome bridge to launch an intent. + + + + + + Removed on 2019-07. + + + + agawronska@chromium.org + michaelpg@chromium.org + + Relative smoothness of animations of KioskNext Home state transitions. 100% + represents ideally smooth 60 frames per second. 50% represents only 30 + frames per second is achieved during the animations. 0% should not happen. + This metric is recorded exactly once when the user switches states of the + KioskNext Home. + + + + + + Removed in 2019-07. + + brunoad@chromium.org + maroun@chromium.org + michaelpg@chromium.org + Records when KioskNextShell becomes enabled or disabled. + + + + + Removed in 2019-07. + + brunoad@chromium.org + maroun@chromium.org + michaelpg@chromium.org + Records launches of KioskNextShell. Only true is recorded. + + + + + Removed 2016-06 -- hit rate is neglible. + + dfalcantara@chromium.org + + Records whether or not an invalid Android Intent was fired to launch Chrome. + (http://crbug.com/445136) + + + + + + Removed 2019-05 -- removed as part of removing mash code + + jamescook@chromium.org + + Records when a mojo ash UI service is started, for example the mojo app + version of the keyboard shortcut viewer. + + + + + + Removed 2018-09. No longer needed. + + chaopeng@chromium.org + input-dev@chromium.org + + We are considering allowing JS scrolling to prevent browser scroll position + restoration. This histogram measures the impact of that change, in terms of + how often restoration would be prevented by JS Scroll. Recorded after each + successful scroll restoration attempt. + + + + + + Replaced by LevelDB.ApproximateMemTableMemoryUse indefinitely. + + thildebr@chromium.org + + The approximate memory use of a LevelDB in bytes. Recorded right after + initializing an on-disk database. + + + + + + Removed in 2020-04. + + cmumford@chromium.org + chrome-owp-storage@google.com + The result of an open attempt of a leveldb. + + + + + Removed 2017-10. Superceded by LevelDB.SharedCache.KBUsed. + + cmumford@chromium.org + + The estimated size (in bytes) of the leveldb shared cache. Recorded once per + UMA ping. + + + + + + Removed 2020-04. + + cmumford@chromium.org + chrome-owp-storage@google.com + + The number of databases currently using the shared block cache. Recorded + once per UMA ping. + + + + + + No longer used. Removed in April, 2020. + + cmumford@chromium.org + + The estimated size (in kilobytes) of the leveldb shared cache. Recorded once + per UMA ping. + + + + + + Removed 2013-10. No thread-unsafety was found. + + dgrogan@chromium.org + + Linux and CrOS use unlocked_stdio(3). If it is used unsafely, record it + here. If there is no record of unsafety after chrome 29 has been in the + stable channel for a few weeks then revert this change. + + + + + + Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE. + + dgrogan@chromium.org + PlatformFileErrors encountered by a single leveldb method. + + + + + Removed 2020-04. + + dmurph@chromium.org + pwnall@chromium.org + + Errors (base::File::Error) encountered by a single leveldb method. + + + + + + Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewLogger. + + dgrogan@chromium.org + Errno of errors encountered in NewLogger. + + + + + Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewSequentialFile. + + dgrogan@chromium.org + Errno of errors encountered in NewSequentialFile. + + + + + Removed 2013-04. As of m28 use LevelDBEnv.IOError.NewRandomAccessFile. + + dgrogan@chromium.org + + File errors in leveldb ChromiumEnv's NewRandomAccessFile method. + + + + + + Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileAppend. + + dgrogan@chromium.org + Errno of errors encountered in WritableFileAppend. + + + + + Removed 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileFlush. + + dgrogan@chromium.org + Errno of errors encountered in WritableFileFlush. + + + + + Removed 2019-06. + + dgrogan@chromium.org + + Number of directories missing when Non-IDB LevelDBEnv tries to create a Lock + file. + + + + + + Removed as of September 20, 2017. + + cmumford@chromium.org + + File descriptor limit recorded every time LevelDB calls NewRandomAccessFile + for clients other than IndexedDB. + + + + + + Removed April, 2020. + + dmurph@chromium.org + pwnall@chromium.org + + When Non-IDB LevelDBEnv successfully retries an operation that had failed, + record the error from the most recent failed attempt. + + + + + + As of M54 no longer creating or using table backup files. + + dgrogan@chromium.org + + Success indicates a successful backup or restore operation for .ldb table + files when used by LevelDB clients other than IndexedDB. + + + + + + Removed 2013-04. As of m28 use LevelDBEnv.TimeUntilSuccessFor. + + dgrogan@chromium.org + + Time Non-IDB LevelDBEnv slept before successfully completing this operation. + 0 means success on the first try. + + + + + + Removed in 2020-04. + + dmurph@chromium.org + pwnall@chromium.org + + Time Non-IDB LevelDBEnv slept before successfully completing this operation. + 0 means success on the first try, as LevelDBEnv only sleeps when retries are + needed. + + + + + + Removed as of 11/2014, removed from code. + + feng@chromium.org + + A boolean that indicates whether the workaround of a Sony framework bug was + used. The metric is Android-specific, and is logged when the browser starts. + See more details at http://crbug.com/311644. + + + + + + Removed 2019-10. The code has stabilized, the failure rate is 0.04% on + Stable. + + lizeb@chromium.org + pasko@chromium.org + + Detailed status of the library prefetch final status. This is an expanded + version of LibraryLoader.PrefetchStatus. Android only, recorded at most once + per browser startup. + + + + + + Removed 2019-10. No longer recorded. + + lizeb@chromium.org + pasko@chromium.org + + Indicates whether the forking of a child process to prefetch the native + library succeeded. Android only, recorded at most once per browser startup. + + + + + + Deprecated 2020-04 in favor of Linux.Distro2 because distro-specific version + metrics were added. + + thestig@chromium.org + thomasanderson@chromium.org + The Linux distro used. Logged on each start up. + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + Records the time measured before starting DNS lookup until after the + connection is complete for main frame subresources observed by the + LoadingPredictor. Only resources that required network connection and + happened before the first contentful paint are recorded. + + + + + + Removed July 2019. + + thestig@chromium.org + Records number of attempts to start local discovery. + + + + + Removed July 2019. + + thestig@chromium.org + Time between detector restarts. + + + + + Removed July 2019. + + thestig@chromium.org + Time before detector trigger notifications. + + + + + Removed July 2019. + + thestig@chromium.org + Records events related to devices page. + + + + + Removed July 2019. + + thestig@chromium.org + + Windows only histogram that reports request time spend accessing firewall + rules. It's logged once per browser process lifetime, when local discovery + is used first time. + + + + + + Removed July 2019. + + thestig@chromium.org + + Windows only histogram that reports, whether a firewall is set, so we can + bind inbound sockets. It's logged once per browser process lifetime, when + local discovery is used first time. + + + + + + Removed July 2019. + + thestig@chromium.org + Records events related to local discovery notifications. + + + + + No longer emitted after onion soup refactor. + + mek@chromium.org + dmurph@chromium.org + + Size of the HTML5 LocalStorage DB in KB in the browser-side cache. + + + + + + No longer emitted after onion soup refactor. + + mek@chromium.org + dmurph@chromium.org + + Time to load HTML5 LocalStorage into the browser-side cache. + {LocalStorageSizes} + + + + + + + No longer emitted after onion soup refactor. Replaced with + LevelDBWrapper.CommitDelay. + + mek@chromium.org + dmurph@chromium.org + + Delay between a page making changes and those changes being written to the + DB. + + + + + + No longer omitted after onion soup refactor. Replaced by + LocalStorage.MojoTimeToPrime. {LocalStorageSizes} + + mek@chromium.org + dmurph@chromium.org + + Time to load HTML5 LocalStorage into the renderer-side cache. + + + + + + + No longer omitted after onion soup refactor. Replaced by + LocalStorage.MojoTimeToPrime. + + mek@chromium.org + dmurph@chromium.org + + Time to load HTML5 LocalStorage into the renderer-side cache. Note that the + name is not 'Renderer' prefixed for continuity with the old naming. + + + + + + Removed 01/2020. It was added to decide if the SplitSettings project could + safely decouple browser page zoom from ARC++/OS zoom. We decided it was safe + and did the decoupling in M78. + + jamescook@chromium.org + jessejames@chromium.org + cros-system-services@google.com + The user's default page zoom setting, recorded on login. + + + + + Removed in M85. Splitted in two: Login.PasswordChanged.ReauthReason and + Login.PasswordNotChanged.ReauthReason. + + achuith@chromium.org + + Tracks the reason why a user was sent through the GAIA re-auth flow. + + + + + + Removed 2020-02-01 because elapsed time should be measured by clients, if + they need it. + + + + amoylan@chromium.org + alanlxl@chromium.org + Elapsed time of one Chrome OS ML Service request. + + + + + Removed 07/2019 because we change to record total (shared+unshared) memory + rather than only private memory. Replaced by + MachineLearningService.PeakTotalMemoryKb. + + alanlxl@chromium.org + amoylan@chromium.org + + Peak private (non-shared) memory used by Chrome OS ML Service over the last + 24 hours. Sampled every 5 minutes, so may miss short-lived spikes. + + + + + + Removed 07/2019 because we change to record total (shared+unshared) memory + rather than only private memory. Replaced by + MachineLearningService.TotalMemoryDeltaKb. + + + + amoylan@chromium.org + alanlxl@chromium.org + + Memory usage increase caused by one Chrome OS ML Service request. + + + + + + Removed 07/2019 because we change to record total (shared+unshared) memory + rather than only private memory. Replaced by + MachineLearningService.TotalMemoryKb. + + alanlxl@chromium.org + amoylan@chromium.org + + Private (non-shared) memory used by Chrome OS ML Service, sampled every 5 + minutes. + + + + + + Removed in M86. + + yilkal@chromium.org + michaelpg@chromium.org + cros-families-eng@google.com + + The depth of blocked frame in the frame tree. The value is recorded when the + renderer frame hosting the blocking page finishes loading. + + + + + + Removed 07/2020 as it is no longer used. + + achuith@chromium.org + + Chrome OS histogram that keeps track of supervised user password change + result. + + + + + + Removed in M85. + + treib@chromium.org + escordeiro@chromium.org + menegola@chromium.org + + The total amount of time taken to parse the JSON contents of a whitelist out + of process. + + + + + + Removed in M85. + + treib@chromium.org + escordeiro@chromium.org + menegola@chromium.org + + The amount of time taken to read a whitelist file from disk. + + + + + + Removed in M85. + + treib@chromium.org + escordeiro@chromium.org + menegola@chromium.org + + The total amount of time taken to load a whitelist from disk and parse it, + including jumps to the blocking thread. + + + + + + Removed as of 2019-10-21. + + mgiuca@chromium.org + mlamouri@chromium.org + Tracks whether the parsed Manifest is the empty Manifest. + + + + + Removed as of July 21, 2014. + + Please list the metric's owners. Add more owner tags as needed. + + Whether accelerated compositing was used for HTML5 media rendering. + + + + + + Removed as of 08/2017 + + qinmin@chromium.org + + Android: Records whether a regular media URL is HLS (HTTP Live Streaming) + media or not. + + + + + + Removed as of 08/2017 + + sandersd@chromium.org + + Android: Records which HLS prediction based on the original URL was best. + + + + + + Removed as of 04/2017 + + qinmin@chromium.org + + Android: Number of consecutive media server crashes monitored before it is + reset to 0. Reset happens if there are no crashes in a minute, or if user + hits the "try again" button on the media throttle info bar. + + + + + + Removed as of 04/2017 + + qinmin@chromium.org + + Android: The distribution of responses to the media throttle infobar prompt. + + + + + + Removed as of June 12, 2017. Replaced by + Media.ChromeArcVideoDecodeAccelerator.InitializeResult. + + johnylin@chromium.org + + Counts of status values returned from calls to + ArcGpuVideoDecodeAccelerator::Initialize(). + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Indicates if the Automatic Gain Control (AGC) is enabled or not. Only + sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed from code as of 07/2019. + + mlamouri@chromium.org + media-dev@chromium.org + + Records time from load starts until audio starts based on autoplay + attribute. + + + + + + Removed from code as of 07/2019. + + mlamouri@chromium.org + media-dev@chromium.org + + Records time from load starts until audio starts based on play method. + + + + + + Removed as of May 2019. + + + + dalecurtis@chromium.org + media-dev@chromium.org + + Records whether the given bitstream audio output format is supported. + Recorded when the browser or audio process AudioManager is constructed. + + + + + + Removed as of 02/2017. + + tommi@chromium.org + + A boolean that reflects whether or not an error was reported during audio + capture. + + + + + + Removed March 2019. + + grunell@chromium.org + + The audio input device latency. The time from when a frame was captured + until it reaches Chrome's platform audio implementation. Sampled for every + buffer received from the device, and reports the latency for the first frame + in the buffer. + + + + + + Removed June 2020. + + maxmorin@chromium.org + olka@chromium.org + + Error codes from AudioInputStreamBroker::ObserverBindingLost. They describe + why an audio input stream ended. + + + + + + Replaced by Media.Audio.Capture.StreamCallbackError2 + + maxmorin@chromium.org + + When AudioInputDevice is stopped, this stat is recorded with whether an + error callback was ever received over IPC. + + + + + + Removed March 2019. + + grunell@chromium.org + + The number of times a glitch was detected by detecting skipped frames (as + with Media.Audio.Capture.Glitches) and disconinuity was flagged by the OS at + the same time (as with Media.Audio.Capture.Win.Discontinuities). Sometimes + these indications are not consistent with each other so this metric helps + understanding how often they aren't. This value is logged when an audio + input stream is closed. + + + + + + Removed March 2019. + + grunell@chromium.org + + The audio engine's period between processing passes. See + IAudioClient::GetDevicePeriod. This value is logged when an audio input + stream is opened. + + + + + + Removed March 2019. + + grunell@chromium.org + + The number of times the device position was less than expected during the + lifetime of an audio stream. This value is logged when an audio input stream + is closed. + + + + + + Removed March 2019. + + grunell@chromium.org + + The number of glitches that were detected at the OS level on Windows while + an audio stream was active, as reported by the OS via the discontinuity flag + (see IAudioCaptureClient::GetBuffer). This value is logged when an audio + input stream is closed. + + + + + + Removed March 2019. + + grunell@chromium.org + + The endpoint buffer size for input audio. This value is logged when an audio + input stream is opened. + + + + + + Removed March 2019. + + grunell@chromium.org + + The maximum stream latency as reported by the OS. See + IAudioClient::GetStreamLatency. This value is logged when an audio input + stream is opened. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Indicates if the size of the audio unit's IO buffer was changed when + starting an input audio stream. Sampled each time an AUAudioInputStream + instance is closed, i.e., we know that input audio has started as it should + when this value is stored. Can be compared with + Media.Audio.InputBufferSizeWasChangedMac which is only added when input + audio fails to start. + + + + + + Removed Feb 2018. Was put in place to debug missing callback issues that + have since been resolved. + + henrika@chromium.org + + Lists device properties that have been changed during an audio input stream + session. We update a map of different property changes during a session and + all these values are recorded when an AUAudioInputStream object is closed, + hence multiple enum values can be emitted when the histogram is stored. + + + + + + Removed Feb 2018. Was put in place to debug missing callback issues that + have since been resolved. + + henrika@chromium.org + + Lists device properties that have been changed during an audio input stream + session. Only sampled when Media.Audio.InputStartupSuccessMac reports + 'Failure' and multiple enum values can be emitted each time that happens. + + + + + + Removed May 2017. Restart mechanism is removed. + + henrika@chromium.org + + Counts the total number of times an attempt to restart input audio has been + done. The value is stored once when a stream is closed and updated when it + has been detected that input audio callbacks are not generated as expected. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Indicates if audio capturing started with a small delay or not. Sampled each + time an AUAudioInputStream instance is closed, i.e., we know that input + audio has started as it should when this value is stored. Can be compared + with Media.Audio.InputStartWasDeferredMac which is only added when input + audio fails to start. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Indicates if audio capturing started with a small delay or not. Only sampled + when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Indicates if the Mac OSX device is on battery power or not. Only sampled + when Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Number of created default input audio streams. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Number of created low-latency input audio streams. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Number of created output audio streams. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of October 2019. + + armax@chromium.org + + When a mojo audio stream factory is destructed, the streams it created are + also destructed. This is a potential source of stat differences between the + new mojo code and the old Chrome IPC code, where streams could potentially + stick around until the destruction of the owning RenderProcessHost. This + histogram measures how many output streams are destructed each time a mojo + output stream factory is destructed. + + + + + + Removed in June 2020. + + guidou@chromium.org + olka@chromium.org + + Number of simultaneous inputs coming to the AudioRendererMixer which renders + audio with user specified latency. The value is logged each time it reaches + a new maximum for the mixer. It is useful for evaluating how mixing audio in + renderer reduces the number of output audio streams going from the renderer + to the browser. + + + + + + Removed in June 2020. + + olka@chromium.org + + Number of simultaneous inputs coming to the AudioRendererMixer which renders + audio with interactive latency. The value is logged each time it reaches a + new maximum for the mixer. It is useful for evaluating how mixing audio in + renderer reduces the number of output audio streams going from the renderer + to the browser. + + + + + + Removed in June 2020. + + olka@chromium.org + + Number of simultaneous inputs coming to the AudioRendererMixer which renders + audio with playback latency. The value is logged each time it reaches a new + maximum for the mixer. It is useful for evaluating how mixing audio in + renderer reduces the number of output audio streams going from the renderer + to the browser. + + + + + + Removed in June 2020. + + olka@chromium.org + + Number of simultaneous inputs coming to the AudioRendererMixer which renders + audio with real time latency. The value is logged each time it reaches a new + maximum for the mixer. It is useful for evaluating how mixing audio in + renderer reduces the number of output audio streams going from the renderer + to the browser. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Subset of audio output latencies encountered by the renderer so far. Logged + each time an audio output with a new latency starts playing. The values are + bitsets where each bit represents corresponding latency according to + AudioLatency::LatencyType. Useful for understanding usecases for audio + output mixing in renderer. + + + + + + Removed June 2019. + + olka@chromium.org + + Reflects how regularly browser issues audio requests to renderer. Depends on + how well the system buffer size the browser side renders audio at and the + buffer size it requests from renderer are aligned. When zero, it means + renderer buffer size is a multiple of system buffer size, and render calls + from browser to renderer are issued evenly. When -1, it means the renderer + buffer size is larger than system buffer size, but is not an exact multiple + of it; in this case browser periodically skips a call to renderer. When + positive, floor(value/2) reflects the number of extra consecutive render + requests issued by browser to renderer each time to fulfill the system audio + render request; if (value/2) is not integer, then plus one more extra call + is issued periodically. The metric is recorded on the edge between browser + and renderer. On Mac the system buffer size may vary dynamically, the metric + does not capture that: only the buffer size mismatch introduced by audio + output device configuration is captured. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The time delta from an AudioInputDevice sending a RecordStream message to it + getting its first data callback. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The time delta between the moment a MojoAudioInputIPC instance on the + renderer process requests a new stream from the browser to the moment it + receives a response. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The time delta from an AudioOutputDevice sending its first PlayStream + message to it getting its first data callback. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The time delta between the moment a MojoAudioOutputIPC instance on the + renderer process requests a new stream from the browser to the moment it + receives a response. + + + + + + Removed 09/2018, and replaced by + Media.Audio.Render.StreamBrokerDisconnectReason2. + + jonasolsson@chromium.org + maxmorin@chromium.org + olka@chromium.org + + Error codes from AudioOutputStreamBroker::ObserverBindingLost. They describe + why an audio output stream ended. + + + + + + Removed on April 2020. + + guidou@chromium.org + olka@chromium.org + + Describes why and in which state an audio output stream ended. + + + + + + Removed as of March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + If the document was destroyed after the broker requested the output stream + from the audio service, but before it received the reply: how long ago the + stream was requested. + + + + + + Removed as of March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + Time interval between the moment the broker requested the output stream from + the audio service, and the moment it received the reply. + + + + + + Replaced by Media.Audio.Render.StreamCallbackError2 + + maxmorin@chromium.org + + When AudioOutputDevice is stopped, this stat is recorded with whether an + error callback was ever received over IPC. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Counts the number of times the system has resumed from power suspension. + Counting is reset each time Chrome restarts. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Aug 2018. + + henrika@chromium.org + + Reports the system uptime in hours for Mac OS X devices. Only sampled when + Media.Audio.InputStartupSuccessMac reports 'Failure'. + + + + + + Removed as of Jan 2018. + + minyue@chromium.org + + Captures bit-exact audio repetitions with pre-defined look back time. As + soon as a repetition is detected, its look back time is reported. Ideally, + no reports should be generated. + + + + + + Removed 06/2019 in issue 975301. + + dalecurtis@chromium.org + Audio channel layout in HTML5 media. + + + + + Removed as of 02/2017. + + dalecurtis@chromium.org + + Whether capture started successfully after an input stream startup was + requested. + + + + + + Removed 06/2020. No longer needed. + + dalecurtis@chromium.org + Measures the time taken for AudioInputDeviceManager:: + + + + + Removed 06/2020. No longer needed. + + dalecurtis@chromium.org + Measures the time taken for AudioOutputController:: + + + + + Removed Mar 2016 in favor of a new PipelineStatus code. + + scherkus@chromium.org + Captures statistics for various AudioRendererImpl events. + + + + + Removed 02/2017. No longer needed. + + grunell@chromium.org + + The maximum number of simultaneous audio render streams over IPC created in + AudioRendererHost for a render process. Logged at render process shutdown. + + + + + + Removed 02/2017. No longer needed. + + grunell@chromium.org + + The maximum number of simultaneous audio render streams over IPC created in + AudioRendererHost for all render processes. Logged at render process + shutdown. + + + + + + Removed 06/2019 in issue 975301. + + dalecurtis@chromium.org + + Audio sample format in HTML5 media. Logged when Audio Decoder initializes. + + + + + + Removed 06/2019 in issue 975301. + + dalecurtis@chromium.org + Audio samples per second in HTML5 media. + + + + + Removed 06/2019 in issue 975301. + + dalecurtis@chromium.org + + Audio samples per second in HTML5 media (atypical values, in Hz). + + + + + + Removed 06/2018. Split into Media.AudioService.ObservedInitialDowntime and + Media.AudioService.ObservedDowntime2. + + marinaciocea@chromium.org + maxmorin@chromium.org + olka@chromium.org + + The audio service downtime, observed from the browser process. The downtime + interval is measured either from when the audio service listener is + initialized to the first audio service start, or from the audio service + shutdown to the next startup. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The audio service downtime, observed from the browser process. The downtime + interval is measured from the audio service shutdown to the next startup. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The audio service downtime, observed from the browser process. The downtime + interval is measured from when the audio service listener is initialized to + the first audio service start. + + + + + + Removed 10/2018. Covered by the more generic stats + ChildProcess.Crashed.UtilityProcessHash and + ChildProcess.Launched.UtilityProcessHash. + + marinaciocea@chromium.org + maxmorin@chromium.org + olka@chromium.org + + The termination status of the audio service process, observed from the + browser process. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The start result of the audio service, observed from the browser process. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The startup time of the audio service, observed from the browser process. + The startup time interval is measured from when a connect request results in + the audio service being created to the moment when the audio service is + started. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The uptime of the audio service, observed from the browser process. The + uptime interval is measured from when the audio service starts to when it is + shut down (either normally or through kill/crash). This metric includes + Media.AudioService.Uptime measurements, logged by the audio service on + normal shutdown. A difference between Media.AudioService.ObservedUptime and + Media.AudioService.Uptime indicates buggy audio service behavior. + + + + + + Removed on March 2020. + + + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The time interval between the moment when a client issues a system + information request to the audio service, and the moment it receives the + responce. Logged individually for each request type. + + + + + + Removed on March 2020. + + armax@chromium.org + guidou@chromium.org + olka@chromium.org + + The uptime of the audio service, observed from the audio service. The uptime + interval is measured from the audio service start to the audio service stop. + + + + + + Removed July 2019. No longer needed. + + grunell@chromium.org + + State of the media stream audio track processing, sampled once during the + life time of a MediaStreamAudioProcessor. + + + + + + Removed January 2019. No longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + The result of autoplaying video elements in cross-origin iframes. + + + + + + Removed 03/2016. No longer needed. + + watk@chromium.org + + The time that a bitstream buffer spends in AVDA's pending bitstream buffer + queue before it is fed to MediaCodec. + + + + + + Removed 10/2016. No longer needed. + + liberato@chromium.org + + Number of times that AVDA stopped decoding because MediaCodec failed to + provide a FORMAT_CHANGED message before sending decoded frames back. True + counts indicate instances where FORMAT_CHANGE was missed, while false + instances indicate any MediaCodec initialization by AVDA. + + + + + + Removed 10/2016. No longer needed. + + watk@chromium.org + + The number of concurrently running AndroidVideoDecodeAccelerators. Logged + during each AVDA initialization. + + + + + + Removed 10/2016. No longer needed. + + liberato@chromium.org + + Number of times that AVDA's deferred rendering encountered a virtual GL + context. True counts indicate virtual, false counts indicate not. + + + + + + Removed 06/2018. This has been renamed to + Media.CodecImage.SurfaceTextureGLOwner.WaitTimeForFrame and + Media.CodecImage.ImageReaderGLOwner.WaitTimeForFrame. + + liberato@chromium.org + + Time spent waiting for a frame to become available in a Non Overlay after + requesting that MediaCodec renders it. + + + + + + Removed 10/2019 in issue 1000058; no longer needed. + + hubbe@chromium.org + media-dev@chromium.org + Kb read by media demuxer from MultiBuffer cache. + + + + + Removed 10/2019 in issue 1000058; no longer needed. + + hubbe@chromium.org + media-dev@chromium.org + Kb read by from network into MultiBuffer cache. + + + + + Removed 10/2019 in issue 1000058; no longer needed. + + hubbe@chromium.org + dalecurtis@chromium.org + + Total number of bytes buffered over the lifetime of a WebMediaPlayer, + suffixed by type of playback. + + + + + + Removed 06/2019 in issue 975278. + + dalecurtis@chromium.org + + Whether a media response might be used to satisfy a future request. + + + + + + Removed as of Dec 18, 2017. Replaced by + Media.GpuArcVideoDecodeAccelerator.InitializeResult. + + johnylin@chromium.org + + Counts of status values returned from calls to + ChromeArcVideoDecodeAccelerator::Initialize(). + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + The average number of delayed and dropped frames for the ChromeCast + application. Reported every 5 seconds. + + + + + + Removed 07/2015 in issue 508534. + + mfoltz@chromium.org + + The average number of displayed frames for the ChromeCast application. + Reported every 5 seconds. + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + Time needed to pre-buffer A/V data before the actual playback for the + ChromeCast application. + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + Time needed to buffer A/V data after an abort for the ChromeCast + application. + + + + + + Not collected as of M83. + + mfoltz@chromium.org + + Time needed to buffer A/V data after an underrun for the ChromeCast + application. + + + + + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut + + ericrk@chromium.org + liberato@chromium.org + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut + + + + + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame + + vikassoni@chromium.org + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame + + + + + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut + + ericrk@chromium.org + liberato@chromium.org + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.FrameTimedOut + + + + + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame + + liberato@chromium.org + + Removed 07/2019. This has been renamed to + Media.CodecImage.CodecBufferWaitCoordinator.WaitTimeForFrame + + + + + + Removed July 2017 in favor of Media.Controls.CTR.DownloadButton. + + mlamouri@chromium.org + nyquist@chromium.org + media-dev@chromium.org + + Records events and user interactions related to the download button shown on + media elements. + + + + + + Removed 07/2019 as no longer needed. + + beccahughes@chromium.org + media-dev@chromium.org + + Records the amount of time the overflow menu is displayed until the user + clicked on a menu item. The overflow menu is shown by clicking the three + dots on the media controls and is used to show more controls when there is + not enough space. This histogram will record up to 100 seconds with accuracy + to the second. + + + + + + Removed 07/2019 as no longer needed. + + beccahughes@chromium.org + media-dev@chromium.org + + Records the amount of time the overflow menu is displayed until the user + dismissed the menu without clicking on a menu item. The overflow menu is + shown by clicking the three dots on the media controls and is used to show + more controls when there is not enough space. This histogram will record up + to 100 seconds with accuracy to the second. + + + + + + Removed May 19 2016 in favor of Media.Controls.Show.{Audio,Video} + + mlamouri@chromium.org + + Record whether the default media controls were shown and why every time they + could be shown. + + + + + + Removed Sep 15 2015 in favor of Media.DetectedAudioCodecHash + + jrummell@chromium.org + Audio codec used in HTML5 media. + + + + + Removed 07/2019 in issue 975315. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected audio tracks in HTML5 media. Not all may be usable by the + player. + + + + + + Removed 07/2019 in issue 975315. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected text tracks in HTML5 media. Not all may be usable by the + player. + + + + + + Removed 07/2019 in issue 975315. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected video tracks in HTML5 media. Not all may be usable by the + player. + + + + + + Removed Sep 15 2015 in favor of Media.DetectedVideoCodecHash + + jrummell@chromium.org + Video codec used in HTML5 media. + + + + + Removed 10/2015 in favor of Permissions.Action. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the actions taken in the media infobar, which prompts the users for + device permission. + + + + + + Removed 03/2017 in favor of Media.Duration2 with larger max bucket. + + scherkus@chromium.org + Duration in milliseconds of HTML5 media (when known). + + + + + Removed 06/2019. Not useful. + + dalecurtis@chromium.org + Duration in milliseconds of HTML5 media (when known). + + + + + Removed 12/2018 since we had enough data to make a decision. + + dalecurtis@chromium.org + media-dev@chromium.org + + Did IsResolutionSupportedForDevice() succeed or fail during + ID3D11VideoDevice::CreateVideoDecoder(). + + + + + + Removed 02/2020. Not useful. + + liberato@chromium.org + sandersd@chromium.org + + Whenever an error is logged from the DXVAVDA, this records the line in + dxva_video_decode_accelerator.cc where the failure occurred. + + + + + + Removed 12/2018 since we had enough data to make a decision. + + dalecurtis@chromium.org + media-dev@chromium.org + + Did IsResolutionSupportedForDevice() succeed or fail during + ID3D11VideoDevice::GetVideoDecoderConfig(). + + + + + + Removed 02/2020. Not useful. + + jbauman@chromium.org + sandersd@chromium.org + + Whenever an error is logged from the DXVAVDA picture buffer code, this + records the line in dxva_picture_buffer_win.cc where the failure occurred. + This histogram can only meaningfully be compared between different versions + of Chromium if no line numbers in that file changed between those versions. + + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + media-dev@chromium.org + addKey result + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + cancelKeyRequest result. + + + + + Removed 08/2019, replaced with Media.EME.CdmFileIO.TimeTo.ReadFile. + + media-dev@chromium.org + The actual time spent by the CDM reading a file. + + + + + Removed 08/2019, replaced with Media.EME.CdmFileIO.TimeTo.WriteFile. + + media-dev@chromium.org + The actual time spent by the CDM writing a file. + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + media-dev@chromium.org + generateKeyRequest result. + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + media-dev@chromium.org + KeyAdded event count. + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + media-dev@chromium.org + KeyError event count. + + + + + Removed 02/2016 with removal of prefixed EME. + + xhwang@chromium.org + media-dev@chromium.org + + Key system support query status and result. Each enum value will be reported + at most once per renderer process. + + + + + + Renamed to Media.EME.EncryptedEvent in 10/2017. + + xhwang@chromium.org + media-dev@chromium.org + EME NeedKey event count. + + + + + Removed 07/2019 as no longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + Records the reason why the Media Engagement data was cleared. Partial + changes and full wipeout will both be recorded as one event. + + + + + + Removed 07/2019 as no longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + Time taken to load the Media Engagement Preloaded List. It should be + recorded once per load of the list which will be once per start up with + additional loads when the list is updated while running. + + + + + + Removed 07/2019 as no longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + Time taken to lookup an entry in the Media Engagement Preloaded List. This + is recorded for every lookup, regardless of its success. + + + + + + Removed 11/2018 in Issue 900679 as we are no longer using this. + + beccahughes@chromium.org + media-dev@chromium.org + + Media engagement scores for each origin, recorded at Chrome startup. It is + converted to a percentage so should be divided by 100 to get the actual + score. + + + + + + Removed 07/2019 as no longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + Records creation and playback status of a Media Engagement Session. This is + recorded at the same time as the data is commited into the content settings + database. + + + + + + Removed 07/2019 as no longer needed. + + mlamouri@chromium.org + media-dev@chromium.org + + Records creation and playback status of a restored Media Engagement Session. + This is recorded at the same time as the data is commited into the content + settings database. Restored information are recorded in addition of regular + ones (Media.Engagement.Session). + + + + + + Removed 07/2019 as no longer needed. + + beccahughes@chromium.org + media-dev@chromium.org + + Recorded when the history is cleared and the media engagement data are + similarly cleared. It records the reduction in score for each affected + origin. The algorithm is made to reduce the score by 0.0 as much as possible + and if it fails, the score will actually become 0.0 so every reduction also + represent the value of the previous score. + + + + + + Removed May 2018; has been 32-bit for years now. + + dalecurtis@chromium.org + + Bits per channel of the hardware audio device which failed to open in low + latency mode and required high latency fallback. + + + + + + Removed 06/2019 in issue 975072. Not useful. + + dalecurtis@chromium.org + + Channel count of the hardware audio device which failed to open in low + latency mode and required high latency fallback. + + + + + + Removed 06/2019 in issue 975072. Not useful. + + dalecurtis@chromium.org + + Channel layout of the hardware audio device which failed to open in low + latency mode and required high latency fallback. + + + + + + Removed 06/2019 in issue 975072. Not useful. + + dalecurtis@chromium.org + + Samples per second of the hardware audio device which failed to open in low + latency mode and required high latency fallback. + + + + + + Removed 06/2019 in issue 975072. Not useful. + + dalecurtis@chromium.org + + Samples per second of the hardware audio device (atypical values, in Hz) + which failed to open in low latency mode and required high latency fallback. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average number of delayed and dropped frames for the Fling application. + Reported every 5 seconds. + + + + + + Removed 07/2015 in issue 508534. + + halliwell@chromium.org + + The average number of displayed frames for the Fling application. Reported + every 5 seconds. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to pre-buffer A/V data before the actual playback for the Fling + application. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to buffer A/V data after an abort for the Fling application. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to buffer A/V data after an underrun for the Fling application. + + + + + + Removed in December 2019 because GpuVideoDecoderError is gone and + crbug.com/902968 is fixed. + + sandersd@chromium.org + Counts of video decode errors reported to GpuVideoDecoder. + + + + + Removed in December 2019 because GpuVideoDecoderError is gone and + crbug.com/902968 is fixed. + + posciak@chromium.org + Results of attempts to GpuVideoDecoder::Initialize(). + + + + + Removed May 2018; has been 32-bit for years now. + + dalecurtis@chromium.org + Bits per channel of the hardware audio device. + + + + + Removed 06/2019 in issue 975072. Not useful. + + dalecurtis@chromium.org + + Samples per second of the hardware audio device (atypical values, in Hz). + + + + + + Removed June 2017. Found that the MediaInfoLoader class (the only user of + this histogram) is no longer used by anyone. + + qinmin@chromium.org + + The time it takes to perform redirect tracking and a CORS access check while + preparing to play a media file. + + + + + + Removed 05/2015 in Issue 1141703002. FFmpeg is now statically linked. + + scherkus@chromium.org + + Errors returned by LoadLibraryEx on Windows while attempting to load + ffmpegsumo.dll. + + + + + + Removed and removed from code as of 02/2016. + + henrika@chromium.org + + Invalid input sample rate when calling AUAudioInputStream::Open on Mac. + + + + + + Removed from code on 05/2020. + + dalecurtis@chromium.org + sandersd@chromium.org + + Whether the WMPI data source is streaming (does not support range requests). + + + + + + Removed in favor of Media.Learning.BinaryThreshold.Aggregate.* + + + + liberato@chromium.org + chcunningham@chromium.org + + Confusion matrix for MediaCapabilities local learning experiment, using a + lookup table and the base MediaCapabilities features (resolution, frame + rate, video format). A positive outcome is smooth playback, while a negative + outcome is not smooth. For example, a False Negative indicates that we + predicted a negative result (not smooth playback), but we later observed + that the result was positive (smooth playback). + + For those observations for which we could not make a prediction due to data + sparsity, the "no-prediction" buckets indicate whether the + observation was positive or negative. + + This is very similar to the existing MediaCapabilities implementation, but + uses the same training set as other learners. + + The "BaseTable" variant uses a lookup table as the model, and uses + the original MediaCapabilities features (resolution, frame rate, video + format). + + The "BaseTree" variant uses ExtraTrees model and the same features + as the BaseTable variant. + + The "EnhancedTree" variant uses ExtraTrees, plus additional + features such as NetworkType. The exact set of features is still in flux, so + be sure to restrict reporting to a particular Chromium version. + + + + + + Removed and removed from code as of January 2019. + + ossu@chromium.org + grunell@chromium.org + + Whether or not the MediaElement is at a playback position of infinity when + checking if playback has ended. + + + + + + Removed 08/2018. Histogram Eraser marked this histogram as unnecessary. See + https://crbug.com/871467 for details. + + henrika@chromium.org + + Level of the microphone volume measured in percent. This value can be larger + than 100% on Linux. Measured approximately four times per minute. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + midi-dev@chromium.org + Connected input port numbers on the initialization. + + + + + Removed 06/2019. + + toyoshim@chromium.org + midi-dev@chromium.org + Connected output port numbers on the initialization. + + + + + Removed 06/2019. + + toyoshim@chromium.org + midi-dev@chromium.org + + The final status of MidiManager on destruction. This can monitor unexpected + failures on initializing platform dependent MIDI stuff. + + + + + + Removed 05/2018. Splicing no longer performed on buffers with estimated + duration. See https://crbug.com/396634. + + chcunningham@chromium.org + + Categorizes MSE audio splicing by the type of duration used in the + overlapped buffer. + + + + + + Removed 07/2019 in issue 975090. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected audio tracks in Media Source Extensions playback. Not all + may be usable by the player. + + + + + + Removed 07/2019 in issue 975090. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected text tracks in Media Source Extensions playback. Not all + may be usable by the player. This count includes only explicitly signalled + tracks in MSE initialization segments parsed from WebM or ISO BMFF + bytestreams. + + + + + + Removed 07/2019 in issue 975090. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of detected video tracks in Media Source Extensions playback. Not all + may be usable by the player. + + + + + + Deleted along with browser side MSE implementation. + + qinmin@chromium.org + timav@chromium.org + + Relative number of late audio frames wrt total number of audio frames in MSE + playback, multiplied by one million. The audio frame is considered late if + it might cause an underrun, i.e. comes from decoder when audio buffer is + already depleted. + + + + + + Deleted along with browser side MSE implementation. + + qinmin@chromium.org + timav@chromium.org + + Relative number of late video frames wrt total number of video frames in MSE + playback, multiplied by one million. The video frame is late if it missed + its presentation time as determined by PTS when it comes from decoder. The + rendering policy (i.e. render or skip) does not affect it. + + + + + + Removed 07/2019 in issue 975898. + + wolenetz@chromium.org + media-dev@chromium.org + + Number of tracks specified to AddId() for Media Source Extensions playback. + May be called multiple times per element if playback is dynamically altered. + + + + + + Renamed to Media.LoadType. + + acolwell@chromium.org + + Whether Media Source Extensions is specified for playback of Media elements. + Sampled when media pipeline starts. + + + + + + Deleted along with browser side MSE implementation. + + qinmin@chromium.org + timav@chromium.org + + Duration of an uninterrupted MSE playback. This is the time interval between + the playback starts or resumes and the moment when user stops the playback + by pressing pause, initiating a seek etc. Measured in media time in + milliseconds. + + + + + + Deleted along with browser side MSE implementation. + + qinmin@chromium.org + timav@chromium.org + + Relative number of starvations wrt total number of frames in MSE playback, + multiplied by one million. Starvation happens when the player interrupts the + regular playback and asks for more data, conditions are player-specific. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The audio bit rate as reported by the Netflix application. May be reported + multiple times as network conditions change during playback. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of audio channels as reported by the Netflix application. May be + reported multiple times as network conditions change during playback. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average number of delayed and dropped frames for the Netflix + application. Reported every 5 seconds. + + + + + + Removed 07/2015 in issue 508534. + + halliwell@chromium.org + + The average number of displayed frames for the Netflix application. Reported + every 5 seconds. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Video bit rate as reported by the Netflix application. May be reported + multiple times as network conditions change during playback. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Video height as reported by the Netflix application. May be reported + multiple times as network conditions change during playback. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average number of delayed and dropped frames for the PlayMovies + application. Reported every 5 seconds. + + + + + + Removed 07/2015 in issue 508534. + + halliwell@chromium.org + + The average number of displayed frames for the PlayMovies application. + Reported every 5 seconds. + + + + + + Removed 03/2020 in https://crbug.com/1053019. + + media-dev@chromium.org + + Indicates if a suspend initiated for preload=metadata was ideal. I.e. we did + not immediately resume after completing the suspend when signaling + ReadyState::HAVE_FUTURE_DATA. + + + + + + Removed 11/2017 in issue 788940. + + miu@chromium.org + + The difference between the estimated transmission capacity and the media + bitrate when capacity is higher. + + + + + + Removed 11/2017 in issue 788940. + + miu@chromium.org + + The difference between the media bitrate and the estimated transmission + capacity when media bitrate is higher. + + + + + + Removed as no more poster image is being downloaded while remoting content. + + miu@chromium.org + + Measures the amount of time it took to ultimately fail to download a poster + image for an HTML5 video while remoting content. + + + + + + Removed as no more poster image is being downloaded while remoting content. + + miu@chromium.org + + Measures the amount of time it took to successfully download a poster image + for an HTML5 video while remoting content. + + + + + + Removed 11/2017 in issue 788940. + + miu@chromium.org + + The estimated content bitrate (including both audio and video) when starting + a remoting session. + + + + + + Removed 11/2017 in issue 788940. + + miu@chromium.org + + The estimated transmission capacity when starting a remoting session. + + + + + + Renamed to Media.RTCVideoDecoderInitDecodeSuccess. + + posciak@chromium.org + Results of attempts to RTCVideoDecoder::InitDecode(). + + + + + Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. + + beccahughes@chromium.org + media-dev@chromium.org + + The number of times a media session abandon audio focus and where the + abandon audio focus call originated from. This is recorded every time a + media session abandons audio focus because it has stopped playing. + + + + + + Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. + + beccahughes@chromium.org + media-dev@chromium.org + + The number of times a media session requested audio focus and where that + focus request originated from. This is recorded every time a media session + requests audio focus because it wants to start playing. + + + + + + Removed 8/2019 in Issue 995521 due to expiry and not needed anymore. + + beccahughes@chromium.org + media-dev@chromium.org + + The number of times a media session requested audio focus for a specific + audio focus type. This is recorded every time a media session requests a new + audio focus type. This may be because the session has started playing or the + type of media being played has changed. + + + + + + Removed 07/2019 in issue 975367. + + media-dev@chromium.org + + Whether a SRC= playback had a poster set at load() when the effective + preload type is "auto". Note that this includes audio playbacks, + since we do not have track metadata at load(); audio elements never have + posters. + + + + + + Removed 07/2019 in issue 975367. + + media-dev@chromium.org + + Whether a SRC= playback had a poster set at load() when the effective + preload type is "metadata". Note that this includes audio + playbacks, since we do not have track metadata at load(); audio elements + never have posters. + + + + + + Removed from code as of 07/2019. + + + + mlamouri@google.com + media-dev@chromium.org + + The width of the media timeline track in CSS pixels, recorded the first time + a media element with controls starts playing (strictly speaking, it's the + width in CSS pixels ignoring CSS transforms, multiplied by pageZoomFactor, + but deliberately ignoring pinch zoom's pageScaleFactor). + + + + + + Removed from code 2018/11/29. + + hubbe@chromium.org + media-dev@chromium.org + + Time in milliseconds from when WebMediaPlayerImpl starts loading until the + first video frame has been shown IFF six or more videos are loading in + parallel. + + + + + + Removed from code 2014/6/18. + + scherkus@chromium.org + + Time in milliseconds from HTML5 media pipeline creation to playing event. + + + + + + Removed 06/2019 in issue 975278. + + dalecurtis@chromium.org + + Reasons a media response won't be used to satisfy a future request. + + + + + + Removed Feb 2017. Media.UnderflowDuration provides more useful counts. + + dalecurtis@chromium.org + + The number of times a src= playback has underflowed; i.e. ran out of data. + + + + + + Removed Aug 2017. Media.UnderflowDuration2.SRC removes zero-weighting so + that we only report actual underflows. + + dalecurtis@chromium.org + + The amount of time taken to leave the underflow state (i.e. resume playback) + for src= playbacks. + + + + + + Removed Aug 2017. Media.UnderflowDuration2.EME removes zero-weighting so + that we only report actual underflows. + + media-dev@chromium.org + + The amount of time taken to leave the underflow state (i.e. resume playback) + for Encrypted Media Extensions (EME) based playbacks. + + + + + + Removed Aug 2017. Media.UnderflowDuration2.MSE removes zero-weighting so + that we only report actual underflows. + + dalecurtis@chromium.org + + The amount of time taken to leave the underflow state (i.e. resume playback) + for Media Source Extensions (MSE) based playbacks. + + + + + + Replaced with Media.URLScheme2 which is only recorded for src=URL playbacks + instead of including MediaSource playbacks which are always blob. + + media-dev@chromium.org + + URL scheme used with HTML5 media. (each URL provides one sample) + + + + + + Removed as of 08/2020. + + hiroh@chromium.org + chromeos-gfx@chromium.org + + Count of VAAPI errors that occur inside the VaapiWrapper due to VPP + functionality needed by the VaapiImageProcessor. + + + + + + Replaced by Media.VaapiMjpegDecodeAccelerator.VAAPIError as of 08/2020. + + andrescj@chromium.org + chromeos-gfx@chromium.org + + Count of VAAPI errors that occur inside the VaapiWrapper due to decoding + functionality needed by the VaapiMjpegDecodeAccelerator. + + + + + + Replaced by Media.VaapiMjpegDecodeAccelerator.Vpp.VAAPIError as of 08/2020. + + kamesan@chromium.org + chromeos-gfx@chromium.org + + Count of VAAPI errors that occur inside the VaapiWrapper due to VPP + functionality needed by the VaapiMjpegDecodeAccelerator. + + + + + + Replaced by Media.VaapiImageDecodeAcceleratorWorker.VAAPIError as of + 08/2020. + + andrescj@chromium.org + chromeos-gfx@chromium.org + + Count of VAAPI errors that occur inside the VaapiWrapper due to + functionality needed by the VaapiJpegDecodeAcceleratorWorker. + + + + + + Replaced by Media.VaapiJpegEncodeAccelerator.Vpp.VAAPIError as of 08/2020. + + wtlee@chromium.org + chromeos-gfx@chromium.org + + Count of VAAPI errors that occur inside the VaapiWrapper due to VPP + functionality needed by the VaapiJpegEncodeAccelerator. + + + + + + Replaced by Media.VaapiVideoDecodeAccelerator.VAAPIError as of 08/2020. + + mcasas@chromium.org + posciak@chromium.org + chromeos-gfx@chromium.org + + Error codes reported by video decode using VA-API hardware video decoder. + + + + + + Removed as of 4/2015, partially replaced by Media.VAVDA.DecoderFailure. + + posciak@chromium.org + + Error codes reported by video decode using VA-API hardware video decoder. + + + + + + Replaced by Media.VaapiVideoEncodeAccelerator.VAAPIError as of 08/2020. + + posciak@chromium.org + + Error codes reported by video encode using VA-API hardware video encoder. + + + + + + Removed from code as of 07/2019. + + mlamouri@chromium.org + media-dev@chromium.org + + Records time from load starts until video starts based on autoplay + attribute. + + + + + + Removed as autoplay muted video by attributed is paused when going offscreen + since https://crbug.com/683141. + + mlamouri@chromium.org + media-dev@chromium.org + + Records the offscreen playing duration of a muted video autoplaying from + autoplay attribute. + + + + + + Removed as of M80, autoplaying muted videos can no longer be blocked. + + mlamouri@chromium.org + media-dev@chromium.org + + Records the reason why autoplay of muted videos was blocked. + + + + + + Removed from code as of 07/2019. + + mlamouri@chromium.org + media-dev@chromium.org + + Records time from load starts until video starts based on play method. + + + + + + Removed from code as of 02/2020. + + mlamouri@google.com + media-dev@chromium.org + + Whether auto rotation of screen orientation is enabled by the user (if so + the user has not locked the screen orientation at the OS level, though the + orientation may still be locked by apps). Recorded each time + MediaControlsOrientationLockDelegate locks the screen orientation in + response to a video going fullscreen (or loading metadata whilst + fullscreen). + + + + + + Removed from code as of 07/2019. + + mlamouri@chromium.org + + Result of the orientation lock attempt when a video enters fullscreen. + + + + + + Removed from code as of 06/2020. + + mlamouri@chromium.org + + Status of the metadata when attempting to lock the screen orientation for a + fullscreen video. + + + + + + Removed as of 11/2018 -- no longer used and expensive to monitor. + + dalecurtis@chromium.org + media-dev@chromium.org + + Records the time distance between consequent keyframes in a video. The new + value is recorded for each video key frame decoded. + + + + + + Removed as of 01/18/2017 in issue 670150. Replaced by + Media.Video.TimeFromForegroundToFirstFrame.DisableTrack and + Media.Video.TimeFromForegroundToFirstFrame.Paused. + + dalecurtis@chromium.org + media-dev@chromium.org + + Records the time between the moment when the video element is brought to the + foreground and when the video frame compositor outputs the next frame. + + + + + + Removed as of 06/2019 -- no longer used after background track disable has + launched. + + dalecurtis@chromium.org + media-dev@chromium.org + + Records the time between the moment when the video element that had video + track disabled in the background is brought to the foreground and when the + video frame compositor outputs the next frame. Recorded even if disabling + video track in the background is turned off to collect data for the control + group. + + + + + + Removed as of 06/2019 -- no longer used after background track disable has + launched. + + dalecurtis@chromium.org + media-dev@chromium.org + + Records the time between the moment when the video element that was paused + in the background is brought to the foreground and when the video frame + compositor outputs the next frame. Recorded even if disabling pausing video + in the background is turned off to collect data for the control group. + + + + + + Removed as of 10/2014 in issue 422822. Replaced by + Media.VideoCaptureManager.Event and the two new values 3 and 4 in the enum + VideoCaptureEvent. + + grunell@chromium.org + mcasas@chromium.org + + Whether any frames were received during a video capture session. This metric + is recorded when a video source is stopped. + + + + + + Removed 10/2014 in Issue 660493002. + + mcasas@chromium.org + + Pixel format provided by a Video Capture Device. The collection is made in + the VideoCaptureController upon reception of the first frame. + + + + + + Removed July 30th. This is no longer used. + + mcasas@chromium.org + + Video Capture and device enumeration/monitoring API used for Mac OS Lion or + later. Collection is made only once when the flags are parsed and the + appropriate library selected and/or loaded, successfully or not. + + + + + + Removed 07/2017 in favor of the more differentiated durations. + + chfremer@chromium.org + + Measures the duration from the time the Browser connected to the video + capture service to the time it closed the connection. + + + + + + Removed 07/2017 in favor of the more differentiated durations. + + chfremer@chromium.org + + Measures the duration from the time the Browser last closed or lost + connection to the video capture service to the time it reconnects. + + + + + + Removed 03/2020 in https://crbug.com/1053030. We have this in UKM. + + dalecurtis@chromium.org + Video codec profile used in HTML5 media. + + + + + Removed 11/2016 in issue 2506533002. + + scherkus@chromium.org + Coded aspect ratio of HTML5 video. + + + + + Removed 11/2016 in issue 2506533002. + + scherkus@chromium.org + Coded width of HTML5 video. + + + + + Removed 03/2020 in https://crbug.com/1053030. + + dalecurtis@chromium.org + + Pixel format color range of HTML5 video. Emitted on video load. + + + + + + Replaced by Media.VideoFramePixelFormat 05/2015. + + mcasas@chromium.org + Pixel format used in HTML5 video. Emitted on video load. + + + + + Removed 03/2020 in https://crbug.com/1053032. + + hubbe@chromium.org + media-dev@chromium.org + Video frame color space. Emitted for each video frame. + + + + + Replaced by Media.VideoPixelFormatUnion 08/2015. + + mcasas@chromium.org + watk@chromium.org + Pixel format used in HTML5 video. Emitted on video load. + + + + + Replaced by Media.VideoFormat 05/2015. + + scherkus@chromium.org + Pixel format used in HTML5 video. Emitted on video load. + + + + + Pixel format has been removed from demuxers. 06/2019 + + mcasas@chromium.org + emircan@chromium.org + + Pixel format used in capture and HTML5 video. Emitted on video load. + + + + + + Replaced by Media.VideoCapture.FramesReceived 09/2014. + + grunell@chromium.org + mcasas@chromium.org + + If any frames were received during a video capture session. It's recorded + when a video source is stopped. + + + + + + Removed 03/2020 in https://crbug.com/1053030. + + dalecurtis@chromium.org + Visible aspect ratio of HTML5 video. + + + + + Removed 03/2020 in https://crbug.com/1053030. + + dalecurtis@chromium.org + Visible width of HTML5 video. + + + + + Removed 05/2016. + + dcastagna@chromium.org + Number of frame buffers used by Vpx decoder. + + + + + Removed 05/2016. + + dcastagna@chromium.org + + Number of frame buffers currently in use by both Vpx decoder and a + VideoFrame. + + + + + + Removed 11/2018 -- shows nothing interesting; it's been static for years. + + dalecurtis@chromium.org + Amount of time taken to decode one VP9 frame. + + + + + Replaced by Media.AudioRendererImpl.SinkStatus in Nov 2018. + + olka@chromium.org + dalecurtis@chromium.org + + Status of audio sink provided to WebMediaPlayer. If not OK, null sink will + be used for audio output instead. + + + + + + Removed because an overwhelming majority of pages do not set the crossorigin + attribute and as a result most HLS content is counted. Superseded by + Media.WebMediaPlayerImpl.HLS.HasAccessControl. + + sandersd@chromium.org + tguilbert@chromium.org + + When an HLS manifest is found during loading (on Android only), records + whether the request was CORS cross-origin or redirected between origins. + These are cases that may or may not be able to be implemented using fetch(), + depending on details of the redirection and the setting of the crossorigin + attribute. Note: subresources referenced by the manifest are not considered; + they may have different origins or CORS configurations. + + + + + + Removed in March 2020. + + wolenetz@chromium.org + + Amount of memory used by the WebMediaPlayerImpl and its components. + + + + + + Removed 09/2018 since support for these containers has been deprecated. + + dalecurtis@chromium.org + + Media container extensions seen by WebView that are not supported by the + standard HTML5 playback path. This value is recorded every time a + WebMediaPlayer is created with one of the unsupported containers. + + + + + + Removed 01/2017 as Windows Core Audio is now the only audio input + implementation on Windows. + + henrika@chromium.org + + Whether Chrome is using Windows Core Audio for audio input or not. Updated + on Windows only when a low-latency audio input stream is created. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average number of delayed and dropped frames for the YouTube + application. Reported every 5 seconds. + + + + + + Removed 07/2015 in issue 508534. + + halliwell@chromium.org + + The average number of displayed frames for the YouTube application. Reported + every 5 seconds. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Time needed to buffer A/V data after an abort for the YouTube application. + + + + + + Removed in M77. Route controller is specific to the old WebUI Cast dialog, + and the new Views dialog does not have it. + + takumif@chromium.org + openscreen-eng@google.com + + Records whether the Media Route Provider succeeded or failed to create a + controller for a media route. + + + + + + Removed in M77. Sink search is specific to the old WebUI Cast dialog, and + the new Views dialog does not have it. + + takumif@chromium.org + openscreen-eng@google.com + + The outcome of querying Media Route Providers for a sink by ID. + "Success" indicates that a sink was found. This is recorded when + the user attempts to cast to a sink with a manually entered ID. + + + + + + Removed in M77. Route controller is specific to the old WebUI Cast dialog, + and the new Views dialog does not have it. + + takumif@chromium.org + openscreen-eng@google.com + + Duration in milliseconds it takes the WebUI route controls in the route + details view to be populated after the view is opened. + + + + + + Removed in M77. This histogram was for tracking whether the old WebUI Cast + dialog opened in sink list view or route details view. + + takumif@chromium.org + openscreen-eng@google.com + + The view that was shown when the Media Router dialog is initially opened. + + + + + + Removed in M77. One day results for Android were 99.99% success, .01% + Exceeded Cache Size, and an even smaller fraction Exceeded Single Entry + Size. + + jkarlin@chromium.org + The outcome of Entry::WriteData in the memory cache. + + + + + Removed 06/2016 Replaced with Memory.Browser.Large2. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by the browser process. Recorded once per UMA + ping. Note the existence of Memory.Browser.Large, which doesn't have + overflow issues. TODO(rkaplow): This should be replaced with + Memory.Browser.Large2 in M54. + + + + + + Removed 03/2018. No direct replacement. + + bashi@chromium.org + kouhei@chromium.org + + The total committed memory used by the browser process. Recorded once per + UMA ping. + + + + + + Removed 07/2016 as it reports wrong numbers. crbug.com/629354. Replaced with + Memory.Browser.Large2 + + erikchen@chromium.org + + The private working set used by the browser process. Recorded once per UMA + ping. + + + + + + Removed 11/2017 Replaced with Memory.Browser.PrivateMemoryFootprint. + + bashi@chromium.org + kouhei@chromium.org + + The private working set used by the browser process. Recorded once per UMA + ping. + + + + + + Removed 11/2017. No direct replacement, but + Memory.Renderer.PrivateMemoryFootprint is similar. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each chrome:// renderer process. Each + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of active chrome:// renderer processes. Recorded once per UMA + ping. + + + + + + Removed as of Aug 2016. CompressibleString has been reverted once at + https://crrev.com/2227933002. + + hajimehoshi@chromium.org + + This records the frequency with which JavaScript source strings are + compressed and decompressed in foreground and background tabs. Compressing + runs 10 seconds after the tab goes background and decompressing runs when + JavaScript source string is required (e.g. V8 starts to compile). This + measurement is a preparation to introduce CompressibleString class for + JavaScript source strings to reduce Blink memory usage. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + + Available free memory until the system will be in a critical state. Critical + is as defined by the OS (swapping will occur, or physical memory will run + out, etc). + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + Time elapsed between the global state changes. + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + The global state of memory coordinator when a critical pressure notification + is received. + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + The global state of memory coordinator when a moderate pressure notification + is received. + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + The total private working set memory used by the browser and renderer + processes when the memory coordinator changes the global memory state. + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + Android: Records trim memory level when the global state is NORMAL. + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + Android: Records trim memory level when the global state is SUSPENDED. + + + + + + Obsolete as of 2/2017 + + bashi@chromium.org + + Android: Records trim memory level when the global state is THROTTLED. + + + + + + Removed 12/2017. Replaced by Memory.Browser.PrivateMemoryFootprint. + + erikchen@chromium.org + + A rough estimate of the private memory footprint of the browser process. + + + + + + Removed 03/2018. + + bashi@chromium.org + + Amount of reclaimed memory (in terms of the private working set size) after + a purge request on the browser process. Recorded 2 seconds after the purge + request. + + + + + + Removed June 2019. + + bashi@chromium.org + + The number of pages compressed per second. Recorded every 60 seconds. Only + recorded on macOS. + + + + + + Removed June 2019. + + bashi@chromium.org + + The number of pages decompressed per second. Recorded every 60 seconds. Only + recorded on macOS. + + + + + + Removed 12/2017. Replaced by Memory.Extension.PrivateMemoryFootprint. + + erikchen@chromium.org + + A rough estimate of the private memory footprint of an extension process. + + + + + + Removed 12/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint. + + erikchen@chromium.org + + A rough estimate of the private memory footprint of the GPU process. + + + + + + Removed 12/2019. + + sebmarchand@chromium.org + catan-team@chromium.org + + The amount of time spent in the critical memory pressure state. Recorded + every time the level changes and at shutdown. + + + + + + Removed 12/2019. + + sebmarchand@chromium.org + catan-team@chromium.org + + The amount of time spent in the no memory pressure state. Recorded every + time the level changes and at shutdown. + + + + + + Removed 08/2018. Made a decision in issue 871507 that we no longer need this + data. + + ssid@chromium.org + + Records the status of OOM intervention if the feature is turned on, with + various reasons for failure, in the browser process. Recorded once at + browser startup. + + + + + + Removed 02/2020. + + bashi@chromium.org + + Records state of the intervention (accepted or declined) when the foreground + renderer is crashed after near-OOM intervention is triggered. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + + Records the time elapsed between a near-OOM detection and when a navigation + is started. + + + + + + Removed 02/2020. + + bashi@chromium.org + + Records the reason for stopping near-OOM detection. This isn't recorded when + a near-OOM situation was detected. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + + Records the time elapsed between a near-OOM detection and when an OOM + protected renderer was crashed. + + + + + + Replaced by ReducedBlinkUsageAfter10secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of blink usage after 10 seconds of intervention. This reports + negative numbers when reduced. + + + + + + Replaced by ReducedBlinkUsageAfter20secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of blink usage after 20 seconds of intervention. This reports + negative numbers when reduced. + + + + + + Replaced by ReducedBlinkUsageAfter30secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of blink usage after 30 seconds of intervention. This reports + negative numbers when reduced. + + + + + + Replaced by ReducedRendererPMFAfter10secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of renderer pmf after 10 seconds of intervention. This + reports negative numbers when reduced. + + + + + + Replaced by ReducedRendererPMFAfter20secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of renderer pmf after 20 seconds of intervention. This + reports negative numbers when reduced. + + + + + + Replaced by ReducedRendererPMFAfter30secs2 in 03/2019. + + yuzus@chromium.org + + Reduced amount of renderer pmf after 30 seconds of intervention. This + reports negative numbers when reduced. + + + + + + Removed 08/2018. Made a decision in issue 871507 that we no longer need this + data. + + ssid@chromium.org + + Records the status of OOM intervention in renderer process if the feature is + turned on, with various reasons for failure. Recorded at each navigation or + reload. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + + Records the time elapsed between a near-OOM detection and when a foreground + renderer process was gone. This histogram does not contain OOM protected + crashes. + + + + + + Removed 1/2019 because RendererTimeSinceLastNavigationAtDetection replaced + this metric by expanding coverage to include detection-only mode. + + yuzus@chromium.org + + Records the time since last main frame navigation start on the renderer + process when intervention is triggered. Record only when navigation happened + at least once. + + + + + + Replaced by Memory.Experimental.OomIntervention.RendererVmSizeAtOOMLarge. + + ssid@chromium.org + + The renderer process' virtual memory usage, when a foreground OOM occurs. + This was last recorded metric by renderer a few seconds before getting + killed. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + Records user decisions on near-OOM intervention. + + + + + Removed 02/2020. + + pdr@chromium.org + paint-dev@chromium.org + + Recorded after every memory purge signal received by a foreground local + frame root with accelerated compositing enabled. Records whether or not the + signal was the first received by the local frame root. + + This metric has changed over time and it is important to consider these + changes when analyzing historical data. + + + + + + Removed 12/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint. + + erikchen@chromium.org + + A rough estimate of the private memory footprint of a renderer process. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + + Amount of reclaimed memory (in terms of + Memory.Experimental.Renderer.TotalAllocated) after a purge request on a + renderer process. Recorded 2 seconds after the purge request. + + + + + + Removed June 2019. + + bashi@chromium.org + + The number of swap-ins per second. Recorded every 60 seconds. + + + + + + Removed June 2019. + + bashi@chromium.org + + The number of swap-outs per second. Recorded every 60 seconds. + + + + + + Removed 03/2019. Replaced by + Memory.Experimental.WMIRefresher.Init.AddEnumDuration2. + + sebmarchand@chromium.org + + The time it takes for the call to |AddEnum| to complete during the + initialization of the WMI Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The time it takes for the call to |AddEnum| to complete during the + initialization of the WMI Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The time it takes for the call to |CoCreateInstance| to complete during the + initialization of the WMI Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The time it takes for the call to |CreateLocalWmiConnection| to complete + during the initialization of the WMI Refresher. + + + + + + Obsolete as of 09/2019 + + sebmarchand@chromium.org + + The result of configuring the WMIRefresher to read the disk idle time + values. + + + + + + Removed 03/2019. Replaced by + Memory.Experimental.WMIRefresher.InitializeDiskIdleTimeConfigDuration2. + + sebmarchand@chromium.org + + The time it takes to initialize the disk idle config in the WMI Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The time it takes to initialize the disk idle config in the WMI Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The time it takes to do a refresh of the disk idle time value in the WMI + Refresher. + + + + + + Obsolete as of 08/2019 + + sebmarchand@chromium.org + + The result of refreshing the disk idle time value in the WMIRefresher. + + + + + + Removed 11/2017. Replaced by Memory.Extension.PrivateMemoryFootprint. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each extension process. Each process + provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 06/2020. No direct replacement. For similar histograms see + Memory.RenderProcessHost.Count.*, Memory.RendererProcessCount and + Memory.ProcessCount. Old data has been preserved at (Google-internal) + https://docs.google.com/document/d/1QleZ5KhAbFZkv0In61sw7e2rWCaJ05dUCdV9DncJZ2E + + creis@chromium.org + nasko@chromium.org + + The count of active extension processes. Recorded once per UMA ping. + + + + + + Removed 11/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint. + + hajimehoshi@chromium.org + jamescook@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by the GPU process. Recorded once per UMA ping. + + + + + + Obsolete as of 11/2015 + + ssid@chromium.org + Size of messages received by IPC::ChannelReader. + + + + + Removed 7/2019. No longer recorded. + + lizeb@chromium.org + + Recorded each time a Movable String is (un)parked, with the context: + foreground/background. + + + + + + Removed 7/2019. No longer recorded. + + lizeb@chromium.org + + This records the number of movable Javascript source string resources in a + given renderer, at the time page is backgrounded. Recorded alongside + Memory.MovableStringsTotalSizeKb. + + + + + + Removed 7/2019. No longer recorded. + + lizeb@chromium.org + + This records the total size of movable Javascript source string resources in + a given renderer, at the time page is backgrounded. Recorded alongside + Memory.MovableStringsCount. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each Native Client loader process. Each + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each Native Client broker process. Each + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 03/2019. Replaced by + Memory.NativeLibrary.MappedAndResidentMemoryFootprint2 to add more precision + to buckets. + + msalama@google.com + lizeb@chromium.org + + The size of the resident memory for the native library code across all + processes. This metric is computed by parsing proc/self/pagemap and counting + native library pages that are mapped and present in RAM for at least one + Chrome process. Recorded once per UMA ping. Available only on Android. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of other various utility processes (nacl, gpu, sandbox, zygote, + utility). Recorded once per UMA ping. + + + + + + Removed 07/2019. No longer recorded. + + lizeb@chromium.org + + Average compression ratio, 100 * compressed_size / initial_size, for all + compressed ParkableStrings. Recorded at the same time as + "Memory.ParkableString.TotalSizeKb". + + + + + + Removed 07/2019. No longer recorded. + + lizeb@chromium.org + + Total size of ParkableStrings assuming no compression, in KB. Recorded 30s + after compression was triggered, provided that the renderer stayed + backgrounded. + + + + + + Deprecated and removed from the code 06/2020. + + lizeb@chromium.org + pasko@chromium.org + + Total main thread time used by PartitionAlloc's decommit logic over the + first 5 minutes of a renderer lifetime. Starting time is renderer + initialization. + + + + + + Removed 11/2017. No direct replacement. + + thestig@chromium.org + + The private working set used by each Pepper Flash plugin process. Each + plugin process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each Pepper plugin process. Each plugin + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each Pepper plugin broker process. Each + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of Pepper plugin broker processes, recorded once per metrics + services (UMA) update. See MetricsReportingScheduler for details. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of active Pepper plugin processes. Recorded once per UMA ping. + + + + + + Removed due to NPAPI removal. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each plugin process. Each plugin process + provides one sample. Recorded once per process per UMA ping. + + + + + + Removed due to NPAPI removal. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of active plugin processes. Recorded once per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + The current process limit. Recorded once per UMA ping. + + + + + Removed 06/2016 Replaced with Memory.Renderer.Large2. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each renderer process. Each renderer process + provides one sample. Recorded once per UMA ping. TODO(rkaplow): This should + be replaced with Memory.Renderer.Large2 in M54. + + + + + + Removed 03/2018. No direct replacement. + + bashi@chromium.org + kouhei@chromium.org + + The total committed memory used by each renderer process. Each renderer + process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 11/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint. + + bashi@chromium.org + kouhei@chromium.org + + The private working set used by each renderer process. Each renderer process + provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 11/2017. No direct replacement, although + Memory.Total.PrivateMemoryFootprint is similar. + + bashi@chromium.org + hajimehoshi@chromium.org + tasak@chromium.org + + The private working set used by each renderer process, including all + renderer types, i.e. this includes Chrome renderer, extensions renderer, as + well as regular renderer processes. Each renderer process provides one + sample. Recorded once per process per UMA ping. + + + + + + Removed 01/2018. No direct replacement, although + Memory.Total.PrivateMemoryFootprint is similar. + + bashi@chromium.org + hajimehoshi@chromium.org + tasak@chromium.org + + The total committed memory used by each renderer process, including all + renderer types, i.e. this includes Chrome renderer, extensions renderer, as + well as regular renderer processes. Each renderer process provides one + sample. Recorded once per process per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Growth speed of the private working set used by each renderer process per 30 + minutes. The usage and growth speed is recorded at most every 30 minutes, + not every exact 30 minutes. If the interval is longer than 30 minutes, it is + normalized to a speed KB per 30 minutes. Each renderer process provides one + sample. Recorded once per UMA log unless this is the first time the UMA log + is recorded after startup of the renderer, 30 minutes have not passed from + the last recording of the renderer or the usage goes down. If the usage goes + down, the amount of the shrink will be recorded in the + Memory.RendererShrinkIn30Min histogram. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Shrink speed of the private working set used by each renderer process per 30 + minutes. The usage and shrink speed is recorded at most every 30 minutes, + not every exact 30 minutes. If the interval is longer than 30 minutes, it is + normalized to a speed KB per 30 minutes. Each renderer process provides one + sample. Recorded once per UMA log unless this is the first time the UMA log + is recorded after startup of the renderer, 30 minutes have not passed from + the last recording of the renderer or the usage goes up. If the usage goes + up, the amount of the growth will be recorded in the + Memory.RendererGrowthIn30Min histogram. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each sandbox helper process. Each sandbox + helper process provides one sample. Recorded once per process per UMA ping. + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.AvailPageFile2. + + georgesak@chromium.org + + Windows-only metric that represents the maximum amount of memory the current + process can commit. This value is equal to or smaller than the system-wide + available commit value. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the maximum amount of memory the current + process can commit. This value is equal to or smaller than the system-wide + available commit value. + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.AvailPhys2. + + georgesak@chromium.org + + Windows-only metric that represents the amount of physical memory currently + available. This is the amount of physical memory that can be immediately + reused without having to write its contents to disk first. It is the sum of + the size of the standby, free, and zero lists. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the amount of physical memory currently + available. This is the amount of physical memory that can be immediately + reused without having to write its contents to disk first. It is the sum of + the size of the standby, free, and zero lists. + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.AvailVirtual2. + + georgesak@chromium.org + + Windows-only metric that represents the amount of unreserved and uncommitted + memory currently in the user-mode portion of the virtual address space of + the calling process. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the amount of unreserved and uncommitted + memory currently in the user-mode portion of the virtual address space of + the calling process. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the approximate percentage of physical + memory that was in use (0 indicates no memory use and 100 indicates full + memory use). + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.TotalPageFile2. + + georgesak@chromium.org + + Windows-only metric that represents the current committed memory limit for + the system or the current process, whichever is smaller. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the current committed memory limit for + the system or the current process, whichever is smaller. + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.TotalPhys2. + + georgesak@chromium.org + + Windows-only metric that represents the amount of actual physical memory. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the amount of actual physical memory. + + + + + + Removed in 595320 and replaced with Memory.Stats.Win.TotalVirtual2. + + georgesak@chromium.org + + Windows-only metric that represents the size of the user-mode portion of the + virtual address space of the calling process. This value depends on the type + of process, the type of processor, and the configuration of the operating + system. For example, this value is approximately 2 GB for most 32-bit + processes on an x86 processor and approximately 3 GB for 32-bit processes + that are large address aware running on a system with 4-gigabyte tuning + enabled. + + + + + + Removed in 05/2019 + + georgesak@chromium.org + + Windows-only metric that represents the size of the user-mode portion of the + virtual address space of the calling process. This value depends on the type + of process, the type of processor, and the configuration of the operating + system. For example, this value is approximately 2 GB for most 32-bit + processes on an x86 processor and approximately 3 GB for 32-bit processes + that are large address aware running on a system with 4-gigabyte tuning + enabled. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by the browser process. Recorded once per UMA ping if the + system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each chrome:// renderer process. Each process provides one + sample. Recorded once per process per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The amount of memory that swap was compressed into. Recorded once per UMA + ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The ratio of swapped data original size to compressed size. Recorded once + per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each extension process. Each process provides one sample. + Recorded once per process per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by the GPU process. Recorded once per UMA ping if the system + has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Indicates that the system has swapped memory out at least once since boot. + Recorded once per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The amount of memory that is used by swap, including bookkeeping. Recorded + once per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each Native Client loader process. Each process provides + one sample. Recorded once per process per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each Native Client broker process. Each process provides + one sample. Recorded once per process per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The number of reads from swap. Recorded once per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The number of writes to swap. Recorded once per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The amount of memory that was swapped out. Recorded once per UMA ping if the + system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each Pepper plugin process. Each plugin process provides + one sample. Recorded once per process per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each Pepper plugin broker process. Each process provides + one sample. Recorded once per process per UMA ping if the system has + swapped. + + + + + + Removed due to NPAPI removal. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each plugin process. Each plugin process provides one + sample. Recorded once per process per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each renderer process. Each renderer process provides one + sample. Recorded once per process per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each sandbox helper process. Each sandbox helper process + provides one sample. Recorded once per process per UMA ping if the system + has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The sum of all processes' swap. Recorded once per UMA ping if the system has + swapped. See Memory.Swap.Total2 for the same metric with higher precision + bucketing. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + rkaplow@chromium.org + + The sum of all processes' swap. Recorded once per UMA ping if the system has + swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by each utility process. Each utility process provides one + sample. Recorded once per process per UMA ping if the system has swapped. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The swap used by the zygote process. Recorded once per UMA ping if the + system has swapped. + + + + + + Removed 09/2016. Replaced by Memory.Total2. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The sum of all processes. This is not aware of shared memory so it is just a + rough estimate. Recorded once per UMA ping. See Memory.Total2 for the same + metric with higher precision bucketing. + + + + + + Removed 11/2017. Replaced by Memory.Total.PrivateMemoryFootprint. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + rkaplow@chromium.org + + The sum of all processes. This is not aware of shared memory so it is just a + rough estimate. Recorded once per UMA ping. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by each utility process. Each utility process + provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 03/2018. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The count of active worker processes. Recorded once per UMA ping. + + + + + + Removed 11/2017. No direct replacement. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + The private working set used by the zygote process. Each zygote process + provides one sample. Recorded once per process per UMA ping. + + + + + + Removed 04/2018. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Time between two consecutive LowMemory notification in one foreground + session. + + + + + + Removed 04/2018 in favor of Android.MemoryPressureNotification. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Memory notifications delivered through system callbacks to Chrome while in + the background. + + + + + + Removed 04/2018 in favor of Android.MemoryPressureNotification. + + hajimehoshi@chromium.org + kenjibaheux@google.com + kouhei@chromium.org + + Memory notifications delivered through system callbacks to Chrome while in + the foreground - we count LowMemory notification vs particular levels of + TrimMemory foreground notification. + + + + + + Obsolete as of 06/2020. + + bashi@chromium.org + The amount of reclaimed memory after a tab became inactive. + + + + + Removed as of 10/2016. + + + [iOS] When the OS sends a memory warning and the app evicts a tab, this + histogram records the time since the evicted tab was active. + + + + + + Removed as of 10/2016. + + + [iOS] When the OS sends a memory warning and the app protects a tab, this + histogram records the time since the protected tab was active. + + + + + + Removed as of 07/2018. + + gab@chromium.org + + The size of the delayed task queue when the loop becomes idle. Diagnosis + metric for https://crbug.com/850450#c4. + + + + + + Removed as of 07/2018. + + gab@chromium.org + + Reports the delay of a delayed task posted to a MessageLoop. Reported once + per delayed task. Diagnosis metric for https://crbug.com/850450#c4. + + + + + + Removed as of 11/2018. + + gab@chromium.org + + The size of the delayed task queue when the loop becomes idle on a UI + thread. Diagnosis metric for https://crbug.com/850450#c4. Note: this metric + is a bit broken on Mac OSX as CFRunLoop doesn't deterministically invoke + MessageLoop::DoIdleWork(). + + + + + + Removed as of 07/2018. + + gab@chromium.org + + Reports the delay for which the MessageLoop successfully slept until an + upcoming delayed task. Reported each time a MessageLoop successfully sleeps + until the next delayed task. + + + + + + Removed as of 07/2018. + + gab@chromium.org + + Reports the delay for which the MessageLoop had planned to sleep (next + delayed task) before it was woken up early. Reported each time a MessageLoop + is woken up early. + + + + + + Removed as of 01/2020. + + carlosil@chromium.org + estark@chromium.org + + Whether a navigation opted out or not of Mixed Content autoupgrades. + Recorded every navigation. + + + + + + Removed as of 01/2020. + + carlosil@chromium.org + + The status of a mixed content websocket that was autoupgraded to WSS. + + + + + + Removed in 07/2020 because it is no longer needed for analysis. + + peconn@chromium.org + pkotwicz@chromium.org + + Records the cases when the splash screen is hidden when the activity is + finishing. Only "true" is recorded. The purpose is to help + determine cause of http://crbug.com/1096171 + + + + + + Removed in 06/2020 because it is no longer needed for analysis. + + peconn@chromium.org + peter@chromium.org + + Records the cases when removing a Trusted Web Activity's or WebAPK's + translucency via a reflective call fails. Only "true" is recorded. + + + + + + Removed in 04/2020. + + xingliu@chromium.org + + Android: Represents the number of system notifications failed to be created + by the Android API. + + + + + + Removed 02/2020. + + qinmin@chromium.org + + Android: Records the total data downloaded by completion status. + + + + + + Removed 02/2020. + + qinmin@chromium.org + + Android: Records the total data wasted during download due to resumptions. + + + + + + Removed 09/2019, replaced by Download.CancelledDownloadRemovedFromHistory. + + qinmin@chromium.org + dtrainor@chromium.org + + Android: Records the number of cancelled download that are cleaned up from + the history, after loading all the downloads from the history DB on startup. + + + + + + Removed in 07/2019. + + qinmin@chromium.org + Android: Records the reason that a download is canceled. + + + + + Removed in 02/2020. + + qinmin@chromium.org + + Android: Records user interaction on the download resumption button. + + + + + + Removed in 02/2020. + + qinmin@chromium.org + + Android: Records the total time for a download by completion status. + + + + + + Removed in 07/2019. + + qinmin@chromium.org + + Android: Records various counts related to the duplicate download infobar. + + + + + + Removed in 02/2020. + + qinmin@chromium.org + hnakashima@chromium.org + hanxi@chromium.org + qinmin@chromium.org + + Android: Records the number of interruptions for the first download started + in background after it reaches a terminal state. + + + + + + Removed in 02/2020. + + hnakashima@chromium.org + hanxi@chromium.org + qinmin@chromium.org + + Android: Records all the interrupt reasons for the first download started in + background after every browser process launch. We only record the first + download so that we can compare the difference between service manager only + mode and full browser process mode. + + + + + + Removed in 02/2020. + + hnakashima@chromium.org + hanxi@chromium.org + qinmin@chromium.org + + Android: After every browser process launch, records the interrupt reason of + the first background download when it is started. This interrupt reason + allows us to know whether download was interrupted due to browser process + crash in an earlier attempt. + + + + + + Removed 09/2016 in Issue 647755 with all downloads going through Chrome. + + qinmin@chromium.org + + Android: Records the reason that Chrome fails to intercept a download and + pass it to the Android DownloadManager. + + + + + + Removed 09/2019, replaced by + Download.InterruptedDownloadsRemovedFromHistory. + + qinmin@chromium.org + dtrainor@chromium.org + + Android: Records the number of interrupted download that are cleaned up from + the history, after loading all the downloads from the history DB on startup. + + + + + + Removed 02/2020. + + qinmin@chromium.org + + Android: Records the total interruptions for a download by completion + status. + + + + + + Removed 10/2017 in Issue 722320 with the removal of + DownloadNotificationService.hideDanglingSummaryNotification. + + dtrainor@chromium.org + + Android: Records the situation where we try to fix a standalone downloads + summary notification, which shouldn't be visible to the user. True if the + notification was a foreground notification, in which case we can't dismiss + it and need to attempt a more drastic workaround. False if it was a normal + notification and we can dismiss it easily (this is okay and expected + behavior in some scenarios). + + + + + + Removed 04/2020 because the Privacy Notice is removed from FRE. (See + crbug.com/1065912) + + justincohen@chromium.org + + iOS: Records the status of the privacy page after user taps on the privacy + link on the first run welcome view. This metric is only recorded if and + after the TOS are accepted. This metric is specific to iOS. + + + + + + Removed from the code 03/2020 + + tedchoc@chromium.org + + For cold starts of Chrome (native not initialized at the time of intent), + record in ChromeTabbedActivity whether the intent had the effect of opening + a new page or was a restore of last session. + + + + + + Deprecated and removed from the code 02/2020 + + tedchoc@chromium.org + twellington@chromium.org + + Android: Tracks whether a homepage was loaded on startup of + ChromeTabbedActivity. Launching a homepage is conditional on a homepage + being configured on the device and the absence of any existing tabs, so it + will only happen on a subsets of cold starts. The metric splits out whether + the homepage was the NTP or some other URL. + + + + + + Removed and removed from the code 05/2018 + + mariakhomenko@chromium.org + + Android: Records the first action the user does within 10s of starting + Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the + starting intent is of type MAIN. + + + + + + Removed 7/2019. No longer tracked. + + dtrainor@chromium.org + + Android: Number of instances of Chrome currently open during a MultiWindow + session. Emitted every time Chrome is paused. Only emitted on Android + MultiWindow devices. + + A MultiWindow session is any period of time that Chrome was not used in a + full screen mode but together with another Activity that is visible at the + same time. This is only supported in a few Android models. + + + + + + Removed 7/2019. No longer tracked. + + twellington@chromium.org + tedchoc@chromium.org + + Android: percent of the screen available for Chrome during a multi-window + session. Emitted every time chrome is paused. Only emitted on Android + MultiWindow devices. + + A multiwindow session is any period of time that Chrome was not used in full + screen mode but together with some other application that is visible at the + same time. This is only supported in a few Android models. + + + + + + Removed and removed from the code 05/2018 + + mariakhomenko@chromium.org + + Android: Records the first action the user does within 10s of starting + Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the + starting intent is not of type MAIN, e.g. VIEW, etc. + + + + + + Removed and removed from the code 05/2018 + + knn@chromium.org + + Android: The time since last use until Chrome is launched from the home + screen. This is measured from the time the last tab is closed until a Main + intent is received. Has a minute level precision for first 10 minutes + increasing exponentially till 30 days. + + Note: this metric is broken in M63 and below and only reliable in M64+. + + + + + + Removed and renamed to MobileStartup.ToolbarFirstDrawTime2 due to double + reporting bug (see https://crbug.com/857508). + + yusufo@chromium.org + + Android: The time it takes from launch to the completion of first draw for + Toolbar. This excludes activity creation time spent in framework. + + + + + + No longer useful, deprecated in M82. + + yusufo@chromium.org + + Android: The time it takes from launch to the completion of first draw for + Toolbar. This excludes activity creation time spent in framework. + + + + + + No longer useful, deprecated in M82 (see https://crbug.com/1053190). + + mheikal@chromium.org + + Android: The state of chrome startup at the first time the user focuses the + omnibox, if the user does so within the first 30s of the launch (excluding + activity creation time spent in the framework). + + + + + + Removed and renamed to MobileStartup.ToolbarFirstFocusTime2 due to double + reporting bug (see https://crbug.com/857508). + + pasko@chromium.org + + Android: The time it takes from launch to the first time the user focuses + the omnibox if the user does so within first 30s of the launch. This + excludes activity creation time spent in framework. + + + + + + No longer useful, deprecated in M82. + + pasko@chromium.org + + Android: The time it takes from launch to the first time the user focuses + the omnibox if the user does so within first 30s of the launch. This + excludes activity creation time spent in framework. + + + + + + Removed and removed from code as of 05/2015. + + anthonyvd@chromium.org + + Represents the difference in bytes deemed modified by the two + ModuleIntegrityVerifier code paths. The suffix indicates which path had a + higher value. Logged when the ModuleIntegrityVerifier determines that a + module is different on disk and in memory after being triggered by an + incident and the reported byte count for both methods is different. + + + + + + Removed 04/2015; replaced by + ModuleIntegrityVerification.RelocationsUnordered. + + anthonyvd@chromium.org + + Logged when the relocations in a module are not ordered causing the module + verification to abort. The value is the index of the affected module. + + + + + + The MachPortRelay was deleted in July 2019. + + amistry@chromium.org + erikchen@chromium.org + + Errors that the broker process encounters while trying to send or receive + Mach ports from a child process. + + + + + + The MachPortRelay was deleted in July 2019. + + amistry@chromium.org + erikchen@chromium.org + + Errors that a child process encounters while trying to receive Mach ports + from the broker process. + + + + + + Removed 2/2018. Has not actually been collected for some time. + + rockot@chromium.org + + Measures the time it takes for a new child process to receive an + initialization request from the Mojo shell. This is precisely the duration + of the MojoShellConnectionImpl::BindToMessagePipe() call in ChildThreadImpl. + + + + + + Removed 2/2018. Data no longer useful. + + rockot@chromium.org + + Measures the time it takes for a child to receive its parent platform handle + synchronously from the broker on startup. This only applies to the subset of + platforms on which the sync broker is used. + + + + + + Removed as of 6/2017. + + rockot@chromium.org + + Number of internal Mojo system messages processed synchronously during a + single execution of NodeController::AcceptIncomingMessages(). This is called + any time an event requires internal Mojo system messages to be pumped. + Values below 4 are no longer logged. + + + + + + Removed 2/2018. Data no longer useful. + + rockot@chromium.org + + Number of connected peer nodes tracked by a node. This is emitted any time a + peer is added to or dropped from a node. + + + + + + Removed 2/2018. Data no longer useful. + + rockot@chromium.org + + Number of connected pending child node connections tracked by a node. This + is emitted any time a parent-child node connection is initiated or dropped. + + + + + + Removed 2020-04. + + mek@chromium.org + + Errors (base::File::Error) encountered by a single leveldb method in + leveldb's Mojo environment. + + + + + + Removed April, 2020. + + mek@chromium.org + chrome-owp-storage@google.com + + When Mojo LevelDBEnv successfully retries an operation that had failed, + record the error from the most recent failed attempt. + + + + + + Removed in 2020-04. + + mek@chromium.org + + Time Mojo LevelDBEnv slept before successfully completing this operation. 0 + means success on the first try, as LevelDBEnv only sleeps when retries are + needed. + + + + + + Removed as of 6/2013, replaced by Mouse.PointerSensitivity.Changed. + + Please list the metric's owners. Add more owner tags as needed. + Tracks mouse sensitivity setting. + + + + + Removed as of 6/2013, replaced by Mouse.PointerSensitivity.Started. + + Please list the metric's owners. Add more owner tags as needed. + Tracks mouse sensitivity setting on startup. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user mousedown-ed a link and when + the user clicked a link. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + For each click handled by an HTML anchor tag link, whether Blink saw a + mousedown event preceding it. This is only measured for clicks handled by + the anchor tag's default click event handler. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of mousedown events detected at HTML anchor-tag links' default + event handler. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user mouseover-ed a link and when + the user clicked a link. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user mouseover-ed a link and when + the user mouseout-ed a link without click. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of mouseover events detected at HTML anchor-tag links' default + event handler. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The tap gesture events detected before click at HTML anchor-tag links' + default event handler. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time elapsed between when the user tapdown-ed a link and when + the user clicked a link. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of gesturetapdown events detected at HTML anchor-tag links' + default event handler. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of gesturetapunconfirmed events detected at HTML anchor-tag + links' default event handler. + + + + + + Removed 08/2016 due to lack of use (Histogram Eraser). + + lassey@google.com + + The time spent waiting for the renderer to acknowledge an input event. + + + + + + Removed 2/2013, renamed. + + Please list the metric's owners. Add more owner tags as needed. + + The time it takes to spawn the first renderer subprocess (including sandbox + init). + + + + + + Removed 2/2013, renamed. + + Please list the metric's owners. Add more owner tags as needed. + + The time it takes to spawn renderer sub processes not counting the first + one. + + + + + + Removed 12/2017 due to lack of usage. + + amaralp@chromium.org + + The length of time the renderer is unresponsive according to the hang + monitor. Recorded when the renderer regains responsiveness. + + + + + + renamed MPArch.IIR_InputEventDelta. + + Please list the metric's owners. Add more owner tags as needed. + + The time spent waiting for the renderer to acknowledge an input event. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + The time spent inside RenderWidgetHost::OnMsgPaintRect. + + + + + Removed 09/2018 as message no longer exists. + + kylechar@chromium.org + vmiura@chromium.org + + The time delta for processing a paint message. On platforms that don't + support asynchronous painting, this is equivalent to + MPArch.RWH_TotalPaintTime. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + The time spent inside RenderWidgetHost::OnMsgScrollRect. + + + + + Removed 10/2017. Replaced with MPArch.RWH_OnMsgResizeOrRepaintACK. + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time that the user sees a blank white page after switching to a + different tab, while the RenderWidgetHost receives data to paint from the + renderer process. + + + + + + Removed 11/2017. Analysis confirms that the number of discards increases + with the number of logged in users. No action will be taken based on this + information. + + skuhne@chromium.org + + The relation of discarded tabs vs. the amount of simultaneous users. The + counts are the number of discards and the buckets are the number of users. + Since the count values are absolute numbers, they need to be normalized + before use - so divide the counts by the percentage of users per session + found under 'MultiProfile.UsersPerSessionIncremental'. + + + + + + Removed 09/2017 when side-by-side multi-profile mode was removed. There is + now only one multi-profile mode (separate desktop). See the metric + 'MultiProfile.UsersPerSessionIncremental' for overall usage of the + multi-profile feature on Chrome OS. + + skuhne@chromium.org + + The session counter for different multi profile modes which gets stored once + per session at the beginning of the session. + + + + + + Retired in M86. + + skuhne@chromium.org + + Count the number of times each UI path is taken for signing into a new + account in a Chrome OS multiprofile session. UI paths include the system + tray and the user account switcher on the browser frame. + + + + + + Removed 04/2018. Was not being maintained - some cases leading to teleport + were not captured. See counts of 'MultiProfile.TeleportWindowType' to assess + the usage of the teleport window feature. + + skuhne@chromium.org + + Counts the number of window teleportations when using separated desktop + mode. + + + + + + Removed 3/2014, renamed to MultiProfile.UsersPerSessionIncremental. + + skuhne@chromium.org + + The number of users simultaneously signed into a multiprofile session on + Chrome OS. This is recorded upon session end. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + + The time it took to download the manifset file for a Native Client module. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + + The time it took to download the main .nexe for a Native Client module. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + + The size of the main .nexe file downloaded for a Native Client module. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + + The time it took between the Native Client plugin initialization and when + proxied execution of the NaCl module begins. This is the general startup + overhead of running as a NaCl module vs a trusted PPAPI plugin. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + + The time it took between the Native Client plugin initialization and when + proxied execution of the NaCl module begins. This is the general startup + overhead of running as a NaCl module vs a trusted PPAPI plugin. + + + + + + Removed 6/2011, renamed. + + adamk@chromium.org + The OS/Architecture of a nexe that was loaded. + + + + + Removed 5/2011, data is duplicated by NaCl.NexeStartupTime, and normalizing + to 'tab opens' is unusual. + + adamk@chromium.org + + The number of times that Native Client has been started by loading a .nexe + compared to the number of times that a tab has been opened. + + + + + + Removed in M77. This metric is not sufficiently used. + + eugenebut@chromium.org + pkl@chromium.org + + The number of times that Chrome detected that a request to download and + install another Google iOS app completed successfully. + + + + + + Removed 2018-02, replaced by Navigation.IsSameProcess.BackForward. + + clamy@chromium.org + + Whether the back-forward navigation lead to a change of process or not. + + + + + + Removed 2018-02, replaced by + Navigation.ReadyToCommitUntilCommit.BackForward. + + clamy@chromium.org + + The time needed to commit a back forward-navigation once it is ready to + commit. This is the time between ReadyToCommit and DidFinishNavigation (for + a navigation that commits). + + + + + + Removed 2018-02, replaced by Navigation.TimeToReadyToCommit.BackForward. + + clamy@chromium.org + + The time delta between the start of a back-forward navigation and the time + it was ready to commit. + + + + + + Removed 11/2019 in favor of + Previews.DeferAllScript.RedirectLoopDetectedUsingCache. + + dougarnett@chromium.org + + Records when a client redirect cycle that is directly back to the referrer + is detected. + + + + + + Removed 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV2. + + dgrogan@chromium.org + + Why and if cross-origin documents would be loaded in a world where we defer + loading until they are visible. + + + + + + Removed 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV3. + + dgrogan@chromium.org + + Why and if cross-origin documents would be loaded if we were to defer + loading as long as possible. + + + + + + Removed 3/2017 in favor of Navigation.DeferredDocumentLoading.StatesV4. + + dgrogan@chromium.org + + Why and if cross-origin documents would be loaded if we were to defer + loading as long as possible. Difference from V2: frames positioned both + above and to the left of the page have their own bucket and are no longer + counted in the "above" bucket. + + + + + + Removed 11/2018 because LazyLoading has real stats now. + + dgrogan@chromium.org + + Why and if cross-origin documents would be loaded if we were to defer + loading as long as possible. Changes from V3: replace detailed reasons with + summaries for four strategies. E.g. any document that would load under a + strategy of loading when a frame is two screens away is logged to the + WouldLoad2Screens AND WouldLoad3Screens bucket. We only record documents + below the current viewport, not to the right of it. + + + + + + Removed 03/2019 in favor of + Navigation.DownloadPolicy.LogArbitraryPolicyPerDownload and + Navigation.DownloadPolicy.LogPerPolicyApplied. + + csharrison@chromium.org + yaoxia@chromium.org + + When a navigation results in a download, logs the download policy applied to + that navigation. + + + + + + Removed 03/2017 in Issue 703460. + + palmer@chromium.org + + Whether the navigation was to a URL that had embedded credentials. + + + + + + Removed May 2019 + + csharrison@chromium.org + + Records whether the InterceptNavigationThrottle ignored the navigation. This + is recorded at the end of every navigation the throttle observes. + + + + + + Removed May 2019 + + csharrison@chromium.org + + The microseconds it takes for the InterceptNavigationThrottle to determine + if the navigation should be ignored, at WillStartRequest time. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed from code April 2020. + + eugenebut@chromium.org + + Counts slow/fast back/forward WKWebView navigations on iOS. Fast navigation + is a back/forward navigation done with WKBackForwardList. + + + + + + Removed from code March 2018. + + cjhopman@chromium.org + nyquist@chromium.org + + Signifies whether a succesfully finished page load for the main frame + content width fits within the device width and/or has a fixed page scale. + + + + + + Removed 03/2017 in Issue 703460. + + palmer@chromium.org + + Whether the main-frame navigation was to a URL that had embedded + credentials. + + + + + + Removed from code June 2020. Replaced with + Navigation.MainFrameHasRTLDomain2. Navigation.MainFrameHasRTLDomain was + logged differently for iOS and Navigation.MainFrameHasRTLDomain2 does not + have this discrepancy. + + cthomp@chromium.org + security-enamel@chromium.org + + Whether the main-frame navigation was to a URL with an RTL domain name. This + is only recorded for finished navigations and not attempts. + + + + + + Removed from code June 2020. Replaced with + Navigation.MainFrameHasRTLDomainDifferentPage2. + Navigation.MainFrameHasRTLDomainDifferentPage was logged differently for iOS + and Navigation.MainFrameHasRTLDomainDifferentPage2 does not have this + discrepancy. + + cthomp@chromium.org + security-enamel@chromium.org + + Whether the main-frame navigation was to a URL with an RTL domain name, + recorded for each main-frame avigation that replaces a document object. This + is not reported for reference fragment navigations, pushState/replaceState + or same page history navigation. This is only recorded for finished + navigations and not attempts. + + + + + + Removed from code June 2020. Replaced with Navigation.MainFrameProfileType2. + Navigation.MainFrameProfileType was logged differently for iOS and + Navigation.MainFrameProfileType2 does not have this discrepancy. + + rhalavati@chromium.org + chrome-privacy-core@google.com + + The browser profile type for each main-frame navigation, recorded after + navigation completion, including NTP. + + + + + + Removed from code June 2020. Replaced with Navigation.MainFrameScheme2. + Navigation.MainFrameScheme was logged differently for iOS and + Navigation.MainFrameScheme2 does not have this discrepancy. + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation. This is only recorded + for finished navigations and not attempts. + + + + + + Removed from code October 2017. + + meacer@chromium.org + + The mime type of the data: URL for each main-frame navigation. This only + contains mime types that can run scripts. This is only recorded for finished + navigations and not attempts. + + + + + + Removed from code June 2020. Replaced with + Navigation.MainFrameSchemeDifferentPage2. + Navigation.MainFrameSchemeDifferentPage was logged differently for iOS and + Navigation.MainFrameSchemeDifferentPage2 does not have this discrepancy. + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation that replaces a + document object. This is not reported for reference fragment navigations, + pushState/replaceState or same page history navigation. This is only + recorded for finished navigations and not attempts. + + + + + + Removed from code June 2020. Replaced with + Navigation.MainFrameSchemeDifferentPageOTR2. + Navigation.MainFrameSchemeDifferentPageOTR was logged differently for iOS + and Navigation.MainFrameSchemeDifferentPageOTR2 does not have this + discrepancy. + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation that replaces a + document object while in incognito. This is not reported for reference + fragment navigations, pushState/replaceState or same page history + navigation. This is only recorded for finished navigations and not attempts. + + + + + + Removed from code June 2020. Replaced with Navigation.MainFrameSchemeOTR2. + Navigation.MainFrameSchemeOTR was logged differently for iOS and + Navigation.MainFrameSchemeOTR2 does not have this discrepancy. + + elawrence@chromium.org + estark@chromium.org + + The scheme of the URL for each main-frame navigation while in incognito. + This is only recorded for finished navigations and not attempts. + + + + + + Removed 2019-01 (M73), replaced by Navigation.ReadyToCommitUntilCommit2 + (same histogram, different bucketing). + + clamy@chromium.org + nasko@chromium.org + + The time needed to commit a navigation once it is ready to commit. This is + the time between ReadyToCommit and DidFinishNavigation (for a navigation + that commits). + + + + + + Removed January 2019 because it wasn't used. + + donnd@chromium.org + + Total length of the redirect URL strings in navigation entry. Logged when + entry is committed. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + kinuko@chromium.org + + Reported when a user triggers reload without any other navigations after the + previous reload in the same page, and the previous reload variant was + RELOAD_MAIN_RESOURCE. Duration time between two reloads is reported. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + kinuko@chromium.org + + Reported when a user triggers reload without any other navigations after the + previous reload in the same page. Duration time between two reloads is + reported. + + + + + + Removed October 2019 + + arthursonzogni@chromium.org + clamy@chromium.org + nasko@chromium.org + + The time needed in the renderer process between receiving the message to + commit the navigation until the navigation has committed. + + + + + + Obsolete as of 06/2018. + + arthursonzogni@chromium.org + clamy@chromium.org + nasko@chromium.org + + The time delta between when the ResourceHandler is allowed to read the + response's body and when it has completed its first read. + + + + + + Obsolete as of 06/2018. + + arthursonzogni@chromium.org + clamy@chromium.org + nasko@chromium.org + + The time delta between when the ResourceHandler started receiving the + response and when it is allowed to read the response's body. + + + + + + Removed as of 09/2019. + + creis@chromium.org + dtapuska@chromium.org + + Counts session history navigations in sandboxed iframes that disallow top + level navigation, for cases that only stay within the iframe's subtree vs + those that affect other frames instead or as well. + + + + + + Removed August 2018 + + csharrison@chromium.org + + window.location and other scheduled navigation changes can cause the current + provisional load to be aborted. Many times these are initiated without user + gesture. This histogram logs counts of the various aborters. + + + + + + Removed August 2018 + + csharrison@chromium.org + + window.location and other scheduled navigation changes can cause the current + provisional load to be aborted. Many times these are initiated without user + gesture. This histogram logs the time between the aborted navigation start + and the scheduled navigation start, if the aborted navigation has a non-zero + navigationStart value. + + + + + + Removed 4/2017 in Issue 712843. + + palmer@chromium.org + felt@chromium.org + + The scheme of the URL for the first main-frame navigation per origin per + non-OffTheRecord session. + + + + + + Removed 4/2017 in Issue 712843. + + palmer@chromium.org + felt@chromium.org + + The scheme of the URL for the first main-frame navigation per origin per + OffTheRecord session. + + + + + + Data collected and posted on issue 675833. + + csharrison@chromium.org + + The difference between Now() in the renderer and browser_navigation_start + for browser-initiated navigations if the difference is negative. This value + should ideally only reflect the IPC time between the browser process and + renderer process, but in practice could be skewed by inter-process timing + errors. If the clocks used for TimeTicks are monotonic across processes, all + samples should fall into the Positive bucket. + + + + + + Data collected and posted on issue 675833. + + csharrison@chromium.org + + The difference between Now() in the renderer and browser_navigation_start + for browser-initiated navigations if the difference is positive. This value + should ideally only reflect the IPC time between the browser process and + renderer process, but in practice could be skewed by inter-process timing + errors. If the clocks used for TimeTicks are monotonic across processes, all + samples should fall into the Positive bucket. + + + + + + Removed March 2018 in favor of Navigation.StartToCommit variants. + + carlosk@chromium.org + + Time between the start of a browser-started navigation request in and its + commit. + + + + + + Removed 2019-01 (M73), replaced by Navigation.TimeToReadyToCommit2 (same + histogram, different bucketing). + + clamy@chromium.org + nasko@chromium.org + + The time delta between the start of a navigation and the time it is ready to + commit. + + + + + + Removed 06/2018 in favor of PageLoad metrics. + + clamy@chromium.org + + Obsolete. Time between receiving an Android Intent and the navigation + commit. + + + + + + Removed 06/2018 in favor of PageLoad metrics. + + clamy@chromium.org + + Obsolete. Time between clicking on a link and the navigation commit. + + + + + + Removed 06/2018 in favor of PageLoad metrics. + + clamy@chromium.org + + Obsolete. Time between receiving an Android intent and the document load + complete event for a navigation in the main frame. + + + + + + Removed 06/2018 in favor of PageLoad metrics. + + clamy@chromium.org + + Obsolete. Time between clicking on a link and the document load complete + event for a navigation in the main frame. + + + + + + Removed 10/2019 Milestone 80. + + tbansal@chromium.org + + Tracks the accuracy of the action taken by navigation predictor. Recorded at + the time of page click. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on a 2G connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on a 3G connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on a 4G connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on a Bluetooth + connection, before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on an Ethernet + connection, before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen while the + NetworkChangeNotifier thought there was no network connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on an unknown connection + type, before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of the fastest round-trip-time seen on a Wifi connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to a 2G connection and receiving the first network + data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to a 3G connection and receiving the first network + data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to a 4G connection and receiving the first network + data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to a Bluetooth connection and receiving the first + network data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to an Ethernet connection and receiving the first + network data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between disconnecting and receiving the first network data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to an unknown connection type and receiving the first + network data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between switching to a Wifi connection and receiving the first network + data. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via a 2G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via a 3G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via a 4G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via a Bluetooth connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via an Ethernet connection, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while the NetworkChangeNotifier thought there + was no network connection, before the NetworkChangeNotifier detected a + connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via an unknown connection type, + before the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How much data was transfered while connected via a Wifi connection, before + the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on a 2G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on a 3G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on a 4G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on a Bluetooth connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on an Ethernet connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen while the NetworkChangeNotifier + thought there was no network connection, before the NetworkChangeNotifier + detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on an unknown connection type, before + the NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Rough estimate of peak throughput seen on a Wifi connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via a 2G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via a 3G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via a 4G connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via a Bluetooth connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via an Ethernet connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent disconnected, before the NetworkChangeNotifier detected a + connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via an unknown connection type, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + How long was spent connected via a Wifi connection, before the + NetworkChangeNotifier detected a connectivity change. + + This metric is recorded when the NetworkChangeNotifier detects a + connectivity change. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time from ConnectionTypeChanged message until IPAddressChanged message. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + Time between DNS configuration change messages. + + + + + Removed 05/2017 in Issue 677365. + + pauljensen@chromium.org + tbansal@chromium.org + + Records the result of querying the network info of the current active + network. Useful for investigating how frequently the current network was + unblocked, and why it was not unblocked. See http://crbug.com/677365. + + + + + + Code removed long ago. + + pauljensen@chromium.org + + How long does each call to NetworkChangeNotifier::GetConnectionType() take. + + + + + + Removed 5/2017 for Issue 592131. + + pauljensen@chromium.org + + True if the first call to ConnectivityManager.getNetworkInfo(Network) did + not throw NullPointerException, false if it did. Useful for investigating + and avoiding unexpected exceptions, see http://crbug.com/592131. + + + + + + Removed 5/2017 for Issue 592131. + + pauljensen@chromium.org + + Recorded after the first call to ConnectivityManager.getNetworkInfo(Network) + threw a NullPointerException. True if the second call to + ConnectivityManager.getNetworkInfo(Network) did not throw + NullPointerException, false if it did. Useful for investigating and avoiding + unexpected exceptions, see http://crbug.com/592131. + + + + + + Removed 5/2017 for Issue 592131. + + pauljensen@chromium.org + + True if the first call to WifiManager.getConnectionInfo() did not throw + NullPointerException, false if it did. Useful for investigating and avoiding + unexpected exceptions, see http://crbug.com/592131. + + + + + + Removed 5/2017 for Issue 592131. + + pauljensen@chromium.org + + Recorded after the first call to WifiManager.getConnectionInfo() threw a + NullPointerException. True if the second call to + ConnectivityManager.getNetworkInfo(Network) did not throw + NullPointerException, false if it did. Useful for investigating and avoiding + unexpected exceptions, see http://crbug.com/592131. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + Time between IP address change messages. + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time from IPAddressChanged message until ConnectionTypeChanged message. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between going online until we go offline change messages, using new + filtered signal. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between going offline until we go online change messages, using new + filtered signal. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between going online until we go offline change messages. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between when we thought we went offline and when we received some + network data (a URLRequest read completed). + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Count of how many times we received network data (a URLRequest read + completed) while offline when some data was received at most five seconds + before going online. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between when we received the last network data (a URLRequest read + completed) while offline and when we thought we went online. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Count of how many times we polled the online/offline status before detecting + an offline to online transition. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between going offline until we go online change messages. + + + + + + Removed 6/2018. + + pauljensen@chromium.org + + Time between when we thought we went offline and when we received some + network data (a URLRequest read completed), while polling + NetworkChangeNotifier::GetConnectionType() still told us we were offline. + + + + + + Removed 10/2014. + + dschinazi@chromium.org + src/net/OWNERS + + Breakdown of how requests which could potentially make use of an alternate + protocol use or don't use the protocol. Loaded data for 1000 servers and we + have persisted 1000 MRU servers. + + + + + + Removed 10/2014. + + dschinazi@chromium.org + src/net/OWNERS + + Breakdown of how requests which could potentially make use of an alternate + protocol use or don't use the protocol. Loaded data for 200 servers and we + have persisted 1000 MRU servers. + + + + + + Obsoleted in April 2020. + + tbansal@chromium.org + rajendrant@chromium.org + robertogden@chromium.org + + Positive net error codes that failed alternative proxy requests end with. + Recorded when an alternative job fails, whether or not the main job + succeeds. + + As of M66 this superceded DataReductionProxy.Quic.OnAlternativeProxyBroken. + + + + + + Removed 2019/8. + + dschinazi@chromium.org + src/net/OWNERS + + The difference between the size of alternative service mappings in cache and + preferences. This tracks zero or negative values (when the difference + between preferences size is less than or equal to memory cache size). + Positive values are tracked by + Net.AlternativeServiceServers.MorePrefsEntries. + + + + + + Removed 2019/8. + + dschinazi@chromium.org + src/net/OWNERS + + The difference between the size of alternative service mappings in + preferences and cache. This tracks positive values (when the difference + between preferences size is greater than memory cache size). Non positive + values are tracked by Net.AlternativeServiceServers.MoreOrEqualCacheEntries. + + + + + + Removed 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The count of unacknowledged ResourceMsg_DataReceived messages. This message + is sent once per chunk of data read from the network. + + + + + + Removed 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The count of unacknowledged ResourceMsg_DataReceived messages at the point + where we pause network loading. + + + + + + Data collection finished on 2015-03-31. + + dschinazi@chromium.org + src/net/OWNERS + + The time between the call of AsyncResourceHandler::OnRequestRedirected and + the FollowRedirect IPC message from ResourceHost, that is, the length of the + redirect browser-renderer-browser hop. + + + + + + Removed 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + The size of a SharedIOBuffer allocation. + + + + + Removed 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + The number of bytes copied into a SharedIOBuffer. + + + + + Removed 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of a SharedIOBuffer allocation that is actually used. + + + + + + Removed in March 2017. See https://crbug.com/700568. + + ricea@chromium.org + + Counts of error codes received while reading the body of an async + revalidation before getting a response. Only async revalidations that had a + read error are counted. + + + + + + Removed in March 2017. See https://crbug.com/700568. + + ricea@chromium.org + + Counts of error codes received while performing an async revalidation before + getting a response. Only async revalidations that had in a response error + are counted. + + + + + + Removed in March 2017. See https://crbug.com/700568. + + ricea@chromium.org + + The result of an async revalidation resulting from application of the + Cache-Control: stale-while-revalidate directive. All async revalidations are + counted. + + + + + + Removed 01/2011 in https://crrev.com/70740 + + Please list the metric's owners. Add more owner tags as needed. + The time to generate a Basic HTTP authentication token. + + + + + Removed 01/2011 in https://crrev.com/70740 + + Please list the metric's owners. Add more owner tags as needed. + The time to generate a Digest HTTP authentication token. + + + + + Removed 01/2011 in https://crrev.com/70740 + + Please list the metric's owners. Add more owner tags as needed. + + The time to generate a Negotiate (or SPNEGO) HTTP authentication token. + + + + + + Removed 01/2011 in https://crrev.com/70740 + + Please list the metric's owners. Add more owner tags as needed. + The time to generate an NTLM HTTP authentication token. + + + + + Removed and removed 06/2019. + + mmenke@chromium.org + + Number of times auto-reload has been attempted before auto-reload stopped + without succeeding, either because the stop button was pressed or because + the renderer was destroyed. + + + + + + Removed and removed 06/2019. + + mmenke@chromium.org + + Number of times auto-reload had to attempt to reload a page before + succeeding. + + + + + + Removed and removed 06/2019. + + mmenke@chromium.org + + Original error code that started an auto-reload which then succeeded on the + first attempt. + + + + + + Removed and removed 06/2019. + + mmenke@chromium.org + + Error code, if any, when auto-reload stopped without succeeding, either + because the stop button was pressed or because the renderer was destroyed. + + + + + + Removed and removed 06/2019. + + mmenke@chromium.org + + Original error code that started an auto-reload which then eventually + succeeded. + + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + Number of bytes received over this stream. + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + Number of bytes sent over this stream. + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + + How long it takes from starting the request to reading the end of the + response. + + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + + How long it takes from starting the request to reading the start of the + response. + + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + + How long it takes from starting the request to when the last byte is sent. + + + + + + Removed 07/2020. Not used in active investigations. + + mef@chromium.org + pauljensen@chromium.org + + How long it takes from starting the request to when we can start sending + data. + + + + + + Part of a concluded experiment, 2016-08-02. + + ellyjones@chromium.org + Counts of response bytes by cache state. + + + + + Part of a concluded experiment, 2016-08-02. + + ellyjones@chromium.org + + State of the cache for a request, delta-encoding eligible or otherwise. + + + + + + Part of a concluded experiment, 2016-08-02. + + ellyjones@chromium.org + + Counts of response bytes by cache state for delta-encoding eligible + requests. + + + + + + Part of a concluded experiment, 2016-08-02. + + ellyjones@chromium.org + State of the cache for a delta-encoding eligible request. + + + + + Fallback code removed 2018-01-23. + + rsleevi@chromium.org + + Whether the certificate common name was used for matching the hostname, + instead of the subjectAlternativeName. + + Measures results for all CAs (internal and publicly-trusted). + + + + + + Fallback code removed 2018-01-23. + + rsleevi@chromium.org + + Whether the certificate common name was used for matching the hostname, + instead of the subjectAlternativeName. + + Measures results ony for internal (non-publicly-trusted) CAs. + + + + + + Removed 03/2020, since the client cert dialog capping logic has been in + place for a year now without any problems. + + dmcardle@chromium.org + davidben@chromium.org + + As of 03/2019, abusive sites can create a nuisance for Android users by + repeatedly displaying client certificate request dialogs. This histogram + records how many client certificate request dialogs were displayed to the + user. At first, we would like to get a handle on the number of request + dialogs displayed by sites in the wild. Once we have sufficient data, we + will impose some limits to prevent abuse without breaking legitimate sites. + + This metric is emitted whenever a new main frame navigation commits and + whenever a WebContents is destroyed. + + https://crbug.com/817208 + + + + + + Removed 06/2017 as SHA-1 was successfully disabled in 01/2017. + + rsleevi@chromium.org + + Whether or not SHA-1 was present in a resource fetched for the main frame, + and if so, what its maximum validity period was. + + + + + + Removed 06/2017 as SHA-1 was successfully disabled in 01/2017. + + rsleevi@chromium.org + + Whether or not SHA-1 was present in a subresource fetch, and if so, what its + maximum validity period was. + + + + + + Renamed to Net.PublicKeyPinSuccess 28 Oct 2011. + + Please list the metric's owners. Add more owner tags as needed. + + A validated certificate chain may be subject to additional + "pinning" requirements on a per-domain basis. This records the + fraction of successful matches between a certificate chain and a pin list. + + + + + + Removed in Chrome 76. + + estark@chromium.org + rsleevi@chromium.org + + Whether an observed Signed Certificate Timestamp (SCT) can be checked for + inclusion. An SCT can be checked for inclusion if the client has a valid + Signed Tree Head (STH) and the STH currently known to the client was issued + 24 hours after the timestamp in the SCT (24 hours being the typical Maximum + Merge Delay). + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.ConnectionComplianceStatus2 + + estark@chromium.org + + The compliance of each QUIC connection with the Certificate Transparency + policy, recorded once on connection setup unless CT evaluation has been + disabled for that connection or the certificate is invalid. Connections can + be compliant, or they can be non-compliant for one of several reasons (not + enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the + build was old so CT compliance wasn't checked). + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.ConnectionComplianceStatus2 + + estark@chromium.org + + The compliance of each SSL connection with the Certificate Transparency + policy, recorded once on connection setup unless CT evaluation has been + disabled for that connection or the certificate is invalid. Connections can + be compliant, or they can be non-compliant for one of several reasons (not + enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the + build was old so CT compliance wasn't checked). + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2 + + estark@chromium.org + + The compliance of each QUIC connection with the Certificate Transparency + policy, for connections for which CT compliance is required for the + connection to succeed. (For example, CT compliance is required for certain + Certificate Authorities, or a site can opt in to having CT be required.) + Recorded once on connection setup for applicable connections unless CT + evaluation has been disabled for that connection or the certificate is + otherwise invalid. + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2 + + estark@chromium.org + + The compliance of each SSL connection with the Certificate Transparency + policy, for connections for which CT compliance is required for the + connection to succeed. (For example, CT compliance is required for certain + Certificate Authorities, or a site can opt in to having CT be required.) + Recorded once on connection setup for applicable connections unless CT + evaluation has been disabled for that connection or the certificate is + otherwise invalid. Not recorded for certificates that chain to + locally-installed roots. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + Counts of specific error codes returned by LogDnsClient at the end of an + attempt to obtain an inclusion proof for a certificate from a Certificate + Transparency log. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + Counts of specific DNS response codes returned by LogDnsClient at the end of + an attempt to obtain an inclusion proof for a certificate from a Certificate + Transparency log. The response codes (rcodes) and meanings are listed on + https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + The time taken attempting to obtain an inclusion proof from a Certificate + Transparency log over DNS. This includes the time taken to obtain the leaf + index first. Emitted at the end of an attempt. Includes attempts that fail. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + The time taken to successfully obtain an inclusion proof from a Certificate + Transparency log over DNS. This includes the time taken to obtain the leaf + index first. Emitted at the end of an attempt. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + Counts of specific error codes returned by LogDnsClient at the end of an + attempt to obtain a leaf index for a certificate from a Certificate + Transparency log. + + + + + + Removed in Chrome 76. + + robpercival@chromium.org + + Counts of specific DNS response codes returned by LogDnsClient at the end of + an attempt to obtain a leaf index for a certificate from a Certificate + Transparency log. The response codes (rcodes) and meanings are listed on + https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6. + + + + + + Replaced by Net.CertificateTransparency.DnsQueryError, which provides the + full range of net::Error codes rather than summarising them into the limited + set used by this histogram. + + robpercival@chromium.org + + The status of each attempt to obtain an inclusion proof from a Certificate + Transparency log over DNS. This can consist of more than one DNS request. + Emitted at the end of an attempt. + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.EVCompliance2.QUIC + + estark@chromium.org + + The state of compliance with Certificate Transparency presence requirements + for each EV certificate. Recorded once on QUIC connection setup when the + connection uses an EV certificate unless CT evaluation has been disabled for + that connection or the certificate is invalid. + + + + + + Removed Nov 2017, replaced with + Net.CertificateTransparency.EVCompliance2.SSL + + estark@chromium.org + + The state of compliance with Certificate Transparency presence requirements + for each EV certificate. Recorded once on SSL connection setup when the + connection uses an EV certificate unless CT evaluation has been disabled for + that connection or the certificate is invalid. + + + + + + Removed in Chrome 76. + + estark@chromium.org + rsleevi@chromium.org + + The result of an inclusion check for a Certificate Transparency log entry + (composed of a TLS certificate observed together with Signed Certificate + Timestamps). Emitted once per (TLS certificate, Signed Certificate + Timestamp) pair observed and checked for inclusion (check results are + cached). + + + + + + Removed 12/2018. + + eranm@chromium.org + + Number of valid Signed Certificate Timestamps (SCTs) present for the + main-frame resource. Emitted every time a main-frame resource is fetched. + + + + + + Removed in Chrome 76. + + estark@chromium.org + rsleevi@chromium.org + + Age of Pilot's Signed Tree Head, as observed by the client, in minutes. + Measuring the age of a particular log's Signed Tree Head will allow more + informed update frequency of the Component Updater component that provides + them. Emitted once for every STH update received by the component updater. + + + + + + Removed 12/2018. + + eranm@chromium.org + + The number of Signed Certificate Timestamps (SCTs) that were available for + each SSL connection, including SCTs embedded in the certificate. This metric + measures how many SSL connections had SCTs available. Emitted during every + SSL connection establishment. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times we sent N packets, but could have sent N-1 packets. + + + + + + This experiment has concluded. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time taken before we failed to resolve the Comodo test DNS + record. This is an experiment, run in conjuction with Comodo, to test the + viability of a DNS based certificate revocation mechanism. + + + + + + This experiment has concluded. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time taken to successfully resolve the Comodo test DNS record. + This is an experiment, run in conjuction with Comodo, to test the viability + of a DNS based certificate revocation mechanism. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was compressed. + Only includes requests which did not go through an explicit proxy and did + not go over SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The compressed number of bytes received per request that was compressed. + Only includes requests which did not go through an explicit proxy and did + not go over SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was not + compressed but appears to have been compressible. Only includes requests + which did not go through an explicit proxy and did not go over SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was compressed. + Only includes requests sent through a proxy without SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The compressed number of bytes received per request that was compressed. + Only includes requests sent through a proxy without SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was not + compressed but appears to have been compressible. Only includes requests + sent through a proxy without SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was compressed. + Only includes requests sent over SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The compressed number of bytes received per request that was compressed. + Only includes requests sent over SSL. + + + + + + Removed as of 02/2015 + + Please list the metric's owners. Add more owner tags as needed. + + The uncompressed number of bytes received per request that was not + compressed but appears to have been compressible. Only includes requests + sent over SSL. + + + + + + The count was inaccurate (it counted transactions rather than connections) + + Please list the metric's owners. Add more owner tags as needed. + + Each bucket is the number of connections of a particular type that the user + has had during the session. + + + + + + Renamed to match HadConnectionType. + + Please list the metric's owners. Add more owner tags as needed. + + Each bucket is the number of successful connections of a particular type + that the user has had during the session. + + + + + + Removed May 2016. + + davidben@chromium.org + + Each bucket is the number of successful connections of a particular type + that the user has had during the session. + + + + + + No longer collected. + + Please list the metric's owners. Add more owner tags as needed. + + Each bucket is the number of failed connections of a particular type that + the user has had during the session. + + + + + + Replaced with Net.ConnectionUsedSSLDeprecatedCipherFallback2 in Chrome 44. + + davidben@chromium.org + + True if an HTTPS connection was made using the deprecated cipher suite + fallback. + + + + + + Removed May 2017. + + davidben@chromium.org + + For each successful HTTPS request, whether it used the deprecated cipher + suite fallback. + + + + + + Replaced by Net.ConnectionUsedSSLVersionFallback in Chrome 21. + + Please list the metric's owners. Add more owner tags as needed. + + True if the HTTP request was to a server which requires SSLv3 fallback + + + + + + Replaced with Net.ConnectionUsedSSLVersionFallback2 in Chrome 44. + + agl@chromium.org + + Nonzero if the HTTP request was to a server which requires SSL version + fallback. The value indicates the SSL version the request fell back on. + + + + + + Removed June 2016. + + davidben@chromium.org + + For each successful HTTPS request, whether it used the SSL version fallback. + The value indicates the SSL version the request fell back on + + + + + + Obsoleted in favor of Net.ContentDecodingFailed2.FilterType below. + + + For each CONTENT_DECODING_FAILED, record the filter that failed. + + + + + + Obsoleted in favor of Net.ContentDecodingFailed2 above. + + mef@chromium.org + pauljensen@chromium.org + + For each CONTENT_DECODING_FAILED, record the filter that failed. + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + Whether or not updates to the backing store succeeded or failed, recorded + every update. + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + Intervals between access time updates for each cookie. + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + Number of cookies in the store (recorded every 10 minutes of active browsing + time) + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + For each cookie removed from the store, the reason it was removed. + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + For each domain, number of cookies in that domain (recorded every 10 minutes + of active browsing time). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + For every top level domain, number of subdomains in that top level domain + (recorded every 10 minutes of active browsing time). + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + For every top level domain, number of cookies in that domain (recorded every + 10 minutes of active browsing time). + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + For each evicted (not expired) cookie, the amount of time since it was last + used + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + Number of minutes until cookie expires when set. + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time (ms) to get cookies for each URL request. + + + + + + Initial typo; only here to get results from builds before r59117. See + "Cookie." group. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time (ms) to load the persistent cookie store at browser + start. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of active mojom::URLLoader instance counts including + network::URLLoader and network::CorsURLLoader in the network service. This + reports every 5 minutes. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + Each CorsURLLoader reports its completion status on finishing each request + to analyze how often requests are blocked by CORS checks. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the number of cache entries in the CORS preflight cache. + This counts the cache entries every 5 minutes. + + + + + + Removed 05/2019, related to cache organization changes that does not store + entries per origin any more. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the number of cache entries for each origin in the CORS + preflight cache. This counts the cache entries for each origin every 5 + minutes. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the total number of cache entries that is sum of all + CORS preflight cache entries in the network service. This counts the cache + entries every 5 minutes. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of the total memory presure in bytes for all CORS preflight + cache in the network service. This counts the cache entries every 5 minutes. + + + + + + Removed 06/2019. + + toyoshim@chromium.org + yhirano@chromium.org + + The distribution of estimated memory pressure caused by each cache entry's + content in the CORS preflight cache. This counts each entry size when a new + entry is added to the cache. + + + + + + Removed 2019/08. + + dschinazi@chromium.org + src/net/OWNERS + + The total number of servers (HostPortPairs) to which alternative protocol + was used. This counts the number of servers persisted to prefs file. + + + + + + Removed 2019/08. + + dschinazi@chromium.org + src/net/OWNERS + + The total number of servers (HostPortPairs in memory) to which alternative + protocol was used. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The total number of servers (HostPortPairs) that support HTTP pipelining. + This counts the number of servers persisted to prefs file. + + + + + + Removed on 2016-08. + + dschinazi@chromium.org + src/net/OWNERS + + The total number of SPDY server names persisted to prefs file. + + + + + + Removed on 2016-10-11. + + dschinazi@chromium.org + src/net/OWNERS + + The total number of SPDY Settings properties persisted to prefs file. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to block to fetch one or + more revocation lists. This measures the amount of time that failures to get + CRL information take. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to block to fetch one or + more revocation lists. This records the fraction of successful requests. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to block to fetch one or + more revocation lists. This measures the amount of time that each fetch + takes. + + + + + + Removed 2018-06-29 in crrev.com/571588. + + dschinazi@chromium.org + src/net/OWNERS + + Measures time spent to deserialize and populate the + net::CachingCertVerifier's cache. + + + + + + Removed 2018-06-29 in crrev.com/571588. + + dschinazi@chromium.org + src/net/OWNERS + + Measures time spent to serialize the net::CachingCertVerifier's cache. + + + + + + Removed 2019-04-23. + + mgersh@chromium.org + + Measures time spent creating the Cronet PrefService, including loading the + prefs from disk synchronously. + + + + + + Removed; refer to Experimental.Bytes.Network + + tbansal@chromium.org + + The total content size in KB of all HTTP/HTTPS response bodies in the + previous calendar day. The metric is reported when the first response in the + current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all HTTP/HTTPS response bodies in the + previous calendar day while the data reduction proxy setting was enabled. + The metric is reported when the first response in the current day is + received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all HTTPS response bodies in the previous + calendar day while the data reduction proxy setting was enabled. The metric + is reported when the first response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all long-bypassed HTTP response bodies in + the previous calendar day while the data reduction proxy setting was + enabled. The metric is reported when the first response in the current day + is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all short-bypassed HTTP response bodies in + the previous calendar day while the data reduction proxy setting was + enabled. The metric is reported when the first response in the current day + is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + bolian@chromium.org + + The total content size in KB of all HTTP response bodies for requests that + were not served by the enabled data reduction proxy for unknown reasons in + the previous calendar day while the data reduction proxy setting was + enabled. The metric is reported when the first response in the current day + is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all HTTP response bodies for requests that + were not served by the enabled data reduction proxy for unknown reasons in + the previous calendar day while the data reduction proxy setting was + enabled. The metric is reported when the first response in the current day + is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total content size in KB of all HTTP/HTTPS response bodies in the + previous calendar day via the data reduction proxy. The metric is reported + when the first response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total HTTP/HTTPS response body size while the data + reduction proxy is enabled to total HTTP/HTTPS response body size in the + previous calendar day. The metric is reported when the first response in the + current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total HTTPS response body size while the data reduction + proxy is enabled to total HTTP/HTTPS response body size in the previous + calendar day. The metric is reported when the first response in the current + day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total long-bypassed response body size while the data + reduction proxy is enabled to total HTTP/HTTPS response body size in the + previous calendar day. The metric is reported when the first response in the + current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total short-bypassed response body size while the data + reduction proxy is enabled to total HTTP/HTTPS response body size in the + previous calendar day. The metric is reported when the first response in the + current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total body size of responses that were not served by the + data reduction proxy for unknown reason while the data reduction proxy is + enabled to total HTTP/HTTPS response body size in the previous calendar day. + The metric is reported when the first response in the current day is + received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of total HTTP/HTTPS response body size via the data reduction + proxy to total HTTP/HTTPS response body size in the previous calendar day. + The metric is reported when the first response in the current day is + received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of data saving in the previous calendar day. A negative + saving will be shown as zero. The metric is reported when the first response + in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of data saving in the previous calendar day while the data + reduction proxy was enabled. A negative saving will be shown as zero. This + only counts responses while the data reduction proxy is enabled. The metric + is reported when the first response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of data saving in the previous calendar day while the data + reduction proxy was enabled. A negative saving will be shown as zero. This + only counts responses while the data reduction proxy is enabled. The metric + is reported when the first response in the current day is received. If no + video bytes were received while the data reduction proxy was enabled, the + metric will not be reported. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of data saving in the previous calendar day via the data + reduction proxy. A negative saving will be shown as zero. This only counts + responses via the data reduction proxy. The metric is reported when the + first response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The percentage of data saving in the previous calendar day via the data + reduction proxy. A negative saving will be shown as zero. This only counts + responses via the data reduction proxy. The metric is reported when the + first response in the current day is received. If no video bytes were + received via the data reduction proxy, the metric will not be reported. + + + + + + Removed; refer to Experimental.Bytes.Network + + bolian@chromium.org + + Total size in KB of all response bodies in the previous calendar day that + were received through the data reduction proxy. + + + + + + Removed; refer to Experimental.Bytes.Network + + bolian@chromium.org + + Total size in KB of all response bodies in the previous calendar day that + were received when the data reduction proxy was enabled. + + + + + + Removed; refer to Experimental.Bytes.Network + + bolian@chromium.org + + The percentage of data saving in the previous calendar day. A negative + saving will be shown as zero. + + + + + + Removed; refer to Experimental.Bytes.Network + + bolian@chromium.org + + The percentage of data saving in the previous calendar day when the data + reduction proxy was enabled for at least some responses during the day. A + negative saving will be shown as zero. + + + + + + Removed- see Net.DailyOriginalContentLength. + + bolian@chromium.org + + Total size in KB specified in the X-Original-Content-Length headers of all + responses in the previous calendar day. If the header is not present in a + response, the size of the response body is used. + + + + + + Removed- see Net.DailyContentLength. + + bolian@chromium.org + + Total size in KB of all response bodies in the previous calendar day. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total size in KB specified in the X-Original-Content-Length headers of + all HTTP/HTTPS response bodies in the previous calendar day. If the header + is not present in a response, the size of the response body is used. The + metric is reported when the first response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total size in KB specified in the X-Original-Content-Length headers of + all HTTP/HTTPS response bodies in the previous calendar day while the data + reduction proxy is enabled. If the header is not present in a response, the + size of the response body is used. The metric is reported when the first + response in the current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + tbansal@chromium.org + + The total size in KB specified in the X-Original-Content-Length headers of + all HTTP/HTTPS response bodies in the previous calendar day via the data + reduction proxy. If the header is not present in a response, the size of the + response body is used. The metric is reported when the first response in the + current day is received. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + bolian@chromium.org + + The percentage of Net.DailyHttpContentLengthViaDataReductionProxy in + Net.DailyHttpReceivedContentLength. + + + + + + Removed; refer to Experimental.Bytes.Network + + bengr@chromium.org + bolian@chromium.org + + The percentage of Net.DailyHttpContentLengthWithDataReductionProxyEnabled in + Net.DailyHttpReceivedContentLength. + + + + + + Removed in Chrome 57. + + kundaji@chromium.org + bengr@chromium.org + + The percentage of data savings in past + |DataReductionProxy::kNumDaysInHistorySummary| days. This number is + displayed to users as their data savings. + + + + + + Removed in Chrome 57. + + kundaji@chromium.org + bengr@chromium.org + + The total data saved in KB in past + |DataReductionProxy::kNumDaysInHistorySummary| days. This number is used to + compute the data savings displayed to the user. + + + + + + Removed in Chrome 64. + + yhirano@chromium.org + + Duration of time that a request associated with DetachableResourceHandler + takes. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Measures time from initiating a fetch of a PAC file from DHCP WPAD to + cancellation of the fetch. For a given fetch, only one of the cancellation + or completion histograms will be added to. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Measures time from initiating a fetch of a PAC file from DHCP WPAD to + completion of the fetch. For a given fetch, only one of the cancellation or + completion histograms will be added to. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Tracks the net error codes received when the DHCP WPAD fetch fails to + retrieve a PAC file (including PAC_NOT_IN_DHCP, which is not really an error + but an indication that a PAC URL was not configured in DHCP). + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Tracks the frequency of each of the different known error codes of calling + the GetAdaptersAddresses Win32 API. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Measures the time taken to call the GetAdaptersAddresses Win32 API, to + validate our understanding that it should complete quickly enough to call + synchronously from the network thread. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Total number of adapters enabled for DHCP as seen when the wait timer in the + DHCP WPAD code hits. This timer fires after a timeout from when we get some + information from the first adapter to finish. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Number of adapters enabled for DHCP that we have not completed retrieving + information for, as seen when the wait timer in the DHCP WPAD code hits. + This timer fires after a timeout from when we get some information from the + first adapter to finish. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + Counts the number of errors from the DhcpRequestParams API that we do not + have specific handling for, so that we can see if there is an abnormally + high rate. + + + + + + Removed in Chrome 65. + + erikchen@chromium.org + + The sum of the size of all files in the HTTP cache directory. + + This is recorded on startup, and then every 24 hours afterwards. However, it + is only recorded for 0.1% of profiles, to reduce overhead for most users. + This is meant to be a temporary metric to help debug a potential HTTP cache + leak. We do not yet know which milestone we expect it to be removed in. + + + + + + Removed 8/2019. + + pauljensen@chromium.org + + For devices using Android private DNS, are their DNS servers known to + support DNS-over-HTTPS. + + + + + + Removed 8/2019. + + pauljensen@chromium.org + + For devices not using Android private DNS, are their DNS servers known to + support DNS-over-HTTPS, thus potential candidates for automatic upgrading + from regular DNS to DNS-over-HTTPS. + + + + + + Removed 8/2019. + + pauljensen@chromium.org + + For devices using Android private DNS, was their DNS-over-TLS server + specified explicitly in their Android settings. When false, they were + automatically upgraded from the standard DNS protocol to DNS-over-TLS via + auto-detection. + + + + + + Removed 9/2019. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by DnsTask in resolutions that failed. Excludes time + spent in the subsequent fallback. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + Total time elapsed from the beginning of ESNI-type DnsTasks to the + completion of ESNI-type DnsTransactions executed during these tasks. + Recorded only for DnsTasks specifically with DnsQueryType::ESNI, i.e. *not* + for those made during the normal built-in resolver flow. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + For an UNSPECIFIED-type DnsTask, the total end-to-end elapsed time from the + beginning of the task to the completion of its final ESNI-type + DnsTransaction, minus the total end-to-end elapsed time to the completion of + the task's final non-ESNI-type transaction. Recorded only when the built-in + resolver is configured to make ESNI queries alongside A and AAAA queries, + and only when the task's ESNI transaction finishes after its final non-ESNI + transaction. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + Total time elapsed from the beginning of a DnsTask to the completion of an + ESNI transaction. Recorded only when the built-in resolver is configured to + make ESNI queries alongside A and AAAA queries. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + Total time elapsed from the beginning of an UNSPECIFIED-type DnsTask to the + completion of its final non-ESNI-type DnsTransaction. Recorded only when the + built-in resolver is configured to make ESNI queries alongside A and AAAA + queries. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + For an UNSPECIFIED-type DnsTask, the total end-to-end elapsed time from the + beginning of the task to the completion of its final non-ESNI-type + DnsTransaction, minus the total end-to-end elapsed time to the completion of + the task's final ESNI-type transaction. Recorded only when the built-in + resolver is configured to make ESNI queries alongside A and AAAA queries, + and only when the task's final non-ESNI transaction finishes no earlier than + its ESNI transaction. + + + + + + As of 02/2020, no longer necessary because the ESNI record fetching + implementation has been superseded by the new HTTPSSVC DNS record type. + + davidvc@chromium.org + ericorth@chromium.org + + Records successful completions and DnsTask-level timeout cancellations of + ESNI (TLS 1.3 Encrypted Server Name Indication, Draft 4)-type DNS + transactions. Recorded only when the built-in resolver is configured to make + ESNI queries alongside A and AAAA queries. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Time elapsed between the time the HostResolverImpl::Job was created and the + time the Job was started. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Time elapsed between the last time the priority of a HostResolverImpl::Job + changed (when a Request was attached or detached) and the time the Job was + started. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by ProcTask in resolutions that failed. + + + + + + Removed 11/2018. + + pauljensen@chromium.org + mef@chromium.org + + Duration of time taken by ProcTask in resolutions that succeeded. + + + + + + Removed 8/2019. + + dmcardle@chromium.org + davidben@chromium.org + + Length of domain name parsed by DnsRecordParser::ReadName(). + + + + + + Removed July 2018. + + mgersh@chromium.org + + When DnsUDPAttempt gets a malformed response, it returns an error but + continues running. This histogram records all attempt outcomes that are + returned to the transaction once a malformed response has been received, + including the original malformed response. + + + + + + Replaced 2020-06 by Net.DNS.SecureDnsMode.Automatic.ResolveTime + + dalyk@google.com + doh-core@google.com + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted for requests issued in AUTOMATIC mode. Excludes cancled, + evicted, and aborted requests. Includes cache hits (recorded as 0). Excludes + speculative requests. + + + + + + Replaced 2020-06 by Net.DNS.SecureDnsMode.Off.ResolveTime + + dalyk@google.com + doh-core@google.com + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted for requests issued in OFF mode. Excludes cancled, evicted, + and aborted requests. Includes cache hits (recorded as 0). Excludes + speculative requests. + + + + + + Replaced 2020-06 by Net.DNS.SecureDnsMode.Secure.ResolveTime + + dalyk@google.com + doh-core@google.com + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted for requests issued in SECURE mode. Excludes cancled, + evicted, and aborted requests. Includes cache hits (recorded as 0). Excludes + speculative requests. + + + + + + Replaced 2020-06 by Net.DNS.Request.TotalTime + + pauljensen@chromium.org + mef@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Excludes speculative requests. + + + + + + Replaced 2020-06 by Net.DNS.Request.TotalTimeAsync + + pauljensen@chromium.org + mef@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests and + requests that returned synchronously (such as cache hits). Excludes + speculative requests. + + + + + + Removed 9/2019. + + + + pauljensen@chromium.org + + Duration of time since a HostResolverImpl::Resolve request to the time a + result is posted. Excludes canceled, evicted, and aborted requests. Includes + cache hits (recorded as 0). Excludes speculative requests. + + + + + + Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 + + Please list the metric's owners. Add more owner tags as needed. + + + + + Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 + + Please list the metric's owners. Add more owner tags as needed. + + + + + Removed- see Net.DNS_Resolution_And_TCP_Connection_Latency2 + + Please list the metric's owners. Add more owner tags as needed. + + + + + Removed 07/2017, not necessary to determine deprecation for invalid DNS + names. + + palmer@chromium.org + + True if |net::IsCanonicalizedHostCompliant| returns true. Used to see if + IsCanonicalizedHostCompliant() runs afoul of real websites. This histogram + is recorded when converting dotted DNS names into DNS query form, in + preparation for issuing a DNS request. This histogram is only recorded if + Net.ValidDNSName is true. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The number of HTTP request responses with MS Office Docs MIME types. The + responses are classified based on their method type and cacheability (POST, + cacheable GET and non-cacheable GET). The histogram is used in Double GET + Experiment, where successful non-cacheable GET requests are intercepted + after initial response and repeated in order to determine how much reissuing + non-cacheable GET requests influences their error rate. The histogram tracks + only initial requests (not the repeated ones). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The response codes encountered for GET request repeated in Double GET + Experiment. In the experiment successful non-cacheable GET requests are + intercepted after initial response and repeated. The goal of the experiment + is to measure how much reissuing non-cacheable GET requests influences their + error rate. + + + + + + Removed as of 03/2015. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + Kbps on download streams exceeding 25KB. Measures from the beginning of the + first byte received until the end of flowing data. + + + + + + Removed in favor of Net.ErrAborted.CountPerUpload2 which has a higher upper + bound + + csharrison@chromium.org + + The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time + histograms are being uploaded. + + + + + + Removed from Chromium as of 2018/7/2. + + csharrison@chromium.org + + The TotalReceivedBytes() at the time the request finishes with ERR_ABORTED. + + + + + + Removed from Chromium as of 2018/7/2. + + csharrison@chromium.org + + The TotalSentBytes() at the time the request finishes with ERR_ABORTED. + + + + + + Removed as of 2012/5/16, replaced by Net.ErrorCodesForHTTPSGoogleMainFrame2, + which measures the same data but includes ERR_ABORT and OK. + + Please list the metric's owners. Add more owner tags as needed. + + Errors resulting from loading pages from https://www.google.com. Note that + this only counts the errors in "main frames", so it is a measure + of the error pages that users actually see (it does not for example count + the error codes for subresoures on a page). This is a temporary histogram, + added in order to debug query loss from the SSL Search launch. + + + + + + Removed as of 7/2018, replaced by Net.ErrorCodesForHTTPSGoogleMainFrame3. + + mmenke@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" for + https://www.google.com. Subresources or main frame navigations to other + origins are not included. + + + + + + Removed as of 7/2018, replaced by Net.ErrorCodesForImages2, which is + recorded in a net-service friendly way. + + skonig@chromium.org + hbengali@chromium.org + + Net error codes that requests for images end with, including net::OK and + net:ERR_ABORTED. + + + + + + Removed as of 2011/5/24, replaced by Net.ErrorCodesForMainFrame2, which + measures the same data but uses a different bucket structure (adds guard + buckets). + + Please list the metric's owners. Add more owner tags as needed. + + Positive net error code that a page failed with. Note that this only counts + the errors in "main frames", so it is a measure of the error pages + that users actually see (it does not for example count the error codes for + subresoures on a page). + + + + + + Removed as of 2012/5/16, replaced by Net.ErrorCodesForMainFrame3, which + measures the same data but includes ERR_ABORTED and OK. + + Please list the metric's owners. Add more owner tags as needed. + + Positive net error code that a page failed with. Note that this only counts + the errors in "main frames", so it is a measure of the error pages + that users actually see (it does not for example count the error codes for + subresoures on a page). + + + + + + Removed as of 7/2018, replaced by Net.ErrorCodesForMainFrame4, which is + recorded in a net-service friendly way. + + mmenke@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" (it + does not for example count the error codes for subresoures on a page). + + + + + + Removed as of 2012/5/16, replaced by Net.ErrorCodesForSubresources2, which + measures the same data but includes ERR_ABORT and OK. + + Please list the metric's owners. Add more owner tags as needed. + + Positive net error code that a page failed with. Note that this only counts + the errors in "subresources". + + + + + + Removed as of 7/2018, replaced by Net.ErrorCodesForSubresources3, which is + recorded in a net-service friendly way. + + mmenke@chromium.org + + Net error codes that requests for "subresources" end with, + including net::OK and net::ERR_ABORTED. + + + + + + Removed as of 7/2018, replaced by + Net.ErrorCodesForTLS13ExperimentMainFrame2, which is recorded in a + net-service friendly way. + + svaldez@chromium.org + + Positive net error codes that requests for pages end with, including net::OK + and net::ERR_ABORTED. This only counts loads in "main frames" for + endpoints used in the initial TLS 1.3 deployment. Subresources or main frame + navigations to other origins are not included. + + + + + + Removed as of 2015/8/21 + + mmenke@chromium.org + + Temporary histogram to investigate http://crbug.com/500556. Records which + button on the network error page was pushed when either the URL Blink + reports for the page is not the internal error page URL or the + NetErrorHelper core has no error information for the current page (or both). + + + + + + Removed as of 2015/8/21 + + mmenke@chromium.org + + Temporary histogram to investigate http://crbug.com/500556. Records whether, + when the handler for a button press on the network error page runs, which of + the following are or are not true: The URL Blink reports for the page is not + the internal error page URL or the NetErrorHelper core has no error + information for the current page. + + + + + + Removed as of 2020/07 + + edwardjung@chromium.org + security-enamel@chromium.org + + Counts of the type of navigation correction suggestions shown on the network + error page. Multiple suggestions can be shown at the same time. + + + + + + Removed as of 2020/07 + + edwardjung@chromium.org + security-enamel@chromium.org + + Usage of navigation correction suggestions shown on the network error page. + + + + + + Removed 10/2016. + + mmenke@chromium.org + + The number of main frame 4xx/5xx responses that have content, to determine + if it's worth hooking up an error page for those that don't. Intended to be + removed from the binary soon. + + + + + + Removed 10/2016. + + mmenke@chromium.org + + The number of non-main frame 4xx/5xx responses that have content, to + determine if it's worth hooking up an error page for those that don't. + Intended to be removed from the binary soon. + + + + + + Removed 04/2017. + + estark@chromium.org + + Sites can send an Expect-CT header to Chrome to indicate that they want a + report to be sent when the connection does not comply with Certificate + Transparency policy. This histogram is recorded whenever Chrome receives an + Expect-CT header, and it records the result of processing the header, such + as whether it was ignored due to a bad value. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file Flush failed with. The code is OS dependent, + so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file GetSize failed with. The code is OS dependent, + so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file Open failed with. The code is OS dependent, so + when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file Read failed with. The code is OS dependent, so + when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file Seek failed with. The code is OS dependent, so + when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file SetEof failed with. The code is OS dependent, + so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code that a file Write failed with. The code is OS dependent, + so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file Flush failed with. Any value other than + 0 indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_Flush. The code is OS + dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file GetSize failed with. Any value other + than 0 indicates that we have received errors in a range outside of the one + in which we recorded the specific errors in Net.FileError_GetSize. The code + is OS dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file Open failed with. Any value other than 0 + indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_Open. The code is OS + dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file Read failed with. Any value other than 0 + indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_Read. The code is OS + dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file Seek failed with. Any value other than 0 + indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_Seek. The code is OS + dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file SetEof failed with. Any value other than + 0 indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_SetEof. The code is + OS dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + System error code range that a file Write failed with. Any value other than + 0 indicates that we have received errors in a range outside of the one in + which we recorded the specific errors in Net.FileError_Write. The code is OS + dependent, so when looking at the histogram don't mix OSes. + + + + + + Removed 2020-04 (M84). + + cmumford@chromium.org + + A compressed SVG file was loaded from the file scheme. This is a temporary + counter to determine how often (if at all) this feature is used. Recorded + during creation of file-request for .svgz resource. See + http://crbug.com/857117 for more information. + + + + + + Data collection ended, corresponding feature removed. + + dschinazi@chromium.org + src/net/OWNERS + + Track usage of alternative services forced by the force-alt-protocols + command line flag. Triggered each time alternative services are queried for + a given origin and the command line flag would make a difference (that is, + there is no advertised alternative service for that origin). + + + + + + Underlying implementation changed to no longer depend on OS. Removed in + Chrome 77. + + davidben@chromium.org + rsleevi@chromium.org + + Whether or not system installed trust anchors could be distinguished from + user installed trust anchors. Recorded on first certificate verification on + Android 4.2 and later. + + + + + + Removed in Chrome 76. + + phajdan.jr@chromium.org + The number of times each FTP Error was observed. + + + + + Removed in Chrome 76. + + phajdan.jr@chromium.org + + The number of Chrome sessions which encountered the indicates FTP Error. + This prevents allowing a user that retried a connection many times (getting + an error each time) from biasing the tallies. + + + + + + Replaced by Net.FtpServerTypeCount2 on 2012-11-03. + + phajdan.jr@chromium.org + + Each bucket is the number of times the FTP server type was encountered. + + + + + + Removed in Chrome 76. + + phajdan.jr@chromium.org + + Each bucket is the number of times the FTP server type was encountered. + + + + + + Removed at some time before 2014/09/15. + + Please list the metric's owners. Add more owner tags as needed. + + The time spent waiting for WinHttpGetProxyForUrl to return with error. + + + + + + Removed at some time before 2014/09/15. + + Please list the metric's owners. Add more owner tags as needed. + + The time spent waiting for WinHttpGetProxyForUrl to return with success. + + + + + + Removed June 2016. + + davidben@chromium.org + + Records a sample for each HTTPS request to a Google server that either + succeeded or received an inappropriate_fallback alert. This is used to + estimate how frequently the fallback is used to recover from a spurious + network failure. + + + + + + Replaced with Net.GoogleConnectionUsedSSLVersionFallback2 in Chrome 44. + + agl@chromium.org + + Nonzero if the HTTP request was to a Google server which required SSL + version fallback. The value indicates the SSL version the request fell back + on. Since Google servers support TLS 1.2, any fallback is an indication of + network middleware problems. + + + + + + Removed June 2016. + + davidben@chromium.org + + For each successful HTTPS request to a Google server, whether it used the + SSL version fallback. The value indicates the SSL version the request fell + back on. Since Google servers support TLS 1.2 and FALLBACK_SCSV, any + fallback is an indication of a broken local SSL MITM proxy. + + + + + + Removed around 2015/03/18. The code which implemented Gzip encoding fixup + was removed. + + asanka@chromium.org + + Resources are sometimes transferred with an incorrect encoding type of gzip. + net::Filter::FixupEncodingTypes() attempts to correct for these situations + by applying a set of heuristics. This histogram counts the frequency of + usage of these heuristics in the wild. + + + + + + The count was inaccurate (it counted transactions rather than connections). + + Please list the metric's owners. Add more owner tags as needed. + + Each bucket is a boolean (0 or 1) indicating whether the user has had a + connection of that type during the session. + + + + + + This statistic measures successful and failed connections, the new one only + measures successful ones. + + Please list the metric's owners. Add more owner tags as needed. + + Each bucket is a boolean (0 or 1) indicating whether the user has had a + connection of that type during the session. + + + + + + Removed May 2016. + + davidben@chromium.org + + Each bucket is a boolean (0 or 1) indicating whether the user has had a + successful connection of that type during the session. + + + + + + Replaced by Net.HadFtpServerType2 on 2012-11-13. + + phajdan.jr@chromium.org + + Each bucket is the number of sessions that encountered a given FTP server + type. Each session reports a given server type at most once. + + + + + + Removed in Chrome 76. + + phajdan.jr@chromium.org + + Each bucket is the number of sessions that encountered a given FTP server + type. Each session reports a given server type at most once. + + + + + + Removed 2020-05. + + davidben@chromium.org + src/net/OWNERS + + Recorded for each host where we query the HSTS state, details on whether the + implementation matched the specification. See https://crbug.com/821811. + + + + + + Removed in 2017 March. + + dschinazi@chromium.org + src/net/OWNERS + Format of :status header value in HTTP/2 response. + + + + + Removed 2017-02. + + davidben@chromium.org + + The SSL/TLS cipher suite that was negotiated, recorded for each successful + HTTP/2 connection. + + + + + + Removed in Chrome 77. + + asanka@chromium.org + + Whether adding an entry to the HTTP auth cache evicted another entry. + + + + + + Removed in Chrome 77. + + asanka@chromium.org + + When an HTTP auth cache entry is evicted, the time since it was created. + + + + + + Removed in Chrome 77. + + asanka@chromium.org + + When an HTTP auth cache entry is evicted, the time since it was last used. + + + + + + Removed in Chrome 77. + + asanka@chromium.org + + Whether adding a path to an entry in the HTTP auth cache evicted another + path. + + + + + + Removed 10/2018 when changing the cache implementation such that the number + of entries examined no longer applies. + + chlily@chromium.org + + The number of entries examined (equal to the cache size) when attempting to + look up an HTTP auth cache entry (either by path or realm) and finding no + matching entries. This is recorded whenever the lookup fails (i.e., value 0 + in Net.HttpAuthCacheLookupPosition and + Net.HttpAuthCacheLookupByPathPosition). + + + + + + Removed 10/2018 when changing the cache implementation such that the lookup + position no longer applies. + + asanka@chromium.org + + When looking up an HTTP auth cache entry by path, the position (1-indexed) + of the entry on a hit, or 0 on a miss. + + + + + + Removed 10/2018 when changing the cache implementation such that the lookup + position no longer applies. + + asanka@chromium.org + + When looking up an HTTP auth cache entry by realm, the position (1-indexed) + of the entry on a hit, or 0 on a miss. + + + + + + Removed in https://crrev.com/209100 + + Please list the metric's owners. Add more owner tags as needed. + + Count of authentication requests for top level pages vs. sub-resources, such + as images or iframes. + + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Time between the HttpNetworkTransaction requesting a connection and the time + it connected. + + + + + + Replaced by Net.HttpContentLengthV2 + + bengr@chromium.org + + Size of the response body. This is the actual number of bytes received, + which usually agrees with but is not necessarily the same as the size + specified by the Content-Length header. + + + + + + Removed 04/2018. + + bengr@chromium.org + + Size of the response body if it is cacheable. This is the actual number of + bytes received, which usually agrees with but is not necessarily the same as + the size specified by the Content-Length header. + + + + + + Removed 04/2018. + + bengr@chromium.org + + Size of the response body if it is cacheable for at least 24 hours. This is + the actual number of bytes received, which usually agrees with but is not + necessarily the same as the size specified by the Content-Length header. + + + + + + Removed 04/2018. + + bengr@chromium.org + + Size of the response body if it is cacheable for at least 4 hours. This is + the actual number of bytes received, which usually agrees with but is not + necessarily the same as the size specified by the Content-Length header. + + + + + + Removed 06/2018. + + bengr@chromium.org + + The difference between the size specified in the X-Original-Content-Length + header and the size of the response body. This is zero if the + X-Original-Content-Length header is not present in the response. + + + + + + Removed 04/2018. + + bengr@chromium.org + + Size of the response body. Only includes resources that have the + X-Original-Content-Length header. + + + + + + Removed as of 12/2016. + + mmenke@chromium.org + + Records the frequency with which a number of hacky HTTP header parsing rules + are invoked. This histogram should be removed after we have enough data to + know if we can remove the hacks. + + + + + + Replaced by Net.HttpOriginalContentLengthV2. + + bengr@chromium.org + + Size specified in the X-Original-Content-Length header. If this header is + not present in the response, the size of the response body is used. + + + + + + Removed as of 10/2016. + + mmenke@chromium.org + Time it takes to request a new (unused) HTTP proxy socket. + + + + + Removed 06/2016 because this is not continuously tracked. + + hiroshige@chromium.org + + Whether a request contains invalid request header values in RFC 7230. This + is counted once for every redirect leg. https://crbug.com/455099. + + + + + + Removed in M79. + + sclittle@chromium.org + bengr@chromium.org + + The network error code that the HTTP request completes with, including OK + and ABORTED. + + + + + + Removed in M79. + + sclittle@chromium.org + bengr@chromium.org + + The network error code that the HTTP main frame resource request completes + with, including OK and ABORTED. + + + + + + Removed 06/2016 because this is not continuously tracked. + + hiroshige@chromium.org + + Whether a response contains invalid response header values in RFC 7230. This + is counted once for every redirect leg. https://crbug.com/455099. + + + + + + Removed as of 06/2019. Net.HttpResponseCode has similar information, but for + all resources, not just the main frame, and includes the full response code. + + mmenke@chromium.org + + The count of HTTP Response codes encountered, in response to MAIN_FRAME + requests only; saving only the hundreds digit, e.g. 100->1, 300->3. + + + + + + Removed as of 06/2016. + + dschinazi@chromium.org + src/net/OWNERS + + Application protocol used in HTTP response. Recorded every time a URLRequest + completes. + + + + + + Removed as of July 2018. + + mmenke@chromium.org + + Application protocol used in HTTP responses to requests for main frames. + Only includes requests that went over the network. + + + + + + Removed as of July 2018. + + mmenke@chromium.org + + Application protocol used in HTTP responses to requests for resources other + than main frames. Does not include internal Chrome requests. Only includes + requests that went over the network. + + + + + + Removed as of July 2019. + + dschinazi@chromium.org + src/net/OWNERS + + The location in http_server_properties_manager.cc where UpdatePrefs was + called. + + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The counts of the type of sockets (all HTTP sockets, regardless of any proxy + used) used for HTTP[s]. + + + + + + Removed as of 12/2016. + + ellyjones@chromium.org + + Records how often violations of RFC 7230's header parsing rules are + observed. + + + + + + Removed as of 1/2018. + + mef@chromium.org + pauljensen@chromium.org + Reports the next state that the Alternative Job is in. + + + + + Removed as of 1/2018. + + mef@chromium.org + pauljensen@chromium.org + Reports the state that the Alternative Job is in. + + + + + Removed as of 1/2018. + + mef@chromium.org + pauljensen@chromium.org + Reports the next state that the Main Job is in. + + + + + Removed as of 1/2018. + + mef@chromium.org + pauljensen@chromium.org + Reports the state that the Main Job is in. + + + + + Removed 08/2017. No longer tracked. + + zhongyi@chromium.org + Time it takes for OnStreamReadyCallback to be called. + + + + + Removed 06/2019. + + mmenke@chromium.org + + Time from when an HTTP request is issued to when the first byte is + processed, for requests with an upload that is > 1 MiB. Excludes chunked + uploads. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The count of handleable socket errors (connection abort/close/reset) per + socket reuse type. + + + + + + Late bindings are on by default now. + + Please list the metric's owners. Add more owner tags as needed. + + The count of handleable socket errors (connection abort/close/reset) per + socket reuse type. Socket late binding is disabled. + + + + + + Late bindings are on by default now. + + Please list the metric's owners. Add more owner tags as needed. + + The count of handleable socket errors (connection abort/close/reset) per + socket reuse type. Socket late binding is enabled. + + + + + + Removed 11/2014. No longer tracked. + + bengr@chromium.org + + Time from when the IOThread is created to when the first URL request is + started. Only requests that are created for a profile while Chrome is + starting up are considered. + + + + + + Removed 1/2015. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + Duration of time spent during the UDP-connect IPv6 probe. + + + + + Removed 03/2015. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Whether the interface-enumeration IPv6 probe method failed given that the + UDP-connect IPV6 probe failed. + + + + + + Removed 03/2015. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Whether the interface-enumeration IPv6 probe method was successful given + that the UDP-connect IPV6 probe was successful. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + The probe results when a test for IPv6 support is done. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The probe results when a test for IPv6 support is done, after a network + change event. + + + + + + Removed 01/2018. + + zhongyi@chromium.org + + This counts number of all the job controllers that are still alive if the + count is a multiple of 100: 100, 200, 300, etc. + + + + + + Removed 01/2018. + + zhongyi@chromium.org + + This counts number of JobControllers that are still alive, not created for + preconnect, and still have a HttpStreamFactoryImpl::Request pending. + + + + + + Removed 01/2018. + + zhongyi@chromium.org + + This counts number of job controllers that are still alive, not created for + preconnect but HttpStreamFactoryImpl::Request has completed. + + + + + + Removed 01/2018. + + zhongyi@chromium.org + + This counts number of job controllers which are used for preconnect and are + still alive. + + + + + + Removed 01/2018. + + zhongyi@chromium.org + + This counts number of all the job controllers that are still alive. + + + + + + Removed 08/2017. + + zhongyi@chromium.org + + This counts number of alternative jobs which are still alive. + + + + + + Removed 08/2017. + + zhongyi@chromium.org + This counts number of main jobs which are still alive. + + + + + Removed 04/2017, replaced by + Net.JobController.CountOfJobController.NonPreconnect.PendingRequest. + + zhongyi@chromium.org + + This counts number of HttpStreamFactoryImpl::Request which are still alive. + + + + + + Removed 04/2017, replaced by + Net.JobController.CountOfJobController.Preconnect. + + zhongyi@chromium.org + + This counts number of job controllers which are used for preconnect and are + still alive. + + + + + + Removed 02/2018, replaced by + Net.KeepaliveStatisticsRecorder.PeakInflightRequests2 + + yhirano@chromium.org + + The peak number of concurrent outstanding requests with keepalive specified. + + + + + + Removed July 2018 + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + The completion status of prefetches that have finished loading. + +
+ Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled + before that point are not registered. + + This applies to requests with net::LOAD_PREFETCH, used by various + prefetching features such as no-state prefetch and RESOURCE_TYPE_PREFETCH. + + Note that "success from cache" means that the + UrlRequest::was_cached() was true and unused_since_prefetch was false. + "success from network" means that was_cached() was false. + "success already prefetched" means that both was_cached() and + unused_since_prefetch were true. Validated results are considered cached, + even though a conditional network request is made. +
+ + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The time that a (non-cancelled) proxy resolution request was stalled waiting + for an execution thread, for MultiThreadedProxyResolver. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that it took for a (non-cancelled) proxy resolution request + to complete, for MultiThreadedProxyResolver. + + + + + + Removed in Chrome 44. + + eroman@chromium.org + + Counts the number of browser launches where chrome://net-internals and + chrome://net-internals/#tests are used. + + + + + + Removed 06/2020 for cleanup. https://crbug.com/1089011. Not actively used, + large size, and information is not actionable. + + chlily@chromium.org + + When Network Error Logging receives a "NEL:" header, what happens + to it. + + + + + + Removed 11/2019 for cleanup. https://crbug.com/1007122 + + chlily@chromium.org + + When Network Error Logging observes a completed request that might generate + a report, what happens to it. NEL observes all requests, both successful and + unsuccessful. It sends reports for successful and unsuccessful requests at + specified sampling rates so that error rates can be calculated. Insecure + requests are discarded for having an insecure origin regardless of existence + of a policy for the origin. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How often automatically retrying to download the main frame of a page in + response to specific HTTP network errors succeeds. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How often automatically retrying to download a subresource in response to + specific HTTP network errors succeeds. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How often automatically retrying to download the main frame of a page in + response to specific HTTP network errors returns another network error. + Histogram includes only the error code that triggered the retry. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + How often automatically retrying to download a subresource in response to + specific HTTP network errors returns another network error. Histogram + includes only the error code that triggered the retry. + + + + + + Removed 2015-08-17 as part of cookie histogram cleanup + (https://crbug.com/521135). + + Please list the metric's owners. Add more owner tags as needed. + + The number of duplicate cookies that were present in the cookie store during + startup. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to make one or more HTTP + fetches to OCSP responders in order to get revocation information. This + measures the amount of time that failures to get OCSP information take. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to make one or more HTTP + fetches to OCSP responders in order to get revocation information. This + records the fraction of successful requests. + + + + + + Removed 2017-04-21 as it was Linux/CrOS only. + + rsleevi@chromium.org + + When validating an HTTPS certificate we may have to make one or more HTTP + fetches to OCSP responders in order to get revocation information. This + measures the amount of time that each of those requests takes. + + + + + + Removed 12/2018. + + rsleevi@chromium.org + + When connecting over HTTPS, a server may include an OCSP response as part of + the TLS handshake so that clients do not have to fetch it, provided the + client requested the server do so. This measures whether or not a server + included an OCSP response when it was requested. + + + + + + Removed 11/2018. + + mgersh@chromium.org + + Positive error code that was returned by the system library + "getaddrinfo()". This error code is platform specific, so when + there is a Windows/Linux conflict, both decodings are shown. + + + + + + Removed 11/2018. + + mgersh@chromium.org + + Positive error code that was returned by the system library + "getaddrinfo()". + + + + + + Removed 11/2018. + + mgersh@chromium.org + + Positive error code that was returned by the system library + "getaddrinfo()". + + + + + + Removed 11/2018. + + mgersh@chromium.org + + Positive error code that was returned by the system library + "getaddrinfo()". + + + + + + Removed 4/27/2016. No longer tracked. + + eroman@chromium.org + + Proxy Auto Config (PAC) allows specifying an arbitrary javascript program to + pick network proxies on a per-request basis (based on the URL). This works + by calling the script's FindProxyForURL() function with the target URL as + its first argument. + + Traditionally, the URL parameter passed into the script contains the exact + URL being loaded, except maybe for having stripped the fragment and embedded + identity portions of the URL. + + This histogram records what happens when the URL passed into + FindProxyForURL() additionally has had its path component stripped. Does it + return the same proxy list as when calling FindProxyForURL() with the + original (unmodified) URL? + + This comparison is done only when the URL scheme implies a secure channel + (i.e. https:// and wss://), in order to gather data for crbug.com/593759. + + + + + + Removed 4/16/2014. No longer tracked. + + davidben@chromium.org + + How long it took for an <a ping> request to receive a response. Only + recorded if a response was received. + + + + + + Removed 4/16/2014. No longer tracked. + + davidben@chromium.org + + The result of an <a ping> request, whether it received a response or + timed out or failed for some other reason. + + + + + + No longer tracked. + + csharrison@chromium.org + + Indicate whether a link navigation was preceded by a recent pre-connect + trigger (within 10 seconds). There is a high chance that loading the page + used a preconnected TCP session. + + + + + + No longer tracked. + + csharrison@chromium.org + + Indicate whether a URLRequest was preceded by a recent pre-connect trigger + (within 10 seconds). There is a high chance that loading the resource used a + preconnected TCP session. + + + + + + Removed May 2018 + + csharrison@chromium.org + + When a preconnection is made, indicate what the motivation was. + +
+ Currently, the most common (only?) motivations are SELF_REFERAL, + LEARNED_REFERAL and OMNIBOX. The SELF_REFERAL indicates that we made sure a + second connection was available for a resource that either was never before + seen, or has historically had no subresources. The LEARNED_REFERAL indicates + that we "learned" that a subresource was commonly needed, and that + motivated the TCP/IP preconnect. The OMNIBOX motivation happens when a + search is being suggested, and we preconnect to the search provider. + (WARNING: Prior to version 7.517.*, enums 7, 8, and 9 may be confused, as + EARLY_LOAD_MOTIVATED was inserted new 6 value.) +
+ + + + + No longer tracked. + + csharrison@chromium.org + + Indicate whether there was a proxy to preclude preconnection. + + + + + + Removed September 2019 + + tbansal@chromium.org + + Indicates number of times a preconnect to proxy server was skipped due to an + existing pending preconnection request. + + + + + + Removed May 2018 + + csharrison@chromium.org + + What did we decide to do about a predicted resource, based on the historical + expected number of connection that this subresource will require. + +
+ This is basically the current thresholding of the SubresourceExpectation, + relative to current static thresholds, and taking into account whether + preconnection is enabled (i.e., if preconnection is disabled, we'll never + decide to preconnect). +
+ + + + + Removed May 2018 + + csharrison@chromium.org + + The expected number of connections, times 100, that we'll make to a given + subresource, based on learned history. + +
+ By comparing this to thresholds, we decide if we will preconnect, + preresolve, or do nothing. This histogram can be used to select those static + thresholds. +
+ + + + + No longer tracked. + + csharrison@chromium.org + + Indicate whether if a preconnect trigger is followed by a resource request + (from link navigations) to the host or not. This is to measure precision of + link-based preconnect triggers. + + + + + + Sourced data corrected, and replaced by NetPreconnectUtilization2 + + Please list the metric's owners. Add more owner tags as needed. + + Indicate final utilization for each attempted socket connection. + +
+ We also include stats for non-speculative sockets. Some socket connections + may never connect, and others may never be used (as the user may abort + before then). +
+ + + + + Removed in M68 (May 2018) + + csharrison@chromium.org + + Indicate final utilization for each attempted socket connection. + +
+ We also include stats for non-speculative sockets. Some socket connections + may never connect, and others may never be used (as the user may abort + before then). +
+ + + + + Dev data was collected which was good enough to make a decision on the size + of the predictor database. + + csharrison@chromium.org + + The index into the predictor's MRU on navigation. This is the size the MRU + had to be in order to effectively predict subresources for this navigation. + + + + + + Removed May 2018 + + csharrison@chromium.org + + The approximate size in bytes of the predictor's database on startup. + + + + + + Removed July 2018 + + jkarlin@chromium.org + + The completion status of prefetches that have finished loading. + +
+ Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled + before that point are not registered. + + This applies to requests with RESOURCE_TYPE_PREFETCH. + + Note that "success from cache" means that the + UrlRequest::was_cached() was true and unused_since_prefetch was false. + "success from network" means that was_cached() was false. + "success already prefetched" means that both was_cached() and + unused_since_prefetch were true. Validated results are considered cached, + even though a conditional network request is made. +
+ + + + + Removed July 2018 + + jkarlin@chromium.org + + Time spent on prefetch requests before the request was canceled. + +
+ This applies to requests with RESOURCE_TYPE_PREFETCH. +
+ + + + + Removed July 2018 + + jkarlin@chromium.org + + Time spent on requests that were served from a cache entry whose + unused_since_prefetch bit is true. + + + + + + Removed July 2018 + + jkarlin@chromium.org + Time spent on prefetch requests when fetched from cache. +
+ This applies to requests with RESOURCE_TYPE_PREFETCH. +
+ + + + + Removed July 2018 + + jkarlin@chromium.org + + Time spent on prefetch requests when fetched from the network, including + validation time. + + + + + + Removed in M52. + + sclittle@chromium.org + + Records how many *.googlezip.net Data Reduction Proxies were removed from + the effective proxy configuration when a proxy reconfiguration occurs. + + + + + + Replaced by Net.Priority_High_Latency_b. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the start of the http transaction until the first byte of the + response for high priority (currently frame and subframe) requests. Only + times under 10 minutes are recorded. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the start of the http transaction until the first byte of the + response for high priority (currently frame and subframe) requests. + + + + + + Replaced by Net.Priority_Low_Latency_b. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the start of the http transaction until the first byte of the + response for low priority (non-frame/subframe) requests. Only times under 10 + minutes are recorded. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the start of the http transaction until the first byte of the + response for low priority (non-frame/subframe) requests. + + + + + + Removed in Chrome 76. + + eroman@chromium.org + mmenke@chromium.org + + Counts how often a 302 (redirect) response is observed during CONNECT (proxy + tunnel establishment). The counts are bucketed by proxy settings source + (auto-detect vs explicit) and load type (subresource vs main frame). + + To interpret this histogram, the most interesting property will be the + number of users in each of the buckets, which can be used to approximate + what fraction of users would be affected by a policy change that blocked + redirects on subresources/non-autodetected proxies. + + + + + + Removed 2019/02/28, in a proxy auth refactor. + + dschinazi@chromium.org + src/net/OWNERS + + When a PROXY_AUTH_REQUESTED error code is handled in + net::HttpStreamFactoryImpl::Job::RunLoop, this is true if connection_ has an + associated value. + + + + + + Removed at some time before 2014/09/15. + + Please list the metric's owners. Add more owner tags as needed. + + The time in milliseconds spent fetch the system proxy configuration, when + polling it for changes. + + + + + + Removed in M85. + + eroman@chromium.org + + The breakdown of URL schemes seen for explicitly configured ProxyAutoConfig + (PAC). This metric is emitted once each time the proxy settings change + (including initial value). Note that this does not count implicitly inferred + PAC URLs (from WPAD). + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total amount of time that was spent executing the proxy script during + "tracing" runs (executions of the script which discovered a new + DNS dependency and were subsequently abandoned). + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total amount of time that was spent executing the proxy script during + "tracing" runs (executions of the script which discovered a new + DNS dependency and were subsequently abandoned). + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total amount of time that was spent in the non-blocking DNS bindings + while executing PAC scripts. This includes the times for abandoned + executions. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time inside of V8 that the proxy script spent executing for + the final pass. This includes the time spent in the javascript bindings. + This does not include the time spent in abandoned execution passes. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times that alert() was called in the final execution of the + script. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of errors that were seen in the final execution of the script. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times that the PAC script execution was restarted. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that the proxy resolution took. This includes all the time + spent waiting for DNS, PAC script execution, and restarts. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that proxy resolution spent waiting for DNS. This also + includes any queuing delays on the origin thread waiting for the DNS result + to be processed. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of unique DNS hostnames that the PAC script tried to resolve. The + *Ex() versions of the bindings count separately. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total amount of time that was spent in the non-blocking DNS bindings + while executing PAC scripts. This includes the times for abandoned + executions. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time inside of V8 that the proxy script spent executing for + the final pass. This includes the time spent in the javascript bindings + (which is probably dominated by Net.ProxyResolver.DnsWaitTotalTime). This + does not include the time spent in abandoned execution passes. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times that alert() was called in the final execution of the + script. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of errors that were seen in the final execution of the script. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times that the PAC script execution was restarted. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The amount of time it took upon completion to run the final task posted back + to the IO thread. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that the proxy resolution took. This includes all the time + spent waiting for DNS, PAC script execution, and restarts. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that proxy resolution spent waiting for DNS. This also + includes any queuing delays on the origin thread waiting for the DNS result + to be processed. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The total time that the proxy resolution took, not including the post back + to the origin thread. This includes all the time spent waiting for DNS, PAC + script execution, and restarts. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + + The number of unique DNS hostnames that the PAC script tried to resolve. The + *Ex() versions of the bindings count separately. + + + + + + Removed in Chrome 39. + + Please list the metric's owners. Add more owner tags as needed. + The length of the URL that was passed into the PAC script. + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + The network error code of resolving a URL by forwarding the request to the + proxy resolver and executing the PAC script. + + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + The time taken to resolve a URL by forwarding the request to the proxy + resolver and executing the PAC script. This includes PAC script execution, + DNS queries, and internal retries. This does not include retries initiated + by the user, such as by calling ProxyService::ReconsiderProxyAfterError(). + + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + Whether proxy resolution occured by forwarding the request to the proxy + resolver and executing the PAC script. This histogram records all URLs, + regardless of whether a proxy configuration is set. Note that in some cases, + the system proxy resolver is used. If so, this histogram indicates whether + the request was forwarded to the system resolver. However, on desktop + platforms, the number of users using the system resolver should be small + since the default is to use V8. Hence, the count of emissions to the 'True' + bucket on desktop caused by users of the system resolver should be small. + + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + The total time taken to resolve a URL. This includes PAC script execution, + DNS queries, and internal retries. This does not include retries initiated + by the user, such as by calling ProxyService::ReconsiderProxyAfterError(). + + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + Whether a proxy resolution resulted in the PAC script terminating + unexpectedly. This does not include terminations that occured during + initialization of a new proxy resolver. This only happens when the resolver + process crashes when using out-of-process PAC. + + + + + + Removed as of Chrome 61. + + eroman@chromium.org + + Whether the creation of a new proxy resolver resulted in the PAC script + terminating unexpectedly. This only happens when the resolver process + crashes when using out-of-process PAC. + + + + + + Removed as of November 2016 because of disuse. Historical data is likely + inaccurate due to changes in the data structure that calculated domain IDs + for this histogram. + + agl@chromium.org + + Second-level domains for which we have observed public key pinning failures. + + + + + + Removed as of 07/2016. Replaced with Net.PublicKeyPinReportSendingFailure2. + + estark@chromium.org + + A validated certificate chain may be subject to additional pinning + requirements on a per-domain basis. When pinning requirements are violated, + Chrome attempts to send a report about the incident. This records the net + error code when sending a pinning violation report fails. + + + + + + Removed 11/2017. + + dschinazi@chromium.org + src/net/OWNERS + + Records whether HTTP/2 response headers have already arrived on a pushed + stream at the time the stream is matched up with a request. See + https://crbug.com/554220. + + + + + + Obsoleted in April 2020. + + tbansal@chromium.org + rajendrant@chromium.org + robertogden@chromium.org + + Breakdown of how requests which could potentially make use of an alternative + QUIC proxy server use or don't use the QUIC server. + + + + + + Removed 11/2019, associated bug is root-caused and fixed. + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of times that QuicChromiumPacketReader should stop reading in the + loop at StartReading. This data will be compared against crashes and help + investigate https://crbug.com/1014092. + + + + + + Removed 11/2019, associated bug is root-caused and fixed. + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of times that QuicChromiumPacketReader should stop reading after + finishing the previous read. This data will be compared against crashes and + help investigate https://crbug.com/1014092. + + + + + + Removed 08/2014, and replaced by + Net.QuicClientHelloServerConfig.InvalidDuration. + + dschinazi@chromium.org + src/net/quic/OWNERS + + How expired server config is for sending inchoate ClientHello to the server. + + + + + + Removed in 2018. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The time since expiration of server config when we sent inchoate ClientHello + to the server. + + + + + + Removed as of 11/2014. Replaced by Net.QuicInchoateClientHelloReason. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The reason (the state of the server config) for sending inchoate ClientHello + to the server. + + + + + + Removed 02/2018. No data for this histogram for more than 30 days. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times Connection's visitor is a nullptr when CloseConnection + is called. + + + + + + Removed in 2018. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times CryptoClientConfig's CachedState is populated from + canonical config whenever we create a new CryptoClientConfig::CachedState. + + + + + + Removed as of 4/15/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Tracks number of times data read/parse/write API calls of QuicServerInfo to + and from disk cache is called. + + + + + + Removed as of 10/2014. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Tracks the opening and closing of disk cache entries. Recorded each time a + disk cache entry is either opened or closed. + + + + + + Removed as of 04/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of ports suggested per server. + + + + + Removed 2016. No longer tracked. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times QuicHttpStream's session_ is a nullptr before + StartRequest() is called. + + + + + + Removed in 2018. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The reason (the state of the server config) for sending inchoate ClientHello + to the server. + + + + + + see Net.QuicSession.Connect*PortForHTTP* + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of client hello messages sent when the crypto handshake was + confirmed. + + + + + + Removed in 07/2020. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of stream frames bundled within a received packet. + + + + + + Removed in 07/2020. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of stream frames per stream ID within a received packet. + + + + + + Removed as of 05/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times QuicHttpStream's stream_ is a nullptr before + IsDoneReading() is called. + + + + + + Removed as of 4/15/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + Time spent to load QUIC server information from disk cache. + + + + + Removed as of 10/2014. Replaced by DiskCacheWaitForDataReadyTime. + + dschinazi@chromium.org + src/net/quic/OWNERS + Time spent to load QUIC server information from disk cache. + + + + + Removed as of 4/19/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Time spent waiting to load QUIC server information from disk cache. + + + + + + Removed as of 4/15/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of times AlternateProtocolMap supports QUIC, but there is no QUIC + server information in the disk cache. This is recorded whenever QUIC server + information is loaded from the disk cache. + + + + + + Removed as of 8/3/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The elapsed time between waiting for reading of QUIC server information from + disk cache, and receiving crypto handshake confirmation from the server. + Will measure the impact of cancelling the WaitForDataReady callback. Logged + after crypto handshake is confirmed. + + + + + + Removed as of 4/15/2017. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The ratio of the time spent waiting to load QUIC server information from + disk cache to the min rtt. Logged when session is closed. + + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + + This histogram summarizes information about a 21 packet sequence, indicating + for each of the 21 possible prefixes of this pattern, how many packets were + received in that prefix. The first range uses buckets 0 and 1, and it + describes the 1st packet in the sequence. It indicates if the first packet + was missing (bucket 0), or the first packet was present (bucket 1). The + second range uses buckets 2 through 4, and describes the first 2 packets in + the prefix of this sequence. It indicates if there were no packets received + in the first two packets (bucket 2), or there was one out of two packets + received (bucket 3), or if there was two out of tow received (bucket 4). + etc. etc. Reading this histogram may require post-processing in a spread + sheet, but can indicate the potential value of using FEC packets to convey + data. + + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Each of the 64 buckets represents a different binary pattern of 6 + consecutive packets that were received by the client. The LSB of the bucket + number corresponds to the reception of the oldest packet. A bit in the + bucket-number being 1 indicates the packet was received, and a 0 means the + packet was never received (by the client). + + + + + + Removed in M81. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The QUIC error code which resulted in the Google QUIC connection being + closed. + + + + + + Removed in M75 + + dschinazi@chromium.org + src/net/quic/OWNERS + + Logs whether channel ID was used when a cookie is sent over QUIC to + https://accounts.google.com. + + + + + + see Net.QuicSession.Connect*PortForHTTP* + + dschinazi@chromium.org + src/net/quic/OWNERS + + Samples of the number of round-trips needed by a QUIC connection before a + request could be sent by the client. + + + + + + The experiments with head of line blocking have been completed, and the code + tracking head of line blocking was removed. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The elapsed time that headers are head of line blocked on others, presumably + due to lost headers stream packets. + + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The frames received on the headers stream which arrived early. + + + + + + Removed 08/2016. No longer tracked. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Time spent resolving the DNS name of the server for a QUIC connection. + + + + + + Removed 2018-10. No longer tracked. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The location where a QUIC internal error was generated, recorded any time an + internal error is generated, which should be once per connection. + + + + + dschinazi@chromium.org + src/net/quic/OWNERS + + If a QUIC connection timed out locally with open streams, this contains the + time since any data was read from the network until the connection was + closed. The suffix specifies whether there were any unacked packets pending + when the connection timed out. {UnackedPackets} + + + + + Removed as of 08/2016. + + + + + Removed as of 08/2016. + + + + + Removed as of 08/2016. + + + + + + + + Removed 04/2020, no longer needed. + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of queued packets when a connection is closed due to writing an + out of order packet. + + + + + + Removed in 2018. + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of queued packets when a connection starts to write queued + packets. + + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Each bucket corresponds to a specific packet sequence number that was sent + by a server to Chrome at the start of a QUIC connection. This histogram is + compared, bucket by bucket, with a second histogram to compute the ratio for + each bucket (each packet sequence number). + + + + + + Removed 02/2018. Use Net.QuicSession.PublicResetAddressMismatch2. + + wtc@google.com + src/net/quic/OWNERS + + When a public reset packet is received, whether the client IP address and + port number in it differ from the client IP address and port number in the + ServerHello handshake message. In the comparison, the first address is the + one in ServerHello and the second address is the one in public reset. Note: + this histogram is obsolete because it failed to treat IPv4-mapped IPv6 + addresses as IPv4 addresses. + + + + + + Removed in M84. Use Net.QuicSession.ReceivedSettings.MaxHeaderListSize2 + instead. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the SETTINGS_MAX_HEADER_LIST_SIZE parameter received on an + HTTP/3 connection, if any. + + + + + + Removed in M84. Use Net.QuicSession.ReceivedSettings.MaxTableCapacity2. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The value of the SETTINGS_QPACK_MAX_TABLE_CAPACITY parameter received on an + HTTP/3 connection, if any. + + + + + + Removed 11/2017. Use Net.QuicSession.RetryAfterWriteErrorCount2. + + dschinazi@chromium.org + src/net/quic/OWNERS + + The number of consecutive times a packet was retried after a write error. + + + + + + Removed 03/2018 as crbug.com/817496 is resolved. + + zhongyi@chromium.org + + The number of times the connection sends connectivity probe to the peer. + + + + + + Removed in 9/19 because this metric was added to inspect a crash and the + crash had been fixed. + + renjietang@chromium.org + zhongyi@chromium.org + + True if at the time of Dns comparison between fresh resolution and stale + resolution, session_ is valid. + + + + + + Removed in 9/19 because this metric was added to inspect a crash and the + crash had been fixed. + + renjietang@chromium.org + zhongyi@chromium.org + + Logs places in code where stale host resolution doesn't have valid results. + For control purpose, it also logs when a valid stale result is used. + + + + + + Removed 04/2015. Tracked as Net.QuicSession.TooManyOpenStreams. + + dschinazi@chromium.org + src/net/quic/OWNERS + + True if more than 100 streams are open when a new stream is activated. + + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of truncated ACK frames received. + + + + + Removed 08/2016. + + dschinazi@chromium.org + src/net/quic/OWNERS + The number of truncated ACK frames sent. + + + + + Removed 06/2018 after https://crbug.com/818040 is fixed. + + wub@chromium.org + + Temporary histogram being used to investigate https://crbug.com/818040. + Records whether a connection is closed when an out of order queued packet is + about to be written. + + + + + + Removed 11/2018. Replaced by MigrationBeforeHandshake2. + + zhongyi@chromium.org + + Status of the connection which is created for migration before handshake is + confirmed. + + + + + + Depecated on 07/2020. Replaced by + Net.QuicConnectivityMonitor.NumAllDegradedSessions. + + zhongyi@chromium.org + src/net/quic/OWNERS + + The number of sessions that are degrading on network change. The suffix + specifies the network change. + + + + + + Deprecated on 07/2020. Replaced by + Net.QuicConnectivityMonitor.NumActiveQuicSessionsAtNetworkChange. + + zhongyi@chromium.org + rockot@chromium.org + src/net/quic/OWNERS + + The number of QUIC sessions when a network change is detected. + + + + + + Depecated on 07/2020. Replaced by + Net.QuicConnectivityMonitor.PercentageAllDegradedSessions. + + zhongyi@chromium.org + src/net/quic/OWNERS + + Of all the exisiting sessions, the percentage of sessions that detects + degrading on network change. The suffix specifies the network change. + + + + + + Removed 06/2016. No longer tracked. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Whether TSVIPCli DLL is loaded or not on windows when the socket is + configured. + + + + + + Removed 08/2016. No longer tracked. + + zhongyi@chromium.org + + Time duration from last packet sent to a new packet sent in QUIC connection. + + + + + + Removed in 2018. + + dschinazi@chromium.org + src/net/quic/OWNERS + + Logged whenever proof verification fails and if the failure occurred before + or after the crypto handshake is confirmed. + + + + + + Removed 03/2015. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + True if the HTTP request was sent to a server which supports the TLS + renegotiation extension. + + + + + + Removed 06/2020. No longer tracked. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a single endpoint group in a + Report-To header once the header itself has been parsed. + + + + + + Removed 06/2020. No longer tracked. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a single endpoint in a Report-To + header once the header itself has been parsed. + + + + + + Removed 06/2020. No longer tracked. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a Report-To header. Once it is + parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints + within it. + + + + + + Removed June 2020 for cleanup. https://crbug.com/1089017 + + juliatuttle@chromium.org + + When Reporting successfully delivers a report, the number of unsuccessful + delivery attempts that preceded the successful one. + + + + + + Removed June 2020 for cleanup. https://crbug.com/1089017 + + juliatuttle@chromium.org + + The delivery latency of reports successfully delivered by Reporting. Starts + when the report is queued and finishes when the delivery attempt returns + successfully. + + + + + + Removed June 2020 for cleanup. https://crbug.com/1089017 + + juliatuttle@chromium.org + + The error (net or HTTP) encountered by Reporting trying to upload one or + more reports to a single endpoint in a single request, recorded when the + upload attempt completes, if and only if the attempt failed with a net error + or an HTTP error other than 410 (which is specified to mean "remove + endpoint"). + + + + + + Removed June 2020 for cleanup. https://crbug.com/1089017 + + juliatuttle@chromium.org + + The outcome of Reporting trying to upload one or more reports to a single + endpoint in a single request, recorded when the upload attempt completes. + + + + + + Replaced by Net.RequestTime2 due to bug in original implementation. + + + The amount of time between request initiation and request completion for + success and various different errors. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + + The amount of time between request initiation and request completion for + success and various different errors. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + ERR_ABORTED when the request's scheme is http/s. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + ERR_ABORTED when the requests TotalReceivedBytes() > 0. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + ERR_ABORTED when the requests TotalReceivedBytes() = 0 and + received_response_content_length() = 0. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + ERR_ABORTED when the requests TotalReceivedBytes() = 0 and + received_response_content_length() > 0. + + + + + + Unused, so removed from Chromium as of 2017/8/31. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + ERR_ABORTED when the request's scheme is not http/s. + + + + + + Removed from Chromium as of 2018/7/2. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + success for main frame resources. + + + + + + Removed from Chromium as of 2018/7/2. + + csharrison@chromium.org + + The amount of time between request initiation and request completion for + success for non-main frame resources. + + + + + + Removed from Chromium as of 2018/7. + + mef@chromium.org + pauljensen@chromium.org + + The largest number of outstanding requests that are handled by the resource + dispatcher host for a single process. + + + + + + Removed from Chromium as of 2018/7. + + mef@chromium.org + pauljensen@chromium.org + + The largest number of outstanding requests that are handled by the resource + dispatcher host across all processes. + + + + + + Removed from code as of 03/2018. + + ksakamoto@chromium.org + + The largest number of outstanding requests handled by the resource + dispatcher host, during the last sample interval (60 seconds). Not logged if + there are no outstanding requests in the interval. This metric is temporary + for the Loading Dispatcher v0 (crbug.com/723233), and will be removed soon. + + + + + + Removed from code as of 11/2018. + + yhirano@chromium.org + toyoshim@chromium.org + + Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) + for HTTP "GET" requests. + + + + + + Removed from code as of 11/2018. + + yhirano@chromium.org + toyoshim@chromium.org + + Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) + for HTTP "POST" requests. + + + + + + Removed from code as of 11/2018. + + yhirano@chromium.org + toyoshim@chromium.org + + Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode) + for HTTP "POST" requests whose url contains a port. + + + + + + Removed 10/2017. + + mmenke@chromium.org + maksim.sisov@intel.com + + Records how many times expected content size equals/less/more than size of + read body/buffer or content size is unkown. Recorded for each resource load. + + + + + + This experiment was turned down, see https://crbug.com/703188. + + tzik@chromium.org + + Counts whether the chunk inlining is applicable or not to a resource + loading. Counts the reason if inapplicable. + + + + + + Removed 09/2020, no longer needed. + + tzik@chromium.org + + Time from the start to the end of receiving a response body. Recorded for + each resource load. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed from Chromium as of 2018/7/2. + + csharrison@chromium.org + + The time elapsed from URLRequest creation to when a ResourceLoader actually + calls Start on it. + + + + + + The code to record this histogram was removed November 2017. + + juliatuttle@chromium.org + + Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by + the browser process. + + + + + + The code to record this histogram was removed November 2017. + + juliatuttle@chromium.org + + Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by + a renderer process. + + + + + + The code to record this histogram was removed November 2017. + + juliatuttle@chromium.org + + Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by + a process not covered by one of the other ResponseSizeByProcess histograms. + + + + + + Removed Aug 2020. This was added to evaluate safety of proposed code + changes, and is no longer necessary as the necessary results were obtained. + + chlily@chromium.org + morlovich@chromium.org + + Logged whenever the RestrictedCookieManager sets a CanonicalCookie. True if + the domain of the cookie matches the domain of the URL, false otherwise. + + + + + + Removed as of 9/2017. + + mef@chromium.org + pauljensen@chromium.org + + Whether an idle socket is reused, timed out, or closed to make room for new + sockets. + + + + + + Removed as of 7/2017. + + mmenke@chromium.org + + Seconds a socket was idle before it was reused. Emitted upon reuse. Does not + record the times sockets were idle before first use. + + + + + + Removed as of 11/2016. + + mef@chromium.org + pauljensen@chromium.org + + Number of milliseconds an idle socket saved in connection establishment + because it is reused. + + + + + + Removed as of 06/2020. + + mmenke@chromium.org + Number of idle sockets when one of them was reused. + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + The time an already used socket sat idle before being used. + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The time an unused socket (all HTTP sockets, regardless of any proxy used) + sat idle before being used. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time a previously used socket sat idle before encountering a recoverable + socket IO error (connection abort/reset/close). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time an unused socket sat idle before encountering a recoverable socket + IO error (connection abort/reset/close). + + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Net error codes that socket initializations end with, including net::OK and + net::ERR_ABORTED. + + + + + + Replaced by Net.SocketUnchangeableReceiveBuffer 3/31/2014. + + + The size of a socket's receive buffer when the attempt to change it via + setsockopt failed. + + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + Time in milliseconds from initial RequestSocket() call until successfully + acquiring a connected socket. + + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + The time from the connection start to connection establish. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + The time waiting to be ready to start connecting. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + + Each bucket is the number of connection type of socket stream. + + + + + + Removed 2014-10-28. No longer generated. Replaced by Net.WebSocket.Duration. + + yhirano@chromium.org + ricea@chromium.org + The time a socket stream was open. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + + Each bucket is the number of protocol type on socket stream. + + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + Number of bytes on a socket stream. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + Number of reads on a socket stream. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + Number of bytes on a socket stream. + + + + + Removed 2014-10-28. No longer generated. No direct replacement. + + yhirano@chromium.org + ricea@chromium.org + Number of Write on a socket stream. + + + + + Removed as of 03/2015. + + Please list the metric's owners. Add more owner tags as needed. + + The counts of the type of sockets returned by the socket pools. + + + + + + see SocketIdleTimeBeforeNextUse_ReusedSocket_SOCK + + Please list the metric's owners. Add more owner tags as needed. + + The time an already used SOCKS socket sat idle before being used. + + + + + + see SocketIdleTimeBeforeNextUse_UnusedSocket_SOCK + + Please list the metric's owners. Add more owner tags as needed. + The time an unused SOCKS socket sat idle before being used. + + + + + see SocketRequestTime_SOCK + + Please list the metric's owners. Add more owner tags as needed. + + Time from initial SOCKSClientSocketPool::RequestSocket() call until + successfully acquiring a connected SOCKS socket. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Time it takes to request a new (unused) SOCKS proxy socket. + + + + + see SocketType_SOCK + + Please list the metric's owners. Add more owner tags as needed. + + The counts of the type of sockets returned by the SOCKS pool. + + + + + + Replaced by Net.SpdyConnectionLatency_2 on 2014-10-21. + + dschinazi@chromium.org + src/net/OWNERS + Time from when the Connect() starts until it completes. + + + + + Removed 2018-02. + + dschinazi@chromium.org + src/net/OWNERS + Time from when the Connect() starts until it completes. + + + + + The last protocol which would trigger this was deprecated in 2014 November. + This histogram is deprecated in 2016 January. + + dschinazi@chromium.org + src/net/OWNERS + + The counts of the flow control state of each frame (with stream flow control + on). + + + + + + Removed in 2020-03 once we confirmed the numbers looked as expected. + + dschinazi@chromium.org + + The highest number of capped frames queued in the SPDY write queue. + + + + + + Obsolete as HTTP/2 standard is finalized. + + dschinazi@chromium.org + src/net/OWNERS + + Frequencies of characters observed in request and response headers. + Temporarily being collected to inform the construction of an optimized + Huffman code for the HTTP/2 specification. Buckets are ASCII codes offset by + 1. + + + + + + Removed 2019-10-01. + + dschinazi@chromium.org + src/net/OWNERS + The RTT for SPDY's PING. + + + + + Removed 2016-05-26. + + dschinazi@chromium.org + src/net/OWNERS + The count of streams at each priority over Spdy sessions. + + + + + Removed because it took up too much space and nobody used it. + + dschinazi@chromium.org + src/net/OWNERS + The number of bytes recevied per stream. + + + + + Removed because it took up too much space and nobody used it. + + dschinazi@chromium.org + src/net/OWNERS + The number of bytes sent per stream. + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + Total number of bytes recevied per session before closing session due to + EOF. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + Total number of bytes recevied per session before closing session due to an + error during read. + + + + + + Replaced by SpdySessionErrorDetails2 on 2013-04-19. + + dschinazi@chromium.org + src/net/OWNERS + + WARNING: r181910 added an enum value in the middle, so don't trust the + counts for values 9 and above for Chrome builds after that revision. + + The type of SPDY Protocol error encountered. + + + + + + Replaced by SpdySessionErrorDetails_Google2 on 2013-04-19. + + dschinazi@chromium.org + src/net/OWNERS + + The type of SPDY Protocol error encountered when talking to a google.com + server. + + + + + + Removed 7/21/2014. No longer tracked. + + bengr@chromium.org + bolian@chromium.org + src/net/OWNERS + + The count of SPDY sessions using the data reduction proxy and the count of + other SPDY sessions. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + SpdySession::GetLocalAddress returned ERR_SOCKET_NOT_CONNECTED. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + SpdySession::GetPeerAddress returned ERR_SOCKET_NOT_CONNECTED. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + The count of SPDY Sessions with or without stalls. + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + The congestion window (in pkts) received at the end of a SpdySession. + + + + + + Removed 2016 July with removal of SPDY/3.1. + + dschinazi@chromium.org + src/net/OWNERS + + The congestion window (in pkts) sent at the beginning of a SpdySession. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + Percentage of sessions which received settings from the server. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + + The Download Retransmission Rate (%) received at the end of a SpdySession. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + The RTT received at the end of a SpdySession. + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + Percentage of sessions which sent settings to the server. + + + + + Removed because it took up too much space and nobody used it. + + dschinazi@chromium.org + src/net/OWNERS + + The time between receiving the first chunk and the last chunk of data on a + Spdy stream. + + + + + + Removed on 2016-10-10. + + dschinazi@chromium.org + src/net/OWNERS + The number of stream stalls per session. + + + + + Removed because it took up too much space and nobody used it. + + dschinazi@chromium.org + src/net/OWNERS + + The time of a Spdy stream. Measured from sending the first chunk to + receiving the last chunk of data. + + + + + + Removed because it took up too much space and nobody used it. + + dschinazi@chromium.org + src/net/OWNERS + + The time between sending the request and receiving the first chunk of data + on a Spdy stream. + + + + + + Removed on 2016-11-28, because SPDY/3 and, accordingly, SYN_STREAM frames + are no longer used. Compression values are now calculated slightly + differently. Replaced by Net.SpdyHeadersCompressionPercentage. + + dschinazi@chromium.org + src/net/OWNERS + + The percent compression achieved when compression SYN_STREAM frames. + + + + + + Removed on 2014-09-11, because the uploaded values were changing as + protocols were removed, therefore statistics couldn't be combined across + different builds. Replaced by Net.SpdyVersion2. + + dschinazi@chromium.org + src/net/OWNERS + + The SPDY protocol version that is used to talk to SPDY servers. + + + + + + Removed on 2016-02-01, because the incorrect bucket count caused data + corruption. Replaced by Net.SpdyVersion3. + + dschinazi@chromium.org + src/net/OWNERS + + The SPDY protocol version that is used to talk to SPDY servers. Logged every + time a SPDY session is initialized. + + + + + + Removed 2016 July with removal of SPDY/3.1. + + dschinazi@chromium.org + src/net/OWNERS + + The SPDY protocol version that is used to talk to SPDY servers. Logged every + time a SPDY session is initialized. + + + + + + Removed 2018-01 with the transition to a unified root list with OS fallback. + + rsleevi@chromium.org + + The results of comparing the built-in list of known Windows roots against + the CERT_AUTH_ROOT_SHA256_HASH_PROP_ID certificate property. Recorded for + each certificate verification on Windows. + + + + + + Removed 7/21/2015. No longer tracked. + + bengr@chromium.org + + Counts of specific error codes returned when opening an SSL connection for + an endpoint which is eligible for fastradio padding. + + + + + + Removed 2018-03-07. No longer tracked. + + svaldez@chromium.org + + Counts of specific error codes returned when opening an SSL connection for + google.com and any subdomain of it. + + + + + + Replaced by Net.SSL_Connection_Latency_2 on 2014-10-21. + + agl@chromium.org + Time from when the Connect() starts until it completes. + + + + + Removed 7/21/2014. No longer tracked. + + bengr@chromium.org + bolian@chromium.org + + Time from when the Connect() starts until it completes when using the data + reduction proxy. This includes certificate retrieval and verification. + + + + + + Removed 2019-07-19. No longer tracked. + + agl@chromium.org + + Time from when the Connect() starts until it completes for full handshakes. + + + + + + Replaced by Net.SSL_Connection_Latency_Google2 on 2014-10-21. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it. + + + + + + Removed 2018-03-07. No longer tracked. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it. + + + + + + Removed 2018-03-07. No longer tracked. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it for full handshakes. + + + + + + Removed in 2011. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it. This only includes users in a 50% field trial that + disables revocation checking for certificate pinned sites. + + + + + + Removed 2018-03-07. No longer tracked. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it for resumption handshakes. + + + + + + Removed in 2011. + + agl@chromium.org + + Time from when the Connect() starts until it completes for google.com and + any subdomain of it. This only includes users not in a 50% field trail that + disables revocation for certificate pinned sites. + + + + + + Experiment ended 2019-10-01. + + agl@chromium.org + davidben@chromium.org + + Time from when the Connect() starts until it completes, but only for servers + that are part of the post-quantum experiment. + + + + + + Removed as of 2016-12-01. + + mab@chromium.org + + Time from when the Connect() starts until it completes (full handshakes + only), for a set of domains that we expect to always offer the experimental + post-quantum (CECPQ1) ciphersuites. + + + + + + Removed as of 2018-07-06. + + agl@chromium.org + + Time from when the Connect() starts until it completes for any server that + echos a dummy post-quantum padding extension. + + + + + + Removed 2019-07-19. No longer tracked. + + agl@chromium.org + + Time from when the Connect() starts until it completes for resumption + handshakes. + + + + + + Removed as of 2016-12-01. + + mab@chromium.org + + For only browsers in the post-quantum (CECPQ1) ciphersuite experiment, + counts the full TLS handshakes where CECPQ1 was, or was not, negotiated on + hosts where we expect it to be negotiated. + + + + + + Removed as of 01/2016. + + eranm@chromium.org + rsleevi@chromium.org + + The state of compliance with Certificate Transparency presence requirements + for each EV certificate. An EV certificate could be non-compliant (in which + case it loses the EV status), comply through inclusion in the EV whitelist + or have the required number of Signed Certificate Timestamps. This metric + will gauge adoption rate of Certificate Transparency and will help identify + when the EV whitelist is no longer needed. Emitted during every SSL + connection establishment, but only if the client is checking compliance with + Certificate Transparency requirements (currently guarded by a Finch + experiment). + + + + + + Removed 06/2017 with the deprecation of the EV certificate whitelist after + all certificates expired. + + eranm@chromium.org + rsleevi@chromium.org + + Whether an EV certificate is present in the Certificate Transparency + whitelist. Emitted once for every EV certificate encountered (during SSL + connection establishment), but only if the client has a valid whitelist. + + + + + + Removed 06/2017 with the deprecation of distinct EV and !EV CT policies. + + eranm@chromium.org + rsleevi@chromium.org + + The state of compliance with Certificate Transparency presence requirements + for each EV certificate. An EV certificate could be non-compliant (in which + case it loses the EV status), comply through inclusion in the EV whitelist + or comply with the CT certificate policy. This metric will gauge adoption + rate of Certificate Transparency and will help identify when the EV + whitelist is no longer needed. Emitted during every SSL connection + establishment. + + + + + + Removed 06/2017 with the deprecation of the EV certificate whitelist after + all certificates expired. + + eranm@chromium.org + rsleevi@chromium.org + + Whether the client holds a valid EV Certificates whitelist or not. Only + emitted when an EV cert that is not compliant with the Certificate + Transparency requirement is encountered. This histogram is intended to be + short-lived and help determine if EV certificates are considered + non-compliant because they are not whitelisted or if the client does not + hold a valid instance of the whitelist. + + + + + + Removed September 2016. + + agl@chromium.org + rsleevi@chromium.org + sigbjorn@opera.com + + Bit strength of the key exchange for DHE. Recorded for each SSL/TLS + connection in the socket pool where Connect() succeeds. + + + + + + Removed May 2016. + + agl@chromium.org + rsleevi@chromium.org + sigbjorn@opera.com + + Bit strength of the key exchange for RSA. Recorded for each SSL/TLS + connection in the socket pool where Connect() succeeds. See |SSL_SESSION|'s + key_exchange_info for more information. + + + + + + Removed on 01/2016. Only ever measured blacklisted Comodo serials, not any + of the other blacklisted certificates and keys. + + agl@chromium.org + + Counts the number of times that users have hit blacklisted certificates. The + indexes match up to the indexes in + net/base/x509_certificate.cc:IsBlacklisted. The details of the certificates + in question is confidential. + + + + + + Removed in 08/2017. + + davidben@chromium.org + + For each HTTPS connection to the TLS 1.3 experiment server set, whether the + TLS 1.3 anti-downgrade mechanism would have fired. This is to measure the + effects of non-compliant middleboxes on this otherwise safe security + feature. The numbers are only valid while the TLS 1.3 experiment set deploys + a TLS 1.3 draft version compatible with the corresponding Chrome version and + implement the our draft anti-downgrade signal. See + https://crbug.com/boringssl/226. + + + + + + Removed June 2016. + + davidben@chromium.org + + For each successful HTTPS request which used the TLS version fallback, the + error code of the last failed attempt. + + + + + + Removed June 2016. + + davidben@chromium.org + + For each successful HTTPS request which used the TLS version fallback, the + type of handshake failure of the last failed attempt. + + + + + + Removed in 2011. + + Please list the metric's owners. Add more owner tags as needed. + Time to complete a DNS lookup for a DNS CAA record. + + + + + Removed in 2011. + + Please list the metric's owners. Add more owner tags as needed. + + Time that we would have wasted had we waited for a CAA lookup in order to + validate a certificate. + + + + + + Removed in 2012. + + Please list the metric's owners. Add more owner tags as needed. + Time to complete a speculative certificate verification. + + + + + Removed in March 2016. + + davidben@chromium.org + + The cipher suite used when the corresponding operation on an SSLClientSocket + fails with ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when + https://crbug.com/593963 is resolved. + + + + + + Removed in March 2016. + + davidben@chromium.org + + The internal, version-specific BoringSSL error reason reported when the + corresponding operation on an SSLClientSocket fails with + ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when + https://crbug.com/593963 is resolved. + + + + + + Superseded by Net.SSLNegotiatedAlpnProtocol in 2016 August. + + dschinazi@chromium.org + src/net/OWNERS + + TLS extension used to negotiate protocol (ALPN or NPN); in case of NPN, + whether the protocol is indeed supported by both the client and the server + or is a fallback because of no overlap; and the negotiated protocol itself. + + + + + + Removed in January 2018. + + davidben@chromium.org + svaldez@chromium.org + + The number of bytes, excluding the record header, of each TLS record read. + + + + + + Removed 2020-06. + + davidben@chromium.org + + For each TLS connection which uses a known root, an RSA key, and TLS 1.2 or + below, what the result of checking the RSA key usage would have been. + + + + + + Removed in August 2019 + + davidben@chromium.org + + For each attempted SSL renegotiation (non-initial handshake), whether the + server supported the renegotiation_info extension (RFC 5746). + + + + + + Replaced by Net.SSLSignatureAlgorithm. + + davidben@chromium.org + + For each SSL connection with a full handshake using a DHE- or ECDHE-based + key exchange, the hash function used in the ServerKeyExchange signature. + + + + + + Removed on 2017-10-02. + + nharper@chromium.org + + For each SSL connection where we resume a session and negotiate HTTP/2, the + simulated minimum number of sessions retained per host it would have + required with TLS 1.3 single-use sessions. See https://crbug.com/631988. + + + + + + Removed on 2015-11-10. + + davidben@chromium.org + + For each SSL connection that resumed a session, whether the session was + resumed at the same version it was established at. This is only recorded in + BoringSSL ports. + + + + + + Removed 2020-07-28. + + svaldez@chromium.org + davidben@chromium.org + + For each HTTPS connection, whether the TLS 1.3 anti-downgrade mechanism + would have fired. This is only recorded if enforcement has been disabled and + includes samples from non-1.3 servers. See https://crbug.com/boringssl/226. + + + + + + Removed 2020-07-28. + + svaldez@chromium.org + davidben@chromium.org + + For each HTTPS connection to the TLS 1.3 experiment server set, whether the + TLS 1.3 anti-downgrade mechanism would have fired. This is only recorded if + enforcement has been disabled and is only valid while the TLS 1.3 experiment + set deploys the final TLS 1.3 version. See https://crbug.com/boringssl/226. + + + + + + Removed 2020-07-28. + + svaldez@chromium.org + davidben@chromium.org + + For each HTTPS connection that triggered the TLS 1.3 anti-downgrade + mechanism, the key exchange and whether the root was known. + + + + + + Removed 2020-07-28. + + svaldez@chromium.org + davidben@chromium.org + + For each HTTPS connection to the TLS 1.3 experiment server set that + triggered the TLS 1.3 anti-downgrade mechanism, the key exchange and whether + the root was known. + + + + + + Removed 2020-03. + + davidben@chromium.org + vasilvv@chromium.org + + For each session added to TLS session cache that uses TLS 1.3 or later, the + lifetime of the session. Note that this incorporates both the + server-supplied timeout and any local restrictions imposed by the client + itself. + + + + + + Removed 2020-03. + + davidben@chromium.org + vasilvv@chromium.org + + For each TLS 1.3 session successfully retrieved from the session cache, the + time between the session was added and the time it was retrieved. + + + + + + Removed on 2014-08-20. + + Please list the metric's owners. Add more owner tags as needed. + + The number of times that we have performed SSLv3 fallback and found a TLS + renegotiation patched server. + + + + + + Removed in 2012. + + Please list the metric's owners. Add more owner tags as needed. + Was a speculative certificate verification used? + + + + + Removed in 2012. + + Please list the metric's owners. Add more owner tags as needed. + Time saved by a speculative certificate vertification. + + + + + Removed April 2018. + + davidben@chromium.org + svaldez@chromium.org + + For each detected SSL version interference against a server in the initial + TLS 1.3 deployment, details on how the initial connection failed. + + + + + + Removed April 2019. + + davidben@chromium.org + + For each detected SSL version interference, what network error the original + failed connection reported. + + + + + + Removed April 2019. + + davidben@chromium.org + + For each SSL version interference probe, what network error triggered it. + Probes are only triggered for a small set of network errors. + + + + + + Removed in 07/2017. + + palmer@chromium.org + + True if a DNS name contains only characters for which + |net::IsValidLabelCharacter| returns true. Used to see if we can deprecate + and remove support for arbitrary bytes in DNS names. This histogram is + recorded after DNS resolution has completed successfully. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Number of idle sockets when the Connect() succeeded. + + + + + Removed 02/2019, as fast open support has been removed. + + dschinazi@chromium.org + src/net/OWNERS + + For sockets for which a TCP Fast Open protocol might be used, the result of + trying to use it. + + + + + + see SocketIdleTimeBeforeNextUse_ReusedSocket_TCPforSOCKS + + Please list the metric's owners. Add more owner tags as needed. + + The time an already used TCP socket sat idle before being used for a SOCKS + request. + + + + + + see SocketIdleTimeBeforeNextUse_UnusedSocket_TCPforSOCKS + + Please list the metric's owners. Add more owner tags as needed. + + The time an unused TCP socket sat idle before being used for a SOCKS + request. + + + + + + see SocketRequestTime_TCPforSOCKS + + Please list the metric's owners. Add more owner tags as needed. + + Time from initial SOCKSClientSocketPool::RequestSocket() call until + successfully acquiring a connected TCP socket. + + + + + + see SocketType_TCPforSOCKS + + Please list the metric's owners. Add more owner tags as needed. + + The counts of the type of sockets returned by the TCP pool used by the SOCKS + pool. + + + + + + Was only used for HTTP[S] connections, renamed to Net.HTTPSocketType. + + Please list the metric's owners. Add more owner tags as needed. + The counts of the type of TCP socket returned. + + + + + Experiment complete, code removed. + + davidben@chromium.org + + The time it took to do an IO to UI round-trip in the + ThreadHopResourceThrottle. This is part of an experiment to determine the + feasibility to moving some high-level resource loading checks to the UI + thread. + + + + + + Token Binding was removed in Q4 2018 and this histogram was removed in + 3/2019. + + nharper@chromium.org + Time spent creating a Token-Binding header. + + + + + Token Binding was removed in Q4 2018 and this histogram was removed in + 3/2019. + + nharper@chromium.org + + Logs on each request that is sent on a connection where Channel ID was sent + whether the key that would be used for Token Binding matches the key used + for Channel ID. + + + + + + Token Binding was removed in Q4 2018 and this histogram was removed in + 3/2019. + + nharper@chromium.org + + For each request to accounts.google.com on a connection where Channel ID was + sent, this logs whether the Cookie store and the Channel ID store were + ephemeral or persistent. + + + + + + Token Binding was removed in Q4 2018 and this histogram was removed in + 3/2019. + + nharper@chromium.org + + The number of secure HTTP requests broken down by support for Token Binding, + indicating if Token Binding was negotiated and supported by both client and + server, or why it wasn't if not. + + + + + + Discontinued as of 4/12/09 + + Please list the metric's owners. Add more owner tags as needed. + + Effective bandwidth in KByte/Second of transactions logged to + Transaction_Latency histogram. Note that only samples durations greater than + zero ms, and less than 1 hour are tallied into this ratio. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the when the network transaction is requested, until the first + byte of the header is received. + + + + + + Replaced by Net.Transaction_Connected_New_b. + + Please list the metric's owners. Add more owner tags as needed. + + When a new connection is established, the time from the when the network + transaction is requested, until the first byte of the header is received. + Only items under 10 minutes are logged. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + When a new connection is established, the time from the when the network + transaction is requested, until the first byte of the header is received. + + + + + + Replaced by Net.Transaction_Connected. + + Please list the metric's owners. Add more owner tags as needed. + + Time from the when the network transaction is requested, until the first + byte of the header is received. Only items under 10 minutes are logged. + + + + + + Replaced by Net.Transaction_Latency_b. + + Please list the metric's owners. Add more owner tags as needed. + + Time from first byte sent until last byte received by the new network stack. + Only items under 1 hour are logged. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Time from first byte sent until last byte received by the new network stack. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a network transaction is requested until last byte received + by the new network stack. + + + + + + Removed as of 11/2014. + + Please list the metric's owners. Add more owner tags as needed. + + When an existing TCP/IP connection is NOT reused, the time from when a + network transaction is requested until last byte received by the new network + stack. + + + + + + Replaced by Net.Transaction_Latency_Total_New_Connection. + + Please list the metric's owners. Add more owner tags as needed. + + When an existing TCP/IP connection is NOT reused, the time from when a + network transaction is requested until last byte received by the new network + stack. Only items under 10 minutes are logged. + + + + + + Replaced by Net.Transaction_Latency_Total. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a network transaction is requested until last byte received + by the new network stack. Only items under 10 minutes are logged. + + + + + + Replaced by Net.Transaction_Latency. + + Please list the metric's owners. Add more owner tags as needed. + + Time from first byte sent until last byte received by the new network stack. + Only items under 10 minutes are logged. + + + + + + Removed a long time ago. + + Please list the metric's owners. Add more owner tags as needed. + + Time from first byte sent until last byte received with old WinHTTP network + stack. Only items under 1 hour are logged. + + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time an already used TCP socket sat idle before being used (either for + direct or non-socks use). + + + + + + Please list the metric's owners. Add more owner tags as needed. + + The time an unused TCP socket sat idle before being used (either for direct + or non-socks use). + + + + + + Please list the metric's owners. Add more owner tags as needed. + + Time from initial ClientSocketPool::RequestSocket() call until successfully + acquiring a connected socket (either for direct or non-socks use). + + + + + + Please list the metric's owners. Add more owner tags as needed. + + The counts of the type of sockets returned by the TCP pool (either for + direct or non-socks use). + + + + + + Removed as of 10/2017. + + Please list the metric's owners. Add more owner tags as needed. + Posix error code from call to bind() UDP socket. + + + + + Removed as of 10/2017. + + Please list the metric's owners. Add more owner tags as needed. + Windows error code from call to bind() UDP socket. + + + + + Removed 6/23/2014. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + True if a URLRequest's referrer is empty or valid when set. + + + + + Removed 1/1/2018. No longer tracked. + + + Indicates the number of URLRequests that are handed out by a + URLRequestContext and are not yet destroyed. + + + + + + Removed 1/1/2018. No longer tracked. + + + Records the annotation type of the URLRequest that is handed out by a + URLRequestContext when Net.URLRequestContext.OutstandingRequests is + recorded. + + + + + + Removed 07/2017, not necessary to determine deprecation for invalid DNS + names. + + palmer@chromium.org + + True if a DNS name contains only characters for which + |net::IsValidLabelCharacter| returns true. Used to see if we can deprecate + and remove support for arbitrary bytes in DNS names. This histogram is + recorded when converting dotted DNS names into DNS query form, in + preparation for issuing a DNS request. + + + + + + Removed in March 2020. + + rajendrant@chromium.org + bengr@chromium.org + + Records the downstream data use of WebSockets. Logged on every read + operation in the WebSocket. + + + + + + Removed in March 2020. + + rajendrant@chromium.org + bengr@chromium.org + + Records the upstream data use of WebSockets. Logged on every write operation + in the WebSocket. + + + + + + Removed in June 2019. + + yhirano@chromium.org + ricea@chromium.org + + Count the number of WebSockets that accepted permessage-deflate extension + for each context take over mode. Used by the new Chromium-based WebSocket + implementation. + + + + + + Removed in June 2019. + + yhirano@chromium.org + ricea@chromium.org + + The time from a WebSocket is successfully opened until it's closed. Used to + study how WebSockets are used. + + + + + + Removed 03/2018, replaced by Net.WebSocket.HandshakeResult2. + + yhirano@chromium.org + ricea@chromium.org + + Results of WebSocket handshakes. Use this histogram as a baseline for + investigating feature usage counters. + + + + + + Removed 2020-04. + + mattreynolds@chromium.org + deviceapi-team@google.com + + The number of Wi-fi adapters on the computer. Because the histogram is + logged each time Chrome performs a Wi-fi scan, it's better to see results in + the "user count" view. + + + + + + Removed 2020-04. + + mattreynolds@chromium.org + deviceapi-team@google.com + The time that a request to Location Based Services takes. + + + + + Removed 2020-04. + + mattreynolds@chromium.org + deviceapi-team@google.com + The time that a Wi-fi scan takes. + + + + + Removed 02/2019. + + eroman@chromium.org + + Duration of time that a failing WPAD QuickCheck takes. WPAD QuickCheck does + a name lookup for "wpad" and times out quickly to fail fast when + there's no WPAD server on the network. + + + + + + Removed 02/2019. + + eroman@chromium.org + + Duration of time that a successful WPAD QuickCheck takes. WPAD QuickCheck + does a name lookup for "wpad" and times out quickly to fail fast + when there's no WPAD server on the network. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the first pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the first pipeline connectivity response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the first pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the second pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the second pipeline connectivity + response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the second pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the third pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the third pipeline connectivity response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the third pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the fourth pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the fourth pipeline connectivity + response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the fourth pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the fifth pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the fifth pipeline connectivity response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the fifth pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The network error, if any, of the stats pipeline connectivity request. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The HTTP response code, if any, of the stats pipeline connectivity response. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + The result of the stats pipeline connectivity request. + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + True if all requests received by the pipelining test server were HTTP/1.1. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + True if the non-pipelined canary request sent immediately before the + pipelining test requests succeeded. Note that if this fails, the rest of the + NetConnectivity.Pipeline.* stats are not collected. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + + The maximum depth of pipelined requests received by the test server. + + + + + + Removed 05/2014, related field trial already long expired. + + Please list the metric's owners. Add more owner tags as needed. + True if the entire pipeline connectivity trial passed. + + + + + Removed 6/25/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP at port 6121 as + rapidly as possible, just after successfully sending an UMA upload. Each + packet was numbered, as was its ACK sent back by Google. If no packets (of + the 21) were ever ACKed, then the port is assumed to be blocked, and no data + is recorded in this histogram. If the port is not blocked, then this + histogram shows the number of echo responses received from the first + + + + + + Removed 6/25/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP at port 6121 as + rapidly as possible, just after successfully sending an UMA upload. Each + packet was numbered, as was its ACK sent back by Google. This histogram + records, for each packet number, how often we received an ACK for that + packet. + + + + + + Removed 6/25/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP at port 6121 as + rapidly as possible, just after successfully sending an UMA upload. If no + packets (of the 21) were ever ACKed, then the port is assumed to be blocked. + The histogram shows if we ever got an ACK for a packet in our series of 21. + + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 100 bytes of TCP data unsuccessfully. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 1K bytes of TCP data successfully. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Status for TCP protocol for echoing + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + Status for echoing 100 bytes of TCP data. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + Status for echoing 1K bytes of TCP data. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for TCP protocol for echoing + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 100 bytes of TCP data successfully. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 1K bytes of TCP data successfully. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 100 bytes of UDP data unsuccessfully. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 1K bytes of UDP data successfully. + + + + + Removed 6/25/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome sends 4 UDP packets in a row to test to see if there is a + probabalistic dependency in packet loss for consecutive packets. We record a + bit vector of packets received, where the least significant bit is a 1 if + the first packet was received, etc. For example, if packets 1 and 3 are + received, but packets 2 and 4 are lost, then we'd record a sample of binary + 0101B, or 5. + + + + + + Removed 6/25/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome sends 6 UDP packets in a row to test to see if there is a + probabalistic dependency in packet loss for consecutive packets. We record a + bit vector of packets received, where the least significant bit is a 1 if + the first packet was received, etc. For example, if all packets other than + packet 2 and 4 are responded to, then we'd have a sample (in binary) of + 110101B, or 53. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Status for UDP protocol for echoing + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + Status for echoing 100 bytes of UDP data. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + Status for echoing 1K bytes of UDP data. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for UDP protocol for echoing + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 100 bytes of UDP data successfully. + + + + + Removed 4/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + The RTT for echoing 1k bytes of UDP data successfully. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + This histogram records how many packets (out of 6 attempted) were sent via + UDP as rapidly as possible, just after successfully sending an UMA upload. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome sends 6 UDP packets in a row to test to see if there is a + probabalistic dependency in packet loss for consecutive packets. We record a + bit vector of packets received, where the least significant bit is a 1 if + the first packet was received, etc. For example, if all packets other than + packet 2 and 4 are responded to, then we'd have a sample (in binary) of + 110101B, or 53. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP as rapidly as + possible, just after successfully sending an UMA upload. Each packet was + numbered, as was its ACK sent back by Google. If no packets (of the 21) were + ever ACKed, then the port is assumed to be blocked, and no data is recorded + in this histogram. If the port is not blocked, then this histogram shows the + number of echo responses received from the first + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP as rapidly as + possible, just after successfully sending an UMA upload. Each packet was + numbered, as was its ACK sent back by Google. This histogram records, for + each packet number, how often we received an ACK for that packet. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP as rapidly as + possible, just after successfully sending an UMA upload. If no packets (of + the 21) were ever ACKed, then the port is assumed to be blocked. The + histogram shows if we ever got an ACK for a packet in our series of 21. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + This histogram records how many packets (out of 21 attempted) were sent via + UDP as rapidly as possible, just after successfully sending an UMA upload. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, 21 packets were sent to Google via UDP on port 443 or + 6121. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 9/2012. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + This histogram records how many packets (out of 6 attempted) were sent via + UDP as rapidly as possible, just after successfully sending an UMA upload. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, a few packets were sent from Google to clients via UDP + on port 443 or 80 to perform net connectivity test. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + In this experiment, a few packets were sent from Google to clients via UDP + on port 443 or 80 to perform net connectivity test. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Next NetConnectivity5 experiment weren't started because there is an + outstading pending write. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network metric sampling the time spent using Cellular to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join a 3G/Cellular + network and configure Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that a + 3G/Cellular network is online after configuring Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that a + 3G/Cellular network is in a captive portal after configuring Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Chrome OS cellular usage API request status codes. + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network metric sampling the time spent using Ethernet to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join a wired + Ethernet network and configure Layer 3 state (typically acquire a DHCP + lease). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that an + Ethernet network is online after configuring Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that an + Ethernet network is in a captive portal after configuring Layer 3 state. + + + + + + Removed 8/2015. + + cschuet@chromium.org + + Chrome OS metric counting the number of network configurations that + contained a NSS nickname identifying a CA certificate, which triggered the + migration to PEM encoding. This metric doesn't consider whether the + migration was successful but once a migration was successful the nickname is + removed. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Chrome OS connection manager service errors seen. + + + + + Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. + + benchan@chromium.org + + Chrome OS network metric that tracks the number of DHCP option failures + encountered by Shill. This indicates that Shill is using minimal DHCP + options due to suspected MTU issues on the return path from the DHCP server + back to the client. + + + + + + Removed since Chrome OS build 10010.0.0 and superceded by + Network.Shill.Cellular.ExpiredLeaseLengthSeconds2 due to change in number of + buckets (crosreview.com/557297, crosreview.com/703679). + + benchan@chromium.org + + Chrome OS network performance metric that tracks the length of a lease for a + cellular network at the time it expired without the DHCP client being able + to renew it. + + + + + + Removed 01/2015. Migrated to Network.Shill.DarkResumeActionsTimeTaken. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes dark resume actions to complete when shill suspends. + + + + + + Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. + + benchan@chromium.org + + Chrome OS network metric that tracks the number of DHCP option failures + encountered by Shill. This indicates that Shill is using minimal DHCP + options due to suspected MTU issues on the return path from the DHCP server + back to the client. + + + + + + Removed since Chrome OS build 10010.0.0 and superceded by + Network.Shill.Ethernet.ExpiredLeaseLengthSeconds2 due to change in number of + buckets (crosreview.com/557297, crosreview.com/703679). + + benchan@chromium.org + + Chrome OS network performance metric that tracks the length of a lease for + an Ethernet network at the time it expired without the DHCP client being + able to renew it. + + + + + + Removed March 2019. + + mortonm@chromium.org + + Chrome OS metric signifying whether a system is running shill in a sandbox + or not. This is controlled through a VariationsService flag, but requires + 1-2 reboots to take affect. This metric will help us ensure that shill is + being run with sandboxing enabled/disabled at the proportion that we expect. + + + + + + Removed 03/2020. Migrated to Network.Shill.SuspendActionTimeTaken. + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes suspend actions to complete when shill suspends. Note that this was a + misspelling of the metric that is really in use by Shill. No histogram + should ever have included this entry. + + + + + + Removed 01/2015. Migrated to Network.Shill.SuspendActionsTimeTaken. + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes suspend actions to complete when shill suspends. + + + + + + Removed 10/2014. Migrated to Network.Shill.SuspendActionResult. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the number of termination + actions that successfully complete or fail when shill suspends. + + + + + + Removed 10/2014. Migrated to Network.Shill.TerminationActionResult. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the number of termination + actions that successfully complete or fail when shill terminates. + + + + + + Removed 01/2015. Migrated to Network.Shill.TerminationActionsTimeTaken. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes termination actions to complete when shill terminates. + + + + + + Removed 10/2014. Migrated to Network.Shill.SuspendActionTime. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes termination actions to complete when shill suspends. + + + + + + Removed 10/2014. Migrated to Network.Shill.TerminationActionTime. + + benchan@chromium.org + + Chrome OS network diagnostic metric sampling the time in milliseconds it + takes termination actions to complete when shill terminates. + + + + + + Removed as of 05/2019. + + kirtika@chromium.org + + Chrome OS network usage metric. The AP mode setting for each successful WiFi + connection. + + + + + + Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. + + kirtika@chromium.org + + Chrome OS network metric that tracks the number of DHCP option failures + encountered by Shill. This indicates that Shill is using minimal DHCP + options due to suspected MTU issues on the return path from the DHCP server + back to the client. + + + + + + Removed since Chrome OS build 10010.0.0 and superceded by + Network.Shill.Wifi.ExpiredLeaseLengthSeconds2 due to change in number of + buckets (crosreview.com/557297, crosreview.com/703679). + + kirtika@chromium.org + + Chrome OS network performance metric that tracks the length of a lease for a + WiFi network at the time it expired without the DHCP client being able to + renew it. + + + + + + Removed 06/2020. + + briannorris@chromium.org + cros-network-metrics@google.com + + Chrome OS metric sampling the number of different frequencies (i.e. + channels) on which a device has connected to a WiFi network. This value is + recorded every time a WiFi connection is established + (WPASupplicant::kInterfaceStateCompleted). Note that the word + "Ever" in the metric name is misleading. Chrome OS actually ages + out historical information, currently after 3 weeks. + + + + + + Wimax support has been dropped from shill since M76. + + benchan@chromium.org + + Chrome OS network metric that tracks the presence of a WiMax device in the + system. A sample is emitted once every 3 minutes. + + + + + + Removed 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected. + + benchan@chromium.org + + Chrome OS network metric that tracks the number of DHCP option failures + encountered by Shill. This indicates that Shill is using minimal DHCP + options due to suspected MTU issues on the return path from the DHCP server + back to the client. + + + + + + Removed since Chrome OS build 10010.0.0 and superceded by + Network.Shill.Wimax.ExpiredLeaseLengthSeconds2 due to change in number of + buckets (crosreview.com/557297, crosreview.com/703679). + + benchan@chromium.org + + Chrome OS network performance metric that tracks the length of a lease for a + WiMax network at the time it expired without the DHCP client being able to + renew it. + + + + + + Wimax support has been dropped from shill since M76. + + benchan@chromium.org + + Chrome OS network performance metric that tracks the length of a lease for a + WiMax network at the time it expired without the DHCP client being able to + renew it. + + + + + + Wimax support has been dropped from shill since M76. + + benchan@chromium.org + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on a WiMax network (typically acquire a DHCP lease). + + + + + + Wimax support has been dropped from shill since M76. + + benchan@chromium.org + + Chrome OS network performance metric sampling the time to initialize a WiMax + device. + + + + + + Wimax support has been dropped from shill since M76. + + benchan@chromium.org + + Chrome OS network performance metric sampling the time to determine that a + WiMax network is online after configuring Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join a 3G/Cellular + network and configure Layer 3 state. Note this metric is deprecated; see + Network.Cellular.TimeToConfig. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join a wired + Ethernet network and configure Layer 3 state (typically acquire a DHCP + lease). Note this metric is deprecated; see Network.Ethernet.TimeToConfig. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on an 802.11 wireless network (typically acquire a DHCP lease). Note + this metric is deprecated; see Network.Wifi.TimeToConfig. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network stability metric sampling the time in seconds between the + networking going online to going offline. Offline events due to device + shutdown or suspend are ignored (along with the online time before that + offline event). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join (associate + plus authenticate) an 802.11 wireless network. Note this metric is + deprecated; see Network.Wifi.TimeToJoin. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on an 802.11 wireless network (typically acquire a DHCP lease). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Network metric reporting the download speed test results run at setup time. + Recorded at least once per day. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network metric sampling the time spent using WiFi to transport + data. These data are mostly useful when summed and compared to TimeOnline + for other network technologies (e.g. WiFi vs Cellular). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time from the resume event + to the time when an 802.11 wireless network has configured its Layer 3 + state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to configure Layer 3 + state on an 802.11 wireless network (typically acquire a DHCP lease). + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to join (associate + plus authenticate) an 802.11 wireless network. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that an + 802.11 wireless network is online after configuring Layer 3 state. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS network performance metric sampling the time to determine that an + 802.11 wireless network is in a captive portal after configuring Layer 3 + state. + + + + + + Removed 08/2016 because it does not provide additional information beyond + NetworkTimeTracker.UpdateTimeFetchFailed and + NetworkTimeTracker.UpdateTimeFetchValid. + + estark@chromium.org + mab@chromium.org + + NetworkTimeTracker makes periodic queries to obtain a secure timestamp over + the network. This histogram increments whenever such a query is attempted. + + + + + + Removed as of 01/2017. Replaced by NewTabPage.ActionAndroid2. + + newt@chromium.org + + Actions taken by users from the new tab page on Android. These actions may + navigate away from the NTP (e.g. searching in the omnibox or opening a + bookmark), but can also happen without navigating away from the NTP (e.g. + opening a bookmark in a new tab). + + + + + + Removed 06/2019. No longer used. + + treib@chromium.org + + The amount of time it takes to download the animated logo. Android only. + + + + + + Removed 02/2019 with the removal of the associated service integration. + + ramyan@chromium.org + yyushkina@chromium.org + + The time it took until a request from the New Tab Page for Google Photos + albums was served. + + + + + + Removed 02/2019 with the removal of the associated service integration. + + ramyan@chromium.org + yyushkina@chromium.org + + The time it took until a request from the New Tab Page for Google Photos (in + a specific album) was served. + + + + + + Removed on M33 with the change to native NTP. + + Please list the metric's owners. Add more owner tags as needed. + + Actions taken by users on partner bookmarks (editing / renaming) on the NTP + on Android. + + + + + + Not used anymore. Removed in April 2020. + + jkrcal@chromium.org + + Android: Result of fetching a favicon for an article suggestion on the New + Tab Page. + + + + + + Not used anymore. Removed in April 2020. + + jkrcal@chromium.org + + Android: Time it takes to fetch a favicon for an article suggestion on the + New Tab Page. + + + + + + Removed in October 2017 (M64) and replaced by + NewTabPage.ContentSuggestions.BreakingNews.ReceivedMessageAction, when + adding support for push-to-refresh messages. + + vitaliii@chromium.org + + Android: Number of received messages and whether they contain pushed news. A + message contains pushed news if the payload key exists in the message. The + payload content is not checked at all (e.g. it may be empty). Recorded when + a message is received. + + + + + + Removed 04/2019. Breaking News feature removed. + + mamir@chromium.org + + Android: Action of a received message. An action can be either push-by-value + or push-to-refresh. A message with a missing or invalid action is recorded + as well. Recorded when a message is received. + + + + + + Removed 04/2019. Breaking News feature removed. + + vitaliii@chromium.org + + Android: The result of a subscription request for breaking news at the + content suggestions server. Recorded when a request finishes. Analogous to + NewTabPage.ContentSuggestions.BreakingNews.UnsubscriptionRequestStatus. + + + + + + Removed 04/2019. Breaking News feature removed. + + vitaliii@chromium.org + + Android: Time between a token validation and the last successful token + retrieval from InstanceID. Recorded when InstanceID answers our token + request for a validation either with a token or an error. If the token was + never received before the validation, the metric is not recorded. + + + + + + Removed 04/2019. Breaking News feature removed. + + vitaliii@chromium.org + + Android: The result of our inquiry to InstanceID to receive the current + token. Recorded when InstanceID replies to our inquiry for a token + (including for a validation). + + + + + + Removed 04/2019. Breaking News feature removed. + + vitaliii@chromium.org + + Android: The result of an unsubscription request for breaking news at the + content suggestions server. Recorded when a request finishes. Analogous to + NewTabPage.ContentSuggestions.BreakingNews.SubscriptionRequestStatus. + + + + + + Removed 04/2019. Breaking News feature removed. + + vitaliii@chromium.org + + Android: Whether a token validation detected an invalid token. This is + recorded only for validations where no error occured and the token was + actually retrieved. + + + + + + Removed in July 2017. This metric was replaced by CountOnNtpOpenedIfVisible. + Initially the metric was not recorded properly if any category was not + visible. This was fixed in https://codereview.chromium.org/2874213002/, + however, not visible categories still were polluting the metric (they were + recorded as showing 0 suggestions). + + treib@chromium.org + + Android: The number of suggestion cards that were available at the time an + NTP was opened. + + + + + + Removed in October 2017 (M63) and replaced by + CountOnNtpOpenedIfVisible.Articles.Prefetched.Offline2, because + underreported. UI checked whether a URL is prefetched asynchronously. As a + result, there was a race condition and this metric could be reported before + all URLs are checked. + + vitaliii@chromium.org + + Android: The number of prefetched suggestion cards that were available in + Articles category if it was visible at the time an NTP was opened and the + user was offline. Analogous to + NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible. + + + + + + Replaced by NewTabPage.ContentSuggestions.MenuOpenedScoreNormalized. + + treib@chromium.org + + Android: The relevance score of a suggestion card on the NTP whose + long-press menu was opened, analogous to + NewTabPage.ContentSuggestions.OpenedScore. + + + + + + Replaced by NewTabPage.ContentSuggestions.OpenedScoreNormalized. + + treib@chromium.org + + Android: The score of a suggestion card on the NTP that is clicked through + to the host website of the content. The recorded score is from the moment + the suggestion was fetched, it could have changed since. + + + + + + Removed in October 2017 (M63) and replaced by + Shown.Articles.Prefetched.Offline2, because underreported. UI checked + whether a URL is prefetched asynchronously. As a result, there was a race + condition and for suggestions immediately visible on the suggestions surface + this metric could be reported before their URLs are actually checked. + + vitaliii@chromium.org + + Android: The position of a prefetched suggestion card that was shown on the + NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is + a card is considered shown when at least 2/3 of its height is visible on the + screen. For each card, at most one impression is recorded per NTP instance. + We track the position the card had in the list when it was first seen by the + user. This tracked position can be different from the position observed by + the user, e.g. when the user dismissed some suggestions from the list or + requested more that got inserted in the middle of the feed. + + + + + + Replaced by NewTabPage.ContentSuggestions.ShownScoreNormalized. + + treib@chromium.org + + Android: The score of a suggestion card that was shown on the NTP. A card is + considered shown when at least 2/3 of its height is visible on the screen. + For each card, at most one impression is recorded per NTP instance. + + + + + + Replaced by NewTabPage.ContentSuggestions.TimeSinceSuggestionFetched. + + markusheintz@chromium.org + + Android: The time since the last successful background fetch of remote + content suggestions. Recorded when the user looks at content suggestions on + the NTP. + + + + + + Removed as of July 2017, in favor of + NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and + NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger. + + jkrcal@chromium.org + + Android: The time since the last fetch, recorded upon the first soft fetch + trigger. The first soft trigger does not necessarily cause a fetch (if it + comes before the end of the respective scheduling interval). This metric is + recorded at most once after each fetch (and additionaly at most once after + each startup of Chrome before the next fetch). This is used to understand + how changing scheduling intervals will impact traffic of background fetches. + + + + + + Replaced by NewTabPage.ContentSuggestions.UIUpdateResult2 in January 2017. + + jkrcal@chromium.org + + Android: The result of updating the list of content suggestions in the UI. + + + + + + Not used anymore. Removed in April 2020. + + jkrcal@chromium.org + + Android: The result of updating the list of content suggestions in one UI + section. + + + + + + Not used anymore. Removed in April 2020. + + jkrcal@chromium.org + + Android: The number of content suggestions that have been seen by the user + in the UI section before the section was successfully updated. The seen + suggestions were not removed in the update so that we do not change visible + parts of the UI. This histogram is only recorded when the UIUpdateResult2 is + "Success (some suggestions replaced)". + + + + + + Removed 2019-08. + + dbeam@chromium.org + yyushkina@chromium.org + + The availability of New Tab Page background customization features on + Desktop, based on feature flags or other configuration settings; logged per + NTP load. + + + + + + Removed 2019-08. + + dbeam@chromium.org + yyushkina@chromium.org + + The availability of New Tab Page shortcut customization features on Desktop, + based on feature flags or other configuration settings; logged per NTP load. + + + + + + Removed 2016-02. + + Please list the metric's owners. Add more owner tags as needed. + The default pane when the NTP is first opened. + + + + + Deprecated as of 08/2020. + + shaktisahu@chromium.org + clank-downloads@google.com + + Android: Records user actions on the explore offline card on the NTP. + + + + + + Removed in favor of ContentSuggestions.Feed.Image.FetchResult. + + wylieb@chromium.org + + Android: Represents success/failure of Feed image loading. Recorded upon + each individual image retrieved from the feed_image_cache. + + + + + + Removed in favor of ContentSuggestions.Feed.Image.LoadFromCacheTime. + + wylieb@chromium.org + + Android: The time it takes for Feed to load an image from the cache. + + + + + + Removed in favor of ContentSuggestions.Feed.Image.LoadFromNetworkTime. + + wylieb@chromium.org + + Android: The time it takes for Feed to load an image from the network. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Histogram of the time, in milliseconds, users have the cursor over a most + visited thumbnail before clicking. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Histogram of the time, in milliseconds, users have the cursor over a most + visited thumbnail before moving it away from the thumbnail without clicking. + + + + + + Removed 2017-04, replaced by NewTabPage.TileType and + NewTabPage.SuggestionsImpression.IconsColor. + + newt@chromium.org + + The number of most visited tiles on the new tab page that are displayed + using a fallback color (as opposed to having an icon, or simply being gray). + Android only. + + + + + + Removed 2017-04, replaced by NewTabPage.TileType and + NewTabPage.SuggestionsImpression.IconsGray. + + newt@chromium.org + + The number of most visited tiles on the new tab page that are displayed as + gray (as opposed to having an icon, or a fallback color). Android only. + + + + + + Removed 2017-04, replaced by NewTabPage.TileType and + NewTabPage.SuggestionsImpression.IconsReal. + + newt@chromium.org + + The number of most visited tiles on the new tab page that are displayed with + the site's icon (as opposed using a fallback color or just gray). Android + only. + + + + + + Removed 2017-05 (and not recorded for some time before that). + + knn@chromium.org + + Android: Whether an attempt to download the image for an interest was + successful. + + + + + + Removed 2017-05 (and not recorded for some time before that). + + knn@chromium.org + + Android: Whether an attempt to fetch the interests for a user was + successful. + + + + + + Removed 2017-05 (and not recorded for some time before that). + + knn@chromium.org + + Android: The number of interests fetched for a user to display on the NTP. + + + + + + Removed 2018-04 with full launch of NTP condensed layout. + + peconn@chromium.org + + Android: A histogram detailing how the NewTabPageLayout is laid out on the + device (eg, whether it fits fully above the fold or not). This is logged + once per NewTabPageLayout creation (so once per NTP). + + + + + + Removed 2020-06 because it was no longer being monitored. + + mvanouwerkerk@chromium.org + + Android: the type of load for the NTP, such as cold or warm start. It's a + warm start if the native library is already loaded and initialized at the + time the activity is created. This might happen if for example a service was + already running. + + + + + + Removed 2017-08 because it was only recorded for cached logos. Replaced by + LogoShownTime2. + + treib@chromium.org + + The amount of time between opening an NTP and the logo appearing. Only + recorded when there is a logo, and only recorded once per NTP. Android only. + + + + + + Removed on M33 with the change to native NTP. + + Please list the metric's owners. Add more owner tags as needed. + + Android: Tallies counts for how the user interacted with the NTP promo page. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + justincohen@chromium.org + newt@chromium.org + + Action taken by the user on the Most Visited NTP pane. If the user switches + panes during this use of the NTP, this action is sometimes not recorded. Ask + mpearson@ for details. + + + + + + Removed 2016-05. + + treib@chromium.org + + The schemes of URLs of most visited thumbnails that the user clicked on. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + justincohen@chromium.org + newt@chromium.org + + Records anomalous events for the Most Visited Tile Placement experiment, + where it is unable to operate as expected. These are recorded during New Tab + Page load time, once for every NTP. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + The number of screenshots that were cached for the non-visible but ranked + suggestions on the Suggested NTP pane. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Given that the user has typed a URL, and given that that specific URL was + ranked but not visible on the Suggested pane of the NTP, this is the rank + that the Suggested pane had for that URL. + + + + + + Removed 2016-07. + + + The number of tiles for which we relied on external tiles as a fallback + because a local screenshot was not available to be used as a thumbnail. + External tiles are those for which the visuals are handled by the page + itself, not by the iframe. Recorded before reloading the suggestions, + navigating to a URL, switching tabs, changing the active window, or closing + the tab/shutting down Chrome. + + + + + + Removed 2016-07. + + + The number of external tiles that are displayed on the NTP. External tiles + are those for which the visuals are handled by the page itself, not by the + iframe. Recorded before reloading the suggestions, navigating to a URL, + switching tabs, changing the active window or closing the tab/shutting down + Chrome. + + + + + + Removed 2016-07. + + + The number of tiles for which we displayed a gray tile with the domain name + as a fallback because a local screenshot was not available to be used as a + thumbnail. Recorded before reloading the suggestions, navigating to a URL, + switching tabs, changing the active window or closing the tab/shutting down + Chrome. + + + + + + Removed 2016-07. + + + The number of tiles for which no thumbnail was specified, but a domain was + so we displayed a gray tile with the domain name in it. Recorded before + reloading the suggestions, navigating to a URL, switching tabs, changing the + active window or closing the tab/shutting down Chrome. + + + + + + Removed 2016-07. + + + The total number of times the user hovered the mouse over Most Visited tile + or title elements before changing focus away from the NTP, be it by + navigating to a URL, switching tabs, changing the active window or closing + the tab/shutting down Chrome. + + + + + + Removed 01/2014. Replaced by NewTabPage.NumberOfThumbnailTiles. + + Please list the metric's owners. Add more owner tags as needed. + + The number of tiles for which we attempted to use a local screenshot as a + thumbnail. Recorded before reloading the suggestions, navigating to a URL, + switching tabs, changing the active window or closing the tab/shutting down + Chrome. + + + + + + Removed 2016-07. + + + The number of thumbnails for which a local screenshot was not available so + we were not able to display them on the Most Visited section of the NTP. + Recorded before reloading the suggestions, navigating to a URL, switching + tabs, changing the active window or closing the tab/shutting down Chrome. + + + + + + Removed 2016-07. + + + The number of tiles for which we attempted to use a local screenshot as a + thumbnail. Recorded before reloading the suggestions, navigating to a URL, + switching tabs, changing the active window or closing the tab/shutting down + Chrome. + + + + + + Removed in M58. + + dewittj@chromium.org + + The amount of time spent waiting for the offline page model to return which + New Tab Page URLs are available offline. + + + + + + Removed 05/2015. Feature was removed. + + Please list the metric's owners. Add more owner tags as needed. + + Histogram for usage of the menu on the NTP that allows the user to access + tabs from other devices. + + + + + + Removed 2016-02. + + Please list the metric's owners. Add more owner tags as needed. + + The pane that had been previously selected when the user switches panes in + the NTP. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + Histogram for NTP bubble promo activity. + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + Histogram for NTP notification promo activity. + + + + + Removed 2018-03 as it doesn't correctly capture all request states. + + kmilka@chromium.org + ramyan@chromium.org + + The time it took until a request from the New Tab page for the middle slot + promo script was served. Recorded only on the local NTP. + + + + + + Removed March 2020. + + pkotwicz@chromium.org + treib@chromium.org + + Records the amount of time that the "Recent Tabs" page is visible + and Chrome is in the foreground on Android. The metric is recorded whenever + the "Recent Tabs" page moves out of the foreground. The metric is + recorded when the "Recent Tabs" page is closed, when the user + switches from the "Recent Tabs" page to a different tab and when + Chrome is backgrounded. + + + + + + Removed February 2017. + + mvanouwerkerk@chromium.org + + The time until the search box became available on the NTP in a cold start. + It's a cold start if the native library is not already loaded and + initialized at the time the activity is created. Only measured on Android. + + + + + + Removed February 2017. + + mvanouwerkerk@chromium.org + + The time until the search box became available on the NTP in a warm start. + It's a warm start if the native library is already loaded and initialized at + the time the activity is created. This might happen if for example a service + was already running. Only measured on Android. + + + + + + Removed 2019-03 as it doesn't correctly capture all request states. + + kmilka@chromium.org + ramyan@chromium.org + + The time it took until a request from the New Tab page for the search + suggestions script was served. Recorded only on the local NTP. + + + + + + Removed 2019-03 as it grouped together requests that returned no suggestions + with those that failed completely, which is misleading. + + kmilka@chromium.org + ramyan@chromium.org + + Whether a request was made for search suggestions on NTP load; and if a + request was not made, the reason why. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + TBD. + + + + + Removed 2016-02. + + Please list the metric's owners. Add more owner tags as needed. + The pane selected when the user switches panes in the NTP. + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Histogram for user clicks of the Recently Closed items. The value is the + recency of the entry being restored (0 is most recent). + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Histogram to track how many times a user switched pages in a single NTP + session. + + + + + + Replaced by NewTabPage.ContentSuggestions.Opened. + + knn@chromium.org + + Android: The position of the snippets card on the NTP, that is clicked + through to the host website of the content. We track the position the + snippet had in the list when NTP was loaded. This tracked position is thus + different from the position observed by the user whenever before scrolling + down to the given snippet, the user discards some snippets in the top of the + list. + + + + + + Replaced by NewTabPage.ContentSuggestions.OpenedAge. + + jkrcal@chromium.org + + Android: The age of the snippets card on the NTP, that is clicked through to + the host website of the content. The age is measured from the moment the + content has been published. In each "_x_y" suffix of the + histogram, only snippets on positions \gt;=x and \lt;=y are tracked. We + track the position the snippet had in the list when NTP was loaded. This + tracked position is thus different from the position observed by the user + whenever before scrolling down to the given snippet, the user discards some + snippets in the top of the list. + + + + + + Removed as of 6/2016 + + jkrcal@chromium.org + + Android: The score of the snippets card on the NTP, that is clicked through + to the host website of the content. The recorded score is from the moment + the snippet was fetched, it could have changed since. In each "_x" + suffix of the histogram, only snippets on positions \lt;=x are tracked. We + track the position the snippet had in the list when NTP was loaded. This + tracked position is thus different from the position observed by the user + whenever before scrolling down to the given snippet, the user discards some + snippets in the top of the list. + + + + + + Replaced by NewTabPage.ContentSuggestions.OpenedScore. + + jkrcal@chromium.org + + Android: The score of the snippets card on the NTP, that is clicked through + to the host website of the content. The recorded score is from the moment + the snippet was fetched, it could have changed since. In each "_x" + suffix of the histogram, only snippets on positions \lt;=x are tracked. We + track the position the snippet had in the list when NTP was loaded. This + tracked position is thus different from the position observed by the user + whenever before scrolling down to the given snippet, the user discards some + snippets in the top of the list. In contrast to CardClickedScore, this + histogram has a proper maximal value of 100 000. + + + + + + Removed as of 4/2016 + + knn@chromium.org + + Android: The position of the snippets card on the NTP, that is expanded to + reveal more content. + + + + + + Removed as of 4/2016 + + knn@chromium.org + + Android: The position of the snippets card on the NTP, for which the + expanded content was minimized/hidden. + + + + + + Replaced by NewTabPage.ContentSuggestions.MenuOpened. + + peconn@chromium.org + + Android: The position of a snippet card when it is long pressed, analagous + to NewTabPage.Snippets.CardClicked. + + + + + + Replaced by NewTabPage.ContentSuggestions.MenuOpenedAge. + + peconn@chromium.org + + Android: The time difference between when a snippet card is long pressed and + when its content was published. Analagous to + NewTabPage.Snippets.CardClickedAge. + + + + + + Replaced by NewTabPage.ContentSuggestions.MenuOpenedScore. + + peconn@chromium.org + + Android: The relevance score of an interest card that is long pressed, + analagous to NewTabPage.Snippets.CardClickedScoreNew. + + + + + + Replaced by NewTabPage.ContentSuggestions.Shown. + + knn@chromium.org + + Android: The position of the snippets card that is shown on the NTP. Each + snippet (its position) is recorded whenever at least 2/3 of its height + becomes visible by scrolling through the NTP. Each snippet is recorded at + most once for a given instance of NTP and a given data set of snippets that + is shown. We track the position the snippet had in the list when NTP was + loaded. This tracked position is thus different from the position observed + by the user whenever before scrolling down to the given snippet, the user + discards some snippets in the top of the list. Previously (in the code + before 2016/05/27), this histogram was recorded each time a snippet became + visible (e.g. by scrolling up and down) at least by 1px; the first snippet + was thus recorded even without scrolling down. + + + + + + Replaced by NewTabPage.ContentSuggestions.ShownAge. + + jkrcal@chromium.org + + Android: The age of the snippets card that is shown on the NTP. Each snippet + (its age) is recorded whenever at least 2/3 of its height becomes visible by + scrolling through the NTP. Each snippet is recorded at most once for a given + instance of NTP and a given data set of snippets that is shown. The age is + measured from the moment the content has been published. In each + "_x_y" suffix of the histogram, only snippets on positions \gt;=x + and \lt;=y are tracked. By this, we mean the position the snippet had in the + list when NTP was loaded. This tracked position is thus different from the + position observed by the user whenever before scrolling down to the given + snippet, the user discards some snippets in the top of the list. + + + + + + Removed as of 6/2016 + + jkrcal@chromium.org + + Android: The score of the snippets card that is shown on the NTP. Each + snippet (its score) is recorded whenever at least 2/3 of its height becomes + visible by scrolling through the NTP. Each snippet is recorded at most once + for a given instance of NTP and a given data set of snippets that is shown. + The recorded score is from the moment the snippet was fetched, it could have + changed since. In each "_x" suffix of the histogram, only snippets + on positions \lt;=x are tracked. By this, we mean the position the snippet + had in the list when NTP was loaded. This tracked position is thus different + from the position observed by the user whenever before scrolling down to the + given snippet, the user discards some snippets in the top of the list. + + + + + + Replaced by NewTabPage.ContentSuggestions.ShownScore. + + jkrcal@chromium.org + + Android: The score of the snippets card that is shown on the NTP. Each + snippet (its score) is recorded whenever at least 2/3 of its height becomes + visible by scrolling through the NTP. Each snippet is recorded at most once + for a given instance of NTP and a given data set of snippets that is shown. + The recorded score is from the moment the snippet was fetched, it could have + changed since. In each "_x" suffix of the histogram, only snippets + on positions \lt;=x are tracked. By this, we mean the position the snippet + had in the list when NTP was loaded. This tracked position is thus different + from the position observed by the user whenever before scrolling down to the + given snippet, the user discards some snippets in the top of the list. In + contrast to CardShownScore, this histogram has a proper maximal value of 100 + 000. + + + + + + Removed 2016-10. + + knn@chromium.org + + Android: A histogram giving an overall summary of important events like + impressions, scroll events, clicks etc. + + + + + + Removed 2016-10. + + mastiz@chromium.org + + Android: The number of snippet articles available to the user in the UI, + logged when the user scrolls below the fold (at max once per NTP load). + + + + + + Replaced by NewTabPage.ContentSuggestions.OpenDisposition. + + peconn@chromium.org + + Android: A histogram detailing how the articles linked from snippets are + opened (eg, plain click, open in new tab, open in incognito). + + + + + + Replaced by NewTabPage.ContentSuggestions.VisitDuration. + + mastiz@chromium.org + + Android: Time spent reading the page linked by an opened (clicked) snippet + card. Exit conditions include the tab not being in the foreground or + starting a new navigation. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Histogram for user clicks of the suggested site thumbnails. The value is + equal to the index of the thumbnail. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + Action taken by the user on the Suggested Sites NTP pane. + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + Time to load the Suggested Sites NTP pane, in milliseconds. + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + Time spent on the Suggested Sites NTP pane, in seconds. + + + + + Removed 2016-07. + + + Indicate, for each impression of the New Tab Page, whether the suggestions + were obtained from the client or server. Recorded before changing focus away + from the NTP, be it by navigating to a URL, switching tabs, changing the + active window or closing the tab/shutting down Chrome. + + + + + + Removed 01/2014. Replaced by NewTabPage.NumberOfThumbnailAttempts and + NewTabPage.NumberOfThumbnailErrors. + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of errors per attempts to load image thumbnails on the New + Tab Page. When an error occurs, a grey tile is shown instead of a thumbnail + image. We measure the rate instead of the number of errors because multiple + attempts are made to load images at different times during the NTP's + lifetime. Each NTP session's error rate is logged after the user navigates + to a new URL from that NTP. + + + + + + Removed 01/2014. Replaced by NewTabPage.NumberOfGrayTileFallbacks and + NewTabPage.NumberOfExternalFallbacks. + + Please list the metric's owners. Add more owner tags as needed. + + The percentage of times most visited tiles use the fallback thumbnail. Only + requests that actually specify a fallback thumbnail are considered here. We + measure the rate instead of the number of errors because multiple attempts + are made to load thumbnails at different times during the NTP's lifetime. + Each NTP session's error rate is logged after the user navigates to a new + URL from that NTP. + + + + + + Removed 07/2019 because the histogram was unused and close to expiration. + + jkrcal@chromium.org + + Mobile only. The result of fetching a favicon for a tile on the New Tab + Page. This is recorded for each gray MostVisited tile on the New Tab Page + once per impression of the tile. + + + + + + Removed 07/2019 because the histogram was unused and close to expiration. + + jkrcal@chromium.org + + Mobile only. The result of fetching a favicon for a tile on the New Tab + Page. This is recorded for each gray PopularSites tile on the New Tab Page + once per updating the set of tiles (notably upon each NTP impression). + + + + + + Removed 06/2017. Replaced by NewTabPage.TileFaviconFetchStatus.Server. + + jkrcal@chromium.org + + Mobile only. The result of fetching a favicon for a tile on the New Tab + Page. This is recorded for each gray MostVisited tile on the New Tab Page + once per lifetime of Chrome (there as an in-memory cache of failed + requests). + + + + + + Removed 06/2019. No longer used. + + treib@chromium.org + + Histogram of the time, in milliseconds since navigation start, it took for + the NTP most visited iframe to receive the data for all of its tiles. This + does not include actually loading the DOM elements for the tiles, in + particular the thumbnail images; see NewTabPage.LoadTime for that. + + + + + + Removed 01/2019, replaced by NewTabPage.TimeToFirstDraw2 when a bug in how + this was calculated was fixed. + + skym@chromium.org + twellington@chromium.org + + The time from when a new tab page is created until the first pre-draw call + on the main UI containing the search provider logo (if available), fake + search box, most visited tiles, etc. More specifically, this is the time + between NewTabPage's constructor and the first pre-draw pass on + NewTabPageLayout. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + The number of screenshots that were cached for the visible suggestions on + the Suggested NTP pane. + + + + + + Removed 2016-02 (and not recorded for some time before that). + + Please list the metric's owners. Add more owner tags as needed. + + Given that the user has typed a URL, and given that that specific URL was + visible on the Suggested pane of the NTP, this is the rank that the + Suggested pane had for that URL. + + + + + + Replaced by Notifications.AuthorDataSize in February 2016. + + peter@chromium.org + + The size, in kilobytes, of the author-provided data associated with a Web + Notification. Recorded when a persistent Web Notification is being shown by + the developer. + + + + + + Removed July 2015. No longer tracked since M42. + + peter@chromium.org + + Records if the requesting and embedding origins are different when + requesting permission to display Web Notifications. + + + + + + Removed October 2017 (fullscreen notifications feature enabled by default). + + bmalcolm@chromium.org + + Counts the number of times a notification was shown for the various types of + sources. The suffix distinguishes between the window state of the app or + webpage that sent the notification. This will be used to determine whether a + legacy mode is required when we allow apps or webpages to display + notifications over fullscreen content in the future. + + + + + + Removed in July 2020 as the metrics are not needed anymore, and + documentation has been amended as a result of this collection. + + dewittj@chromium.org + peter@chromium.org + + The number of action buttons the developer provided for a notification + created using the extensions notification API. Logged when creating the + notification. + + + + + + Removed in June 2019 because this was measuring risk for a feature that has + now been implemented and shipped. + + peter@chromium.org + + The length, in characters, of the id given to an extension notification. + These can be automatically generated, in which case they will be either 36 + bytes (GUID) or 16 bytes (random data) in length, or provided by the + developer. Measured when the notification is being displayed through the + chrome.notifications.create() extension API. + + + + + + Removed in July 2020 as the metrics are not needed anymore as platforms have + moved to native notifications, for which these metrics were used. + + dewittj@chromium.org + peter@chromium.org + + The type of a notification created using the extensions notification API. + Logged when creating the notification. + + + + + + Removed Nov 2019 because the histogram data was not being used. + + knollr@chromium.org + peter@chromium.org + + Whether a click on a notification header caused it to collapse, expand or + had no effect at all. Logged when clicking on the notification header. + + + + + + Removed Nov 2016 in favor of Notifications.LoadFileSize.* + + peter@chromium.org + The number of bytes loaded for a Web Notification icon. + + + + + Removed Nov 2016 in favor of Notifications.LoadFailTime.* + + peter@chromium.org + + The number of milliseconds it took to fail loading an icon for a Web + Notification. + + + + + + Removed Nov 2016 in favor of Notifications.LoadFinishTime.* + + peter@chromium.org + + The number of milliseconds it took to finish successfully loading an icon + for a Web Notification. + + + + + + Removed Nov 2016 in favor of Notifications.LoadScaleDownTime.* + + peter@chromium.org + + The number of milliseconds it took to scale down an icon for a Web + Notification. + + + + + + Removed in June 2019. + + + + peter@chromium.org + + The number of milliseconds it took to fail loading an icon/image for a Web + Notification. + + + + + + Removed in June 2019. + + + + peter@chromium.org + + The number of bytes loaded for a Web Notification icon/image. + + + + + + Removed in June 2019. + + + + peter@chromium.org + + The number of milliseconds it took to finish successfully loading an + icon/image for a Web Notification. + + + + + + Removed in June 2019. + + + + peter@chromium.org + + The number of milliseconds it took to scale down an icon/image for a Web + Notification. + + + + + + Removed 06/2018. Replaced by NotificationActivatorPrimaryStatus and + NotificationActivatorSecondaryStatus. + + chengx@chromium.org + + The execute status of NotificationActivator::Activate. Logged whenever a + notification_helper process is launched by Windows. + + + + + + Removed 01/2016, no longer used. + + peter@chromium.org + deepak.m1@samsung.com + + Recorded when the data associated with a persistent Web Notification gets + deleted. The value will be true if data deletion succeeded, and false if + there was an error. + + + + + + Removed July 2020 as the Origin Trial is ramping down. + + knollr@chromium.org + peter@chromium.org + + Indicates if the notificaiton has a show trigger. This is recorded before a + notification is written to the database if the notification triggers feature + is enabled. + + + + + + Removed July 2020 as the Origin Trial is ramping down. + + knollr@chromium.org + peter@chromium.org + + The specified delay until the notification is displayed. This is recorded + before writing a notification with a valid show trigger to the database. + + + + + + Obsolete 10/2018 as we no long record this metric. + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + Amount of time taken to destroy a NotificationImageRetainer object when the + image directory is valid. + + + + + + Obsolete 10/2018 as we no long record this metric. + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + Amount of time taken to initialize the image retainer directory. + + + + + + Obsolete 06/2020 as we no long record this metric. + + chengx@chromium.org + peter@chromium.org + + The status of OnDismissed requests in NotificationPlatformBridgeWin (Windows + only). Logged whenever a dismiss event is handled. + + + + + + Replaced with Notifications.Windows.SetReadyCallbackStatus2 which is not + skewed. + + finnur@chromium.org + peter@chromium.org + + The status of SetReadyCallback requests in NotificationPlatformBridgeWin + (Windows only). Logged once at startup. + + + + + + Removed 06/2018. Replaced with Notifications.Windows.StartMenuShortcutStatus + where typo is fixed. + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + Used to indicate the status of start menu shortcut (Windows only). Logged + whenever a notification display attempt is made. + + + + + + Removed 12/2018 as this is no longer needed. + + chengx@chromium.org + finnur@chromium.org + peter@chromium.org + + Used to indicate the reason why toast activator CLSID in shortcut is + different from the one retrieved from the installer (Windows only). Logged + whenever this mismatch is detected during a notification display attempt. + + + + + + Removed 05/2018 as this is no longer needed. + + chengx@chromium.org + peter@chromium.org + + Used to indicate the code path where the user profile manager shows up + during startup (Windows only). Logged whenever a notification event is being + handled. + + + + + + Obsoleted in Jan 2019 + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated downstream throughput (in + kilobits per second) and the observed downstream throughput (in kilobits per + second). Downstream throughput estimated by the network quality estimator at + the time of navigation start is compared with the downstream throughput + observed during the specified time interval following the start of the + navigation. + + + + + + Obsoleted in Jan 2019 + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated effective connection type and + the observed effective connection type. Effective connection type is + estimated by the network quality estimator at the time of navigation start + is compared with the effective connection type observed during the specified + time interval following the start of the navigation. + + + + + + Obsoleted in Jan 2019 + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated HTTP RTT and the observed HTTP + RTT. HTTP RTT estimated by the network quality estimator at the time of + navigation start is compared with the HTTP RTT observed during the specified + time interval following the start of the navigation. + + + + + + Obsoleted in Jan 2019 + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated transport RTT and the observed + transport RTT. Transport RTT estimated by the network quality estimator at + the time of navigation start is compared with the transport RTT observed + during the specified time interval following the start of the navigation. + + + + + + Obsoleted in October 2018 + + devdeepray@chromium.org + tbansal@chromium.org + + The value of the downstream throughput used to compute the bandwidth delay + product. The 80th percentile throughput observation is used to calculate the + bandwidth delay product. This gets recorded everytime the BDP is computed. + + + + + + Obsoleted in October 2018 + + devdeepray@chromium.org + tbansal@chromium.org + + The value of the TransportRTT used to compute the bandwidth delay product. + The 20th percentile TransportRTT observation is used to calculate the + bandwidth delay product. This gets recorded everytime the BDP is computed. + + + + + + Obsoleted in October 2018 + + devdeepray@chromium.org + tbansal@chromium.org + + An estimate of the bandwidth delay product which is computed on main-frame + requests. It is calculated using the 80th percentile throughput and 20th + percentile TransportRTT values whenever |ComputeEffectiveConnectionType| is + called and the throughput and TransportRTT estimates are available. + + + + + + Obsoleted April 2020. + + tbansal@chromium.org + + Cellular signal strength level reported by the device at the time of ECT + computation. Recorded only on cellular networks, and only when the value is + available. The value ranges between 0 and 4 (both inclusive). + + + + + + Obsoleted. + + tbansal@chromium.org + bengr@chromium.org + + Difference between the minimum and the maximum received signal strength + since the last connection change event. Recorded only on cellular + connections on Android platform when the cellular signal strength was + available. Recorded right before a connection change event. + + + + + + Replaced by NQE.CellularSignalStrength.LevelAvailable in June 2017. + + tbansal@chromium.org + bengr@chromium.org + + Whether the signal strength for the cellular network was available or not. + Recorded right before a connection change event. Recorded only on cellular + connections on Android platform. + + + + + + Replaced by NQE.CellularSignalStrength.LevelDifference in June 2017. + + tbansal@chromium.org + bengr@chromium.org + + Difference between the minimum and the maximum received signal strength + since the last connection change event. Recorded only on cellular + connections on Android platform when the cellular signal strength was + available. Recorded right before a connection change event. + + + + + + Obsoleted in Apr 2020. + + jfwang@chromium.org + tbansal@chromium.org + + Records the count of in-flight requests causing the peak queueing delay + within the current ongoing measurement period. These samples are bucketized + into 10 peak queueing delay levels. This is emitted at the end of the + current measurement period. + + + + + + Obsoleted in April 2020. + + jfwang@google.com + tbansal@chromium.org + + Records the score that evaluates the mapping between the count of in-flight + requests to the peak observed queueing delay. The score is the percentage of + total samples that follow the rule 'the more in-flight requests, the higher + peak queueing delay' when a new peak queueing delay mapping sample is + acquired. This is emitted at the end of the current measurement period and + only when there are at least 10 cached mapping samples. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + + This metric is recorded when the network quality change notification is + received by content and before the network quality change is notified to the + renderers. Records true if the notified network quality change is + meaningfully different from the last network quality notified to the + renderers. + + + + + + Obsoleted in December 2017. + + tbansal@chromium.org + bengr@chromium.org + + Records estimated network quality (estimated RTT, estimated downlink + bandwidth), resource load size, and the resource load time in a single UMA + sample. This metric is recorded randomly when a resource load finishes. Each + sample in this sparse histogram consists of multiple metrics (each occupying + few bits in the sample). The data in the histogram would be analyzed using + custom scripts. A sample is recorded only when the resource size is between + 0 Kilobits (inclusive) and 128 Kilobits (exclusive). + + + + + + Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. + + bengr@chromium.org + tbansal@chromium.org + + Difference between the actual RTT observation and the estimated RTT. This + metric is recorded on every request when the actual observation is higher + than the estimated value. + + + + + + Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. + + bengr@chromium.org + tbansal@chromium.org + + Difference between the estimated RTT and the actual RTT observation. This + metric is recorded on every request when the estimated value is higher than + the actual observation. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + bengr@chromium.org + + This histogram records whether the estimate of the network quality metric + was available or not. Recorded at every main frame request. + + + + + + Obsoleted in February 2018. + + bengr@chromium.org + tbansal@chromium.org + + Records the estimate of the downlink bandwidth (in Kbps) provided by the + external estimate provided. Recorded every time the external estimate + provider provides a valid downlink bandwidth estimate to the network quality + estimator. + + + + + + Obsoleted in February 2018. + + bengr@chromium.org + tbansal@chromium.org + + Records the estimate of the RTT provided by the external estimate provided. + Recorded every time the external estimate provider provides a valid RTT + estimate to the network quality estimator. + + + + + + Obsoleted in February 2018. + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the HTTP RTT estimated by the external + estimate provider and the observed HTTP RTT. The HTTP RTT estimated by the + external estimate provider at the time of navigation start is compared with + the HTTP RTT observed during the specified time interval following the start + of the navigation. + + + + + + Obsoleted in February 2018. + + bengr@chromium.org + tbansal@chromium.org + + Records the interaction (availability and query count) of Network Quality + Estimator with external estimates provider. Logged on network change events, + everytime external estimate provider is queried for an updated estimate, and + when it proactively notifies that an updated estimate is available. + + + + + + Obsoleted in August 2017 + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the fastest round-trip-time, before a connectivity change + is detected. + + This metric is recorded when a connectivity change is detected. This will + miss data from users whose connection type never changes and will be biased + to users whose connection type changes frequently. + + + + + + Obsoleted in April 2020. + + tbansal@chromium.org + bengr@chromium.org + + Number of Kbps observations indexed by the source of the observation. + Recorded by the network quality estimator every time a new observation is + made or synthesized. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + bengr@chromium.org + + Downstream throughput observation received or synthesized by network quality + estimator. Observations from different sources are recorded in separate + histograms. + + + + + + Obsoleted in M84. + + tbansal@chromium.org + bengr@chromium.org + + Effective connection type estimated by network quality estimator. Suffixed + with the connection type reported by the operating system. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted in M81. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the downstream peak throughput at different percentiles. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted in M84. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the URLRequest layer at + different percentiles. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted in M81. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the transport layer at + different percentiles. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted in August 2017 + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of downstream peak throughput, before a connectivity change + is detected. + + This metric is recorded when a connectivity change is detected. This will + miss data from users whose connection type never changes and will be biased + to users whose connection type changes frequently. + + + + + + Obsoleted in Apr 2020. + + tbansal@chromium.org + ryansturm@chromium.org + + Records the duration of the time period for which there was at least one + peer to peer active connection. Recorded when the count of peer to peer + connections drop from a non-zero value to a zero value. + + + + + + Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics. + + bengr@chromium.org + tbansal@chromium.org + + Ratio of the estimated RTT to the actual RTT observation multiplied by 100. + + + + + + Obsoleted in M-77. + + tbansal@chromium.org + bengr@chromium.org + + Count of the number of times renderers were notified of the changes in the + network quality estimator. This metric makes sense to compare in frequency + relative to other events like the number of page loads or the number of + renderers seen. It is expected that we will see at least 1 notification per + renderer (on average), and less than 100. + + + + + + Removed 01/2018. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the URLRequest layer at + different percentiles. + + This metric is recorded immediately after a connectivity change is detected. + The metric name is suffixed with the connection type before the connectivity + change was detected. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + HTTP RTT observation received by the network quality estimator. Recorded + when the request is detected as hanging. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + HTTP RTT observation received by the network quality estimator. Recorded at + the beginning of a request if the request is detected as not hanging because + the observed HTTP RTT was comparable to the end to end RTT estimate. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + HTTP RTT observation received by the network quality estimator. Recorded + when the request is detected as not hanging because it was comparable to the + HTTP RTT estimate. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + HTTP RTT observation received by the network quality estimator. Recorded + when the request is detected as not hanging because the RTT value was lower + than the minimum threshold RTT needed to be categorized as a hanging + request. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + HTTP RTT observation received by the network quality estimator. Recorded + when the request is detected as not hanging because it was comparable to the + transport RTT estimate. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + bengr@chromium.org + + RTT observation received or synthesized by network quality estimator. + Observations from different sources are recorded in separate histograms. + + + + + + Replaced in May 2016 by NQE.MainFrame.RTT.* metrics. + + bengr@chromium.org + tbansal@chromium.org + + RTT observations at the URLRequest layer made by network quality estimator, + recorded on every request. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + Count of the requests that were marked as hanging by the heuristic algorithm + in the throughput analyzer in the network quality estimator. A sample is + recorded everytime the heuristic algorithm is run. + + + + + + Obsoleted in Feb 2019. + + tbansal@chromium.org + + Count of the requests that were not marked as hanging by the heuristic + algorithm in the throughput analyzer in the network quality estimator. A + sample is recorded everytime the heuristic algorithm is run. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + + Throughput observation made by network quality estimator, and eventually + discarded because the window (over which the througput was computed) was + detected as hanging. + + + + + + Obsoleted in M81. + + tbansal@chromium.org + + Throughput observation made by network quality estimator, and used when the + window (over which the througput was computed) was detected as not hanging. + + + + + + Removed 01/2018. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the transport layer at + different percentiles. + + This metric is recorded immediately after a connectivity change is detected. + The metric name is suffixed with the connection type before the connectivity + change was detected. This will miss data from users whose connection type + never changes and will be biased to users whose connection type changes + frequently. + + + + + + Obsoleted in August 2017. + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated HTTP RTT and the observed HTTP + RTT. HTTP RTT estimated by the network quality estimator at the time of + navigation start is compared with the HTTP RTT observed during the specified + time interval following the start of the navigation. Both the estimated and + the observed RTT are computed using average algorithm that assigns equal + weight to all observations. + + + + + + Obsoleted in August 2017. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the URLRequest layer + computed using average algorithm that assigns equal weight to all + observations. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted in August 2017. + + tbansal@chromium.org + bengr@chromium.org + + Records the difference between the estimated HTTP RTT and the observed HTTP + RTT. HTTP RTT estimated by the network quality estimator at the time of + navigation start is compared with the HTTP RTT observed during the specified + time interval following the start of the navigation. Both the estimated and + the observed RTT are computed using weighted average algorithm. + + + + + + Obsoleted in August 2017. + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the URLRequest layer + computed using weighted average algorithm. + + This metric is recorded on main-frame requests. + + + + + + Obsoleted April 2020. + + tbansal@chromium.org + + Wifi signal strength level reported by the device at the time of ECT + computation. Recorded only on Wifi networks, and only when the value is + available. The value ranges between 0 and 4 (both inclusive). + + + + + + Obsoleted in M81. + + tbansal@chromium.org + bengr@chromium.org + + Difference between the minimum and the maximum received signal strength + since the last connection change event. Recorded only on Wifi connections on + Android platform when the Wifi signal strength was available. Recorded right + before a connection change event. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + + Removed 10/2011. No longer tracked, replaced with NewTabPage.DefaultPageType + + Please list the metric's owners. Add more owner tags as needed. + The default pane when the NTP is first opened. + + + + + Removed 10/2011. No longer tracked, replaced with + NewTabPage.SelectedPageType + + Please list the metric's owners. Add more owner tags as needed. + The pane selected when the user switches panes in the NTP. + + + + + Long removed. + + knn@chromium.org + + This histogram records whether the account ID is actually an email if we + detect an account that has an account ID but not email. + + + + + + Long removed. + + knn@chromium.org + + This histogram records the account ID migration status from email to GAIA ID + if we detect an account that has an account ID but not email. + + + + + + Long removed. + + tbarzic@chromium.org + + Failure reason of final OAuth2 access token retrieval call during Chrome OS + login. + + + + + + Long removed. + + tbarzic@chromium.org + + Retry reason of failed OAuth2 access token retrieval call during Chrome OS + login. + + + + + + Removed 2015-05-22. Replaced by Signin.ListAccountsFailure. + + zelidrag@chromium.org + + Failure reason of final ListAccounts call failure during Chrome OS login. + This data is now included in Signin.ListAccountsFailure. + + + + + + Removed 2015-05-22. Replaced by Signin.ListAccountsRetry. + + zelidrag@chromium.org + + Retry reason of failed ListAccounts call during Chrome OS login. This data + is now included in Signin.ListAccountsRetry. + + + + + + Long removed. + + tbarzic@chromium.org + + Failure reason of final OAuthLogin (with SID+LSID) call during Chrome OS + login. + + + + + + Long removed. + + tbarzic@chromium.org + + Retry reason of failed OAuthLogin (with SID+LSID) call during Chrome OS + login. + + + + + + Removed 2015-05-22 + + zelidrag@chromium.org + + Failure reason of final OAuthLogin (with uber token) call during Chrome OS + login. This data is now (M44+) included in Signin.UberTokenFailure. + + + + + + Removed 2015-05-22 + + zelidrag@chromium.org + + Retry reason of failed OAuthLogin (with uber token) call during Chrome OS + login. This data is now (M44+) included in Signin.UberTokenRetry. + + + + + + Long removed. + + knn@chromium.org + + Only applicable on M47 on Android. Measure the frequency of a suppressed + error state when the account is not seeded. + + + + + + Removed 2016-10, and replaced by OfflinePages.AggregatedRequestResult2. + + dimich@chromium.org + jianli@chromium.org + Result of servicing requests that may contain offline page. + + + + + Removed 2017-10, and replaced by + OfflinePages.ArchiveManager.ArchiveDirsCreationResult2 with suffixes for + temporary and persistent pages. + + dimich@chromium.org + + This is recorded every time the archive directory is being created. It + doesn't include the case which the archive directory exists. + + + + + + Removed in M61. + + chili@chromium.org + The error codes that caused a page load failure. + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + Reason for the Chrome Custom Tabs API prerender call to be ignored. + + There are several causes for the Chrome Custom Tabs API calls to be ignored, + this tracks the potential causes so we can see how often the prerenderer + doesn't prerender due to these being switched off. Since this is checked + elsewhere (CCTAPI), this only catches the user switching off the third party + cookies or navigation prediction after the CCT API has checked. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + True if all requested CSS was loaded when a background page loaded. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + True if all requested images were loaded when a background page loaded. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + True if all requested XHRs were completed when a background page loaded. + + + + + + Removed in M61. + + dougarnett@chromium.org + offline-dev@chromium.org + + Connection type when prerenderer reports Unsupported Scheme error. + + To give insight about Unsupported Scheme errors that may be due to lost + network connection (as data URL used for rendering an error page will + manifest as an Unsupported Scheme error by the prerenderer). + + + + + + Removed 2/2018. No longer used. + + jianli@chromium.org + Number of offline pages that are deleted in a batch. + + + + + Removed in M65. + + jianli@chromium.org + + Total size, in kilobytes, of all offline pages that are deleted in a batch. + + + + + + Removed on 6/2019. No longer considered useful. + + carlosk@chromium.org + fgorski@chromium.org + + Reports whether a web page complies with all requirements for it to be + allowed to be saved as an offline page. This is reported only on Android, + after a successful main frame navigation is finished. + + + + + + Removed 3/2016, and replaced by OfflinePages.ClearAllStatus2. + + jianli@chromium.org + Status code of wiping out the offline page data. + + + + + Removed a long time ago, marked as expired for M83. + + jianli@chromium.org + Status code of wiping out the offline page data. + + + + + Removed as of Jan 2018, replaced by + OfflinePages.ClearTemporaryPages.BatchSize. + + dimich@chromium.org + + Number of pages deleted in a batch during one clear-storage request. + + + + + + Removed in Oct 2017 and replaced by OfflinePages.ClearStoragePreRunUsage2 as + it was reporting data in bytes instead of the expected MiB. + + petewil@chromium.org + + The total storage size used by all offline pages from a specific client + namespace. + + + + + + Removed as of Jan 2018, replaced by OfflinePages.ClearTemporaryPages.Result. + + dimich@chromium.org + Result of asking storage manager to clear storage. + + + + + Removed 12/2017, replaced by OfflinePages.ConsistencyCheck.Temporary.Result + and OfflinePages.ConsistencyCheck.Persistent.Result. + + romax@chromium.org + + Whether an attempt to delete archive files without metadata was successful. + + + + + + Removed 12/2017, replaced by OfflinePages.ConsistencyCheck.Temporary.Result + and OfflinePages.ConsistencyCheck.Persistent.Result. + + romax@chromium.org + + Whether an attempt to delete pages without archives was successful. + + + + + + Removed 11/2016, replaced by + OfflinePages.Consistency.DeletePagesMissingArchiveFileResult. + + romax@chromium.org + + Whether an attempt to expire pages without archives was successful. + + + + + + Removed 12/2017, replaced by + OfflinePages.ConsistencyCheck.Temporary.PagesMissingDbEntryCount and + OfflinePages.ConsistencyCheck.Persistent.PagesMissingDbEntryCount. + + romax@chromium.org + + Number of archives without metadata entry when checking consistency. + + + + + + Removed 12/2017, replaced by + OfflinePages.ConsistencyCheck.Temporary.PagesMissingArchiveFileCount and + OfflinePages.ConsistencyCheck.Persistent.PagesMissingArchiveFileCount. + + romax@chromium.org + + Number of offline pages without archive file when checking consistency. + + + + + + Removed 04/2018, since saving public offline pages to external download + directory needs a different consistency check strategy. + + romax@chromium.org + + Number of persistent offline pages without archive file when checking + consistency. It will only be reported if the number is larger than 0. + + + + + + Removed 04/2018, since saving public offline pages to external download + directory needs a different consistency check strategy. + + romax@chromium.org + + Number of archives without database entry when checking persistent page + consistency. It will only be reported if the number is larger than 0. + + + + + + Removed as of 12/2017. Replaced by OfflinePages.AccessCount. + + jianli@chromium.org + + Number of accesses to the offline page since its creation. This is reported + when the offline page was deleted. + + + + + + Removed 2/2018. No longer used, duplicate of + OfflinePages.SavePage.FreeSpaceMB. + + jianli@chromium.org + + The amount of free space available, in megabytes, on the user's device after + the page is deleted. + + Note that before M52 this operation was started before delete operation. + + + + + + Removed as of 5/2016. Marginal applicability. + + jianli@chromium.org + + The percentage of free space available on the user's device when the page is + being deleted. + + + + + + Removed as of 01/2018. Replaced by OfflinePages.PageAccessInterval. + + jianli@chromium.org + + Length of time between when an offline page was created and was opened last + time. This is reported when the page was deleted. + + + + + + Removed 2/2018. No longer used, duplicate of OfflinePages.PageSize. + + jianli@chromium.org + Size of the offline page, in kilobytes, that was deleted. + + + + + Removed as of 01/2018. Replaced by OfflinePages.PageAccessInterval. + + jianli@chromium.org + + Length of time between when an offline page was last opened and was deleted. + + + + + + Removed as of 03/2018. Replaced by similar metric + OfflinePages.StorageInfo.InternalUsagePercentage and + OfflinePages.StorageInfo.ExternalUsagePercentage. + + fgorski@chromium.org + jianli@chromium.org + + The percentage of space taken by offline pages from the free space that + could be available, if the feature was not present. I.e. considering + situation where the user has: Free Space, Offline content, other apps and + data. This is a percentage of: Offline content / (Offline content + Free + Space). + + The value will be recorded after user deletes a single or multiple offline + pages. In case pages are removed in bulk, this value will be reported once. + This value is only reported with deleting, as we are trying to infer if lack + of free space might have caused the user to delete. + + + + + + Removed 2/2018. No longer used. + + dewittj@chromium.org + dimich@chromium.org + + The number of downloaded pages with the same URL that exist at the time that + we delete a downloaded page. + + + + + + Removed 2/2018. No longer used. + + dewittj@chromium.org + dimich@chromium.org + + The number of downloaded pages with the same URL that exist at the time that + we save a downloaded page. + + + + + + Removed 2/2018. No longer used. + + dewittj@chromium.org + dimich@chromium.org + + If at save time there is another downloaded page with the same URL, this + tracks this amount of time between creation of the most recent existing page + and the current page. + + + + + + Removed 5/2016. Offline pages no longer depend on bookmarks UI. + + dougarnett@chromium.org + + Whether a user-edited bookmark URL had a saved offline page. + + + + + + Removed 11/2016. Offline pages no longer use two-step expiration. + + romax@chromium.org + Number of pages that are expired in a batch. + + + + + Removed 11/2016. Offline pages no longer use two-step expiration. + + romax@chromium.org + + Length of time between when an offline page was created and was expired. + + + + + + Removed 11/2016. Offline pages no longer use two-step expiration. + + romax@chromium.org + Result of updating expired page in store. + + + + + Removed 11/2016. Offline pages no longer use two-step expiration. + + romax@chromium.org + + Length of time between when an offline page was last opened and was expired. + + + + + + Removed 5/2016. Offline pages no longer depend on bookmarks UI. + + fgorski@chromium.org + jianli@chromium.org + + Whether user is connected when entering the filter with offline only + content. + + + + + + Removed 5/2016. Offline pages no longer depend on bookmarks UI. + + fgorski@chromium.org + jianli@chromium.org + + Whether user is connected when leaving the filter with offline only content. + + + + + + Removed 2/2018. Merged to OfflinePages.PageAccessInterval. + + jianli@chromium.org + + The time elapsed between creation of the offline page and the first time it + was opened. + + + + + + Removed 5/2016. Not longer needed. + + jianli@chromium.org + + Whether the page that was being saved offline was in incognito mode. + + + + + + Removed 5/2016. Offline pages no longer depend on bookmarks UI. + + fgorski@chromium.org + jianli@chromium.org + Logs a UI location from which an offline page is launched. + + + + + Removed in M65. + + jianli@chromium.org + + Status code of loading from the offline pages metadata store. + + + + + + Removed 10/2015, and replaced by OfflinePages.LoadStatus. + + jianli@chromium.org + + Whether an attempt to load the offline pages metadata store was successful. + + + + + + Removed 2/2018. No longer used. + + dewittj@chromium.org + jianli@chromium.org + + The amount of time to create the offline pages archive directory. + + + + + + Removed in M65. + + dewittj@chromium.org + jianli@chromium.org + + The amount of time to create the offline pages archive directory and load + the offline page model. + + + + + + Removed 2/2018. No longer used. + + dimich@chromium.org + + Whether the metadata database was successfully loaded, after possibly + several retries. + + + + + + Removed 2/2018. No longer used. + + dimich@chromium.org + + The count of attempts spent to open the metadata database. In the best case, + it's 1. There is a small upper limit. This is recorded only at success. + Failures are counted by OfflinePages.Model.FinalLoadSuccessful. + + + + + + Removed 5/2016. This was the dup of OfflinePages.SavedPageCount. + + fgorski@chromium.org + jianli@chromium.org + Number of offline pages the user has. Android only. + + + + + Removed 5/2016. Offline pages no longer depend on bookmarks UI. + + jianli@chromium.org + + Whether the user was online when a saved page with offline copy was opened. + + + + + + Removed 2/2018. Merged to OfflinePages.PageAccessInterval. + + jianli@chromium.org + Length of time between two consecutive opens. + + + + + Removed 9/2017. Replaced by OfflinePages.Prefetching.ActionAttempts + + carlosk@chromium.org + + Number of attempts to perform a specific retriable pipeline action for each + finished prefetch item. + + + + + + Removed 8/2018. + + carlosk@chromium.org + + Reports differences between the expected size of a prefetch archive -- as + reported by the service -- and the actual downloaded file size. + + + + + + Removed as of 5/2018. Replaced with + OfflinePages.Prefetching.FetchThumbnail.Complete2. + + harringtond@chromium.org + + Records the final status of attempts to fetch thumbnails for prefetched + offline pages. + + + + + + Removed as of 2/2019. + + harringtond@chromium.org + carlosk@chromium.org + + Records the final status of attempts to fetch thumbnails for prefetched + offline pages. The 1st attempt takes place right after the prefetch item was + sent to the cloud service as part of a request for the creation of its + offline snapshot. The 2nd attempt occurs right after the offline snapshot + was successfully downloaded by the client. + + + + + + Removed as of 2/2019. + + harringtond@chromium.org + Reports each time a thumbnail fetch is attempted. + + + + + Removed as of 8/2019. No longer needed. + + carlosk@chromium.org + offline-dev@chromium.org + + Tracks the time between store closing and reopening again within a session. + The store is meant to close itself after a period of inactivity. We are + trying to assess how much time the store is unloaded from memory vs. time it + is loaded and not used. This event will be reported when the store is opened + after being closed within the same lifetime of Chrome. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + When publishing an archive, we create the download directory if it doesn't + already exist. If we get an error, we record it here. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + When publishing an offline page, the move file step can fail. This returns + the reason for failure as a linux errno. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + When a move file fails for publishing, what caused the failure. + + + + + + Removed on 04/2020 in favor of becoming a special case of + OfflinePages.SavePageResult2. + + petewil@chromium.org + + Failure attempting to move a file while publishing downloaded page. + + + + + + Removed 8/2016. Use OfflinePages.RequestResult instead. + + dimich@chromium.org + + Result of automatic redirect to offline version of the page or back. Emitted + exactly once when offline-to-online or online-to-offline redirect is + determined to be needed and conveys the outcome of redirect. + + + + + + Removed 6/2016. Refactored into OfflinePages.RedirectResult. + + jianli@chromium.org + + Number of times an offline copy was loaded instead when the user is trying + to load the online version of a saved page and there is no network + connection. + + + + + + Removed 6/2016. Refactored into OfflinePages.RedirectResult. + + jianli@chromium.org + + Number of times an online version was loaded instead when the user is trying + to load the offline copy of a saved page and there is network connection. + connection. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Records whether the content read from intent URI (file:// or content://) + changed after the initial validation that was done to route the request when + the intent was received. This is recorded at the time that Offline Page + Request Handler tried to read the data, in preparation to show an offline + page to a user. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Positive net error code for opening the underlying file to serve the offline + page, including net::OK. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Track whether the range header is provided when an offline page is served. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Positive net error code for the failure to read the underlying file to serve + the offline page. net::OK is not included. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + + Positive net error code for the failure to seek the underlying file to serve + the offline page. net::OK is not included. + + + + + + Removed as of 2/2018. Replaced by OfflinePages.SavedPageCountUponQuery. + + jianli@chromium.org + + Number of saved pages restored from the offline pages metadata store when it + is logged. + + + + + + Removed as of 03/2018. Replaced by similar metric + OfflinePages.StorageInfo.InternalFreeSpaceMB. + + jianli@chromium.org + + The amount of free space available, in megabytes, on the user's device after + the page is saved. + + Note that before M52 this operation was started before save operation. + + + + + + Removed as of 5/2016. Marginal applicability. + + jianli@chromium.org + + The percentage of free space available on the user's device when the page is + being saved. + + + + + + Removed on 04/2020. The same information can be obtained from + OfflinePages.SavePageResult2.* (from each namespace suffix). + + dimich@chromium.org + + Counts the number of times an offline page is saved. Events are reported per + offline pages namespace. + + + + + + Removed on 04/2020. Replaced with OfflinePages.SavePageResult2. + + jianli@chromium.org + Result of saving an offline copy for a page. + + + + + Removed 6/2016. Refactored into OfflinePages.RedirectResult. + + jianli@chromium.org + + Whether an offline page is shown, instead of error page, when the network is + disconnected or poor condition. + + + + + + Removed 3/2019. + + dimich@chromium.org + + If the directory to store the SQLite database file does not exist, it is + created. This is recorded every time the database is opened, even if the + directory already exists, in which case it's reported as FILE_OK. + + + + + + Removed as of 8/2019. No longer needed. + + carlosk@chromium.org + offline-dev@chromium.org + + Tracks the time between store closing and reopening again. The store is + meant to close itself after a period of inactivity. We are trying to assess + how much time the store is unloaded from memory vs. time it is loaded and + not used. This event will be reported when the store is opened after being + closed within the same lifetime of Chrome. + + + + + + Removed as of 03/2018. Replaced by similar metric + OfflinePages.StorageInfo.TotalArchiveSize. + + fgorski@chromium.org + jianli@chromium.org + + Total size of all the offline pages saved by the user. + + This value is recorded whenever the number of pages change, meaning after a + page is added or removed. If pages are removed in bulk, this value will be + reported only once. + + + + + + Removed as of 5/2016. Marginal applicability. + + fgorski@chromium.org + jianli@chromium.org + + Total size of all the offline pages saved by the user as a percentage of + total storage size. + + This value is recorded whenever the number of pages change, meaning after a + page is added or removed. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + jianli@chromium.org + + Percentage of battery remaining when the offline page background loading + task wakes up to check for work. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + jianli@chromium.org + + Whether the device is plugged in when the offline page background load task + wakes up to check or work. + + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + jianli@chromium.org + + Time delay from a dinosaur page to connection being available. + + + + + + Removed in M77. + + petewil@chromium.org + jianli@chromium.org + + Which network is available (if any) when the offling page background loading + task wakes up to check for work. + + + + + + Removed as of 8/2019. No longer needed. + + carlosk@chromium.org + offline-dev@chromium.org + + Indicates whether the browser was connected when Open online button was + clicked on Page Info popup, which causes a reload of an offline page to + online version. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + When a page is loaded in offline mode, the percentage of resources on that + page that were successfully loaded. + + + + + + Removed 2019/08, this metrics doesn't reflect the measurement speed because + it is dependent on the length of text. + + yiyix@chromium.org + fserb@chromium.org + + Time spent in microseconds to perform calls to measure TextMetrics for + OffscreenCanvas. It's measured each time TextMetrics is called. + + + + + + Aggressive HistoryURL provider field trial deleted in spring 2012. + + Please list the metric's owners. Add more owner tags as needed. + + A number that indicates what omnibox ranking behavior the user is seeing as + part of the OmniboxAggressiveHistoryURLProvider field trial + (OmniboxAggressiveHistoryURLProvider). + + + + + + Removed in August 2020. + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-android-omnibox-team@google.com + + Records number of times an Answer is presented as one of the Omnibox + Suggestions at the time the user exited the omnibox. Exiting the omnibox + includes navigating (to entered text or any suggestion), pressing the system + back key, clearing omnibox, blanking screen / locking the phone (whether + intentionally or due to inactivity), or closing the Chrome app. This metric + is logged every time the omnibox is exited, including when no answer is + present in the list of suggestions. + + Nota bene: in some circumstances this histogram is double counting on + purpose. Scenarios cover repetitive actions that expose same answer + suggestion, ie. leave-enter-leave application, or leave-enter-clear where no + new suggestion fetches are done. + + This histogram assumes that no more than 1 AiS suggestion is shown at a + time, which was enforced by the backend at the time the histogram was + created. Additional histogram/s may be required to properly track how + frequently answers are shown in general - and in what quantity. + + This histogram is related to Omnibox.SuggestionUsed.AnswerInSuggest. + + + + + + This became the new implementation of Omnibox.CharTypedToRepaintLatency as + of 08/2017. + + asvitkine@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + A refinement of the Omnibox.CharTypedToRepaintLatency metric that attempts + to more accurately track the latency by measuring until the point when the + compositor has actually put pixels on the screen. In particular, this will + capture the time used to also paint the Omnibox result views as a result of + the character insertion, which is not covered by + Omnibox.CharTypedToRepaintLatency. If there are multiple keystrokes before a + paint, logs the time since the earliest one. + + + + + + Removed 06/2020. Use "Omnibox.EditUrlSuggestion.*" user actions + instead. + + jdonnelly@chromium.org + mdjones@chromium.org + fgorski@chromium.org + ender@chromium.org + + The action performed on the edit-URL omnibox suggestion that contains the + "what you typed"/current URL. If visible, this is the first + suggestion. + + + + + + Removed 10/2018 and replaced with "Omnibox.EnteredKeywordMode2". + + mpearson@chromium.org + + The number of times users enter keyword hint mode "Search ___ + for:" and how. + + + + + + Replaced with Omnibox.FocusToOpenTimeAnyPopupState in April 2014. + + mpearson@chromium.org + + The length of time between when a user focused on the omnibox and opened an + omnibox match (which could be what they typed or a suggestion). + + + + + + Replaced with Omnibox.FocusToOpenTimeAnyPopupState2 in August, 2016. + + mpearson@chromium.org + + The length of time between when a user focused on the omnibox and opened an + omnibox match (which could be what they typed or a suggestion). This is + recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. + + + + + + Replaced with Omnibox.FocusToOpenTimeAnyPopupState3 in January, 2017, which + only differs in the bucketing and range. + + mpearson@chromium.org + + The length of time between when a user focused on the omnibox and opened an + omnibox match (which could be what they typed or a suggestion). This is + recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. + It is not recorded if a match is opened without triggering a focus event, + e.g., when a user drags a URL to the omnibox to navigate. + + To know how common this last condition is, compare the total count of this + histogram to the total number of omnibox events. + + Android started logging this in M76. + + + + + + Removed 2020-07-15 + + mpearson@chromium.org + jdonnelly@chromium.org + pkl@chromium.org + + iOS: Records whether a hardware keyboard is used to input text. This is + recorded each time a UIKeyboardWillChangeFrameNotification is sent while + editing the omnibox text. + + + + + + Removed 2015-01-27 + + mpearson@chromium.org + + Whether there was at least one legal default match without an + |inline_autocompletion|. Recorded every time + AutocompleteResult::SortAndCull() is called, which could happen multiple + times on each keystroke. + + + + + + Removed in August 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Times URLIndexPrivateData::HistoryIDSetFromWords(), which is called by the + omnibox's HistoryQuick provider. + URLIndexPrivateData::HistoryIDSetFromWords() can be called multiple times + per keystroke due to, for example, the cursor being in the middle of the + input string or SearchProvider's calls to Classify(). + + + + + + Made obsolete in July 2020 for the M86 Milestone. + + mahmadi@chromium.org + tommycli@chromium.org + + The maximum number of matches returned by the provider. Triggered when + zero-prefix suggestions are enabled and requested as a result of user focus + into the Omnibox or the Realbox on the NTP. + + + + + + Made obsolete in July 2020 for the M86 Milestone. + + mahmadi@chromium.org + tommycli@chromium.org + + The number of search terms examined until the maximum possible matches are + fulfilled. Used to determine the upper bound of search terms to query from + the keyword search terms database. Triggered when zero-prefix suggestions + are enabled and requested as a result of user focus into the Omnibox or the + Realbox on the NTP. + + + + + + Removed 2019-11-10. Replaced by Omnibox.MatchStability.AsyncMatchChange2. + + tommycli@chromium.org + jdonnelly@chromium.org + + This histogram was buggy and the data should be disregarded. + + The original intent was to count asynchronous match updates for each + position. The implementation had a bug, and it overcounted. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Records a boolean value indicating whether the Physical Web provider was + invoked by focusing the omnibox during the current omnibox session. This is + unexpected; it's probably a bug somwhere. Recorded when the user selects an + omnibox suggestion. Does not record when the Physical Web omnibox provider + is disabled. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + The number of matches returned by PhysicalWebProvider. Emitted when the + omnibox is first focused, unless the user is in incognito mode. Capped at + 10. + + + + + + Obsolete 05/16/2017. Data is unused (crbug.com/719801). + + kkimlabs@chromium.org + + The number of progress bar break point updates from page load started to + page load finished. + + + + + + Obsolete 05/16/2017. Data is unused (crbug.com/719801). + + kkimlabs@chromium.org + + The number of progress bar frame updates from page load started to page load + finished. If there is no animation, this matches + Omnibox.ProgressBarBreakPointUpdateCount. Note that there can be additional + updates after page load finished, animating to 100%, but this histogram + doesn't include them. + + + + + + Removed 2015-06-12. Replaced by Omnibox.ProviderTime2. + + mpearson@chromium.org + + The length of time taken by the named provider"s synchronous pass. + + + + + + Removed 2012-11-14. Replaced by Omnibox.ProviderTime. + + Please list the metric's owners. Add more owner tags as needed. + + Time the HistoryContentProvider takes to perform a bookmark search. + + + + + + Removed in June 2019 for M-78. + + mpearson@chromium.org + jdonnelly@chromium.org + stkhapugin@chromium.org + + The elapsed time to acquire the location sent in the X-Geo header for an + Omnibox query. + + + + + + Removed in June 2019 for M-78. + + mpearson@chromium.org + jdonnelly@chromium.org + stkhapugin@chromium.org + + The estimated horizontal accuracy of the location sent in the X-Geo header + for an Omnibox query. + + + + + + Removed in August 2020 + + mpearson@chromium.org + jdonnelly@chromium.org + stkhapugin@chromium.org + + For iOS, whether the application is authorized to use location services when + the user enters a search query into the Omnibox. + + + + + + Removed 2015-06-12. Replaced by Omnibox.QueryTime2. + + mpearson@chromium.org + + Time it takes for the omnibox to become responsive to user input after the + user has typed N characters. This measures the time it takes to start all + the asynchronous autocomplete providers (but not wait for them to finish). + + + + + + Removed in August 2020. + + ender@chromium.org + jdonnelly@chromium.org + mpearson@chromium.org + chrome-android-omnibox-team@google.com + + Records, for each entity suggestion (people, music, ...) whether it was + decorated with image / color / icon at the time the user exited the omnibox. + Exiting the omnibox includes navigation (url or query), pressing back key, + locking the phone, clearing the omnibox, closing Chrome, or just screen + blacking out due to prolonged inactivity. + + This metric is currently only recorded on Android, though it could be added + to the other platforms. + + + + + + Removed in August 2020. + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-android-omnibox-team@google.com + + Records number of presented Rich Entity suggestions at the time the user + exited the omnibox. Exiting the omnibox includes navigating (to entered text + or any suggestion), pressing the system back key, clearing omnibox, blanking + screen / locking the phone (whether intentionally or due to inactivity), or + closing the Chrome app. This metric is logged every time the omnibox is + exited, including when no entities are present in the list of suggestions. + + Nota bene: in some circumstances this histogram is double counting on + purpose. Scenarios cover repetitive actions that expose same entity + suggestions, ie. leave-enter-leave application, or leave-enter-clear where + no new suggestion fetches are done. + + This histogram is related to Omnibox.SuggestionUsed.RichEntity. + + + + + + Removed in June 2019 for M-78. + + mpearson@chromium.org + jdonnelly@chromium.org + + When a user switches tabs, whether the omnibox had an edit in progress. + + + + + + Made obsolete around Chrome 32. Use Omnibox.SearchEngineType instead. + + Please list the metric's owners. Add more owner tags as needed. + + The id of search engine that was used for search in omnibox. See + src/chrome/browser/search_engines/template_url_prepopulate_data.cc for more + info. + + + + + + Removed in June 2019 for M-78. + + mpearson@chromium.org + jdonnelly@chromium.org + + Time it takes to add all the raw history results to the list of matches. + + + + + + Deleted in August 2018 in M-70. + + mpearson@chromium.org + + Time it takes to convert all the results to matches and add them to a map, + to keep the most relevant match for each result. + + + + + + Deleted in August 2018 in M-70. + + mpearson@chromium.org + + Time it takes for the omnibox to search the previous query history database + for queries that start with the omnibox text. + + + + + + Removed in M84. + + chrome-android-omnibox-team@google.com + ender@chromium.org + jdonnelly@chromium.org + mpearson@chromium.org + + Counts how often omnibox suggestions are used, and in the case a regular + search / url (not an Answer, Entity or any other specialized) suggestion was + selected - records how the suggestion was decorated. + + This histogram is related to Omnibox.IconOrFaviconShown. + + + + + + Removed in M58, replaced with Omnibox.SuggestionUsed.NearbyURLCount.AtFocus + and Omnibox.SuggestionUsed.NearbyURLCount.AtMatchCreation. + + + The number of nearby Physical Web URLs when the user focused the omnibox. + Recorded when the user accepts an omnibox suggestion, regardless of whether + the suggestion came from PhysicalWebProvider. Capped at 50. + + In M57, the values recorded by this histogram were determined to be bugged. + It's believed that it was recording uninitialized values due to a corner + case on Android that allows an omnibox suggestion to be selected without + first focusing the omnibox. In addition to the new histograms, + Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus was added to + detect this case. https://crbug.com/691059 + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + The number of nearby Physical Web URLs when Physical Web Provider was last + focused (i.e., the start of the current session). Recorded when the user + accepts an omnibox suggestion, regardless of whether the suggestion came + from PhysicalWebProvider. Capped at 50. + + Does not record if the omnibox was not focused during the current session. + Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus records true + when we hit this case. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + The number of nearby Physical Web URLs when Physical Web Provider last + constructed matches. Recorded when the user accepts an omnibox suggestion, + regardless of whether the suggestion came from PhysicalWebProvider. Capped + at 50. + + + + + + Removed in August 2020. + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-android-omnibox-team@google.com + + Whether a Rich Entity omnibox suggestion was selected when the user used the + omnibox to go somewhere. + + This histogram is related to Omnibox.RichEntityShown. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from the page first appearing in the foreground to its + first meaningful paint. Only recorded on navigations that use a prerender + that is to a search query suggestion selected from the omnibox. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from the page first appearing in the foreground to its + first contentful paint. Only recorded on navigations that use a prerender + that is to a search query suggestion selected from the omnibox. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from a page being navigated to in prerender to it first + showing up in foreground. Only recorded on navigations that used a prerender + that was to a search query suggestion selected from the omnibox. This is + only recorded on pages that experience a first contentful paint. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from the page first appearing in the foreground to its + first meaningful paint. Only recorded on navigations that use a prerender + that is to a URL suggestion selected from the omnibox. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from the page first appearing in the foreground to its + first contentful paint. Only recorded on navigations that use a prerender + that is to a URL suggestion selected from the omnibox. + + + + + + Prerender was retired from the code long ago; this histogram was finally + removed in July 2020. + + mpearson@chromium.org + jdonnelly@chromium.org + + Measures the time from a page being navigated to in prerender to it first + showing up in foreground. Only recorded on navigations that used a prerender + that was to a URL suggestion selected from the omnibox. This is only + recorded on pages that experience a first contentful paint. + + + + + + Removed as of 12/2019 + + mdjones@chromium.org + lzbylut@google.com + + The amount of time that passes in ms between the user focusing the omnibox + and performing some action on Android. This is only recorded the first time + the user performs this action per omnibox focus event. Other + Omnibox.TimeUntilFirst.* events are not recorded past the first event. + + + + + + Removed in 06/2020 for M-85. + + mpearson@chromium.org + jdonnelly@chromium.org + cthomp@chromium.org + + The amount of time, in milliseconds, between the start of a typed URL + navigation in the omnibox (the user typing a URL to completion, or selecting + a URL from the inline autocomplete or dropdown) and the start of a redirect + upgrading the URL to HTTPS. This is only recorded when the upgraded URL is + the same except for the scheme and the addition/removal of a + "www." prefix. + + To calculate the percentage of HTTP URL navigations that have been upgraded + in this way, divide the count of this histogram by the count for HTTP in + Omnibox.URLNavigationScheme. + + + + + + Removed 05/2019 because histogram was not recorded in every circumstance. + Superseded by Omnibox.ZeroSuggest.Eligible.OnFocusV2. + + mpearson@chromium.org + jdonnelly@chromium.org + + Whether the user has settings configured so that the current page URL can be + sent to the suggest server to request contextual suggestions. For example, + this is only supported for users who have Google as their default search + engine (unmodified version of Google), have search suggest enabled, are + signed-in and syncing without a custom passphrase, and don't have an + incognito window open. There are other criteria too. Recorded on focus in + the omnibox if there is default search provider and we've constructed a + suggest URL. + + Some additional guidelines: if an incognito window is open, all focus events + will go into the "generally ineligible" bucket. Likewise, if the + current page is a search results page, we don't allow contextual suggestions + either so focus events on those pages go in the "generally + ineligible" bucket. The difference between "eligible" and + "generally eligible but not this time" depends only the properties + of the current URL. + + Recorded regardless of whether contextual or non-contextual zero suggest is + currently enabled on the user's platform. However, if zero suggest (in all + forms) is entirely disabled, the user will be perpetually ineligible. + + + + + + Removed from code as of M87 / September 2020. This is no longer useful. + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Whether the user is eligible to receive personalized zero suggestions on the + NTP. This histogram is updated only when the user focuses the omnibox on the + NTP and is emitted only once even if multiple criteria make a user + ineligible. Consult the source code to learn more about the precedence of + these values. + + This metric is recorded for all contexts (including users non-syncing, in + incognito mode, or using different search engines) and targets specifically + eligibility in the current situation. + + + + + + Removed from code as of M87 / September 2020. This is no longer useful. + + ender@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Whether the user is eligible to receive personalized zero suggestions on the + NTP. This histogram is updated every time Chrome registers a profile change. + + This metric is recorded for all contexts (including users non-syncing, in + incognito mode, or using different search engines) and targets overall + profile eligibility to receive zero-prefix query suggestions on a New Tab + Page. + + + + + + Obsolete as of M85. Added back in 2013 (https://crrev.com/23600051), this is + no longer useful. + + mpearson@chromium.org + jdonnelly@chromium.org + hfung@chromium.org + + The number of most visited suggestions returned when ZeroSuggest would have + triggered. The suggestions appear when the user has focused but not modified + the omnibox. + + + + + + Obsolete because of using suffixes. + + jeffreycohen@chromium.org + sebsg@chromium.org + + Whether the user has clicked the item when it is shown" Logged when the + share option is shown in the omnibox context menu" + + + + + + Obsolete as of M85. Supervised screen has gone so this metric became + obsolete. + + raleksandrov@google.com + cros-oac@google.com + + Number of times error screen has appeared during supervised user creation. + + + + + + Removed as of 08/27/2020. No longer needed to track size of a response. + + raleksandrov@google.com + cros-oac@google.com + chromesky-eng@google.com + The size of the recommend-apps JSON response. + + + + + Removed as of 01/2020. + + mcrouse@chromium.org + dougarnett@chromium.org + + The remaining time a fetched hint that was loaded for use has before it + expires and is removed from the hint cache store. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + dougarnett@chromium.org + sophiechang@chromium.org + + Records when the optimization guide hint cache has a hint entry for a URL's + host at commit time. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + dougarnett@chromium.org + sophiechang@chromium.org + + Records when the optimization guide hint cache has a hint entry for a URL's + host before commit time (e.g., at original navigation time or redirected + navigation time). + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + dougarnett@chromium.org + sophiechang@chromium.org + + Records when the optimization guide hint cache has a loaded hint entry + matching a URL's host at commit time. This is recorded regardless of whether + an associated preview type is allowed for the navigation or not. If no + associated preview type is allowed, the hint will not be loaded from a + backing store, so this will only capture matches for in-memory hints. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + dougarnett@chromium.org + sophiechang@chromium.org + + Records when the optimization guide hint cache has a loaded page hint for a + URL at commit time. This is recorded regardless of whether an associated + preview type is allowed for the navigation or not. If no associated preview + type is allowed, the hint will not be loaded from a backing store, so this + will only capture matches for in-memory hints. + + + + + + Removed as of 01/2020. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records that a fetched hint loaded from the store has expired. If expired, + the hint is not provided. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + mcrouse@chromium.org + sophiechang@chromium.org + + Records once per navigation if the host that was navigated to was included + in a hints fetch request in the last 7 days, even if no hints were returned, + or had a hint served via the Optimization Hints component at commit. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + sophiechang@chromium.org + mcrouse@chromium.org + + Records once per navigation if the host that was navigated to was included + in a hints fetch request in the last 7 days, even if no hints were returned, + or had a hint served via the Optimization Hints component before commit. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records when hints fetching is enabled whether the HTTPS host being + navigated to was included in a hints fetch request and any hints returned + have not since expired. Captured at navigation start so it will not include + hints fetched based on the current navigation. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records whether the host being navigated to was included in a hints fetch + request and any hints returned have not since expired. Captured after a + navigation is committed in order to determine if the fetch attempt made at + navigation start succeeded or not. + + + + + + Obsolete as of 04/2020 since this histogram no longer makes sense with the + current request flow. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records whether the host being navigated to was included in a hints fetch + request and any hints returned have not since expired. Captured at + navigation start so will not include any newly fetched hints for this + navigation. + + + + + + Removed as of 08/2019 + + mcrouse@chromium.org + dougarnett@chromium.org + + Records whether the host being navigated to was included in a hints fetch + and any hints returned have not since expired. + + + + + + Removed as of 08/2019 + + dougarnett@chromium.org + sophiechang@chromium.org + + The percentage (0-100) of hints loaded over all attempted page loads between + component updates. Recorded when the OptimizationGuideService receives a + component with a new version. + + + + + + Removed as of 01/2020 since it rarely ever happens that there is a load + collision. + + mcrouse@chromium.org + sophiechang@chromium.org + + For each load of a prediction model from the OptimizationGuideStore, reports + whether the load collided with an update being made to the store. + + + + + + Removed as of 05/2020 to in favor of recording the version on update and on + load. + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the version of the prediction model being updated and stored in the + prediction model store and made available for use. Recorded only if the + model is valid and successfully loaded into memory for use. + + + + + + Removed with CL 731423002. OriginChip has been removed. + + gbillock@chromium.org + The number of clicks on the origin chip. + + + + + Obsolete as of Chrome 54. Sort of replaced by OriginTrials.ValidationResult. + + chasej@chromium.org + iclelland@chromium.org + + Counts the results of origin trial checks to enable experimental features. + The result for each feature check is counted at most once per execution + context (e.g. page, worker). + + + + + + Obsolete as of Chrome 54. + + chasej@chromium.org + iclelland@chromium.org + + Counts how often an error message is generated for each origin trial check + to enable an experimental feature. + + + + + + Obsolete as of Chrome M81. + + cfroussios@chromium.org + vasilii@chromium.org + + Error code returned by SecKeychainFindGenericPassword when the encryption + key is retrieved. + + + + + + Obsolete as of Chrome 72. + + tsabolcec@google.com + vasilii@chromium.org + + The number of times that Chrome prevented overwriting the encryption key in + a row. This metric is logged once on startup. + + + + + + Obsolete as of Chrome M81. + + cfroussios@chromium.org + vasilii@chromium.org + + Result of the second call to SecKeychainFindGenericPassword when the + encryption key was not found but was expected to be there. + + + + + + Obsolete as of Chrome M81. + + cfroussios@chromium.org + vasilii@chromium.org + + Action taken when retrieving the encryption key from the Keychain. This + metric is logged once on startup. + + + + + + Obsolete as of Chrome 73. This has been replaced by Bluetooth.Availability. + + erikchen@chromium.org + + The availability and capabilities of the Bluetooth driver on OSX devices. + This metric is logged on startup. + + + + + + Obsolete as of Chrome 43. See OmahaProxy for more relevant statistics. + + mark@chromium.org + The cat's flavor and how many bits there are in it. + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + Records the Fast User Switching events that occur. + + + + + Removed as of Chrome 40. See OSX.Fullscreen.Enter.Style, + OSX.Fullscreen.Enter.WindowLocation and + OSX.Settings.ScreensHaveSeparateSpaces. + + erikchen@chromium.org + + This event is recorded each time a user triggers fullscreen for a browser + window. The value's bits reflect different parameters. Bit 0: Fullscreen + entry mechanism (AppKit vs Immersive). Bit 1: Whether the window was on the + primary screen (Primary vs. Secondary). Bit 2: Whether displays have + separate spaces options is enabled (Seperate vs Shared). Bit 3: Whether + there are multiple screens. + + + + + + Removed as of 11/2018. + + spqchan@chromium.org + + This event is recorded each time a user triggers fullscreen and when the + fullscreen toolbar is updated with a new style. + + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + Records the filesystem type that the app lives on. + + + + + Removed 2020 August. + + kerrnel@chromium.org + mark@chromium.org + + The number of previous times that the keychain reauthorization did not + complete, when run during the main browser launch. + + + + + + Removed 2020 August. + + kerrnel@chromium.org + mark@chromium.org + + The number of previous times that the keychain reauthorization did not + complete, when run at update time. + + + + + + Removed 2020 August. + + kerrnel@chromium.org + mark@chromium.org + + How many times the keychain reauthorization ran before finally succeeding, + when run at update time. + + + + + + Removed 2020 August. + + kerrnel@chromium.org + mark@chromium.org + + How many times the keychain reauthorization ran before finally succeeding, + when run during the main browser launch. + + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + + Records how many other instances of this binary are running at startup. + + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + + The result of the update process's check for other instances of Chrome. + + + + + + Removed as of 11/2015. + + erikchen@chromium.org + + This event records the amount of time that the browser process main thread + blocks, waiting for a frame with the right dimensions to arrive from the gpu + process. + + + + + + Removed as of Chrome 51 since Mach has become the default mechanism. + + erikchen@chromium.org + + A histogram entry is emitted each time a base::SharedMemory object is + constructed. The value of the entry indicates the mechanism used to back the + shared memory region. + + + + + + Removed as of 02/2019 in favor of StagingDirectoryLocation2. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + Records first staging directory location that works. + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + + Records, during Chrome startup, the first staging directory location that + works. This is for the change to the updating system. + + + + + + Removed 2020 January. + + avi@chromium.org + rsesek@chromium.org + mark@chromium.org + + Records, during Chrome startup, the state of any staged updates. + + + + + + Replaced with HeapProfiling.ProfiledProcess.Type. + + erikchen@chromium.org + + One metric is emitted every 24-hours after Chrome is launched for every + process that is being profiled. The timer is reset if Chrome exits. + + + + + + Replaced with HeapProfiling.ProfilingMode. + + erikchen@chromium.org + + One metric is emitted every 24-hours after Chrome is launched for every + Chrome instance that is using out of process heap profiling. The timer is + reset if Chrome exits. + + + + + + Replaced with HeapProfiling.RecordTrace.Success. + + erikchen@chromium.org + + The metric is emitted each time Chrome attempts to record a memory-infra + trace to upload an out-of-process heap-profiling memory dump. + + + + + + Replaced with HeapProfiling.UploadTrace.Size. + + erikchen@chromium.org + + The metric is emitted each time Chrome uploads a trace. It reflects the + uncompressed size of the trace. + + + + + + Replaced with HeapProfiling.UploadTrace.Success. + + erikchen@chromium.org + + The metric is emitted each time Chrome uploads a trace. It reflects whether + the upload was successful. + + + + + + Removed as of Chrome 59 in favour of Overscroll.Cancelled3. + + rbyers@chromium.org + nzolghadr@chromium.org + + Overscroll gestures that were aborted before they were completed. + + + + + + Removed as of Chrome 44 in favour of Overscroll.Cancelled and + Overscroll.Navigated2. + + rbyers@chromium.org + mfomitchev@chromium.org + Completed overscroll gestures. +
+ An overscroll gesture starts when user scrolls past the edge of the web page + and continues scrolling in the same direction. An overscroll gesture is + completed when user stops scrolling (e.g. by lifting the fingers from the + touchscreen or touchpad). +
+ + + + + Removed as of Chrome 44 to switch to NavigationDirection enum. + + rbyers@chromium.org + mfomitchev@chromium.org + + Navigations that were triggered due to completed overscroll gesture. Note + that not all completed overscroll gestures trigger a navigation. + + + + + + Removed as of Chrome 59 in favour of Overscroll.Navigated3. + + rbyers@chromium.org + mfomitchev@chromium.org + + Navigations that were triggered due to completed overscroll gesture. Note + that not all completed overscroll gestures trigger a navigation. + + + + + + Removed as of Chrome 44 to switch to NavigationDirection enum. + + rbyers@chromium.org + mfomitchev@chromium.org + + Overscroll gestures initiated by the user. Note that not all overcroll + gestures started are completed (e.g. the overscroll gesture is aborted if + user clicks or presses a key during the gesture). + + + + + + Removed as of Chrome 59 in favour of Overscroll.Started3. + + rbyers@chromium.org + mfomitchev@chromium.org + + Overscroll gestures initiated by the user. Note that not all overscroll + gestures started are completed (e.g. the overscroll gesture is aborted if + user clicks or presses a key during the gesture). + + + + + + Removed Nov 2019 + + pkotwicz@google.com + + The squared distance between taps which occur in quick succession. Only + reported when the taps are far apart and touch noise filtering is enabled. + + + + + + Removed Nov 2019 + + pkotwicz@google.com + + The horizontal distance from a "touch press" to the closest other + touch. Only reported if there are two or more fingers onscreen and touch + noise filtering is enabled. + + + + + + Removed Nov 2019 + + pkotwicz@google.com + + The amount of time between noisy touches. The amount of time since Chrome + startup is recorded for the first noisy touch after startup. + + + + + + Removed Nov 2019 + + pkotwicz@google.com + + The time between taps which occur in quick succession at the same screen + location. Only reported when touch noise filtering is enabled. + + + + + + Removed In June 2019. + + kouhei@chromium.org + + Number of pages that had any HTML form interaction before next page load. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + bmcquade@chromium.org + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted due to being backgrounded. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a client side redirect (Javascript navigation). + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by the user closing the tab or browser. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a forward or back navigation. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a new navigation. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted. The abort cause is unknown. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a reload. + + + + + + Removed in favor of PageLoad.Experimental.AbortTiming equivalent. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by the user pressing stop. + + + + + + We now have sufficient infrastructure to always characterize aborts that + resulted in new navigations. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a navigation with unknown transition type. + + + + + + Removed 07/2020. Replaced with + PageLoad.Clients.Ads.AdPaintTiming.NavigationToFirstContentfulPaint2; see + http://crbug.com/1103782. + + jkarlin@chromium.org + johnidel@chromium.org + + Records the time from frame navigation start to FirstContentfulPaint of each + ad frame that receives a FirstContentfulPaint. The time could be quite + large, as some ads don't paint until they're scrolled into view. But the + metric is still useful in aggregate. + + Recorded for all ad frames with non-zero bytes or cpu usage that receive a + FirstContentfulPaint. Recorded when the ad frame or page is destroyed. + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.Network. + + jkarlin@chromium.org + + The size (in KB) of the resources loaded for all of the ad frames on the + page that loaded over the network. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.PercentNetwork. + + jkarlin@chromium.org + + The percentage of bytes loaded for all ad frames that were loaded over the + network. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.Aggregate.Total. + + jkarlin@chromium.org + + The size (in KB) of the resources loaded for all of the ad frames on the + page. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.Network. + + jkarlin@chromium.org + + The size (in KB) of the resources loaded for an ad frame from the network. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.PercentNetwork. + + jkarlin@chromium.org + + The percentage of bytes loaded for a single ad frame that were loaded over + the network. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.AdFrames.PerFrame.Total. + + jkarlin@chromium.org + + The size (in KB) of the resources loaded for an ad frame. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Network. + + jkarlin@chromium.org + + The size (in KB) of all of the page's resources that loaded over the + network. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.FullPage.Network.PercentAds. + + jkarlin@chromium.org + + The percentage of bytes loaded for the page (from the network) that came + from resource loads in ad frames (from the network). + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Total. + + jkarlin@chromium.org + + The size (in KB) of all of the page's resources. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.FullPage.Total.PercentAds. + + jkarlin@chromium.org + + The percentage of bytes loaded for the page that came from resource loads in + ad frames. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed 01/2019. Replaced with + PageLoad.Clients.Ads.Bytes.NonAdFrames.Aggregate.Total. + + jkarlin@chromium.org + + The size (in KB) of all of the page's resources except for those loaded in + ad frames. + + Only recorded if the page has at least one identified ad frame. Bytes are + measured as over-the-wire (e.g., compressed) response body KBs and do not + include header bytes. An ad frame consists of the identified ad frame and + all of its children (which may also be ads, but are counted as part of the + ancestor ad frame). + + + + + + Removed In July 2018, metric was buggy for subresource filter ads. + + jkarlin@chromium.org + + When a frame that is (or previously was) an ad frame renavigates, record + whether it renavigated to an ad frame or a non-ad frame. + + An ad frame consists of the identified ad frame and all of its children. Its + children (which may also be ads) are not counted when they renavigate. + + This metric is recorded as the event happens. Note that this is unlike most + other Clients.Ads metrics, which are recorded when the page load is + complete. + + + + + + Removed In July 2018. + + jkarlin@chromium.org + + When a frame that has never been part of an ad frame renavigates, record + whether it renavigated to an ad frame or a non-ad frame. + + This metric is recorded as the event happens. Note that this is unlike most + other Clients.Ads metrics, which are recorded when the page load is + complete. + + + + + + Removed in September 2018. At deprecation, 98.12% of parent frames were + known. + + jkarlin@chromium.org + + Records whether or not a parent frame is found for a subframe that finishes + navigating. + + + + + + Removed in September 2018. At time of deprecation: Subframe 80%, Script + 6.5%, Images 10%, and XHR was 3%. + + jkarlin@chromium.org + + Records the content::ResourceType when a resource finishes loading but the + ads metrics aren't aware of a committed frame for the resource. + + + + + + Removed 01/19. + + johnidel@chromium.org + jkarlin@chromium.org + + Whether or not the ad frame had a display: none style set, meaning it was + not visible to the user. Only recorded for ad frames with non-zero total + bytes. Recorded when the page is destroyed or navigated. + + + + + + Removed In May 2017. + + jkarlin@chromium.org + + The number of frames (with parent frame of main frame) that are on the page + identified as Google Ad Frames. + + Only recorded if the page has at least one identified ad frame. Child frames + of an ad frame are not included in the count. + + + + + + Removed In May 2017. + + jkarlin@chromium.org + + The percentage of frames (with parent frame of main frame) on the page that + are identified as Google Ad Frames. + + Only recorded if the page has at least one identified ad frame. An ad frame + consists of the identified ad frame and all of its children (which may also + be ads, but are counted as part of the ancestor ad frame). + + + + + + Removed In May 2017. + + jkarlin@chromium.org + + The number of frames (with parent frame of main frame) on the page. + + Only recorded if the page has at least one identified ad frame. + + + + + + Removed In July 2017. Use + PageLoad.Clients.Ads.All.Navigations.AdFrameRenavigatedToAd instead. + + jkarlin@chromium.org + + When a frame that is (or previously was) an ad frame renavigates, record + whether it renavigated to an ad frame or a non-ad frame. + + An ad frame consists of the identified ad frame and all of its children. Its + children (which may also be ads) are not counted when they renavigate. + + This metric is recorded as the event happens. Note that this is unlike most + other Clients.Ads metrics, which are recorded when the page load is + complete. + + + + + + Removed In July 2017. Use + PageLoad.Clients.Ads.All.Navigations.NonAdFrameRenavigatedToAd instead. + + jkarlin@chromium.org + + When a frame that has never been part of an ad frame renavigates, record + whether it renavigated to an ad frame or a non-ad frame. + + This metric is recorded as the event happens. Note that this is unlike most + other Clients.Ads metrics, which are recorded when the page load is + complete. + + + + + + Removed In July 2017. Use PageLoad.Clients.Ads.All.ParentExistsForSubFrame + instead. + + jkarlin@chromium.org + + Records whether or not a parent frame is found for a subframe that finishes + navigating. + + + + + + Removed In July 2017. Use + PageLoad.Clients.Ads.All.ResourceTypeWhenNoFrameFound instead. + + jkarlin@chromium.org + + Records the content::ResourceType when a resource finishes loading but the + ads metrics aren't aware of a committed frame for the resource. + + + + + + Removed March 2019 in favor of PageLoad.Clients.Ads.Resources.Bytes.Ads2. + + jkarlin@chromium.org + johnidel@chromium.org + + Total number of network bytes that went towards loading ad resources for a + single page over it's entire lifetime. This includes resources that did not + finish or were canceled. Only recorded for pages with non-zero ad bytes. + + + + + + Removed 02/2019. Replaced with + PageLoad.Clients.Ads.Bytes.MainFrame.Ads.Network. + + jkarlin@chromium.org + johnidel@chromium.org + + Total number of network bytes that were used to load top-level ad resources + on the page. This includes resources that did not finish or were canceled. + Only recorded for pages with non-zero ad bytes. + + + + + + Removed 01/19. Replaced with PageLoad.Clients.Ads.Bytes.FullPage.Network. + + jkarlin@chromium.org + johnidel@chromium.org + + Total number of network bytes that were used to load resources on the page. + This includes resources that did not finish loading or were canceled. Only + recorded for pages with non-zero ad bytes. + + + + + + Removed 04/2019 in favor of PageLoad.Experimental.Bytes.Unfinished. + + jkarlin@chromium.org + johnidel@chromium.org + + Total number of network bytes that were used to load resources that did not + finish loading on the page (e.g. ongoing video). This includes resource + loads that were canceled or resource loads that were ongoing when the page + was destroyed. Only recorded for pages with non-zero ad bytes. + + + + + + Removed 7/2019, replaced by + PageLoad.Clients.AMP.LayoutInstability.CumulativeShiftScore.Subframe + + bmcquade@chromium.org + skobes@chromium.org + + Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred + during the session, in the AMP subframe. Recorded for same-document + navigations. + + + + + + Removed 7/2019, replaced by + PageLoad.Clients.AMP.LayoutInstability.CumulativeShiftScore.Subframe.FullNavigation + + bmcquade@chromium.org + skobes@chromium.org + + Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred + during the session, in the AMP subframe. Recorded for non-same-document + navigations. + + + + + + Removed July 2019 in favor of FirstInputDelay4. + + bmcquade@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation, in an AMP subframe document. Recorded on first page + interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes + scrolls. Only same-document navigations are included. + + + + + + Removed July 2019 in favor of FirstInputDelay4. + + bmcquade@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation, in an AMP subframe document. Recorded on first page + interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes + scrolls. Only non-same-document navigations are included. + + + + + + Removed 7/2019. + + bmcquade@chromium.org + + The time from user input to largest "contentful" paint in an AMP + subframe document. Only same-document navigations are included. + + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + Will be zero or near-zero in cases where the AMP subframe document was + prerendered. + + + + + + Removed 7/2019. + + bmcquade@chromium.org + + The time from user input to largest "contentful" paint in an AMP + subframe document. Only non-same-document navigations are included. + + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + + + + + Removed 5/2019 + + bmcquade@chromium.org + Count of same document page views for AMP pages. + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + 100 times the ratio of network bytes received to network bytes the user + would have seen without data reduction proxy (not including headers) in a + page load that had its main resource loaded through data reduction proxy. + Recorded as a percent if the data reduction proxy saved the user data. + Recorded per page load when the user navigates away, hides the tab, or + backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + 100 times the ratio of network bytes received to network bytes the user + would have seen without data reduction proxy (not including headers) in a + page load that had its main resource loaded through data reduction proxy. + Recorded as a percent if the data reduction proxy saved the user data. + Recorded per page load when the user navigates away, hides the tab, or + backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the data + reduction proxy inflated for the user in a page load that had its main + resource was loaded through data reduction proxy. Recorded per page load + when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the data + reduction proxy inflated for the user in a page load that had its main + resource was loaded through data reduction proxy. Recorded per page load + when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The inflation in network kilobytes (not including headers) the user saw due + to using data reduction proxy in a page load that had its main resource was + loaded through data reduction proxy. Recorded as a percent when the user saw + inflated data. Recorded per page load when the user navigates away, hides + the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The inflation in network kilobytes (not including headers) the user saw due + to using data reduction proxy in a page load that had its main resource was + loaded through data reduction proxy. Recorded as a percent when the user saw + inflated data. Recorded per page load when the user navigates away, hides + the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes that were not fetched through the data + reduction proxy (not including headers) in a page load that had its main + resource was loaded through data reduction proxy. Recorded per page load + when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes that were not fetched through the data + reduction proxy (not including headers) in a page load that had its main + resource was loaded through data reduction proxy. Recorded per page load + when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the user would + have seen without using data reduction proxy in a page load that had its + main resource was loaded through data reduction proxy. Recorded per page + load when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the user would + have seen without using data reduction proxy in a page load that had its + main resource was loaded through data reduction proxy. Recorded per page + load when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The percent of network kilobytes (not including headers) in a page load that + went through data reduction proxy when the main resource was loaded through + data reduction proxy. Recorded per page load when the user navigates away, + hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The percent of network kilobytes (not including headers) in a page load that + went through data reduction proxy when the main resource was loaded through + data reduction proxy. Recorded per page load when the user navigates away, + hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes that were fetched through the data reduction + proxy (not including headers) in a page load that had its main resource was + loaded through data reduction proxy. Recorded per page load when the user + navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes that were fetched through the data reduction + proxy (not including headers) in a page load that had its main resource was + loaded through data reduction proxy. Recorded per page load when the user + navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the data + reduction proxy saved the user in a page load that had its main resource was + loaded through data reduction proxy. Recorded per page load when the user + navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that the data + reduction proxy saved the user in a page load that had its main resource was + loaded through data reduction proxy. Recorded per page load when the user + navigates away, hides the tab, or backgrounds the app. + + + + + + Removed 10/2018 + + bengr@chromium.org + ryansturm@chromium.org + + The percent of completed resources loaded from network in a page load that + use data reduction proxy when the main resource was loaded through data + reduction proxy. Recorded per page load when the user navigates away, hides + the tab, or backgrounds the app. + + + + + + Removed 05/2020 + + bengr@chromium.org + ryansturm@chromium.org + + Records info about the completed resources loaded from network in a page + load that use data reduction proxy when the main resource was loaded through + data reduction proxy. Recorded per page load when the user navigates away, + hides the tab, or backgrounds the app. The number of proxies, non-proxied, + percent of proxied are recorded as suffixes. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The actual delay added to page loads by DelayNavigationThrottle, for page + loads that started in the foreground and reached first paint in the + foreground. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The absolute delta between the specified and actual delays added to main + frame navigations by DelayNavigationThrottle, for page loads that started in + the foreground and reached first paint in the foreground. + + + + + + Removed March 2018 + + bmcquade@chromium.org + + The specified delay added to main frame navigations by + DelayNavigationThrottle, for page loads that started in the foreground and + reached first paint in the foreground. + + + + + + Removed in August 2020 as the behavior is launched + + xiaochengh@chromium.org + rendering-core-dev@chromium.org + + This metrics measures PageLoad.LayoutInstability.CumulativeShiftScore when + the first rendering cycle has been delayed in favor of font preloading + + + + + + Removed in August 2020 as the behavior is launched + + xiaochengh@chromium.org + rendering-core-dev@chromium.org + + This metrics measures + PageLoad.Experimental.PaintTiming.NavigationToLargestImagePaint when the + first rendering cycle has been delayed in favor of font preloading + + + + + + Removed in August 2020 as the behavior is launched + + xiaochengh@chromium.org + rendering-core-dev@chromium.org + + This metrics measures + PageLoad.Experimental.PaintTiming.NavigationToLargestTextPaint when the + first rendering cycle has been delayed in favor of font preloading + + + + + + Removed May 2018 + + mdw@chromium.org + Events related to Google CAPTCHA pages being seen by users. + + + + + Functionality removed in M77. + + bengr@chromium.org + ryansturm@chromium.org + + The number of network kilobytes (not including headers) that LoFi resources + used in a page load that had at least one LoFi resource. Recorded per page + load when the user navigates away, hides the tab, or backgrounds the app. + + + + + + Functionality removed in M77. + + bengr@chromium.org + ryansturm@chromium.org + + The number of network LoFi resources in a page load that had at least one + LoFi resource. Recorded per page load when the user navigates away, hides + the tab, or backgrounds the app. + + + + + + Removed June 2019. + + ksakamoto@chromium.org + + Records the number of tabs with inflight loading activities. Recorded when a + new page load starts. + + + + + + Removed June 2018 (M69) in favor of + PageLoad.Clients.ServiceWorker2.PageTransition. + + falken@chromium.org + + The core transition type for main frame page loads controlled by a service + worker. + + + + + + Removed May 2018 (M68) in favor of + SubresourceFilter.PageLoad.ActivationDecision + + bmcquade@chromium.org + + Records the policy decision to activate subresource filtering for a page + load. 'Activated' indicates that subresource filtering was activated. All + other reasons indicate that subresource filtering was not activated. Page + loads where subresource filtering was activated ('Activated') and at least + one subresource matched the subresource filter are counted in + PageLoad.Clients.SubresourceFilter.Count. + + + + + + Removed May 2018 (M68) in favor of + SubresourceFilter.PageLoad.NumSubresourceLoads.MatchedRules (e.g. by looking + at 0 and non-zero buckets). + + bmcquade@chromium.org + + Records 'true' for page loads where the subresource filter matched a + subresource loaded by the page. Includes dryrun matches. To compute the + percentage of total page loads affected by subresource filtering, divide by + the sum of counts for (PageLoad.ParseTiming.NavigationToParseStart + + PageLoad.ParseTiming.NavigationToParseStart.Background). + + + + + + Removed in 12/2019. + + jkarlin@chromium.org + johnidel@chromium.org + + The time from navigation start to the first contentful paint of third-party + frames on pages. Note that this can be significantly delayed due to lazy + loading. + + + + + + Removed in 01/2020. + + jkarlin@chromium.org + johnidel@chromium.org + + The time from navigation start to the first contentful paint of third-party + (third party in respect to eTLD+1) frames on pages. Note that this can be + significantly delayed due to lazy loading. + + + + + + Removed in 01/2020. + + jkarlin@chromium.org + + The number of third party origins on a page that read cookies either via + resource request headers or document.cookie. + + + + + + Removed in 01/2020. + + jkarlin@chromium.org + + The number of third party origins on a page that changed cookies either via + resource response headers or document.cookie. + + + + + + Removed in 01/2020. + + yaoxia@chromium.org + + The number of third party origins on a page that access local storage via + window.localStorage. + + + + + + Renamed to PageLoad.Clients.ThirdParty.Origins.CookieRead. + + jkarlin@chromium.org + + The number of third party origins on a page that read cookies either via + resource request headers or document.cookie. + + + + + + Removed in 01/2020. + + yaoxia@chromium.org + + The number of third party origins on a page that access session storage via + window.sessionStorage. + + + + + + Renamed to PageLoad.Clients.ThirdParty.Origins.CookieWrite. + + jkarlin@chromium.org + + The number of third party origins on a page that changed cookies either via + resource response headers or document.cookie. + + + + + + Removed in May 2018 (M69). + + csharrison@chromium.org + + The time spent parsing author style sheets before the first contentful + paint. + + + + + + Removed in May 2018 (M69). + + csharrison@chromium.org + + The sum of CSSTiming.Update and CSSTiming.Parse variants for this page load. + + + + + + Removed in May 2018 (M69). + + csharrison@chromium.org + + The time spent in Document::updateStyle before the first contentful paint. + + + + + + Removed 12/2019. Use NavigationToFirstContentfulPaint instead. + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first layout is performed, for main frame documents. + + + + + + deprecated in favor of PageLoad.Events.* + + csharrison@chromium.org + bmcquade@chromium.org + + Captures counts of various page load events. These are enumerated in the + enum page_load_metrics::PageLoadEvent, and include events like 'page load + aborted before first layout' + + + + + + Removed in favor of PageLoad.Timing2.NavigationToCommit and + PageLoad.AbortTiming. + + csharrison@chromium.org + bmcquade@chromium.org + + Captures counts of load events post-commit, on relevant page loads (i.e. + http/https, not same-page, not an error page). These events include aborts + before first layout and successful first layouts. Note that the event + 'Committed load started' when segmented by background/foreground specifies + whether the eventually committed load started in the background or + foreground, not whether we backgrounded before the actual commit event. This + is because we don't have all the data to filter relevant page loads on + provisional loads. + + + + + + Removed in favor of PageLoad.Internal.ErrorCode. + + csharrison@chromium.org + bmcquade@chromium.org + + Counts of various internal error conditions in the page_load_metrics system. + + + + + + Removed Feb 2016 in favor of PageLoad.AbortTiming and + PageLoad.Timing2.NavigationToFailedProvisionalLoad. Note that the + corresponding background enumerations are no longer being tracked in the + timing histograms. + + csharrison@chromium.org + bmcquade@chromium.org + + Captures counts of provisional load events. These include aborted, failed, + and successful (committed) provisional loads. + + + + + + Removed in favor of PageLoad.Internal.ClientRedirect.*. + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a client side redirect (Javascript navigation). + + + + + + Removed in favor of PageLoad.Experimental.Bytes.Cache2. + + jkarlin@chromium.org + + The number of prefiltered (e.g., compressed) response body KiloBytes loaded + from the cache via the browser process for a page load. Recorded when the + page load is terminated. Only recorded for complete resources. + + + + + + Removed in favor of PageLoad.Experimental.Bytes.Total2. + + jkarlin@chromium.org + + The number of prefiltered (e.g., compressed) response body KiloBytes loaded + via the browser process for a page load. Does not include any header or + overhead bytes. Recorded when the page load is terminated. Only recorded for + complete resources. + + + + + + Removed Jan 2018 + + csharrison@chromium.org + + The percent of resources loaded from cache for the given page load. Recorded + at the end of HTML parsing. + + + + + + Removed Jan 2018 + + csharrison@chromium.org + + The number of resources a given page finished loading from cache at parse + stop. + + + + + + Removed in favor of PageLoad.Experimental.CompletedResources.Cache2. + + csharrison@chromium.org + jkarlin@chromium.org + + The number of completed resources loaded from the cache via the browser + process for a page load. Recorded when the page load is terminated. + + + + + + Removed in favor of PageLoad.Experimental.CompletedResources.Total2. + + csharrison@chromium.org + jkarlin@chromium.org + + The total number of completed resources loaded via the browser process for a + page load. Recorded when the page load is terminated. + + + + + + Removed 7/2019, replaced by PageLoad.LayoutInstability.CumulativeShiftScore + + bmcquade@chromium.org + skobes@chromium.org + + Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred + on the page (including all subframes) during the session. + + + + + + Removed 7/2019, replaced by + PageLoad.LayoutInstability.CumulativeShiftScore.MainFrame + + bmcquade@chromium.org + skobes@chromium.org + + Measures the amount of layout jank (bit.ly/lsm-explainer) that has occurred + in the main frame during the session. + + + + + + Removed 1/2020. + + dproy@chromium.org + tdresser@chromium.org + + Measures Time to Interactive, a metric based on main thread and network + heuristics to approximate the point in time when the page feels interactive + to the user. See https://goo.gl/TFw6xz for detailed explanation. This + histogram uses First Meaningful Paint as the lower bound for quiescent + windows. + + + + + + Removed in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint. + + bmcquade@chromium.org + + Measures the total time the page load was active after first paint, up until + being backgrounded, prior to the page load terminating. Recorded only for + page loads that started in the foreground. + + + + + + Removed in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint. + + bmcquade@chromium.org + + Measures the total time the page load was active after first paint, for page + loads that spend the entire time in the foreground. + + + + + + Removed in favor of PageLoad.PageTiming.ForegroundDuration. + + bmcquade@chromium.org + + Measures the total time the page load was active, up until being + backgrounded, for page loads that started in the foreground. + + + + + + Removed in favor of PageLoad.PageTiming.ForegroundDuration. + + bmcquade@chromium.org + + Measures the total time the page load was active, for page loads that spend + the entire time in the foreground. + + + + + + Removed in favor of + PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2. + + ksakamoto@chromium.org + + Whether the user had any interaction on the page (except mouse move) after + first paint, and whether the user left the page before network stable or + not. + + + + + + Removed as of 05/17/2017. + + ksakamoto@chromium.org + + Whether the user had any interaction on the page (except mouse move) after + first paint, and whether the user left the page before network stable or + not. Not logged if page load was aborted before first paint. + + + + + + Removed as of 05/17/2017. + + ksakamoto@chromium.org + + Measures the time between when the first meaningful paint + (http://bit.ly/ttfmp-doc) was computed to have happened, and when we + actually logged the metric. + + This metric is useful in helping us tweak when FirstMeaningfulPaintDetector + should stop observing layout operations. + + + + + + Removed in Sep 2020. + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from a background tab being switched to the foreground to + the time the first meaningful paint is performed, for main frame documents. + + + + + + Removed 7/2019, replaced by + PageLoad.PaintTiming.LargestContentfulPaint.ContentType + + maxlg@chromium.org + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest content paint, whose timestamp is measured by + PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaintAllFrames, + comes from text or image. This value is recorded whenever + PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaintAllFrames + is recorded. + + + + + + Removed 7/2019, replaced by + PageLoad.PaintTiming.LargestContentfulPaint.MainFrame.ContentType + + maxlg@chromium.org + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest content paint, whose timestamp is measured by + PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaint, comes + from text or image. This value is recorded whenever + PageLoad.Experimental.PaintTiming.NavigationToLargestContentPaint is + recorded. + + + + + + Removed 7/2019, replaced by + PageLoad.PaintTiming.NavigationToLargestContentfulPaint.MainFrame + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, for main frame documents. + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + + + + + Removed 7/2019, replaced by + PageLoad.PaintTiming.NavigationToLargestContentfulPaint + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, for main frame documents. + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. Compared with NavigationToLargestContentPaint, this is the + aggregate results from all frames, while NavigationToLargestContentPaint is + only for main frame. See http://bit.ly/fcp_plus_plus for details. + + + + + + Removed Mar 2020 in favor of + PageLoad.PaintTiming.NavigationToLargestContentfulPaint. + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest image is first painted after fully loaded, for main frame documents. + The value is recorded at the end of each page load. See + http://bit.ly/fcp_plus_plus for details. + + + + + + Removed Mar 2020 in favor of + PageLoad.PaintTiming.NavigationToLargestContentfulPaint. + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest text is first painted, for main frame documents. The value is + recorded at the end of each page load. See http://bit.ly/fcp_plus_plus for + details. + + + + + + Removed Mar 2019 + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + last image is first painted after fully loaded, for main frame documents. + The value is recorded at the end of each page load. See + http://bit.ly/fcp_plus_plus for details. + + + + + + Removed Mar 2019 + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + last text is first painted, for main frame documents. The value is recorded + at the end of each page load. The value is recorded at the end of each page + load. See http://bit.ly/fcp_plus_plus for details. + + + + + + Removed Jan 2018 + + csharrison@chromium.org + + The parse duration of the page load where 0-50% of all subresources (loaded + during parsing) were served from the HTTP cache (including 304s). + + + + + + Removed Jan 2018 + + csharrison@chromium.org + + The parse duration of the page load where 51-100% of all subresources + (loaded during parsing) were served from the HTTP cache (including 304s). + + + + + + Renamed to + PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.FirstMeaningfulPaintOrdering + + ksakamoto@chromium.org + + Whether the two variants of First Meaningful Paint reported different + values, and if so, which one was reported first. + + + + + + Renamed to + PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.HadNetworkQuiet + + ksakamoto@chromium.org + + Recorded when the page load reached network 0-quiet (no active network + connection for 0.5 seconds), or network 2-quiet (no more than 2 active + network connections for 2 seconds). + PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2 + histogram gives the fraction of page loads that had network 2-quiet, so it + can be used as a baseline. + + + + + + Removed 1/2020. + + tdresser@chromium.org + dproy@chromium.org + + Records whether the Time To Interactive metric was reported for the page + load, or why it wasn't if not. See https://goo.gl/TFw6xz for definition of + Time to Interactive. + + + + + + Removed Jan 2018 + + csharrison@chromium.org + + The number of resources a given page finished loading at parse stop. + + + + + + Removed April 2018, replaced by OriginStatus. + + ericrobinson@chromium.org + + For each identified ad frame, whether the origin of the ad matches the + origin of the main frame. + + An ad frame consists of the identified ad frame and all of its children + (which may also be ads, but are counted as part of the ancestor ad frame). + Frames of zero bytes (e.g., never had a document or their document was + doc.written and no sub-resources were loaded) are not counted. + + + + + + Removed July 2019 in Issue 962616. + + johnidel@chromium.org + jkarlin@chromium.org + + Whether or not the ad frame would have triggered the Adframe size + intervention. This is determined by checking if a frame does not have a user + gesture when its size exceeds 1050 kilobytes. Only recorded for ad frames + with non-zero total bytes. Recorded for each frame when the page is + destroyed or navigated. + + + + + + Removed July 2019 in Issue 962616. + + johnidel@chromium.org + jkarlin@chromium.org + + Whether or not the ad frame that would have triggered the Adframe size + intervention had media playing at any point in its lifetime. An adframe will + trigger the intervention if it does not have a user gesture when its size + exceeds 1050 kilobytes. Recorded for each offending frame when the page is + destroyed or navigated. + + + + + + Removed 01/2020. Available in UKM via AdFrameLoad.Visibility.FrameHeight and + AdFrameLoad.Visibility.FrameWidth. + + johnidel@chromium.org + jkarlin@chromium.org + + The smallest dimension of a root ad frame in pixels. Only recorded for ad + frames with non-zero total bytes. Recorded when the page is destroyed or + navigated. Display none iframes will not always update their size because + they lack a content view. This uses the last size of frame before it was set + to display: none. + + + + + + Removed 09/2019 in favor of PageLoad.FrameCounts.AdFrames.Total. + + jkarlin@chromium.org + + The number of frames on the page that have loaded more than 0 bytes of + content. + + For pages with zero ad frames, the other PageLoad.Clients.Ads metrics are + not recorded unless otherwise specified. + + Child frames of an ad frame are not included in the count. + + + + + + Removed 09/2018 in favor of PageLoad.HeavyAds.ComputedType2. + + johnidel@chromium.org + jkarlin@chromium.org + + Records heavy ad type for each ad frame, as determined by the first + threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of + feature flag or other conditions that prevent the heavy ad intervention from + occuring. Recored for all ad frames with non-zero bytes. Recorded when the + ad frame destroyed or when the page is destroyed. + + + + + + Removed 09/2018 in favor of PageLoad.HeavyAds.InterventionType2. + + johnidel@chromium.org + jkarlin@chromium.org + + Records the type of heavy ad unloaded by the heavy ad intervention. Heavy ad + type is determined by the first threshold hit. This is not recorded for ad + frames that are considered heavy but did not fufill other criteria for the + intervention. This includes the feature being enabled and being below the + per-origin intervention cap. + + + + + + Removed on January 2019 in favor of + PageLoad.InteractiveTiming.FirstInputDelay2 which correctly excludes some + scrolling cases that were previously not excluded from this metric. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation. See https://goo.gl/tr1oTZ for a detailed explanation. + In ms. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + + Removed January 2020 as the SkipTouchFilter experiment is completed. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + This metric will be used to compare first inputs during the + SkipTouchEventFilter experiment. + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation. Recorded on first page interaction. See + https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + + + + + Removed on February 2019 in favor of + PageLoad.InteractiveTiming.FirstInputDelay3 which brings the metric more in + line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation. Recorded on first page interaction. See + https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + + Removed in July 2019 in favor of PageLoad.InteractiveTiming.FirstInputDelay4 + which includes input events which were filtered previously. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation. Recorded on first page interaction. See + https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + + Removed on January 2019 in favor of + PageLoad.InteractiveTiming.FirstInputTimestamp2 which correctly excludes + some scrolling cases that were previously not excluded from this metric. + + tdresser@chromium.org + + The duration between navigation start and the hardware timestamp of the + first meaningful input per navigation. See https://goo.gl/tr1oTZ for a + detailed explanation. In ms. + + + + + + Removed January 2020 as the SkipTouchFilter experiment is completed. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + This metric will be used to compare first inputs during the + SkipTouchEventFilter experiment. + + The duration between navigation start and the hardware timestamp of the + first meaningful input per navigation. Recorded on first page interaction. + See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + + + + + Removed on February 2019 in favor of + PageLoad.InteractiveTiming.FirstInputTimestamp3 which brings the metric more + in line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + first meaningful input per navigation. Recorded on first page interaction. + See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + + + + + Removed in July 2019 in favor of + PageLoad.InteractiveTiming.FirstInputTimestamp4 which includes input events + which were filtered previously. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + first meaningful input per navigation. Recorded on first page interaction. + See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + + + + + Removed on January 2019 in favor of PageLoad.InteractiveTiming.InputDelay2 + which correctly excludes some scrolling cases that were previously not + excluded from this metric. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between the hardware timestamp and the start of event + processing on the main thread for a meaningful input. In ms. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + + Removed on February 2019 in favor of PageLoad.InteractiveTiming.InputDelay3 + which brings the metric more in line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between the hardware timestamp and the start of event + processing on the main thread for a meaningful input. Excludes scrolls. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + + Removed on January 2019 in favor of + PageLoad.InteractiveTiming.InputTimestamp2 which correctly excludes some + scrolling cases that were previously not excluded from this metric. + + tdresser@chromium.org + + The duration between navigation start and the hardware timestamp of a + meaningful input. In ms. + + + + + + Removed on February 2019 in favor of + PageLoad.InteractiveTiming.InputTimestamp3 which brings the metric more in + line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of a + meaningful input. Excludes scrolls. + + + + + + Removed on January 2019 in favor of + PageLoad.InteractiveTiming.LongestInputDelay2 which correctly excludes some + scrolling cases that were previously not excluded from this metric. + + tdresser@chromium.org + + Measures longest Input Delay, the longest duration between the hardware + timestamp and the start of event processing on the main thread for the + meaningful input per navigation. In ms. + + + + + + Removed on February 2019 in favor of + PageLoad.InteractiveTiming.LongestInputDelay3 which brings the metric more + in line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures longest Input Delay, the longest duration between the hardware + timestamp and the start of event processing on the main thread for the + meaningful input per navigation. Excludes scrolls. + + + + + + Removed in October 2019 in favor of LongestInputDelay4, which updates naming + to be consistent with LongestInput UKM. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures longest Input Delay, the longest duration between the hardware + timestamp and the start of event processing on the main thread for the + meaningful input per navigation. Excludes scrolls. + + + + + + Removed on January 2019 in favor of + PageLoad.InteractiveTiming.LongestInputTimestamp2 which correctly excludes + some scrolling cases that were previously not excluded from this metric. + + tdresser@chromium.org + + The duration between navigation start and the hardware timestamp of the + meaningful input with longest queuing delay per navigation. In ms. + + + + + + Removed on February 2019 in favor of + PageLoad.InteractiveTiming.LongestInputTimestamp3 which brings the metric + more in line with the EventTiming API. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + meaningful input with longest queuing delay per navigation. Excludes + scrolls. + + + + + + Removed in October 2019 in favor of LongestInputTimestamp4, which updates + naming to be consistend with LongestInput UKMs. + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + meaningful input with longest queuing delay per navigation. Excludes + scrolls. + + + + + + Removed in favor of PageLoad.Internal.ClientRedirect.FirstPaintToNavigation + and PageLoad.Internal.ClientRedirect.NavigationWithoutPaint. + + bmcquade@chromium.org + + The delay between first paint and a client-side redirection. This metric is + only intended to help in choosing a heuristic delay to distinguish between + client-side redirects and other client initiated navigations, and will be + deprecated in M54. Please contact bmcquade@chromium.org before using this + metric. + + + + + + Removed on 10/14/2016. No longer needed. + + bmcquade@chromium.org + + The delay between commit and completion, for page loads that did not receive + any timing IPCs. This metric is only intended to help understand the cases + where committed page loads don't receive timing IPCs. Please contact + bmcquade@chromium.org before using this metric. + + + + + + Removed 1/2020. + + dproy@chromium.org + tdresser@chromium.org + + Measures time delta between Time to Interactive and when we can detect TTI. + TTI cannot be detected in real time - we have to wait sufficiently long to + determine main thread and network quiescence. See https://goo.gl/TFw6xz for + detailed explanation of Time to Interactive. This histogram uses First + Meaningful Paint as the lower bound for quiescent windows. + + + + + + Removed July 2019. + + ksakamoto@chromium.org + + Whether the user had any interaction on the page before + FirstMeaningfulPaint. Recorded when the page load reaches network idle. + + + + + + Removed July 2019. + + ksakamoto@chromium.org + + Whether the two variants of First Meaningful Paint reported different + values, and if so, which one was reported first. + + + + + + Removed July 2019. + + ksakamoto@chromium.org + + Recorded when the page load reached network 0-quiet (no active network + connection for 0.5 seconds), or network 2-quiet (no more than 2 active + network connections for 2 seconds). + PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2 + histogram gives the fraction of page loads that had network 2-quiet, so it + can be used as a baseline. + + + + + + deprecated May 2018: The swap-timestamp comes from a different process, and + comparing that with the paint-time (which is from the local process) does + not produce a reliable metric. + + panicker@chromium.org + + Records the delta between the renderer timestamp and swap timestamp for + first paint, first contentful paint, first meaningful paint, first text + paint, and first image paint. The renderer timestamp is recorded on the + Paint path, while the swap timestamp is the result of a CC SwapPromise + (queued on the Paint path) either being successfully fulfilled, or broken in + cases where the swap did not occur. As we switch to using the swap + timestamps in place of their renderer counterparts, this metric allows us to + see the discrepancies between the two timestamps. + + + + + + Removed in 07/2020 due to misspelling. Use + PageLoad.LayoutInstability.CumulativeShiftScore.AfterBackForwardCacheRestore + instead. + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Measures the cumulative layout shift score (bit.ly/3fQz29y) that has + occurred on the page (including all subframes) after the page is restored + from the back-forward cache. Recorded when the user navigates away or closes + the page after the page was restored from back-forward cache. + + + + + + Removed in 07/2020 due to misspelling. Use + PageLoad.LayoutInstability.CumulativeShiftScore.MainFrame.AfterBackForwardCacheRestore + instead. + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Measures the cumulative layout shift score (bit.ly/3fQz29y) that has + occurred in the main frame after the page is restored from the back-forward + cache. Recorded when the user navigates away or closes the page after the + page was restored from back-forward cache. + + + + + + Discontinued Nov 2018 because data is no longer being used. + + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first non-blank text is painted, for main frame documents. + + + + + + deprecated in favor of PageLoad.Timing2.* + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + DOMContentLoaded event is fired, for main frame documents. + + + + + + deprecated in favor of PageLoad.Timing2.* + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first layout is performed, for main frame documents. + + + + + + deprecated in favor of PageLoad.Timing2.* + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + load event is fired, for main frame documents. + + + + + + deprecated in favor of PageLoad.DocumentTiming.ParseDuration + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from when DOM loading occurs (the time that HTML parsing + begins) to the time the DOMContentLoaded event is fired, for main frame + documents. This is equivalent to the time that the HTML document resource + was being parsed. + + + + + + deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from when DOM loading occurs (the time that HTML parsing + begins) to first "contentful" paint. + + + + + + deprecated in favor of PageLoad.PaintTiming.ForegroundToFirstPaint + + pkotwicz@chromium.org + + Measures the time from a background tab being switched to the foreground to + the time the first paint is performed, for main frame documents. + + + + + + Removed in favor of PageLoad.ParseTiming.NavigationToParseStart + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + navigation committed, for main frame documents. + + + + + + deprecated in favor of + PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + DOMContentLoaded event is fired, for main frame documents. This metric is + being phased out in favor of the PageLoad.DocumentTiming equivalent and will + be deprecated in M54. + + + + + + deprecated in favor of PageLoad.PageTiming.NavigationToFailedProvisionalLoad + + bmcquade@chromium.org + shivanisha@chromium.org + + Measures the time from navigation timing's navigation start to the time the + provisional load failed. Only measures provisional loads that failed in the + foreground. + + + + + + deprecated in favor of PageLoad.AbortTiming.Background.* + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + user first backgrounds the tab. Only measures navigations that started in + the foreground. + + + + + + deprecated in favor of PageLoad.PaintTiming.NavigationToFirstContentfulPaint + + ksakamoto@chromium.org + + The time from navigation start to first "contentful" paint. This + metric is being phased out in favor of the PageLoad.PaintTiming equivalent + and will be deprecated in M54. + + + + + + deprecated in favor of PageLoad.PageTiming.NavigationToFirstForeground + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + user first foregrounds an initially backgrounded tab. Only measures + navigations that started in the background. + + + + + + deprecated in favor of PageLoad.PaintTiming.NavigationToFirstImagePaint + + ksakamoto@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first image is painted, for main frame documents. For images that render + progressively, this is recorded as soon as any image pixels have been drawn. + This metric is being phased out in favor of the PageLoad.PaintTiming + equivalent and will be deprecated in M54. + + + + + + deprecated in favor of PageLoad.DocumentTiming.NavigationToFirstLayout + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first layout is performed, for main frame documents. This metric is being + phased out in favor of the PageLoad.DocumentTiming equivalent and will be + deprecated in M54. + + + + + + deprecated in favor of PageLoad.PaintTiming.NavigationToFirstPaint + + ksakamoto@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first paint is performed, for main frame documents. This metric is being + phased out in favor of the PageLoad.PaintTiming equivalent and will be + deprecated in M54. + + + + + + deprecated in favor of PageLoad.PaintTiming.NavigationToFirstTextPaint + + ksakamoto@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first non-blank text is painted, for main frame documents. This metric is + being phased out in favor of the PageLoad.PaintTiming equivalent and will be + deprecated in M54. + + + + + + deprecated in favor of PageLoad.DocumentTiming.NavigationToLoadEventFired + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + load event is fired, for main frame documents. This metric is being phased + out in favor of the PageLoad.DocumentTiming equivalent and will be + deprecated in M54. + + + + + + deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts, + for main frame documents that started parsing. + + + + + + deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts, + for main frame documents that finished parsing. This metric is being phased + out in favor of the PageLoad.ParseTiming equivalent and will be deprecated + in M54. + + + + + + deprecated in favor of + PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts + inserted from document.write, for main frame documents that started parsing. + + + + + + deprecated in favor of + PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts + inserted from document.write, for main frame documents that finished + parsing. This metric is being phased out in favor of the + PageLoad.ParseTiming equivalent and will be deprecated in M54. + + + + + + deprecated in favor of PageLoad.ParseTiming.ParseDuration + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser was active, for main frame documents + that finished parsing. This metric is being phased out in favor of the + PageLoad.ParseTiming equivalent and will be deprecated in M54. + + + + + + deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from when the HTML parser started, to when the page first + paints content. This metric is being phased out in favor of the + PageLoad.PaintTiming equivalent and will be deprecated in M54. + + + + + + Removed 6/2019. No longer used. + + jianli@chromium.org + offline-dev@chromium.org + + Recorded when the popup overlays are removed from MHTML serialization. + + + + + + Replaced by PaintHolding.CommitTrigger2 in M-79 + + schenney@chromium.org + paint-dev@chromium.org + + Records the reason that a commit was triggered, to enable research into + which event (non-same-origin, FCP, timeout, etc) led to the first commit. + + + + + + Replaced with PaintHolding.InputTiming2 in M-79. + + schenney@chromium.org + paint-dev@chromium.org + + Records whether or not input arrived before the first commit. + + + + + + Removed Aug 2017 + + csharrison@chromium.org + + The delay from when bytes are received on the main thread to when the + BackgroundHTMLParser starts tokenizing them. Always a shorter time than the + time emitted to Parser.PreloadTokenizeDelay. + + + + + + Removed May 2017 + + csharrison@chromium.org + + The time it takes to enqueue a ParsedChunk onto the shared parser queue. + + + + + + Removed Feb 2020 + + csharrison@chromium.org + + The number of speculative tokens discarded by the parser when a rewind is + needed. + + + + + + Removed Aug 2017 + + csharrison@chromium.org + + The maximum number of pending Chunks in the ParsedChunkQueue after the + parser is detached. + + + + + + Removed Aug 2017 + + csharrison@chromium.org + + The maximum number of pending tokens in the ParsedChunkQueue after the + parser is detached. + + + + + + Removed May 2017 + + csharrison@chromium.org + + The delay from when bytes are received on the main thread to when they are + tokenized and preloads are sent back to the main parser. Always a greater + time than the time emitted to Parser.AppendBytesDelay. + + + + + + Removed as of 07/2019. Use Memory.Renderer.* and + Memory.Experimental.Renderer2.* instead. + + haraken@chromium.org + + The committed memory size in PartitionAlloc. The value is reported when we + see the highest memory usage we've ever seen in the renderer process. + + + + + + Removed 2017-12 by PartnerBookmark.Count2. + + wychen@chromium.org + + The number of partner bookmark entries. Note that zero would be + under-represented because reading is throttled if the last result is zero. + Logged when using the bookmark, not skipped (PartnerBookmark.Skipped == + False), and at most once per cold start. Note that the distribution is + weighted by bookmark usage. + + + + + + No longer recorded as of Apr 2018 + + wychen@chromium.org + + Whether there's no partner bookmark provider. By default, the system image + contains a dummy partner bookmarks provider that provides zero entries. + Logged when using the bookmark, not skipped (PartnerBookmark.Skipped == + False), and at most once per cold start. + + + + + + No longer recorded as of Apr 2018 + + wychen@chromium.org + + Whether reading of partner bookmark is skipped. Logged when using the + bookmark, and at most once per cold start. + + + + + + Removed 2017-12. Use PartnerBookmark.TimeSinceLastEmptyRead2. + + wychen@chromium.org + + When trying to load the partner bookmarks, if no partner bookmark is read + last time, record the time elapsed since then. It is recorded no matter + whether loading would be skipped. + + + + + + No longer recorded as of Apr 2018 + + wychen@chromium.org + + When trying to load the partner bookmarks, if no partner bookmark is read + last time, record the time elapsed since then. It is recorded no matter + whether loading would be skipped. + + + + + + Removed 2019-07. See crbug.com/975263 for wrap-up analysis. + + tedchoc@chromium.org + wychen@chromium.org + + Number of elements read from the partner bookmarks favicon cache, recorded + once per cold start when reading partner bookmarks. Only recorded on + Android. + + + + + + Removed 2020-04. + + vasilii@chromium.org + jdoerrie@chromium.org + + Records whether there is a username conflict with existing credentials when + the user clicks 'Generate Password'. + + + + + + Removed 10/2018 in favor of PasswordGeneration.UserDecision. + + ioanap@chromium.org + vasilii@chromium.org + + Records user-triggered events related to a generated password. Each event is + logged at most once per lifetime of the generated password. + + + + + + Removed July 2019. + + alexmos@chromium.org + battre@chromium.org + + Records attempts to submit a password on a form in an about:blank frame, + indicating whether this attempt is for a main frame or subframe. Recorded + once per form submission. + + + + + + Removed as of Chrome 56. See the histograms for one and more accounts. + + vasilii@chromium.org + The dismissal reason of the account chooser. + + + + + Removed as of 06/19. + + vasilii@chromium.org + The number of accounts displayed in the account chooser. + + + + + Removed as of 06/19. + + vasilii@chromium.org + + The count of the placeholder avatars shown in the account chooser. + + + + + + Removed as of 06/19. + + vasilii@chromium.org + + Whether the account chooser includes an empty username or any duplicates + + + + + + Removed in M79 in favor of PasswordManager.AccountsPerSiteHiRes. + + dvadym@chromium.org + vasilii@chromium.org + + The number of accounts stored per site in the password manager (one event + per site) + + + + + + Removed 2020/02 because it's unused. + + dvadym@chromium.org + engedy@chromium.org + vasilii@chromium.org + + Records, for each account, the number of other accounts (across all sites + and usernames) that reuse the same password. Only non-blacklisted, + HTML-form-based accounts are considered. + + For each account, samples will only be recorded into the histograms that + have the first suffix corresponding to whether that account was saved on a + secure website or not. The second suffix is used to further categorize the + other accounts that reuse the same password based on how they relate to the + account in question, and whether they are secure. The number of other + accounts in each category will be reported into histogram with the + respective second suffixes. + + Metrics are collected once per browser start-up. In case of multiple + profiles, the counts are for the profile for which a WebContents is first + created. + + + + + + Removed as of Chrome 32. See PasswordManagerActionsTakenWithPsl + + + Stats documenting how we handle every form containing a password, bucketed + by the actions taken. + + + + + + Removed as of 12/10/2019. + + estark@chromium.org + + Stats documenting how we handle every form containing a password on a + non-secure page, bucketed by the actions taken. + + + + + + Removed as of 12/10/2019. + + dvadym@chromium.org + vasilii@chromium.org + + Stats documenting how we handle every form containing a password, bucketed + by the actions taken. + + + + + + Removed as of 3/18/2014. See PasswordManagerActionsTakenV3. + + yfriedman@chromium.org + + Stats documenting how we handle every form containing a password, bucketed + by the actions taken. + + + + + + No longer recorded as of May 2015. + + engedy@chromium.org + + The number of facets affiliated with a dummy Web facet, according to the + affiliation information retrieved from the cache. Recorded for each dummy + Web facet, once shortly after start-up, and then periodically every hour; + but only if getting affiliations succeeded for the Web facet. + + + + + + No longer recorded as of May 2015. + + engedy@chromium.org + + Whether or not affiliations of a dummy Web facet could be successfully + retrieved from the cache. Recorded for each dummy Web facet, once shortly + after start-up, and then periodically every hour. + + + + + + The bubble isn't shown anymore. Become obsolete in Feb. 2015. + + melandory@chromium.org + vasilii@chromium.org + Why was "Allow to collect URL?" bubble closed? + + + + + No longer recorded as of June 2019. + + fhorschig@chromium.org + vasilii@chromium.org + + Records what happened to the progress bar during exporting passwords when + its dismissal was requested. + + + + + + No longer recorded as of June 2019. + + fhorschig@chromium.org + + Records whether a user triggered the search function while visiting the + password preferences page on Android. + + + + + + Removed February 2019. + + gcasto@chromium.org + + If the password manager UI was suppressed because generation UI was already + being displayed for the same field. + + + + + + Corresponding clean-up logic got introduced in M70 and has run its course. + + jdoerrie@chromium.org + + The number of duplicates forms from the password store. Recorded once for + the profile on startup. + + + + + + Removed in M76 in favor of PasswordManager.BlacklistedSitesHiRes. + + jdoerrie@chromium.org + vasilii@chromium.org + + The total number of sites that the user has blacklisted in the password + manager's profile-scoped store. Recorded by iterating over stored passwords + once per run of Chrome. + + + + + + Corresponding clean-up logic got introduced in M76 and has run its course. + + jdoerrie@chromium.org + vasilii@chromium.org + + Records once on startup whether the blacklisted sites in the password store + need to be normalized. + + + + + + Corresponding clean-up logic got introduced in M70 and has run its course. + + jdoerrie@chromium.org + vasilii@chromium.org + + Records once on startup whether the blacklisted sites in the password store + need to be cleared of duplications. + + + + + + Removed August 2018. + + vasilii@chromium.org + + Records once on startup whether the blacklisted sites in the password store + need to be updated to remove username/password. Can be removed around Chrome + M69 (https://crbug.com/817754). + + + + + + Removed April 2019. + + jdoerrie@chromium.org + vasilii@chromium.org + + Boolean indicating whether adding a blacklist entry was prevented due to an + already existing entry. Recorded after every blacklist site submission. + + + + + + Removed as of 07/2020. + + battre@chromium.org + vasilii@chromium.org + + The number of accounts that do not trigger password save prompts anymore. + The count is recorded once per browser start-up. (In case of multiple + profiles, the counts are for the profile that first has a WebContents + created.) + + + + + + Removed as of 07/2020. + + battre@chromium.org + vasilii@chromium.org + + The number of domains for which at least one account exists that does not + trigger password save prompts anymore. The count is recorded once per + browser start-up. (In case of multiple profiles, the counts are for the + profile that first has a WebContents created.) + + + + + + Removed as of 06/2020. + + vasilii@chromium.org + + Records the result of removing passwords that cannot be decrypted when + retrieving passwords from LoginDatabase. Called for Mac users for each + profile. + + + + + + Removed as of 06/2019. + + msramek@chromium.org + vasilii@chromium.org + + When parsing a password form, and no username field is detected, whether + this was a password change form. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + When offering to save a password, whether the username is empty. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + When parsing a password form, whether a username field is detected. + + + + + + Removed as of 09/2018. The investigation this metric was supporting has been + concluded in 2016. + + msramek@chromium.org + vasilii@chromium.org + + The number of password fields for password forms that do not have a username + field. This is recorded every time such a password form is successfully + parsed. Note that the parsing is attempted when the form is encountered (i.e + when the document is loaded) and also when it is submitted. + + + + + + Removed as of 09/2018. The investigation this metric was supporting has been + concluded in 2016. + + msramek@chromium.org + vasilii@chromium.org + + The total number of text and password fields for password forms that do not + have a username field. This is recorded every time such a password form is + successfully parsed. Note that the parsing is attempted when the form is + encountered (i.e when the document is loaded) and also when it is submitted. + + + + + + Removed as of 06/2019. + + msramek@chromium.org + vasilii@chromium.org + + Number of password forms with empty username in the Login Database for which + there is not another password form from the same realm with a nonempty + username. In other words, number of password forms with empty username which + we do not suspect to be reauthentication forms. + + + + + + Removed as of 2019/07. Password exporting has been rolled out. + + cfroussios@chromium.org + ioanap@chromium.org + vasilii@chromium.org + The number of passwords exported in CSV format per user. + + + + + Removed as of 2019/07. Password exporting has been rolled out. + + cfroussios@chromium.org + ioanap@chromium.org + vasilii@chromium.org + The success or error type of exporting passwords into CSV. + + + + + Removed as of 05/2017. This metric has been replaced by + PasswordManager.MediationOptional. + + vasilii@chromium.org + + Tracks result of navigator.credentials.get() with unmediated=false. That is + the result of account chooser. + + + + + + Removed as of 05/2017. This metric has been replaced by + PasswordManager.MediationSilent. + + vasilii@chromium.org + + Tracks result of navigator.credentials.get() with unmediated=true. That is + the result of auto sign-in. + + + + + + Removed as of M72. Superseded by PasswordManager.HttpCredentials. + + gemene@google.com + jdoerrie@chromium.org + + Number of HTTP credentials, with HSTS enabled as given in the histogram + suffix, for which a conflicting (i.e.same host and username, but different + password) HTTPS credential exists. Recorded once for the profile on startup. + + + + + + Removed as of M72. Superseded by PasswordManager.HttpCredentials. + + gemene@google.com + jdoerrie@chromium.org + + Number of HTTP credentials, with HSTS enabled as given in the histogram + suffix, for which an equivalent (i.e. same host, username and password) + HTTPS credential exists. Recorded once for the profile on startup. + + + + + + Removed as of M72. Superseded by PasswordManager.HttpCredentials. + + gemene@google.com + jdoerrie@chromium.org + + Number of HTTP credential, with HSTS enabled as given in the histogram + suffix, for which no HTTPS credential for the same username exists. Recorded + once for the profile on startup. + + + + + + Removed as of 07/2018. This metric was deleted at + https://chromium-review.googlesource.com/c/chromium/src/+/1131495. + + + The result of importing passwords stored in IE7 into Chrome's password + store. + + + + + + Removed as of 03/2016. This metric has been replaced by + PasswordManager.UIDismissalReason. + + + The distribution of responses to the "Do you want Chrome to remember + this password"? info bar prompt. + + + + + + Corresponding clean-up logic got introduced in M71 and has run its course. + + jdoerrie@chromium.org + vasilii@chromium.org + + Records once on startup whether forms with wrong signon_realm created by + HTTP to HTTPS migration need to be removed. See https://crbug.com/881731 for + more details. + + + + + + Removed as of 09/2016. + + vasilii@chromium.org + + After migration from the Mac Keychain fails, records the number of passwords + in the Keychain owned by Chrome but not accessible by it. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + After migration from the Mac Keychain fails, records the number of passwords + in the Chrome Password Manager database for which the corresponding values + in the Keychain are not accessible by Chrome. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + After migration from the Mac Keychain fails, records the number of passwords + in the Chrome Password Manager database to be migrated. As there is no + partial migration, it's the total number of passwords in the DB. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + The status of passwords migration from the Keychain. It's recorded shortly + after startup. + + + + + + Removed as of 07/2019. + + dvadym@chromium.org + cfroussios@chromium.org + + The success or failure of deserializing PasswordForms in KWallet. Failure + either indicates corrupted data or the presense of bugs in the + deserialization code. + + + + + + Removed as of Sept 2020. + + cfroussios@chromium.org + jdoerrie@chromium.org + + Whether the password store has been migrated to an encrypted login database. + This is recorded on startup, before any migration attempts. + + + + + + Removed as of Sept 2020. + + cfroussios@chromium.org + jdoerrie@chromium.org + + Whether the password store has been migrated to an encrypted login database. + This is recorded at the end of a migration attempt. + + + + + + Removed 02/2020. + + cfroussios@chromium.org + dvadym@chromium.org + + The time it took to read credentials from the native backend and write them + into the encrypted login database. This is logged once per migration + (normally once per client), at the end of copying into the database. The + migration is triggered on the first operation to the password store. + + + + + + Removed 10/2019. + + cfroussios@chromium.org + dvadym@chromium.org + + The time it took to read credentials from the unencrypted login database and + insert them into the native backend. This is logged once per migration + (normally once per client), at the end of copying into the backend. The + migration is triggered on the first operation to the password store. + + + + + + Removed 07/2019. + + cfroussios@chromium.org + dvadym@chromium.org + + Information about usage of password storage backends on Linux. It also + includes whether a command line flag for a specific backend is given. + + + + + + Removed 06/2019. + + vasilii@chromium.org + + The version of LoginDatabase if the migration to a new one failed. + + + + + + Removed 03/2018 in favor of PasswordManager.UpdateUIDismissalReason. + + dvadym@chromium.org + + A user action when a password update bubble with multiple accounts is shown. + + + + + + Removed as of 09/2020. + + jdoerrie@chromium.org + kazinova@google.com + + Records the number of password forms extracted by PasswordFormHelper at the + moment of submission. This metric is needed to check the assumption that + received and parsed message contains only one form at a a time. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + Number of passwords deleted when the user chooses to clear passwords via the + clear browsing data UI. + + + + + + Removed as of 06/2019. + + vasilii@chromium.org + + Number of passwords deleted when browsing data is cleared during rollback. + + + + + + Removed as of 08/2015. + + + When the user chooses to never remember passwords for a form, we remove all + previously saved credentials for that form. This is the count of those + credentials. + + + + + + Removed as of 04/2020. + + achulkov@google.com + ioanap@chromium.org + + Result of the combined saving flow consisting of the potentially shown + onboarding dialog and the save infobar. Recorded when the user is prompted + to save their password. + + + + + + Removed as of 04/2020. + + achulkov@google.com + ioanap@chromium.org + + Result of the combined saving flow consisting of the shown onboarding dialog + and the save infobar. Recorded when the user is propmpted to save their + password only if the onboarding was actually shown. + + + + + + Removed as of 04/2020. + + achulkov@google.com + ioanap@chromium.org + + The current state of showing the password manager onboarding to the user. + Recorded on startup. + + + + + + Removed as of 04/2020. + + achulkov@google.com + ioanap@chromium.org + + Reason of dismissal of the password manager onboarding dialog. Recorded when + the user is propmpted to save their password and the dialog is shown. + + + + + + Removed as of May 17 2017. Replaced by + PasswordProtection.RequestOutcome.ProtectedPasswordEntry. + + dvadym@chromium.org + chrome-safebrowsing-alerts@google.com + + A password reuse is an event when the user typed a string that is equal to a + saved password on another domain, and this saved password is called reused + password. + + This metric shows whether a password reuse happens on a page whose main + frame url matches CSD whitelist. + + + + + + Removed as of 05/2018. + + kolos@chromium.org + + Measures whether users update passwords with automatic prompt or manual + fallback. + + + + + + Removed 2020-04. + + vasilii@chromium.org + jdoerrie@chromium.org + + Why was the update password UI closed when a generated password caused a + conflict? + + + + + + Removed 01/2020. + + dvadym@chromium.org + vasilii@chromium.org + + Breakdown on trigger rate of providing a password form autofill entry based + on matching stored information using the public suffix list (PSL) for + possible matches. In addition, this metric also counts cases where a + existing federated entry was successfully matched via PSL. For example, this + includes cases where an existing federated credential for + https://example.com was used for https://subdomain.example.com. + + + + + + Removed 03/2019. + + engedy@chromium.org + + Records, for each password form seen by the password manager, whether the + PasswordStore responded quickly enough so that + PasswordManager.SuppressedAccount histogram samples could be computed. + + + + + + Removed as of 06/2020. + + vasilii@chromium.org + + Collects positive number of inaccessible passwords that were successfully + deleted when retrieving them from the database. Recorded for Mac users. + + + + + + Removed as of 03/2016. + + + Indicates whether the save password prompt disappeared in less than one + second. This most likely indicates that the prompt was dismissed + automatically, e.g. due to a page navigation, before the user was able to + respond to the infobar. + + + + + + Removed as of 03/2016. + + Indicates whether the save password prompt was displayed. + + + + + Removed as of 03/2016. + + + Breakdown of which response the user selected from the save password prompt. + + + + + + Removed 03/2019. + + dvadym@chromium.org + miniailau@google.com + + Measures sending/not sending password forms to the browser process by + PasswordAutofillAgent::SendPasswordForms. + + + + + + Removed 06/2017 + + engedy@chromium.org + melandory@chromium.org + + Tracks the pair of initial values and pair of final values for the legacy + preference for controlling the Chrome Password Manager and the new + preference for controlling Smart Lock on Android. A single sample is + recorded after sync has merged last snapshot and finished initialization for + sync users, and on profile initialization for non-sync users. + + + + + + Removed 06/2017 + + engedy@chromium.org + melandory@chromium.org + + Tracks the pair of initial values for both for the legacy preference for + controlling the Chrome Password Manager and new preference for controlling + Smart Lock on Android. Sample is recorded on every profile initialization + before reconciliation logic is taken place, e.g. when user logs in to + browser, on a startup of a browser. + + + + + + Removed as of M78. PasswordManager.ProvisionalSaveFailure contains strictly + more information. + + jdoerrie@chromium.org + + This metric is recorded every time Chrome detects a password form + submission. The credential might be proposed to be saved, or it might be + blocked. It is blocked if the previously detected password form submission + was successful, and the current submission is from a URL with the same + origin, but a different and insecure scheme. That is, if the previously + provisionally saved credential is for https://example.com, a new credential + for http://example.com would be blocked. More details can be found in the + doc associated with http://crbug.com/571580. + + + + + + Removed 06/2019 + + vasilii@chromium.org + + Records if the user still has to click through the first run experience to + benefit from auto sign-in behavior. Recorded on every start-up. + + + + + + Removed 08/2018 because the decision this should have helped with is now + moot. See https://crbug.com/871509#c3. + + dvadym@chromium.org + + Records results of the new and the old algorithm for detecting whether to + show a password prompt to the user. Recorded on each password form + successful submission. + + + + + + Removed 08/2020. + + vasilii@chromium.org + fhorschig@chromium.org + + Recorded when the "Show all saved passwords" fallback is accepted. + + + + + + Removed 08/2020. + + vasilii@chromium.org + fhorschig@chromium.org + + Recorded when the "Show all saved passwords" fallback is shown. + + + + + + Removed 05/2018 because the feature never launched. + + estark@chromium.org + + Recorded (at most once per main-frame navigation) when a password form shows + a warning that the form is not secure. + + + + + + Removed as of 06/19. + + vasilii@chromium.org + + User action on the Chrome Sync promo that appears in the password bubble. + The promo offers to sign in to Chrome. + + + + + + Removed as of 12/16/16. New statistic is + PasswordManager.SignInPromoCountTil*. + + vasilii@chromium.org + + The number of times the Sign In promo in the password bubble was shown + before user clicked on it. + + + + + + Removed as of 06/19. + + vasilii@chromium.org + + The number of times the Sign In promo in the password bubble was shown + before user clicked on "No thanks". + + + + + + Removed as of 06/19. + + vasilii@chromium.org + + The number of times the Sign In promo in the password bubble was shown + before user clicked on "Sign in". + + + + + + Removed as of 06/19. + + vasilii@chromium.org + + The number of times the Sign In promo in the password bubble was implcitly + dismissed. Recorded each time the promo is implicitly dismissed. + + + + + + Removed as of 14 September 2017, due to being no longer useful. + + xunlu@chromium.org + + Whether password manager stored passwords imported from CSV file + successfully. + + + + + + Removed as of October 2019 + + cfroussios@chromium.org + dvadym@chromium.org + + The time (ms) it takes for the synchronous part of the AddLogin on the + PasswordStore to complete. + + + + + + Removed as of October 2019 + + cfroussios@chromium.org + dvadym@chromium.org + + The time (ms) it takes for the synchronous part of the GetLogin on the + PasswordStore to complete. + + + + + + Removed as of October 2019 + + cfroussios@chromium.org + dvadym@chromium.org + + The time (ms) it takes for the synchronous part of the GetLogins on the + PasswordStore to complete. + + + + + + Removed as of October 2019 + + cfroussios@chromium.org + dvadym@chromium.org + + The time (ms) it takes for the synchronous part of the RemoveLogin on the + PasswordStore to complete. + + + + + + Removed as of October 2019 + + cfroussios@chromium.org + dvadym@chromium.org + + The time (ms) it takes for the synchronous part of the UpdateLogin on the + PasswordStore to complete. + + + + + + Removed since August 28, 2018, due to removing the corresponding feature. + + + When the user logs in with their sync credential, PasswordManager checks if + there are any outdated copies of it in the password store, in order to purge + them. This histogram records whether password store data are ready during + this check. + + + + + + Removed 06/2019. + + dvadym@chromium.org + + Indicates whether submitting a password login form changes the registry + controlled domain of the main frame. + + + + + + Removed 07/2019. + + vasilii@chromium.org + + The type of password suggestion on iOS displayed in the keyboard accessory. + Recorded for each tap on the suggestion. + + + + + + Removed 07/2019. + + vasilii@chromium.org + + The type of password suggestions on iOS displayed in the keyboard accessory. + Recorded each time the password suggestion is shown. + + + + + + Removed 03/2019. + + engedy@chromium.org + + Records, for each password form seen by the password manager, whether there + were `suppressed` credentials, meaning stored credentials that were not + filled because they were for an origin that was similar to, but not exactly + (or PSL) matching the origin of the observed form (see the suffix + description for the possible classes of such near-matches). If there were + such credentials, the histogram also records whether the username and + password of such suppressed credentials matched those submitted. + + + + + + Password manager no longer supports this behavior and the code that could + generate values in this histogram is gone as of M74. + + battre@chromium.org + vasilii@chromium.org + + This histogram is reported for those forms on accounts.google.com, on which + Chrome is forced by Finch/flags during autofilling to remove sync + credentials from password store results. It reports true if sync credentials + were indeed removed from the store results, and false if there were no sync + credentials in the results to begin with. + + + + + + Removed as of 2019/07. Password exporting has been rolled out. + + battre@chromium.org + cfroussios@chromium.org + ioanap@chromium.org + + The time it takes to fetch and serialise the passwords for export. + + + + + + Removed as of 11/11/14. New statistic is + PasswordManager.TimesPasswordUsed.AutoGenerated. + + + The number of times each generated password has been used to log in. + Recorded by iterating over stored passwords once per run. This information + is persisted and synced. + + + + + + Removed in M76 in favor of PasswordManager.TotalAccountsHiRes.ByType. + + battre@chromium.org + vasilii@chromium.org + + The number of accounts stored in the password manager (across all sites), + split by whether created by the user or generated by Chrome, and further by + whether the user used sync with custom passphrase or not. + + + + + + Removed 03/2018 in favor of PasswordManager.UpdateUIDismissalReason. + + dvadym@chromium.org + vasilii@chromium.org + + The password submission event happened when the user changes their password + on a website, say foo.com or types new password on a sign-in form for saved + credential (which might mean that the password was changed in a different + browser). The later case called password overriding. This histogram measures + whether the user has any passwords saved in the Chrome password manager for + foo.com or the password was overriden on sign-in form, and what action the + user performed on the offered bubble. It's recorded when the bubble is + closed. + + + + + + Removed 07/2016 because this information is no longer stored in + PasswordForm. See also http://crbug.com/413020. + + xunlu@chromium.org + gcasto@chromium.org + + Whether saved password for HTTPS site had a valid SSL cert when the password + was saved. + + + + + + Removed since caching is not the root cause of time out issue. + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes for PasswordProtectionService to cache a verdict. + + + + + + Removed since 03/2020 due to no usage. + + vakh@chromium.org + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how a user interacts with the chrome://settings page that displays + the password protection warning. Logged when the page is shown and when the + user chooses to change their password on the page. + + + + + + Removed in M78. The DOM features always parsed successfully, so this + histogram wasn't useful. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether the DOM features were parsed successfully when returned from + the renderer. This is logged on every PhishGuard ping. + + + + + + Removed since caching is not the root cause of time out issue. + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes for PasswordProtectionService to get a cached verdict. + + + + + + Removed 2019-01 due to lack of usage. https://crbug.com/915894 + + chrome-safebrowsing-alerts@google.com + + When user manually navigates to chrome://reset-password page, records how + this user interacts with this page. Logged when the interstitial is shown + and when the user chooses to change their password. + + + + + + Removed since 07/2018 due to lack of usage. + + chrome-safebrowsing-alerts@google.com + + Number of password protection verdicts stored in content settings of a + profile before this profile is destructed. + + + + + + Removed in M71+. + + chrome-safebrowsing-alerts@google.com + + We start changing the way of caching password protection verdicts in M69. + This histogram counts the number of verdicts migrated to the new way during + initialization of PasswordProtectionService. It helps determine when we can + remove migration code. + + + + + + Removed since May 12 2017. Replaced by + PasswordProtection.Verdict.ProtectedPasswordEntry. + + chrome-safebrowsing-alerts@google.com + + Verdict types returned by Safe Browsing server for password reuse events. + + + + + + Removed September 18 2018. This wasn't being used, and can be recreated on + the backend if needed. + + chrome-safebrowsing-alerts@google.com + + The referrer chain size of a password protection request. This is recorded + when Chrome receives a verdict for this request. + + + + + + Removed since May 12 2017. Replaced by + PasswordProtection.Verdict.PasswordFieldOnFocus. + + chrome-safebrowsing-alerts@google.com + + Verdict types returned by Safe Browsing server for unfamiliar login pages. + + + + + + Removed since 07/2018 due to lack of usage. + + chrome-safebrowsing-alerts@google.com + + Whether the user has clicked through the Safe Browsing interstitial before + the password protection ping is triggered on the same page. Logged right + before password protection ping is sent. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when CanMakePayment was not called by the + merchant. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the merchant used the CanMakePayment method during a Payment + Request. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + The effect of the CanMakePayment return value on whether Show was called. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when CanMakePayment was called by the + merchant and returned false. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when CanMakePayment was called by the + merchant and returned true. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + When the merchant has processed the user's Payment Request. + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + When a Payment Request gets initiated by the user. + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + When the user clicks the "pay" button in the Payment Request UI. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + When the browser retrieves the instrument details from the payment app to + complete a purchase. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + When the Payment Request UI gets shown after initialization. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + When the Payment Request UI gets skipped to go directly to the payment app. + + + + + + Removed 09/2020. Made decision in issue 1128111 to remove unused payment + sheet histograms. + + danyao@chromium.org + web-payments-team@google.com + + The number of times the user added an entry during a Payment Request. + + + + + + Removed 09/2020. Made decision in issue 1128111 to remove unused payment + sheet histograms. + + danyao@chromium.org + web-payments-team@google.com + + The number of times the user changed an entry during a Payment Request. + + + + + + Removed 09/2020. Made decision in issue 1128111 to remove unused payment + sheet histograms. + + danyao@chromium.org + web-payments-team@google.com + + The number of times the user edited an entry during a Payment Request. + + + + + + M62+ Included in PaymentRequest.Events + + danyao@chromium.org + + Tracks what user information is required by merchants to complete a Payment + Request. + + + + + + M62+ Included in PaymentRequest.Events + + danyao@chromium.org + + Tracks what payment method was used to complete a transaction in Payment + Request. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when the user did not have a complete + suggestion offered for each requested information. + + + + + + Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July + 19th 2017. + + danyao@chromium.org + + Whether the flow was completed when the user did not have a a form of + payment on file when the Payment Request was shown. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when the user did not have suggestions + offered for each requested information. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + + Whether the flow was completed when the user had at least one complete + suggestion offered for each requested information. + + + + + + Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July + 19th 2017. + + danyao@chromium.org + + Whether the flow was completed when the user had a form of payment on file + when the Payment Request was shown. + + + + + + M62+ Part of PaymentRequest.Events + + danyao@chromium.org + web-payments-team@google.com + + Whether the flow was completed when the user had suggestions offered for + each requested information. + + + + + + Removed in February 2020. + + hnakashima@chromium.org + + Tracks documents opened in the PDF viewer that displayed one or more pages + with the given annotation type. + + + + + + Removed in March 2020. + + thestig@chromium.org + + Tracks which features are used by documents opened in the PDF viewer, logged + when the document finishes loading. + + + + + + Removed in July 2019. + + thestig@chromium.org + The size of PDF documents opened in the PDF viewer. + + + + + Removed in June 2019. + + npm@chromium.org + + Measures if PDFs opened in the PDF viewer require fonts to be substituted. + This is logged whenever a document is opened in the PDF viewer. + + + + + + Removed in July 2019. + + hnakashima@chromium.org + + Measures if PDFs opened in the PDF viewer are Linearized PDFs. This is + logged whenever a document is opened in the PDF viewer. + + + + + + Removed as of 5/2019. + + raymes@chromium.org + + Counts various actions related to the Pepper Broker interface. + + + + + + Removed as of 8/2017. + + raymes@chromium.org + + Whether a Pepper media stream request (mic/cam access) comes from a plugin + in a secure or an insecure origin. + + + + + + Removed as of June 2019. + + maxlg@chromium.org + + The count of possible incoming values to the endMark parameter in + performance.measure(). The purpose is to investigate how much the change of + API of User Timing L3 will impact the real world use cases. This histogram + was deprecated in 05/2018 and re-reenabled in 11/2018. The re-enabled + histogram adds the counting of undefined, null, number and unprovided, to + the original navigation-timing names, object and string. This value is + recorded at each call to performance.measure(). + + + + + + Removed as of June 2019. + + maxlg@chromium.org + + The count of possible incoming values to the startMark parameter in + performance.measure(). The purpose is to investigate how much the change of + API of User Timing L3 will impact the real world use cases. This histogram + was deprecated in 05/2018 and re-reenabled in 11/2018. The re-enabled + histogram adds the counting of undefined, null, number and unprovided, to + the original navigation-timing names, object and string. This value is + recorded at each call to performance.measure(). + + + + + + Removed 2020-01-06 as this was only added for a brief exploration. + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the plurality and visibility state of all BrowsingInstances over + time. An entry in each bucket corresponds to a page in a BrowsingInstance + being in that state for one second. This is effectively "page + seconds" of time spent in each state. Recorded on state changes and + every 5 minutes. + + + + + + Removed 2020-01-06 as this was only added for a brief exploration. + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the plurality and visibility state of all BrowsingInstances over + time. An entry in each bucket corresponds to a BrowsingInstance being in + that state for one second. Recorded on state changes and every 5 minutes. + + + + + + Removed 2019-06-04 in favour of variant 2. + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the types of frames that are being hosted by a process over its + entire lifetime. An entry in the + "AllFramesHaveDistinctSiteInstances" means that the process only + ever hosted frames with distinct site instances over its entire lifetime. + Recorded on state changes and every 5 minutes. + + + + + + Removed 2019-06-04 in favour of variant 2. + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the types of frames that are being hosted by a process, aggregated + over time. Each entry in each bucket corresponds to a process being in that + state for one second. Recorded on state changes and every 5 minutes. + + + + + + Expired on 2019-07-01. + + sebmarchand@chromium.org + + Average percentage of time during which the disk has been idle, logged at + regular intervals. If the system has multiple disks then this is the average + value for all of them. Windows only. + + + + + + Expired on 2019-07-01. + + sebmarchand@chromium.org + + The amount of free physical memory available, logged at regular intervals. + Windows only. + + + + + + Removed on 2020-06-19 as most permissions are no longer exposed to insecure + origins to begin with, and even those few that are recorded no useful data + any longer. + + dominickn@chromium.org + engedy@chromium.org + hkamila@chromium.org + mlamouri@chromium.org + + Tracks whether a permission was granted, rejected, etc on an insecure + origin. The suffix of the histogram indicates which particular permission. + + + + + + Removed on 2020-06-19 as most permissions are no longer exposed to insecure + origins to begin with, and even those few that are recorded no useful data + any longer. + + dominickn@chromium.org + engedy@chromium.org + hkamila@chromium.org + mlamouri@chromium.org + + Tracks whether a permission was granted, rejected, etc on a secure origin. + The suffix of the histogram indicates which particular permission. + + + + + + Permission blacklisting was removed in M67. + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks the response (if received) from Safe Browsing when the API blacklist + is queried for an (origin, permission) pair. The response could be that the + origin was blacklisted, not blacklisted, or Safe Browsing timed out before a + response was received. + + + + + + Permission blacklisting was removed in M67. + + dominickn@chromium.org + kcarattini@chromium.org + + Records the elapsed time between the client sending a request to Safe + Browsing and receiving a result, or the maximum wait time is exceeded and + Safe Browsing is deemed to have timed out. + + + + + + Persist toggle experiments ran from M56 to M59. + + dominickn@chromium.org + kcarattini@chromium.org + + For each granted permission prompt displayed with a persistence toggle + (remember my decision), records whether the persistence toggle was enabled + (persist) or not enabled (don't persist). + + + + + + Replaced by Permissions.Prompt.Accepted.PriorDismissCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt accept, records the + total number of prompt dismissal events for this origin since the last time + the user cleared their history or site data and prior to the accept. The + suffix of the histogram indicates which particular permission. + + + + + + Replaced by Permissions.Prompt.Accepted.PriorIgnoreCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt accept, records the + total number of prompt ignore events for this origin since the last time the + user cleared their history or site data and prior to the accept. The suffix + of the histogram indicates which particular permission. + + + + + + Persist toggle experiments ran from M56 to M59. + + dominickn@chromium.org + kcarattini@chromium.org + + For each denied permission prompt displayed with a persistence toggle + (remember my decision), records whether the persistence toggle was enabled + (persist) or not enabled (don't persist). + + + + + + Replaced by Permissions.Prompt.Denied.PriorDismissCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt deny, records the + total number of prompt dismissal events for this origin since the last time + the user cleared their history or site data and prior to the accept. The + suffix of the histogram indicates which particular permission. + + + + + + Replaced by Permissions.Prompt.Denied.PriorIgnoreCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt deny, records the + total number of prompt ignore events for this origin since the last time the + user cleared their history or site data and prior to the accept. The suffix + of the histogram indicates which particular permission. + + + + + + Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt dismissal, records + the total number of prompt dismissal events for this origin since the last + time the user cleared their history or site data, inclusive of the current + dismissal. Every event in a bucket larger than 1 in this histogram will also + have an event in each smaller bucket. The suffix of the histogram indicates + which particular permission. + + + + + + Replaced by Permissions.Prompt.Dismissed.PriorDismissCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt dismiss, records + the total number of prompt dismissal events for this origin since the last + time the user cleared their history or site data and prior to the dismiss. + The suffix of the histogram indicates which particular permission. + + + + + + Replaced by Permissions.Prompt.Dismissed.PriorIgnoreCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt dismiss, records + the total number of prompt ignore events for this origin since the last time + the user cleared their history or site data and prior to the dismiss. The + suffix of the histogram indicates which particular permission. + + + + + + Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt ignore, records the + total number of prompt ignore events for this origin since the last time the + user cleared their history or site data, inclusive of the current ignore. + Every event in a bucket larger than 1 in this histogram will also have an + event in each smaller bucket. The suffix of the histogram indicates which + particular permission. + + + + + + Replaced by Permissions.Prompt.Ignored.PriorDismissCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt ignore, records the + total number of prompt dismissal events for this origin since the last time + the user cleared their history or site data and prior to the ignore. The + suffix of the histogram indicates which particular permission. + + + + + + Replaced by Permissions.Prompt.Ignored.PriorIgnoreCount2 on 05/2020. + + dominickn@chromium.org + kcarattini@chromium.org + + This metric, recorded at the time of a permission prompt ignore, records the + total number of prompt ignore events for this origin since the last time the + user cleared their history or site data and prior to the ignore. The suffix + of the histogram indicates which particular permission. + + + + + + Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same + counts are available in Permissions.Prompt.Accepted. + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks acceptance of permission bubble request types that have been merged + into coalesced bubbles. + + + + + + Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same + counts are available in Permissions.Prompt.Denied. + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks denial of permission bubble request types that have been merged into + coalesced bubbles. + + + + + + Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same + counts are available in Permissions.Prompt.Shown. + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks the permission bubble request types that are being merged into + coalesced bubbles. + + + + + + Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same + counts are available in Permissions.Prompt.Shown. + + dominickn@chromium.org + kcarattini@chromium.org + + How many permission requests each permissions prompt shown to the user + contains. + + + + + + Removed 02/2017, no longer used + + dominickn@chromium.org + kcarattini@chromium.org + keenanb@google.com + jww@chromium.org + + The embedder's permission setting at the time of a cross-origin iframe + permission request for a given permission type. See the corresponding + histogram suffixes. + + A request is when a website makes a permission request and the user has the + permission set to prompt (i.e. not blocked or allowed). + + Note this is probably not the metric you want - it does not correspond to + the total number of times websites request a permission. Also, because + specific permissions have code that can automatically block or grant + permissions based on things like incognito, installed extensions etc., this + does also not correspond to the number of times users are prompted to allow + permissions. + + See https://crbug.com/638076 for more details. + + + + + + Removed 02/2017, no longer used + + dominickn@chromium.org + kcarattini@chromium.org + keenanb@google.com + jww@chromium.org + + The permission type (geolocation, and such) of a same-origin permission + request. + + A request is when a website makes a permission request and the user has the + permission set to prompt (i.e. not blocked or allowed). + + Note this is probably not the metric you want - it does not correspond to + the total number of times websites request a permission. Also, because + specific permissions have code that can automatically block or grant + permissions based on things like incognito, installed extensions etc., this + does also not correspond to the number of times users are prompted to allow + permissions. + + See https://crbug.com/638076 for more details. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Referer used by user to reach the main Physical Web Activity. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + Initial state of the Physical Web in Chrome for iOS. + + + + + Removed 01/2017, no longer used + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Time between the most recent opt in notification update and when the user + arrives at the ListUrlsActivity. + + + + + + Removed 01/2017, no longer used + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Time between the most recent standard notification update and when the user + arrives at the ListUrlsActivity. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Round trip time to the metadata server for a Physical Web URL resolution + which the client requests during a background scan. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Round trip time to the metadata server for a Physical Web URL resolution + which the client requests during a foreground scan, that is not explicitly + requested via a refresh. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Round trip time to the metadata server for a Physical Web URL resolution + which the client requests during a foreground scan, that is explicitly + requested via a refresh. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + olivierrobin@chromium.org + Round trip time to the metadata server for Physical web. + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + Whether bluetooth is on, off, or unknown. + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + Whether the data connection is active. + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + Whether location permission has been accepted. + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + Whether location services are enabled. + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Whether the preference is on, off, or if the user is in an onboarding state + when Chrome first starts up. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + The number of URLs displayed to a user when a list of nearby URLs is first + displayed. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + The number of URLs displayed to a user when a list of nearby URLs is + displayed after refreshing. + + + + + + Obsolete 4/2018, Physical Web is disabled (crbug.com/826540). + + cco3@chromium.org + mattreynolds@chromium.org + mmocny@chromium.org + + Count of how many times the user selected a nearby URL at the specified + index in the Physical Web WebUI list view (zero-based). Capped at 50. + + + + + + Removed 11/2018 in favor of Platform.Cast.MeminfoMemAvailable2 with a larger + range. + + halliwell@chromium.org + + /proc/meminfo's 'MemAvailable' in Mbytes. Collected on Cast devices with + kernel version 3.14 and above and capped at 500. + + + + + + Removed 11/2018 in favor of Platform.Cast.MeminfoMemFreeDerived2 with a + larger range. + + halliwell@chromium.org + + free + buffers + cache memory in Mbytes on Cast devices, capped at 500. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Average size of user's Cache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Maximum size of user's Cache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Average size of user's Cache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Maximum size of user's Cache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Average size of user's GCache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Maximum size of user's GCache directory. Logged once a day, if disk usage is + high. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Days since the least frequently used account signed in. Logged once a day, + if disk usage is high. + + + + + + Removed 8/2019 due to lack of usage. + + Please list the metric's owners. Add more owner tags as needed. + + The 32-bit hash of a kernel warning. This is the hash of the + "file:line" string corresponding to the location of the warning, + for instance: "/mnt/host/source/src/third_party/kernel/files/drivers + /gpu/drm/i915/intel_dp.c:351" (ignore spurious spaces). The hash is + produced by this code: while (*string) hash = (hash << 5) + hash + + *string++; Separately each warning is also collected (with its hash) via the + crash reporter, but only its first occurrence in each boot session. + + + + + + Removed 6/2020 due to lack of usage. + + gwendal@chromium.org + sarthakkukreti@chromium.org + + Type of encrypted mount used for the encrypted stateful file system on + Chrome OS. + + + + + + Removed 8/2019 due to lack of usage. + + ddavenport@chromium.org + + The 32-bit hash of the name of the service that failed. The name of the + service is hashed using the same algorithm as used for the hashes in + Platform.KernelWarningHashes. The first instance of each service failure is + also collected separately via the crash reporter. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + scroll event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + CPU utilization for the specified swap group and time interval after a tab + switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 9/2013 when the SwapJank64vs32Parrot experiment ended. + + Please list the metric's owners. Add more owner tags as needed. + + Page faults/second for the specified swap group and time interval after a + tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc. + + + + + + Removed 09/2020 + + mka@chromium.org + + Temperature reading at wireless interface 0 collected every few seconds (may + vary between devices). + + This metric is specific to Chrome OS. + + + + + + Removed 09/2020 + + mka@chromium.org + + Temperature reading at wireless interface 1 collected every few seconds (may + vary between devices). + + This metric is specific to Chrome OS. + + + + + + Removed 09/2020 + + mka@chromium.org + + Temperature reading at wireless interface 2 collected every few seconds (may + vary between devices). + + This metric is specific to Chrome OS. + + + + + + Removed 09/2020 + + mka@chromium.org + + State of the thermal zone of wireless interface 0 collected every second. + State depends on device, higher state corresponds to a higher temperature. + + This metric is specific to Chrome OS. + + + + + + Removed 09/2020 + + mka@chromium.org + + State of the thermal zone of wireless interface 1 collected every second. + State depends on device, higher state corresponds to a higher temperature. + + This metric is specific to Chrome OS. + + + + + + Removed 09/2020 + + mka@chromium.org + + State of the thermal zone of wireless interface 2 collected every second. + State depends on device, higher state corresponds to a higher temperature. + + This metric is specific to Chrome OS. + + + + + + Removed 06/2020 as there is no data and no mention of it in the codebase. + + apronin@chromium.org + cros-hwsec+uma@chromium.org + + Each sample is the number of consecutive reboots performed while attempting + to clear a TPM (Trusted Platform Module) error. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Retries needed to enable a FET on tps65090 (AKA tpschrome). Tps65090 is a + power management unit (PMU) used on many ARM Chromebooks. Until version ES7 + was rolled into production we would sometimes run into a problem where FET1 + (the FET used to switch on and off the backlight) wouldn't turn on properly. + This problem was especially prevalent when the voltage was high (like when + the device was plugged into the wall). Retrying by turning the FET off and + on again is nearly always effective, so the kernel will retry up to 5 times + (currently) and will also log the fact that it needed to retry. On newest + kernels (kernel 3.8 and up) a kernel warning will be logged with WARN_ON if + the FET still failed to turn on after 5 tries. Refer to the kernel warning + reports to find that information. For more details about this bug refer to + http://crbug.com/338657 and http://crosbug.com/p/16009. Note that we log + retries on all 7 FETs even though we've only ever seen failures of FET1. + + + + + + Removed as of 2016-07 because the histogram's purpose of adding colour to + the description of File::Flush() has been fulfilled. + + tnagel@chromium.org + The time it takes to run File::Flush(). + + + + + Removed as of 2013-05, replaced by PlatformFile.UnknownCreateFileErrorsWin + in chrome 29. + + Please list the metric's owners. Add more owner tags as needed. + + Errors returned by CreateFile on windows that PlatformFileError doesn't yet + support. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + Distribution of actual finished pages, vs abandoned pages, where we needed + to declare a finish time prematurely since the page was being closed + (exited). + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + + The PLT.Abandoned histogram for pages loaded after WebRequest API was used. + + + + + + Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by Abandoned_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + Diagnose why a page load was considered abandoned. + + + + + Use PageLoad.Timing2.NavigationToCommit instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "begin" to "commit." "Begin"== + "request" if user requested, and "start" otherwise. + "Request"== time when user requested document. "Start"== + time when renderer requested load of document, after any unload of last + document. "Commit"== time when renderer got first byte of + document. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + + Removed as of http://crrev.com/392823002 + + kouhei@chromium.org + + PLT.BeginToFinish, but for pages requested just after a new preconnect + request. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + PLT.BeginToFinish, but for pages which contained prefetch links. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + PLT.BeginToFinish, but for pages which were referred to by pages which + contained prefetch links. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadNormal_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadNormal_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + No longer needed. + + + The PLT.BeginToFinish histogram for pages loaded by following a link, after + WebRequest API was used. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadNormal_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadNormal_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadNormal_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadReload_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadReload_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + No longer needed. + + + The PLT.BeginToFinish histogram for pages reloaded by JavaScript or by + following a link, after WebRequest API was used. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadReload_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadReload_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadReload_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + No longer needed. + + + The PLT.BeginToFinish histogram for pages loads initiated by back/forward + buttons, or by a change of encoding, after WebRequest API was used. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by + BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + No longer needed. + + + The PLT.BeginToFinish histogram for pages loaded by entering a URL or a + search query into Omnibox, after WebRequest API was used. + + + + + + Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Removed 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest. + + Please list the metric's owners. Add more owner tags as needed. + + + + + + Use PLT.PT_BeginToFinish_DataReductionProxy instead. + + Please list the metric's owners. Add more owner tags as needed. + PLT.BeginToFinish, but for pages fetched over a SPDY proxy. + + + + + Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead. + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + + Removed as of http://crrev.com/392823002 + + kouhei@chromium.org + + PLT.BeginToFinishDoc, but for pages requested just after a new preconnect + request. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + PLT.BeginToFinishDoc, but for pages which contained prefetch links. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + PLT.BeginToFinishDoc, but for pages which were referred to by pages which + contained prefetch links. + + + + + + Use PLT.PT_BeginToFinishDoc_DataReductionProxy instead. + + Please list the metric's owners. Add more owner tags as needed. + + PLT.BeginToFinshDoc, but for pages fetched over a SPDY proxy. + + + + + + Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. + + pmeenan@chromium.org + + Time from "begin" to "first paint." "Begin"== + "request" if user requested, and "start" otherwise. + "Request"== time when user requested document. "Start"== + time when renderer requested load of document, after any unload of last + document. "First paint"== time when first paint operation was + performed. + + + + + + No longer needed. + + bmcquade@chromium.org + + Magnitude and difference between begin and first paint, when first_paint + precedes begin. This is a temporary metric used to better understand the + root cause of http://crbug.com/125273. + + + + + + The first paint after load is not useful for most documents. Consider using + PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. + + pmeenan@chromium.org + + Time from "big" to "first paint after load." + "Begin"== "request" if user requested, and + "start" otherwise. "Request"== time when user requested + document. "Start"== time when renderer requested load of document, + after any unload of last document. "First paint after load"== time + after onload() when first paint operation is performed. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "commit" to "finish." "Commit"== + time when renderer got first byte of document. "Finish"==after + onload() and all resources are loaded. + + + + + + Use PageLoad.ParseTiming.ParseDuration instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "commit" to "finish doc." "Commit"== + time when renderer got first byte of document. "Finish doc" == + main document loaded, before onload(). "Finish"==after onload() + and all resources are loaded. + + + + + + Use PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "commit" to "first paint." + "Commit"== time when renderer got first byte of document. + "First paint"== time when first paint operation was performed. + + + + + + The first paint after load is not useful for most documents. Consider using + PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "commit" to "first paint after load." + "Commit"== time when renderer got first byte of document. + "First paint after load"== time after onload() when first paint + operation is performed. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "finish doc" to "finish." "Finish + doc"== main document loaded, before onload(). "Finish"==after + onload() and all resources are loaded. + + + + + + The first paint after load is not useful for most documents. Consider using + PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "finish " to "first paint after load." + "Finish"==after onload() and all resources are loaded. "First + paint after load"== time after onload() when first paint operation is + performed. + + + + + + Experiment has ended 2020-06. + + djean@chromium.org + eugenebut@chromium.org + + Page load time for Browser-initiated navigations when battery level is below + a certain threshold (20%). Recorded when + CRWWebRequestController::didFinishWithURL completes successfully. iOS + specific. + + + + + + Experiment has ended 2020-06. + + djean@chromium.org + eugenebut@chromium.org + + Page load time for Renderer-initiated navigations when battery level is + below a certain threshold (20%). Recorded when + CRWWebRequestController::didFinishWithURL completes successfully. iOS + specific. + + + + + + Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.* + instead. + + Please list the metric's owners. Add more owner tags as needed. + + Probability distribution for enumerated varieties of page loads. + + + + + + Removed as of 2014-06. + + Please list the metric's owners. Add more owner tags as needed. + + Diagnose error conditions in PLT reporting. A start time should always be + present. + + + + + + deprecated 2012-01-19 in favour of PLT.PT_* + + Please list the metric's owners. Add more owner tags as needed. + + The time elapsed between the Navigation Timing metrics navigationStart and + loadEventEnd. Definitions: http://www.w3.org/TR/navigation-timing/ + + + + + + deprecated 2012-01-19 in favour of PLT.PT_* + + Please list the metric's owners. Add more owner tags as needed. + + The time elapsed between the Navigation Timing metrics navigationStart and + loadEventStart. Definitions: http://www.w3.org/TR/navigation-timing/ + + + + + + Removed 09/2016. + + bolian@chromium.org + + Time from connectStart to connectEnd based on Navigation Timing. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from domanLookupEnd to connectStart based on Navigation Timing. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from fetchStart to domainLookupStart based on Navigation Timing. + + + + + + Removed as of 7/19/2016. Replaced by + PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired. + + bolian@chromium.org + + Time from responseStart to domLoading based on Navigation Timing. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from navigationStart to fetchStart based on Navigation Timing when no + redirect. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from navigationStart to fetchStart excluding time spent on redirects + based on Navigation Timing. Only page loads with redirects are considered. + + + + + + Removed as of 7/19/2016. Replaced by + PageLoad.DocumentTiming.NavigationToLoadEventFired. + + bolian@chromium.org + + Time from domContentLoadedEventEnd to loadEventStart based on Navigation + Timing. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from connectEnd to requestStart based on Navigation Timing. + + + + + + Removed 09/2016. + + bolian@chromium.org + + Time from domainLookupStart to domainLookupEnd based on Navigation Timing. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToDOMContentLoadedEventFired + instead. + + bolian@chromium.org + + Time from domContentLoadedEventStart to domContentLoadedEventEnd based on + Navigation Timing. + + + + + + Removed 09/2016. + + bolian@chromium.org + + Time from domInteractive to domContentLoadEventStart based on Navigation + Timing. + + + + + + Removed 09/2016. + + bolian@chromium.org + + Time from domLoading to domInteractive based on Navigation Timing. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + bolian@chromium.org + + Time from loadEventStart to loadEventEnd based on Navigation Timing. + + + + + + Removed as of 7/19/2016. + + bolian@chromium.org + + Time from redirectStart to redirectEnd based on Navigation Timing when + redirects exist. + + + + + + Removed as of 7/19/2016. Replaced by + PageLoad.ParseTiming.NavigationToParseStart. + + bolian@chromium.org + + Time from requestStart to responseStart based on Navigation Timing. + + + + + + Removed as of 7/19/2016. Replaced by PageLoad.ParseTiming.ParseDuration. + + bolian@chromium.org + + Time from responseStart to responseEnd based on Navigation Timing. + + + + + + Removed as of 5/02/2011. + + Please list the metric's owners. Add more owner tags as needed. + Distribution of discarded and displayed prerendered pages. + + + + + Removed as of 5/02/2011, replaced by Prerender.RendererPLT. + + Please list the metric's owners. Add more owner tags as needed. + + Perceived load time of a page. For non-prerendered pages, this is just + BeginToFinish. For displayed prerendered pages, this is the time from when + the prerendered page is moved into a TabContents until finish. + "Finish" == after onload() and all resources are loaded. Note that + this is 0 if the loading finishes before the page is moved into a + TabContents. + + + + + + Removed as of 5/02/2011, replaced by Prerender.RendererPerceivedPLTMatched. + + Please list the metric's owners. Add more owner tags as needed. + + Perceived load time of a prerendered page that is displayed. This is the + time from when the prerendered page is moved into a TabContents until + finish. "Finish" == after onload() and all resources are loaded. + Note that this is 0 if the loading finishes before the page is moved into a + TabContents. + + + + + + Removed as of 5/02/2011, replaced by Prerender.RendererTimeUntilDisplay. + + Please list the metric's owners. Add more owner tags as needed. + + The time elapsed between when the prerendering of a page starts and when the + page is displayed. Prerendered pages discarded without being displayed are + excluded from this count. + + + + + + Removed as of 5/02/2011, replaced by Prerender.RendererIdleTime. + + Please list the metric's owners. Add more owner tags as needed. + + This is the time from when a prerendered page finishes loading to when it is + displayed. When a page is displayed before it finishes loading, no value is + recorded in this histogram. + + + + + + Removed. Use PageLoad.Timing2.* instead. + + bmcquade@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first document layout is performed. + + + + + + Removed. Use PageLoad.Timing2.* instead. + + bmcquade@chromium.org + + Measures the time from navigation timing's response start to the time the + first document layout is performed. + + + + + + Use PageLoad.Timing2.NavigationToCommit instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or + navigationStart if user-initiated request. + + + + + + Removed 9/2016. Use Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToCommit + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or + navigationStart if user-initiated request. Only page loads through the data + reduction proxy are considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.BeginToFinish. Finish: loadEventEnd. Begin: requestStart or + navigationStart if user-initiated request. + + + + + + Removed 9/2016. Use Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.BeginToFinish_SpdyProxy. Finish: loadEventEnd. Begin: + requestStart or navigationStart if user-initiated request. Only page loads + through the data reduction proxy are considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.BeginToFinishDoc. FinishDoc: loadEventStart. Begin: + requestStart or navigationStart if user-initiated request. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.BeginToFinishDoc_SpdyProxy. FinishDoc: loadEventStart. Begin: + requestStart or navigationStart if user-initiated request. Only page loads + through the data reduction proxy are considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd. + Only page loads through the data reduction proxy are considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc: + loadEventStart. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc: + loadEventStart. Only page loads through the data reduction proxy are + considered. + + + + + + No longer needed. + + Please list the metric's owners. Add more owner tags as needed. + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc: + loadEventStart. + + + + + + Removed 09/2016. + + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc: + loadEventStart. Only page loads through the data reduction proxy are + considered. + + + + + + Use PageLoad.Timing2.NavigationToCommit instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and measures the time until + the renderer got first byte of document. Commit: time when renderer got + first byte of document. Request: navigationStart. + + + + + + Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and measures the time until + the beginning of the DOMContentLoaded event. DOMContentLoaded: + domContentLoadedEventStart. Request: navigationStart. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.RequestToFinish. Finish: loadEventEnd. Request: + navigationStart. + + + + + + Removed 09/2016. Use + PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired + instead. + + pmeenan@chromium.org + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.RequestToFinish. Finish: loadEventEnd. Request: + navigationStart. Only page loads through the data reduction proxy are + considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + pmeenan@chromium.org + + This time is based on the NavigationTiming spec and measures the page load + time until the beginning of the load event. Finish: loadEventStart. Request: + navigationStart. + + + + + + Removed 09/2016. + + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.RequestToStart. Start: requestStart. Request: + navigationStart. Only page loads through the data reduction proxy are + considered. + + + + + + Removed 09/2016. + + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.StartToCommit. Start: requestStart. Commit: responseStart. + Only page loads through the data reduction proxy are considered. + + + + + + Removed 09/2016. + + bengr@chromium.org + megjablon@chromium.org + + This time is based on the PerformanceTiming spec and is a more accurate + version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd. + Only page loads through the data reduction proxy are considered. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "request" to "finish." "Request" == + time when user requested document. "Finish" == after onload() and + all resources are loaded. + + + + + + Use PageLoad.Timing2.NavigationToCommit instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "start" to "commit." "Start"== time + when renderer requested load of document, after any unload of last document. + "Commit"== time when renderer got first byte of document. + + + + + + Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead. + + Please list the metric's owners. Add more owner tags as needed. + + Time from "start" to "finish." "Start"== time + when renderer requested load of document, after any unload of last document. + "Finish"==after onload() and all resources are loaded. + + + + + + Removed as of 07/2014. + + Please list the metric's owners. Add more owner tags as needed. + StartToFinish times when using http and no proxy. + + + + + Removed as of 07/2014. + + Please list the metric's owners. Add more owner tags as needed. + StartToFinish times when using https and no proxy. + + + + + Removed as of 07/2014. + + Please list the metric's owners. Add more owner tags as needed. + StartToFinish times when using http over a proxy. + + + + + Removed as of 07/2014. + + Please list the metric's owners. Add more owner tags as needed. + StartToFinish times when using https over a proxy. + + + + + Removed as of 09/2016. + + pmeenan@chromium.org + + This time is based on the User Timing spec and measures the time from + Navigation Timing navigationStart until the point where the page called + performance.mark(). + + + + + + Removed as of 09/2016. + + pmeenan@chromium.org + + This time is based on the User Timing spec and reports the time between two + arbitrary points defined by the page being loaded and directly matches the + measurement exposed by performance.measure(). + + + + + + Removed as of 01/2017 (M65). + + xhwang@chromium.org + media-dev@chromium.org + + The availability status of Widevine CDM. In normal cases, this is reported + per render process if EME API is used. This is not reported if EME API is + not used. This could be reported multiple times per render process until + PLUGIN_AVAILABLE is reported (which should be a rare case). + + + + + + Removed as of 06/2019 (M77). + + pastarmovj@chromium.org + tommycli@chromium.org + Tracks whether plugins that were disabled were migrated. + + + + + Removed 10/2019. + + tommycli@chromium.org + + Aspect ratio of Flash plugins users click at least once. The aspect ratio is + multiplied by 100 and stored as a rounded integer. + + + + + + Removed 10/2019. + + tommycli@chromium.org + Height of Flash plugins users click at least once. + + + + + Removed 10/2019. + + tommycli@chromium.org + Width of Flash plugins users click at least once. + + + + + Removed 12/2017 in Issue 781644 as we no longer use Site Engagement Index as + a signal for Flash display. + + dominickn@chromium.org + + The engagement score of origins which have passed through a site engagement + check to permit or block Flash. Recorded every time the Flash plugin is + requested with the PreferHtmlOverPlugins feature active. + + + + + + Removed 10/2019. + + tommycli@chromium.org + + Collects the sizes of all loaded Flash plugin instances. This is for + determining the prevalence of tiny flash plugin instances. + + + + + + Removed from code 07/2019. + + mlamouri@chromium.org + media-dev@chromium.org + + Records the YouTube Flash embed rewrite status when attempted. + + + + + + Removed due to NPAPI removal. + + wfh@chromium.org + + The plugin group of an NPAPI plugin that is no longer supported. Recorded + when the NPAPI removal infobar is shown for a plugin which is no longer + supported. + + + + + + Removed due to NPAPI removal. + + wfh@chromium.org + + The plugin group of an NPAPI plugin that will be unsupported soon. Recorded + when the NPAPI removal infobar is shown after an NPAPI plugin first loads to + warn the user that NPAPI support for this plugin will be removed soon. + + + + + + Removed due to NPAPI removal. + + wfh@chromium.org + + Records whether NPAPI plugins are supported by the platform, and if so, + whether they are enabled or disabled. Recorded once at browser startup. + + + + + + Removed in favor of Plugin.PowerSaver.PeripheralHeuristicInitialDecision. + + tommycli@chromium.org + + Records each decision of the Plugin Power Saver peripheral content + heuristic. This UMA is counted once per peripheral query, and may count a + single plugin instance multiple times as it is resized. + + + + + + Removed 10/2019. + + tommycli@chromium.org + + Records the initial decision of the Plugin Power Saver peripheral content + heuristic for each plugin instance. This is recorded once per plugin + instance. + + + + + + Removed 10/2019. + + tommycli@chromium.org + + Record how many plugin object tags use poster param. This is recorded once + per plugin instance, and is currently restricted to Flash plugin instances. + + + + + + Removed from code 07/2019. + + mlamouri@chromium.org + Result of HTMLPluginElement::requestObject in Blink. + + + + + Removed due to NPAPI removal. + + gab@chromium.org + + Roundtrip times for synchronous IPC calls from the renderer to NPAPI plugin + processes. + + + + + + Removed 10/2019. + + twellington@chromium.org + wfh@chromium.org + + Error codes when parsing the built-in plugin list. Logged when the + PluginFinder singleton is created. + + + + + + Removed 02/2017 in favor of power benchmarks that have less variability than + data from users' machines. + + jeremy@chromium.org + + The percentage of battery capacity used per hour relative to a full battery. + Reported once when the power adaptor is plugged back in after the system is + on battery power for more than 30 minutes. If at any point the system is + suspended or all Chrome renderers are closed the measurement is not + recorded. Anytime the user unplugs the power adaptor, a new measurement will + begin being recorded. Collection of this histogram only starts after 30 + minutes of uptime at which point the clock starts (assuming the user is on + battery power at that point). The system will need to remain unplugged for + at least another 30 minutes in order for any measurement to be recorded. + Values are normalized to a percent per hour scale. This measurement is tied + tightly to hardware model/OS and is not comparable across different hardware + configurations. + + + + + + Removed 02/2017 in favor of power benchmarks that have less variability than + data from users' machines. + + jeremy@chromium.org + + The percent of depleted battery capacity relative to a full battery over the + first 15 minutes after battery power collection information starts. + Collection of this histogram only starts after 30 minutes of uptime at which + point the clock starts (assuming the user is on battery power at that + point). The system will need to remain unplugged for at least another 15 + minutes in order for any measurement to be recorded. Values are normalized + to a percent per hour scale. This measurement is tied tightly to hardware + model/OS and is not comparable across different hardware configurations. + + + + + + Removed 02/2017 in favor of power benchmarks that have less variability than + data from users' machines. + + jeremy@chromium.org + + The percent of depleted battery capacity relative to a full battery over the + first 30 minutes after battery power collection information starts. + Collection of this histogram only starts after 30 minutes of uptime at which + point the clock starts (assuming the user is on battery power at that + point). The system will need to remain unplugged for at least another 30 + minutes in order for any measurement to be recorded. Values are normalized + to a percent per hour scale. This measurement is tied tightly to hardware + model/OS and is not comparable across different hardware configurations. + + + + + + Removed 02/2017 in favor of power benchmarks that have less variability than + data from users' machines. + + jeremy@chromium.org + + The percent of depleted battery capacity relative to a full battery over the + first 5 minutes after battery power collection information starts. + Collection of this histogram only starts after 30 minutes of uptime at which + point the clock starts (assuming the user is on battery power at that + point). The system will need to remain unplugged for at least another 5 + minutes in order for any measurement to be recorded. Values are normalized + to a percent per hour scale. This measurement is tied tightly to hardware + model/OS and is not comparable across different hardware configurations. + + + + + + Removed as of 03/2012, no longer being generated by powerd. + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge + sampled when the device runs on battery. + + + + + + Removed as of 03/2012, no longer being generated by powerd. + + tbroch@chromium.org + + Chrome OS remaining time to empty battery in minutes sampled when the device + runs on battery. + + + + + + Removed as of 5/2013. See Accel_BrightnessDown_F6 and Accel_BrightnessUp_F7 + user actions instead. + + tbroch@chromium.org + + Number of times the user has adjusted brightness up and down while running + on battery power. + + + + + + Removed as of 5/2013. See Accel_BrightnessDown_F6 and Accel_BrightnessUp_F7 + user actions instead. + + tbroch@chromium.org + + Number of times the user has adjusted brightness up and down while running + on AC power. + + + + + + Removed 11/2014 in issue 427057. + + tbroch@chromium.org + + External power supply type such as MAINS_CHARGER, USB_CHARGER, + UNCONFIRMED_SPRING_CHARGER, SAFE_SPRING_CHARGER. A sample is reported each + time a charger is connected to the device. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average power consumption, measured in milli-units per hour, when sync + invalidator listens to on_application_active events. Values for this metric + are per session, i.e. from battery level at application entering foreground + to returning to background, and normalized to an hourly average consumption. + This is an iOS only measurement. Due to how iOS reports battery levels, it + is likely to see many readings of 0. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average power consumption, measured in milli-units per hour, for other + sync invalidator methods. Values for this metric are per session, i.e. from + battery level at application entering foreground to returning to background, + and normalized to an hourly average consumption. This is an iOS only + measurement. Due to how iOS reports battery levels, it is likely to see many + readings of 0. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average power consumption, measured in milli-units per hour, when sync + invalidator uses peer-to-peer notifications. Values for this metric are per + session, i.e. from battery level at application entering foreground to + returning to background, and normalized to an hourly average consumption. + This is an iOS only measurement. Due to how iOS reports battery levels, it + is likely to see many readings of 0. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The average power consumption, measured in milli-units per hour, when sync + invalidator uses server-based non-blocking invalidator. Values for this + metric are per session, i.e. from battery level at application entering + foreground to returning to background, and normalized to an hourly average + consumption. This is an iOS only measurement. Due to how iOS reports battery + levels, it is likely to see many readings of 0. + + + + + + Removed Feb 2014 by Power.SuspendAttemptsBeforeCancel and + Power.SuspendAttemptsBeforeSuccess. + + tbroch@chromium.org + + The number of times Chrome OS retried suspend due to previous failure. + + + + + + Removed Jan 2014 by Power.SuspendAttempt and Power.SuspendResult. + + tbroch@chromium.org + Chrome OS suspend status. + + + + + No longer sent. + + tbroch@chromium.org + + The percentage of aborted fan attempts out of total fan attempts per + session, where an abort is due to hysteresis. This value is computed from + boot and sent when powerd starts and then every 15 minutes afterwards. + + + + + + No longer sent. + + tbroch@chromium.org + + The percentage of fan trip point passes that are more than one trip point. + This value is computed from boot and sent when powerd starts and then every + 15 minutes afterwards. + + + + + + Removed July 11 2017. + + bengr@chromium.org + rajendrant@chromium.org + + The battery level in percentage when the precache task was started. + + + + + + Removed July 11 2017. + + bengr@chromium.org + rajendrant@chromium.org + + Measures the difference between the battery level percentage when the + precache task is started and ended. This value indicates the possible + battery usage due to the precache task. Logged when the precache task ends, + which could be due to successful completion, time-out, error conditions, max + download limit exceeded, etc. + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + The size in kilobytes occupied by all the entries existing in the cache at + the time of the last precache. + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + Like HttpCache.Pattern but only for requests not made during precaching. + Logged per-request. + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + Like Precache.CacheStatus.NonPrefetch but only for requests which having a + matching URL in the precache. Measures the amount of precache misses due to + expiration or eviction. Logged per-request. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + jamartin@chromium.org + + Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer + not in the user's top visited hosts. See History.TopHostsVisitsByRank for + details on the top hosts computation. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + jamartin@chromium.org + + Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer + in the user's top visited hosts. See History.TopHostsVisitsByRank for + details on the top hosts computation. + + + + + + Removed July 11 2017. + + jamartin@chromium.org + twifkak@chromium.org + + Like HttpCache.Pattern but only for requests made during precaching. Logged + per-request. + + + + + + Removed July 11 2017. + + bengr@chromium.org + + The number of bytes that were downloaded over the network for HTTP/HTTPS + fetches that were not motivated by precaching. Logged per-request. + + + + + + Removed July 11 2017. + + bengr@chromium.org + + The number of bytes that were downloaded because of precaching. Logged + per-request. + + + + + + Removed July 11 2017. + + rajendrant@chromium.org + bengr@chromium.org + + Enumerates the various failure reasons and events of interest for + precaching. The events are persisted when the native library is not loaded, + and recorded when the library loads next time. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + bengr@chromium.org + + A bit vector of reasons why the precache fetch failed to start. Bit values + are documented in the FailureReason Java enum. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + + The minimum resource weight that is fetched in a given precache run. + Reported if the precache completed successfully or was canceled due to the + byte cap, but not if it was cancelled due to an ill-formed manifest or + exceeding the time limit. Reported only if global_ranking is true. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + bengr@chromium.org + + The percent of manifests for which all resources have been downloaded. + Logged per prefetch run. + + + + + + Removed July 29 2015. + + twifkak@chromium.org + bengr@chromium.org + + The total number of response bytes received from all prefetch requests, + including config, manifests, and resources. Logged per prefetch run. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + + The total number of response bytes in 24 hours received over the network + from all prefetch requests, including config, manifests, and resources. + Logged during the next precache run after the 24 hours has elapsed. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + bengr@chromium.org + + The total number of response bytes received over the network from all + prefetch requests, including config, manifests, and resources. Logged per + prefetch run. + + + + + + Removed July 11 2017. + + rajendrant@chromium.org + bengr@chromium.org + + The total number of response bytes received over the network for a wasted + resource precache fetch. Logged when a partially downloaded resource + precache fetch gets cancelled due to per-resource size limit or max precache + size limit. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + bengr@chromium.org + + The total number of response bytes contained in all prefetch requests, + including config, manifests, and resources. Logged per prefetch run. + + + + + + Removed July 11 2017. + + twifkak@chromium.org + bengr@chromium.org + + The time, in milliseconds, to complete a prefetch run. Only applies to + non-cancelled runs (those for which PercentCompleted is 100). + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + The freshness lifetimes of the resources that were precached from the moment + they were fetched or revalidated as described in RFC 2616 13.2.4. Logged per + precache request. + + + + + + Removed March 7 2017. + + twifkak@chromium.org + bengr@chromium.org + + The latency for requests that were not made during precaching. Logged + per-request. + + + + + + Removed March 7 2017. + + twifkak@chromium.org + bengr@chromium.org + + Like Precache.Latency.NonPrefetch, but limited to requests with a referer + not in the user's top visited hosts. See History.TopHostsVisitsByRank for + details on the top hosts computation. + + + + + + Removed March 7 2017. + + twifkak@chromium.org + bengr@chromium.org + + Like Precache.Latency.NonPrefetch, but limited to requests with a referer in + the user's top visited hosts. See History.TopHostsVisitsByRank for details + on the top hosts computation. + + + + + + Removed March 7 2017. + + twifkak@chromium.org + bengr@chromium.org + + The latency for requests that were made during precaching. Logged + per-request. + + + + + + Removed July 11 2017. + + rajendrant@chromium.org + bengr@chromium.org + + The time between successive precache periodic GCM task invocations. When + precache task is started, the time interval from previous task invocation is + logged. + + + + + + Removed July 11 2017. + + bengr@chromium.org + + The number of bytes during user browsing that were served from the cache, + but would have been downloaded over a network if precaching was disabled. + Logged per-request. + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + The freshness lifetimes (RFC 2616 13.2.4) of the resources that were + precached and later used (and thus served from the cache). This is computed + at serving time and thus possibly different from the precached value if the + cache entry was revalidated. Logged per-request but only once per URL and + precaching cycle (as Precache.Saved). + + + + + + Removed July 11 2017. + + jamartin@chromium.org + bengr@chromium.org + + The time between the the beginning of the last precache session and each of + the URL fetches made by the user ever since. Logged per-request. + + + + + + Removed March 31 2020. + + dom@chromium.org + yhirano@chromium.org + yoavweiss@chromium.org + + Recorded when a prefetch request is made, and when a prefetch request is + redirected. Specifically, PrefetchURLLoader::PrefetchURLLoader records + "Prefetch request made", and PrefetchURLLoader::FollowRedirect + records one of the two redirection values. This is to collect data on how + often prefetch requests experience redirects. Note that when the + PrefetchRedirectError flag is enabled, no events are recorded. We do not + want to interact with this histogram when we're experimenting with the + redirect mode for prefetch requests. + + + + + + Removed 07/2019. + + rkaplow@chromium.org + The amount of time that elapsed during CreateProfilePrefs. + + + + + Removed as of 7/2019. No longer needed. + + petewil@chromium.org + + Count events where Network Prediction was enabled or disabled. + + + + + + Removed 5/25/2016 in favor of PreloadScanner.Counts2 + + csharrison@chromium.org + The number of preloads generated by the preload scanner. + + + + + Removed 5/25/2016 in favor of PreloadScanner.Counts2.Miss + + csharrison@chromium.org + + The number of unused preloads generated by the preload scanner. Note that + some link rel preloads are not referenced until after this point, so they + will be falsely marked as preload misses. These will show up in the Raw + bucket. + + + + + + Removed Feb 2018, no longer useful. + + csharrison@chromium.org + The number of preloads generated by the preload scanner. + + + + + Removed Feb 2018, no longer useful. + + csharrison@chromium.org + + The number of unused preloads generated by the preload scanner. Note that + some link rel preloads are not referenced until after this point, so they + will be falsely marked as preload misses. + + + + + + DocumentWriteEvaluator was removed in 07/2017 + + csharrison@chromium.org + + Time spent executing a script tag in the blink preload scanner, for the + purpose of preloading scripts that will be fetched via a call to + document.write. The execution failed to generate a preload request. + + + + + + DocumentWriteEvaluator was removed in 07/2017 + + csharrison@chromium.org + + Time spent executing a script tag in the blink preload scanner, for the + purpose of preloading scripts that will be fetched via a call to + document.write. The execution successfully resulted in a preload request. + + + + + + DocumentWriteEvaluator was removed in 07/2017 + + csharrison@chromium.org + + The reason a particular inline script was blocked from evaluation. + + + + + + DocumentWriteEvaluator was removed in 07/2017 + + csharrison@chromium.org + + Time spent initializing a new V8 context for the purpose of evaluating it + and preloading document.written strings. + + + + + + No longer needed + + csharrison@chromium.org + + The length of the inline script that is being considered for document write + evaluation. + + + + + + Removed August 2018 + + csharrison@chromium.org + + The number of preloads generated by scanning an external preloaded CSS + resource. As of 4/25/2016 this only includes @import declarations. + + + + + + Removed August 2018 + + csharrison@chromium.org + + Microseconds it took to scan the first chunk of external CSS for preloads. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed May 2018 + + csharrison@chromium.org + + The time between preload discovery and when the resource is actually + referenced. This is implemented by marking when a preload is discovered by + the scanner, and when it has its first ResourceClient added to it. Note that + for link rel preloads, this tracks the time from scanner discory to DOM + discovery of the link declaration, not the actual resource. + + + + + + Removed May 2018 + + csharrison@chromium.org + + The time between preload discovery and when the first bytes of the response + data arrive. + + + + + + Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). + + davidben@chromium.org + pasko@chromium.org + + Time from when a prerendered page is abandoned to when it is first used due + to user navigation. If the page is swapped before begin abandoned, a zero is + recorded. + + + + + + Removed March 13 2015. + + pasko@chromium.org + + Enumeration of what types of cookies were sent for a prerender. + + + + + + Removed March 13 2015. + + pasko@chromium.org + Enumeration of what cookie actions a prerender caused. + + + + + Removed Dec 12 2014. + + + Enumeration of what events related to prerendering have occurred. + + + + + + deprecated May 10 2012 + + Please list the metric's owners. Add more owner tags as needed. + Hover Event counts for prerendering. + + + + + deprecated 2016-05-12 + + + Final status for prerender pages - either success, or why it was canceled. + This is for the MatchComplete set of pages (including some pages that were + not actually prerendered), to match the control group. + + + + + + Removed Jan 14 2014. + + Please list the metric's owners. Add more owner tags as needed. + + For prerenders that are swapped in, the percentage of pixels that is already + final at swap-in time compared to when the spinner stops. + + + + + + deprecated May 10 2012 + + Please list the metric's owners. Add more owner tags as needed. + + Duration that a user hovers a link before clicking on it. + + This is recorded for all pages loaded in a session. + + + + + + deprecated May 10 2012 + + Please list the metric's owners. Add more owner tags as needed. + + Duration that the mouse pointer hovers on a link before the mouse pointer + moves off of it. + + This is recorded for all pages loaded in a session. + + + + + + Removed April 2015 + + pasko@chromium.org + + Enumeration of what events related to the local predictor have occurred + + + + + + Removed April 2015 + + pasko@chromium.org + + Time to perform the LoggedIn Lookup for the local predictor. This operation + checks whether a user is likely logged into a page that we would like to + prerender. + + + + + + Removed April 2015 + + pasko@chromium.org + + The PrerenderLocalPredictor uses local browsing history and the prerender + service to predict pages likely visited soon. Some of these URLs are + prefetched. When such prefetched likely next pages are visited, this + histogram records the PLT for such pages. In particular, this also happens + if prefetch is actually disabled, allowing (by pivoting on whether or not + prefetch is enabled) to compare the effect of prefetch on PLT. + + + + + + Removed April 2015 + + pasko@chromium.org + + Time to perform the Service Lookup for the local predictor. This operation + queries a Google service to obtain pages to prerender, as well as whether + prerender candidate pages are likely safe for prerendering. + + + + + + Removed April 2015 + + pasko@chromium.org + + Time from when a prerendered page is started to when it is first used due to + user navigation. If the page is never used, it is not included in this + histogram. This only refers to prerenders based on the local predictor. + + + + + + Removed April 2015 + + pasko@chromium.org + + Time to perform the URL Lookup for the local predictor. This operation + retrieves from the user's local browsing history the URLs corresponding to + URLIDs. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + The transition type for each new visit as recorded in the local visits + database. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + Size of the local visits database (number of entries). + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + Enumeration of what events related to local visits have occurred + + + + + + Removed as of 10/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Previous version of the Prerender.PagespeedHeader.* histograms. + + + + + + Removed May 13th 2014, use Prerender.NetworkBytesTotalForProfile instead. + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents + deletion. Includes prerender bytes. Bytes are only counted when prerendering + is enabled and not in a control group. The sum of the distribution for a + single user represents all of that user's network transfers for resource for + that time period while prerendering was enabled. + + + + + + Removed May 13th 2014, use Prerender.NetworkBytes.Used instead. + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been + used). + + + + + + Removed May 13th 2014, use Prerender.NetworkBytes.Wasted instead. + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead) for a prerender that was not used. + + + + + + Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been + used). + + + + + + Removed December 28, 2016, use Prerender.PrefetchAge instead. + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + Time between the prefetch and the actual load of the page. + + + + + Removed 2020-04, as NoStatePrefetch is launched everywhere. + + pasko@chromium.org + + A boolean that indicates whether the Omnibox navigation being committed + could have been prerendered by the Omnibox Prerender system. This provides + an upper bound for Prerender.OmniboxNavigationsUsedPrerenderCount and allows + the potential for Omnibox Prerendering coverage to be understood. If Omnibox + Prerendering is disabled, this histogram will register a 'false' entry. The + total count is the equivalent of the deprecated + NetworkActionPredictor.NavigationCount histogram. + + + + + + Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). + + pasko@chromium.org + + The number of navigations that use a prerender initiated from the Omnibox. + The count is incremented when the Prerendered tab is swapped in if the + Prerender was initiated by the Omnibox, which obviously requires + Prerendering from the Omnibox to be enabled. + + + + + + Removed 2017-09. + + pasko@chromium.org + + The number of prerenders initiated from the Omnibox. This is incremented + when the NetworkActionPredictor suggests Prerendering as an optimal strategy + given the text the user has entered and the Autocomplete suggestion + currently selected. It is only incremented if Prerendering from the Omnibox + is enabled. + + + + + + Removed April 2018 + + pasko@chromium.org + + The number of responses received bucketed into the range [0,4]: bucket 0 is + the total number of responses received; bucket 1 is the number of responses + received with an X-Mod-Pagespeed header [indicating a mod_pagespeed server]; + bucket 2 is the number of responses received with an X-Page-Speed header and + a header value in the X-Mod-Pagespeed format (a.b.c.d-e) [indicating an + ngx_pagespeed server]; bucket 3 is the number of responses received with an + X-Page-Speed header and a header value in the PageSpeed Service format + (a_b_c) [indicating a PSS server]; and bucket 4 is the number of responses + received with an X-Page-Speed header and a header value in neither of the + preceding formats [indicating some other server; IISpeed is the only known + one at this stage]. + + + + + + Removed April 2018 + + pasko@chromium.org + + The number of responses received that either have an X-Mod-Pagespeed header + or have an X-Page-Speed header with a value in the X-Mod-Pagespeed format + (a.b.c.d-e), bucketed into the range [1,99]: bucket 1 is for header values + that aren't in the a.b.c.d-e format, the remaining buckets are an encoding + of the value: 2 + 2 * (max(c, 10) - 10) + (d > 1 ? 1 : 0). The rationale + is that 'c' is incremented with each new release and 'd' is initially 0 but + is incremented for each patch to a release. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + Types of pages rendered. + + + + + deprecated March 30, 2015 + + pasko@chromium.org + + Indicates whether the user has ever visited (in the past) a URL for which a + prerender is launched. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLT_ContentPrefetchPrerenderControl. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This particular histogram is for all page loads for users who do not have + prerendering enabled. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLTMatched_ContentPrefetchPrerenderControl. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This particular histogram is only for pages that would have been prerendered + if the user had prerender enabled. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLTMatched_ContentPrefetchPrerender. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This particular histogram is for all prerendered page loads for users who + have prerender enabled. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLT_ContentPrefetchPrerender. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This particular histogram is for all page loads for users who have + prerendering enabled. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLTWindowed_ContentPrefetchPrerenderControl. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This particular histogram is for all page loads within 30 seconds after a + prefetch tag is seen for users who do not have prerendering enabled. + + + + + + Removed 03/24/11. Replaced by + Prerender.PerceivedPLTWindowed_ContentPrefetchPrerender. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load pre navigation. + + This particular histogram is for all page loads within 30 seconds after a + prefetch tag is seen for users who have prerendering enabled. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded for all pages loaded in a session. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded for the first page load completing immediately after a + prerender. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + "FirstAfterMiss" means the first pageload after a prerender miss. + There are two types: Any, and Non-overlapping. The latter only applies to + page loads initiated after the prerender. This variable records cases where + only Any triggered. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + "FirstAfterMiss" means the first pageload after a prerender miss. + There are two types: Any, and Non-overlapping. The latter only applies to + page loads initiated after the prerender. This variable records cases where + both triggered. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded for the first page load completing immediately after a + prerender, but which has also started after the prerender has been + initiated. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + "FirstAfterMiss" means the first pageload after a prerender miss. + There are two types: Any, and Non-overlapping. The latter only applies to + page loads initiated after the prerender. This variable records cases where + only Non-overlapping triggered. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded only for prerendered pages, or for pages which would have + been prerendered in the control case. + + + + + + Removed August 2016 + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded only for prerendered pages, or for pages which would have + been prerendered in the control case. + + In MatchedComplete, the prerender group also contains cancelled prerenders, + so as to produce a perfect match of page views attributed this group in the + prerender group with those attributed to this group in the control group. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded for all page loads which happen within 30 seconds after a + prefetch tag is observed. + + + + + + Removed 2017-03. + + pasko@chromium.org + + Time from when a user navigates to a page to when it loads. Since the pages + may start loading before the user navigates to it, this does not include any + portion of load prior to navigation. + + This is recorded for all page loads which happen within 30 seconds after a + prefetch tag is observed and which do not correspond to a prerender tag. + + + + + + Obsoleted in Feb 2019. + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Whether the perceived Time to First Contentful Paint (TTFCP) was recorded + successfully for a prerendered page. Since a prerendered page will start + loading before a user navigates to it, the perceived TTFCP does not include + an time prior to the user navigation. If true, there is an associated + PrefetchTTFCP that records the TTFCP from the swapped-in navigation start. + If false, no PrefetchTTFCP was recorded. + + + + + + Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). + + pasko@chromium.org + + For prerenders that are swapped in, the percentage of the time from load + start until the onload event fires that has elapsed at the time of the + swapin. + + + + + + Removed 2020-04. + + pasko@chromium.org + + How long the cleanup portion of PrerenderManager::PeriodicCleanup takes, to + measure jank. + + + + + + Removed 2020-04. + + pasko@chromium.org + + How long the resource check portion of PrerenderManager::PeriodicCleanup + takes, to measure jank. + + + + + + Deprecated July 2020 + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Time between a prefetch or effective prefetch and the actual load of the + page. For NoState prefetch, this is the time of the actual prefetch. For + prerendering, it is the time that prerender began. For control groups in + NoState prefetch experiments, it is the time that prefetch would have + occurred. + + + + + + Deprecated July 2020 + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Time to first contentful paint (TTFCP) for navigations related to prefetch + (including prerender, no-state prefetch, and associated experiments). This + measures user-visible TTFCP. For no-state prefetch this is standard + navigation-to-FCP; for prerender this is the time from navigation start when + the prerender is swapped in to FCP. + + + + + + Removed 2017-03. + + pasko@chromium.org + + After launching a prerender, how many simultanious prerenders are recorded + as running, out of a maximum of three. + + + + + + Removed 2017-03. + + pasko@chromium.org + + For prerenders that finish loading before they are ever swapped in, their + page load time until the onload event fires. + + + + + + Removed 2020-05-07 + + justincohen@chromium.org + + This is the time from when a prerendered page begins to load to when it is + swapped in as the main page load. Recorded when the swap occurs, only on + iOS. + + + + + + Removed 2020-04. + + pasko@chromium.org + + For each prerender link added to a document, records the rel types present + on the link element. + + + + + + Removed 2020-04. + + pasko@chromium.org + + For each prerender in a document which starts prerendering, records the rel + types present on the link element. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + This is the time from when a prerendered page finishes loading to when it is + displayed, as measured by the renderer process. When a page is displayed + before it finishes loading, no value is recorded in this histogram. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + Perceived load time of a page, as measured by the renderer process. For + non-prerendered pages, this is just BeginToFinish. For displayed prerendered + pages, this is the time from when the prerendered page is moved into a + TabContents until finish. "Finish" == after onload() and all + resources are loaded. Note that this is 0 if the loading finishes before the + page is moved into a TabContents. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + Perceived load time of a prerendered page that is displayed, as measured by + the renderer process. This is the time from when the prerendered page is + moved into a TabContents until finish. "Finish" == after onload() + and all resources are loaded. Note that this is 0 if the loading finishes + before the page is moved into a TabContents. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + + The time elapsed between when the prerendering of a page starts and when the + page is displayed, as measured by the renderer process. Prerendered pages + discarded without being displayed are excluded from this count. + + + + + + Removed 2020-04. + + pasko@chromium.org + + The detailed reason why a prerender is canceled with + FINAL_STATUS_UNSUPPORTED_SCHEME + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + Enumeration of how prerender was used per session. + + + + + Removed Dec 12 2014. + + pasko@chromium.org + Time to perform the session storage namespace merge. + + + + + Removed April 2015 + + pasko@chromium.org + + For simulated local browsing prerendering, the baseline PLT of pages without + any prerendering for pages that would be prerendered. + + + + + + Removed April 2015 + + pasko@chromium.org + + For simulated local browsing prerendering, the estimated PLT of pages with + prerendering enabled for pages that would be prerendered. + + + + + + Obsoleted in Dec 2019. + + pasko@chromium.org + + A boolean that indicates how often we suppress a dialog from a tab when + swapping it with a prerender. + + + + + + Removed April 2015 + + pasko@chromium.org + + Enumeration of what events related to the TabHelper class have occurred. + + + + + + Removed 2017-09. + + pasko@chromium.org + Time between subsequent prerender requests. + + + + + Removed 2017-09. + + pasko@chromium.org + + The time elapsed between the most recent visit to a URL and when an + attempted prerender of the same URL is cancelled with + FINAL_STATUS_RECENTLY_VISITED. + + + + + + deprecated Nov 16 2012 + + Please list the metric's owners. Add more owner tags as needed. + Duration that a user hovers a link before clicking on it. + + + + + deprecated Nov 16 2012. See Prerender.TimeUntilUsed2, which has a larger + range. + + Please list the metric's owners. Add more owner tags as needed. + + Time from when a prerendered page is started to when it is first used due to + user navigation. If the page is never used, it is not included in this + histogram. + + + + + + Removed 2017-09 as prerenders can no longer be 'used' (=='swapped-in'). + + pasko@chromium.org + + Time from when a prerendered page is started to when it is first used due to + user navigation. If the page is never used, it is not included in this + histogram. + + + + + + Functionality removed in M77. + + bengr@chromium.org + tbansal@chromium.org + + User interactions with the Lo-Fi context menu options. These include: + + Displays and clicks on the "Load image" and "Load + images" context menu options. Count of pages where the user has clicked + "Load image" at least once. + + + + + + Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in + 07/2019. + + jegray@chromium.org + + Records the result of loading the metadata while initializing the + HintCacheLevelDBStore. + + + + + + Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in + 07/2019. + + jegray@chromium.org + + Records each status change within the HintCacheLevelDBStore. + + + + + + Replaced by OptimizationGuide.HintCacheLevelDBStore.LoadMetadataResult in + 07/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records that a fetched hint loaded from the store has expired. If expired, + the hint is not provided. + + + + + + Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.HostCount in + 06/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts selected for sending a OnePlatform client hint + request. This will be captured when any OnePlatform client hint request is + initiated. + + + + + + Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.NetErrorCode in + 06/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + Net error codes for HintsFetch requests to the Optimization Guide Service on + success and failure. + + + + + + Replaced by OptimizationGuide.HintsFetcher.GetHintsRequest.Status in + 06/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + For each HintsFetch request to the Optimization Guide Service, log the HTTP + response code on success and failure. + + + + + + Replaced by + OptimizationGuide.HintsFetcher.TopHostProvider.BlacklistSize.OnInitialize in + 06/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts placed on the HintsFetcherTopHostBlacklist when + it is initialized. + + + + + + Replaced by + OptimizationGuide.HintsFetcher.TopHostProvider.BlacklistSize.OnRequest in + 06/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts on the HintsFetcherTopHostBlacklist when top + hosts are requested. + + + + + + Removed in M76. + + bengr@chromium.org + tbansal@chromium.org + + User interactions with the previews "Saved data" infobar. These + include: + + Displays of the infobar and clicks on the "Load original" link. + Whether the infobar was dismissed by navigation or the user clicking on + "X" close button. + + + + + + Replaced by Previews.StalePreviewTimestampShown as of 09/2018. + + megjablon@chromium.org + + Whether the timestamp for a stale preview was shown on the infobar. If the + timestamp was not shown, states the reason why. + + + + + + Offline Previews functionality removed in M86. + + robertogden@chromium.org + tbansal@chromium.org + + Whether or not an offline preview that was committed showed an error page. + This metric is recorded every time an offline preview is committed. + + + + + + Offline Previews functionality removed in M86. + + robertogden@chromium.org + ryansturm@chromium.org + + Whether or not the navigated URL was allowed to trigger an offline preview. + This is done by checking an in-memory cache of all available offline + previews which is designed to prevent false positive triggering. This metric + is recorded on every preview eligible navigation when the + OfflinePreviewsFalsePositivePrevention feature is enabled. + + + + + + Offline Previews functionality removed in M86. + + robertogden@chromium.org + ryansturm@chromium.org + + The number of entries in the false positive prevention pref. This is + recorded every time we update the pref from a DB query, at most once per + session. + + + + + + Removed July 2019. + + robertogden@chromium.org + + Whether the verbose status string was shown on a Preview page. This is + recorded on every transition from a non-preview page to a preview page. An + entry of false means that the Previews Icon appeared without the + "Lite" string only because there was not enough room to show the + string. + + Note that it is possible for the Lite string to not be shown on the page + after true is recorded if the user rotates their device or enters + multi-window mode while viewing the page, or the converse. + + + + + + Removed in favor of OptimizationGuide.OptimizationFilterStatus as of + 07/2019. + + dougarnett@chromium.org + + Status of processing OptimizationFilter configurations for server-provided + blacklists. Recorded when the PreviewsOptimizationGuide receives a + notification to process hints. + + + + + + Removed in favor of OptimizationGuide.HintCache.FetchedHint.TimeToExpiration + as of 08/2019. + + mcrouse@chromium.org + dougarnett@chromium.org + + The remaining time a fetched hint that was loaded for use has before it + expires and is removed from the hint cache store. + + + + + + Removed in favor of OptimizationGuide.HintCache.HasHint.AtCommit as of + 08/2019. + + dougarnett@chromium.org + + Records the effective connection type when the optimization guide hint cache + has a hint entry for a URL's host at commit time. + + + + + + Removed in favor of OptimizationGuide.HintCache.HasHint.BeforeCommit as of + 08/2019. + + dougarnett@chromium.org + + Records the effective connection type when the optimization guide hint cache + has a hint entry for a URL's host before commit time (e.g., at original + navigation time or redirected navigation time). + + + + + + Replaced by OptimizationGuide.HintCache.HintType.Loaded in 07/19. + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the store entry type of a hint when it is loaded from the hint cache + store. + + + + + + Removed in favor of OptimizationGuide.HintCache.HostMatch.AtCommit as of + 08/2019. + + dougarnett@chromium.org + + Records the effective connection type when the optimization guide hint cache + has a loaded hint entry matching a URL's host at commit time. This is + recorded regardless of whether an associated preview type is allowed for the + navigation or not. If no associated preview type is allowed, the hint will + not be loaded from a backing store, so this will only capture matches for + in-memory hints. + + + + + + Removed in favor of OptimizationGuide.HintCache.PageMatch.AtCommit as of + 08/2019. + + dougarnett@chromium.org + + Records the effective connection type when the optimization guide hint cache + has a loaded page hint for a URL at commit time. This is recorded regardless + of whether an associated preview type is allowed for the navigation or not. + If no associated preview type is allowed, the hint will not be loaded from a + backing store, so this will only capture matches for in-memory hints. + + + + + + No longer used as of 06/2018. + + ryansturm@chromium.org + + The number of rows in the Previews opt out SQLite table at profile startup. + + + + + + No longer used as of 06/2018. + + ryansturm@chromium.org + + The SQLite error code that the previews opt out store saw when trying to + open the SQLite database. This is logged when an unexpected error occurs + when trying to open the database file. + + + + + + Merged with OptimizationGuide.ProcessHintsResult in 07/2019. + + dougarnett@chromium.org + + Whether processing the previews hints succeeded and if any previews hints + were found. Recorded when the PreviewsOptimizationGuide receives a + notification to process hints. + + + + + + Removed in M84. + + robertogden@chromium.org + + The reason that a navigation is blacklisted from loading a server lite page + preview by a dynamic blacklist. Recorded only after the observed navigation + has passed static eligibility checks. + + + + + + Removed in M84. + + robertogden@chromium.org + tombergan@chromium.org + src/components/data_reduction_proxy/OWNERS + + Whether or not the server directed Chrome to blacklist the requested host on + a bypass response. + + + + + + Replaced January 2019 by Previews.ServerLitePage.Penalty.* + + robertogden@chromium.org + + The time spent on a navigation request that loaded a fallback signal from + the lite page previews server. This does not include any penalty incurred + because of network errors. + + + + + + Removed in M84. + + robertogden@chromium.org + + The reasons that a navigation is not eligible to be shown a server lite page + preview by static eligibility checks. Each check is evaluated on every + observed navigation when the feature is enabled. + + + + + + Removed November 2018 when PLM support was reverted. + + robertogden@chromium.org + + Every time a navigation is restarted on account of this preview we attempt + to report the cumulative total penalty to page load metrics. This histogram + tracks penalties that were not successfully reported. The penalty is the + amount of time between the navigation start of the original (i.e.: + user-initiated) navigation and the current navigation when this histogram is + reported. This histogram is reported at the start of every navigation for + every navigation seen by the Lite Page Redirect Navigation Throttle. + + + + + + Removed in M79. + + robertogden@chromium.org + + The lost time spent attempting a server lite page via canceling and + restarting navigations. This value is the difference between the final + navigation's start time and the start time of the original navigation. This + metric is recorded everytime the Previews NavigationThrottle acts on a + response, whether that is from the previews server or a network error. + + This histogram is only recorded in M73 for the non-URLLoader implementation + of this feature. For M72, refer to + Previews.ServerLitePage.HttpOnlyFallbackPenalty which records this penalty + for failure statuses only. + + + + + + Removed in M84. + + robertogden@chromium.org + tbansal@chromium.org + + Recorded whenever lite page preview predictor preconnects to a URL. True is + recorded when the URL that is preconnected is for the lite pages previews + server, False is when the origin is preconnected. + + + + + + Removed in M84. + + robertogden@chromium.org + tbansal@chromium.org + + Recorded whenever the lite page preview predictor state is changed. True is + recorded when preresolving or preconnecting starts and False is recorded + when it stops. + + + + + + Removed in M84. + + robertogden@chromium.org + tbansal@chromium.org + + Recorded whenever lite page preview preresolver preresolves a URL. True is + recorded when the URL that is preresolved is for the lite pages previews + server, False is when the origin is preresolved. + + + + + + Removed November 2018 when PLM support was reverted. + + robertogden@chromium.org + + Every time a navigation is restarted on account of this preview we attempt + to report the cumulative total penalty to page load metrics. This histogram + tracks penalties that were successfully reported. The penalty is the amount + of time between the navigation start of the original (i.e.: user-initiated) + navigation and the current navigation when this histogram is reported. This + histogram is reported at the start of every navigation for every navigation + seen by the Lite Page Redirect Navigation Throttle. + + + + + + Removed in favor of + Previews.ServerLitePage.ServerNetError.(After|Before)Commit + + robertogden@chromium.org + ryansturm@chromium.org + + The net error from connecting to the previews server. Recorded every time a + connection to the server is finished. + + + + + + Removed in M84. + + robertogden@chromium.org + ryansturm@chromium.org + + The net error from connecting to the previews server after commit. Recorded + every time a connection to the server is finished after commit. + + + + + + Removed in M84. + + robertogden@chromium.org + ryansturm@chromium.org + + The net error from connecting to the previews server before commit. Recorded + every time a connection to the server is finished before commit. + + + + + + Removed in M84. + + robertogden@chromium.org + + The type of response given by the previews server when a server lite page + preview was triggered. + + + + + + Replaced by Previews.ServerLitePage.PredictorToggled. + + robertogden@chromium.org + tbansal@chromium.org + + Recorded whenever the lite page preview preresolver state is changed. True + is recorded when preresolving starts and False is recorded when it stops. + + + + + + Removed in M79. + + robertogden@chromium.org + + Whether or not the server lite page preview is triggered. Recorded on every + observed navigation when the feature is enabled. + + + + + + Removed in M84. + + ryansturm@chromium.org + + Whether or not the server lite page preview was attempted during a + navigation. Recorded when the lite page URLLoader feature is enabled, during + any leg of the navigation (redirects trigger recording the histogram). + + + + + + Stale timestamp functionality removed in M86. + + robertogden@chromium.org + + Whether the timestamp for a stale preview was shown on the UI. If the + timestamp was not shown, states the reason why. + + + + + + Replaced by Previews.Triggered.EffectiveConnectionType2 as of 01/2019. + + dougarnett@chromium.org + + Records the effective connection type of a navigation that triggers a + preview. This is captured for slow page preview types - that is, ones that + support variable thresholds depending on matching a page pattern in the + optimization guide hints. + + + + + + Removed 06/2017 as part of crbug.com/734161. + + thestig@chromium.org + + Count of events in PrinterService on Chrome OS related to USB printers. + + + + + + Removed 2020-05. + + valleau@chromium.org + skau@chromium.org + + Records the source from which a network printer was configured in Chrome OS + if it was setup automatically with unpopulated make and model fields. Used + to determine the source pathway from which printers without any make and + model information are able to be setup automatically with a PPD. + + + + + + Removed 2020-05. + + valleau@chromium.org + skau@chromium.org + + Records the source from which a USB printer was configured in Chrome OS if + it was setup automatically with unpopulated make and model fields. Used to + determine the source pathway from which printers without any make and model + information are able to be setup automatically with a PPD. + + + + + + Removed 06/2020 because it is not longer needed (Issue 1046125). + + luum@chromium.org + skau@chromium.org + + Records when a synced printer's invalid PPD reference has been resolved by + stripping off the autoconf flag. Recorded during initial sync across + PrintersSyncBridge. + + + + + + Most users do not provide their own PPDs. + + skau@chromium.org + + Records the source of PostScript Printer Description files used during + printer setup. Entries are recorded for every attempted configuration. Only + recorded on Chrome OS. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + nikitapodguzov@chromium.org + skau@chromium.org + + The number of entries in the print job database. Recorded when the database + is initialized. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + nikitapodguzov@chromium.org + skau@chromium.org + + The size in bytes of the entry in the print job database. Recorded every + time when new print job is written to the database. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + nikitapodguzov@chromium.org + skau@chromium.org + + Records the time it takes to fetch compeleted print jobs from the database. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + nikitapodguzov@chromium.org + skau@chromium.org + + Indicates whether we were successful performing saving print job database + operation. + + + + + + Removed 09/2020 as it is no longer needed for analysis. + + nikitapodguzov@chromium.org + skau@chromium.org + + Indicates whether we were successful performing deleting print jobs database + operation. + + + + + + Removed 2020-04. + + valleau@chromium.org + skau@chromium.org + + Records whether a printer supports the + pwg-raster-document-resolution-supported attribute. + + + + + + Removed in 2020-06. kUseFrameAssociatedLoaderFactory has shipped in M83 and + Printing.FrameIsActiveOnCreateLoaderFactory is true in 100% of cases on all + platforms. + + yhirano@chromium.org + lukasza@chromium.org + + Records whether the associated frame is active when + PrepareFrameAndViewForPrint::CreateURLLoaderFactory is called. If it is + always active we want to replace the CreateFailingURLLoaderFactory call with + a DCHECK. + + + + + + Removed 01/2015 as part of crbug.com/278148. + + thestig@chromium.org + + Count of font file formats embeeded in print preview PDFs. These numbers are + biased by what the platforms supports in terms of detection. + + + + + + No longer used as of 09/2017. + + thestig@chromium.org + + Actions performed by the user when the Google Cloud Print add-printers + promotion is shown to the user. + + + + + + No longer used as of 07/2019. + + nasko@chromium.org + + Logged when a document calls the window.print() API. The boolean value + indicates whether it is invoked by the main frame. It will be false for + documents in subframes. + + + + + + No longer used as of 07/2019. + + nasko@chromium.org + + Logged when a document calls the window.print() API in any frame. The + boolean value will be true when the API call is invoked by a document which + is in a process different than the top level document. It will be false in + all other cases. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The page count of the initial print preview, a.k.a. the total number of + pages in documents to be printed. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to PDF and + opened in Preview.app on Mac. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to a cloud + printer. + + + + + + No longer used as of 01/2016. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to a cloud + printer using web dialog. + + + + + + Removed 07/2019. + + rbpotter@chromium.org + thestig@chromium.org + + The final page count (after page selection) of documents printed to Google + Drive. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to PDF. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to a + printer. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to an + extension printer (using printerProvider API). + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed to a privet + printer. + + + + + + Removed 07/2019. + + thestig@chromium.org + + The final page count (after page selection) of documents printed using + system dialog. + + + + + + Removed 07/2019. + + rbpotter@chromium.org + + Actions taken on the PDF viewer inside Print Preview's preview area. + + + + + + Removed 06/2020. + + thestig@chromium.org + Print preview events. + + + + + Removed 01/2020. + + alexmos@chromium.org + + The number of cross-site frames contained in a document being printed, as + defined by comparing scheme and eTLD+1. + + + + + + Removed 01/2020. + + alexmos@chromium.org + + The number of cross-site visible frames contained in a document being + printed. + + + + + + Removed 01/2020. + + alexmos@chromium.org + + The number of out-of-process frames contained in a document being printed. + + + + + + Removed as of 4/2018. + + dullweber@google.com + msramek@google.com + + Logs whether the UserEventServiceReady is ready when recording a consent. + This should always be true as the service is created at startup. + + + + + + The check seems to be needed for as long as Windows 7 is supported. Removed + 2020-05. + + pastarmovj@chromium.org + + Measure how often the automatic recognition for terminal services + environment would have incorrectly decided that the job object should be + applied, when it shouldn't have been as dictated by the flag + --allow-no-sanbox-job. This histogram will guide the final removal of the + flag, which will be possible when the number of false values becomes + insignificant. + + + + + + Replaced by PolicyGlobalSizeOnSuccess as failure cases were uninteresting. + Removed 2020-04. + + ajgo@chromium.org + src/sandbox/policy/win/OWNERS + + Size of policy global memory used when policy was committed on Windows for + all outcomes. 0 indicates that no rules were used. + + + + + + Policy size reduced, metric no longer required. Removed 2020-06. + + ajgo@chromium.org + src/sandbox/policy/win/OWNERS + + Size of policy global memory used when policy was committed after successful + process start on Windows. 0 indicates that no rules were used. + + + + + + Removed 04/2020. See crrev.com/c/2129507 + + + + mrefaat@google.com + The time spent in product tour screens for ios. + + + + + Not accessed in months. All results say "authentication was + unnecessary". Removed 2020-03. + + bcwhite@chromium.org + + Counts of authorization results when trying to open a locked profile from + the User Manager. + + + + + + No longer recorded as of M87. + + chengx@chromium.org + Load status of an avatar for decorating the Windows taskbar + + + + + Removed 07/2019. + + rkaplow@chromium.org + Length of time to setup profile. + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the CreateBrowserContextServices call + within OnPrefsLoaded. + + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during ProfileManager::CreateProfileHelper. + This is called when a profile is created synchronously (usually at startup). + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Back-end time elapsed while creating a new profile. The max is 30 seconds, + when an external timeout was applied. + + + + + + Removed as of 8/2013. + + Please list the metric's owners. Add more owner tags as needed. + + Time elapsed before the user decided to cancel creation of a new profile. + Since only managed-user profile creation can be canceled, this time comes + from managed-user registration. The max is 30 seconds, when an external + timeout was applied. + + + + + + Removed as of 6/2019. + + treib@chromium.org + michaelpg@chromium.org + + Time elapsed from when the handler received the message that a user clicked + 'Create' until the user decided to cancel creation of a new profile. Since + only managed-user profile creation can be canceled, this time comes from + managed-user registration. + + + + + + Replaced by Profile.Menu.ClickedActionableItem in M81. + + msarda@chromium.org + tangltom@chromium.org + + Track user interactions that can be performed in the user menu and user + manager. The origin of the action, whether the an interaction in the content + area or some other source, is noted in the histogram suffix. + + + + + + Removed 02/2015. Profile.CreateAndInitializeProfile is more useful. + + rkaplow@chromium.org + Length of time to retrieve profile. + + + + + Removed 06/2020. There are no recordings of this event since M83. + + msarda@chromium.org + alexilin@chromium.org + + Whether Profile::GetProfileInfoPath is called with a profile that does not + have the user data directory as a parent directory. This is expected to + never happen, but there are a few events recorded on stable as of M80. This + metric should be removed once http://crbug.com/981374 is fixed. + + + + + + Removed 06/2020. There are no recordings of this event since M83. + + msarda@chromium.org + alexilin@chromium.org + + Whether Profile::InitProfileUserPrefs is called with a profile that does not + have the user data directory as a parent directory. This is expected to + never happen, but there are a few events recorded on stable as of M80. This + metric should be removed once http://crbug.com/981374 is fixed. + + + + + + Removed 03/2020. + + rogerta@chromium.org + + Number of times users launch a browser window from either a primary or + secondary profile (i.e., each time a browser window is opened we log which + type of profile it belongs to). + + + + + + Removed 12/2019. We do not lock profiles anymore. + + msarda@chromium.org + + How long locked profiles have been locked for. This is logged each time any + profile is loaded. Note that this does not track the total time the profile + was locked, but rather the span from when the profile was locked to when the + measurement takes place. + + + + + + Removed 2017-10-16. No longer tracked. Feature removed. + + mlerman@chromium.org + + Tracks user interactions with the 'Not You?' bubble that users can navigate + to from the Upgrade bubble after upgrade to the New Avatar Menu. + + + + + + Removed 2017-10-19. No longer tracked. Feature removed. + + mlerman@chromium.org + + Tracks user interactions with the signin bubble that appears in the New + Avatar Menu upon signin. This bubble appears after the user signs in using + the Inline Signin flow. + + + + + + Removed 2017-10-16. No longer tracked. Feature removed. + + mlerman@chromium.org + + Tracks user interactions with the bubble that appears for users in the new + avatar menu after upgrade. + + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the Notify() of + NOTIFICATION_PROFILE_CREATED during ProfileImpl::DoFinalInit(). + + + + + + Removed 2013-04-09. No longer tracked. See Profile.NumberOfProfiles. + + rogerta@chromium.org + + Counts the number of profiles on a user's machine whenever a profile is + added or deleted. + + + + + + Removed; replaced by Profile.NumberOfProfiles on 2013-04-09. Data are + suspect, especially after 2012-02-24: see https://crbug.com/189213. + + rogerta@chromium.org + + Counts the number of profiles on a user's machine when Chrome starts up. + + + + + + Removed; replaced by Profile.NumberOfSignedInProfiles on 2013-04-09. + + rogerta@chromium.org + + Counts the number of profiles that are signed in to Chrome when Chrome + starts up. + + + + + + Removed 03/2020. + + anthonyvd@chromium.org + + Counts the number of times profiles were switched in a browser session. This + value is incremented when a profile is switched to and the result is logged + during shutdown. + + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during ProfileImpl::OnLocaleReady. This + happens once after profile was loaded. + + + + + + Removed 04/2015, and replaced by Profile.OnLocaleReadyTime. + + rkaplow@chromium.org + + The amount of time that elapsed during ProfileImpl::OnPrefsLoaded. + + + + + + Removed because it did not present the information clearly. + + Please list the metric's owners. Add more owner tags as needed. + The frequency of ways that the profiles are opened. + + + + + Removed 03/2020. + + rogerta@chromium.org + + The frequency with which the user opens the different profile menus or + switches profiles. For the open statistics, this does not mean the user + necessarily opened a profile after clicking. The switch statistics indicate + how often and how the user switches profiles. They are provided together for + comparison of how often the user actually switches after opening the avatar + bubble menu. + + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the ProfileImpl::DoFinalInit(). + + + + + + Removed 02/2020 since the histogram indicators were stable. + + dullweber@chromium.org + + The amount of time that elapsed during profile statistics calculation. + + + + + + Long removed. + + Please list the metric's owners. Add more owner tags as needed. + + The error code generated in the final step (registration step) of creating a + new supervised profile. + + + + + + Long removed. + + Please list the metric's owners. Add more owner tags as needed. + + The error code generated in the final step (registration step) of importing + a supervised profile. + + + + + + Long removed. + + Please list the metric's owners. Add more owner tags as needed. + + Time elapsed from when the handler received the message that a user clicked + 'Create' to create a new supervised user profile until the registration ends + either successfully or with a failure (both recorded in + Profile.SupervisedProfileCreateResult). + + + + + + Long removed. + + Please list the metric's owners. Add more owner tags as needed. + + Time elapsed from when the handler received the message that a user clicked + 'Import supervised user' until the registration ends either successfully or + with a failure (both recorded in Profile.SupervisedProfileImportResult). + + + + + + Removed because it did not present the information clearly. + + Please list the metric's owners. Add more owner tags as needed. + Activity of the user with regards to sync. + + + + + Removed 11/2018 as this histogram is not of sufficient value anymore. It + only records events made through the advanced settings dialog which are very + rare and not representative for most analysis purposes. + + tschumann@google.com + + Number of times the user signed into sync from original or secondary + profile. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + Size of the thumbnails database. + + + + + Removed 07/2019. Replaced by Profile.TimeToOpenUserManagerUpTo1min with the + max time increased from 10 seconds to 1 minute. + + msarda@chromium.org + tangltom@chromium.org + + Time required to open the UserManager, from when it started to show until + when its javascript started executing. + + + + + + Removed 6/3/2020. No longer needed. + + phillis@chromium.org + cmumford@chromium.org + + Record the result of updating taskbar decoration on Windows. + + + + + + Removed 8/2014. Upgrade Promotional UI removed. + + mlerman@chromium.org + + The process which leads a user to enroll in New Profile Management. Also + tracks if the user chooses to opt out, and tutorials which guide the user + into New Profile Management. + + + + + + Removed 07/2019. No longer tracked. + + engedy@chromium.org + vasilii@chromium.org + + Signifies if the user selected "Send feedback" checkbox in the + Reset Profile dialog. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Errors that Protector detects about default search provider in Web Data. + Reported once when Web Data is loaded. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + Errors that Protector detects about protected settings in Preferences. + Reported once when profile is loaded. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + When the default search provider setting is changed outside of Chrome, which + is detected by the Protector, this histogram reports the new setting. + + + + + + Removed 8/2013. No longer tracked. + + Please list the metric's owners. Add more owner tags as needed. + + When the startup settings are changed outside of Chrome, which is detected + by the Protector, this histogram reports the new setting. + + + + + + Removed 9/2016. Never added to histograms.xml and value is always 1. + + + The number of extensions overriding the proxy, triggering the proxy override + extension warning bubble. + + + + + + Removed April 2017. + + tasak@google.com + + The memory usage of the BlinkGC allocator after a background renderer is + purged and suspended. Note: this metric is for A/B testing. + + + + + + Removed April 2017. + + tasak@google.com + + The memory usage of the discardable memory after a background renderer is + purged and suspended. Note: this metric is for A/B testing. + + + + + + Removed April 2017. + + tasak@google.com + + The memory usage of the malloc after a background renderer is purged and + suspended. Note: this metric is for A/B testing. + + + + + + Removed April 2017. + + tasak@google.com + + The memory usage of PartitionAlloc after a background renderer is purged and + suspended. Note: this metric is for A/B testing. + + + + + + Removed April 2017. + + tasak@google.com + + The sum of the memory usages of PartitionAlloc, malloc, discardable memory, + mainThreadIsolate() and BlinkGC allocator after a backgrounded renderer is + purged and suspended. Note: this metric is for A/B testing. + + + + + + Removed April 2017. + + tasak@google.com + + The memory usage of mainThreadIsolate() after a backgrounded renderer is + purged and suspended. Note: this metric is for A/B testing. + + + + + + Removed Oct 2017. + + tasak@google.com + + This records how many tasks are still in task queues when a backgrounded + renderer is suspended. + + + + + + Removed April 2020 + + mamir@chromium.org + + When a message arrives for a lazy subscription and Chrome isn't in the + foreground, it is persisted on disk until next time Chrome is in the + foreground. This is recorded before adding the message the persisted queue + to estimate how large does the queue grow. + + + + + + Removed Dec 2019 + + peter@chromium.org + knollr@chromium.org + + When a message arrives to a subscription while Chrome is in the background, + the subscription is checked first for being lazy, and accordingly the + message is forwarded or persisted on disk. Since this check may require disk + access, this histogram measures the time spent in checking if the + subscription is lazy. + + + + + + Removed June 2019 + + jarrydg@chromium.org + + The number of days since an origin's data was last accessed. Logged upon + access when the time since last access is at least 24 hours. + + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + + Number of errors on evicting origin by QuotaTemporaryStorageEvictor in an + hour. + + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + + Number of errors on getting usage and quota by QuotaTemporaryStorageEvictor + in an hour. + + + + + + calamity@chromium.org + + The time since the evicted origin was last accessed. Logged when the origin + is evicted. + + + + + + jarrydg@chromium.org + Amount of free disk space for profile directory. + + + + + jarrydg@chromium.org + Initial quota for global temporary storage. + + + + + Removed July 2018 + + dgrogan@chromium.org + + Types of origins that are initially selected for eviction via LRU. Some of + these types are exempt from eviction. + + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of origins using persistent storage. + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of protected origins using persistent storage. + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of protected origins using temporary storage. + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of origins using temporary storage. + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of unlimited origins using persistent storage. + + + + + Expired on 2018-08-30. Removed in M74. + + tzik@chromium.org + Number of unlimited origins using temporary storage. + + + + + jarrydg@chromium.org + + Percentage of the storage device that is being use for temporary storage. + Logged at irregular intervals (during eviction). + + + + + + calamity@chromium.org + + Time since an origin was last chosen to be evicted from the storage, + recorded each time the origin is evicted (except for the first eviction). + + + + + + Removed June 2019 + + jarrydg@chromium.org + + Time spent querying the embedder for the settings values. Logged at + irregular intervals as the values are refreshed. + + + + + + Removed November 2016 + + michaeln@chromium.org + + Time spent initializing the global quota. Logged when the storage + partition's quota manager is initialized. + + + + + + Expired on 2018-08-30. Removed in M75. + + tzik@chromium.org + + Overage of the temporary global storage usage at beginning of an eviction + round. + + + + + + Removed 2015/05/05. + + holte@chromium.org + + Rappor.DailyEvent.IntervalType reported under the wrong name. + + + + + + Replaced by RecurrenceRanker.InitializationStatus. + + tby@chromium.org + charleszhao@chromium.org + + Reports different kinds of misconfigurations of a RecurrenceRanker. + + + + + + Removed December 2019. Distribution between file open types is approximately + 33% download, 26% launch, 26% open, 15% save as. + + jiameng@chromium.org + thanhdng@chromium.org + tby@chromium.org + + Records number of file opens for each file open type events. + + + + + + Replaced by RecurrenceRanker.SerializationStatus. + + tby@chromium.org + charleszhao@chromium.org + + Reports various saving/loading errors for a RecurrenceRanker or + RecurrencePredictor. + + + + + + The cases this reported can no longer occur. + + tby@chromium.org + charleszhao@chromium.org + + Reports when a RecurrenceRanker is used in a way not supported by its + underlying RecurrencePredictor. + + + + + + We successfully shipped a 4k restriction in M77, and no longer require the + data on `referer` header length. + + mkwst@chromium.org + + The size of each outgoing request's 'Referer' header field's value, in + bytes. + + + + + + Removed Dec 2016. This metric did not report the number of shared workers + correctly, since it used the RenderProcessHostImpl ref counts, which in the + shared worker case is more like a boolean flag (zero or one or maybe two) + than the number of shared workers. So its results can be thought of as + roughly the number of service workers only. + + kinuko@chromium.org + + Maximum number of workers (SharedWorker or ServiceWorker) that are + simultaneously hosted in a single renderer process. Recorded when the + renderer process host is being destructed. + + + + + + Removed May 2018. There are no longer accelerated fixed root backgrounds. + + Please list the metric's owners. Add more owner tags as needed. + + Keeps track of the number of main frame scrolls with an accelerated fixed + root background, the number of main frame scrolls with an unaccelerated + fixed root background, and the total number of main frame scrolls. + + + + + + Replaced by Scheduling.Renderer.DrawDuration. This metric did not + differentiate between processes. + + brianderson@chromium.org + The time it takes for the compositor to draw a frame. + + + + + Measurement no longer taken. + + brianderson@chromium.org + + The amount by which the compositor's draw duration was overestimated in a + particular frame (0 if the duration was perfectly predicted or + underestimated). + + + + + + Measurement no longer taken. + + brianderson@chromium.org + + The amount by which the compositor's draw duration was underestimated in a + particular frame (0 if the duration was perfectly predicted or + overestimated). + + + + + + Measurement no longer taken. + + brianderson@chromium.org + + The delay between the compositor submitting a command to the GPU and that + command executing on the GPU. This delay is measured once per frame. + + + + + + Measurement no longer taken. + + brianderson@chromium.org + + The amount by which GPU latency was overestimated in a particular frame (0 + if the latency was perfectly predicted or underestimated). + + + + + + Measurement no longer taken. + + brianderson@chromium.org + + The amount by which GPU latency was underestimated in a particular frame (0 + if the latency was perfectly predicted or overestimated). + + + + + + Removed as of 3/2015. + + benjhayden@chromium.org + + Duration of the FrameView::performLayout trace event, which occurs at most + once per frame. + + + + + + Removed as of 3/2015. + + benjhayden@chromium.org + + Amount of time spent doing line layout during FrameView::performLayout. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + A lower-bound on the percentage increase in memory that would result from + promoting all layers that have a webkit-transition on opacity or transform. + + + + + + Removed as of 10/2013. + + Please list the metric's owners. Add more owner tags as needed. + + This measures how long all unload event handlers required to run whenever an + unload event is processed. + + + + + + Removed 12/2019 as it is no longer hit or recorded. + + michaeldo@chromium.org + + [iOS] Counts the number of times a WKNavigationDelegate callback was called + after the CRWWebController was closed. This is unexpected and could be the + cause of many crashes. If this histogram is ever logged, it means that + Chrome needs to gracefully handle the case when WKNavigationDelegate + callbacks are called for a destroyed web controller. Only logged on iOS. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a document finished loading to when all it's resources + are also loaded. + + + + + + Removed 6/15/09. Replaced by Renderer2.RequestToFinish_L + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page was requested by a user to when it is fully + loaded. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page was requested by a user to when it is fully + loaded. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page was requested by a user to its first layout. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page was requested by a user to when it starts loading. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page started loading to when it is fully loaded. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page starts loading to when the main document is + finished loading. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + The time from when a page starts loading to its first layout. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Distribution of actual finished pages, vs abandoned pages, where we needed + to declare a finish time prematurely since the page was being closed + (exited). + + + + + + Removed 2014-05 because of impl-side painting. + + wiltzius@chromium.org + + Time spent by WebKit painting the page, in milliseconds, when the GPU + acceleration is active, for paints that affect non-root layers. + + + + + + Removed 2014-05 because of impl-side painting. + + wiltzius@chromium.org + + WebKit paint throughput, measured in megapixels per second, when GPU + acceleration is active, for paints that affect non-root layers. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + Time between frames when GPU acceleration is active. + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time spent by WebKit painting the page, in milliseconds, when the GPU + acceleration is active, for paints that affect the root layer. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + WebKit paint throughput, measured in megapixels per second, when GPU + acceleration is active, for paints that affect the root layer. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from when the animation callback was posted to when it ran. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "begin" to "commit." "Begin"== + "request" if user requested, and "start" otherwise. + "Request"== time when user requested document. "Start"== + time when renderer requested load of document, after any unload of last + document. "Commit"== time when renderer got first byte of + document. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + TBD + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + TBD + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "begin" to "first paint." "Begin"== + "request" if user requested, and "start" otherwise. + "Request"== time when user requested document. "Start"== + time when renderer requested load of document, after any unload of last + document. "First paint"== time when first paint operation was + performed. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "big" to "first paint after load." + "Begin"== "request" if user requested, and + "start" otherwise. "Request"== time when user requested + document. "Start"== time when renderer requested load of document, + after any unload of last document. "First paint after load"== time + after onload() when first paint operation is performed. + + + + + + Obsolete as of M80. Partial raster has shipped for a long period of time / + is not being tuned. + + ericrk@chromium.org + + Percentage of pixels which would have been rastered, but were skipped due to + the partial raster optimization. Logged for each raster task run in a + Browser process. The histogram is suffixed by the RasterBufferProvider which + is in use. + + + + + + Obsolete as of 11/2019. Replaced by + Renderer4.Browser.RasterTaskSchedulingDelayNoAtRasterDecodes since the + semantics changed: we used to count raster tasks that depended on at-raster + image decodes, but this is no longer the case. + + andrescj@chromium.org + chromeos-gfx@google.com + + The wall time elapsed between creating a raster task in the client and being + ready to issue raster work to the driver in the GPU process. This includes + time decoding and uploading images. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "commit" to "finish." "Commit"== + time when renderer got first byte of document. "Finish"==after + onload() and all resources are loaded. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "commit" to "finish doc." "Commit"== + time when renderer got first byte of document. "Finish doc" == + main document loaded, before onload(). "Finish"==after onload() + and all resources are loaded. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "commit" to "first paint." + "Commit"== time when renderer got first byte of document. + "First paint"== time when first paint operation was performed. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "commit" to "first paint after load." + "Commit"== time when renderer got first byte of document. + "First paint after load"== time after onload() when first paint + operation is performed. + + + + + + Removed in 12/2017. Renderer4.MainThreadGestureScrollReason and + Renderer4.MainThreadWheelScrollReason could track more detailed reasons of + main thread scrolling. + + vollick@chromium.org + + It's possible for compositor hit testing to determine conclusively that + compositor thread scrolling can or cannot be done. It's also possible that + the hit testing result is inconclusive. We would like to see the I-don't- + know result as little as possible. This histogram tracks the ratios. + + + + + + Removed in 06/2018, M69. Renderer4.CompositorThreadImplDrawDelay is no + longer needed due to issue 851784. + + wiltzius@chromium.org + + Time between frames, as measured on the compositor thread. This is collected + once per frame while it is being drawn to the screen in the compositor. + + + + + + Renamed to Renderer4.pixelCountCulled_Draw. + + wiltzius@chromium.org + + Number of pixels that culling prevented being drawn to the screen, + normalized to the viewport size. This is collected once per frame while it + is being drawn to the screen in the compositor. + + + + + + Renamed to Renderer4.pixelCountOpaque_Draw. + + wiltzius@chromium.org + + Number of pixels drawn to the screen and known opaque, normalized to the + viewport size. This is collected once per frame while it is being drawn to + the screen in the compositor. + + + + + + Renamed to Renderer4.pixelCountTranslucent_Draw. + + wiltzius@chromium.org + + Number of pixels drawn to the screen and not known opaque, normalized to the + viewport size. This is collected once per frame while it is being drawn to + the screen in the compositor. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "finish doc" to "finish." "Finish + doc"== main document loaded, before onload(). "Finish"==after + onload() and all resources are loaded. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "finish " to "first paint after load." + "Finish"==after onload() and all resources are loaded. "First + paint after load"== time after onload() when first paint operation is + performed. + + + + + + Removed 9/2018 and merged into Renderer4.MainThreadGestureScrollReason. + + tdresser@chromium.org + + For every touch scroll, we record whether the scroll occurred on the main + thread, on the compositor thread, or on the compositor thread but blocked on + the main thread. The last case will happen when there is a blocking event + listener. + + + + + + Removed as of 06/2017. No longer generated. + + vmpstr@chromium.org + + Indication whether the first ref of a GPU image upload was wasted (not used + in raster). Images are uploaded prior to raster; this indicates whether the + upload was used during the first ref. + + + + + + Removed as of 06/2017. No longer generated. + + vmpstr@chromium.org + + Indication whether the GPU image upload was used in raster. Images are + uploaded prior to raster; this indicates whether the upload was used during + raster. + + + + + + Removed 10/2019. + + ericrk@chromium.org + enne@chromium.org + + If gpu rasterization is enabled, whether this page contains both slow-paths + (making it suitable for MSAA) and non-AA paints (making it not-suitable for + MSAA). This indicates a case where we would like to use MSAA, but may have + to avoid it for correctness reasons. + + + + + + Removed 10/2019. Gpu rasterization is no longer dynamically triggerd by + content. + + ericrk@chromium.org + enne@chromium.org + + If gpu rasterization is enabled, whether the page contents contain no more + than 5 slow paths, and is suitable for non-MSAA gpu rasterization (checked + once after the page is painted for the first time). + + + + + + Removed 09/2019. Gpu rasterization is no longer dynamically triggerd by + content. + + ericrk@chromium.org + enne@chromium.org + + If gpu rasterization is enabled, whether it was triggered (checked once + after the page is painted for the first time). + + + + + + Removed 02/2019. Due to changes in the code, this is synonymous with + Renderer4.GpuRasterizationEnabled. + + alokp@chromium.org + + If gpu rasterization is enabled, whether it was actually used for the page + (checked once after the page is painted for the first time). + + + + + + Removed 02/2018. The ideal content scale closely matches the default device + scale factor. + + vmpstr@chromium.org + + The contents scale at which picture layer impl should be rasterized in order + to appear crisp. This is also known as ideal contents scale. This value is + recorded any time the ideal contents scale changes. Some examples of this + are pinch-zoom and JavaScript transform changes. + + + + + + Removed 06/2019. + + khushalsagar@chromium.org + + The mip level at which images are decoded for rasterization in the renderer. + This value is recorded each time an image is decoded in the compositor and + records the mip level used for the decode. Note that the mip levels recorded + lie between [1, 32], with the value of 1 indicating the use of the original + image. + + + + + + Removed July 2020, expired and no longer useful. + + ccameron@chromium.org + + For each cc::Layer that has more than zero discardable images, this metric + records the percent of image pixels that were from images that were + originally specified in an sRGB color space. + + + + + + Removed July 2020, expired and no longer useful. + + ccameron@chromium.org + + For each cc::Layer that has more than zero discardable images, this metric + records the percent of images that were originally specified in an sRGB + color space. + + + + + + Removed in 06/2018, M69. Renderer4.LanguageDetection is no longer needed due + to issue 851784. + + wiltzius@chromium.org + + Time to determine the page language. This is done after the page has been + loaded. + + + + + + Removed as of 02/2015. No longer generated. + + wiltzius@chromium.org + + The ratio of LCDText CC Layers / candidate LCDText layers. Recorded in + LayerTreeHost, after LayerTreeHostCommon::CalculateDrawProperties() has + computed the properties we need. Only recorded for the first 50 frames of + every page. + + + + + + Removed as of 02/2015. No longer generated. + + wiltzius@chromium.org + + The ratio of CC Layers which are candidates for LCDText AA / total picture + or content Layers. Recorded in LayerTreeHost, after + LayerTreeHostCommon::CalculateDrawProperties() has computed the properties + we need. Only recorded for the first 50 frames of every page. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Probability distribution for enumerated varieties of page loads. + + + + + + Removes as of 6/2020. We now get enough cache hit information from + Renderer4.SoftwareImageDecodeState* and don't need to divide it into tile + bins. + + cblume@chromium.org + vmpstr@chromium.org + + For each attempted lock of a cached image, records whether it was + successful. + + + + + + Obsolete after 07/2019. Investigation concluded. + + ericrk@chromium.org + + The percentage of input events which are janks (not processed in the + expected frame) during each momentum scroll gesture due to unstable ordering + of begin frame with regards to input delivery. Computed by tracking the + number of times we coalesce an extra input event close to the point at which + we process it. Added to track the impact of https://crbug.com/952930. Logged + once after a scroll with momentum events completes. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Number of pixels known to be opaque, recorded as 10 times the percentage of + the viewport that these pixels cover. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Number of pixels painted by WebKit into main memory, recorded as 10 times + the percentage of the viewport that these pixels cover. This is collected + once per commit from WebKit to the compositor. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Number of pixels not known to be opaque opaque, recorded as 10 times the + percentage of the viewport that these pixels cover. + + + + + + Not used after M77. No longer tuning this code. + + ericrk@chromium.org + + The type of clear which was needed for each cc::RasterSource rasterized. + + + + + + Removed 02/2017 in Issue 675840. + + vmpstr@chromium.org + + For each tile that was ready to draw at some point, logs whether the tile + was actually used in a draw. This is logged at tile destruction time. + + + + + + Obsolete as of M80. Partial raster has shipped for a long period of time / + is not being tuned. + + ericrk@chromium.org + + Percentage of pixels which would have been rastered, but were skipped due to + the partial raster optimization. Logged for each raster task run in a + Renderer process. The histogram is suffixed by the RasterBufferProvider + which is in use. + + + + + + Obsolete as of 11/2019. Replaced by + Renderer4.Renderer.RasterTaskSchedulingDelayNoAtRasterDecodes since the + semantics changed: we used to count raster tasks that depended on at-raster + image decodes, but this is no longer the case. + + andrescj@chromium.org + chromeos-gfx@google.com + + The wall time elapsed between creating a raster task in the client and being + ready to issue raster work to the driver in the GPU process. This includes + time decoding and uploading images. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "request" to "finish." "Request"== + time when user requested document. "Finish"==after onload() and + all resources are loaded. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "request" to "start." "Request"== + time when user requested document. "Start"== time when renderer + requested load of document, after any unload of last document. + + + + + + Removed in M85 as no longer being needed. + + bbudge@chromium.org + + The size of the contiguous memory block reserved in the renderer so that + large allocations are more likely to succeed. The reservation is currently + made in BlinkInitializer. + + + + + + 07/2020: Replaced by the Compositing.ResourcePoolMemoryUsage. + + ericrk@chromium.org + + Size of the in-use portion of the ResourcePool. Recorded each time resources + are reclaimed after tile work completes. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + Time to capture a renderer snapshot. + + + + + Removed in 06/2018, M69. Renderer4.SoftwareCompositorThreadImplDrawDelay is + no longer needed due to issue 851784. + + wiltzius@chromium.org + + Time between frames when the software renderer is being used, as measured on + the compositor thread. This is collected once per frame while it is being + drawn to the screen in the compositor. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + Time between frames when the page is not GPU accelerated. + + + + + Removed in issue 755432 as no longer being needed. + + wiltzius@chromium.org + + Time spent by WebKit painting the page, in milliseconds, when the page is + not GPU accelerated. + + + + + + Removed in issue 755432 as no longer being needed. + + wiltzius@chromium.org + + WebKit paint throughput, measured in megapixels per second, when the page is + not GPU accelerated. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "start" to "commit." "Start"== time + when renderer requested load of document, after any unload of last document. + "Commit"== time when renderer got first byte of document. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Time from "start" to "finish." "Start"== time + when renderer requested load of document, after any unload of last document. + "Finish"==after onload() and all resources are loaded. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + The number of microseconds it took to upload a tile's full texture as + measured on the GPU process. + + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + Time to capture a renderer thumbnail. + + + + + Removed at an unknown time. No longer used in code. + + wiltzius@chromium.org + + Number of tiles that culling prevented being uploaded to texture memory. + This is an approximation and is recorded as a 100 times the percentage of + the number of tiles, of default size, needed to cover the viewport. This is + collected once per commit from WebKit to the compositor. + + + + + + Removed as of 04/2012, replaced with Renderer4.tileCountCulled_Upload. + + wiltzius@chromium.org + + Number of pixels that culling prevented being uploaded to texture memory, + normalized to the viewport size. This is collected once per commit from + WebKit to the compositor. + + + + + + Renamed to Renderer4.pixelCountOpaque_Upload. + + wiltzius@chromium.org + + Number of pixels uploaded to texture memory and known to be opaque, + normalized to the viewport size. This is collected once per commit from + WebKit to the compositor. + + + + + + Renamed to Renderer4.pixelCountTranslucent_Upload. + + wiltzius@chromium.org + + Number of pixels uploaded to texture memory and not known opaque, normalized + to the viewport size. This is collected once per commit from WebKit to the + compositor. + + + + + + Removed 9/2018 and merged into Renderer4.MainThreadWheelScrollReason. + + tdresser@chromium.org + + For every wheel tick, we record whether the scroll occurred on the main + thread, on the compositor thread, or on the compositor thread but blocked on + the main thread. The last case will happen when there is a blocking event + listener. + + + + + + Removed 6/2018 and replaced with PageScheduler.PageLifecycleStateTransition. + + fmeawad@chromium.org + panicker@chromium.org + + Tracks the transitions of the renderer scheduler when it is backgrounded. + Once it is backgrounded, it can be stopped after a timeout, stopped due to + critical resources, resumed or foregrounded. + + + + + + Replaced with RendererScheduler.BackgroundRendererMainThreadLoad2 as of May + 2017. + + altimin@chromium.org + + Renderer main thread load when renderer is backgrounded, i.e. percentage of + time spent on running tasks. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per minute per + renderer amortized. + + + + + + Replaced with + RendererScheduler.RendererMainThreadLoad3.Background.AfterFirstMinute as of + July 2017. + + altimin@chromium.org + + Renderer main thread load when renderer is backgrounded, i.e. percentage of + time spent on running tasks. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per minute per + renderer amortized. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus2 as of Feb + 2018. Buckets were changed. + + npm@chromium.org + tdresser@chromium.org + + Expected queueing time split by tasks according to their frame status, in + microseconds. The sum of the split values will be equal to the total, + reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded for + each 1000 ms window. + + + + + + Removed March 2019. + + npm@chromium.org + tdresser@chromium.org + + Expected queueing time split by tasks according to their frame status, in + microseconds. The sum of the split values will be equal to the total, + reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded for + each 1000 ms window. + + + + + + Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus as of + December 2017. + + npm@chromium.org + + Expected queueing time split by tasks according to their frame type. The sum + of the split values should be equal to the total, reported on + RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms + window. + + + + + + Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue2 as of Feb + 2018. Buckets were changed. + + npm@chromium.org + tdresser@chromium.org + + Expected queueing time split by tasks according to the type of their task + queue, in microseconds. The sum of the split values should be equal to the + total, reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded + for each 1000 ms window. + + + + + + Removed February 2019. + + npm@chromium.org + tdresser@chromium.org + + Expected queueing time split by tasks according to the type of their task + queue, in microseconds. The sum of the split values should be equal to the + total, reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded + for each 1000 ms window. + + + + + + Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue as of + December 2017. + + npm@chromium.org + + Expected queueing time split by tasks according to the type of their task + queue. The sum of the split values should be equal to the total, reported on + RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms + window. + + + + + + Removed 04/2018. + + tdresser@chromium.org + + Expected queueing time for events which were queued on the main thread + longer or shorter than a threshold, given by the QueueingTimeThreshold + suffix. + + Team: input-dev@chromium.org. + + + + + + Removed June 2020. + + tdresser@chromium.org + + The estimated queueing duration which would be observed for additional high + priority tasks posted to the RendererScheduler. Recorded for each 1000 ms + window. + + + + + + Replaced with RendererScheduler.ExpectedTaskQueueingDuration3 as of Feb + 2018. Buckets were changed. + + tdresser@chromium.org + npm@chromium.org + + The estimated queueing duration which would be observed for additional high + priority tasks posted to the RendererScheduler, in microseconds. Recorded + for each 1000 ms window. + + + + + + Removed June 2020. + + tdresser@chromium.org + npm@chromium.org + speed-metrics-dev@chromium.org + + The estimated queueing duration which would be observed for additional high + priority tasks posted to the RendererScheduler, in microseconds. Recorded + for each 1000 ms window. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed March 2019. + + tdresser@chromium.org + npm@chromium.org + + The estimated queueing duration which would be observed for additional high + priority tasks posted to the RendererScheduler, in microseconds, for + renderer processes that do not host any main frame. Recorded for each 1000 + ms window. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced with RendererScheduler.ForegroundRendererMainThreadLoad2 as of May + 2017. + + altimin@chromium.org + + Renderer main thread load when renderer is foregrounded, i.e. percentage of + time spent on running tasks. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per minute per + renderer amortized. + + + + + + Replaced with + RendererScheduler.RendererMainThreadLoad3.Foreground.AfterFirstMinute as of + July 2017. + + altimin@chromium.org + + Renderer main thread load when renderer is foregrounded, i.e. percentage of + time spent on running tasks. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per minute per + renderer amortized. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Removed June 2020. + + maxlg@chromium.org + + The single maximum estimated queueing duration (or max queueing time) + between when user starts navigation and user navigates away. Navigate-away + is defined as a fast shutdown or a natural ending of renderer, or the new + navigation start which replacing the old navigation. + + The queueing time is estimated on a sliding window basis. The width of the + sliding window is 1 second, the sliding step being 50ms. The max queueing + time keeps track of the largest queueing time on each slide. + + This metric resets itself at navigation start, updates the max of queueing + time with the sliding window moving, reports the max queueing times to the + histogram at the next navigation start of the same or different renderer + process. + + + + + + Replaced with RendererScheduler.NumberOfTasksPerQueueType2 as of May 2017. + + altimin@chromium.org + alexclarke@chromium.org + + The number of completed renderer tasks split per task queue type. Used to + monitor usage of each type of task queue. Reported each time when task is + completed. + + + + + + Replaced with RendererScheduler.TaskCountPerQueueType as of July 2017. + + altimin@chromium.org + alexclarke@chromium.org + + The number of completed renderer tasks split per task queue type. Used to + monitor usage of each type of task queue. Reported each time when task is + completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Removed as of 08/2017. Replaced with + RendererScheduler.ExpectedQueueingTimeWhenQueueingTime. + + tdresser@chromium.org + + Time between sending an event to the renderer main thread and when the + renderer begins to process that event, for events which were dispatched when + the expected queueing time was past some threshold. + + Team: input-dev@chromium.org. + + + + + + This metric still used 1-minute reporting chunks. Replaced with + RendererMainThreadLoad4 as of July 2017. + + altimin@chromium.org + + Renderer main thread load (percentage of time spent in tasks), reported in + one minute chunks. + + See http://bit.ly/chromium-renderer-main-thread-load-metric for details. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per second per + renderer amortized. + + + + + + Replaced with RendererMainThreadLoad5 as of August 2017. + + altimin@chromium.org + + Renderer main thread load (percentage of time spent in tasks), reported in + one second chunks. + + See http://bit.ly/chromium-renderer-main-thread-load-metric for details. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per second per + renderer amortized. + + + + + + Replaced with RendererScheduler.TaskCPUDurationPerTaskType2.DedicatedWorker + as of June 2018 due to overflows (crbug.com/809668). Some metrics are + incremented with large amounts that they sometimes overflow and roll + negative before they get uploaded. + + altimin@chromium.org + + Total duration of dedicated worker tasks (thread time) split by per thread + type. Reported each time when task is completed and current accumulated + duration is longer than 1ms. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskCPUDurationPerThreadType2 as of June + 2018 due to overflows (crbug.com/809668). Some metrics are incremented with + large amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + + Total cpu time of renderer tasks split by per thread type. Wall time is + tracked by RendererScheduler.TaskDurationPerThreadType histogram. This + histogram is used to compare CPU usage of tasks from different threads. + + Only 1% of randomly sampled tasks have cpu time measured and report duration + for this histogram. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskDurationPerFrameOriginType2 as of June + 2018 due to overflows (crbug.com/809668). Some metrics are incremented with + large amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + + Total cpu time of renderer tasks split by per frame origin type (main frame + vs same-origin frame vs cross-origin frame). + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskDurationPerFrameType2 due to the + introduction of new types of frames as of 11/2017. + + altimin@chromium.org + + Total duration of renderer per-frame tasks split per frame type. Used to + monitor workload coming from different frames. Reported each time when task + is completed and current accumulated duration is longer than 1ms. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + + Replaced with RendererScheduler.TaskDurationPerFrameType3 as of June 2018 + due to overflows (crbug.com/809668). Some metrics are incremented with large + amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + + Total duration of renderer per-frame tasks split per frame type. Used to + monitor workload coming from different frames. Reported each time when task + is completed and current accumulated duration is longer than 1ms. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + + Replaced with RendererScheduler.TaskDurationPerQueueType2 as of May 2017. + + altimin@chromium.org + alexclarke@chromium.org + + Total duration of renderer tasks split per task queue type. Used to monitor + usage of each type of task queues. Reported each time when task is completed + and current accumulated duration is longer than 1ms. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + + Replaced with RendererScheduler.TaskDurationPerQueueType3 as of June 2018 + due to overflows (crbug.com/809668). Some metrics are incremented with large + amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + alexclarke@chromium.org + + Total duration of renderer tasks split per task queue type. Used to monitor + usage of each type of task queues. Reported each time when task is completed + and current accumulated duration is longer than 1ms. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskDurationPerTaskType2 as of June 2018 due + to overflows (crbug.com/809668). Some metrics are incremented with large + amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + hajimehoshi@chromium.org + + Total duration of renderer per-frame tasks split per task type. Used to + monitor usage of each task type. Reported each time when task is completed + and current accumulated duration is longer than 1ms. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + + Replaced with RendererScheduler.TaskDurationPerTaskType2.DedicatedWorker as + of June 2018 due to due to overflows (crbug.com/809668). Some metrics are + incremented with large amounts that they sometimes overflow and roll + negative before they get uploaded. + + altimin@chromium.org + + Total duration of dedicated worker tasks (wall time) split by per thread + type. Reported each time when task is completed and current accumulated + duration is longer than 1ms. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskDurationPerThreadType2 as of June 2018 + due to overflows (crbug.com/809668). Some metrics are incremented with large + amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + lpy@chromium.org + + Total duration of renderer tasks split by per thread type. Used to compare + CPU usage of tasks from different threads. Reported each time when task is + completed and current accumulated duration is longer than 1ms. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + + Replaced with RendererScheduler.TaskDurationPerUseCase2 as of June 2018 due + to overflows (crbug.com/809668). Some metrics are incremented with large + amounts that they sometimes overflow and roll negative before they get + uploaded. + + altimin@chromium.org + farahcharab@chromium.org + + Total duration (measured in ms) of renderer main thread tasks split by + scheduler use case. Use case is a scheduler's educated guess of the current + state of the world. See renderer/use_case.h and + RendererSchedulerImpl::UpdatePolicy for more details. + + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + + The delta between when a delayed task was scheduled to run and when the + RendererScheduler actually ran it. Note: to reduce overhead only 10% of + tasks are sampled. + + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + + The queueing duration for non-delayed tasks posted to the RendererScheduler. + This metric is only recorded if TrackingInfo::time_posted is set (i.e. not + on android). Note: to reduce overhead only 10% of tasks are sampled. + + + + + + Replaced with RendererScheduler.TaskTime2 as of May 2017. + + sunyunjia@chromium.org + tdresser@chromium.org + + The duration of every task queued in the _renderer_ scheduler to see the + distribution of the task duration. + + + + + + Removed 07/2020. Summary of collected data: https://crbug.com/1019856#c6. + + fdoray@chromium.org + etiennep@chromium.org + + Time spent running tasks from other agents between when an agent task + becomes ready and when it starts running. A non-delayed task is ready when + it is posted. A delayed task is ready when its delay expires. Recorded for 1 + out of 1000 tasks. + + + + + + Removed 11/2019. Replace with + RendererScheduler.TimeRunningOtherAgentsWhileTaskReady. + + fdoray@chromium.org + etiennep@chromium.org + + Time spent running tasks from other frames between when a frame task becomes + ready and when it starts running. A non-delayed task is ready when it is + posted. A delayed task is ready when its delay expires. Recorded for 1 out + of 1000 tasks. + + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + Duration of gestures (scrolls and pinches). + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + Whether a user gesture was predicted correctly. + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + + Time between when the UserModel was last reset (which happens on navigation) + and a gesture starting. + + + + + + Removed from code 2017-08. + + alexclarke@chromium.org + Time between subsequent gestures (scrolls and pinches). + + + + + Removed Oct 2018. + + alexmos@chromium.org + boliu@chromium.org + + Record whether a local root frame ever received post messages from another + cross origin frame that's not a descendent. This is useful to evaluate if a + frame is safe to be reloaded automatically. Recorded when a frame crashed + while invisible, and then becomes visible to the user; this is the point a + crashed frame would be reloaded. Note this is not logged for the main frame, + which only has descendant frames. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidChangeScrollOffset. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidClearWindowObject. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidCommitProvisionalLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidCreateScriptContext. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidFailProvisionalLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidFinishDocumentLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidFinishLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidMeaningfulLayout. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.DidStartProvisionalLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.FocusedNodeChanged. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.OnMessageReceived. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.ScriptedPrint. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.WillCommitProvisionalLoad. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.WillSendSubmitEvent. + + + + + + Removed 2/2018 + + joelhockey@chromium.org + + Cumulative time spent by all RenderFrameObservers in + RenderFrameImpl.WillSubmitForm. + + + + + + Removed as of June 2020. + + jochen@chromium.org + + State of the profile that is activated via the "Open Link as User" + menu. Logged when one of the "Open Link as User" context menu + options is selected. + + + + + + Removed as of June 2020. + + jochen@chromium.org + + Whether or not other profiles are active when the "Open Link as + User" context menu is shown. Logged when the context menu is created. + + + + + + Removed as of June 2020. + + jochen@chromium.org + + Count of the profiles shown for the "Open Link as User" context + menu. Logged when the context menu is created. + + + + + + Moved to Net.Reporting.HeaderEndpointGroupOutcome. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a single endpoint group in a + Report-To header once the header itself has been parsed. + + + + + + Moved to Net.Reporting.HeaderEndpointOutcome. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a single endpoint in a Report-To + header once the header itself has been parsed. + + + + + + Moved to Net.Reporting.HeaderOutcome. + + juliatuttle@chromium.org + + The outcome of Reporting trying to process a Report-To header. Once it is + parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints + within it. + + + + + + Moved to Net.Reporting.ReportDeliveredAttempts. + + juliatuttle@chromium.org + + When Reporting successfully delivers a report, the number of unsuccessful + delivery attempts that preceded the successful one. + + + + + + Moved to Net.Reporting.ReportDeliveredLatency. + + juliatuttle@chromium.org + + The delivery latency of reports successfully delivered by Reporting. Starts + when the report is queued and finishes when the delivery attempt returns + successfully. + + + + + + Moved to Net.Reporting.ReportOutcome. + + juliatuttle@chromium.org + + The outcome of Reporting trying to deliver a report, recorded when the + report is finally erased from memory. + + + + + + Removed as of March 9, 2020. + + chlily@chromium.org + sburnett@chromium.org + + Size on disk of the Reporting and NEL database. This is recorded when the + database is initialized, which typically happens upon the first network + request after startup. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + The state of the requestAutocomplete() dialog when it was dismissed. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + The initial state of a user that's interacting with a freshly shown + requestAutocomplete() dialog. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + User interactions with the Autofill popup shown while filling an + requestAutocomplete() dialog. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the frequency of security warnings and errors in the + RequestAutocomplete dialog. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the duration for which an requestAutocomplete() dialog was shown. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the duration for which an requestAutocomplete() dialog was shown, + in cases where the user ended up canceling out of the dialog. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the duration for which an requestAutocomplete() dialog was shown, + in cases where the user ended up accepting the dialog. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures how users are interacting with the requestAutocomplete() dialog UI. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the duration of time it takes for the requestAutocomplete() UI to + be actionable by the user after it is shown. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the frequency of errors in communicating with the Google Online + Wallet server. + + + + + + Removed as of 5/5/2016. + + estade@chromium.org + + Measures the frequency of required user actions returned by the Google + Online Wallet server. + + + + + + Removed as of 18/1/2019. + + lpy@chromium.org + + The number of IPCs from frame to GRC. Recorded every 1 minute. + + + + + + Removed as of 18/1/2019. + + lpy@chromium.org + + The number of IPCs from page to GRC. Recorded every 1 minute. + + + + + + Removed as of 18/1/2019. + + lpy@chromium.org + + The number of IPCs from process to GRC. Recorded every 1 minute. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database after deleting + it after a failed repair attempt. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database after a repair + attempt. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + The result of trying to repair the Local Site Characteristics database after + a failed open. + + + + + + Removed July 2020. + + + + sebmarchand@chromium.org + + The cumulative observation time before a feature tracked in the Local Site + Characteristics database gets used. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + The size of the Local Site Characteristics database on disk. Recorded at + startup when the database gets opened. + + + + + + Removed July 2020. + + sebmarchand@chromium.org + + Boolean indicating if the read operation from the Local Site Characteristics + database has completed when we query for the characteristics of a site. + + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + The amount of wall-clock time a measurement cycle occupied. + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + + The number of unexpected processes encountered during memory measurement. + This is expected to be non-zero as new processes can be created after a + measurement cycle is initiated, plus non-renderer processes are counted here + at the moment. + + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + + A boolean that measures how often a performance measurement notification + arrives at a WebContents that has been re-navigated. + + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + + An enumeration indicating the outcome of each memory measurement attempt. + + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + + The number of processes that didn't get a memory measurement. This can + happen if processes die as or after measurement is initiated. + + + + + + Removed April 2019. No longer recorded. + + siggi@chromium.org + + The number of processes that were measured for CPU at least. + + + + + + Obsoleted July 2020. + + tbansal@chromium.org + + The count of resource loading blocking patterns received by the renderer. + Recorded every time resource loading hints mojom message is received. + Recorded at most once per triggered navigation. + + + + + + Removed 03/2019 as it was never a useful metric. + + tbansal@chromium.org + + The count of page hints received by the browser from the component updater. + Recorded every time a page hint is received by the browser from the + optimization guide service. + + + + + + Removed 03/2019 as it was never a useful metric. + + tbansal@chromium.org + + The total count of page hints received by the browser from the component + updater. Only the page hints that have at least one resource loading hint + are counted. One sample is recorded every time optimization guide service + processes the optimization hints provided by the component updater. The + count of hints loaded to memory may be lower than this. + + + + + + Removed 03/2019 as it was never a useful metric. + + tbansal@chromium.org + + The total count of resource loading hints across all page hints received by + the browser from the component updater. One sample is recorded every time + optimization guide service processes the optimization hints provided by the + component updater. The count of hints loaded to memory may be lower than + this. + + + + + + Obsoleted July 2020. + + tbansal@chromium.org + + Records if the resource patterns were available at the time of page commit + if the committed previews type was RESOURCE_LOADING_HINTS. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + Like HttpCache.Pattern but only for requests made during speculative + prefetch. Logged per successful request. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + This metric measures the host coverage of the predictor database: On each + navigation, it records what percentage of the top X history entries are + found in the predictor DB. Caveats: (1) This metric is only recorded once + the user has accumulated enough browsing history, implemented as a minimum + threshold of total page visits by the user. (2) This metric is sampled, so + it's actually only recorded for 1 out of every K navigations. + + + + + + Removed October 2016. No longer recorded. + + zhenw@chromium.org + + A boolean that used to indicate a corner case when certain resources are not + written to the Predictor database becuase their URLs are too long. We + monitor this number to ensure that we do not discard too many resources. + + + + + + Removed 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent. + + zhenw@chromium.org + + A boolean that indicates if the speculative resource prefetch predictor has + predictions for a Navigation. This is updated on each navigations and helps + us determine the coverage of the predictor. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + A boolean that used to indicate a corner case when we may not have prefetch + results even though prefetching is enabled and predictions are present, + because another navigation in the same tab canceled the prefetching of the + previous load. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + The visit count of a URL in the history database, measured when the onload + fires for the URL. Helpful in figuring out what visit count should be used + to start learning about a URL. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Assuming a fixed number (25 or 50) of URLs could be prefetched max, how many + would be available for prefetch (after we apply our heuristics for picking + subresources to prefetch for a navigation). + + This stat is recorded when the predictor uses the host of the main frame url + as the key for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the cache restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the host of the main frame url + as the key for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the network restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the host of the main frame url + as the key for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Similar to ResourcePrefetchPredictor.Host.PredictedPrefetchFromNetwork but + as a percent of the total number of resources the page actually fetched from + the network. This depcits the major gains that we can get. + + This stat is recorded when the predictor uses the host of the main frame url + as the key for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page not used + by the page, restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the host of the main frame url + as the key for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + prefetches cancelled as a percentage of the total number of resources that + the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + prefetches failed as a percentage of the total number of resources that the + predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from cache while prefetching but were not + requested by the page, as a percentage of the total number of resources that + the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from cache while prefetching and also came + from the cache when the page requested it, as a percentage of the total + number of resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from cache while prefetching but came from + the network when the page requested it, as a percentage of the total number + of resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from network while prefetching but were not + requested by the page, as a percentage of the total number of resources that + the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from network while prefetching but came from + the cache when the page requested it, as a percentage of the total number of + resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of + successful prefetches that came from cache while prefetching and also came + from the network when the page requested it, as a percentage of the total + number of resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of resources + that were prefetchable but were not prefetched as a percentage of + prefetchable resources. + + + + + + Removed January 2017. This is effectively the same as + ResourcePrefetchPredictor.HostTableRowCount2 after refactoring of the + predictor database. + + zhenw@chromium.org + + The count of number of unique hosts in the HostTable, i.e. the number of + hosts that the database has prediction data for. This data is useful for + determining the recall/precision as a function of the number of hosts that + need to be tracked by the database. Measured at startup. + + + + + + Removed January 2017. Replaced by + ResourcePrefetchPredictor.HostTableRowCount2. + + zhenw@chromium.org + + The count of number of rows in the HostTable. This is effecively the number + of (host, resource URL) pairs in the database. This is measured at startup + and used to get an estimate of the data size. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + The number of rows in the HostTable. This is effectively the number of hosts + in the database. This is measured at startup and used to get an estimate of + the data size. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + When the prefetch predictor has resources in the local database for a given + navigation, the count of predicted urls. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + When the prefetch predictor has resources in the local database for a given + navigation, the precision of the predictions, in percentage. This is + computed as 100 \times \frac{correct predictions}{predictions}. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + When the prefetch predictor has resources in the local database for a given + navigation, the recall of the predictions, in percentage. This is computed + as 100 \times \frac{correct predictions}{all prefetchable subresources}. + + + + + + Obsoleted in M-69. + + alexilin@chromium.org + + Records stats about main frame navigations. Records the total number of + requests/responses/redirects for main frame urls along with the numbers for + how often the predictor can process such events. This is useful to figure + out what percentange of requests are handled by the predictor and also for + sanity checking the other stats. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Records stats about various interesting events such as - request start, + response start, redirect, onload, etc during the load of a main frame. + Essential for understanding the complete life of a navigation request start + to the onload fire and the events that occur in between. + + + + + + Removed 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent. + + zhenw@chromium.org + + The status of various navigations from the view point of the 'onload' event. + Since we measure the prediction accuracy and learn navigation subresources + on the onload event, it is useful to know how many of the navigations are + abandoned before 'onload' fires. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Records the number of pages on each type of network after a page is loaded. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Page load time. It starts from when the main frame URL request is sent out + to when the main frame document load is completed. + + This is recorded for both prefetched and non-prefetched pages. + + + + + + Removed 01/2013. Replaced with specific ones for Url and Host. + + zhenw@chromium.org + + Assuming a fixed number of URLs could be prefetched max, how many would be + available for prefetch (after we apply our heuristics for picking + subresources to prefetch for a navigation). + + + + + + Removed 01/2013. Replaced with specific ones for Url and Host. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the cache restricted to some max predictions. + + + + + + Removed 01/2013. Replaced with specific ones for Url and Host. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the network restricted to some max predictions. + + + + + + Removed 01/2013. Replaced with specific ones for Url and Host. + + zhenw@chromium.org + + Similar to ResourcePrefetchPredictor.Predicted.PrefetchFromNetwork but as a + percent of the total number of resources the page actually fetched from the + network. This depcits the major gains that we can get. + + + + + + Removed 01/2013. Replaced with specific ones for Url and Host. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page not used + by the page, restricted to some max predictions. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + The count of successfully prefetched subresources for a single page. + Recorded after all subresource prefetches have reached a terminal + success/failure state. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + The total amount of data consumed by predictor for a single page. Only + successfully finished requests taken into account. Recorded after all + subresource prefetches have reached a terminal success/failure state. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Number of resources that were prefetched and requested by a page load, for + cached requests. Logged after the prefetcher completes. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Number of resources that were prefetched and requested by a page load, for + non cached requests. Logged after the prefetcher completes. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Amount of useful data fetched from the network for a prefetch request. This + is the total size of the resources accounted for in + ResourcePrefetchPredictor.PrefetchHitsCount.NotCached. Logged after the + prefetcher completes. + + + + + + Removed at M72. No longer recorded. + + alexilin@chromium.org + + Amount of time available for prefetching. Specifically, this is a time + interval between corresponding StartPrefetching() and StopPrefetching() + calls. This is recorded for both prefetched and non-prefetched pages. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Number of resources that were prefetched but not requested by a page load, + for cached requests. Logged after the prefetcher completes. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Number of resources that were prefetched but not requested by a page load, + for non cached requests, that is waste. Logged after the prefetcher + completes. + + + + + + Removed at M66. No longer recorded. + + lizeb@chromium.org + + Amount of wasted data fetched from the network for a prefetch request. This + is the total size of the resources accounted for in + ResourcePrefetchPredictor.PrefetchMissesCount.NotCached. Logged after the + prefetcher completes. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + When the prefetch predictor has resources in the local database for a given + navigation, records stats about whether redirect was predicted correctly or + incorrectly. + + + + + + Removed at M72. No longer recorded. + + alexilin@chromium.org + + Records stats about various interesting events such as - when partial or all + of history is cleared. It will include events which do not necessarily + happen during a navigation (which are reported in + ResourcePrefetchPredictor.NavigationEvent). + + + + + + Obsoleted in M-69. + + alexilin@chromium.org + + Records stats about requests, redirects, and responses observed by the + LoadingPredictorObserver. These stats are useful as a baseline for other + stats. + + + + + + Removed 08/2016 with the removal of the recording code. + + zhenw@chromium.org + + The distribution of the reasons for which subresources are ignored during + prefetching. This helps us prioritze reasons we should further investigate + to increase coverage. This is reported as a bit map and every status will be + a bitwise or of the underlying reasons. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Assuming a fixed number of URLs could be prefetched max (25 or 50), how many + would be available for prefetch (after we apply our heuristics for picking + subresources to prefetch for a navigation). + + This stat is recorded when the predictor uses the main frame url as the key + for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the cache restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the main frame url as the key + for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page and served + from the network restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the main frame url as the key + for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + Similar to ResourcePrefetchPredictor.Url.PredictedPrefetchFromNetwork but as + a percent of the total number of resources the page actually fetched from + the network. This depcits the major gains that we can get. + + This stat is recorded when the predictor uses the main frame url as the key + for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + When we have predictions for a navigation, we measure the accuracy of the + predictions against the actual resources downloaded. This histogram gives + the distribution of the predictions that were fetched by the page not used + by the page, restricted to some max predictions (25 or 50). + + This stat is recorded when the predictor uses the main frame url as the key + for prediction. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of prefetches + cancelled as a percentage of the total number of resources that the + predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of prefetches + failed as a percentage of the total number of resources that the predictor + tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from cache while prefetching but were not requested by + the page, as a percentage of the total number of resources that the + predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from cache while prefetching and also came from the + cache when the page requested it, as a percentage of the total number of + resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from cache while prefetching but came from the network + when the page requested it, as a percentage of the total number of resources + that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from network while prefetching but were not requested + by the page, as a percentage of the total number of resources that the + predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from network while prefetching but came from the cache + when the page requested it, as a percentage of the total number of resources + that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on the main frame URL, the percentage of successful + prefetches that came from cache while prefetching and also came from the + network when the page requested it, as a percentage of the total number of + resources that the predictor tried to prefetch. + + + + + + Removed September 2016. No longer recorded. + + zhenw@chromium.org + + For prefetching based on host of main frame URL, the percentage of resources + that were prefetchable but were not prefetched as a percentage of + prefetchable resources. + + + + + + Removed September 2016. This is effectively the same as + ResourcePrefetchPredictor.UrlTableRowCount2 after refactoring of the + predictor database. + + zhenw@chromium.org + + The count of number of unique main frame urls in the UrlTable, i.e. the + number of webpages that the database has prediction data for. This data is + useful for determining the recall/precision as a function of the number of + webpages that need to be tracked by the database. Measured at startup. + + + + + + Removed October 2012. No longer recorded. + + zhenw@chromium.org + + The count of number of unique main frame urls that are deleted from the URL + table at startup because they are no longer in history. Essential to figure + out how much data we are loosing out. + + + + + + Removed October 2012. No longer recorded. + + zhenw@chromium.org + + Same as ResourcePrefetchPredictor.UrlTableMainFrameUrlsDeletedNotInHistory + but recording percentage of URLs in the table rather than absolute numbers. + + + + + + Removed January 2017. Replaced by + ResourcePrefetchPredictor.UrlTableRowCount2. + + zhenw@chromium.org + + The count of number of rows in the UrlTable. This is effecively the number + of (main frame URL, resource URL) pairs in the database. This is measured at + startup and used to get an estimate of the data size. + + + + + + Removed at M66. No longer recorded. + + alexilin@chromium.org + + The number of rows in the UrlTable. This is effectively the number of main + frame URLs in the database. This is measured at startup and used to get an + estimate of the data size. + + + + + + Removed 04/2020. + + afakhry@chromium.org + + The CPU usage range reported for the browser process when the Chrome OS + device memory pressure (which is the percentage of total memory used by the + system) is critical. This is emitted only when memory pressure changes from + a low pressure to a higher pressure. + + + + + + Removed 04/2020. + + afakhry@chromium.org + + The system memory usage range reported for the browser process when the + Chrome OS device memory pressure (which is the percentage of total memory + used by the system) is critical. This is emitted only when memory pressure + changes from a low pressure to a higher pressure. + + + + + + Removed 04/2020. + + afakhry@chromium.org + + The CPU usage range reported for the GPU process when the Chrome OS device + memory pressure (which is the percentage of total memory used by the system) + is critical. This is emitted only when memory pressure changes from a low + pressure to a higher pressure. + + + + + + Removed 04/2020. + + afakhry@chromium.org + + The system's RAM memory usage range reported for the GPU process when the + Chrome OS device memory pressure (which is the percentage of total memory + used by the system) is critical. This is emitted only when memory pressure + changes from a low pressure to a higher pressure. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the ResourceScheduler is informed of a + Client's creation or starts loading and when that Client finishes loading in + a Client which has been user-observable the entire time. + + Note: Will not include time for the main resource if PlzNavigate is in use. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the ResourceScheduler is informed of a + Client's creation or starts loading and when that Client finishes loading in + a Client which has been background the entire time. + + Note: Will not include time for the main resource if PlzNavigate is in use. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the ResourceScheduler is informed of a + Client's creation or starts loading and when that Client finishes loading in + a Client which has switched between Active and Background. + + Note: Will not include time for the main resource if PlzNavigate is in use. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between the last time that a Client becomes + user-observable and when that Client finishes loading in a Client that was + user-observable when the load completed. + + Note: Will not include time for the main resource if PlzNavigate is in use. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time the ResourceScheduler is throttling a request after + WillStartRequest is called for a request in a client that was + user-observable at creation and start time. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time the ResourceScheduler is throttling a request after + WillStartRequest is called for a request in a client that was background at + creation and start time. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time the ResourceScheduler is throttling a request after + WillStartRequest is called on a request without a Client or a request in a + Client which is in a different state since the request was made. Note that + this won't capture requests which have switched state an even number of + times. Switching from Active to Background back to Active will be recorded + in the Active version of this histogram. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the request was created and when the + ResourceScheduler stops throttling the request in a client that was + user-observable at creation and start time. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the request was created and when the + ResourceScheduler stops throttling the request in a client that was + background at creation and start time. + + + + + + Removed 1/2016 + + aiolos@chromium.org + + The amount of time between when the request was created and when the + ResourceScheduler stops throttling a request without a client or a request + in a Client which is in a different state since the request was made. Note + that this won't capture requests which have switched state an even number of + times. Switching from Active to Background back to Active will be recorded + in the Active version of this histogram. + + + + + + Removed in M76. + + shampson@chromium.org + steveanton@chromium.org + + The amount of data that gets read out via each call to the RTCQuicStream + readInto() API. The RTCQuicStream can record multiple ReadIntoAmountBytes in + its lifetime. + + + + + + Removed in M76. + + shampson@chromium.org + steveanton@chromium.org + + How data is read out with a finish (FIN) bit for each call to the + RTCQuicStream readInto API. The RTCQuicStream can record multiple + ReadIntoResults in its lifetime. + + + + + + Removed in M76. + + shampson@chromium.org + steveanton@chromium.org + + The amount of data that gets written via each call to the RTCQuicStream + write() API. The RTCQuicStream can record multiple WriteAmountBytes in its + lifetime. + + + + + + Removed in M76. + + shampson@chromium.org + steveanton@chromium.org + + How data is written with a finish (FIN) bit for each call to the + RTCQuicStream write() API. The RTCQuicStream can record multiple WriteUsages + in its lifetime. + + + + + + Replaced with Tabs.SadTab.* in R20. + + Please list the metric's owners. Add more owner tags as needed. + + Track number of times we built a sad tab page for a renderer crash or kill. + The user may not have seen the page if it was not the frontmost tab. + + + + + + Replaced with Tabs.SadTab.* in R20. + + Please list the metric's owners. Add more owner tags as needed. + + Track number of times the user actually saw a sad tab page for a renderer + crash or kill. + + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the height of content area when the user opens a new browser window + or when the user finishes resizing a browser window. + + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the width of content area when the user opens a new browser window + or when the user finishes resizing a browser window. + + + + + + Not in the code anymore (10/2015). + + feng@chromium.org + + Records the user action that enables/disables safe browsing feature in the + Settings page on Android. + + + + + + Removed in M80 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Number of file types (aka file extensions) present in the FileTypePolicies + proto loaded. + + This is for the file types loaded from the component-update system. This + includes both those loaded from disk shortly after startup, and those + received over the network when the component version changes + + + + + + Removed in M80 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Number of file types (aka file extensions) present in the FileTypePolicies + proto loaded. + + This is for the file types loaded from the resource bundle packaged with + Chrome, which is always loaded at startup. + + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Records the default font size on user startup. + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Records the default fixed font size on user startup. + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Records the minimum font size on user startup. + + + + + Removed in M77. Was used to get a general sense of this value when planning + visual features in PhishGuard pings. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Records the minimum logical font size on user startup. + + + + + Replaced by SafeBrowsing.V4GetHash.Network.Result. + + kcarattini@google.com + + Response or error codes from the SafeBrowsing Pver4 service. Logged after a + GetHash or request finishes to capture the response code or error code for + that call. + + + + + + Replaced by SafeBrowsing.V4GetHash.Network.Time. + + kcarattini@chromium.org + + The time that it took to receive a response from the Safe Browsing servers + for a V4 GetHash request. + + + + + + Replaced by SafeBrowsing.V4GetHash.Result. + + kcarattini@chromium.org + + Track return status from V4 GetHash attempts. The buckets of this histogram + overlap, so the counts cannot be used as percentages. + + + + + + No longer used. Removed 2020-06. + + csharp@chromium.org + proberge@google.com + + A windows only historgram. Records when an unknown base relocation type is + encountered while reading the reloc table of a loaded module. + + + + + + Removed in M71+. + + chrome-safebrowsing-alerts@google.com + + Count of how many ResolvedIPAddresses get removed in each periodic clean up. + This is a rough estimation of the number of IPs associated with main frame + and sub-frame navigations every two minutes. + + + + + + Removed in M85+. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The net error code for failed reports sent by NotificationImageReporter, or + net::OK if successful. + + + + + + Replaced by SafeBrowsing.V4GetHash.Parse.Result. + + kcarattini@chromium.org + + Track the parsing results of a status 200 GetV4Hash request. + + + + + + Replaced by SafeBrowsing.V4Update.Parse.Result. + + chrome-safebrowsing-alerts@google.com + + Track the parsing results of a status 200 GetV4Update request. + + + + + + Removed in or before M86. See SafeBrowsing.Pref.Extended + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the Extended Reporting preference transition. Suffixes track which + opt-in text users are viewing and the values of each Extended Reporting + preference. Recorded for all non-Incognito profiles on profile startup. + + + + + + This is unused due to it being part of SBER1. Deprecated 06/01/2020. + + lpz@chromium.org + + Tracks user decisions about the Extended Reporting opt-in on security + interstitials by comparing the initial and final states of the preference. + Suffixes specify the type of change that was made. Recorded when a user + closes a security interstitial or navigates away. + + + + + + Removed in or before M86. See SafeBrowsing.Pref.Extended.* + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the Extended Reporting preference being changed. Suffixes track which + Extended Reporting preference was changed, and the specific UI that the + change was made on. Recorded when a user changes the preference on any UI. + + + + + + Removed in or before M86. + + lpz@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks reasons for the Extended Reporting preference transition, such as a + user entering an experiment group or seeing a security interstitial for the + first time. Recorded for all non-Incognito profiles on profile startup. + + + + + + Removed in M78 due to lack of use and utility. See crbug.com/975258 + + lpz@chromium.org + + A threat report contains a DOM hierarchy that is ambiguous. This indicates + that the parent/child relationship among the elements in the DOM may not be + accurate. + + + + + + Removed in M78 due to lack of use and utility. See crbug.com/975258 + + lpz@chromium.org + + Whether the threat report generated for a subframe of a page hit the maximum + number of nodes. When this is true, the data from that frame will be + truncated. + + + + + + Removed 09-2020 since this is no longer recorded. + + dtrainor@chromium.org + chrome-safebrowsing-alerts@google.com + + File types that were allowed to be downloaded without verifying their + content nor their source URLs with Safe Browsing. + + + + + + Removed 09-2020 since this is no longer recorded. + + dtrainor@chromium.org + chrome-safebrowsing-alerts@google.com + + File types that were allowed to be downloaded without verifying their + content nor their source URLs with Safe Browsing due to the requestor URL + being on the Safe Browsing whitelist. Each sample recorded on this histogram + is also recorded in SafeBrowsing.UnverifiedDownloads.Allowed. + + + + + + Removed 09-2020 since this is no longer recorded. + + dtrainor@chromium.org + chrome-safebrowsing-alerts@google.com + + File types that were allowed to be downloaded without verifying their + content nor their source URLs with Safe Browsing due to the SafeBrowsing + service being disabled. Each sample recorded on this histogram is also + recorded in SafeBrowsing.UnverifiedDownloads.Allowed. + + + + + + Removed 09-2020 since this is no longer recorded. + + dtrainor@chromium.org + + Count of alternate extensions that were supplied when attempting to download + a file without verifying their content nor their source URLs with Safe + Browsing. + + + + + + Removed 09-2020 since this is no longer recorded. + + dtrainor@chromium.org + chrome-safebrowsing-alerts@google.com + + File types that were blocked from downloaded without verifying their content + nor their source URLs with Safe Browsing. + + + + + + Removed 04/25/2018 since it was not being used actively or monitored. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to copy the SafeBrowsing list update as a string, + into a map which contains the hash prefixes that are looked up when a client + queries for the reputation of a resource (URL, full hash, etc.). + + + + + + Replaced by SafeBrowsing.V4AddUnlumpedHashes.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to copy the SafeBrowsing list update as a string, + into a map which contains the hash prefixes that are looked up when a client + queries for the reputation of a resource (URL, full hash, etc.). + + + + + + Replaced by SafeBrowsing.V4*.ApplyUpdate.Result. + + chrome-safebrowsing-alerts@google.com + + Track the result of applying the update fetched from the PVer4 service for a + particular store. + + + + + + Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Result. + + chrome-safebrowsing-alerts@google.com + + Track the result of applying an update read from disk after parsing it + successfully as a protobuf. + + + + + + Replaced by SafeBrowsing.V4*.DecodeAdditions.Result. + + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of additions of 4-byte + hash prefixes. This is logged once per store, per update containing + Rice-encoded additions. + + + + + + Replaced by SafeBrowsing.V4*.DecodeAdditions.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded additions to the + blacklist into raw format. + + + + + + Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Result. + + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of indexes of hash + prefixes to remove since the last update. This is logged once per store, per + update containing Rice-encoded removals. + + + + + + Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded removals from the + blacklist into raw format. + + + + + + Replaced by SafeBrowsing.V4GetHash.CacheHit.Result. + + kcarattini@chromium.org + chrome-safebrowsing-alerts@google.com + Track cache hits for V4 full hashes. + + + + + Replaced by SafeBrowsing.V4GetHash.Check.Result. + + kcarattini@chromium.org + chrome-safebrowsing-alerts@google.com + Track get hash response hits for V4 full hash requests. + + + + + Replaced by SafeBrowsing.V4GetHash.Network.Time. + + chrome-safebrowsing-alerts@google.com + + The time that it took to receive a response from the Google SafeBrowsing + servers for a full hash request. + + + + + + Removed in favor of the TimeUs variant + + chrome-safebrowsing-alerts@google.com + + The time that it took to check a URL against our in-memory database. It is + dominated by the time to perform checks for CheckBrowseUrl. + + + + + + Removed 01/2019 due to lack of use (Histogram Eraser). + + csharrison@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that it took to check a URL against our in-memory database. It is + dominated by the time to perform checks for CheckBrowseUrl. Note that this + metric is recorded even for users with low resolution clocks. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by SafeBrowsing.V4*.MergeUpdate.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to merge the existing state of the list with the + update. The update may have been received from the server, or it may have + just been read from disk. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to process a SafeBrowsing list full update. It + includes V4AddUnlumpedHashes.Time for each prefix-sized list, and + V4ProcessFullUpdate.MergeUpdate.Time. Additionally, if the update is + Rice-encoded, it includes V4ProcessFullUpdate.DecodeAdditions.Time for each + prefix-sized list that's Rice-encoded. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded additions to the + blacklist into raw format when applying a full update to a store. + + + + + + Removed 04/25/2018 since it was not being used actively or monitored. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to merge the existing state of the list with a + full update received from the server. + + + + + + Replaced by SafeBrowsing.V4ProcessFullUpdate.ApplyUpdate.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to process a SafeBrowsing list full update. It + includes V4AddUnlumpedHashesTime for each prefix-sized list, and + V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes + V4DecodeAdditionsTime for each prefix-sized list that's Rice-encoded. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to process a SafeBrowsing list partial update. It + includes V4AddUnlumpedHashes.Time for each prefix-sized list, and + SafeBrowsing.V4ProcessPartialUpdate.MergeUpdate.Time. Additionally, if the + update is Rice-encoded, it includes + V4ProcessPartialUpdate.DecodeRemovals.Time, and + V4ProcessPartialUpdate.DecodeAdditions.Time for each prefix-sized list + that's Rice-encoded. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded additions to the + blacklist into raw format when applying a partial update to a store. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded removals from the + blacklist into raw format when applying a partial update to a store. + + + + + + Removed 04/25/2018 since it was not being used actively or monitored. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to merge the existing state of the list with a + partial update received from the server. + + + + + + Replaced by SafeBrowsing.V4ProcessPartialUpdate.ApplyUpdate.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to process a SafeBrowsing list partial update. It + includes V4AddUnlumpedHashesTime for each prefix-sized list, and + V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes + V4DecodeRemovalsTime, and V4DecodeAdditionsTime for each prefix-sized list + that's Rice-encoded. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to read, parse, and process a SafeBrowsing list + stored on disk. This happens at Chromium start-up. It includes + V4AddUnlumpedHashes.Time for each prefix-sized list, and + SafeBrowsing.V4ReadFromDisk.MergeUpdate.Time. Additionally, if the file is + Rice-encoded, it includes V4ReadFromDisk.DecodeAdditions.Time for each + prefix-sized list that's Rice-encoded. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes to decode the Rice-encoded additions to the + blacklist into raw format when reading a store file from disk. + + + + + + Removed 04/25/2018 since it was not being used actively or monitored. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to perform in-memory copy of the map of raw hash + prefixes read from disk. + + + + + + Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Time. + + chrome-safebrowsing-alerts@google.com + + Records the time it takes to read, parse, and process a SafeBrowsing list + stored on disk. This happens at Chromium start-up. It includes + V4AddUnlumpedHashesTime for each prefix-sized list, and V4MergeUpdateTime. + Additionally, if the file is Rice-encoded, it includes V4DecodeAdditionsTime + for each prefix-sized list that's Rice-encoded. + + + + + + Removed in M77 since the histogram was very stable: crbug.com/984286. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how often IsStoreAvailable fails due to an invalid store identifier. + This is logged each time a store is checked (a few times for each download, + and once when a potentially dangerous subresource is loaded). + + + + + + Replaced by SafeBrowsing.V4StoreRead.Result. + + chrome-safebrowsing-alerts@google.com + + Track the parsing results of reading the SafeBrowsing V4 store file from + disk. Recorded every time a store is read from disk. + + + + + + Removed in M78 since there's only ever been just 1 version number. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Version of V4Store read from a store file. This would be useful in tracking + the usage and rollout of new V4Store versions. + + + + + + Replaced by SafeBrowsing.V4StoreWrite.Result. + + chrome-safebrowsing-alerts@google.com + + Track the results of writing the SafeBrowsing V4 store file to disk. + Recorded every time a store is written to disk. + + + + + + Removed in M86. See https://crbug.com/1089439 + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the presence of store files that were previously created but have been + deprecated since so need to be removed from disk. Logged once per startup. + + + + + + Removed in M73. See https://crbug.com/916192 + + chrome-safebrowsing-alerts@google.com + + Track the presence of Safe Browsing list files used for PVer3, which has + been deprecated. Logged once per startup. + + + + + + Removed in M78 due to lack of use and timed out rate being less than 0.03% + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + True if a PVer4 update request timed out. + + + + + Replaced by SafeBrowsing.V4Update.Network.Result. + + chrome-safebrowsing-alerts@google.com + + Response or error codes when fetching updates from the SafeBrowsing PVer4 + service. + + + + + + Replaced by SafeBrowsing.V4Update.ResponseSizeKB. + + chrome-safebrowsing-alerts@google.com + + The size of the response sent by the SafeBrowsing PVer4 service, in KB. + + + + + + Replaced by SafeBrowsing.V4Update.Result. + + chrome-safebrowsing-alerts@google.com + + Track return status from V4 update attempts. The buckets of this histogram + overlap, so the counts cannot be used as percentages. + + + + + + Removed in June 2020. + + ricea@chromium.org + + Time spent on SafeBrowsing lookup. Since this includes any time spent on the + interstitial page the average may not be useful. + + + + + + Removed in June 2019. + + ricea@chromium.org + + Results of a SafeBrowsing lookup for a WebSocket handshake. All lookups are + counted. Note: the "ABANDONED" bucket contains both connections + that were abandoned before the check completed and those that were cancelled + when the user navigated away from the SafeBrowsing interstitial. + + + + + + Removed in December 2019 because logic was simplified to remove this race. + + ntfschr@chromium.org + + WebView can simultaneously check for user opt-in and Safe-Browsing-check the + first URL, with both asynchronous checks racing to finish. This records the + outcome of that race: (1) which asynchronous method finished first; (2) if + user consent finished first, what was the outcome; and (3) did we show + malicious content to the user. This is recorded only once, for the first + Safe Browsing check. + + + + + + Removed 06/2020 as SafeBrowsingBinaryUploadRequest.TimeToGetFCMToken + provides the same information with a better range of durations. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This record how long it took for the request to get the FCM token. It is + logged every time a deep scanning request successfully gets a token. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The first stage check that measures the time that Chrome took to check if a + URL is present in our in-memory bloom filter. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + TBD. + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The second stage check that measures the time that Chrome took to check if a + URL is present in our SQLite database. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The second stage check that mesures the time that Chrome took to check if a + URL is present in our SQLite database. This time includes the filter check + time. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + This measures the time that SafeBrowsing actually delayed the browsing + experience. It records the difference between the time when Chrome would + have started reading the response for a URL and when the SafeBrowsing system + completed its check of that URL. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The first stage check that measures the time that Chrome took to check if a + URL is present in our in-memory hash table. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The third and final stage check that mesures the time that Chrome took to + get a response from the Google SafeBrowsing servers for a particular URL. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + The third and final stage check that mesures the time that Chrome took to + get a response from the Google SafeBrowsing servers for a particular URL. + This time includes the filter and database check time. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + + This measures the time that SafeBrowsing actually delayed the browsing + experience. It records the difference between the time when Chrome would + have started reading the response for a URL and when the SafeBrowsing system + completed its check of that URL. + + + + + + Has not been generated for years (7/8/14). + + Please list the metric's owners. Add more owner tags as needed. + TBD. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The number of add prefixes stored in the database after the last update. + + + + + + Bloom filter support deleted in October 2012. + + Please list the metric's owners. Add more owner tags as needed. + + Track failures when in processing the safe-browsing database bloom filter. + + + + + + This became misleading around M-22 (September 2012), deleted in M-32 + (November 2013). + + Please list the metric's owners. Add more owner tags as needed. + + All prefix misses (server returned no full hashes) and prefix misses due to + false positives in the bloom filter. + + + + + + Bloom filter support deleted in October 2012. + + Please list the metric's owners. Add more owner tags as needed. + Time to load the BloomFilter file. + + + + + Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.Browse. + + chrome-safebrowsing-alerts@google.com + + The size of the browsing SafeBrowsing database file on disk in kilobytes, + after an update has occurred. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The time that it took to regenerate the filter after we have received all + the update chunks. + + + + + + Removed because it was exceeding the range. Replaced by + SB2.BuildReadKilobytes. + + Please list the metric's owners. Add more owner tags as needed. + + The number of bytes read by the browser process during the bloom filter + generation phase. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The number of kilobytes read by the browser process during the filter + generation phase. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The number of read operations issued by the browser process during the + filter generation phase. + + + + + + Removed because it was exceeding the range. Replaced by + SB2.BuildWriteKilobytes. + + Please list the metric's owners. Add more owner tags as needed. + + The number of bytes written by the browser process during the bloom filter + generation phase. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The number of kilobytes written by the browser process during the filter + generation phase. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The number of write operations issued by the browser process during the + filter generation phase. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The time that it takes to write one redirect URL (which can contain multiple + chunks) to the database. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The network time between the request and response for a chunk. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + The size of one chunk URL. + + + + + Removed because it was exceeding the range. Replaced by + SB2.DatabaseKilobytes. + + Please list the metric's owners. Add more owner tags as needed. + The size of the SafeBrowsing database file on disk. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + Track failures when updating the safe-browsing database. + + + + + Replaced by SB2.BrowseDatabaseKilobytes. + + chrome-safebrowsing-alerts@google.com + + The size of the SafeBrowsing database file on disk in kilobytes. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The time it takes to initialize the SafeBrowsing storage backend, in + milliseconds. + + + + + + Removed after the launch of PVer4 in M57. + + gab@chromium.org + + The size of one of the SafeBrowsing database file on disk in kilobytes, + after a database update has occurred (once a few minutes after startup, and + every thirty minutes or so thereafter). + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The size of the update file before merging with the database file, in + kilobytes. + + + + + + Removed in M65. Replaced by SB2.NoUserActionResourceLoadingDelay + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that SafeBrowsing actually delayed the browsing experience. It + records the difference between the time when Chrome would have started + reading the response for a URL and when the SafeBrowsing system completed + its check of that URL. This is the sum of .Mainframe and .Subresource + breakout metrics. + + + + + + Removed in M65. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that SafeBrowsing actually delayed the browsing experience. It + records the difference between the time when Chrome would have started + reading the response for a URL and when the SafeBrowsing system completed + its check of that URL. Logged for main frame resources only. + + + + + + Removed in M65. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that SafeBrowsing actually delayed the browsing experience. It + records the difference between the time when Chrome would have started + reading the response for a URL and when the SafeBrowsing system completed + its check of that URL. Logged for non-main frame resources only. + + + + + + Deleted in M-34 (February 2014). + + Please list the metric's owners. Add more owner tags as needed. + Obsolete download BINHASH add chunks deleted. + + + + + Deleted in M-34 (February 2014). + + Please list the metric's owners. Add more owner tags as needed. + Obsolete download BINHASH sub chunks deleted. + + + + + Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.Download. + + chrome-safebrowsing-alerts@google.com + + The size of the downloads SafeBrowsing database file on disk in kilobytes, + after an update has occurred. + + + + + + Removed 01/2017. Was measuring the lifetime of a network request + corresponding to a download, which may or may not correspond to the total + duration of a download. + + chrome-safebrowsing-alerts@google.com + The time it takes for a download to finish. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + The time it takes for SafeBrowsing to check hash of a download file. + + + + + + Removed 3/11/11, and replaced by SB2.DownloadChecks. + + Please list the metric's owners. Add more owner tags as needed. + Records results of SafeBrowsing download url check. + + + + + Removed 03/2015. Replaced by + SecurityInterstitialInteraction::EXTENDED_REPORTING_IS_ENABLED. + + felt@chromium.org + + Whether the user has Safe Browsing extended reporting enabled at the time a + Safe Browsing warning was dismissed. This tracks the fraction of all SB + interstitials that had reporting enabled. + + + + + + Removed, replaced by SB2.DatabaseFailure BROWSE_DB_UPDATE_FINISH. + + Please list the metric's owners. Add more owner tags as needed. + + The count of the number of times an update failed when being committed to + the database. + + + + + + Removed in favor of SafeBrowsing.V4GetPrefixMatches.TimeUs + + chrome-safebrowsing-alerts@google.com + + The time that it took to check a URL against our in-memory filter. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + The size of the current bloom filter in kilobytes. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + Which filter file the database loaded from disk. + + + + + Removed, replaced by SB2.DatabaseFailure FILTER_MISSING. + + Please list the metric's owners. Add more owner tags as needed. + + The count of the number of times we attempted to load the bloom filter file + but it was missing. + + + + + + Removed, replaced by SB2.DatabaseFailure FILTER_READ. + + Please list the metric's owners. Add more owner tags as needed. + + The count of the number of times we attempted to load the bloom filter file + but failed while reading the file on disk. + + + + + + Removed because it was exceeding the range. Replaced by SB2.FilterKilobytes. + + Please list the metric's owners. Add more owner tags as needed. + The size of the current bloom filter. + + + + + Removed, replaced by SB2.DatabaseFailure FILTER_WRITE. + + Please list the metric's owners. Add more owner tags as needed. + + The count of the number of times we attempted to save the bloom filter file + but failed while writing the file to disk. + + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + Collection of boolean events for SafeBrowsingFileStore instances. Includes + corruptions detected, old versions detected, and various failures detected. + + + + + + Removed after the launch of PVer4 in M57. + + vakh@google.com + + Response or error codes from the SafeBrowsing service. Logged after a + GetChunk request finishes to capture the response code or error code for + that call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49. + + + + + + Removed in favor of SB2.GetHashResult STATUS_200. + + Please list the metric's owners. Add more owner tags as needed. + + The number of GetHash requests that returned data (valid requests). + + + + + + Removed in favor of SB2.GetHashResult STATUS_204. + + Please list the metric's owners. Add more owner tags as needed. + + The number of GetHash requests that returned empty data (false positives). + + + + + + Removed after the launch of PVer4 in M57. + + mattm@chromium.org + + Track return status from GetHash attempts (STATUS_200, STATUS_204, + NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result + failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT, + MISS). EMPTY means the response had no full hashes, and should contain all + of the 204 responses plus all *_ERROR cases. HIT means that one of the full + hashes matched. MISS means that none of the hashes matched (there was a + prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and + BACKOFF_ERROR were added in M36.) + + + + + + Removed after the launch of PVer4 in M57. + + mattm@chromium.org + + Track return status from GetHash attempts (STATUS_200, STATUS_204, + NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result + failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT, + MISS). EMPTY means the response had no full hashes, and should contain all + of the 204 responses plus all *_ERROR cases. HIT means that one of the full + hashes matched. MISS means that none of the hashes matched (there was a + prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and + BACKOFF_ERROR were added in M36.) + + + + + + Removed in favor of SB2.GetHashResult FULL_HASH_* and + SB2.BloomFilterFalsePositives. It is unclear if this histogram ever reported + useful data. + + Please list the metric's owners. Add more owner tags as needed. + + The number of GetHash requests returning full hashes that didn't match the + URL that initiated the request. + + + + + + Removed, replaced by SB2.DatabaseFailure CORRUPT. + + Please list the metric's owners. Add more owner tags as needed. + + The count of the number of times a database was found corrupt and reset. + + + + + + Removed, replaced by: interstitial.malware.* and interstitial.phishing.*. + + felt@chromium.org + + Track number of times Safe Browsing interstitials have been shown, and how + many times they have been clicked through or not. + + + + + + Removed, replaced by: interstitial.malware.* and interstitial.phishing.*. + + felt@chromium.org + + Tracks the click-through rate for specific cases of the interstitial. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user navigating away by for example, closing the tab, clicking the browser + back button or typing another URL in the address bar. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user clicking on diagnostic page link. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user expanding the "see more info" section of the page. (Only + applies to field trial version 2 of the interstitial.) + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user clicking on the learn more about malware link. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user clicking on the privacy policy link. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user clicking on the proceed link. + + + + + + Removed 9/2014. + + felt@chromium.org + + The time between when we show the SafeBrowsing malware interstitial and the + user clicking on the big green back button. + + + + + + Removed in M65. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that it took to receive a response from the Google SafeBrowsing + servers for a GetHash request. + + + + + + Removed in M77 since it is fairly flat and not really useful. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The total delay, in milliseconds, caused by SafeBrowsing for a resource + load, if the SafeBrowsing interstitial page is not shown and therefore no + user action is involved. At most one value is reported for each resource + load. If SafeBrowsing causes delays at different stages of a load, the sum + of all the delays will be reported. + + + + + + Removed 7/2014. No longer generated. + + chrome-safebrowsing-alerts@google.com + Size of v1 database deleted from client profile. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + + Indicates how sharded safe-browsing on-disk stores are. Values like 0 to 4 + are reasonable. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + + The size of the PrefixSet storage in bits, divided by the number of prefixes + represented. Should almost always be 16. + + + + + + Removed 9/2012. No longer generated, BloomFilter being removed. + + Please list the metric's owners. Add more owner tags as needed. + + Records how well the PrefixSet implementation matches the BloomFilter + implementation. + + + + + + Removed 01/2014. Replaced by suffixed SB2.PrefixSetSizeKilobytes. + + chrome-safebrowsing-alerts@google.com + The size of one of the PrefixSet files in kilobytes. + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + Time to load one of the PrefixSet files. + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. How many extra results GetPrefixes returns. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. How many fewer results GetPrefixes returns. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + + The size of one of the PrefixSet files in kilobytes. Logged after a database + update has occurred and the PrefixSet has been flushed to disk (once a few + minutes after startup, and every thirty minutes or so thereafter). + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. How far unsorted deltas are from expected value. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. Distance of unsorted elements from expected + location. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. How far into the results unsorted elements were + found. Interesting values would be 0%, 50%, or 100%. + + + + + + Removed 9/2012. No longer generated. + + Please list the metric's owners. Add more owner tags as needed. + + For debugging PrefixSet. Size of unsorted sets. To see if there is a problem + with a particular size of dataset. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + Version read from one of the PrefixSet files. + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + Time to store one of the PrefixSet files. + + + + + Removed in M84. This feature is not launched. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates whether the local Safe Browsing blacklists can be used on this + Android device. Logged once on first URL check request. + + + + + + Removed Oct 2018 + + csharrison@chromium.org + chrome-safebrowsing-alerts@google.com + + Wall time in microseconds for calling + Java_SafeBrowsingApiBridge_startUriLookup. Logged at every Safe Browsing + check on Android. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M64 (Nov 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + + Number of outstanding calls for URLs getting classified through + RemoteSafeBrowsingDatabaseManager. The size of the queue is logged before + initiating each request. + + + + + + No longer generated. Replaced by SB2.RemoteCall.InternalErrorStatusCode2 + + chrome-safebrowsing-alerts@google.com + + The status code provided by GmsCore if it is unable to respond to a URL + check request due to incorrect initialization, not being ready, etc. Logged + on each URL check that hits the internal error condition. The total number + of these should add up to the INTERNAL_ERROR reports under + SB2.RemoteCall.Result. + + + + + + Removed M81. The latency looks good, not needed anymore. + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates the time for synchronous local allowlist lookup on Java side. This + metrics provides the evidence of whether asynchronous implementation is + needed for local allowlist. + + + + + + Removed in M84. This feature is not launched. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates the time since the local blacklists were successfully updated + last. Logged each time the verdict of local blacklists lookup is stale or + possibly unsafe, if the local blacklists feature is enabled (i.e. + SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) + + + + + + Removed in M84. This feature is not launched. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates the result of local Safe Browsing blacklist lookup on Android. + Logged for each URL lookup, if the local blacklists feature is enabled (i.e. + SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) + + + + + + Removed in M84. This feature is not launched. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates the result of local blacklists' update. Logged each time an update + of local blacklists is attempted, if the local blacklists feature is enabled + (i.e. SB2.RemoteCall.CanUseLocalBlacklists == ENABLED) + + + + + + Removed 06/2014. Replaced by SB2.ExtendedReportingIsEnabled. + + Please list the metric's owners. Add more owner tags as needed. + + Whether the user has Safe Browsing extended reporting enabled at the time a + Safe Browsing warning was dismissed. This tracks the fraction of all SB + interstitials that had reporting enabled. + + + + + + Superseded by SB2.ResourceTypes2 in December 2015. + + chrome-safebrowsing-alerts@google.com + + Resource types of resources that were inspected by Safe Browsing in the + SafeBrowsingResourceThrottle. + + + + + + Removed 03/2015. Replaced by + SecurityInterstitialInteraction::SET_EXTENDED_REPORTING_ENABLED. + + felt@chromium.org + + Tracks changes to the Safe Browsing extended reporting opt-in which is shown + in the Safe Browsing interstitial. + + + + + + Removed 06/2014. Replaced by SB2.SetExtendedReportingEnabled. + + Please list the metric's owners. Add more owner tags as needed. + + Tracks changes to the Safe Browsing extended reporting opt-in which is shown + in the Safe Browsing interstitial. + + + + + + Removed 12/2014. Merged into SB2.PrefixSetWrite. + + chrome-safebrowsing-alerts@google.com + + Time to store the Side Effect Free Whitelist PrefixSet file. Note: this + histogram was intended to be stored as + SB2.SideEffectFreeWhitelistPrefixSetWrite but was actually reported as + SB2.SideEffectFreePrefixSetWrite from its inception to its deprecation... + + + + + + Removed 12/2014. Moved to SB2.DatabaseSizeKilobytes.SideEffectFreeWhitelist. + + chrome-safebrowsing-alerts@google.com + + The size of the Side Effect Free Whitelist SaafeBrowsing database file on + disk in kilobytes, after an update has occurred. + + + + + + Removed 12/2014. Moved to + SB2.PrefixSetSizeKilobytes.SideEffectFreeWhitelist. + + chrome-safebrowsing-alerts@google.com + + The size of the Side Effect Free Whitelist PrefixSet file in kilobytes, + after an udpate has occurred. + + + + + + Removed 12/2014. Merged into SB2.PrefixSetLoad. + + chrome-safebrowsing-alerts@google.com + Time to load the Side Effect Free Whitelist PrefixSet file. + + + + + Removed 4/2015. + + chrome-safebrowsing-alerts@google.com + The instantiation status of the SideEffectFreeWhitelist. + + + + + Removed after the launch of PVer4 in M57. + + chrome-safebrowsing-alerts@google.com + Version read from the store file. + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + + The number of sub prefixes stored in the database after the last update. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + + The time from the receipt of the update request to the receipt of the final + update chunk. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + The payload size of update requests to the server. + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + Result from trying to update the SafeBrowsing data. + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + The size of all the chunk URLs in an update response. + + + + + Was used for an experiment in late 2014. + + chrome-safebrowsing-alerts@google.com + + The size of all the chunk URLs in an update response when Chrome is in the + background. + + + + + + Was used for an experiment in late 2014. + + chrome-safebrowsing-alerts@google.com + + The size of all the chunk URLs in an update response when Chrome is in the + foreground. + + + + + + Removed in M58 (Aug 2017). No longer generated. + + chrome-safebrowsing-alerts@google.com + The number of chunk URLs in an update response. + + + + + The operation this is tracking has been deleted as of 09/2014. + + chrome-safebrowsing-alerts@google.com + + Older versions of the safe-browsing code incorrectly added additional + SBPrefix items when receiving full hashes. This caused errors when + calculating when to send gethash requests to the server. An additional pass + over the data has been added to remove the excess prefixes. This histogram + tracks progress of that code for purposes of informing a decision on when to + remove the additional pass. See http://crbug.com/361248 . + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + chrome-safebrowsing-alerts@google.com + dtrainor@chromium.org + + Records a histogram of archive file types that were found while examining a + downloaded ZIP file. Each archive file type in a single ZIP file is recorded + at most once. The relative incidence rate of each filetype in this histogram + should indicate the probability of finding that file type in a ZIP file + given that that ZIP file contains an archive file. + + + + + + This histogram was marked obsolete in 08/2020 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records a histogram of how often users download a file with a possibly + dangerous file extension (e.g., exe, class) within an archive. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The original number of archived_binaries found in a DMG-like file when it's + scanned, if at least one is found. The actual number sent in the download + request may be capped below this value. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of DMG-like file types that failed to be successfully analyzed by the + SafeBrowsing download service. + + + + + + Replaced by SBClientDownload.DmgFileHas[No]ExecutableByType in M51. + + rsesek@chromium.org + + For each DMG file analyzed by the SafeBrowsing download service, records if + the DMG contained an executable file. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of DMG-like file types which were analyzed by the SafeBrowsing + download service that contained an executable file. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of DMG-like file types which were analyzed by the SafeBrowsing + download service that did NOT contain an executable file. + + + + + + Replaced by SBClientDownload.DmgFile{Success,Failure}ByType in M51. + + rsesek@chromium.org + + For each DMG file analyzed by the SafeBrowsing download service, records + true if the analysis was successful, or false if there was an error + analyzing the file. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a given DMG download was too big to unpack, as specified by + configuration option set in SafeBrowsing download service. This metric is + logged each time the user downloads a DMG file on Mac. + + + + + + Removed 09/19, since the metric was not being actively used and there were + no near-term plans to begin using it. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + A Mac-only metric that records whether a given download contains a detached + code signature file. This metric is logged before Chrome sends SafeBrowsing + download pings. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether download files without an Apple disk image file extension + have a 'koly' signature. This can be used to identify distribution of disk + image files to Mac users without simply relying on file extension. This + metric is logged before Chrome sends SafeBrowsing download pings. + + + + + + Removed in M78, since the metrics were not being actively used and there was + no near-term plan to begin using them. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the portion of the SafeBrowsing download service check starting with + the point CheckClientDownloadRequest::StartTimeout() is called. It is + recorded regardless if a ping was sent or not. It is not recorded for + requests that were cancelled. + + + + + + Removed in M78, since the metrics were not being actively used and there was + no near-term plan to begin using them. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + For SafeBrowsing binary download checks which reached the + CheckClientDownloadRequest::StartTimeout() call, records the final result + (once the check finishes or is cancelled). + + + + + + Removed in M76, replaced by SBClientDownload.ExtractDmgFeaturesTimeMedium. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + rsesek@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded DMG file. + + + + + + Removed in M77. Extracting image headers was usually fast (84% were less + than 1ms), so this histogram was not providing useful data. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + grt@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + image headers from a downloaded binary. + + + + + + Removed in M76, replaced by SBClientDownload.ExtractRarFeaturesTimeMedium. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded rar file. + + + + + + Removed in M78, since the metrics were not being actively used and there was + no near-term plan to begin using them. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + signature info from a downloaded binary. This includes both unsigned and + signed binaries. + + + + + + Removed in M76, replaced by SBClientDownload.ExtractZipFeaturesTimeMedium. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded zip file. + + + + + + Removed in 08/2018. + + dtrainor@chromium.org + Time taken to complete a PPAPIDownloadRequest. + + + + + Removed in 08/2018. + + dtrainor@chromium.org + + Outcome of running CheckPPAPIDownloadRequest. Most failure modes cause an + UNKNOWN result to be returned to the caller. If the attempt succeeds, the + result returned to the caller is based on the SafeBrowsing resopnse. The + final result returned is counted in + SBClientDownload.PPAPIDownloadRequest.Result. + + + + + + Removed in 08/2018. + + dtrainor@chromium.org + Result returned to the caller of CheckPPAPIDownloadRequest. + + + + + Removed 09-2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The original number of archived_binaries found in a rar-like file when it's + scanned, if at least one is found. The actual number sent in the download + request may be capped below this value. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each rar file analyzed by the SafeBrowsing download service, records + true if the rar did not contain any executables but did contain another + archive file, false otherwise. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each rar file analyzed by the SafeBrowsing download service, records if + the rar contained an executable file. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each rar file analyzed by the SafeBrowsing download service, records if + the unpacking was 100% successful. + + + + + + Marked obsolete 07-2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether the RAR headers are encrypted, preventing any meaningful + content analysis. This is in contrast to encryption of the content of the + archive, which still exposes file name information. This histogram is + recorded every time a RAR archive is downloaded. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each rar file analyzed by the SafeBrowsing download service, records if + the file could be opened. This should be close to 100% success because the + library doesn't actually open the file; it is handed an open file handle and + the Open() function call sets that as the file handle to use. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each rar file analyzed by the SafeBrowsing download service, records if + the unrar library considers this file a valid RAR archive. It includes + checking the following, and more: magic number is present, valid RAR version + format can be parsed, headers are valid, etc. + + + + + + Removed in M78, since the metrics were not being actively used and there was + no near-term plan to begin using them. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the number of signed vs. unsigned executables that are downloaded. + + + + + + Removed in Chrome 50. Replaced by SBClientDownload.CheckWhitelistResult.*. + + mattm@chromium.org + + Counter which is incremented whenever an executable is downloaded which is + either signed or whose URL matches the download whitelist. + + + + + + Removed M76, since there had been no such downloads for over a year. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how often different file extensions are downloaded with schemes that + aren't supported by Safe Browsing (e.g. ftp, gopher, content, cid, etc). + + + + + + Removed in M79 due to lack of use, and no future plans for use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether the total uncompressed size of a ZIP overflowed our total. + This is logged once per ZIP file scanned. + + + + + + Removed in M79 due to lack of use, and no future plans for use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the compression ratio for each scanned ZIP archive. This is logged + once per ZIP file scanned, unless + SBClientDownload.ZipArchiveUncompressedSizeOverflow is true. + + + + + + Removed in M79 due to lack of use, and no future plans for use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the uncompressed size of each entry in a scanned ZIP file. This + histogram is logged once per entry in the ZIP. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The original number of archived_binaries found in a zip-like file when it's + scanned, if at least one is found. The actual number sent in the download + request may be capped below this value. + + + + + + Removed in 12/2018 during a refactoring. The data was not being actively + used. + + chrome-safebrowsing-alerts@google.com + + A Mac-only metric that records whether a downloaded zip file contains an + .app directory, signifying the presence of installable software. + + + + + + Removed 09/19, since the metric was not being actively used and there were + no near-term plans to begin using it. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of ZIP-like file types that failed to be successfully analyzed by the + SafeBrowsing download service. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + For each zip file analyzed by the SafeBrowsing download service, records + true if the zip did not contain any executables but did contain another zip + file, false otherwise. + + + + + + This histogram was marked obsolete in 05/2020 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + For each zip file analyzed by the SafeBrowsing download service, records if + the zip contained an executable file. + + + + + + Removed 04/19. This approach to measuring platform-dependent extraction does + not work, so the data was not useful. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of Local File Headers (identified by their magic number) present + in the file, that were not extracted during ZIP inspection. A non-zero entry + implies some potential files were not extracted. That could be intended, or + it could indicate ZIPs with platform-dependent extraction. This metric is + sampled with small probability during each ZIP download. + + + + + + Removed 09/19, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of ZIP-like file types were successfully analyzed by the SafeBrowsing + download service. + + + + + + Removed in M77, since the metric was not being actively used and there were + no near-term plans to begin using it. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a given ZIP download was too big to unpack, as specified by + configuration option set in SafeBrowsing download service. This metric is + logged each time the user downloads a ZIP file. + + + + + + Removed in 07-2020 since the SBClientMalware feature was removed. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of pages that we could have possibly classified (essentially the + number of top page navigations by users with SBClientMalware enabled). The + name is slightly misleading as it is recorded before + "Preclassification" happens. + + + + + + Removed in 07-2020 since the SBClientMalware feature was removed. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of malware classifications that were skipped because a + pre-classification check failed. + + + + + + Removed in 07-2020 since the SBClientMalware feature was removed. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + True if at least one resource url matched the malware IP list. Recorded when + client side malware feature extraction is done. + + + + + + Removed 03/2014. That part of the code got deleted. + + noelutz@chromium.org + + Counts the number of times the page ID that completed the page load does not + match the browse info page ID. We expect that number to be zero. + + + + + + Removed in M47. + + noelutz@chromium.org + + The number of times client-side phishing classifier expected to have no + pending classifications running but that check failed. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The counts for phishing verdicts given by client side model. + + + + + + Removed in M47 + + noelutz@chromium.org + Time spent generating the thumbnail. + + + + + Removed in Chrome 37, which now uses //net's internal matching. + + mattm@chromium.org + + The number of times that the phishing detection service could not be + initialized due to an error parsing the private IP networks. This would + indicate a bug. + + + + + + Removed 12/2011. Whitelist entries are no longer part of + ClientPhishingResponse. + + Please list the metric's owners. Add more owner tags as needed. + + The number of whitelist_expression entries in a ClientPhishingResponse that + could not be canonicalized. + + + + + + This was replaced by SBClientPhishing.PreClassificationCheckResult in + 08-2020, since that histogram is easier to reason about. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of phishing classifications that were skipped because a + pre-classification check failed. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The counts for phishing verdicts given by server side model. + + + + + + Removed in M77 due to lack of use. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The counts for various reasons why a phishing classification is skipped. + + + + + + Removed in M77, since the information was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Count of times download feedback has been started, broken down by danger + type. + + + + + + Marked obsolete 07-2020 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + When a new download feedback request is added, records the number of + download requests currently active and/or pending. + + + + + + Removed in M85, since the histogram is not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Count of times eligible download notifications are shown. Broken down by + danger type. + + + + + + Removed in M77, since the information was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Count of times download feedback cannot be sent due to empty file path. + + + + + + Removed in M86, since the information was not being used. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The net error or response code that caused the TwoPhaseUploader to fail + while uploading the file. This is logged whenever the TwoPhaseUploader fails + while uploading the file. + + + + + + Removed in M86, since the information was not being used. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The net error or response code that caused the TwoPhaseUploader to fail + while uploading metadata. This is logged whenever the TwoPhaseUploader fails + while uploading metadata. + + + + + + Starting with M32, replaced by SBDownloadFeedback.Eligible. + + mattm@chromium.org + + Count of times download feedback button has been shown, broken down by + danger type. + + + + + + Removed in M77, since the information was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Size of downloads that were of the correct danger type, regardless if they + meet the max file size check or if they are actually uploaded or not. + + + + + + Marked obsolete 07-2020 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Size of downloads that failed to be uploaded to the feedback service. + + + + + + Marked obsolete 07-2020 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Size of downloads that were successfully uploaded to the feedback service. + + + + + + Removed in M77, since the information was not being used. + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For each non-SAFE file, records whether the server requested that that file + be uploaded. + + Logged before checking the file size, so it may be dropped there. + + + + + + Marked obsolete 07-2020 due to lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Final result of attempt to upload binary to download feedback service. + + + + + + Blacklist Load analysis was removed in M63. + + caitkp@google.com + + The elapsed time to compute the hash of a blacklisted module. + + + + + + Blacklist Load analysis was removed in M63. + + caitkp@google.com + + The elapsed time to validate the signature of a blacklisted module. + + + + + + Removed 07/2019. + + caitkp@google.com + + The number of incidents collated into a single safe browsing incident + report. + + + + + + Removed 08/2015. + + caitkp@google.com + + The percentage of incidents pruned from a safe browsing incident report on + account of having been previously reported. + + + + + + Removed Jan 2020. + + grt@google.com + + The size, in bytes, of a profile's platform state store. This histogram is + logged on each write, which always replaces any previous contents. + + + + + + Removed Jan 2020. + + grt@google.com + The result of loading data from the platform state store. + + + + + Removed 07/2019. + + caitkp@google.com + The elapsed time to upload a safe browsing incident report. + + + + + Removed 07/2019. + + proberge@google.com + + The result of initializing the state store and comparing the preferences to + the platform-specific state store. + + + + + + Suspicious Module detection was removed in M63. + + proberge@google.com + + The elapsed time to check loaded modules against the module whitelist. + + + + + + Suspicious Module detection reporting removed in M63. + + proberge@google.com + The number of suspicious modules found. + + + + + Suspicious Module detection reporting removed in M63. + + proberge@google.com + + The elapsed time to create incidents for suspicious modules. + + + + + + Superseded by SBOffDomainInclusion2.Abort in December 2015. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis was aborted. This histogram is suffixed with the abort + reason. + + + + + + Removed 01/2015. + + gab@chromium.org + + Logs the resource type of each resource request for which an off-domain + inclusion was detected by the OffDomainInclusionDetector. + + + + + + Removed 01/2015. Moved to SBOffDomainInclusion.Abort.EmptyMainFrameURL. + + gab@chromium.org + + Logs the resource type of each resource request for which the main frame URL + was unexpectedly empty in the OffDomainInclusionDetector. + + + + + + Superseded by SBOffDomainInclusion2.InHistory in December 2015. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis concluded in no inclusion whitelist hit but a browsing + history hit. + + + + + + Removed 01/2015 (was never reported, confirming experiment that handling it + is irrelevant). + + gab@chromium.org + + Logs the resource type of each resource request for which the main frame URL + was unexpectedly invalid (and not empty) in the OffDomainInclusionDetector. + + + + + + Superseded by SBOffDomainInclusion2.RequestAnalyzed in December 2015. + + gab@chromium.org + + Logs the resource type of each resource request analyzed by the + OffDomainInclusionDetector. + + + + + + Superseded by SBOffDomainInclusion2.Suspicious in December 2015. + + gab@chromium.org + + Logs the resource type of each resource request for which an off-domain + inclusion was detected by the OffDomainInclusionDetector and considered + suspicious. + + + + + + Superseded by SBOffDomainInclusion2.Suspicious in December 2015. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis concluded in an inclusion whitelist hit. + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis was aborted. This histogram is suffixed with the abort + reason. + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis concluded in no inclusion whitelist hit but a browsing + history hit. + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + gab@chromium.org + + Logs the resource type of each resource request analyzed by the + OffDomainInclusionDetector. + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + gab@chromium.org + + Logs the resource type of each resource request for which an off-domain + inclusion was detected by the OffDomainInclusionDetector and considered + suspicious. + + + + + + Removed 2016-05 as the OffDomainInclusionDetector was removed. + + gab@chromium.org + + Logs the resource type of each resource request for which the off-domain + inclusion analysis concluded in an inclusion whitelist hit. + + + + + + 2020-02-25: Replaced by Scheduler.CancelableTaskTracker.TaskState, which + allows correlation of live/canceled with same/off-sequence states. + + wez@chromium.org + scheduler-dev@chromium.org + + True if a task posted to CancelableTaskTracker was canceled before it got + the chance to run. Recorded for every task posted via CancelableTaskTracker, + immediately before it would be run. + + + + + + 2020-02-25: Replaced by Scheduler.CancelableTaskTracker.TaskDuration2_* + which correllate duration with liveness, off-sequence and task priority + states. + + wez@chromium.org + scheduler-dev@chromium.org + + Time taken for a task posted to a CancelableTaskTracker to run. Durations + are not recorded for canceled tasks. + + + + + + Replaced by ActivateDuration2, due to inefficient bucketing scheme. + + brianderson@chromium.org + + How long it takes for the compositor to simply activate the pending tree. + Does not include any PrepareTiles or raster time. + + + + + + Replaced by BeginMainFrameIntervalCritical2, due to inefficient bucketing + scheme. + + brianderson@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + + + + + Replaced by BeginMainFrameIntervalNotCritical2, due to inefficient bucketing + scheme. + + brianderson@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is not set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + + + + + Replaced by BeginMainFrameQueueDurationCritical2, due to inefficient + bucketing scheme. + + brianderson@chromium.org + + How long it takes for the main side to start the BeginMainFrame in response + to the compositor's SendBeginMainFrame when the on_critical_path flag is + set. + + + + + + Replaced by SendBeginMainFrameToCommit.BeginMainSentToStarted of + CompositorLatency metrics as of 02/2020. + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes for the main side to start the BeginMainFrame in response + to the compositor's SendBeginMainFrame when the on_critical_path flag is + set. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by BeginMainFrameQueueDurationNotCritical2, due to inefficient + bucketing scheme. + + brianderson@chromium.org + + How long it takes for the main side to start the BeginMainFrame in response + to the compositor's SendBeginMainFrame when the on_critical_path flag is not + set. + + + + + + Replaced by BeginMainFrameStartToCommitDuration2, due to inefficient + bucketing scheme. + + brianderson@chromium.org + + The time from when the main side actually starts the BeginMainFrame to when + the commit completes on the impl side. + + + + + + Replaced by SendBeginMainFrameToCommit of CompositorLatency metrics as of + 02/2020. + + vmiura@chromium.org + sadrul@chromium.org + + The time from when the main side actually starts the BeginMainFrame to when + the commit completes on the impl side. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by BeginMainFrameQueueDurationCritical, + BeginMainFrameQueueDurationNotCritical, and + BeginMainFrameStartToCommitDuration. + + brianderson@chromium.org + + How long it takes for the blink main thread to respond to the compositor's + SendBeginMainFrame. + + + + + + Removed in 08/2018, M69. Since there is no impl thread on Browser side, + there is no activation state for Browser. + + brianderson@chromium.org + + How long it takes for the compositor to simply activate the pending tree. + Does not include any PrepareTiles or raster time. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 06/2018, M69, due to too much noise in the collected data. + + brianderson@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + + Removed in 07/2018, M69. All begin frames are in critical path for browser, + no data is reported. + + brianderson@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is not set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69. All begin frames are in critical path for browser, + no data is reported. + + brianderson@chromium.org + + How long it takes for the main side to start the BeginMainFrame in response + to the compositor's SendBeginMainFrame when the on_critical_path flag is not + set. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by BeginMainFrameStartToCommitDuration. This was recorded as a + result of a typo in the code that didn't include "Duration". + + brianderson@chromium.org + + The time from when the main side actually starts the BeginMainFrame to when + the commit completes on the impl side. + + + + + + Replaced by BeginMainFrameStartToCommitDuration2. This was recorded as a + result of a typo in the code that didn't include "Duration". + + brianderson@chromium.org + + The time from when the main side actually starts the BeginMainFrame to when + the commit completes on the impl side. + + + + + + Removed in 06/2018, M69, due to too much noise in the collected data. + + brianderson@chromium.org + + The time delta between the *draw* times of back-to-back BeginMainFrames that + result in a commit. + + The interval is only recorded when the BeginMainFrames are running and + committing continuously, where continuously means when another + BeginMainFrame is requested by the next BeginImplFrame after activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + + Removed in 06/2018, M69, due to too much noise in the collected data. + + brianderson@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + + Removed in 07/2018, M69, due to too much noise in the data. + + paint-dev@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap, when there is at least + one composited animation. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69, due to too much noise in the data. + + paint-dev@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames of new + active trees only, regardless of whether or not they result in a swap, when + there is at least one main thread animation. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 08/2018, M69, since there is no impl thread in Browser side, this + metric does not record any meaningful data. + + brianderson@chromium.org + + Recorded every time the compositor draws with a new active tree. A value of + 0 indicates the main-side started and finished within the same frame + interval as the impl-side. Positive values correspond to how old any + main-side updates are compared to the impl-side updates. If there are no + mid-frame updates, this metric is a good proxy for how well the main and + impl threads are synchronized. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69. Since there is no pending tree in Browser, no data + is ever reported. + + ericrk@chromium.org + + Time between creating a pending tree and activating that tree. This differs + from Scheduling.ActivateDuration in that it includes time taken to raster + the pending tree, not just the time to activate it. + + The interval is recorded each time a pending tree is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69. Since there is no pending tree in Browser, no data + is ever reported. + + khushalsagar@chromium.org + + Time between starting raster work on the pending tree and when it is ready + to activate. Unlike PendingTreeDuration which - includes the time to commit + to this tree, the raster duration and the time for which the pending tree + waits before it can be activated - this only measures the time taken to + rasterize tiles required for activation. + + The interval is recorded each time we are notifed that a pending tree is + ready for activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69. No data reported because there is no pending tree + on impl thread for browser side. + + brianderson@chromium.org + + How long does the pending tree wait after it is ready to be activated and + before it is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. Impl side invalidation initiated pending tree + + + + + + Replaced by EndCommitToActivation of CompositorLatency metrics as of + 08/2020. + + vmiura@chromium.org + sadrul@chromium.org + + How long does the pending tree wait after it is ready to be activated and + before it is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. Commit initiated pending tree. + + + + + + Replaced by CommitInterval2, due to inefficient bucketing scheme. + + brianderson@chromium.org + + The time delta between the *draw* times of back-to-back BeginMainFrames that + result in a commit. + + The interval is only recorded when the BeginMainFrames are running and + committing continuously, where continuously means when another + BeginMainFrame is requested by the next BeginImplFrame after activation. + + + + + + Replaced by CommitToReadyToActivateDuration2, due to inefficient bucketing + scheme. + + brianderson@chromium.org + + How long it takes for the compositor to rasterize pending tree content after + a commit before it is ready for activation. + + + + + + Replaced by DrawDuration2, due to inefficient bucketing scheme. + + brianderson@chromium.org + How long it takes the compositor to draw a frame. + + + + + Replaced by DrawInterval2, due to inefficient bucketing scheme. + + brianderson@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap. + + The interval is only recorded when every BeginImplFrame wants to draw. + + + + + + Removed 05/2018 because the experiment described in Issue 754471 is + completed. + + paint-dev@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames of new + active trees only, regardless of whether or not they result in a swap, when + there is at least one main thread animation that could be composited but + not, due to running experiment. + + The interval is only recorded when every BeginImplFrame wants to draw. + + + + + + Removed 03/28/2018 + + khushalsagar@chromium.org + + Duration for updating animated images and invalidating layers for images + invalidated on the sync tree in the compositor. This interval is recorded + each time the sync tree is updated after a commit or an impl-side + invalidation. + + + + + + Replaced by MainAndImplFrameTimeDelta2, due to inefficient bucketing scheme. + + brianderson@chromium.org + + Recorded every time the compositor draws with a new active tree. A value of + 0 indicates the main-side started and finished within the same frame + interval as the impl-side. Positive values correspond to how old any + main-side updates are compared to the impl-side updates. If there are no + mid-frame updates, this metric is a good proxy for how well the main and + impl threads are synchronized. + + + + + + Replaced by PrepareTIlesDuration2, due to inefficient bucketing scheme. + + brianderson@chromium.org + + How long it takes the compositor to PreapreTiles, which determines what + rasterization work to do. + + + + + + Replaced by ReadyToActivateToActivationDuration2, due to inefficient + bucketing scheme. + + brianderson@chromium.org + + How long does the pending tree wait after it is ready to be activated and + before it is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by Activation stage of CompositorLatency metrics as of 08/2020. + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes for the compositor to simply activate the pending tree. + Does not include any PrepareTiles or raster time. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + This is no longer usefull and would not be replaced, as of 08/2020. + + vmiura@chromium.org + sadrul@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + + This is no longer usefull and would not be replaced. as of 02/2020 + + vmiura@chromium.org + sadrul@chromium.org + + This is the time delta between back-to-back BeginMainFrames completions on + the compositor side when the on_critical_path flag is not set, regardless of + whether they abort (have no updates) or commit (have updates). + + The interval is only recorded when the BeginMainFrames are running + continuously; sepcifically when another BeginMainFrame is requested by the + next BeginImplFrame after a) an abort or b) activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + This is no longer usefull and would not be replaced. as of 02/2020 + + vmiura@chromium.org + sadrul@chromium.org + + The time delta between the *draw* times of back-to-back BeginMainFrames that + result in a commit. + + The interval is only recorded when the BeginMainFrames are running and + committing continuously, where continuously means when another + BeginMainFrame is requested by the next BeginImplFrame after activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + flackr@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap, when there is at least + one composited animation. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + flackr@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames of new + active trees only, regardless of whether or not they result in a swap, when + there is at least one main thread animation. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + This is no longer usefull and would not be replaced. as of 02/2020 + + vmiura@chromium.org + sadrul@chromium.org + + Recorded every time the compositor draws with a new active tree. A value of + 0 indicates the main-side started and finished within the same frame + interval as the impl-side. Positive values correspond to how old any + main-side updates are compared to the impl-side updates. If there are no + mid-frame updates, this metric is a good proxy for how well the main and + impl threads are synchronized. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + This duration is reported in EndCommitToActivation and Activation of + CompositorLatency metrics, and is removeded as of 03/2020. + + ericrk@chromium.org + + Time between creating a pending tree and activating that tree. This differs + from Scheduling.ActivateDuration in that it includes time taken to raster + the pending tree, not just the time to activate it. + + The interval is recorded each time a pending tree is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Replaced by EndCommitToActivation of CompositorLatency metrics as of + 08/2020. + + vmiura@chromium.org + sadrul@chromium.org + + How long does the pending tree wait after it is ready to be activated and + before it is activated. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in 07/2018, M69. The swap ack is always received within 8 seconds. + + brianderson@chromium.org + + True if the swap ack was received within approximately 8 seconds of the + swap. Although 8 seconds isn't exactly fast, it is a threshold that + represents a hang or the appearance of a hang. + + + + + + Replaced by SwapToAckLatency2, due to inefficient bucketing scheme. + + brianderson@chromium.org + How long it takes the swap ack to return after a swap. + + + + + Experiment complete, histogram gathering code removed. + + ellyjones@chromium.org + + Whether an SDCH dictionary was advertised over a secure scheme or not. This + histogram is logged inside SdchManager at advertisement time. + + + + + + Removed 2017-9. + + + The number of dictionaries advertised in an HTTP GET transaction that + supports SDCH. Note that only non-zero advertisements are logged. + + + + + + Removed 2017-9. + + + The reason why a blacklist blocking a request from advertising SDCH was + implemented. There is one entry in this histogram per inhibited request. + + + + + + Removed 2017-9. + + + Each sample is the byte count for a dictionary that is loaded by Chrome. A + dictionary is loaded shortly after the first Google query performed in each + session, and allows future SDCH transactions to be encoded/decoded using + that dictionary. + + + + + + Removed 2017-9. + + + The fate, both on input and output, of dictionary requests. There is + intended to be two entries in this histogram for each Get-Dictionary seen + (except failed requests are not currently tracked). + + + + + + Removed 2017-9. + + + The number of times a dictionary has been successfully used for decoding, + recorded at the time it is evicted from the manager. + + + + + + Replaced by Sdch3.Experiment3_Holdback. + + + Duration in time from when a request was made, until all bytes were + received. During the running of an SDCH latency experiment, these packets + were part of an SDCH encoded transmission made after the link had proven it + was capable of handling SDCH compression. + + + + + + Replaced by Sdch3.Experiment3_Holdback. + + + Duration in time from when a request was made, until all bytes were + received. During the running of an SDCH latency experiment, these packets + were part of a holdback, which precluded SDCH despite the fact that the link + had proven it was capable of handling SDCH compression. + + + + + + Removed 2017-9. + + + Duration in time from the first byte of a request was received, until all + bytes were received. During the running of an SDCH latency experiment, these + packets were part of an SDCH encoded transmission made after the link had + proven it was capable of handling SDCH compression. + + + + + + Removed 2017-9. + + + Duration in time from the first byte of a request was received, until all + bytes were received. During the running of an SDCH latency experiment, these + packets were part of a holdback, which precluded SDCH despite the fact that + the link had proven it was capable of handling SDCH compression. + + + + + + Replaced by Sdch3.Experiment2_Decode. + + + Duration in time from when a request was made, until all bytes were + received. During the running of an SDCH latency experiment, these packets + were part of an SDCH encoded transmission made after the link had proven it + was capable of handling SDCH compression. + + + + + + Replaced by Sdch3.Experiment2_Holdback. + + + Duration in time from when a request was made, until all bytes were + received. During the running of an SDCH latency experiment, these packets + were part of a holdback, which precluded SDCH despite the fact that the link + had proven it was capable of handling SDCH compression. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + During the running of an SDCH latency experiment, these packets were part of + a holdback, which precluded SDCH despite the fact that the link had proven + it was capable of handling SDCH compression. + + + + + + Removed 2016-11. + + + The duration between receipt of the 1st holdback (non-SDCH encoded) packet + and receipt of the last packet. Only groups that are part of the holdback + (i.e., could have been sdch encoded) are sampled. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + During the running of an SDCH latency experiment, these packets were part of + a holdback, which precluded SDCH despite the fact that the link had proven + it was capable of handling SDCH compression. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + During the running of an SDCH latency experiment, these packets were part of + a holdback, which precluded SDCH despite the fact that the link had proven + it was capable of handling SDCH compression. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + During the running of an SDCH latency experiment, these packets were part of + a holdback, which precluded SDCH despite the fact that the link had proven + it was capable of handling SDCH compression. + + + + + + Removed 2016-11. + + + If SDCH decoding was disabled client side, this records how many URLs were + processed by the SDCH filter before disabling this feature. The most common + number is 1, which happens when there is one home-page tab that contains + SDCH encoded data, for which there is no dictionary loaded into the Chrome + process (yet), since Chrome was just restarted. Large values in this + histogram are indicative of flaky decompression, that works for a while, and + then is disabled. Values of 2 or 3 may appear if a user has more than one + home page with a query, and restarts there browser. + + + + + + Removed 2017-9. + + + The amount of time between creation/load of an SDCH dictionary and its first + use. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 1st SDCH encoded packet and receipt of the 2nd packet, for + processing by the SDCH filter. Packet count boundaries are calculated each + time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + The duration between receipt of the 1st SDCH encoded packet and receipt of + the last packet, for processing by the SDCH filter. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 2nd SDCH encoded packet and receipt of the 3rd packet, for + processing by the SDCH filter. Packet count boundaries are calculated each + time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 3rd SDCH encoded packet and receipt of the 4th packet, for + processing by the SDCH filter. Packet count boundaries are calculated each + time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 4th SDCH encoded packet and receipt of the 5th packet, for + processing by the SDCH filter. Packet count boundaries are calculated each + time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + (discontinued 7/29/2009, and replaced by + Sdch3.Network_Decode_Bytes_Processed_b) The number of bytes processed + (received over the net or from cache) by the SDCH filter chain. + + + + + + Removed 2017-9. + + + The number of bytes processed (received over the net or from cache) by the + SDCH filter chain. + + + + + + Removed 2016-11. + + + The number of bytes emitted after decoding by the SDCH filter. + + + + + + Removed 2016-11. + + + The duration between putting the first byte of a request (such as a GET) on + the wire, until the last by of compressed SDCH encoded content is received + (with durations over 10 minutes discarded). During a planned latency + experiment, some clients will receive encoded SDCH data, and other will + received mere gzip'ed data (that passes through the SDCH filter unchanged). + + + + + + Removed 2016-11. + + + An approximation to the total number of SDCH encoded packets received for + processing by the SDCH filter. Packet count boundaries are calculated each + time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + The ratio of the number of bytes read from the network (or cache) and fed to + the filter chain (usually the gunzip filter) vs. the number of bytes emitted + by the SDCH filter to be rendered. This is commonly described as the SDCH + compression ratio. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + The duration between receipt of the 1st **NON**-SDCH encoded packet to + receipt of the last packet, for processing by the SDCH filter. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + Sampling only transmissions with 5 or more packets, the duration between + receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet, + for processing by the SDCH filter. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + + The duration between putting the first byte of a request (such as a GET) on + the wire, until the last by gzip compressed content is received and + passed-through unchanged by the SDCH filter (with durations over 10 minutes + discarded). During a planned latency experiment, some clients will receive + encoded SDCH data, and other will received mere gzip'ed data (that passes + through the SDCH filter unchanged). + + + + + + Removed 2016-11. + + + The total number of **NON**-SDCH encoded packets received for processing by + the SDCH filter in one URL fetch. Packet count boundaries are calculated + each time a read from the filter is called, assuming 1430 bytes of data per + packet since the last boundary calculation. This *tends* to properly count + small packets, but can err if small packets come at roughly the same time. + + + + + + Removed 2016-11. + + ellyjones@chromium.org + + The absolute difference in bytes between the amount of data entering the + SDCH filter and the amount of data exiting the SDCH filter. + + + + + + Removed 2017-9. + + ellyjones@chromium.org + + Absolute sizes, in bytes, of SDCH dictionaries fetched over the network. + These are logged in SdchOwner when dictionary fetches complete. + + + + + + Removed 2016-11. + + + If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF + decoder still has internally buffered data that has never been read, this + histogram reports the number of bytes that were received over the net (or + from the cache) and fed to the start of the filter chain (usually to the + gunzip filter). + + + + + + Removed 2016-11. + + + If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF + decoder still has internally buffered data that has never been read, this + histogram reports the number of bytes that were received over the net (or + from the cache) and fed to VCDIFF decoder (usually after gunzipping). + + + + + + Removed 2016-11. + + + If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF + decoder still has internally buffered data that has never been read, this + histogram reports the number of bytes that were output by the VCDIFF decoder + (and sent toward the renderer). + + + + + + Removed 2017-9. + + + Tracks failures that occur when reading in or writing out persisted + dictionary information. + + + + + + Removed 2014-11. Sdch3.ProblemCodes_5 used instead. + + Each sample is the report of a distinct problem code. + + + + + Removed 2014-11. Sdch3.ProblemCodes_5 used instead. + + Each sample is the report of a distinct problem code. + + + + + Removed 2017-9. + + Each sample is the report of a distinct problem code. + + + + + Removed 2017-9. + + + Attempted SDCH decoding can fail at the Read() filter processing stage. In + some of those cases, the request is corrupted enough that it must be either + retried or failed completely. This histogram records the details of why the + request was considered corrupted, for results returned from the cache. + + + + + + Removed 2017-9. + + + Attempted SDCH decoding can fail at the Read() filter processing stage. In + some of those cases, the request is corrupted enough that it must be either + retried or failed completely. This histogram records the details of why the + request was considered corrupted for results returned from the network. + + + + + + Removed 2017-9. + + ellyjones@chromium.org + + Measures the time-weighted memory use of SDCH dictionaries, in bytes. The + numerator is bytes of dictionary times seconds that dictionary was in + memory, and the denominator is seconds that the Chrome process lives. + + + + + + Removed 2016-11. + + + If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is + still buffering output of the VCDIFF decoder that has never been read, this + histogram reports the number of bytes that were in that buffer. + + + + + + Removed 2016-11. + + + If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is + still buffering output of the VCDIFF decoder that has never been read, this + histogram reports the number of bytes that were received over the net (or + from the cache) and fed to the start of the filter chain (usually to the + gunzip filter). + + + + + + Removed 2016-11. + + + If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is + still buffering output of the VCDIFF decoder that has never been read, this + histogram reports the number of bytes that were received over the net (or + from the cache) and fed to VCDIFF decoder (usually after gunzipping). + + + + + + Removed 2016-11. + + + If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is + still buffering output of the VCDIFF decoder that has never been read, this + histogram reports the number of bytes that were output by the VCDIFF decoder + (and sent toward the renderer). + + + + + + Use Sdch3.UsageInterval2 instead. + + + The amount of time from the last time an SDCH dictionary was used. For the + first use of a dictionary, the maximum time is used. + + + + + + Removed 2017-9. + + + The amount of time from the last time an SDCH dictionary was used. Not + recorded on first dictionary use. First use is recorded as + Sdch3.FirstUseInterval. + + + + + + Replaced by Search.AddSearchProvider2, which is also now obsolete. + + estade@chromium.org + + Measures how much the user modifies their search engines, whether through + window.external.AddSearchProvider or chrome://settings. + + + + + + AddSearchProvider was removed 05/2016. + + estade@chromium.org + + Measures usage of window.external.AddSearchProvider and user interaction + with the resulting confirmation dialog (if any). Only works on Views + platforms (Win, Linux, CrOS). + + + + + + Removed 05/2017 because it's no longer ever used. + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen during a contextual search where the + selected text consisted of all capital letters. Only logged when contextual + search is triggered due to a tap. Implemented for Android. + + + + + + Discontinued on 5/2017 due to experiment being completed. + + donnd@chromium.org + pedrosimonetti@chromium.org + twellington@chromium.org + + The details (blacklist reason and whether the results were seen) of every + search term issued by a tap gesture. Implemented for Android. + + + + + + Discontinued on 2/2017 Due to data being buggy and not useful. + + donnd@chromium.org + twellington@chromium.org + + The time from opening the panel until the SERP is fully loaded. Applies only + to non-prefetched requests. Implemented for Android. + + + + + + Discontinued on 2/2017 Due to data being buggy and not useful. + + donnd@chromium.org + twellington@chromium.org + + The time from opening the panel until the SERP is fully loaded. Applies only + to prefetched requests. Implemented for Android. + + + + + + Contextual Search icon sprite removed 04/2017. + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen, whether the search provider icon sprite + was animated when the panel first appeared, and the triggering gesture. If + animation is disabled due to a field trial, we still log + "animated" if the animation would have run otherwise. + + + + + + Removed because the feature no longer exists. + + donnd@chromium.org + pedrosimonetti@chromium.org + twellington@chromium.org + + The number of times the Peek Promo was seen. This histogram will be emitted + when the Panel closes. The panel is always visible when the Peek Promo is + shown, so this histogram will always be emitted after a Promo is shown + (except in the case of a crash). This histogram does not care whether the + Panel was opened. + + + + + + Removed because the feature no longer exists. + + donnd@chromium.org + pedrosimonetti@chromium.org + twellington@chromium.org + + The number of times the Peek Promo was seen until the Panel was opened. This + histogram will be emitted when the Panel closes, if the Panel was opened + with the Peek Promo visible. If the Panel is not opened, nothing will be + emitted. + + + + + + Removed because the feature no longer exists. + + donnd@chromium.org + pedrosimonetti@chromium.org + twellington@chromium.org + + The outcome of the Contextual Search Peek Promo for those who have seen the + promo and for those who would have seen the promo if it was enabled, so we + can compare the effect of the promo on users opening the Panel. This + histogram will be emitted when the Panel closes, if the conditions to + display the Peek Promo are met, regardless of whether the Peek Promo was + actually visible (the Promo is controlled by Finch) and regardless of + whether the Panel was opened. + + + + + + Discontinued on 2/2017 Due to data not being useful. + + donnd@chromium.org + twellington@chromium.org + + A summary histogram for prefetch timings, indicating fully preloaded, etc. + Implemented for Android. + + + + + + Removed 02/2017. + + donnd@chromium.org + twellington@chromium.org + + The duration since a recent scroll when the results were not seen. Recorded + when the UX is hidden. Implemented for Android. + + + + + + Removed 02/2017. + + donnd@chromium.org + twellington@chromium.org + + The duration since a recent scroll when the results were seen. Recorded when + the UX is hidden. Implemented for Android. + + + + + + Removed 05/2017 because it's no longer ever used. + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen (Contextual Search panel was opened) when + the selection was part of a URL, broken down by original triggering gesture. + Includes both users that have enabled Contextual Search and users that are + undecided (have neither enabled or disabled the feature). Implemented for + Android. + + + + + + Removed 11/2017 because the data is no longer valuable. + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap during suppression when Tap Suppression + is enabled. Recorded when the UX is hidden. Implemented for Android. + + + + + + Removed 02/2017 because the data is no longer valuable. + + donnd@chromium.org + twellington@chromium.org + + Whether the SERP was fully loaded when an opened panel was closed. + + + + + + Removed in M75 because the data is no longer needed. + + donnd@chromium.org + twellington@chromium.org + + Emitted when a translate one-box should be forced, to indicate if it + actually was forced or simply would have been forced if not disabled by a + flag in the variations_service. + + + + + + Removed 05/2017 because the data is no longer needed. + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen during a contextual search where the + selected text started with a capital letter but was not all capital letters. + Only logged when contextual search is triggered due to a tap. Implemented + for Android. + + + + + + Removed 11/2017 because the data is no longer valuable. + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap before suppression when Tap Suppression + is enabled. Recorded when the UX is hidden. Implemented for Android. + + + + + + Made obsolete around Chrome 32. Use Search.DefaultSearchProviderType + instead. + + Please list the metric's owners. Add more owner tags as needed. + + The id of the default search engine that is loaded after Chrome startup. See + src/chrome/browser/search_engines/prepopulate_engines.json for more info. + + + + + + Removed 05/2016 because desktop searches are no longer opened in the default + browser. + + fdoray@chromium.org + + The action performed by the user to close the infobar explaining that a + desktop search has been redirected to the default search engine. + + + + + + Removed 05/2016 because desktop searches are no longer opened in the default + browser. + + fdoray@chromium.org + + The action performed when a desktop search URL is passed to the browser + through the command line. + + + + + + Removed 06/2017, no longer recorded. + + lizeb@chromium.org + + On Android, when Chrome connects to a bound service exposed by GSA, the + memory footprint of the GSA process in KB, as measured by PSS. Reported at + most once per Chrome startup. + + + + + + Removed after migrator is deleted in 12/2016. + + caitkp@chromium.org + + The number of times that a user-selected DSE was migrated from separate + String/List/..Value preferences to the new single DictionaryValue used in + M36. + + + + + + Removed 2018-12 after HTTPBad was rolled out for all HTTP pages. This metric + was recorded only after sensitive input events, which were removed. + + estark@chromium.org + + Records the time from when a page was put into a warning state because of a + sensitive input on an HTTP page until a navigation starts. Recorded at most + once per main-frame navigation. The Finch trial 'mark-non-secure-as' + controls whether the user sees an omnibox warning for this state, or just a + console warning. + + + + + + Removed on 2016-11-10 because this is replaced by two separate metrics: + Security.HTTPBad.UserWarnedAboutSensitiveInput.CreditCard and + Security.HTTPBad.UserWarnedAboutSensitiveInput.Password. + + elawrence@chromium.org + estark@chromium.org + + Whether a "Not Secure" warning was shown in the omnibox because a + security-sensitive form field was rendered in a non-secure context. Logged + at most once per main-frame navigation. + + + + + + Removed 2018-12 after HTTPBad was rolled out for all HTTP pages, and + discrete credit card / password tracking was removed. + + elawrence@chromium.org + estark@chromium.org + + Whether a "Not Secure" warning was shown in the omnibox because a + credit card form field was rendered in a non-secure context. Logged at most + once per main-frame navigation. + + + + + + Removed 2018-12 after HTTPBad was rolled out for all HTTP pages, and + discrete credit card / password tracking was removed. + + elawrence@chromium.org + estark@chromium.org + + Whether a "Not Secure" warning was shown in the omnibox because a + password form field was rendered in a non-secure context. Logged at most + once per main-frame navigation. + + + + + + Removed 2018-12 after HTTPBad was rolled out for all HTTP pages. This metric + was recorded only after sensitive input events, which were removed. + + estark@chromium.org + + Records the time delta between when a page was put into a warning state + because of a sensitive input on an HTTP page and when the WebContents was + destroyed. Recorded at most once per main-frame navigation, and it is not + recorded if the user starts a navigation before the WebContents is + destroyed. The Finch trial 'mark-non-secure-as' controls whether the user + sees an omnibox warning for this state, or just a console warning. + + + + + + Removed 2018-01-31, split into ValidEV and ValidNonEV. + + estark@chromium.org + + Tracks Page Info bubble actions that take place on a valid HTTPS URL with no + security issues (e.g. no mixed content). + + + + + + Removed March 2019 in favor of Security.TimeOnPage2. + + cthomp@chromium.org + + Records the time spent on the page (the time that the page was in the + foreground from the start of the navigation to the page visit completing due + to a new navigation or the tab being closed). This aggregates all foreground + time over the entire visit (multiple times in the foreground are added + together). For pages that were never backgrounded, this histogram + (accidentally) collects 0 instead of the actual foreground time. + + + + + + Removed April 2020 as it is no longer used. + + mkwst@chromium.org + + Records the number of origins which will be treated as secure based on their + presence in the '--unsafely-treat-insecure-origin-as-secure' command-line + flag. + + + + + + Removed 05/2020. + + jeffreycohen@chromium.org + sebsg@chromium.org + tgupta@chromium.org + + Record how many valid devices are shown when user trigger to see the device + list. + + + + + + Removed 05/2020. + + sebsg@chromium.org + jeffreycohen@chromium.org + tgupta@chromium.org + + The use of desktop notification for SendTabToSelf. + + These notifications are tied to a sync type so there is a distinction + between user initiated actions (Opened, Dismissed) and actions that are + initiated by changes to the sync model (Shown, DismissedRemotely). + + + + + + Removed 05/2020. + + jeffreycohen@chromium.org + sebsg@chromium.org + + The result of the add entry method when a tab is shared via SendTabToSelf + + + + + + Removed 05/2020. + + jeffreycohen@chromium.org + sebsg@chromium.org + + The result of the ApplySyncChanges method when a tab is shared via + SendTabToSelf + + + + + + Removed 05/2020. + + tgupta@chromium.org + + Whether or not the SendTabToSelf model was loaded in time to perform the + necessary update. + + + + + + Removed 05/2020. + + jeffreycohen@chromium.org + tgupta@chromium.org + + The number of entry that are sent to the SendTabToSelf NotificationHandler. + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from activating a sensor in the ISensor API, used in + the implementation of W3C sensors on Windows. This includes both errors and + successes (S_OK). + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from starting a sensor in the ISensor API, used in the + implementation of W3C sensors on Windows. This includes both errors and + successes (S_OK). + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from stopping a sensor in the ISensor API, used in the + implementation of W3C sensors on Windows. This includes both errors and + successes (S_OK). + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from activating a sensor in the + Windows.Devices.Sensors WinRT API, used in the implementation of W3C sensors + on Windows. This includes both errors and successes (S_OK). + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from starting a sensor in the Windows.Devices.Sensors + WinRT API, used in the implementation of W3C sensors on Windows. This + includes both errors and successes (S_OK). + + + + + + Removed in M82 after the WinRT backend experiment concluded. + + reillyg@chromium.org + wensh@microsoft.com + + The HRESULTs returned from stopping a sensor in the Windows.Devices.Sensors + WinRT API, used in the implementation of W3C sensors on Windows. This + includes both errors and successes (S_OK). + + + + + + Removed 02/2018. SequencedWorkerPool has been removed. + + gab@chromium.org + + How long it takes to wait for tasks that block shutdown to complete. + + + + + + Histogram wasn't even reported anymore when ownership was taken in 11/2015. + + gab@chromium.org + + How many pending tasks there are on each request for work from a worker + thread. + + + + + + Histogram wasn't even reported anymore when ownership was taken in 11/2015. + + gab@chromium.org + How many tasks we skip over to find the next runnable task. + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + horo@chromium.org + + The time taken for the browser to find and possibly start an active worker + to dispatch a FetchEvent for a main frame resource request. BEWARE: This + metric includes the time taken for redirects. It starts when the URLRequest + is created, and ends when the worker is ready. For context, a FetchEvent can + only be dispatched to an ACTIVATED worker that is running (it has been + successfully started). The measurements starts when the browser process + receives the request. The browser then finds the worker appropriate for this + request (if there is none, this metric is not recorded). If that worker is + already started, the browser process can send the request to it, so the + measurement ends quickly. Otherwise the browser process has to start the + worker and the measurement ends when the worker is successfully started (we + do not include in the time it takes for the worker to become ACTIVATED). The + metric is not recorded in the following situations: 1) The worker was in + state INSTALLED or ACTIVATING, and the browser had to wait for it to become + ACTIVATED. This is to avoid including the time to execute the activate event + handlers in the worker's script. 2) The worker was started for the fetch AND + DevTools was attached during startup. This is intended to avoid including + the time for debugging. 3) The request is for New Tab Page. This is because + it tends to dominate the stats and makes the results largely skewed. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + Removed June 2019. + + falken@chromium.org + + The type of preparation needed for the browser to find and possibly start an + active worker to dispatch a FetchEvent for a main frame resource request. + See details at ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. + The suffixed histograms for .Time record the time required for each type. + + + + + + Removed 2015-05 in favor of ServiceWorker.ActivateEvent.Time. + + shimazu@chromium.org + + Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for + waitUntil() promise to settle. + + + + + + Removed 08/2018, and renamed to BackgroundFetchSuccessEvent. See + ServiceWorker.BackgroundFetchSuccessEvent.Time instead. + + peter@chromium.org + + The time taken between dispatching a BackgroundFetchedEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + The result of ServiceWorkerContextRequestHandler handling a request for a + service worker script. The histogram is suffixed to distinguish new vs + installed workers and main vs imported scripts. + + Note that since M64, this no longer includes most script loads because those + are handled by ServiceWorkerInstalledScriptsManager, which doesn't record + this histogram. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + Removed because the migrator was removed as of 12/2015. + + nhiroki@chromium.org + + Records result of ServiceWorkerDiskCacheMigrator::Start that migrates + resources in BlockFile backend to Simple backend. + + + + + + Removed because the migrator was removed as of 12/2015. + + nhiroki@chromium.org + + Execution time of ServiceWorkerDiskCache migration from BlockFile to Simple. + + + + + + Removed because the migrator was removed as of 12/2015. + + nhiroki@chromium.org + + The counts of resources migrated by ServiceWorkerDiskCacheMigrator. This + includes the main script and imported scripts. + + + + + + Removed Oct 2018 (M72) + + horo@chromium.org + + The time taken between sending an event IPC from the browser process to a + Service Worker and executing the event handler in the Service Worker. + + For subresource fetch events (_FETCH_SUB_RESOURCE suffix) When NetS13nSW + (https://crbug.com/715640) is enabled, this is the time between sending a + DispatchFetchEvent message from the main thread and executing the event + handler in the Service Worker. + + + + + + Removed July 2018 (M69) + + kinuko@chromium.org + + Records the proportion of (non foreign) fetch events that are handled + compared to the number of events that are fired for a ServiceWorker. + Recorded each time the ServiceWorker is stopped when at least one event was + fired. + + + + + + Removed July 2018 (M69) + + mek@chromium.org + + Records the proportion of foreign fetch events that are handled compared to + the number of events that are fired for a ServiceWorker. Recorded each time + the ServiceWorker is stopped when at least one event was fired. + + + + + + Removed on 2015-07-13; please use ServiceWorker.FetchEvent.HasResponse.Time + or ServiceWorker.FetchEvent.Fallback.Time. + + shimazu@chromium.org + + Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for + the respondWith() promise to settle. + + + + + + Removed 2015-05 in favor of ServiceWorker.FetchEvent.Time. + + shimazu@chromium.org + + Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for + the respondWith() promise to settle. + + + + + + Removed April 2018. + + mek@chromium.org + + The number of origins a particular service worker with foreign fetch + registrations will intercept fetches from. A value of zero indicates that + the foreign fetch service worker intercepts requests from any origin. + Recorded at the end of a successful install event, if the service worker + registered for foreign fetch. A service worker that registers for foreign + fetch must always intercept fetches from at least one origin or intercept + fetches from all origins. + + + + + + Removed April 2018. + + mek@chromium.org + + The number of foreign fetch scopes a particular service worker registered + for. Recorded at the end of every successful install event. A value of zero + indicates that the service worker did not register for foreign fetch. + + + + + + Removed 2018 + + mek@chromium.org + + The time taken between dispatching a ForeignFetchEvent to a Service Worker + and receiving a fallback-to-network reply. Includes the time for the + waitUntil() promise to settle, if any. + + + + + + Removed 2018 + + mek@chromium.org + + The time taken between dispatching a ForeignFetchEvent to a Service Worker + and receiving a response. Includes the time for the respondWith() promise to + settle. + + + + + + Removed 2018 + + shimazu@chromium.org + + The time taken between dispatching a ForeignFetchEvent to a Service Worker + and finishing the ForeignFetch. Includes the time for the waitUntil() + promise to settle. If there is no waitUntil promise, this will be almost the + same with HasResponse.Time or Fallback.Time. + + + + + + Removed 2015-05 in favor of ServiceWorker.InstallEvent.Time. + + shimazu@chromium.org + + Execution time of ServiceWorkerGlobalScope.oninstall. Includes the time for + the waitUntil() promise to settle. + + + + + + Removed 2018-11 in favor of + ServiceWorker.LoadTiming.MainFrame.MainResource.ForwardServiceWorkerToWorkerReady2. + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) a resource loading request is routed to service + worker path, to (b) a service worker is ready to handle the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + + Removed 2018-11 in favor of + ServiceWorker.LoadTiming.MainFrame.MainResource.ResponseReceivedToCompleted2. + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) response headers from service worker are received, + to (b) reading response body is completed. Recorded when a fetch event + handler handled the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + + Removed 2018-12 in favor of + ServiceWorker.LoadTiming.Subresource.ResponseReceivedToCompleted2. + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) response headers from service worker are received, + to (b) reading response body is completed. Only recorded when a fetch event + handler handled the request. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + + Removed 2018-01 in favor of PageLoad.Clients.ServiceWorker.PageTransition. + + horo@chromium.org + + The transition type for main frame page loads controlled by a service + worker. + + + + + + Removed 2018-01. + + horo@chromium.org + + Total length of the server redirects during main frame page loads controlled + by a service worker. + + + + + + Removed 2018-11, see https://crbug.com/902100 + + falken@chromium.org + chrome-worker@google.com + + Describes whether a main resource request (i.e., a request for a main frame, + subframe, or shared worker) was routed to service worker or network and why. + The purpose is to debug why ServicifiedServiceWorker has a lower count of + ServiceWorker.MainResource.FetchEvent.Status than the control: + https://crbug.com/866335. + + Recorded for every main resource request that is seen by + ServiceWorkerControlleeRequestHandler (usually means all http(s) requests). + If redirects occur, it is recorded for each redirect. + + + + + + Removed 2016-04 in favor of ServiceWorker.ExtendableMessageEvent.Time. + + shimazu@chromium.org + Execution time of ServiceWorkerGlobalScope.onmessage. + + + + + Removed 2015-05 in favor of ServiceWorker.MessageEvent.Time. + + shimazu@chromium.org + Execution time of ServiceWorkerGlobalScope.onmessage. + + + + + This experiment was turned down, see https://crbug.com/616502. + + horo@chromium.org + + The precision of the speculative launch of Service Workers for navigation + hints. Recorded when the worker is stopped. If there was no main/sub frame + fetch event fired on the worker, this value is false. This means that the + speculative launch wasn't helpful. + + + + + + Removed June 2017 in favor of ServiceWorker.NavPreload.ConcurrentTime, see + https://crbug.com/728035. + + falken@chromium.org + + The duration of time when both (1) a service worker is being found and + possibly started up, (2) the navigation preload request is in-flight. The + measurement ends once either the worker is prepared, or the navigation + preload response is received (OnReceiveResponse() is called). This is a + rough estimate of the performance win of using navigation preload, ignoring + concurrency overhead. This histogram is recorded when a navigation preload + response is succesfully forwarded to the service worker's fetch event, with + the same restrictions as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + additionally recorded to the appropriate suffixed histograms. + + + + + + Removed June 2017 in favor of ServiceWorker.NavPreload.FinishedFirst, see + https://crbug.com/728035. + + falken@chromium.org + + Whether the navigation preload response arrived before the activated and + running service worker was prepared. This histogram is recorded when a + navigation preload response is succesfully forwarded to the service worker's + fetch event, with the same restrictions as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + additionally recorded to the appropriate suffixed histograms. + + + + + + Expired June 2020. + + horo@chromium.org + + The size of Service-Worker-Navigation-Preload header when the navigation + preload request is to be sent. The default value of the header is + "true", so the default size is 4. + + + + + + Removed June 2017. No replacement exists. See https://crbug.com/728035. + + falken@chromium.org + + This is recorded in the case where the activated and running service worker + was prepared before the navigation preload response arrived. It is the + remaining time it took to receive the response after the worker was + prepared. + + This histogram is recorded when a navigation preload response is succesfully + forwarded to the service worker's fetch event (for the case mentioned + above), with the same restrictions as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + additionally recorded to the appropriate suffixed histograms. + + + + + + Removed June 2017 in favor of ServiceWorker.NavPreload.ResponseTime. See + https://crbug.com/728035. + + falken@chromium.org + + The time taken for the navigation preload response to start, i.e., when + OnReceiveResponse() is called. This histogram is recorded when a navigation + preload response is successfully forwarded to the service worker's fetch + event, with the same restrictions as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + additionally recorded to the appropriate suffixed histograms. + + + + + + Removed June 2017 in favor of ServiceWorker.NavPreload.WorkerWaitTime. See + https://crbug.com/728035. + + falken@chromium.org + + This is recorded in the case where the navigation preload response arrived + before the activated and running service worker was prepared. It is the + remaining time it took to prepare the worker after the response arrived. + + This histogram is recorded when a navigation preload response is succesfully + forwarded to the service worker's fetch event (for the case mentioned + above), with the same restrictions as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + additionally recorded to the appropriate suffixed histograms. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + The duration of time when both (1) a service worker is being found and + possibly started up, (2) the navigation preload request is in-flight. The + measurement ends once either the worker is prepared, or the navigation + preload response is received (OnReceiveResponse() is called). This is a + rough estimate of the performance win of using navigation preload, ignoring + concurrency overhead. This histogram is recorded when a navigation preload + response is succesfully forwarded to the service worker's fetch event, with + the same restrictions enumerated 1) through 3) for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + only recorded to the appropriate suffixed histograms. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + Whether the navigation preload response arrived before the activated and + running service worker was prepared. This histogram is recorded when a + navigation preload response is succesfully forwarded to the service worker's + fetch event, with the same restrictions numbered 1) through 3) for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + only recorded to the appropriate suffixed histograms. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + The time taken for the navigation preload response to start, i.e., when + OnReceiveResponse() is called. This histogram is recorded when a navigation + preload response is successfully forwarded to the service worker's fetch + event, with the same restrictions numbered 1) through 3) for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + only recorded to the appropriate suffixed histograms. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + The type of preparation needed for the browser to find and possibly start an + active worker to dispatch a FetchEvent for a main frame resource request, + when navigation preload also occurred. + + This histogram is recorded when a navigation preload response is succesfully + forwarded to the service worker's fetch event (for the case mentioned + above), with the same restrictions numbered 1) through 3) as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + only recorded to the appropriate suffixed histograms. + + This is similar to + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Type_NavigationPreloadEnabled. + The difference is ServiceWorker.NavPreload.WorkerPreparationType gets logged + if the navigation preload successfully occurred, at the same time as the + other ServiceWorker.NavPreload.* metrics so is more safely comparable to + them. We could deprecate the Type_NavigationPreloadEnabled histogram if it + turns out there is no significant difference. + + It will be removed after NetS13nSW ships. https://crbug.com/715640 + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + This is recorded in the case where the navigation preload response arrived + before the activated and running service worker was prepared. It is the + remaining time it took to prepare the worker after the response arrived. + + This histogram is recorded when a navigation preload response is succesfully + forwarded to the service worker's fetch event (for the case mentioned + above), with the same restrictions numbered 1) through 3) as for + ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is + only recorded to the appropriate suffixed histograms. + + + + + + Removed 2015-05 in favor of ServiceWorker.NotificationClickEvent.Time. + + peter@chromium.org + + Execution time of ServiceWorkerGlobalScope.onnotificationclick. + + + + + + Removed 2015-05 in favor of ServiceWorker.PushEvent.Time. + + peter@chromium.org + Execution time of ServiceWorkerGlobalScope.onpush. + + + + + No longer needed as found the cause of stability issue to be number of + registrations rather than size of registrations. Removed in July 2020. + + nidhijaju@google.com + bashi@chromium.org + chrome-worker@google.com + + Number of service worker registrations to be added in + ServiceWorkerRegistry::DidGetAllRegistrations(). + + + + + + No longer needed as found the cause of stability issue to be number of + registrations rather than size of registrations. Removed in July 2020. + + nidhijaju@google.com + bashi@chromium.org + chrome-worker@google.com + + The length of the scope url in the ServiceWorkerRegistrationInfo is measured + for each service worker registration to give a better idea of the data + structure as a whole. This metric is collected in + ServiceWorkerRegistration::GetInfo(). + + + + + + Removed June 2019. + + falken@chromium.org + + The number of Service Worker request timeouts, by request type. + + + + + + Removed June 2018 (M69). This was recorded as 100% success since service + worker script streaming launched in M64, since load failures didn't reach + this UMA. When there is an error reading the script from storage, it's + typically recorded as a start worker failure under + SERVICE_WORKER_ERROR_DISK_CACHE. + + falken@chromium.org + + Whether loading the service worker script succeeded. Only recorded for + installed service workers. Recorded by the browser process when reported + back by the renderer during worker startup. + + + + + + Removed June 2019. + + horo@chromium.org + + The precision of the speculative launch of Service Workers for navigation + hints. Recorded when the worker is stopped. True if a fetch event for a + main/sub frame navigation was fired on the worker before it stopped; + otherwise, false. False means the speculative launch wasn't helpful. + + + + + + Removed June 2019. + + falken@chromium.org + + The result of trying to start a Service Worker that has not yet installed. + See also ServiceWorker.StartWorker.Status for installed workers. + + + + + + Removed from code in July 2019 since ServiceWorkerScriptStreaming + successfully launched. + + shimazu@chromium.org + + The result of sending installed scripts over + ServiceWorkerInstalledScriptsSender. This is recorded after every start + worker attempt that sent the scripts through + ServiceWorkerInstalledScriptsSender. + + + + + + Removed from code in Oct 2015, replaced with ServiceWorker.WorkerStopped. + + falken@chromium.org + + The result of trying to stop a Service Worker. Recorded only for installed + Service Workers that succesfully stopped or were detected as stalling. If a + worker stalled and later stopped, it will be recorded as both STALLED and + STALLED_THEN_STOPPED. + + + + + + Removed because the migrator was removed as of 12/2015. + + nhiroki@chromium.org + + Records the final result of diskcache migration in ServiceWorkerStorage. + ServiceWorker.DiskCacheMigrator.MigrationResult records more detailed status + of migration operations. + + + + + + Removed in M77. + + wanderview@chromium.org + + The time between when the ServiceWorkerSubresourceLoader receives a Response + with a blob body and when the main blob data starts to get read. This will + be triggered for every successful subresource load handled by a + ServiceWorker with ServiceWorker servification enabled. + + + + + + Removed in June 2017. + + falken@chromium.org + + The time taken in the renderer process between the main thread asking the + worker thread to terminate and getting ACK that it terminated. + + + + + + Removed in June 2017. + + falken@chromium.org + + Called at the beginning of each ServiceWorkerVersion::Dispatch*Event + function: the time elapsed since idle. Generally this is the time between + one event ending and one event starting, if the worker remained running in + the interim. + + + + + + Removed 2015-06 in favor of ServiceWorker.EventHandledStatus*. + + kinuko@chromium.org + + Records the ratio of unhandled events to all events that are dispatched to + each ServiceWorker. Recorded when each ServiceWorkerVersion is destructed. + + + + + + Removed 2020-07 because we could confirm byte-for-byte update checking for + imported scripts works. + + shimazu@chromium.org + + Records the result of byte-for-byte update checking. If it's not OK, it + means that script comparison doesn't work well. Recorded only when + ServiceWorkerImportedScriptUpdateCheck is enabled. + + + + + + Removed 2020-07 because we could confirm byte-for-byte update checking for + imported scripts works. + + shimazu@chromium.org + + Records the result of byte-for-byte update checking. Recorded only when + ServiceWorkerImportedScriptUpdateCheck is enabled and + ServiceWorker.UpdateCheck.Result is OK. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + horo@chromium.org + + Records the the mode of request that was fallbacked to the network by the + Service Worker. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + Records the result of a main resource request forwarded to a Service Worker. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + Records the error provided when the renderer returns a response with status + code zero to a main resource request forwarded to a Service Worker (i.e., + ServiceWorker.URLRequestJob.MainResource.Result was + REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO). + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + Records the result of a subresource request forwarded to a Service Worker. + + + + + + No longer recorded since NetS13nSW shipped on Dec 2018. + + falken@chromium.org + + Records the error provided when the renderer returns a response with status + code zero to a subresource request forwarded to a Service Worker (i.e., + ServiceWorker.URLRequestJob.Subresource.Result was + REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO). + + + + + + No longer needed as found the cause of stability issue to be number of + registrations rather than size of registrations. Removed in July 2020. + + nidhijaju@google.com + bashi@chromium.org + chrome-worker@google.com + + Number of clients associated with each service worker version, for better + estimation of the size of ServiceWorkerRegistrationInfo. This metric is + collected in ServiceWorkerVersion::GetInfo(), and clients for all versions + (active, waiting, and installing) are counted for now. + + + + + + No longer needed as found the cause of stability issue to be number of + registrations rather than size of registrations. Removed in July 2020. + + nidhijaju@google.com + bashi@chromium.org + chrome-worker@google.com + + The length of the script url in ServiceWorkerVersionInfo is measured for + each service worker version to give a better idea of the memory size of + ServiceWorkerRegistrationInfo as a whole. This metric is collected in + ServiceWorkerVersion::GetInfo(). + + + + + + This histogram was removed in M77. + + nhiroki@chromium.org + + Records the response type to be added in the Cache by Cache.add()/addAll(). + + + + + + Expired 2020-04. + + wanderview@chromium.org + chrome-owp-storage@google.com + + The network result code produced by disk_cache::Backend::CreateEntry() when + cache_storage is attempting to put a new request/response pair on disk. + + + + + + No longer used. Removed in April 2020. + + cmumford@chromium.org + + The absolute difference between the ServiceWorker Cache size saved to the + CacheStorage index and the actual cache size when opened. + + + + + + Replaced in M78 with ServiceWorkerCache.PeakParallelSharedOps2 that uses a + smaller histogram range with the same number of buckets in order to improve + bucket granularity. + + wanderview@chromium.org + chrome-owp-storage@google.com + + The peak number of shared operations that ran simultaneously during a single + "batch" of operations. A batch is defined as the time from when an + idle scheduler begins running a shared operation until the count of running + shared operations drops back to zero. + + + + + + Removed in M85 since the parallel operation trial launched already. Also, + this histogram did not provide very useful information. + + wanderview@chromium.org + chrome-owp-storage@google.com + + The peak number of shared operations that ran simultaneously during a single + "batch" of operations. A batch is defined as the time from when an + idle scheduler begins running a shared operation until the count of running + shared operations drops back to zero. + + + + + + This histogram was removed in M77 when we began deleting entries with the + deprecated url field. + + horo@chromium.org + + True if a response read from the CacheStorage has a url field. This field + was deprecated in M57. + + + + + + This histogram was removed in M85 in favor of the OperationDuration2 + histograms that provide full timing information for operations. + + wanderview@chromium.org + + An operation is slow (true) if it takes at least 10 seconds to run. If an + operation never completes, it will still be recorded as slow. + + + + + + This histogram was deprecated in M72 in favor of + ServiceWorkerCache.Scheduler.OperationDuration2. + + wanderview@chromium.org + + The time in ms from when an operation is started until it completes. + + + + + + This histogram was deprecated in M72 in favor of + ServiceWorkerCache.Scheduler.QueueDuration2. + + wanderview@chromium.org + + The time in ms from when an operation was queued until its task is posted. + + + + + + Removed 2019-02 in favour of Servicification.Startup2. The data was + incompelete since it was only recorded the first time when the + ServiceManager was launched. + + hanxi@chromium.org + yfriedman@chromium.org + hnakashima@chromium.org + mheikal@chromium.org + + Histogram of how Chrome is launched, either in ServiceManager only mode or + as full browser, as well as either cold start or warm start. See + go/servicification_startup_metrics for more details. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + + The actions that have occurred in a session restore timeline. These are to + be interpreted as raw event counts. Tabs are almost certainly deferred due + to the existence memory pressure, but this may not always be the case. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + catan-team@chromium.org + + The time from SessionRestore start until all tabs have finished loading. + + + + + + Removed 2017-02 as not actionable. + + + The size of the commands written to disk. See CommandStorageBackend for + details. + + + + + + Removed 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint and + ultimately SessionRestore.ForegroundTabFirstPaint3. + + jeremy@chromium.org + sky@chromium.org + TBD + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + catan-team@chromium.org + + The time from SessionRestore start until a visible tab has finished loading. + + + + + + Removed 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2 and + ultimately SessionRestore.ForegroundTabFirstPaint3. + + jeremy@chromium.org + sky@chromium.org + + Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2 + and ultimately SessionRestore.ForegroundTabFirstPaint3. + + + + + + Removed 2015-05 in favor of SessionRestore.ForegroundTabFirstPaint3. + + jeremy@chromium.org + sky@chromium.org + + The time from SessionRestore start until a visible tab's first paint. This + metric only records paints that have occurred after a tab has loaded. + + + + + + Removed 06/2019 in favor of SessionRestore.ForegroundTabFirstPaint4. + + chrisha@chromium.org + georgesak@chromium.org + + The time from SessionRestore start until a visible tab's first paint. + + + + + + Removed 2018-05-02. This data was used to confirm that the unique name + generation change succeeded in reducing memory usage, and is no longer + needed. + + dcheng@chromium.org + + The size of a unique name derived from the browsing context name. Emitted + when generating a unique name for a new subframe or when a subframe's + browsing context name is changed before the first real load is committed. + Only applies to subframes as main frames always have an empty unique name. + + + + + + Removed 2017-08 due to unique name generation change. Please use + SessionRestore.FrameUniqueNameFromRequestedNameSize and + SessionRestore.FrameUniqueNameWithFramePathSize instead. + + dcheng@chromium.org + + Records the length of unique names for web frames that are saved as part of + session restore data. It is logged each time the unique name changes, which + typically happens when a web frame is first created or its name is changed + by mutating window.name. + + + + + + Removed 2018-05-02. This data was used to confirm that the unique name + generation change succeeded in reducing memory usage, and is no longer + needed. + + dcheng@chromium.org + + The size of the browsing context name (based on the iframe name attribute or + window.name) when generating the unique name. Emitted when generating a + unique name for a new subframe or when a subframe's browsing context name is + changed before the first real load is committed. Only applies to subframes + as main frames always have an empty unique name. + + + + + + Removed 2018-05-02. This data was used to confirm that the unique name + generation change succeeded in reducing memory usage, and is no longer + needed. + + dcheng@chromium.org + + The size of a unique name when falling back to the frame path algorithm. The + fallback path is used when the browsing context name is empty or non-unique. + Emitted when generating a unique name for a new subframe or when a + subframe's browsing context name is changed before the first real load is + committed. Only applies to subframes as main frames always have an empty + unique name. + + + + + + Removed 2018-05-02. This data was used to confirm that the unique name + generation change succeeded in reducing memory usage, and is no longer + needed. + + dcheng@chromium.org + + The size of a unique name when falling back to the frame path algorithm, + divided by the depth of the frame. Used to normalize sizes for deeper nodes + in a frame tree. Emitted when generating a unique name for a new subframe or + when a subframe's browsing context name is changed before the first real + load is committed. Only applies to subframes as main frames always have an + empty unique name. + + + + + + Removed 2017-02 as not actionable. + + The size, in k, of the last session file on disk. + + + + + Removed 2017-02 as not actionable. + + + Like NavEntryCommittedPeriod, but specifically to provide a clearer + breakdown of samples in the 10 minutes - 8 hours range. + + + + + + Removed 2017-02 as not actionable. + + + Milliseconds between subsequent Save() operations due to a nav entry being + committed (new tab created + nav initiated). + + + + + + Removed 2017-02 as not actionable. + + + Like NavListPrunedPeriod, but specifically to provide a clearer breakdown of + samples in the 10 minutes - 8 hours range. + + + + + + Removed 2017-02 as not actionable. + + + Milliseconds between subsequent Save() operations due to the navigation list + being pruned (typically a change in back/forward stacks). + + + + + + Removed 2017-02 as not actionable. + + + The number of tabs that were loaded simultaneously when restoring a session. + + + + + + Removed 2017-02 as not actionable. + + + Amount of time to read and assemble the commands from the last session. + + + + + + Removed in July 2019 / M77. + + creis@chromium.org + + How often history navigations in subframes restore a different URL than the + frame's default src URL. This indicates how much users rely on subframe + session history items. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + + The site engagement score associated with a tab restored by session restore, + recorded at the moment the tab is restored. + + + + + + Removed in July 2019 / M77, since new approach landed in r493153 (M62). + + creis@chromium.org + + Records the length of unique names that include frame paths, for subframes + that are restoring a different URL than the frame's default src URL during a + history navigation. Large values here would indicate a possible challenge + for the plan to truncate frame unique names (to save memory). + + + + + + Removed 2017-02 as not actionable. + + + Like SavePeriod, but specifically to provide a clearer breakdown of samples + in the 10 minutes - 8 hours range. + + + + + + Removed 2017-02 as not actionable. + + + Amount of time between subsequent SessionService Save() operations (aka + updates to session data). + +
+ Periods longer than 10 minutes are grouped together; see SaveLongPeriod for + resolution. +
+ + + + + Removed 2019-05 as data is no longer needed. + + dcheng@chromium.org + + How often a subframe is assigned a new name between the initial empty + document and the first navigation. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + + A breakdown of key events that occur to individual tabs as they are + processed by an ongoing session restore. + + + + + + Removed 2017-02 as not actionable. + + + TabClosedPeriod, but specifically to provide a clearer breakdown of samples + in the 10 minutes - 8 hours range. + + + + + + Removed 2017-02 as not actionable. + + + Milliseconds between subsequent Save() operations due to a tab being closed. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + + The number of tabs involved in a single session restore event. + + + + + + Removed 2020-05. Not actively used in current projects. + + chrisha@chromium.org + + The boolean indicates whether the tab load was initiated because a previous + tab load completed (including the tab was closed) or whether the tab load + was initiated because a timer fired to start the next load (true) during + session restore. + + + + + + Removed during the SessionStorage onion soup refactoring. + + cmumford@chromium.org + The result of a commit to the sessionStorage database. + + + + + Removed in Chrome 30. Use Search.DefaultSearchProviderType instead. + + Please list the metric's owners. Add more owner tags as needed. + + The id of the default search engine domain that is specified in user + preferences when a profile is loaded. + + + + + + Removed from the codebase in M85. This trial has long been obsolete. + + gab@chromium.org + + Whether the SettingsEnforcement group was successfully determined from the + field trial or if it had to revert to the hardcoded default. + + + + + + Removed in Chrome 30. Replaced by Settings.HomePageEngineType. + + Please list the metric's owners. Add more owner tags as needed. + + The id of the home page domain that is specified in user preferences when a + profile is loaded. + + + + + + Removed 08/05/2013. Replaced by + Settings.GivenShowHomeButton_HomePageIsNewTabPage. + + Please list the metric's owners. Add more owner tags as needed. + + Whether or not the home page user preference is set to the default NTP value + when a profile is loaded. + + + + + + Removed in Aug 2018. + + Please list the metric's owners. Add more owner tags as needed. + + The value of the home-page-is-new-tab-page pref when pulled down from sync + to update an out-of-sync local pref store. + + + + + + Removed in Aug 2018. + + Please list the metric's owners. Add more owner tags as needed. + + The value of the home-page-is-new-tab-page pref when pushed up to sync from + a change made locally. + + + + + + Removed in July 2019. + + csharp@chromium.org + gab@chromium.org + + Logged on first run when generating the Preferences file from + master_preferences. True if serializing the generated Preferences file to + disk was successful, false otherwise. Note: this event does not occur if + there is no master_preferences file on first run. + + + + + + Removed 02/2015. Replaced by Settings.JsonDataReadSizeKilobytes. + + gab@chromium.org + + The size of the JSON settings content about to be written to disk in + kilobytes. Suffixed with the name of the JSON file being written to disk. + + + + + + Removed 11/2018 due to lack of use. + + raymes@chromium.org + + The number of writes of a JSON file that occur in every 5 minute period of + running Chrome. Suffixed with the name of the corresponding JSON file. + + + + + + Removed 07/2019. LegacyMachineIdGeneration failed extremely rarely. + + proberge@chromium.org + + Whether generation of the RLZ deterministic machine-specific device id was + successful when creating the ProfilePrefStore. + + + + + + Removed 07/2019. Non MD version of Settings has been deprecated. + + stevenjb@chromium.org + + The amount of time between the render frame host StartProvisionalLoad event + and the render frame DocumentOnLoadCompleted event for the settings page. + + + + + + Removed 07/2019. Non MD version of Settings has been deprecated. + + stevenjb@chromium.org + + The amount of time between the render frame host StartProvisionalLoad and + DidFinishDocumentLoad events for the settings page. + + + + + + Removed in Chrome 63, as we verified that machine id generation was not + flaky. + + proberge@chromium.org + + Whether generation of the deterministic machine-specific device id was + successful when initializing the PrefHashStore. + + + + + + Removed in Chrome 54, as we stopped legacy migration of preferences. + + csharp@chromium.org + gab@chromium.org + + Whether, while loading a profile, any preference hashes were migrated from + Local State to either Preferences or Protected Preferences. + + + + + + Removed September 2020; no longer necessary. + + mpearson@chromium.org + The number of pinned tabs opened when a profile is loaded. + + + + + Removed 07/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during RegisterProfilePrefs. + + + + + + Removed in Aug 2018. + + mpearson@chromium.org + + The enabled state of the Home button pref when pulled down from sync to + update an out-of-sync local pref store. + + + + + + Removed in Aug 2018. + + mpearson@chromium.org + + The enabled state of the Home button pref when pushed up to sync from a + change made locally. + + + + + + Removed in Chrome 30. Replaced by Settings.StartupPageEngineTypes. + + Please list the metric's owners. Add more owner tags as needed. + + The ids of startup page domains that are specified in user preferences when + a profile is loaded. + + + + + + Removed in Aug 2018. + + mpearson@chromium.org + + The startup page setting when pulled down from sync to update an out-of-sync + local pref store. + + + + + + Removed in Aug 2018. + + mpearson@chromium.org + + The startup page setting when pushed up to sync from a change made locally. + + + + + + Not needed. Removed August 2019. + + mpearson@chromium.org + + The number of URLs to be loaded on startup when a profile is loaded, if the + startup page setting is set to load URLs. + + + + + + Removed 12/2015. + + mad@chromium.org + The startup URLs pref migration steps. + + + + + Removed 12/2015. + + mad@chromium.org + + The time elapsed in milliseconds in between startup URLs pref migration. A + value of 0 indicates that the last migration time was in the future due to + e.g. an incorrect system time. + + + + + + Removed March 2020. + + msalama@chromium.org + chrome-signin-team@google.com + + Tracks the sWAA value we show to the user in chrome://settings/syncSetup for + sync users. This tracks as well the different states for which sWAA can be + off. This is recorded everytime the sWAA state is calculated/refreshed. Only + Desktop. + + + + + + Removed 2014-07. + + gab@chromium.org + + Logs the tracked preference id when it is migrated to the new MAC algorithm. + This should only happen once per pref per profile. + + + + + + Removed 2014-06. + + gab@chromium.org + + The version of a PrefHashStore, reported once for each alternate + PrefHashStore (not associated to the default profile) from a delayed task on + startup. + + + + + + Removed 2014-06. + + gab@chromium.org + + The previous version of an alternate PrefHashStore (not associated to the + default profile) that was updated from a delayed task on startup. This + should match Settings.TrackedPreferencesAlternateStoreVersion fairly closely + for all versions but VERSION_LATEST which should never be reported here. + + + + + + Removed 2014-02 in favor of + Settings.TrackedPreferencesAlternateStoreVersionUpdatedFrom. + + gab@chromium.org + + Preference tracking was initialized for an unloaded profile. This should + happen at most once per profile. + + + + + + No longer used. Removed 2020-04. + + gab@chromium.org + + The number of items that had changed in a dictionary pref when + Settings.TrackedPreferenceChanged is reported for that pref. + + + + + + Removed 2015-08-18. + + wjmaclean@chromium.org + + Tracks migration to per-partition zoom-level preferences during profile + initialization. + + + + + + Removed 06/2019. All signs indicate that it is exceptionally rare for + initialization to fail. + + grt@chromium.org + + Indicates whether or not the Windows Settings app monitor was initialized. + + + + + + Removed 04/2020. Replaced with Settings.PrivacyElementInteractions to stick + to naming conventions. + + harrisonsean@chromium.org + msramek@chromium.org + sauski@chromium.org + + Which privacy related settings elements a user interacted with. Recorded + every time a user interacts with an element of interest. + + + + + + Removed 03/2020. Recording too much duplicate data with route navigation + histogram (WebUI.Settings.PathVisited). + + harrisonsean@chromium.org + msramek@chromium.org + + Which settings a user interacted with. Recorded every time a user interacts + with a setting. + + + + + + Removed 07/2019. + + alito@chromium.org + + The feature parameter determining the amount of time to wait after startup + before attempting to show the settings reset prompt. Logged once after + startup. + + + + + + Removed on 2018-01-16. + + alito@chromium.org + + The number of extensions that were disabled after the user accepted the + settings reset prompt. + + + + + + Removed on 2018-01-16. + + alito@chromium.org + + The number of extensions that will be disabled if the user accepts the + settings reset prompt. Logged once after startup. + + + + + + Removed in M59 in April 2017 and replaced by + SettingsResetPrompt.TimeUntilCanceled and + SettingsResetPrompt.TimeUntilDismissed. + + alito@chromium.org + + The time between the settings reset prompt dialog being shown and the user + declining the prompt. + + + + + + Removed 06/2019. + + grt@chromium.org + + The elapesed time to apply a patch to a previous version's chrome.7z archive + to generate a new chrome.7z archive. This histogram only applies to diff + updates. + + + + + + Expired in M82, then replaced by Setup.Install.CumulativeDiskUsage2 on + 06/2020. + + etiennep@chromium.org + grt@chromium.org + + The cumulative disk usage in MB during install or uninstall attempt, + recorded right after the install/uninstall attempt on windows only. + + + + + + Removed 2020-02 + + grt@chromium.org + + Hit following a successful install or update when the legacy + "app_host.exe" binary is deleted from the filesystem. + + + + + + Removed 06/2019. + + grt@chromium.org + + True if the chrome.packed.7z archive contains a patch (in which case a diff + update is taking place) or false if it contains a full archive (in which + case a new install or a full update is taking place). + + + + + + Removed 03/2020. + + zmin@chromium.org + + Record the NTSTATUS code of unpacking the contents of a 7z file. + + + + + + Removed 03/2020. + + etiennep@chromium.org + + Record the return value of unpacking the contents of a 7z file. + + + + + + Removed 2020-02 + + grt@chromium.org + + Hit following a successful install or update when data from a legacy + multi-install Chrome Frame is deleted from the registry. + + + + + + Removed 06/2019. In 88% of cases, we aborted after the maximum number of + attemps was reached. The remaining 12% of cases occured when another process + tried to acquire the setup singleton. + + fdoray@chromium.org + + Number of calls to DeleteOldVerions() made by a --delete-old-versions + process that didn't delete all files that belong to old versions of Chrome. + A --delete-old-versions process exits when another process tries to acquire + the SetupSingleton or after too many unsuccessful attempts to delete all old + files. A --delete-old-versions process that successfully acquires the + SetupSingleton records to either the + Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the + Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram. + + + + + + Removed 06/2019. 50th percentile: 1.5. 75th percentile: 1.77. 99th + percentile: 2.75. + + fdoray@chromium.org + + Number of calls to DeleteOldVersions() made by a --delete-old-versions + process that successfully deleted all files that belong to old versions of + Chrome. A --delete-old-versions process that successfully acquires the + SetupSingleton records to either the + Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the + Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram. + + + + + + Removed 06/2019 because it is not used. + + fdoray@chromium.org + + The result of trying to acquire a setup singleton. On Windows, a setup.exe + process must hold the setup singleton of a Chrome installation when it makes + changes to it. + + + + + + Removed 2017-01 + + grt@chromium.org + + The disposition of a stranded Chrome install discovered while updating + multi-install Chrome Binaries. This metric is only logged in an edge case. + The buckets indicate whether or not the "stranded" Chrome install + has been used in the last 28 days. If so, it respresents a Chrome that has + not been updating due to a logic flaw in the installer and will be repaired + in the current update. If not, it likely represents Chrome Binaries that + were previously used by Chrome Frame that has since been uninstalled and + that will be uninstalled in a future update. + + + + + + Removed 06/2019. + + grt@chromium.org + + The elapsed time to uncompress a chrome.7z patch. This histogram only + applies to diff updates. + + + + + + Removed 06/2019. + + grt@chromium.org + + The elapsed time to uncompress a full chrome.7z archive. This histogram only + applies to new installs and to full updates. + + + + + + Removed 06/2019. + + grt@chromium.org + + The elapsed time to unpack the uncompressed chrome.7z archive. This + histogram applies to all installs and updates. + + + + + + Not accessed in months. Primary error was CREATE_FILE_MAPPING_FAILURE by + far. Removed 2020-03. + + erikchen@chromium.org + alexilin@chromium.org + + A histogram entry is emitted each time a shared memory object is constructed + (for example, base::ReadOnlySharedMemoryRegion or the deprecated + base::SharedMemory). The value of the entry indicates the type of error + encountered during construction. + + + + + + Not accessed in months and no data reported for it at all. Removed 2020-03. + + alexilin@chromium.org + + Emitted each time a shared memory region could not be created due to a + failed Mac system call. The value of the entry indicates the return value of + the failed call. + + + + + + Not accessed in months. Primary error was #1455 by far. Removed 2020-03. + + bcwhite@chromium.org + + A histogram entry is emitted each time a shared memory object could not be + created due to a failed Windows system call (for example, + base::ReadOnlySharedMemoryRegion or the deprecated base::SharedMemory). The + value of the entry indicates the result of the GetLastError() API call. + + + + + + Removed 2015-06 because the Finch experiment SharedMemoryCreateStrategy has + finished running. + + erikchen@chromium.org + + The time spent making a new region of shared, anonymous memory. This metric + is not emitted if the shared memory region is read only. + + + + + + Replaced with BrowserRenderProcessHost.KeepAliveDuration as of Aug 2017. + + horo@chromium.org + + A survival time of RenderProcessHostImpl for the In-renderer Shared Worker + from when FastShutdownIfPossible() is called. + + + + + + Removed June 2019. + + horo@chromium.org + + The lifetime of a SharedWorkerHost. This roughly corresponds to the lifetime + of SharedWorker. + + + + + + Removed June 2019. + + horo@chromium.org + + The time from the creation of SharedWorkerHost until when WorkerScriptLoaded + is called. + + + + + + Removed June 2019. + + horo@chromium.org + + The time from the creation of SharedWorkerHost until when + WorkerScriptLoadFailed is called. + + + + + + Removed in M84 after gathering enough data as a baseline. + + himanshujaju@chromium.org + knollr@chromium.org + peter@chromium.org + + Time taken to find a phone number in highlighted text for context menu. + Desktop only. + + Note: This metric drops reports on clients with low-resolution clocks, which + means these reports will be biased against a portion of the population on + Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. + + + + + + Removed in M81 in favor of Sharing.ClickToCallDialerPresent + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Logged when a user taps a Click to Call notification and a dial intent is + fired to open the dialer. Distinguishes between empty string (no phone + number) and not empty. Android only. + + + + + + Removed in M81 as there was not a lot of usage of the help link. + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Logged whenever a user clicks on the help text in a Click to Call dialog. + The value is used to distinguish which dialog type was shown. Desktop only. + + + + + + Removed in M82 after collecting enough data. See https://crbug.com/1053140. + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time from opening the dialer until a phone call is initiated. This is + logged when we detect an outgoing phone call after opening the dialer as + part of the Click to Call feature. Android only. + + + + + + Removed in M82 as the experiment has been stopped. + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The number of digits in a phone number. Logged when right clicking on a + selected phone number or tel link, showing the Click to Call dialog and when + selecting a device. Desktop only. + + + + + + Removed in M82 as the experiment has been stopped. + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The number of characters in a phone number including digits and non-digits. + Logged when right clicking on a selected phone number or tel link, showing + the Click to Call dialog and when selecting a device. Desktop only. + + + + + + Removed in M82 as the experiment has been stopped. + + + + knollr@chromium.org + mvanouwerkerk@chromium.org + + The result of comparing a phone number regex variant against the simple + version. Logged after right clicking on a selection and when selecting a + device from the context menu. Desktop only. + + + + + + Removed in M82 after collecting enough data. See https://crbug.com/1053140. + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The device state when receiving a Click to Call message. Indicates if the + screen is on or off and if Chrome is running in foreground. Recorded when + handling a Click to Call message. Android only. + + + + + + Removed 06/2020. Never launched. + + gayane@chromium.org + src/components/send_tab_to_self/OWNERS + + Records how long it took to the failed attempt to save the QR code image. + + + + + + Removed 06/2020. Never launched. + + gayane@chromium.org + src/components/send_tab_to_self/OWNERS + + Records how long it took to successfully save the QR code image. + + + + + + Replaced by SendAckMessageResult in M78. + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Whether an ack message was sent successfully by the Sharing service. Logged + in the callback for sending the message to FCM. All platforms. + + + + + + Replaced by SendMessageResult in M78. + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Whether a SharingMessage was sent successfully by the Sharing service. + Success requires receiving an ack message before the timeout. Logged after + the send message callback is run. Not logged for sending ack messages. All + platforms. + + + + + + Removed 2020-06 as the result is always successful. + + alexchau@chromium.org + peter@chromium.org + + Result of Sharing VAPID key generation during registration. Logged after + Sharing VAPID key generation is attempted. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + Result of parsing received ice candidate. Logged when trying to add received + ice candidate. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + Error reason for closing a WebRTC connection. Logged when a p2p WebRTC + connection is closed. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + Type of routing used to establish a connection with a remote device. Logged + when a p2p connection is established using WebRTC by SharingService. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + Result of receiving and handling a message via WebRTC. Logged after + receiving a message from remote device via WebRTC. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + Result of sending a SharingMessage by SharingService via WebRTC. Logged + after sending the message. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + himanshujaju@chromium.org + knollr@chromium.org + + State of the WebRTC connection when it timed out. Logged when the connection + has been inactive for 30 seconds. + + + + + + Removed 2020-09 as the WebRTC experiment is shut down. + + + + himanshujaju@chromium.org + knollr@chromium.org + + Sharing WebRTC timing events logged during an active WebRTC connection. + + + + + + Removed 09/11/2020 as it has been unused for a while with no expectation to + be used in the future. + + manukh@chromium.org + chrome-omnibox-team@google.com + + The time it takes for the ShortcutsProvider to perform a query after the + user has typed N characters. + + + + + + Replaced by Shutdown.browser_exit.time2 to get more resolution into the tail + of the distribution (10/2016). + + hashimoto@chromium.org + + Time for shutdown initiated by the browser exit menu command. + + + + + + Replaced by Shutdown.end_session.time2 to get more resolution into the tail + of the distribution (10/2016). + + hashimoto@chromium.org + + Time for shutdown initiated by an end session (user logs off, shuts down or + reboots without explicitly exiting). + + + + + + Replaced by Shutdown.window_close.time2 to get more resolution into the tail + of the distribution (10/2016). + + hashimoto@chromium.org + + Time for shutdown initiated by the last browser window being closed. + + + + + + Removed 2/2019 in favor of SignedExchange.LoadResult2. + + kinuko@chromium.org + kouhei@chromium.org + ksakamoto@chromium.org + + Records the result of loading a resource from Signed HTTP Exchange. Emitted + each time a response is handled as Signed Exchange. + + + + + + Removed 2/2019 in favor of SignedExchange.Prefetch.LoadResult2. + + kinuko@chromium.org + kouhei@chromium.org + + Records if the prefetched Signed Exchange was properly formatted and passed + verification steps. Reported for each completed SignedExchange prefetch. + + + + + + Instrumentation code has been removed as the conversion has been completed. + + msarda@chromium.org + sdefresne@chromium.org + + This histogram records the removal of the ServiceState property from the + identities known to the AccountTracker. It records whether the deprecated + flag was found in the loaded data and had to be deleted. + + This histogram will be used to check whether the migration has completed for + all active installs on a given platform or not (and whether the code can be + removed). + + This is recorded on each profile load. + + + + + + Removed 2019-07 as it was never used by the sign-in team. + + msarda@chromium.org + droger@chromium.org + + Track when chrome successfully adds an account. Failures are not tracked. + + + + + + Removed this histogram since we have had newly designed histograms + Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and + Signin.SigninReason. + + guohui@chromium.org + Track how a user interfacts with the android signin promo. + + + + + Removed on 2020-03 as it is not needed by the signin team. + + bsazonov@chromium.org + droger@chromium.org + + Duration of time between UpdateAccountList calls. Recorded when + OAuth2TokenServiceDelegateAndroid::UpdateAccountList completes. + + + + + + Removed 2019-09. No longer useful after Dice is launched. + + droger@chromium.org + + Logs the state of the Chrome account when the user signs out on the web. + This assumes that a logout of the web is always a complete logout of all the + web accounts (e.g. single session signout is not supported). + + + + + + Replaced by Signin.DiceMigrationStatus. Does not have any meaningful + information. + + droger@chromium.org + + Whether Dice is enabled for the current profile, recorded at startup. + + + + + + Removed M80. Dice migration is complete. + + msalama@chromium.org + msarda@chromium.org + + Tracks the reason of why DICE migration is not ready. It is computed by Dice + reconcilor delegate on every reconciliation cycle. + + + + + + Removed 03/2020, as it was equivalent to Signin.SigninAllowed. + + droger@chromium.org + + The Dice migration status, recorded at startup for each profile. + + + + + + Removed M77 in favor of Signin.SigninCompletedAccessPoint + + msarda@chromium.org + droger@chromium.org + + Track if the profile sign in took place during First Run or not. Logged at + signin time. True means signin took place during First Run, False means + anytime after. + + + + + + Removed M77 as not relevant. + + msarda@chromium.org + droger@chromium.org + + Track how many minutes of local system time elapsed from when Chrome was + installed to when Signin occured for this profile. + + + + + + Removed in M76. Use Signin.OAuthMultiloginResponseStatus instead. + + droger@chromium.org + msarda@chromium.org + + Reconds finished calls to Gaia Multilogin endpoint, both successful or not, + and return the GoogleAuthError state NONE is a success, other values are + failures. + + + + + + Removed in M76, because multilogin switched to a new error type. + + droger@chromium.org + msarda@chromium.org + + Retry reason of failed Multilogin call during Chrome reconcile. + + + + + + Replaced on 2020-04 by Signin.OAuth2TokenGetResult. + + msarda@chromium.org + droger@chromium.org + + Reason fetching an OAuth2 Token failed. Available on all OSes. + + + + + + Removed 2014-09 because chrome no longer tries to reconcile from the cookie + jar to the browser. + + mlerman@chromium.org + + How many accounts were added to the browser's token service because they + were in the cookie jar. + + + + + + Removed in favor of Signin.Reconciler.Duration.UpTo3mins. + + rogerta@chromium.org + msarda@chromium.org + Records the execution time of the account reconciler. + + + + + Removed this histogram along with the code that was logging it. + + pavely@chromium.org + + Track when chrome successfully sends RefreshTokenAnnotationRequest. + + + + + + Removed 2019-07, replaced with a log message. + + msarda@chromium.org + + Tracks when Chrome adds or removes the Desktop Identity Consistency HTTP + header to Gaia. + + + + + + Removed 2019-07, replaced with a log message. + + msarda@chromium.org + + Tracks when Chrome adds or removes the the X-Chrome-Connected HTTP header to + Gaia. + + + + + + Removed in 7/2019 as the information it provides is no longer useful. + + msarda@chromium.org + droger@chromium.org + + Track how many minutes of real time (not browser active time) elapsed + between profile signin and signout. + + + + + + Removed this histogram since we have had newly designed histograms + Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and + Signin.SigninReason. + + noms@chromium.org + + Logs the original source that displayed the signin or reauth Gaia page, + before the page is displayed. + + + + + + Obsolete after Unified Consent launch. + + bsazonov@chromium.org + + Tracks the usage of different flows that switch sync accounts. Logged after + accounts have been switched. + + + + + + Removed M80. Obsolete after Dice migration completed. + + msalama@chromium.org + msarda@chromium.org + + Tracks the state of kTokenServiceDiceCompatible preference. This is recorded + at every startup, if the account consistency method is in Dice migration and + is not ready yet to migrate to Dice. + + + + + + Removed 2019-09. Obsolete after Dice is launched. + + droger@chromium.org + + Tracks the changes of refresh token states for all accounts. Tokens can have + three states: Regular (retrieved from Gaia), Invalid (created by Chrome and + known to be invalid) or None (no token). Recorded when a token is loaded or + changed. + + + + + + Obsolete because the XDevicePromo never shipped. + + anthonyvd@chromium.org + mlerman@chromium.org + + How long a browsing session was measured to be. Logged when a Browser window + becomes active if the previous activation was longer than the minimum + configured in the "CrossDevicePromo" experiment. Desktop only. + + + + + + Obsolete because the XDevicePromo never shipped. + + anthonyvd@chromium.org + mlerman@chromium.org + + How often browsers are considered activated, which in turn triggers the + CrossDevicePromo. Logged every time a Browser window becomes active. We need + this to estimate QPS for RPC calls. Desktop only. + + + + + + Obsolete because the XDevicePromo never shipped. + + anthonyvd@chromium.org + mlerman@chromium.org + + The reasons for which a profile is or is not eligible for the Desktop Cross + Device Sign In Promo. Logged every time a new Browsing session is detected + as part of a Browser window becoming active. Desktop only. + + + + + + Obsolete because the XDevicePromo never shipped. + + anthonyvd@chromium.org + mlerman@chromium.org + + Tracks if profiles initialized the XDevicePromo, and if not, why. Logged at + Profile startup and (if not initialized then) when a new browsing session is + detected during Browser window activation. Desktop only. + + + + + + Removed 2020-08. + + morlovich@chromium.org + + The time to open the stream 2 file successfully on disk cache entry open + with known key, when the size of payload is greater than 32 bytes. + + + + + + Removed 2020-08. + + morlovich@chromium.org + + The time to open the stream 2 file successfully on disk cache entry open + with known key, when the size of payload is 32 bytes or less. + + + + + + Removed 2018-02. Not creating stream 2 on CreateEntry entries is indeed a + good idea, since stream 2 writes are done on things opened with OpenEntry. + (Which also means this metric wasn't good at evaluating the prevalence of + stream 2 in general). + + morlovich@chromium.org + + Whether, upon creation of a new cache entry, the file for stream 2 was + omitted since that stream was empty. + + + + + + Removed 2020-08. Look at SyncOpenResult and SyncCreateResult. + + morlovich@chromium.org + + For entry creation operations that were sent to the disk, the result of + creation. + + + + + + Removed 2020-08-17 + + morlovich@chromium.org + + Whether, upon opening of an existing cache entry, stream 2 was empty and the + file for that stream was therefore removed. + + + + + + Removed 2019-03. + + morlovich@chromium.org + + At the time that operations are run, the number of pending operations on a + particular entry. + + + + + + Removed 2020-05 due to excessive quantities of data. + + wanderview@chromium.org + + The number of bytes read at the end of the entry file in order to process + the EOF footer and the stream 0 data. + + + + + + Removed 2013 in favour of SimpleCache.Eviction.CacheSizeOnStart2 + + morlovich@chromium.org + The size of the cache at the beginning of an eviction. + + + + + Removed 2013 in favour of SimpleCache.Eviction.MaxCacheSizeOnStart2 + + morlovich@chromium.org + + The maximum allowed size of the cache at the beginning of an eviction. + + + + + + Removed 2013 in favour of SimpleCache.Eviction.SizeOfEvicted2 + + morlovich@chromium.org + The number of bytes to be erased in an eviction. + + + + + Removed 2013 in favour of SimpleCache.Eviction.SizeWhenDone2 + + morlovich@chromium.org + The size of the cache after running an eviction. + + + + + Removed 2019-07-03 + + morlovich@chromium.org + + The maximum limit of how many file descriptors a process can open. Emitted + each time the browser is launched, if the limit could be retrieved. (This is + the highest value we could raise the current limit to if we liked.) + + + + + + Removed 2019-07-03. Consider Memory.Browser.OpenFDsSoftLimit for similar + information. + + morlovich@chromium.org + + The current limit of how many file descriptors a process can open. Emitted + each time the browser is launched, if the limit could be retrieved. (We can + raise this to the maximum limit if we like, without root access.) + + + + + + Removed 2019-07-03 + + morlovich@chromium.org + + The result of trying to get the file descriptor limit. Emitted each time the + browser is launched. + + + + + + Removed 2019-07-03. + + morlovich@chromium.org + + The number of open entries across all caches backed by the Simple Cache. An + entry is opened whenever a caller asks to open it to read or write cache + data, and remains open until the last caller asks to close it. Logged + whenever an entry is opened or closed. + + + + + + Removed 2018-06-05 + + morlovich@chromium.org + + How the header size has changed in a Simple Cache entry, emitted every time + a write operation occurs on the header stream. (This includes the initial + write, rewrites, and other writes that we couldn't classify.) + + + + + + Removed 2018-06-05 + + morlovich@chromium.org + + The absolute size decrease of the header stream of a Simple Cache entry, + emitted every time the headers are rewritten with a smaller size. + + + + + + Removed 2018-06-05 + + morlovich@chromium.org + + The relative size decrease of the header stream of a Simple Cache entry, + emitted every time the headers are rewritten with a smaller size. + + + + + + Removed 2018-06-05 + + morlovich@chromium.org + + The absolute size increase of the header stream of a Simple Cache entry, + emitted every time the headers are rewritten with a larger size. + + + + + + Removed 2018-06-05 + + morlovich@chromium.org + + The relative size increase of the header stream of a Simple Cache entry, + emitted every time the headers are rewritten with a larger size. + + + + + + Removed in M85, but code was missing at that point already. + + morlovich@chromium.org + For each index load, whether the index file was corrupt. + + + + + Removed in M85 + + morlovich@chromium.org + Number of entries loaded from the index file on start. + + + + + Removed in M85 + + morlovich@chromium.org + + Number of entries restored from disk when there was no index or the index + was corrupted. + + + + + + Removed in M85 + + morlovich@chromium.org + + At the time of index initialization, the number of enqueued jobs awaiting + index initialization. + + + + + + Removed in M85, but didn't actually work before that. + + morlovich@chromium.org + + Time (as measured on the worker pool) spent loading the index file. + + + + + + Removed 07/2013, and replaced by IndexFileStateOnLoad. + + morlovich@chromium.org + For each index load, whether the index file was stale. + + + + + Removed pre-M85. + + morlovich@chromium.org + + The interval between index saves, for apps in the background. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + The interval between index saves, for apps in the foreground. + + + + + + Removed 2013-05 in favour of + SimpleCache.SimpleIndexWriteToDiskTime.Background and + SimpleCache.SimpleIndexWriteToDiskTime.Foreground. + + morlovich@chromium.org + + The amount of time spend writing the index file to disk, measured starting + at the beginning of the write on the callback thread, and calculated using + the completion time on the worker pool. + + + + + + Removed in M85 + + morlovich@chromium.org + + The amount of time spend writing the index file to disk, for apps in the + background, measured starting at the beginning of the write on the callback + thread, and calculated using the completion time on the worker pool. + + + + + + Removed in M85 + + morlovich@chromium.org + + The amount of time spend writing the index file to disk, for apps in the + foreground, measured starting at the beginning of the write on the callback + thread, and calculated using the completion time on the worker pool. + + + + + + Removed 2016-05 as the match checking was moved back into the entry itself, + so this result is now reported in the SimpleCache.x.SyncOpenResult + histograms. + + morlovich@chromium.org + + For each call to OpenEntry, whether the key on disk matched the request key. + + + + + + Removed 2018-01; not viewed as actionable. + + morlovich@chromium.org + + For each file in the Simple Cache, the percentage of disk space used by the + cluster loss, the unused disk space in the last 4096 byte cluster of the + file. + + + + + + Removed 2018-01; not viewed as actionable. + + morlovich@chromium.org + + For each file in the Simple Cache, the number of bytes in the last 4096 byte + cluster when the entry is saved to disk. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + Number of operations that were queued behind a particular doom operation + (with a mass doom counting as a single operation). + + + + + + Removed pre-M85. + + morlovich@chromium.org + + Delay between when the I/O portion of CreateEntry is enqueued and when its + execution begins. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + Delay between when the I/O portion of OpenEntry is enqueued and when its + execution begins. + + + + + + Removed pre-M85. + + morlovich@chromium.org + bingler@chromium.org + + Delay between when the I/O portion of OpenOrCreateEntry is enqueued and when + its execution begins. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + Delay between when an operation is deferred due to a pending doom for its + key, and when it can resume execution. + + + + + + Removed 2018-07-02. See https://crrev.com/c/1122706 + + morlovich@chromium.org + + For each Read operation, whether it could have been issued in parallel of a + previous Read operation. + + + + + + Removed pre-M85. + + morlovich@chromium.org + The outcome of Entry::ReadData in the simple cache. + + + + + Removed pre-M85 + + morlovich@chromium.org + + Whether a read from stream 1 (conventionally used for payload body) was + satisfied from prefetched data. Reported only on the first read operation on + the stream (including if there are multiple readers, or even some writers). + + + + + + Removed pre-M85. + + morlovich@chromium.org + + For each EOFRecord found with a valid magic number, indicates if the record + also contains a CRC. + + + + + + Removed pre-M85. Consider SyncCreatePlatformFileError + + morlovich@chromium.org + + The result, at the synchronous layer, reported when attempting to create a + new cache entry. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + The result of the the key SHA256 check done when opening stream 0 for each + entry. + + + + + + Replaced Dec, 2018 by SimpleCache.SyncOpenPrefetchMode. The new histogram is + an enumeration that can distinguish between full file prefetching from + trailer prefetching. + + morlovich@chromium.org + + Whether an attempt was made to prefetch the entire file when executing + disk_cache::Backend::OpenEntry. + + + + + + Removed pre-M85. + + morlovich@chromium.org + + The age of the entry (time since last modified), when opened at the + synchronous layer. + + + + + + Removed 2018-07-02. See https://crrev.com/c/1122706 + + morlovich@chromium.org + + Shows whether a write operation depends on the previous operation in queue + particularly in the aspect of its possibility to run in parallel. + + + + + + Replaced 2013/09/03 by WriteResult2, which adds "fast empty + return", which previously showed up as "success". + + morlovich@chromium.org + The outcome of Entry::WriteData in the simple cache. + + + + + Removed pre-M85. SyncWriteResult may be of interest. + + morlovich@chromium.org + The outcome of Entry::WriteData in the simple cache. + + + + + Removed on 9/2019: metric is not monitored for the UI compositor. + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of stages in the pipeline while processing a single + frame on the single thread compositor, where the Main frame did not miss its + deadline. + + A Main frame that missed its deadline is a frame such that + SubmitCompositorFrame happened before a commit and activation happened. E.g. + BeginImplFrame1 -> BeginMainFrame1 -> SubmitCompositorFrame -> + BeginImplFrame2 -> Commit1 -> Activate1 -> SubmitCompositorFrame + + + + + + Removed on 9/2019: metric is not monitored for the UI compositor. + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of stages in the pipeline while processing a single + frame on the single thread compositor, where the Main frame missed its + deadline. + + A Main frame that missed its deadline is a frame such that + SubmitCompositorFrame happened before a commit and activation happened. E.g. + BeginImplFrame1 -> BeginMainFrame1 -> SubmitCompositorFrame -> + BeginImplFrame2 -> Commit1 -> Activate1 -> SubmitCompositorFrame + + + + + + Removed on 9/2019. Did not provide enough information about latency. + + sadrul@chromium.org + graphics-dev@chromium.org + + The latency increase of an abnormally long activation stage on the single + thread compositor pipeline when the frame is missed. + + These latency increases are determined by comparing the stage duration to + the times from past non-missed frames. These times are also reported to + "SingleThreadedCompositorLatency.MissedFrame.<StageName>" + + + + + + Removed in M60. See crbug.com/712493. + + calamity@chromium.org + dominickn@chromium.org + felt@chromium.org + + The percentage of total site engagement accumulated by this profile for + HTTPS URLs as a proportion of all engagement for HTTPS and HTTP URLs. + Recorded at startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. + + + + + + Removed in M60. See crbug.com/712493. + + calamity@chromium.org + dominickn@chromium.org + felt@chromium.org + + Distribution of the engagement scores accumulated by a user, recorded at + startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. Limited specifically to + HTTP URLs. + + + + + + Removed in M60. See crbug.com/712493. + + calamity@chromium.org + dominickn@chromium.org + felt@chromium.org + + Distribution of the engagement scores accumulated by a user, recorded at + startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. Limited specifically to + HTTPS URLs. + + + + + + Removed in M81. + + charleszhao@chromium.org + dominickn@chromium.org + kcarattini@chromium.org + + The distribution of zero versus non-zero engagement scores accumulated by + the user, recorded at the same time as + SiteEngagementService.EngagementScore. + + + + + + Removed in M81. + + calamity@chromium.org + dominickn@chromium.org + + The percentage of all origins recorded by the site engagement service which + have reached the absolute site engagement point cap, recorded at startup per + non-incognito profile, and then upon the first engagement-increasing event + every hour thereafter. + + + + + + Removed in M81. + + calamity@chromium.org + dominickn@chromium.org + + The site engagement score of an origin prior to applying decay. Recorded at + the first engagement event after decay, independently per decay event. + + + + + + Removed in M81. + + calamity@chromium.org + dominickn@chromium.org + + The site engagement score of an origin once decay has occured. Recorded at + the first engagement event after decay, independently per decay event. + + + + + + Split this histogram into SiteIsolatedCodeCache.JS.Behaviour and + SiteIsolatedCodeCache.WASM.Behaviour to collect statistics for JS and WASM + code caches in separate histograms. + + mythria@chromium.org + + The behaviour of site isolated javascript code cache recorded for each cache + transaction. It records if the request was serviced and if serviced how it + was serviced for ex: hit, miss, update. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of all network responses received by a renderer. Each response is + corresponding to one URL requested by a renderer. Incremented when the first + network packet of a response of this type is received. + + + + + + Deprecated in March 2020; see Memory.RenderProcessHost.Count.* instead. + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + The count of all renderer processes, including WebUI and extensions. + Recorded once per UMA ping. + + + + + + Deprecated in March 2020. For about:flags usage, see Launch.FlagsAtStartup. + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + True if the --isolate-origins mode was enabled from the command line, + about:flags, or enterprise policy. Recorded on browser startup and then once + every 24 hours. + + + + + + Deprecated in March 2020. For about:flags usage, see Launch.FlagsAtStartup. + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + True if the --site-per-process mode was enabled from the command line, + about:flags, or enterprise policy. Recorded on browser startup and then once + every 24 hours. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since site-per-process has already shipped on desktop in M67 (see + https://crbug.com/810843). + + creis@chromium.org + + The upper bound of the predicted renderer process count if we isolated all + sites, subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since site-per-process has already shipped on desktop in M67 (see + https://crbug.com/810843). + + creis@chromium.org + + The lower bound of the predicted renderer process count if we isolated all + sites, subject to the process limit. Happens to be the number of unique + sites. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since site-per-process has already shipped on desktop in M67 (see + https://crbug.com/810843). + + creis@chromium.org + + The predicted renderer process count if we isolated all sites and if there + were no process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since site-per-process has already shipped on desktop in M67 (see + https://crbug.com/810843). + + creis@chromium.org + + The predicted total process count if we isolated all sites, subject to the + process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since isolate-extensions has already shipped in M56 (see + https://crbug.com/545200). + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The upper bound of the predicted renderer process count if we isolated only + Chrome extensions, subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since isolate-extensions has already shipped in M56 (see + https://crbug.com/545200). + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The lower bound of the predicted renderer process count if we isolated only + Chrome extensions, subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since isolate-extensions has already shipped in M56 (see + https://crbug.com/545200). + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted renderer process count if we isolated only Chrome extensions + and if there were no process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77 - the histogram is no longer useful + since isolate-extensions has already shipped in M56 (see + https://crbug.com/545200). + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted total process count if we isolated only Chrome extensions, + subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The upper bound of the predicted renderer process count if we isolated only + HTTPS (not HTTP) sites, subject to the process limit. Recorded once per UMA + ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The lower bound of the predicted renderer process count if we isolated only + HTTPS (not HTTP) sites, subject to the process limit. Happens to be the + number of isolated sites. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted renderer process count if we isolated only HTTPS (not HTTP) + sites and if there were no process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted total process count if we isolated only HTTPS (not HTTP) + sites, subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The upper bound of the estimated renderer process count if we isolated no + sites, subject to the process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The lower bound of the predicted renderer process count if we isolated no + sites, subject to the process limit. Happens to be the number of isolated + sites. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted renderer process count if we isolated no sites and if there + were no process limit. Recorded once per UMA ping. + + + + + + Logging code has been removed in M77. + + creis@chromium.org + lukasza@chromium.org + site-isolation-dev@chromium.org + + The predicted total process count if we isolated no sites, subject to the + process limit. Recorded once per UMA ping. + + + + + + Deprecated in March 2020. + + alexmos@chromium.org + + The number of currently enabled isolated origins. This includes origins + specified via the --isolate-origins command-line flag as well as those + configured via enterprise policy. Recorded on browser startup. + + + + + + Code deleted in June 2020. + + rsesek@chromium.org + + The number of times a render process transitions its main thread isolate + into or out of memory savings mode. This is recorded per-renderer-process + upon the creation of the first main frame or the destruction of the last + main frame. + + + + + + Deprecated in March 2020. + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + Whether or not the RenderProcessHost is disqualified from process reuse + because it has a pending navigation to a URL for which SiteInstance does not + assign a site URL, such as chrome-native://newtab. This is intended to + measure how often this scenario results in spinning up extra processes. + Measured once per IsSuitableHost() invocation. + + + + + + Removed in June 2019 / M77. Some old data have been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + The total count of responses that were would be blocked by the cross-site + document blocking logic in the browser process, but were only allowed + because the request was initiated by a content script of an extension. + Recorded with a resource type (0-17) when the response is allowed. + + Note that this histogram is not reimplemented in the NetworkService version + of Cross-Origin Read Blocking feature. This should be okay since we hope to + gather enough data before NetworkService ships. + + + + + + Removed in September 2020 / M87. (It was not needed anymore, since + CORS-for-content-scripts has successfully shipped in M85.) + + creis@chromium.org + lukasza@chromium.org + + Logs an upper bound of how many new content script requests might be blocked + if we start making them subject to CORS. We haven't yet started passing + Origin headers on these requests, so this will report true/risky even if in + the future the server might respond with a valid Access-Control-Allow-Origin + header when presented with an expected Origin request header. + + Logged when 1) CORB processes a http response (so excluding requests from + allowlisted content script and requests from extension background pages + where CORB is disabled) and 2) the request was associated with a non-http + isolated world origin (so not logging anything when the + CorbAllowlistAlsoAppliesToOorCors and OOR-CORS features are enabled since + the former feature forces ignoring the isolated world origin when OOR-CORS + is enabled) and 3) CORB allows the response (based on non-CORB-content-type + header OR sniffing decided that this is not a CORB type). + + Logs "risky" if the request would be blocked by CORS if made from + a web page (cross-origin, mode=cors, and no valid ACAO response header). + Logs "safe" otherwise. + + + + + + Removed in June 2019 / M77. Some old data have been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + The total count of responses that were blocked by the cross-site document + blocking logic in the browser process. Recorded with a resource type (0-17) + when the response is blocked; up to 1024 bytes of the response are + considered. This is also recorded with a suffix indicating the MIME type + category. + + + + + + Removed in June 2019 / M77. Some old data has been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + For each responses blocked by the cross-site document blocking logic in the + browser process, logs network::ResourceResponseInfo::content_length of the + response (but only if the content length value was available - if the value + was not -1). + + + + + + Removed in June 2019 / M77. Some old data has been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + For each responses blocked by the cross-site document blocking logic in the + browser process, logs whether network::ResourceResponseInfo::content_length + was available (i.e. value was 0 or greated) or not available (i.e. value was + equal to -1) if the value was available (i.e. the value was not -1). + + + + + + Removed in June 2019 / M77. Some old data have been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + The total count of responses that were blocked by the cross-site document + blocking logic in the browser process, due to the presence of a Javascript + parser-breaker pattern (like "for(;;);", or ")]}'", or a + non-empty JSON dictionary like "{\"a\":". Recorder with + a resource type (0-17) when the response is blocked; up to 1024 bytes of the + response are considered. + + + + + + Removed in June 2019 / M77. Some old data has been saved in a + Google-internal doc at + https://docs.google.com/document/d/1hgPpFD5GpxgWsTQvrA0eLunrG0mwb_uJgWWJmG_kVN4 + + creis@chromium.org + lukasza@chromium.org + + The number of bytes of the network response buffered for sniffing purposes, + when attempting to sniff the response to determine if it should be blocked + as a cross-site document. Recorded after sniffing is attempted. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The number of bytes in the first network packet for a response with headers + that imply potential illegal cross-site access. Recorded when the first + network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having HTML + content type header and contents sniffed as HTML. Sampled with value of 1 + when the first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to their HTML contents. Sampled with value + 1 when the first network packet of a response of this type is received. + + + + + + Superseded by SiteIsolation.XSD.HTML.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.) among blocked + cross-site document responses due to their HTML contents. Sampled with a + resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.) among blocked + cross-site document responses due to their HTML contents. Sampled with a + resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to having HTML content type and nosniff + headers. Sampled with value 1 when the first network packet of a response of + this type is received. + + + + + + Superseded by SiteIsolation.XSD.HTML.NoSniffBlocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having HTML content type and nosniff + headers. Sampled with a resource type (0-14) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having HTML content type and nosniff + headers. Sampled with a resource type (0-17) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of not blocked responses despite having an HTML content type + header due to the failure of content sniffing. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses that may be parsed as JavaScript among not blocked + responses. Sampled with value 1 when the first network packet of a response + of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having JSON + content type header and contents sniffed as JSON. Sampled with value 1 when + the first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to their JSON contents. Sampled with value + 1 when the first network packet of a response of this type is received. + + + + + + Superseded by SiteIsolation.XSD.JSON.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their JSON contents. Sampled with a + resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their JSON contents. Sampled with a + resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to having JSON content type and nosniff + headers. Sampled with value 1 when the first network packet of a response of + this type is received. + + + + + + Superseded by SiteIsolation.XSD.JSON.NoSniffBlocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having JSON content type and nosniff + headers. Sampled with a resource type (0-14) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having JSON content type and nosniff + headers. Sampled with a resource type (0-17) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of not blocked responses despite having an JSON content type + header due to the failure of content sniffing. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses that may be parsed as JavaScript among not blocked + responses with a JSON content type header. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + MIME type codes for content type header values of potentially cross-site + document responses, excluding same-site or not http(s) urls. Sampled with a + MIME type code (0-4) when the first network packet of a response of this + type is received. + + + + + + Removed in May 2019. + + creis@chromium.org + lukasza@chromium.org + + Logs whether CORB blocking might have been caused by treating + |request_initiator| as opaque when |request_initiator_origin_lock| is + incompatible (as may be the case for HTML Imports). + + Logged when CORB allows or blocks a response, only when NetworkService is + enabled. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having Plain + content type header and contents sniffed as HTML. Sampled with value 1 when + the first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + responses due to their Plain.HTML contents. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Superseded by SiteIsolation.XSD.Plain.HTML.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.HTML contents. Sampled with + a resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.HTML contents. Sampled with + a resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having Plain + content type header and contents sniffed as JSON. Sampled with value 1 when + the first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to their Plain.JSON contents. Sampled with + value 1 when the first network packet of a response of this type is + received. + + + + + + Superseded by SiteIsolation.XSD.Plain.JSON.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.JSON contents. Sampled with + a resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.JSON contents. Sampled with + a resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to having Plain content type and nosniff + headers. Sampled with value 1 when the first network packet of a response of + this type is received. + + + + + + Superseded by SiteIsolation.XSD.Plain.NoSniffBlocked.RenderableStatusCode2 + in December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having Plain content type and nosniff + header. Sampled with a resource type (0-14) when the first network packet of + a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having Plain content type and nosniff + header. Sampled with a resource type (0-17) when the first network packet of + a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of not blocked responses despite having an Plain content type + header due to the failure of content sniffing. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses that may be parsed as JavaScript among not blocked + responses with a Plain content type header. Sampled with value 1 when the + first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having Plain + content type header and contents sniffed as XML. Sampled with value 1 when + the first network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to their Plain.XML contents. Sampled with + value 1 when the first network packet of a response of this type is + received. + + + + + + Superseded by SiteIsolation.XSD.Plain.XML.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with renderable HTTP status codes sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.XML contents. Sampled with + a resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with renderable HTTP status codes sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their Plain.XML contents. Sampled with + a resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of blocked cross-site document responses due to having XML content + type header and contents sniffed as XML. Sampled with value 1 when the first + network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with nonrenderable HTTP status codes among blocked + cross-site document responses due to their XML contents. Sampled with value + 1 when the first network packet of a response of this type is received. + + + + + + Superseded by SiteIsolation.XSD.XML.Blocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with renderable HTTP status codes sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their XML contents. Sampled with a + resource type (0-14) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with renderable HTTP status codes sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to their XML contents. Sampled with a + resource type (0-17) when the first network packet of a response of this + type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a nonrenderable HTTP status code among blocked + cross-site document responses due to having XML content type and nosniff + headers. Sampled with value 1 when the first network packet of a response of + this type is received. + + + + + + Superseded by SiteIsolation.XSD.XML.NoSniffBlocked.RenderableStatusCode2 in + December 2015. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having XML content type and nosniff + headers. Sampled with a resource type (0-14) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses with a renderable HTTP status code sub-categorized by + their requesting context type (e.g., image, script, etc.), among blocked + cross-site document responses due to having XML content type and nosniff + headers. Sampled with a resource type (0-17) when the first network packet + of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of not blocked responses despite having an XML content type header + due to the failure of content sniffing. Sampled with value 1 when the first + network packet of a response of this type is received. + + + + + + Removed in March 2018; in M67+, browser-process CORB policy is enabled. + + creis@chromium.org + + The count of responses that may be parsed as JavaScript among not blocked + responses with an XML content type. Sampled with value 1 when the first + network packet of a response of this type is received. + + + + + + Removed 2019/08. + + hansberry@chromium.org + + The duration of time between when Smart Lock successfully establishes a + secure channel connection to the host device, and receives an + "authenticated" remote status from it (i.e., the Smart Lock icon + becomes green). + + + + + + Removed 2019/08. + + hansberry@chromium.org + + The duration of time between when Smart Lock begins to try to find the host + device, and receives an "authenticated" remote status from it, + which allows the device to be unlocked (i.e., the Smart Lock icon becomes + green). + + See + MultiDevice.SecureChannel.BLE.Performance.StartScanToAuthenticationDuration.Background + and SmartLock.AuthenticationToReceiveUnlockableRemoteStatus.Unlock.Duration + for breakdowns of this metric. + + See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the + remote status from the host. + + + + + + Removed as of 09/2017. Replaced with + SoftwareReporter.Cleaner.DownloadStatusErrorCode. + + joenotcharles@google.com + + The HTTP response code for the Chrome Cleanup Tool download request. + + + + + + Removed 07-2020 because of lack of use. + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The state of software reporter cleaner tool runs. A value of "Not + Completed" can mean either the tool crashed, or the tool was still + running when Chrome checked. + + + + + + Removed on 2018-01-15. + + joenotcharles@google.com + + The number of attempts to download the Chrome Cleanup tool until it either + succeeds or fails. + + + + + + Removed on 2019-05-29. + + joenotcharles@google.com + + Indicates how the user was prompted to reboot the machine to complete a run + of the Chrome Cleanup Tool. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + The build version of the software reporter cleaner tool. + + + + + Deprecate in M82 as the histogram is renamed to + SoftwareReporter.ConfigurationErrors. + + joenotcharles@google.com + + Whether a configuration error prevented the experimental Software Reporter + from running. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time between the Chrome Cleaner dialog being shown and the dialog being + closed. + + + + + + Replaced 2017-08-01 with SoftwareReporter.PromptShownWithType. + + joenotcharles@google.com + + Whether the user has been prompted to run the Chrome Cleanup Tool. + + + + + + Removed as of 2017-11-01. Replaced with + SoftwareReporter.PromptDialogResponse. + + joenotcharles@google.com + Usage of the Software Removal Tool (SRT) Prompt. + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + Indicates the result of a reporter sequence once it ends. + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The amount of time it took to run the software reporter tool as reported by + the tool itself via the registry. Logged just after the software reporter + tool has finished. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Error encountered when reading the software reporter tool's start and end + times from the registry. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The registration and execution steps for the software reporter. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The total count of SRT log upload failures experienced by this machine for + all time. This value is reported at startup by Chrome and is capped at 64. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The longest run of upload failures logged by SRT runs. This value is + reported at startup by Chrome and is capped at 64. + + + + + + Removed 07-2020 due to lack of use + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The total count of successful SRT log uploads experienced by this machine + for all time. This value is reported at startup by Chrome and is capped at + 64. + + + + + + Reworked as Spellcheck.Windows.ChromeLocalesSupport.NoSupport and + Spellcheck.Windows.ChromeLocalesSupport.NativeOnly in M80. + + gujen@google.com + chrome-language@google.com + + Counts how many languages are currently added to Chrome by the user but are + not eligible for spellchecking because we have no Hunspell dictionaries for + them. This is recorded once during spellcheck initialization, and then once + each time the user changes their Chrome languages. + + + + + + Reworked as Spellcheck.Windows.SpellcheckLocalesSupport.HunspellOnly and + Spellcheck.Windows.SpellcheckLocalesSupport.NoSupport in M80. + + gujen@google.com + chrome-language@google.com + + Counts how many Hunspell spellcheck locales are currently enabled by the + user but are not supported by the Windows OS spellchecker because there are + no language packs installed for them. Locales that are not supported by + Hunspell are not counted. This is recorded once during spellcheck + initialization, and then once each time the user changes which spellcheck + languages are enabled. + + + + + + Moved to Sqlite.Error.AppCache in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite for the appcache db. + + + + + Removed in M74. + + costan@google.com + + Record times for INSERT/UPDATE/DELETE statements run outside of an explicit + transaction. + + + + + + Removed in M74. + + costan@google.com + Record time spent in explicit COMMIT statements. + + + + + Moved to Sqlite.Error.Cookie in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite the cookie db. + + + + + Moved to Sqlite.Error.DatabaseTracker in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite the websqldb tracker db. + + + + + Moved to Sqlite.Error.DomainBoundCerts in M-27. + + Please list the metric's owners. Add more owner tags as needed. + + Error codes returned by sqlite for the domain-bound certs db. + + + + + + Moved to Sqlite.Error.DomStorageDatabase in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite for the domstorage db. + + + + + Replaced 5/14/2013 by expanded Sqlite.Error histogram. + + Please list the metric's owners. Add more owner tags as needed. + SQLite extended SQLITE_IOERR codes for all databases. + + + + + Moved to Sqlite.Error.History in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite for the history db. + + + + + Removed in M74. + + costan@google.com + Record times for all statements run against the database. + + + + + Moved to Sqlite.Error.Quota in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite for the quota db. + + + + + Removed in M75. + + peria@chromium.org + costan@google.com + Size in kilobytes of pre-existing database at startup. + + + + + Removed in favor of Sqlite.Stats2 in M74. + + costan@google.com + Stats for different API calls in sql/. + + + + + Moved to Sqlite.Error.Text in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite the full text db. + + + + + Moved to Sqlite.Error.Thumbnail in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite for the thumbnail db. + + + + + Removed in M74. + + costan@google.com + + Record times for statements which could update the database file. Includes + commit and autocommit time. + + + + + + Removed 2018/02/06. + + shess@chromium.org + + Buffer sizes passed to browser-process SQLite VFS functions. + + + + + + Removed 2018/02/06. + + shess@chromium.org + + I/O operations measured by browser-process SQLite VFS wrapper. + + + + + + Moved to Sqlite.Error.Web in M-27. + + Please list the metric's owners. Add more owner tags as needed. + Error codes returned by sqlite the web db. + + + + + Removed 07/2017. Reference: crbug.com/708041 + + jww@chromium.org + + When resources are checked for mismatching integrity and whether the + mismatch forces a refetch. + + + + + + Removed 03/2020. Reference: crbug.com/1059826 + + carlosil@chromium.org + + When the "Learn more" link on an SSL interstitial is clicked, this + histogram records if the navigation succeded, if it failed with an + interstitial, or if it failed with a different error. + + + + + + Removed as of 07/2016. Replaced with SSL.ExpectCTReportFailure2. + + estark@chromium.org + + Sites can opt in to Expect CT, a reporting feature that sends a report + whenever a TLS connection does not have valid Certificate Transparency + information associated with it. This records the error code when Chrome + fails to send an Expect CT report. + + + + + + Removed December 2017 (M65). This information in this histogram can be found + in LoginCustomFlags (for users who have set a flag) or by filtering to users + with the MarkHttpAs feature enabled (for seeing the field trial breakdown). + + estark@chromium.org + felt@chromium.org + + Reports whether the user has selected to mark HTTP origins with an + experimental UI treatment (such as showing a warning on HTTP pages that + collect sensitive information). This histogram is recorded whenever the + security level (the overall security state of a page, roughly corresponding + to the lock icon) is computed for an HTTP page. + + + + + + Removed 09/2016 and replaced with SSL.MarkHttpAsStatus. + + palmer@chromium.org + + Reports whether the user has selected to mark non-secure origins as Neutral + (the status quo), Dubious, or Non-Secure. + + + + + + Removed in M60. Roughly 50% of Chrome startups that had *any* pending + minidumps had at least one pending minidump without any logcat output. About + 5% had multiple minidumps without any logcat output. + + isherman@chromium.org + + The number of un-uploaded minidumps present in the Android Crash Reports + directory. Each minidump file (should) correspond to a crash. This is + recorded on startup, just prior to initiating uploading for these minidumps. + This is intended as a temporary metric, to be removed around M60: + http://crbug.com/699785 + + + + + + Removed in M60. Roughly 50% of Chrome startups that had *any* pending + minidumps had at least one pending minidump without any logcat output. About + 5% had multiple minidumps without any logcat output. + + isherman@chromium.org + + The number of un-uploaded minidumps present in the Android Crash Reports + directory that do not yet have logcat output attached. Each minidump file + (should) correspond to a crash. This is recorded on startup, just prior to + initiating uploading for all pending minidumps. This is intended as a + temporary metric, to be removed around M60: http://crbug.com/699785 + + + + + + Removed 04/2019 as we no longer record it in favour of the two variants + below. + + mheikal@chromium.org + smaier@chromium.org + wnwen@chromium.org + + Records the number of minidumps processed by Crashpad, split by process + type. This metric is similar to one that could be computed server-side based + on received crash uploads; but the client-side metric also includes any + minidumps that were not successfully uploaded. + + + + + + Removed 04/2020 (data for go/site-isolation-stability has been collected + long time ago; nobody on chrome-stability@ spoke in defense of this + histogram). + + lukasza@chromium.org + + The age of a crashed extension process. Not logged on iOS. Logged together + with CrashExitCodes.Extension. + + + + + + Removed 04/2020 (data for go/site-isolation-stability has been collected + long time ago; nobody on chrome-stability@ spoke in defense of this + histogram). + + lukasza@chromium.org + + The age of a crashed extension process. Not logged on iOS. Logged together + with CrashExitCodes.Renderer. + + + + + + Removed 09/2019 after having collected enough data. + + eugenebut@chromium.org + olivierrobin@chromium.org + + Recorded when Chrome for iOS attempts to create a config for synthetic crash + report. Used to debug the feature, which suppose to upload synthetic crash + report using Breakpad. + + + + + + Removed 5/2019 after having collected enough data to analyze jank. + + chengx@chromium.org + wittman@chromium.org + + Amount of time taken to deserialize all pending call stack profiles. + + + + + + Removed 11/2018 as we no longer record this metric. + + chengx@chromium.org + wittman@chromium.org + + Amount of time taken to deserialize a call stack profile string. + + + + + + Removed 11/2018 as we no longer record this metric. + + chengx@chromium.org + wittman@chromium.org + Amount of time taken to serialize a call stack profile. + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the bookmarks bar view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the depth of a folio when it is selected in the clipper. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the number of folios visible when a folio is selected in the clipper. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of folios when the clipper is opened. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the folio view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips with Google related urls (points to internal Google + resources). Logs every time user goes to chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips with Google related urls within first 20 (points to + internal Google resources). Logs every time user goes to chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips with images. Logs every time user goes to + chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips with images within first 20. Logs every time user goes + to chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when a bookmark is launched from the + bookmarks bar view. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when a bookmark is launched from the folio + view. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when a bookmark is launched from the search + view. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when a bookmark is launched from the smart + group view. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when a bookmark is launched from the + timeline view. + + + + + + Removed 01/2020 as we no longer record this metric. + + lpromero@chromium.org + + Logs every time a bookmark is launched from an assortment of different UI + surfaces with Stars, the new bookmarks UI. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips without images or snippets. Logs every time user goes to + chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Percentage of clips without images or snippets within first 20. Logs every + time user goes to chrome://bookmarks. + + + + + + Removed 01/2020 as we no longer record this metric. + + yefim@chromium.org + + Logs number of bookmark nodes every time stars extension is loaded. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the profile view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + jbbegue@chromium.org + + Count the actions performed by the user on the stars promo panel currently + only on android and ios. + + + + + + Removed 01/2020 as we no longer record this metric. + + lpromero@chromium.org + + A boolean that indicates if a salient image was found for a displayed + bookmark. It is recorded every single time a bookmark is displayed. That + way, this histogram shows the proportion of bookmarks the user sees with an + image. This is used only with Stars, the new bookmarks UI. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the search view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the smart group view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + + Logs the approx number of clips when the timeline view is activated. + + + + + + Removed 01/2020 as we no longer record this metric. + + accamed@google.com + Logs the extension version the user is using. + + + + + This metric was deprecated in M68 in favour of + "Startup.Android.Cold.TimeToFirstContentfulPaint.Tabbed". It has + moved out of experimental and records a smaller range of numbers (medium + times instead of long times). The ".Tabbed" suffix is added since + the histogram is being tracked for WebApkActivity using the + ".WebApk" suffix. + + pasko@chromium.org + alexilin@chromium.org + + Android: The time from the activity creation point to the first contentful + paint of the first loaded page. It's not recorded when the first loaded page + is non http(s) page like a chrome error page, a new tab page, a blank page. + It's also not recorded if the application wasn't in the foreground since the + start till the end of event. + + + + + + This metric was deprecated in M68 in favour of + "Startup.Android.Cold.TimeToFirstNavigationCommit.Tabbed". It has + moved out of experimental and records a smaller range of numbers (medium + times instead of long times). The ".Tabbed" suffix is added since + the histogram is being tracked for WebApkActivity using the + ".WebApk" suffix. + + pasko@chromium.org + alexilin@chromium.org + + Android: The time from the activity creation point to the moment the first + navigation is committed, i.e. when renderer gets the first byte of the + document. It's not recorded when the first loaded page is non http(s) page + like a chrome error page, a new tab page, a blank page. It's also not + recorded if the application wasn't in the foreground since the start till + the end of event. + + + + + + Removed 03/2018 with Mash AppList refactoring. + + tapted@chromium.org + + Time for a newly created browser process to perform the first paint of the + app launcher, when started with the --show-app-list flag and with no + currently running Chrome processes. + + + + + + Removed 03/2018 with Mash AppList refactoring. + + tapted@chromium.org + + Time for a running browser process to perform the first paint of the app + launcher. Measured from the time a second Chrome process started, which sent + its --show-app-list command line argument to the already-running process and + will soon exit. + + + + + + Removed as of 02/2020. + + rkaplow@chromium.org + + Measured when Chrome is invoked, this counts the number of URLs passed via + command line. Note that this handles the case of a URL passed to Chrome + starting up, or when a running Chrome is given the message to open a new + URL. + + + + + + Removed 01/2020. Data is not used. + + fdoray@chromium.org + + Time from the ChromeMain() entry in the browser process to the first + RendererMain() entry. + + + + + + Removed 2/2018, as MessageLoopStart is after MainNavigationStart with + browser-side navigation. + + asvitkine@chromium.org + + Time between Startup.BrowserMessageLoopStartTime and + Startup.FirstWebContents.MainNavigationStart. Recorded explicitly to allow + easy breakdown of Startup.FirstWebContents.MainNavigationStart when + diagnosing issues. + + + + + + Removed 1/2016. + + chrisha@chromium.org + + The number of hard faults incurred in the browser process from startup to + start of the main thread's message loop on first run. This is only reported + on Windows 7 and greater. + + + + + + Removed 12/2015. No longer tracked because values collected on stable show + that the function pretty much never fails (succeeds 99.9996% of the time). + + chrisha@chromium.org + fdoray@chromium.org + + If OS support was detected (Windows 7 and greater) indicates whether it was + possible to determine the number of hard faults that have occurred in the + process from startup to start of the main thread's message loop. This can + fail because the underlying call is inherently racy. + + + + + + Removed 12/2016. crbug.com/634408 + + fdoray@chromium.org + gab@chromium.org + + Time from main entry to the start of the main thread's message loop. This + stat is only recorded after 7 minutes of OS uptime to try to mitigate the + variance resulting from Chrome being autostarted. Replaced with + Startup.BrowserMessageLoopStartTimeFromMainEntry2 which is recorded all the + time. + + + + + + Removed 12/2016. crbug.com/634408 + + fdoray@chromium.org + gab@chromium.org + + Time from main entry to the start of the main thread's message loop on first + run. This stat is only recorded after 7 minutes of OS uptime to try to + mitigate the variance resulting from Chrome being autostarted. Replaced with + Startup.BrowserMessageLoopStartTimeFromMainEntry.FirstRun2 which is recorded + all the time. + + + + + + Removed 01/2020. Replaced with Startup.BrowserMessageLoopStartTime.FirstRun. + + fdoray@chromium.org + gab@chromium.org + + Time from main entry to the start of the main thread's message loop on first + run. + + + + + + Removed 2018-01 in favor of + Startup.BrowserMessageLoopStartTimeFromMainEntry3 which does not involve a + conversion from Time to TimeTicks. + + fdoray@chromium.org + gab@chromium.org + + Time from main entry to the start of the main thread's message loop. + + + + + + Removed 01/2020. Startup.BrowserMessageLoopStartTime has similar data. + + fdoray@chromium.org + gab@chromium.org + + Time from main entry to the start of the main thread's message loop. + + + + + + Removed 01/2020. Data is not used. + + fdoray@chromium.org + + Time taken to open the initial tab or to restore tabs from previous session. + + + + + + Removed 7/2015. To be replaced with Cast events. + + jeremy@chromium.org + + The elapsed time from the ChromeCast application launch to the first video + frame displayed. + + + + + + Removed in M-41. + + erikchen@chromium.org + + An experimental metric only collected on the dev and canary channels. + Measure the elapsed time from process launch to the first main frame load of + the first web contents. Uses significantly more buckets, with reduced + ranges. + + + + + + Moved to Startup.FirstWebContents.MainFrameLoad in M-41. + + erikchen@chromium.org + + An experimental metric only collected on the dev and canary channels. + Measure the elapsed time from process launch to the first main frame load of + the first web contents. Uses standard bucket ranges. + + + + + + Removed in M-41. + + erikchen@chromium.org + + An experimental metric only collected on the dev and canary channels. + Measure the elapsed time from process launch to the first non-empty paint of + the first web contents. Uses significantly more buckets, with reduced + ranges. + + + + + + Moved to Startup.FirstWebContents.NonEmptyPaint in M-41. + + erikchen@chromium.org + + An experimental metric only collected on the dev and canary channels. + Measure the elapsed time from process launch to the first non-empty paint of + the first web contents. Uses standard bucket ranges. + + + + + + Replaced by Startup.FirstCommitNavigationTime2 + + pasko@chromium.org + + [Android only] The time from the earliest entry point in the browser process + to the moment the first navigation is committed, i.e. when renderer gets the + first byte of the document. + + + + + + Replaced with Startup.FirstCommitNavigationTime3 on 6/2017 + + pasko@chromium.org + wnwen@chromium.org + + [Android only] The time from the first foreground entry point in the app to + the moment the first navigation is committed, i.e. when renderer gets the + first byte of the document. + + + + + + Replaced with Startup.Android.Experimental.Cold.TimeToFirstNavigationCommit + on 11/2017 + + pasko@chromium.org + wnwen@chromium.org + + [Android only] The time from the first foreground entry point in the app to + the moment the first navigation is committed, i.e. when renderer gets the + first byte of the document. + + + + + + Removed with 3/2016 with M48. + + erikchen@chromium.org + gab@chromium.org + + [Desktop] DEPRECATED (but kept as a known basis until M48 is phased out). + Measure the elapsed time from process launch to the first main frame load of + the first web contents. Deprecated in favor of + Startup.FirstWebContents.MainFrameLoad2 which now avoids counting ill-cases + (ref. FirstWebContentsProfiler::FinishReason). + + + + + + Removed with M77. Startup.FirstWebContents.NonEmptyPaint3 is a better + indicator of startup time as perceived by users. + + fdoray@chromium.org + gab@chromium.org + + [Desktop] Measure the elapsed time from process launch to the first main + frame load of the first web contents. Only comprised of cases where the + initial foreground tab gets to complete its rendering task unimpeded (an + improvement over Startup.FirstWebContents.MainFrameLoad). + + + + + + Removed with 3/2016 with M48. + + erikchen@chromium.org + gab@chromium.org + + [Desktop] DEPRECATED (but kept as a known basis until M48 is phased out). + Measure the elapsed time from process launch to the first non- empty paint + of the first web contents. Deprecated in favor of + Startup.FirstWebContents.NonEmptyPaint2 which now avoids counting ill-cases + (ref. FirstWebContentsProfiler::FinishReason). + + + + + + Replaced with Startup.FirstWebContents.NonEmptyPaint3 on 06/2020, which uses + application start time instead of process creation time to reduce noise. + + fdoray@chromium.org + gab@chromium.org + chrome-analysis-team@google.com + + [Desktop] Measure the elapsed time from process launch to the first non- + empty paint of the first web contents. Only comprised of cases where the + initial foreground tab gets to complete its rendering task unimpeded (an + improvement over Startup.FirstWebContents.NonEmptyPaint). + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the execution time for a single task to execute on UI if + it was not possible to execute UI tasks under 1/60s within certain limits, + after WebContents was painted at least once. This is recorded at most once + per Chrome launch. Used as a measure of responsiveness on startup. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the elapsed time for a single task to execute on UI if it + was not possible to execute it under 1/60s within certain limits, 10 second + after first WebContents was painted at least once. This is recorded at most + once per Chrome launch. Used as a measure of responsiveness on startup. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the elapsed time for a single task to execute on UI if it + was not possible to execute it under 1/60s within certain limits, 1 second + after first WebContents was painted at least once. This is recorded at most + once per Chrome launch. Used as a measure of responsiveness on startup. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the elapsed time it takes for a task to execute on UI + under 1/60s after first WebContents was painted at least once. This is + recorded at most once per Chrome launch. Used as a measure of responsiveness + on startup. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the elapsed time it takes for a task to execute on UI + under 1/60s, 10 second after the first WebContents was painted. This is + recorded at most once per Chrome launch. Used as a measure of responsiveness + on startup. + + + + + + Removed 10/2015. + + gayane@chromium.org + + [Desktop] Measures the elapsed time it takes for a task to execute on UI + under 1/60s, 1 second after the first WebContents was painted. This is + recorded at most once per Chrome launch. Used as a measure of responsiveness + on startup. + + + + + + Removed 7/2015. To be replaced with Cast events. + + jeremy@chromium.org + + The elapsed time from the Fling application launch to the first video frame + displayed. + + + + + + Removed 12/2011. Merged into MobileSessionStartType. + + jeremy@chromium.org + Whether a startup is a resume (vs a cold start). + + + + + Removed 12/2016. crbug.com/634408 + + fdoray@chromium.org + gab@chromium.org + + Time from the main() function in chrome.exe to chrome.dll's main(). This + stat is only recorded after 7 minutes of OS uptime to try to mitigate the + variance resulting from Chrome being autostarted. Replaced with + Startup.LoadTime.ExeMainToDllMain2 which is recorded all the time. + + + + + + Removed 03/2020. Replaced with Startup.LoadTime.ApplicationStartToChromeMain + which applies to most platforms. + + fdoray@chromium.org + gab@chromium.org + + Time from the main() function in chrome.exe to chrome.dll's main(). + + + + + + Removed 12/2016. crbug.com/634408 + + fdoray@chromium.org + gab@chromium.org + + Time from the process creation to chrome.dll's main(). This stat is only + recorded after 7 minutes of OS uptime to try to mitigate the variance + resulting from Chrome being autostarted. Replaced with + Startup.LoadTime.ProcessCreateToDllMain2 which is recorded all the time. + + + + + + Removed 03/2020. Replaced with + Startup.LoadTime.ProcessCreateToApplicationStart which applies to most + platforms. + + fdoray@chromium.org + gab@chromium.org + Time from the process creation to chrome.dll's main(). + + + + + Removed 12/2016. crbug.com/634408 + + fdoray@chromium.org + gab@chromium.org + + Time from the process creation to executing the main() function in + chrome.exe. This stat is only recorded after 7 minutes of OS uptime to try + to mitigate the variance resulting from Chrome being autostarted. Replaced + with Startup.LoadTime.ProcessCreateToExeMain2 which is recorded all the + time. + + + + + + Removed 03/2020. Now covered by + Startup.LoadTime.ProcessCreateToApplicationStart and + Startup.LoadTime.ApplicationStartToChromeMain. + + fdoray@chromium.org + gab@chromium.org + + Time from the process creation to executing the main() function in + chrome.exe. + + + + + + Removed as of 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the first untracked section of + ChromeBrowserMainParts::PreMainMessageLoopRunImpl. + + + + + + Removed as of 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the second untracked section of + ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android. + + + + + + Removed as of 7/2019. + + rkaplow@chromium.org + + The amount of time that elapsed during the third untracked section of + ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android. + + + + + + Removed as of 2/2015. + + rkaplow@chromium.org + + The amount of time that elapsed during + ChromeBrowserMainParts::PreMainMessageLoopRunImpl. + + + + + + Removed 8/2019. See startup_metric_utils.cc for a summary of old data. + + fdoray@chromium.org + gab@chromium.org + + The number of startups the current version has been through. Reported once + per Chrome session, on startup. Any user that reports X for this version + will also have previously reported [1,X-1] for this version through the + previous X-1 Chrome sessions. + + + + + + Removed 2018-03. + + tapted@chromium.org + + Time for a newly created browser process to reach the code that starts + showing the app launcher, when started with the --show-app-list flag and + with no currently running Chrome processes. + + + + + + Removed 2018-03. + + tapted@chromium.org + + Time for a running browser process to reach the code that starts showing the + app launcher. Measured from the time a second Chrome process started, which + sent its --show-app-list command line argument to the already-running + process and will soon exit. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to load bookmarks from disk. This measurement is only sent for + startups that take >10 seconds after an uptime of 7 minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to finish initialization of the extension service including + loading built-in extensions. This measurement is only sent for startups that + take >10 seconds after an uptime of 7 minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time the final stages of profile initialization taking including + initialization of profile keyed services. This measurement is only sent for + startups that take >10 seconds after an uptime of 7 minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to load the NSS libraries and initialize it. This measurement + is only sent for startups that take >10 seconds after an uptime of 7 + minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to load preferences from disk. This measurement is only sent + for startups that take >10 seconds after an uptime of 7 minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to initialize the ProfileIOData object - this includes + initialization of the cookie store. This measurement is only sent for + startups that take >10 seconds after an uptime of 7 minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to load the safe browsing database from disk. This measurement + is only sent for startups that take >10 seconds after an uptime of 7 + minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes to initialize the safe browsing service. This measurement is + only sent for startups that take >10 seconds after an uptime of 7 + minutes. + + + + + + Removed 06/2015. + + jeremy@chromium.org + + Time it takes for session restore to finish initiating creation of restored + tabs and windows. This measurement is only sent for startups that take + >10 seconds after an uptime of 7 minutes. + + + + + + Removed 02/2015. Startup.StartupBrowserCreator_Start is more useful. + + rkaplow@chromium.org + + The amount of time that elapsed during + StartupBrowserCreator::ProcessCmdLineImpl. + + + + + + Remove 01/2020. Data is no longer used. + + fdoray@chromium.org + + The time elapsed between system boot and Chrome browser process launch. This + is recorded just before the main message loop starts. + + + + + + Removed 06/2019. + + feuunk@chromium.org + + The time of day in GMT that the startup was performed. This is logged in + HHMM format, with the minutes rounded down to the nearest 10 minute + interval. + + This can be used to make traffic estimates for requests made from startup. + + + + + + Removed 08/2019. See startup_metric_utils.cc for a summary of old data. + + fdoray@chromium.org + + Time elapsed since the last startup that went up to the main message loop + start. This is recorded just before the main message loop starts. + + + + + + Removed 01/2020. The data is no longer used. + + fdoray@chromium.org + + Time for a running browser process to start processing the command line + passed in by a second Chrome process, which just sent its command line + arguments to the already-running process and will soon exit. Measured from + the time the second Chrome process started. + + + + + + Removed as of 10/2014. + + dschinazi@chromium.org + src/net/OWNERS + + Time duration measured from the time the startup timebomb was started and + when it went off. + + + + + + No longer relevant. There are almost never any failures. + + dmurph@chromium.org + + Recorded when we create the blob storage directory for the blob storage + system. When we need to write blob data to files, we create this directory + if it doesn't exist. We write blob data to files when either we have a new + blob that's larger than our memory limit, or we're approaching our in-memory + limit for blob storage. + + + + + + Removed as of 3/2016. Use Storage.Blob.Broken to see the fraction of blobs + that are broken, and Storage.Blob.BrokenReason for the number of broken + blobs that are broken because of memory constraints. + + dmurph@chromium.org + + True if a created blob exceeded the internal in-memory storage memory limit + for blobs. + + + + + + Removed as of 12/18. Metric wasn't used for anything and wasn't useful. + + dmurph@chromium.org + + The number of blob items in a blob, recorded at blob construction. (Blobs + are immutable, so this won't change afterwards). + + + + + + Removed as of 12/18. Use Storage.Blob.MaxDiskSpace2 instead. + + dmurph@chromium.org + + Records the calculated max disk space the blob storage system can use. + Recorded on storage partition initialization. + + + + + + Not an accurate way to measure the normal max blob usage. + + dmurph@chromium.org + + Records the total in-memory storage size of blobs before a blob item is + appended. Can be subtracted by Storage.Blob.StorageSizeBeforeAppend to find + the true distribution of blob storage sizes. + + + + + + Not an accurate way to measure the normal max blob usage. + + dmurph@chromium.org + + Records the total in-memory storage size of blobs before a blob item is + appended. Can be subtracted from Storage.Blob.StorageSizeAfterAppend to find + the true distribution of blob storage sizes. + + + + + + Removed on 12/18. Metric wasn't used for anything and wasn't useful. + + dmurph@chromium.org + + The size in KB of items (or parts of items) appended to blobs. + + + + + + Removed on 12/18. Metric wasn't used for anything and wasn't useful. + + dmurph@chromium.org + + The size in KB of items (or parts of items) appended to blobs that come from + the slicing of other blobs. This happens when using Blob.slice, where we are + using a part of an item in the original blob (not the whole item). + + + + + + Removed on 12/18. Metric was always false. + + dmurph@chromium.org + + True if the file size of a filesystem object on blob append is unknown + (which means the full file), or false if a specific file length was + populated. Recorded in BlobStorageContext when we are adding a filesystem + item to a blob. + + + + + + Removed in 2020-04. + + mek@chromium.org + chrome-owp-storage@google.com + The number of bytes read. Recorded on each read. + + + + + Removed in 2020-04. + + mek@chromium.org + chrome-owp-storage@google.com + The number of bytes written. Recorded on each write. + + + + + No longer emitted. + + dmurph@chromium.org + mek@chromium.org + + Records if a blob attempted to be written to IndexedDB used the + base::CopyFile optimization. Recorded for every blob attempted to be written + to IndexedDB. + + + + + + Removed 2019-02, no longer used. + + futhark@chromium.org + + Microseconds spent in StyleSheetContents::ParseAuthorStyleSheet. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 07/2018, no longer used. + + csharrison@chromium.org + + Tracks % of lazy rules that ended up needing to be parsed. A sheet logs + counts into this histogram as it is parsed (i.e. as properties are parsed + lazily). Once a certain percent of rules have been parsed, we log a count + immediately. Note that this implies that a stylesheet which uses all of its + rules will log counts in every bucket. + + + + + + Removed 07/2018, no longer used. + + csharrison@chromium.org + + Tracks the total number of rules that have parsing lazily deferred in an + author style sheet. + + + + + + Removed 07/2018, no longer used. + + csharrison@chromium.org + + Tracks the total number of rules that have parsing lazily deferred in an + author style sheet, for sheets that ended up needing all their rules. + + + + + + Removed 07/2018, replaced by Style.RecalcTime and + Style.RebuildLayoutTreeTime. + + futhark@chromium.org + + Microseconds spent in Document::UpdateStyle. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed June 2018 in favor of SubresourceFilter.Actions2 + + csharrison@chromium.org + + Counts of various UI and user action events related to the + SubresourceFilter. This will be triggered in response to Content Settings + changes, as well as when portions of the UI are shown or interacted with. + Main frame navigations are also tracked for ease of comparison and analysis. + + + + + + Removed April 2019 + + csharrison@chromium.org + jkarlin@chromium.org + + Logs the delay the ad delay throttle added to a request. Logged for every + subresource request that was delayed. + + + + + + Removed April 2019 + + csharrison@chromium.org + jkarlin@chromium.org + + Logs the expected delay the ad delay throttle added to a request. This is + the delay imposed assuming no task queuing delay. Logged for every + subresource request that was delayed. + + + + + + Removed April 2019 + + csharrison@chromium.org + jkarlin@chromium.org + + Logs the task queuing delay the ad delay throttle added to a request. This + is the actual delay minus the expected delay. Logged for every subresource + request that was delayed. + + + + + + Removed July 2018. Replaced with Ads.Features.AdResourceIsIsolated. + + csharrison@chromium.org + jkarlin@chromium.org + + For a given ad request, logs information related to whether it is isolated + from the top-level context. Logged per ad subresource request. + + + + + + Removed July 2018. Replaced with Ads.Features.ResourceIsSecure. + + csharrison@chromium.org + jkarlin@chromium.org + + For a given request, logs information related to whether it is marked as an + ad, and whether it is secure (e.g. https). Logged per subresource request. + + + + + + Removed July 2019. + + csharrison@chromium.org + + Records the total time the activation state navigation throttle within a + document is delayed while calculating activation. Recorded at resume time. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed July 2019. + + csharrison@chromium.org + + Records the total time the activation state navigation throttle within a + main frame document is delayed while calculating activation. Recorded at + resume time. + + + + + + Expired in M77, then deprecated in July 2019. + + engedy@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total number of subresource + loads that have been disallowed. This only differs from `MatchedRules` when + filtering is performed in dry-run mode. + + + + + + Expired in M77, then deprecated in July 2019. + + engedy@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total number of subresource + loads that have been evaluated. This only differs from 'Total' when the + document is subject to a deactivating rule with DOCUMENT activation type. + + + + + + Expired in M78, then deprecated in July 2019. + + engedy@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total number of subresource + loads that have matched filtering rules. This only differs from `Disallowed` + when filtering is performed in dry-run mode. + + + + + + Expired in M77, then deprecated in July 2019. + + engedy@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total number of subresource + loads that have gone through the subresource filtering pipeline. + + + + + + Removed in August 2019. Replaced by SubframeFilteringDelay.Disallowed2. + + csharrison@chromium.org + + Records the total time a subframe navigation was delayed while calculating + whether it should be disallowed or not. Logged for all navigations that were + disallowed or would be disallowed. + + + + + + Removed in July 2019. + + pkalinnikov@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total thread CPU time spent on + processing subresource requests in allowLoad. + + Note: this histogram is emitted for all clients, both ones which have + high-resolution timer available and those which don't. + + + + + + Removed in July 2019. + + pkalinnikov@chromium.org + + Whenever a document load is finished in a main frame or subframe with + subresource filtering activated, records the total real time spent on + processing subresource requests in allowLoad, including the time spent on + waiting or being descheduled. + + Note: this histogram is emitted for all clients, both ones which have + high-resolution timer available and those which don't. + + + + + + Removed in favor of the Verify2 metric + + csharrison@chromium.org + + The total time it took to verify the indexed ruleset in the browser process. + Logged every time verification occurs, which usually occurs when the first + page with activation is navigated to. + + + + + + Removed in favor of SubresourceFilter.PageLoad.Activation.RedirectPosition2 + + ericrobinson@chromium.org + + For pages that trigger Safe Browsing activations (not including dry runs), + records the position in the redirect chain for the page the activation was + triggered by. If SubresourceFilterConsiderRedirects is disabled, then always + returns "Only navigation". + + + + + + Metric is broken and will be replaced by + ContentSettings.Popups.StringBlocked.NumBlocked. This only logged values for + sites which are also activated for subresource filtering, when most sites + will probably only be marked for popup blocking. + + csharrison@chromium.org + + Records the number of popups blocked per page load due to subresource filter + logic. Recorded when a new main frame navigation commits. Note that this + histogram is recorded for all pages which are activated by the subresource + filter, including ones which do not trigger the stronger popup blocker. + + + + + + Removed in favor of SubresourceFilter.PageLoad.ActivationList. + + melandory@chromium.org + + Records, for each main frame navigation, whether the last URL in the + redirect chain matched the Safe Browsing blacklist specified by the + histogram suffix. + + + + + + Removed May 2018 in favor of SubresourceFilter.PageLoad.ActivationDecision + + csharrison@chromium.org + + Logged when the first resource is disallowed from a page with forced + activation. For example, if the devtools ad blocking option is set. + + + + + + Removed May 2018 + + melandory@chromium.org + + Total number of server redirects during the navigation. This histogram is + recorded in several for every list where subresource fiter is active. + + + + + + Obsolete as of April 2017, since the don't have correct data to record + anymore. + + melandory@chromium.org + + For each main frame navigation, records a pattern that indicates which URLs + in the redirect chain matched Safe Browsing blacklists, and which did not. + For example, for the redirect chain A-B-C-D metric tracks: 1. If initial URL + (A) was on a Safe Browsing blacklist. 2. If any if middle urls (B, C) were + on a Safe Browsing blacklist. 3. If committed URL (B) was on a Safe Browsing + blacklist. This histogram is recorded in several flavours: with prefix + SubresourceFilterOnly in case the redirect chain contains url from the Safe + Browsing SubresourceFilter list and without the prefix for all other + redirect chains. + + + + + + Removed in May 2018 (M69). We have enough data to show that the redirect + speculations we do are necessary, especially for Android. + + csharrison@chromium.org + + The navigation delay that would have been imposed by the subresource filter + on a given navigation due to Safe Browsing checks if redirect speculation + was removed. Removing this feature would cause more delay if a navigation + has redirects. + + + + + + Removed in favor of the whitelisted bucket in SubresourceFilter.Actions2 + + melandory@chromium.org + + Number of times the user has requested a reload for the page by clicking on + the reload button. + + + + + + Removed in favor of SubresourceFilter.Action + + melandory@chromium.org + + Number of times Safebrowsing Subresource Filter decided to toggle visibility + of the prompt. + + + + + + Removed in May 2018 in favor of the more general + SB2.RemoteCall.CheckDispatchTime. + + csharrison@chromium.org + + The microseconds it took to dispatch the Safe Browsing check. This includes + IPC descheduling delays to communicate with SafetyNet on Android, and + synchronous db checks on desktop. + + Note: this histogram is emitted for all clients, both ones which have + high-resolution timer available and those which don't. + + + + + + Removed in May 2019 in favor of the TotalCheckTime variant. + + csharrison@chromium.org + + The time an individual Safe Browsing URL check took before finishing. Logged + when a check is complete or cancelled due to a timeout. + + + + + + Long removed. + + aberent@chromium.org + + Time to get the response to requesting whether a URL should be accessible to + the supervised user, when Chrome was not previously running. + + + + + + Long removed. + + aberent@chromium.org + + Time to get the response to requesting whether a URL should be accessible to + the supervised user, when Chrome was already running. + + + + + + Long removed. + + aberent@chromium.org + + True if a request to find out whether a URL should be accessible to a + supervised user timed out. + + + + + + Renamed to SupervisedUsers.Extensions2 in M84. + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Records the progress of supervised users as they try to install Chrome + extensions. New extension approval granted count increments when the + custodian initially grants approval to install the extension. New version + approval granted count increments when the supervised user approves a newer + version of an existing extension. Removed count increments when the + supervised user removes an extension. + + + + + + Removed in April 2020 (M84). + + tobyhuang@chromium.org + cros-families@google.com + + Records the progress of supervised users as they try to install Chrome + extensions during the COVID-19 crisis, before the parent approval dialog is + ready. kAllowlistMiss count increments whenever we query for an extension id + in the allowlist and it is not found. kAllowlistHit count increments + whenever the extension id is found in the allowlist. + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during app association (M18 and earlier were mispelled with this + histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of apps run failures, used to compare failure rates between data types + for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by AppSettingsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of app settings association failures. + + + + + Replaced by AppsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of app association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of app association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed in M80. + + jkrcal@chromium.org + mastiz@chromium.org + Time taken during association of this data type. + + + + + Removed 2018-04, Sync attachments were never launched. + + maxbogue@chromium.org + Whether attachment checksums match on download or not. + + + + + Removed 2018-04, Sync attachments were never launched. + + maxbogue@chromium.org + Response or error codes from downloading sync attachments. + + + + + Removed 2018-04, Sync attachments were never launched. + + maxbogue@chromium.org + + The total time a download takes including request and server overhead. + + + + + + Removed 2018-04, Sync attachments were never launched. + + maxbogue@chromium.org + The result of initializing the sync attachment store. + + + + + Removed 2018-04, Sync attachments were never launched. + + maxbogue@chromium.org + Response or error codes from uploading sync attachments. + + + + + Removed in M85. + + mastiz@chromium.org + mmoskvitin@google.com + + Enumeration of results from attempting to migrate Sync's nigori node and its + encryption keys to support keystore. + + + + + + Removed in M53. + + zea@chromium.org + + Age of all auth tokens rejected by the invalidation server. Measured from + the time they were created. + + + + + + Removed in M53. + + zea@chromium.org + + Age of auth tokens younger than one hour that were rejected by the + invalidation server. Measured from the time they were created. + + + + + + Removed in M53. + + zea@chromium.org + Time taken during initial authorization. + + + + + Removed in M53. + + zea@chromium.org + + Age of all auth tokens rejected by the sync server. Measured from the time + they were created. + + + + + + No longer relevant since transition to OAuth. + + zea@chromium.org + + Age of auth tokens younger than one hour that were rejected by the sync + server. Measured from the time they were created. + + + + + + Removed in M77. + + jkrcal@chromium.org + treib@chromium.org + + Reported for autofill profile sync once per every locally committed entity + creation/update. It breaks down the origin of such a local change. + + + + + + Removed in M77. + + jkrcal@chromium.org + treib@chromium.org + + Reported for autofill profile sync once per every locally committed entity + deletion. It breaks down the origin of such a local deletion. + + + + + + Replaced by Sync.AutofillProfilesAssociationTime. + + zea@chromium.org + + Time taken during autofill profile association (M18 and earlier were + mispelled with this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of autofill profiles run failures, used to compare failure rates + between data types for a particular profile (see other Sync*RunFailures + histograms). + + + + + + Replaced by AutofillProfilesConfigureFailure. See crbug.com/478226. + + zea@chromium.org + + Enumeration of types of autofill profile association failures. + + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of autofill profile association failures (M18 and + earlier were mispelled with this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of autofill (autocomplete) run failures, used to compare failure rates + between data types for a particular profile (see other Sync*RunFailures + histograms). + + + + + + Replaced by AutofillConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of autofill association failures. + + + + + Removed in M85. + + mastiz@chromium.org + mmoskvitin@google.com + + Number of times this client has overwritten the nigori node to update the + encryption keys without a user action (during this instantiation of Chrome). + + + + + + Removed in M53. + + zea@chromium.org + + Compares sync's has_setup_completed pref against the set of types actually + restored from the sync DB. Mismatches should be rare. + + + + + + Removed in M53. + + zea@chromium.org + + Number of bad requests since application startup, when the Sync error + infobar asking the user to update their account details is displayed. + + + + + + Removed as of m18 + + zea@chromium.org + Time taken during bookmark association. + + + + + Removed as of 12/2019. Replaced by Sync.BookmarkGUIDSource2 which fixes a + bug affecting bucket 2 (field left empty) which counted permanent nodes. + + psivieroleitao@google.com + mamir@chromium.org + mastiz@chromium.org + + Records the source of GUIDs for remote bookmark updates, recorded when + processing a remote bookmark update. + + + + + + Removed as of m19. + + zea@chromium.org + + Count of bookmark run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Removed as of M80. + + mamir@chromium.org + + Estimated number of bookmark duplications after bookmark association. + + + + + + Removed 2020-05. + + mamir@chromium.org + treib@chromium.org + + Time used to parse the Bookmarks persisted sync metadata after being read + from the Bookmarks JSON file. It includes the time spent in initializing + Bookmark Sync data structures as well as the time spent to check the + correctness of the data. It's reported on every startup for already syncing + users. It's not reported for non-syncing users or users going through the + first sync experience. + + + + + + Removed as of M80. + + mamir@chromium.org + + Tracks state of local bookmark model version relative to the sync version + when a new bookmark duplication occurs during bookmark association. + + + + + + Removed as of M80. + + mamir@chromium.org + + Estimated number of new bookmark duplications after bookmark association. + + + + + + Replaced by BookmarksConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of bookmark association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of bookmark association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed 10/2019. Was used for investigation of not completed Nigori + migration to keystore and recorded 0 suspicious samples. + + mmoskvitin@google.com + mastiz@chromium.org + + Records whether Nigori keybag can be decrypted with base64 decoded keystore + keys, when Nigori is not migrated to keystore and cryptographer is not + ready. + + + + + + Removed in 2019-02. + + pavely@chromium.org + + Records events encountered during sync's ClearServerData flow. + + + + + + Removed in M80. + + jkrcal@chromium.org + mastiz@chromium.org + + Enumeration of types of configuration failures of this data type. + + + + + + Replaced by Sync.ConfigureTime_Long.ABORTED in m21. + + zea@chromium.org + + Time spent configuring data types in the case where configuration is + aborted. + + + + + + Replaced by Sync.ConfigureTime_Long.OK in m21. + + zea@chromium.org + + Time spent configuring data types in the case where configuration succeeds. + + + + + + Replaced by Sync.ConfigureTime_Long.PARTIAL_SUCCESS in m21. + + zea@chromium.org + + Time spent configuring data types in the case where only some data types + succeed. + + + + + + Replaced by Sync.ConfigureTime_Long.UNRECOVERABLE_ERROR in m21. + + zea@chromium.org + + Time spent configuring data types in the case where configuration encounters + an unrecoverable error. + + + + + + Replaced by Sync.ConfigureTime_Initial.ABORTED and + Sync.ConfigureTime_Subsequent.ABORTED in M75. + + zea@chromium.org + + Time spent configuring data types in the case where configuration is + aborted. + + + + + + Replaced by Sync.ConfigureTime_Initial.OK and + Sync.ConfigureTime_Subsequent.OK in M75. + + zea@chromium.org + + Time spent configuring data types in the case where configuration succeeds. + + + + + + Removed in M75. + + zea@chromium.org + + Time spent configuring data types in the case where only some data types + succeed. + + + + + + Replaced by Sync.ConfigureTime_Initial.UNRECOVERABLE_ERROR and + Sync.ConfigureTime_Subsequent.UNRECOVERABLE_ERROR in M75. + + zea@chromium.org + + Time spent configuring data types in the case where configuration encounters + an unrecoverable error. + + + + + + Removed 12/2011. No longer tracked. See crbug.com/107816. + + zea@chromium.org + + Number of times we fix a circularity sync conflict. This is not expected to + be hit anymore. + + + + + + Removed 12/2011. No longer tracked. See crbug.com/107816. + + zea@chromium.org + + Number of times we fix a removed directory with content sync conflict. This + is not expected to be hit anymore + + + + + + Removed in M53. + + zea@chromium.org + + Whether or not we detected missing credentials during startup. This may be + related to crbug.com/121755. + + + + + + Removed as of m26. + + zea@chromium.org + + Boolean histogram for whether a custom passphrase was entered during sync + setup. Samples are taken every time sync is (re)configured, and the unique + userid count shows how many users entered a custom passphrase. + + + + + + Removed 10/2018, replaced by Sync.CustomSync2. + + zea@chromium.org + + Samples are taken every time sync is (re)configured, and the unique userid + count shows how many users explicitly chose to sync this data type via the + "Advanced Sync Preferences" dialog. + + + + + + Removed in M53. + + zea@chromium.org + + Number of clients that have fixed themselves up from a datatype preference + loss. Clients are not expected to have this happen more than once. This + value can be compared to Sync.BackendInitializeRestoreSuccess to determine + what percentage of users are still recovering. + + + + + + Removed 10/2018. Replaced by Sync.DataTypeRunFailures2 which correctly + splits run and start failures. + + zea@chromium.org + + Histogram of the run failures for the different sync datatypes. These are + failures that occur after startup while the datatype is syncing. Note: Due + to an enumeration reordering, pre-M23 labels are inaccurate (see + sync/base/model_type.h). + + + + + + Removed 10/2018. Replaced by Sync.DataTypeStartFailures2 which correctly + splits run and start failures. + + zea@chromium.org + + Histogram of the startup failures for the different sync datatypes. These + are failures due to missing top level sync nodes or model association Note: + Due to an enumeration reordering, pre-M23 labels are inaccurate (see + sync/base/model_type.h). + + + + + + Removed in 2020-08 (M86). + + grt@chromium.org + pastarmovj@chromium.org + + Reports the result of an attempt to delete a Windows user's roaming User + Data directory. This directory was erroneously created for signed-in users + who were not using the local sync server. See https://crbug.com/980487 for + details. + + + + + + Removed in M74. + + mastiz@chromium.org + jkrcal@chromium.org + + The largest number of active syncing devices known to any profile. May be 0 + when there are no signed in/syncing profiles open. + + + + + + Removed in M53. + + pavely@chromium.org + + When signin_scoped_device_id from pref doesn't match the one in + DeviceInfoSpecfics this histogram tells if sync or pref copy was empty. This + will indicate how often such mismatch happens and what was the state before. + + + + + + Replaced by DictionaryConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of dictionary association failures. + + + + + Removed in M85. + + jkrcal@chromium.org + + Whether the Sync Directory encountered a catastrophic error. + + + + + + Removed 11/2011. No longer tracked. + + zea@chromium.org + Number of failures trying to open the sync database on mac. + + + + + Removed 11/2011. No longer tracked. + + zea@chromium.org + + Number of failures trying to open the sync database on a non-windows non-mac + platform. + + + + + + Removed 11/2011. No longer tracked. + + zea@chromium.org + + Number of failures trying to open the sync database on windows. + + + + + + Removed 2020-05. + + zea@chromium.org + Tracks success of failure of sync directory initialization. + + + + + Removed 06/2020. + + mastiz@chromium.org + treib@chromium.org + + Whether the sync cache GUID and birthday are stored consistently across the + sync directory and prefs. + + + + + + Removed 01/2020. No longer tracked. + + mamir@chromium.org + mastiz@chromium.org + + Counts the number of password updates downloaded in case of error during the + MergeSyncData(). This is introduced to detect if there is corrleation + between number of password updates and failure during merge. Recorded only + for USS implementation. + + + + + + Removed 2019-09 - we collected sufficient data, see crbug.com/995534. + + treib@chromium.org + jkrcal@chromium.org + + Whether ModelTypeWorker received any duplicate client tag hashes within a + full GetUpdates cycle (which, in the case of pagination, might consist of + multiple individual GetUpdates responses). + + + + + + Removed 2019-09 - we collected sufficient data, see crbug.com/995531. + + treib@chromium.org + jkrcal@chromium.org + + Whether ModelTypeWorker received any duplicate client tag hashes within a + single GetUpdates response (which, in the case of pagination, might be only + part of a full GetUpdates cycle). + + + + + + Removed 2019-09 - we collected sufficient data, see crbug.com/995528. + + mamir@chromium.org + treib@chromium.org + + Whether ModelTypeWorker received any duplicate client tag hashes within a + full GetUpdates cycle that happen to have different server ids (which, in + the case of pagination, might consist of multiple individual GetUpdates + responses). + + + + + + Removed 2019-09 - we collected sufficient data, see crbug.com/995529. + + mamir@chromium.org + treib@chromium.org + + Whether ModelTypeWorker received any duplicate server ids within a full + GetUpdates cycle (which, in the case of pagination, might consist of + multiple individual GetUpdates responses). + + + + + + Removed as of m26. + + zea@chromium.org + + Boolean histogram for whether the "Encrypt all synced data" radio + button was selected during sync setup. Samples are taken every time sync is + (re)configured, and the unique userid count shows how many users chose to + encrypt their sync data. + + + + + + Removed 02/2020, Sync.PassphraseType2 can give the same data in a better + way. + + mmoskvitin@google.com + mastiz@chromium.org + mamir@chromium.org + + Records EncryptEverything state when Nigori is not migrated to keystore and + cryptographer is not ready. + + + + + + Removed as of M85. + + mamir@chromium.org + mastiz@chromium.org + + The positioning scheme used within sync entities. It is reported for data + types migrated to USS only. While it is reported for all data types, the + positioning information are expected to be set for bookmarks only. + "MISSING" is reported only for non deleted bookmarks. + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during extension association (M18 and earlier were mispelled with + this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of extension run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by ExtensionSettingsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + + Enumeration of types of extension settings association failures. + + + + + + Replaced by ExtensionsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of extension association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of extension association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed as of 07/2018. No longer tracked (because it is directory-specific + and related to now obsolete metrics Sync.ModelTypeCount). + + gangwu@chromium.org + + Counts the total number of extra copies of sync data in memory. This count + is emitted once, after loading Sync Directory. The count will indicate how + many Directory entities fail to share client and server specifics. + + + + + + Replaced by a Sync.SyncedHistoryFaviconAvailability in M77. Note: Last data + entries will be inconsistent since we keep recording this histogram while + behavior has not been changed for every SyncFaviconRequestOrigin histogram + suffix. In particular, Sync.FaviconAvailability.RECENTLY_CLOSED_TABS on + Android has always been recorded for remote only entries. + + victorvianna@google.com + jkrcal@chromium.org + + Records the availability status (local, sync or non-available) for each + favicon displayed by an interface. Recorded when the recent tabs menu is + opened or when a request is done to chrome://favicon by page url, which + happens for example for the chrome://history and chrome://history/syncedTabs + interfaces. + + + + + + Removed in M84. + + zea@chromium.org + Whether a sync favicon cache lookup succeeded or not. + + + + + Removed in M53. + + zea@chromium.org + Number of synced favicons at initialization time. + + + + + Replaced by FaviconImagesConfigureFailure. See crbug.com/478226. + + zea@chromium.org + + Enumeration of types of favicon images association failures. + + + + + + Removed in M53. + + zea@chromium.org + + Number of client that have filled their sync favicon cache and must evict + old favicons vs those whose cache is not full. + + + + + + Replaced by FaviconTrackingConfigureFailure. See crbug.com/478226. + + zea@chromium.org + + Enumeration of types of favicon tracking association failures. + + + + + + Removed in M53. + + zea@chromium.org + Time between updates to a synced favicon's visit time. + + + + + Removed 11/2011. Was counted incorrectly. Replaced by + Sync.BackendInitializeFirstTimeSuccess. + + zea@chromium.org + + Tracks sync backend initialization success rate during initial sync setup. + + + + + + Backup logic has been removed since 02/2016. + + haitaol@chromium.org + First sync delay casued by backing up user data. + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for apps. Used as estimate of datatype commit frequency. + Logged when a sync cycle is performed for apps. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for autofill entries. Used as estimate of datatype + commit frequency. Logged when a sync cycle is performed for autofill + entries. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for autofill profiles. Used as estimate of datatype + commit frequency. Logged when a sync cycle is performed for autofill + profiles. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for bookmarks. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for boomarks. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for dictionary. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for dictionary. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for extensions. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for extensions. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for favicon images. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for favicon images. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for favicon tracking. Used as estimate of datatype + commit frequency. Logged when a sync cycle is performed for favicon + tracking. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for nigori. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for nigori. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for passwords. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for passwords. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for preferences. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for preferences. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for search engines. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for search engines. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for sessions. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for sessions. + + + + + + Removed in M53. + + zea@chromium.org + + Time between nudges for synced notifications. Used as estimate of datatype + commit frequency. Logged when a sync cycle is performed for synced + notifications. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for themes. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for themes. + + + + + + Removed 03/2018 (M67). Replaced by Sync.SyncCycleInterval. + + zea@chromium.org + + Time between nudges for typed urls. Used as estimate of datatype commit + frequency. Logged when a sync cycle is performed for typed urls. + + + + + + Removed in M53. + + zea@chromium.org + + Time between nudges for WiFi credentials. Used as estimate of datatype + commit frequency. Logged when a sync cycle is performed for WiFi + credentials. + + + + + + Removed as of 06/2020. + + mastiz@chromium.org + treib@chromium.org + + Two navigations with different unique_ids shared a global_id/timestmap. This + means that user events will be ambiguously referencing navigations. + + + + + + Removed 02/2020. Instrumented in a wrong way and replaced by + Sync.NigoriConfigurationWithInvalidatedCredentials. + + mmoskvitin@google.com + mastiz@chromium.org + + Recorded when Nigori-only configuration failed. Indicates whether there was + a valid access token when failure happened. + + + + + + Removed 02/2020. Instrumented in a wrong way and replaced by + Sync.NigoriConfigurationWithInvalidatedCredentials. + + mmoskvitin@google.com + mastiz@chromium.org + + Recorded when Nigori-only configuration failed with 5 seconds backoff. + Indicates whether there was a valid access token when failure happened. + + + + + + Removed as of 5/2016. + + pkotwicz@chromium.org + + Count of the number of session sync invalidations. The goal of the metric is + to track how the number of session sync invalidations changes over time. + + + + + + Removed as of 04/2020 because directory implementation of Nigori is no + longer used and enough data for corresponding investigation was recorded. + + mmoskvitin@google.com + mastiz@chromium.org + + Indicates whether Nigori node state is migrated after the migration attempt. + + + + + + Removed as of 6/2019 in favor of Sync.Local.FileSizeKB. + + pastarmovj@chromium.org + Tracks the size of the local sync backend database file. + + + + + Removed 2019-09. Was only ever recorded for passwords. + + vasilii@chromium.org + + Counts cases when a sync type failed to load the local data during startup. + + + + + + Removed 2019-09. Was only ever recorded for bookmarks. + + zea@chromium.org + + Counts instances of out of sync local models detected during startup. + + + + + + Removed 2019-11. + + pnoland@chromium.org + + Counts instances of navigations that are recorded locally but not synced. + Recorded once per active tab for every inferred sync cycle. Sync cycles are + inferred by examining the is_synced and is_syncing flags of sync directories + when recording local changes to tabs or windows. Sync cycles that occur + without changes to tabs or windows won't cause this metric to be logged. + + + + + + Removed 2019-07. + + gangwu@chromium.org + + Counts the number of times a user's sync service received a + MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down + cleanly. The sync service emits this number the next time the user's sync + service is started, which will likely happen the next time the user's + profile is opened after a Chrome restart. This count is emitted once per + user/profile. Things like browser crashes that implicitly bring down all + users' sync services will cause unclean shutdown tags to appear on all open + profiles, meaning that there will be multiple emissions to this histogram as + those profiles are re-opened. + + + + + + Removed 2019-07. + + gangwu@chromium.org + + Counts the number of times a user's sync service received a + MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down + uncleanly. The sync service emits this number the next time the user's sync + service is started, which will likely happen the next time the user's + profile is opened after a Chrome restart. This count is emitted once per + user/profile. Things like browser crashes that implicitly bring down all + users' sync services will cause unclean shutdown tags to appear on all open + profiles, meaning that there will be multiple emissions to this histogram as + those profiles are re-opened. + + + + + + Removed as of 7/2018. Replaced by Sync.ModelTypeCount2 which does record + data consistently for both directory data types and USS data types. + + gangwu@chromium.org + + Counts the number of entries for each model type in sync DB at startup. + + + + + + Removed as of 8/2018. Replaced by Sync.ModelTypeCount3 which fixes a bug in + recording the counts for USS data types + + gangwu@chromium.org + + Counts the number of entries for each model type. For directory types, the + count is based on the directory contents, for USS types, the count is based + on metadata entries for the type. Recorded after sync configuration. This + metric is used for monitoring general health of sync client-side code. + + + + + + Removed as of 9/2018. Replaced by Sync.ModelTypeCount4 which fixes a + off-by-one bug that the root node get also recorded for directory data + types. + + jkrcal@chromium.org + + Counts the number of entries for each model type. For directory types, the + count is based on the directory contents, for USS types, the count is based + on metadata entries for the type. Recorded after sync configuration. This + metric is used for monitoring general health of sync client-side code. + + + + + + Removed as of 10/2018. Replaced by Sync.ModelTypeEntityChange3 which splits + initial remote updates from incremental remote updates. + + jkrcal@chromium.org + + Recorded once for every sync entity change (whenever it is commited to the + server or updated from the server). This metric is used for monitoring + general health of sync client-side code. Note: This is only recorded with a + data type suffix. The base version is never recorded. + + + + + + Removed as of 11/2018. Replaced by Sync.ModelTypeEntityChange3 which fixes a + bug affecting a subset of datatypes (directory codepath). + + jkrcal@chromium.org + + Recorded once for every sync entity change (whenever it is commited to the + server or updated from the server). This metric is used for monitoring + general health of sync client-side code. Note: This is only recorded with a + data type suffix. The base version is never recorded. + + + + + + Removed as of 05/2020. + + mastiz@chromium.org + + Records the number of write batches committed to leveldb + (ModelTypeStoreBackend) per datatype. + + + + + + Removed in M78 after sufficient data was gathered. + + mastiz@chromium.org + + Records the result of ModelTypeStoreBackend initialization. Used to analyze + frequency and causes of backend initialization failures. + + + + + + Removed in M84 after corresponding investigation was completed. + + mmoskvitin@google.com + mastiz@chromium.org + + Recorded when Nigori-only configuration pending while user credentials were + invalidated. + + + + + + Removed as of 04/2020 because directory implementation of Nigori is no + longer used and enough data for corresponding investigation was recorded. + + mmoskvitin@google.com + mastiz@chromium.org + + Records whether Nigori was attempted to migrate before recording migration + failure. + + + + + + Removed in M84 because directory implementation of Nigori is no longer used + and enough data for corresponding investigation was recorded. + + mmoskvitin@google.com + mastiz@chromium.org + + Records the condition, which triggered Nigori migration to keystore. + + + + + + Removed in M85. + + mastiz@chromium.org + mmoskvitin@google.com + Breakdown of sync's nigori node keystore migration state. + + + + + Removed as of 04/2020 because directory implementation of Nigori is no + longer used and enough data for corresponding investigation was recorded. + + mmoskvitin@google.com + mastiz@chromium.org + + Records the method, which triggered Nigori migration to keystore. + + + + + + Was used during the launch to compare new and old implemetations. + + melandory@chromium.org + + The number of invalidations received per sync data type for cases when only + single invalidation was emited by the invalidation component. In some cases + the invalidation component emits many invalidations grouped together, this + histogram doesn't track those cases. + + + + + + Was used during the launch to compare new and old implementations. + + melandory@chromium.org + + The sync datatype of the recieved invalidation. Recorded only for the + invalidations with known version and recieved not in a group. + + + + + + Was used during the launch for the new implementation. + + melandory@chromium.org + + The sync datatype of the recieved invalidation with fresh version. + + + + + + Removed as of 05/2019 because it recorded freshness only up to 1hr and most + samples were thus out of bounds. Replaced by + Sync.NonReflectionUpdateFreshnessPossiblySkewed2 which records freshness up + to 7 days. + + mastiz@chromium.org + melandory@chromium.org + + Freshness of the sync data per received sync entity update, excluding + reflections. The time represents the clock difference from the model being + modified (usually on another device) until the change is processing by this + instance of the browser. Beware of potential clock skew due to two clients + being involved. + + + + + + Removed in M66. + + skym@chromium.org + + The client side execution time to check for revisits with bookmarks data. + + + + + + Removed in M66. + + skym@chromium.org + + Age of bookmark that matches a navigation event, where matching means the + urls match. If multiple bookmarks match, the most recently created is used. + + + + + + Removed in M66. + + skym@chromium.org + Transition type to a page that matched a bookmark. + + + + + Removed in M66. + + skym@chromium.org + Transition type to a page that didn't match a bookmark. + + + + + Removed in M66. + + skym@chromium.org + + Difference in time between finding the match and the creation of the most + recent foreign modification of the parent tab. The parent tab's modification + will not always be indicative of when the matching navigation occurred. + + + + + + Removed in M66. + + skym@chromium.org + + The number of navigations forward or backwards the matching noncurrent + navigation is from the current navigation in its tab. Negative values + represent backwards and positive values represent forwards. Zero should not + occur since it would cease to be noncurrent. + + + + + + Removed in M66. + + skym@chromium.org + Transition type that matched a synced navigation. + + + + + Removed in M66. + + skym@chromium.org + Transition type that didn't match a synced navigation. + + + + + Removed in M66. + + skym@chromium.org + + The client side execution time to check for revisits with session data. + + + + + + Removed in M66. + + skym@chromium.org + + Difference in time between finding the match and the creation of the most + recent foreign modification of the given tab. + + + + + + Removed in M66. + + skym@chromium.org + Transition type that matched a synced tab. + + + + + Removed in M66. + + skym@chromium.org + Transition type that didn't match a synced tab. + + + + + Removed in M66. + + skym@chromium.org + + The client side execution time to check for revisits with typed URL data. + + + + + + Removed in M66. + + skym@chromium.org + + Difference in time between finding the match and the last time this URL was + typed on a foreign client. + + + + + + Removed in M66. + + skym@chromium.org + Transition type that matched a typed URL. + + + + + Removed in M66. + + skym@chromium.org + Transition type that didn't match a typed URL. + + + + + Removed 2020-05. + + zea@chromium.org + + Number of partially synced types (those with a progress marker but no + initial sync ended bit) that exist at sync startup. + + + + + + Removed 2020-05. + + zea@chromium.org + Whether a passphrase decryption attempt succeeded or not. + + + + + Removed 2020-05. + + zea@chromium.org + Enumeration of how a user dismissed the passphrase dialog. + + + + + Removed in M53. + + zea@chromium.org + + Time taken during password association (M18 and earlier were mispelled with + this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of passwords run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by PasswordsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of password association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of password association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during preference association (M18 and earlier were mispelled + with this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of preferences run failures, used to compare failure rates between + data types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Removed 2020-06. + + tschumann@chromium.org + treib@chromium.org + + Counts the number of times a client received a remote pref update with a + value type different from the registered pref type. The client will ignore + those remote updates. + + + + + + Removed in M79 because support for lazy pref registration was removed. + + tschumann@chromium.org + treib@chromium.org + + The number of unknown prefs being synced. This number is computed after the + sync model has been associated. Preferences which get handled by sync even + before being registered are considered "unknown". This might be + limited to a whitelist of preferences. + + + + + + Replaced by PreferencesConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of preference association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of preference association failures (M18 and earlier + were mispelled with this histogram). + + + + + + Removed in M53. + + zea@chromium.org + Time taken from startup for the user to reauthorize. + + + + + Removed 05/2019. + + jkrcal@chromium.org + mastiz@chromium.org + + Recorded for each GetUpdates response (and each data type included). Records + whether the newly received token is new (as this data type had none before) + or whether it is the same as before or whether it has changed. + + + + + + Removed 04/2016 as not useful since it always logged true. + + zea@chromium.org + + Whether OAuth2 refresh token was available at the time when + ProfileSyncService was starting backend. + + + + + + Deleted in M75, Issue 900075. + + gangwu@chromium.org + + The request content size for a single HTTP/HTTPS call from sync client to + server. The content is compressed by gzip. + + + + + + Deleted in M75, Issue 900075. + + gangwu@chromium.org + + The original request content size for a single HTTP/HTTPS call from sync + client to server. It is the size before content got compressed. + + + + + + Deleted in M84. + + victorvianna@google.com + jkrcal@chromium.org + + Records the number of active requests simultaneously done to the Google + favicon server that were associated with a same icon url and could have thus + been grouped. Recorded when one of the following is displayed: entries in + chrome://history that are known to be present in remote history data; all + entries in chrome://history/syncedTabs; tabs from other devices in the 3 + dots history menu (desktop); tabs from other devices in the android Recent + Tabs UI. + + + + + + Deleted 2020-02. + + treib@chromium.org + mastiz@chromium.org + + Enumeration of types of conflict resolutions. Recorded every time a conflict + is resolved for a data type that has been converted to USS. + + + + + + Removed 06/2020. + + mastiz@chromium.org + treib@chromium.org + Enumeration of types of simple conflict resolutions. + + + + + Deleted in M75, Issue 900073. + + gangwu@chromium.org + + The response content size for a single HTTP/HTTPS call from sync server to + client. The content is compressed by gzip. + + + + + + Deleted in M75, Issue 900073. + + gangwu@chromium.org + + The original response content size for a single HTTP/HTTPS call from sync + server and client. It is the size after content got uncompressed. + + + + + + Removed 11/2011. Was counted incorrectly. Replaced by + Sync.BackendInitializeRestoreSuccess. + + zea@chromium.org + + Tracks sync backend initialization success rate in cases where sync was + previously initialized. + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during search engine association (M18 and earlier were mispelled + with this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of search engine run failures, used to compare failure rates between + data types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by SearchEnginesConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of search engine association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of search engine association failures (M18 and earlier + were mispelled with this histogram). + + + + + + Replaced by Sync.ConfigureTime_Initial.{OK, ABORTED, UNRECOVERABLE_ERROR} in + M75 when solving bug 169053. + + zea@chromium.org + + Time spent on first-time configure. May include time spent on retries. + + + + + + Replaced by Sync.ConfigureTime_Subsequent.{OK, ABORTED, UNRECOVERABLE_ERROR} + in M75 when solving bug 169053. + + zea@chromium.org + + Time spent on non-first-time configure. May include time spent on retries. + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during session association (M18 and earlier were mispelled with + this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of sessions run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Removed as of 2018-11. + + mastiz@chromium.org + treib@chromium.org + + Number of foreign sessions entries detected with bad client tag hash value + during MergeDataAndStartSyncing. These will be immediately deleted. The + overwhelming majority of clients should report a value of 0 upon startup. + + + + + + Removed 2020-05. + + zea@chromium.org + + Delay from the time chrome://history is loaded until the other devices' + sessions data became available. + + + + + + Replaced by SessionsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of session association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of session association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed as of 2018-11. + + mastiz@chromium.org + treib@chromium.org + + The number of windows present within Chrome at the time Sync associates the + SESSIONS datatype. + + + + + + Removed in M69. + + mastiz@chromium.org + + https://crbug.com/639009, count of duplicate sync ids (tab node id) when any + are encountered. Likely caused from a persistence race between native tab + storage and sync db on Android. Should be trending to zero. + + + + + + Removed in M84 because directory implementation of Nigori is no longer used + and enough data for corresponding investigation was recorded. + + mmoskvitin@google.com + mastiz@chromium.org + + Indicates that Nigori would be migrated again right after migration if + AttemptToMigrateNigoriToKeystore called. + + + + + + Removed 2020-05. + + zea@chromium.org + + Time taken from the start of sync shutdown (in ProfileSyncService) until the + backend (SyncEngine) is fully destroyed. + + + + + + Removed in M53. + + zea@chromium.org + + Amount of time the UI thread waits (at shutdown) to stop the + SyncBackendRegistrar. + + + + + + Removed in M53. + + zea@chromium.org + + Amount of time the UI thread waits (at shutdown) to stop the sync thread. + + + + + + Replaced by Sync.RequestGroupSizeForSyncedHistoryFavicons in M77. + + victorvianna@google.com + jkrcal@chromium.org + + Records the number of active requests simultaneously done to the Google + favicon server that were associated with a same icon url and could have thus + been grouped. Recorded when opening the recent tabs menu, chrome://history + or chrome://history/syncedTabs with both history sync and the + EnableHistoryFaviconsGoogleServerQuery feature enabled. + + + + + + Removed, see TimeDeferred2. + + jeremy@chromium.org + zea@google.com + + Time spent after ProfileSyncService *creation* but before SyncEngine + initialization. + + + + + + Removed in M53. + + zea@chromium.org + + Counts the number of times sync clients have encountered an auth error and + number of times auth errors are fixed. + + + + + + Removed 2019-03. + + treib@chromium.org + + The interval between successive sync cycles. Recorded whenever a sync cycle + starts, except for the very first one after Chrome startup. + + + + + + Removed in M53. Replaced by SyncedNotificationsConfigureFailure. See + crbug.com/478226. + + zea@chromium.org + + Enumeration of types of synced notifications association failures. + + + + + + Removed 12/2011. No longer tracked. See crbug.com/107816. + + zea@chromium.org + + Number of times the sync conflict resolver gets stuck. This is not expected + to be hit anymore. + + + + + + Removed 10/2018, replaced by Sync.SyncEverything2. + + zea@chromium.org + + Boolean histogram for whether the "Sync Everything" option was + selected during sync setup. Samples are taken every time sync is + (re)configured, and the unique userid count shows how many users chose to + sync all available data types. + + + + + + Removed as of m19 + + zea@chromium.org + + Time taken during theme association (M18 and earlier were mispelled with + this histogram). + + + + + + Removed as of m19. + + zea@chromium.org + + Count of theme run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by ThemesConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of theme association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of theme association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed in M53. + + zea@chromium.org + + Time taken during typed url association (M18 and earlier were mispelled with + this histogram). + + + + + + Removed in M53. + + zea@chromium.org + + The percentage of history DB operations initiated by the typed URL change + processor that return an error. The cumulative count for the current sync + session is logged after every typed URL change. + + + + + + Removed 2020-05. + + zea@chromium.org + + The percentage of history DB operations during merge data that return an + error. This is logged at the end of typed URL merge data, which happens once + each time sync starts up. + + + + + + Removed in M53. + + zea@chromium.org + + The percentage of history DB operations during model association that return + an error. This is logged at the end of typed URL model association, which + happens once each time sync starts up. + + + + + + Removed as of m19. + + zea@chromium.org + + Count of typed url run failures, used to compare failure rates between data + types for a particular profile (see other Sync*RunFailures histograms). + + + + + + Replaced by TypedUrlsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + Enumeration of types of typed url association failures. + + + + + Removed as of m19. + + zea@chromium.org + + Enumeration of types of typed url association failures (M18 and earlier were + mispelled with this histogram). + + + + + + Removed as of 06/2020. + + mastiz@chromium.org + treib@chromium.org + + Enumeration of the different reasons for unrecoverable errors and how often + they have occurred. + + + + + + Removed in M53. + + zea@chromium.org + Time the user spends looking at the authorization dialog. + + + + + Removed in M53. + + zea@chromium.org + Time taken during bookmark association. + + + + + Removed in M82. + + pavely@chromium.org + Time it took sync to load models for USS datatypes. + + + + + Removed in M85. + + mastiz@chromium.org + + Counts the number of sync entities per model type successfully migrated from + directory to USS. + + + + + + Removed in M85. + + treib@chromium.org + mastiz@chromium.org + Counts directory to USS migration failures per model type. + + + + + Removed in M85. + + treib@chromium.org + mastiz@chromium.org + Counts directory to USS migration successes per model type. + + + + + Removed as of 05/2019. + + jkrcal@chromium.org + feuunk@chromium.org + + Counts number of data entities that are removed when sync / Wallet sync gets + disabled. + + + + + + Removed as of 2020-03. + + rushans@google.com + jkrcal@chromium.org + + Records errors with storage keys in ClientTagBasedModelTypeProcessor during + updates and loading of metadata for AUTOFILL_WALLET_DATA data type. + + + + + + Removed as of 2019-08. + + jkrcal@chromium.org + mastiz@chromium.org + + Counts number of old orphan metadata entities that are removed on startup. + + + + + + Removed in M53. + + zea@chromium.org + Time taken during WiFi credentials association. + + + + + Removed in M53. + + zea@chromium.org + + Enumeration of types of WiFi credentials configuration failures. + + + + + + Replaced by WifiCredentialsConfigureFailure. See crbug.com/478226. + + zea@chromium.org + + Enumeration of types of WiFi credentials association failures. + + + + + + Removed in M67. After more than a year, almost all clients are reporting + FALSE. + + skym@chromium.org + + Whether there are still encrypted updates that the cryptographer cannot + decrypt during ApplyUpdates in the ModelTypeWorker (USS Only). Emitting true + is an invalid state that hopefully never happens, as it is a potential data + loss scenario. + + + + + + Removed in M66. + + skym@chromium.org + Upon NTP load, the age of the youngest synced foreign tab. + + + + + Removed in M53. + + petewil@chromium.org + zea@chromium.org + + The actions taken on synced notifications, recorded every time they happen. + This histogram will record every single event that happens separately. + + + + + + Removed 06/2019. + + dbeam@chromium.org + + Shows actions taken on the "Not signed in? You're misssing out" + link on the top right of chrome://apps. Logged once per visit of + chrome://apps as well as on each click of the sync promo. + + + + + + Removed 03/2018. SyzyAsan has been deprecated. + + georgesak@chromium.org + + Record whether the deferred free mechanism was successfully enabled or not. + This is only recorded in syzyasan builds with the feature enabled. + + + + + + Removed 06/2020 + + pkotwicz@chromium.org + + Whether a tab which was opened in the background (e.g. via "Open link + in new tab") is foregrounded prior to being closed. + + + + + + Removed 06/2020 + + pkotwicz@chromium.org + + Counts the number of background tabs opened via the context menu per page + URL. The count is reset on each navigation of the parent tab. Zero counts + are not recorded. + + + + + + Removed 01/2019. + + + Time in milliseconds from trying to close the tab to actually closing it. + Includes time that's spent in JS OnUnload handlers. + + + + + + Removed 01/2019. + + + Time in milliseconds from when JS OnUnload handlers have finished to + actually closing tab. Doesn't include time that's spent in JS OnUnload + handlers. If there are no UnLoad handlers, should be identical to Tab.Close. + + + + + + Removed 11/2016. No longer useful after finding out that it has no effect on + tab reactivation rates. + + pmonette@chromium.org + + A tab was deactivated. Closing tabs are not included. This histogram also + records if the tab's URL was bookmarked. + + + + + + No longer recorded. + + pmonette@chromium.org + + A tab was deactivated. Closing tabs are not included. This histogram also + records if the tab had any form interaction. + + + + + + No longer recorded. + + pmonette@chromium.org + + A tab was deactivated. Closing tabs are not included. This histogram also + records if the tab was pinned to the tab strip or not. + + + + + + Removed 10/2015, not needed anymore. + + georgesak@chromium.org + + Metric to track counts of actions related to tab discarding. Namely, we get + an event for every tab switch, split into two groups, whether it was a + discarded tab not. We also get an event whenever a tab gets discarded as + well as when a tab that's playing audio gets discarded. + + + + + + Removed 10/2015, and replaced by TabManager.Discarding.DiscardCount. + + georgesak@chromium.org + + Metric to track the number of discards tabs have gone through. Each time a + tab is discarded, this histogram is recorded. Therefore, this metric is + cumulative, ie. as a tab gets discarded over and over, it gets a hit in each + bin (1, 2, 3...). + + + + + + Removed as of 10/2016. + + + [iOS] When switching to an evicted tab, this histogram records whether or + not the tab had ever been active. For example, the tab was opened via + "Open in new tab" but evicted before being viewed for the first + time. + + + + + + Removed as of 10/2016. + + + A count of form activity (e.g. fields selected, characters typed) in a tab. + Recorded only for tabs that are evicted due to memory pressure and then + selected again. + + + + + + Removed 06/2020 + + pkotwicz@chromium.org + + [Android] When a tab that was opened in the background (e.g. via "Open + link in new tab") is evicted prior to the first time that it is shown, + we record the tab's age at the time that the tab is shown. + + + + + + Removed 07/2020, no longer used. + + kmilka@chromium.org + ramyan@chromium.org + + The time for the new tab page to fire the "DOMContentLoaded" + event. + + + + + + Removed 07/2020, no longer used. + + kmilka@chromium.org + ramyan@chromium.org + + The time for the new tab page to start executing JavaScript. + + + + + + Removed in favor of Tab.TabUnder.PopupToTabUnderTime. + + csharrison@chromium.org + + Measures the time from when a tab opens a popup to when it navigates itself + cross-origin in the background. + + + + + + Removed in favor of Tab.TabUnder.VisibleTime. + + csharrison@chromium.org + + Measures the total time a tab is visible after it navigates itself + cross-origin in the background. Measured at WebContents destruction. The tab + must have opened a popup (as classified by the popup blocker) before the + navigation. + + + + + + Removed 11/2016. No longer useful after finding out that it has no effect on + tab reactivation rates. + + pmonette@chromium.org + + A tab was reactivated after being hidden. This histogram also records if the + tab's URL was bookmarked. + + + + + + No longer recorded. + + pmonette@chromium.org + + A tab was reactivated after being hidden. This histogram also records if the + tab had any form interaction. + + + + + + No longer recorded. + + pmonette@chromium.org + + A tab was reactivated after being hidden. This histogram also records if the + tab was pinned to the tab strip. + + + + + + No longer logged + + + The status of a tab collected each time the tab is displayed on Android, + including user switching to the tab and displays of newly created tabs, such + as NTP or tabs opened to handle intents. + + + + + + No longer logged + + marq@chromium.org + + [Android and iOS] The status of a tab collected each time the user switches + to it on mobile with the data reduction proxy enabled. This is populated + identically, and in addition to Tab.StatusWhenSwitchedBackToForeground for + any given tab switching event if the proxy is enabled. + + + + + + Removed as of 04/2014. + + + Each time a tab is brought to the foreground, this histogram indicates if + chrome was launched without an URL (i.e., from the launcher), or with an URL + (i.e., from another app). + + + + + + Removed as of 04/2014. + + + Rank in MRU order (0 being first) when the tab was switched to foreground. + + + + + + No longer logged + + Count of all tabs when a tab is switched. + + + + + Removed as of 04/2014. + + + Each time a tab is brought to the foreground, this histogram indicates if + this is the first viewing of the tab since Chrome was put into foreground, + or if it was a return to a tab that has already been shown in this session. + + + + + + Removed August 2018 + + csharrison@chromium.org + + Measures the engagement score associated with the URL that is detected as + the target of a tab-under navigation. + + + + + + Removed as of 10/2016. + + + [iOS] When an existing tab becomes active, this histogram records the time + since it was made inactive. + + + + + + Removed as of 10/2016. + + + [iOS] When an evicted tab becomes active, this histogram records the time + since it was made inactive. + + + + + + Removed as of 10/2016. + + + Time elapsed since there was form activity (e.g. fields selected, characters + typed) in a tab. Recorded only for tabs that are evicted due to memory + pressure and then selected again. + + + + + + No longer recorded. + + pmonette@chromium.org + + The time elapsed from the moment a tab was deactivated until it was + reactivated. Only recorded for tabs that are pinned or had form interaction. + + + + + + No longer recorded. + + pmonette@chromium.org + + The time elapsed from the moment a tab was deactivated until it was + reactivated. Only recorded for tabs that are not pinned nor had form + interaction. + + + + + + This metric was deprecated in favor of just using Tab.TabUnder.VisibleTime + directly. Consider bringing it back if we care about visible time after a + suspicious redirect without an associated popup. + + csharrison@chromium.org + + Measures the total time a tab is visible after it navigates itself + cross-origin in the background. Measured at WebContents destruction. + + + + + + Removed June 2020. + + chrisha@chromium.org + + The expected queueing duration of tasks in a foreground tab during a + background tab opening session (the duration of time from when the browser + starts to open background tabs until the time the browser has finished + loading those tabs or otherwise decided to stop loading them). The metric + reflects the responsiveness of a tab. A lower value means the tab will + respond to inputs faster. This metric is equivalent to + RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all + tasks in each 1000-ms window. The metric is not recorded when the session + overlaps with session restore. + + + + + + Removed 11/2017. Analysis showed that MRU was as good as engagement score to + choose which tabs to discard. The new plan is to build a machine learning + model to choose which tabs to discard. + + georgesak@chromium.org + + Site engagement score of a discarded tab. Recorded for each discard if the + score is available. + + + + + + Removed 07/2018, and replaced by ResourceCoordinator.LocalDB.DatabaseInit. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database. + + + + + + Removed 07/2018, and replaced by + ResourceCoordinator.LocalDB.DatabaseInitAfterDelete. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database after deleting + it after a failed repair attempt. + + + + + + Removed 07/2018, and replaced by + ResourceCoordinator.LocalDB.DatabaseInitAfterRepair. + + sebmarchand@chromium.org + + The result of opening the Local Site Characteristics database after a repair + attempt. + + + + + + Removed 07/2018, and replaced by ResourceCoordinator.LocalDB.DatabaseRepair. + + sebmarchand@chromium.org + + The result of trying to repair the Local Site Characteristics database after + a failed open. + + + + + + Removed 06/2019, check Arc.LowMemoryKiller.FirstKillLatency instead. + + cywang@chromium.org + georgesak@chromium.org + + Elapsed time to collect memory usage of each tab triggered by a LogMemory() + call(). + + + + + + Removed 11/2017. Analysis showed that MRU was as good as engagement score to + choose which tabs to discard. The new plan is to build a machine learning + model to choose which tabs to discard. + + georgesak@chromium.org + + Site engagement score of a reloaded tab. Recorded for each reload if the + score is available. Note that this will be the same score the tab had when + discarded (which could have changed by the time it gets reloaded). + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.BackgroundTabOpening.TabSwitchLoadTime.UntilTabIsLoaded. + + zhenw@chromium.org + + The tab load time of a tab that is switched to during a background tab + opening session (the duration of time from when the browser starts to open + background tabs until the time the browser has finished loading those tabs + or otherwise decided to stop loading them). Tab load time is defined as the + time between when the user switches to a backround tab, and the time when + that tab finishes loading in the foreground. If the user switches away + before the tab finishes loading, a metric will not be recorded unless the + user switches back, in which case the tab load time is measured from that + point in time. The metric is only recorded when a tab is switched to from + another tab within the same tabstrip. As a result, the initial forground tab + is not included in this metric since it was not switched to from another + tab. The metric is not recorded when the session overlaps with session + restore. + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.SessionRestore.TabSwitchLoadTime.UntilTabIsLoaded. + + chrisha@chromium.org + + The tab load time of a tab that is switched to during a session restore. Tab + load time is defined as the time between when the user switches to a + backround tab, and the time when that tab finishes loading in the + foreground. If the user switches away before the tab finishes loading, a + metric will not be recorded unless the user switches back, in which case the + tab load time is measured from that point in time. The metric is only + recorded when a tab is switched to from another tab within the same + tabstrip. As a result, the initial forground tab is not included in this + metric since it was not switched to from another tab. The metric is only + recorded when session restore is actively loading tabs, which ends when + either all tabs have been loaded and their pages rendered, or tab loading + needs to be deferred in cases where the system is under memory pressure. The + metric is not recorded when the session overlaps with background tab opening + session. + + + + + + Removed on 21/1/2019. + + chrisha@chromium.org + lpy@chromium.org + + Measures the time duration from when the tab is backgrounded to when a + JavaScript alert is updated. Only recorded when the tab is in the + background. + + + + + + Removed on 21/1/2019. + + chrisha@chromium.org + lpy@chromium.org + + Measures the time duration from when the tab is backgrounded to when audio + starts to play. Only recorded when the tab is in the background. + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.SessionRestore.CompressedPagesPerSecond. + + fmeawad@chromium.org + + The number of pages compressed per second during session restore. Recorded + at the end of session restore as an average over the entire period, defined + as the period of time when session restore is actively loading tabs, which + ends when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. Only recorded on macOS. + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.SessionRestore.DecompressedPagesPerSecond. + + fmeawad@chromium.org + + The number of pages decompressed per second during session restore. Recorded + at the end of session restore as an average over the entire period, defined + as the period of time when session restore is actively loading tabs, which + ends when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. Only recorded on macOS. + + + + + + Removed June 2020. + + chrisha@chromium.org + + The expected queueing duration of tasks in a foreground tab during session + restore. This metric reflects the responsiveness of a tab. A lower value + means the tab will respond to inputs faster. This metric is equal to + RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all + tasks in each 1000-ms window. The metric is not recorded when the session + overlaps with background tab opening session. + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.SessionRestore.SwapInPerSecond. + + fmeawad@chromium.org + + The number of swap-ins per second during session restore. Recorded at the + end of session restore as an average over the entire period, defined as the + period of time when session restore is actively loading tabs, which ends + when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. + + + + + + Removed 08/2017, and replaced by + TabManager.Experimental.SessionRestore.SwapOutPerSecond. + + fmeawad@chromium.org + + The number of swap-outs per second during session restore. Recorded at the + end of session restore as an average over the entire period, defined as the + period of time when session restore is actively loading tabs, which ends + when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. + + + + + + Removed 10/2015, and replaced by TabManager.Discarding.DiscardCount. + + jamescook@chromium.org + + Cumulative number of tabs discarded due to low memory conditions, recorded + once per tab discard event. For example, a user who had 3 tabs discarded + records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the number + of sessions where users experienced N or more tab discard events. + + + + + + Removed 11/2017. Average number of minutes between discard events is + available in Tabs.Discard.InitialTime2 and Tabs.Discard.IntervalTime2. + + jamescook@chromium.org + + Whether or not a tab was discarded in the last minute of usage. Total count + is number of minutes of device usage. 100 / discard percentage gives the + average number of minutes between discard events. + + + + + + Removed May 4, 2012. Replaced by Tabs.Discard.InitialTime2 because this stat + had too low of a range maximum. No longer tracked. + + jamescook@chromium.org + + Time in seconds between system startup and when the first tab is discarded + due to low memory conditions. Higher is better. + + + + + + Removed 11/2017. Replaced with Discarding.Urgent.TimeSinceStartup which is + recorded when Chrome has to discard tabs or apps urgently (instead of before + an individual tab is urgently or proactively discarded). + + jamescook@chromium.org + + Time in seconds between system startup and when the first tab is discarded + due to low memory conditions. Higher is better. Range maximum is + approximately one day. + + + + + + Removed May 4, 2012. Replaced by Tabs.Discard.IntervalTime2 because this + stat had too low of a range maximum. No longer tracked. + + jamescook@chromium.org + + Time in seconds between tab discard events after the first one, recorded + once per discard event. Higher is better. + + + + + + Removed 11/2017. Replaced with Discarding.Urgent.TimeSinceLastUrgent which + is recorded before a set of tabs/apps are urgently discarded (instead of + before an individual tab is urgently or proactively discarded). + + jamescook@chromium.org + + Time in milliseconds between tab discard events after the first one, + recorded once per discard event. Should occur no faster than once every 750 + ms. Higher is better. + + + + + + Removed 05/2019 + + jamescook@chromium.org + + System-wide memory allocation at the time a tab was discarded, roughly + equivalent to the sum of memory allocated with malloc() in userspace plus + graphics driver memory. + + + + + + Removed December 7, 2012. Replaced by Tabs.Discard.MemAllocatedMB because + this stat has insufficient precision in the 2-4 GB range and does not + properly account for graphics memory on ARM. + + jamescook@chromium.org + + System-wide anonymous memory allocation at the time a tab was discarded, + roughly equivalent to memory allocated with malloc(). + + + + + + Removed 05/2019 + + jamescook@chromium.org + + System-wide file-backed memory plus free memory, roughly equivalent to what + the kernel uses to trigger low-memory notifications for tab discards. If + lower than the kernel's threshold then we are not effectively freeing memory + in response to the initial notification and are repeatedly being notified. + + + + + + Removed 05/2019 + + jamescook@chromium.org + + Graphics driver (GEM object) memory at the time of a tab discard. + + + + + + Removed 05/2019 + + jamescook@chromium.org + + System-wide shared memory at the time of a tab discard. Used primarily for + shared buffers in the graphics system. Tracked because it's a historical + source of leaks on Chrome OS. + + + + + + Removed 10/2015, and replaced by TabManager.Discarding.ReloadCount. + + jamescook@chromium.org + + Cumulative number of times a tab was reloaded because it was discarded and + the user clicked on it later, recorded once per reload event. For example, a + user who clicks on 3 discarded tabs will record a count in the 1 bin, 2 bin, + and 3 bin. Thus each bin N is the number of sessions where users experienced + N or more reload events. Compare to Tabs.Discard.DiscardCount. + + + + + + Removed 11/2017. Replaced with Discarding.Urgent.NumAliveTabs which records + the number of tabs that are not pending load or discarded when an urgent + discard request is received (vs. this that records the total number of tabs + every time a tab is discarded, no matter the reason). + + jamescook@chromium.org + + The number of tabs open across all browser windows when a tab was discarded + due to low memory conditions. + + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between closing a tab and opening another, to + track very frequent tabs. + + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between opening a tab and opening another, to + track very frequent tabs. + + + + + + Removed 2019-07. + + joenotcharles@google.com + + Fine-grained (in msec) time between opening a tab and closing it, to track + very short-lived tabs. + + + + + + Removed 2020-06. + + + + adityakeerthi@google.com + fdoray@chromium.org + + The percentage of hidden tabs that are frozen. This metric is recorded every + 5 minutes, as a tab heartbeat metric. Desktop only. + + + + + + Code removed long ago. + + pauljensen@chromium.org + + Page load time (PLT) for iOS that does not include time spent following + redirects. On other platforms this is calculated from Navigation Timings but + on iOS Navigation Timings are not available so we're recreating a + calculation similar to PLT.PT_RequestToFinish but not including time spent + following redirects. This metric represents the time between when navigation + is initiated (prior to DNS, TCP connect, etc but after following redirects) + until loading ends (i.e. JS onload event). On non-iOS Chrome this is + (performance.timing.loadEventEnd - performance.timing.redirectEnd). On + Chrome for iOS we're calculating the time between the creation of the + top-level URLRequest and when webDidFinishWithURL is called. + + + + + + No longer logged + + + Applicability of speculative tab restore, recorded every time a tab is + switched. This allows to estimate the fraction of tab restores experienced + on mobile that can be mitigated using speculative restore. Options higher in + the enum take precedence over the lower ones (i.e. low-memory tablet will be + accounted as tablet). + + + + + + No longer logged + + + Accuracy of the tab switch predictions made when the user begins the side + swipe gesture. + + + + + + No longer logged + + + Accuracy of the tab switch predictions made when the user enters the tab + switcher. + + + + + + No longer logged + + + Status of a tab recorded when the tab is targeted with speculative restore. + + + + + + No longer logged + + + Time between starting the speculative load and actual tab switch for correct + speculative load predictions made when the user begins the side swipe + gesture. + + + + + + No longer logged + + + Time between starting the speculative load and actual tab switch for correct + speculative load predictions made when the user enters the tab switcher. + + + + + + Removed as of 4/2017. + + kouhei@chromium.org + tzik@chromium.org + + Tabs.StateTransfer.TimeA_B measures the time a tab was in state A before it + transferred to state B. + + + + + + Removed as of 07/2020. Rename to + Tabs.Suggestions.NumSuggestionsChanged.Closing. + + yusufo@chromium.org + davidjm@chromium.org + + The user is presented with recommendations on which Tabs they could close. + The user has the option to: 1) Remove a Tab from the recommendation 2) Add a + Tab which wasn't in the recommendation to the recommendation + + This metric records the sum of the number of times the user does 1) or 2) + and is a measure of how useful the recommendation is. This metric is + recorded after the user accepts a recommendation - potentially with edits by + performing 1) or 2). + + + + + + Removed as of 09/2020 as the way the metric is emitted has changed. Replaced + with Tabs.TabSearch.WindowDisplayedDuration2. + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for their desired tabs. It can be opened and closed. This records the amount + of time between when a Tab Search bubble is opened and when it is closed. It + does so by recording the difference in time between when the Tab Search's + WebView is first set visible and when the WebView's destructor is called. + + The Tab Search UI is a bubble anchored to an element within a browser window + and is closed if the user switches to a tab, presses the escape key or + performs an action to return focus to the hosting window. The Tab Search UI + bubble will also close if the hosting browser window is closed or crashes. + + Users may leave the bubble open for long periods of time without directly + interacting with the UI which could result in a long tail of displayed + durations. + + + + + + Removed 2019-07. + + alexmos@chromium.org + dcheng@chromium.org + + Reports the delta between the last user interaction time with a WebContents + and the time browser code wants to verify a recent user interaction with + that WebContents. Used to tune the threshhold for timing out a user + interaction. + + + + + + Removed 2019-06. + + afakhry@chromium.org + + The requested window creation state from the tabs extensions API when it's + used to create a new window or update the state of an existing one. + + + + + + Removed 10/2018. Instead of recording a histogram with the number of + BLOCK_SHUTDOWN tasks posted during shutdown, we generate a crash when too + many BLOCK_SHUTDOWN tasks are posted during shutdown. A crash dump is more + actionnable than a histogram. + + fdoray@chromium.org + + Number of BLOCK_SHUTDOWN tasks that were posted to a base::TaskScheduler + after its Shutdown() method was called but before it returned. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Time elapsed between when the thread managed by a SchedulerWorker is + detached and when the main function of a new thread managed by the same + SchedulerWorker is entered (following a wake up). Recorded each time that a + thread is recreated for a given SchedulerWorker. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Latency of dummy "heartbeat" tasks posted with specific traits + (see suffix). The heartbeat recording avoids dependencies between this + report and other work in the system. See + TaskScheduler.TaskLatencyMicroseconds.* for a metric that is closer to the + real workload. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + etiennep@chromium.org + fdoray@chromium.org + gab@chromium.org + + Number of workers running a task in a given SchedulerWorkerPool. Recorded + every 59 minutes (sampling rate is not expected to affect the distribution). + + + + + + Removed as of 03/2019. The number of cancelled delayed tasks found by the + lazy approach is 0 more than 99% of the time. + + adityakeerthi@google.com + fdoray@chromium.org + + Lower-bound number of cancelled tasks that remain in the DelayedTaskManager. + An exact number is not recorded, as it could potentially be expensive to + calculate. Instead, a lazy count is maintained by noting cancelled tasks as + new delayed tasks are added. Recorded every time the ServiceThread performs + a heartbeat latency report. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Number of tasks executed by a SchedulerWorker before it detached. Recorded + when a SchedulerWorker detaches. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Number of tasks executed by a SchedulerWorker between two waits on its + WaitableEvent. This should be maximized without affecting perceived browser + performance. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + + Number of tasks run by TaskScheduler while task was queuing (from time task + was posted until time it was run). Recorded for dummy "heartbeat" + tasks posted with specific traits (see suffix). The heartbeat recording + avoids dependencies between this report and other work in the system. + Recorded every time the ServiceThread performs a heartbeat latency report. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + etiennep@chromium.org + fdoray@chromium.org + gab@chromium.org + + Number of workers that live in a given SchedulerWorkerPool. Recorded every + 59 minutes (sampling rate is not expected to affect the distribution). + + + + + + Removed as of 03/2019. The number of cancelled delayed tasks found by the + lazy approach is 0 more than 99% of the time. + + adityakeerthi@google.com + fdoray@chromium.org + + Lower-bound percentage of tasks in the DelayedTaskManager that have been + cancelled. An exact number is not recorded, as it could potentially be + expensive to calculate. Instead, a lazy count is maintained by noting + cancelled tasks as new delayed tasks are added. Recorded every time the + ServiceThread performs a heartbeat latency report. + + + + + + Removed 4/2017. Units changed from milliseconds to microseconds. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Time elapsed between when a task is posted and when it starts to run. + Recorded for each task that runs inside the TaskScheduler. This metric is + useful to determine true latency of the average task in the average runtime + scenario. Its total count can also be used as a proxy for the number of + tasks posted to a given category. On the other hand, a fallout of this + metric is that timing every task means each report is dependent on the many + things that can cause an individual task to be delayed (e.g. tasks on a + single bogged down sequence will be reported with high latency even if not + stalling the scheduler itself). See + TaskScheduler.HeartbeatLatencyMicroseconds.* for a metric that is + independent of such factors. + + + + + + Removed 4/2019. Prefix renamed to ThreadPool. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Time elapsed between when a task is posted and when it starts to run. + Recorded for each task that runs inside the TaskScheduler. + + + + + + Removed 07/2020. + + alancutter@chromium.org + calamity@chromium.org + joelhockey@chromium.org + + Number of times that each menu item is clicked from the terminal system app + menu button. + + + + + + Removed 06/2020 as it is no longer needed for analysis. + + katie@chromium.org + dtseng@chromium.org + dmazzoni@chromium.org + + The user picked a default voice of the specified voice ID, which is hashed + from a JSON string of the voice name and extension ID. + + + + + + Removed 06/2020 as it is no longer needed for analysis. + + katie@chromium.org + dtseng@chromium.org + dmazzoni@chromium.org + + When the user requests a preview of a text-to-speech voice, records which + voice was previewed. + + + + + + Removed 08/2018. + + katie@chromium.org + dtseng@chromium.org + dmazzoni@chromium.org + + True if a voice parsed from a ttsEngine extension manifest has a specific + gender. This is recorded each time a TTS extension is parsed, which may + occur multiple times per extension, in tts_engine_manifest_handler: + TtsVoices::Parse. + + + + + + Removed 08/2018. + + katie@chromium.org + dtseng@chromium.org + dmazzoni@chromium.org + + True if a voice specified in chrome.ttsEngine.updateVoices by a ttsEngine + extension has a specific gender. + + + + + + Removed 12/2017. + + pmonette@chromium.org + + Records the size of the in-memory representation of the installed + third-party programs on the user's machine. + + + + + + Removed 07/2018. + + pmonette@chromium.org + + Records the time it took to gather the list of installed third-party + programs and their install location or components. + + + + + + Removed as of 14 Aug 2018 as reporting to this metric was incorrect since + its inception. Replaced by ThirdPartyModules.ShellExtensionsCount2. + + pmonette@chromium.org + + The number of registered shell extensions found on the user's machine. This + is emitted shortly after startup when the shell extensions enumeration takes + place. + + + + + + Removed on 30/08/2018 now that the enumeration removes duplicate entries. + + pmonette@chromium.org + + The number of registered shell extensions found on the user's machine. This + is emitted shortly after startup when the shell extensions enumeration takes + place. + + + + + + Removed 7/2020. Not used in active investigations. + + etiennep@chromium.org + fdoray@chromium.org + gab@chromium.org + + Number of workers running a task in a given SchedulerWorkerPool. Recorded + every 59 minutes (sampling rate is not expected to affect the distribution). + + + + + + Removed 8/2019. Not used in active investigations. + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Number of tasks executed by a SchedulerWorker between two waits on its + WaitableEvent. This should be maximized without affecting perceived browser + performance. + + + + + + Stopped recording on 21/4/2020 due to a bug. + + fdoray@chromium.org + scheduler-dev@chromium.org + + Number of tasks in a ThreadPool sequence, recorded every time a task is + pushed to a sequence. This is recorded to determine how often the size of a + sequence grows above 10000 tasks, and whether it is reasonable to upload a + process dump when that happens. + + + + + + Removed 7/2020. Not used in active investigations. + + etiennep@chromium.org + fdoray@chromium.org + gab@chromium.org + + Number of workers that live in a given SchedulerWorkerPool. Recorded every + 59 minutes (sampling rate is not expected to affect the distribution). + + + + + + Doesn't exist anymore as of 2019-06. + + treib@chromium.org + + A page thumbnail (for use on the New Tab page) was added to TopSites. + + + + + + Removed 2019-03. + + treib@chromium.org + + The result of trying to capture a thumbnail of the current page. + + + + + + Replaced by Compositing.Renderer.GPUMemoryForTilingsInKb which is an + existing metric tracking the same value. + + xidachen@chromium.org + ericrk@chromium.org + + The amount of GPU memory, in kilobytes. Recorded on devices with less than + or equal to 512MB of memory and when tile manager had sufficient memory to + schedule all visible tiles. + + + + + + Replaced by Compositing.Renderer.GPUMemoryForTilingsInKb which is an + existing metric tracking the same value. + + pdr@chromium.org + ericrk@chromium.org + + The amount of GPU memory used for tiles, in kilobytes. Recorded when the + tile manager had sufficient memory to schedule all visible tiles. + + + + + + We no longer have component actions. + + rdevlin.cronin@chromium.org + + The number of component action icons the Browser Actions Container knows + about (visible or in the overflow bucket). Does not count icons that have + been permanently hidden by the user. Measured once per startup per + (non-incognito) profile. + + + + + + After the removal of component actions, this histogram is equivalent to + ExtensionToolbarModel.BrowserActionsCount. See that histogram instead. + + rdevlin.cronin@chromium.org + + The total number of action icons the Browser Actions Container knows about + (visible or in the overflow bucket). Does not count icons that have been + permanently hidden by the user. Measured once per startup per + (non-incognito) profile. + + + + + + Obsolete. See ExtensionToolbarModel.BrowserActionsVisible instead. Stopped + recording 2019-07. + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of visible toolbar icons in the Browser Actions Container + (visible as in number of icons not in the overflow bucket). 0 means all + icons are in the overflow bucket. MAX_INT means the toolbar is always + showing all icons. Measured once per startup per (non-incognito) profile but + only for those profiles that have one or more browser actions showing in the + toolbar. + + + + + + Stopped recording 2019-07. + + rdevlin.cronin@chromium.org + + The number of millseconds between when the user opens the app menu and when + the app menu is closed. Logged once per app menu run when the menu closes. + Not recorded for menu runs that are initiated by a drag-and-drop sequence. + Note that the code paths for Views-platforms vs Mac are different, so cross- + platform comparison may not always be reasonable. + + + + + + Long removed. + + peterlaurens@chromium.org + + The number of millseconds between the user requesting a new tab, e.g. by + tapping the New Tab entry in the main tools menu, and it completing its + animation on screen. + + + + + + Removed in M86. + + alemate@chromium.org + + The number of times TopSitesImpl::ApplyBlockedUrls is called. + + + + + + Removed in M86. + + alemate@chromium.org + + The number of urls blocked in TopSites. Logged every time + TopSitesImpl::ApplyBlockedUrls is called. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + + Tracks how often each touch action is allowed (AKA the frequency of each + effective touch action) at the end of each touch sequence. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + + Tracks how often the effective touch action computed by blink is or is not + equivalent to the whitelisted touch action computed by the compositor at the + end of each touch sequence. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + + Tracks how often a gesture event is or is not dropped due to the current + allowed touch action state not matching the gesture event. + + + + + + Removed in 06/2020. + + xidachen@chromium.org + nzolghadr@chromium.org + + Track whether a gesture event is allowed or filtered or deferred. + + + + + + Removed 8/2017. + + jhawkins@chromium.org + + Tracks unusual CrOS touchpad operational states (e.g. running into the noisy + ground issue). This is sampled at every touchpad event. + + + + + + Removed as of 6/2013, replaced by Touchpad.PointerSensitivity.Changed. + + jhawkins@chromium.org + Tracks touchpad sensitivity setting changes by the user. + + + + + Removed as of 6/2013, replaced by Touchpad.PointerSensitivity.Started. + + jhawkins@chromium.org + Tracks touchpad sensitivity setting on startup. + + + + + Removed as of 7/2013. + + jhawkins@chromium.org + + + + + Removed as of 7/2013. + + jhawkins@chromium.org + + + + + Removed as of 7/2018. + + aelias@chromium.org + + How the user interacted with the tap disambiguation feature on Android. + + + + + + Removed as of 09/2017. Code measured by this histogram no longer exists. + + fdoray@chromium.org + + Time spent in base::ThreadData::GetRetiredOrCreateThreadData(). This method + is called at most once per thread, when its name is set, when it posts a + task or when it runs a task (whichever comes first). + + + + + + Removed 2018/07. + + sclittle@chromium.org + bengr@chromium.org + + The amount of time spent waiting to perform an amortization run. This is + logged at the end of each amortization run, before passing any DataUse + objects to their respective callbacks. + + + + + + Removed 2018/07. + + sclittle@chromium.org + bengr@chromium.org + + The number of DataUse objects processed in an amortization run. + + + + + + Removed 2018/07. + + sclittle@chromium.org + bengr@chromium.org + + The number of unique tabs seen across all DataUse objects buffered for a + single amortization run by the TrafficStatsAmortizer. This is recorded even + if TrafficStats byte counts are unavailable, but not recorded if no DataUse + objects have been buffered. + + + + + + Removed 2018/07. + + sclittle@chromium.org + bengr@chromium.org + + The total bytes after performing amortization across all DataUse objects + buffered for a single amortization run by the TrafficStatsAmortizer. This is + recorded even if TrafficStats byte counts are unavailable, but not recorded + if no DataUse objects have been buffered. + + + + + + Removed 2018/07. + + sclittle@chromium.org + bengr@chromium.org + + The total bytes before performing amortization across all DataUse objects + buffered for a single amortization run by the TrafficStatsAmortizer. This is + recorded even if TrafficStats byte counts are unavailable, but not recorded + if no DataUse objects have been buffered. + + + + + + Removed as of 11/2017, since cld2 is deprecated. + + rkaplow@google.com + + Accuracy of the language detected by CLD2. Only recorded if the detection + returned a "known" result. + + + + + + Removed as of 11/2017, since cld2 is deprecated. + + rkaplow@google.com + Language of page detected by CLD2. + + + + + Removed as of 04/2020. No longer used for analysis. + + anthonyvd@chromium.org + yyushkina@chromium.org + chrome-language@google.com + + Whether or not the backoff threshold for triggering Translate on UI-language + content is reached when the translation process is initiated. + + + + + + Removed as of 11/2013, and replaced by Translate.InitiationStatus.v2. + + chrome-language@google.com + kenjibaheux@google.com + + The reason why Chrome decided to perform the next action (e.g., to show + infobar, to translate a page without any prompting, and so on) when Chrome + Translate is ready to translate a page. + + + + + + Removed from code as of 04/2020. + + chrome-language@google.com + + This metric logs CLD3-detected languages for pages that specify a + conflicting English language in their markup. In these cases, we must decide + on a language source to favor. + + Bucket names are of the form "x,y", where x is the common English + language code specified in the page markup (or "other" if the + English language code is uncommon), and y is the CLD3-detected language. + + This histogram only logs detection conflicts. Hence, "matching" + buckets (e.g. "en,en", "en-AU,en") will never be + populated. + + + + + + Removed 2/2018 + + chrome-language@google.com + joelhockey@chromium.org + + The time spent capturing plain text from the DOM. This is reported by + ChromeRenderViewObserver when a page is loaded completely. + + + + + + Removed 5/2013 by Translate.UndisplayableLanguage + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the detected language is not supported by Translate + Element. + + + + + + Removed 7/2010. No longer tracked. + + chrome-language@google.com + kenjibaheux@google.com + + The number of times an infobar proposing to translate a page has been shown. + + + + + + Removed 06/2020. Duplicate of Translate.ShowErrorUI + + chrome-language@google.com + kenjibaheux@google.com + + Chrome Translate shows an error infobar when an error happens on translation + and the infobar message depends on what kind of error happens. This metric + counts how often each error message is shown. + + + + + + Retired in M77 in favour of TrustedWebActivity.TimeInVerifiedOrigin.V2 which + uses a more appropriate timescale. + + peconn@chromium.org + peter@chromium.org + + Time spent in a verified origin until navigating to an unverified one or + pausing the Trusted Web Activity. + + + + + + Retired in M77 in favour of TrustedWebActivity.TimeOutOfVerifiedOrigin.V2 + which uses a more appropriate timescale. + + peconn@chromium.org + peter@chromium.org + + Time spent out of verified origins until navigating back to a verified one + or pausing the Trusted Web Activity. + + + + + + Replaced by Mobile.Splash.TranslucencyRemovalFailed. + + peconn@chromium.org + peter@chromium.org + + Records the cases when removing a Trusted Web Activity's translucency via a + reflective call fails. Only "true" is recorded. + + + + + + Removed 02/2016 in Issue 1741103002, and replaced by + Renderer4.CompositorWheelScrollUpdateThread and + Renderer4.CompositorTouchScrollUpdateThread. + + tdresser@chromium.org + Whether a scroll is executed on main thread. + + + + + Removed in M65. + + kylechar@chromium.org + + The amount of time the CompositorResizeLock was held in milliseconds. This + is a measure of jank as UI will not generate new frames as long as the lock + is held. + + + + + + Removed in M65. + + kylechar@chromium.org + + Tracks whether the CompositorResizeLock is being released due to timing out + or not. + + + + + + Removed in M85. + + kylechar@chromium.org + + The amount of time it took for UI's CompositorFrame to activate due to a + surface synchronization event. This a measure of jank as UI will not + generate new frames as long synchronization is in progress. This metric is + similar to UI.CompositorResizeLock.Duration but measures the new + synchronization code path. + + + + + + Removed 2/2018 by UKM.Entries.SerializedCount2. + + rkaplow@chromium.org + ukm-team@google.com + Number of serialized UKM entries when storing a UKM log. + + + + + Removed in favor of UKM.LogSize.OnSuccess + + asvitkine@chromium.org + holte@chromium.org + + Reports total upload length in bytes when the UKM service type is used. + + + + + + Removed 10/2018 by UKM.Sources.SerializedCount2. + + holte@chromium.org + rkaplow@chromium.org + Number of serialized UKM sources when storing a UKM log. + + + + + Removed 11/2018 for UKM.ConsentObserver.AllowedForAllProfiles. + + bcwhite@chromium.org + rkaplow@chromium.org + ukm-team@google.com + + Information about the determination by the UkmConsentStateObserver on why it + enabled or disabled UKM. + + + + + + Removed 11/2018 for UKM.ConsentObserver.Purge. + + bcwhite@chromium.org + rkaplow@chromium.org + ukm-team@google.com + + Logged in the UpdateSyncState call from the UkmConsentStateObserver. This + records if the UKM allowed change will trigger a purge of the local UKM + data. + + + + + + Replaced by UKM.LogUpload.ResponseOrErrorCode + + holte@chromium.org + rkaplow@chromium.org + + For each upload to the UKM server, log the response received from the + server. + + + + + + Removed in M45. + + asvitkine@chromium.org + + Recorded when the one-time UMA client id reset was performed (and the client + id of this user was migrated). + + + + + + Removed as of August 2015. The histogram showed no unexpected slowness, and + a profiler is a better tool for identifying any future issues. + + asvitkine@chromium.org + + The time to run the external metrics collection task (Chrome OS). + + + + + + Removed as of Jun 2016. The histogram was added for debugging purpose and is + not needed anymore. + + asvitkine@chromium.org + yiyaoliu@chromium.org + + Records attempts to compute the current the signin status and error + encountered when computing. + + + + + + Removed April, 2018 as the information has never shown any problems. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records attempts to create histograms in presistent space and any errors + encountered when doing so. + + + + + + No longer useful or monitored, removed 2020-01-06. + + wnwen@chromium.org + src/base/metrics/OWNERS + + Measures how much time it took to complete all async deferred startup tasks + on the background thread. Only logged on Android. + + + + + + No longer useful or monitored, removed 2020-01-06. + + wnwen@chromium.org + src/base/metrics/OWNERS + + Measures how much time since application was first in foreground till all + deferred tasks are done. Only logged on Android. + + + + + + No longer useful or monitored, removed 2020-01-06. + + wnwen@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Measures how much time it took to complete deferred startup tasks on the UI + thread. Only logged on Android. + + + + + + Removed 01/2017 for + UMA.Debug.EnableCrashUpload.DeferredStartupAsyncTaskDuration. + + wnwen@chromium.org + asvitkine@chromium.org + + Measures how much time it took to complete async deferred startup tasks on + the background thread. Only logged on Android. + + + + + + No longer useful or monitored, removed 2020-01-06. + + wnwen@chromium.org + src/base/metrics/OWNERS + + Measures the maximum amount of time a single deferred startup task took. + + + + + + Replaced by UMA.Debug.EnableCrashUpload.DeferredStartUptime2 + + asvitkine@chromium.org + + Measures how much time since start up it took for onDeferredStartup() to be + called, which schedules enablePotentialCrashUploading() to be executed on an + async task. Only logged on Android. + + + + + + Removed 2017. No longer tracked. + + wnwen@chromium.org + asvitkine@chromium.org + + Measures how much time since application was first in foreground till + deferred tasks are initialized and queued on the idle handler. Only logged + on Android. + + + + + + Replaced by UMA.Debug.EnableCrashUpload.PostDeferredStartUptime2 + + asvitkine@chromium.org + + Measures how much time since start up it took before ChromeActivity's + postDeferredStartupIfNeeded() was called. Only logged on Android. + + + + + + Removed 2017. No longer tracked. + + wnwen@chromium.org + asvitkine@chromium.org + + Measures how much time since application was first in foreground till + ChromeActivity's postDeferredStartupIfNeeded() was called exactly once. Only + logged on Android. + + + + + + Replaced by UMA.Debug.EnableCrashUpload.Uptime2 + + asvitkine@chromium.org + + Measures how much time since start up it took before crash reporting was + enabled via enablePotentialCrashUploading() as part of deferred start up. + Only logged on Android. + + + + + + Replaced by UMA.Debug.EnableCrashUpload.Uptime3 + + asvitkine@chromium.org + + Measures how much time since start up it took before crash reporting was + enabled via enablePotentialCrashUploading() as part of deferred start up. + Only logged on Android. + + + + + + Removed 2017. No longer tracked. + + wnwen@chromium.org + asvitkine@chromium.org + + Measures how much time since application was first in foreground till crash + reporting was enabled as part of deferred start up. Only logged on Android. + + + + + + Replaced by UMA.Truncate* metrics. + + asvitkine@chromium.org + rkaplow@chromium.org + + The number of events that would be discarded at log transmission time + because the event count was already too large. Note that this doesn't + measure actual discards - in case the UMAThrottleEvents feature is disabled, + the discards won't occur. + + + + + + Removed 11/2016 for UMA.FieldTrialAllocator.Used + + lawrencewu@chromium.org + bcwhite@chromium.org + asvitkine@chromium.org + + Size, before padding, of objects allocated from persistent memory in the + browser process for field trials. Updated on each subprocess launch. + + + + + + Removed 2012. No longer tracked. + + asvitkine@chromium.org + + Log whether the --enable-benchmarking flag was set, which causes field + trials to only use the default group. + + + + + + Removed April, 2018 as the information it provides is no longer useful. + + asvitkine@chromium.org + bcwhite@chromium.org + + The number of old metrics files for which a delete was attempted. This is + logged once with each upload operation. Values greater than 1 indicate that + the files are not deletable by the browser and must be cleaned up by + whatever process is creating them. + + + + + + Removed April, 2018 as no problems were ever indicated. + + asvitkine@chromium.org + bcwhite@chromium.org + + The number of metrics files in a directory that need to be uploaded. This is + logged once with each upload operation. + + + + + + Removed 07/2017. Was only for short-term analysis. About 95% of dropped + files were less than 1 day old. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records the last-modified age of a file that was dropped for lack of an + embedded profile. + + + + + + Removed 2019/04 with the resolution of https://crbug.com/695880 + + asvitkine@chromium.org + bcwhite@chromium.org + + Records the number of histograms present in a file that was dropped for lack + of an embedded profile. + + + + + + Removed 2019/04 as times are small, consistent, and now on a background + thread. + + bcwhite@chromium.org + + Tracks the time used to record all histograms from a file with an embedded + profile. + + + + + + Removed 2019/04 with the resolution of https://crbug.com/695880 + + asvitkine@chromium.org + bcwhite@chromium.org + + Records attempts to upload metrics from files with embedded system profiles. + Counts are not necessarily mutually exclusive. + + + + + + This metrics was to provide information for crbug/760317 which has been + resolved. Removed February, 2018. + + bcwhite@chromium.org + + Records various happenings within the FileMetricsProvider for debugging + purposes. + + + + + + Access times are consistently on the order of a few ms. Removed 2019/06. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent checking and mapping an initial metrics + file on disk. + + + + + + Removed April, 2018 as the information it provides is no longer useful. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent checking and mapping initial metrics + from all files on disk. + + + + + + Access times are consistently on the order of a few ms. Removed 2019/06. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent collecting initial stability metrics + from a file on disk. + + + + + + Removed April, 2018 as the information it provides is no longer useful. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent collecting initial stability metrics + from all files on disk. + + + + + + Access times are consistently on the order of a few ms. Removed 2019/06. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent collecting metrics from a file on disk. + + + + + + Removed April, 2018 as the information it provides is no longer useful. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent collecting metrics from all files on + disk. + + + + + + Removed as of August 2015. No longer tracked. + + asvitkine@chromium.org + + For each attempt to generate the low entropy source, log whether or not the + load required generating a new low entropy source. + + + + + + Removed as of October 2017. No longer tracked. + + asvitkine@chromium.org + bcwhite@chromium.org + + Type and flags of every histogram created plus other activities. Counts are + not mutually-exclusive except for the different types. + + + + + + Removed on 2020-03-18. Renamed to + UMA.JavaCachingRecorder.DroppedHistogramSampleCount and reports also + histogram samples dropped due to a limit of the number of cached histograms. + + bttk@chromium.org + src/base/metrics/OWNERS + + Number of histogram samples that were not recorded when flushing due to a + per-histogram sample count limit in the Java in-memory cache. + + + + + + Removed on 2020-03-18 to reduce the number of histograms emitted by the + cache. + + bttk@chromium.org + src/base/metrics/OWNERS + + Number of histograms for which not all samples may have been recorded when + flushing the Java in-memory cache due to a per-histogram sample count limit. + + + + + + Removed on 2020-03-18 to reduce the number of histograms emitted by the + cache. UMA.JavaCachingRecorder.DroppedHistogramSampleCount includes + histogram samples that were reported in this histogram. + + bttk@chromium.org + src/base/metrics/OWNERS + + Number of samples that were not recorded when flushing the Java in-memory + cache due to a histogram count limit. + + + + + + Removed on 2020-03-18. Renamed to + UMA.JavaCachingRecorder.InputHistogramSampleCount. + + bttk@chromium.org + src/base/metrics/OWNERS + + Number of histogram samples seen by the time the Java in-memory cache was + flushed. This is a sum of DroppedSampleCount and FlushedHistogramCount. + + + + + + Removed on 2020-03-18 to reduce the number of histograms emitted by the + cache. + + bttk@chromium.org + src/base/metrics/OWNERS + + The remaining histogram count limit when flushing in the Java in-memory + cache. + + + + + + Removed on 2020-03-18 to reduce the number of histograms emitted by the + cache. + + bttk@chromium.org + src/base/metrics/OWNERS + + The smallest remaining sample count limit in metrics flushed from the Java + in-memory cache. + + + + + + Removed 2020-04 + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Number of bytes in an excessively large log that was discarded at shutdown + instead of being saved to disk to retry during next chrome run. + + + + + + Removed 2020-04 + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Number of bytes in a log was was rejected by server, and then discarded. + + + + + + Removed as of August 2015. The histograms showed no unexpected slowness, and + a profiler is a better tool for identifying any future issues. + + asvitkine@chromium.org + + The time spent to load (de-serialize) unsent logs from local state, recorded + during the MetricsService startup sequence. + + + + + + No longer tracked. + + asvitkine@chromium.org + + Simple counter of the number of times LogLoadComplete was called (bug + demonstration, as we're called more often than once per page load :-/ ) + + + + + + Used for analyzing UMA log uploads on cellular connection, but necessary + after the analysis is finished. + + asvitkine@chromium.org + gayane@chromium.org + + The network connection type for each successful metrics log upload. + + + + + + Removed in favor of UMA.LogSize.OnSuccess + + asvitkine@chromium.org + holte@chromium.org + + Reports total upload length in bytes when the UMA service type is used. + + + + + + This metrics was to provide information for crbug/760317 which has been + resolved. Removed February, 2018. + + bcwhite@chromium.org + + Records the size of the metrics directory size, after failing to be deleted. + This is a temporary metric that will be removed in M63 or M64. + + + + + + This metrics was to provide information for crbug/760317 which has been + resolved. Removed February, 2018. + + bcwhite@chromium.org + + Records the size of the metrics directory size, after being successfully + deleted. This should always be zero unless there is a bug in the return + code. This is a temporary metric that will be removed in M63 or M64. + + + + + + Removed February, 2018 because persistent metrics are fully launched with no + observable change in operation time. + + asvitkine@chromium.org + bcwhite@chromium.org + + Records how much wall time was spent merging, taking snapshots, and + recording histograms for reporting to UMA. + + + + + + Removed 01/2019 in b/110205489 being split into ChromeOS.CWP.CollectPerf and + ChromeOS.CWP.UploadPerf. + + asvitkine@chromium.org + + A count of successes and various failure modes related to collecting and + processing performance data obtained through "perf" on Chrome OS. + + + + + + Removed 2/2017 for Issue 689315 which indicated they weren't being used. + + bcwhite@chromium.org + asvitkine@chromium.org + + Size, before padding, of objects allocated from persistent memory. This is + updated with every allocation. + + + + + + Data showed many files being deleted during rollout and then tapering off to + near zero. Removed 2019/07. + + bcwhite@chromium.org + asvitkine@chromium.org + + Number of old .tmp files of the kind that Windows creates and leaves around + when trying to rename a file to another one that already exists. See + https://crbug.com/934164 + + + + + + Removed as of Jun 2016. The histogram was added for debugging purpose and is + not needed anymore. + + asvitkine@chromium.org + yiyaoliu@chromium.org + + Record the number of loaded profiles when a profile is erased from the + profiles map kept by profile manager. + + + + + + Removed as of Sep, 2013. Gzipping protobufs is now the default. + + asvitkine@chromium.org + Was the UMA protobuf uploaded earlier compressed or not. + + + + + Removed as of August 2015. See UMA.ProtoCompressionRatio instead. + + asvitkine@chromium.org + + Kilobytes saved from gzipping the protobufs before uploading them. + + + + + + Removed as of August 2015. The histograms showed no unexpected slowness, and + a profiler is a better tool for identifying any future issues. + + asvitkine@chromium.org + + The time spent to store unsent logs to local state, which is done + periodically and also during start up if there was an initial stability log. + + + + + + Removed 2020/04 + + asvitkine@chromium.org + bcwhite@chromium.org + src/base/metrics/OWNERS + + The number of subprocesses from which persistent metrics were collected, + logged once with every reporting cycle. + + + + + + Removed 2019/06 after not reporting anything in years. + + asvitkine@chromium.org + bcwhite@chromium.org + + The number of subprocesses, by type, from which persistent metrics are NOT + collected because there is no information about this (likely new) process + type. Process numbers 1000 or greater are "custom" processes used + by embedders. + + + + + + Removed as of August 2015. + + asvitkine@chromium.org + + The number of synthetic field trials added to the UMA log when the system + profile is recorded. Since this is done prior to capturing the histograms + from the current process, this will generally be logged once per UMA log. + + + + + + Removed as of May, 2012 (i.e. Chrome 21+). Replaced by the + UMA.UploadResponseStatus.XML and UMA.UploadResponseStatus.Protobuf + histograms. + + asvitkine@chromium.org + The server returned a 400 code, and we discarded a log. +
+ This tends to indicate that a syntax error is present in a log, such as + would appear when a bogus XML tag is included, or the XML is not balanced + and well structured. +
+ + + + + Removed as of August 2015. This failure case no longer exists. + + asvitkine@chromium.org + + For each attempted UMA upload, log whether the upload was successfully + constructed. An upload might fail to be constructed, for example, if we try + to upload before the system is fully initialized; or if serialization of the + data fails. + + + + + + Replaced by UMA.LogUpload.ResponseOrErrorCode + + asvitkine@chromium.org + + For each upload to the protocol buffer (v2) UMA server, log whether the + upload was successful, or whether there was an error. + + + + + + Removed 2013. No longer tracked. + + asvitkine@chromium.org + + For each upload to the XML (v1) UMA server, log whether the upload was + successful, or whether there was an error. + + + + + + No longer tracked. + + asvitkine@chromium.org + + Log whether the --reset-variation-state flag was set before the low entropy + source was requested. + + + + + + Removed 2013. No longer tracked. + + asvitkine@chromium.org + + The time spent in converting the XML tree into a character buffer when + closing a metrics log (Chrome OS). + + + + + + Removed 2013. No longer tracked. + + asvitkine@chromium.org + + The time spent in freeing the XML writer and tree when closing a metrics log + (Chrome OS). + + + + + + Removed 2018/11, because the consent bump was removed. + + tangltom@chromium.org + msarda@chromium.org + + The action the user takes when the unified consent bump is shown. + + + + + + Removed 2018/11, because the consent bump was removed. + + droger@chromium.org + msarda@chromium.org + tangltom@chromium.org + + Boolean indicating whether the user is eligible for seeing the consent bump. + This metric is recorded at every startup when Unified Consent is enabled. + Note: There can be multiple entries per user. + + + + + + Removed 2018/11, because the consent bump was removed. + + tangltom@chromium.org + msarda@chromium.org + + The reason the consent bump isn't shown to the user. This is recorded at + startup during the migration to Unified Consent. + + + + + + Removed 2018/11 because it's no longer necessary. + + droger@chromium.org + msarda@chromium.org + tangltom@chromium.org + + The reason the unified consent was revoked. This is recorded every time the + consent state changes from "unified consent given" to + "unified consent not given". + + + + + + Renamed as UnifiedConsent.MakeSearchesAndBrowsingBetter.OnStartup in 01/2020 + because today the UnifiedConsent service only manages the Make Searches and + Browsing better feature. + + msarda@chromium.org + droger@chromium.org + + State of the user settings for Sync and Google services, recorded at + startup. Multiple samples may be recorded at once, except for 'None' which + is recorded when no other bucket is used. + + + + + + Removed 05/2018 in Issue 721891 with removal of X11. Replaced by + Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in ChromeOS M69. + Equal to 0 since at least ChromeOS M62. + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when all user-associated + processes (including the X server) have been terminated during the logout + process. This statistic is not collected if the logout is part of a restart + or shutdown. + + + + + + Replaced by Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in + ChromeOS M69. Equivalent to the new name since at least ChromeOS M62. + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when the X server has been + terminated from a previous logout and when Chrome is started again to show + the login screen. + + + + + + Served its purpose; deprecated 9/2018 in M71 (https://crbug.com/827173). + + grt@chromium.org + + The time it took to build and set the URL blacklist on the main thread + within URLBlacklistManager's constructor. + + + + + + Removed 10/2017. + + mmenke@chromium.org + + Size (in kilobytes) of response bodies retrieved as strings from URLFetcher. + + + + + + This was added to assess possible impact of UserActivationV2, by comparing + pre- and post-launch stats. + + mustaq@chromium.org + + Outcomes (success/failure) of transient user activation availability check + attempts for each type of caller frame (null, ancestor, descedant, other). + + + + + + This was added to assess possible impact of UserActivationV2, by comparing + pre- and post-launch stats. + + mustaq@chromium.org + + Outcomes (success/failure) of user activation consumption attempts for each + type of caller frame (null, ancestor, descedant, other). + + + + + + Removed in M57. + + rsleevi@chromium.org + svaldez@chromium.org + + Distribution of Content-Disposition headers sent with x-x509-user-cert + content types. + + + + + + Removed on 2020-07 (crbug.com/975700). + + raleksandrov@google.com + cros-oac@google.com + + Distribution of the default images that users choose in Change Picture + dialog (Chrome OS). One sample is taken each time the user changes picture. + + + + + + Removed in M85. The OOBE user image screen is long gone. + + achuith@chromium.org + + Distribution of the default images chosen on user image screen during + out-of-the-box experience (Chrome OS). One sample is taken each time the + user confirms the choice by clicking OK button. + + + + + + Removed on 2020-07 (crbug.com/1037348). + + raleksandrov@google.com + cros-oac@google.com + + Profile image download result for UserManager (either on behalf of the + Change Picture prefs page, OOBE or scheduled refresh after user login). + + + + + + Removed in M85. The OOBE user image screen is long gone. + + achuith@chromium.org + + Time histogram of the "Choose Picture" OOBE screen display delay. + + + + + + Removed. Chrome can't listen to changes in the background, these are delayed + until the app becomes active again. Use UserInterfaceStyle.CurrentlyUsed + instead. + + javierrobles@chromium.org + rkgibson@google.com + bling-team@google.com + + [iOS] Used on iOS 13+ to report the changes to Light and Dark mode. This is + logged when the interface style changes and Chrome is active. Can be caused + by the system automatic switch or by the user manually changing the style. + + + + + + Removed on 2020-06 (crbug.com/975711). + + raleksandrov@google.com + cros-oac@google.com + + Whether the user pods were enabled during login, and what could disable + them. + + + + + + Removed 5/2017 in Issue 704922. Replaced by V8.ArrayBufferLargeAllocations. + + gdeepti@chromium.org + titzer@chromium.org + kschimpf@chromium.org + Number of bytes requested in an array buffer allocation. + + + + + Removed on 2019-06 (crbug.com/969997). + + mstarzinger@chromium.org + titzer@chromium.org + Size of asm.js module (in asm.js format). + + + + + Removed on 2019-06 (crbug.com/969997). + + mstarzinger@chromium.org + titzer@chromium.org + + Time to convert asm.js code to WebAssembly. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + clemensb@chromium.org + + Throughput of translation of asm.js code to WebAssembly in MB/s. + + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + TBD + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + TBD + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + Time spent generating native code for functions. + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + rmcilroy@chromium.org + + Fraction of the total generated code which was generated using the + Crankshaft optimizing compiler, after each GC in percent. + + + + + + This histogram has been replaced by V8.CompileMicroSeconds. + + hablich@chromium.org + yangguo@chromium.org + Time spent in V8 compiler (full codegen). + + + + + This histogram has been replaced by V8.CompileDeserializeMicroSeconds. + + vogelheim@chromium.org + Time spent deseriailzing code, used by V8 code caching. + + + + + This histogram has been replaced by V8.CompileEvalMicroSeconds. + + yangguo@chromium.org + Time spent in V8 compiler (full codegen) for eval. + + + + + This histogram has been replaced by V8.CompileTime.CacheBehaviour. + + kouhei@chromium.org + + V8 script compile function variant which was picked. This contains + information such as {if,why} v8 {code,parser} was + {produced,consumed,bypassed}. + + + + + + This histogram has been replaced by + V8.CompileTimeMicroSeconds.NoCache.InlineScript. + + yangguo@chromium.org + Time spent compiling an inline script. + + + + + This histogram has been replaced by V8.CompileLazyMicroSeconds. + + hablich@chromium.org + Time spent compiling functions lazily on first run. + + + + + This histogram has been replaced by the subcategories of + V8.CompileTimeMicroSeconds.NoCache + + yangguo@chromium.org + + Time spent compiling a script that cannot be subject to caching. + + + + + + This histogram has been replaced by V8.CompileScriptMicroSeconds. + + yangguo@chromium.org + + Total time spent in compiling a script (incl. parsing/caching). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + This histogram has been replaced by V8.CompileSerializeMicroSeconds. + + vogelheim@chromium.org + Time spent serializing code, used by V8 code caching. + + + + + This histogram is no longer present in V8 + + hablich@chromium.org + Time spent generating deferred code stubs. + + + + + This histogram has been removed. + + ulan@chromium.org + + Number of garbage collections that a detached global context survives, + recorded after each major garbage collection. Values greater than 7 indicate + a memory leak. + + + + + + This histogram is no longer present in V8 + + hablich@chromium.org + + The maximum memory used to store V8 compiled code on a given process. + + + + + + Removed in Feb 2019. No longer tracked in V8. + + gab@chromium.org + + Latency (post-to-schedule) of each parallel task posted during V8 garbage + collection. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in April 2020. No longer tracked. + + hpayer@chromium.org + Time spent doing a full GC during an IdleNotification. + + + + + Removed in April 2020. No longer tracked. + + hpayer@chromium.org + Time spent in IdleNotifications. + + + + + Removed in August 2017. No longer tracked. + + hpayer@chromium.org + Idle time passed to V8 via IdleNotifications. + + + + + Removed in August 2017. No longer tracked. + + hpayer@chromium.org + + Milliseconds the idle time limit was overshot by the IdleNotification. + + + + + + Removed in August 2017. No longer tracked. + + hpayer@chromium.org + + Milliseconds the idle time limit was undershot by the IdleNotification. + + + + + + Removed in April 2020. No longer tracked. + + hpayer@chromium.org + Time spent in LowMemoryNotifications. + + + + + Removed in April 2020. No longer tracked. + + mlippautz@chromium.org + + Type of garbage collection strategy used to collect the young generation. + + + + + + This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. + + hpayer@chromium.org + + External memory fragmentation in the cell space after each GC in percent. + + + + + + This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. + + hpayer@chromium.org + + External memory fragmentation in the old data space after each GC in + percent. + + + + + + This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace. + + hpayer@chromium.org + + External memory fragmentation in the old pointer space after each GC in + percent. + + + + + + This histogram has been replaced by Memory.Experimental.Renderer2.V8. + + ulan@chromium.org + + The committed memory used by V8 in KB averaged over time, logged before each + GC. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the cell space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the code space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the lo space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the map space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the new space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the old data space after each GC in + percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the old pointer space after each GC in + percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + Fraction of the total heap used by the old space after each GC in percent. + + + + + + Removed as of 09/2017. + + hpayer@chromium.org + + The size of committed memory in the cell space after each GC in KB. + + + + + + This histogram has been replaced by + Memory.Experimental.Renderer2.V8.AllocatedObjects. + + ulan@chromium.org + + The live memory used by V8 in KB averaged over time, logged before each GC. + + + + + + This histogram has been replaced by V8.ParseMicroSeconds. + + marja@chromium.org + Time spent in V8 parser. + + + + + This histogram has been replaced by V8.ParseLazyMicroSeconds. + + marja@chromium.org + + Time spent parsing functions when they are lazily compiled on first run. + + + + + + Removed. + + marja@chromium.org + + Time spent parsing functions when they are lazily compiled on first run. + + + + + + Removed. + + marja@chromium.org + Time spent in V8 parser. + + + + + This histogram has been replaced by V8.PreParseMicroSeconds. + + marja@chromium.org + Time spent preparsing source code. + + + + + Removed. + + marja@chromium.org + Time spent preparsing source code. + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + Time spent on rewriting ASTs before compilation. + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + TBD + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + TBD + + + + + This histogram is no longer present in V8. + + yangguo@chromium.org + + The generation a compiled script was found in the compilation cache. + + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + Time spent analysing the usage of variables. + + + + + This histogram is no longer present in V8. + + hablich@chromium.org + TBD + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to execute a single WebAssembly code GC, measured from when it is + triggered until all isolates reported live code and all dead code was freed. + Recorded after each WebAssembly code GC if a high-resolution clock is + available. + + + + + + Removed in M82 (crbug.com/1053286). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to decode a WebAssembly function. Recorded on each validation of a + WebAssembly function. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to decode a WebAssembly module. Recorded for each WebAssembly module + which is decoded for validation, compilation, or deserialization. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Peak memory used to decode a WebAssembly module. Recorded for each + WebAssembly module which is decoded for validation, compilation, or + deserialization. + + + + + + Removed 10/2019. No longer tracked. + + bbudge@chromium.org + clemensb@chromium.org + adamk@chromium.org + + Time to deserialize a WebAssembly module during streaming compilation (via + the 'WebAssembly.compileStreaming' API). Recorded on each streaming + WebAssembly deserialization from the code cache, but only if a + high-resolution clock is available. Note that compilation speed is often + limited by the network speed, which is also reflected in thie metric. + + + + + + Removed 03/2019. No longer tracked. + + titzer@chromium.org + adamk@chromium.org + + Time spent executing WebAssembly. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time for lazy compilation of WebAssembly functions. This is recorded per + function for the functions that are lazily compiled. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Throughput of compilation of lazily compiled WebAssembly functions in KB/s + (size of function in wasm format divided by time to compile it). This is + recorded per function for functions that are lazily compiled. + + + + + + Removed in M82 (crbug.com/1053285). + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The amount of WebAssembly code freed by garbage collection, in MiB. Recorded + for each live module after each full GC. + + + + + + Removed 1/2013. No longer tracked. + + asvitkine@chromium.org + src/base/metrics/OWNERS + + A count of the number of times we hit the code where a field trial is + disabled because no entropy provider was provided. + + + + + + Removed 02/2020. Replaced by Variations.WebViewDownloadJobFetchTime2, which + has a higher maximum bucket. + + rmcelrath@chromium.org + src/android_webview/OWNERS + + The duration of the network request to downloads a new WebView variations + seed from the variations server to the central on-device service. + + + + + + Removed 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode. + + asvitkine@chromium.org + + The counts of network error codes encountered by VariationsService when an + attempt to fetch a variations seed from the server fails. + + + + + + Removed 2/2014. No longer tracked. + + asvitkine@chromium.org + + The latency of a VariationsService seed fetch that results in a not modified + response. + + + + + + Removed 2/2014. No longer tracked. + + asvitkine@chromium.org + + The latency of a VariationsService seed fetch that results in neither a + success nor not modified response. + + + + + + Removed 2/2014. No longer tracked. + + asvitkine@chromium.org + + The latency of a VariationsService seed fetch that results in a success + response. + + + + + + No longer logged + + jwd@chromium.org + + If the registry value for Google Update experiment labels contains + Variations experiments, and therefore needs to have them cleared. This will + be recorderd once per sessions, right before attempting to clear the value. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + How long it took to create the X-Client-Data header. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + Removed 9/2012. No longer tracked. + + asvitkine@chromium.org + + Whether or not the network was available when requested by the + VariationsService. + + + + + + Removed as of M85 / Jun 2020. + + rmcelrath@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + Number of consecutive times WebView started up with a stale seed. Only + written by WebView, when its loaded seed is fresh after previously being + stale. Note that this means it won't be written for WebViews that are never + able to get a fresh seed, or ones that consistently have a fresh seed. + + + + + + Removed as of M66 / Jan 2018. Replaced by + Variations.SafeMode.FellBackToSafeMode2. + + isherman@chromium.org + + Whether or not the VariationsService /would/ fall back to Safe Mode, due to + either too many crashes or too many failures to fetch a new seed, given some + initial/unrefined heuristics. Recorded during Chrome startup, when the + VariationsService is created. + + This metric was only reported before Safe Mode was actually implemented, as + a sanity-check for the forthcoming implementation. + + + + + + Removed as of 9/2015. + + gab@chromium.org + + Logged on startup when creating field trials from the variations seed if the + build time is ahead of or within 24 hours of the kVariationsSeedDate. Used + as an experiment to see whether the build time could be used to discard very + old seeds. + + + + + + Removed as of 9/2015. + + gab@chromium.org + + Logged on startup when creating field trials from the variations seed if the + build time is behind the kVariationsSeedDate by a day or more. Used as an + experiment to see whether the build time could be used to discard very old + seeds. + + + + + + Removed as of 9/2015. + + gab@chromium.org + + Logged on startup when creating field trials from the variations seed if the + system clock is ahead of or within 24 hours of the kVariationsSeedDate. Used + as an experiment to see whether the system clock could be used to discard + very old seeds. + + + + + + Removed as of 9/2015. + + gab@chromium.org + + Logged on startup when creating field trials from the variations seed if the + system clock is behind the kVariationsSeedDate by a day or more. Used as an + experiment to see whether the system clock could be used to discard very old + seeds. + + + + + + Removed in M61, and replaced by Variations.SeedLoadResult. This histogram + incorrectly conflated failures from loading the seed with failures while + attempting to store seeds with delta compression. + + asvitkine@chromium.org + + Records whether the variations seed was successfully read from local state + on startup. Records a detailed reason on read failure. + + + + + + Removed 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode. + + asvitkine@chromium.org + + The counts of HTTP response codes encountered by VariationsService when + attempting to fetch a variations seed from the server. + + + + + + Removed 2019-06. See results on https://crbug.com/936172#c8. + + changwan@chromium.org + + Records the time spent loading the variations seed in WebView, specifically, + the time to call VariationsUtils.readSeedFile(). This is logged once per + WebView startup, and is only logged if loading was successful. + + + + + + Removed 2019-06. See results on https://crbug.com/936172#c8. + + changwan@chromium.org + + Records how long we would block WebView startup to wait for the variations + seed if there were no timeout. This is measured from when we start blocking + until when the FutureTask which loads the seed finishes. The FutureTask may + finish before we block at all, in which case this will be 0. This is logged + once per WebView startup, whether or not loading was successful. + + + + + + Removed 11/2012. No longer tracked. + + asvitkine@chromium.org + + Whether or not the 1-Percent uniformity trial from the Variations server was + expired when loaded. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + On successful save of a delta-compressed variations seed, records the size + of the delta in KiB. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + On successful save of a delta-compressed variations seed, records the size + of the delta as a percentage of the decoded seed size. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + Records the size of the gzip-compressed variations seed in KiB. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + Records the size of the gzip-compressed variations seed as a percentage of + the decoded seed size. Note that variations seed could be first + delta-compressed and then gzip-compressed. In this case we record + gzip-compressed seed size as a percentage of the delta-compressed seed size. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + Records whether a country code was present when storing the variations seed. + + + + + + Removed 2019/07 + + asvitkine@chromium.org + + On successful save of a non-delta-compressed variations seed, records the + size of the received seed in KiB. + + + + + + Removed 1/2013. No longer tracked. + + asvitkine@chromium.org + + A count of the number of times we hit the code where the + UMA-Uniformity-Trial-1-Percent field trial is disabled as a result of the + expiration check. + + + + + + Removed 1/2013. No longer tracked. asvitkine@chromium.org - Recorded when the one-time UMA client id reset was performed (and the client - id of this user was migrated). + Tracks whether the UMA-Uniformity-Trial-1-Percent field trial was not active + and which factors contributed to it. + + + + + + Removed 2019/6 because it's equivalent to VirtualKeyboard. + ControllerStateTransition. + + oka@chromium.org + + Validity of a state transtion. This is equivalent to the positiveness of + VirtualKeyboard.ControllerStateTransition. + + + + + + Removed 04/2016 as doesn't have data nor owner. + + Please list the metric's owners. Add more owner tags as needed. + + Counts the number of keys typed by the virtual keyboard between each + backspace. This metric provides a rough approximation of an error rate for + the virtual keyboard. + + + + + + This previously reported a latency metric for Viz on all platforms. This has + been replaced by improved tracing and Graphics.Smoothness metrics. Marked + obsolete in M87. + + jonross@chromium.org + + Records the delta from when a viz::LocalSurfaceId was allocated, to the time + where it is first embedded by the Viz Service. + + + + + + Previously recorded for CrOS, but is no longer used. Marked obsolete in M86. + + xiaohuic@chromium.org + + Records the time between a voice interaction session start and end. + + + + + + Removed 02/2018 in issue 799074. + VR.Component.Assets.DurationUntilReady.OnRegisterComponent measures the + intended metric more accurately. + + tiborg@chromium.org + + Duration from starting Chrome until VR assets component is ready to use. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + Duration from entering a VR mode until the VR assets component is ready to + use. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + Duration from registering VR assets component until it is ready to use. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + Status of the VR assets component when entering a VR mode. + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + The component version and status of loading the VR assets. The value is + encoded as (XXX)(YYY)(SSS) where XXX is the major component version, YYY the + minor component version and SSS the status. See + //chrome/browser/vr/assets_load_status.h for possible status values. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + The version and update status of the VR assets component. The value is + encoded as (XXX)(YYY)(SSS) where XXX is the major version, YYY the minor + version and SSS the status. See + //chrome/browser/vr/assets_component_update_status.h for possible status + values. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + Recorded every time a user tries to enter the VR browser without the VR + feature module installed. Is success if the user could enter the VR browser + nonetheless. Is failure if entering the VR browser was blocked (on + smartphone VR) or started in 2D-in-VR mode (on standalones). + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + Network connection type when entering a VR mode. + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + + Network connection type when registering the VR component(s). + + + + + + Removed 02/2020 + + xr-dev@chromium.org + + Number of times voice search is started in a single VR session. Recorded + when a new disjoint session has begun or when the session has ended in a + non-continuable way. + + + + + + Removed 06/2020. + + xr-dev@chromium.org + + We must suppress monocularly rendered ui elements in VR. This records which + ui element suppressions are encountered in practice. + + + + + + Removed 06/2020. + + vollick@chromium.org + + We must exit VR mode when browsing in certain situations. This records which + situations are encountered in practice. + + + + + + Removed 06/2020. + + xr-dev@chromium.org + The end state of a voice search request in VR. + + + + + Removed 06/2020. + + xr-dev@chromium.org + + Chrome shows a prompt when the OS's record audio permission is needed for + voice search. The prompt gives user two choices: CANCEL or CONTINUE. This + records the user's selection. + + + + + + Removed as of 02/2019, VR DLAs are no longer supported. + + ymalik@chromium.org + + Whether we're auto-presenting the first time we enter WebVR mode. + + + + + + As of 5/18/2020 this appears to no longer be logged. + + alcooper@chromium.org + xr-dev@chromium.org + + The result of calls to VRDisplay::requestPresent(). Reported twice per + requestPresent() call, once to record the call, and once to record the + result. + + + + + + Removed 06/2020. + + alcooper@chromium.org + xr-dev@chromium.org + The version of the runtime being used for VR. + + + + + Removed 02/2020 + + alcooper@chromium.org + xr-dev@chromium.org + + Count of navigations while in a VR session. Logged when a new disjoint + session has begun, or when the session has ended in a non-continuable way. + + + + + + Removed as of 02/2019, VR DLAs are no longer supported. + + ymalik@chromium.org + + The duration of a single VR session initiated via a deep-linked WebVR app. + Logged when a new disjoint session has begun, or when the session has ended + in a non-continuable way. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's accept legal + document API call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's authenticate + instrument API call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's get full wallet API + call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's get wallet items + API call. + + + + + + Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's save address API + call. + + + + + + Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's save instrument API + call. + + + + + + Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's save instument and + address API call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's save to wallet API + call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's send status API + call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's unknown API calls. + + + + + + Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's update address API + call. + + + + + + Removed as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet. + + estade@chromium.org + + Measures the time taken by Google Online Wallet server's update instument + API call. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + + Counts the number of times each Wallet API failed due to being unable to + parse the response. + + + + + + requestAutocomplete was removed in M52. + + estade@chromium.org + HTTP response codes seen by Wallet client. + + + + + Removed 08/2016 because CertVerifier is not used for web view cert + verification. + + eugenebut@chromium.org + + [iOS] Reports certificate verification mismatch between SecTrust API and + CertVerifier. SecTrust API is used for making load/no-load decision and + CertVerifier is used for getting the reason of verification failure. It is + expected that mismatches will happen for those 2 approaches (e.g. SecTrust + API considers cert as good, but CertVerifier considers same cert as bad). + This metric helps to understand how common mismatches are. + + + + + + Removed as of 9/2013, replaced by + Web.CurrentOriginEqualsLastCommittedOrigin. + + michaeldo@chromium.org + + [iOS] Reports URL matches between the return value from the WebState's + GetLastCommittedURL and GetCurrentURL methods. It is expected the values + will be equal to confirm that GetCurrentURL can now be replaced with + GetLastCommittedURL. This will be called each time WebStateImpl:: + GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an + old method of obtaining the url and trust level. The trust level was only + relevant with UIWebView, so this method is only called from code which has + not yet been updated since UIWebView was removed. + + + + + + Removed 2017-09. As of M64, this is no longer recorded. + + hanxi@chromium.org + ranj@chromium.org + yfriedman@chromium.org + + Records the available space that can be used when installing a WebAPK from + Google Play succeeds. The space recorded is the available space beyond the + system's minimum free space threshold, with a range between -1000 and 1000 + MB. Negative values mean that there is less free space available than the + system's minimum, by the given amount. + + + + + + Removed in Chrome M69. + + hanxi@chromium.org + yfriedman@chromium.org + + Records the available space that can be used when installing a WebAPK from + Google Play fails after freeing up cache and unimportant storage. The space + recorded is the available space beyond the system's minimum free space + threshold, with a range between -1000 and 1000 MB. Negative values mean that + there is less free space available than the system's minimum, by the given + amount. + + + + + + Removed in Chrome M69. + + hanxi@chromium.org + ranj@chromium.org + yfriedman@chromium.org + + Records the available space that can be used when installing a WebAPK from + Google Play fails after freeing up unimportant storage. The space recorded + is the available space beyond the system's minimum free space threshold, + with a range between -1000 and 1000 MB. Negative values mean that there is + less free space available than the system's minimum, by the given amount. + + + + + + Removed 2020-04. + + hanxi@chromium.org + yfriedman@chromium.org + + Records the Chrome cache size when installing a WebAPK from Google Play + fails, with a range between 0 and 1000, rounded to the nearest 10MB. + + + + + + Removed in Chrome M69. + + hanxi@chromium.org + ranj@chromium.org + yfriedman@chromium.org + + Records the Chrome unimportant storage size when installing a WebAPK from + Google Play fails, with a range between 0 and 1000, rounded to the nearest + 10MB. + + + + + + Removed in Chrome M69. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + Records the amount of time that it takes to bind to the play install service + for WebAPK installs. + + + + + + Deleted in M61. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + On web app and WebAPK installation, records whether a WebAPK could be + installed via the Google Play flow. If not, records why the WebAPK could not + be installed via the Google Play flow (and a web app was added to the + homescreen instead). Warning: This metric is recorded whenever a site is + added to the homescreeen as a web app, not just for sites with a WebAPK + compatible Web Manifest. + + + + + + Removed 2017-08. As of M62, this is no longer recorded. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or + the add to homescreen menu item. This stat tracks whether the installation + is triggered by an app banner or by the add to homescreen menu. + + + + + + No longer recorded as of M65. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or + the add to homescreen menu item. If the installation is via an app banner, + user could either accept to install or dismiss the infobar; while via the + add to homescreen menu, the installation will start automatically. This stat + tracks the ways that user accepts to install a WebAPK. + + + + + + Removed 2020-04. + + hanxi@chromium.org + yfriedman@chromium.org + + Whether there is enough space to install a WebAPK. Recorded on each attempt + to install a WebAPK. + + + + + + Removed 2017-08. As of M62, this is no longer recorded. + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or + the add to homescreen menu item. If the user clicks the add to homescreen + menu, and a WebAPK has been installed before, an infobar with an open button + will show. The open button will also show on the infobar after a successful + installation. This stat tracks whether user clicks the open button on the + infobar or dismiss it. + + + + + + Removed 2018-01. Replaced by WebApk.LaunchInterval2 + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + Records the amount of time since the user last launched the WebAPK from the + homescreen. Not recorded on first launch. + + + + + + Removed 2020-01. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + Records the amount of time since the user last launched the WebAPK from the + homescreen. Not recorded on first launch. + + + + + + Removed 2020-04. + + hartmanng@chromium.org + peconn@chromium.org + pkotwicz@chromium.org + + Recorded each time that a child tab - e.g. a tab opened via window.open() - + is navigated. Records whether the navigation is within the scope of the + WebAPK's Web Manifest. + + + + + + Removed in Chrome M69. + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + When a user visits a PWA for which they have a WebAPK installed, the menu + item changes from 'Add to homescreen' to 'Open WebAPK'. This stat tracks + whether the opening of the WebAPK is successful when this menu item is + clicked. + + + + + + Removed 2017-11. This UMA logs extra requests. Replaced by + ChromePermissionDenied2. + + hanxi@chromium.org + pkotwicz@chromium.org + ranj@chromium.org + yfriedman@chromium.org + + The number of Android runtime permission requests that are denied for the + WebAPK because Chrome does not have access to that permission. + + + + + + Removed 2020-03. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + The number of Android runtime permission requests that are denied for the + WebAPK because Chrome does not have access to that permission. + + + + + + Removed 2020-03. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + Records the amount of requests of Android runtime permissions which haven't + been granted to Chrome when Chrome is running in WebAPK runtime. + + + + + + Removed 2018-08 in favour of WebApk.Session.TotalDuration2. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + The length of a WebAPK session (launch/foregrounding to backgrounding) in + milliseconds. + + + + + + Removed 2018-08 in favour of WebApk.ShellApkVersion2. + + hanxi@chromium.org + pkotwicz@chromium.org + yfriedman@chromium.org + + Records WebAPK "Shell APK version" when the WebAPK is launched. + The "Shell APK version" is documented in shell_apk_version.gni + + + + + + Removed 3/2019 because only counts PWAs. Superseded by the WebApp.Engagement + histogram with suffixes. + + calamity@chromium.org + mgiuca@chromium.org + + The type of engagement (navigation, user input, etc.) which led to an + accumulation in site engagement within a PWA app window. Should be collected + for a subset of SiteEngagementService.EngagementType, which is triggered for + all browsing contexts. Recorded at the time of engagement accumulation + (e.g., when mouse is clicked). + + + + + + Removed 2019-11 and replaced by Webapp.Install.DisplayMode2, which correctly + records manifest display modes on desktop. + + peter@chromium.org + yfriedman@chromium.org + + Records the display mode (as defined in the Web App Manifest spec) at the + install time of a WebApp (including WebApks). + + + + + + Removed 2018-01 in favour of Webapp.Install.InstallEvent. + + mcgreevy@chromium.org + + Records the mechanism by which a web app installation was triggered, + regardless of whether the installation was successful. + + + + + + Expired in M77. + + dominickn@chromium.org + + Records whether or not the check that a site is or isn't a Progressive Web + App (PWA) completes before the add to homescreen dialog on Android forcibly + times out and falls back to generating an icon. + + + + + + Expired in M77. + + dominickn@chromium.org + + Records whether or not the check that a site is or isn't a Progressive Web + App (PWA) has completed when the user taps the add to homescreen menu item + on Android. + + + + + + Expired in M77. + + dominickn@chromium.org + + Records whether or not the check that a site is or isn't a Progressive Web + App (PWA) has completed when the user opens the menu on Android. + + + + + + Replaced by Webapp.SystemApps.FreshInstallDuration in 09/2020, issue + https://crbug.com/1129275. + + calamity@chromium.org + ortuno@chromium.org + + Records the number of seconds taken to install system web apps, from when we + dispatch a call to install them, until we get all the installation results. + Recorded in milliseconds, from 1 millisecond to 3 minutes. + + + + + + Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer + needed or recorded. + + mlamouri@chromium.org + + Records the status of the splashscreen's background color (default or + custom). + + + + + + Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer + needed or recorded. + + mlamouri@chromium.org + Records the time during which the splashscreen was visible. + + + + + Removed 2020-04. + + pkotwicz@chromium.org + hartmanng@chromium.org + Records the signal that was used to hide the splashscreen. + + + + + Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer + needed or recorded. + + mlamouri@chromium.org + + Records the size of the icon used to construct the splashscreen in device + pixels (ie. real size divided by device pixel density). This is only + recording one dimension, the icon being square. + + + + + + Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer + needed or recorded. + + mlamouri@chromium.org + + Records the origin of the icon used to construct the splashscreen. + + + + + + Removed 07/2019 in Issue http://crbug.com/1716136. Information no longer + needed or recorded. + + mlamouri@chromium.org + + Records the status of the splashscreen's theme color (default or custom). + + + + + + Removed 08/2020. Information no longer recorded. + + alancutter@chromium.org + loyso@chromium.org + + Records installation result code for sync initiated fallback installs in the + new USS-based web applications system. + + + + + + Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher + supported sample rates. + + rtoy@chromium.org + hongchan@chromium.org + + The sample rate (in Hz) requested by createBuffer(). Recorded for every call + to createBuffer(). Probably many (tens or hundreds) per page. + + + + + + Replaced by SampleRateRatio384kHz in Issue 644683 on 2016/10 due to higher + supported sample rates. + + rtoy@chromium.org + hongchan@chromium.org + + The ratio of the buffer sample rate from createBuffer() to the context + sample rate. This indicates if the buffer needs to be resampled. Recorded + for every call to createBuffer(). Probably many (tens or hundreds) per page. + + + + + + Removed 02/2018 in Issue 764396. Information no longer needed or recorded. + + rtoy@chromium.org + hongchan@chromium.org + + The number of times the AudioParam value setter was called that also + conflicts with an ongoing AudioParam automation. Updated when the realtime + AudioContext is closed. + + + + + + Removed 02/2018 in Issue 764396. Information no longer needed or recorded. + + rtoy@chromium.org + hongchan@chromium.org + + The percentage of number of calls to an AudioParam value setter that + conflicts with an ongoing AudioParam automation to the total number of calls + to the value setter. Updated once when an AudioContext is closed. + + + + + + Removed 02/2018 in Issue 764396. Information no longer needed or recorded. + + rtoy@chromium.org + hongchan@chromium.org + + The number of times the AudioParam value setter was called per tab. Updated + when the realtime AudioContext is closed. + + + + + + Removed in Issue 774526 on 2017/10; statistics aren't needed anymore. + + rtoy@chromium.org + hongchan@chromium.org + + The Q value (in 0.25 dB steps) used for a highpass BiquadFilter. Recorded + each time the value is set for a highpass filter via the .value setter or + the automation methods linearRampToValueAtTime, exponentialValueAtTime, and + setValueAtTime. + + + + + + Removed in Issue 774526 on 2017/10; statistics aren't needed anymore. + + rtoy@chromium.org + hongchan@chromium.org + + The Q value (in 0.25 dB steps) used for a lowpass BiquadFilter. Recorded + each time the value is set for a lowpass filter via the .value setter or the + automation methods linearRampToValueAtTime, exponentialValueAtTime, and + setValueAtTime. + + + + + + Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher + supported sample rates. + + rtoy@chromium.org + hongchan@chromium.org + + The sample rate (in Hz) specified for the offline audio context. Recorded + for every offline context created. Probably only a few per page, but could + be potentially much more (thousands). + + + + + + Removed 2016-09. As of M55, this is no longer recorded. + + mlamouri@chromium.org + + Records whether WebAudio had a user gesture requirement and whether it was + fulfilled. + + + + + + Superseded 02/2020 by WebAuthentication.CableV1DiscoveryEvent + + agl@chromium.org + + Records events that occur during the lifetime of a caBLE v1 getAssertion + operation so that any causes of drop-off can be identified. + + + + + + Removed on 07/2019. + + eugenebut@chromium.org + + [iOS] Chrome for iOS crashes because NavigationManager does not have any + navigation items and visible navigation item is dereferenced + (crbug.com/565457). The assumption is that crash occurs if pending load was + stopped for a child window. This metric will prove or disprove that + assumption. + + + + + + Removed 2017-02. This metric disproved the assumption mentioned in the + summary and it is no longer needed. + + eugenebut@chromium.org + + Chrome for iOS crashes in |didCommitNavigation:| if Navigation Manager is + empty. It's unclear how the app can get into this state and one assumption + is that didStartProvisionalNavigation: does not add a pending navigation. + This metric is logged when didStartProvisionalNavigation: fails to add a + pending item. + + + + + + It is common for WKWebView to have certificateChain, which does not allow + constructing net::X509Certificate. Logging was removed on 2020-01-23. + + eugenebut@google.com + + Whether or not WKWebView has provided a valid -certificateChain when loaded + a page over a secure connection. + + + + + + This has been superseded by Blink.UseCounter.CSSProperties which does not + count multiple times per page load. See https://crbug.com/458925. + + ajuma@chromium.org + + Counts the number of times each CSS property is animated. There is no limit + on the number of times each property is counted per page view -- a property + that is animated multiple times during a single page view is counted each + time it animates. + + + + + + Removed 10/2018 with Blink.Canvas.IsComposited, + Blink.Canvas.ResourceProviderIsAccelerated, + Blink.Canvas.ResourceProviderType and Blink.Canvas.2DLayerBridgeIsDeferred + + zmin@chromium.org + fserb@chromium.org + + The usage of Canvas 2D Context API. Logged when the particular API is used. + + + + + + As of M57 this has been superseded by Blink.UseCounter.Features which fixes + a number of issues. See https://crbug.com/676837. + + rbyers@chromium.org + + Count of how many page loads use various features. The PageVisits bucket is + incremented for each page load, and the other buckets incremented at most + once per PageVisit via the WebCore::UseCounter class. + + + + + + As of M57 this has been superseded by Blink.UseCounter.CSSProperties which + fixes a number of issues. See https://crbug.com/676837. + + mikelawther@chromium.org + + Records usage of CSS properties used on a page, either statically or + dynamically, from the time the page is initialised to when it is closed or + navigated away from. Each property is counted at most once per page per + view. + + + + + + Removed in M77 because we're not tracking this anymore. + + rakina@chromium.org + altimin@chromium.org + + Records how much time it takes for find-in-page scoping over the idle task + deadline. + + + + + + Removed in September 2018 for a version that also tracks if the frame is an + ad frame. + + japhet@chromium.org + + Records instances of child frames navigating the top frame. Includes whether + or not the navigation would have been permitted if not for our special case + for 'framebusting', the practice of ensuring a given document is never + displayed in a frame. + + + + + + Removed in March 2019. + + japhet@chromium.org + jkarlin@chromium.org + + Records instances of child frames navigating the top frame. Includes whether + or not the navigation would have been permitted if not for our special case + for 'framebusting', the practice of ensuring a given document is never + displayed in a frame. It also includes whether the frame that initiated the + navigation was an ad frame or not. + + + + + + As of chrome 26, use {Consistency, Read, Write}Error instead. + + dgrogan@chromium.org + + Count of internal IndexedDB errors (data corruption, I/O errors, etc) + encountered. + + + + + + Removed as of July 2018. + + dgrogan@chromium.org + + Count total number of front end API calls of IndexedDB methods. + + + + + + Removed 1/19. Metric never actually worked, as -1 / 1024 yields 0. + + dgrogan@chromium.org + + Count of how many times LevelDBDatabase got an error trying to check free + disk space. + + + + + + Removed 1/19. Use Quota.AvailableDiskSpace instead. + + dgrogan@chromium.org + + Amount of free disk space on the partition/volume/etc where LevelDB failed + to open. + + + + + + Removed 1/19. Use Quota.AvailableDiskSpace instead. + + dgrogan@chromium.org + + Amount of free disk space on the partition/volume/etc where LevelDB was + successfully opened. + + + + + + Removed in M84. + + cmumford@chromium.org + chrome-owp-storage@google.com + + The time that it takes to write the data IndexedDB to the LevelDB backing + store for a put operation. + + + + + + Removed in M72. + + cmumford@chromium.org + + The time that it takes to commit an IndexedDB transaction to its LevelDB + backing store. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE. + + dgrogan@chromium.org + + Errno errors encountered by a single LevelDBEnv method when opening an + IndexedDB instance. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE. + + dgrogan@chromium.org + + PlatformFileErrors encountered by a single LevelDBEnv method when opening an + IndexedDB instance. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE. + + dgrogan@chromium.org + + Errno errors encountered by a single LevelDBEnv method when reading an + IndexedDB instance. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE. + + dgrogan@chromium.org + + PlatformFileErrors encountered by a single LevelDBEnv method when opening an + IndexedDB instance. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE. + + dgrogan@chromium.org + + Errno errors encountered by a single LevelDBEnv method when writing to an + IndexedDB instance. + + + + + + Removed 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE. + + dgrogan@chromium.org + + PlatformFileErrors encountered by a single LevelDBEnv method when writing to + an IndexedDB instance. + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + The type of key (number, string, etc.) used for an index entry for a record + being newly stored or updated in an Indexed DB object store. For array keys, + the types of sub-keys are not recorded. + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + The type of key (number, string, etc.) used for a record being newly stored + or updated in an Indexed DB object store. For array keys, the types of + sub-keys are not recorded. + + + + + + Removed 2018-11. No longer needed. + + cmumford@chromium.org + + The delay between the receipt of the request to open an IndexedDB database + and the firing of the blocked event. + + + + + + Removed 2018-11. No longer needed. + + cmumford@chromium.org + + The delay between the receipt of the request to open an IndexedDB database + and the firing of the error event. + + + + + + Removed 2018-11. No longer needed. + + cmumford@chromium.org + + The delay between the receipt of the request to open an IndexedDB database + and the firing of the success event. + + + + + + Removed 2018-11. No longer needed. + + cmumford@chromium.org + + The delay between the receipt of the request to open an IndexedDB database + and the firing of the upgradeneeded event. + + + + + + Replaced with WebCore.IndexedDB.PutValueSize2 on 6/2017 + + dmurph@chromium.org + + The size of the IndexedDB value used in an IndexedDB object store 'put' + operation. Recorded for every 'put' operation. + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + Records the 'keyPath' type (none, string, or array) during IDBObjectStore's + createIndex operation. See http://www.w3.org/TR/IndexedDB/ + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + Records the 'multiEntry' flag value during IDBObjectStore's createIndex + operation. See http://www.w3.org/TR/IndexedDB/ + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + Records the 'unique' flag value during IDBObjectStore's createIndex + operation. See http://www.w3.org/TR/IndexedDB/ + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + Records the 'autoIncrement' flag value during IDBDatabase's + createObjectStore operation. See http://www.w3.org/TR/IndexedDB/ + + + + + + Removed August 2019. Was added to measure use of features which not all + actively developed browser engines supported. No longer relevant. + + jsbell@chromium.org + + Records the 'keyPath' type (none, string, or array) during IDBDatabase's + createObjectStore operation. See http://www.w3.org/TR/IndexedDB/ + + + + + + Replaced with WebCore.IndexedDB.TombstoneSweeper.NumDeletedTombstones in + 07/2017. + + dmurph@chromium.org + + Records the number of tombstones encountered by the IndexedDB Tombstone + Sweeper. Recorded on the browser side (back end) when the sweeper has + completed scanning and it is in 'statistics' mode. See + https://goo.gl/coKwA7. + + + + + + Replaced with WebCore.IndexedDB.TombstoneSweeper.DeletionTotalTime.Complete + in 07/2017. + + dmurph@chromium.org + + Records the time it takes for the IndexedDB Tombstone Sweeper to fully scan + the indexes. Recorded on the browser side (back end) when the sweeper has + completed scanning all indexes (so partial scans are not recorded) and it is + in 'statistics' mode. See https://goo.gl/coKwA7. + + + + + + Replaced with WebCore.IndexedDB.TombstoneSweeper.DeletedTombstonesSize in + 07/2017. + + dmurph@chromium.org + + Records the total size of tombstones encountered by the IndexedDB Tombstone + Sweeper. Recorded on the browser side (back end) when the sweeper has + completed scanning and it is in the 'statistics' mode. See + https://goo.gl/coKwA7. + + + + + + Replaced with WebCore.IndexedDB.Transaction.ReadOnly.SizeOnCommit2 on 6/2017 + + dmurph@chromium.org + + The total temporary size of an IndexedDB ReadOnly Transaction. Since this is + a readonly transaction, the size should only be >0 when the transaction + is removing tombstone index keys. Recorded on transaction commit. + + + + + + Replaced with WebCore.IndexedDB.Transaction.ReadWrite.SizeOnCommit2 on + 6/2017 + + dmurph@chromium.org + + The total temporary size of an IndexedDB ReadWrite Transaction. This is the + memory that is temporarily stored before writing to disk. Recorded on + transaction commit. + + + + + + Replaced with WebCore.IndexedDB.Transaction.VersionChange.SizeOnCommit2 on + 6/2017 + + dmurph@chromium.org + + The total temporary size of an IndexedDB VersionChange Transaction. This is + the memory that is temporarily stored before writing to disk. Version change + transactions happen when creating a database or updating a current database + schema. Recorded on transaction commit. + + + + + + Removed, preloads are issued on the main thread now, so this is less useful. + + csharrison@chromium.org + + The delay between when the preload scanner discovers a resource on the + parser thread and when the preload request is issued on the main thread. + + + + + + Removed April 2017. + + clamy@chromium.org + + Number of dead resources found in the memory cache over the lifetime of the + ResourceFetcher. + + + + + + Removed April 2017. + + clamy@chromium.org + + Number of resources that needed to be loaded by the ResourceFetcher over its + lifetime. + + + + + + This metric has been not recorded at least since 2016/01. The displayed enum + labels might be unreliable because C++ enum values of blink::Resource::Type + have been changed over time. + + clamy@chromium.org + + The type of the resource (e.g. image, script...) upon a cache hit. + + + + + + Removed April 2017. + + clamy@chromium.org + + Number of dead resources that needed to be revalidated by the + ResourceFetcher over its lifetime. + + + + + + Removed November 2017. + + rmcilroy@chromium.org + + The amount of time allotted to a requestIdleCallback callback, i.e., the + difference between the time when it is called and when its deadline expires. + + + + + + Removed December 2017. + + rmcilroy@chromium.org + + The amount of time by which a requestIdleCallback callback overran its + deadline. Callbacks which don't overrun their deadline will report an + overrun of 0. + + + + + + Removed April 2020. + + shaseley@chromium.org + The callback type for every idle task that was run. + + + + + Removed April 2020. + + shaseley@chromium.org + + The amount of time an idle task was queued before running. This metric is + only recorded for idle tasks that run during idle periods, not for those + that run as a result of an expired timeout. + + + + + + Removed April 2020. + + shaseley@chromium.org + + The timeout value specified for each idle task that was run, regardless of + whether or not it was run due to its timeout expiring. A value of 0 + indicates that no timeout was specified. + + + + + + Removed April 2020. + + shaseley@chromium.org + + The timeout value for idle tasks that were run because their timeout + expired. + + + + + + Removed as this data was needed for streaming investigations, no longer + needed. + + marja@chromium.org + + Whether a parsing blocking script was already preloaded from the net or the + cache by the time it was needed. + + + + + + Removed as this data was needed for streaming investigations, no longer + needed. + + marja@chromium.org + + Time between the events "script is loaded" and "script is + compiled" for parsing blocking scripts. + + + + + + Removed in M85 as we haven't observed any related performance alerts, and no + team is actively monitoring it. + + xiaochengh@chromium.org + + The amount of time between consecutive spellcheck requests made by Blink, + with the exception that requests made simultaneously checking different + parts of the same editing host count as only one request. + + + + + + Temporary histogram replaced by Blink.UseCounter.CSSProperties. + + rbyers@chromium.org + + + + + Temporary histogram replaced by Blink.UseCounter.Features. + + rbyers@chromium.org + + + + + Temporary histogram replaced by Blink.UseCounter.SVGImage.CSSProperties. + + rbyers@chromium.org + + + + + Temporary histogram replaced by Blink.UseCounter.SVGImage.Features. + + rbyers@chromium.org + + + + + Removed 05/2013, we no longer have the code that uses this metric. + + Please list the metric's owners. Add more owner tags as needed. + + Duration of time taken to create a V8 Context for an isolated world. + + + + + + Removed 05/2013, we no longer have the code that uses this metric. + + Please list the metric's owners. Add more owner tags as needed. + + Duration of time taken to create a V8 Context for the main world. + + + + + + Deprecate 2017-06, as we've collected enough data to discuss. (see issue + 584616). + + yhirano@chromium.org + ricea@chromium.org + + Count the number of changes to WebSocket.binaryType after the connection + opened, per connection. Assignments that match the existing binaryType are + not counted. This is recorded after WebSocket close, whether explicit or due + to error or navigation. It is not recorded if the render process is + destroyed before the WebSocket is closed. + + + + + + Removed 2014-06 when we replaced the WebSocket implementation (see issue + 226931). + + yhirano@chromium.org + ricea@chromium.org + + Count the number of WebSocket handshake for each result. Use this histogram + as a baseline for investigating feature usage counters. + + + + + + Removed as of 2020-09 + + yhirano@chromium.org + ricea@chromium.org + + The sizes of binary WebSocket messages received, broken down by type. One + entry per message. Clamped to 100 MB. + + + + + + Removed as of 2020-09 + + yhirano@chromium.org + ricea@chromium.org + + The sizes of binary WebSocket messages sent, broken down by type. One entry + per message. Clamped to 100 MB. + + + + + + Removed 2014-06 when we replaced the WebSocket implementation (see issue + 226931). + + yhirano@chromium.org + ricea@chromium.org + + Count the number of WebSockets that accepted permessage-deflate extension + for each context take over mode. Used by the old Blink-based WebSocket + implementation. + + + + + + Removed as of 2020-02. + + yhirano@chromium.org + ricea@chromium.org + + Count the number of messages for each message type and set binary type. + + + + + + Removed as of 7/2014. This histogram was used to determine when it would be + ok to remove the deprecated XMLHttpRequest.send(ArrayBuffer) overload. The + support for ArrayBuffer was un-deprecated in the WHATWG spec for XHR, and + subsequently un-deprecated in Blink. + + costan@gmail.com + + Count the number of XHR.send() calls for each argument type to see when we + can deprecate the ArrayBuffer type support. + + + + + + Removed June 2019. + + bashi@chromium.org + kenjibaheux@chromium.org + The success or failure of web fonts CORS-enabled fetching. + + + + + Removed Jan 2020. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + Uncompressed font image size divided by the duration of time OTS takes to + decode the font image, in kilobytes per second. + + + + + + Removed 08/2019. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + Recorded upon an eviction of a cache entry for a font in Google Fonts. + Records the age of the cache entry. + + + + + + Removed 08/2019. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + Recorded upon a cache hit for a font in Google Fonts. Records the age of the + cache entry. + + + + + + Removed 08/2019. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + When a cache entry for a font in Google Fonts is evicted, records the reuse + count of the cache entry. + + + + + + Removed 08/2019. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + Recorded upon a cache hit for a font in Google Fonts. Records the reuse + count of the cache entry. + + + + + + Removed 08/2019 in favor of WebFont.HttpCacheStatus. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + Whether the font was in the cache or not. "Previously in the + cache" means there was an evicted entry for the font in the cache. + Recorded upon a disk cache query for a font in Google Fonts. + + + + + + Removed 10/2017. Related field trial has finished rolling out. + + toyoshim@chromium.org + kenjibaheux@chromium.org + + For each WebFont load attempt, records whether User Agent Intervention was + triggered, and whether the request (would have) timed out or not. The + intervention takes adaptive behaviors to handle loading timeouts to improve + user experiences on slow networks. - + - Removed as of August 2015. The histogram showed no unexpected slowness, and - a profiler is a better tool for identifying any future issues. + Removed 10/2017. Related field trial has finished rolling out. - asvitkine@chromium.org + toyoshim@chromium.org + kenjibaheux@chromium.org - The time to run the external metrics collection task (Chrome OS). + Like InterventionResult, this records whether User Agent Intervention was + triggered, and whether the request (would have) timed out or not. But this + version records only when data actually comes from network, not from disk or + memory cache, and is not provided in a data URL format. - + - Removed as of Jun 2016. The histogram was added for debugging purpose and is - not needed anymore. + Renamed to WebFont.StyleRecalcToDownloadLatency for clarity. - asvitkine@chromium.org - yiyaoliu@chromium.org + kenjibaheux@chromium.org + ksakamoto@chromium.org - Records attempts to compute the current the signin status and error - encountered when computing. + The time from when the webfont was referenced by a calculated style for the + first time to the start of the font download. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.0.Under10KB. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of under + 10KB. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.1.10KBTo50KB. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 10KB-50KB. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.2.50KBTo100KB. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 50KB-100KB. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.3.100KBTo1MB. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 100KB-1MB. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.4.Over1MB. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of over + 1MB. + + + + + + Removed as of 8/2013, replaced by WebFont.DownloadTime.LoadError. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time taken for a webfont download that failed. Includes aborted + requests. + + + + + + Removed Jan 2020. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The packaging format of the font file (e.g. SFNT, WOFF ...) upon a webfont + load. + + + + + + Removed 11/2013. No longer tracked. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time from when the webfont was referenced by a calculated style for the + first time to the start of the font download. Recorded at most once for each + FontResource object (not recorded if the font is retrieved from the memory + cache). + + + + + + Removed 11/2013. No longer tracked. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + For each webfont, this records (a) if the font was 'styled', i.e. referenced + by a calculated style for a RenderText before the font data was used, and + (b) if the font was actually used or not, i.e. the renderer requested the + font data or not. (A Font can be used without being styled, for example when + drawn by a Canvas 2D Context.) This is recorded upon a download request of a + webfont, or destruction of a FontResource object. Recorded at most once for + each FontResource object in the renderer's memory cahce. + + + + + + Removed as of 9/2013, replaced by + WebFont.Resource.StyleRecalcToDownloadLatency. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time from when the webfont was referenced by a calculated style for the + first time to the start of the font download. + + + + + + Removed as of 9/2013, replaced by WebFont.Resource.UsageType. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + For each webfont, this records (a) if the font was 'styled', i.e. referenced + by a calculated style for a RenderText before the font data was used, and + (b) if the font was actually used or not, i.e. the renderer requested the + font data or not. (A Font can be used without being styled, for example when + drawn by a Canvas 2D Context.) This is recorded upon a download request of a + webfont, or destruction of a CSSFontFaceSource object. Recorded at most once + for each url() source of @font-face CSS rule. + + + + + + Removed June 2019. + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The number of webfonts used in a page. This is recorded when the first + layout is done, and so will not count webfonts dynamically loaded by + scripts. + + + + + + Removed March 2020. + + msalama@chromium.org + chrome-signin-team@google.com + + Records the state of web and app activity everytime a request to query sWAA + is completed. The request is triggered when the user opens the history page, + sync setup settings page or clear browsing data dialog. Desktop only. + + + + + + Removed 5/2019 in issue bugs.webrtc.org/10563 due to the reporting component + (AEC2) being deprecated. + + hlundin@chromium.org + + Captures if the estimated delay between rendered and captured audio is out + of bounds which can cause the Echo Cancellation to fail. This is logged + roughly once every 5 seconds. The values are logged in four buckets + reflecting how well the Echo Cancellation likely performs based on the + estimated delay. + + + + + + Removed as of 12/2014, replaced by + WebRTC.ApplicationMaxConsecutiveBytesDiscard.v2. + + guoweis@chromium.org + + The maximum consecutive discarded bytes caused by not enough buffer + available in WebRTC's socket implementation. This happens when WebRTC + IpcPacketSocket's throttling mechanism kicks in. + + + + + + Removed 4/2019 in issue bugs.webrtc.org/10563 due to the reporting component + (AEC2) being deprecated. + + hlundin@chromium.org + + The AEC in WebRTC will sometimes realign the far- and near-end signal + buffers to keep in sync with delay changes in the echo path. This metric + logs each such realignment, storing the delay change in ms, when the change + is triggered by a shift in the signal based delay estimation (a.k.a + delay-agnostic). + + + + + + Removed 4/2019 in issue bugs.webrtc.org/10563 due to the reporting component + (AEC2) being deprecated. + + hlundin@chromium.org + + The AEC in WebRTC will sometimes realign the far- and near-end signal + buffers to keep in sync with delay changes in the echo path. This metric + logs each such realignment, storing the delay change in ms, when the change + is triggered by a shift in system reported delay. + + + + + + Removed 11/2019 due to old AEC system (AEC2) being removed. + + hlundin@chromium.org + + The AEC in WebRTC keeps a buffer to mimic the audio buffers in the lower + layers. This histogram logs a sudden positive jump in buffer size. Since we + detect jumps in the capture thread, only positive values are feasible. Note + that the difference in milliseconds is logged and not the actual AEC system + delay value. Sampled every time the AEC system delay changes more than 50 + milliseconds. + + + + + + Removed in M81 as the metric is no longer used for analysis. + + peah@chromium.org + + This histogram logs the level of the comfort noise in the WebRTC echo + canceller in the lower 4 kHz. A new value is logged every 10 seconds. + + + + + + Removed in M81 as the metric is no longer used for analysis. + + peah@chromium.org + + This histogram logs the level of the comfort noise in the WebRTC echo + canceller between 4 and 8 kHz. A new value is logged every 10 seconds. + + + + + + Removed in M81 as the metric is no longer used for analysis. + + peah@chromium.org + + This histogram logs the echo suppressor gain in the WebRTC echo canceller in + the lower 4 kHz. A new value is logged every 10 seconds. + + + + + + Removed in M81 as the metric is no longer used for analysis. + + peah@chromium.org + + This histogram logs the echo suppressor gain in the WebRTC echo canceller + between 4 and 8 kHz. A new value is logged every 10 seconds. + + + + + + Removed 11/2019 due to old AEC system (AEC2) being removed. + + hlundin@chromium.org + + Number of triggered WebRTC.Audio.AecSystemDelayJump during a call. This is + recorded when a WebRTC based call has ended. AecSystemDelayJump can be + triggered when, for example, the capture thread is stalled, which can harm + the AEC. NumOfAecSystemDelayJumps shows how often this occurs in general as + well as during a call. + + + + + + Removed 11/2019 due to old AEC system (AEC2) being removed. + + hlundin@chromium.org + + Number of triggered WebRTC.Audio.PlatformReportedStreamDelayJump during a + call. This is recorded when a WebRTC based call has ended. + PlatformReportedStreamDelayJump can be triggered when, for example, the + capture thread is stalled, which can harm the AEC. + NumOfPlatformReportedStreamDelayJumps shows how often this occurs in general + as well as during a call. + + + + + + Removed 11/2019 due to old AEC system (AEC2) being removed. + + hlundin@chromium.org + + The difference in stream delay reported to WebRTC by Chrome. Since we detect + jumps in the capture thread, only positive values are feasible. Note that + the difference in milliseconds is logged and not the actual stream delay + value. Sampled every time the stream delay changes more than 50 + milliseconds. + + + + + + Removed 01/2020 due to not being monitored in Chrome. + + hlundin@chromium.org + + The sum of the jitter buffer delay and the sound card's buffering delay for + the receiving side. That is, the sum of the metrics + WebRTC.Audio.ReceiverDeviceDelayMs and + WebRTC.Audio.ReceiverJitterBufferDelayMs. Sampled once every 10 ms when + WebRTC audio is playing. + + + + + + Removed from code 2014/2/25. + + Please list the metric's owners. Add more owner tags as needed. + Duration in milliseconds of WebRTC audio capture session. + + + + + No longer exists in the code as of 2014/2/25. + + Please list the metric's owners. Add more owner tags as needed. + Size of WebRTC audio input buffers (in audio frames). + + + + + No longer exists in the code as of 2014/2/25. + + Please list the metric's owners. Add more owner tags as needed. + + Size of WebRTC audio input buffers (atypical values, in audio frames). + + + + + + Removed from code on 2014/2/25. + + Please list the metric's owners. Add more owner tags as needed. + Audio output channel layout in WebRTC. + + + + + Removed from code Sep 2014. + + henrika@chromium.org + Size of WebRTC audio output buffers (in audio frames). + + + + + Removed from code Sep 2014. + + henrika@chromium.org + + Size of WebRTC audio output buffers (atypical values, in audio frames). + + + + + + Removed from code 2014/2/25. + + Please list the metric's owners. Add more owner tags as needed. + Duration in milliseconds of WebRTC audio render session. + + + + + Removed as of Aug 2016, replaced by + Media.Audio.Render.GetSourceDataTime.WebRTC. + + henrika@chromium.org + + Measures the time spent in WebRtcAudioRenderer::SourceCallback. Sampled 10 + times per second. + + + + + + Removed 11/2018 due to little use and high implementation complexity. + + saza@chromium.org + + The amount of time between sending the first and the last audio RTP packets + through the audiostreams of a Call object. This is logged when the Call + object is destroyed. This is only logged if audio RTP packets are at some + point in time received, and is a way to omit temporary objects that do not + send any actual media. + + + + + + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. + + hbos@chromium.org + hta@chromium.org + + Setting up a call involves a number of steps; this enum describes which + "answerer step" the peer connection reached in its most successful + attempt. See blink::AnswererState for more information. + + + + + + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. + + hbos@chromium.org + hta@chromium.org + + Setting up a call involves a number of steps; this enum describes the status + of the most successful attempt. See blink::CallSetupState for more + information. + + + + + + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. + + hbos@chromium.org + hta@chromium.org + + Setting up a call involves a number of steps; this enum describes which + "answerer step" the peer connection reached in its most successful + attempt. See blink::OffererState for more information. - + - Removed April, 2018 as the information has never shown any problems. + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. - asvitkine@chromium.org - bcwhite@chromium.org + hbos@chromium.org + hta@chromium.org - Records attempts to create histograms in presistent space and any errors - encountered when doing so. + Setting up a call involves a number of steps; this enum describes which + "answerer step" the peer connection reached in its most successful + attempt. See blink::AnswererState for more information. This is the same as + "WebRTC.PeerConnection.CallSetupState.AnswererState" except it is + only reported for peer connections on pages where getUserMedia() has been + called. - + - No longer useful or monitored, removed 2020-01-06. + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. - wnwen@chromium.org - src/base/metrics/OWNERS + hbos@chromium.org + hta@chromium.org - Measures how much time it took to complete all async deferred startup tasks - on the background thread. Only logged on Android. + Setting up a call involves a number of steps; this enum describes the status + of the most successful attempt. See blink::CallSetupState for more + information. This is the same as + "WebRTC.PeerConnection.CallSetupState.CallSetupState" except it is + only reported for peer connections on pages where getUserMedia() has been + called. - + - No longer useful or monitored, removed 2020-01-06. + These metrics were useful when Unified Plan was made the default SDP + semantics. They will again become useful when Plan B is becoming deprecated. + Until then, these are of little value and are temporarily disabled. - wnwen@chromium.org - src/base/metrics/OWNERS + hbos@chromium.org + hta@chromium.org - Measures how much time since application was first in foreground till all - deferred tasks are done. Only logged on Android. + Setting up a call involves a number of steps; this enum describes which + "answerer step" the peer connection reached in its most successful + attempt. See blink::OffererState for more information. This is the same as + "WebRTC.PeerConnection.CallSetupState.OffererState" except it is + only reported for peer connections on pages where getUserMedia() has been + called. - + - No longer useful or monitored, removed 2020-01-06. + Removed on Dec 2016. This histogram is used to gauge the risk of making the + change for issue 6030. The decision has been made and this is not needed any + more. - wnwen@chromium.org - asvitkine@chromium.org - src/base/metrics/OWNERS + zhihuang@chromium.org - Measures how much time it took to complete deferred startup tasks on the UI - thread. Only logged on Android. + Whether the application specified a value for RTCP-mux policy, and if so, + which value, "Require" or "Negotiate". Recorded after + parsing the configuration when creating the RTCPeerConnection. - + - Removed 01/2017 for - UMA.Debug.EnableCrashUpload.DeferredStartupAsyncTaskDuration. + Replaced by WebRTC.UserMediaRequest.Result2 in Feb 2018. - wnwen@chromium.org - asvitkine@chromium.org + andresp@chromium.org - Measures how much time it took to complete async deferred startup tasks on - the background thread. Only logged on Android. + Counters for UserMediaRequests results such as failure reasons. - + - No longer useful or monitored, removed 2020-01-06. + Removed 08/27/2020. - wnwen@chromium.org - src/base/metrics/OWNERS + sprang@chromium.org - Measures the maximum amount of time a single deferred startup task took. + Fraction of time the call was classified as bad because of any reason. - + - Replaced by UMA.Debug.EnableCrashUpload.DeferredStartUptime2 + Removed 08/27/2020. - asvitkine@chromium.org + sprang@chromium.org - Measures how much time since start up it took for onDeferredStartup() to be - called, which schedules enablePotentialCrashUploading() to be executed on an - async task. Only logged on Android. + Fraction of time the call was classified as bad because of low framerate. - + - Removed 2017. No longer tracked. + Removed 08/27/2020. - wnwen@chromium.org - asvitkine@chromium.org + sprang@chromium.org - Measures how much time since application was first in foreground till - deferred tasks are initialized and queued on the idle handler. Only logged - on Android. + Fraction of time the call was classified as bad because of high framerate + variance. - + - Replaced by UMA.Debug.EnableCrashUpload.PostDeferredStartUptime2 + Removed 08/27/2020. - asvitkine@chromium.org + sprang@chromium.org - Measures how much time since start up it took before ChromeActivity's - postDeferredStartupIfNeeded() was called. Only logged on Android. + Fraction of time the call was classified as bad because of high qp. - + - Removed 2017. No longer tracked. + Removed 03/28/2019. - wnwen@chromium.org - asvitkine@chromium.org + asapersson@chromium.org - Measures how much time since application was first in foreground till - ChromeActivity's postDeferredStartupIfNeeded() was called exactly once. Only - logged on Android. + The number of complete frames received per second for a received video + stream. Recorded when a stream is removed. The total number of frames is + divided by the time the video stream exists. - + - Replaced by UMA.Debug.EnableCrashUpload.Uptime2 + Removed 03/28/2019. - asvitkine@chromium.org + asapersson@chromium.org - Measures how much time since start up it took before crash reporting was - enabled via enablePotentialCrashUploading() as part of deferred start up. - Only logged on Android. + Percentage of discarded packets by the jitter buffer due to arriving too + late for a received video stream. Recorded when a stream is removed. - + - Replaced by UMA.Debug.EnableCrashUpload.Uptime3 + Removed 03/28/2019. - asvitkine@chromium.org + asapersson@chromium.org - Measures how much time since start up it took before crash reporting was - enabled via enablePotentialCrashUploading() as part of deferred start up. - Only logged on Android. + Percentage of duplicated packets in the jitter buffer for a received video + stream. Recorded when a stream is removed. - + - Removed 2017. No longer tracked. + Removed as of r253828 (27 Feb 2014). - wnwen@chromium.org - asvitkine@chromium.org + tommi@chromium.org - Measures how much time since application was first in foreground till crash - reporting was enabled as part of deferred start up. Only logged on Android. + Counts number of calls to WebRTC APIs from JavaScript, once per origin per + renderer process. - + - Replaced by UMA.Truncate* metrics. + Removed March 2020. - asvitkine@chromium.org - rkaplow@chromium.org + ericwilligers@chromium.org + hartmanng@chromium.org + hzjian@chromium.org + yfriedman@chromium.org - The number of events that would be discarded at log transmission time - because the event count was already too large. Note that this doesn't - measure actual discards - in case the UMAThrottleEvents feature is disabled, - the discards won't occur. + File types included in navigator.share() requests, where file content and + source URLs were not verified with Safe Browsing. - + - Removed 11/2016 for UMA.FieldTrialAllocator.Used + Removed October 2016 in favor of Security.PageInfo.Action.HttpsUrl.Valid, + Security.PageInfo.Action.HttpsUrl.Dangerous, and + Security.PageInfo.Action.HttpsUrl.Downgraded. - lawrencewu@chromium.org - bcwhite@chromium.org - asvitkine@chromium.org + estark@chromium.org - Size, before padding, of objects allocated from persistent memory in the - browser process for field trials. Updated on each subprocess launch. + Tracks WebsiteSettings actions that take place on an HTTPS URL. This + completely disregards security status. - + - Removed 2012. No longer tracked. + Removed 12/2014 in Issue 433776, and replaced by + WebsiteSettings.OriginInfo.PermissionChanged. - asvitkine@chromium.org + sashab@chromium.org - Log whether the --enable-benchmarking flag was set, which causes field - trials to only use the default group. + Count of how often a specific content type (permission) is changed using the + Page Info UI. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. - + - Removed April, 2018 as the information it provides is no longer useful. + Removed 12/2018. We're no longer monitoring WebSQL performance. - asvitkine@chromium.org - bcwhite@chromium.org + cmumford@chromium.org - The number of old metrics files for which a delete was attempted. This is - logged once with each upload operation. Values greater than 1 indicate that - the files are not deletable by the browser and must be cleaned up by - whatever process is creating them. + The time required to try (and fail) to open a Web SQL database. - + - Removed April, 2018 as no problems were ever indicated. + Removed 12/2018. We're no longer monitoring WebSQL performance. - asvitkine@chromium.org - bcwhite@chromium.org + cmumford@chromium.org + The time required to successfully open a Web SQL database. + + + + + There is no remaining code that is emmiting this metric. It was removed at + an unknown time. + + joshwoodward@google.com - The number of metrics files in a directory that need to be uploaded. This is - logged once with each upload operation. + Webstore Widget app: the reason why the suggest apps dialog was closed. - + - Removed 07/2017. Was only for short-term analysis. About 95% of dropped - files were less than 1 day old. + There is no remaining code that is emmiting this metric. It was removed at + an unknown time. - asvitkine@chromium.org - bcwhite@chromium.org + joshwoodward@google.com - Records the last-modified age of a file that was dropped for lack of an - embedded profile. + Webstore Widget app: whether the Webstore item user selected was + successfully installed or not. - + - Removed 2019/04 with the resolution of https://crbug.com/695880 + There is no remaining code that is emmiting this metric. It was removed at + an unknown time. - asvitkine@chromium.org - bcwhite@chromium.org + joshwoodward@google.com - Records the number of histograms present in a file that was dropped for lack - of an embedded profile. + Webstore Widget app: whether the initialization of the dialog succeeded or + not. - + - Removed 2019/04 as times are small, consistent, and now on a background - thread. + There is no remaining code that is emmiting this metric. It was removed at + an unknown time. - bcwhite@chromium.org + joshwoodward@google.com - Tracks the time used to record all histograms from a file with an embedded - profile. + Webstore Widget app: time to load the widget contained in the app. Measured + between the moment window appears and the moment all the contents in the app + including the Chrome Webstore widget are ready. - + - Removed 2019/04 with the resolution of https://crbug.com/695880 + Removed 2019-12 after expiration, while adding the similar + XHR.Sync.BlockingTime.MainThread and XHR.Sync.BlockingTime.WorkerThread. - asvitkine@chromium.org - bcwhite@chromium.org + qinmin@chromium.org + cduvall@chromium.org - Records attempts to upload metrics from files with embedded system profiles. - Counts are not necessarily mutually exclusive. + Records the total duration the renderer spent on each sync XHR resource + request, including requests that time out. - + - This metrics was to provide information for crbug/760317 which has been - resolved. Removed February, 2018. + Obsolete in M72 as initialization of WebUsbDetector no longer blocks the + main thread. - bcwhite@chromium.org + reillyg@chromium.org + juncai@chromium.org - Records various happenings within the FileMetricsProvider for debugging - purposes. + Records the time spent initializing the WebUSB detector module. - + - Access times are consistently on the order of a few ms. Removed 2019/06. + Obsolete 04/04/2018 as it has been replaced by + Android.WebView.LoadDataWithBaseUrl.HistoryUrl. - asvitkine@chromium.org - bcwhite@chromium.org + jamwalla@chromium.org - Records how much wall time was spent checking and mapping an initial metrics - file on disk. + Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/ + null, the same as the baseUrl parameter, or different from baseUrl. - + - Removed April, 2018 as the information it provides is no longer useful. + Removed 4/2013. No longer tracked. - asvitkine@chromium.org - bcwhite@chromium.org + kuscher@chromium.org - Records how much wall time was spent checking and mapping initial metrics - from all files on disk. + The number of panel windows open when a load completes. Panels are windows + docked to the bottom of the OS desktop, which are visible to the user even + while the user is interacting with other applications. - + - Access times are consistently on the order of a few ms. Removed 2019/06. + Removed 01/2020 as it was causing dead lock issues. crbug.com/1043353. - asvitkine@chromium.org - bcwhite@chromium.org + stanisc@chromium.org - Records how much wall time was spent collecting initial stability metrics - from a file on disk. + Time spent inside CreateThread() Windows API call creating a single thread. - + - Removed April, 2018 as the information it provides is no longer useful. + Removed 03/2020 after insight about OpenXPS has lead to more general + question of XPS availability (either type). - asvitkine@chromium.org - bcwhite@chromium.org + awscreen@chromium.org + thestig@chromium.org - Records how much wall time was spent collecting initial stability metrics - from all files on disk. + If the version of Xpsprint.dll is sufficiently modern to support OpenXPS. + Reported once per browser session, on startup. - + - Access times are consistently on the order of a few ms. Removed 2019/06. + Removed 06/2019 - asvitkine@chromium.org - bcwhite@chromium.org + wfh@chromium.org + brucedawson@chromium.org - Records how much wall time was spent collecting metrics from a file on disk. + A boolean used to indicate when the Windows version reported by + GetVersionEx() and the Windows version reported by VerQueryValue() on + kernel32 do not match. This is queried shortly after startup. - + - Removed April, 2018 as the information it provides is no longer useful. + Removed 04/2020. Necessary data was collected and a decision was made. See + https://crbug.com/920704 for details. - asvitkine@chromium.org - bcwhite@chromium.org + brucedawson@chromium.org + jmadill@chromium.org - Records how much wall time was spent collecting metrics from all files on - disk. + The ucrtbase.dll version, converted to a base::win::Version enum. This is + queried shortly after startup. - + - Removed as of August 2015. No longer tracked. + Removed 10/2016 as this is enabled by default so provides no useful data. - asvitkine@chromium.org + wfh@chromium.org - For each attempt to generate the low entropy source, log whether or not the - load required generating a new low entropy source. + Count of browser launches where Win32k renderer lockdown is enabled. - + - Removed as of October 2017. No longer tracked. + Obsolete 07/06/2017 as we are no long recording this metric. - asvitkine@chromium.org - bcwhite@chromium.org + chengx@chromium.org - Type and flags of every histogram created plus other activities. Counts are - not mutually-exclusive except for the different types. + The number of jumplist icons requested to create per jumplist update. It is + recorded whenever UpdateJumpList() is called. - + - Removed on 2020-03-18. Renamed to - UMA.JavaCachingRecorder.DroppedHistogramSampleCount and reports also - histogram samples dropped due to a limit of the number of cached histograms. + Obsolete 07/06/2017 as we are no long recording this metric. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - Number of histogram samples that were not recorded when flushing due to a - per-histogram sample count limit in the Java in-memory cache. + Time spent in CreateIconFiles(). This method is called whenever there is a + jumplist update and the JumpListIcons folder is empty. - + - Removed on 2020-03-18 to reduce the number of histograms emitted by the - cache. + Obsolete 07/06/2016 as we are no long recording this metric. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org + Time spent in DeleteDirectoryContentAndLogRuntime(). + + + + + Obsolete 04/25/2017 as we are no long recording this metric. + + chengx@chromium.org + Time spent in DeleteDirectoryAndLogResults(). + + + + + Obsolete 04/25/2017 as we are no long recording this metric. + + chengx@chromium.org - Number of histograms for which not all samples may have been recorded when - flushing the Java in-memory cache due to a per-histogram sample count limit. + This metric records the detailed delete result of JumpListIcons directory. - + - Removed on 2020-03-18 to reduce the number of histograms emitted by the - cache. UMA.JavaCachingRecorder.DroppedHistogramSampleCount includes - histogram samples that were reported in this histogram. + Obsolete 04/25/2017 as we are no long recording this metric. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - Number of samples that were not recorded when flushing the Java in-memory - cache due to a histogram count limit. + This metric records the detailed delete result of JumpListIconsOld + directory. - + - Removed on 2020-03-18. Renamed to - UMA.JavaCachingRecorder.InputHistogramSampleCount. + Obsolete 12/13/2016 as we are no long recording this metric. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - Number of histogram samples seen by the time the Java in-memory cache was - flushed. This is a sum of DroppedSampleCount and FlushedHistogramCount. + This metric is recorded when folder JumpListIcons is moved (can be rename or + copy and delete) to JumpListIconsOld. This happens when tabs are closed, + mostly visited URLs get updated, etc. There are several key steps in this + folder move operation. Before the move operation, there is another step that + JumpListIconsOld folder is deleted. The status of these steps are put + together and recorded in this metric. The failure of any of these steps is + suspected to be related to a known issue. - + - Removed on 2020-03-18 to reduce the number of histograms emitted by the - cache. + Obsolete 03/10/2017 as it is replaced by DetailedFolderResultsDeleteUpdated. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - The remaining histogram count limit when flushing in the Java in-memory - cache. + This metric is recorded when folders JumpListIcons and JumpListIconsOld get + updated. These two folders are updated when tabs are closed, mostly visited + URLs get updated, etc. These two folders are updated as follows 1) + JumpListIconsOld with its content get deleted; 2) if step 1 succeeds, + JumpListIcons is moved, 3) if any of the previous steps fails, JumpListIcons + is deleted, 4) A new JumpListIcons folder is created. The status of these 4 + file operations are put together and recorded in this metric. The failure of + any of these file operations is suspected to be related to a known issue. - + - Removed on 2020-03-18 to reduce the number of histograms emitted by the - cache. + Obsolete 03/20/2017. New metrics named WinJumplist.DeleteStatusJumpListIcons + and WinJumplist.DeleteStatusJumpListIconsOld are used instead. - bttk@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - The smallest remaining sample count limit in metrics flushed from the Java - in-memory cache. + This metric is recorded when folders JumpListIcons and JumpListIconsOld get + updated. These two folders are updated when tabs are closed, mostly visited + URLs get updated, etc. These two folders are updated as follows 1) + JumpListIconsOld with its content get deleted; 2) if step 1 succeeds, + JumpListIcons is renamed to JumpListIconsOld, 3) if any of the previous + steps fails, JumpListIcons is deleted, 4) A new JumpListIcons folder is + created if deletion of JumpListIcons' content succeeds (only fail to delete + the directory is okay). The status of these 4 file operations are put + together and recorded in this metric. The failure of any of these file + operations is suspected to be related to a known issue. - + - Removed 2020-04 + Obsolete 04/25/2017 as we are no long recording this metric. - asvitkine@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - Number of bytes in an excessively large log that was discarded at shutdown - instead of being saved to disk to retry during next chrome run. + This metric records whether the folder JumpListIcons exists; and if it does, + whether it is empty or non-empty. - + - Removed 2020-04 + Obsolete 04/25/2017 as we are no long recording this metric. - asvitkine@chromium.org - src/base/metrics/OWNERS + chengx@chromium.org - Number of bytes in a log was was rejected by server, and then discarded. + This metric records whether the folder JumpListIconsOld exists; and if it + does, whether it is empty or non-empty. - + - Removed as of August 2015. The histograms showed no unexpected slowness, and - a profiler is a better tool for identifying any future issues. + Obsolete 12/08/2016. DetailedFolderMoveResults is used for more detailed + analysis. - asvitkine@chromium.org + chengx@chromium.org - The time spent to load (de-serialize) unsent logs from local state, recorded - during the MetricsService startup sequence. + This metric is recorded when folder JumpListIcons is moved (can be rename or + copy and delete) to JumpListIconsOld. This happens when tabs are closed, + mostly visited URLs get updated, etc. There are 3 possible steps in this + folder move operation. Before the move operation, there is another step that + JumpListIconsOld folder is deleted. The status of these steps are put + together and recorded in this metric. The failure of any of these steps is + suspected to be related to a known issue listed below. + https://bugs.chromium.org/p/chromium/issues/detail?id=179576 - + - No longer tracked. + Obsolete 12/13/2016, as we are now recording DetailedFolderResults. - asvitkine@chromium.org + chengx@chromium.org - Simple counter of the number of times LogLoadComplete was called (bug - demonstration, as we're called more often than once per page load :-/ ) + This metric is recorded when folders JumpListIcons and JumpListIconsOld get + updated. These two folders are updated when tabs are closed, mostly visited + URLs get updated, etc. These two folders are updated as follows 1) + JumpListIconsOld with its content get deleted; 2) JumpListIcons is moved, 3) + A new JumpListIcons folder is created. The status of these three file + operations are put together and recorded in this metric. The failure of any + of these file operations is suspected to be related to a known issue. - + - Used for analyzing UMA log uploads on cellular connection, but necessary - after the analysis is finished. + Obsolete 07/10/2017 as it's no longer needed. - asvitkine@chromium.org - gayane@chromium.org + chengx@chromium.org - The network connection type for each successful metrics log upload. + The time interval between two adjacent update notifications if it's less + than 3500 ms. - + - Removed in favor of UMA.LogSize.OnSuccess + Obsolete 07/23/2017 as it's no longer needed. - asvitkine@chromium.org - holte@chromium.org + chengx@chromium.org - Reports total upload length in bytes when the UMA service type is used. + The time interval between two adjacent update notifications. A zero value + indicates the interval is greater than 3500 ms. - + - This metrics was to provide information for crbug/760317 which has been - resolved. Removed February, 2018. + Obsolete 06/22/2017 as it's no longer needed. - bcwhite@chromium.org + chengx@chromium.org + Time spent in OnFaviconDataAvailable(). + + + + + Obsolete 07/23/2017 as it's no longer needed. + + chengx@chromium.org - Records the size of the metrics directory size, after failing to be deleted. - This is a temporary metric that will be removed in M63 or M64. + The ratio of the duration spent adding the most-visited category compared to + the duration spent adding the recently-closed category, multiplied by 10. - + - This metrics was to provide information for crbug/760317 which has been - resolved. Removed February, 2018. + Obsolete 06/22/2017 as it's no longer needed. - bcwhite@chromium.org + chengx@chromium.org + Time spent in StartLoadingFavicon(). + + + + + Obsolete 04/20/2017 as it's no longer accurate due to the code change. + + chengx@chromium.org - Records the size of the metrics directory size, after being successfully - deleted. This should always be zero unless there is a bug in the return - code. This is a temporary metric that will be removed in M63 or M64. + Time spent in UpdateJumpList(). This method is called whenever there is a + jumplist update. - + - Removed February, 2018 because persistent metrics are fully launched with no - observable change in operation time. + Obsolete 07/26/2017 as it's no longer needed. - asvitkine@chromium.org - bcwhite@chromium.org + chengx@chromium.org + Time spent in JumpListUpdater::AddCustomCategory. + + + + + Obsolete 07/10/2017 as it's no longer needed. + + chengx@chromium.org + Time spent in JumpListUpdater::AddTasks. + + + + + Obsolete 07/26/2017 as it's no longer needed. + + chengx@chromium.org + Time spent in JumpListUpdater::BeginUpdate. + + + + + Obsolete 07/26/2017 as it's no longer needed. + + chengx@chromium.org + Time spent in JumpListUpdater::CommitUpdate. + + + + + Removed 01/2017. + + Please list the metric's owners. Add more owner tags as needed. - Records how much wall time was spent merging, taking snapshots, and - recording histograms for reporting to UMA. + Incremented each time the TimeTicks field trial runs on a machine with + multiple cores, but failed to change thread affinity. Broken down by Windows + version. - + - Removed 01/2019 in b/110205489 being split into ChromeOS.CWP.CollectPerf and - ChromeOS.CWP.UploadPerf. + Removed 01/2017. - asvitkine@chromium.org + Please list the metric's owners. Add more owner tags as needed. - A count of successes and various failure modes related to collecting and - processing performance data obtained through "perf" on Chrome OS. + The smallest non-zero delta reported by subsequent calls to + QueryPerformanceCounter. - + - Removed 2/2017 for Issue 689315 which indicated they weren't being used. + Removed 01/2017. - bcwhite@chromium.org - asvitkine@chromium.org + Please list the metric's owners. Add more owner tags as needed. - Size, before padding, of objects allocated from persistent memory. This is - updated with every allocation. + True if the CPU's timestamp counter ticks at a constant rate regardless of + CPU frequency. - + - Data showed many files being deleted during rollout and then tapering off to - near zero. Removed 2019/07. + Removed 01/2017. - bcwhite@chromium.org - asvitkine@chromium.org + Please list the metric's owners. Add more owner tags as needed. - Number of old .tmp files of the kind that Windows creates and leaves around - when trying to rename a file to another one that already exists. See - https://crbug.com/934164 + The number of times the TimeTicks field trial failed because + QueryPerformanceCounter ticked backwards. Broken down by Windows version. - + - Removed as of Jun 2016. The histogram was added for debugging purpose and is - not needed anymore. + Removed 01/2017. - asvitkine@chromium.org - yiyaoliu@chromium.org + Please list the metric's owners. Add more owner tags as needed. - Record the number of loaded profiles when a profile is erased from the - profiles map kept by profile manager. + The number of times the TimeTicks field trial succeeded. Broken down by + Windows version. - + - Removed as of Sep, 2013. Gzipping protobufs is now the default. + Removed 01/2017. - asvitkine@chromium.org - Was the UMA protobuf uploaded earlier compressed or not. + Please list the metric's owners. Add more owner tags as needed. + + The number of times the TimeTicks field trial ran for comparison with + WinTimeTicks.VersionSuccess. Broken down by Windows version. + - + - Removed as of August 2015. See UMA.ProtoCompressionRatio instead. + Removed Jan 2020. - asvitkine@chromium.org + hiroshige@chromium.org + nhiroki@chromium.org - Kilobytes saved from gzipping the protobufs before uploading them. + Type of worker top-level script's request URL's origin, relative to parent + execution context's origin, recorded on each successful classic dedicated + worker creation. - + - Removed as of August 2015. The histograms showed no unexpected slowness, and - a profiler is a better tool for identifying any future issues. + Removed July 2019. - asvitkine@chromium.org + kinuko@chromium.org - The time spent to store unsent logs to local state, which is done - periodically and also during start up if there was an initial stability log. + Worker thread load, i.e. percentage of time spent on running tasks. This + metric is emitted at most once per kWorkerThreadLoadTrackerReportingInterval + sec per worker thread amortized. E.g. if a worker ran a single task for X + seconds and then went to idle for Y seconds before it shuts down, and + assuming the interval rate was 1 sec, we get X samples for 100% and Y + samples for 0%. - + - Removed 2020/04 + Removed on 2018-02. - asvitkine@chromium.org - bcwhite@chromium.org - src/base/metrics/OWNERS + nhiroki@chromium.org + The time taken for running a debugger task on WorkerThread. + + + + + Removed July 2019. + + kinuko@chromium.org - The number of subprocesses from which persistent metrics were collected, - logged once with every reporting cycle. + The amount of time a worker thread ran for. Starts recording when a worker + scheduler for the thread is created, and stops when the scheduler is shut + down. - + - Removed 2019/06 after not reporting anything in years. + Removed on 2018-02. The sample count was overflowing. crbug.com/809672. - asvitkine@chromium.org - bcwhite@chromium.org + nhiroki@chromium.org + The time taken for running a worker task on WorkerThread. + + + + + Removed on 2020-04. Bucket sizes are not very useful for measuring jank. The + only user of AnimationFrameTimeHistogram. + + kkimlabs@chromium.org - The number of subprocesses, by type, from which persistent metrics are NOT - collected because there is no information about this (likely new) process - type. Process numbers 1000 or greater are "custom" processes used - by embedders. + Frame times of the Android wrench menu opening animation. For example, if + the menu opening animation runs exactly at 60fps for a second, then each + frame time is 16ms, and a total of 60 values of 16ms are recorded. If the + animation is janky, we will see values greater than 16ms in the histogram. - + - Removed as of August 2015. + Removed 03/2020 - asvitkine@chromium.org + alcooper@chromium.org + xr-dev@chromium.org - The number of synthetic field trials added to the UMA log when the system - profile is recorded. Since this is done prior to capturing the histograms - from the current process, this will generally be logged once per UMA log. + Indicates which VR APIs are installed. Recorded shortly after startup. - + - Removed as of May, 2012 (i.e. Chrome 21+). Replaced by the - UMA.UploadResponseStatus.XML and UMA.UploadResponseStatus.Protobuf - histograms. + Removed 02/2020 - asvitkine@chromium.org - The server returned a 400 code, and we discarded a log. -
- This tends to indicate that a syntax error is present in a log, such as - would appear when a bogus XML tag is included, or the XML is not balanced - and well structured. -
+ alcooper@chromium.org + xr-dev@chromium.org + + The action that triggered the transition into Chrome in VR, either from 2D + or another VR app. + - + - Removed as of August 2015. This failure case no longer exists. + Removed as of 06/2020. - asvitkine@chromium.org + alcooper@chromium.org + mlamouri@chromium.org + xr-dev@chromium.org - For each attempted UMA upload, log whether the upload was successfully - constructed. An upload might fail to be constructed, for example, if we try - to upload before the system is fully initialized; or if serialization of the - data fails. + Records the actions of a user consent dialog which is displayed on + requesting an XR session. - + - Replaced by UMA.LogUpload.ResponseOrErrorCode + Removed as of 06/2020. - asvitkine@chromium.org + alcooper@chromium.org + mlamouri@chromium.org + xr-dev@chromium.org - For each upload to the protocol buffer (v2) UMA server, log whether the - upload was successful, or whether there was an error. + Time the user takes to abort the consent flow by clicking on the + window-close system button of a session request consent dialog. - + - Removed 2013. No longer tracked. + Removed as of 06/2020. - asvitkine@chromium.org + alcooper@chromium.org + mlamouri@chromium.org + xr-dev@chromium.org - For each upload to the XML (v1) UMA server, log whether the upload was - successful, or whether there was an error. + Time the user takes to click on the allow-and-enter-VR button on a session + request consent dialog. - + - No longer tracked. + Removed as of 06/2020. - asvitkine@chromium.org + alcooper@chromium.org + mlamouri@chromium.org + xr-dev@chromium.org - Log whether the --reset-variation-state flag was set before the low entropy - source was requested. + Time the user takes to click on dont-allow button on a session request + consent dialog. - + - Removed 2013. No longer tracked. + Removed 02/2020 - asvitkine@chromium.org + alcooper@chromium.org + xr-dev@chromium.org - The time spent in converting the XML tree into a character buffer when - closing a metrics log (Chrome OS). + The action that triggered VR presentation, which is the display of web + content on a VR device. - + - Removed 2013. No longer tracked. + Removed July 2019. This was being tracked in case the assumptions about + feature availability based on platform version turned out to be incorrect, + but it appears that this is working as intended. The webxr-render-path flag + that could be used to override this at runtime was previously removed in + https://crrev.com/c/1487074. - asvitkine@chromium.org + klausw@chromium.org - The time spent in freeing the XML writer and tree when closing a metrics log - (Chrome OS). + Records the WebXR/WebVR render path used for presentation on presentation + start. The render path is affected by overrides and device capabilities. diff --git a/tools/metrics/histograms/histograms_xml/offline/histograms.xml b/tools/metrics/histograms/histograms_xml/offline/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..64f7385d9dbb5028823fbc17bf377fd61ab51bca --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/offline/histograms.xml @@ -0,0 +1,1070 @@ + + + + + + + + + + sinansahin@google.com + twellington@chromium.org + + For OfflineIndicatorV2, records whether the native browser controls can be + animated and whether the omnibox is focused. Recorded when the device goes + offline. + + + + + sinansahin@google.com + twellington@chromium.org + + For OfflineIndicatorV2, records whether the native browser controls can be + animated and whether the omnibox is focused. Recorded when the device goes + online. + + + + + dimich@chromium.org + jianli@chromium.org + + Records events related to click through rate (CTR) calculation for Offline + Indicator UI. The CTR can be calculated by computing Clicked/Displayed. + + + + + sinansahin@google.com + twellington@chromium.org + + The duration the offline indicator was shown. Recorded when the offline + indicator hides. + + + + + jianli@chromium.org + + Number of accesses to the offline page since its creation. This is reported + when the offline page was deleted. + + + + + jianli@chromium.org + offline-dev@chromium.org + + Logs the UI location from which an offline page was launched. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Counts the number of times an offline page is accessed. Events are reported + per offline pages namespace. + + + + + dimich@chromium.org + jianli@chromium.org + offline-dev@chromium.org + Result of servicing requests that may contain offline page. + + + + dimich@chromium.org + offline-dev@chromium.org + + This is recorded every time the archive directory is being created. It + doesn't include the case which the archive directory exists. It has suffixes + indicating results for temporary or persistent archives directories. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + This is recorded every time the auto-fetch complete notification is shown or + interacted with. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + This is recorded every time the auto-fetch in-progress notification is shown + or interacted with. + + + + + petewil@chromium.org + offline-dev@chromium.org + + Effective connection type at the start of an offlining attempt for an + attempt that eventually failed. + + This metric is recorded for RequestCoordinator::SavePageLater API calls. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Effective connection type when pausing one or more background loads is + requested. + + This metric is recorded for RequestCoordinator::PauseRequests API calls. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Effective connection type when removing one or more background loads is + requested. + + This metric is recorded for RequestCoordinator::RemoveRequests API calls. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Effective connection type when resuming one or more background loads is + requested. + + This metric is recorded for RequestCoordinator::ResumeRequests API calls. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Effective connection type when a background load is requested. + + This metric is recorded for RequestCoordinator::SavePageLater API calls. + + + + + chili@chromium.org + offline-dev@chromium.org + + Status code of background offlining requests at the final step. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests available for processing when + processing starts immediately (vs. scheduled). This is for non-svelte + devices (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests available for processing when + processing starts immediately (vs. scheduled). This is for svelte devices + (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests unavailable for processing when + processing starts immediately (vs. scheduled). This is for non-svelte + devices (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests unavailable for processing when + processing starts immediately (vs. scheduled). This is for svelte devices + (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Status of attempt to immediately start offlining a page in the background + while application is still concurrently using the foreground. This may be + attempted when an web page download is initially requested or resumed. + + + + + chili@chromium.org + offline-dev@chromium.org + + The combined http and net error codes that caused a page load failure. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Status code of background offlining (loading and saving) requests. + + + + + petewil@chromium.org + offline-dev@chromium.org + + Whether any previews were selected for a page we were asked to make + available offline. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of started attempts by failed background load requests. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of started attempts by successful background load requests. + + + + + chili@chromium.org + offline-dev@chromium.org + Whether the save page result came from chrome custom tabs. + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests available for processing when + background scheduled processing starts. This is for non-svelte devices + (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests available for processing when + background scheduled processing starts. This is for svelte devices (where + svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests unavailable for processing when + background scheduled processing starts. This is for non-svelte devices + (where svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Number of queued background load requests unavailable for processing when + background scheduled processing starts. This is for svelte devices (where + svelte is determined by base::SysInfo::IsLowEnd()). + + + + + dougarnett@chromium.org + offline-dev@chromium.org + Time from background request until it was canceled. + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Time from background request until it was successfully saved. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Time from background request until processing it was first started. This is + for non-svelte devices. + + + + + dougarnett@chromium.org + offline-dev@chromium.org + + Time from background request until processing it was first started on svelte + device. Svelte is determined by base::SysInfo::IsLowEnd(). + + + + + harringtond@chromium.org + offline-dev@chromium.org + Number of thumbnails removed by the thumbnail cleanup task. + + + + carlosk@chromium.org + offline-dev@chromium.org + + The total disk storage size used by all offline pages from a specific client + namespace. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of pages deleted in a batch in one clear storage task. + + + + + romax@chromium.org + offline-dev@chromium.org + + Result of clearing temporary pages to release storage space. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + When a temporary page is deleted due to storage pressure, reports the time + since its creation. This metric should be useful to track the occurrence of + "content thrashing", when automatically created temporary pages + are forcing the deletion of recently saved temporary pages. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of files which are deleted during legacy dir clearing since they have + no associated DB entry and live in private directory. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of DB entries (in persistent namespaces) that have been missing their + files for longer than 365 days, and deleted during maintenance task. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of files that are found missing during maintenance task, which is + also the number of DB entries that are updated with valid file missing time. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of files that were marked as missing reappeared in the file system, + which is also the number of DB entries that removes file missing time. + + + + + dimich@chromium.org + offline-dev@chromium.org + Result of persistent page consistency check. + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of temporary offline pages without archive file when checking + consistency. It will only be reported if the number is larger than 0. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Number of archives without database entry when checking temporary page + consistency. It will only be reported if the number is larger than 0. + + + + + dimich@chromium.org + offline-dev@chromium.org + Result of temporary page consistency check. + + + + dimich@chromium.org + offline-dev@chromium.org + + Counts the number of times an offline page is deleted. Events are reported + per offline pages namespace. + + + + + jianli@chromium.org + offline-dev@chromium.org + Result of removing an offline copy for a page. + + + + dewittj@chromium.org + fgorski@chromium.org + offline-dev@chromium.org + + If at request time there is another request with the same URL, this tracks + this amount of time between creation of the most recent request and the + current request. + + + + + dewittj@chromium.org + fgorski@chromium.org + offline-dev@chromium.org + + If at request time there is another downloaded page with the same URL, this + tracks this amount of time between creation of the most recent existing page + and the current request. + + + + + harringtond@chromium.org + offline-dev@chromium.org + + Whether or not a thumbnail was provided for a prefetched offline article. + Recorded when the item is shown in Downloads Home. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Upon starting saving a new last_n offline page snapshot, report if that is + being done for a page that is new (a navigation happened) or for one that + has been previously saved in the same session (no navigation happened). This + metric will assist in determining if there is the need to better track + actual content changes in pages saved more than once by last_n. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Result of an attempt to load an MHTML archive to display a trusted offline + page, recorded per offline namespace by OfflinePageTabHelper after renderer + attempts to load the archive. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Result of an attempt to load an MHTML archive to display an untrusted + offline page, recorded by OfflinePageTabHelper after the renderer attempts + to load the archive. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Counts user-days when Chrome was used in specific ways regarding navigation + to online and offline content. Buckets are mutually exclusive so that only + one bucket is incremented per reported day. This metric is not recorded to + UMA immediately due to potential data loss while offline. So day counters + are persisted to prefs and reported to the histogram only when the next UMA + data upload is likely to succeed. For more details see: + https://goo.gl/GJXwFe. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Counts user-days when Chrome was used in specific ways regarding navigation + to online and offline content. Buckets are mutually exclusive so that only + one bucket is incremented per reported day. + + This metric is a mirror of OfflinePages.OfflineUsage but it doesn't use any + of the offline resilient mechanisms that one has. Ideally both should report + exactly the same values but it is expected this one will lose more samples. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Length of time between accesses to an offline page. This is the same time + period used for expiring temporary pages. This metric is recorded when an + offline page is accessed. + + + + + jianli@chromium.org + offline-dev@chromium.org + + Length of time between when an offline page was created and was removed. + + + + + jianli@chromium.org + offline-dev@chromium.org + Size of the saved copy of an offline page. + + + + carlosk@chromium.org + offline-dev@chromium.org + + Records the archive size of an offline page loaded during a navigation that + took place while the device was considered to be offline or with poor + connectivity. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Records the archive size of an offline page loaded during a navigation that + took place while the device was considered to be online. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Counts user-days when candidate articles were suggested to the Offline + Prefetch pipeline while it was enabled. This metric is not recorded to UMA + immediately due to potential data loss while offline. So day counters are + persisted to prefs and reported to the histogram only when the next UMA data + upload is likely to succeed. For more details see: https://goo.gl/GJXwFe. + + + + + dewittj@chromium.org + offline-dev@chromium.org + + Number of attempts to perform a specific retriable pipeline action for each + finished prefetch item. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Actual size of archive file successfully downloaded by offline page + prefetching. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Expected download size of archive file, after gzip content encoding, that + started being downloaded by offline page prefetching. Sizes reported in this + metric are less than the sizes reported in DownloadedFileSize due to content + gzip encoding. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Reports the possible outcomes of an archive download finishing and its + respective prefetch item being updated in the store. Downloads are expected + to succeed or fail but a respective item should always exist and be updated. + The "item not found" cases are exceptions. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Error code representing the reason why each offline prefetch item was + finalized. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + The lifetime of an offline prefetch item, from creation until + "zombie-fication" (after metrics collection). + + + + + dewittj@chromium.org + offline-dev@chromium.org + + Actions taken with respect to the offline prefetch notification, includes + show attempts to calculate CTR. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Final result of an attempt to import a prefetched article into the Offline + Pages system. + + + + + petewil@chromium.org + offline-dev@chromium.org + + Status returned by a request to the Offline Page Service's GetOperation + method. + + + + + petewil@chromium.org + offline-dev@chromium.org + + Status returned by a request to the Offline Page Service's GetPageBundle + method. + + + + + petewil@chromium.org + offline-dev@chromium.org + + A prefetch item was seen in this state when starting the background task. + + + + + petewil@chromium.org + offline-dev@chromium.org + + A prefetch item was found in this state after more than 7 days since its + creation, time enough for it to have been finalized by the pipeline. + + + + + dewittj@chromium.org + offline-dev@chromium.org + + When receiving suggestions in the prefetch pipeline, emits the number of new + suggestions added to the database. If there is an error, nothing is emitted. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Counts when the offline pages prefetch store is opened or closed. + + + + + dimich@chromium.org + offline-dev@chromium.org + + Counts user-days categorized by how Offline Prefetch performed and had its + content accessed by the user. Buckets are mutually exclusive so that only + one bucket is incremented per reported day. This metric is not recorded to + UMA immediately due to potential data loss while offline. So day counters + are persisted to prefs and reported to the histogram only when the next UMA + data upload is likely to succeed. For more details see: + https://goo.gl/GJXwFe. + + + + + petewil@chromium.org + + When publishing an offline page, a page might not be found. This returns the + publishing path that was used (ex: by Guid or by OfflineId). + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Total number of saved offline pages recorded when they are all queried from + the store. This value is more meaningful when filtered by unique users as + that eliminates multiple reports from the same Chrome instance. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to successfully create the store metadata entry for an offline + page archive during the process of saving an offline page. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to successfully compute the digest of an offline page archive + during the process of saving an offline page. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to successfully create an offline page archive during the process + of saving an offline page. + + + + + twellington@chromium.org + ianwen@chromium.org + + The percentage of the page load completed when the button to save an offline + page is pressed. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to successfully move an offline page archive to the public + downloads folder during the process of saving an offline page. + + + + + jianli@chromium.org + offline-dev@chromium.org + Result of saving an offline copy for a page. + + + + jianli@chromium.org + offline-dev@chromium.org + + The amount of time taken to save an offline copy for a page. + + + + + dewittj@chromium.org + offline-dev@chromium.org + Whether a shared page was an offline page or not. + + + + dimich@chromium.org + offline-dev@chromium.org + + Result of publishing internal page while sharing. CANCELLED means the page + to publish isn't found. ALREADY_EXISTS means the page have already been + published before. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Used as a counter to track different events related to offline page store + inner working. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The storage space used by the archive files of offline pages, including all + files in public directory with mhtml/mht extensions. Collected after every + time an offline page is saved successfully. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The amount of free space on the external drive (which contains the public + download directory). Collected after every time an offline page is saved + successfully. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The percentage of storage space on the external volume (that contains public + download directory) used by offline pages archives. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The storage space used by the archive files of offline pages, including the + files in temporary and private directory. Collected after every time an + offline page is saved successfully. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The amount of free space on the internal drive (which contains the app + directory). Collected after every time an offline page is saved + successfully. + + + + + dimich@chromium.org + offline-dev@chromium.org + + The percentage of storage space on internal volume (that contains the app + directory) used by offline pages archives. + + + + + carlosk@chromium.org + offline-dev@chromium.org + + Tracks the reload of contents of an existing tab that is being restored + either because that tab is being presented for the first time after Chrome + was restarted or because its contents were discarded. All buckets are + mutually exclusive (adding up all reported values amounts to the total + number of tracked tab restores). This metric is focused on last_n offline + pages and is exclusive to Chrome on Android. + + + + + jianli@chromium.org + + The trust state of the offline page. This is recorded when an offline page + is being opened. + + + + + fgorski@chromium.org + + Indicates whether Open online was visible in Page Info popup, when it was + shown for an offline page. (The button is visible only when Chrome is + connected when the Page Info popup is opened for offline page.) + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/omnibox/histograms.xml b/tools/metrics/histograms/histograms_xml/omnibox/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..66623060713f518dc9fcd91b1ffc29b5452fe1cc --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/omnibox/histograms.xml @@ -0,0 +1,1058 @@ + + + + + + + + + + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + For each answer received in suggest responses, the number that are + well-formed and contain all the required elements. + + + + + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + The number of times each omnibox suggestion answer type (e.g., weather, + sports score) was received and parsed successfully. Can be normalized with + the count of emits to Omnibox.SuggestRequest.Success.GoogleResponseTime, + which counts all successful suggest responses from Google, not just those + with answers attached. Note that GoogleResponseTime is technically off given + that it will still count cases where we fail to extract, deserialize, or + parse the response. But these cases are rare to non-existent. + + + + + + + manukh@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + The time elapsed between the ChromeOmniboxClient requesting a suggestion's + image to receiving the image. This includes both uncached and cached + requests. See BitmapFetcher.Fetch and BitmapFetcher.Decode for what + contributes to uncached images latency; however, the sum of those metrics + can be greater than this metric as image prefetching begins before the + ChromeOmniboxClient requests an image. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + asvitkine@chromium.org + + Records the time taken between a keystroke being typed in the omnibox and + the text being painted. If there are multiple keystrokes before a paint, + logs the time since the earliest one. + + This duration is composed of three parts: + + a) the time spent processing the initial input event + + b) the time spent for the repaint task to be scheduled on the message loop + + c) the time spent painting the Omnibox + + d) (on views platforms) the time until the pixels are actually composited + + There's a number of breakdown metrics to help diagnose a regression. First, + Omnibox.CharTypedToRepaintLatency.ToPaint measures the combined time of (a) + and (b). Omnibox.QueryTime2 is a good proxy for just (a). And there's also + Omnibox.PaintTime that corresponds to (c). We don't have a direct metric for + (d), but if neither Omnibox.CharTypedToRepaintLatency.ToPaint nor + Omnibox.PaintTime regressed, then the regression must be in (d). + + Note: The semantics of this metric on views platforms changed in M62, as + previously time (d) was not included in the metric. + + + + + asvitkine@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + A refinement of Omnibox.CharTypedToRepaintLatency metric. It measures the + time between the first character insertion in a series that happen during a + frame, to the time the compositor reports the text was rendered on-screen. + Compositor-provided timestamps are used for this version of the metric, so + it is expected to be more accurate: the baseline CharTypedToRepaintLatency + uses now() from when the subsequent has-processed notification arrives back + on the UI thread, which may overestimate user-visible latency. + + + + + asvitkine@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records the time between when OnPaint() is called to the time the compositor + reports pixels were successfully drawn to the screen. This a subset of the + time reported in Omnibox.CharTypedToRepaintLatency.InsertToPresent. + + + + + asvitkine@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records the time taken between a keystroke being typed in the omnibox and + the time when we're ready to paint the omnibox. This is a breakdown + diagnostic metric for Omnibox.CharTypedToRepaintLatency, to help diagnose + regressions in that metric. See that metric's description for more info. + + + + + gangwu@chromium.org + fgorski@chromium.org + + Recorded every time the clipboard suggestion is removed from omnibox + suggestion list and the system clipboard. The value indicates the estimated + age of the clipboard. + + + + + gangwu@chromium.org + jdonnelly@chromium.org + + Recorded every time the omnibox is focussed and recent content from the + user's clipboard is suggested. The value indicates the estimated age of the + clipboard. (If Chrome observed the clipboard modification, this age is + exact. If Chrome did not observe the modification, then it's a conservative + estimate: the last time Chrome observed a clipboard modification, which is + certainly older than the current clipboard. If Chrome never observed a + clipboard modification, no clipboard suggestion is shown, meaning this + histogram will never be emitted to.) + + Intended to be compared with MobileOmnibox.PressedClipboardSuggestionAge. + + + + + gangwu@chromium.org + jdonnelly@chromium.org + + Recorded every time the omnibox is focussed and a recent content from the + user's clipboard is suggested. The number emitted is the number of times the + clipboard content has been suggested within the same session including the + current time. Thus, the third time it is shown, we'll emit a three to this + histogram, and this histogram will have previously seen emits of one and + two. If the clipboard content was the same during a previous run of Chrome + and this clipboard content was suggested during that run, those impressions + are not counted. Also, if the clipboard content changes during a particular + run of Chrome to other content, the omnibox is focused and that clipboard + content is suggested, then content changes back and Chrome starts suggesting + the older clipboard content again, the counts start again from scratch. + Chrome only remembers the number of times the clipboard content was shown + consecutively. + + This value is useful to compare with the number of times a clipboard + suggestion has been shown when it is clicked. This value can be obtained + from OmniboxEvent records in which the selected suggestion is from Clipboard + provider. In those cases, look in the Clipboard provider's ProviderInfo + field for |times_returned_results_in_session|. Note that at the time of this + writing that OmniboxEvent logs aren't recorded in incognito whereas + histograms are. Thus, the total counts will not be comparable, though the + distributions should be. + + + + + gangwu@chromium.org + jdonnelly@chromium.org + + Recorded every time the omnibox is focussed and a recent content from the + user's clipboard is suggested. The value indicates whether the current URL + was shown (which would appear above the clipboard suggestion) or was absent + (which ought to only happen when the omnibox is empty / the user is on the + NTP). + + On Android, the total count for this histogram can be usefully compared with + the count of the user action FocusLocation in order to determine the rate at + which a clipboard suggestion is shown in the omnibox. To determine the same + rate on iOS, one needs to compare this histogram's count with the sum of the + user actions MobileFocusedOmniboxOnNtp, MobileFocusedFakeboxOnNtp, and + MobileFocusedOmniboxNotOnNtp. + + Furthermore, on either platform, this histogram's count can be usefully + compared with the count in the clipboard bucket of the + Omnibox.SuggestionUsed.Provider histogram to determine the clickthrough rate + on these suggestions. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The number of cut or copy commands on all selected text in the omnibox. + Gathered on desktop platforms (Win, Mac, Linux, Chrome OS). + + + + + mpearson@chromium.org + jdonnelly@chromium.org + skare@chromium.org + + Counts the number of document suggest requests the omnibox sent, were + invalidated, and were completed successfully. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + skare@chromium.org + + Number of results returned in each document suggestion reply. Logged for + successful requests where the provider returned a parseable result set. + + + + + livvielin@chromium.org + tommycli@chromium.org + + The state of URL elision in the omnibox, e.g. URL default behavior, + prevented by context menu option, or prevented by Chrome extension. This + histogram is recorded the first time ShouldPreventElision is called on + ChromeLocationBarModelDelegate with an existing profile. This occurs every + time a browser window is open, including when opening a new profile or + moving a tab to a new window. This metric measures the percentage of browser + windows that use each type of elision behavior. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The new enumeration of how many times users enter keyword hint mode + "Search ___ for:" and how. Note that we don't recognize the + changing of the keyword itself as entering keyword mode, if the user never + left keyword mode e.g. if the user was arrowing around the suggestions, so + we'll preserve the original keyword mode entry method in this case. + + + + + ender@chromium.org + jdonnelly@chromium.org + mpearson@chromium.org + tommycli@chromium.org + + This records whether user initiated navigation after focusing the Omnibox + versus switches focus elsewhere without navigating. This metric includes + accidental focus-then-losing-focus events, including brief ones. It also + includes ones in which the user did not type any text or otherwise engage + with the Omnibox. E.g., the user tabbing through all top Chrome UI controls + will cause this metric to be recorded. If the user switches focus from the + Chrome window to another window while the Omnibox is focussed, that also + counts as a loss of focus. + + This metric is not recorded for the Realbox interactions. + + Recorded every time the Omnibox focus is cleared. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The length of time between when a user focused on the omnibox and first + modifies the omnibox. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The length of time between when a user focused on the omnibox and opened an + omnibox match (which could be what they typed or a suggestion). This is + recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. + It is not recorded if a match is opened without triggering a focus event, + e.g., when a user drags a URL to the omnibox to navigate. + + To know how common this last condition is, compare the total count of this + histogram to the total number of omnibox events. + + + + + estark@chromium.org + carlosil@chromium.org + + The time duration that the user hovers the mouse over the omnibox before + exiting the hover or focusing the omnibox. Whenever the user's mouse enters + the omnibox, this histogram is recorded when the mouse next exits or the + omnibox is focused, whichever comes first. The recorded value is a delta + from a timestamp noted when the user's mouse first entered the omnibox. + + + + + ender@chromium.org + jdonnelly@chromium.org + mpearson@chromium.org + chrome-android-omnibox-team@google.com + + Records suggestions decorated with specific icon or favicon at the time the + user exited the omnibox. Exiting the omnibox includes navigating (to entered + text or any suggestion), pressing the system back key, clearing omnibox, + blanking screen / locking the phone (whether intentionally or due to + inactivity), or closing the Chrome app. This metric is logged every time the + omnibox is exited, including when no answer is present in the list of + suggestions. + + This histogram is related to Omnibox.SuggestionUsed.IconOrFaviconType. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The kind of input the user provided when using the omnibox to go somewhere. + The type can be misleading. For example if the user typed 'http:/', it gets + marked as a query because it cannot be opened as a URL even though the user + probably wanted and selected a URL from the list of suggestions. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Whether an omnibox interaction is a paste-and-search/paste-and-go action. + (This histogram records both of these in the "True" bucket for + this histogram because both of these are referred to as paste-and-go in the + code.) These typically involve right-clicking in the omnibox and selecting + that option from the dropdown. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + Whether the omnibox popup (a.k.a. dropdown) is open at the time the user + used the omnibox to go somewhere. It can be closed if, for instance, the + user clicked in the omnibox and hit return to reload the same page. Also, + because paste-and-search/paste-and-go actions ignore the current content of + the omnibox dropdown (if it is open) when they happen, we pretend the + dropdown is closed when logging these. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Whether the user deleted text immediately before selecting an omnibox + suggestion. This is usually the result of pressing backspace or delete. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + mahmadi@chromium.org + tommycli@chromium.org + + The length of time it takes for the corresponding URLs that would produce a + deleted match to be queried asynchronously and deleted. Triggered when user + deletes a local history zero-prefix suggestion. + + + + + mahmadi@chromium.org + tommycli@chromium.org + + The number of search terms extracted from the keyword search terms database + and examined (e.g., sorted) to produce local zero-prefix suggestions. + Triggered when zero-prefix suggestions are enabled and requested as a result + of user focus into the Omnibox or the Realbox on the NTP. + + + + + mahmadi@chromium.org + tommycli@chromium.org + + The length of time it takes to extract search terms from the keyword search + terms database and examine (e.g., sort) them to produce local zero-prefix + suggestions. + + + + + mahmadi@chromium.org + tommycli@chromium.org + + The length of time it takes to handle the deletion request for a match and + to update the list of provider matches synchronously. Triggered when user + requests to delete a local history zero-prefix suggestion. + + + + + tommycli@chromium.org + jdonnelly@chromium.org + + This tracks how unstable our matches are due to asynchronous updates. + Whenever a dropdown position gets asynchronously set to a new match that's + different from the old match, this histogram logs the index. + + We primarily care the default match, which is logged at index 0. All indices + matter though, so we track the other indices too. When the number of matches + changes asynchronously, matches that are removed are considered a + "change" and logged here. Matches that are appended are less + disruptive to the user, and are not logged. + + This is because this metric is primarily interested in how many times the + user could be looking at a match with the intention of selecting it, and + then it surprisingly goes away. + + Note that merely adding a new asynchronous provider will increase these + counts. That's intentional. Swapping matches out annoys users, and to avoid + this, we should do some things like: caching, update coaslescing, update + deferral until next keystroke, provider timeouts, etc. + + This metric is designed to be normalized by the True count of + Omnibox.Start.WantAsyncMatches, which will yield the number of match changes + asynchronously per keystroke or other user gesture. + + + + + tommycli@chromium.org + jdonnelly@chromium.org + + This tracks how unstable our matches are due to asynchronous updates. + + For each asynchronous autocomplete update, this histogram logs whether any + match in any position has changed. Note: if the only change is new matches + appended to the end of the list, that does not count as a change, since it's + not very disruptive to the user. + + This metric is designed to be normalized by the True count of + Omnibox.Start.WantAsyncMatches, which will yield the number of times any + match changes asynchronously per keystroke or other user gesture. + + This histogram can be considered a boolean analogue to + Omnibox.MatchStability.AsyncMatchChange2. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The number of times users used the omnibox to go somewhere. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The number of terms in the text the user entered in the omnibox when they + used the omnibox to go somewhere. Terms are defined by splitting on + whitespace. All values larger than 6 are recorded in bucket 6. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + cch@chromium.org + suggest-2g@google.com + + Time it takes for omnibox on device head provider to fulfill the + asynchronous suggest request. + + + + + cch@chromium.org + suggest-2g@google.com + + The number of results returned by the on device head model which matches the + user input. Note all numbers greater than 5 are recorded in bucket 5. + + + + + asvitkine@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Records the time to paint the omnibox contents. This is a subcomponent of + Omnibox.CharTypedToRepaintLatency. Implemented on desktop platforms. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The number of paste commands on the text in the omnibox. Reported every time + a paste command is done. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + + The number of paste-and-go commands on the text in the omnibox. Reported + every time a paste-and-go command is done. + + + + + jdonnelly@chromium.org + orinj@chromium.org + chrome-omnibox-team@google.com + + Counts the type (concept ID) of omnibox pedals shown when the user used the + omnibox to go somewhere. + + Pedals are a button attached to a search suggestion that either navigate to + a chrome:// URL or trigger a Chrome action (for example, opening the page + translation dialog or opening a new window in Incognito mode). + + Note that, while it is uncommon, it is possible for multiple pedals to be + shown at one time so this can't be used as a count of how many times a pedal + or pedals were present. + + This histogram is related to Omnibox.SuggestionUsed.Pedal. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The length of time taken by the named provider"s synchronous pass. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Time it takes for the omnibox to become responsive to user input after the + user has typed N characters. This measures the time it takes to start all + autocomplete providers (but not wait for the asynchronous ones to finish). + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records the number of searches done from omnibox using + default search engine on desktop and android devices, sliced based on being + in regular mode or private modes. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The type of search engine associated with a match opened from the omnibox. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The number of matches returned by SearchProvider. Emitted on every call to + SearchProvider::Start(), which effectively means every key stroke in the + omnibox. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + The index of the item that the user selected in the omnibox popup (a.k.a. + dropdown) list. 0 means the inline suggestion shown within the omnibox. This + is also the same suggestion shown as the top item in the dropdown. The + second item in the dropdown will be recorded as bucket 1. The selected + position is always set to 0 when the popup is closed at the time of + navigation or if the user did a paste-and-search or paste-and-go action. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + livvielin@chromium.org + tommycli@chromium.org + + Tracks whether the context menu option to prevent URL elisions in the + omnibox is enabled. Recorded when the pref is toggled. + + + + + tommycli@chromium.org + jdonnelly@chromium.org + + Whether asynchronous matches are requested. Recorded every time + AutocompleteController::Start() is called. + + False counts roughly correspond to non-interactive invocations of + AutocompleteController - like when we are classifying user text as a Search + or URL. + + True counts roughly correspond to keystrokes or on-focus events, and can be + used as a normalizer for per-user-gesture metrics. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Counts how often omnibox suggestions are used, and in the case an Answer + suggestion was selected - records the type of an answer. This histogram is + useful because there is no distinct suggestion type recorded for answers so + their use is not recorded by Omnibox.SuggestionUsed.ProviderAndResultType. + + + + + gangwu@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Measures whether the suggestion that was selected by the user offered a tab + match. A tab match occurs when the URL specified by the suggestion matches + the URL navigated to by another tab in the browser, within the margin of our + URL stripping scheme. + + This metric typically only makes sense with respect to + Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser + send the metric. Therefore, other metrics may include datapoints not covered + by this metric (unless one narrows the data by version.) + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + jdonnelly@chromium.org + orinj@chromium.org + chrome-omnibox-team@google.com + + Counts how often omnibox pedals are used and records the type (concept ID) + of the pedal used. + + Pedals are a button attached to a search suggestion that either navigate to + a chrome:// URL or trigger a Chrome action (for example, opening the page + translation dialog or opening a new window in Incognito mode). + + This histogram is related to Omnibox.PedalShown. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Measures the time from navigation start to first meaningful paint. Only + recorded for a search query suggestion selected from the omnibox. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Measures the time from navigation start to first contentful paint. Only + recorded for a search query suggestion selected from the omnibox. + + + + + gangwu@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Measures whether the suggestion that was selected by the user offered a tab + match and specifically that the user chose the tab match over normal + navigation. A tab match occurs when the URL specified by the suggestion + matches the URL navigated to by another tab in the browser, within the + margin of our URL stripping scheme. By selecting the tab match, the browser + simply switches focus to the matching tab. + + This metric typically only makes sense with respect to + Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser + send the metric. Therefore, other metrics may include datapoints not covered + by this metric (unless one narrows the data by version.) + + This metric should be stricly less than + Omnibox.SuggestionUsed.OfferedTabMatch, and is typically used to discover + the percentage of offered tab matches that the user accepts. + + In M-74 and earlier, this was only recorded if the user had no incognito + windows open. In M-75 and later, it records all omnibox interactions + regardless, in order to be consistent with how user actions and histograms + are handled. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Measures the time from navigation start to first meaningful paint. Only + recorded for a URL suggestion selected from the omnibox. + + + + + jdonnelly@chromium.org + mpearson@chromium.org + chrome-omnibox-team@google.com + + Measures the time from navigation start to first contentful paint. Only + recorded for a URL suggestion selected from the omnibox. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + cch@chromium.org + + The time elapsed between the sending of a suggest request to Google until + the time the request was returned with status==failed. Ignores requests that + were canceled before being returned. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + cch@chromium.org + + The time elapsed between the sending of a suggest request to Google until + the time the request was returned with status==success. Ignores requests + that were canceled before being returned. + + + + + manukh@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + The number of images prefetched by the search provider on retrieving a + successful search response. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + cch@chromium.org + + Counts about the number of suggest requests the omnibox sent, invalidated, + and replies received. + + + + + mahmadi@google.com + chrome-omnibox-team@google.com + + Counts the number of times a suggestion group ID is prevented form appearing + in the results. This is recorded when the user hides a set of grouped + suggestions, such as proactive zero-suggest, in the omnibox UI using the + control in the grouped suggestions' header. + + + + + mahmadi@google.com + chrome-omnibox-team@google.com + + Counts the number of times a suggestion group ID is permitted to appear in + the results. This is recorded when the user makes a set of previously hidden + grouped suggestions, such as proactive zero-suggest, visible in the omnibox + UI using the control in the grouped suggestions' header. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + chrome-omnibox-team@google.com + + The scheme of the destination URL for the selected omnibox suggestion. This + could be a what-you-typed suggestion (if the user fully typed a URL), an + inline autocompletion, or something in the dropdown, anything as long as + it's a URL navigation, not a search query. Excludes omnibox URL navigations + that are effectively reloads as well as cut-and-pastes of URLs. Also does + not take into account any redirects that destination URL may do before + finally serving a page. In other words, it's the scheme of the first request + in a possible chain. + + + + + kenjibaheux@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Counts the number of times that the user text is cleared. IME users are + sometimes in the situation that IME was unintentionally turned on and failed + to input latin alphabets (ASCII characters) or the opposite case. In that + case, users may delete all the text and the user text gets cleared. This + histogram helps us estimate how often this scenario happens. + + Note that since we don't currently correlate "text cleared" events + with IME usage, this also captures many other cases where users clear the + text; though it explicitly doesn't log deleting all the permanent text as + the first action of an editing sequence (see comments in + OnAfterPossibleChange()). + + + + + etienneb@chromium.org + mpearson@chromium.org + jdonnelly@chromium.org + + Time it takes for the omnibox to process the first user interaction after + startup. This measures the time it takes to start all autocomplete providers + and their initialisation steps. This metric may be recorded twice as there + is the normal omnibox path and also the "classify text" path to + the autocomplete system. + + + + + mpearson@chromium.org + jdonnelly@chromium.org + + Whether the user has settings configured so that the current page URL can be + sent to the suggest server to request contextual suggestions. For example, + this is only supported for users who have Google as their default search + engine (unmodified version of Google), have search suggest enabled, are + signed-in and syncing without a custom passphrase, and don't have an + incognito window open. There are other criteria too. Recorded on focus in + the omnibox if there is default search provider and we've constructed a + suggest URL. + + Some additional guidelines: if an incognito window is open, all focus events + will go into the "generally ineligible" bucket. Likewise, if the + current page is a search results page, we don't allow contextual suggestions + either so focus events on those pages go in the "generally + ineligible" bucket. The difference between "eligible" and + "generally eligible but not this time" depends only the properties + of the current URL. + + Recorded regardless of whether contextual or non-contextual zero suggest is + currently enabled on the user's platform. However, if zero suggest (in all + forms) is entirely disabled, the user will be perpetually ineligible. + + This histogram captures all scenarios that are generally ineligible for zero + suggest suggestions (including incognito mode), and reports eligibility for + suggestions even if kOmniboxPopupShortcutIconsInZeroState is enabled + (meaning: suggestions are not shown, but current URL is eligible). + + + + + mpearson@chromium.org + jdonnelly@chromium.org + + Whether the user has settings configured so that the current page URL could + be sent to the suggest server to request contextual suggestions. For + example, this is only supported for users who have Google as their default + search engine (unmodified version of Google), have search suggest enabled, + and are signed-in and syncing without a custom passphrase. There are other + criteria too. Recorded on profile open. Note that opening an incognito + window (if none are currently open under the given profile) counts as + opening a new profile. + + Some additional guidelines: unlike Omnibox.ZeroSuggest.Eligible.OnFocus, + because this is recorded on profile open, users cannot be declared + ineligible because they have an incognito window open (it's impossible to + have an incognito window open for a given profile at the time of profile + open) and also cannot be declared ineligible because the user is viewing a + search results page. (We test this on-profile-open using an arbitrary URL.) + + Recorded regardless of whether contextual or non-contextual zero suggest is + currently enabled on the user's platform. However, if zero suggest (in all + forms) is entirely disabled, the user will be perpetually ineligible. + + + + + ender@chromium.org + tommycli@chromium.org + chrome-omnibox-team@google.com + + Counts about the number of zero suggest requests (requests for suggestions + when the user has focused but not modified the omnibox) the omnibox sent, + invalidated, and replies received. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/oobe/histograms.xml b/tools/metrics/histograms/histograms_xml/oobe/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..715d4967fd95606d9beeb1466b6c6b64e1cff62f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/oobe/histograms.xml @@ -0,0 +1,379 @@ + + + + + + + + + + raleksandrov@google.com + cros-oac@google.com + + Whether the review Google Play following setup box is checked. Recorded when + user leaves ArcTermsOfService screeen. + + + + + alemate@chromium.org + rsorokin@chromium.org + cros-oac@google.com + Time from the login screen start to user session start. + + + + raleksandrov@google.com + cros-oac@google.com + + Time spent on error screens during enrollment or autoenrollment. + + + + + raleksandrov@google.com + cros-oac@google.com + Time spent on error screens during signin. + + + + raleksandrov@google.com + cros-oac@google.com + + Time spent on error screens during supervised user creation. + + + + + raleksandrov@google.com + cros-oac@google.com + Time spent on error screens during update. + + + + raleksandrov@google.com + cros-oac@google.com + + Tracks all user actions on the EULA screen. Recorded when user clicks on + buttons on the EULA screen. + + + + + + + rsorokin@chromium.org + alemate@chromium.org + cros-oac@google.com + + Time from acceptance of the EULA until the login screen is first displayed. + + + + + raleksandrov@google.com + cros-oac@google.com + + Tracks all user actions on the fingerprint screen. Recorded when user clicks + on buttons on the fingerprint screen. + + + + + + + mmourgos@chromium.org + tbarzic@chormium.org + + Records the amount of time that each page within the gesture navigation OOBE + screen is shown. Recorded when the gesture navigation oobe screen is + exiting. + + + + + rrsilva@google.com + cros-oac@google.com + + The result of a request performed by the MarketingBackendConnector used in + the OOBE MarketingOptInScreen when subscribing the user to Chromebook + emails. This data is used to determine the success rate of the requests + being performed. + + + + + rrsilva@google.com + cros-oac@google.com + + Records the choice a user takes when prompted with a toggle on the OOBE + MarketingOptInScreen to subscribe to Chromebook emails. + + + + + rrsilva@google.com + cros-oac@google.com + + Records whether the user's geolocation was resolved successfully. + + + + + rrsilva@google.com + cros-oac@google.com + + Records the length of the country code that was returned when determining + the user's geolocation. + + + + + achuith@google.com + + Number of times error screen has appeared during enrollment or + autoenrollment. + + + + + achuith@google.com + Number of times error screen has appeared during signin. + + + + achuith@google.com + Number of times error screen has appeared during update. + + + + raleksandrov@google.com + cros-oac@google.com + play-bm-eng@google.com + The number of recommended apps. + + + + rsorokin@chromium.org + cros-oac@google.com + play-bm-eng@google.com + The time it takes to fetch the recommended apps. + + + + rsorokin@chromium.org + cros-oac@google.com + chromesky-eng@google.com + The response code of fetching the recommended apps. + + + + rsorokin@chromium.org + cros-oac@google.com + chromesky-eng@google.com + The result of parsing the recommend-apps response. + + + + rsorokin@chromium.org + cros-oac@google.com + chromesky-eng@google.com + The user action on the recommend apps screen. + + + + rsorokin@chromium.org + cros-oac@google.com + chromesky-eng@google.com + The number of apps user selected. + + + + raleksandrov@google.com + cros-oac@google.com + chromesky-eng@google.com + The ratio of selected and recommended apps. + + + + rsorokin@chromium.org + cros-oac@google.com + chromesky-eng@google.com + Whether the reocmmend apps screen is shown. + + + + + + alemate@chromium.org + antrim@chromium.org + rsorokin@chromium.org + cros-oac@google.com + Time spent on specific OOBE screen. + + + + raleksandrov@google.com + cros-oac@google.com + Time spent on specific OOBE screen grouped by exit reason. + + + + jamescook@chromium.org + cros-oac@google.com + + Whether the sync consent screen was shown, skipped with sync disabled, or + skipped with sync enabled. Recorded when the screen is closed. Metrics + Sync.InitialState and OOBE.SyncConsentScreen.SyncEnabled provide more detail + on the state of the sync engine. + + + + + raleksandrov@google.com + cros-oac@google.com + + Whether the review following setup box is checked. Recorded when user leaves + SyncConsent screen. + + + + + jamescook@chromium.org + cros-oac@google.com + + Final state of the sync service at the end of the sync consent OOBE step. + The dialog may have been shown or skipped (e.g. by enterprise policy). See + OOBE.SyncConsentScreen.Behavior for skip reasons. + + + + + jamescook@chromium.org + cros-oac@google.com + + Which button the user clicked on the out-of-box sync consent screen. + Recorded when the user clicks the button, which also closes the screen. + + + + + dkuzmin@google.com + cros-oac@google.com + + Time spent on Checking of the ChromeOS update. Recorded when the stage is + done and the next stage is about to start. + + + + + dkuzmin@google.com + cros-oac@google.com + + Time spent on Downloading of the ChromeOS update. Recorded when the stage is + done and the next stage is about to start. + + + + + dkuzmin@google.com + cros-oac@google.com + + Time spent on Finalizing of the ChromeOS update. Recorded when the stage is + done and the next stage is about to start. + + + + + dkuzmin@google.com + cros-oac@google.com + + Time spent on Verifying of the ChromeOS update. Recorded when the stage is + done and the next stage is about to start. + + + + + raleksandrov@google.com + cros-oac@google.com + + Time spent on downloading ChromeOS update when critical updated is found + during OOBE. Recorded when update is uploaded and ChromeOS device is about + to restart to apply the update. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Measures time spent by switch between WebUI and Views-based display hosts. + + + + + dkuzmin@google.com + cros-oac@google.com + + Measures usage of the accessibility options on the welcome screen during + OOBE. Recorded when user enables or disables any of the accessibility + options from accessibility menu on the welcome screen. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/optimization/histograms.xml b/tools/metrics/histograms/histograms_xml/optimization/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5b55ca46ef582ad208bbbf0466d7185c14110435 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/optimization/histograms.xml @@ -0,0 +1,446 @@ + + + + + + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + The decision made for whether the optimization type can be applied on the + page load. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + Records the decision made for whether the optimization type can be applied + on a page load when all information for that page load has been sufficiently + gathered. This will be recorded once per callback registered, so if two + callbacks were registered for the same optimization type and page load, this + will be recorded twice for that case. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records whether the optimization guide store was available when fetched + hints are cleared from the store after browser history is cleared. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records whether the optimization guide store was available when host model + features are cleared from the store after browser history is cleared. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the store entry type of a hint when it is loaded from the hint cache + store. + + + + + dougarnett@chromium.org + sophiechang@chromium.org + + Records the result of loading the metadata while initializing the + HintCacheLevelDBStore. + + + + + dougarnett@chromium.org + sophiechang@chromium.org + + Records each status change within the HintCacheLevelDBStore. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + Records when an in-flight hints request was canceled before it finished. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + The duration of a request to fetch hints from the remote Optimization Guide + Service starts until it completes. Recorded every time hints are fetched and + parsed successfully. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the number of hints received from the remote Optimization Guide + Service for every successful HintsFetch request. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts selected for sending a hint request. This will + be captured when any hint request is initiated. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + Net error codes for HintsFetch requests to the Optimization Guide Service on + success and failure. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + For each HintsFetch request to the Optimization Guide Service, log the HTTP + response code on success and failure. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the number of URLs selected for sending a hint request. This will be + captured when any hint request is initiated. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + The status of making a Batch Update context request of the OptmizationGuide + HintsFetcher. This includes whether a network request was actually sent or + not. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + The status of making a Page Navigation context request of the + OptmizationGuide HintsFetcher. This includes whether a network request was + actually sent or not. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts placed on the HintsFetcherTopHostBlacklist when + it is initialized. + + + + + mcrouse@chromium.org + dougarnett@chromium.org + + Records the number of hosts on the HintsFetcherTopHostBlacklist when top + hosts are requested. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + The number of active hints fetches initiated by the hints manager. Recorded + when a fetch is initiated to the remote Optimization Guide Service at + navigation start. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Status of a fetch attempt being raced against the current navigation start + and whether it includes hosts and urls. Recorded on navigation start + (including client redirects) by the hints manager. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records whether the prediction model being constructed for an optimization + target is valid or not. Recorded when prediction models are loaded into + memory by the prediction manager. + + + + + dougarnett@chromium.org + sophiechang@chromium.org + + Status of processing OptimizationFilter configurations for server-provided + blacklists. Recorded when the OptimizationGuideService receives a + notification to process hints. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + Records the major version of the Optimization Hints component that was + pushed to the client. This will be recorded at startup and when a new + component is received. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Whether the PredictionManager had HostModelFeatures for the host of the + navigation. Recorded when ShouldTargetNavigation is called. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the number of host model features loaded into the map used by the + PredictionManager. This is recorded when the host model features are loaded + from the store. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + The duration of evaluating a prediction model for a registered optimization + target. Recorded every time a prediction model is successfuly evaluated by + the prediction manager. Not recorded if a cached decision is used or if the + evaluation fails. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the number of hosts included in a remote Optimization Guide Service + client model request. This will be captured when any GetModelsRequest is + initiated. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the number of host model features received from the remote + Optimization Guide Service for every successful GetModelsRequest. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Net error codes for GetModelsRequest to the Optimization Guide Service on + success and failure. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + For each GetModelsRequest to the Optimization Guide Service, log the HTTP + response code on success and failure. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the version of the prediction model that was loaded from the store + and used until updated by a fetch. Recorded only if the loaded model was + valid. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the result of loading the host model features metadata while + initializing the OptimizationGuideStore. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the version of the prediction model that was fetched as an update. + Recorded only if a model returned was valid and is available for use. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + Records the duration of construction and validation of a prediction model + when the prediction manager loads it into memory for a given optimization + target. Recorded only if the model is valid and successfully loaded into + memory for use. + + + + + dougarnett@chromium.org + sophiechang@chromium.org + + Whether processing the hints succeeded or failed at a particular step. + Recorded when the OptimizationGuideService receives a notification to + process hints. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + Whether the session is enabled for fetching information from the remote + Optimization Guide Service. Recorded when the profile is initialized for the + session if Optimization Hints are enabled and the profile is a non-incognito + profile. + + + + + mcrouse@chromium.org + sophiechang@chromium.org + + The status of the prediction model for an optimization target within the + prediction manager. Recorded when the manager is asked if a navigation + should be targeted and the decision for the navigation has not already been + made. + + + + + sophiechang@chromium.org + mcrouse@chromium.org + + The decision made for whether the page load matches the optimization target. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/others/histograms.xml b/tools/metrics/histograms/histograms_xml/others/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..a3a92cba0ab97283cb55ff422301b0b2cdfe078a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/others/histograms.xml @@ -0,0 +1,17017 @@ + + + + + + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Records the source of in-session account addition (or re-authentication) + triggers on Chrome OS. This is recorded whenever an in-session account + addition (or re-authentication) is triggered - either explicitely by the + user, or automatically by Gaia (for accounts requiring immediate + re-authentication). + + + + + sinhak@chromium.org + anastasiian@chromium.org + + The result of creating a Reauth Proof Token (RAPT) for the parent in + secondary EDU account addition flow. Recorded after parent enters their + password and child access token is fetched. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + The result of fetching an access token for the child with |accounts.reauth| + scope in secondary EDU account addition flow. Recorded after parent enters + their password. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + The result of fetching a list of parents in secondary EDU account addition + flow. Recorded when user opens 'Add EDU account' flow. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Records the last completed step in the EDU account addition flow. Allows to + track the drop rate by screen. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Measures the time taken to fully initialize Chrome OS Account Manager. This + is recorded once per user session, at login time. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Tracks the service type received with the mirror response header. + + + + + sinhak@chromium.org + + Tracks the final result of migrating accounts to Chrome OS Account Manager. + This is recorded only once per session, at login time. + + + + + + + sinhak@chromium.org + + Tracks the result of individual migration steps of migrating accounts to + Chrome OS Account Manager. This is recorded only once per session, at login + time. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Whether user has received a Mirror re-authentication request for account + with invalid cookies. Recorded when we open a re-authentication dialog for + the invalid account. See https://crbug.com/1012649 for details. + + + + + sinhak@chromium.org + + Tracks the number of accounts stored in Chrome OS Account Manager by a given + user. This is recorded only once per session, at login time. + + + + + sinhak@chromium.org + anastasiian@chromium.org + + Tracks the status of token loads from disk by Chrome OS Account Manager, for + a given user. This is recorded only once per session, at login time. + + + + + siggi@chromium.org + + The analyzer creation error code. Logged each time analyzer creation fails, + at most once per processed stability debug file. + + + + + siggi@chromium.org + + Status of the initialization to collect stability debug files. Logged once, + during the initialization of the stability debug file collection. + + + + + siggi@chromium.org + + Number of files found during stability file collection. Logged each time the + stability file collection proceeds (at most once per launch). + + + + + siggi@chromium.org + + Status for the collection of a stability debug file. Logged each time a + debug file collection attempt is made. + + + + + siggi@chromium.org + + Status for the analysis of the system session state. Logged each time a + debug file is collected. + + + + + siggi@chromium.org + + Time spent collecting stability debug information. Logged each time a + collection is performed. + + + + + siggi@chromium.org + + Status of the minidump writing. Logged each time a writing a minidump is + attempted. + + + + + siggi@chromium.org + + Events that occur during crash collection of the debug file. Logged each + time an event of interest occurs during crash debug file collection. + + + + + siggi@chromium.org + + Status for the collection of a stability debug file. Logged each time a + debug file collection attempt is made from the crash handler. + + + + + siggi@chromium.org + + Events pertaining to recording to the debug file. Logged each time an event + of interest occurs wrt debug file recording. + + + + + tobyhuang@chromium.org + michaelpg@chromium.org + danan@chromium.org + + Records the number of users who go through the Add Supervision process to + convert regular accounts to Geller accounts. Initiated count is incremented + when Add Supervision dialog is opened. Completed count is incremented when + supervision is successfully enrolled. Signed out count is incremented when + the user clicks "Sign out" after enrollment at the end of the + process in the dialog. Closed count is incremented when the Add Supervision + dialog is closed prior to enrollment, excluding sign out. Switched accounts + count is incremented when the user clicks "Sign out" within the + dialog to swich accounts before enrollment completion. + + + + + tobyhuang@chromium.org + michaelpg@chromium.org + danan@chromium.org + + Measures the amount of time in milliseconds for users to successfully enroll + in supervision. + + + + + tobyhuang@chromium.org + michaelpg@chromium.org + danan@chromium.org + + Measures the amount of time in milliseconds for users to exit the Add + Supervision dialog without enrollment. This can happen if the user closes + the Add Supervision dialog or signs out to switch accounts. + + + + + tobyhuang@chromium.org + michaelpg@chromium.org + danan@chromium.org + + Measures the amount of time in milliseconds for users to sign out after + enrolling in supervision. Elapsed time is measured starting from when the + Add Supervision dialog was first opened. + + + + + johnidel@chromium.org + dalecurtis@chromium.org + + Duration in milliseconds of HTML5 media (when known). Only recorded for + media within ad subframes. This is recorded every time the duration changes + for a video, and can be recorded multiple times for a single video (the + overall duration may not be known when loading starts). Because the duration + will generally increase as more video gets buffered, this histogram may skew + low. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Load type of HTML5 media in ad subframes such as URL, MediaSource and + MediaStream. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + For a given resource fetched from the disk cache or blink memory cache, logs + the encoded body length of the resource, even if the resource request was + canceled or incomplete. Recorded when the resource request is complete, or + when the page is destroyed/navigated for incomplete resources. The sum of + samples across a page load may differ substatially from the true sum due to + per-sample rounding. These are not intended to be compared to page level + histograms. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + For a given resource fetched from the network, logs the network bytes used + to load the resource (including headers), even if the resource request was + canceled or incomplete. Recorded when the resource request is complete, or + when the page is destroyed/navigated for incomplete resources. The sum of + samples across a page load may differ substatially from the true sum due to + per-sample rounding. These are not intended to be compared to page level + histograms. + + + + + tbansal@chromium.org + + True if the target link of the anchor element has the same host as the root + document. Recorded only on default search engine pages. + + + + + tbansal@chromium.org + ryansturm@chromium.org + src/chrome/browser/navigation_predictor/OWNERS + + True if the target link of the anchor element has the same host as the root + document. Recorded only on pages whose URL do not match the default search + engine. + + + + + chelu@chromium.org + tbansal@chromium.org + + True if the target link of the anchor element has the same host as the root + document. + + + + + chelu@chromium.org + tbansal@chromium.org + + The number of anchor element metrics sent to the browser process on a page + load. Anchor elements having the same href are merged and counted as 1. This + histogram is recorded when the webpage is loaded. + + + + + khushalsagar@chromium.org + + If the frame rate for the image animation can not be reached, frames in the + animation are skipped to catch up to the desired frame. This metric tracks + the number of frames skipped during catch up, and can be used to assess the + smoothness of these animations. It records the number of frames skipped each + time the animation is ticked forward to draw the next frame. In the ideal + case, where the animation can be drawn at the desired rate, 0 frames should + be skipped. Note that skipping of frames can also be triggered if the + animation was intentionally paused (on becoming off-screen, or the tab being + hidden). + + + + + majidvp@chromium.org + animations-dev@chromium.org + + The time it takes the WorkletMutatorDispatcher to complete an asynchronous + mutation request of animation worklet. The measured time is the total + elapsed time from when a request is queued until the results are received. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + majidvp@chromium.org + animations-dev@chromium.org + + The time it takes the WorkletMutatorDispatcher to dispatch to and mutate all + animation worklet mutators synchronously. This includes the time that it + takes each AnimationWorkletGlobalScope to produce its output (which includes + V8 script execution) and also any queuing cost associated with posting + mutation tasks and receiving responses. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + majidvp@chromium.org + kevers@chromium.org + animations-dev@chromium.org + + The time it takes for an AnimationWorklet to produce a mutation update. This + includes all V8 script execution cost. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + mkwst@chromium.org + brandm@microsoft.com + + Records if various requests to access storage are allowed or not and if the + Storage Access API unblocked the request or not. Recorded whenever a + decision to access storage like getting/setting cookies or opening an + indexeddb connection is made in CookieSettings. + + + + + mkwst@chromium.org + brandm@microsoft.com + + Records if a generated grant was implicit or explicit at the time it was + created. + + + + + mkwst@chromium.org + brandm@microsoft.com + + Records requests to use document.requestStorageAccess and reasons the + request may be approved or rejected. + + + + + dominickn@chromium.org + pjmclachlan@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks + usage of the BeforeInstallPromptEvent, which allows developers to control + when an app banner appears. The events in this histogram are not mutually + exclusive - for example, preventDefault() must be called if prompt() is + called. + + + + + pjmclachlan@google.com + pcovell@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks the + different ways that an app banner left the screen, e.g. through an automatic + dismissal after navigation or an explicit user action. + + + + + pjmclachlan@google.com + pcovell@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks + when an app banner was requested and how the request was handled, e.g. the + user blocked its appearance or the banner was ultimately created. + + + + + dominickn@chromium.org + pjmclachlan@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks the + status code logged by the app banner system as it processes a site's + eligibility for an app banner. Every request for a banner will be logged in + a bucket of this histogram. + + + + + pjmclachlan@google.com + pcovell@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks + when a user triggers an install dialog for the app promoted by the banner, + as well as whether or not the user ultimately decided to install the app. + + + + + dominickn@chromium.org + pjmclachlan@google.com + + App banners promote an application related to the current website, and are + requested specifically through the current page's HTML. This stat tracks the + number of minutes between the first recorded visit to an origin and the time + when the banner is actually shown. + + + + + dominickn@chromium.org + pjmclachlan@google.com + + This stat tracks the user reponse when the add-to-homescreen dialog is shown + either: (A) Via the website's JavaScript (B) Via the user tapping the app + banner which promotes the application related to the current site. + + + + + pwnall@chromium.org + mek@chromium.org + + The proportion of manifests that use the Chrome-specific header. Only tracks + manifests that were successfully parsed. + + + + + pwnall@chromium.org + mek@chromium.org + + The proportion of manifests parsed with dangerous features enabled. Only + tracks manifests that were successfully parsed. + + + + + pwnall@chromium.org + mek@chromium.org + + Usage of CHROMIUM-INTERCEPT entries in AppCache manifests. Only tracks + manifests that were successfully parsed. + + + + + mek@chromium.org + + Tracks the number of times the appcache reinit process occurs. The boolean + value indicates whether it was a repeated attempt to reinitialize during a + browsing session. + + + + + cmp@chromium.org + pwnall@chromium.org + Tracks whether the update job was canceled. + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times we encountered corruption and fixed it while + handling a 304 response. We only attempt to recover corruption during 304 + response handling, so for any corrupt caches that exist and don't trigger a + conditional request, these cases can't result in the possibility of fixing + corruption through this path. + + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times we plan to check whether we can reuse existing + resources. + + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times we encounter a corrupt resource while checking if + we can reuse an existing resource. This is only called when we find a + corrupt resource, so any resources that are corrupt but aren't tested won't + be included in this count. If all resources are non-corrupt, then the + default value (0) will be sent for metrics collection. + + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times we encountered a corrupt resource and chose to + recover the corruption by refetching the resource in a non-conditional + request. This metric is always emitted upon AppCacheUpdateJob destruction + and is only incremented when the corruption recovery feature is enabled and + a corrupt resource is detected. If either corruption recovery is disabled or + no corrupt resources are recovered, then this will not be emitted. + + This metric was enabled in M81 (Dec 19, 2019), disabled in M82 (Feb 18, + 2020), and re-enabled in M86 (Aug 2020). In M86 this includes 0 values (no + corruption recovered), but in M87 and later it does not. + + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times we encounter a non-corrupt resource while + checking if we can reuse an existing resource. This is only called when we + find a non-corrupt resource, so any resources that aren't corrupt but aren't + tested won't be included in this count. If all resources are corrupt, then + the default value (0) will be sent for metrics collection. + + + + + cmp@chromium.org + enne@chromium.org + + Tracks the number of times we encounter a corrupt resource while checking if + we can reuse an existing resource. This is only called when we find a + corrupt resource, so any resources that are corrupt but aren't tested won't + be included in this count. + + Unlike ExistingResourceCorrupt this is only emitted when there are any + corrupt resources found. + + + + + cmp@chromium.org + enne@chromium.org + + Tracks the number of times we encounter a non-corrupt resource while + checking if we can reuse an existing resource. This is only called when we + find a non-corrupt resource, so any resources that aren't corrupt but aren't + tested won't be included in this count. + + Unlike ExistingResourceNotCorrupt this is only emitted when there are any + non-corrupt resources found. + + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the number of times while checking existing resources that we + determined we can reuse that resource. + + + + + cmp@chromium.org + pwnall@chromium.org + Tracks the final internal state for the update job. + + + + cmp@chromium.org + pwnall@chromium.org + + Tracks the resource freshness we cached in a response as we consider whether + we can reuse an existing resource. This metric is in days and typically + reflects the Cache-Control: max-age=X server response header. It may + indicate the Expires: header in some cases at the time of the response if a + max-age header was not provided. Note that max-age is in seconds and we're + generally interested in a range of 0 days to ~1 year. + + + + + spqchan@chromium.org + The number of times an AppleScript event gets called. + + + + + + jshikaram@chromium.org + dominickn@chromium.org + + The actions taken by the user when they are viewing the app details of an + app in App Management (chrome://os-settings/app-management). + + + + + jshikaram@chromium.org + dominickn@chromium.org + The ways the user opens up the App Management interface. + + + + pauljensen@chromium.org + mef@chromium.org + + Whether DnsConfigService::OnConfigChange actually corresponded to a change + in DnsConfig. + + + + + pauljensen@chromium.org + mef@chromium.org + + Duration of time between calls to DnsConfigService::InvalidateConfig. + + + + + pauljensen@chromium.org + mef@chromium.org + Duration of time spent parsing DnsConfig. + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of results of parsing DnsConfig in DnsConfigServicePosix. + + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of results of parsing DnsConfig in DnsConfigServiceWin. + + + + + pauljensen@chromium.org + mef@chromium.org + Whether DnsHosts were parsed successfully. + + + + pauljensen@chromium.org + mef@chromium.org + + Whether DnsConfigService::OnHostsChange actually corresponded to a change in + DnsHosts. + + + + + pauljensen@chromium.org + mef@chromium.org + + Duration of time between calls to DnsConfigService::InvalidateHosts. + + + + + pauljensen@chromium.org + mef@chromium.org + Duration of time spent parsing DnsHosts. + + + + pauljensen@chromium.org + mef@chromium.org + + Counts of results of parsing DnsHosts in DnsConfigServiceWin. + + + + + pauljensen@chromium.org + mef@chromium.org + + Count of servers in DnsConfig. Recorded on every new DnsSession, which is + created on DNS change. + + + + + pauljensen@chromium.org + mef@chromium.org + + Duration of time since the last empty config result to the time a non-change + OnConfigChange is received. + + + + + ericorth@chromium.org + src/net/OWNERS + + Duration of time since the last empty config result to the time a non-change + OnHostsChange is received. + + + + + ericorth@chromium.org + src/net/OWNERS + + The result of DnsConfigService watch. Counts STARTED on every initialization + and FAILED_* on any failure. + + + + + jbauman@chromium.org + + Whether the browser compositor uses GPU or the software renderer. + + + + + alemate@chromium.org + oshima@chromium.org + + The amount of time spent painting a WebContents frame when a window switches + from occluded to visible state. + + + + + seblalancette@chromium.org + + Logged when the Autocomplete Retention Policy cleaned up expired entries. + Expired entries are entries that haven't been used in the last 14 months. + + + + + seblalancette@chromium.org + + Logged when users select Autocomplete entries in the dropdown, this + histogram captures the number of days that have passed since the selected + autocomplete entry was last used. I.e., the distribution of time between + uses of an "active" autocomplete entry. + + + + + seblalancette@chromium.org + + Autocomplete events recorded when the user interacts with suggestions served + from Autocomplete. + + + + + tbansal@chromium.org + ryansturm@chromium.org + chrome-omnibox-team@google.com + jdonnelly@chromium.org + + Type of AutocompleteMatch. Recorded every time the autocomplete action + predictor in omnibox triggers a preresolve, or a preconnect. + + + + + tbansal@chromium.org + + Every time we calculate the confidence for a URL to determine if it should + be prerendered, we track the URL and confidence calculated. When an Omnibox + navigation happens, if we calculated a confidence for that URL, a count is + incremented for the confidence that was calculated. This histogram is then a + histogram of counts that relates the number of correctly predicted URLs to a + confidence value. By comparing that number to the + AutocompleteActionPredictor.NavigationCount and + Prerender.OmniboxNavigationsUsedPrerenderCount histograms, it's possible to + determine the effect of changing the confidence threshold on the accuracy of + prerendering prediction. + + + + + tbansal@chromium.org + + The distribution of network actions recommended by the + AutocompleteActionPredictor. A network action can be one of the enumerated + AutocompleteActionPredictor::Action values: PRERENDER, PRECONNECT, or NONE. + The AutocompleteActionPredictor recommends one of these based on a + confidence score for a given URL and user-entered text pair. + + + + + tbansal@chromium.org + + The distribution of confidence ratings. The AutocompleteActionPredictor uses + a heuristic to calculate a confidence score given a URL and user-entered + text pair. It is in the range [0,1] and is mapped on to a recommended + action, one of the enumerated AutocompleteActionPredictor::Action values: + PRERENDER, PRECONNECT or NONE. This is the distribution of those scores + multiplied by 100. + + + + + tbansal@chromium.org + chrome-omnibox-team@google.com + jdonnelly@chromium.org + + Trackes the number of times something is added, removed, or deleted from the + AutocompleteActionPredictor backing database. + + + + + tbansal@chromium.org + + The distribution of row counts for the AutocompleteActionPredictorDatabase. + Each row contains information regarding the user's Omnibox use history. + + + + + tbansal@chromium.org + chrome-omnibox-team@google.com + jdonnelly@chromium.org + + A boolean that indicates if the autocomplete suggestion under consideration + by the AutocompleteActionPredictor was found in the database. This gives an + upper bound on the fraction of suggestions it is possible to calculate a + confidence for, and thus an upper bound on the fraction of suggestions that + can be prerendered. + + + + + tbansal@chromium.org + + The number of navigations triggered by the Omnibox and seen by the + AutocompleteActionPredictor. This triggers when the Omnibox is showing + Autocomplete results to the user and they select one with the mouse or by + pressing enter. + + + + + robertogden@chromium.org + tbansal@chromium.org + + How old a cached probe result was when it was used, in hours. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the completion status of a probe when it completes each attempt. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the completion status of a probe retry after an externally reported + failure. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the end state of a probe just before it goes inactive. This happens + when the prober succeeds, fails and has no more retries, or the delegate + stops probing. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the net error of a completed or timed out probe. Note that if a HTTP + response does not occur within the probe's TTL, when a sample will also be + added to the ERR_TIMED_OUT bucket. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the number of attempts that are made to achieve a successful probe + result. Only recorded on success. This metric is 1-based so if a probe + succeeds the first time, a sample of 1 will be recorded. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the HTTP response code of a completed probe, when a HTTP response is + received. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the amount of time spent working on a single probe attempt to get to + a failed state. Recorded every time a probe fails. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Records the amount of time spent working on a single probe attempt to get to + a successful state. Recorded every time a probe succeeds. + + + + + phillis@chromium.org + cmumford@chromium.org + The result from updating the app badge on macOS. + + + + timvolodine@chromium.org + device-dev@chromium.org + + Number of batteries reported by the UPower service on Linux at the start of + the Battery Status API. + + + + + timvolodine@chromium.org + + Number of internal batteries reported by MacOS at the start of the Battery + Status API. + + + + + timvolodine@chromium.org + + Number of batteries reported by Windows at the start of the Battery Status + API. + + + + + timvolodine@chromium.org + + Whether the Battery Status API was successfully started up on Android. + + + + + shaktisahu@chromium.org + + Records the size of the uncompressed commit messages received by Blimp + compositor. + + + + + shaktisahu@chromium.org + + Records whether connection attempt to the Blimp engine was successful. + + + + + shaktisahu@chromium.org + Records whether Blimp is supported. + + + + shaktisahu@chromium.org + Records whenever a Blimp tab toggles visibility. + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records a duration of a Bluetooth adapter + being lost. This helps us better understand the Bluetooth controller drop + issue in the field. + + + + + sonnysasaka@chromium.org + + This is specific to Chrome OS. Records a duration of a Bluetooth adapter + being lost caused by hardware disconnection. This helps us better understand + the Bluetooth controller drop issue in the field. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the number of existing advertisements + when registering for a new advertisement. This helps us better understand + the common amount of advertisments used and the registration failures due to + the limited number of advertisement slots. + + + + + + + mmandlik@google.com + chromeos-bt-platform-sw-core@google.com + + Records the outcome of bluetooth profile connection request to a remote + device. This helps to understand the percentage of successful profile + connections against failures and the causes of failures. + + + + + + + mmandlik@google.com + chromeos-bt-platform-sw-core@google.com + + Records the outcome of bluetooth profile probing while pairing with a remote + device. This helps to understand the percentage of successful profile + probing against failures and the causes of failures. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the reason of Bluetooth disconnection + between the local device and the remote Bluetooth device. This helps us + better understand the initiator of disconnection request. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the outcomes of advertisement + registration. This helps us better understand the persentage of successful + advertisements against failures and the causes of failures. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the outcomes of connection requests + to remote devices. This helps us better understand the persentage of + successful connections against failures and the causes of failures. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the outcomes of pairing with remote + devices. This helps us better understand the persentage of successful + pairing against failures and the causes of failures. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the duration when the local device is + performing Bluetooth advertisment and discoverable as a Bluetooth Low Energy + device by other devices. This helps us better understand the amount of + successful advertisment sessions and the duration. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the duration when the local device is + discoverable by other devices as a Bluetooth classic device. This helps us + better understand the amount of requests to expose the local device as a + Bluetooth classic device and the duration. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the duration for the local device to + perform device discovery. This helps us better understand the amount of + device discovery request and the duration for users to find the target + device. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the duration taken to finish a + successful pairing between the local device and a remote Bluetooth device. + This helps us better understand the latency of completing Bluetooth pairing. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the duration taken to finish a + successful connection between the local device and a remote Bluetooth + device. This helps us better understand the latency of connecting to a + Bluetooth device. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the types of device discovery + performed by the local device. This helps us better understand the most + common type of device discovery performed. + + + + + mcchou@chromium.org + + This is specific to Chrome OS. Records the types of discovered devices in + terms of Bluetooth classic, Bluetooth low energy and Dual-mode supports. + This helps us better understand the persentage of Bluetooth devices in terms + of type. + + + + + + + calamity@chromium.org + chrome-analysis-team@google.com + + Logs when a user action triggers a command in the bookmark manager. Commands + can be triggered by keyboard shortcuts, menu items or other buttons in the + UI. + + Revised in M-76 when the "Open (double click/enter)" bucket was + split into two separate buckets, one for bookmarks and one for folders. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + calamity@chromium.org + + Logs where the menu was opened from when a user action opens the command + menu in the bookmark manager. + + + + + calamity@chromium.org + + Logs the number of bookmarks that were dragged simultaneously by a user. + + + + + calamity@chromium.org + dbeam@chromium.org + + Records the time taken to load the bookmarks Web UI and render. This is + roughly equivalent to 'time to first meaningful paint' for the bookmark + manager. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records when a bookmark is added sliced on profile type. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records the count of tabs when a user bookmarks all open + tabs, in incognito mode. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records the count of tabs when a user bookmarks all open + tabs, in regular mode. + + + + + calamity@chromium.org + + Logs the number of bookmark items inside a folder every time a folder is + opened inside the bookmark manager. + + + + + supertri@chromium.org + isherman@chromium.org + aidanday@google.com + mamir@chromium.org + + The total number of bookmarks a user has saved. Recorded when a profile is + opened - precisely, when bookmarks are loaded into storage from disk. The + count includes all bookmarks both in the "Bookmarks Bar" and also + under "Other Bookmarks". + + + + + mamir@chromium.org + mastiz@chromium.org + + The number of bookmarks a user has saved with a URL that is also present in + at least one other bookmark. This excludes folders (which don't have a URL). + Recorded when bookmarks are loaded into storage from disk if there is at + least one duplicate. + + + + + twellington@google.com + chrome-android-app@chromium.org + + Records the number of bookmarks which are opened using the "Open in + incognito tab" button from selection mode in the Android bookmark + manager. + + + + + twellington@google.com + chrome-android-app@chromium.org + + Records the number of bookmarks which are opened using the "Open in new + tab" button from selection mode in the Android bookmark manager. + + + + + mastiz@chromium.org + sky@chromium.org + + Time taken to build the bookmark index. Logged upon profile load when the + bookmarks JSON file is read. + + + + + mastiz@chromium.org + sky@chromium.org + + Time taken to decode the bookmarks JSON file. Logged upon profile load when + the bookmarks JSON file is read. + + + + + mamir@chromium.org + mastiz@chromium.org + + Time to compute values to be logged for UMA metrics + Bookmarks.Count.OnProfileLoad.*. + + + + + ianwen@chromium.org + How users add a new bookmark. + + + + ianwen@chromium.org + Logs a UI location from which a bookmark is launched. + + + + pkotwicz@chromium.org + + Logs how frequently BookmarkModel::OnFaviconsChanged() is called with a + non-empty |icon_url| to determine whether BookmarkNodes should be cached + based on their favicon URLs (e.g. http://www.google.com/favicon.ico) in + addition to their page URLs (e.g. http://www.google.com). OnFaviconChanged() + is expected to be called less than 10 times per user per day with a + non-empty |icon_url|. + + + + + wychen@chromium.org + + Logs whether the bookmark entry is a user bookmark or a partner bookmark + when it is opened. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + The number of times bookmarks are used in each profile type. Recorded when a + bookmark is clicked. + + + + + bccheng@chromium.org + semenzato@chromium.org + Time from power on to login panel ready (Chrome OS). + + + + eustas@chromium.org + Compressed/Decompressed size ratio. + + + + eustas@chromium.org + More detailed failure reason. + + + + eustas@chromium.org + The final state of BrotliFilter. + + + + eustas@chromium.org + Maximal amount of memory allocated by decoder. + + + + yiyix@chromium.org + fserb@chromium.org + + Time spent in microseconds to perform calls to SetFont in Canvas for + Canvas2d. It's measured each time SetFont is called. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + mmourgos@chromium.org + newcomer@chromium.org + + Within one minute of the default network reporting a portal network, if we + see an offline detection result, it is likely the client got blacklisted. + Record the boolean rate that Chrome observes offline vs non-offline + detection results. See go/bad-portal for client blacklisting problem. + + + + + meacer@chromium.org + Records the result of a captive portal probe. + + + + ericorth@chromium.org + doh-core@google.com + cros-networking@google.com + + Reason for attempting a captive portal probe. This is logged only when a + probe HTTP request is made. If there are multiple reasons that triggered + this probe, only the first is logged. + + + + + + + ryanchung@google.com + + Records the result of the Cast certificate verification on the Cast sender. + + + + + + + ryanchung@google.com + + Records whether the correct nonce challenge was in the Cast receiver's + response. + + + + + + + ryanchung@google.com + + Records whether the signature returned by the Cast receiver is verifiable + with the challenge and device certificate. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Records the time the network has been down on a Cast device. Recorded when + network goes up. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + Records the time the network has been up on a Cast device. Recorded when + network goes down. + + + + + takumif@chromium.org + mfoltz@chromium.org + openscreen-eng@google.com + Records the media type of every video being cast. + + + + maybelle@chromium.org + miguelg@chromium.org + + Records the result of a request to play remotely on a per player app basis + within Chrome for Android. + + + + + mfoltz@chromium.org + openscreen-eng@google.com + + Records the percentage of the video left at the time the remote playback is + stopped. This will be recorded when the playback is stopped by the user, or + when it's stopped by the cast device. + + + + + tguilbert@google.com + media-dev@chromium.org + + Records the type of the remote playback device selected by the user. This + will be recorded when the user has chosen the device from the media route + chooser dialog. + + + + + tguilbert@google.com + media-dev@chromium.org + + Record each interaction with the fullscreen remote playback controls in + cases when the corresponding media element on the page was present. + + + + + tguilbert@google.com + media-dev@chromium.org + + Record each interaction with the fullscreen remote playback controls in + cases when the corresponding media element on the page was not present. + + + + + tguilbert@google.com + media-dev@chromium.org + + Indicates whether the corresponding media element on the page was present + when the fullscreen remote playback controls were shown. + + + + + tguilbert@google.com + media-dev@chromium.org + + Records the ratio of the time the media element was detached from the remote + playback session to the total duration of the session (as from when the + element has been attached till when the session stopped or disconnected), in + percents. + + + + + tguilbert@google.com + media-dev@chromium.org + + Records the result of resolving the video URL for cast, including checking + its CORS header. + + + + + posciak@chromium.org + + Indicates whether initialization of a video encode accelerator for Cast + sender was successful. + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + The latency between when a Cast V2 connection is established and the first + message is received on that connection. "Unknown" is the peer + type, which is not known at this point in the CastV2 connection + establishment. Naming conforms to the CastV2 sender-side histogram naming + convention "CastV2.[action].[name].[peer_type]". + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + On accepting a Cast V2 transport socket connection, if an error is + encountered, the error code is logged here. "Unknown" is the peer + type, which is not known at this point in the CastV2 connection + establishment. "SslHandshake.Error" is the name of the action. + Naming conforms to the CastV2 sender-side histogram naming convention + "CastV2.[action].[name].[peer_type]". + + + + + Please list the metric's owners. Add more owner tags as needed. + cast-analytics@google.com + + The time taken to do the handshake during Cast V2 transport socket creation. + "Unknown" is the peer type, which is not known at this point in + the CastV2 connection establishment. Naming conforms to the CastV2 + sender-side histogram naming convention + "CastV2.[action].[name].[peer_type]". + + + + + + + + + rsleevi@chromium.org + + Information about the certificate algorithms and sizes in use on the web, to + examine compliance with the CA/Browser Forum requirements and security best + practice. This histogram considers the notBefore as the issuance date, for + purposes of what requirements apply. + + + + + sinhak@chromium.org + escordeiro@chromium.org + + Number of forced logouts for child accounts on an account reconciliation + error. Check |ChromeOSChildAccountReconcilorDelegate|. + + + + + jam@chromium.org + + Count of child processes killed because they sent an IPC that couldn't be + deserialized. + + + + + + + wfh@chromium.org + chrome-stability-core@google.com + + Recorded when a crash occurs in a Utility process. On crash, the exit code + will indicate the exception code of the crash. + + + + + wfh@chromium.org + chrome-stability-core@google.com + + Count of child utility process crashes, bucketed by the hash of their + process name. The process name is typically the service name of the mojo + service. + + + + + + + wfh@chromium.org + chrome-stability-core@google.com + Count of child process crashes grouped by process type. + + + + wfh@chromium.org + + Count of child process abnormal channel disconnects grouped by process type. + + + + + + + wfh@chromium.org + + Count of child process abnormal channel disconnects that are not classified + and reported because we took the exit code too early. Grouped by process + type. + + + + + asvitkine@chromium.org + + Whether creating field trials from shared memory succeeded. Recorded by each + child process on process startup. + + + + + asvitkine@chromium.org + + Whether creating field trials from --force-fieldtrials switch succeeded. + Recorded by each child process on process startup. + + + + + cduvall@chromium.org + cmumford@chromium.org + + The amount of avaiable memory when a renderer hangs. Recorded for every + renderer hang. + + + + + cduvall@chromium.org + cmumford@chromium.org + + Whether a renderer hang happened in the foreground or background. Recorded + for every renderer hang on Android. + + + + + + + wfh@chromium.org + chrome-stability-core@google.com + Count of child process kills grouped by process type. + + + + oshima@chromium.org + + Out of ChildProcess.Killled, number of kills due to SIGKILL, which is a + strong signal of out of memory on Chrome OS, grouped by process type. + + + + + nasko@chromium.org + + Count of child processes killed by the extension API (processes.terminate). + + + + + wfh@chromium.org + + Count of child utility process launches, bucketed by the hash of their + process name. The process name is typically the service name of the mojo + service. + + + + + rsesek@chromium.org + + The amount of time it took to load the native libraries in the browser + process. + + + + + rsesek@chromium.org + + The amount of time it took to load the native libraries in the renderer + process. + + + + + jamiewalch@chromium.org + + Recorded every time a Chromoting connection enters a new state. + + + + + jamiewalch@chromium.org + + The duration of sessions that were closed, normally by a user-initiated + action. + + + + + jamiewalch@chromium.org + The duration of sessions that failed to connect. + + + + jamiewalch@chromium.org + + The time taken to authenticate as part of a Chromoting connection request. + + + + + jamiewalch@chromium.org + + The time taken to connect to a remote-host, after a request has been + authenticated. + + + + + joedow@chromium.org + lambroslambrou@chromium.org + + Input event delivery latency from the browser to the plugin. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + jamiewalch@chromium.org + + The bandwidth of non-empty packets in Chromoting remote sessions, updated + every time a video packet is processed and logged every 1s. + + + + + jamiewalch@chromium.org + + The time to capture a video frame on the host, returned as part of a video + packet. + + + + + jamiewalch@chromium.org + + Amount of time wasted on IPC and threading overhead when capturing a video + frame. + + + + + joedow@chromium.org + lambroslambrou@chromium.org + + The time from when an input event is received to when the next frame is + captured. + + + + + jamiewalch@chromium.org + The time to decode a video packet on the client. + + + + joedow@chromium.org + lambroslambrou@chromium.org + + The time to encode a video packet on the host, returned as part of a video + packet. + + + + + jamiewalch@chromium.org + + Delay before a newly captured frame is passed to the encoder. + + + + + joedow@chromium.org + lambroslambrou@chromium.org + + The frame-rate of non-empty packets in Chromoting remote sessions, updated + every time a video packet is processed and logged every 1s. + + + + + jamiewalch@chromium.org + + Estimated network roundtrip latency calculated by subtracting total + processing time on host and client from the total roundtrip time. + + + + + jamiewalch@chromium.org + + The packets/sec, including empty packets, in Chromoting remote sessions, + updated every time a video packet is processed and logged every 1s. + + + + + jamiewalch@chromium.org + The time to paint a decoded video packet on the client. + + + + jamiewalch@chromium.org + + The time from an input being sent from the client to a response being + received by the client after it is processed by the host. + + + + + jamiewalch@chromium.org + + Delay before an encoded video packet is written to the send buffer. + + + + + Please list the metric's owners. Add more owner tags as needed. + + The length of time between a dangerous download appearing on the download + shelf, and the "Keep" button being clicked. + + + + + yoavweiss@chromium.org + tbansal@chromium.org + mkwst@chromium.org + + Duration for which the origin requested the client hints to be persisted. + Collected on the renderer side. + + + + + yoavweiss@chromium.org + tbansal@chromium.org + mkwst@chromium.org + + Count of events when the client hints needs to be persisted to the disk by + the browser. + + + + + yoavweiss@chromium.org + tbansal@chromium.org + mkwst@chromium.org + + Count of client hints that need to be persisted to the disk. Recorded by the + renderer. + + + + + huangdarwin@chromium.org + src/ui/base/clipboard/OWNERS + + Counts how often each Clipboard format is read by the platform clipboard. + These reads generally imply that an application requested this format after + checking that the format is available, but there are some cases where Chrome + reads a format to check for existence (outside the + ui::Clipboard::ReadAvailableTypes() function). Please prefer interpreting + these numbers as relative use changes, as opposed to absolute user usage. + + + + + huangdarwin@chromium.org + src/ui/base/clipboard/OWNERS + + Counts how often the Windows clipboard fails to register a format. Recorded + when RegisterClipbaordFormat fails (returns 0). Failure rates will inform + whether we implement error handling. https://crbug.com/1000919 + + + + + huangdarwin@chromium.org + src/ui/base/clipboard/OWNERS + + Counts how often each Clipboard format is written by the platform clipboard. + These writes all imply that an application had this format available, and + therefore wrote this format. + + + + + dcheng@chromium.org + pkotwicz@chromium.org + + The length of time that it takes to transfer ownership of Chrome's CLIPBOARD + selection to the clipboard manager when Chrome exits. + + + + + sorin@chromium.org + + The number of times the component updater called UpdateClient::Install or + UpdateClient::Update. These correspond to the number of manual component + update checks performed as a result of a user action, and the number of + automated component update checks. + + + + + xiaochu@chromium.org + + Chrome OS only. Installation error code in CrosComponentManager. + + + + + xiaochu@chromium.org + Chrome OS only. Time it takes to mount a component image. + + + + sorin@chromium.org + The result of an install or an update check. + + + + sorin@chromium.org + The result of an install or an update check. + + + + sorin@chromium.org + + Time to complete an Install or an Update component update call. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages in the pipeline as a single frame goes + through the various stages in the compositor. This is reported for frames + that went through all the compositor stages in chromium, and was presented + to the user. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages in the pipeline as a single frame goes + through the various stages in the compositor in the cases that there is no + damage from main thread. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + behdadb@chromium.org + sadrul@chromium.org + + For the compositor pipeline, measures how far the presentation time of a + compositor frame is from the frame deadline (i.e. vsync time). + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages in the pipeline as a single frame goes + through the various stages in the compositor. This is reported for frames + that the user did not see: this includes frames that are dropped in various + stages inside chromium, or even frames that went through all stages in + chromium, but ultimately was not presented to the user. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the duration of various stages in the pipeline as a single frame goes + through the various stages in the compositor. This is reported for frames + that went through all the compositor stages in chromium, and was presented + to the user, but were delayed and missed their deadline. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Whether frame is dropped or presented meeting or missing the deadline or is + a compositor only frame. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Modeset attempt result of an external display. Every time an external + display is connected/disconnected, or when the display mode of the external + screen is changed by the user, Chrome attempts to modeset the display. This + metric tracks the result of those attempts. Resolution and RefreshRate + metrics will be recorded for each attempt. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Modeset attempt result of an internal display. This is recorded after Chrome + attempted all the available modes and finally modeset the display. All the + previously attempted modes and refreshes, including the successful one will + be recorded. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Refresh rate of the mode for the display we're about to modeset. This is + recorded every time an external display is connected/disconnected, or when + the display mode of the external screen is about to change. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + DisplayResolution of the mode for the external display we're about to + modeset. 0 means the display was powered off. This is recorded every time an + external display is connected/disconnected, or when the display mode of the + external screen is about to change. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Modeset attempt result of an internal display. Chrome might try additional + modes after a failed attempt. Every time an external display is + connected/disconnected, or when the display mode of the external screen is + changed by the user, Chrome attempts to modeset the display. This metric + tracks the result of those attempts. Resolution and RefreshRate metrics will + be recorded for each attempt. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Modeset attempt result of an internal display. This is recorded after Chrome + attempted all the available modes and finally modeset the display. All the + previously attempted modes and refreshes, including the successful one will + be recorded. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + Refresh rate of the mode for the display we're about to modeset. This is + recorded every time the internal display is powered on/off, or when an + external monitor is plugged in. + + + + + dcastagna@chromium.org + marcheu@chromium.org + chromeos-gfx@chromium.org + + DisplayResolution of the mode for the internal display we're about to + modeset. 0 means the display was powered off. This is recorded every time + the internal display is powered on/off, or when an external monitor is + plugged in. + + + + + chrisha@chromium.org + + The number of confirmed bad modules found during module enumeration. + + + + + chrisha@chromium.org + + The length of time it takes to enumerate the loaded modules in the browser + process. + + + + + chrisha@chromium.org + + The length of time it takes to enumerate the shell extensions. + + + + + chrisha@chromium.org + + The length of time it takes to enumerate the Winsock LSP modules. + + + + + chrisha@chromium.org + + The cumulative length of time it takes to inspect all modules on disk, + extracting their certificates and version information. This work is actually + spread out over a much longer period of time so as not to impact the user. + + + + + chrisha@chromium.org + + The cumulative length of time it takes to enumerate and inspect all modules. + This work is actually spread out over a much longer period of time so as not + to impact the user. + + + + + chrisha@chromium.org + + The number of suspected bad modules found during module enumeration. + + + + + ebeach@google.com + + Connectivity Diagnostics App: WiFi signal strength recorded during + NIC_SIGNAL_STRENGTH test. + +
+ The "Strength" property of a WiFi signal is a partially-reversible + function that linearly maps the RSSI range -120dBm to -20dBm to Strength + values from 0 to 100. +
+ + + + ebeach@google.com + Resolution latency seen by the Connectivity Diagnostics. +
+ Resolver latency is computed by using the chrome.dns API to query three + randomly generated Google hostnames (*-ccd-testing-v4.metric.gstatic.com). + The random hostnames guarantees that there will be no caching of DNS + hostnames. The time taken from issuing the DNS request to receiving a + response is clocked in JavaScript and the arithmetic mean of the three times + is used as the resolver latency. +
+ + + + michaeldo@chromium.org + src/ios/web/web_state/ui/OWNERS + + Logs true when the system touches are cancelled in order to show the Context + Menu instead of performing a default system action. Only logged on iOS. + + + + + michaeldo@chromium.org + src/ios/web/web_state/ui/OWNERS + + Logged when DOM element details are not yet available when the user + completes a long press. Also logs if the context menu was shown once the + element details became available or if the display was cancelled. This + ensures that all context menu gestures are eventually processed. Only logged + on iOS. + + + + + michaeldo@chromium.org + src/ios/web/web_state/ui/OWNERS + + Logged when the Context Menu will be displayed. Also logs if the element for + the last touch was found in the main frame or a iframe. Only logged on iOS. + + + + + mrsuyi@chromium.org + gambard@chromium.org + + Logged when the copying image from context menu is invoked and relevant + events happen during the copying image procedure. + + + + + mrsuyi@chromium.org + gambard@chromium.org + + Result of getting image data by JavaScript for CopyImage, SaveImage and + SearchByImage from iOS context menu. Recorded when the JavaScript returns, + or fails for timeout. + + + + + benwgold@google.com + lens-chrome@google.com + + Whether the user supports the Lens intent and if not, the reason why. + Recorded only if the feature is enabled when the long-press context menu is + shown for an image. + + + + + qinmin@chromium.org + + Type of the url when user saves the content through the save link context + menu. + + + + + + + avi@chromium.org + mpearson@chromium.org + chrome-analysis-team@google.com + + The option that the user selected from a context menu on Android. This is + logged on Android only; check out ContextMenu.SelectedOptionIOS for iOS, and + ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is + invoked on mixed content, only one of the submetrics receives the log; read + the code to determine which one. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + avi@chromium.org + mpearson@chromium.org + + The option that the user selected from a context menu on desktop. This is + logged on desktop only; check out ContextMenu.SelectedOptionIOS for iOS, and + ContextMenu.SelectedOptionAndroid for Android. Note that if a menu is + invoked on mixed content, only one of the submetrics receives the log; read + the code to determine which one. + + + + + + + avi@chromium.org + mpearson@chromium.org + chrome-analysis-team@google.com + + The option that the user selected from a context menu on iOS. This is logged + on iOS only; check out ContextMenu.SelectedOptionAndroid for Android, and + ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is + invoked on mixed content, only one of the submetrics receives the log; read + the code to determine which one. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + mpearson@chromium.org + + Recorded when a context menu is shown, sliced by whether a web contents was + present. (It generally should be; indeed, this code path should not be + followed when it is absent. For instance, invoking a context menu from the + new tab page or from the sad tab page will not cause an emission to this + histogram.) Note that this refers to link context menus, not the + cut-copy-paste context menus that can appear during long presses on text on + a web page or long presses in the omnibox. This is an Android-only metric; + compare with RenderViewContextMenu.Shown and RenderViewContextMenu.Used on + desktop. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + Logged when the callback to fetch the thumbnail returns a result: Success + (bitmap data received) or Failure (null bitmap). Android only. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + The time it takes for the user to abandon the context menu after it's shown + by pressing back or touching outside the menu. This is only logged if the + menu is abandoned. See ContextMenu.TimeToTakeAction.SelectedItem for the + cases where it is closed as a result of user interaction with the menu. + Android only. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + + The time it takes for the user to select an item. This is only logged if the + menu is closed as a result of the user clicking a menu item or a DirectShare + button. See ContextMenu.TimeToTakeAction.Abandoned for the cases where it is + abandoned by the user. Android only. + + + + + twellington@chromium.org + chrome-android-app@chromium.org + Logged when the URL is clicked. Android only. + + + + ramyan@chromium.org + yyushkina@chromium.org + + Number of times the emoji item in the views text services context menu is + used. + + + + + michaeldo@chromium.org + src/ios/web/web_state/ui/OWNERS + + Logs true when the context menu gesture recognizer fully recognizes a long + press, but is still waiting on the DOM element details before the context + menu can be shown. Only logged on iOS. + + + + + johnidel@chromium.org + csharrison@chromium.org + + Records the time it takes to clear conversion data. Logged any time site + data is cleared in Chrome. + + + + + johnidel@chromium.org + csharrison@chromium.org + + Records the "extra" non-scheduled time it took to send a + particular conversion report. This is primarily due to a report's scheduled + report time taking place while the browser is closed. Recorded when a + conversion report is sent. + + + + + johnidel@chromium.org + csharrison@chromium.org + + Records the number of registered conversions + (https://github.com/WICG/conversion-measurement-api) on a given top level + page load. Recorded when the page navigates away or is otherwise closed. + Only recorded for non-off-the-record profiles (OTR profiles have the feature + disabled). + + + + + johnidel@chromium.org + csharrison@chromium.org + + Records the high level request status of a conversion report. Recorded for + every conversion report sent. + + + + + wychen@chromium.org + + The cache hit status of metadata extraction for AppIndexing. + + + + + wychen@chromium.org + + The time spent on scanning the document in the main frame to extract the + metadata. The metadata would be used to feed Icing for CopylessPaste feature + on Android. This only counts pages with failed or empty JSON extraction. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + wychen@chromium.org + The error status of metadata extraction for AppIndexing. + + + + wychen@chromium.org + + The time spent on scanning the document in the main frame to extract the + metadata. The metadata would be used to feed Icing for CopylessPaste feature + on Android. This only counts pages with successful JSON extraction. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + + wfh@chromium.org + chrome-stability-core@google.com + + The exit codes for crashed extension processes. Note: Due to + https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. + + + + + + + wfh@chromium.org + chrome-stability-core@google.com + + The exit codes for crashed renderer processes. Note: Due to + https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. + + + + + jperaza@chromium.org + crashpad-dev@chromium.org + + The reason that a crash report entered the upload pending state. + + + + + jperaza@chromium.org + crashpad-dev@chromium.org + The size of a crash report minidump on disk when captured. + + + + jperaza@chromium.org + crashpad-dev@chromium.org + Logs whether a crash uploaded succeeded or failed. + + + + jperaza@chromium.org + crashpad-dev@chromium.org + The reason that a crash report upload was skipped. + + + + jperaza@chromium.org + crashpad-dev@chromium.org + The outcome of execution of the Crashpad exception handler. + + + + mark@chromium.org + crashpad-dev@chromium.org + The exception code encountered in a crash on Mac OS X. + + + + jperaza@chromium.org + crashpad-dev@chromium.org + The exception code encountered in a crash on Windows. + + + + jperaza@chromium.org + crashpad-dev@chromium.org + + A count of the number of exceptions handled by Crashpad with two buckets for + starting and finishing. + + + + + mark@chromium.org + crashpad-dev@chromium.org + + The exception code encountered for a crash of the crash handler process on + Mac OS X. + + + + + jperaza@chromium.org + crashpad-dev@chromium.org + + The exception code encountered for a crash of the crash handler process on + Windows. + + + + + jperaza@chromium.org + crashpad-dev@chromium.org + Handler start/crash/exit events. + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + Reports the Foundation error code of an attempt to upload a breakpad crash + report. "NSNoError" if the upload was successful. + + + + + mutexlox@chromium.org + iby@chromium.org + cros-telemetry@google.com + + The amount of time crash_sender takes to run when invoked directly on Chrome + OS, without counting time spent sleeping (e.g. for hold_off_time). Used to + make an informed decision about a timeout. + + + + + mutexlox@chromium.org + iby@chromium.org + cros-telemetry@google.com + + The amount of time crash_sender takes to run when invoked directly on Chrome + OS. Used to make an informed decision about a timeout. + + + + + grt@chromium.org + sky@chromium.org + Errors when trying to load DataPack files. + + + + rajendrant@chromium.org + mcrouse@chromium.org + + The request and response size of the messages exchanged by all the services. + Whenever a URLRequest of a service is completed, the number of exchanged + bytes is logged in this histogram. The buckets in this histogram are + services recorded by the corresponding network traffic annotation tag + hashes, so it makes it possible to compare the use of different services in + different conditions. Different conditions are added as suffixes to this + histogram. If the OS is not Android all the requests are considered + foreground. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the data use of Chrome user traffic by the foregound vs. background + state of the app and tab. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + The time since Chrome is in background when background data use happens. + Recorded for each byte of background data use. The source of traffic whether + from user browsing or chrome services is added as suffix to this histogram. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + The time since Chrome is in background when first background data use + happens. Recorded when first background downstream data use after Chrome is + in background. The source of traffic whether from user browsing or chrome + services is added as suffix to this histogram. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Count of total bytes received by the Chrome on the network. With network + servicification this is recorded when requests complete. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Count of total bytes sent by the Chrome on the network. With network + servicification this is recorded when requests complete. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Data use of user traffic by different content types. Recorded in KB when + network bytes are received by Chrome. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the downstream network data use of favicon requests. Logged when the + request is completed or redirected. Zero bytes are recorded when the request + is served from cache. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the downstream network data use of favicon requests with non 200 + response code. Logged when the request is completed or redirected. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Data use of user traffic by different core page transition types. Recorded + in KB when the URL request finishes. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + The total amount of data use of Chrome for user traffic. This traffic has + content::ResourceRequestInfo attached to its request. If the OS is not + Android all the requests are considered foreground. + + + + + satorux@chromium.org + Whether an asynchronous D-Bus method call is successful. + + + + satorux@chromium.org + The time spent for an asynchronous D-Bus method call. + + + + satorux@chromium.org + + Whether a call to a D-Bus exported method is handled successfully. + + + + + satorux@chromium.org + + The time spent for handling a call to a D-Bus exported method. + + + + + satorux@chromium.org + The time spent for handling a D-Bus signal. + + + + satorux@chromium.org + The time spent for sending a D-Bus signal. + + + + satorux@chromium.org + Whether a synchronous D-Bus method call is successful. + + + + satorux@chromium.org + The time spent for a synchronous D-Bus method call. + + + + pmonette@chromium.org + grt@chromium.org + + The HRESULT from ActivateApplication when opening the Win10+ settings page + fails. + + + + + pmonette@chromium.org + + Possible user interactions with the default browser info bar. + + + + + gab@chromium.org + + Results of interaction with set-as-default dialog in Win8+ first run flow. + + + + + pmonette@chromium.org + + The outcome of an attempt to set Chrome as the user's default browser. + + + + + pmonette@chromium.org + + The reason why the default browser settings interaction concluded on Windows + 10. + + + + + pmonette@chromium.org + + The registry keys for the default browser protocols (http/https) are + monitored to know when the user finished interacting with the system + settings. This is how long it took for the last registry watcher to get + signaled. + + + + + + + gab@chromium.org + pmonette@chromium.org + + Whether Chrome was the default browser when it started up. + + Only logged correctly on Windows, Mac, and Linux. Logged incorrectly on + other platforms. + + For ChromeOS, no histogram is necessary because Chrome is always the default + browser. + + For Android, see Mobile.DefaultBrowser.State. + + For iOS, in the future Chrome will be allowed to be the default browser. How + that will be logged is to be decided at the time of writing this + description. + + + + + pmonette@chromium.org + + When changing the default browser on Windows 10, records whether the browser + chooser is successfully invoked when opening the settings page. This + histogram is only recorded when the Win10AcceleratedDefaultBrowserFlow + experiment is enabled. + + + + + pmonette@chromium.org + + The outcome of an attempt to set Chrome as the user's default client for a + protocol. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + The currently active app or window. Sampled during demo sessions and + reported while the user remains active. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Records apps that have been launched by a user using the device during Demo + mode. The sample is recorded when each app is launched. For any given app + id, the metric is recorded only once per Demo Session. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + The source of app launches in demo mode, either the shelf, the app list, or + the highlights app. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + The duration the user spent interacting with the demo session, measured from + the first user activity to the last user activity. This metric rounds the + duration to the nearest second and uses exponential bucketing capped at 1 + hour. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Tracks whether the idle logout warning was canceled or proceeded to logout. + Note: the count of "shown" includes both cases, so the count of + "shown and proceeded" is equal to "shown" minus + "canceled". + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Tracks the reason for removal of pre-install demo resources. To support + offline demo mode, factory Chrome OS devices will have a set of offline + enabled demo mode apps pre-installed. These resources are removed once they + are not needed anymore. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Tracks the result of requests to remove pre-installed demo resources. To + support offline demo mode, factory Chrome OS devices will have a set of + offline enabled demo mode apps pre-installed. These resources are removed + once they are not needed anymore. This will record only requests that + attempted deleting pre-installed resources from disk. Requests that fail + early will be ignored. For example, a request will fail early if the device + is in demo mode, or the resources have already been removed. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + A demo session starts when a user signs in using the policy-configured + public account. It stops when the user signs out, either manually or after + an idle timeout. Session length is the duration between the start and stop + events. It is recorded during signing out and reported on the next chrome + run. This metric tracks the recorded session length rounded down to the + nearest minute and is capped at 2 hours. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + This records the time taken to download the demo mode resources when demo + mode is setup for the first time. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + This records the time taken to enterprise-enroll the device when demo mode + is setup for the first time. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + When demo mode is setup for the first time, it must download the demo mode + resources and enterprise-enroll the device. This records the time taken for + these two steps to complete. (See DemoMode.Setup.DownloadDuration and + DemoMode.Setup.EnrollDuration) + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Records the number of times an operator has encountered an error during the + loading screen and been required to retry setup. This is only recorded after + setup completes successfully. + + + + + drcrash@chromium.org + cros-demo-mode-eng@google.com + + Records how many unique apps have been launched by a user using the device + during Demo mode. The sample is recorded when the DemoMode session closes. + + + + + melandory@chromium.org + + DeprecatedInvlalidatorRegistrar is crashing on the browser shut down. The + reason for the crash is that not all invalidation handlers de-registister + themselves. Histogram records the type of the handler which hasn't + unregistered itself. Analyzing the histogram will allow us to understand, + which handlers are causing the crash. + + + + + pdyson@chromium.org + + Counts the number times dialog boxes are created using a particular parent + class. + + + + + pdyson@chromium.org + + Counts the number times various types of dialog boxes are created. + + + + + pdyson@chromium.org + + How long dialog boxes are open, for dialog boxes created using the parent + class DialogDelegate. This will include bubbles that use + BubbleDialogDelegateView as a parent class, and dialogs that use + DialogDelegateView as a parent class. This is logged on delegate + destruction. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The number of tabs discard candidates. This is recorded each time Chrome + needs to urgently discard a tab. + + + + + + + fdoray@chromium.org + + Number of tabs discarded in each interval of 10 minutes, per discard reason. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The number of tab discard attempts during a high-PMF session. Recorded at + the end of each high PMF session, or when the number of discard attempts + within the same high-PMF session reaches 100 (at which point the counter + will reset, e.g. 102 discards attempts would be recorded in two pieces as + "100" and "2"). + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Indicates if a tab has been successfully discarded during a high-PMF + session. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The memory pressure level when the High-PMF policy decides to discard a tab. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The amount of memory that has been reclaimed after discarding a tab during a + high-PMF session. In the case of a memory increase the value will be + reported as 0 and will go in the underflow bucket. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The number of successful tab discards during a high-PMF session. Recorded at + the end of each high PMF session, or when the number of successful discards + within the same high-PMF session reaches 100 (at which point the counter + will reset, e.g. 102 successful discards would be recorded in two pieces as + "100" and "2"). + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The largest tab's resident set among all the urgent discarding candidates. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + The resident set of the oldest urgent discarding candidate. + + + + sebmarchand@chromium.org + catan-team@chromium.org + + An estimate of the total resident set of Chrome when receiving a critical + memory pressure event, in megabytes. Note that the estimate is based on the + most recent data collected by Performance Manager, which are refreshed at a + low frequency (up to 2 minutes). + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + An estimate of the total resident set of Chrome when receiving a critical + memory pressure event, in percentage of the total amount of RAM. Note that + the estimate is based on the most recent data collected by Performance + Manager, which are refreshed at a low frequency (up to 2 minutes). + + + + + + + fdoray@chromium.org + + Whether the machine was online when a discarded tab was reloaded. + + + + + + + fdoray@chromium.org + + Number of discarded tabs reloaded in each interval of 10 minutes, grouped by + their discard reason. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The amount of physical memory available when receiving a low memory + notification, in megabytes. Windows 8.1+ only. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The time it takes to receive a high memory notification from the OS after + receiving a low memory notification. Windows 8.1+ only. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The memory pressure level when receiving a low memory notification from the + OS. Windows 8.1+ only. + + + + + sashamcintosh@chromium.org + chromeos-gfx@google.com + + Type of failure that occurs during EDID parsing. Typically the failure is + caused by a mismatch between the EDID size and the expected offset of the + data component. + + + + + malaykeshav@chromium.org + + The zoom percentage that the user has set on the internal display and is + actively using. This is emitted when the zoom factor has been updated in + display manager and has not been changed for a while. + + + + + zentaro@chromium.org + baileyberro@chromium.org + + The number of displays connected to the device that are in software or + hardware mirror mode. This is emitted once when the normal or mixed mirror + mode is enabled through API call, or the display configuration changes (e.g. + adding or removing a display) when mirror mode is on. + + + + + zentaro@chromium.org + baileyberro@chromium.org + + The types of mirror mode in which the displays connected to the device are + in. This is emitted once when the normal or mixed mirror mode is enabled + through API call, or the display configuration changes ( e.g. adding or + removing a display) when mirror mode is on. + + + + + zentaro@chromium.org + cros-peripherals@google.com + + The mode in which the connected displays to the device are in. This is + emitted once when displays are added or removed, or when the user changes + the mode by e.g. enabling mirror or unified modes. + + + + + zentaro@chromium.org + cros-peripherals@google.com + + The number of displays connected to the device when Unified Desktop mode is + on. This is emitted when Unified Desktop mode is turned on, or the displays + are added or removed while in Unified Mode. + + + + + zentaro@chromium.org + nohle@chromium.org + + Records the execution time to update the display configuration. Emitted when + the update-display-configuration task finishes, successfully or not. + + + + + zentaro@chromium.org + nohle@chromium.org + + Records whether or not the display configuration was successfully updated. + Emitted when the update-display-configuration task finishes, successfully or + not. + + + + + mgersh@chromium.org + + The duration of time used by the DNS pre-resolving threads to resolve a host + name via the network. Any resolutions that are faster than 15ms are + considered to be local cache hits, not requiring network access, and are not + included in this histogram. This histogram is most useful for estimating the + typical cost of a name resolution, but it also estimates the total number of + network-based resolutions induced by this feature. Not all these resolutions + prove helpful (i.e., the user does not always actually visit the resolved + hostnames). + + + + + ericorth@chromium.org + src/net/OWNERS + + Status of DNS diagnostic probe updates sent to a Chrome net error page. + + + + + ericorth@chromium.org + src/net/OWNERS + + Time ticks between starting and finishing a DNS diagnostics probe. + + + + + ericorth@chromium.org + src/net/OWNERS + Result of DNS diagnostics probes sent by the probe service. + + + + panicker@chromium.org + + Records result of invoking beforeunload handler, that determines whether to + show the dialog. + + + + + hajimehoshi@chromium.org + keishi@chromium.org + + Records the GC count between the time when the document is shut down and and + the time when the document is actually destroyed. This only counts documents + that are destroyed before the process dies. + + + + + hajimehoshi@chromium.org + keishi@chromium.org + + Records documents that survives some GCs after the document is shut down. + + + + + sullivan@chromium.org + + Milliseconds spent in beforeunload dialog. Does not include time to process + beforeunload event in JavaScript (see + DocumentEventTiming.BeforeUnloadDuration). Recorded immediately after + closing dialog, upon user confirmation to navigate away from the page. + + + + + panicker@chromium.org + + Microseconds spent in beforeunload. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + panicker@chromium.org + + Microseconds spent in onfreeze. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + panicker@chromium.org + + Microseconds spent in pagehide. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + panicker@chromium.org + + Microseconds spent in vibilitychange (hidden). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + panicker@chromium.org + + Microseconds spent in onresume. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + panicker@chromium.org + + Microseconds spent in unload. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + fletcherw@chromium.org + bmgordon@chromium.org + project-bolton@google.com + + Chrome OS document scan metric that tracks which SANE backend (effectively a + scanner driver) was used when a scan failed. + + + + + fletcherw@chromium.org + bmgordon@chromium.org + project-bolton@google.com + + Chrome OS document scan metric that tracks which SANE backend (effectively a + scanner driver) that a user requested to use for a scan. + + + + + fletcherw@chromium.org + bmgordon@chromium.org + project-bolton@google.com + + Chrome OS document scan metric that tracks which SANE backend (effectively a + scanner driver) was used when a scan succeeded. + + + + + qfiard@google.com + + The distribution over daily active users of Google Search of the ratio of + Google searches in the past day that were issued by the user on a Google + domain that is not the primary one used by the user over the same time + period. + + + + + qfiard@google.com + + The distribution over daily active users of Google Search of the ratio of + Google searches in the past 30 days that were issued by the user on a Google + domain that is not the primary one used by the user over the same time + period. + + + + + qfiard@google.com + + The distribution over daily active users of Google Search of the ratio of + Google searches in the past week that were issued by the user on a Google + domain that is not the primary one used by the user over the same time + period. + + + + + qfiard@google.com + + The distribution over daily active users of Google Search of the ratio of + Google searches in the past two weeks that were issued by the user on a + Google domain that is not the primary one used by the user over the same + time period. + + + + + grt@chromium.org + + The number of items within the Cache directory that could not be moved aside + following a downgrade. 0 indicates that the target directory could not be + created. + + + + + grt@chromium.org + + Indicates whether or not moving a user's cache dir following a downgrade + succeeded or failed. + + + + + grt@chromium.org + ydago@chromium.org + + The number of items within from an invalid snapshot directory that could not + be moved. 0 indicates that the target directory could not be created. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not moving an invalid snapshot directory succeeded or + failed. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not cleaning up after a snapshot restoration failure + succeeded or failed. + + + + + grt@chromium.org + ydago@chromium.org + + The number of items within from a snapshot directory that could not be + restored following a downgrade. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not restoring a snapshot of the user data dir succeeded + or failed. + + + + + grt@chromium.org + ydago@chromium.org + + The number of items within the user data directory that could not be + snapshotted following an upgrade. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates the id of an item that failed to be copied when taking a user data + snapshot. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not moving a user data snapshot dir before replacing it + with a newer snapshot succeeded or failed. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not creating a profile directory while creating a user + data snapshot succeeded or failed. + + + + + grt@chromium.org + ydago@chromium.org + + Indicates whether or not creating a snapshot of the user data dir succeeded + or failed. + + + + + grt@chromium.org + + The type of User Data downgrade detected, if any. The "none" + bucket is not reported. + + + + + grt@chromium.org + + The number of items within User Data that could not be moved aside following + a downgrade. + + + + + grt@chromium.org + + Indicates whether or not moving a user's User Data dir following a downgrade + succeeded or failed. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Tracks whether the push notification is initially enabled for Drive. + Recorded when the first notification is processed. Notification is emulated + by polling if the push notication is disabled. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Tracks whether the push notification request is registered correctly for + Drive. Recorded when the push notification manager is initialized. + + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to launch Google Drive for the first time. + + + + + dats@chromium.org + sammc@chromium.org + Records outcomes of attempts to mount Google Drive. + + + + dats@chromium.org + sammc@chromium.org + How long did it take to mount Google Drive. + + + + dats@chromium.org + sammc@chromium.org + Records outcomes of attempts to unmount Google Drive. + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to perform a lookup of pinned files in local Google + Drive cache. + + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to perform a search of shared files in local Google + Drive cache. + + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to search a title in local Google Drive cache. + + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to perform a search of shared files in online Google + Drive. + + + + + dats@chromium.org + sammc@chromium.org + + How long did it take to perform a search in online Google Drive. + + + + + slangley@chromium.org + weifangsun@chromium.org + + Outcome of enabling Google Drive offline mode automatically when a user + first logs into a Chrome OS device. This process involves opening a hidden + web page in the context of the Google Drive hosted app to perform the + initialization of offline mode. + + + + + andrescj@chromium.org + mcasas@chromium.org + chromeos-gfx@google.com + + Number of bits per channel described by a parsed EDID blob. This UMA is + recorded whenever the color space is extracted from an EDID blob. + + + + + andrescj@chromium.org + mcasas@chromium.org + chromeos-gfx@google.com + + Whether an EDID blob was detected. This UMA is recorded whenever we attempt + to parse the EDID from a display. + + + + + andrescj@chromium.org + mcasas@chromium.org + chromeos-gfx@google.com + + Whether a EDID blob contained an HDR transfer function (e.g. SMPT SE2084 or + HLG). This UMA is recorded whenever the color space is extracted from an + EDID blob. + + + + + andrescj@chromium.org + mcasas@chromium.org + chromeos-gfx@google.com + + When attempting to get the color space from an EDID blob, whether the sanity + checks passed (and if not, which check failed). This UMA is recorded + whenever the color space is extracted from an EDID blob. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Upon a successful Smart Lock unlock or signin, records whether the user's + phone was locked during any point while the lock screen was up. This can be + used to get a sense for whether users are using Smart Lock for Chromebook + without something like Smart Lock for Android to keep their phones unlocked. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Measures the use of Smart Lock on the sign-in screen: records whether a + Smart Lock login succeeded or failed; or if a password fallback was used, + the reason why. Recorded upon a login attempt for users who have the Smart + Lock feature enabled. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Measures the time elapsed between the user focusing their user pod and + signing in using Smart Lock. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Measures the use of Smart Lock on the lock screen: records whether a Smart + Lock unlock attempt succeeded or failed; or if a password fallback was used, + the reason why. Recorded upon an unlock attempt for users who have the Smart + Lock feature enabled. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Measures the time elapsed between the lock screen being shown and the user + unlocking the device using Smart Lock. The lock screen is typically shown + when the user opens their Chromebook's lid (or otherwise wakes the + computer), but can also be shown when the user manually locks the device. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The hash of the phone model used to successfully sign in or unlock using + Smart Lock. + +
+ This hash is calculated by taking the first 4 bytes of the MD5 hash of the + device model. +
+ + + + hansberry@chromium.org + better-together-dev@google.com + + Measures the exponentially weighted rolling average of the received signal + strength indicator (RSSI) of the phone when the user successfully unlocks or + signs in using Smart Lock. + +
+ The exponentially weighted averaging formula is: + + rollingRssi = (1 - weight) * rollingRssi + weight * currentRssi; + + RSSI readings are inherently noisy, so this averaging gives a smoothed RSSI + value to work with as a heuristic for proximity. + + If no RSSI was read, then a sentinel value of 127 will be recorded. +
+ + + + hansberry@chromium.org + better-together-dev@google.com + + Whether a lock screen and a trust agent are enabled on the remote device + (Android phone) for Easy Unlock. Recorded once per status update message + from the remote device. A status update message is expected to be sent once + when the secure channel between the local and the remote device is + established, and also each time the user-presence status changes on the + remote side. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The time it takes after resuming from a suspended state (ie. opening the + Chromebook lid) to when a remote device is connected and a request is made. + Note that it is possible for the remote device not to be present when + resuming from suspend, and the device may be connected at a later time. + Therefore, large values for this metric may not be too meaningful due to + meddling users. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records the reason that the BottomSheet-based Ephemeral Tab panel was + closed. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records the reason that the Ephemeral Tab panel was closed. Recorded when + the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records whether the user fully opened the Ephemeral Tab panel when it was + shown. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records whether the user opened the Ephemeral Tab panel beyond peeking + state. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records the duration in milliseconds that the Ephemeral Tab was left open. + Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + jinsukkim@chromium.org + + Records the duration in milliseconds that the Ephemeral Tab was peeking. + Recorded when the UX is hidden. Implemented for Android. + + + + + mgiuca@chromium.org + + The number of times the fullscreen bubble was re-shown due to inactivity + during a session of fullscreen mode (not including mouse or keyboard lock). + If the mouse or keyboard is also locked while a re-show occurs, both this + and BubbleReshowsPerSession.MouseLock and/or + BubbleReshowsPerSession.KeyboardLock are incremented. Includes all types of + fullscreen (user-triggered, extension-triggered and page-triggered). + Recorded at the end of the session if the simplified-fullscreen-ui flag is + enabled. + + + + + joedow@chromium.org + + The number of times the keyboard lock exit bubble was re-shown during a + session of keyboard lock mode. This occurs when the ExclusiveAccessMode + inactivity timer fires (roughly every 15 minutes). If also in fullscreen + while a re-show occurs both this and BubbleReshowsPerSession.Fullscreen are + incremented in that scenario. Recorded at the end of the session if the + simplified-fullscreen-ui flag is enabled. + + + + + joedow@chromium.org + + The number of times the keyboard lock exit bubble was re-shown during a + session of keyboard lock mode due to the user pressing the escape key + repeatedly. This metric does not count reshows due to inactivity. Recorded + at the end of the session if the simplified-fullscreen-ui flag is enabled. + + + + + mgiuca@chromium.org + + The number of times the mouse lock bubble was re-shown due to inactivity + during a session of mouse lock mode. If also in fullscreen while a re-show + occurs, both this and BubbleReshowsPerSession.Fullscreen are incremented. + Recorded at the end of the session if the simplified-fullscreen-ui flag is + enabled. + + + + + dewittj@chromium.org + petewil@chromium.org + + If we find a bad catalog from the network, report which problems it had. + + + + + dewittj@chromium.org + petewil@chromium.org + Results of the Explore Sites network request for a catalog. + + + + dewittj@chromium.org + petewil@chromium.org + + The Explore Sites catalog can be requested in several code paths. This + identifies which code path was used for the request. + + + + + + + dewittj@chromium.org + petewil@chromium.org + chrome-analysis-team@google.com + + The number of times the user clicked on a site in a category with the + selected type on the Explore Sites page. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + dimich@chromium.org + + 0-based index of a category tile on NTP which was clicked by the user. + Indices are assigned by counting category tiles left-to-right, top-to-bottom + as they appear on NTP. Recorded on click. + + + + + dewittj@chromium.org + Counts when the explore sites store is opened or closed. + + + + dimich@chromium.org + + Http response code from ExploreSitesFetcher. Recorded every time the fetcher + is finishing without network error and actually has HTTP response code. 2XX + codes also included. + + + + + dimich@chromium.org + + Net error results from ExploreSitesFetcher. Recorded every time the fetcher + is finishing. OK and ABORTED are included. + + + + + freedjm@chromium.org + chrome-explore-team@google.com + Tracks the result of image decoding for the favicons. + + + + dimich@chromium.org + + Number of unique hosts visited by the user during the last 30 days. Reported + at most once a week for all users on Android only, with a 5 second delay + after startup. This is different from History.MonthlyHostCount which is + reported for a percentage of startups, to avoid bias toward more active + users. + + + + + chili@chromium.org + dewittj@chromium.org + + Recorded every time a user navigates out of the explore sites page and comes + back to it within 30 seconds on the same tab. This is used to measure + accidental clicks, where we expect users who navigate to the wrong page will + navigate back to the ExploreSites page immediately afterward. + + + + + dimich@chromium.org + + Recorded every time NTP is opened while ExploreSites feature is enabled. + Indicates whether or not the local cached version of ExploreSites catalog + was available or a network request was initiated to load one. + + + + + dimich@chromium.org + freedjm@chromium.org + + Reported each time from the result callback of the ExploreSitesFetcher. + Values include Success and several failure codes. + + + + + dewittj@chromium.org + petewil@chromium.org + + The total index of the selected tile on the ExploreSites page. This measures + how far down from the top it is, counting all the other tiles in cards above + it. This assumes 10 tiles per category, which is set to the maximum of the + tile counts of all existing variations of the ExploreSites page. + + + + + pmarko@chromium.org + rogerta@chromium.org + + Record the validity of |rlz_embargo_end_date| in RW_VPD. This is recorded + when the VPD value is accessed, which may be multiple times in the same + chrome invocation. This is not recorded when the VPD value is missing. + + + + + agawronska@chromium.org + tobyhuang@chromium.org + xiqiruan@chromium.org + cros-families-eng@google.com + + Records the Chrome OS user session duration in milliseconds. Reports current + daily duration at the first session start on next day. This is only logged + for active usage time of device, determined by UsageTimeState::ACTIVE. + + + + + agawronska@chromium.org + tobyhuang@chromium.org + xiqiruan@chromium.org + cros-families-eng@google.com + + Records the Chrome OS user engagement hour within the current day (0-23), + total of weekday and weekend. Logged on + UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report the + same hour multiple times. + + + + + agawronska@chromium.org + tobyhuang@chromium.org + xiqiruan@chromium.org + cros-families-eng@google.com + + Records the Chrome OS user engagement hour of day (0-23) on weekday. Logged + on UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report + the same hour multiple times. + + + + + agawronska@chromium.org + tobyhuang@chromium.org + xiqiruan@chromium.org + cros-families-eng@google.com + + Records the Chrome OS user engagement hour of day (0-23) on weekend. Logged + on UsageTimeStateNotifier::UsageTimeState changes to INACTIVE. Might report + the same hour multiple times. + + + + + brucedawson@chromium.org + + Records several bits of information about whether the Windows + FaultTolerantHeap might be enabled. This is logged (from a delayed task) + when the browser process starts up. + + + + + victorvianna@google.com + jkrcal@chromium.org + + Records whether an icon already existed in the thumbnail DB when downloading + an on-demand one. On-demand icons are the ones added to local cache without + the user visiting the corresponding page. + + + + + mastiz@chromium.org + + Records the number of large icons that were fetched from the local cache + (e.g. during NTP impression), where the URL (of the page or the icon) + matches a hardcoded blacklist. Suspicious mismatches are reported as errors. + + + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Records the size (concretely the width) in pixel of the favicon downloaded + from Google favicon server (size 0 denotes that download has failed). + + + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Records the size (concretely the width) in pixel of the favicon that is used + to generate a fallback style in the case when large enough favicon is not + available (size 0 denotes that no favicon is available at all). + + + + + + + melandory@chromium.org + Net error codes for failed subscription requests. + + + + + + + + melandory@chromium.org + treib@chromium.org + + Status of the message from the FCM channel. Recorded upon receiving response + from the FCM channel. + + + + + + + melandory@chromium.org + treib@chromium.org + + Status of the initial attempt to retrieve the instance id token. + + + + + tschumann@chromium.org + treib@chromium.org + + Status of resetting the client instance ID, which includes unregistering + from FCM servers. + + + + + + + melandory@chromium.org + treib@chromium.org + + Status of subscription request to the Per User Topic server. Recorded upon + receiving response from server. + + + + + + + melandory@chromium.org + treib@chromium.org + + For each subcription request to the FCM Per-User-Topic server, log the + response received from the server. + + + + + + + melandory@chromium.org + treib@chromium.org + + For each subcription request to the FCM Per-User-Topic server, log the + response received from the server per topic. Note: This is only recorded + with a data type suffix. The base version is never recorded. + + + + + + + melandory@chromium.org + treib@chromium.org + + Records the outcome of instance ID token requests (i.e. whether the token + changed). Such requests are made when invalidations are first enabled (e.g. + on sign-in), and then periodically every 24 hours. + + + + + + + melandory@chromium.org + treib@chromium.org + + Status of unsubscription request to the Per User Topic server. Recorded upon + receiving response from server. + + + + + weili@chromium.org + robliao@chromium.org + + Records how user interacts with Happiness Tracking Surveys (HaTS) bubble + prompt which is shown for a subset of users. Each time when the bubble is + shown, there should be one and only one enum type is recorded. + + + + + sauski@google.com + msramek@chromium.org + + Records the first reason why the Happiness Tracking Surveys (HaTS) bubble + was or was not shown. While the request to show may not meet multiple + criteria, the first criterion is reported here. + + + + + afakhry@chromium.org + cros-telemetry@google.com + Records the source that requested showing the feedback app. + + + + ghendel@chromium.org + pkl@chromium.org + Track whether Firebase is enabled or not at app startup. + + + + jlebel@chromium.org + olivierrobin@chromium.org + + Counts the number of times First Run experience was triggered by another + application launching Chrome. This metric measures the effectiveness of + Smart App Banner promotions on installation of Chrome. + + + + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the Google Apps new user experience. We + record both accept and reject but are not recording when a user ignored the + prompt completely. Users can ignore this prompt by closing the tab or + navigating away, we record when the prompt is shown. + + + + + hcarmona@chromium.org + scottchen@chromium.org + + Records what Google apps were selected as part of the Google Apps New User + Experience. Histogram is only recorded when a user accepts the prompt to add + Google Apps. + + + + + + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the landing page of the onboarding + process. We record that the page was seen and what action the user took. + + + + + hcarmona@chromium.org + johntlee@chromium.org + + Records when a user interacts with the NTP Backgrounds new user experience. + We record the number of times the page is seen, how they interacted with the + page (i.e. interacted with the options and buttons), and through what method + they leave the page (i.e, confirm, cancel, neither). The new user experience + should only be shown once to new profiles. + + + + + hcarmona@chromium.org + johntlee@chromium.org + + Records the time taken to load a NTP background image for preview. This is + recorded when a user clicks on a background to preview and the full-size + version of the background finishes loading. + + + + + + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the set default page of the onboarding + process. We record that the page was seen and what action the user took. + + + + + hcarmona@chromium.org + scottchen@chromium.org + + Records when a user interacted with the sign in interstitial of the + onboarding process. We record that the page was seen and what action the + user took. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + Result of sentinel file has been written. + + + + jlebel@chromium.org + chrome-signin-team@google.com + File error when the sentinel file was not written. + + + + + + fernandex@chromium.org + jlebel@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + Result of the sign in flow during first run on iOS. + + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + WARNING: The list of actions used to identify new tasks hasn't been + attentively updated for several years (as of 2017). Some actions that should + likely be considered new tasks are probably missing. Take this histogram + with a grain of salt. Was expired for M85, M86. + + The amount of time (in seconds) that the app was in the background before + the user started it + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + WARNING: The list of actions used to identify new tasks hasn't been + attentively updated for several years (as of 2017). Some actions that should + likely be considered new tasks are probably missing. Take this histogram + with a grain of salt. Was expired for M77-M86. + + On handsets, the type of the first user action performed after the app was + started or unbackgrounded. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + WARNING: The list of actions used to identify new tasks hasn't been + attentively updated for several years (as of 2017). Some actions that should + likely be considered new tasks are probably missing. Take this histogram + with a grain of salt. Was expired for M82-M86. + + On tablets, the type of the first user action performed after the app was + started or unbackgrounded. + + + + + drott@chromium.org + etienneb@chromium.org + + Time to retrieve the fallback fonts on the system when not found in cache. + + + + + drott@chromium.org + etienneb@chromium.org + The amount of font returned for a given font family. + + + + drott@chromium.org + etienneb@chromium.org + Time to retrieve the fallback fonts on the system. + + + + oyiptong@chromium.org + storage-dev@chromium.org + + Records the number of font families observed by the font enumeration cache + as part of the Font Access API. + + + + + oyiptong@chromium.org + storage-dev@chromium.org + + Records errors returned when obtaining the list of system fonts from + DirectWrite's GetSystemFontCollection. + + + + + oyiptong@chromium.org + storage-dev@chromium.org + + Records the most frequent failure to obtain metadata for a font family when + enumerating fonts as part of the Font Access API. Recorded in + FontEnumerationCacheWin when all fonts have been enumerated. Values are + Windows HRESULT error codes, and also includes custom values specific to + this implementation. + + + + + oyiptong@chromium.org + storage-dev@chromium.org + The number of duplicate fonts returned by fontconfig. + + + + oyiptong@chromium.org + storage-dev@chromium.org + The number of fonts returned by fontconfig. + + + + oyiptong@chromium.org + storage-dev@chromium.org + + The number of fonts whose name table entries could not be read. + + + + + oyiptong@chromium.org + storage-dev@chromium.org + Time spent enumerating fonts. + + + + msalama@chromium.org + msarda@chromium.org + + Tracks revoke actions taken by the account reconcilior to force Dice + migration. To enforce consistency, the reconcilior may invalidate the + primary account or revoke one or more secondary account tokens, if no + equivalent valid gaia cookie exist for those accounts. + + + + + + + droger@chromium.org + msarda@chromium.org + + Reports the network error code for requests to the ListAccounts Gaia + endpoint. + + + + + + + msarda@chromium.org + droger@chromium.org + chrome-signin-team@google.com + + Detailed error type in bad requests for OAuth2 access tokens. Recorded when + a HTTP 400 is received in response to a access token request. + + + + + + + msarda@chromium.org + droger@chromium.org + chrome-signin-team@google.com + + URLFetcher response codes for OAuth2AccessToken. Positive values are HTTP + status codes, negative values are network error codes. Recorded on responses + to OAuth access token requests. + + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + Records an integer value that can be used to identify a connected gamepad + device. The value is constructed from the 16-bit vendor ID in the high-order + bytes and the 16-bit product ID in the low-order bytes, then cast to a + 32-bit signed integer. The GamepadVendorProduct enum lists IDs for several + popular gamepads but is incomplete. To identify a device not included in the + enum, convert back to the vendor/product IDs and look up the human-friendly + product name in go/gamepad-ids. This histogram records a new entry when a + device with a vendor and product ID matching a known gaming input device is + detected during Gamepad API enumeration. + + + + + mattreynolds@chromium.org + deviceapi-team@google.com + + Records an enumeration value identifying the active data fetcher when a + fetcher enumerates a device that is not on the list of known gamepads, but + is recognized as a gamepad by the fetcher. + + + + + Please list the metric's owners. Add more owner tags as needed. + Result of the authentication for Drive. + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gesture was made beyond a threshold big enough to regard it as a + valid gesture navigation i.e. at least 1/3 of the arrow puck is visible. + Similar to 'Triggered' but is used in pair with 'Cancelled' on M81 forward + to measure cancellation rate. Implemented for Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gestures that were cancelled before they were completed. Similar + to 'Abandoned' but is used in pair with 'Activated' on M81 forward to + measure cancellation rate. Implemented for Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Navigations that were triggered due to completed overscroll gesture. + Implemented for Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gesture was made to trigger navigation, but within 3 seconds user + used overscroll gesture to navigate back to the page. Implemented for + Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gesture was made to trigger navigation bottom sheet to peeked + state. Peek state can be entered and exited more than once in a sequence of + overscroll gesture (until user lifts his finger). They are recorded as just + one event per sequence. Implemented for Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Index of the entries in the navigation bottom sheet that user tapped. + Negative means navigating backward, positive forward. Zero index means that + the user chose "Show full history". + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + User tapped one of the entries in the expanded navigation bottom sheet to + navigate to other page. Implemented for Android. + + + + + jinsukkim@chromium.org + chrome-android-app@chromium.org + + Overscroll gesture was made to trigger navigation bottom sheet to expanded + state where the whole list of history items are presented. + + + + + ccameron@chromium.org + graphics-dev@chromium.org + + The time that elapsed between a call to glCreateProgram and the call to + query GL_LINK_STATUS via glGetProgramiv in Skia's GrGLInterface. This + encompasses the creation of the vertex, fragment, and geometry shaders, + their compilation, and their linking. This is called for every program + created by Skia via the GrGLInterface. + + + + + ccameron@chromium.org + khushalsagar@chromium.org + + The time that the GPU's main CPU thread spends waiting for previous frames' + GPU work to complete. Recorded at every frame. + + + + + ccameron@chromium.org + graphics-dev@chromium.org + + Compiling a MTLLibrary will sometimes hang forever. When initializing the + gpu process, a test shader is compiled to see if the MTLCompilerService is + responding or not. This records the time that it took for the compile to + succeeded, up to 1 minute. After 1 minute, a timeout sentinel value of 3 + minutes is reported. + + + + + ccameron@chromium.org + graphics-dev@chromium.org + + Linking a MTLRenderPipelineState will sometimes hang forever. When + initializing the GPU process, a test shader is compiled to see if the + MTLCompilerService is responding or not. This records the time that it took + for the compile to succeeded, up to 1 minute. After 1 minute, a timeout + sentinel value of 3 minutes is reported. + + + + + ccameron@chromium.org + graphics-dev@chromium.org + + The time that it takes to create a new MTLLibrary, including all retries. + Recorded after every call to -[MTLDeviceProxy newLibraryWithSource:] + completes. + + + + + ccameron@chromium.org + graphics-dev@chromium.org + + The time that it takes to create a new MTLRenderPipelineState, including all + retries. Recorded after every call to -[MTLDeviceProxy + newRenderPipelineStateWithDescriptor:] completes. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Presentation timestamp comes from the driver when showing a display frame on + screen. These timestamps could be invalid, and be earlier than the swap + time. This metric records how much time before the swap-time such invalid + timestamps are. If the presentation timestamp is after the swap-time, then + this metric is not recorded. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Presentation timestamp comes from the driver when showing a display frame on + screen. These timestamps can sometimes be in the future. This metric records + how far in the future these timestamps can be. If the timestamp is not in + the future, then this metric is not recorded. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Measures very large (more than 3 minutes) delay in presenting display + frames. Presentation timestamp comes from the driver when showing a display + frame on screen. There are times when the presentation can be delayed a long + time. This metric reports how often this can happen. This is reported only + if the presentation takes 3 minutes or more. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of frames that were shown with checkerboards during a + particular sequence of frames (e.g. during scroll, animation, etc.). Note + that this is only recorded for sequences of length > 4. + + Checkerboarding is measured by tracking the number of times checkerboard + frames are displayed (as opposed to the number of checkerboard frames + produced), since the same checkerboard frame can be displayed more than + once. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Counts the number of frames expected during a particular sequence of frames + (e.g. during scroll, animation, etc.). + + + + + sadrul@chromium.org + mjzhang@chromium.org + graphics-dev@chromium.org + + Tracks the percent of janks for a particular sequence of frames (e.g. during + scroll, animation, etc.). This is reported in various sub-metrics with + suffixes describing the type of the sequence (e.g. TouchScroll etc.). + + Jank is measured by tracking the number of abrupt increases in frame + presentation interval, divided by the total number of frames expected to be + produced and displayed. The lower this number is, the less the smoothness + varies over time. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of dropped frames for a particular sequence of frames + (e.g. during scroll, animation, etc.). This is reported in various + sub-metrics with suffixes describing the type of the sequence (e.g. + TouchScroll etc.). + + PercentDroppedFrames is measured by tracking the number of frames which were + not displayed on screen out of the total number of frames expected to be + produced and displayed. In other words, the lower this number is, the + smoother experience. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + ericrk@chromium.org + + Tracks the percent of dropped frames for a particular sequence of frames for + all animations. This metric is reported for all animations (e.g. + comositor-driven animations, main-thread driven animations, and raf-driven + animations). + + PercentDroppedFrames is measured by tracking the number of frames which were + not displayed on screen out of the total number of frames expected to be + produced and displayed. In other words, the lower this number is, the + smoother experience. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + ericrk@chromium.org + + Tracks the percent of dropped frames for a particular sequence of frames + where a user-input (e.g. scroll, pinch) is active. This metric is reported + for all sources of user-input (i.e. both touchscreen and + touchpad/mouse-wheel). + + PercentDroppedFrames is measured by tracking the number of frames which were + not displayed on screen out of the total number of frames expected to be + produced and displayed. In other words, the lower this number is, the + smoother experience. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + ericrk@chromium.org + + Tracks the percent of dropped frames for a particular sequence of frames. + This metric is reported for all animations and all interactions. + + PercentDroppedFrames is measured by tracking the number of frames which were + not displayed on screen out of the total number of frames expected to be + produced and displayed. In other words, the lower this number is, the + smoother experience. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of frames that missed the deadline for a particular + sequence of frames (e.g. during scroll, animation, etc.). This is reported + in various sub-metrics with suffixes describing the type of the sequence + (e.g. TouchScroll etc.). + + PercentMissedDeadlineFrames is measured by tracking the number of frames + which were displayed on screen but missed the vsync interval. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of frames that missed the deadline for a particular + sequence of frames for all animations. This metric is reported for all + animations (e.g. comositor-driven animations, main-thread driven animations, + and raf-driven animations). + + PercentMissedDeadlineFrames is measured by tracking the number of frames + which were displayed on screen but missed the vsync interval. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of frames that missed the deadline for a particular + sequence of frames where a user-input (e.g. scroll, pinch) is active. This + metric is reported for all sources of user-input (i.e. both touchscreen and + touchpad/mouse-wheel). + + PercentMissedDeadlineFrames is measured by tracking the number of frames + which were displayed on screen but missed the vsync interval. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + sadrul@chromium.org + graphics-dev@chromium.org + + Tracks the percent of frames that missed the deadline for a particular + sequence of frames. This metric is reported for all animations and all + interactions. + + PercentMissedDeadlineFrames is measured by tracking the number of frames + which were displayed on screen but missed the vsync interval. + + Note that this metric is reported only when there are sufficient number of + frames (>= 100). If there are sequences with fewer frames, then these are + aggregated until there are enough frames to produce the metric. + + + + + yiyix@chromium.org + chrome-gpu-metrics@google.com + + The amount of time it takes for the BeginFrame to travel to the Client from + the DisplayCompositor. + + Note that this metrics is only recorded on clients on which a + high-resolution clock is available + + + + + yiyix@chromium.org + chrome-gpu-metrics@google.com + + How long the client takes to prepare a compositor frame after receiving a + BeginFrameArgs. + + Note that this is only recorded on clients on which a high-resolution clock + is available. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the dirty span of the transition animation between + Tab and Grid Tab Switcher. The dirty span is the duration from the start of + the animation to the last View invalidation. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the frame rate of the transition animation between + Tab and Grid Tab Switcher. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the maximum interval between rendered frames during + the transition animation between Tab and Grid Tab Switcher. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the result of thumbnail fetching in the Grid Tab + Switcher. + + + + + vtsyrklevich@chromium.org + dynamic-tools@google.com + + Reports the GWP-ASan crash analysis result. That can either be a + determination that the crash was related to GWP-ASan, not related to + GWP-ASan, or an error making that determination. Recorded with every crash. + + Deprecated in favor of GwpAsan.CrashAnalysisResult.Malloc and + GwpAsan.CrashAnalysisResult.PartitionAlloc in M76 + + + + + sadrul@chromium.org + zmo@chromium.org + + Records the system hardware concurrency collected in the info collection GPU + process, once per UMA ping. For most systems, it is equivalent to the number + of CPU cores. + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + + The number of displays present right after the user has attached or detached + a new display. Excludes mirrored displays, but includes sleeping displays. + + + + + sashamcintosh@chromium.org + chromeos-gfx@chromium.org + + The number of displays present at start up. Excludes mirrored displays, but + includes sleeping displays. + + + + + sadrul@chromium.org + zmo@chromium.org + + Records a rough estimation of the system total disk space collected in the + info collection GPU process, once per UMA ping. + + + + + erikchen@chromium.org + chrome-memory@google.com + + One metric is emitted every 24-hours after Chrome is launched for every + process that is being profiled. The timer is reset if Chrome exits. + + + + + erikchen@chromium.org + chrome-memory@google.com + + One metric is emitted every 24-hours after Chrome is launched for every + Chrome instance that is using out of process heap profiling. The timer is + reset if Chrome exits. + + + + + erikchen@chromium.org + chrome-memory@google.com + + The metric is emitted each time Chrome attempts to record a memory-infra + trace to upload an out-of-process heap-profiling memory dump. + + + + + erikchen@chromium.org + chrome-memory@google.com + + The metric is emitted each time Chrome uploads a trace. It reflects the + uncompressed size of the trace. + + + + + erikchen@chromium.org + chrome-memory@google.com + + The metric is emitted each time Chrome uploads a trace. It reflects whether + the upload was successful. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Which HID were detected when user pressed Continue on OOBE dialog. This + metric is specific to Chrome OS. + + + + + rsorokin@chromium.org + cros-oac@google.com + + Whether HID detection dialog was shown on OOBE. Logged on screen show or on + screen skip respectively. This metric is specific to Chrome OS. + + + + + rsorokin@chromium.org + alemate@chromium.org + cros-oac@google.com + + Records number of times the dialog was shown by the time OOBE is completed. + This metric is specific to Chrome OS. + + + + + asvitkine@chromium.org + bcwhite@chromium.org + + The hash codes of histograms that were found to have bad construction + arguments. These would be DCHECK exceptions in debug builds but have simply + been logged and corrected as best as possible rather than crash. + + + + + asvitkine@chromium.org + + The amount of discrepancy found when examining a single histogram's data in + the browser process for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. + + + + + asvitkine@chromium.org + + The amount of discrepancy found when examining a single histogram's data in + a child process for transmission via UMA. Inconsistent data is NOT + transmitted via UMA. + + + + + asvitkine@chromium.org + bcwhite@chromium.org + + The hash codes of histograms that were found to have construction arguments + different from a previous instantiation of the same name. Entries here have + conflicting definitions and should be investigated. Data collected for the + secondary definitions will be silently dropped. + + + + + Please list the metric's owners. Add more owner tags as needed. + + When metrics services (UMA) ran an update, the number of child processes + that did not respond, providing histogram updates, before the timeout. + + + + + asvitkine@chromium.org + bcwhite@chromium.org + + The hash codes of histograms of which the external name storage was altered + after the histogram was created. + + + + + Please list the metric's owners. Add more owner tags as needed. + + When metrics services (UMA) ran an update, the number of times the process + groups (renderer processes and plugin/gpu processes) did not respond, + providing histogram updates, before the timeout. + + + + + asvitkine@chromium.org + bcwhite@chromium.org + + The hash codes of histograms that were found to request more than 1000 + buckets. These would be DCHECK exceptions in debug builds if the limit is + lowered so are being logged before that change. + + + + + calamity@chromium.org + src/chrome/browser/ui/page_action/OWNERS + + Counts which content setting buttons in the hosted app frame are pressed by + the user. + + + + + calamity@chromium.org + alancutter@chromium.org + + Number of times that each menu item is clicked from the hosted app window + menu button. + + + + + morlovich@chromium.org + + For every http cache transaction with a pattern (see HttpCache.Pattern), the + time from the first access to the disk cache until the transaction was done. + + + + + morlovich@chromium.org + + For http cache transactions in which a network request was sent, the time + elapsed between sending it over the network until the transaction was done. + + + + + morlovich@chromium.org + + For http cache transactions in which a network request was sent, the time + elapsed between beginning the request and sending it over the network; this + is the time spent accessing the disk cache. + + + + + jkarlin@chromium.org + + For each request that results in an unconditionalizable network request, the + cause for the request. + + + + + morlovich@chromium.org + + For each request with HttpCache.CantConditionalizeCause == Zero Freshness, + this is true iff the zero freshness status was determined by looking at + in-memory hints in disk cache index, rather than by opening the entry and + looking at headers. + + + + + jkarlin@chromium.org + morlovich@chromium.org + + The time spent waiting for write lock on a disk cache entry. + + + + + ericrobinson@chromium.org + shivanisha@chromium.org + + Whether the HttpCache was forced to reset upon creation, effectively + clearing out its previous content. This is recorded when the cache is + created for the browsing session. + + + + + jkarlin@chromium.org + shivanisha@chromium.org + + Records whether a cache request has a network isolation key set or not, + which is used for double-keying. + + + + + shivanisha@chromium.org + + Records whether a transaction either created a Writers object when one + didn't exist, or joined an existing Writers object, or why it failed to do + so (e.g., it's a range request, it's not a GET request, etc.). + + + + + morlovich@chromium.org + jkarlin@chromium.org + For each http cache transaction, the recorded pattern. + + + + morlovich@chromium.org + Net error results from non-restartable cache read errors. + + + + morlovich@chromium.org + Net error results from restartable cache read errors. + + + + jkarlin@chromium.org + For each validation attempt, the cause for the validation. + + + + + + garryxiao@chromium.org + cylai@chromium.org + cros-hwsec-userland-eng+uma@chromium.org + + The result of attestation-related operations on the Chrome OS side. + + + + + kojii@chromium.org + layout-dev@chromium.org + The time it takes to open a hyphenation dictionary. + + + + kojii@chromium.org + layout-dev@chromium.org + The time it takes to open a hyphenation dictionary file. + + + + ftang@chromium.org + intl-libs-team@google.com + + This metric logs the creation of key ICU objects. These object creation + called directly from Chrome code or indirectly from depending library such + as blink and v8. + + + + + ftang@chromium.org + intl-libs-team@google.com + + This metric logs the ICU built-in data file name opened and used by chrome. + These file open calls are perform internally inside ICU while Chrome + directly or indirectly call ICU to create object and cause ICU to load new + data files, such as loading codeset conversion table, create break iterator, + and open dictionary files for word break/line break iterator. It however + does not include the opening of resource bundle files. + + + + + gcomanici@chromium.org + + The size of the history on Auto Import from IE. This measure is only logged + on a succesfull Auto Import. + + + + + gab@chromium.org + The importer used on first run Auto Import. + + + + gab@chromium.org + The importer used on import from the bookmarks file API. + + + + gab@chromium.org + + The importer used on import from the chrome://settings/importData UI. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + File error on Windows when ImportantFileWriter fails to mark the temporary + file for deletion upon closure. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + File error happened upon temporary file creation at ImportantFileWriter. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + File error happened upon temporary file deletion at ImportantFileWriter when + it was not possible to retry in a delayed task. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + The final file error when all retries for deleting the temorary file fail. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + The number of retries needed to successfully delete the temporary file. Only + recorded when at least one retry (two attempts) is needed. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + File error happened upon temporary file renaming at ImportantFileWriter. + + + + + grt@chromium.org + xaerox@yandex-team.ru + + File error happened upon writing data to temporary file at + ImportantFileWriter. + + + + + grt@chromium.org + lassey@google.com + + Count of various failures in ImportantFileWrite when manipulating a temp + file to write to before moving it into place (replacing another file). + + + + + robliao@chromium.org + + The thread used to initialize the Windows parental controls. + + + + + robliao@chromium.org + + The amount of time that elapsed during a run of + PlatformParentalControlsValue::IsParentalControlActivityLoggingOnImpl on + Windows 7 and above. + + + + + pmonette@chromium.org + + Records whether the user was automatically shown the + chrome://settings/incompatibleApplications page following a Chrome crash. + + + + + pmonette@chromium.org + + The number of incompatible applications detected by Chrome at the time the + chrome://settings/incompatibleApplications page was opened. + + + + + timvolodine@chromium.org + + Whether the Sensor.TYPE_LINEAR_ACCELERATION was available at the start of + Device Motion. + + + + + timvolodine@chromium.org + + Whether the Sensor.TYPE_ACCELEROMETER was available at the start of Device + Motion. + + + + + timvolodine@chromium.org + + Whether the SENSOR_TYPE_ACCELEROMETER_3D was available at the start of + Device Motion on the Windows platform. + + + + + timvolodine@chromium.org + + Provides a histogram of the base sensors (if any) that are used at the start + of the Device Orientation API. Currently Sensor.TYPE_GAME_ROTATION_VECTOR is + the default sensor for orientation, if it's not available fall-back options + are provided by using either Sensor.TYPE_ROTATION_VECTOR or a combination of + Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD. + + + + + timvolodine@chromium.org + + Whether the SENSOR_TYPE_GYROMETER_3D was available at the start of Device + Motion on the Windows platform. + + + + + timvolodine@chromium.org + + Whether the Sensor.TYPE_GYROSCOPE was available at the start of Device + Motion. + + + + + timvolodine@chromium.org + + Whether the SENSOR_TYPE_INCLINOMETER_3D was available at the start of Device + Orientation on the Windows platform. + + + + + timvolodine@chromium.org + + This histogram counts the number of Device Motion API invocations in the + default implementation (Linux and CrOS). The default implementation does not + provide any sensors so the result is always false. + + + + + timvolodine@chromium.org + + Whether the sudden motion sensor was available at the start of Device Motion + on the MacOS platform. + + + + + timvolodine@chromium.org + + This histogram counts the number of Device Orientation API invocations in + the default implementation (Linux and CrOS). The default implementation does + not provide any sensors so the result is always false. + + + + + timvolodine@chromium.org + + Whether the sudden motion sensor was available at the start of Device + Orientation on the MacOS platform. + + + + + + + rkaplow@chromium.org + src/components/infobars/OWNERS + + Records how many times a particular infobar was shown to the user. On + Android, the infobar may be partially hidden due to stacking. On desktop, a + tab with a visible infobar will increment this histogram every time the user + switches away from the tab and back to it with the infobar still visible. + + + + + + + mdjones@chromium.org + dominickn@chromium.org + + Records how many times a particular infobar was displayed in a hidden state + due to at least one other infobar existing. If there are no existing + infobars, but the user scrolls at the exact moment a new infobar is added, + the infobar may be hidden, but not recorded in this metric. Reliably + triggering and detecting this combination is tricky so it isn't done. Only + recorded on Android. + + + + + + + mdjones@chromium.org + dominickn@chromium.org + + Records how many times a particular infobar was visible and hiding a new + infobar behind it. Only recorded on Android. + + + + + + + mdjones@chromium.org + dominickn@chromium.org + + Records how many times a particular infobar was displayed in a visible state + due to no other infobars existing. If there are no existing infobars, but + the user scrolls at the exact moment a new infobar is added, the infobar may + be hidden, but recorded here as visible. Reliably triggering and detecting + this combination is tricky so it isn't done. Only recorded on Android. + + + + + nyquist@chromium.org + xingliu@chromium.org + + Records if in-product help configuration is parsed correctly, and the + failure reasons for parsing failures. + + + + + nyquist@chromium.org + xingliu@chromium.org + + + + Records if database initialization succeeds for in-product help. + + + + + nyquist@chromium.org + xingliu@chromium.org + + + + Records if database successfully loads the data for in-product help. + + + + + nyquist@chromium.org + xingliu@chromium.org + + Records the total number of event records in the database for in-product + help after the event model is loaded. + + + + + nyquist@chromium.org + xingliu@chromium.org + + + + Records if each database update succeeds for in-product help. + + + + + nyquist@chromium.org + xingliu@chromium.org + + + + Records if the model is ready when in-product help event happens. + + + + + collinbaker@chromium.org + + Last step of in-product help (IPH) for reopening tabs that user followed + before finishing the IPH flow or dismissing it early. Recorded when the IPH + flow is dismissed, which is at one of three possible times: when the promo + bubble times out, when the menu is closed after the user opens it for IPH, + or when the user opens the last closed tab. The last is considered a + success. + + + + + nyquist@chromium.org + xingliu@chromium.org + + + + Records if in-product help is shown to the user, and the failure reasons if + in-product help is not shown. Recorded on its own across all in-product help + features, in addition to being a base name for feature-specific histograms. + + + + + peter@chromium.org + Status code of the outcome of DeleteToken request. + + + + jianli@chromium.org + + Length of time taken to complete the GetToken request successfully. If the + request is retried multiple times, the length of time is counted for the + last successful retry. + + + + + peter@chromium.org + platform-capabilities@chromium.org + + Net error code from an Instance ID GetToken attempt. Recorded when URL + loading completes. + + + + + peter@chromium.org + + The number of options provided to the GetToken request. Recorded when the + request has been received by the InstanceID instance. + + + + + peter@chromium.org + Status code of the outcome of GetToken request. + + + + peter@chromium.org + + Number of Instance IDs restored from the persistent store at startup. + + + + + peter@chromium.org + + Number of InstanceID tokens restored from the persistent store at startup. + + + + + nyquist@chromium.org + khushalsagar@chromium.org + melandory@chromium.org + + Status of sending outgoing invalidation message through GCM upsteam. + + + + + melandory@chromium.org + + Status of the invalidation component. The metric is recorded on startup + unless invalidations are disabled, plus when the state changes. + + + + + erikchen@chromium.org + + Errors that the privileged attachment broker encounters while trying to + broker attachments. + + + + + erikchen@chromium.org + + Errors that an unprivileged attachment broker encounters while trying to + broker attachments. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the amount of time that the navigation to a previously prefetched + page was delayed because cookies had to be copied from the isolated cookie + jar. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records whether a previously prefetched subresource from an Isolated + Prerender was served from cache when its page was later navigated to. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the response body length as cached in memory encountered when + isolated prefetching a mainframe HTML resource from the Google Search Result + Page. Recorded for non-network error prefetches only. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the time taken to establish a socket connection when isolated + prefetching a mainframe HTML resource from the Google Search Result Page. + Recorded for non-network error prefetches only. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the number of cookies that needed to be copied from the prefetch + navigation to the user's profile after a prefetched link is navigated to. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the Net Error encountered when isolated prefetching a mainframe HTML + resource from the Google Search Result Page. Recorded for every completed + prefetch. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the HTTP response code encountered isolated prefetching a mainframe + HTML resource from the Google Search Result Page. Recorded for non-network + error prefetches only. Redirects are not included here. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the total number of redirects encountered while doing all the + prefetches on an eligible Google Search Result page. Only recorded when at + least one prefetch was attempted. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the total time taken when isolated prefetching a mainframe HTML + resource from the Google Search Result Page. Recorded for successful + non-network error prefetches only. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the net error encountered when prefetching a single subresource + during Isolated Prerenders. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the number of subresources that were NoStatePrefetch'd during an + Isolated Prerender. Recorded once for each page that is NoStatePrefetch'd + during Isolated Prerenders. + + + + + robertogden@chromium.org + ryansturm@chromium.org + tbansal@chromium.org + + Records the HTTP response code encountered when prefetching a single + subresource during Isolated Prerenders. + + + + + avi@chromium.org + + For onbeforeunload dialogs, the user's choice between staying on the page + and leaving it. + + + + + avi@chromium.org + carlosil@chromium.org + meacer@chromium.org + + For dialogs, the relationship of the origins of the main frame vs the + alerting frame. + + + + + avi@chromium.org + carlosil@chromium.org + meacer@chromium.org + The scheme of the URL showing a JavaScript dialog. + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Time in milliseconds to acquire a Kerberos ticket. The value is recorded no + matter if the operation was successful or not. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Type of the Chrome OS login user (primary user) who requests Kerberos + tickets. Reported at most once a day by the Kerberos daemon when a Kebreros + ticket is acquired or Kerberos files are requested, which happens e.g. on + Chrome startup. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + The Kerberos encryption types used while succesfully creating or refreshing + a Kerberos TGT. This value is derived from the Kerberos configuration + 'enctypes' fields. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of managed Kerberos accounts owned by the current Chrome OS user. A + managed account is an account that got added via the KerberosAccounts + policy. Reported at most once a day similar to Kerberos.DailyActiveUsers. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of Kerberos accounts owned by the current Chrome OS user that use the + 'Remember password' feature, i.e. the account password is stored by the + Kerberos daemon. Reported at most once a day similar to + Kerberos.DailyActiveUsers. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Total number of Kerberos accounts owned by the current Chrome OS user. + Reported at most once a day similar to Kerberos.DailyActiveUsers. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of unmanaged Kerberos accounts owned by the current Chrome OS user. + An unmanaged account is an account that was added manually by the user. + Reported at most once a day similar to Kerberos.DailyActiveUsers. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Number of Kerberos accounts owned by the current Chrome OS user that use the + login password for authentication. These accounts were added via the + KerberosAccounts policy, using the '${PASSWORD}' placeholder as password. + Reported at most once a day similar to Kerberos.DailyActiveUsers. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to acquire a Kerberos ticket. This happens whenever a + new ticket is added or an existing ticket is reauthenticated. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to add a new Kerberos account, either through the + Kerberos Tickets settings page or via the KerberosAccounts policy. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to clear Kerberos accounts, usually through toggling + Kerberos related policies. For instance, disabling the KerberosEnabled + policy clears all accounts. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to retrieve a Kerberos ticket from the Kerberos + daemon. Systems using Kerberos (Chrome, SMB file shares) perform this action + during startup and when they get notified that the files changed. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to list Kerberos accounts, usually through opening + the Kerberos Tickets settings page or making changes to accounts. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to remove a new Kerberos account through the Kerberos + Tickets settings page. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to set Kerberos configuration. This happens right + before acquiring a Kerberos ticket. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Result from an attempt to validate Kerberos configuration. This happens when + the user tries to set configuration in the Advanced section of the dialog to + add new Kerberos tickets. + + + + + fsandrade@chromium.org + tomdobro@chromium.org + + Error code from an attempt validate Kerberos configuration. Contains more + specific information than KerberosErrorType about the result of the + validation. + + + + + jamescook@chromium.org + msw@chromium.org + wutao@chromium.org + + Time delay between the user gesture that triggered the keyboard shortcut + viewer dialog (e.g. pressing Ctrl-Alt-/) and the dialog widget being shown, + including layout time for the views::Views. + + + + + fhorschig@chromium.org + + Android only. Records whenever users faces an action in the accessory bar or + one of its sheets. + + + + + fhorschig@chromium.org + + Android only. Records whenever users select an action in the accessory bar + or one of its sheets. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Android only. Records how often users encounter the keyboard accessory bar. + Its buckets show the contents when it came up. Every bucket may be logged up + to one time per impression. + + + + + fhorschig@chromium.org + + Android only. Records how many suggestions a user faced when opening a + sheet. The base histogram counts impressions across all sheets. + + + + + fhorschig@chromium.org + + Android only. Records which type of suggestion was selected from an open + sheet. + + + + + ioanap@chromium.org + fhorschig@chromium.org + + Android only. Records how often the user clicks on a certain toggle when + opening an accessory sheet together with the state the toggle was in before + clicking. + + + + + ioanap@chromium.org + fhorschig@chromium.org + + Android only. Records how often the user sees a certain toggle when opening + an accessory sheet together with the state the toggle was in. + + + + + fhorschig@chromium.org + + Android only. Records how often the bottom sheet was opened or closed by a + user and the overall count of closures. Closing buckets may be logged up to + one time per trigger. There are suffixes for each specific sheet type. + + + + + ioanap@chromium.org + fhorschig@chromium.org + + Android only. Records the number of times that the keyboard accessory was + shown on a form for which saving is disabled (with a crossed-out key icon). + Recorded when the user focuses the password field. + + Note: Only the "Shown" bucket should contain samples. + + + + + + + ioanap@chromium.org + vasilii@chromium.org + + Android only. Records the interactions with the password generation dialog + for automatic generation. + + + + + xiyuan@chromium.org + apotapchuk@chromium.org + Tracks cryptohome failure during kiosk launch. + + + + xiyuan@chromium.org + apotapchuk@chromium.org + Tracks kiosk launch errors. + + + + xiyuan@chromium.org + aghuie@chromium.org + + Records kiosk launches, whether it is an enterprise or consumer kiosk and + whether it is an auto launch or manual launch. + + + + + googleo@chromium.org + chrome-language@google.com + + The actions taken on languages settings, recorded every time they happen. + This histogram will record every single event that happens separately. + + + + + googleo@chromium.org + chrome-language@google.com + The type of panes which language settings loads. + + + + anthonyvd@chromium.org + frechette@chromium.org + chrome-language@google.com + Accept languages. + + + + dvallet@chromium.org + chrome-language@google.com + The number of accepted languages in the user preferences. + + + + anthonyvd@chromium.org + frechette@chromium.org + chrome-language@google.com + Application languages used for UI. + + + + + + asvitkine@chromium.org + ntfschr@chromium.org + + Logs which Chrome flags from about:flags were active on start up. Android + WebView supports flags differently than most platforms, see + https://chromium.googlesource.com/chromium/src/+/HEAD/android_webview/docs/developer-ui.md + for details. + + + + + dominickn@chromium.org + hartmanng@chromium.org + peconn@chromium.org + + Records how Chrome handled a launch from an Android Home screen shortcut. + + + + + dominickn@chromium.org + hartmanng@chromium.org + peconn@chromium.org + + Records the source of an Android homescreen launch intent used to launch + Chrome. + + The Menu item bucket is deprecated as of M57, and will only contain records + for shortcuts added to the homescreen until M56. + + For M57+, the Menu item (standalone) bucket contains all launch intents + originating from the add to homescreen menu item that launch to standalone + mode and *are not* WebAPKs. These are sites which do not meet the PWA + eligibility criteria, but have an app manifest that specifies either + standalone or fullscreen display. This bucket also contains PWA *and* + non-PWA intents that were added to the homescreen *prior* to M57, as we + cannot distinguish between them after they are added. + + For M57+, the Menu item (shortcut) bucket contains all launch intents + originating from the add to homescreen menu item that launch to a browser + tab, regardless of when the intent was added. + + + + + dfalcantara@chromium.org + + Records flags (and combinations of flags) that were attached to the Intent + that started ChromeLauncherActivity. + + + + + + + calamity@chromium.org + grt@chromium.org + The different ways Chrome is launched. + + + + peter@chromium.org + yfriedman@chromium.org + + Records the display mode (as defined in the Web App Manifest spec) at the + launch of the Added to Home screen or installed Web App (including WebAPKs). + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, at least half of which were + complex text fragments, the average number of microseconds spent laying out + each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, at least half of which were + floats, the average number of microseconds spent laying out each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, the average number of + microseconds spent laying out each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, at least half of which were + fixed or absolute positioned, the average number of microseconds spent + laying out each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, at least half of which were + simple text fragments, the average number of microseconds spent laying out + each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + benjhayden@chromium.org + + For layouts that considered at least 100 nodes, at least half of which were + table cells, the average number of microseconds spent laying out each node. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + skobes@chromium.org + + Records the number of times ScrollAnchor adjusts the scroll offset. + + + + + pnoland@chromium.org + + Records the status of attempts to restore a serialized scroll anchor. + + + + + pnoland@chromium.org + + The number of characters in the selector computed for a serialized scroll + anchor. Recorded when a scroll anchor is serialized. + + + + + ymalik@chromium.org + + Records the number of times scroll anchoring is suppressed because of the + SANACLAP bit being set on an ancestor (see bit.ly/sanaclap). + + + + + pnoland@chromium.org + + The time it took to compute the selector of a serialized anchor element. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ymalik@chromium.org + + The time it took to find a suitable anchor element. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + pnoland@chromium.org + + The time it took to restore the scroll anchor using the serialized anchor + element. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + nyquist@chromium.org + salg@google.com + + The approximate MemTable memory use of a LevelDB in bytes. Recorded right + after initializing an on-disk database. + + + + + cmumford@chromium.org + chrome-owp-storage@google.com + + Tracks the success rate of deleting an unused leveldb table backup file. + + + + + dmurph@chromium.org + pwnall@chromium.org + Methods where leveldb's Chromium environment has IO errors. + + + + dmurph@chromium.org + pwnall@chromium.org + + Number of backup files found without corresponding ldb files. As measured by + GetChildren when used in LevelDB clients other than IndexedDB. + + + + + mek@chromium.org + + Delay between the browser process receiving changes and those changes being + written to the DB. + + + + + chengx@chromium.org + + This metric records the LoadLibraryExW and LoadLibraryW Windows API call + results, which are used in native_library_win.cc. + + + + + lizeb@chromium.org + + Percentage of the native library code pages resident in memory. Recorded + immediately before the library prefetching kicks in, only on Android. + + + + + thestig@chromium.org + thomasanderson@chromium.org + + The Debian version number (eg. 8: Jessie, 9: Stretch). Logged once on + startup if Linux.Distro is Debian. + + + + + thestig@chromium.org + thomasanderson@chromium.org + + The Fedora version number (eg. 27, 28) Logged once on startup if + Linux.Distro is Fedora. + + + + + thestig@chromium.org + thomasanderson@chromium.org + + The openSUSE Leap version number, logged as 1000*major + minor (eg. 15001 = + 15.1). Logged once on startup if Linux.Distro is openSUSE Leap. + + + + + thestig@chromium.org + thomasanderson@chromium.org + + The Ubuntu version number, logged as 1000*year + month (eg. 16004 = 16.04 + Xenial). Logged once on startup if Linux.Distro is Ubuntu. + + + + + thestig@chromium.org + thomasanderson@chromium.org + The Linux distro used. Logged on each start up. + + + + thestig@chromium.org + + The version of glibc used. (Linux only) Logged on each start up. + + + + + mpdenton@google.com + src/sandbox/linux/OWNERS + + The Linux sandbox status. This describes what sandboxing features are + enabled (such as the suid/namespace sandboxes, various namespaces, seccomp + bpf, ...). Emitted once at startup. + + + + + pkotwicz@chromium.org + thomasanderson@chromium.org + + The window manager used. (Linux only) Logged on each start up. + + + + + thomasanderson@chromium.org + rjkroege@chromium.org + + The amount of time (ms) to construct the GbmSupportX11 singleton. + + + + + thomasanderson@chromium.org + + RTT between Chrome and the X11 server. Tracked in X11EventSource by + measuring the latency to receive a property event after changing a property. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + mcrouse@chromium.org + rajendrant@chromium.org + + Whether the LiteVideo hint cache contains hint for the host of the + navigation being considered for the LiteVideo optimization. Recorded for + every HTTP/HTTPS navigation. + + + + + mcrouse@chromium.org + rajendrant@chromium.org + + When determining whether the LiteVideo should be attempted on a navigation, + the host could be blocklisted for various reasons. This reports the reason + the host of the navigation was blocklisted, or was allowed. Recorded for + every HTTP/HTTPS navigation. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the total count of media responses that were currently being + throttled. Recorded whenever a new response gets throttled. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records whether the LiteVideo hint agent in the renderer process received + hints. + + + + + mcrouse@chromium.org + rajendrant@chromium.org + + Records the total number of LiteVideoHints, keyed by host, cached locally by + the LiteVideoDecider for use when queried by subframes. + + + + + mcrouse@chromium.org + rajendrant@chromium.org + + Records the number of entries in the map that records the number of rebuffer + events within each frame. Recorded once per navigation. + + + + + mcrouse@chromium.org + rajendrant@chromium.org + + Indicates whether the hints for configuring LiteVideo throttling provided + via Finch were successfully parsed and loaded for use. Android only, + recorded once per browser startup. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records how much a media response was throttled by LiteVideo. Recorded once + for each throttled response. + + + + + sophiechang@chromium.org + tbansal@chromium.org + + The status of when the optimization hints were received by the Loading + Predictor. This will be recorded on navigations for which predictions from + the Optimization Guide were received. + + + + + alexilin@chromium.org + + The number of origins that were preconnected for a page load. It includes + preconnect attempts that don't result in new opened connection. Logged after + the preconnect manager completes all jobs attached to the page load. + + + + + alexilin@chromium.org + + The percentage of origins that were preconnected and requested by a page + load to the total number of origins that were preconnected for a page load. + Logged after the preconnect manager completes all jobs attached to the page + load. + + + + + alexilin@chromium.org + tbansal@chromium.org + + When the loading predictor has origins in the local database for a given + navigation to preconnect and preresolve, the count of predicted origins. + + + + + alexilin@chromium.org + tbansal@chromium.org + + When the loading predictor has origins in the local database for a given + navigation to preconnect and preresolve, the precision of the predictions in + percentage. This is computed as 100 \times \frac{correct + predictions}{predictions}. + + + + + alexilin@chromium.org + tbansal@chromium.org + + When the loading predictor has origins in the local database for a given + navigation to preconnect and preresolve, the recall of the predictions, in + percentage. This is computed as 100 \times \frac{correct predictions}{all + prefetchable subresources}. + + + + + alexilin@chromium.org + tbansal@chromium.org + + When the prefetch predictor has origins in the local database for a given + navigation to preconnect and preresolve, records stats about whether + redirect was predicted correctly or incorrectly. + + + + + alexilin@chromium.org + + The number of hosts that were preresolved for a page load. It includes only + successful DNS lookups. Logged after the preconnect manager completes all + jobs attached to the page load. + + + + + alexilin@chromium.org + + The percentage of hosts that were preresolved and requested by a page load + to the total number of hosts that were preresolved for a page load. Logged + after the preconnect manager completes all jobs attached to the page load. + + + + + tbansal@chromium.org + + Original Blink priority of the request that belongs to an iframe. Recorded + for every request fetched via Blink, but only when the experiment to lower + the priority of iframes is enabled. + + + + + tbansal@chromium.org + + Original Blink priority of the request that belongs to the main frame. + Recorded for every request fetched via Blink, but only when the experiment + to lower the priority of iframes is enabled. + + + + + + + amoylan@chromium.org + alanlxl@chromium.org + + CPU time (for one CPU core) of one Chrome OS ML Service request. Reported + for all users; users without high-resolution clocks will report 0 for short + requests. + + + + + alanlxl@chromium.org + amoylan@chromium.org + + Fraction of total CPU resources used by Chrome OS ML Service, sampled every + 5 minutes. + + + + + amoylan@chromium.org + alanlxl@chromium.org + + The result of CreateGraphExecutor, which can be OK or some specific error. + + + + + amoylan@chromium.org + alanlxl@chromium.org + + The result of Execute, which can be OK or some specific error. + + + + + amoylan@chromium.org + alanlxl@chromium.org + charleszhao@chromium.org + + The result of load handwriting model, which can be OK or some specific + error. The error code could be logged in machine learning service in chrome + or in chromeos when handwriting model is not loaded successfully. + + + + + amoylan@chromium.org + alanlxl@chromium.org + charleszhao@chromium.org + + The result of handwriting recognition, which can be OK or some specific + error. + + + + + amoylan@chromium.org + alanlxl@chromium.org + + The error result of LoadModel in cases when the model name could not be + determined. See MachineLearningService.*.LoadModelResult.Event for the + result broken down by model name when the name is known. + + + + + amoylan@chromium.org + alanlxl@chromium.org + + The result of LoadModel, which can be OK or some specific error. + + + + + alanlxl@chromium.org + amoylan@chromium.org + + Events related to the connection and disconnection of the Mojo IPC channel + between Chrome and the Chrome OS ML Service. + + + + + alanlxl@chromium.org + amoylan@chromium.org + honglinyu@chromium.org + + Peak total (shared and non-shared) memory used by Chrome OS ML Service over + the last 24 hours. Sampled every 5 minutes, so may miss short-lived spikes. + + + + + amoylan@chromium.org + alanlxl@chromium.org + honglinyu@chromium.org + + Memory usage increase caused by one Chrome OS ML Service request. + + + + + alanlxl@chromium.org + amoylan@chromium.org + honglinyu@chromium.org + + Total (shared and non-shared) memory used by Chrome OS ML Service, sampled + every 5 minutes. + + + + + yilkal@chromium.org + michaelpg@chromium.org + cros-families-eng@google.com + + The number of blocked iframes per unblocked main frame load. The value is + recorded when the main frame finishes loading. + + + + + agawronska@chromium.org + cros-families@google.com + + The counts of results from supervised user URL filtering. Each entry + includes the outcome of the filter (i.e. allowed, blocked, or unknown) and + the page transition type (how the user got there, e.g. typed URL, clicked + link). + + + + + escordeiro@chromium.org + unichrome-eng@google.com + + The extra page load delays introduced by network requests due to the + supervised user url filtering feature, measured once per page load, for + failed requests. This is the delay to fetch the token and call the + ClassifyUrl rpc, when there is a cache miss. + + + + + escordeiro@chromium.org + unichrome-eng@google.com + + The extra page load delays introduced by network requests due to the + supervised user url filtering feature, measured once per page load. This is + the delay to fetch the token and call the ClassifyUrl rpc, when there is a + cache miss. Only recorded for successful requests. + + + + + escordeiro@chromium.org + unichrome-eng@google.com + + The counts of response status from supervised user + KidsManagementURLCheckerCLient. Each entry includes the outcome of a request + (i.e. success, net error, parsing error). + + + + + michaelpg@chromium.org + yilkal@chromium.org + cros-families-eng@google.com + + The counts of request for permission sent from main frame or sub-frame. + + + + + agawronska@chromium.org + cros-families@google.com + + The extra page load delays introduced by network requests due to the + supervised user SafeSites feature, measured once per page load. + + + + + treib@chromium.org + escordeiro@chromium.org + menegola@chromium.org + + The counts of results from the supervised user safety filter. Each entry + includes the outcome of the filter (i.e. allowed, blocked, or unknown) and + the page transition type (how the user got there, e.g. typed URL, clicked + link). This only includes URL requests that were handled by the SafeSites + filter (both online and the static blacklist). + + + + + agawronska@chromium.org + cros-families@google.com + + The number of whitelists installed for a supervised user. Recorded at every + profile startup. + + + + + mgiuca@chromium.org + mlamouri@chromium.org + + Tracks whether the Manifest fetch succeed and why it failed if it failed. + + + + + mgiuca@chromium.org + mlamouri@chromium.org + + Tracks which properties of a Manifest were present when it was parsed. If a + property can't be parsed, it will be recorded as not present. These + histograms will only be used if the Manifest was correctly fetched and + parsed and the parsed manifest is not empty. + + + + + mgiuca@chromium.org + mlamouri@chromium.org + + Tracks the Manifest parsing result. A failure will be recorded if the + Manifest was incorrectly structured. This doesn't take into account parse + failures for each individual properties. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of credentials presented to the user in the "Use + other password..." view in Manual Fallback. This is logged everytime + the user opens this view. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of cards presented to the user in Manual Fallback. This is + logged everytime the user opens this view. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of credentials presented to the user in the Passwords + Manual Fallback view. This is logged everytime the user opens this view. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of profiles presented to the user in Manual Fallback. This + is logged everytime the user opens this view. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of autofill suggestions present when the user taps on the + credit card button in manual fallback. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of password suggestions present when the user taps on the + password button in manual fallback. + + + + + javierrobles@chromium.org + gambard@chromium.org + + Tracks the number of autofill suggestions present when the user taps on the + profiles (address) button in manual fallback. + + + + + akhouderchah@chromium.org + benchan@chromium.org + + The result (e.g. success or the type of failure) of a modem interface switch + operation performed by mist on Chrome OS. + + + + + carlosil@chromium.org + + The net error or HTTP response code of a mixed content resource request that + was autoupgraded to HTTPS + + + + + carlosil@chromium.org + + Whether or not an autoupgrade mixed content request was for a resource we + know to be an ad + + + + + carlosil@chromium.org + estark@chromium.org + + Logs the type of each resource request that is autoupgraded to HTTPS and + fails to load. + + + + + carlosil@chromium.org + estark@chromium.org + + Logs the type of each resource request that was autoupgraded to HTTPS and + resulted in a response. + + + + + carlosil@chromium.org + estark@chromium.org + + Logs the type of each resource request that is autoupgraded to HTTPS. This + is logged when the request is started. + + + + + carlosil@chromium.org + + The status of a mixed content resource request that was autoupgraded to + HTTPS + + + + + pmonette@chromium.org + + Records the result of writing the path of the module blacklist cache to the + registry so that chrome_elf.dll can use it. A value is emitted every time + the cache is updated because another instance of Chrome with a different + User Data directory could have overwritten the path to point to their own + version of the cache. + + + + + pmonette@chromium.org + + The status of a blacklisted module in the process. Recorded when the cache + is updated. + + + + + pmonette@chromium.org + + The result of deleting the module blacklist cache when third-party module + blocking is disabled. Attempting to delete an empty file is considered a + success. + + + + + pmonette@chromium.org + + Records whether the MD5 digest of the module blacklist cache matched the one + recorded in the Local State file. + + + + + pmonette@chromium.org + + Records the number of modules in the module blacklist cache at the time it + was written to disk. + + + + + pmonette@chromium.org + + The result of reading the current module blacklist cache while updating it. + + + + + pmonette@chromium.org + The result of writing the updated module blacklist cache. + + + + anthonyvd@chromium.org + + Represents the amount of bytes in a module that are different on disk and in + memory. Logged when the ModuleIntegrityVerifier determines that a module is + different on disk and in memory after being triggered by an incident. + + + + + grt@chromium.org + + Logged when the relocations in a module are not ordered causing the module + verification to abort. + + + + + amistry@chromium.org + bgeffon@chromium.org + rockot@google.com + The number of handles sent with a channel message. + + + + amistry@chromium.org + bgeffon@chromium.org + rockot@google.com + + Measures the time taken to fully write a channel message to the underlying + channel. + + + + + amistry@chromium.org + bgeffon@chromium.org + rockot@google.com + The size of a message written to a channel. + + + + amistry@chromium.org + bgeffon@chromium.org + rockot@google.com + + Tracks whether or not a message is written directly to a channel or queued. + + + + + amistry@chromium.org + bgeffon@chromium.org + rockot@google.com + + The number queued messages waiting to be written, measured when a channel + flush is attempted. + + + + + siggi@chromium.org + rockot@chromium.org + + The maximal unread message quota used for the lifetime of a Connector. This + is sampled for a configurable percentage of Connectors only when the feature + MojoRecordUnreadMessageCount is enabled. By default 1% of Connectors are + sampled, as there's some overhead involved in enabling the unread message + quota on a MessagePipe. See //mojo/public/cpp/bindings/lib/connector.cc. + + + + + mek@chromium.org + Methods where leveldb's Mojo environment has IO errors. + + + + zentaro@chromium.org + cros-peripherals@chromium.org + Tracks mouse acceleration setting changes by the user. + + + + zentaro@chromium.org + cros-peripherals@chromium.org + Tracks mouse acceleration setting on startup. + + + + zentaro@chromium.org + cros-peripherals@google.com + + Tracks mouse sensitivity setting changes by the user. This replaces the old + Mouse.Sensitivity.Changed metric. + + + + + zentaro@chromium.org + cros-peripherals@google.com + + Tracks mouse sensitivity setting on startup. This replaces the old + Mouse.Sensitivity.Started metric. + + + + + lannm@chromium.org + Tracks mouse reverse scroll setting changes by the user. + + + + lannm@chromium.org + Tracks mouse reverse scroll setting on startup. + + + + + + khorimoto@chromium.org + zentaro@chromium.org + Whether mouse scroll acceleration is enabled. + + + + + + khorimoto@chromium.org + zentaro@chromium.org + Mouse scroll sensitivity value. + + + + ppi@chromium.org + + The time it takes to spawn the first child subprocess (including sandbox + init). + + + + + ppi@chromium.org + + The time it takes to spawn child sub processes not counting the first one. + + + + + lizeb@chromium.org + + Time to call fork() or clone(), in ms. Recorded at each fork excluding from + the zygote, only on posix platforms. + + + + + ppi@chromium.org + + The number of RenderProcessHosts (i.e. renderer processes) present when each + load completes. This is basically the average number of sub-processes over + time. See also Tabs.TabCountPerLoad. + + + + + Please list the metric's owners. Add more owner tags as needed. + TBD + + + + jbauman@chromium.org + + Time from tab switch requested to tab appearing on screen (Aura and Mac + only). + + + + + vecore@google.com + better-together-dev@google.com + hsuregan@chromium.org + + Breaks down the percentage of users who either accepted or declined + MultiDevice OOBE setup. + + + + + vecore@google.com + better-together-dev@google.com + + Counts the number of each MultiDevice setup notification clicked by a user. + This metric should be compared with MultiDeviceSetup_NotificationShown. + + + + + vecore@google.com + better-together-dev@google.com + + Counts the number of each MultiDevice setup notification dismissed by a + user. This metric should be compared with + MultiDeviceSetup_NotificationShown. + + + + + vecore@google.com + better-together-dev@google.com + + Counts the number of each MultiDevice setup notification shown to a user. + + + + + skuhne@chromium.org + + Count the number of times each UI path is taken for switching the active + account in a Chrome OS multiprofile session. UI paths include the system + tray and the keyboard shortcut. + + + + + skuhne@chromium.org + + Counts the number of teleported windows by types in separated desktop mode. + + + + + skuhne@chromium.org + + The number of users simultaneously signed into a multiprofile session on + Chrome OS. This is recorded whenever a user gets added to the session. To + get the correct count, all following counts must be subtracted. Example: If + 100 single user, 20 two user and 5 three user sessions, there were + 100-20-5=75 single user sessions, 100-80=20 dual user sessions and so on. + + + + + mek@chromium.org + src/content/browser/native_file_system/OWNERS + + Did the user confirm read access to a directory via the Native File System + API. + + + + + mek@chromium.org + src/content/browser/native_file_system/OWNERS + + The number of files a user picked using the file picker in the Native File + System API. Recorded as 0 if the user cancelled the picker. + + + + + mek@chromium.org + src/content/browser/native_file_system/OWNERS + + The result of an attempt to request write permission to a file or directory + via the Native File System API. + + + + + mek@chromium.org + src/content/browser/native_file_system/OWNERS + + Records if the file or directory selected by the user through the Native + File System API is considered a sensitive directory, and thus was blocked. + + + + + mek@chromium.org + src/content/browser/native_file_system/OWNERS + + The result of an attempt to request write permission to a file or directory + via the Native File System API. + + + + + simmonsjosh@google.com + src/chrome/browser/chromeos/smb_client/OWNERS + + The method used to authenticate to a share. This is called on each attempted + mount. + + + + + simmonsjosh@google.com + src/chrome/browser/chromeos/smb_client/OWNERS + + The result of the GetShares operation for Native SMB File Share. This is + recorded after the D-Bus call to GetShares returns. + + + + + simmonsjosh@google.com + src/chrome/browser/chromeos/smb_client/OWNERS + + The number of active mounts that a user has. This is recorded after a share + has been successfully mounted. + + + + + simmonsjosh@google.com + src/chrome/browser/chromeos/smb_client/OWNERS + + The result of the mount operation for Native SMB File Share. This is + recorded after the D-Bus call to Mount returns. + + + + + zentaro@chromium.org + + The number of entries read when calling ReadDirectory. This is recorded + after the D-Bus call to ReadDirectory returns. + + + + + zentaro@chromium.org + + The duration of ReadDirectory call to SmbProvider in milliseconds. This is + recorded after the D-Bus call returns. + + + + + zentaro@chromium.org + + The result of the Remount operation during startup. This is recorded after + the D-Bus call to Remount returns. + + + + + pkasting@chromium.org + robliao@chromium.org + Time required to run ui::NativeTheme::GetSystemColor(). + + + + pkasting@chromium.org + robliao@chromium.org + Records if the color provider computed the color. + + + + bmcquade@chromium.org + + The connection subtype of the network the client is connected to, when the + client is on a cellular connection. This histogram is logged once per UMA + record, if the user is on a cellular connection, at the time the record is + finalized. + + + + + tbansal@chromium.org + bengr@google.com + + The MCC (mobile country code) and MNC (mobile network code) of the network + operator when a new metrics log is created or when the network connection is + changed. A value of zero means a non-mobile network or the operator code is + unknown. + + + + + cclem@chromium.org + better-together-dev@google.com + + If the Nearby Share certificate manager successfully downloads public + certificates, then record the total number of certificates downloaded across + all pages. + + + + + cclem@chromium.org + better-together-dev@google.com + + If the Nearby Share certificate manager fails to download public + certificates, then record the page number of the page on which the failure + occurred. + + + + + cclem@chromium.org + better-together-dev@google.com + + Records the result of the async ListPublicCertificates API call to the + Nearby Sharing server when the certificate manager periodically downloads + public certificates. Recorded when the async callback is invoked or when the + call times out. + + + + + cclem@chromium.org + better-together-dev@google.com + + If the Nearby Share certificate manager successfully downloads public + certificates, then record the number of pages downloaded by the RPC. + + + + + cclem@chromium.org + better-together-dev@google.com + + Records whether the Nearby Share certificate manager successfully downloaded + public certificates from the server and stored them in leveldb. + + + + + cclem@chromium.org + better-together-dev@google.com + + Records the result of the async GetDecryptedPublicCertificate call in + certificate manager. + + + + + cclem@chromium.org + better-together-dev@google.com + + If the Nearby Share certificate storage successfully initializes the public + certificate database, then record the number of attempts it took. + + + + + cclem@chromium.org + better-together-dev@google.com + + For individual initialization attempts of the Nearby Share certificate + storage public certificate database, record the init status returned by + leveldb_proto. + + + + + cclem@chromium.org + better-together-dev@google.com + + Record success rate of Nearby Share storage operation {Operation}. + + + + + + + + + + + + + cclem@chromium.org + better-together-dev@google.com + + Records the result of the async UpdateDevice API call to the Nearby Sharing + server when the device data updater makes a request. Recorded when the async + callback is invoked or when the call times out. + + + + + tsepez@chromium.org + + Count of requests which contained a basic auth username and password + embedded in the URL itself. + + + + + stevenjb@chromium.org + + Number of shared remembered (preferred) networks on Chrome OS. Updated any + time the network list changes. + + + + + stevenjb@chromium.org + + Number of private remembered (preferred) networks on Chrome OS. Updated any + time the network list changes. + + + + + stevenjb@chromium.org + + Number of visible (in-range) networks on Chrome OS. Updated any time the + network list changes. + + + + + tbansal@chromium.org + bengr@chromium.org + + Records if the cached network quality (from memory or from a persistent + source) was available. Recorded right after connection change event. + + + + + tbansal@chromium.org + + Number of buckets by which effective connection type was reduced or capped + due to low cellular signal strength. Recorded only on cellular networks, and + only when the value of the effective connection typed is capped. + + + + + tbansal@chromium.org + bengr@chromium.org + + Whether the signal strength for the cellular network was available or not. + Recorded right before a connection change event. Recorded only on cellular + connections on Android platform. + + + + + rockot@google.com + zhongyi@chromium.org + + When ConnectivityMonitor establishes that the current default network may be + failing and is Wi-Fi, it asks the operating system to activate a mobile + network for subsequent use. Whenever the system's default network changes, + this logs the relationship between the new default network and the network + preemptively activated by ConnectivityMonitor, if any. + + + + + rockot@google.com + zhongyi@chromium.org + + The Network Quality Estimator (NQE) observes network activity to look for + connectivity issues. If it begins to observe failures on a previously + functioning network, it tracks the time at which the failures were first + observed. If the device subsequently switches its default network to + different network (or offline), this histogram logs the number of + milliseconds elapsed since the original failures were observed. + + + + + tbansal@chromium.org + src/net/nqe/OWNERS + + Effective connection type estimated by the network quality estimator. + Recorded every time the effective connection type is computed. + + + + + tbansal@chromium.org + src/net/nqe/OWNERS + + Rough estimate of the computed end-to-end round trip time. Recorded by the + network quality estimator every time the effective connection type is + computed. + + + + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the downstream peak throughput (in kilobits per second). + Recorded by the network quality estimator every time the effective + connection type is computed. + + + + + tbansal@chromium.org + bengr@chromium.org + + Whether the NetworkID (SSID of the Wi-Fi network, or the MCC/MNC operator of + the cellular network) was available or not. Recorded only on Wi-Fi and + cellular networks. Recorded right after the connection type changes. + + + + + tbansal@chromium.org + bengr@chromium.org + + Number of times the network quality prefs were read by the network quality + estimator. + + + + + tbansal@chromium.org + bengr@chromium.org + + Count of the number of network IDs in the prefs read by the network quality + estimator. + + + + + tbansal@chromium.org + bengr@chromium.org + + Number of times the network quality prefs were written by the network + quality estimator. + + + + + tbansal@chromium.org + bengr@chromium.org + + Number of RTT observations indexed by the source of the observation. + Recorded by the network quality estimator every time a new observation is + made or synthesized. + + + + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the round trip time at the URLRequest layer. Recorded by + the network quality estimator every time the effective connection type is + computed. + + + + + tbansal@chromium.org + mcrouse@chromium.org + + Recorded as true when the signal strength of the current network is queried. + + + + + bengr@chromium.org + tbansal@chromium.org + + Rough estimate of the computed round trip time at the transport layer. + Recorded by the network quality estimator every time the effective + connection type is computed. + + + + + tbansal@chromium.org + bengr@chromium.org + + Whether the signal strength for the Wifi network was available or not. + Recorded right before a connection change event. Recorded only on Wifi + connections on Android platform. + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Failure reason of MergeSession call during Chrome OS login, Chrome Signin or + account addition. On all OSes as of M44 (previously CrOS only). + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Retry reason of failed MergeSession call during Chrome OS login, Chrome + Signin or account addition. On all OSes as of M44 (previously CrOS only). + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Outcome of Chrome OS GAIA cookie post-merge session verification process. It + measures how often /MergeSession request collided with browser session + restore process resulting in partially authenticated primary GAIA session. + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Outcome of Chrome OS GAIA cookie pre-merge session verification process. It + measures how often we need to perform /MergeSession request to + re-authenticated exisitng user with GAIA. + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + Outcome of Chrome OS GAIA cookie session restore process. + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + How long it takes for the session restore to fail. + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + How long it takes for the session restore to finish succeessfully. + + + + + davidbienvenu@chromium.org + fdoray@chromium.org + + Incremented each time a mouse event is handled by a window that is marked as + occluded. This number should be 0 or very close to 0. It should be much less + than the number of times a window is mark occluded - + WindowOcclusionChanged.Occluded. + + + + + yiyix@chromium.org + fserb@chromium.org + + Time spent in microseconds to perform call SetFont in canvas for + OffscreenCanvas. It's measured each time SetFont is called. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + chasej@chromium.org + iclelland@chromium.org + feature-control@chromium.org + + Counts the results of token validation checks to enable experimental + features. The result for each token validation check is counted once per + token per execution context (e.g. page, worker). + + + + + cfroussios@chromium.org + mamir@chromium.org + + The backend selected for this user and whether it was initialised + successfully. + + + + + wfh@chromium.org + forshaw@chromium.org + + The Windows GetLastError after a failure from calling into DPAPI to decrypt + the master key for the os_crypt library on Windows. This is recorded during + the OSCrypt::Init each time the decryption fails. + + + + + mark@chromium.org + Events seen by the OSX NSException swizzle. + + + + spqchan@chromium.org + + This event is recorded each time a user triggers fullscreen for a browser + window. It indicates if the fullscreen is triggered for the browser or the + tab content. + + + + + erikchen@chromium.org + + This event is recorded each time a user triggers fullscreen for a browser + window. It indicates the mechanism (immersive vs. AppKit) and the type of + AppKit Fullscreen (Presentation Mode vs. Canonical Fullscreen). + + + + + erikchen@chromium.org + + This event is recorded each time a user triggers fullscreen for a browser + window. It indicates the screen in which the window was fullscreened, and + the number of screens available. + + + + + erikchen@chromium.org + + This event is recorded each time a Handoff is received by Chrome on OSX. The + enumeration indicates the source of the Handoff. + + + + + avi@chromium.org + mark@chromium.org + + The instances of other copies of Google Chrome on the user's Mac. Logged + once on startup, and only for Chrome Beta and Chrome Dev. Will be used to + determine if/how home directory migration will be done for side-by-side. + + + + + lgrey@chromium.org + + Whether the user successfully shared via a native sharing extensions after + selecting it from the share menu. False can indicate failure or + user-initiated cancellation. + + + + + erikchen@chromium.org + + The configuration of the setting "Screens Have Separate Spaces" + available in OSX 10.9+. + + + + + erikchen@chromium.org + + Whether an attempt to load the system hotkeys on a Mac was successful. + + + + + mad@chromium.org + + Counts the number of times the user clicked on the later button of the + outdated upgrade bubble, before clicking on the enable updates button in the + same Chrome session. + + + + + mad@chromium.org + + Counts the number of times the user clicked on the later button of the + outdated upgrade bubble, before clicking on the reinstall button in the same + Chrome session. + + + + + nzolghadr@chromium.org + + Overscroll gestures that were aborted before they were completed. + + + + + nzolghadr@chromium.org + + Navigations that were triggered due to completed overscroll gesture. Note + that not all completed overscroll gestures trigger a navigation. + + + + + nzolghadr@chromium.org + + Overscroll gestures initiated by the user. Note that not all overscroll + gestures started are completed (e.g. the overscroll gesture is aborted if + user clicks or presses a key during the gesture). + + + + + napper@chromium.org + robsc@chromium.org + + When a stylus is touched to screen, the number of palms on the device at + that time. + + + + + napper@chromium.org + robsc@chromium.org + + The time between a finger and a stylus touch. The finger may or may not + still be on the touchscreen. + + + + + napper@chromium.org + robsc@chromium.org + + The time between a palm and a stylus touch. The palm may or may not still be + on the touchscreen. + + + + + robsc@chromium.org + + The count of the number of held events cancelled when we decide to finally + cancel a stroke. Only reported if events have been held, and will be + positive. Events are only held from PalmDetectionFilter. + + + + + robsc@chromium.org + + The count of the number of held events released at once for a stroke when we + decide to release. Only reported if events have been held, and will be + positive. Events are only held from PalmDetectionFilter. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The wall-clock time spent until a lookup was canceled. This is reported + every time p2p is used to find a candidate but the request was canceled. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of candidates on the LAN, i.e. the number of peers on the LAN + offering at least N bytes of the requested file X. This is reported after + examining responses from all peers on the LAN and picking a candidate. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of p2p downloads of the peer that the returned URL points to. + This is reported after examining responses from all peers on the LAN and + picking a candidate. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The wall-clock time spent waiting for the LAN-wide number of p2p downloads + (i.e. the sum of p2p downloads from each peer on the LAN) to drop below the + threshold. This is reported after examining responses from all peers on the + LAN and picking a candidate. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The result of the lookup. Possible values include "Found" (if a + candidate - i.e. a peer offering at least N bytes of file X - was chosen), + "Not Found" (if no candidate could be found), "Vanished" + (if a candidate was found but vanished while waiting in line), + "Canceled" (if a candidate was found but the request was canceled + while waiting in line), and "Filtered" (if it was detected that + mDNS was filtered). This is reported after examining responses from all + peers on the LAN when p2p is used to find a candidate. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of peers implementing p2p file sharing on the network. This is + reported every time p2p is used to look up a resource on a network where + mDNS is not filtered. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The wall-clock time spent waiting for one or more candidates (i.e. peers + offering at least N bytes of file X) that all vanished before the LAN-wide + number of p2p downloads dropped below the threshold. This is reported every + time candidates were found using p2p but then vanished. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of currently connected HTTP clients. This is reported every time + a HTTP client connects. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + Number of megabytes (1,000,000 bytes) served from the device (via HTTP) + where the client disconnects prematurely. This is reported every time a file + is served and the client disconnects before receiving all data. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + Number of megabytes (1,000,000 bytes) served from the device (via HTTP). + This is reported every time a file have been served successfully. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The average speed at which the download was served at, in kB/s. This is + reported every time a file have been served successfully. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of files available via p2p. This is reported every time a file is + added or removed to the /var/cache/p2p directory. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + When a client resumes a download, the HTTP request includes range specifier + to skip the bytes it already has. This metric conveys this as a percentage + of the file size. This is reported every time a file is served, even if the + request does not include a range specifier (in which case 0 is reported). + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The result of the HTTP request. Possible values include "Response + Sent" (the resource was found and the response was successfully sent), + "Response Interrupted" (the resource was found but the client + disconnected), "Malformed" (the request was malformed), "Not + Found" (the request was for a resource that was not found), and + "Index" (the request was for the '/' or '/index.html' resource). + This is reported for every HTTP request handled. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Records the reason that a commit was triggered, to enable research into + which event (non-same-origin, FCP, timeout, etc) led to the first commit. + + + + + schenney@chromium.org + paint-dev@chromium.org + + Records whether or not input arrived before the first commit. + + + + + bttk@chromium.org + wychen@chromium.org + + The number of partner bookmark entries. Logged when using the bookmark, and + at most once per cold start. Note that the distribution is weighted by + bookmark usage. + + + + + tedchoc@chromium.org + wychen@chromium.org + + The response we got back from our favicon fetching throttler, once for each + bookmark at each cold start. Only recorded on Android. + + + + + bttk@chromium.org + wychen@chromium.org + + The time spent on loading partner bookmarks, from kickOffReading() to + bookmarkModelLoaded() callback. + + + + + hnakashima@chromium.org + + Tracks user actions in the PDF viewer. Logged when the document is opened + and when one of the relevant user actions is taken, such as opening the + bookmarks bar or setting the zoom mode to fit-to-page. The enum values that + are named "First" are logged only once per document, so that we + can measure in what percentage of documents a given action was performed at + least once. + + + + + rharrison@chromium.org + thestig@chromium.org + + Tracks what types of forms are present in PDF document, logged when the + document finishes loading. + + + + + hnakashima@chromium.org + thestig@chromium.org + + Measures if PDFs opened in the PDF viewer have attachments. This is logged + whenever a document is opened in the PDF viewer. + + + + + dmazzoni@chromium.org + thestig@chromium.org + + Tracks documents opened in the PDF viewer that are Tagged PDFs. + + + + + thestig@chromium.org + ankk@microsoft.com + mohitb@microsoft.com + virens@microsoft.com + + Records the number of overlapping link and highlight annotations in a PDF + page. This is logged once per page whenever accessibility tree creation is + triggered for that page. It will not be logged on render or scroll + operations. + + + + + kmoon@chromium.org + thestig@chromium.org + + Tracks what happens when Chrome tries to load a PDF. This metric tracks all + cases, but is focused on measuring failed PDF embeds, which occur if the + user is on Android, or if PDF plugin is disabled. + + + + + hnakashima@chromium.org + thestig@chromium.org + + Tracks the number of pages in PDF documents opened in the PDF viewer. + + + + + dhoss@chromium.org + thestig@chromium.org + Tracks versions of documents opened in the PDF viewer. + + + + jbauman@chromium.org + + True if a non-flash Pepper Graphics3D context has a share group. + + + + + bbudge@chromium.org + raymes@chromium.org + + The number of out-of-process plugin processes that have loaded a particular + PPB interface version. + + + + + raymes@chromium.org + rsleevi@chromium.org + + Whether a Pepper TCP connect attempt comes from a plugin in a secure or an + insecure origin. + + + + + raymes@chromium.org + rsleevi@chromium.org + + Whether a Pepper UDP bind attempt comes from a plugin in a secure or an + insecure origin. + + + + + jds@chromium.org + src/chrome/browser/performance_hints/OWNERS + + Records the result of querying PerformanceHintsObserver for a URL-specific + performance hint. This enables tracking how often the + OptimizationGuideDecider provides a hint in time for a HintForURL request. + + + + + jds@chromium.org + src/chrome/browser/performance_hints/OWNERS + + Records the PerformanceClass determined for a given URL. This value + represents the expected loading performance for the URL. This is recorded + before any overrides are performed by the PerformanceHintsObserver. + + + + + jds@chromium.org + src/chrome/browser/performance_hints/OWNERS + + Records the result of a hint lookup in a single source (e.g. link hints of + the current page, the page's OptimizationMetadata, etc). See the + PerformanceHintsSource suffix for name completions. All source suffix + histograms should have the same total count. + + + + + bokan@chromium.org + kouhei@chromium.org + platform-architecture-dev@chromium.org + + Tracks the total number of agents hosted by the browser by time. An entry in + bucket N corresponds to N agents being hosted across all live renderer + process for 1 second. Recorded on state changes and every 5 minutes. + + + + + bokan@chromium.org + kouhei@chromium.org + platform-architecture-dev@chromium.org + + Tracks the number of agents hosted per renderer by time. An entry in bucket + N corresponds to N agents being hosted by a renderer process for 1 second. + Recorded on state changes and every 5 minutes. + + + + + bokan@chromium.org + kouhei@chromium.org + platform-architecture-dev@chromium.org + + Tracks the number of unique agents hosted by the browser by time. An entry + in bucket N corresponds to N unique agents being hosted across all live + renderer process for 1 second. Unique means that the agent count would + remain the same if they were in one process (i.e. they have different + protocol+site). Recorded on state changes and every 5 minutes. + + + + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the types of frames that are being hosted by a process over its + entire lifetime. An entry in the + "AllFramesHaveDistinctSiteInstances" means that the process only + ever hosted frames with distinct site instances over its entire lifetime. + Recorded on state changes and every 5 minutes. + + + + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the types of frames that are being hosted by a process, aggregated + over time. Each entry in each bucket corresponds to a process being in that + state for one second. Recorded on state changes and every 5 minutes. + + + + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the number of frames hosted per renderer by time. An entry in bucket + N corresponds to N frames being hosted by a renderer process for 1 second. + Recorded on state changes and every 5 minutes. + + + + + chrisha@chromium.org + catan-team@chromium.org + + Tracks the number of site instances hosted per renderer by time. An entry in + bucket N corresponds to N site instances being hosted by a renderer process + for 1 second. Recorded on state changes and every 5 minutes. + + + + + pmonette@chromium.org + catan-team@chromium.org + + Records a boolean indicating if a worker's client frame node could be found + when trying to connect the worker to a client frame, given its ID. This is + supposed to be always true if the performance manager has perfect coverage + of WebContents objects. + + + + + oysteine@chromium.org + + Average CPU utilization of a process, read out at each two-minute interval. + The utilization is in the 0-100% range per CPU, which is then summed up. + I.e. a quadcore system fully loaded would read as 400%. + + + + + etienneb@chromium.org + oysteine@chromium.org + + Average disk utilization of a process, recorded at every two-minute + interval. The amount of data transferred (Total I/O bytes per second) for a + given process. + + + + + lgrey@chromium.org + markchang@chromium.org + + (Mac only) A synthetic power use estimate, as displayed in macOS Activity + Monitor and the battery menu. This incorporates CPU utilization, idle + wakeups, IO, and task QoS level using per-machine-model weights. Divide by + 100 to match Activity Monitor's scale. Recorded every two minutes. + + + + + oysteine@chromium.org + + The number of times a process has continuously stayed above a certain + threshold of CPU utilization over a certain time period (currently set to + two minutes). + + + + + lgrey@chromium.org + markchang@chromium.org + + The average CPU idle wakeups per second, sampled every two minutes. + + + + + lgrey@chromium.org + markchang@chromium.org + + (Mac only) The average package exit idle wakeups per second, sampled every + two minutes. This is a subset of wakeups that indicate that the processor + complex was taken out of low-power state. For more info, see the + powermetrics man page on macOS. + + + + + nator@chromium.org + rayankans@chromium.org + + Records the number of `periodicsync` events which were fired in a batch. A + batch is defined as the set of `periodicsync` events dispatched at the same + time by the BackgroundSyncManager. Periodic syncs usually run in a batch. + + + + + nator@chromium.org + rayankans@chromium.org + + Records whether the fired `periodicsync` events upon completion orginated + from a background wakeup task or the foreground. + + + + + nator@chromium.org + rayankans@chromium.org + + Time taken to execute a batch of periodicsync events. A batch is defined as + the set of `periodicsync` events dispatched at the same time by the + BackgroundSyncManager. Periodic syncs often run in a batch. + + + + + + + khorimoto@chromium.org + better-together-dev@google.com + + Indicates the feature state of Phone Hub features. This metric is emitted to + at the creation of the user session (when the user logs in), and when + feature state updates occur. + + + + + fbeaufort@chromium.org + media-dev@chromium.org + + Records Picture-in-Picture window control buttons pressed by user (basically + everything except user tap gestures). + + + + + fbeaufort@chromium.org + media-dev@chromium.org + + Records Picture-in-Picture window control user tap gestures. + + + + + djean@chromium.org + eugenebut@chromium.org + + Page load time for Browser-initiated navigations. Recorded when + CRWWebRequestController::didFinishWithURL completes successfully. iOS + specific. + + + + + djean@chromium.org + eugenebut@chromium.org + + Page load time for Renderer-initiated navigations. Recorded when + CRWWebRequestController::didFinishWithURL completes successfully. iOS + specific. + + + + + Please list the metric's owners. Add more owner tags as needed. + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.RequestToStart. Start: requestStart. Request: + navigationStart. + + + + + Please list the metric's owners. Add more owner tags as needed. + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.StartToCommit. Start: requestStart. Commit: responseStart. + + + + + Please list the metric's owners. Add more owner tags as needed. + + This time is based on the NavigationTiming spec and is a more accurate + version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Time from "request" to "start." "Request"== + time when user requested document. "Start"== time when renderer + requested load of document, after any unload of last document. + + + + + horo@chromium.org + webpackage-dev@chromium.org + + The body size of each prefetched signed exchanges in + PrefetchedSignedExchangeCache which is attached to a frame. Recorded when + the frame is deleted or is navigated to different document. + + + + + horo@chromium.org + webpackage-dev@chromium.org + + The total body size of prefetched signed exchanges in + PrefetchedSignedExchangeCache which is attached to a frame. This metric is + recorded when the frame is deleted or is navigated to different document. + This is not recorded when there is no prefetched signed exchanges. + + + + + horo@chromium.org + webpackage-dev@chromium.org + + The number of prefetched signed exchanges in PrefetchedSignedExchangeCache + which is attached to a frame. This metric is recorded when the frame is + deleted or is navigated to different document. This is not recorded when + there is no prefetched signed exchanges. + + + + + horo@chromium.org + webpackage-dev@chromium.org + + The total headers size of prefetched signed exchanges including outer + response headers and inner response headers in PrefetchedSignedExchangeCache + which is attached to a frame. This metric is recorded when the frame is + deleted or is navigated to different document. This is not recorded when + there is no prefetched signed exchanges. + + + + + holte@chromium.org + The status when loading PersistedLogs from Prefs. + + + + csharp@chromium.org + + Enumeration of errors that happened when reading Preferences files. + + + + + ryansturm@chromium.org + tbansal@chromium.org + + Final status for prerender pages - either success, or why it was canceled. + + + + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents + deletion. Includes prerender bytes. Bytes are only counted when prerendering + is enabled and not in a control group. The sum of the distribution for a + single user represents all of that user's network transfers for resource for + that time period while prerendering was enabled. + + + + + hajimehoshi@chromium.org + jkarlin@chromium.org + kouhei@chromium.org + + Number of bytes transferred on the network for URLRequests (not including + HTTP/TLS/TCP/IP overhead) for a prerender that was not used. All + nostate-prefetch bytes are currently counted as wasted because it is hard to + track byte use in HTTP cache. + + + + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Length of the redirect chain for main resources loaded by NoStatePrefetch. + Recorded when the final response in the chain is received. + + + + + jam@chromium.org + + Time a prefetch renderer is kept alive after parsing to wait for + subresources to finish loading. + + + + + jam@chromium.org + + Time between prefetch renderer startup and when parsing is complete. + + + + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Type of responses received by NoStatePrefetch, distinguishing cacheable + resources from no-store resources, and main resources from sub-resources. + Recorded when a response is received, including on each redirect. + + + + + droger@chromium.org + mattcary@chromium.org + pasko@chromium.org + + Length of the redirect chain for sub-resources loaded by NoStatePrefetch. + Recorded when the final response in the chain is received. + + + + + gambard@chromium.org + justincohen@chromium.org + + Whether the load was completed when the pre-render was used. If the + prerender is cancelled, this is not logged. Only on iOS. + + + + + justincohen@chromium.org + + Whether or not a successful prerender happens on a NTP with no history. + + + + + justincohen@chromium.org + + The last comitted index before a successful preload is committed. Recorded + only on iOS. + + + + + ryansturm@chromium.org + tbansal@chromium.org + + The number of sessions that have at least X successful prerenders. Recorded + only on iOS since 2017-09. + + + + + gambard@chromium.org + justincohen@chromium.org + + This is the time from when a prerendered page begins to load to when it is + swapped in as the main page load or to when the pre-loaded page is fully + loaded, whichever came first. Recorded when the swap occurs, only on iOS. + + + + + pasko@chromium.org + + A boolean that indicates how often we fail to delete an old prerendered tab + before the timeout. + + + + + dougarnett@chromium.org + mcrouse@chromium.org + src/components/data_reduction_proxy/OWNERS + + Blocked previews due to Cache-Control:no-transform directive. + + + + + ryansturm@chromium.org + + The actual data used for a page load using a preview optimization. + + + + + ryansturm@chromium.org + + The estimated amount that the content was inflated for a page load using a + previews optimization. Recorded when a page load using a previews + optimization inflates the data used. + + + + + ryansturm@chromium.org + + The estimated percent of data used that a page load would have otherwise + cost for a page load using a previews optimization. Recorded when a page + load using a previews optimization inflates the data used. + + + + + ryansturm@chromium.org + + The estimated data savings for a page load using a previews optimization. + Recorded when a page load using a previews optimization reduces the data + used. + + + + + ryansturm@chromium.org + + The estimated percent of data savings for a page load using a previews + optimization. Recorded when a page load using a previews optimization + reduces the data used. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + Records true when a URL matches the regex of denylist. Recorded at the time + of navigation commit. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + Records true when a redirect loop is detected when defer all script is in + use. Recorded at the time of navigation commit. + + + + + ryansturm@chromium.org + + When evaluating whether to show a user a preview, the preview might be + disallowed for various reasons. If the preview is disallowed, then this + reports the reason for disallowing it. If the preview is allowed, then this + generally reports "Previews Allowed". It may instead report + "Previews Allowed without server rule check" for a preview that + expects to check server rules but they are not enabled. Recorded throughout + navigation at the beginning of each navigation, after each redirect, and + during commit. + + + + + robertogden@chromium.org + src/components/data_reduction_proxy/OWNERS + + User interactions with the HTTPS Server Previews notification InfoBar. + + + + + robertogden@chromium.org + User interactions with the Previews Android Omnibox UI. + + + + ryansturm@chromium.org + + Whether the user chose to reload the original page when shown a preview. + + + + + ryansturm@chromium.org + + The estimated content length of a page load using a preview optimization. + + + + + robertogden@chromium.org + Records why the page load ended on a given preview type. + + + + dougarnett@chromium.org + mcrouse@chromium.org + src/components/data_reduction_proxy/OWNERS + + Records the effective connection type of a navigation that triggers a + preview. This is captured at commit time but uses the effective connection + type from the beginning of the navigation. + + + + + msramek@chromium.org + sauski@google.com + + The number of unique cookie domains for which accesses has been recorded for + in the Access Context Audit database. Logged on initialization of the Access + Context Audit DB on 1% of starts. + + + + + msramek@chromium.org + sauski@google.com + + Size of the Access Context Audit database file in KiB. Determined by + directly inspecting the database file. Logged on initialization of the + Access Context Audit DB on 1% of starts. + + + + + msramek@chromium.org + sauski@google.com + + The total number of access records stored in the Access Context Audit + database. Logged on initialization of the Acceess Context Audit DB on 1% of + starts. + + + + + msramek@chromium.org + sauski@google.com + + The number of unique origins associated with origin keyed storage APIs + recorded in the Access Context Audit database. Logged on initialization of + the Access Context Audit DB on 1% of starts. + + + + + msramek@chromium.org + sauski@google.com + + The number of unique top frame origins for which access to storage APIs has + been recorded in the Access Context Audit database. Logged on initialization + of the Acceess Context Audit DB on 1% of starts. + + + + + markusheintz@google.com + msramek@google.com + + Logged each time the user grants a consent for a feature integrated with the + consent auditor. The value indicates which feature. + + + + + markusheintz@google.com + msramek@google.com + + Logged each time the user denies or revokes a consent for a feature + integrated with the consent auditor. The value indicates which feature. + + + + + dullweber@chromium.org + huanzhong@chromium.org + + Whether the cookie controls setting is enabled. Recorded at the Profile + startup. + + + + + mkwst@chromium.org + msramek@chromium.org + + Whether the Do Not Track setting is enabled. Recorded at the Profile + startup. + + + + + dullweber@chromium.org + huanzhong@chromium.org + + Records whether third party cookie blocking was enabled for a site on page + load. Only recorded for users who enabled the cookie controls ui. + + + + + + + mkwst@chromium.org + msramek@chromium.org + dullweber@chromium.org + + Whether the third party cookie blocking setting is enabled. Recorded at the + Profile startup. + + Previously recorded as the "ThirdPartyCookieBlockingEnabled" and + "ThirdPartyCookieBlockingDisabled" actions. + + + + + forshaw@chromium.org + wfh@chromium.org + + Errors returned while launching sandboxed process on Windows. For decoding + error code please refer to http://goo.gl/fJJiAv. + + + + + forshaw@chromium.org + wfh@chromium.org + + Warnings returned while launching sandboxed process on Windows. For decoding + error code please refer to http://goo.gl/fJJiAv. This will only be logged + when SpawnTarget succeeds with SBOX_ALL_OK but the last warning result does + not equal SBOX_ALL_OK. + + + + + forshaw@chromium.org + wfh@chromium.org + + The warning launch error returned while launching sandboxed process on + Windows. This will only be logged when SpawnTarget succeeds with SBOX_ALL_OK + but the last warning result does not equal SBOX_ALL_OK. + + + + + shrikant@chromium.org + + Errors returned while launching lowbox enabled sandboxed process on Windows. + For decoding error code please refer to http://goo.gl/fJJiAv. + + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB Destroy call was successful or not. + + + + nyquist@chromium.org + ssid@chromium.org + + The LevelDB Status returned from a failed ProtoDatabase Get call. + + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB Get call found what was requested. + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB Get call was successful or not. + + + + nyquist@chromium.org + ssid@chromium.org + The LevelDB Status from a ProtoDatabase Init call. + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB LoadEntries call was successful or not. + + + + nyquist@chromium.org + ssid@chromium.org + + Whether a ProtoDB LoadKeysAndEntries call was successful or not. + + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB LoadKeys call was successful or not. + + + + ssid@chromium.org + salg@chromium.org + + Tracks the init state progress of a proto database. An enum value is + recorded for each state of progression through the initialization process. + Shows the number of users hitting each stage. The enum values starting with + success and failure indicate that the final output of initialization is a + success or failure. See + //components/leveldb_proto/internal/proto_init_state_description.md. + + + + + nyquist@chromium.org + ssid@chromium.org + + The LevelDB Status returned from a failed Protodatabase UpdateEntries call. + + + + + nyquist@chromium.org + ssid@chromium.org + Whether a ProtoDB UpdateEntries call was successful or not. + + + + hansberry@chromium.org + + Provides a breakdown of how often each BLE weave connection result occurs. + + + + + hansberry@chromium.org + + Provides a breakdown of how many times each possible Bluetooth GATT + connection result occurs. + + The bucket "Unknown result" indicates that the Bluetooth platform + returned an unknown error code; if it has any counts, the client code should + be changed to account for the new error code. + + + + + hansberry@chromium.org + + Provides a breakdown of how many times each possible Bluetooth GATT + "notify session" attempt result occurs. + + The bucket "Unknown result" indicates that the Bluetooth platform + returned an unknown error code; if it has any counts, the client code should + be changed to account for the new error code. + + + + + hansberry@chromium.org + + Provides a breakdown of how many times each possible Bluetooth GATT + "write characteristic" attempt result occurs. + + + + + rdevlin.cronin@chromium.org + + The action taken by the user when the "proxy overridden" extension + warning bubble is shown. Logged immediately after the action is taken. + + + + + + + tasak@google.com + + The growth of the background renderer's memory usage after a background + renderer is purged. This is recorded 5, 10 and 15 minutes after the purge. + + + + + tasak@google.com + + Time elapsed from when the backgrounded and purged renderer is foregrounded + until the renderer is painted. This is recorded every time the backgrounded + and purged renderer is foregrounded. + + + + + tasak@google.com + + Time elapsed from when the renderer, which is kept backgrounded for more + than 5 minutes, is foregrounded until the renderer is painted. This is + recorded every time such renderer is foregrounded. + + + + + peter@chromium.org + + Whenever a Service Worker receives a push message, this records the budget + available to the service worker, which is an internal Chrome value for the + amount of background processing a service worker is allowed to do without + visibly alerting the user. Scale for the budget is 0 to 100. + + + + + peter@chromium.org + + When a Service Worker receives a push message, this records whether the + overall operation was successful, or otherwise the type of error + encountered. + + + + + peter@chromium.org + + When attempting to deliver a push message to a Service Worker, this records + the result of finding the Service Worker registration given its ID and + origin. + + + + + peter@chromium.org + + When a Service Worker receives a push message, this records the precise + result received from the Service Worker code. + + + + + peter@chromium.org + + When a webpage asks for details about its current push messaging + registration, this records whether the request is successful, or otherwise + the type of error encountered. + + + + + peter@chromium.org + rayankans@chromium.org + knollr@chromium.org + viviy@google.com + + When a Service Worker receives a pushsubscriptionchange event, this records + whether the overall operation was successful, or otherwise the type of error + encountered. + + + + + peter@chromium.org + knollr@chromium.org + + Whenever a Service Worker receives a push message, this records whether + Chrome is completely running in the background. A successful report means + that the message was received when Chrome was in complete background mode, + without UI, while a failure means it was in some other state: in background + with some apps running, showing browser windows, etc. + + + + + peter@chromium.org + knollr@chromium.org + + When a webpage registers for push messaging, this records whether the + request is successful, or otherwise the type of error encountered. + + + + + peter@chromium.org + + When a Service Worker hits low budget when servicing a push message, this + records what the Site Engagement Service score is at that time. + + + + + peter@chromium.org + + When a Service Worker hits zero budget when servicing a push message, this + records what the Site Engagement Service score is at that time. + + + + + peter@chromium.org + knollr@chromium.org + + When a message arrives for a lazy subscription and Chrome isn't in the + foreground, it is persisted on disk until next time Chrome is in the + foreground. This histogram measures the time spent in reading and replaying + persisted messages when Chrome goes to the foreground. + + + + + peter@chromium.org + + When unregistering a legacy non-InstanceID push messaging subscription, this + records the result returned by the GCMDriver (note that exceeding the + maximum number of retries due to network errors is logged as SERVER_ERROR). + + + + + peter@chromium.org + knollr@chromium.org + + When unregistering an InstanceID push messaging subscription, this records + the result returned from deleting the InstanceID (note that exceeding the + maximum number of retries due to network errors is logged as SERVER_ERROR). + + + + + peter@chromium.org + + When unregistering a website from push messaging, this records the reason + why it is being unregistered. + + + + + peter@chromium.org + + When unregistering a website from push messaging, this records whether the + request is successful, or otherwise the type of error encountered. + + + + + peter@chromium.org + + When a Service Worker receives a push message, this records whether it + showed user-visible UX (like a notification), or whether we showed a forced + notification on its behalf. + + + + + knollr@chromium.org + peter@chromium.org + + Records the number of visible notifications for a Service Worker when it + receives a push message. Counted and recorded after handling the push event. + + + + + llin@google.com + croissant-eng@chromium.org + + For quick answer impression that fulfills a user's intent, records the + result type. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For quick answer impression that fulfills a user's intent, records the + impression duration. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answer click event, records the result type. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answer click event, records the duration between fetch + finish and user clicks. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answers consent impression, records how many times the user + has seen the consent. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answers consent interaction event, records how long the user + has seen the consent before. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answers consent interaction event, records how many times + the user has seen the consent before. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For quick answer fetch, records the intent generated on-device. ChromeOS + only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answers fetch, records the duration between fetch start and + fetch finish. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answers fetch, records the result status. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answer result received event, records the result type. + ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answer result received event, records the duration between + fetch start and fetch finish. ChromeOS only. + + + + + llin@google.com + croissant-eng@chromium.org + + For every quick answer request, records the length of the selected text that + is being considered for fetching quick answers. ChromeOS only. + + + + + holte@chromium.org + Counts how often daily interval events were fired. + + + + holte@chromium.org + + For each Rappor log that is discarded, the reason that it was discarded. + + + + + holte@chromium.org + Net error codes for failed Rappor uploads. + + + + holte@chromium.org + + Success or errors encountered when loading Rappor cohort pref. + + + + + holte@chromium.org + + Success or errors encountered when loading Rappor secret pref. + + + + + holte@chromium.org + + For each upload to the Rappor server, log the response received from the + server. + + + + + gambard@chromium.org + bling-team@google.com + + The action chosen by the user after displaying the reading list context + menu. + + + + + gambard@chromium.org + bling-team@google.com + + Number of tries before the download of the entry is successful. + + + + + gambard@chromium.org + bling-team@google.com + Final status of the download of a reading list entry. + + + + gambard@chromium.org + bling-team@google.com + + Time since the first read of the reading list entry getting deleted. 0 if it + has never been read. + + + + + gambard@chromium.org + bling-team@google.com + Whether the displayed version is the offline one. + + + + gambard@chromium.org + bling-team@google.com + + Time since the creation of the read reading list entry getting deleted. + + + + + gambard@chromium.org + bling-team@google.com + Number of read entries in reading list. + + + + gambard@chromium.org + bling-team@google.com + + Time since the creation of the unread reading list entry getting deleted. + + + + + gambard@chromium.org + bling-team@google.com + Number of unread entries in reading list. + + + + robertshield@chromium.org + Log each stage of a recovery component event. + + + + + + tby@chromium.org + charleszhao@chromium.org + + Records situations that can occur during the configuration and + initialization of a RecurrenceRanker. + + + + + + + tby@chromium.org + charleszhao@chromium.org + + Whether the conversion of a JSON config for a RecurrenceRanker succeeded for + failed. + + + + + + + tby@chromium.org + charleszhao@chromium.org + + Reports the result of a save or load of a RecurrenceRanker model. + + + + + + + tby@chromium.org + charleszhao@chromium.org + + Reports when the functions of a RecurrenceRanker model are used. + + + + + grt@chromium.org + + The result of an attempt to show a relaunch notification dialog. + + + + + engedy@chromium.org + + For each load and dropped Mojo interface request in a frame, records a + sample with a value corresponding to the hash of the interface name, + calculated as the lower 31 bits of the interface name's metric name hash. + + Interface requests to RenderFrame::GetRemoteInterfaces are dropped when they + arrive to the RenderFrameHostImpl after the RenderFrameHostImpl had already + committed the next cross-document navigation. + + This means that |document_scoped_interface_provider_binding_| was already + unbound at the time from the interface connection that had been used to + service RenderFrame::GetRemoteInterface for the previous load, so those + interface requests are dropped. + + + + + engedy@chromium.org + + For each load in a frame, records the number of interface requests to + RenderFrame::GetRemoteInterfaces that arrived to the RenderFrameHostImpl + after the RFHI had already committed the next cross-document navigation. + + This means that |document_scoped_interface_provider_binding_| was already + unbound at the time from the interface connection that had been used to + service RenderFrame::GetRemoteInterface for the previous load, so those + interface requests are dropped. This histogram measures how often, if at + all, that happens in practice. + + + + + ccameron@chromium.org + etienneb@chromium.org + + Time retrieve the fallback fonts on the system used for + RenderTextHarfBuzz::ShapeRuns. This metric is known to be quite slow on bad + cases. + + + + + ccameron@chromium.org + etienneb@chromium.org + + Time retrieve the preferred fallback font on the system used for + RenderTextHarfBuzz::ShapeRuns. Fallback font is determined based on the + input text and locale. + + + + + ccameron@chromium.org + etienneb@chromium.org + + This metric records the fallback font mechanism required to complete the + shaping of a text. + + + + + ccameron@chromium.org + etienneb@chromium.org + + Time to perform RenderTextHarfBuzz::ShapeRuns with retrieved the fallback + fonts. This metric is known to be quite slow on bad cases. + + + + + avi@chromium.org + mpearson@chromium.org + Count of renderer view context menu items shown. + + + + + + avi@chromium.org + mpearson@chromium.org + chrome-analysis-team@google.com + + Count of renderer view context menu items (Only commands now) used. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + chlily@chromium.org + sburnett@chromium.org + + The outcome of updating the backing store. This is recorded whenever a batch + of pending operations is committed to the backing store. Success occurs when + all operations are committed successfully. Trouble is recorded when some + operations are unsuccessful but committing the batch succeeds. Failure is + recorded when the commit fails. + + + + + chlily@chromium.org + sburnett@chromium.org + + Records the detection of a corrupted meta table for the Reporting and NEL + DB. This is recorded when database migration fails to update the database to + the current version. + + + + + chlily@chromium.org + sburnett@chromium.org + + Records a failure to recover a corrupted meta table for the Reporting and + NEL DB. This is recorded when a corrupt meta table is detected (see + ReportingAndNEL.CorruptMetaTable), and attempting to recover by deleting and + reinitializing the database fails. + + + + + chlily@chromium.org + sburnett@chromium.org + + The outcome of initializing the SQLite database. This is recorded upon the + first load request after startup, which will typically occur upon the first + network request. + + + + + chlily@chromium.org + sburnett@chromium.org + + Whether killing the database because it was corrupted beyond repair + succeeded. This is recorded when a fatal SQLite error is detected. + + + + + chlily@chromium.org + sburnett@chromium.org + + The number of NEL policies loaded from the store. This is recorded when the + NetworkErrorLoggingService requests a load from the backing store, which + typically happens upon the first network request after startup. + + + + + chlily@chromium.org + sburnett@chromium.org + + The number of Reporting endpoint groups loaded from the store. This is + recorded when the ReportingCache requests a load from the backing store, + which happens upon receipt of the first Report-To header or queued report + after startup. + + + + + chlily@chromium.org + sburnett@chromium.org + + The number of Reporting endpoints loaded from the store. This is recorded + when the ReportingCache requests a load from the backing store, which + happens upon receipt of the first Report-To header or queued report after + startup. + + + + + chlily@chromium.org + sburnett@chromium.org + + The time (ms) taken to initialize the Reporting and NEL DB. This is recorded + when the DB is initialized, which typically occurs upon the first network + request after startup. + + + + + merkulova@chromium.org + + Records the number of times the factory reset dialog was shown. Grouped by + the viewtype. + + + + + tbansal@chromium.org + + Records if the loading of a resource was blocked because the resource URL + matched the resource loading hints. Recorded every time a resource load is + requested. + + + + + tbansal@chromium.org + + Records the resource load priority of a resource when its loading is not + blocked due to the resource loading hints. Recorded every time a resource + load is requested, and the load is not blocked due to the resource loading + hints. + + + + + tbansal@chromium.org + + Records the resource load priority of a resource when its loading is blocked + due to the resource loading hints. Recorded every time a resource load is + requested and the resource load is blocked because the resource URL matched + the resource loading hints. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + Records if the resource patterns were available at the time of page commit + if the committed previews type was RESOURCE_LOADING_HINTS and the navigation + was redirected. This is a subset of the ResourcePatternsAvailableAtCommit + histogram. + + + + + tbansal@chromium.org + + The number of active resource scheduler clients indicates the severity of + system contention. A client is active when it has at least one request + either in the pending request queue owned by the client or in flight. This + is emitted when a new resource scheduler client is created. + + + + + tbansal@chromium.org + + The amount of time the ResourceScheduler queued a browser initiated request + that was expected to be heavy (i.e., has large request/response sizes). + Recorded when the request is dispatched by the resource scheduler to the + network stack. Recorded only when the traffic annotation tag of the request + is present in the set of annotation tags that can be throttled. + + + + + tbansal@chromium.org + + Records how long after the start of a delayable resource request, a + non-delayable resource request arrived. This is the duration of time that + the delayable request should have been queued for so as to avoid any network + contetion with later-arriving non-delayable requests. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + The duration of time between the end of a non-delayable resource request to + the start of the next non-delayable resource request. Recorded at the start + of all non-delayable requests that are preceeded by at least one completed + non-delayable request in the same resource scheduler client. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + The duration of time between the end of a non-delayable resource request to + the start of the next non-delayable resource request. Recorded at the start + of all non-delayable requests that are preceeded by at least one completed + non-delayable request in the same resource scheduler client. Recorded only + when a non-delayable request is NOT in-flight. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + The duration of time between the start of a non-delayable resource request + or end of a non-delayable request (whichever happened later) to the start of + the next non-delayable resource request. Recorded at the start of all + non-delayable requests that are preceeded by at least one started + non-delayable request in the same resource scheduler client. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + The duration of time between the start of a non-delayable resource request + to the start of the next non-delayable resource request. Recorded at the + start of all non-delayable requests that are preceeded by at least one + started non-delayable request in the same resource scheduler client. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + The duration of time between the start of a non-delayable resource request + to the start of the next non-delayable resource request. Recorded at the + start of all non-delayable requests that are preceeded by at least one + started non-delayable request in the same resource scheduler client. + Recorded only when a delayable request is in-flight. + + + + + tbansal@chromium.org + + Records the number of delayable requests in-flight when a non-delayable + request is started. + + + + + csharrison@chromium.org + + The number of LoadAnyStartablePendingRequests scans that were skipped due to + smarter task scheduling around reprioritization. + + + + + tbansal@chromium.org + + Records the highest number of delayable requests that were in-flight when + the given request with higher priority was in-flight. + + + + + tbansal@chromium.org + dougarnett@chromium.org + + Within a request's lifetime, the peak observed queueing delay tells whether + the request was affected by the network congestion. Records the maximum + network queueing delay when the given request was in-flight. This is emitted + when the request is completed. + + + + + tbansal@chromium.org + + The amount of time the ResourceScheduler queued a request. Recorded in + separate histograms based on the request loading priority at the time the + request was dequeued. + + + + + jfwang@chromium.org + tbansal@chromium.org + + Records the count of number of requests in-flight. Recorded when a request + is started by the resource scheduler. + + + + + wzang@chromium.org + + Record if updating |should_send_rlz_ping| in RW_VPD is successful within the + maximum retry counts. + + + + + mpolzer@google.com + managed-platforms@google.com + + The result when attempting to restore data during a Chrome OS rollback. + + + + + mpolzer@google.com + managed-platforms@google.com + + The result when attempting to save data during a Chrome OS rollback. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records results of SafeBrowsing download check, including both url check and + downloaded file hash check. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + The time it takes for SafeBrowsing to check a download url. + + + + vakh@google.com + + Response or error codes from the SafeBrowsing service. Logged after a + GetHash request finishes to capture the response code or error code for that + call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49. + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user navigating away by for example, closing the tab, clicking the browser + back button or typing another URL in the address bar. + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user expanding the "see more info" section of the page. (Only + applies to field trial version 2 of the interstitial.) + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user clicking on the learn more link. + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user clicking on the proceed link. + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user clicking on the report error link. + + + + + felt@chromium.org + + The time between when we show the SafeBrowsing phishing interstitial and the + user clicking on the big green back button. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Count of how many URLs were actually checked vs skipped via + RemoteSafeBrowsingDatabaseManager because the scheme is not supported by + Safe Browsing. Incremented each time a resource load is initiated. + + + + + vakh@chromium.org + csharrison@chromium.org + chrome-safebrowsing-alerts@google.com + + The microseconds between sending the Safe Browsing API call and receiving + the response. Logged in java code and does not include any thread hops or + extra work. Note that this does include task queue time to respond to the + IPC (and that queue time is often non-trivial). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Latency of URL-classification API calls from Chrome via + RemoteSafeBrowsingDatabaseManager, logged per-request. This includes the + time to go through JNI, check the URL, and return the result and includes + several thread hops betwetween IO and UI threads. The resource-load will not + necessarily be delayed this much (see SB2.Delay for that). + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The status code provided by GmsCore if it is unable to respond to a URL + check request due to incorrect initialization, not being ready, etc. Logged + on each URL check that hits the internal error condition. The total number + of these should add up to the INTERNAL_ERROR reports under + SB2.RemoteCall.Result. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Result of URL-classification API calls from Chrome via + RemoteSafeBrowsingApiHandler. Logged after each URL is judged safe/not-safe, + or hits a deadline. The INTERNAL_ERROR cases are further classified under + SB2.RemoteCall.InternalErrorStatusCode. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The threat sub-type annotated for URLs classified as PHA via remote calls + through RemoteSafeBrowsingApiHandler. "PHA" classifications + generate "malware" interstitials. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The threat sub-type annotated returned for URLs classified as social + engineering via remote calls through RemoteSafeBrowsingApiHandler. + "Social engineering" classifications generate "phishing" + interstitials. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Resource types of resources that were inspected by Safe Browsing in the + SafeBrowsingResourceThrottle. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes for the TwoPhaseUploader to complete. This is logged on + every upload. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident discarded by the safe browsing incident reporting + service as a result of profile or service destruction. + + + + + caitkp@chromium.org + The result of deleting a profile's download metadata file. + + + + caitkp@chromium.org + The result of reading a profile's download metadata file. + + + + caitkp@chromium.org + The result of writing a profile's download metadata file. + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident given to the safe browsing incident reporting service + but dropped as a result of not participating in safe browsing. + + + + + caitkp@google.com + + The elapsed time to collect environmental data for a safe browsing incident + report. + + + + + caitkp@google.com + + The elapsed time to find the most recent binary download from all loaded + profiles when creating a safe browsing incident report. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident included in an incident report by the safe browsing + incident reporting service. + + + + + caitkp@google.com + + The elapsed time between two successive incidents collated into the same + incident report by the safe browsing incident reporting service. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident pruned by the safe browsing incident reporting service + as a result of not having a matching binary download. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident pruned from a report in the safe browsing incident + reporting service as a result of having previously been reported. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The type of incident received by the safe browsing incident reporting + service. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + The size, in bytes, of a safe browsing incident report. + + + + caitkp@google.com + + The result of an attempted report upload by the safe browsing incident + reporting service. + + + + + caitkp@google.com + + The elapsed time to verify the binary integrity of chrome.exe. + + + + + caitkp@google.com + + The elapsed time to verify the binary integrity of chrome.dll. + + + + + caitkp@google.com + + The elapsed time to verify the binary integrity of chrome_child.dll. + + + + + caitkp@google.com + + The elapsed time to verify the binary integrity of chrome_elf.dll. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Measures the total duration (including delay due to retries) of a failed + upload request. This is recorded after the last retry on every failed + upload. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The HTTP response code or net error from each upload attempt. This is + recorded once for each network request made as part of an upload, i.e. if an + upload fails the first time, but a retry succeeds, this metric is recorded + twice. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts how many retries were needed to complete the upload request. This is + emitted for every successful upload. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Measures the total duration (including delay due to retries) of a successful + upload request. This is recorded for every successful upload. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The size of the upload request body. This is a combination of the upload + data and metadata. This is recorded once for each upload, regardless of + whether it was successful. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the overall upload request succeeded or not. This is recorded once + for an upload request, regardless of how many retries were needed to + complete the upload. + + + + + + + wez@chromium.org + scheduler-dev@chromium.org + + Time taken for a task posted to a CancelableTaskTracker to run. Durations + are not recorded for tasks skipped due to having been canceled. + + + + + wez@chromium.org + scheduler-dev@chromium.org + + Records whether a task posted to CancelableTaskTracker was canceled before + it got the chance to run, and whether it was same-sequence or off-sequence. + Recorded for every task posted via CancelableTaskTracker, immediately before + it would be run. + + + + + + + kdillon@chromium.org + shaseley@chromium.org + + Queueing time of a task posted via the postTask API. Reported when the task + is starts and bycked by priority. Tasks who have had their priority changed + are skipped. + + + + + kdillon@chromium.org + shaseley@chromium.org + + Records whether or not a task posted via scheduler.postTask had it's + priority changed. Records when the task is started. + + + + + altimin@chromium.org + + Total wall time of all tasks in scheduler-managed threads split per thread. + + The bucket value is the sum of thread durations of all tasks in this thread + across all browsing instances. This metric is reported each time we execute + a task which has cpu time measurement. + + + + + altimin@chromium.org + + Total cpu time of scheduler-managed threads in the renderer process. + + It is supposed that Scheduler.Experimental.Renderer.CPUTimePerThread.Tracked + and Scheduler.Experimental.Renderer.CPUTimePerThread.Untracked histograms + should be analysed together. + + The bucket value is the sum of thread durations of all tasks in this thread + across all browsing instances. This metric is reported each time we execute + a task. Due to thread time being expensive to measure, only 0.01% of threads + report this metric. + + + + + altimin@chromium.org + + Sum of durations of all scheduler-managed tasks in the renderer process. + + Due to implementation constraints a difference between .Positive and + .Negative subhistograms should be analysed. See + blink::scheduler::TotalDurationMetricReporter for details. + + These metrics are updated each time a new task is executed. + + + + + altimin@chromium.org + + The results of the attempts to sample scheduling tasks into the UKM. Used to + ensure that we're not silently dropping tasks, which can lead to biases in + our analyses. + + Recorded each time a scheduling task UKM is recorded. + + + + + altimin@chromium.org + + Total wall time of all tasks in scheduler-managed threads split per thread. + + The bucket value is the sum of thread durations of all tasks in this thread + across all browsing instances. This metric is reported each time we execute + a task which has wall time measurement. + + + + + stanisc@chromium.org + + The time from v-sync to when the main side actually starts the + BeginImplFrame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes for the compositor to rasterize pending tree content after + a commit before it is ready for activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes the compositor to draw a frame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes for the compositor to rasterize pending tree content after + an impl-side invalidation before it is ready for activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes the compositor to PreapreTiles, which determines what + rasterization work to do. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes for the main side to start the BeginMainFrame in response + to the compositor's SendBeginMainFrame when the on_critical_path flag is not + set. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + + vmiura@chromium.org + sadrul@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for + the solution. + + + + + xidachen@chromium.org + animations-dev@chromium.org + + The time delta between the draw times of back-to-back BeginImplFrames, + regardless of whether or not they result in a swap, when there is at least + one custom property animation. + + The interval is only recorded when every BeginImplFrame wants to draw. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + khushalsagar@chromium.org + + Time between starting raster work on the pending tree and when it is ready + to activate. Unlike PendingTreeDuration which - includes the time to commit + to this tree, the raster duration and the time for which the pending tree + waits before it can be activated - this only measures the time taken to + rasterize tiles required for activation. + + The interval is recorded each time we are notifed that a pending tree is + ready for activation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vmiura@chromium.org + sadrul@chromium.org + + How long it takes the swap ack to return after a swap. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + antrim@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + ultrotter@chromium.org + + What type of authentication was attempted when the user failed to unlock the + lock screen. + + + + + antrim@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + ultrotter@chromium.org + The time spent for authentication in case of a failure. + + + + antrim@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + ultrotter@chromium.org + + What type of authentication was attempted when the user successfully + unlocked the lock screen. + + + + + antrim@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + ultrotter@chromium.org + The time spent for authentication in case of a success. + + + + antrim@chromium.org + jessejames@chromium.org + rsorokin@chromium.org + ultrotter@chromium.org + The time spent before the screen locker is ready. + + + + jeffreycohen@chromium.org + tgupta@chromium.org + Tracks the user flow for sending a tab for SendTabToSelf. + + + + jeffreycohen@chromium.org + sebsg@chromium.org + tgupta@chromium.org + + Record whether the user has clicked the item when it is shown. + + + + + alemate@chromium.org + + Records result of fetching and parsing OEM customization manifest. See + ServicesCustomizationDocument class for more info. Used only on Chrome OS. + + + + + hanxi@chromium.org + yfriedman@chromium.org + hnakashima@chromium.org + mheikal@chromium.org + + Histogram of how Chrome is launched, either in ServiceManager only mode or + as full browser, as well as either cold start or warm start. See + go/servicification_startup_metrics for more details. + + + + + hanxi@chromium.org + yfriedman@chromium.org + hnakashima@chromium.org + mheikal@chromium.org + + Histogram of how Chrome is launched, either in ServiceManager only mode or + as full browser, as well as either cold start or warm start. See + go/servicification_startup_metrics for more details. The UMA data is cached + in the SharedPreference compared with Servicification.Startup2, which might + lose some data when Chrome is running in the ServiceManager only mode. + + + + + forshaw@chromium.org + + True if the the installer successfully added AppContainer ACEs to the + application directory during installation and updating. + + + + + etiennep@chromium.org + grt@chromium.org + + The cumulative disk usage in MB during install or uninstall attempt, + recorded right after the install/uninstall attempt on windows only. + + + + + grt@chromium.org + src/chrome/installer/OWNERS + + Hit following a successful install or update when the legacy "app + launcher" Clients key is deleted from the registry. + + + + + grt@chromium.org + src/chrome/installer/OWNERS + + Hit following a successful install or update when the legacy + "binaries" Clients key is deleted from the registry. + + + + + grt@chromium.org + src/chrome/installer/OWNERS + + Hit following a successful install or update when the COM registration for + the legacy "IExecuteCommand" implementation class key is deleted + from the registry. + + + + + grt@chromium.org + src/chrome/installer/OWNERS + + Hit following a successful install or update when the legacy + "install-extension" app command is deleted from the registry. + + + + + zmin@chromium.org + grt@chromium.org + Record the status of unpacking the contents of a 7z file. + + + + huangs@chromium.org + + The peak page file usage by setup.exe in KB during install or uninstall + attempt. + + + + + huangs@chromium.org + + The peak working set size of setup.exe in KB during install or uninstall + attempt. + + + + + waffles@chromium.org + + Hit following a successful install or update when the legacy profile count + keys / values are deleted from the registry. + + + + + + + grt@chromium.org + bcwhite@chromium.org + + The final exit-result of the entire run of setup.exe on Windows. + + + + + ganesh@chromium.org + sorin@chromium.org + xiaolingbao@chromium.org + The outcome of attempting to install a service on Windows. + + + + ganesh@chromium.org + sorin@chromium.org + xiaolingbao@chromium.org + + The outcome of attempting to rollback an install of a service on Windows. + + + + + + + ganesh@chromium.org + sorin@chromium.org + xiaolingbao@chromium.org + Win32 APIs that error out during setup. + + + + dcheng@chromium.org + rsesek@chromium.org + + Tracks whether an attempt to map shared memory was blocked due to too much + shared memory already being mapped into the address space. + + + + + mpearson@chromium.org + + The number of entries in shortcuts backend's database when initialized, + which happens during profile load. + + + + + hashimoto@chromium.org + + Time for shutdown initiated by the browser exit menu command. + + + + + hashimoto@chromium.org + + Time for shutdown initiated by the browser exit menu command per renderer + process. + + + + + hashimoto@chromium.org + + Time for shutdown initiated by an end session (user logs off, shuts down or + reboots without explicitly exiting). + + + + + hashimoto@chromium.org + + Time for shutdown initiated by an end session (user logs off, shuts down or + reboots without explicitly exiting) per renderer process. + + + + + hashimoto@chromium.org + + The number of renderer processes that couldn't be shutdown quickly due to + onbeforeunload or onunload listeners. + + + + + hashimoto@chromium.org + + The number of renderer processes running when shutdown was called. + + + + + hashimoto@chromium.org + The type of the last shutdown. + + + + hashimoto@chromium.org + + Time for shutdown initiated by the last browser window being closed. + + + + + hashimoto@chromium.org + + Time for shutdown initiated by the last browser window being closed per + renderer process. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Records if the fetched Signed Exchange certchain was served from HTTP cache + or not. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Reports the result of Signed Exchange cert verification, including success. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Reports the result of Signed Exchange CT verification, including success. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Records true when a fallback redirect of Signed Exchange has failed with + ERR_TO_MANY_REDIRECTS. + + Total count of SignedExchange.LoadResult2 should be used as a baseline of + this histogram. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Records the result of loading a resource from Signed HTTP Exchange. Emitted + each time a response is handled as Signed Exchange. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + The status of OCSP response in Signed Exchange certificates. Reported each + time Signed Exchange's OCSP check is performed. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Reports the revocation status of OCSP response in Signed Exchange + certificates. Emitted when Signed Exchange's OCSP check is performed, but + only when an up-to-date OCSP response was stapled. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Records if the prefetched Signed Exchange was properly formatted and passed + verification steps. Reported for each completed SignedExchange prefetch. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Records if the prefetched Signed Exchange was actually the target of a + navigation which happened within 30 seconds. Reported when a corresponding + navigation is observed, or from an periodic timer event which cleans up the + unmatched prefetch entries. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Records how much Signed Exchange navigations were prefetched and not + prefetched. Matched against 30 seconds window. Reported for each Signed + Exchange navigations. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Recorded when Signed Exchange signature was expired. Records the time delta + between current time and signature's "expires" value. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + Recorded when Signed Exchange signature was not yet valid. Records the time + delta between current time and signature's "date" value. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Reports the result of Signed Exchange signature verification, including + success. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + The amount of time elapsed to fetch certificate chain from certUrl, for + which the fetch has failed. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + The amount of time elapsed to fetch certificate chain from certUrl, for + which the fetch has succeeded. + + + + + ksakamoto@chromium.org + kinuko@chromium.org + horo@chromium.org + + The amount of time that elapsed during + SignedExchangeSignatureVerifier::Verify. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + Number of seconds until the Signed Exchange's expiration time. Recorded when + Signed Exchange signature verification is performed, and emitted only for + Signed Exchanges within the validity period. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + + The amount of time elapsed to ping the original publisher of the Signed + Exchanges. + + + + + kinuko@chromium.org + ksakamoto@chromium.org + horo@chromium.org + Reports the result of the Signed Exchange validity ping. + + + + peconn@chromium.org + peter@chromium.org + + Logs which way had the user navigated into settings screens when they press + "Clear and Reset" button in settings of a single website. + + + + + calamity@chromium.org + dominickn@chromium.org + + The number of days between launches of an origin saved to homescreen or as a + bookmark app shortcut. Recorded at the second and each following launch of a + specific origin from a shortcut, independently per origin. + + + + + calamity@chromium.org + dominickn@chromium.org + + Distribution of the engagement scores accumulated by a user, recorded at + startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. + + + + + calamity@chromium.org + dominickn@chromium.org + + The percentage of sites on a user's profile that have engagement scores that + fall in these buckets, recorded at startup per non-incognito profile, and + then upon the first engagement-increasing event every hour thereafter. + + + + + calamity@chromium.org + dominickn@chromium.org + + The type of engagement (navigation, user input, etc.) which led to an + accumulation in site engagement. + + + + + calamity@chromium.org + dominickn@chromium.org + + The mean site engagement per origin accumulated by this profile, recorded at + startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. + + + + + calamity@chromium.org + dominickn@chromium.org + + The median site engagement per origin accumulated by this profile, recorded + at startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. + + + + + calamity@chromium.org + dominickn@chromium.org + + The total number of origins with a non-zero site engagement score for this + profile, recorded at startup per non-incognito profile, and then upon the + first engagement-increasing event every hour thereafter. + + + + + calamity@chromium.org + dominickn@chromium.org + + The number of origins which have reached the daily site engagement point + cap, recorded at startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. Thus, each bin N contains + the number of clients where at least N origins have reached the maximum + daily site engagement point cap. + + + + + calamity@chromium.org + dominickn@chromium.org + + The number of origins which have reached the absolute site engagement point + cap, recorded at startup per non-incognito profile, and then upon the first + engagement-increasing event every hour thereafter. Thus, each bin N contains + the number of clients where at least N origins have reached the maximum + absolute site engagement point cap. + + + + + calamity@chromium.org + dominickn@chromium.org + + The total site engagement accumulated by this profile, recorded at startup + per non-incognito profile, and then upon the first engagement-increasing + event every hour thereafter. + + + + + mythria@chromium.org + v8-team@google.com + + The behaviour of site isolated javascript code cache recorded for each cache + transaction. It records if the request was serviced and if serviced how it + was serviced for ex: hit, miss, update. + + + + + bbudge@chromium.org + + The behaviour of site isolated web assembly code cache recorded for each + cache transaction during WASM compilation. It records if the request was + serviced and if serviced how it was serviced for ex: hit, miss, update. + + + + + alexmos@chromium.org + creis@chromium.org + + The count of all current BrowsingInstances. Recorded once per UMA ping. + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + The blocking decision CORB would have made on the response, if the request + was cross-origin. Reported if the response looked sensitive under the cache + heuristic (i.e. had Cache-Control: Private and Vary: Origin response + headers). + + + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + True if the response has an Accept-Ranges header, which indicates the server + supports range requests on the resource and could be used to bypass CORB. + Only reported if the resource looked sensitive under the Cache heuristic and + was a protected MIME type. + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + The blocking decision CORB would have made on the response, if the request + was cross-origin. Reported if the response looked sensitive under the CORS + heuristic (i.e. had the Access-Control-Allow-Origin header with a value + other than * or null). + + + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + True if the response has an Accept-Ranges header, which indicates the server + supports range requests on the resource and could be used to bypass CORB. + Only reported if the resource looked sensitive under the CORS heuristic and + was a protected MIME type. + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + True if the response has a nosniff header. If the nosniff header is not + present, then CORB must have decided to block without sniffing due to a + partial response, or because the MIME type was a never sniff type. Only + reported on resources CORB would have blocked/protected without sniffing + that have a protected MIME type. + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + True if the resource was found to be sensitive by either the CORS or Cache + heuristics. Recorded for every resource CORB sees. + + + + + krstnmnlsn@chromium.org + creis@chromium.org + + True if the response has an Accept-Ranges header, which indicates the server + supports range requests on the resource. Only reported if the response + looked sensitive under the cache or CORS heuristics. + + + + + lukasza@chromium.org + nasko@chromium.org + + Logged when FileSystemManagerImpl::Open fails CanAccessDataForOrigin check. + The value indicates whether the requested origin came from a http/https + origin VS from another origin (possibly from a Chrome App). + + + + + alexmos@chromium.org + lukasza@chromium.org + + Logs whether or not a password form was submitted from a site-isolated + process that's dedicated to a single site. Recorded when a password form is + submitted. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + nasko@chromium.org + + The count of all out-of-process iframes. Recorded once per UMA ping. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + The count of all RenderFrameProxyHosts. Recorded once per UMA ping. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + The count of RenderFrameProxyHosts in each BrowsingInstance. Recorded each + UMA ping, once per BrowsingInstance. + + + + + clamy@chromium.org + + Whether SiteInstances with a ProcessReusePolicy of + REUSE_PENDING_OR_COMMITTED_SITE could reuse an existing RenderProcessHost or + they had to create a new one. True when they reused an existing process, + false when they created a new one. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + + The number of currently saved user-triggered isolated sites. This includes + sites where the user has entered a password while using Site Isolation for + password sites (which is the target Site Isolation mode for Android). + Recorded once on browser startup. + + + + + alexmos@chromium.org + creis@chromium.org + lukasza@chromium.org + nasko@chromium.org + + The count of SiteInstances in a single BrowsingInstance. Recorded each UMA + ping, once per BrowsingInstance. + + + + + creis@chromium.org + lukasza@chromium.org + + Various actions related to cross-site document blocking in the browser + process, indicating whether the response was blocked from the renderer. + Recorded as the response is processed in the network stack. + + + + + creis@chromium.org + lukasza@chromium.org + + The total count of responses that were blocked by the cross-site document + blocking logic in the browser process. Recorded with a canonical MIME type + when the response is blocked. + + + + + ericrk@chromium.org + The scale factor of any images drawn by Skia. + + + + ericrk@chromium.org + + Whether a call to drawBitmap(Rect) or drawImage(Rect) used the tiled or + non-tiled rasterization path. + + + + + ericrk@chromium.org + + The count of images drawn by Skia with a given filter quality. + + + + + ericrk@chromium.org + + The path taken by Skia when it attempts to lock a texture for use. + + + + + + + pavely@chromium.org + src/chrome/browser/ui/messages/OWNERS + + Records the identifier of a snackbar every time one is shown. + + + + + ianwen@chromium.org + + Records how users interact with the special locale promotion dialog. + + + + + timvolodine@chromium.org + + Whether the Android spellchecking service was available at the start of a + new spellchecking session. Note that the user can disable the Android + spellchecking service in settings, in which case it will show up as not + available in the histogram. + + + + + timvolodine@chromium.org + + Measures the amount of time it takes to receive results from the + spellchecking service on Android. More precisely this is the + SystemClock.elapsedRealtime() between the + SpellCheckerSession.getSentenceSuggestions() and the invocation of the + onGetSentenceSuggestions() callback. + + + + + gujen@google.com + chrome-language@google.com + The percentage of misspelled words within checked words. + + + + gujen@google.com + chrome-language@google.com + The percentage of replaced words within misspelled words. + + + + groby@chromium.org + chrome-language@google.com + + Whether the user has opted in to asking Google for spelling suggestions. + Recorded both when spelling is initialized and when the preference is + changed. + + + + + yyushkina@google.com + gujen@google.com + chrome-language@google.com + + The elapsed time, in ms, between the moment the SimpleURLLoader starts + downloading the request and the moment the SimpleURLLoader callback is + invoked after the request finishes, whether an error or a success. + + + + + yyushkina@google.com + gujen@google.com + chrome-language@google.com + The HTTP code of Spelling service responses. + + + + yyushkina@google.com + gujen@google.com + chrome-language@google.com + + Describes the results returned by the Spelling service by assigning them to + one of three high-level buckets: request/service error, success with no + suggestions, and success with spelling suggestions. + + + + + gujen@google.com + chrome-language@google.com + + The percentage of replacement executions within suggestion occurrences. + + + + + gujen@google.com + chrome-language@google.com + + Counts how many languages are added to Chrome by the user but are not + supported for spell check (today Chrome only supports a hard-coded list of + locales for spell check). + + This is a measure of the potential impact of adding support for non-Hunspell + locales in the spell check settings. This also helps answer the following + question: should the Chrome spell check settings raise awareness of Windows + language packs and / or link to documentation describing how to install a + Windows language pack? + + This is recorded once during spell check initialization, and then once each + time the user changes their Chrome languages. + + + + + gujen@google.com + chrome-language@google.com + + Of all the currently enabled spell check languages, counts how many are + supported by the different spell checkers (Hunspell and the Windows OS). + + This helps measure the impact and reach of the native spell checker + integration. + + This is recorded once during spell check initialization, and then once each + time the user changes their enabled spell check languages. + + + + + gujen@google.com + chrome-language@google.com + + Measures the time it takes to perform one spell check end to end. The start + time is taken just before invoking Hunspell or the native spell checker (via + Mojo), and the end time is taken just before invoking the Blink spell check + callback. + + This is recorded every time a spell check is performed. + + + + + gujen@google.com + chrome-language@google.com + + Measures the time it takes to generate spelling suggestions when a user + right clicks a misspelled word. The start time is taken just before invoking + Hunspell for the suggestions, and the end time is taken just after the final + suggestion list is constructed. + + This is recorded every time the user opens the context menu on a misspelled + word, but only if the suggestions hadn't been pre-generated (which happens + when all spell check locales are supported by the OS spell checker). + + + + + costan@google.com + Error which prevented database close. + + + + costan@google.com + + Annotations for which bits of sql::MetaTable::CheckDeprecated() fire. + + + + + costan@google.com + SQLite extended error codes. + + + + costan@google.com + + SQLite memory footprint from sqlite3_memory_used() recorded 1 day after + first database is opened by sql::Database. + + + + + costan@google.com + + SQLite memory footprint from sqlite3_memory_used() recorded 1 hour after + first database is opened by sql::Database. + + + + + costan@google.com + + SQLite memory footprint from sqlite3_memory_used() recorded 1 week after + first database is opened by sql::Database. + + + + + costan@google.com + + SQLite memory footprint from sqlite3_memory_used() recorded 10 minutes after + first database is opened by sql::Database. + + + + + costan@google.com + + Time used to migrate History database schema to a new version. + + + + + costan@google.com + src/storage/OWNERS + Error which prevented database open. + + + + costan@google.com + Error from first read of the database. + + + + costan@google.com + Errors attempting to Raze() database. + + + + costan@google.com + Errors on second attempt to Raze() database. + + + + costan@google.com + Errors truncating database for Raze(). + + + + costan@google.com + + SQLite error code from failed ATTACH in sql::Recovery::Init(). + + + + + costan@google.com + + Records specific failure and success cases in sql::Recovery implementation, + to determine which cases warrant further development. This histogram tracks + detected errors, some of which may cause multiple results. See recovery.cc + for details. + + + + + costan@google.com + Error from sqlite3_backup_init() in sql::Recovery. + + + + costan@google.com + Error from sqlite3_backup_step() in sql::Recovery. + + + + pwnall@chromium.org + + SQLite failures encountered by //sql code. Intended to be viewed using + unique user counts. SQLite errors should be caused by media failures (random + variable with fairly low probability) or bad A/V software (not random, but + hopefully low enough that we can pretend it is). + + + + + costan@google.com + Version of pre-existing database at startup. + + + + meacer@chromium.org + + Users can opt in to send reports of certificate validation errors to Google. + This records the outcome whenever Chrome sends such a report. + + Some certificate validation reports might not be received because proxies, + firewalls or other content filters might filter report uploads. + + + + + estark@chromium.org + + Users can opt in to send reports of certificate validation errors to Google. + This records the error code whenever Chrome fails to send such a report. + + + + + estark@chromium.org + + Sites can opt in to Expect CT, a reporting feature that sends a report + whenever a TLS connection does not have valid Certificate Transparency + information associated with it. This records the error code when Chrome + fails to send an Expect CT report. + + + + + estark@chromium.org + + Sites can opt in to Expect CT, a reporting feature that sends a report + whenever a TLS connection does not have valid Certificate Transparency + information associated with it. This metric fires whenever Chrome attempts + to send an Expect CT report. + + + + + estark@chromium.org + + Keeps track of various insecure content events, such as loading an HTTP + script from an HTTPS page. + + + + + carlosil@chromium.org + Tracks when mixed content is displayed or run. + + + + carlosil@chromium.org + estark@chromium.org + + Tracks when mixed content is loaded from a "non-webby" URL, e.g. + an external protocol. The security of such URLs is unknown, but they are + exempt from mixed content UI treatment because they don't usually return + data to the browser. This histogram tracks how often such content is loaded + so that we can decide whether to block such resources unless an enterprise + policy is enabled. + + + + + msarda@chromium.org + + Number of accounts available for Single Sign On with the current device, + recorded at the time the SSO Promo is shown. + + + + + msarda@chromium.org + + Action the user takes when the Single Sign On promotion is shown. + + + + + msarda@chromium.org + + Number of times the promotion has been seen on the current device. + + + + + charliea@chromium.org + wittman@chromium.org + + The number of sample metadata item slots used after successfully setting a + metadata item. This count reflects both active and inactive metadata items. + + + + + futhark@chromium.org + + Microseconds spent in StyleEngine::InvalidateStyle. Only samples from high + resolution timers are recorded. + + + + + futhark@chromium.org + + Microseconds spent in RebuildLayoutTree called from Document::UpdateStyle. + + + + + futhark@chromium.org + + Microseconds spent in RecalcStyle called from Document::UpdateStyle. + + + + + mathp@chromium.org + + The counts of network error codes encountered by SuggestionsService when an + attempt to fetch suggestions from the server fails. + + + + + mathp@chromium.org + + The counts of HTTP response codes encountered by SuggestionsService when + attempting to fetch suggestions from the server. + + + + + mathp@chromium.org + + The latency of a SuggestionsService fetch that results in a success + response. + + + + + siggi@chromium.org + + Number of URLs present in the Suggestions local blacklist when the + Suggestions service is created. + + + + + mathp@chromium.org + + The counts of response states (such as empty or invalid) encountered by + SuggestionsService when attempting to fetch suggestions from the server. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Records supervised users trying to enable or disable extensions. Enabled + count increments when the supervised user successfully enables an extension. + Disabled count increments when the supervised user successfully disables an + extension. Enable attempt failed count increments when the parent has turned + off the "Permissions for sites, apps and extensions" toggle and + the supervised user tries to enable an extension that requires custodian + approval or has a permissions increase. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Records the actions of supervised users on the Extension Install Dialog. + Opened count increments when the supervised user tries to install an + extension from the Chrome Web Store and launches the Extension Install + Dialog. Asked Parent count increments when the supervised user clicks + "Ask a parent". Child Canceled count increments when the + supervised user clicks "Cancel". + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Measures the amount of time in milliseconds for the child user to click the + "Ask a parent" button on the Extension Install Dialog. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Measures the amount of time in milliseconds for the child user to click the + "Cancel" button on the Extension Install Dialog. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Records the progress of supervised users as they try to install Chrome + extensions. Extension Approval Granted count increments when the custodian + initially grants approval to install the extension. Permissions Increase + Granted count increments when the supervised user approves a newer version + of an existing extension with increased permissions. Extension Approval + Removed count increments when the supervised user removes an extension. + + + + + tobyhuang@chromium.org + cros-families@google.com + + Records the state of the "Permissions for sites, apps and + extensions" toggle. When parents/custodians have the toggle enabled, + supervised users may install extensions with parent/custodian approval, and + can approve permission updates by themselves. Otherwise, supervised users + cannot install extensions and cannot approve permission updates. If the + toggle is disabled and an extension has permissions updates, the extension + would remain force-disabled. The Disabled count increments when the parent + flips the toggle off, and increments twice if the supervised user logs in + while the toggle is in the off state. The Enabled count increments when the + parent flips the toggle on, and increments twice if the supervised user logs + in while the toggle is in the on state. While the double counting upon + logging in is less than ideal, at least the counts are balanced relative to + each other. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Records the actions of parents on the Parent Permission Dialog. Opened count + increments when the Parent Permission Dialog first opens. Parent Approved + count increments when the parent successfully types their password and + approves the extension. Parent Canceled count increments when the parent + cancels the dialog, denying the supervised user's attempt to enable the + extension. Failed count increments when there was some sort of failure in + the Parent Permission Dialog. No Parent Error count increments when the + supervised user doesn't have any associated parent email addresses for + asking approval. Note that this error also increments the Failed count. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Measures the amount of time in milliseconds after opening for the Parent + Permission Dialog to fail due to various reasons. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Measures the amount of time in milliseconds for the parent to successfully + type their password and approve the extension. + + + + + tobyhuang@chromium.org + agawronska@chromium.org + danan@chromium.org + cros-families@google.com + + Measures the amount of time in milliseconds for the parent to cancel the + Parent Permission Dialog. + + + + + agawronska@chromium.org + yilkal@chromium.org + cros-families@google.com + + The count of applications with time limit set by parents. Recorded once per + PerAppTimeLimit policy change. + + + + + agawronska@chromium.org + yilkal@chromium.org + cros-families@google.com + + The count of applications blocked by parents. It only applies to ARC++ + applications. Recorded once per PerAppTimeLimit policy change. + + + + + agawronska@chromium.org + yilkal@chromium.org + cros-families@google.com + + Per-App Time Limits feature engagement measured by the number of apps with + time limits set for child user. Reported at the beginning of each user + session. + + + + + agawronska@chromium.org + yilkal@chromium.org + cros-families@google.com + + The total number of PerAppTimeLimits policy changes seen in a session. + Recorded once at the end of the session. + + + + + agawronska@chromium.org + cros-families@google.com + + Action originated in parent access code dialog. Logged every time the action + happens. + + + + + agawronska@chromium.org + cros-families@google.com + + The context in which parent access code was used. Logged every time the new + parent access dialog is shown. + + + + + escordeiro@google.com + brunoad@google.com + ldaguilar@google.com + + The event that triggered status report for supervised account. + + + + + minch@chromium.org + omrilio@chromium.org + + Drag an app window from top in tablet mode will result in different window + states. Logged when the app drag ended to record the window end state. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of the action that drag an app window from top in tablet mode. + Logged when the TabletModeController is destructed, which means the user + session is ended. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of the action that drag an app window from top in tablet mode + when splitview is active. Logged when the TabletModeController is + destructed, which means the user session is ended. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of each volume adjust type in tablet mode. Logged when starts + volume adjust while in tablet mode. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of the action that drag a tab of the browser window in tablet + mode. Logged when the TabletModeController is destructed, which means the + user session is ended. + + + + + minch@chromium.org + omrilio@chromium.org + + The type of a tab drag done in tablet mode. Logged when start to drag a tab + of the browser window in tablet mode. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of the action that drag a tab of the browser window in tablet + mode when splitview is active. Logged when the TabletModeController is + destructed, which means the user session is ended. + + + + + minch@chromium.org + omrilio@chromium.org + + The type of the window (app window or tab strip) drag end event in tablet + mode. Logged when the window drag in tablet mode ended. + + + + + minch@chromium.org + omrilio@chromium.org + + The number of windows in overview when dragging a window from top in tablet + mode. Logged when start the window drag and overview has been opened behind. + + + + + altimin@chromium.org + farahcharab@chromium.org + + Used to track the number of active task queues in the task queue manager. + Reported every time a task is selected for execution. + + + + + altimin@chromium.org + farahcharab@chromium.org + + Used to track the number of tasks serviced due to starvation versus the + number of tasks serviced due to priroity. Incremented whenever a task queue + is selected to service. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether we found multiple matches for a selector. Recorded when + TextFragmentAnchor finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether the page did a non-zero scroll in order to scroll the match into + view. Only recorded if we found a match and scrolled it into view. Recorded + when TextFragmentAnchor finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The raw length of the directive in the URL (e.g. spaces count as the three + characters '%20'), regardless of how many text= terms there are. Recorded if + there was a text directive, regardless of whether a match was found. + Recorded when TextFragmentAnchor finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether an element-id based fragment was found in the document. Counted only + when a fragment was specified and it wasn't parsed into a |targetText| style + anchor. + + + + + nburris@chromium.org + bokan@chromium.org + + The length of the end parameter, in the case of a range match. Only recorded + if a match was found. Recorded when TextFragmentAnchor finishes searching + once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The length of the matched text, in the case of an exact match. Only recorded + if a match was found. Recorded when TextFragmentAnchor finishes searching + once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether the match was within a list item. Only recorded for exact text + fragments and only if a match was found. Recorded when TextFragmentAnchor + finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The percentage of selectors for which a match was found in the document. + Recorded when TextFragmentAnchor finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + An enum indicating which parameters were specified in the text fragment + anchor. Only recorded if a match was found. Recorded when TextFragmentAnchor + finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The length of the matched text, in the case of a range match. Only recorded + if a match was found. Recorded when TextFragmentAnchor finishes searching + once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether the scroll into view was cancelled by a user gesture or programmatic + scroll. Recorded when TextFragmentAnchor finishes searching once the page is + loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The number of selectors in the text fragment anchor if it is present. + Recorded when TextFragmentAnchor finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The length of the start parameter, in the case of a range match. Only + recorded if a match was found. Recorded when TextFragmentAnchor finishes + searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + Whether the match was within a table cell. Only recorded for exact text + fragments and only if a match was found. Recorded when TextFragmentAnchor + finishes searching once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The time between creating the TextFragmentAnchor (i.e. when it is parsed) + and scrolling the target into view. Only recorded if there is a match and we + scroll it into view. Recorded when TextFragmentAnchor finishes searching + once the page is loaded. + + + + + nburris@chromium.org + bokan@chromium.org + + The time between scrolling a match into view and the user scrolling back to + the top of the page. Used as a signal for whether a match was useful. Only + recorded if a match is scrolled into view and the user subsequently scrolled + back to the top of the page. Recorded when TextFragmentAnchor finishes + searching once the page is loaded. + + + + + dmazzoni@chromium.org + + Events fired by the text-to-speech engine when speaking an utterance. + + + + + dmazzoni@chromium.org + katie@chromium.org + + Indicates if an utterance spoken via synthesized text-to-speech was + triggered by the Chrome TTS extension API or the web speech API. + + + + + dmazzoni@chromium.org + + True if an utterance spoken via synthesized text-to-speech requested a + specific gender. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance spoken via synthesized text-to-speech specified a + language code. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance spoken via synthesized text-to-speech requested a + specific pitch other than the default. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance spoken via synthesized text-to-speech requested a + specific speech rate other than the default. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance spoken via synthesized text-to-speech requested a + specific voice by name. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance spoken via synthesized text-to-speech requested a + specific volume other than the default. + + + + + dmazzoni@chromium.org + katie@chromium.org + + True if an utterance is spoken with native speech provided by the operating + system, otherwise it's spoken via a Chrome extension that implements + text-to-speech support. + + + + + dmazzoni@chromium.org + katie@chromium.org + + The length of an utterance to be spoken via synthesized text-to-speech. + + + + + chrisha@chromium.org + + The total number of certificates for modules loaded (or potentially loaded) + into the browser process that are signed by Microsoft. A catalog counts as a + single certificate, and may refer to many modules. Measured shortly after + startup. Windows only. + + + + + chrisha@chromium.org + + The total number of certificates for modules loaded (or potentially loaded) + into the browser process. A catalog counts as a single certificate, and may + refer to many modules. Measured shortly after startup. Windows only. + + + + + pmonette@chromium.org + + Records whether an equivalent driver letter path was found for a device + path. + + + + + pmonette@chromium.org + + Records the number of modules that were blocked from loading into the + browser process by the third-party DLL blocking feature. This is recorded + every 5 minutes. + + + + + pmonette@chromium.org + + Records whether or not Chrome is still blocking third-party DLLs. This is a + bit that turns to false when the in-process printing is invoked. Recorded + every 5 minutes. + + + + + pmonette@chromium.org + + Records the number of unique modules that were blocked from loading into the + browser process by the third-party DLL blocking feature. This is recorded + every 5 minutes. + + + + + pmonette@chromium.org + + The number of registered input method editors found on the user's machine. + This is emitted shortly after startup when the IME enumeration takes place. + + + + + pmonette@chromium.org + + Records the time it took to gather the list of installed third-party + programs and their install location or components. + + + + + pmonette@chromium.org + + Records whether retrieving the current user SID was successful. + + + + + chrisha@chromium.org + + The total number of third-party modules (neither Microsoft nor Google) that + are loaded in the browser process. Measured shortly after startup. Windows + only. + + + + + chrisha@chromium.org + + The total number of third-party modules (neither Microsoft nor Google) that + are not yet loaded in the browser process, but may potentially be (shell + extensions, for example). Measured shortly after startup. Windows only. + + + + + chrisha@chromium.org + + The total number of signed modules loaded (or potentially loaded) into the + browser process. Measured shortly after startup. Windows only. + + + + + chrisha@chromium.org + + The total number of modules loaded (or potentially loaded) into the browser + process that are signed via a catalog. Measured shortly after startup. + Windows only. + + + + + chrisha@chromium.org + + The total number of modules loaded (or potentially loaded) into the browser + process that are signed by Microsoft. Measured shortly after startup. + Windows only. + + + + + chrisha@chromium.org + + The total number of modules loaded (or potentially loaded) into the browser + process. Measured shortly after startup. Windows only. + + + + + chrisha@chromium.org + + The total number of unsigned modules loaded (or potentially loaded) into the + browser process. Measured shortly after startup. Windows only. + + + + + pmonette@chromium.org + + The number of registered shell extensions found on the user's machine. This + is emitted shortly after startup when the shell extensions enumeration is + done. Doesn't count duplicates. + + + + + pmonette@chromium.org + + Indicates whether the TimeDateStamp for a loaded module was successfully + obtained. + + + + + pmonette@chromium.org + + Records whether or not a loaded third party module could be uninstalled + using the Windows Apps & Features page. + + + + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Time elapsed between when the thread managed by a SchedulerWorker is + detached and when the main function of a new thread managed by the same + SchedulerWorker is entered (following a wake up). Recorded each time that a + thread is recreated for a given SchedulerWorker. + + + + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Latency of dummy "heartbeat" tasks posted with specific traits + (see suffix). The heartbeat recording avoids dependencies between this + report and other work in the system. See + ThreadPool.TaskLatencyMicroseconds.* for a metric that is closer to the real + workload. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Number of tasks executed by a SchedulerWorker before it detached. Recorded + when a SchedulerWorker detaches. + + + + + fdoray@chromium.org + + Number of tasks run by ThreadPool while task was queuing (from time task was + posted until time it was run). Recorded for dummy "heartbeat" + tasks posted with specific traits (see suffix). The heartbeat recording + avoids dependencies between this report and other work in the system. + Recorded every time the ServiceThread performs a heartbeat latency report. + + + + + fdoray@chromium.org + gab@chromium.org + robliao@chromium.org + + Time elapsed between when a task is posted and when it starts to run. + Recorded for each task that runs inside the ThreadPool. + + + + + dschinazi@chromium.org + src/net/OWNERS + + The time it takes indicated thread to respond with a pong message for a ping + message from WatchDog thread. + + + + + dschinazi@chromium.org + src/net/OWNERS + + This is the total number of watched threads that are responding when we got + no response from the watched thread. + + + + + dschinazi@chromium.org + src/net/OWNERS + + This is the total unresponsive time since last pong message for the + indicated thread when we got no response from the watched thread. + + + + + dschinazi@chromium.org + src/net/OWNERS + + This is the total number of watched threads that are not responding when we + got no response from the watched thread. + + + + + dfried@chromium.org + pbos@chromium.org + + While taking a screenshot of the current tab for use as a thumbnail, the + time it took to copy the tab's contents into a bitmap. + + + + + carlosk@chromium.org + skym@chromium.org + + The time it takes to detect whether a thumbnail requires a gradient overlay. + This is run when thumbnails are downloaded for content suggestions, as they + load and the result is cached for future use. It is Android specific. + + + + + carlosk@chromium.org + skym@chromium.org + + Whether a thumbnail used for a suggestions image requires a gradient to be + overlaid to not fade into the background. It applies to the thumbnails used + for content suggestions and is Android specific. + + + + + dfried@chromium.org + pbos@chromium.org + + While taking a screenshot of the current tab for use as a thumbnail, the + time it took to post-process the captured bitmap. + + + + + pdr@chromium.org + vmpstr@chromium.org + + Measures whether the tile manager exceeded the hard GPU memory budget + (OOMed). Recorded each time the tile manager assigns GPU memory to tiles. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + Events in TimeZoneRequest. + + + + + + alemate@chromium.org + michaelpg@chromium.org + Http response codes in TimeZoneRequest. + + + + + + alemate@chromium.org + michaelpg@chromium.org + + The time elapsed between the sending of the first API request and the time + the final (failed) response was recorded. Includes all retries. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + + The time elapsed between the sending of the first API request and the time + the final (successfull) response was recorded. Includes all retries. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + Result of TimeZoneRequest. + + + + + + alemate@chromium.org + michaelpg@chromium.org + Number of retries until the final response was recorded. + + + + peterlaurens@chromium.org + + The number of millseconds between the user requesting a new incognito tab, + e.g. by tapping the New Incognito Tab entry in the main tools menu, and it + completing its animation on screen. + + + + + peterlaurens@chromium.org + + Number of milliseconds passed between the event that triggers the + presentation of the tools menu (the main menu of actions accessed from the + toolbar), and the actual appearance of the menu on screen. Includes the + animation duration. + + + + + peterlaurens@chromium.org + + The number of millseconds between the user requesting a new incognito tab, + from within the tab switcher, e.g. by tapping the New Tab button from the + tab switcher UI, and it completing its animation on screen. + + + + + peterlaurens@chromium.org + + The number of millseconds between the user requesting a new tab, from within + the tab switcher UI, e.g. by tapping the New Tab button from the tab + switcher UI, and it completing its animation on screen. + + + + + spqchan@chromium.org + Tracks the usage of the default touch bar buttons. + + + + zentaro@chromium.org + cros-peripherals@chromium.org + Tracks touchpad acceleration setting changes by the user. + + + + zentaro@chromium.org + cros-peripherals@chromium.org + Tracks touchpad acceleration setting on startup. + + + + jhawkins@chromium.org + Tracks touchpad device state. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad natural scroll setting changes by the user. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad natural scroll setting on startup. + + + + zentaro@chromium.org + cros-peripherals@google.com + + Tracks touchpad sensitivity setting changes by the user. This replaces the + old Touchpad.Sensitivity.Changed metric. + + + + + zentaro@chromium.org + cros-peripherals@google.com + + Tracks touchpad sensitivity setting on startup. This replaces the old + Touchpad.Sensitivity.Started metric. + + + + + + + khorimoto@chromium.org + zentaro@chromium.org + Whether touchpad scroll acceleration is enabled. + + + + + + khorimoto@chromium.org + zentaro@chromium.org + Touchpad scroll sensitivity value. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad TapDragging setting changes by the user. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad TapDragging setting on startup. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad TapToClick setting changes by the user. + + + + zentaro@chromium.org + cros-peripherals@google.com + Tracks touchpad TapToClick setting changes by the user. + + + + nzolghadr@chromium.org + input-dev@chromium.org + + The touch device driver failed to send a TOUCHEVENTF_UP, and chromium + generated a simulated event to maintain consistency/correctness. + + This workaround will be removed once usage drops off. See + https://crbug.com/811273 for details. + + + + + tdresser@chromium.org + + Tracks whether Touch Event Feature Detection is enabled. This is based on + the touch events enabled flag and the presence of a touchscreen. + + Team: input-dev@chromium.org. + +
+ NOTE: This metric was incorrectly recorded on Chrome OS for versions 42 + through 45, see http://crbug.com/499476 for more details. As of + http://crbug.com/644318, we changed the internal name to + TouchEventFeatureDetection, but we still keep the old histogram name here to + keep consistensy. +
+ + + + semenzato@google.com + + Reported at boot if the previous boot session was interrupted in the middle + of a TPM command during the first 30 seconds of uptime. + + + + + ssid@chromium.org + + Reason why background tracing finalization was not allowed. Also see + "Tracing.Background.ScenarioState" metric, which records the total + number of times finalization was allowed and not allowed. + + + + + oysteine@chromium.org + + The size, in kilobytes, of a finalized trace ready to be uploaded. + + + + + ssid@chromium.org + + Connection type of the network used to determine the trace buffer size, when + background tracing was triggered. Recorded only on Android. + + + + + ssid@chromium.org + + Connection type of the network used to determine the trace upload limit, + when background tracing upload was started. Recorded only on Android. + + + + + oysteine@chromium.org + + Records state of the Background Tracing system, from when scenarios are + attempted to be activated until they're completed (successfully or failed) + + + + + eseckler@chromium.org + tracing@chromium.org + + Records success or failure of creating the shared buffer in + ProducerClient::InitSharedMemoryIfNeeded() + + + + + peconn@chromium.org + peter@chromium.org + + Emits true if the user went to site settings from the dialog that is shown + after a Trusted Web Activity client app has had its data cleared. + + + + + peconn@chromium.org + peter@chromium.org + + Emits true if the user went to site settings from the dialog that is shown + after a Trusted Web Activity client app has been uninstalled. + + + + + peconn@chromium.org + peter@chromium.org + + Logs which kind of fallback for notification small icon was used for Trusted + Web Activity notification delegation. + + + + + eirage@chromium.org + peconn@chromium.org + + When a site running in Truested Web Activity is accessing geolocation, + records whether the last tracked focused Trusted Web Activity client app + enrolled location delegation. + + + + + eirage@chromium.org + peconn@chromium.org + + When a Trusted Web Activity client app's location permission is changed, + record the previous state and new stase. + + + + + eirage@chromium.org + peconn@chromium.org + + Records the boolean result (granted or not) from requesting a Trusted Web + Activity client app's location permission. + + + + + eirage@chromium.org + peconn@chromium.org + + Records an error code when we get a new location update or location error + from the Trusted Web Activity client app. Record + "LocationUpdateError.NONE" (value = 0) if there is no error and + the geoposition is valid. + + + + + eirage@chromium.org + peconn@chromium.org + + When Trusted Web Activity launches or navigates to a site that violate the + quality criteria, records the violation type. + + + + + peconn@chromium.org + peter@chromium.org + Recorded when data is shared via a Trusted Web Activity. + + + + peconn@chromium.org + peter@chromium.org + + Records whether or not a splash screen has been shown when launching a + Trusted Web Activity. + + + + + peconn@chromium.org + peter@chromium.org + + Time spent in a verified origin until navigating to an unverified one or + pausing the Trusted Web Activity. + + + + + peconn@chromium.org + peter@chromium.org + + Time spent out of verified origins until navigating back to a verified one + or pausing the Trusted Web Activity. + + + + + bsep@chromium.org + + The device scales available on the system at startup. A system may report + more than one if it has multiple displays with varying device scales. Only + logged on Windows. + + + + + malaykeshav@chromium.org + + Records the time spent in uncompressing a gzipped animation file. + + + + + + + msarda@chromium.org + droger@chromium.org + + State of the user settings for making searches and browsing better, recorded + at startup. + + + + + + + droger@chromium.org + msarda@chromium.org + + All *off* sync data types are recorded when the user confirmed the sync + setup after going through the advanced opt-in flow. + + + + + sorin@chromium.org + + The number of download jobs found in the Windows BITS queue. This value is + expected to be zero in most cases, or a small number otherwise. Large values + indicate a problem with the job creation or clean up code. The metric is + recorded before a new BITS job is created and inserted into BITS queue. + + + + + sorin@chromium.org + + True if a new BITS job was created to download the url, or false, if an + existing job was found in the BITS queue. The metric is recorded when the + component updater background downloader is asked to download a CRX. + + + + + ksspiers@chromium.org + nrpeter@chromium.org + + Measures the time elapsed from an update being visible to the browser and + the browser being restarted or quit. + + + + + spqchan@chromium.org + + Tracks the upgrade notification stage. This is recorded with every UMA log. + + + + + mpolzer@google.com + managed-platforms@google.com + + Tracks what is the reason we're doing a rollback instead of an update (going + to a more stable channel or admin-initiated enterprise rollback). We're + showing different notifications depending on the reason. + + Sent when the device finished installing the rollback image, shows the + notification and is waiting for reboot. + + This metric is specific to Chrome OS. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when Chrome is started, and + when the login prompt is again visible after a logout. This statistic is + only collected when preceeded by a logout. + + + + + satorux@chromium.org + hashimoto@chromium.org + + The system uptime on Chrome OS when the dbus-daemon process crashes, + resulting in a reboot. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS for setting up for a login after a + logout. More specifically, it is the time between when the Cryptohome is + unmounted (the last step in the logout process) and when the login prompt is + again visible after a logout. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS when performing a logout. More + specifically, it is the time between when a logout is initiated and when the + Cryptohome is unmounted, signaling the last step in the logout process. This + statistic is not collected when the logout is part of a restart or shutdown. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between initiating a logout and the + next time the login prompt is visible again. This statistic is not collected + if the machine is shutdown between the logout initiation and the prompt + becoming visible. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when a logout is initiated + and the UI has stopped (and Chrome has exited) during the logout process. + This statistic is not collected if the logout is part of a restart or + shutdown. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when all user-associated + processes have been terminated during the logout process and when Chrome is + started again to show the login screen. Since at least ChromeOS M62, + equivalent to Uptime.XTerminatedToChromeExecAfterLogout. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Measures the time elapsed on Chrome OS between when the UI has stopped + (Chrome has exited), and when all other associated processes have been + terminated during the logout process. This statistic is not collected if the + logout is part of a restart or shutdown. + + + + + pnoland@chromium.org + fgorski@chromium.org + + Android: count of Usage Stats events. Recorded as these events occur; e.g. + when a domain is associated with a token, or a site is suspended. + + + + + achuith@chromium.org + + Distribution of the default images that existing users login with (Chrome + OS). One sample is taken each time the user logs in. + + + + + achuith@chromium.org + The time it took to download user's profile picture. + + + + javierrobles@chromium.org + rkgibson@google.com + bling-team@google.com + + [iOS] Used on iOS 13+ to report the usage of Light and Dark mode. This is + logged at startup and on each user interface style change. Can be caused by + the system automatic switch or by the user manually changing the style. + + + + + achuith@chromium.org + + The number of users of different types that log in to the system (Chrome + OS). + + + + + + + alemate@chromium.org + rsorokin@chromium.org + cros-oac@google.com + + The time between one regular user logging out and a different regular user + logging in (Chrome OS). Delays above thirty minutes or which span system + reboots or non-regular-user logins are not reported. + + + + + atwilson@chromium.org + + Whether the profile_ever_initialized() user attribute migration has + completed for the current user. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + rsorokin@chromium.org + cros-oac@google.com + + This is logged when new user type reported by Gaia is different from the old + one (for existing user). + + + + + rsorokin@chromium.org + cros-oac@google.com + + The result of restoring account id on Chrome restart after crash on Chrome + OS. + + + + + binlu@google.com + + Records instances of navigator.vibrate. Includes whether or not it comes + with a user gesture, same-origin subframe or cross-origin subframe. + + + + + yoshiki@chromium.org + + Chrome OS Video Player: the results of the cast API extension load. This is + recorded after the initialization of the extension is finished. + + + + + yoshiki@chromium.org + + Chrome OS Video Player: the length of casted video (in seconds). + + + + + yoshiki@chromium.org + + Chrome OS Video Player: the number of cast devices. This is recorded when + the cast extension finishes the discovery. + + + + + yoshiki@chromium.org + + Chrome OS Video Player: the number of files being opened on launch. + + + + + yoshiki@chromium.org + + Chrome OS Video Player: type of playback (eg. local play, cast). This is + recorded when a video starts playing. + + + + + bokan@chromium.org + + Tracks the proportion of non-mobile optimized (i.e. zoom disabled or layout + width matches viewport) page views that had a user-initiated page scale + (e.g. pinch-zoom, double-tap). Recorded on navigation to a new page - on + Android only. + + + + + bokan@chromium.org + + Tracks the maximum scale factor that a user has scaled to over the lifetime + of the page. The scale is counted at pinch end (e.g. zooming to 300% and + back out to 150% in one gesture would count as 150%). Reported only on + non-mobile optimized pages (i.e. zoom disabled or layout width matches + viewport) which have had a page scale changing gesture. Recorded on + navigation to a new page - on Android only. + + + + + bokan@chromium.org + + The viewport meta tag type seen on each page load. Only recorded on Android. + + + + + bokan@chromium.org + + The screen width as a percentage of viewport width (i.e. zoom at which we + can see the whole page). Only recorded on Android and for viewport meta tags + with constant width. + + + + + wychen@chromium.org + dtrainor@chromium.org + The interval between ViewResourceAdapter#getBitmap calls. + + + + oka@chromium.org + + An integer representing a state transition from x to y in the form of x * + 1000 + y. If the transition is not expected, the value is negated. For + example an expected transition from SHOWING (= 2) to SHOWN (= 1) is denoted + as 2001, and an unexpected transition from SHOWING to SHOWING is denoted as + -2002. See KeyboardControllerState for the correspondence between the number + and the enum. + + + + + oka@chromium.org + Latency of the keyboard being loaded for the first time. + + + + Please list the metric's owners. Add more owner tags as needed. + + A count of various control events that can occur on the virtual keyboard, + such as showing and hiding. + + + + + oka@chromium.org + + Records whenever an intermediate keyboard state has been active for longer + than a fixed timeout. + + + + + dcastagna@chromium.org + hoegsberg@chromium.org + + Overlay strategies used to promote Hardware Overlays, per frame. Recorded + every time a frame is rendered by the display compositor. + + + + + magchen@chromium.org + zmo@chromium.org + + Any root damage excluding overlay damage in the current frame? + + + + + magchen@chromium.org + zmo@chromium.org + + The root damage type excluding underlay damage in the current frame. + + + + + samans@chromium.org + sadrul@chromium.org + viz-team-wat@google.com + + The time it took from when FrameSinkVideoCapturerImpl sent a request for an + I420 readback until the result comes back and ReadI420Planes successfully + finishes. + + + + + samans@chromium.org + sadrul@chromium.org + viz-team-wat@google.com + + Whether an I420 readback initiated by FrameSinkVideoCapturerImpl succeeded. + + + + + samans@chromium.org + sadrul@chromium.org + viz-team-wat@google.com + + The time it took from when FrameSinkVideoCapturerImpl sent a request for an + RGBA readback until the result comes back and ReadRGBAPlane successfully + finishes. + + + + + samans@chromium.org + sadrul@chromium.org + viz-team-wat@google.com + + Whether an RGBA readback initiated by FrameSinkVideoCapturerImpl succeeded. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + + Android: The source of a dismissed voice search, such as omnibox or NTP. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + + Android: The source of a failed voice search, such as omnibox or NTP. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + + Android: The source of a successful voice search, such as omnibox or NTP. + + + + + muyuanli@chromium.org + + Counts the number of requests to retrieve voice interaction context when no + user interaction is initiated. + + + + + wylieb@chromium.org + tedchoc@chromium.org + + Records the time it takes between the user clicking the mic and chrome + recieving the transcribed voice query. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + + Android: The source of a voice search start event, such as omnibox or NTP. + + + + + wylieb@chromium.org + tedchoc@chromium.org + + Android: The source of an incoming result that doesn't align with an + outgoing request from Chrome. + + + + + muyuanli@chromium.org + + Records the time between user interaction and the actual request arrival. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + + Android: Records the confidence value of a successful voice search as a + percentage. + + + + + wylieb@chromium.org + tedchoc@chromium.org + yusufo@chromium.org + Android: Records whether the voice search produced results. + + + + ymalik@chromium.org + + Whether the user had been through the FRE when Chrome is launched in VR + mode. + + + + + alcooper@chromium.org + xr-dev@chromium.org + + The duration of the VR session. Logged when a new disjoint session has + begun, or when the session has ended in a non-continuable way. + + + + + alcooper@chromium.org + xr-dev@chromium.org + + Number of videos watched in a VR session. Logged when a new disjoint session + has begun, or when the session has ended in a non-continuable way. + + + + + alcooper@chromium.org + xr-dev@chromium.org + + The duration of a single session spent watching video in VR. Logged when a + new disjoint session has begun, or when the session has ended in a + non-continuable way. + + + + + alcooper@chromium.org + xr-dev@chromium.org + The type of headset being used for VR. + + + + eugenebut@chromium.org + gambard@chromium.org + + [iOS] Reports URL matches between the return value from the WebState's + GetLastCommittedURL and GetCurrentURL methods. It is expected the origins + will be equal to confirm that GetCurrentURL can now be replaced with + GetLastCommittedURL. This will be called each time WebStateImpl:: + GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an + old method of obtaining the url and trust level. The trust level was only + relevant with UIWebView, so this method is only called from code which has + not yet been updated since UIWebView was removed. + + + + + dominickn@chromium.org + peconn@chromium.org + + Records the number of milliseconds that the add to homescreen dialog + required to check installability eligibility. + + + + + finnur@chromium.org + beverloo@chromium.org + + Keeps track of what verbiage was shown in the App menu versus what was + actually installed. + + + + + asamidoi@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + Records the result of the promotability check that decides if a PWA install + prompt appears depending on that the site has a service worker with offline + support. + + + + + asamidoi@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + Records the time to complete the promotability check that decides if a PWA + install prompt appears depending on that the site has a service worker with + offline support. + + + + + calamity@chromium.org + mgiuca@chromium.org + loyso@chromium.org + + The type of engagement (navigation, user input, etc.) which led to an + accumulation in site engagement within a web app window or tab. Should be + collected for a subset of SiteEngagementService.EngagementType, which is + triggered for all browsing contexts. Recorded at the time of engagement + accumulation (e.g., when mouse is clicked). + + + + + alancutter@chromium.org + mgiuca@chromium.org + loyso@chromium.org + + The HTTP status code class returned for each icon loaded during a WebApp's + creation. See corresponding + Extensions.BookmarkApp.Icon.HttpStatusCodeClassOnCreate histogram for legacy + extension-based system. Recorded when WebAppDataRetriever starts downloading + icons. + + + + + alancutter@chromium.org + mgiuca@chromium.org + loyso@chromium.org + + The HTTP status code class returned for each icon loaded when syncing a + WebApp. See Extensions.BookmarkApp.Icon.HttpStatusCodeClassOnSync histogram + for legacy extension-based system. Recorded when WebAppDataRetriever starts + downloading icons. + + + + + alancutter@chromium.org + raymes@chromium.org + loyso@chromium.org + + The HTTP status code class returned for each icon loaded when updating a + WebApp. Recorded when WebAppDataRetriever starts downloading icons. + + + + + ericwilligers@chromium.org + peter@chromium.org + yfriedman@chromium.org + + Records the display mode (as defined in the Web App Manifest spec) at the + install time of a WebApp. Fixes a bug in the data collection for desktop web + apps. + + + + + dominickn@chromium.org + alancutter@chromium.org + + Records when a web app install bounced for different install sources. A + bounce is when the user uninstalls the web app within 1 hour of installing + it. + + + + + dominickn@chromium.org + loyso@chromium.org + calamity@chromium.org + + Records the mechanism and source from which a web app installation was + triggered, regardless of whether the installation was successful. + + + + + dmurph@chromium.org + desktop-pwa-team@google.com + + Records the reason that the WebApp install confirmation dialog is closed. + This dialog is shown when the user clicks on the 'install' icon in the + omnibox for websites that are installable. This metric is intended to give + data for an experiment to choose the best install icon. + + + + + + + calamity@chromium.org + ortuno@chromium.org + Records the result code of Web App installs. + + + + + + calamity@chromium.org + ortuno@chromium.org + + Records why System Web App .crx extension is disabled during System Web App + installs. Certain properties of the profile might cause Extensions to be + disabled as soon as they are installed. For example, kiosk profile might set + policies to disable all Extensions, including System Web Apps which are + considered Extensions. + + + + + + + calamity@chromium.org + ortuno@chromium.org + + Records .crx extension error code when System Web App install fails. + + + + + davidbienvenu@chromium.org + jessemckenna@google.com + + The result of a Progressive Web App (PWA) launcher's attempt to launch + Chrome. Windows-only. + + + + + davidbienvenu@chromium.org + jessemckenna@google.com + + The result of updating a single Progressive Web App (PWA) launcher with the + latest version of chrome_pwa_launcher.exe. Windows-only. + + + + + alancutter@chromium.org + dxie@google.com + loyso@google.com + mgiuca@google.com + + The result of deploying a follow up migration after a migration bug + (https://crbug.com/1125020) that caused users' web apps to open in a browser + tab instead of a standalone window. This follow up migration only runs once + at startup for all Chrome profiles. If it fails it will retry until + successful on subsequent start ups, metrics are only recorded on success. + + + + + peter@chromium.org + hartmanng@chromium.org + + Records whether the top-level navigations in standalone Web Apps result in + presenting the web content or showing the error page. + + + + + alancutter@chromium.org + desktop-pwas-team@google.com + + Records how many preinstalled web app config files failed to parse as valid + JSON with valid fields. See external_web_app_utils.cc ParseConfig(). This is + recorded at start up. + + + + + alancutter@chromium.org + desktop-pwas-team@google.com + + Records how many preinstalled web apps configs were disabled for the device. + This is recorded at start up. + + + + + alancutter@chromium.org + desktop-pwas-team@google.com + + Records how many preinstalled web apps configs were enabled for the device. + This is recorded at start up. + + + + + phillis@chromium.org + dmurph@chromium.org + Records the result of shortcut creation for PWA. + + + + alancutter@chromium.org + loyso@chromium.org + + Records uninstallation result for sync initiated uninstalls in the new + USS-based web applications system. + + + + + calamity@chromium.org + ortuno@chromium.org + + Records the time taken to perform a fresh install of all system web apps. It + measures the time from when we dispatch a call to install them, until we get + all the installation results. This intentionally excludes the scenario where + we don't request to install all the apps for consistency. Recorded in + milliseconds, from 1 millisecond to 3 minutes. + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of uninstalling a WebApp when the user clicks on + "Uninstall" from the 3-dot menu of the respective WebApp window. + + + + + dmurph@chromium.org + desktop-pwas-team@google.com + + Records the result of uninstalling an app from the chrome://apps page. This + happens whena user right-clicks on a greyed out webapp icon in the + chrome://apps page and clicks "Uninstall". + + + + + benwells@chromium.org + dominickn@chromium.org + loyso@chromium.org + + Records the user response to the dialog shown when uninstalling a web app. + + + + + alancutter@chromium.org + loyso@chromium.org + raymes@chromium.org + + Records the result of web app manifest update checks during page + navigations. Note that "No app in scope" results are ignored due + to the expected several orders of magnitude higher volume than all other + update results. + + + + + qjw@chromium.org + ortuno@chromium.org + desktop-pwas-team@google.com + Records the result of WebAppUrlLoader::PrepareForLoad(). + + + + agl@chromium.org + + Tracks events related to prompting users for permission to pass WebAuthn + attestation information back to origins. "Queried" means that the + embedder was queried for a decision. (Since such decisions can be resolved + by enterprise policy, that doesn't imply that a user saw a permissions + prompt in every case.) Then one of four things can happen: a timeout, a + positive or negative resolution, or the request is abandoned. The latter + case occurs when, for example, the tab is closed or the user navigates away. + + + + + agl@chromium.org + martinkr@google.com + + Records events that occur during caBLE v1 authenticator discovery so that + potential discovery failures can be identified. + + + + + kenrb@chromium.org + martinkr@google.com + + When a relying party is attempting to authenticate a user using the + WebAuthentication API, this metric reports the number of valid credentials + that the RP has registered for the user. + + + + + kenrb@chromium.org + martinkr@google.com + + Records the transport used for all WebAuthentication GetAssertion requests + sent to authenticators. This does not necessarily mean that there was a + success response from any given authenticator. + + + + + kenrb@chromium.org + martinkr@google.com + + Records the transport used when an authenticator responds with success to a + WebAuthentication GetAssertion request. + + + + + kenrb@chromium.org + martinkr@google.com + + Record at startup whether the current system has a platform authenticator + available; i.e. whether IsUVPAA JS call would return true or false. + + + + + kenrb@chromium.org + martinkr@google.com + + When a relying party is attempting to register a credential for a new user + using the WebAuthentication API, this metric reports the number of existing + credentials already registered in order to prevent re-registration. + + + + + kenrb@chromium.org + martinkr@google.com + + Records the transport used for all WebAuthentication MakeCredential requests + sent to authenticators. This does not necessarily mean that there was a + success response from any given authenticator. + + + + + kenrb@chromium.org + martinkr@google.com + + Records the transport used when an authenticator responds with success to a + WebAuthentication MakeCredential request. + + + + + kenrb@chromium.org + martinkr@google.com + + Records failures associated with verifying the relying party origin when + that relying party is attempting to make a credential or get an assertion + using the WebAuthentication API. Failures include when the relying party's + origin is opaque or non-secure, or when the caller-provided relying party ID + or app ID is not valid for this origin. + + + + + agl@chromium.org + + Tracks events related to prompting users for permission to pass U2F + attestation information back to origins. "Queried" means that the + embedder was queried for a decision. (Since such decisions can be resolved + by enterprise policy, that doesn't imply that a user saw a permissions + prompt in every case.) Then either a positive or negative result can happen. + However, note some complications: a negative will be recorded when the tab + is closed or the user navigates away, and a positive result will be recorded + when the user accepts the permission prompt but the request has already + timed out. + + + + + ajuma@chromium.org + gambard@chromium.org + + [iOS] Counts the number of time the backForwardList of the WebView gets out + of sync with the URL exposed by the WebView. This should not happen and is + probably an issue in WebKit. This is only recorded when there is an error. + + + + + ajuma@chromium.org + gambard@chromium.org + + [iOS] Records the action take when the backForwardList of the WebView is out + of sync with the URL exposed by the WebView when starting a new provisional + navigation. The URLs can get out of sync because of a bugs in WebKit. This + is only recorded when the URLs are out of sync. + + + + + eugenebut@chromium.org + gambard@chromium.org + + [iOS] Report cache hit/miss for WKWebView cert verification. + CRWWKNavigationHandler has a cache of pending cert verification results to + avoid extra verifications when presenting SSL interstitial. This metric + helps to understand how often this cache miss happens. + + + + + mrefaat@chromium.org + + [iOS] Measures the proportion of external URL requests that originate from a + subframe without any user interaction (e.g. an advertisement contains an + iframe directed at the App Store). + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + A histogram tracking the time we spent showing blank text because a web font + wasn't available by the time we needed it. Measured once per @font-face that + ended up showing blank text. + + + + + hajimehoshi@chromium.org + kenjibaheux@chromium.org + kouhei@chromium.org + ksakamoto@chromium.org + + Recorded upon web fonts load. Counts the number of times web font is loaded + from cache (disk cache or memory cache), fetched over network, or served + from data URL. + + + + + kenjibaheux@chromium.org + xiaochengh@chromium.org + + The number of 'font-display: auto' web fonts whose display periods are + modified to 'swap' or 'failure' before a timeout to ensure a good LCP. This + is a diagnostic metric for feature AlignFontDisplayAutoTimeoutWithLCPGoal. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of under + 10KB. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 10KB-50KB. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 50KB-100KB. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of + 100KB-1MB. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time it takes for a webfont download to finish, for webfonts of over + 1MB. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The time taken for a webfont download that failed. Includes aborted + requests. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + The value of font-display @font-face descriptor. Counted only when + explicitly specified in the @font-face rule. + + + + + kenjibaheux@chromium.org + ksakamoto@chromium.org + + This metrics is logged when a page that use web fonts is loaded. The value + is whether we had to wait on at least one web font and ended up showing + blank text, or not. + + + + + yaoxia@chromium.org + shivanisha@chromium.org + + For each http cache transaction for a font in Google Fonts, record the cache + status. + + + + + ksakamoto@chromium.org + toyoshim@chromium.org + + The load limit state when the first disk-cache-only request fails by cache + miss, if WebFonts cache-aware timeout adaptation is enabled and applicable. + + + + + hajimehoshi@chromium.org + kenjibaheux@chromium.org + kouhei@chromium.org + ksakamoto@chromium.org + + Whether a locallly installed font is actually used when @font-face had local + sources. + + + + + zea@chromium.org + + Percentage of results that are present locally but are not returned by the + web history API call. Recorded every time a signed-in user visits the + chrome://history page and the results from the web history are received. + + + + + zea@chromium.org + + Whether getting the OAuth token was successful for a web history query. On + visits to the chrome://history page this token is obtained and then used to + get the user's synced web history. + + + + + zea@chromium.org + + HTTP Response code returned by the server when trying to fetch the OAuth + token for a web history query. + + + + + zea@chromium.org + + Whether the web history API call was successful. Every time a signed-in user + visits the chrome://history page this query is executed to get the user's + synced web history. If successful, the local and remote results are merged + and shown in the history page. + + + + + zea@chromium.org + + Time it took for the web history to reply. Recorded when the web history API + call triggered by visiting chrome://history receives the data, measuring how + much time it took for the server to reply. + + + + + droger@chromium.org + + Histogram for the format of decoded WebP images on iOS, as Chrome re-encodes + WebP images on that platform. + + + + + mgiuca@chromium.org + + Counts the number of calls to navigator.share. Includes both successful and + failed shares. + + + + + mgiuca@chromium.org + + Records the outcome of calls to navigator.share. This will not count any + calls that never complete (e.g., if the page closes while the picker is + open). Therefore, DO NOT look at the raw percentages of this histogram; + instead, compare these numbers with the WebShare.ApiCount.Share total. + + NOTE: At the moment, if the user cancels the picker, its recording will be + delayed, and possibly never recorded (https://crbug.com/636274), so that + will account for a discrepancy between ShareOutcome and ApiCount.Share. + + + + + estark@chromium.org + dullweber@chromium.org + + Tracks actions with the website setting (a.k.a. page info / origin info) + bubble, such as opening it up or clicking on the Connection tab. + + + + + mxcai@chromium.org + dominickn@chromium.org + + Tracks actions with the "All Sites" page in website settings for + builds older than M82. + + + + + jarrydg@chromium.org + mxcai@chromium.org + + Tracks actions with the "All Sites" page in website settings + starting in M82. + + + + + miguelg@chromium.org + finnur@chromium.org + + Count of how often a specific content type (permission) is changed using the + content settings menu. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + miguelg@chromium.org + finnur@chromium.org + + Count of how often a specific content type (permission) is set to 'Allowed' + using the content settings menu. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + miguelg@chromium.org + finnur@chromium.org + + Count of how often a specific content type (permission) is set to 'Ask' + using the content settings menu. + + + + + miguelg@chromium.org + finnur@chromium.org + + Count of how often a specific content type (permission) is set to 'Blocked' + using the content settings menu. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + miguelg@chromium.org + finnur@chromium.org + + Count of how often a specific content type (permission) is reset to the + default value using the content settings menu. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + timloh@chromium.org + + Count of how often a specific content type (permission) is changed to the + session only value using the content settings menu. This option only exists + for cookies. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Count of how often a specific content type (permission) is changed using the + Origin Info dialog. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Count of how often a specific content type (permission) is set to 'Allowed' + using the Origin Info dialog. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Count of how often a specific content type (permission) is set to 'Blocked' + using the Origin Info dialog. + + Note: The values of this metric collected for Chrome 49 (early 2016) are + innacurate and should not be trusted. crbug.com/589255. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Counts the number of WebSQL databases opened for secure vs insecure origins. + + + + + jackhou@chromium.org + + The success or failure of all extension installs from the webstore. This + includes those initiated by sync. + + + + + dbeam@chromium.org + URLs for which Chrome creates WebUIControllers. + + + + dschuyler@chromium.org + tbuckley@chromium.org + bettes@chromium.org + + Paths within chrome://settings visited. For evaluating popularity and + priorities for chrome://settings GUI. Note that this metric used to include + paths that were part of OS settings, but starting with M-81, this metric + only records browser settings paths. + + + + + collinbaker@chromium.org + dfried@chromium.org + + The WebUI tab strip is a more touch-friendly tab strip used in place of + Chrome's native tab strip in some cases. It can be opened and closed. This + records how a user closed it. + + + + + johntlee@chromium.org + dpapad@chromium.org + + The WebUI tab strip is a more touch-friendly tab strip used in place of + Chrome's native tab strip in some cases. This records how a user closed a + tab within the WebUI tab strip. + + + + + collinbaker@chromium.org + dfried@chromium.org + + The WebUI tab strip is a more touch-friendly tab strip used in place of + Chrome's native tab strip in some cases. It can be opened and closed. This + records how a user opened it. + + + + + collinbaker@chromium.org + dfried@chromium.org + + The WebUI tab strip is a more touch-friendly tab strip used in place of + Chrome's native tab strip in some cases. It can be opened and closed. This + records how long it was open when closing. + + + + + robliao@chromium.org + johntlee@chromium.org + + WebUI Tabstrip: Time from activating a tab from WebUI to receiving an + activation notification in WebUI. + + + + + robliao@chromium.org + johntlee@chromium.org + + WebUI Tabstrip: Time needed to create all of the tab elements at launch. + + + + + robliao@chromium.org + johntlee@chromium.org + + WebUI Tabstrip: Time from requesting the tab data to receiving the data. + + + + + + + reillyg@chromium.org + juncai@chromium.org + + Records the reason why the WebUSB device chooser was closed. + + + + + + + reillyg@chromium.org + juncai@chromium.org + + Records the reason why the "WebUSB device detected" notification + was dismissed. + + + + + + + reillyg@chromium.org + juncai@chromium.org + + Records when the user revokes permission for an origin to connect to a USB + device using the WebUSB API. + + + + + changwan@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + Records calls to WebView APIs in WebViewChromium. + + + + tmartino@chromium.org + msarda@chromium.org + droger@chromium.org + chrome-signin-team@google.com + + Records the result of promoting sign-in via the Welcome page. + + + + + tmartino@chromium.org + + Records whether or not Chrome was the default browser when the user left the + Win10-specific Welcome page. + + + + + pmonette@chromium.org + tmartino@chromium.org + + Emits a "true" sample when the revamped WebUI-based welcome page + is added to the startup tabs list. This means that barring an error on + startup, it was shown to the user. This histogram can only be recorded + during first-run flow, when the EnableWelcomeWin10 experiment is enabled. + + + + + pmonette@chromium.org + tmartino@chromium.org + + Emits a "true" sample when the old external welcome page is added + to the startup tabs list. This means that barring an error on startup, it + was shown to the user. This histogram can only be recorded during first-run + flow, when the EnableWelcomeWin10 experiment is disabled. + + + + + pmonette@chromium.org + tmartino@chromium.org + + Records whether or not the check that verifies if Chrome is pinned to the + taskbar has timed out. This check is done when the welcome page is opened in + order to determine which instructions to display to the user. + + + + + tmartino@chromium.org + + Records whether or not Chrome was pinned to the taskbar when the user left + the Win10-specific Welcome page. + + + + + sahel@chromium.org + + Records whether or not a GSU event with wheel source is latched to the + current scrolling element. It is false for the first GSU event of every + scrolling sequence and true for the rest of the GSU events. + + + + + zturner@chromium.org + + Count of page loads in each of the 2 different environments (metro/desktop) + on Windows 8. + + + + + kuscher@chromium.org + + The number of app windows open when a load completes. This includes windows + opened by an app shortcut, or apps opened in a popup. This only counts v1 + apps. + + + + + kuscher@chromium.org + + The number of popup windows open when a load completes. Popup windows only + have one content area (no multiple tabs) and a stripped down toolbar + consisting only of a read-only address bar. + + + + + kuscher@chromium.org + + The number of tabbed windows open when a load completes. A tabbed window is + a normal browser window which can have one or more tabs. + + + + + davidbienvenu@chromium.org + fdoray@chromium.org + + A top level window's occlusion state. Recorded each time the state changes. + + + + + noms@chromium.org + The type of category clicked in the Windows Jumplist + + + + nhiroki@chromium.org + chrome-worker@google.com + Records the exit code of WorkerThread. + + + + ainslie@chromium.org + edwardjung@chromium.org + Number of times that each menu item is clicked. + + + + rpop@chromium.org + + The number of times each tab or window restore option in the Recent Tabs + submenu is clicked. + + + + + ainslie@chromium.org + edwardjung@chromium.org + + The time a user takes to select a menu item after opening the menu. + + + + + kkimlabs@chromium.org + + Time difference between touch down and touch up on Android wrench button. + + + + + huangdarwin@chromium.org + src/ui/base/clipboard/OWNERS + + Counts how often the X11 server fails to register an atom. Recorded when + ::XInternAtom fails (returns None). Failure rates will inform whether we + implement error handling. https://crbug.com/1000919 + + + + + panicker@chromium.org + + Records occurence of async XHR during page dismissal state (unload, + beforeunload, pagehide etc). + + + + + foolip@chromium.org + + Records the time spent in sync XHR requests on the main thread. + + + + + foolip@chromium.org + + Records the time spent in sync XHR requests in a worker thread. + + + + + panicker@chromium.org + + Records occurence of sync XHR during page dismissal state (unload, + beforeunload, pagehide etc). + + + + + kdillon@chromium.org + panicker@chromium.org + + Records occurence of sync XHR requests during page dismissal state (unload, + beforeunload, pagehide etc) that were forbidden. + + + + + alcooper@chromium.org + mlamouri@google.com + xr-dev@chromium.org + + Indicates which XR runtime was used for a session. Recorded when the session + was successfully created. + + + + + alcooper@chromium.org + xr-dev@chromium.org + + Records which reference space was requested when a site calls + XRSession.requestReferenceSpace(). + + + + + alcooper@chromium.org + xr-dev@chromium.org + + Records which reference spaces are successfully created when the promise + returned by XRSession.requestReferenceSpace() is resolved. + + + + + hfung@chromium.org + + The number of results (either query or URL) from ZeroSuggest. This is set + every time a successful response from ZeroSuggest is received, which can be + every time the user focuses on the omnibox. + + + + + hfung@chromium.org + + The number of query results returned from ZeroSuggest. This is set every + time a successful response from ZeroSuggest is received, which can be every + time the user focuses on the omnibox. + + + + + hfung@chromium.org + + The number of URL results returned from ZeroSuggest. This is set every time + a successful response from ZeroSuggest is received, which can be every time + the user focuses on the omnibox. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/page/histograms.xml b/tools/metrics/histograms/histograms_xml/page/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..2feab92cbe6c68abf19c0fef80857e83bc5e8459 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/page/histograms.xml @@ -0,0 +1,2240 @@ + + + + + + + + + + rdevlin.cronin@chromium.org + extensions-core@chromium.org + + The number of Extensions that have Page Actions. Measured once per startup + per profile. + + + + + jkarlin@chromium.org + johnidel@chromium.org + + Records the time from frame navigation start to FirstContentfulPaint of each + ad frame that receives a FirstContentfulPaint. The time could be quite + large, as some ads don't paint until they're scrolled into view. But the + metric is still useful in aggregate. + + Recorded for all ad frames with non-zero bytes or cpu usage that receive a + FirstContentfulPaint. Recorded when the ad frame or page is destroyed. + + + + + altimin@chromium.org + bmcquade@chromium.org + hajimehoshi@chromium.org + + Counts the events related to the back-forward cache, like when the page is + put into the back-forward cache. + + + + + jkarlin@chromium.org + johnidel@chromium.org + + Only recorded if the page has at least one identified ad frame. Recorded in + PageLoadMetrics when the page is destroyed. Bytes include all bytes used by + the network to load a resource and response body bytes for cached resources + (from both the HTTP and memory caches). An ad frame consists of the + identified ad frame and all of its children (which may also be ads, but are + counted as part of the ancestor ad frame). Includes resources that did not + finish loading. + + + + + justinmron@chromium.org + johnidel@chromium.org + + The page's maximum ad density by area over its lifecycle as a percent from + 0-100. The density measurement is throttled in page load metrics propagation + from renderer to browser and in the ads page load metrics observer, this may + lead to inaccurate maximum density. Recorded at the time a page is + destroyed. + + + + + justinmron@chromium.org + johnidel@chromium.org + + The page's maximum ad density by height over its lifecycle as a percent from + 0-100. The density measurement is throttled in page load metrics propagation + from renderer to browser and in the ads page load metrics observer, this may + lead to inaccurate maximum density. Recorded at the time a page is + destroyed. + + + + + justinmron@chromium.org + johnidel@chromium.org + + Whether the ad density was recorded on the page for both density by area and + density by height. Recorded at the time a page is destroyed. + + + + + alexmt@chromium.org + johnidel@chromium.org + + Total number of network bytes that went towards loading non-ad resources for + a single page over its entire lifetime. This includes resources that did not + finish or were canceled. Only recorded for pages with non-zero total bytes, + including those without an ad frame and pages with no ad resources. Recorded + when the page is destroyed. + + + + + alexmt@chromium.org + johnidel@chromium.org + + The percentage of network bytes loaded by the page that are attributed to ad + resources (including ad resources in the main frame) across the entire page + load. Only recorded for pages with non-zero network bytes, including those + without an ad frame and pages with no ad resources. Recorded when the page + is destroyed. + + + + + alexmt@chromium.org + johnidel@chromium.org + + The percentage of all bytes loaded by the page that are attributed to ad + resources (including ad resources in the main frame) across the entire page + load. Only recorded for pages with non-zero total bytes, including those + without an ad frame and pages with no ad resources. Recorded when the page + is destroyed. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records whether a frame that was created by ad script was ignored by + restricted AdTagging heuristics. This can occur if the frame was navigated + same-domain to the top-level page and did not have a matching blocklist + rule, or if the frame was navigated to an allowlist rule. If a frame is + initially ignored then later considered an ad, this is recorded twice for + that frame. For ignored frames, this is recorded at the time they would have + been initially tracked for metrics. For non-ignored frames, this is recorded + when the frame is destroyed, or when the page is destroyed/navigated. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records whether the heavy ad intervention was disallowed by the blocklist on + a frame. Only recorded when the heavy ad blocklist is enabled and available + (e.g. this is not recorded in incognito mode). + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records whether a heavy ad frame was deleted prior to the page being + destroyed/navigated. Recorded per-frame, only if the frame is considered a + heavy ad, when the frame is destroyed. For example, this is true if the + iframe element is deleted by javascript. This is recorded whether or not the + ads are actually unloaded by the intervention. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records whether a possible intervention was ignored because the page was the + result of a reload. This is checked prior to checking whether a given site + is blocklisted. Therefore it is possible this histogram records |Ignored| + when the intervention wouldn't have actually triggered. This is recorded + when an ad frame becomes eligible for the heavy ad intervention to unload + it. + + + + + johnidel@chromium.org + justinmiron@google.com + + Records the number of network bytes used by a heavy ad unloaded due to + network usage by the heavy ad intervention. It is recorded at the time of + unload and the value may be larger than the heavy ads threshold due to the + delay in unloading an ad. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records whether a page with a heavy ad is reloaded or navigated/destroyed + for any other reason. Only recorded for pages that had at least one heavy ad + prior to being navigated/reloaded/destroyed. This is recorded whether or not + the ads are actually unloaded by the intervention. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Total number of network bytes that went towards loading ad resources for a + single page over it's entire lifetime. This includes resources that did not + finish or were canceled. Only recorded for pages with non-zero ad bytes. + + + + + bmcquade@chromium.org + + The time from the user input that triggers the top-level navigation for an + AMP document to the time that the navigation for the AMP document is + initiated in the AMP frame. This gives insight into how often AMP documents + are navigated to via same document navigations without being prerendered. + + + + + bmcquade@chromium.org + + The time from the main frame navigation to the subsequent subframe + navigation for the AMP document. Only recorded for non-same-page + navigations. + + + + + bmcquade@chromium.org + + The time from navigation in the AMP frame to the user input that triggers + the top-level navigation for that AMP document. This gives insight into the + delta between when an AMP frame is prerendered and when it is actually + displayed for same document navigations. + + + + + bmcquade@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation, in an AMP subframe document. Recorded on first page + interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes + scrolls. Only same-document navigations are included. + + + + + bmcquade@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation, in an AMP subframe document. Recorded on first page + interaction. See https://goo.gl/tr1oTZ for a detailed explanation. Excludes + scrolls. Only non-same-document navigations are included. + + + + + bmcquade@chromium.org + skobes@chromium.org + + Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has + occurred in the AMP subframe. Recorded for same-document AMP navigations in + the main frame, at the end of the AMP document lifetime, such as when the + document is being navigated away from. + + + + + bmcquade@chromium.org + skobes@chromium.org + + Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has + occurred in the AMP subframe. Recorded for non same-document AMP navigations + in the main frame, at the end of the AMP document lifetime, such as when the + document is being navigated away from. + + + + + bmcquade@chromium.org + + The time from user input to first "contentful" paint in an AMP + subframe document. Will be zero or near-zero in cases where the AMP subframe + document was prerendered. Only same-document navigations are included. + + + + + bmcquade@chromium.org + + The time from user input to first "contentful" paint in an AMP + subframe document. Only non-same-document navigations are included. + + + + + bmcquade@chromium.org + + The time from user input to largest "contentful" paint in an AMP + subframe document. Only same-document navigations are included. + + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + Will be zero or near-zero in cases where the AMP subframe document was + prerendered. + + + + + bmcquade@chromium.org + + The time from user input to largest "contentful" paint in an AMP + subframe document. Only non-same-document navigations are included. + + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + + + + bmcquade@chromium.org + + Counts the number of pages where a script loaded via document.write could + have been blocked. + + + + + shivanisha@chromium.org + bmcquade@chromium.org + jkarlin@chromium.org + + This metric measures the counts of pages for various loading behaviors of + document.written scripts. + + + + + shivanisha@chromium.org + bmcquade@chromium.org + + This metric measures reloads in pages that have synchronous, cross-origin + document.written scripts that could be blocked if document.write script + blocking feature is enabled. + + + + + tbansal@chromium.org + + Records if the time from navigation to first contentful paint was less than + the specified threshold. Also, records the total number of first contentful + paints. For a single first contentful paint event, data may be recorded in + multiple buckets. Recorded at the time when first contentful paint happens. + Recorded only for page loads that have scheme http://. + + + + + dougarnett@chromium.org + tbansal@chromium.org + + Records if the time from navigation to first contentful paint was less than + the specified threshold. Also, records the total number of first contentful + paints. For a single first contentful paint event, data may be recorded in + multiple buckets. Recorded at the time when first contentful paint happens. + Recorded only for page loads that have scheme http://, are user-initiated, + and are new navigations (that is, they are not reloads nor forward or back + navigations). + + + + + tbansal@chromium.org + + Records if the time from navigation to first contentful paint was less than + the specified threshold. Also, records the total number of first contentful + paints. For a single first contentful paint event, data may be recorded in + multiple buckets. Recorded at the time when first contentful paint happens. + Recorded only for page loads that have scheme https://. + + + + + dougarnett@chromium.org + tbansal@chromium.org + + Records if the time from navigation to first contentful paint was less than + the specified threshold. Also, records the total number of first contentful + paints. For a single first contentful paint event, data may be recorded in + multiple buckets. Recorded at the time when first contentful paint happens. + Recorded only for page loads that have scheme https://, are user-initiated, + and are new navigations (that is, they are not reloads nor forward or back + navigations). + + + + + falken@chromium.org + + The core transition type for main frame page loads controlled by a service + worker that has a fetch event handler. + + + + + dtapuska@chromium.org + kenjibaheux@google.com + + Measures the time from navigation start to first contentful paint. Recorded + for pages that contain a resource that may benefit from stale while + revalidate. + + + + + dtapuska@chromium.org + kenjibaheux@google.com + + Measures the time from parse start to first contentful paint. Recorded for + pages that contain a resource that may benefit from stale while revalidate. + + + + + robertogden@chromium.org + tbansal@chromium.org + + How long the query to the cookie manager took to complete. Recorded on every + query response. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The number of days since any origin in the redirect chain was last visited, + according to the history service. Recorded whenever there was a previous + visit to record. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Whether or not there was a previous visit to any origin in the redirect + chain, as reported by the history service. Each positive entry corresponds + to a single entry in + "PageLoad.Clients.SubresourceLoading.DaysSinceLastVisitToOrigin". + Recorded on page end for every committed page load. + + + + + robertogden@chromium.org + tbansal@chromium.org + + How long the query to the history service took to complete. Recorded on + every query response. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The count of CSS or JS subresources on a page that were loaded from cache + before FCP occurred. Only recorded for Lite mode (AKA Data Saver) users. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The count of CSS or JS subresources on a page that were loaded from the + network before FCP occurred. Only recorded for Lite mode (AKA Data Saver) + users. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Whether or not any main frame request in the redirect chain had cookies. + + + + + jkarlin@chromium.org + johnidel@chromium.org + + The time from navigation start to the first contentful paint of third-party + (in respect to scheme://eTLD+1) frames on pages. Note that this can be + significantly delayed due to lazy loading. + + + + + jkarlin@chromium.org + yaoxia@chromium.org + + The number of third party (in respect to scheme://eTLD+1) origins on a page + that read cookies either via resource request headers or document.cookie. + + + + + jkarlin@chromium.org + yaoxia@chromium.org + + The number of third party (in respect to scheme://eTLD+1) origins on a page + that changed cookies either via resource response headers or + document.cookie. + + + + + yaoxia@chromium.org + jkarlin@chromium.org + + The number of third-parties (in respect to scheme://eTLD+1) on a page that + access local storage via window.localStorage. + + + + + yaoxia@chromium.org + jkarlin@chromium.org + + The number of third-parties (in respect to scheme://eTLD+1) on a page that + access session storage via window.sessionStorage. + + + + + shivanisha@chromium.org + jkarlin@chromium.org + + Records the largest contentful paint only for pages that load a third party + font and whose largest contentful resource type is text. See + PageLoad.PaintTiming.NavigationToLargestContentfulPaint for details. + + + + + ericrobinson@chromium.org + csharrison@chromium.org + + Only recorded if the page has at least one identified ad frame. Recorded in + PageLoadMetrics when the page is destroyed. Cpu measures the wall time of + tasks attributable to a frame as reported by the MainThreadTaskScheduler as + well as time spent servicing scripted animations by each document (not + attributable by the MainThreadTaskScheduler). An ad frame consists of the + identified ad frame and all of its children (which may also be ads, but are + counted as part of the ancestor ad frame). Includes resources that did not + finish loading. Does not consider time while a page is backgrounded. + + + + + alexmt@chromium.org + johnidel@chromium.org + + Recorded when the page is destroyed or the app is backgrounded on mobile. + Records the total wall time of tasks attributable to the page across its + lifetime. Considers both the CPU usage while the page is in the foreground + and in the background. + + + + + alexmt@chromium.org + johnidel@chromium.org + + Recorded when the page is destroyed or the app is backgrounded on mobile. + Records the total wall time of tasks attributable to the page across its + lifetime. Does not consider CPU usage while a page is backgrounded. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + DOMContentLoaded event is fired, for main frame documents. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + load event is fired, for main frame documents. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted due to being backgrounded. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by the user closing the tab or browser. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a forward or back navigation. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a new navigation. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted. The abort cause is unknown. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by a reload. + + + + + csharrison@chromium.org + + This metric is still experimental and not yet ready to be relied upon. + Measures the time from navigation start to the time the page load was + aborted by the user pressing stop. + + + + + jkarlin@chromium.org + johnidel@chromium.org + + The number of prefiltered (e.g., compressed) response body KiloBytes loaded + from the cache via the browser process for a page load. Recorded when the + page load is terminated. Only recorded for complete resources. Includes + resources from both the http cache and memory cache. + + + + + jkarlin@chromium.org + + The number of prefiltered (e.g., compressed) response body KiloBytes loaded + over the network via the browser process for a page load. Does not include + any header or overhead bytes. Recorded when the page load is terminated. + Only recorded for complete resources. + + + + + jkarlin@chromium.org + + The number of prefiltered (e.g., compressed) KiloBytes loaded over the + network via the browser process for a page load. This includes network + headers/overhead. Recorded when the page load is terminated. Recorded for + incomplete resources. + + + + + jkarlin@chromium.org + johnidel@chromium.org + + The number of prefiltered (e.g., compressed) response body KiloBytes loaded + via the browser process for a page load. Does not include any header or + overhead bytes. Recorded when the page load is terminated. Only recorded for + complete resources. Includes resources from both the http and memory cache. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Total number of network bytes that were used to load resources that did not + finish loading on the page (e.g. ongoing video). This includes resource + loads that were canceled or resource loads that were ongoing when the page + was destroyed. + + + + + dougarnett@chromium.org + tbansal@chromium.org + tdresser@chromium.org + + The maximum size click input burst for the page load. A click input burst is + a sequence of user click inputs at approximately the same screen position + where the clicks each occur soon after the previous one (e.g., within half + second). This is intended to detect possible rage clicks by the user. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + The number of completed resources loaded from the cache via the browser + process for a page load. Recorded when the page load is terminated. Includes + resources from both the http and memory cache. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + The number of completed resources loaded from the network via the browser + process for a page load. Recorded when the page load is terminated. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + The total number of completed resources loaded via the browser process for a + page load. Recorded when the page load is terminated. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the headers of the 103 Early Hints response is + received in reply to the final HTTP request and when the headers of the + final HTTP response is received for the main resource of a main frame + navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the final HTTP request is sent and when the + headers of the 103 Early Hints response is received in reply to the request + for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the first HTTP request is sent and when the + headers of the 103 Early Hints response is received in reply to the request + for the main resource of a main frame navigation. + + + + + sullivan@chromium.org + tdresser@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the navigation actually starting. + + + + + sullivan@chromium.org + tdresser@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the navigation actually starting, for background loads. + + + + + sullivan@chromium.org + tdresser@chromium.org + + The time between the OS-level click/tap event and navigation start, for + clicks on links in the renderer. + + + + + sullivan@chromium.org + tdresser@chromium.org + + The time between the OS-level keypress/tap event in the omnibox and + navigation start, for navigations from the omnibox. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when a callback for the navigation loader is last + invoked and when navigation commit message is sent to a renderer process for + the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the final HTTP request is sent and when the + headers of the final HTTP response is received for the main resource of a + main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the headers of the final HTTP response is received + and when a callback for the navigation loader is last invoked for the main + resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the first HTTP request is sent and when the + headers of the first HTTP response is received for the main resource of a + main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The interval between when the headers of the first HTTP response is received + and when a callback for the navigation loader is first invoked for the main + resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that a callback for the navigation + loader is last invoked for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that the final HTTP request is sent + for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that the headers of the final HTTP + response is received for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that a callback for the navigation + loader is first invoked for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that the first HTTP request is sent + for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that the headers of the first HTTP + response is received for the main resource of a main frame navigation. + + + + + nhiroki@chromium.org + chrome-loading@google.com + + The time relative to navigation start that navigation commit message for a + main frame navigation is sent to a renderer process. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + Determines the PageLoadType for this page load. That is, records whether the + page was never foregrounded, was foregrounded but did not reach FCP, or did + reach FCP. The metric is recorded at the end of each page load. As usual + with PageLoad metrics, we consider app backgrounding on Android to be the + end of page load as well as the app could be evicted by Android anytime + after that happens. + + + + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + + Records whether the First Meaningful Paint metric was reported for the page + load, or why it wasn't if not. See http://bit.ly/ttfmp-doc for the + definition of First Meaningful Paint. + + + + + sullivan@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the first contentful paint of the page that was loaded in the navigation. + + + + + sullivan@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the first contentful paint of the page that was loaded in the navigation, + for background loads. + + + + + sullivan@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the first paint of the page that was loaded in the navigation. + + + + + sullivan@chromium.org + + The time between the OS-level input event that initiated a navigation, and + the first paint of the page that was loaded in the navigation, for + background loads. + + + + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the first + meaningful paint (http://bit.ly/ttfmp-doc), for main frame documents. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from when the HTML parser started, to the first meaningful + paint (http://bit.ly/ttfmp-doc), for main frame documents. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + The total amount of time the page spent in the foreground. Note that this + metric adds all foreground durations occurring for the page. For example: if + the page starts foregrounded during 1 second, then goes to the background + for a while, then is foregrounded again for 2 seconds, and then is unloaded, + this metric reports 3 seconds. The metric is recorded at the end of each + page load. As usual with PageLoad metrics, we consider app backgrounding on + Android to be the end of page load as well as the app could be evicted by + Android anytime after that happens. + + + + + cammie@chromium.org + jkarlin@chromium.org + + For each identified ad frame, whether the origin of the ad creative frame + matches or differs from the origin of the main frame. + + The ad creative frame is heuristically determined, from among an identified + ad frame and all of its children, as the first of these frames to record a + First Contentful Paint. If no FCP is recorded, the creative origin status is + marked as indeterminate. + + + + + cammie@chromium.org + jkarlin@chromium.org + + For each identified ad frame, whether the origin of the ad creative frame + matches or differs from the origin of the main frame, further split by + whether the frame has lifecycle updates throttled. Metric is emitted on + frame deletion. + + The ad creative frame is heuristically determined, from among an identified + ad frame and all of its children, as the first of these frames to record a + First Contentful Paint. If no FCP is recorded, the creative origin status is + marked as indeterminate. Frames that are render-throttled will not have an + FCP. Ad frames with indeterminate creative origin status are broken out as + throttled or not. + + + + + ericrobinson@chromium.org + + For each identified ad frame, whether the origin of the ad matches the + origin of the main frame, differs from the origin of the main frame, or is + indeterminable. + + An ad frame consists of the identified ad frame and all of its children + (which may also be ads, but are counted as part of the ancestor ad frame). + Frames of zero bytes (e.g., never had a document or their document was + doc.written and no sub-resources were loaded) are not counted. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + The square root of the area of a root adframe in pixels. Only recorded for + ad frames with non-zero total bytes. Recorded when the page is destroyed or + navigated. Display none iframes will not always update their size because + they lack a content view. This uses the last size of frame before it was set + to display: none. + + + + + johnidel@chromium.org + csharrison@chromium.org + + For each identified ad frame, whether the sticky user activation bit was + ever set on the frame. Recorded for each ad frame when the page is destroyed + or navigated away from, including ad frames that no longer exist. + + An ad frame consists of the identified ad frame and all of its children + (which may also be ads, but are counted as part of the ancestor ad frame). + Frames of zero bytes (e.g., never had a document or their document was + doc.written and no sub-resources were loaded) are not counted. + + + + + jkarlin@chromium.org + + The number of frames on the page that have loaded more than 0 bytes of + content or had non-zero CPU usage. + + For pages with zero ad frames, the other PageLoad.Clients.Ads metrics are + not recorded unless otherwise specified. This metric is not recorded on + sites where the subresource filter is enabled. + + Child frames of an ad frame are not included in the count. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records heavy ad type for each ad frame, as determined by the first + threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of + feature flag or other conditions that prevent the heavy ad intervention from + occuring. Recored for all ad frames with non-zero bytes. Recorded when the + ad frame destroyed or when the page is destroyed. + + It is possible for multiple thresholds to be hit at the same time, with the + higher valued enums winning those race conditions. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records heavy ad type for each ad frame, as determined by the first + threshold hit (see FrameData::HeavyadStatus). This is recorded regardless of + feature flag or other conditions that prevent the heavy ad intervention from + occuring. This includes 1 megabyte of random additive noise on the network + threshold. As such, it is possible for this histogram to record different + values for the same frame than PageLoad.HeavyAds.ComputedType2. + + Recored for all ad frames with non-zero bytes. Recorded when the ad frame + destroyed or when the page is destroyed. + + It is possible for multiple thresholds to be hit at the same time, with the + higher valued enums winning those race conditions. + + + + + johnidel@chromium.org + jkarlin@chromium.org + + Records the type of heavy ad unloaded by the heavy ad intervention. Heavy ad + type is determined by the first threshold hit. This is not recorded for ad + frames that are considered heavy but did not fufill other criteria for the + intervention. This includes the feature being enabled and being below the + per-origin intervention cap. + + It is possible for multiple thresholds to be hit at the same time, with the + higher valued enums winning those race conditions. + + + + + tdresser@chromium.org + + Measures the time to first non-scroll input after the first paint. + + + + + tdresser@chromium.org + input-dev@chromium.org + + Measures the time to first scroll input after the first paint. + + + + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + speed-metrics-dev@chromium.org + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per back-forward navigation. Recorded on first page interaction after + the page is restored from the back-forward cache. See https://goo.gl/tr1oTZ + for a detailed explanation. Excludes scrolls. + + + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + Measures First Input Delay, the duration between the hardware timestamp and + the start of event processing on the main thread for the first meaningful + input per navigation. Recorded on first page interaction. See + https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + Log of major changes: http://bit.ly/chrome-speed-metrics-changelog + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + first meaningful input per navigation. Recorded on first page interaction. + See https://goo.gl/tr1oTZ for a detailed explanation. Excludes scrolls. + + + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + The duration between the hardware timestamp and the start of event + processing on the main thread for a meaningful input. Excludes scrolls. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + WARNING: The long tail of this metric is buggy on Mac (overflows for a + subset of users) which can lead to surprising false regressions or + improvements. + + + + + + + sullivan@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of a + meaningful input. Excludes scrolls. + + + + + sullivan@chromium.org + speed-metrics-dev@chromium.org + + Measures longest Input Delay, the longest duration between the hardware + timestamp and the start of event processing on the main thread for the + meaningful input per navigation. Excludes scrolls. + + + + + sullivan@chromium.org + speed-metrics-dev@chromium.org + + The duration between navigation start and the hardware timestamp of the + meaningful input with longest queuing delay per navigation. Excludes + scrolls. + + + + + bmcquade@chromium.org + + The delay between first paint and a client-side redirect navigation, for + pages that reported a first paint. This metric is only intended to help in + choosing a heuristic delay to distinguish between client-side redirects and + other client initiated navigations, and will be deprecated in M54. Please + contact bmcquade@chromium.org before using this metric. + + + + + bmcquade@chromium.org + + Counts how often a client-side redirect was initiated from a page that did + not report a first paint. This metric is only intended to help in choosing a + heuristic delay to distinguish between client-side redirects and other + client initiated navigations, and will be deprecated in M54. Please contact + bmcquade@chromium.org before using this metric. + + + + + csharrison@chromium.org + bmcquade@chromium.org + + Counts of various internal error conditions in the page_load_metrics system. + + + + + bmcquade@chromium.org + Whether a navigation started in the foreground. + + + + bmcquade@chromium.org + + The difference in magnitude between existing and updated timing, for + inter-frame timings that are received out of order. Page load metrics + observes timing updates in all frames on a page. It's possible for timings + in different frames to arrive out of order. This metric tracks how often + this happens, along with the magnitude of the difference. + + + + + bmcquade@chromium.org + + Whether a page load completed after the app entered the background. We log a + 'Started' value for each PageLoadTracker that is active when the app enters + the background, and a 'Completed' value for each of those PageLoadTrackers + that successfully runs its destructor. This helps to understand how many + trackers are destroyed while the app is in the background before they are + able to run their destructor. This metric is only intended to help in + understanding how often app background leads to data loss, and will be + deprecated in a subsequent release. Please contact bmcquade@chromium.org + before using this metric. + + + + + bmcquade@chromium.org + + The status of PageLoadTiming structs received from the render process over + IPC. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest contentful paint, whose timestamp is measured + by PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint, + comes from text or image. This value is recorded whenever + PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint is + recorded. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest content paint in the main frame, whose + timestamp is measured by + PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint.MainFrame, + comes from text or image. This value is recorded whenever + PageLoad.PaintTiming.NavigationToExperimentalLargestContentfulPaint.MainFrame + is recorded. + + + + + maxlg@chromium.org + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest contentful paint, whose timestamp is measured + by PageLoad.PaintTiming.NavigationToLargestContentfulPaint, comes from text + or image. This value is recorded whenever + PageLoad.PaintTiming.NavigationToLargestContentfulPaint is recorded. + + + + + maxlg@chromium.org + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures whether the largest content paint in the main frame, whose + timestamp is measured by + PageLoad.PaintTiming.NavigationToLargestContentPaint.MainFrame, comes from + text or image. This value is recorded whenever + PageLoad.PaintTiming.NavigationToLargestContentfulPaint.MainFrame is + recorded. + + + + + sullivan@chromium.org + + Breakdown of NavigationToFirstContentfulPaint counts by process that + initiated the navigation (this will only be renderer or browser). + + + + + bmcquade@chromium.org + + Counts the number of prerender navigations. Only logs true values. + + + + + csharrison@chromium.org + + This histogram counts the number of provisional loads aborted by other + navigations, until a final forward back navigation commits. + + + + + csharrison@chromium.org + + This histogram counts the number of provisional loads aborted by new + navigations, until a final new navigation commits. + + + + + csharrison@chromium.org + + This histogram counts the number of provisional loads aborted by new + navigations. In this case the chain never ends with a commit. This is logged + on the next abort signal comes in (e.g. tab close or new navigation). + + + + + csharrison@chromium.org + + This histogram counts the number of provisional loads aborted by other + navigations, until a final reload navigation commits. + + + + + csharrison@chromium.org + + This histogram counts the number of consecutive provisional loads aborted by + other navigations with the same url (before redirects). It's logged when a + provisional abort does not share a URL, or when a load finally commits. Note + that we don't log chains of length 0. + + + + + panicker@chromium.org + + For first paint, first contentful paint, first meaningful paint, first text + paint, and first image paint, we use the swap timestamp of the corresponding + paint, which is the timestamp the CC SwapPromise was positively fulfilled + (i.e. DidSwap() was invoked). If the swap did not occur (DidNotSwap() was + invoked), we use the timestamp when the swap promise fails. However, in the + future we may stop reporting timestamps for certain failure reasons. This + metric records whether or not the swap occurred, and the reason for failure + if it failed. The distribution of this metric will help determine the effect + of not reporting timestamps in certain cases. + + + + + sadrul@chromium.org + + 'Swap time' is the timestamp of the renderer submitting a CompositorFrame, + and 'Presentation time' is the timestamp of the frame becoming visible on + screen. This metric measures the duration between the swap-time and the + presentation-time. This is recorded only if a valid presentation-timestamp + is available. See PageLoad.Internal.Renderer.PresentationTime.Valid for how + often the presentation-timestamp is valid. This is reported only for + compositor-frames that report a paint-timing metric (e.g. + FirstContentfulPaint etc.), and after that frame has been displayed on + screen. + + + + + sadrul@chromium.org + + This boolean keeps track of whether a valid presentation-timestamp was + received or not. This is reported only for compositor-frames that report a + paint-timing metric (e.g. FirstContentfulPaint etc.), and after that frame + has been displayed on screen. + + + + + bmcquade@chromium.org + skobes@chromium.org + + Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has + occurred on the page (including all subframes). Recorded at the end of the + page lifetime, such as when the page is being navigated away from or when a + tab is being closed. Stable since M79; previous versions are expermental and + subject to fluctuation between releases. + + Log of major changes: http://bit.ly/chrome-speed-metrics-changelog + + + + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Measures the cumulative layout shift score (bit.ly/3fQz29y) that has + occurred on the page (including all subframes) after the page is restored + from the back-forward cache. Recorded when the user navigates away or closes + the page after the page was restored from back-forward cache. + + + + + bmcquade@chromium.org + skobes@chromium.org + + Measures the cumulative layout shift score (bit.ly/lsm-explainer) that has + occurred in the main frame. Recorded at the end of the page lifetime, such + as when the page is being navigated away from or when a tab is being closed. + + + + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + + Measures the cumulative layout shift score (bit.ly/3fQz29y) that has + occurred in the main frame after the page is restored from the back-forward + cache. Recorded when the user navigates away or closes the page after the + page was restored from back-forward cache. + + + + + csharrison@chromium.org + + The number of URLs in the redirect chain for this navigation. This excludes + the first URL. + + + + + bmcquade@chromium.org + + For page loads that start in the foreground, measures the duration of time + until one of the following events occurs: the load of the main resource + fails, the page load is stopped, the tab hosting the page is closed, the + render process hosting the page goes away, a new navigation which later + commits is initiated in the same tab, or the tab hosting the page is + backgrounded. This metric has a very long tail, for pages that spend a long + period of time in the foreground. As such, use of the mean or tail values + are not recommended. + + + + + jkarlin@chromium.org + + The time since navigation start before the user presses the back button on a + page. Only measures page loads that remained in foreground and were created + by user gesture inside the renderer (as opposed to browser UX gestures). + + + + + bmcquade@chromium.org + shivanisha@chromium.org + + Measures the time from navigation timing's navigation start to the time the + provisional load failed. Only measures provisional loads that failed in the + foreground. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + user first foregrounds an initially backgrounded tab. Only measures + navigations that started in the background. + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from a background tab being switched to the foreground to + the time the first contentful paint is performed, for main frame documents. + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from a background tab being switched to the foreground to + the time the first paint is performed, for main frame documents. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, across all frames. See + PageLoad.PaintTiming.NavigationToLargestContentfulPaint for more + information. This experimental version includes content that has been + removed. + + + + + npm@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, for main frame documents. + See PageLoad.PaintTiming.NavigationToLargestContentfulPaint for more + information. This experimental version includes content that has been + removed. + + + + + + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + chrome-analysis-team@google.com + + The time from navigation start to first "contentful" paint. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. + + Log of major changes: http://bit.ly/chrome-speed-metrics-changelog + + + + + tdresser@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first image is painted, for main frame documents. For images that render + progressively, this is recorded as soon as any image pixels have been drawn. + + + + + ksakamoto@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + first paint is performed, for main frame documents. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + altimin@chromium.org + hajimehoshi@chromium.org + bfcache-dev@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from back-forward navigation timing's navigation start to + the time the first paint is performed, for main frame documents. Recorded + only when the page is restored from back-forward cache. + + Do not modify this metric in any way without contacting + speed-metrics-dev@chromium.org. + + + + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, across all frames. + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. Stable since M79; + previous versions are experimental and subject to fluctuation between + releases. + + Log of major changes: http://bit.ly/chrome-speed-metrics-changelog + + + + + maxlg@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from navigation timing's navigation start to the time the + largest content (text or image) is first painted, for main frame documents. + Excludes any content painted after user input. The value is recorded at the + end of each page load unless there is an abort or user input before text or + image paint. See http://bit.ly/fcp_plus_plus for details. + + + + + bmcquade@chromium.org + csharrison@chromium.org + speed-metrics-dev@chromium.org + + Measures the time from when the HTML parser started, to when the page first + paints content. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time from navigation timing's navigation start to the time the + parser started, for main frame documents. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the execution of + scripts, for main frame documents that finished parsing. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the execution of + scripts inserted from document.write, for main frame documents that finished + parsing. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts, + for main frame documents that finished parsing. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser spent blocked on the load of scripts + inserted from document.write, for main frame documents that finished + parsing. + + + + + bmcquade@chromium.org + csharrison@chromium.org + + Measures the time that the HTML parser was active, for main frame documents + that finished parsing. + + + + + panicker@chromium.org + + Tracks the transitions of the page between the various PageLifecycleStates: + active, hidden/backgrounded, hidden/foregrounded, and frozen. A page is + considered active if is visible. A page is considered backgrounded if not + visible and not currently providing a useful service, such as playing audio. + A page is considered foregrounded if it is not backgrounded. A page can be + frozen due to being hidden/backgrounded for a specified amount of time, or + frozen due to critical resources. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Total time the browser process waited for all render processes to save their + respective frames while saving a page into MHTML. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time the browser process waited on a single frame to be saved by a render + processes while saving a page into MHTML. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to encode into MTHML the fully serialized contents of a frame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sclittle@chromium.org + offline-dev@chromium.org + Final status of the MHTML save operation for a page. + + + + sclittle@chromium.org + offline-dev@chromium.org + Time taken to save a page into an MHTML file. + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time spent by the main threads of all involved render processes while saving + the frame tree of a page to MHTML. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time spent by the renderer main thread while saving one frame of a page to + MHTML. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + The longest time taken by the main thread of a render processes to save one + frame of a page being saved to MHTML. In other words this is the maximum + value reported in + PageSerialization.MhtmlGeneration.RendererMainThreadTime.SingleFrame for one + page save operation. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to fully serialize the contents of a frame, including HTML and + CSS and image resources. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time spent writing a frame's encoded MHTML data to the file or data pipe + handle passed to the Renderer, recorded when the writing is done and the + handle is closed. Note that when writing to a data pipe, this metric does + not precisely reflect the time taken to write the data to disk. + + + + + sclittle@chromium.org + offline-dev@chromium.org + Reports the result of an attempt to load an MHTML archive. + + + + dimich@chromium.org + + Percentage of loaded CSS elements in the main frame at the time of + serialization. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Percentage of loaded images in the main frame at the time of serialization. + + + + + dimich@chromium.org + + Total number of CSS elements in the main frame for serialization. + + + + + dimich@chromium.org + Total number of images in the main frame for serialization. + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time spent serializing a CSS element (including embedded "sub"-CSS + and images). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time taken to generate HTML data from a frame's DOM and serialize it + (without sub-resources like CSS and images). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + sclittle@chromium.org + offline-dev@chromium.org + + Time spent serializing an image element. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/password/histograms.xml b/tools/metrics/histograms/histograms_xml/password/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..d24e4a414346919a111ad141b5eedf16c15778b0 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/password/histograms.xml @@ -0,0 +1,2353 @@ + + + + + + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Whether the user proceeded to the list of the left compromised passwords + from the bubble following save/update password. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The state of the bubble shown after users saves/updates a password. It + notifies the user about leftover compromised passwords. + + + + + vasilii@chromium.org + + When the password management bubble opened, what state was it in? + + + + + jdoerrie@chromium.org + kolos@chromium.org + vasilii@chromium.org + + Measures the frequency of various password generation events. + + Note that this histogram is logged from the renderer process, and + consequently the numbers should not be directly compared to the other + PasswordGeneration.* histograms, which are logged from the browser process. + Histograms logged in different processes are lost at different rates, which + introduces systematic bias between histograms logged in the renderer process + vs. those logged in the browser process. + + + + + kolos@chromium.org + + Measures the frequency of user editing of generated passwords. Uploaded once + per generated password save. Applicable to automatic and manual generations. + + + + + kolos@chromium.org + + Measures the frequency of manually triggered password generations. + + + + + jdoerrie@chromium.org + kolos@chromium.org + + Measures the frequency of submission events for passwords that could have + been generated, but the user didn't choose to use the feature. This is to + compare with PasswordGeneration.SubmssionEvent. + + + + + jdoerrie@chromium.org + kolos@chromium.org + + Measures the frequency of submission events for generated passwords. This is + similar to PasswordManager.ActionsTakenWithPsl but only tracks events which + are interesting for generated passwords. + + + + + jdoerrie@chromium.org + kolos@chromium.org + vasilii@chromium.org + + The number of times that we try to upload a form that we believe should + trigger password generation. False means that something about the form would + not allow us to try upload (not an Autofillable field, uploading disabled, + Autofill servers in backoff, etc.). True does not mean that the upload + actually completed successfully, just that it was started. + + + + + ioanap@chromium.org + vasilii@chromium.org + + Records user-triggered events related to a generated password. Only the last + occurring event is logged. The recording takes place when the password form + is destroyed. + + + + + mlerman@chromium.org + + Time required to create the local hash of the user's GAIA password. + + + + + vasilii@chromium.org + src/components/password_manager/OWNERS + + Records attempts to prompt user to save a password when password store is + not ready for saving passwords due to an initialization error. Recorded once + per form submission. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The type of event that the Password Manager used for detecting a password + form submission when saving or updating a password. Recorded each time a + user accepts a password save/update prompt. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Recorded whenever the user accesses the passwords in the settings page. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The dismissal reason of the account chooser with multiple accounts. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The dismissal reason of the account chooser with one account. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The number of accounts stored per site in the password manager's + profile-scoped store. Records one event per site, split by whether created + by the user or generated by Chrome, and further by whether the user used + sync with custom passphrase or not. + + + + + mamir@chromium.org + treib@chromium.org + + Records whether the account-scoped password storage had to be cleared during + profile initialization. + + + + + mamir@chromium.org + treib@chromium.org + + Recorded whenever the opt-in for the account-scoped password storage is + cleared for all Google Accounts. This typically happens because the signin + cookies were cleared. The recorded value is the number of opt-ins that were + cleared. + + + + + treib@chromium.org + victorvianna@google.com + + When the user accepts to move a password from the profile store to the + account store, this records what user action caused the moving flow to be + offered. If the flow is offered but rejected by the user, the histogram is + not recorded. Recorded only in Win/Mac/Linux. + + + + + treib@chromium.org + victorvianna@google.com + + When the user is offered to move a password from the profile store to the + account store, this records what user action caused the moving flow to be + offered. Recorded only in Win/Mac/Linux. + + + + + mamir@chromium.org + treib@chromium.org + + Recorded whenever a user opts in to the account-scoped password storage. The + recorded value is the total number of opted-in accounts in this profile, + including the new opt-in. + + + + + mamir@chromium.org + treib@chromium.org + + Recorded whenever a user opts out of the account-scoped password storage. + The recorded value is the total number of opted-in accounts remaining in + this profile after the current opt-out. + + + + + treib@chromium.org + victorvianna@google.com + + Records whether a signed-in account was still found by the time Chrome + attempted to opt out the user of passwords account storage and clear the + associated settings. If no signed-in account is found, the opt-out and clean + up won't happen. Recorded only in Win/Mac/Linux, when opting out of the + account-scoped passwords storage. One example would be when the user clicks + the opt-out button in chrome://settings/passwords. + + + + + treib@chromium.org + victorvianna@google.com + + Records how many passwords in the account store were unsynced when the user + signed out of their Google Account. Recorded only in Win/Mac/Linux when a + user of the account-scoped password storage signs out. + + + + + + + mamir@chromium.org + treib@chromium.org + + The amount of active browsing time that was spent in different user states + related to the PasswordManager's account-scoped storage. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser (as determined by + DesktopSessionDurationTracker) or their user state changes. These end-points + are when the metric is emitted. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + + + + jdoerrie@chromium.org + mamir@chromium.org + treib@chromium.org + vasilii@chromium.org + + The number of accounts stored per site in the password manager's + account-scoped store. Records one event per site, split by whether created + by the user or generated by Chrome, and further by whether the user used + sync with custom passphrase or not. + + + + + jdoerrie@chromium.org + mamir@chromium.org + treib@chromium.org + vasilii@chromium.org + + The total number of sites that the user has blacklisted in the password + manager's account-scoped store. Recorded by iterating over stored passwords + once per run of Chrome. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + mamir@chromium.org + treib@chromium.org + + Number of password forms with empty username in the account-scoped Login + Database. This is recorded on startup. + + + + + vasilii@chromium.org + mamir@chromium.org + treib@chromium.org + + The number of saved passwords in the account-scoped store that could not be + decrypted. Recorded once for the profile on startup. + + + + + battre@chromium.org + jdoerrie@chromium.org + mamir@chromium.org + treib@chromium.org + + The number of times each saved password from the account-scoped storage has + been used to log in. Split by whether created by the user or generated by + Chrome, and further by whether the user used sync with custom passphrase or + not. Recorded by iterating over stored passwords once per browser run, soon + after startup. + + + + + battre@chromium.org + mamir@chromium.org + treib@chromium.org + vasilii@chromium.org + + The number of accounts stored in the password manager's account-scoped store + (across all sites), split by whether created by the user or generated by + Chrome, and further by whether the user used sync with custom passphrase or + not. + + + + + battre@chromium.org + mamir@chromium.org + treib@chromium.org + vasilii@chromium.org + + The number of accounts stored in the password manager's account-scoped store + (across all sites) for origins with the scheme (e.g., HTTP, HTTPS, FTP) as + given in the histogram suffix. For each scheme, the count is recorded once + per browser start-up. (In case of multiple profiles, the counts are for the + profile that first has a WebContents created.) + + + + + mamir@chromium.org + treib@chromium.org + + The number of accounts stored in the password manager's account-scoped store + that don't exist in the profile-scoped store. Recorded once per run of + Chrome, soon after startup. + + + + + mamir@chromium.org + treib@chromium.org + + The number of accounts stored in the password manager with a conflicting + password between the account-scoped store and profile-scoped store (i.e. the + signon realm and username match, but the password does not). Recorded once + per run of Chrome, soon after startup. + + + + + mamir@chromium.org + treib@chromium.org + + The number of accounts stored in both the password manager's account-scoped + store and profile-scoped store. Recorded once per run of Chrome, soon after + startup. + + + + + mamir@chromium.org + treib@chromium.org + + The number of accounts stored in the password manager's profile-scoped store + that don't exist in the account-scoped store. Recorded once per run of + Chrome, soon after startup. + + + + + engedy@chromium.org + + The number of facets for which affiliation information was requested in a + network fetch. Recorded for each network fetch. + + + + + engedy@chromium.org + + The time elapsed between creation of the AffiliationBackend and the first + time it needed to issue a network fetch. + + + + + engedy@chromium.org + + The elapsed time between subsequent network fetches. Recorded whenever the + AffiliationBackend initiated a network fetch, regardless of success or + failure. + + + + + engedy@chromium.org + + The network error code, as reported by the underlying URLFetcher. Recorded + only for each network fetch that failed due to network/server errors. + + + + + engedy@chromium.org + + The HTTP response code, as reported by the underlying URLFetcher. Recorded + only for each network fetch that failed due to network/server errors. + + + + + engedy@chromium.org + + Whether the network fetch succeeded, failed due to network/server errors, or + contained malformed data. Recorded for each network fetch. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a password credential entry in the preferences + on Android. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a password of a password credential entry in + the preferences on Android. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a username of a password credential entry in + the preferences on Android. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a website of a password credential entry on + Android. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a password exception entry in the preferences + on Android. + + + + + fhorschig@chromium.org + ioanap@chromium.org + + Records the action taken with a website of a password exception entry in the + preferences on Android. + + + + + mamir@chromium.org + mastiz@chromium.org + + Records different results upon adding a remote password to the password + manager. It is recorded every time after receiving remote password + incremental updates from the server. + + + + + mamir@chromium.org + mastiz@chromium.org + + Records different results upon updating a remote password to the password + manager. It is recorded every time after receiving remote password + incremental updates from the server. + + + + + mamir@chromium.org + mastiz@chromium.org + + Records different states upon applying remote sync changes to the password + manager. It recorded every time after receiving remote password incremental + updates from the server. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The dismissal reason of the auto-signin first run experience. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The total number of sites that the user has blacklisted. Recorded by + iterating over stored passwords once per run of Chrome. + + + + + battre@chromium.org + vasilii@chromium.org + + The number of accounts stored in password_manager::StatisticsTable. These + are accounts for which the user ignored the save bubble at least once. The + count is recorded once per browser start-up. (In case of multiple profiles, + the counts are for the profile that first has a WebContents created.) + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of credentials initially to be checked when the password bulk check + was canceled. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The time the password bulk check was running until canceled by the user. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of credentials analyzed when the password bulk check completed + successfully. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + Error encountered during the password bulk check. + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of leaked credentials found when the password bulk check completed. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Referrer of a navigation to the Password Check page. Recorded when the user + visits the Password Check settings page, either via native or Web UI. + + + + + ioanap@chromium.org + fhorschig@chromium.org + + Referrer of a navigation to the Password Check UI Settings view. Recorded + when the user enters the view. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The time it took for the password bulk check to complete successfully. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + The average time per credential when the password bulk check completed + successfully. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + User actions performed on the Password Check settings page. + + + + ioanap@chromium.org + fhorschigg@chromium.org + User actions performed on the Password Check settings view. + + + + kolos@chromium.org + + The time (ms) it takes to infer button titles within a form tag. + + + + + kolos@chromium.org + + The time (ms) it takes to infer button titles outside of form tags. + + + + + battre@chromium.org + jdoerrie@chromium.org + chrome-password-manager-team@google.com + + When the password manager sees new forms on the page, it records in this + histogram whether there were any SSL certificate errors. The presence of SSL + errors likely means that the password manger will stop working, so the + reporting is done at the last point when password manager is still + guaranteed to be active. Some particular errors are distinguished, with the + rest being reported in a catch-all bucket. + + + + + vakh@chromium.org + vasilii@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a password hash was saved or not on Chrome sign-in page. + Recorded whenever the user types a password on Chrome sign-in page. + + + + + vasilii@chromium.org + src/components/password_manager/OWNERS + + Collects positive number of undecryptable passwords that were successfully + deleted when syncing was enabled. Called for sync user for each profile if + there is at least one password deleted when merging logins from Sync and + local database. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Collects the type of compromised credential when it is added, updated, or + removed from the table. Compromised credentials are saved passwords that are + added when they are leaked or phished, updated when signon_realm and/or + username is changed, or removed when the password is dropped from the + password_manager or the password has changed. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of known leaked credentials in the database on start-up. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of known leaked credentials in the database on start-up if the + password bulk check was executed at least once. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Count of known phished credentials in the database on start-up. + + + + + fhorschig@chromium.org + mamir@chromium.org + + Records how many credentials from the account store are available to a user + right after they unlocked the account store. If a credential is an exact + duplicate with a local credential, it still counts into this metric. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The number of stored (non-blacklisted) credentials for which + "duplicates" exist. A duplicate is a credential with the same + signon realm, username, and password - i.e. indistinguishable from the + user's point of view. This records the number of *sets* of duplicated + credentials; the number of credentials in each set of duplicates is not + recorded. Recorded once per browser start-up. (In case of multiple profiles, + the counts are for the profile that first has a WebContents created.) + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The number of stored (non-blacklisted) credentials for which + "mismatched duplicates" exist. A mismatched duplicate is a + credential with the same signon realm and username, but different password. + This records the number of *sets* of duplicated credentials; the number of + credentials in each set of duplicates is not recorded. Recorded once per + browser start-up. (In case of multiple profiles, the counts are for the + profile that first has a WebContents created.) + + + + + mamir@chromium.org + treib@chromium.org + + The default store for newly-saved passwords (profile-scoped store or + account-scoped store), recorded whenever it is set explicitly. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Records the return value of the DeleteUndecryptableLogins method in the + LoginDatabase class. Called for sync user and for each profile when merging + logins from Sync and local database. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Records availability of password manager suggestions in regular and + off-the-record modes. + + + + + jdoerrie@chromium.org + battre@chromium.org + + Records a bitmask of password form changes after the first time this form is + seen by Password Manager. Recorded once per a form when the form is removed + from DOM. Bit 0 - changes in number of fields, bit 1 - changes in fields + renderer ids, bit 2 - changes in autocomplete attributes, bit 3 - changes in + form control types. + + + + + battre@chromium.org + vasilii@chromium.org + + Indication whether users change the credentials (username and password) in + the save bubble of the password manager, considering only cases where the + user saves a new credential or updates a credential. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Number of password forms with empty username in the profile-scoped Login + Database. This is recorded on startup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Indicates whether the password manager is enabled when a tab is opened. This + includes prerendered tabs. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Records number of rows in FieldInfoTable, which contains locally learned + predictions about field types. Recorded once for the profile on startup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + When a credential is filled, whether it comes from an Android app. + + + + + jdoerrie@chromium.org + battre@chromium.org + + This metric records the user experience with regards to passwords filling. + It is only recorded on password form submissions that are considered to be + successful. + + The first 4 buckets (0..3) are ranging from the best filling behavior + (automatic filling on page load without user interaction necessary) to the + worst (the user had to manually type a password that was already saved). + + The following buckets (4..5) indicate cases when it was impossible to fill + credentials because unknown credentials were submitted, meaning that the + submitted password was not saved before. + + The last bucket (6) corresponds to the strange cases, where the submitted + form has neither user input nor autofilled data in password fields. This + might indicate third-party password manager use, or might be a + measurement/submission classification error. + + + + + mamir@chromium.org + treib@chromium.org + + This metric records the source of filled passwords: The profile-scoped + store, the account-scoped store, both of them, or none of them (if the user + typed the password manually). It is only recorded on password form + submissions that are considered to be successful. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + When offering to fill the username and password, whether at least one of the + credentials in the dropdown comes from an Android app. + + + + + jdoerrie@chromium.org + battre@chromium.org + + Records whether the PasswordAutofillAgent in the renderer manages to fill + credentials as instructed by the browser or records a failure reason + otherwise. Only the outcome of the first attempt to fill is recorded. + + This is replicated as PasswordForm.Fill.FirstFillingResultInRenderer in UKM. + + + + + jdoerrie@chromium.org + battre@chromium.org + + This metric records why the browser instructs the renderer not to fill the + credentials on page load but to wait for the user to confirm the credential + to be filled. Only the value of the first decision to fill is recorded. + + This is replicated as PasswordForm.Fill.FirstWaitForUsernameReason in UKM. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The success or failure of deserializing saved FormData. Failure either + indicates corrupted data or the presence of bugs in the serialization or + deserialization code. + + + + + jdoerrie@chromium.org + kolos@chromium.org + + When the generation state of a password was changed, records whether an + existing form corresponding to the password was found. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The result of an attempted navigation to the Google Password Manager. + Recorded when a signed-in and password syncing user navigates to + https://passwords.google.com by clicking a link. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took for a failed navigation to the Google Password Manager. + Recorded when a signed-in and password syncing user navigates to + https://passwords.google.com by clicking a link and the navigation fails + before timing out. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took for a successful navigation to the Google Password Manager. + Recorded when a signed-in and password syncing user navigates to + https://passwords.google.com by clicking a link and the navigation succeeds + before timing out. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Breakdown of HTTP credentials with regard to the existence of a HTTPS + credential with the same username and whether the corresponding website has + HSTS enabled. Recorded once for each HTTP credential of the profile on + startup. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Number of HTTP saved passwords that were migrated to HTTPS. Recorded on + HTTPS password form load when there are no credentials saved. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The mode of migration applied to HTTP passwords migrating to HTTPS. Recorded + on HTTPS password form load when there are no credentials saved. + + + + + vasilii@chromium.org + src/components/password_manager/OWNERS + The number of passwords imported in CSV format per user + + + + vasilii@chromium.org + src/components/password_manager/OWNERS + + The response code of successful or failed password import attempt from a CSV + file. + + + + + vasilii@chromium.org + mamir@chromium.org + + The number of saved passwords in the profile-scoped store that could not be + decrypted. Recorded once for the profile on startup. + + + + + djean@chromium.org + sczs@google.com + + This metric counts how many times the Save Password infobar is shown. + + + + + djean@chromium.org + sczs@google.com + + This metric counts how many times the Update Password infobar is shown. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric reports whether a sync password hash is saved. Recorded shortly + after Chrome startup. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric is recorded shortly after Chrome Startup, only for Advanced + Protection users. This is a subset of + PasswordManager.IsSyncPasswordHashSaved. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Records selection of password manager suggestions in regular and + off-the-record modes. + + + + + jdoerrie@chromium.org + battre@chromium.org + + Records whether a successfully submitted password form has only values that + came from JavaScript. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Status of an attempted fetch of an access token. Recorded when a token fetch + completes. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Net Error Code of a failed attempt to fetch an access token. Recorded when a + token fetch completes with an error state. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + Result of analyzing a single leak response. + + + + jdoerrie@chromium.org + vasilii@chromium.org + The time it took to analyze a single leak lookup response. + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Reason of the dismissal of the leak detection dialog. Recorded when a leaked + credential is detected and the dialog is shown. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Indicates whether the password manager leak detection feature is enabled. + Recorded for each profile on browser start-up. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Shows the error that happened in password leak detection on sign-in. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + HTTP response code of a leak lookup request. Only recoded for each network + fetch that failed due to network/server errors. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + When a password is determined as leaked, records if it's saved for other + sites. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + When a password is determined as leaked, records if it's saved in Chrome. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + When a password is determined as leaked, records if the user is syncing + passwords without passphrase. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Whether the network fetch succeeded, failed due to network/server errors, or + contained malformed data. Recorded for each leak lookup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Network error code of a leak lookup request. Only recoded for each network + fetch that failed due to network/server errors. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took from starting a leak check to notifying the user about a + leak. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took to obtain an access token for an authenticated leak lookup + request. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took to prepare the payload for a single leak lookup request. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The time it took to receive a server response after issuing a request for a + single leak lookup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The number of matched prefixes in a single leak lookup response. Only + recorded if the network response was wellformed. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The size of a single leak lookup response in bytes. Only recorded if there + was no network or server error. + + + + + vasilii@chromium.org + mamir@chromium.org + An error on LoginDatabase initialization. + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Referrer of a navigation to the "Manage Passwords" page. Recorded + when the user attempts to see their list of passwords, either via native or + Web UI. + + + + + ioanap@chromium.org + vasilii@chromium.org + + Referrer of a navigation to the "Manage Passwords" page. Recorded + only for signed in users syncing passwords without a custom passprase, when + the user attempts to see their list of passwords. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Tracks result of navigator.credentials.get() with + mediation="optional". That is the result of account chooser. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Tracks result of navigator.credentials.get() with + mediation="required". That is the result of forced account + chooser. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Tracks result of navigator.credentials.get() with + mediation="silent". That is the result of auto sign-in. + + + + + mamir@chromium.org + mastiz@chromium.org + + Records different results upon adding a remote password to the password + manager. It is recorded during the initial sync when merging remote and + local data. + + + + + mamir@chromium.org + mastiz@chromium.org + + Records different results upon updating a remote password in the password + manager. It is recorded during the initial sync when merging remote and + local data. + + + + + + + mamir@chromium.org + treib@chromium.org + + Why was the "move password to account?" bubble closed? Recorded + whenever the bubble is closed, either because the user clicked one of the + buttons or it went away automatically (lost focus). + + + + + nepper@chromium.org + battre@chromium.org + kolos@chromium.org + + For a newly saved password, whether the password was generated by Chrome or + typed manually by the user. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric reports a type of a password hash change event where the + associated account is not syncing. Recorded when a non sync password hash is + saved or cleared. + + + + + jdoerrie@chromium.org + kazinova@google.com + + Records how many FormManagers are deleted on the main frame navigation. This + metric is useful for estimation of memory footprint. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The password manager only shows those credentials that are considered the + best match for a particular form. This stat keep track of the credentials + that were not as good of a match and were suppressed. + + + + + vasilii@chromium.org + jdoerrie@chromium.org + + Indicates whether the user's OS password is blank or not at browser startup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Breakdown of how other possible usernames are displayed. Recorded every time + we autofill a password form. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Logs the type of the suggestion in the password dropdown when selected. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + Logs the state of the password dropdown when it's shown. + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric shows how many saved credentials (num unique registry-controlled + domains) have password that's equal to the reused password. + + Before M63 this logged a "0" for sync-reuse. + + A "password reuse" is when the user typed a string that is equal + to a saved password on another domain or is equal to the sync password on a + non google-login domain. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric reports whether a password field had been detected on a page + when a password reuse happened. + + A "password reuse" is when the user typed a string that is equal + to a saved password on another domain or is equal to the sync password on a + non google-login domain. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric shows the length of the reused password. + + Change in M63: If multiple passwords are matched simultaneously, this logs + the length of the longest password. Also, before M63, a "0" was + logged for sync-reuse. + + A "password reuse" is when the user typed a string that is equal + to a saved password on another domain or is equal to the sync password on a + non google-login domain. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric shows how many credentials are stored in Password Manager when a + password reuse happened. This counts unique registry-controlled domains with + passwords saved. + + A "password reuse" is when the user typed a string that is equal + to a saved password on another domain or is equal to the sync password on a + non google-login domain. + + During M61/M62 this metric logged a "1" for every sync-reuse. It + was fixed in M63 such that it logs actual Password Manager credential count. + + + + + kolos@chromium.org + + Measures whether users save passwords with automatic prompt or manual + fallback. + + + + + kolos@chromium.org + battre@chromium.org + + PasswordScriptsFetcher's cache state when the fetcher is requested to return + script availability. + + + + + kolos@chromium.org + battre@chromium.org + + HTTP response code or network error code of fetching a list of available + password scripts. + + + + + kolos@chromium.org + battre@chromium.org + Result of parsing of a list of available password scripts. + + + + kolos@chromium.org + battre@chromium.org + + Response time for fetching a list of available password scripts. + + + + + dullweber@chromium.org + treib@chromium.org + mamir@chromium.org + + Records how often browsing data succeeds to delete account store passwords + from the Sync server. False is emitted in the rare situations when the + operation times out or the user disables Sync before the deletions are fully + propagated to the Sync server. True is emitted when the password deletion is + successfully propagated to the server. + + + + + vasilii@chromium.org + src/components/password_manager/OWNERS + + Success rate of initialization of password store. Recorded for every user + once on the Chrome profile startup. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Whether the passwords are syncing and, if not, then what's causing sync + failures. Recorded after the first sync attempt either succeeds or fails. + + + + + koerber@google.com + + Records successful fills of prefilled username values known as placeholders + and unsuccessful fills that were blocked because the prefilled value was not + identified as a placeholder. Recorded once per PasswordAutofillAgent + instance, when attempting to fill a password form that contains a username + value which was prepopulated by the website. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Breakdown of cases where a password is submitted, but we don't even try and + save it. Recorded for every password form submit. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Recorded whenever the user interacts with reauthentication in order to + access the passwords in settings, or when such reauthentication is skipped + for a well-defined reason. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Collects the cause of the change in the Password Store login which causes a + call of a remove SQL statement on the compromised credentials table. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Collects the cause of why remove SQL statement is called on the compromised + credentials table. + + + + + battre@chromium.org + jdoerrie@chromium.org + + HTTP response code of fetching a password requirements file. + + + + + battre@chromium.org + jdoerrie@chromium.org + + Network error code of fetching a password requirements file. + + + + + battre@chromium.org + jdoerrie@chromium.org + + Time until the lookup for a password requirements file completed (or was + aborted). + + + + + battre@chromium.org + jdoerrie@chromium.org + + Result of fetching requirements for password during password generation. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the type of password (e.g saved password, sync password, enterprise + password etc) reused by the user. This is logged when a password reuse + happens. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of enterprise password hashes that have been saved for + password reuse detection. This is logged during the initialization of + PasswordStore class. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of Gaia password hashes that have been saved for password + reuse detection. This is logged during the initialization of PasswordStore + class. + + + + + + + vasilii@chromium.org + treib@chromium.org + mamir@chromium.org + Why was the save password UI (bubble or infobar) closed? + + + + ioanap@chromium.org + vasilii@chromium.org + + Why was the save password UI (bubble or infobar) closed? This is currently + recorded only for Android and only after the user has unblacklisted an + origin for saving from the accessory sheet. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Records user actions when Chrome offers to save a username on a page which + is considered to be a username first flow. Recorded on a successful + submission. + + + + + cfroussios@chromium.org + jdoerrie@chromium.org + + Describes the result of decrypting a password value from the LoginDatabase. + + + + + mamir@chromium.org + treib@chromium.org + + Which of the password manager's stores (the profile-scoped one and/or the + account-scoped one) were used within the last 28 days for filling passwords. + Recorded whenever a password form is successfully submitted. This should + typically only be used with "Count unique clients". + + + + + mamir@chromium.org + treib@chromium.org + + Which of the password manager's stores (the profile-scoped one and/or the + account-scoped one) were used within the last 7 days for filling passwords. + Recorded whenever a password form is successfully submitted. This should + typically only be used with "Count unique clients". + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Records a frame type (eg. main frame, iframe with the same url as the main + frame) of a submitted password form. + + + + + jdoerrie@chromium.org + kolos@chromium.org + + The type (e.g. signup, login, change password) of all submitted password + forms. This is logged on form submission, but doesn't require that the + password manager saves. + + + + + estark@chromium.org + + The type (e.g. signup, login, change password) of all submitted password + forms on non-secure pages. This is logged on form submission, but doesn't + require that the password manager saves. + + + + + nepper@chromium.org + battre@chromium.org + kolos@chromium.org + + For a successful login, whether the origin is HTTPS or HTTP. A succesful + login is detected by local heuristics. The heuristics can misclassify + whether a login succeeded, so this is an approximation. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + The type of event that the Password Manager used for detecting a password + form submission. Recorded for each successful password form submission. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + chrome-password-manager-team@google.com + + Information about the user's current sync status crossed with whether their + synced password is saved. + + + + + mamir@chromium.org + mastiz@chromium.org + + This metric reports the error observed when trying to read the Sync metadata + from the password store during the start of Password sync. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + This metric reports a type of a sync password hash change event. Recorded + when a sync password hash is saved or cleared. + + + + + jdoerrie@chromium.org + battre@chromium.org + + The time between receiving saved credentials from the password store and + predictions from the Autofill server. Recorded each time when predictions + for a form are received. + + + + + battre@chromium.org + jdoerrie@chromium.org + + The number of times each saved password from the profile-scoped storage has + been used to log in. Split by whether created by the user or generated by + Chrome, and further by whether the user used sync with custom passphrase or + not. Recorded by iterating over stored passwords once per run. This + information is persisted and synced. + + + + + battre@chromium.org + vasilii@chromium.org + + The number of accounts stored in the password manager's profile-scoped store + (across all sites), split by whether created by the user or generated by + Chrome, and further by whether the user used sync with custom passphrase or + not. + + + + + battre@chromium.org + vasilii@chromium.org + + The number of accounts stored in the password manager's profile-scoped store + (across all sites) for origins with the scheme (e.g., HTTP, HTTPS, FTP) as + given in the histogram suffix. For each scheme, the count is recorded once + per browser start-up. (In case of multiple profiles, the counts are for the + profile that first has a WebContents created.) + + + + + jdoerrie@chromium.org + fhorschig@chromium.org + + The index of a selected credential in the Touch To Fill sheet. Only recorded + when the sheet showed at least two entries. + + + + + jdoerrie@chromium.org + fhorschig@chromium.org + + The reason why a user dismissed the Touch To Fill sheet. Recorded once for + each dismissal. + + + + + jdoerrie@chromium.org + fhorschig@chromium.org + The number of credentials shown in the Touch To Fill sheet. + + + + jdoerrie@chromium.org + fhorschig@chromium.org + + The action a user took when interacting with the Touch To Fill sheet. + + + + + vasilii@chromium.org + + Why was the password manager's UI (bubble or infobar) closed? Save and + update UI are tracked separately. + + + + + vasilii@chromium.org + Why was the update password UI (bubble or infobar) closed? + + + + kolos@chromium.org + + Chrome saves locally all fields a user typed on a sign-up form. If Chrome + saved an incorrect username and the user changes the username on a sign-in + form to a value of another field from the sign-up form, then Chrome uploads + a username correction vote which points to the correct username field. This + histogram measures how many correction votes are uploaded. + + + + + kolos@chromium.org + + Measures what method was used for username field detection in the renderer + code. The metric may be recorded several times for page visit because it is + recorded at every PasswordForm creation. If a site changes HTML attributes + of fields or server-side predictions is received, different values can be + recorded for the same form. If an outcome of HTML classifier or a + server-side prediction coincides with the outcome of base heuristic, the + metric points to base heuristic method. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + A JSON file with change password form url is fetched from gstatic. This + metric logs if the response arrived in time and if the url override was + available for a given origin. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Logs the error code when the fetch to the gstatic file failed. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Logs the response code when the fetch to the gstatic file failed. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + + Logs if the request for the gstatic file succeeded, failed or if the + response was malformed. + + + + + jdoerrie@chromium.org + vasilii@chromium.org + Logs the loading time for the gstatic file request. + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes to extract the DOM features of a login page before sending + a PasswordProtectionRequest. Logged on every password reuse PhishGuard ping. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of Gaia password reuse warnings shown to user before user changes + their password. Logged when we see that user has changed their Gaia + password. The number of reuses will be reset to zero if current session of + browser process ends. This count doesn't include the reuses that user marked + as legitimate. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how a user interacts with the password protection interstitial + (a.k.a chrome://reset-password page). Logged when the interstitial is shown + and when the user chooses to change their password. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the type of strings shown to the user on chrome://reset-password + page. Logged when the interstitial in initialized. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how a user interacts with the password protection modal warning + dialog. Logged when the dialog is shown and when the user chooses to change + their password, ignore warning, or navigate away. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the interval between when the password protection modal warning + dialog is constructed and when the dialog is destructed. The dialog can be + destructed when the user takes action or the web content is destroyed. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how a user interacts with page info bubble that displays the + password protection warning. Logged when such page info bubble is shown and + when the user chooses to change their password, ignore warning, or mark site + as legitimate via buttons on the page info bubble. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Reports the zoom factor for a login page, when the protected password is + entered. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the outcome of the password alert mode, indicating if password alert + warning is shown successfully or if it is skipped for some reason. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Response or error codes for PasswordProtectionRequest. Logged after chrome + receives response of PasswordProtectionRequest from Safe Browsing service. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + When password protection service detects a reuse of Chrome sync password, + record the type of Chrome sync account on which the reuse happens (e.g. + @gmail.com, @googlemail.com, or other dasher account). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The result from the renderer after DOM feature extraction. This is collected + when Chrome password protection detects password reuse, or (for SBER users), + when the user focuses on a password field. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes for PasswordProtectionService request. It is not recorded + for requests that were canceled. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the outcome of the password protection request, indicating if + request is sent out successfully or if it is skipped or canceled for some + reason. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs when an event where users reuse their password or focus on a password + field is sent as a sample ping when the URL in the allowlist to Safe + Browsing. Events only happen 1% of the time when URLs match the allowlist. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Verdict types returned by Safe Browsing server for a password protection + request. Request can be triggered when user focuses on a password field or + enters a protected password (syncing, signed-in, or saved). + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes to extract the visual features of a login page before + sending a PasswordProtectionRequest. Logged every time visual features are + extracted (when an SBER user sends an On Focus ping). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/payment/histograms.xml b/tools/metrics/histograms/histograms_xml/payment/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..3fb4d9d8e37abab1a9dea5b9072471c3df747928 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/payment/histograms.xml @@ -0,0 +1,234 @@ + + + + + + + + + + danyao@chromium.org + web-payments-team@google.com + + Counts the number of Payment Requests (PR) that go through each checkout + step. A single PR may be counted in multiple buckets depending on its final + status. e.g. A completed PR will be counted in all of the following buckets + 1- Initiated, 2- show() called 3- Payment request triggered 4- Payment + handler invoked, 5- Completed. + + + + + danyao@chromium.org + web-payments-team@google.com + The reason that lead to an abort of the Payment Request. + + + + danyao@chromium.org + web-payments-team@google.com + + The reason that leads to the Payment Request not being shown to the user. + + + + + danyao@chromium.org + web-payments-team@google.com + + A bitfield representing the different events that happened during the + Payment Request. + + + + + sahel@chromium.org + web-payments-team@google.com + + Whether a journey logger has recorded an events bit field or not. + + + + + sahel@chromium.org + web-payments-team@google.com + + When a journey logger attempts to record multiple events bit fields. + + + + + sahel@chromium.org + web-payments-team@google.com + + A bitfield representing different missing fields of the contact section in + payment sheet. This only gets recorded when no complete contact profile is + available. In case of multiple partially complete profiles, this is only + recorded for the most complete one which is also the first profile in the + suggestion list. + + + + + sahel@chromium.org + web-payments-team@google.com + + A bitfield representing different missing fields of the payment info section + in the payment sheet. This only gets recorded when no complete payment + instrument is available (SW based instruments are always considered as + complete). In case of multiple partially complete cards this is only + recorded for the first card in the suggestion list. + + + + + sahel@chromium.org + web-payments-team@google.com + + A bitfield representing different missing fields of the shipping section in + the payment sheet. This only gets recorded when no complete shipping profile + is available. In case of multiple partially complete profiles, this is only + recorded for the most complete one which is also the first profile in the + suggestion list. + + + + + danyao@chromium.org + web-payments-team@google.com + + The number of suggestions shown to the user during a payment request. + + + + + sahel@chromium.org + web-payments-team@google.com + + True when chrome crawls to refetch the missing icon of an already installed + payment app. + + + + + danyao@chromium.org + web-payments-team@google.com + + Records the size of Credential ID for secure-payment-confirmation method in + bytes. + + + + + sahel@chromium.org + web-payments-team@google.com + True when a service worker times out 5 mins after request. + + + + sahel@chromium.org + web-payments-team@google.com + + Records the time between a payment request .show() and its completion. + + + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the time between a payment request .show() and its completion when + payment sheet is shown. + + + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the time between a payment request .show() and its completion when + payment sheet is skipped. + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the time between a payment request .show() and its termination by + any factors other than the user (e.g. merchant). + + + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the time between a payment request .show() and its termination by + user. + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the transaction amounts completed using payment request API after + converting to USD. + + + + + sahel@chromium.org + web-payments-team@google.com + + Records the transaction amounts triggered using payment request API after + converting to USD. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/permissions/histograms.xml b/tools/metrics/histograms/histograms_xml/permissions/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..317de05c55a81435e5a9b747a2c7c18a287550c4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/permissions/histograms.xml @@ -0,0 +1,493 @@ + + + + + + + + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks whether a permission was granted, rejected, etc. The suffix of the + histogram indicates which particular permission. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Tracks the action that a user had taken per permission prompt UI + disposition. Suffixed by the UI disposition that the prompt used. Recorded + when a permission prompt has been resolved. + + + + + dominickn@chromium.org + kcarattini@chromium.org + + For every permission request that would show a prompt to the user, this + metric tracks whether the request is suppressed by embargo (and the source + of that embargo), or whether there is no embargo and the prompt is shown. + This is the proportion of permission prompts that the user would have seen + that have been blocked due to embargo. + + If the (origin, permission) pair was previously placed under embargo, no + prompt is displayed and the reason for embargo is recorded. Otherwise, the + prompt is shown and a no embargo reason is recorded. + + + + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks the reason that an (origin, permission) pair has been placed under + embargo (blocked from making requests for that permission for a period of + time). This is triggered when a permission is placed under embargo for + blacklisting (once Safe Browsing has returned a result), when a permission + prompt has been shown and it is placed under embargo for repeated + dismissals, or when a permission prompt is shown and not embargoed. + + + + + timloh@chromium.org + + Battery percentage when a geolocation permission prompt was accepted on + Android. + + + + + timloh@chromium.org + + Battery percentage when a location settings dialog was accepted. + + + + + timloh@chromium.org + + Battery percentage when a geolocation permission prompt was denied on + Android. + + + + + timloh@chromium.org + + Battery percentage when a location settings dialog was denied. + + + + + timloh@chromium.org + + Battery percentage when a geolocation permission prompt was dismissed on + Android. + + + + + bsep@chromium.org + engedy@chromium.org + olesiamarukhno@google.com + + Records how long it takes for the user to click on the permission chip after + it was shown. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Whenever a notification permission prompt is to be displayed, crowd deny + might trigger based on site reputation which will result in a quiet + permission prompt UI to be used. Whenever this happens, there is a small + chance that the normal UI will still be used. This records, when a quiet UI + is supposed to be shown, whether it has been randomly selected into the + hold-back group. In this case the normal UI will be displayed unless + overriden by the user Prefences. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records, each time a notification permission prompt is about to be shown, + the NotificationUxQuality result for the requesting origin. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records, each time a notification permission prompt is about to be shown, + the whether there is preload data that indicates the origin being on a + warning list. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records, each time a Safe Browsing request is made in response to a website + requesting the notification permission, how long that Safe Browsing request + took. This also includes all delays introduced by thread hopping. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records, each time a Safe Browsing request is made in response to a website + requesting the notification permission, the Safe Browsing verdict regarding + the notification prompt experience on that site. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks the engagement score for sites where permission prompts are accepted. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks the engagement score for sites where permission prompts are denied. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks the engagement score for sites where permission prompts are + dismissed. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks the engagement score for sites where permission prompts are ignored. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Recorded when the "Chrome needs permission..." infobar is + resolved. Records the resulting action that was taken. Suffixed by + `PermissionTypes` to provide information per permission type. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Recorded when the "Chrome needs permission..." infobar might be + displayed to the user because a site already has the permission but Chrome + does not. Records whether the infobar should be displayed or not. Ignores + situations when the infobar cannot be displayed (for example because there + is no appropriate web contents) as in those cases no decision is actually + made. Suffixed by `PermissionTypes` to provide information per permission + type. + + + + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks the permission bubbles (merged and non-merged) that are accepted. + Merged bubbles are considered accepted if all permissions are allowed. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt accept, records the + total number of prompt dismissal events for this origin since the last time + the user explicitly set the permission state or cleared history / site data + and prior to the accept. The suffix of the histogram indicates which + particular permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt accept, records the + total number of prompt ignore events for this origin since the last time the + user explicitly set the permission state or cleared history / site data and + prior to the accept. The suffix of the histogram indicates which particular + permission. + + + + + dominickn@chromium.org + kcarattini@chromium.org + + Tracks the permission bubbles (merged and non-merged) that are denied. + Merged bubbles are considered denied if any permission is denied. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt deny, records the + total number of prompt dismissal events for this origin since the last time + the user explicitly set the permission state or cleared history / site data + and prior to the accept. The suffix of the histogram indicates which + particular permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt deny, records the + total number of prompt ignore events for this origin since the last time the + user explicitly set the permission state or cleared history / site data and + prior to the accept. The suffix of the histogram indicates which particular + permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt dismiss, records + the total number of prompt dismissal events for this origin since the last + time the user explicitly set the permission state or cleared history / site + data and prior to the dismiss. The suffix of the histogram indicates which + particular permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt dismiss, records + the total number of prompt ignore events for this origin since the last time + the user explicitly set the permission state or cleared history / site data + and prior to the dismiss. The suffix of the histogram indicates which + particular permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt ignore, records the + total number of prompt dismissal events for this origin since the last time + the user explicitly set the permission state or cleared history / site data + and prior to the ignore. The suffix of the histogram indicates which + particular permission. + + + + + engedy@chromium.org + elklm@chromium.org + + This metric, recorded at the time of a permission prompt ignore, records the + total number of prompt ignore events for this origin since the last time the + user explicitly set the permission state or cleared history / site data and + prior to the ignore. The suffix of the histogram indicates which particular + permission. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Tracks whether the user has expanded the infobar notification permission + request. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Tracks how many times permission prompts are shown to users. + + + + + bsep@chromium.org + engedy@chromium.org + olesiamarukhno@google.com + + Records how long it takes for the user to make a decision about permission + request, from when permission prompt is shown until when the user clicks on + one of the buttons in the prompt (accept, block or close). + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records, each time the quiet UI gets enabled in preferences, whether it was + enabled by the adaptive activation logic. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records when the quiet notification permission UI state changes, that is, it + either gets enabled or disabled, in preferences. + + + + + andypaicu@chromium.org + engedy@chromium.org + hkamila@chromium.org + + Records whether the quiet notification permission UI is enabled in + preferences at profile creation. No sample recorded when notifications are + set to be blocked completely. + + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the time elapsed since the grant of the permission until it's + revoked. + + + + + reillyg@chromium.org + src/content/browser/serial/OWNERS + + Records the reason why the Serial API chooser, triggered by a call to + navigator.serial.requestPort(), was closed. + + + + + reillyg@chromium.org + src/content/browser/serial/OWNERS + Records when permission to access a serial port is revoked. + + + + engedy@chromium.org + src/components/permissions/PERMISSIONS_OWNERS + + Records the time elapsed since the grant of the permission until it's latest + usage. This histogram will be recorded only for the first usage of a given + permission after the site has loaded. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/platform/histograms.xml b/tools/metrics/histograms/histograms_xml/platform/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..cca72f5efc51ef97a09f30add7c92d2083be6582 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/platform/histograms.xml @@ -0,0 +1,1456 @@ + + + + + + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of crashes (user, kernel, and unclean shutdowns) during the previous + day, or the most recent day the device was in use. Reported at most once a + day. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of crashes (user, kernel, and unclean shutdowns) during the previous + epoch-week, or the most recent epoch-week the device was in use. Reported at + most once a week. Epoch-weeks divide the time in 7-day intervals starting at + the UNIX epoch. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS (ARM Chromebooks using Exynos 5250 only) Adaptive Support Voltage + Group, recorded once per bootup. Indicates which "bin" the SoC is + part of, which sets the voltage that different rails on the system will run + at. The values 0-11 are valid. A value of 12 indicates an error parsing + dmesg and should be investigated. See also Platform.LotIdEnum. + + + + + cernekee@chromium.org + + Indicates whether the kernel's ACPI Smart Battery System driver logged an + error trying to find the battery on boot. + + + + + mnissler@chromium.org + dossym@chromium.org + + Indicates the status of the developer switch on Chrome OS hardware. The + developer switch allows users to run their own code on the device. + + + + + mnissler@chromium.org + dossym@chromium.org + + On Chrome OS hardware, indicates whether flash write protection is enabled + for the firmware indicated by the histogram suffix. + + + + + mnissler@chromium.org + dossym@chromium.org + + Indicates the status of the hardware write protect switch on Chrome OS + hardware. The write protect switch protects firmware from being rewritten. + + + + + sonnyrao@chromium.org + chromeos-performance@google.com + + Chrome OS number of disk sectors read at boot from kernel start to + login-prompt-ready. + + + + + sonnyrao@chromium.org + chromeos-performance@google.com + + Chrome OS number of disk sectors written at boot from kernel start to + login-prompt-ready. + + + + + halliwell@chromium.org + + /proc/meminfo's 'MemAvailable' in MiB. Collected every 5s on Cast devices + with kernel version 3.14 and above and capped at 2000. + + + + + halliwell@chromium.org + + Collect free + buffers + cache memory in MiB every 5s on Cast devices, + capped at 2000. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Chrome OS size of allocated swap area in megabytes (before compression) + + + + + sonnyrao@chromium.org + chromeos-performance@google.com + + CPU frequency as percent of the baseline frequency, sampled every 30s. This + may be throttled down from 100% due to power dissipation issues (too high + temperature). It may also be throttled up (turbo), but the kernel does not + report the actual turbo frequency, so we put such samples in the 101% + bucket. + + + + + sonnyrao@chromium.org + cast-analytics@google.com + + Peak total (single core) CPU usage for the last sample interval. The sample + interval may vary from seconds to several minutes. + + + + + vbendeb@chromium.org + + A sparse histogram of values of Board ID flags programmed in H1 devices in + the field. Board ID flags is a 32 bit field, and while there only are a few + expected values, conceivably any bit combination could be encountered. + + + + + vbendeb@chromium.org + apronin@chromium.org + cros-hwsec+uma@chromium.org + + A sparse histogram of values indexed by 4 byte Board ID code programmed in + H1 reported by devices where there is a mismatch between the RLZ code and + the Board ID value programmed in the H1. + + + + + apronin@chromium.org + vbendeb@chromium.org + cros-hwsec+uma@chromium.org + + A histogram of flash log event types collected from the H1 device. Log event + type is an 8 bit value. This histogram does not allow to drill into + particular log entries' contents, but allows to collect a general statistics + of events. A script running on the Chrome OS device polls the H1 for new + flash log events after every start up. + + + + + vbendeb@chromium.org + + A sparse histogram of values indexed by 4 byte Board ID code programmed in + H1, reported by devices where there is no mismatch between the RLZ code and + the Board ID value. + + + + + vbendeb@chromium.org + apronin@chromium.org + cros-hwsec+uma@chromium.org + + A sparse histogram of values indexed by 4 byte RLZ code reported by devices + where there is a mismatch between the RLZ code and the Board ID value + programmed in the H1. Since RLZ code could be misprogrammed, a sparse + histogram is used to allow keeping track of outliers. + + + + + iby@chromium.org + mutexlox@chromium.org + cros-telemetry@google.com + + (Chrome OS only) An enum indicating the reasons for removal of crash reports + on devices. Generally, we'll remove crash reports after successfully sending + them, but there are other reasons for removal (e.g. if the metadata file was + malformed). These should be rare, but bugs in the crash reporting system may + cause us to start removing crashes before sending them more often. This + metric is intended to monitor crash reporting system health. + + + + + + + + + iby@chromium.org + mutexlox@chromium.org + vapier@chromium.org + + Generic event of interest from Chrome OS. Intended mainly to help assess the + frequency of rare error conditions. + + + + + drinkcat@chromium.org + dnschneid@chromium.org + + Detects presence of /run/crouton, indicating that crouton has been started + since the previous boot. Value 0/"Total count" is reported on + boot, 1/"Started" is reported after the file presence is detected + (checked periodically). + + + + + semenzato@chromium.org + bsimonnet@chromium.org + + Total CPU time accumulated since the last version update. Reported at most + once a day. + + + + + semenzato@chromium.org + bsimonnet@chromium.org + + Total use time (device ON and not asleep) since last version update. + Reported at most once a day. + + + + + semenzato@chromium.org + bsimonnet@chromium.org + + Total use time (device ON and not asleep) in the previous day, or the most + recent day the device was in use. Reported at most once a day. + + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + + Ratio of time a detachable base keyboard is active, i.e. when the USB + interface is not auto-suspended. Reported every 30 seconds when the base is + connected. + + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + + For devices with a detachable base: whether or not the base is connected on + boot. Recorded by upstart task on boot. + + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + Result of a detachable base pair operation. + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + + Detachable base firmware updates can be configured to only occur on boot. In + this mode, any update will be considered "pending" until the + system is rebooted, at which point the update may take place. Every time a + detachable base is connected to the system, a metric representing the + pending update status is recorded. Its possible values are as follows: (0) + communication error; (1) no update available; (2) critical update available; + or (3) non-critical update available. The definition of "critical" + is up to the software performing updates, and would typically be used in the + case of a security issue, or broken functionality in a previous firmware + version. + + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + Result of a detachable base RO firmware update. + + + + drinkcat@chromium.org + fshao@chromium.org + chromeos-kukui@google.com + Result of a detachable base RW firmware update. + + + + achuith@chromium.org + tls@chromium.org + + Number of users home directories on the device. Logged once a day. + + + + + achuith@chromium.org + omrilio@chromium.org + + Days since last login of the least recently user on device. Logged once a + day, if disk usage is high. + + + + + achuith@chromium.org + omrilio@chromium.org + + Number of user home dirs on device. Logged once a day, if disk usage is + high. + + + + + keescook@google.com + + Chrome OS KB in use in the /home/chronos filesystem tree. Logged once a day + during log file cleanup. + + + + + keescook@google.com + + Chrome OS KB in use in the /var filesystem tree. Logged once a day during + log file cleanup. + + + + + andrewlassalle@chromium.org + chromeos-core-services@google.com + + The result of an attempt to Install a DLC package. DLCs are ChromiumOS + Software packages that are installed in the stateful partition. + + + + + andrewlassalle@chromium.org + chromeos-core-services@google.com + + The result of an attempt to Uninstall a DLC package. DLCs are ChromiumOS + Software packages that are installed in the stateful partition. + + + + + gwendal@google.com + + eMMC [5.0] Device life time estimation for flash. This field provides an + estimated indication about the device life time that is reflected by the + averaged wear out of memory of a given type relative to its maximum + estimated lifetime. + + + + + gwendal@google.com + + Number of file system errors, as reported by dumpe2fs "FS Error + count" field. Reported once per boot. + + + + + gwendal@google.com + + True when kernel reports that the file system needs deep recovery. File + system has corruption the kernel can not fix by itself. Reported once per + boot. + + + + + gwendal@google.com + + True when kernel reports that the file system needed recovery at boot. It + indicates the filesytem was not properly unmounted, but was recovered. + Reported once per boot. + + + + + fbarchard@chromium.org + pwnall@chromium.org + + The maximum supported micro-architecture on an Intel platform. This value is + logged at program start time. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of kernel crashes during the previous day, or the most recent day the + device was in use. Reported at most once a day. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of kernel crashes since the last OS update, normalized as number of + crashes per year of active use (active use = device is ON and not asleep). + Reported daily. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of kernel crashes since the last OS update, normalized as number + crashes per year of CPU time. Reported daily. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of kernel crashes since the last OS update, reported daily. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Count of kernel crashes during the previous epoch-week, or the most recent + epoch-week the device was in use. Reported at most once a week. Epoch-weeks + divide the time in 7-day intervals starting at the UNIX epoch. + + + + + grundler@chromium.org + groeck@chromium.org + sonnyrao@chromium.org + + Time elapsed between the last two kernel crashes. Sent after every kernel + crash. + + + + + sonnyrao@chromium.org + chromeos-performance@google.com + + Number of logical processors. This includes Hyperthreaded cores. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Chrome OS (ARM Chromebooks using Exynos 5250 only) indication about whether + we're part of a special lot ID. Special lot IDs are groups of chips that + have special case handling in the kernel for the Adaptive Support Voltage + code (the normal logic doesn't work). See also Platform.AsvGroup. Note that + fused devices are never part of a special lot (currently) and only some + unfused lots are "special". + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + sonnyrao@chromium.org + chromeos-memory@google.com + + Various memory usage % of total memory on Chrome OS devices (snapshotted + every 30s). + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + sonnyrao@chromium.org + chromeos-memory@google.com + + Various memory usage amount on Chrome OS devices (snapshotted every 30s). + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of all ARC processes in Chrome OS, reported every 10 minutes. + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of browser and helper processes (excluding GPU process and + renderers) in Chrome OS, reported every 10 minutes. + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of user-level daemons in Chrome OS, reported every 10 minutes. + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of the GPU process in Chrome OS, reported every 10 minutes. + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of renderer processes in Chrome OS, reported every 10 minutes. + + + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Memory usage of VMs (crostini) in Chrome OS, reported every 10 minutes. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + cast-analytics@google.com + + Peak memory bandwith (read and write) usage during the last sample interval. + The sample interval may vary from seconds to several minutes. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Chrome OS total anonymous memory (active + inactive) as % of total memory 1 + minute after boot. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Chrome OS total anonymous memory (active + inactive) as % of total memory 5 + minutes after boot. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Chrome OS total anonymous memory (active + inactive) as % of total memory 30 + minutes after boot. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Chrome OS total anonymous memory (active + inactive) as % of total memory + 150 minutes after boot. + + + + + hajimehoshi@chromium.org + kouhei@chromium.org + + Chrome OS total anonymous memory (active + inactive) as % of total memory + 750 minutes after boot. + + + + + apronin@chromium.org + mnissler@chromium.org + cros-hwsec+uma@chromium.org + + File system encryption key status for the encrypted stateful file system on + Chrome OS. The encryption key is the one that is used by the kernel to + protect actual file contents on disk. + + + + + apronin@chromium.org + mnissler@chromium.org + cros-hwsec+uma@chromium.org + + Type/Origin of the system key used for the encrypted stateful file system on + Chrome OS. This key is used to wrap the actual file system encryption key. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Page faults per second averaged over 30s interval, sampled continuously. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Page faults per second averaged over 1s interval, sampled every 30s. + + + + + gwendal@google.com + + Number of disk sectors per second read by Chrome OS in a long interval + (currently 30s) + + + + + gwendal@google.com + + Number of disk sectors per second read by Chrome OS in a short interval + (currently 1s, sampled every 30s) + + + + + asavery@chromium.org + gwendal@chromium.org + + The remaining reserved space (SMART 232). The value counts down typically + from 100 to 0, sent at boot. + + + + + asavery@chromium.org + gwendal@chromium.org + + The total number of 512-byte sectors written during the lifetime of the + device, sent at boot. + + + + + asavery@chromium.org + gwendal@chromium.org + + The total number of 512-byte sectors written during the lifetime of the + device, sent at boot. + + + + + asavery@chromium.org + gwendal@chromium.org + + Percentage Used Endurance Indicator. A value of 0 indicates a new device, a + value of 100 indicates the device is at the end of its lifespan as projected + by the manufacturer. Values greater than 100 indicate the device is beyond + the projected lifespan. Maximum value is 255, sent at boot. + + + + + gwendal@google.com + Disk communication errors (SMART 199), sent at boot. + + + + gwendal@google.com + Uncorrectable disk errors (SMART 187), sent at boot. + + + + vpalatin@google.com + + USB device ID of the charger plugged into a Spring device (if any), sent + once a minute. The Device ID is composed from the following 4 8-bit + registers of the TSU6721 chip: ADC (07h), Device Type 3 (15h), Device Type 2 + (0Bh), Device Type 1 (0Ah). Device Type 1/2/3 is a bitmap and most of bits + are mutually exclusive (excepted VBUS debounce). ADC is the 5-bit value of + the ID pin, but for most types (as in Device Type), there are only one or + two possible ID pin connections/values. The datasheet can be found here: + http://www.ti.com/lit/ds/symlink/tsu6721.pdf. + + Note that different brand/models of the charger can have the same ID. + + + + + jamescook@chromium.org + gwendal@chromium.org + + Chrome OS stateful partition space free. Sampled once daily. + + + + + asavery@chromium.org + gwendal@chromium.org + + Chrome OS stateful partition lifetime writes. Sampled once daily. + + + + + asavery@chromium.org + gwendal@chromium.org + + The amount of time in hours since the last trim when chromeos-trim triggers + a trim for the stateful partition. The chromeos-trim script is run daily, + but a trim is only triggered if the previous run was interrupted, the amount + of writes since the last trim is greater than X% of the remaining space in + stateful or we have not trimmed in 7 days. Reported at most once a day. + + + + + asavery@chromium.org + gwendal@chromium.org + + The amount of data in the stateful partition that is erased when + chromeos-trim triggers a trim. The chromeos-trim script is run daily, but a + trim is only triggered if the previous run was interrupted, the amount of + writes since the last trim is greater than X% of the remaining space in + stateful or we have not trimmed in 7 days. Reported at most once a day. + + + + + achuith@chromium.org + omrilio@chromium.org + Chrome OS stateful partition usage level. + + + + asavery@chromium.org + gwendal@chromium.org + + Chrome OS stateful partition space used. Sampled once daily. + + + + + asavery@chromium.org + gwendal@chromium.org + + Chrome OS stateful partition KiB writes per day. Sampled once daily. + + + + + dehrenberg@chromium.org + cast-analytics@google.com + + The number of blocks marked bad in an MTD partition. This is relevant for + devices with raw NAND flash, such as Chromecast. Sampled once daily, if the + Chromecast is on for any significant length of time in the day. + + + + + asavery@chromium.org + gwendal@chromium.org + + Vendor specific estimate of the percentage of NVM subsystem life used based + on the actual usage and the manufacturer's prediction of NVM life. A value + of 100 indicates the estimated endurance has been consumed, but may not + indicate a failure. Values can exceed 100, with percentages greater than 254 + represented as 255. + + + + + asavery@chromium.org + gwendal@chromium.org + + UFS Device life time estimation. This field provides an indication of the + device life time based on the amount of performed program/erase cycles. The + calculation is vendor specific. + + + + + asavery@chromium.org + chromeos-storage@google.com + Number of pages swapped IN over a day, sampled daily. + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Average pages/second swapped IN over a 30s interval, sampled every 30s. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Average pages/second swapped IN over a 1s interval, sampled every 30s. + + + + + asavery@chromium.org + chromeos-storage@google.com + Number of pages swapped OUT over a day, sampled daily. + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Average pages/second swapped OUT over a 30s interval, sampled every 30s. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Average pages/second swapped OUT over a 1s interval, sampled every 30s. + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 0 (TSR0) taken every 30s. + + This metric is specific to Chrome OS + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 0 (TSR0) taken after resume + from sufficiently long suspend. + + This metric is specific to Chrome OS + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 1 (TSR1) taken every 30s. + + This metric is specific to Chrome OS + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 1 (TSR1) taken after resume + from sufficiently long suspend. + + This metric is specific to Chrome OS + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 2 (TSR2) taken every 30s. + + This metric is specific to Chrome OS + + + + + fletcherw@chromium.org + + Temperature reading from EC temperature sensor 2 (TSR2) taken after resume + from sufficiently long suspend. + + This metric is specific to Chrome OS + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 3 (I2C_PCH-Object) taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 4 (I2C_DDR-Die) taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 5 (I2C_DDR-Object) taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 6 (Charger-Die), taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 7 (Charger-Object) taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Temperature reading at sensor 8 (ECInternal) taken every 30s. + + + + + Please list the metric's owners. Add more owner tags as needed. + Temperature reading at sensor 9 (PECI) taken every 30s. + + + + julanhsu@google.com + caiz@google.com + + Temperature reading at sensor 0 of the CPU collected every few seconds (may + vary between devices). + + This metric is specific to Chrome OS. + + + + + fletcherw@chromium.org + + Temperature reading at sensor 0 of the CPU collected when resuming from a + sufficiently long suspend. + + This metric is specific to Chrome OS. + + + + + julanhsu@google.com + caiz@google.com + + State of the thermal zone of the CPU collected every second. State depends + on device, higher state corresponds to a higher temperature. + + This metric is specific to Chrome OS. + + + + + semenzato@chromium.org + + Each sample is the result code of a TPM authorized command issued through + tcsd. Success is 0. For the other error codes, see + /usr/include/tss/tpm_error.h. + + + + + cylai@chromium.org + cros-hwsec-userland-eng+uma@chromium.org + + Each sample is the value of the TPM dictionary attack counter reported at + boot and hourly while running. Any non-zero value is unexpected. + + + + + cylai@chromium.org + cros-hwsec-userland-eng+uma@chromium.org + + Each sample is the status of an hourly attempt to reset the TPM dictionary + attack counter. + + + + + semenzato@chromium.org + + Each sample is the result code of a TPM command issued through tcsd. Success + is 0. For the other error codes, see /usr/include/tss/tpm_error.h. + + + + + mnissler@chromium.org + cros-hwsec+uma@chromium.org + + Number of attempts until a successful TPM firmware update. This is the total + sum of attempts, i.e. number of failed attempts + 1 for the final successful + attempt. Note that we're not in a position to report UMA after failed + attempts, so this will only be reported by devices that eventually see a + successful attempt. + + + + + mnissler@chromium.org + cros-hwsec+uma@chromium.org + Status of a complete TPM firmware update attempt. + + + + mnissler@chromium.org + cros-hwsec+uma@chromium.org + Exit status of the TPM firmware updater script. + + + + anatol@google.com + + Trusted Platform Module hardware alerts that signal about the chip abnormal + situation. + + + + + mnissler@chromium.org + cros-hwsec+uma@chromium.org + + Indicates a fingerprint of hardware + firmware versions for the TPM chip + present in a Chrome OS device. + + + + + cylai@chromium.org + cros-hwsec-userland-eng+uma@chromium.org + Records occurrences of U2F commands sent to cr50. + + + + cylai@chromium.org + cros-hwsec-userland-eng+uma@chromium.org + Records occurrences of legacy U2F commands sent to cr50. + + + + semenzato@chromium.org + bsimonnet@chromium.org + + Count of crashes (unclean shutdown) during the previous day, or the most + recent day the device was in use. Reported at most once a day. + + + + + semenzato@chromium.org + bsimonnet@chromium.org + + Count of crashes (user) during the previous day, or the most recent day the + device was in use. Reported at most once a day. + + + + + tnagel@chromium.org + + Number of unknown RW_VPD entries on Chrome OS, sent once per boot. + + + + + briannorris@chromium.org + cros-network-metrics@google.com + + Sample collected 10s after boot, showing how many WiFi interfaces are + present. + + + + + rajatja@chromium.org + briannorris@chromium.org + chromeos-kernel-wifi@google.com + cros-network-metrics@google.com + + Logged (with a constant value of 1) if a WiFi device experienced a PCI + failure such that it is being removed from the system. Typically, Chrome OS + will follow such a removal with an attempt to rescan the bus and recover + device functionality. See also Platform.WiFiStatusAfterForcedPCIRescan for + the result of such attempts. + + + + + rajatja@chromium.org + briannorris@chromium.org + cros-network-metrics@google.com + + Shows the WiFi status after the PCI bus is rescanned to recover WiFi. The UI + depends on shill noticing that wlan0 is back up, so the only happy case is + one where shill recognizes wlan0 after the rescan completes. + + + + + gwendal@google.com + + Number of disk sectors per second written by Chrome OS in a long interval + (currently 30s) + + + + + gwendal@google.com + + Number of disk sectors per second written by Chrome OS in a short interval + (currently 1s, sampled every 30s) + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + Compressed swap size in megabytes. This is the actual amount of RAM used by + the system to compress memory (i.e. after compression). Snapshot every 30s. + + + + + sonnyrao@chromium.org + chromeos-memory@google.com + + The ratio of compressed memory (zram) before and after compression when the + denominator at least 1 MB. Ratios of interest are between 1 and 6 (typically + between 2 and 3), and we express them as a percentage (between 100% and + 600%). The size of memory before compression includes zero-filled pages. + Values close to 100% indicate low compression effectiveness. Snapshot every + 30s. + + + + + asavery@chromium.org + gwendal@chromium.org + + Number of incompressible pages stored in zram. A large number suggests lower + compression effectiveness. Snapshot every 30s. + + + + + asavery@chromium.org + gwendal@chromium.org + + The fraction of compressed memory that consists of incompressible pages. We + express this as a percentage (between 0% and 100%). Values close to 100% + mean we are not able to effectively benefit from compression. Snapshot every + 30s. + + + + + asavery@chromium.org + gwendal@chromium.org + + The fraction of the uncompressed memory size that consists of incompressible + pages. We express this as a percentage (between 0% and 100%). Values close + to 100% mean we are not able to effectively benefit from compression. + Snapshot every 30s. + + + + + sonnyrao@google.com + chromeos-memory@google.com + + RAM savings in megabytes from using memory compression. This is the + difference between the RAM size before and after compression. Snapshot every + 30s. + + + + + sonnyrao@google.com + chromeos-memory@google.com + + Number of zero-filled pages that the OS is compressing. A large number + suggests wasteful allocation. Snapshot every 30s. + + + + + sonnyrao@google.com + chromeos-memory@google.com + + The fraction of compressed memory that consists of zero-filled pages. + Snapshot every 30s. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Errors returned by CreateFile on POSIX that PlatformFileError doesn't yet + support. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Errors returned by CreateFile on Windows that PlatformFileError doesn't yet + support. + + + + + olka@chromium.org + handellm@chromium.org + + Realtime period the thread is attempted to be configured with. Zero means + the default empirical configuration is used. Reported only on Mac. + + + + + olka@chromium.org + handellm@chromium.org + + Realtime thread period logged if it was applied successfully. Zero means the + default empirical configuration is used. Comparison with + PlatformThread.Mac.AttemptedRealtimePeriod may point to problematic + configurations. Reported only on Mac. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/plugin/histograms.xml b/tools/metrics/histograms/histograms_xml/plugin/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..49e83ed768fac1fe40168e937bac209549d14264 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/plugin/histograms.xml @@ -0,0 +1,214 @@ + + + + + + + + + + Please list the metric's owners. Add more owner tags as needed. + Record usage of PPB_Flash.Navigate() Pepper API. + + + + yzshen@chromium.org + thestig@chromium.org + Collects Flash usage data. + + + + tommycli@chromium.org + + Record how many throttled plugins are unthrottled, and by what method. + + + + + xhwang@chromium.org + media-dev@chromium.org + + The error code of a PPAPI broker load failure. Only reported on Windows. + + + + + xhwang@chromium.org + media-dev@chromium.org + The result from an attempt to load a PPAPI broker. + + + + xhwang@chromium.org + media-dev@chromium.org + The time spent to load a PPAPI broker. + + + + xhwang@chromium.org + media-dev@chromium.org + + The error code of a PPAPI plugin load failure. Only reported on Windows. + + + + + xhwang@chromium.org + media-dev@chromium.org + The result from an attempt to load a PPAPI plugin. + + + + xhwang@chromium.org + media-dev@chromium.org + The time spent to load a PPAPI plugin. + + + + gab@chromium.org + + The time it took to complete a synchronous IPC made from the PPAPI process. + + + + + timloh@google.com + joelhockey@google.com + + Records the number of Plugin VM apps in the registry at login time. This + only logs if Plugin VM has already benn enabled for the current user. + + + + + kimjae@google.com + timloh@google.com + Recorded at each time PluginVM DLC is installed. + + + + timloh@google.com + joelhockey@google.com + + Times when user is engaged and Plugin VM apps are running in the background, + but the user isn't focusing on an Plugin VM app window. See + PluginVm.EngagementTime.Total for further details. + + + + + timloh@google.com + joelhockey@google.com + + Times when user is engaged and focuses on a Plugin VM window. See + PluginVm.EngagementTime.Total for further details. + + + + + timloh@google.com + joelhockey@google.com + + Total of PluginVm.EngagementTime.Background and .Foreground, which is the + time the user is engaged and Plugin VM is running either in the foreground + or background. See PluginVm.EngagementTime.Total for further details. + + + + + timloh@google.com + joelhockey@google.com + + Total CrOS user session time (from login to logout) excluding times when + user "disengages": screen is locked or dims down due to user idle. + Engagement time metrics, along with foreground and background time, are only + collected on users with Plugin VM enabled. All four metrics are accumulated + and recorded to UMA once a day. For Total Plugin VM engagement time, see + PluginVm.EngagementTime.PluginVmTotal. + + + + + aoldemeier@chromium.org + okalitova@chromium.org + timloh@chromium.org + + The size of the PluginVm image downloaded in MB. Recorded each time PluginVm + image is sucessfully downloaded. + + + + + aoldemeier@chromium.org + okalitova@chromium.org + timloh@chromium.org + + Recorded at each attempt to launch PluginVm, recording whether this attempt + is successful or not. + + + + + timloh@chromium.org + chromeos-core-services@google.com + Recorded when the Plugin VM installer fails. + + + + aoldemeier@chromium.org + okalitova@chromium.org + timloh@chromium.org + + Recorded at each attempt to set up PluginVm, recording the setup result. As + of M83, errors are grouped together here and broken down in + PluginVm.SetupFailureReason. + + + + + aoldemeier@chromium.org + okalitova@chromium.org + timloh@chromium.org + + Recorded at each successful attempt to set up PluginVm, recording the time + that user spent waiting for setup to be finished. When error occurs during + setup and user clicks retry button - time between pressing retry button and + setup being finished is recorded. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/power/histograms.xml b/tools/metrics/histograms/histograms_xml/power/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..f3ffd78d2fb5b97c4967c98c22f3bf5865d88641 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/power/histograms.xml @@ -0,0 +1,1057 @@ + + + + + + + + + + eseckler@chromium.org + skyostil@chromium.org + + Total seconds of CPU time consumed by Chrome, split by process type as well + as core type and core frequency. Currently only implemented on Android. For + every second of CPU time consumed by a process on a specific CPU core type + and at a specific frequency, a sample is recorded into the bucket for the + frequency range. Samples are recorded periodically depending on the task + load of each process's main thread. The histogram thus shows the total sum + of CPU time seconds spent for a specific process and core type across all + users. + + Compared with Power.CpuTimeSecondsPerCoreTypeAndFrequency, the values in + this histogram are approximated from more widely supported global + per-CPU-core time_in_state stats, while + Power.CpuTimeSecondsPerCoreTypeAndFrequency reads per-thread time_in_state + stats that are only supported on newer Pixel devices (as of mid-2020). + + For a histogram of daily per-user values, select "Per-Client + Aggregation Mode". + + + + + tbroch@chromium.org + + The level of the backlight as a percentage when the user is on AC. Sampled + every 30 seconds. + + + + + tbroch@chromium.org + + The level of the backlight as a percentage when the user is on battery. + Sampled every 30 seconds. + + + + + tbroch@chromium.org + + Chrome OS battery charge health percentage. Sampled once when device starts + charging. + + + + + tbroch@chromium.org + + Chrome OS battery discharge rate in mW sampled every 30 seconds while the + device runs on battery. + + + + + tbroch@chromium.org + + Chrome OS battery discharge rate in mW while the system was suspended, + sampled at resume. Only reported if the system was on battery power both + before suspending and after resuming, if the energy level didn't increase + while suspended (which would indicate that an AC adapter was connected), and + if the system was suspended for at least a minute. + + + + + tbroch@chromium.org + + Counts the number of times we have read the battery status from sysfs and if + it gave us sensible values. + + + + + ryansturm@chromium.org + tbansal@chromium.org + + The drop in battery since the last operating system battery update as a + percent of total device battery. If the drop is not a round percentage + point, the unreported amount will be carried over until the battery level + drops by a full percentage point. Recorded when the battery level drops by + more than a percentage point. If the user charges the device, the battery + tracking is reset (the amount carried over is reset). This histograms sum is + most likely the most useful figure when comparing experiments. Recorded even + when Chrome is in the background. + + + + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge, + sampled at the end of a user session when the device is on AC. + + + + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge, + sampled at the end of a user session when the device is on battery. + + + + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge, + sampled at the start of a user session when the device is on AC. + + + + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge, + sampled at the start of a user session when the device is on battery. + + + + + tbroch@chromium.org + + Chrome OS remaining battery charge as percent of the maximum battery charge, + sampled when charging starts. + + + + + dianders@chromium.org + + Chrome OS (Snow RO firmware 2695.90.0 only) number of 8K chunks that were + fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0 + around 97% of the time and a non-zero value around 3% of the time. + + + + + dianders@chromium.org + + Chrome OS (Snow RO firmware 2695.90.0 only) number of 4-byte words that were + fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0 + around 97% of the time and a non-zero value around 3% of the time. Would be + exactly equal to Power.BitfixChunks if there were only one corrupted word in + each chunk but is sometimes several times higher. + + + + + bleung@chromium.org + tbroch@chromium.org + + Connected charging ports on Chrome OS. A sample is reported every time that + the power manager polls sysfs (typically every 30 seconds). Ordinals are + assigned based on the lexicographical ordering of power supply names from + sysfs and have no implied correspondence with ports' physical locations. For + example, with ports 'CROS_USB_PD_CHARGER0' and 'CROS_USB_PD_CHARGER1', + 'first' refers to the former and 'second' to the latter. To determine a + port's physical location, see the powerd charging_ports pref in the device's + overlay. + + + + + eseckler@chromium.org + skyostil@chromium.org + + For clients enrolled in CPU affinity restriction experiments (e.g. + restricting execution to little cores only), records whether the CPU + affinity for a process could be succcessfully set. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Total seconds of CPU time consumed by Chrome, split by process type as well + as core type and core frequency. Currently only implemented on Android. For + every second of CPU time consumed by a process on a specific CPU core type + and at a specific frequency, a sample is recorded into the bucket for the + frequency range. The histogram thus shows the total sum of CPU time seconds + spent for a specific process and core type across all users. + + For a histogram of daily per-user values, select "Per-Client + Aggregation Mode". + + + + + eseckler@chromium.org + skyostil@chromium.org + + Total seconds of CPU time consumed by Chrome, split by process type. + Currently only implemented on Android. For every second of CPU time consumed + by one process, a sample is recorded into the bucket for the process's type. + The histogram thus shows the total sum of CPU time seconds spent per process + type across all users. + + For a histogram of daily per-user values, select "Per-Client + Aggregation Mode". + + + + + eseckler@chromium.org + skyostil@chromium.org + + Total seconds of CPU time consumed by Chrome, split by process type and + thread type. Currently only implemented on Android. For every second of CPU + time consumed by one thread, a sample is recorded into the bucket for the + thread's type. CPU time consumed by a process that cannot be attributed to a + specific thread is recorded into the "UnattributedThread" bucket. + The histogram thus shows the total sum of CPU time seconds spent per thread + type (within processes of a specific type) across all users. + + For a histogram of daily per-user values, select "Per-Client + Aggregation Mode". + + + + + chirantan@chromium.org + abhishekbh@chromium.org + ravisadineni@chromium.org + + The amount of time a system spent awake every time it woke up in dark + resume. + + + + + chirantan@chromium.org + abhishekbh@chromium.org + ravisadineni@chromium.org + + The amount of time a system spent awake every time it woke up in dark resume + triggered by an unknown or unsupported wake trigger. + + + + + chirantan@chromium.org + abhishekbh@chromium.org + ravisadineni@chromium.org + + The amount of time a system spent awake every time it woke up in dark resume + triggered by a WiFi disconnect. + + + + + chirantan@chromium.org + abhishekbh@chromium.org + ravisadineni@chromium.org + + The amount of time a system spent awake every time it woke up in dark resume + triggered by a WiFi packet pattern match. + + + + + chirantan@chromium.org + abhishekbh@chromium.org + ravisadineni@chromium.org + + The amount of time a system spent awake every time it woke up in dark resume + triggered by a net detect SSID match. + + + + + chirantan@chromium.org + + The number of times a system woke up in dark resume in an hour. Note that + this value is scaled up or down to an hour based on the amount of time the + system spent in suspend. So if the system suspended for 20 minutes and woke + up 3 times, it would report a value of 9. + + + + + tbroch@chromium.org + + The result of attempting to read an external display's brightness on Chrome + OS. A read attempt is made after successfully requesting the brightness (see + Power.ExternalBrightnessRequestResult). + + + + + tbroch@chromium.org + + The result of requesting an external display's brightness on Chrome OS. A + request is sent when the user presses a brightness key and the current + brightness is not already cached. A successful request is followed shortly + thereafter by a read attempt (see Power.ExternalBrightnessReadResult). + + + + + tbroch@chromium.org + + The result of attempting to change an external display's brightness on + Chrome OS. A request is sent when the user presses a brightness key and the + current brightness is either already cached or successfully loaded. + + + + + tbroch@chromium.org + + The result of attempting to open an I2C device to control an external + display's brightness on Chrome OS. An attempt is made when a display is + connected to a device that lacks an internal display. + + + + + tbroch@chromium.org + + The time that the firmware took to resume the Chrome OS device from + suspend-to-RAM state when running on AC at pre-suspend time. + + + + + tbroch@chromium.org + + The time that the firmware took to resume the Chrome OS device from + suspend-to-RAM state when running on battery at pre-suspend time. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Records a sample for every 0.1 milliampere-hours of battery capacity that + are drained while Chrome is the foreground app and the device is on battery + power. Only supported on Android. The histogram thus shows the total sum of + battery capacity consumed across all users. + + For a histogram of daily per-user values, see the computed histogram + Power.DailyForegroundBatteryDrain. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Periodically samples the battery capacity drained while Chrome is the + foreground app and the device is on battery power. Sampled every 30 seconds + and when Chrome is backgrounded or the device connects to a charger. Sample + values are reported as provided by the battery capacity counter (in + microampere-hours). Because the resolution of this counter is rather coarse + (usually between .5 and 50 mAh), the uAh value may have been drained over a + longer time period than 30 seconds. See also + Power.ForegroundBatteryDrain.30SecondsAvg, which averages the values over + successive sampling points without change in counter values. + + Only supported on Android. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Periodically samples the battery capacity drained while Chrome is the + foreground app and the device is on battery power. Sampled every 30 seconds + and when Chrome is backgrounded or the device connects to a charger. Sample + values are reported as provided by the battery capacity counter (in + microampere-hours). Because the resolution of this counter is rather coarse + (usually between .5 and 50 mAh), the uAh value may have been drained over a + longer time period than 30 seconds. Only time intervals where Chrome was the + only foreground app are reported. See also + Power.ForegroundBatteryDrain.30SecondsAvg.Exclusive, which averages the + values over successive sampling points without change in counter values. + + Only supported on Android. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Periodically samples the battery capacity drained while Chrome is the + foreground app and the device is on battery power. Sampled every 30 seconds + and when Chrome is backgrounded or the device connects to a charger. Sample + values are reported in microampere-hours and averaged over successive + sampling points without a change in capacity counter values. + + Only supported on Android. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Periodically samples the battery capacity drained while Chrome is the + foreground app and the device is on battery power. Sampled every 30 seconds + and when Chrome is backgrounded or the device connects to a charger. Sample + values are reported in microampere-hours and averaged over successive + sampling points without a change in capacity counter values. Only time + intervals where Chrome was the only foreground app are reported. + + Only supported on Android. + + + + + eseckler@chromium.org + skyostil@chromium.org + + Records a sample for every 0.1 milliampere-hours of battery capacity that + are drained while Chrome is the foreground app and the device is on battery + power. Only supported on Android. The histogram thus shows the total sum of + battery capacity consumed across all users. Only time intervals where Chrome + was the only foreground app are reported. + + For a histogram of daily per-user values, see the computed histogram + Power.DailyForegroundBatteryDrain.Exclusive. + + + + + eseckler@chromium.org + skyostil@chromium.org + + A companion metric for Power.ForegroundBatteryDrain.30SecondsAvg which + reports the time interval between successive capacity drops reported by the + battery manager. + + Only supported on Android. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Number of times that that the screen has been dimmed in response to user + inactivity, reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Number of times that that the screen has been turned off in response to user + inactivity, reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Number of times that that the system has suspended in response to user + inactivity, reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time since the screen dimmed sampled when the user + becomes active again if the device runs on AC. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time since the screen dimmed sampled when the user + becomes active again if the device runs on battery. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time since the screen turned off sampled when the user + becomes active again if the device runs on AC. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time since the screen turned off sampled when the user + becomes active again if the device runs on battery. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time sampled when the user becomes active again if the + device runs on AC. + + + + + tbroch@chromium.org + jiameng@chromium.org + + Chrome OS user idle time sampled when the user becomes active again if the + device runs on battery. + + + + + tbroch@chromium.org + + The time that the kernel took to resume the Chrome OS device from + suspend-to-RAM state when running on AC at pre-suspend time. + + + + + tbroch@chromium.org + + The time that the kernel took to resume the Chrome OS device from + suspend-to-RAM state when running on battery at pre-suspend time. + + + + + tbroch@chromium.org + + The time that the kernel took to suspend-to-RAM the Chrome OS device when + running on AC. + + + + + tbroch@chromium.org + + The time that the kernel took to suspend-to-RAM the Chrome OS device when + running on battery. + + + + + tbroch@chromium.org + + The level of the keyboard backlight as a percentage. Sampled every 30 + seconds. + + + + + tbroch@chromium.org + + The length of time, in seconds, that a user spent in a single session. + Values for this metric are clamped to 12 hours, so the last bucket should be + considered to be including all metrics above 12 hours. + + + + + tbroch@chromium.org + + Number of times that that the system has suspended in response to its lid + being closed, reported daily. The count is accumulated through the day, + spanning reboots, and sent once the system clock indicates that a full day + or more has passed since the last report. If the system is suspended or off + for more than a day, the current count will be reported immediately the next + time the system boots, but the skipped days will not be reported. Chrome OS + only. + + + + + lgrey@chromium.org + markchang@chromium.org + + Instantaneous power consution in milliwatts, for the system as a whole and + broken down by component. Only recorded on macOS. NB: The collection method + was changed in May 2019, which may look like a regression in timeline view. + + + + + lgrey@chromium.org + + When metrics collection started, records true if a handle to the System + Management Controller (SMC) was successfully opened to monitor power + consumption, false otherwise. If false, a system API might have changed in a + new version of macOS, or Chrome might be running in a nonstandard + environment (VM, hackintosh). Only recorded on macOS. + + + + + olivierli@chromium.org + lgrey@chromium.org + + Every minute after startup a measure of the remaining and maximum battery + capacity is taken. Then a ratio of the remaining capacity over the maximum + capicity is calculated and scaled by 10000. (For example: 13 / 2000 = 0.0065 + ; 0.0065 * 10000 = 65). Power.Mac.BatteryDischarge is the the delta in this + relative capacity measure compaired to the measurement that was taken a + minute before. This metric is only recorded when on battery power. Only + recorded on macOS. + + + + + lgrey@chromium.org + + Whether the user's machine is on battery power. Sampled once per minute. + + + + + lgrey@chromium.org + + Thermal state of the user's machine as reported by macOS's [NSProcessInfo + thermalState]. Sampled once per minute. + + + + + tbroch@chromium.org + + Reasons why power-management-related daily metrics were reported. Chrome OS + only. + + + + + tbroch@chromium.org + jiameng@chromium.org + + The number of times that the Automatic Light Sensor (ALS) adjusted the + brightness during a session. Values for this metric are clamped to 10k + count, so the last bucket should be considered to be including all metrics + above 10k. + + + + + tbroch@chromium.org + + The number of user sessions that occured since the last time that the device + was charged. Values for this metric are clamped at 10k, so the last bucket + should be considered to include all metrics about 10k. + + + + + tbroch@chromium.org + + The amount of time between the user pressing the power button and Chrome + acknowledging the button-down event on Chrome OS. Values for this metric are + capped to two seconds. + + + + + tbroch@chromium.org + + The amount of time between the user pressing the power button and releasing + it on Chrome OS. + + + + + minch@chromium.org + xdai@chromium.org + Actions performed while the power button menu is open. + + + + minch@chromium.org + xdai@chromium.org + + Press power button in laptop mode will result in different scenarios + according to the power button up state. Counts the different power button + press scenarios in laptop mode. + + + + + minch@chromium.org + xdai@chromium.org + + Press power button in tablet mode will result in different scenarios + according to the power button up state. Counts the different power button + press scenarios in tablet mode. + + + + + bleung@chromium.org + tbroch@chromium.org + + The maximum power supported by the connected power supply on Chrome OS. A + sample is reported every time that the power manager polls sysfs (typically + every 30 seconds) and sees a connected supply. + + + + + bleung@chromium.org + tbroch@chromium.org + + The maximum voltage supported by the connected power supply on Chrome OS. A + sample is reported every time that the power manager polls sysfs (typically + every 30 seconds) and sees a connected supply. + + + + + bleung@chromium.org + tbroch@chromium.org + + The type of the connected power supply on Chrome OS. A sample is reported + every time that the power manager polls sysfs (typically every 30 seconds) + and sees a connected supply. + + + + + tbroch@chromium.org + + The reason for the Chrome OS power manager shutting down or rebooting the + system. + + + + + thanhdng@chromium.org + jiameng@chromium.org + Type of messages that are reported by smart charging. + + + + tbroch@chromium.org + + The number of suspend attempts on Chrome OS. Samples are reported before + each attempt, so this histogram may include cases where the system crashed + instead of suspending. + + + + + tbroch@chromium.org + + The number of suspend attempts performed for a single suspend request (e.g. + triggered by the lid being closed) that was eventually canceled on Chrome + OS. This also includes requests that were canceled due to the system + eventually shutting down due to repeated suspend failures. + + + + + tbroch@chromium.org + + The number of suspend attempts performed for a single suspend request (e.g. + triggered by the lid being closed) that eventually succeeded on Chrome OS. + This includes the successful attempt. + + + + + tbroch@chromium.org + + The results of suspend attempts on Chrome OS. Samples are reported after + each attempt. + + + + + tbroch@chromium.org + + Chrome OS time in minutes spent in suspend-to-RAM mode sampled at boot + (i.e., the device most likely ran out of battery while in suspend). + + + + + tbroch@chromium.org + + Chrome OS time in minutes spent in suspend-to-RAM mode sampled at resume. + + + + + tbroch@chromium.org + jiameng@chromium.org + + The number of times that the user adjusted the brightness during a session + when on AC. Values for this metric are clamped to 10k count, so the last + bucket should be considered to be including all metrics above 10k. + + + + + tbroch@chromium.org + jiameng@chromium.org + + The number of times that the user adjusted the brightness during a session + when on battery. Values for this metric are clamped to 10k count, so the + last bucket should be considered to be including all metrics above 10k. + + + + + jiameng@chromium.org + + What happens when UserActivityManager receives a screen dim imminent + notification. Only applicable to Chrome OS. + + + + + jiameng@chromium.org + + What happens after screen is dimmed following model instruction. Only + applicable to Chrome OS. + + + + + jiameng@chromium.org + + What happens after screen dim is deferred following model instruction. Only + applicable to Chrome OS. + + + + + jiameng@chromium.org + + What happens after screen is dimmed by powerd by ignoring the model + instruction. Only applicable to Chrome OS. + + + + + jiameng@chromium.org + + Status of logging previous idle event after a screen dim imminent signal is + received. Only applicable to Chrome OS. + + + + + alanlxl@chromium.org + amoylan@chromium.org + jiameng@chromium.org + + Records the event (various failures or success) of loading smart dim + component. Only applicable to Chrome OS. + + + + + alanlxl@chromium.org + amoylan@chromium.org + jiameng@chromium.org + + Records the type of expected version (default, experimental or empty) used + by smart dim component installer. Only applicable to Chrome OS. + + + + + alanlxl@chromium.org + amoylan@chromium.org + jiameng@chromium.org + + Records the worker type that is used by smart dim ml agent to make a + decision. Only applicable to Chrome OS. + + + + + amoylan@chromium.org + jiameng@chromium.org + napper@chromium.org + pmalani@chromium.org + + The time elapsed between a Smart Dim Inference Request being sent to the ML + model, and the request being canceled before the result is returned. + + + + + amoylan@chromium.org + jiameng@chromium.org + napper@chromium.org + pmalani@chromium.org + + The time elapsed between a Smart Dim Inference Request being sent to the ML + model and a result being returned. + + + + + jiameng@chromium.org + + This is the status code returned by the model when calculating a user + inactivity score. If it is any value other than 0 (success), then some issue + has occurred in the score calculation, either because preprocess was not + loaded or parsed correctly, or the preprocessor failed to process a + RankerExample. Only applicable to Chrome OS. + + + + + jiameng@chromium.org + + The result of parsing the dim threshold parameter value. Only applicable to + Chrome OS. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/print/histograms.xml b/tools/metrics/histograms/histograms_xml/print/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..2323dabd544b11b82d75a9674308eda6c80d99c1 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/print/histograms.xml @@ -0,0 +1,234 @@ + + + + + + + + + + rbpotter@chromium.org + thestig@chromium.org + + Actions performed by the user when the print destination search widget is + shown to the user. + + + + + thestig@chromium.org + dhoss@chromium.org + + Time from when print preview is initiated until the initial preview is sent + to the preview tab for rendering. + + + + + + + thestig@chromium.org + dhoss@chromium.org + + Time from when print preview is initiated until the preview PDF generation + is started. + + + + + thestig@chromium.org + + Count the number of requests received to show the manage printers dialog. + + + + + thestig@chromium.org + dhoss@chromium.org + + Count the total number of printers shown in destination drop down list. + + + + + thestig@chromium.org + dmazzoni@chromium.org + + The average size of a page in the printed document when the source is HTML. + + + + + thestig@chromium.org + dhoss@chromium.org + + The average size of a page in the printed document when the source is PDF. + + + + + rbpotter@chromium.org + + Track type of documents printed (HTML vs PDF). Recorded immediately after a + user requests that a document be printed. + + + + + gavinwill@chromium.org + cros-peripherals@google.com + + Records true if the user printed, or false if the user canceled, while being + shown a red/error status for their selected printer on Chrome OS. + + + + + gavinwill@chromium.org + cros-peripherals@google.com + + Records true if the user printed, or false if the user canceled, while being + shown a green/good status for their selected printer on Chrome OS. + + + + + gavinwill@chromium.org + cros-peripherals@google.com + + Records true if the user printed, or false if the user canceled, while being + shown a grey/unknown status for their selected printer on Chrome OS. + + + + + thestig@chromium.org + + Track the popularity of print settings. (Settings when printing to PDF are + excluded from this statistic.) + + + + + rbpotter@chromium.org + thestig@chromium.org + + Actions performed by the user interacting with print settings UI elements. + + + + + thestig@chromium.org + + The number of times regenerate preview requests received before the user + clicked the cancel button. + + + + + thestig@chromium.org + + The number of times regenerate preview requests received before the first + preview data is available. + + + + + thestig@chromium.org + dhoss@chromium.org + + The number of times regenerate preview requests received before the user + clicked the print button. + + + + + + + thestig@chromium.org + dhoss@chromium.org + + Time taken to render and generate PDF for print preview. (Includes time to + reflow the page back to normal, but not the time to reflow the page to + prepare for printing.) + + + + + + + thestig@chromium.org + dhoss@chromium.org + + Time taken to render and generate PDF for print preview divided by the + number of pages. (Includes time to reflow the page back to normal, but not + the time to reflow the page to prepare for printing.) + + + + + thestig@chromium.org + dhoss@chromium.org + + Count how frequently a set of pre-defined print preview errors occur. + + + + + thestig@chromium.org + Time taken to render each PDF page for print preview. + + + + thestig@chromium.org + Time taken to render to PDF for print preview. + + + + thestig@chromium.org + + Action taken by the user in the preview tab such as print, cancel, print to + pdf and show advanced print settings dialog. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/printing/histograms.xml b/tools/metrics/histograms/histograms_xml/printing/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9a5f84e001d3ffe5ac13bdc7acddb7f08be89ebe --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/printing/histograms.xml @@ -0,0 +1,391 @@ + + + + + + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to EMF. + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to EMF with + the GDI Text experiment turned on. + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to EMF with + the reduced rasterization feature turned on. + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to EMF with + the reduced rasterization feature turned on and the GDI Text experiment + turned on. + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to level 2 + PostScript. + + + + + thestig@chromium.org + awscreen@chromium.org + + On Windows, the average size of a printed page after converting to level 3 + PostScript. + + + + + thestig@chromium.org + awscreen@chromium.org + + On desktop, the average size of a printed page after converting to PWG + Raster format. + + + + + skau@chromium.org + + Records whether resolution of a .local address via mDNS was successful. The + metric is recorded during attempted setup of a printer discovered via mDNS. + + + + + skau@chromium.org + pawliczek@chromium.org + + Records the highest IPP version reported by a printer when we query the + printer for attributes. Useful to understand the population of printers + currently used. Recorded during printer setup for IPP printers. Recorded + only on ChromeOS. + + + + + vkuzkokov@chromium.org + skau@chromium.org + + Records when advanced attribute is set for a print job. Recorded when print + job is being formed for sending. + + + + + vkuzkokov@chromium.org + skau@chromium.org + + Records the number of advanced capabilities made available by a single + printer. Recorded when attributes are pulled from the printer. + + + + + skau@chromium.org + + Record if the request for IPP attributes was successful during printer + setup. This only occurs for setup attempts of IPP and IPPS printers. + Starting with M79, this is only recorded if the printer was reachable. + + + + + vkuzkokov@chromium.org + skau@chromium.org + + Records the number of advanced attributes used by a single print job. + Recorded when print job is being formed for sending. + + + + + skau@chromium.org + + Record if the request for IPP attributes was successful in reaching the + printer. Recorded during the attempt to setup IPP/IPPS printers. + + + + + jschettler@chromium.org + project-bolton@google.com + + Records the print job duration of a cancelled print job. Includes time spent + in a suspended or error state. Only recorded on Chrome OS. + + + + + jschettler@chromium.org + project-bolton@google.com + + Records the print job duration of a done/completed print job. Includes time + spent in a suspended or error state. Only recorded on Chrome OS. + + + + + skau@chromium.org + + The final status of every print job that was succesfully queued. Only used + on Chrome OS. + + + + + luum@chromium.org + cros-printing-dev@chromium.org + + Records when a synced printer's outdated separate make and model strings + have been migrated to the new merged form. Recorded during initial sync + across PrintersSyncBridge. + + + + + skau@chromium.org + project-bolton@google.com + + The number of detected network printers that have not been saved. Recorded + when the user navigates to the OS Settings Printing page to set up printers. + Only recorded on Chrome OS. + + + + + jschettler@chromium.org + project-bolton@google.com + + Records the total size of the printed document (PDF) sent to CUPS. Only + recorded on Chrome OS. + + + + + skau@chromium.org + + The protocol for a printer that was added. Used to track printer churn by + protocol. Only on Chrome OS. + + + + + skau@chromium.org + + The protocol for a printer that was removed. Used to track printer churn by + protocol. Only on Chrome OS. + + + + + skau@chromium.org + + The number of printers shown in the discovered printers dialog during + printer set up. Only recorded on Chrome OS. + + + + + skau@chromium.org + + The success or error code for the setup of a CUPS printer. Recorded when + setup is attempted through the settings dialogs. Only recorded on Chrome OS. + + + + + gavinwill@chromium.org + cros-peripherals@google.com + + Records the success outcome of a printer status query to a local printer. + + + + + gavinwill@chromium.org + cros-peripherals@google.com + + Records the status reasons returned by a local printer from a printer status + query. Each returned printer status request can contain multiple status + reasons so summing these buckets will overcount the total # of status + queries. + + + + + skau@chromium.org + + The size of the print queue when a print job is initially queued. When the + first job is started, a zero is recorded. Only used on Chrome OS. + + + + + jimmyxgong@chromium.org + cros-peripherals@google.com + + Records the entry point of where the Print Management App was launched from + in Chrome OS. Used to track the relative entry points of the app. + + + + + skau@chromium.org + + Records the protocol for a selected printer in Chrome OS. Used to track + usage of the various printer protocols. Since a selection occurs when print + preview is opened, this will count at least one every time that happens if a + CUPS printer was selected. + + + + + skau@chromium.org + project-bolton@google.com + + The total number of detected network printers. Recorded when the user + navigates to the OS Settings Printing page to set up printers. Only recorded + on Chrome OS. + + + + + dhoss@chromium.org + thestig@chromium.org + + Records instances in which print preview encounters an unknown PPD color + model. + + + + + baileyberro@chromium.org + cros-peripherals@google.com + + Records the source from which a USB printer was configured in Chrome OS. + Used to track relative usage of the various printer setup routes. Only emits + after a successful printer setup. + + + + + skau@chromium.org + luum@chromium.org + + Tracks printer setups with a valid/invalid PpdReference. PpdReferences are + invalid if more than one field is specified. Due to a bug, some invalid + references could be saved in users' profile, track if they need to be + migrated. Recorded during printer install. Only tracked on ChromeOS. + + + + + kdlee@chromium.org + cros-printing-dev@chromium.org + + The success or error code for the setup of a Zeroconf printer. Recorded when + setup is attempted through the settings dialogs. Only recorded on Chrome OS. + Printer setup results go into either this histogram or the + Printing.CUPS.PrinterSetupResult histogram - not both. + + + + + vkuzkokov@chromium.org + skau@chromium.org + + Records the time it takes to pull capabilities of a single printer from + OS-specific backend. Recorded immediately on completion. + + + + + pawliczek@chromium.org + skau@chromium.org + + Records the number of print servers that must be queried according to + policies. Only non-zero values are recorded. The histogram is emitted when + ExternalPrintServers* policies are loaded and processed. It happens when a + profile is opened or when one of the policies is modified. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/profile/histograms.xml b/tools/metrics/histograms/histograms_xml/profile/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..88c6cc2c8695df971c112561f15947f8232fc9a4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/profile/histograms.xml @@ -0,0 +1,702 @@ + + + + + + + + + + rogerta@chromium.org + The frequency of ways that new user profiles are added. + + + + jkrcal@chromium.org + droger@chromium.org + + Classification of what account categories out of {consumer, enterprise} + appear or appeared in this profile since the last time gaia cookies got + deleted. Thus, this also includes signed-out accounts. If both categories + appeared, it also distinguishes whether sync is enabled and for which of + them. Recorded on every activation of a Chrome window (for the respective + profile). + + + + + jkrcal@chromium.org + droger@chromium.org + + Classification of what gaia names appear or appeared in this profile since + the last time gaia cookies got deleted. Thus, this also includes signed-out + accounts. In order to protect privacy, only reports whether multiple + distinct gaia names appeared in this profile and if so, whether sync is + enabled for one of them. Furthermore, this metric uses a low-entropy hash to + detect distinct names. In case of a rare hash collision (less than 0.1% of + cases), multiple names get recorded as a single name. Recorded on every + activation of a Chrome window (for the respective profile). + + + + + bsazonov@chromium.org + chrome-signin-team@google.com + + Track user interactions that can be performed in the Android account + management menu. + + + + + Please list the metric's owners. Add more owner tags as needed. + The number of installed apps when a profile is opened. + + + + jkrcal@chromium.org + droger@chromium.org + The frequency of selection of each avatar. + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the bookmarks database. + + + + msarda@chromium.org + tangltom@chromium.org + + Recorded every time a browser window becomes active. Each profile on a + client is assigned a unique bucket, i.e. whenever a browser window of + profile x becomes active, an entry is recorded in bucket x. + + Example: A user has 2 profiles and opens 1 browser window for each of them. + When the user switches back and forth between the windows, multiple entries + will be recorded in bucket 1 and 2, corresponding to the profiles. + + Note: The guest profile has bucket 0. Regular profiles start at bucket 1. + Incognito browser windows count towards the original profile. + + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the cookies database. + + + + treib@chromium.org + rogerta@chromium.org + msarda@chromium.org + Result (final status) when creating a new profile. + + + + treib@chromium.org + michaelpg@chromium.org + msarda@chromium.org + + Time elapsed from when the handler received the message that a user clicked + 'Create' until the creation either failed with a local error (see + Profile.CreateResult), was canceled (also recorded in + Profile.CreateTimeCanceledNoTimeout), or completed successfully. + + + + + msarda@chromium.org + droger@chromium.org + + This histogram tracks the deletion of the profile. This tracks when the + cleanup actually takes place, not the UI interaction. The parameter + indicates if the profile was signed in or not; true means the profile was + signed in, false means the profile was not signed in. + + + + + msarda@chromium.org + droger@chromium.org + anthonyvd@chromium.org + + This histogram tracks which UI screen was used to initiate and confirm the + deletion of a profile. This does not track when the profile is actually + deleted, which is an asynchronous process that happens later. + + + + + msarda@chromium.org + tangltom@chromium.org + + This histogram tracks whether the accounts cached in the GAIA cookie service + manager are stale when presenting the user menu when DICE is enabled. + + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the extension cookies database. + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the favicons database. + + + + hajimehoshi@chromium.org + kouhei@chromium.org + Size of the history database. + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + This histogram records the lifetime duration of incognito profiles. It is + recorded once an off the record profile for an incognito session is closed. + + + + + droger@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Recorded when an actionable item(e.g. button, link) in the profile menu is + clicked. + + + + + droger@chromium.org + jkrcal@chromium.org + + When the profile menu is opened, after the identity animation was shown, + this records the time since the animation was shown. In the control group + for the identity pill experiment, this is still recorded as the time since + the animation *would have been* shown. + + + + + droger@chromium.org + siyua@chromium.org + + When the profile menu is opened, after the avatar was highlighted, this + records the time since the highlight was shown. + + + + + rogerta@chromium.org + + Counts of users added and deleted. Percentages are not meaningful. Please + look at the ratio of the counts/percentages. + + + + + msarda@chromium.org + droger@chromium.org + + Counts the number of Google-managed accounts linked to a profile. This may + be counted multiple times per profile. Please review with the "Show + user counts" option enabled on the dashboard. + + + + + droger@chromium.org + feuunk@chromium.org + + Counts the number of profiles on a user's machine every 24 hours while + Chrome is running. + + As opposed to Profile.NumberOfProfiles, this counts only profiles that have + been used in the last 28 days. + + + + + agawronska@chromium.org + michaelpg@chromium.org + cros-families@google.com + + Counts the number of locally managed profiles on a user's machine every 24 + hours while Chrome is running, among cases with at least one profile. + + This counts only profiles that have been used in the last 28 days. + + + + + feuunk@chromium.org + msarda@chromium.org + + Counts the number of profiles that have a user-defined name on a user's + machine every 24 hours while Chrome is running. + + This counts only profiles that have been used in the last 28 days. + + + + + droger@chromium.org + jkrcal@chromium.org + + Counts the number of profiles on a user's machine every 24 hours while + Chrome is running. + + This counts the total number of profiles on the user's device, regardless of + whether they've been used recently. + + + + + jkrcal@chromium.org + droger@chromium.org + + Records the count of profiles for each profile switch (incl. switching + between concurrently open profiles by activating their browser windows). The + count excludes the Guest profile so records in bucket 1 denote switches + between the single profile and the Guest profile. + + + + + msarda@chromium.org + droger@chromium.org + + Counts the number of signed-in (syncing) profiles with GAIA authentication + error on a user's machine every 24 hours while Chrome is running. + + This counts only profiles that have been used in the last 28 days. + + + + + droger@chromium.org + jkrcal@chromium.org + + Counts the number of signed-in (syncing) profiles on a user's machine every + 24 hours while Chrome is running. + + This counts only profiles that have been used in the last 28 days. + + + + + msarda@chromium.org + droger@chromium.org + + Counts the number of signed-in (syncing) profiles that are using the GAIA + image as the avatar icon. Note that profiles with a GAIA image but without + Sync consent are not counted. This is counted every 24 hours while Chrome is + running. + + This counts only profiles that have been used in the last 28 days. + + + + + msarda@chromium.org + droger@chromium.org + + Counts the number of profiles unused within the past 28 days on a user's + machine. This is recorded every 24 hours while Chrome is running. + + + + + agawronska@chromium.org + michaelpg@chromium.org + cros-families@google.com + + Tracks the percentage (0-100) of profiles that are locally managed, recorded + when Chrome starts up. + + + + + tnagel@chromium.org + + The error with the current user profile that caused an error dialog to be + shown. This dialog is shown usually when there is some sort of corruption in + the user's profile data. + + + + + msarda@chromium.org + tangltom@chromium.org + + Browsing session duration in minutes, recorded per profile. Each profile on + a client is assigned a unique bucket. + + Recorded when the user switches profiles, after some time of + inactivity(usually 5 minutes) or at browser shutdown. + + Example: A user has 2 profiles. They open a browser window of profile 1 and + interact with the browser for 8 minutes. Then they open a browser window of + profile 2 and interact with the browser for 3 minutes. Then they do nothing + (=stay inactive) for while. The recorded values will be: (bucket 1: 8), + (bucket 2: 3). + + Note: The guest profile has bucket 0. Regular profiles start at bucket 1. + Incognito profiles count towards the original profile. + + + + + jkrcal@chromium.org + droger@chromium.org + + The state of profile avatars as would be displayed to the user in the + profile picker. Recorded on startup of Chrome and whenever Chrome is used + after at least 30 minutes of inactivity. + + + + + jkrcal@chromium.org + droger@chromium.org + + The number of days since a profile was last used. Recorded on startup of + Chrome and whenever Chrome is used after at least 30 minutes of inactivity. + + + + + jkrcal@chromium.org + droger@chromium.org + + The state of profile name as would be displayed to the user in the profile + picker. Recorded on startup of Chrome and whenever Chrome is used after at + least 30 minutes of inactivity. + + + + + jkrcal@chromium.org + droger@chromium.org + + The type of profile's unconsented primary account. Recorded on startup of + Chrome and whenever Chrome is used after at least 30 minutes of inactivity. + + + + + Please list the metric's owners. Add more owner tags as needed. + + Counts of when users switch to using their GAIA photo instead of an avatar + icon or the opposite when they switch back to an avatar icon instead of + their GAIA photo. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Number of times and ways the user customized the sync options of their + profile. Percentages are not meaningful. To determine percentages, take the + count of a given action over the count of number of customizations. The + histogram has expired in '2018-08-30' and is resurrected in '2020-03-09'. + + + + + msarda@chromium.org + droger@chromium.org + + Time required to open the UserManager, from when it started to show until + when its javascript started executing. + + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the top sites database. + + + + Please list the metric's owners. Add more owner tags as needed. + Total size of all history databases. + + + + Please list the metric's owners. Add more owner tags as needed. + Total size of the profile data (excluding sub-folders). + + + + robertshield@chromium.org + + Indicates whether a profile had a reset trigger that caused it to launch a + reset flow. The presence of this trigger is recorded during profile + creation. + + + + + msarda@chromium.org + droger@chromium.org + + Recorded when a profile name and/or avatar was updated from the settings + page. + + + + + msarda@chromium.org + tangltom@chromium.org + + Helper histogram to track user actions per profile. Recorded when there is + an active profile browser instance and a UMA UserAction is recorded, i.e. if + there's an active profile, a recording of a UMA UserAction will result in a + recording of a sample in this histogram. + + Each profile on a client is assigned a unique bucket, i.e. whenever a user + action happens in a browser of profile x, an entry is recorded in bucket x. + + Example: A user has 2 profiles and opens a browser window for each of them. + When the user adds a new tab in each of the browsers, an entry is recorded + in bucket 1 and 2, corresponding to the profiles. (Adding a new tab is a + recorded user metrics action.) + + Note: The guest profile has bucket 0. Regular profiles start at bucket 1. + Incognito profiles count towards the original profile. + + + + + anthonyvd@chromium.org + + Whether the active profile is a guest profile when -validateMenuItem in the + ProfileMenuController gets an invalid value for the current profile's index. + + + + + anthonyvd@chromium.org + + The count of profiles in the avatar menu when -validateMenuItem in the + ProfileMenuController gets an invalid value for the current profile's index. + + + + + anthonyvd@chromium.org + + The selector associated with the menu item when -validateMenuItem in the + ProfileMenuController gets an invalid value for the current profile's index. + + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the visited links database. + + + + Please list the metric's owners. Add more owner tags as needed. + Size of the web data database. + + + + vasilii@chromium.org + ewald@chromium.org + + Whether any profile was shown in the list when the profile chooser was + opened. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the state of the "Ask on startup" user preference that + controls whether the profile picker should be shown on startup. Recorded on + startup of Chrome. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the state of the "Ask on startup" checkbox upon user + action to check/uncheck "Ask on startup" in the profile picker + main screen. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Whether the user picked to create a desktop shortcut for the new profile + created through the local profile creation in the profile picker. Recorded + on platforms where desktop shortcut is enabled. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the theme color of a new profile just created through the profile + picker local profile creation. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the reason why the profile picker has been shown to the user. + Recorded every time the profile picker window is shown or reactivated. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the time between Chrome startup and the call to + ProfilePickerView::Display(). Only recorded when the profile picker is shown + at startup. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the time between web view creation and the first paint. Only + recorded when the profile picker is shown at startup. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the time between web view creation and main view being initialized + in javascript. Only recorded when the profile picker is shown at startup. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the time between ProfilePickerView::Display() is called and the web + view creation. Only recorded when the profile picker is shown at startup. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Represents user navigation in the profile picker. Recorded every time a + different UI is visible in the profile picker. + + + + + msalama@chromium.org + chrome-signin-team@google.com + + Records the action performed by the user in the profile picker. + + + + + proberge@chromium.org + + Encodes from where the request for resetting the profile settings + originated. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/quickoffice/histograms.xml b/tools/metrics/histograms/histograms_xml/quickoffice/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..f495735d500bd550d41b902873a9e6cc4f79ff09 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/quickoffice/histograms.xml @@ -0,0 +1,233 @@ + + + + + + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of cells that contain formatting data in the default + worksheet when a comma separated value spreadsheet is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of non-empty cells in the default worksheet when a comma + separated value spreadsheet is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of worksheets when a comma separated value spreadsheet is + opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the page count when a compound binary format document is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the paragraph count when a compound binary format document is + opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the section count when a compound binary format document is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the page count when an OOXML format document is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the paragraph count when an OOXML format document is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the section count when an OOXML format document is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the various different error types encountered when opening and + reading MS Office file formats in the Quickoffice viewer. These range from + Nacl crashes and uncaught javascript exceptions to document errors inside + Quickoffice Web Toolkit (eg QOWT). The errors are recorded against the file + format in which they occurred. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the various different file types supported by Quickoffice (like MS + Word, Excel, Powerpoint files) when they opened in the browser to measure + which file formats are most popular. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of slide masters when a compound binary format + presentation is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the slide count when a compound binary format presentation is + opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of slide masters when an OOXML format presentation is + opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the slide count when an OOXML format presentation is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of cells that contain formatting data in the default + worksheet when a compound binary format spreadsheet is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of non-empty cells in the default worksheet when a + compound binary format spreadsheet is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of worksheets when a compound binary format spreadsheet + is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of cells that contain formatting data in the default + worksheet when an OOXML format spreadsheet is opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of non-empty cells when an OOXML format spreadsheet is + opened. + + + + + dpnkar@google.com + meenakshiv@google.com + + Records the number of worksheets when an OOXML format spreadsheet is opened. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/quota/histograms.xml b/tools/metrics/histograms/histograms_xml/quota/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..8a15c227daf46086aafad128122565d567b19c2d --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/quota/histograms.xml @@ -0,0 +1,258 @@ + + + + + + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + How many kilobytes are how old. Similar to |AgeOfOrigin| except a sample is + added for each kilobyte of an origin's data. Logged hourly for all origins + with stored data. + + + + + jarrydg@chromium.org + + How many days it's been since an origin's temporary storage has been + accessed. Logged hourly for all origins with stored data. + + + + + jarrydg@chromium.org + + Amount of free disk space for the storage directory. Logged at irregular + intervals. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Amount of free disk space for the storage directory. Logged when collecting + usage information. + + + + + jarrydg@chromium.org + + The number of days since an origin was last chosen to be evicted from the + storage, recorded each time the origin is evicted (except for the first + eviction). + + + + + jarrydg@chromium.org + + Difference between acceptable lower limit of diskspace and actual free + diskspace at beginning of an eviction round. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Amount of usage used by evicted origins in an eviction round. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + The number of times the evicted origin was accessed. Logged when the origin + is evicted. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + The number of days since the evicted origin was last accessed. Logged when + the origin is evicted. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + Number of evicted origins in an hour. + + + + jarrydg@chromium.org + Number of eviction rounds in an hour. + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + The size of the global temporary storage pool. Logged at irregular + intervals. + + + + + jarrydg@chromium.org + Global usage of persistent storage. + + + + jarrydg@chromium.org + Global usage of temporary storage. + + + + jarrydg@chromium.org + Number of evicted origins per round. + + + + jarrydg@chromium.org + + If our hardcoded OS accomodation is too large for the volume size, we define + the value as a fraction of the total volume size instead. The + OSAccomodationDelta is the difference between the hardcoded and computed + values. + + + + + jarrydg@chromium.org + + Percentage of the storage device that is free. Logged at irregular + intervals. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Percentage of the storage device that is free. Logged when collecting usage + information. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Percentage of an origin's quota that is being used by the origin. Logged at + irregular intervals. + + + + + jarrydg@chromium.org + + Percentage of the storage device that is being use for temporary storage. + Logged when collecting usage information. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + The quota value computed for an origin using temporary storage. Logged at + irregular intervals. (In the process of writing new data, storage systems + consult the quota system for "usage and quota" to determine if + there is sufficient space available for the new data. This value is logged + at the time of that consultation. The frequency is dependent on how + individual websites use the various storage apis.) + + + + + jarrydg@chromium.org + Number of skipped eviction rounds in an hour. + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + While accumulating usage information, ClientUsageTracker is encountering + invalid origins. This enum histogram will capture the type of invalid + origins that are encountered. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + Time between two consecutive active eviction rounds. + + + + jarrydg@chromium.org + Time spent to an eviction round. + + + + jarrydg@chromium.org + + Total disk space for the storage directory. Logged at irregular intervals. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + Disk space (in MB) currently used by an origin. Logged hourly. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/renderer/histograms.xml b/tools/metrics/histograms/histograms_xml/renderer/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..05fdb33719ade7934a9a5c4f646b5a651f022014 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/renderer/histograms.xml @@ -0,0 +1,474 @@ + + + + + + + + + + hartmanng@chromium.org + + Total count of the number of RenderLayers which are scrollable areas, need + to be promoted to stacking containers, and will use composited scrolling. + Each bucket is sampled at most once per RenderLayer, when the RenderLayer + first becomes scrollable, first needs to become a stacking container, and + first uses composited scrolling, respectively. + + + + + avi@chromium.org + + The length of time render processes are hung, in milliseconds. Note that + because technically speaking render processes are "hung" from the + moment an input event is sent to them until the moment that they return an + ACK, only hangs of minimum length 5s are recorded. Note that this combines + measurements from both renderer processes that recover on their own, and + render processes that are killed. + + + + + dfalcantara@chromium.org + + Android: Records the terminal event associated with a hung renderer infobar. + This includes both the explicit user actions as well as implicit dismissals, + e.g., when the renderer regains responsiveness before the infobar is + interactively dismissed. + + + + + falken@chromium.org + chrome-loading@google.com + + Time between the two messages OnReceiveResponse and + OnStartLoadingResponseBody as observed by the renderer process in + URLLoaderClientImpl. The idea is to see whether there is a performance cost + in having two separate messages, as the plan is to combine them into one. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the number of milliseconds spent blocking Blink's main thread while + capturing the main frame. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records a boolean indicating whether a capture for the main frame succeeded. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records the number of milliseconds spent blocking Blink's main thread while + capturing a subframe. + + + + + ckitagawa@chromium.org + mahmoudi@chromium.org + fredmello@chromium.org + + Records a boolean indicating whether a capture for a subframe succeeded. + + + + + kkhorimoto@chromium.org + + [iOS] A boolean that is used to indicate that the WebKit rendering bug in + http://crbug.com/583231 has occurred. This occurs when a page with no + viewport tag is rendered with an unusable zoom scale. Only logged on iOS. + + + + + altimin@chromium.org + lpy@chromium.org + + This boolean keeps track the count of the visibility change of a frame. + Recorded every time when the visibility of a frame is changed. + + + + + + + kdillon@chromium.org + shaseley@chromium.org + + Tracks the queueing time of tasks on the main thread of the renderer broken + down by queue type. Reported when the task is completed. + + Note that this metric is only recorded when a renderer is not backgrounded. + + + + + altimin@chromium.org + + Renderer main thread load (percentage of time spent in tasks), reported in + one second chunks. + + See http://bit.ly/chromium-renderer-main-thread-load-metric for details. + + This metric is emitted when the renderer main thread task is completed or + renderer is backgrounded or foregrounded, at most once per second per + renderer amortized. + + + + + farahcharab@chromium.org + altimin@chromium.org + + Used to track the number of resource loading tasks split by net priority. + Recorded each time the resource's request priority is changed. + + + + + farahcharab@chromium.org + altimin@chromium.org + + Used to track the number of resource loading tasks split by execution + priority. Recorded each time a task is executed. + + + + + altimin@chromium.org + + The number of completed renderer tasks split per frame type. Used to monitor + usage of each type of frame. Reported each time when task is completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + tasak@google.com + + The number of completed renderer tasks which have safepoints, split per + frame type. Used to monitor usage of each type of frame. Reported each time + when task is completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + + The number of completed renderer tasks split per task queue type. Used to + monitor usage of each type of task queue. Reported each time when task is + completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + + Total duration (reported in full seconds) of dedicated worker tasks (thread + time) split by per thread type. Note that partial seconds are rounded + up/down so that they average to the correct value when many reports are + added. For more details, check base::ScaledLinearHistogram. + + This is reported each time a task is completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + + Total cpu time (reported in full seconds) of renderer tasks split by per + thread type. Note that partial seconds are rounded up/down so that they + average to the correct value when many reports are added. For more details, + check base::ScaledLinearHistogram. + + Wall time is tracked by RendererScheduler.TaskDurationPerThreadType + histogram. This histogram is used to compare CPU usage of tasks from + different threads. + + Only 1% of randomly sampled tasks have cpu time measured and report duration + for this histogram. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + + Total cpu time (reported in full seconds) of renderer tasks split by per + frame origin type (main frame vs same-origin frame vs cross-origin frame). + Note that partial seconds are rounded up/down so that they average to the + correct value when many reports are added. For more details, check + base::ScaledLinearHistogram. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + + Total duration (reported in full seconds) of renderer per-frame tasks split + per frame type. Note that partial seconds are rounded up/down so that they + average to the correct value when many reports are added. For more details, + check base::ScaledLinearHistogram. + + Used to monitor workload coming from different frames. Reported each time a + task is completed. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + altimin@chromium.org + scheduler-dev@chromium.org + + Total duration (reported in full seconds) of renderer tasks split per task + queue type. Note that partial seconds are rounded up/down so that they + average to the correct value when many reports are added. For more details, + check base::ScaledLinearHistogram. + + Used to monitor usage of each type of task queues. Reported each time a task + is completed. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + altimin@chromium.org + hajimehoshi@chromium.org + + Total duration (reported in full seconds) of renderer per-frame tasks split + per task type. Note that partial seconds are rounded up/down so that they + average to the correct value when many reports are added. For more details, + check base::ScaledLinearHistogram. + + Used to monitor usage of each task type. Reported each time a task is + completed. + + This metric is susceptible to problematic outliers and should be analyzed + with custom scripts accounting for that rather than from a dashboard. + + + + + altimin@chromium.org + + Total duration (repored in full seconds) of dedicated worker tasks (wall + time) split by per thread type. Note that partial seconds are rounded + up/down so that they average to the correct value when many reports are + added. For more details, check base::ScaledLinearHistogram. + + Reported each time a task is completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + lpy@chromium.org + + Total duration (reported in full seconds) of renderer tasks split by per + thread type. Note that partial seconds are rounded up/down so that they + average to the correct value when many reports are added. For more details, + check base::ScaledLinearHistogram. + + Used to compare CPU usage of tasks from different threads. Reported each + time a task is completed. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + altimin@chromium.org + farahcharab@chromium.org + + Total duration (reported in full seconds) of renderer main thread tasks + split by scheduler use case. Note that partial seconds are rounded up/down + so that they average to the correct value when many reports are added. For + more details, check base::ScaledLinearHistogram. + + Use case is a scheduler's educated guess of the current state of the world. + See renderer/use_case.h and + + RendererSchedulerImpl::UpdatePolicy for more details. + + + + + tasak@google.com + keishi@chromium.org + + Number of safepoints (defined by cooperative scheduling manager) inside a + single non-nested task executed on the main thread of a renderer process. + This is recorded when each non-nested task stops executing. + + + + + tasak@google.com + keishi@chromium.org + + The duration of every task slices. The non-nested task executed in main + thread of the renderer process scheduler is split into slices by the + safepoints defined by cooperative scheduling manager. This metrics doesn't + record the duration of task without any safepoints. This is recorded both + inside a safepoint and when the tasak finishes. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + tasak@google.com + keishi@chromium.org + + The duration of every non-nested task executed in main thread of the + renderer process which has more than one safepoint. This is recorded when + the task finishes. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + + + + sunyunjia@chromium.org + tdresser@chromium.org + + The duration of every task queued in the _renderer_ scheduler to see the + distribution of the task duration. + + Note that this metric discards tasks longer than 30 seconds because they are + considered to be a result of measurement glitch. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + maxlg@chromium.org + + The count of same-document-navigations split by whether it is the + same-document backward/forward navigation, history API navigation, or other + fragment navigation. + + + + + altimin@chromium.org + + Number of web frame schedulers per renderer scheduler. Recorded once per + navigation. + + + + + altimin@chromium.org + + Number of web view schedulers per renderer scheduler. Recorded once per + navigation. + + + + + ppi@chromium.org + + Roundtrip times for synchronous IPC calls from the renderer to browser. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/renderer4/histograms.xml b/tools/metrics/histograms/histograms_xml/renderer4/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..742b3c7c71c7553839debb217034fcb1124b46a3 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/renderer4/histograms.xml @@ -0,0 +1,316 @@ + + + + + + + + + + andrescj@chromium.org + chromeos-gfx@google.com + + The wall time elapsed between creating a raster task in the client and being + ready to issue raster work to the driver in the GPU process. This includes + time decoding and uploading images. Note that this does not count raster + tasks that depend on at-raster image decodes. Since this metric is only + reported for Chrome OS clients, it has data only from high-resolution + clocks. + + + + + khushalsagar@chromium.org + chrome-gpu@google.com + + Time spent completing all work for a compositor rasterization task. This + includes the time in the renderer process for sending GL or paint commands + to the GPU process and the time for flushing these commands to the driver. + + WARNING: This metric is only reported for clients with high resolution + clocks, which means this will be biased to a portion of the population on + windows. + + + + + tdresser@chromium.org + Whether the scroll from touch is executed on main thread. + + + + tdresser@chromium.org + + Whether the scroll from mouse wheel is executed on main thread. + + + + + cblume@chromium.org + vmpstr@chromium.org + + Gpu image decode usage statistics. Images are decoded and locked prior to + upload; this indicates how that decode is used during tile management. + + + + + sashamcintosh@chromium.org + ericrk@chromium.org + + The current number of bytes locked by the GpuImageDecodeCache compared to + the maximum allowed number of bytes to lock. This value is recorded every + time the tile manager assigns GPU memory to tiles. + + + + + cblume@chromium.org + vmpstr@chromium.org + + Indication whether the first lock of an image decode was wasted (image was + not used). Images are decoded and locked prior to raster; this indicates + whether the decode was used or not during the first lock. + + + + + cblume@chromium.org + khushalsagar@chromium.org + + Gpu image upload usage statistics. Images are uploaded and locked prior to + use; this indicates how that upload is used during tile management. + + + + + ericrk@chromium.org + + Indication whether the first lock of an image upload was wasted (image was + not used). Images are uploaded and locked prior to raster; this indicates + whether the upload was used or not during the first lock. + + + + + ericrk@chromium.org + enne@chromium.org + + Whether gpu rasterization is enabled (checked once after the page is painted + for the first time). + + + + + + + + + + + cblume@chromium.org + vmpstr@chromium.org + sashamcintosh@chromium.org + + This metric records the duration of an image decode for the raster path in + the compositor. It is recorded every time we decode an image. It is suffixed + by the type of rasterization we're in (either Gpu or Software). The + rasterization suffix is optionally prefixed by the image type (WebP, Jpeg, + etc.) or OutOfRaster. + + Warning: Before version M78 this metric may include reports from clients + with low-resolution clocks (i.e. on Windows, ref. + |TimeTicks::IsHighResolution()|). Such reports will cause this metric to + have an abnormal distribution. + + + + + + + sashamcintosh@chromium.org + chromeos-gfx@google.com + + This metric records the duration of an image upload for the raster path in + the compositor. It is recorded every time we upload an image. The metric is + optionally suffixed by the image type (WebP, Jpeg, etc.) or OutOfRaster. + + + + + wiltzius@chromium.org + + Number of rects inside of a PictureLayer's invalidation region per commit. + + + + + tdresser@chromium.org + pdr@chromium.org + + Ideally we'd always scroll on the impl thread, but there are a variety of + situations where we need to scroll on main. We should try to drive these + down. For every gesture, we record whether or not the scroll occurred on the + main thread or it should scroll on the impl thread but is blocked on main + thread, and if it did, what the reason was. + + + + + tdresser@chromium.org + pdr@chromium.org + + Ideally we'd always scroll on the impl thread, but there are a variety of + situations where we need to scroll on main. We should try to drive these + down. For every wheel tick, we record whether or not the the scroll occurred + on the main thread or it should scroll on the impl thread but is blocked on + main thread, and if it did, what the reason was. + + + + + ericrk@chromium.org + + The percentage of input events which are janks (not processed in the + expected frame) during each momentum scroll gesture. Computed by tracking + the number of extra coalesced momentum scroll events during a gesture. Extra + coalesced event indicates that the events were not handled in the target + frame. Logged once after a scroll with momentum events completes. + + + + + wiltzius@chromium.org + + Number of pixels that culling prevented being drawn to the screen, recorded + as 10 times the percentage of the viewport that these pixels cover. This is + collected once per frame while it is being drawn to the screen in the + compositor. + + + + + andrescj@chromium.org + chromeos-gfx@google.com + + The wall time elapsed between creating a raster task in the client and being + ready to issue raster work to the driver in the GPU process. This includes + time decoding and uploading images. Note that this does not count raster + tasks that depend on at-raster image decodes. Since this metric is only + reported for Chrome OS clients, it has data only from high-resolution + clocks. + + + + + khushalsagar@chromium.org + chrome-gpu@google.com + + Time spent completing all work for a compositor rasterization task. This + includes the time in the renderer process for sending GL or paint commands + to the GPU process and the time for flushing these commands to the driver. + + WARNING: This metric is only reported for clients with high resolution + clocks, which means this will be biased to a portion of the population on + windows. + + + + + enne@chromium.org + chrishtr@chromium.org + + The number of render passes (or render targets) in the renderer's frame. If + the value is more than one, then an intermediate rendering target must be + used during the rendering of the frame for each render pass greater than + one. + + + + + + + bokan@chromium.org + input-dev@chromium.org + + For each scroll gesture (i.e. at GestureScrollBegin), records whether the + scroll is: handled unblocked on the compositor thread, handled on the + compositor thread but blocked on main thread event listeners, or being + handled on the main thread. Broken down by scroll device. + + + + + cblume@chromium.org + vmpstr@chromium.org + + Software image decode usage statistics. Images are decoded and locked prior + to raster; this indicates how that decode is used during tile management. + + + + + cblume@chromium.org + vmpstr@chromium.org + + Indication whether the first lock of an image decode was wasted (image was + not used). Images are decoded and locked prior to raster; this indicates + whether the decode was used or not during the first lock. + + + + + reveman@chromium.org + + Time between the issue of a texture copy operation and detecting that it has + completed as measured by the GPU process. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/safe_browsing/histograms.xml b/tools/metrics/histograms/histograms_xml/safe_browsing/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..30b4466b2553ec5abc558b7363b72e73b94b9f90 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/safe_browsing/histograms.xml @@ -0,0 +1,1572 @@ + + + + + + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + For users known to be already enrolled in Advanced Proection, records the + service error of refreshing OAuth2 access token during fetching the user's + advanced protection status. Logged once a day and will retry on transient + failures. This is a subset of + SafeBrowsing.AdvancedProtection.TokenFetchStatus. + + + + + drubey@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the service error of refreshing OAuth2 access token during fetching + the user's advanced protection status. Logged at startup for all users, once + a day for AP users, and will retry on transient failures. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records if the telemetry ping sent for APK download contained a full + referrer chain, or if there was an error collecting the referrer chain. + Logged each time a user opted into extended reporting downloads an APK file + from a normal window on Android. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a telemetry ping for APK download was sent, or if not, then + why not. Logged each time a user downloads an APK file on Android. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the resource type that triggers the safe browsing blocking page. Logged + each time a safe browsing blocking page is created. This metric is useful to + show the priority of checking each resource type in real time. Note that + this metric may be bias towards mainframe, because the default resource type + is set to mainframe. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether the Safe Browsing check via CheckBrowseUrl method matched any + local hash prefixes. Logged each time the Safe Browsing reputation of a URL + is checked using local blocklists. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts the number of times the Safe Browsing reputation lookup timeout + happens. Logged each time the Safe Browsing reputation of a URL is checked. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the duration from the time the binary is uploaded for deep + scanning of a download request until the time the user decides to bypass the + verdict. It is logged once for each binary upload when the user bypasses the + verdict. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the bytes/sec from the size of a download request divided by + the duration of a successful deep scanning upload request. It is logged once + for each successful binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request. It is + logged once for each binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + FailedToGetToken result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + non-successful scan verdict. It is logged once for each binary upload with + that result. + + + + + rogerta@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + FileEncrypted result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + FileTooLarge result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + Success result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + SB.This records the deep scanning duration of a user download request with a + Timeout result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with an + Unknown result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user download request with a + UnsupportedFileType result. It is logged once for each binary upload with + that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the bytes/sec from the size of an upload request caused by a + "drag and drop" from the user divided by the duration of a + successful deep scanning upload request. It is logged once for each + successful binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the duration from the time the binary is uploaded for deep + scanning of a "drag and drop" until the time the user decides to + cancel the upload. It is logged once for each binary upload when the user + bypasses the verdict. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request. It is logged once for each binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a FailedToGetToken result. It is logged once for each binary + upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a non-successful scan verdict. It is logged once for each + binary upload with that result. + + + + + rogerta@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a FileEncrypted result. It is logged once for each binary + upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a FileTooLarge result. It is logged once for each binary upload + with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a Success result. It is logged once for each binary upload with + that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + SB.This records the deep scanning duration of a user "drag and + drop" request with a Timeout result. It is logged once for each binary + upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with an Unknown result. It is logged once for each binary upload + with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user "drag and drop" + request with a UnsupportedFileType result. It is logged once for each binary + upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the bytes/sec from the size of a user paste request divided by + the duration of a successful deep scanning upload request. It is logged once + for each successful binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the duration from the time the binary is uploaded for deep + scanning of a paste until the time the user decides to cancel the upload. It + is logged once for each binary upload when the user bypasses the verdict. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request. It is + logged once for each binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + FailedToGetToken result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + non-successful scan verdict. It is logged once for each binary upload with + that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + FileTooLarge result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + Success result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + Timeout result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with an + Unknown result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user paste request with a + UnsupportedFileType result. It is logged once for each binary upload with + that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the bytes/sec from the size of an upload request divided by the + duration of a successful deep scanning upload request. It is logged once for + each successful binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the duration from the time the binary is uploaded for deep + scanning of an upload until the time the user decides to cancel the upload. + It is logged once for each binary upload when the user bypasses the verdict. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request. It is + logged once for each binary upload. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + FailedToGetToken result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + non-successful scan verdict. It is logged once for each binary upload with + that result. + + + + + rogerta@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + FileEncrypted result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + FileTooLarge result. It is logged once for each binary upload with that + result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + Success result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + SB.This records the deep scanning duration of a user upload request with a + Timeout result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with an + Unknown result. It is logged once for each binary upload with that result. + + + + + domfc@chromium.org + webprotect-team@google.com + + This records the deep scanning duration of a user upload request with a + UnsupportedFileType result. It is logged once for each binary upload with + that result. + + + + + meacer@chromium.org + chrome-safebrowsing-alerts@google.com + + Records when a user in the Delayed Warnings experiment group visits a page + with a delayed SafeBrowsing phishing warning, triggers the delayed warning + (via keypress), or leaves the page without interacting. Only recorded when + user has not disabled URL elision via "Always Show Full URLs" + context menu item, or by installing the Suspicious Site Reporter extension. + + + + + meacer@chromium.org + chrome-safebrowsing-alerts@google.com + + Same as SafeBrowsing.DelayedWarnings.Event but only recorded when user has + disabled URL elision via "Always Show Full URLs" context menu + item, or by installing the Suspicious Site Reporter extension. + + + + + meacer@chromium.org + estark@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how long a user in the Delayed Warnings experiment group spends on a + page with a delayed SafeBrowsing phishing warning. The time is recorded from + when the page loads to when the warning is shown or the user leaves the + page, whichever comes first. Only recorded when user has not disabled URL + elision via "Always Show Full URLs" context menu item, or by + installing the Suspicious Site Reporter extension. + + + + + meacer@chromium.org + estark@chromium.org + chrome-safebrowsing-alerts@google.com + + Same as SafeBrowsing.DelayedWarnings.TimeOnPage but only recorded when user + has disabled URL elision via "Always Show Full URLs" context menu + item, or by installing the Suspicious Site Reporter extension. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The result of reading/parsing/accepting a new proto for the FileTypePolices + repo of file extensions and their meta data. + + This is for the file types loaded from the component-update system. This + includes both those loaded from disk shortly after startup, and those + received over the network when the component version changes + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Integer version number citing which version of the proto data chrome just + loaded. Latest version is in download_file_types.asciipb. + + This is for the file types loaded from the component-update system. This + includes both those loaded from disk shortly after startup, and those + received over the network when the component version changes + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The result of reading/parsing/accepting a new proto for the FileTypePolices + repo of file extensions and their meta data. + + This is for the file types loaded from the resource bundle packaged with + Chrome, which is always loaded at startup. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Integer version number citing which version of the proto data chrome just + loaded. Latest version is in download_file_types.asciipb. + + This is for the file types loaded from the resource bundle packaged with + Chrome, which is always loaded at startup. + + + + + ntfschr@chromium.org + src/android_webview/OWNERS + + Which interstitial type is being displayed to the user? This currently + applies only to WebView (where we show Loud vs. Quiet interstitials). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Count of how many NavigationEvents get removed in each periodic clean up. + This is a rough estimation of the number of navigations every two minutes. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the Safe Browsing enhanced protection service is currently enabled. + Recorded for all non-Incognito profiles on profile startup. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the Safe Browsing extended reporting service is currently enabled. + Recorded for all non-Incognito profiles on profile startup. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the Safe Browsing service is currently enabled. Recorded for all + non-Incognito profiles on profile startup. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the current user has ever seen a security interstitial. Recorded for + all non-Incognito profiles on profile startup. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The result of referrer attribution, including different types of success or + failure. This is incremented each time a safe browsing ping or download ping + is generated. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Number of times referrer attribution encounters an invalid tab ID. This is + incremented a safe browsing ping or download ping is generated and an + invalid tab ID is encountered during attribution. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The length of referrer URL chain we get from referrer attribution. This is + logged each time a safe browsing ping or download ping is generated. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether the local Safe Browsing stores are available. If not, all URLs + are marked as safe during real time URL lookup. Logged each time a top frame + URL navigation happens for users who have the real time URL lookups enabled. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs if the real time URL lookup service is currently in backoff state due + to previous errors. Logged each time a top frame URL navigation happens in + non-incognito mode for users who have real time URL lookups enabled. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the time it takes to run a cleanup task in cache manager. Logged each + time a cleanup task is run. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of real time URL verdicts stored for this profile. Logged + each time a new real time url verdict is cached. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether Safe Browsing database can be checked in Safe Browsing URL + checker. Logged each time a URL is checked by Safe Browsing URL checker. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the latency between the start of getting a result from the cache and + when the cache is actually obtained. The time includes bouncing between IO + and UI threads. This is an indicator of the efficiency of loading the cache. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the result of real time URL cache lookup. If the result is + VERDICT_TYPE_UNSPECIFIED, that means cache miss and a ping will be sent + afterwards. Otherwise, ping won't be sent. This is an indicator of cache hit + rate. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the latency between the start of a token request and when the token is + actually obtained. Logged each time a user performs a real-time Safe + Browsing check with token. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether a token received from the token fetcher is nonempty. Logged + each time a response is received from the token fetcher. It shows the + validity of the tokens received from the token fetcher. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether a token is attached when a URL lookup request is sent. Logged + each time a URL lookup request is sent. It shows the percentage of URL + lookup requests that are attached with tokens. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs if cache manager is valid when real time URL check is enabled. Logged + each time if the URL doesn't match the high confidence allowlist. Ideally, + cache manager should be valid whenever real time URL check is enabled. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether the real time lookup service is available when a real time URL + check is needed. The real time lookup service is available if it is not + nullptr and it is not in backoff mode. Logged when real time URL check is + enabled and the URL doesn't match the allowlist. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs whether the response of the real time URL lookup is successful. Logged + on each resource check for which a lookup request is sent to the server. A + failure can be either a network error or a parsing error. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the result of checking the URL against the local Safe Browsing high + confidence allowlist. Logged each time a top frame URL navigation happens + for users who have the real time URL lookups enabled. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Response or error codes from SafeBrowsing real time URL lookups. Logged on + each resource check for which a lookup request is sent to the server. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the roundtrip time it took to perform a Safe Browsing real time URL + lookup. Logged on each resource check for which a lookup request is sent to + the server. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the user population that was checked by Safe Browsing real time URL + lookup. Logged on each resource check for which a lookup request is sent to + the server. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the resource type that was checked by Safe Browsing real time URL + lookup. Logged on each resource check that is eligible for real time checks. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the resource type that was requested to be checked by Safe Browsing + real time URL lookup. Logged on each resource check. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the number of verdicts received in the real time URL check response. + Logged on each resource check for which a lookup request is sent to the + server. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the user action performed on the Safe Browsing settings page. Depending + on the enum value, logged when the page is showned to the user or when the + user performs an action on the page. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Logs the error type from the token fetcher. Logs each time safe browsing + gets a response from the token fetcher. When the error type is none, it + means the token is obtained successfully. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the actions taken by the Ad Popup trigger whenever it is executed. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the actions taken by the Ad Redirect trigger whenever it is executed. + It is logged when we detect a blocked redirect attempt caused by an ad. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the actions taken by the Ad Sampling trigger whenever it is executed. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the state of the Suspicious Site trigger when its report delay timer + fires. Used to investigate variance in event order. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the events occurring in the Suspicious Site trigger whenever it is + executed. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Tracks the reasons that a report requested by the Suspicious Site trigger is + rejected by the Trigger Manager. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The size of the SafeBrowsing database or file on disk in kilobytes, after + reading it from disk on startup and after a database update has occurred. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time it takes to parse and load the SafeBrowsing database from disk, in + milliseconds. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Track cache hits for V4 full hashes. + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + Track get hash response hits for V4 full hash requests. + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of prefixes included in a full hash request sent to the Google + Safe Browsing servers. + + + + + vakh@google.com + kcarattini@google.com + chrome-safebrowsing-alerts@google.com + + Response or error codes from the SafeBrowsing Pver4 service. Logged after a + GetHash or request finishes to capture the response code or error code for + that call. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that it took to receive a response from the Google SafeBrowsing + servers for a full hash request. + + + + + + + vakh@chromium.org + kcarattini@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the parsing results of a status 200 GetV4Hash request. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track return status from V4 GetHash attempts. The buckets of this histogram + overlap, so the counts cannot be used as percentages. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the outcome of a check to AreAllStoresAvailableNow. This will be + logged whenever the database is queried (several times in the process of a + download, and once when a potentially dangerous subresource is loaded). + + + + + ajuma@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a network response has been received for a request to update + the Safe Browsing local database, since the browser was launched. This will + be logged whenever the database is queried. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of verdicts received in the full hash check. Logged each + time a full hash check response is received. + + + + + ajuma@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time since the last network response was received for a request + to udpate the Safe Browsing local database. This will be logged whenever the + database is queried, but only if at least one such network response has been + received since the browser was launched. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of additions hashes in a SafeBrowsing list full update. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of applying a full update for a store received from PVer4 + SafeBrowsing service. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of additions of 4-byte + hash prefixes. This is logged once per store, per update containing + Rice-encoded additions. This histogram is specific to processing full + updates received from the server. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of removals hashes in a SafeBrowsing list full update. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of additions hashes in a SafeBrowsing list partial + update. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of applying a partial update for a store received from + PVer4 SafeBrowsing service. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of additions of 4-byte + hash prefixes. This is logged once per store, per update containing + Rice-encoded additions. This histogram is specific to processing partial + updates received from the server. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of indexes of hash + prefixes to remove since the last update. This is logged once per store, per + update containing Rice-encoded removals. + + + + + xinghuilu@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the number of removals hashes in a SafeBrowsing list partial update. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of applying an ListUpdateResponse read from disk after + parsing it successfully as a protobuf. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the result of decoding the Rice-encoded list of additions of 4-byte + hash prefixes. This is logged once per store, per Chrome launch. It is + specific to processing V4StoreFileFormat proto read from disk. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether a store has valid data, when it is queried. This is logged + each time a store is checked (a few times for each download, and once when a + potentially dangerous subresource is loaded). + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the parsing results of reading the SafeBrowsing V4 store file from + disk. Recorded every time a store is read from disk. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the results of writing the SafeBrowsing V4 store file to disk. + Recorded every time a store is written to disk. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Response or error codes when fetching updates from the SafeBrowsing PVer4 + service. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track the parsing results of a status 200 GetV4Update request. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The size of the response sent by the SafeBrowsing PVer4 service, in KB. + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Track return status from V4 update attempts. The buckets of this histogram + overlap, so the counts cannot be used as percentages. + + + + + ntfschr@chromium.org + src/android_webview/OWNERS + + Records whether the application has explicitly opted in or out of Safe + Browsing by manifest tag, or if they're relying on the default behavior. + This is recorded once during startup. + + + + + ntfschr@chromium.org + src/android_webview/OWNERS + + Records whether the user has explicitly opted in or out of Safe Browsing + (determined by the Google Play Protect Verify Apps setting in GMS). This + also captures when WebView cannot determine user preference due to a GMS API + failure. This is recorded once during startup. + + + + + ntfschr@chromium.org + src/android_webview/OWNERS + + When encountering an unsafe resource, this indicates whether the WebView is + considered to be viewable or not. Currently, we define "viewable" + as getVisibility() == View.VISIBLE and attached to the Android View + hierarchy. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records the verdict of deep scanning for Advanced Protection users. It + can be used to determine how often we warn the user about malware after they + upload a file for deep scanning. It is recorded after every Advanced + Protection deep scan. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records whether DLP scanning succeeded or not. It is logged once for + each binary upload with DLP scanning enabled (file download or upload with + the appropriate enterprise policies enabled). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records the duration of each binary upload request. It is logged once + for each binary upload (file download or upload with the appropriate + enterprise policies enabled). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records whether the malware deep scanning succeeded or not. It is + logged once for each binary upload with malware scanning enabled (file + download or upload with the appropriate enterprise policies enabled). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records the verdict of deep scanning for enterprise users. It can be + used to determine how often we warn the user about malware after they upload + a file for deep scanning. It is recorded after every enterprise malware deep + scan. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records the outcome of each binary upload request. It is logged once + for each binary upload (file download or upload with the appropriate + enterprise policies enabled). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This record how long it took for the request to get the FCM token. It is + logged every time a deep scanning request successfully gets a token. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the incoming message has the expected key. Recorded on every FCM + message received by the Safe Browsing FCM handler. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the incoming message has a token that was previously registered with + the FCM handler. Recorded on every FCM message received by the Safe Browsing + FCM handler. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the incoming message was successfully parsed as valid base64-encoded + data. Recorded on every FCM message received by the Safe Browsing FCM + handler. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the incoming message was successfully parsed as a valid + base64-encoded serialized proto. Recorded on every FCM message received by + the Safe Browsing FCM handler. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/sb_client/histograms.xml b/tools/metrics/histograms/histograms_xml/sb_client/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..e589dfbb31b96659c36e7b0f8f623dd0bc7497a3 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/sb_client/histograms.xml @@ -0,0 +1,567 @@ + + + + + + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records a histogram of the reason why downloads are marked as being + malicious or clean by the improved SafeBrowsing binary download protection. + Note that UNSUPPORTED_URL_SCHEME was split out of the INVALID_URL bucket in + M41. The NOT_BINARY_FILE check was moved before the UNSUPPORTED_URL_SCHEME + check in M42. The WHITELISTED_URL check was moved to before NOT_BINARY_FILE + in M62. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + For each download supported by the SafeBrowsing download protection service, + records if it matches a certain whitelist (e.g. matches URL whitelist, + matches signature whitelist, or does not match any whitelists). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Counts of DMG-like file types that were successfully analyzed by the + SafeBrowsing download service. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records a histogram of how often users download a file with a file extension + that is possibly dangerous (e.g., exe, class). + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + A Mac-only metric that records whether a given download file is a + cryptographically signed DMG archive. This metric is logged before Chrome + sends SafeBrowsing download pings. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the total time it takes for the SafeBrowsing download service to + check whether the content of a download is malicious or not, including file + feature extraction, whitelist checking, and server ping. This histogram only + includes checks that sent a ping to the SafeBrowsing server. It does not + include requests that were cancelled, but does include requests that + received a bad response. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + The net error code for all CheckClientDownloadRequest URLFetchers. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the time it takes for the SafeBrowsing download service ping. It is + not recorded for requests that were cancelled. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the results of SafeBrowsing binary download checks which caused a + server ping. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + The size of the upload data for CheckClientDownloadRequest URLFetchers. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + For CheckClientDownloadRequest URLFetchers with successful status, the HTTP + response code that was received. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + rsesek@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded DMG file. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded rar file. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + mattm@chromium.org + + Records the time it takes for the SafeBrowsing download service to extract + info from a downloaded zip file. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + For each zip file analyzed by the SafeBrowsing download service, records if + the unpacking was 100% successful. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The net error code for all ClientMalwareRequest URLFetchers. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The size of the upload data for ClientMalwareRequest URLFetchers. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + For ClientMalwareRequest URLFetchers with successful status, the HTTP + response code that was received. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Measures the success rate of sending malware reports. Sending a report can + fail due to a client reaching the limit on the number of reports it can send + per day or due to the report failing to be serialized. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + The counts for malware verdicts given by server side model. + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The counts for various reasons why an in-progress phishing classification + was canceled. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of pages that we could have possibly classified (essentially the + number of top page navigations by users with SBClientPhishing enabled). The + name is slightly misleading as it is recorded before + "Preclassification" happens. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Records events in the phishing classifier including reasons that prevents + phishing detection to complete on the renderer side. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the result of the last model fetch. This is only recorded when + classification fails because the model is not ready. This is useful for + distinguishing different reasons the model may not be ready (never fetched, + fetch failed, etc.) + + + + + vakh@google.com + + Response or error codes from the SafeBrowsing service. Logged after a + request for the client side model finishes to capture the response code or + the error code for that HTTP request. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The counts for various model status codes that we get after loading a new + client-side phishing model. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the version of the local phishing detection model fetched. This + histogram is logged each time we load a model. + + + + + gab@chromium.org + + The time that an individual chunk of DOM feature extraction work took. + + + + + gab@chromium.org + + The number of times that DOM feature extraction finished early because the + active WebDocument's frame was removed during traversal. + + + + + gab@chromium.org + + The number of iterations that the DOM feature extractor took to finish. + + + + + gab@chromium.org + + The time that it took to resume DOM feature extraction for the phishing + classifier. Longer times may indicate that the page DOM changed between + chunks of work and the extractor had to re-traverse up to the saved + position. + + + + + gab@chromium.org + + The number of phishing classifications that were aborted because DOM feature + extraction took too long. + + + + + gab@chromium.org + + The time that the DOM feature extarctor took to finish, summed across all + chunks of work. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of features which were omitted from phishing classification + because they were added with an illegal value. This would indicate a bug. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether the local phishing detection model detects phishing. This + histogram is logged each time the model is run (roughly on every navigation + to a non-allowlisted site) + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + This records whether a page capture event matches the last URL requested + from the browser process. This histogram is recorded on every page capture + event. + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the duration it takes for client side phishing detection to finish. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + The result enum received from the renderer-side classifier + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the result of phishing pre-classification checks. This is recorded + on every classification attempt (roughly every page load). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of phishing classifications that were previously cached as being + phishing but that will get re-classified (to possibly fix false positives). + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of phishing classifier pingbacks that were skipped because + serializing the request protocol buffer to string failed. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of times that a cached phishing classification result was used, + rather than pinging the server. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + Records the status when we create a scorer object for the client-side + phishing detection classifier. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records whether the server-side phishing detection model detects phishing. + This histogram is logged each time we contact Safe Browsing to evaluate + whether a site is phishing. + + + + + vakh@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of phishing classifications that were aborted because the term + feature extractor failed to initialize an ICU break iterator. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that an individual chunk of term feature extraction work took. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of iterations that the term feature extractor took to finish. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of phishing classification that were aborted because term feature + extraction took too long. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time that the term feature extarctor took to finish, summed across all + chunks of work. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of times that the limit on the number of phishing classifier + features for a page was reached. This may indicate a bug, or that + kMaxFeatureSize is too small. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time taken to extract URL features for the phishing classifier. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how long it took to compare visual features against the visual + phishing model. This is recorded on every phishing classification. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Records how long it took to extract visual features. This is recorded on + every phishing classification. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/search/histograms.xml b/tools/metrics/histograms/histograms_xml/search/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0218d2ef23d14529a0a67d952986a7e29bec7c67 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/search/histograms.xml @@ -0,0 +1,1483 @@ + + + + + + + + + + + + + + donnd@chromium.org + twellington@chromium.org + chrome-analysis-team@google.com + + Records whether the user opened the panel when it was shown. Recorded for + all gestures for all users when the UX is hidden. Implemented for Android. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + donnd@chromium.org + twellington@chromium.org + + The type of card returned in the Search Term Resolution Response from the + server when a search is resolved in response to a Tap gesture that uses + surrounding text to determine the best search. This characterises what we'll + show in the Bar. Recorded when the panel is closed. Implemented for Android. + + + + + + + donnd@chromium.org + twellington@chromium.org + + The type of card shown in the Bar when the panel has been opened. Recorded + when the panel is closed. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records the duration of persisted outcomes between the time they were stored + and the time that they were sent back to the server. Recorded when persisted + data is sent to the server. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Logs that the UX has entered a state where features are available to be + recorded to Ranker. A value of true indicates that the available features + include outcomes, false if they are just features at inference-time. Use to + correlate with what actually gets recorded in the Search. + ContextualSearch.Ranker.Recorded histogram. Recorded when a tap gesture is + recognized that might trigger our UX (for pure features), and when the UX is + actually shown (for outcomes). Implemented for Android. + + + + + donnd@chromium.org + charleszhao@chromium.org + Tracks the outcome of attempts to download a Ranker Model. + + + + donnd@chromium.org + twellington@chromium.org + + Records whether the user opened the panel when a tap was not suppressed by + Ranker. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Logs that features were recorded to Ranker and whether it was an outcome or + not. Recorded when the UX is shown or hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Logs that features were recorded to Ranker from native code and whether it + was an outcome or not. Recorded when the UX is shown or hidden. Implemented + for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records Ranker's prediction about whether a tap should be suppressed or not. + Recorded when the UX is hidden. Implemented for Android. + + + + + charleszhao@chromium.org + donnd@chromium.org + + Time taken for the Ranker Model Loader to download its model from the + configured URL, in ms. + + + + + charleszhao@chromium.org + donnd@chromium.org + + Time taken for the Ranker Model Loader to parse its model, in ms. + + + + + charleszhao@chromium.org + donnd@chromium.org + + Time taken for the Ranker Model Loader to read its model from local storage + (cache), in ms. + + + + + charleszhao@chromium.org + donnd@chromium.org + + Time taken for the Ranker Model Loader to write its model to local storage, + in ms. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether Ranker was able to make a prediction about tap suppression. + Recorded when the UX is triggered by tap. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether the user opened the panel when a tap would be suppressed by + Ranker if suppression was enforced. Recorded when the UX is hidden. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records that a resolve response was received from the server, and whether + that was due to a Tap gesture or not (vs longpress). Recorded when the user + triggers the feature and the server responds. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records that a resolve request was sent to the server, and whether that was + due to a Tap or not (vs longpress). Recorded when the user triggers the + feature. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records that a resolve request from the server caused the selection to be + expanded, and whether that original selection was due to a Tap or not (vs + longpress). Recorded when the qualifying server response is received. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether the user opened the panel when it was shown in response to a + tap gesture, for all users. Recorded when the UX is hidden. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether the user opened the panel when it was shown for sync-enabled + users only (this is an approximation for the population that logs to UKM). + Recorded for all gestures for users with sync enabled when the UX is hidden. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records that a translation is needed for the current Contextual Search, and + whether the selection was originally created by a Tap gesture. This is + recorded regardless of whether the user will actually be shown a translation + or not. Recorded any time a selection is established or changed with the + Contextual Search Translations feature enabled. Implemented for Android. + + + + + donnd@chromium.org + contextual-search-eng@google.com + + Records whether an IPH promoting the Opt-in for the Translations experiment + has ever been shown for the current user. Recorded when the Overlay Panel is + closed. Implemented for Android. + + + + + donnd@chromium.org + contextual-search-eng@google.com + + Records whether the user actually did Opt-in right after seeing the IPH for + the Translations experiment. Recorded when the Overlay Panel is closed. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records the previous state of the user's enabled preference to indicate + whether they were decided or undecided about fully enabling this feature. + Recorded during the rollout of Unified Consent when the Contextual Search + preference is changed. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether throttling for Unified Consent was done for all requests. + Recorded when the user taps on text and the system would like the server to + suggest what to search for using page context, regardless of feature-enabled + state. Recorded multiple times for each request. Supports the rollout of + Unified Consent for Contextual Search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Records whether this user had a request throttled or not when needed. + Recorded when the user taps on text and the system would like the server to + suggest what to search for using page context, and throttling is in effect + for this user. Supports the rollout of Unified Consent for Contextual + Search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration that the panel was peeking before being opened when triggered + by a tap that was in a part of the screen where it overlaps the Bar. Logged + when the panel is closed after being opened. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a Tap was suppressed because the Bar overlapped the selection area. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration that the panel was peeking before being opened when triggered + by a tap at the bottom of the screen where it overlaps the Bar. Logged when + the panel is closed after being opened. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether the Bar overlapped the selection area and whether the results were + seen. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The protocol of the base page, logged at the time that any Search Term + Resolution Response is received. + + + + + + + donnd@chromium.org + twellington@chromium.org + + Whether Contextual Cards data was shown in the Contextual Search Bar. + Contextual Cards data is included with the search term resolution response. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen as part of a Contextual Search when + Contextual Cards data was shown. This indicates that the panel was opened. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration between the panel being triggered and the panel being dismissed + due to a scroll when search results were not seen. Implemented for Android. + Prior to M57 this was recorded on tap and longpress; on M57+ it is only + recorded on tap. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration between the panel being triggered and the panel being dismissed + due to a scroll when search results were seen. Implemented for Android. + Prior to M57 this was recorded on tap and longpress; on M57+ it is only + recorded on tap. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from initiating to ending a contextual search, when results were + seen as part of the search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from initiating to ending a contextual search, when results were + not seen as part of the search and the search did not end with the beginning + of another contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from initiating to ending a contextual search, when results were + not seen as part of the search and the search ended with the beginning of + another contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (previous state and reason) of the first entry into the closed + panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (previous state and reason) of the first entry into the expanded + panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (previous state and reason) of the first entry into the + maximized panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (previous state and reason) of the first entry into the peeked + panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen as part of a Contextual Search when a tap + was on a word that we think is an entity. Recorded when Contextual Search is + dismissed. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (destination state and reason) of the first exit out of the + closed panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (destination state and reason) of the first exit out of the + expanded panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (destination state and reason) of the first exit out of the + maximized panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The details (destination state and reason) of the first exit out of the + peeked panel state within a contextual search. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The status of the Contextual Search fallback Search request. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The state of the Contextual Search Preference after the first run flow. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether the first run flow's panel was seen as part of a contextual search. + Only logged when the user triggered the first run flow yet exited the search + still in the undecided preference state. Implemented for Android. + + + + + donnd@chromium.org + mahmoudi@chromium.org + twellington@chromium.org + + The number of times the Contextual Search panel is opened, categorized by + whether In-Product Help for Contextual Search was shown before. Logged when + the panel is opened. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from starting a literal search until the results in the SERP start + to become viewable. Applies only to prefetched requests. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The status of the Contextual Search low priority Search request. Implemented + for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The outcome of the mandatory Promo broken down by original triggering + gesture. Logged for each view of the promo. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The status of the Contextual Search normal priority Search request. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from opening the panel beyond peek until the panel is closed. + Implemented for Android. + + + + + donnd@chromium.org + mahmoudi@chromium.org + twellington@chromium.org + + The number of times the Contextual Search panel is opened, categorized by + whether In-Product Help for opening the panel was shown before. Logged when + the panel is opened. Implemented for Android. + + + + + + + donnd@chromium.org + twellington@chromium.org + + The state of the Contextual Search Preference. Can be logged multiple times. + Used to determine the population size (user view). Implemented for Android. + + + + + + + donnd@chromium.org + twellington@chromium.org + + The Contextual Search preference state after a modification from the + preference menu. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The CTR from the previous 28 day period for each user, expressed as a + percentage. Logged the first time the panel is closed in each new week. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The number of user impressions of the Bar from the previous 28 day period. + Logged the first time the panel is closed in each new week. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The CTR from the previous week for each user, expressed as a percentage. + Logged the first time the panel is closed in each new week. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The number of user impressions of the Bar from the previous week. Logged the + first time the panel is closed in each new week. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The total count of times that the bar with the promo has been opened. Once + the user decides, this counter is no longer updated. + + + + + donnd@chromium.org + twellington@chromium.org + + The outcome of the promo broken down by original triggering gesture. Logged + for each view of the promo. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether the promo was seen, broken down by original triggering gesture. + Logged each time the promo was activated. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The historic number of taps that showed a peeking bar with the opt-out promo + before the first time the user opened the panel. + + + + + donnd@chromium.org + twellington@chromium.org + + The historic number of taps that showed a peeking bar with the opt-out promo + for users who have never opened the panel. This count may be limited by the + Finch config param promo_on_limited_taps. + + + + + donnd@chromium.org + twellington@chromium.org + + The number of remaining taps that can trigger the promo for this user. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The category of quick actions shown in the Contextual Search bar. Recorded + when the quick action is set. Implemented for Android. + + + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a quick action in the Contextual Search bar was clicked, which + activates the associated intent. Recorded when Contextual Search is + dismissed due to a click on a QuickAction in the Bar. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a Contextual Search quick action intent resolved to zero, one, or + many apps. Recorded when the quick action intent URI is resolved. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen as part of a Contextual Search when a quick + action was shown. Recorded when Contextual Search is dismissed. Implemented + for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a quick action was shown in the Contextual Search bar. Recorded when + the quick action is set. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a Quick Answer was activated, considered an answer, and seen. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether showing the Tap to Search UX in response to a Tap was suppressed by + a recent scroll. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from starting a resolving search until the Search Term Resolves. + Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time from starting a resolving search until the results in the SERP + start to become viewable. Applies only to prefetched requests. Implemented + for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether the search term was single or multi-word, logged at the time that + any Search Term Resolution Response is received. + + + + + + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen as part of a contextual search. Implemented + for Android. + + + + + + + donnd@chromium.org + twellington@chromium.org + + Whether search results were seen, broken down by original triggering + gesture. Only includes users that have enabled. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether Taps near the top of the screen was suppressed. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a second tap that was allowed to override ML + Tap Suppression. Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The length of the triggering selection when search results were not seen. + Only logged when contextual search is triggered due to a tap. Implemented + for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The length of the triggering selection when search results were seen. Only + logged when contextual search is triggered due to a tap. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a Tap was suppressed because the selection length was less than the + minimum selection length. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether a Contextual Search selection was valid. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration of a tap that triggered a Contextual Search when the user does + not open the panel. Implemented for Android. Logged when the panel closes + after being triggered by a tap. + + + + + donnd@chromium.org + twellington@chromium.org + + The duration of a tap that triggered a Contextual Search when the user does + open the panel. Implemented for Android. Logged when the panel closes after + being triggered by a tap and subsequently opened. + + + + + donnd@chromium.org + mahmoudi@chromium.org + twellington@chromium.org + + The number of times the Contextual Search is triggered by tapping, + categorized by whether In-Product Help for tapping was shown before. Logged + when Contextual Search is triggered by tapping. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap that was of long duration. Recorded when + the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap that was on a word considered long. + Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap that was on the middle part of a word. + Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap that was of short duration. Recorded + when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap that was on a word considered short. + Recorded when the UX is hidden. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The count of taps that showed a peeking bar without the opt-out promo since + this user has last opened the panel. + + + + + donnd@chromium.org + twellington@chromium.org + + The count of taps that showed a peeking bar with the opt-out promo since + this user has last opened the panel. + + + + + donnd@chromium.org + twellington@chromium.org + + Whether results were seen for a Tap and whether any suppression heuristic + was satisifed. Recorded when the UX is still shown (suppression not enabled, + only logged). Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The time between tapping on a word and performing a search. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The DPs count histogram for Taps that were not seen. Implemented for + Android. + + + + + donnd@chromium.org + twellington@chromium.org + + The DPs count histogram for Taps that were seen. Implemented for Android. + + + + + donnd@chromium.org + twellington@chromium.org + + For each contextual search that is triggered by tap, records whether the + translation conditions are met. Implemented for Android. + + + + + mathp@chromium.org + + The origin/cause of a change to the default search provider. + + + + + mpearson@chromium.org + csharp@chromium.org + + The type of the default search engine that is loaded when a profile is + opened or after a profile reset. Note that at least one profile is opened on + startup. Due to an error, there was a period from roughly May 9 2014 to May + 23 2014 during which this was not being logged. + + + + + lizeb@chromium.org + + On Android, when GSA tells Chrome about an account change, what is the + notification mechanism used, which is either the service connection, or a + broadcast. Recorded once per account change. + + + + + lizeb@chromium.org + + On Android, whether GSA tells Chrome about account changes through the + service or through a broadcast. This is reported at most once per Chrome + startup. + + + + + wychen@chromium.org + yusufo@chromium.org + + The last sequential number in the delta file for Icing. This is measured on + cold start. + + + + + wychen@chromium.org + yusufo@chromium.org + + The number of entries in the delta file level DB for Icing. This is measured + on cold start. + + + + + wychen@chromium.org + yusufo@chromium.org + + The number of entries in the usage report level DB for Icing. This is + measured on cold start. + + + + + donnd@chromium.org + + Records the reason why a context report to Icing failed, every time Chrome + attemps to record the current context (tab switching, navigations, etc). + Also records reasons why context reporting might be disabled. Recorded on + Android only. + + + + + sczs@chromium.org + gambard@chromium.org + + When an iOS user changes the default search engine in chrome Settings, + records the search engine's type. + + + + + yusufo@chromium.org + + The entry point used for all searches performed under partnership after the + Android search engine promo dialog was shown. This is a dialog prompting the + user to pick a default search engine. This metric is collected for every + search query performed. + + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Indicates whether or not a bitmap could be shown for a tile. + + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the time taken to fetch a bitmap for a tile when a bitmap could be + found. It includes the time starting from the UI layer requesting the + backend till the backend returns the associated bitmap. + + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + + Records duration from time when first task scheduled to time the fetch task + completed. + + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + Records the hour (0-23) when the TileFetcher task starts. + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + Records the HTTP response code get from TileFetcher. + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + Records the net error code get from TileFetcher. + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + + Records the reasons caused the tile group pruned in TileManager. + + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + + Records the TileManager status after initialized and loaded completed. + + + + + xingliu@chromium.org + chrome-upboarding-eng@google.com + + Records the image preloading events when the query tile images are fetched + from the background task. + + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the time taken by the bitmap request for a tile when no bitmap could + be found. It includes the time starting from the UI layer requesting the + backend till the backend returns the associated bitmap. + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the index of the query tile chip that was clicked from the fake + search box on the new tab page. + + + + + hesen@chromium.org + chrome-upboarding-eng@google.com + + Records the TileFetcher status after request send to server and response + received. + + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the index of the tile that was clicked. The index refers to the + position of the tile in the carousel. + + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + Indicates whether the tile clicked was a top level tile. + + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Indicates the number of tiles displayed in the UI after the backend was + loaded. + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the number of tiles per row that can be fit into the screen in the + default scroll position. + + + + + shaktisahu@chromium.org + chrome-upboarding-eng@google.com + + Records the width of a single query tile when shown in the carousel. + + + + + + + yusufo@chromium.org + + The search engines listed in the options for search engine promo. This is an + Android specific dialog prompting the user to pick a default search engine. + The dialog was shown on a device that had Chrome before it was first + introduced. + + + + + yusufo@chromium.org + + The search engine selected by the user from the search engine promo. This is + an Android specific dialog prompting the user to pick a default search + engine. The dialog was shown on a device that had Chrome before it was first + introduced. + + + + + yusufo@chromium.org + + The current state for search widget use and whether the device is a + partnership device related with the Android Search Widget. Collected on + every cold start. + + + + + mmourgos@chromium.org + newcomer@chromium.org + Time between showing and hiding the answer card. + + + + newcomer@chromium.org + + Time between sending an answer server request and the end of loading of the + answer card. Failed requests and requests not returning an answer are not + counted. + + + + + newcomer@chromium.org + + Time between sending an answer server request and successful finish of + navigation. Failed requests and requests not returning an answer are not + counted. + + + + + newcomer@chromium.org + Result of a answer server request. + + + + newcomer@chromium.org + + Time between successfully loading an answer card request and updating its + preferred size. There might be no or more than one size update per card + load. Size updates that happen before the card finishes loading are ignored + since they are not visible. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/security/histograms.xml b/tools/metrics/histograms/histograms_xml/security/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..42a09570b486c73bcb491161fc45a938d8e6cbf9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/security/histograms.xml @@ -0,0 +1,623 @@ + + + + + + + + + + estark@chromium.org + + The compliance of each main frame navigation's connection with the + Certificate Transparency policy. Recorded whenever a main-frame, + non-same-page navigation is committed. Connections can be compliant, or they + can be non-compliant for one of several reasons (not enough Signed + Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old + so CT compliance wasn't checked). + + + + + jdeblasio@chromium.org + + When TLS client authentication is requested by the server, Chrome must + choose whether to return a certificate or to abort the handshake. This + histogram records how this determination was made, either as a result of + user action, or as chosen automatically due to content settings. It only + records when a fresh certificate selection would be attempted (and thus + ignores cache hits). This histogram is recorded in SSLClientAuthObserver for + user-selected outcomes and in ChromeContentBrowserClient for policy + outcomes. This histogram does not cover mobile, as certificate handling is + not handled by Chrome on Android nor iOS. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records whether the page would have a legacy TLS warning (if the user were + in the appropriate field trial) when a download is initiated from the page + (*not* the legacy TLS status of the download URL itself). This is recorded + regardless of whether the warning is actually displayed. This histogram is + not recorded for downloads that are initiated in a new tab or window, as the + legacy TLS status of the initiating page cannot be tracked. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records whether the page would have a legacy TLS warning (if the user were + in the appropriate field trial) when submitting a form. This is recorded + whenever a form submission navigation begins. The recorded status is of the + page the form was submitted from, not the one that the form targets. + + + + + cthomp@chromium.org + estark@chromium.org + security-enamel@chromium.org + + Records whether the page would have a legacy TLS warning (if the user were + in the appropriate field trial) when the navigation to the page commits. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Tracks Page Info bubble actions along with whether the page would have a + legacy TLS warning (if the user were in the appropriate field trial). + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the reason the page visit ended (e.g., reload, tab closed, new + navigation, etc.) for page loads that committed. + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on an HTTPS URL that has + been marked dangerous or not secure (such as for malware or broken HTTPS). + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on a valid HTTPS URL that + has a security issue (e.g. mixed content). + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on a valid HTTPS URL with no + security issues (e.g. no mixed content) and an Extended Validation + Certificate. + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on a valid HTTPS URL with no + security issues (e.g. no mixed content), but no Extended Validation + Certificate. + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on an HTTP URL that has been + marked dangerous (such as for malware). + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on an HTTP URL that does not + have an omnibox security indicator warning associated with it. + + + + + estark@chromium.org + + Tracks Page Info bubble actions that take place on an HTTP URL that has been + given a "Not secure" warning in the omnibox. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the amount of time the Page Info bubble is open before the user + closes it or takes an action which closes it. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the amount of time the Page Info bubble is open before the user + closes it, for cases where the user has performed an action inside it. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the amount of time the Page Info bubble is open before the user + closes it, for cases where the user performed no action inside it. + + + + + meacer@chromium.org + security-enamel@chromium.org + + Site engagement level of the URL of the top frame of the navigation when the + user modifies a password field on the page. Only recorded once per + navigation for the top frame. + + + + + meacer@chromium.org + security-enamel@chromium.org + + Site engagement level of the URL of the top frame of the navigation when the + user focuses on a password field on the page. Only recorded once per + navigation for the top frame. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records the Safety Tip status on a page that initiated a download (*not* the + Safety Tip status of the download URL itself). This is recorded regardless + of whether the Safety Tip UI is enabled or disabled. This histogram is not + recorded for downloads that are initiated in a new tab or window, as the + Safety Tip status of the initiating page cannot be tracked. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records the Safety Tip status of a page when submitting a form. This + histogram is recorded whenever a form submission navigation begins. The + recorded safety tip status is the status of the page the form was submitted + from, not the one that the form targets. Recorded regardless of whether the + Safety Tip UI is enabled or disabled. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records a user's interaction with a Safety Tip. Recorded every time a user + uses one of the Safety Tip's buttons or dismisses it explicitly. Can be + normalized against Security.SafetyTips.SafetyTipShown, filtered to users + with the feature enabled to show the UI. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user explicitly closed the bubble. This is recorded in addition to the more + specifc metric that indicates how the user dismissed the Safety Tip. + + + + + jdeblasio@chromium.org + estark@chromium.org + livvielin@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user explicitly closed the bubble with the close button. This is recorded in + addition to the base dismiss metric. + + + + + jdeblasio@chromium.org + estark@chromium.org + livvielin@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user explicitly closed the bubble with the esc key. This is recorded in + addition to the base dismiss metric. + + + + + jdeblasio@chromium.org + estark@chromium.org + livvielin@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user explicitly closed the bubble with the ignore button. This is recorded + in addition to the base dismiss metric. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user closed the bubble by heeding the call-to-action to leave the site. + + + + + jdeblasio@chromium.org + estark@chromium.org + + Records the amount of time a Safety Tip bubble is open, for cases where the + user did not dismiss or take action in the bubble. + + + + + estark@chromium.org + jdeblasio@chromium.org + + Tracks Page Info bubble actions along with the Safety Tip status of the + page. + + + + + jdeblasio@chromium.org + src/chrome/browser/reputation/OWNERS + + Records the Safety Tip status of a page after navigation commit or page + visibility change. This is the same as SafetyTipShown, but with additional + suffixes for clarity. + + + + + jdeblasio@chromium.org + livvielin@chromium.org + + Records the Safety Tip status of a page after navigation commit for a page + where the Safety Tip has previously been ignored. + + + + + jdeblasio@chromium.org + livvielin@chromium.org + + Records the Safety Tip status of a page after navigation commit or page + visibility change. + + + + + jdeblasio@chromium.org + src/chrome/browser/reputation/OWNERS + + TEMPORARY histogram that records the Safety Tip status of a page after + navigation commit or page visibility change. This is the same as + SafetyTipShown, but records *after* the flag is checked to evaluate the + impact of starts_active. + + + + + jdeblasio@chromium.org + meacer@chromium.org + + Records the Safety Tip status of a page after navigation commit, alongside + how the corresponding navigation was initiated. Only recorded on navigations + that were visible at commit time. + + + + + + + + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the high-water-mark of the number of reports in the SCT auditing + cache size over each browser session. Recorded when the SCT auditing cache + is destroyed (normally during browser shutdown, and potentially if the + network service crashes). + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records whether a report was deduplicated (i.e., the SCTs were already in + the cache) or not. Recorded on each new report seen by the SCT auditing + cache (i.e., on each connection using certificate transparency). + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records whether a report was sampled to be sent to Safe Browsing. Recorded + for each new report seen by the SCT auditing cache that was not + deduplicated. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the size of an SCT auditing report that will be sent to Safe + Browsing (i.e., was not deduplicated and was sampled). + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records whether sending an SCT auditing report succeeded or not. This is + recorded after we receive the headers from the server (or we stop due to a + connection error). + + + + + estark@chromium.org + + Records the security level of a page with a cryptographic scheme (e.g. + https). This histogram is recorded once at navigation commit time, and can + be called again for the same document if the security level changes + dynamically. Note that the security level can change very quickly after + commit time, for example if the page includes mixed content on load (which + can downgrade the security level). This histogram should be analyzed with + care because each recorded security level is not necessarily user-visible: + in particular, a page may commit as a secure level (SECURE, EV_SECURE, + SECURE_WITH_POLICY_INSTALLED_CERT) but get quickly downgraded to NONE if it + shows mixed content on load. Therefore the histogram values should be + regarded as an upper-bound on what the user actually sees for these security + levels. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the security level of the page that initiated a download (rather + than the security state of the connection to the download URL itself). The + recorded security level is the level of the page the download was initiated + from, not that of the download URL. This histogram is not recorded for + downloads that are initiated in a new tab or window, as the security level + of the initiating page cannot be tracked. + + + + + carlosil@chromium.org + cthomp@chromium.org + + Records the security level of a page when submitting a form. This histogram + is recorded whenever a form submission navigation begins. The recorded + security level is the level of the page the form was submitted from, not the + one that the form targets. + + + + + estark@chromium.org + livvielin@chromium.org + + Records the security level of a page when submitting a form on a top-frame + navigation with a non-cryptographic scheme. This histogram is recorded + whenever a form submission navigation begins. The recorded security level is + the level of the page the form was submitted from, not the one that the form + targets. + + + + + estark@chromium.org + livvielin@chromium.org + + Records the security level of a page on top-frame navigations with a + non-cryptographic scheme that are not form submissions. This histogram is + compared against Security.SecurityLevel.InsecureMainFrameFormSubmission. + + + + + estark@chromium.org + + Records the security level of a page with a non-cryptographic scheme (e.g. + http). This histogram is recorded once at navigation commit time, and can be + called again for the same document if the security level changes + dynamically. Note that the security level can change very quickly after + commit time, for example if the page includes a password field on load + (which can downgrade the security level). This histogram should be analyzed + with care because each recorded security level is not necessarily + user-visible: in particular, a page may commit as NONE or WARNING but get + quickly downgraded to WARNING or DANGEROUS, depending on field trial + configuration, if it shows a password field on load. Therefore the histogram + values should be regarded as an upper-bound on what the user actually sees + for the NONE and WARNING levels. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the security level of a page at the time the navigation commits. + Note that the security level of a page can change after commit time, so this + histogram should often be compared against + Security.SecurityLevel.OnComplete. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the security level of a page at the end of the page visit (i.e., + navigating away from the page, reloading the page, clicking a link, closing + the tab, etc.). Note that this security level can be different than the + initial security level of the page, so this histogram should often be + compared against Security.SecuritLevel.OnCommit. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + The final Site Engagement score (0 to 100) of a URL during a visit to a + page. Recorded when the user closes the page or initiates a new navigation. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + The change in Site Engagement score for a site between the page navigation + committing and the user closing the page or navigating away. Recorded when + the user closes the page or initiates a new navigation. + + The delta is logged as a linear count in [0, 100]. To use, convert back to + the original difference (in the range [-100,100]) by multiplying by 2 and + subtracting 100. + + + + + cthomp@chromium.org + security-enamel@chromium.org + + Records the time spent on the page (the time that the page was in the + foreground from the start of the navigation to the page visit completing due + to a new navigation or the tab being closed). This aggregates all foreground + time over the entire visit (multiple times in the foreground are added + together). + + + + + mkwst@chromium.org + arthursonzogni@chromium.org + + Record uses of the X-Frame-Options header when a page is loaded as an + iframe. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/service/histograms.xml b/tools/metrics/histograms/histograms_xml/service/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..ada65b36ecea189ab1be854453d91f760efec17e --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/service/histograms.xml @@ -0,0 +1,1261 @@ + + + + + + + + + + nhiroki@chromium.org + jinho.bang@samsung.com + + The time taken between dispatching an AbortPaymentEvent to a Service Worker + and receiving a message that it finished handling the event. Includes the + time for the waitUntil() promise to settle. + + + + + shimazu@chromium.org + chrome-worker@google.com + + Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for + waitUntil() promise to settle. + + + + + falken@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + The result of dispatching the activate event to the worker. This is recorded + to both ServiceWorker.ActivateEventStatus and whichever of + ServiceWorker.ActivateEventStatus_InShutdown + ServiceWorker.ActivateEventStatus_NotInShutdown is appropriate. (InShutdown + means the context was null or ServiceWorkerProcessManger::Shutdown was + called.) + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + The time taken between dispatching a BackgroundFetchAbortEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + The time taken between dispatching a BackgroundFetchClickEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + The time taken between dispatching a BackgroundFetchFailEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + nator@chromium.org + peter@chromium.org + rayankans@chromium.org + + The time taken between dispatching a BackgroundFetchSuccessEvent to a + Service Worker and receiving a message that it finished handling the event. + Includes the time for the waitUntil() promise to settle. This event is sent + when the background fetch succeeds. + + + + + nator@chromium.org + rayankans@chromium.org + + The time taken between dispatching a SyncEvent to a Service Worker and + receiving a message that it finished handling the event. Includes the time + for the waitUntil() promise to settle. + + + + + horo@chromium.org + wanderview@chromium.org + + The length of cached metadata of scripts which are stored to the + CacheStorage by the installing service worker. + + + + + horo@chromium.org + wanderview@chromium.org + + The total length of cached metadata of scripts which are stored to the + CacheStorage by the installing service worker. + + + + + horo@chromium.org + wanderview@chromium.org + + The counts of scripts which are stored to the CacheStorage by the installing + service worker. + + + + + horo@chromium.org + wanderview@chromium.org + + The length of scripts which are stored to the CacheStorage by the installing + service worker. + + + + + horo@chromium.org + wanderview@chromium.org + + The total length of scripts which are stored to the CacheStorage by the + installing service worker. + + + + + nhiroki@chromium.org + jinho.bang@samsung.com + + The time taken between dispatching an CanMakePaymentEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + rayankans@chromium.org + platform-capabilities@chromium.org + + The time taken between dispatching a ContentDeleteEvent to a Service Worker + and receiving a message that it finished handling the event. Includes the + time for the waitUntil() promise to settle. + + + + + pwnall@chromium.org + + The time taken between dispatching a CookieChangeEvent to a Service Worker + and receiving a message that it finished handling the event. Includes the + time for the waitUntil() promise to settle. + + + + + bashi@chromium.org + nhiroki@chromium.org + + Records result of destroy database operations in ServiceWorkerDatabase. + + + + + + + nhiroki@chromium.org + + Records result of opening a database for ServiceWorkerDatabase. + + + + + bashi@chromium.org + nhiroki@chromium.org + Records result of read operations in ServiceWorkerDatabase. + + + + bashi@chromium.org + nhiroki@chromium.org + + Records result of write operations in ServiceWorkerDatabase. + + + + + bashi@chromium.org + nhiroki@chromium.org + + Records result of opening a disk cache for ServiceWorkerDiskCache. + + + + + bashi@chromium.org + nhiroki@chromium.org + + Records result of reading response from ServiceWorkerDiskCache. + + + + + bashi@chromium.org + nhiroki@chromium.org + + Records result of writing response into ServiceWorkerDiskCache. This is not + recorded when response has no body. Note that this is recorded on every + write operation, and can there can be multiple write operations for the same + response if it is large enough. + + + + + panicker@chromium.org + + Records when StartWorker is received on the renderer. This is used to + surface discrepancy between StartWorker being sent on the browser side and + not getting received by renderer. + EmbeddedWorkerInstance.Start.TimeToSendStartWorker should be used as a + baseline. TODO(panicker): This should be removed after investigation of + crbug/790903, potentially in M68. + + + + + nhiroki@chromium.org + chrome-worker@google.com + + The time taken between dispatching an ExtendableMessageEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + lazyboy@chromium.org + + The duration an external request spent to keep a service worker alive. + Currently, extension service workers use external requests to keep the + worker alive during the time the worker requests an extension API. + + + + + falken@chromium.org + chrome-worker@google.com + + The time taken between dispatching a FetchEvent to a Service Worker and + receiving a fallback-to-network reply. + + + + + falken@chromium.org + chrome-worker@google.com + + The time taken between dispatching a FetchEvent to a Service Worker and + receiving a response. Includes the time for the respondWith() promise to + settle. + + + + + falken@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + The result of dispatching a fetch event to a Service Worker for a main + resource request (i.e., a request for a navigation or a shared worker). + + + + + asamidoi@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + The time that a fetch event was queued. The start time is when the event is + created on the service worker thread and added to the + ServiceWorkerEventQueue. The end time is when the event is dequeued and the + event handler starts to execute. + + + + + falken@chromium.org + shimazu@chromium.org + chrome-worker@google.com + + The result of dispatching a fetch event to a Service Worker for a + subresource request (i.e., not a navigation or a shared worker request). + + + + + shimazu@chromium.org + chrome-worker@google.com + + The time taken between dispatching a FetchEvent to a Service Worker and + finishing the FetchEvent. Includes the time for the waitUntil() promise to + settle. If there is no waitUntil promise, this will be almost the same with + HasResponse.Time or Fallback.Time. + + + + + wanderview@chromium.org + + Measures how long the service worker thread is blocked creating a + mojo::DataPipe during FetchEvent.respondWith() processing. + + + + + bashi@chromium.org + chrome-worker@google.com + + Execution time of ServiceWorkerContextWrapper::GetAllOriginsInfo(). + + + + + shimazu@chromium.org + chrome-worker@google.com + + The time taken between dispatching an InstallEvent to a Service Worker and + receiving a message that it finished handling the event. Includes the time + for the waitUntil() promise to settle. + + + + + falken@chromium.org + chrome-worker@google.com + The result of dispatching the install event to the worker. + + + + bashi@chromium.org + chrome-worker@google.com + + The method that the user takes to arrive at + chrome://serviceworker-internals, based on the query string. Specifically, + it logs if a user accessed it through the DevTools link in the Application + Panel, or not. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) renderer process sends an IPC message to notify that + a resource loading request needs to be fall back to network, to (b) browser + process received the IPC. Recorded when no fetch event handler provided a + response to the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) renderer process sends an IPC message to notify that + a promise of respondWith() is settled, to (b) browser process received the + IPC message. Recorded when a fetch event handler handled the request and + provided a response to the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) a fetch event is dispatched, to (b) respondWith() is + settled for the fetch event, or fetch event dispatch is finished without + respondWith() being called. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) a resource loading request is routed to service + worker path, to (b) a service worker is ready to handle the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) response headers from service worker are received, + to (b) reading response body is completed. Recorded when a fetch event + handler handled the request. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) the start of a navigation request, to (b) the + request is forwarded to a service worker code path. This includes looking up + a service worker registration and throttling. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) browser process sends an IPC message to dispatch a + fetch event, to (b) a renderer process received the IPC message and is about + to dispatch a fetch event. + + Recorded for each navigation request (including redirects) where there is a + fetch event handler and the fetch event was successfully dispatched to the + service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) service worker sends a mojo message to notify that a + resource loading request needs to be fall back to network, to (b) the mojo + message is received on the other side of mojo endpoint (a background thread + executing subresource loading). Recorded when no fetch event handler + provided a response to the request. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) service worker sends a mojo message to notify that a + promise of respondWith() is settled, to (b) the mojo message is received on + the other side of mojo endpoint (a background thread executing subresource + loading). Recorded when a fetch event handler handled the request and + provided a response to the request. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) a subresource request is routed to the URLLoader (on + a background thread) for service worker controlled loads starts handling a + subresource request, to (b) a service worker is ready to handle the request. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) response headers from service worker are received, + to (b) reading response body is completed. Only recorded when a fetch event + handler handled the request. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + bashi@chromium.org + chrome-worker@google.com + + The time taken from (a) a fetch event is dispatched, to (b) respondWith() is + settled for the fetch event, or fetch event dispatch is finished without + respondWith() being called. + + Recorded for each subresource request where there is a fetch event handler + and the fetch event was successfully dispatched to the service worker. + + + + + shimazu@chromium.org + chrome-worker@google.com + + The time taken from (a) a resource loading request is routed to service + worker path, to (b) existance of a registered service worker is looked up. + This metric only cares about looking up a registration for navigation. This + doesn't include look-ups for updating a service worker. + + Please refer to the suffixed histograms for each of the cases where a + registration is found, not found, and an error happens. + + + + + falken@chromium.org + chrome-worker@google.com + + Counts main frame page loads controlled by a service worker. + + + + + peter@chromium.org + knollr@chromium.org + + The time taken between dispatching a NotificationClickEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + nsatragno@chromium.org + peter@chromium.org + + The time taken between dispatching a NotificationCloseEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + falken@chromium.org + chrome-worker@google.com + Counts page loads controlled by a service worker. + + + + nhiroki@chromium.org + jinho.bang@samsung.com + + The time taken between dispatching an PaymentRequestEvent to a Service + Worker and receiving a message that it finished handling the event. Includes + the time for the waitUntil() promise to settle. + + + + + nator@chromium.org + platform-capabilities@chromium.org + + The time taken between dispatching a PeriodicSyncEvent to a Service Worker + and receiving a message that it finished handling the event. Includes the + time for the waitUntil() promise to settle. + + + + + peter@chromium.org + + The time taken between dispatching a PushEvent to a Service Worker and + receiving a message that it finished handling the event. Includes the time + for the waitUntil() promise to settle. + + + + + peter@chromium.org + rayankans@chromium.org + knollr@chromium.org + viviy@google.com + + The time taken between dispatching a PushSubscriptionChangeEvent to a + Service Worker and receiving a message that it finished handling the event. + Includes the time for the waitUntil() promise to settle. The event is + dispatched and finishes in PushMessagingRouter::FireSubscriptionChangeEvent. + + + + + falken@chromium.org + chrome-worker@google.com + + The number of origins that have a service worker registration. Recorded near + browser startup, when the service worker storage system is initialized. + + + + + falken@chromium.org + + The amount of time a service worker ran for (wall time). Starts recording + when the service worker finished starting, and stops when the service worker + finished stopping. Not recorded if DevTools was attached to the service + worker at some point while it was running. + + + + + falken@chromium.org + chrome-worker@google.com + + The length of cached metadata of Service Worker scripts. Logged on each load + of Service Worker script only when the cached metadata is available. It + doesn't include the size of imported scripts. This histogram is only + recorded for classic workers, not module workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The total length of cached metadata of Service Worker scripts. Logged on + each start of Service Worker only when the cached metadata is available. It + includes the main script and imported scripts. This histogram is only + recorded for classic workers, not module workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The counts of scripts per Service Worker. Logged on each start of Service + Worker. It includes the main script and imported scripts. This histogram is + only recorded for classic workers, not module workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The length of Service Worker scripts. Logged on each load of Service Worker + script. It doesn't include the size of imported scripts. This histogram is + only recorded for classic workers, not module workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The total length of Service Worker scripts. Logged on each start of Service + Worker. It includes the main script and imported scripts. This histogram is + only recorded for classic workers, not module workers. + + + + + falken@chromium.org + + The result of trying to send the IPC message to a renderer process telling + it to stop an embedded worker. Recorded in EmbeddedWorkerInstance::Stop. + This was previously recorded for both the IPC and Mojo service worker + implementations, but as of Jan 2017, this is only recorded for the IPC + implementation. This histogram will be removed after the IPC implementation + is removed. + + + + + falken@chromium.org + chrome-worker@google.com + + The result of starting a service worker for a navigation hint. + + + + + falken@chromium.org + chrome-worker@google.com + + The time taken to start a Service Worker that has not yet installed, from + process allocation to ACK of started from the renderer (which occurs after + script execution). This may include script download time. The metric is not + recorded if DevTools was ever attached to the Service Worker during startup. + See also ServiceWorker.StartWorker.Time for installed workers. + + + + + kinuko@chromium.org + + The sum of all the times spent posting tasks between the UI and IO threads + during ServiceWorker startup. Recorded on a successful startup and when + DevTools was not attached. + + Note: This metric drops reports on clients with low-resolution clocks, which + means these reports will be biased against a portion of the population on + Windows. See Windows.HasHighResolutionTimeTicks for the affected sample. + + Also note that this one's recorded slightly different from others as it's + recorded even if the inter-process timings were inconsistent (see + ServiceWorker.StartTiming.ClockConsistency). + + + + + falken@chromium.org + shimazu@chromium.org + + Recorded on each successful service worker startup. + ServiceWorker.StartTiming.* uses timing data from both the renderer process + and browser process. This histogram describes whether the clocks are known + to be accurate and consistent accross processes, and whether the actual + timing data for this worker startup was consistent, i.e., TimeTicks did not + go backwards. + + If the clocks and timing were inconsistent, ServiceWorker.StartTiming.* + metrics (other than this one) are not recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken to start a service worker that is already installed, from + start of the start sequence (finding a renderer) to ACK of started from the + renderer (which occurs after script execution). The metric is not recorded + if DevTools was ever attached to the Service Worker during startup. It does + not include time, if any, waiting for the service worker to finish stopping + before asking it to start, if that occurred. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the renderer receiving the start worker IPC message, + to (b) initial JavaScript evaluation starting on the worker thread. Recorded + when ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) initial JavaScript evaluation finishing on the + worker thread, to (b) the browser receiving the worker started IPC message + (the final step of worker startup). Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) initial JavaScript evaluation starting on the worker + thread, to (b) initial JavaScript evaluation finishing on the worker thread. + Recorded when ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the browser sending the start worker IPC message, to + (b) the renderer receiving the start worker IPC message. Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the start of service worker startup, to (b) the + renderer receiving the start worker IPC message. Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the start of service worker startup, to (b) initial + JavaScript evaluation finishing on the worker thread. Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the start of service worker startup, to (b) initial + JavaScript evaluation starting on the worker thread. Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + shimazu@chromium.org + + The time taken from (a) the start of service worker startup, to (b) the + browser sending the start worker IPC message. Recorded when + ServiceWorker.StartTiming.Duration is recorded. + + + + + falken@chromium.org + chrome-worker@google.com + + The result of trying to start a service worker after it has failed + consecutively. Recorded only for installed workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The number of consecutive startup failures of a service worker. Recorded + each time the service worker failed (so there is double counting: failing + twice results in 1 and 2 being logged). Only for installed workers. + + + + + falken@chromium.org + chrome-worker@google.com + + When a worker startup succeeded after failing, the number of times the + worker had consecutively failed. Recorded only for installed workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The purpose for starting up a service worker. Recorded only for installed + workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The result of trying to start a Service Worker that is already installed. + See also ServiceWorker.StartNewWorker.Status for new workers. See also + ServiceWorker.StartWorker.StatusByPurpose_* for the breakdown by event type. + + + + + falken@chromium.org + chrome-worker@google.com + + The result of trying to start a service worker for a particular event type + (see ServiceWorker.StartWorker.Status for the total). Only recorded for + installed workers. For event type: + + + + + falken@chromium.org + chrome-worker@google.com + + The time taken to start a Service Worker that is already installed, from + process allocation to ACK of started from the renderer (which occurs after + script execution). The metric is not recorded if DevTools was ever attached + to the Service Worker during startup. See also + ServiceWorker.StartNewWorker.Time for new workers. + + + + + falken@chromium.org + chrome-worker@google.com + + Records the start purpose for a service worker that timed out while starting + up. Recorded only for installed workers. + + + + + falken@chromium.org + chrome-worker@google.com + + The phase the EmbeddedWorker was in when ServiceWorker startup timed out. + + + + + falken@chromium.org + The time taken to stop a Service Worker. + + + + bashi@chromium.org + chrome-worker@google.com + + Records result of storage recovery operations in ServiceWorkerStorage. + + + + + nhiroki@chromium.org + + Records successes and failures of purging a stale resource in + ServiceWorkerStorage. + + + + + wanderview@chromium.org + + The time between when the ServiceWorkerSubresourceLoader receives a Response + and when it notifies the loader's client that the body has started loading. + This is different from SubresourceStartBlobReadingDelay in that notifying + the client about the Response may take place some time later than when the + blob body reading begins. This will be triggered for every successful + subresource load handled by a ServiceWorker with servification enabled. + + + + + falken@chromium.org + + True if a message from the renderer intended for a browser-side embedded + worker instance found its recipient. False if the instance did not exist + when the message was received (e.g., it was a detached worker). Recorded in + EmbeddedWorkerRegistry::GetWorkerForMessage. + + + + + falken@chromium.org + chrome-worker@google.com + + The mechanism by which a service worker entered running status STOPPED. + + + + + wanderview@chromium.org + dmurph@chromium.org + chrome-owp-storage@google.com + + The time to perform operations on the Cache object in the ServiceWorker + Cache API. + + + + + jkarlin@chromium.org + + Records the response type to be added in the Cache by all operations that + write to the cache. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The time to perform a 'match' operation on a given Cache when that cache is + known to be fully initialized. This includes measurements for hits, misses, + and errors. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The time to perform a 'match' operation on a given Cache when the operation + was initiated from a service worker currently processing a FetchEvent with a + matching request URL. This includes measurements for hits, misses, and + errors. + + + + + dmurph@chromium.org + wanderview@chromium.org + chrome-owp-storage@google.com + + The time to perform operations on the CacheStorage object in the + ServiceWorker Cache API. + + + + + jkarlin@chromium.org + + Whether a new ServiceWorkerCacheStorage and its directory were successfully + created on disk. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + Whether the origin provided in the + DidGenerateCacheableMetadataInCacheStorage message is allowed for the given + renderer process. This message is sent when the renderer has generated code + cache for a script and wants to store it in cache_storage. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + Records where the generic kErrorStorage value is triggered within the + cache_storage code. + + + + + jkarlin@chromium.org + + The result of opening the backend in the ServiceWorker Cache API. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The result from parsing and validating the index protobuf while calculating + the list of cache_storage origins. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The time in ms from when an operation is started until it completes. This + histogram differs from the old OperationDuration in that it uses a different + bucket size to measure longer values. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The time in ms from when an operation was queued until its task is posted. + This histogram differs from the old QueueDuration in that it uses a + different bucket size to measure longer values. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + The number of operations in the scheduling queue just before enqueuing a new + operation. + + + + + wanderview@chromium.org + chrome-owp-storage@google.com + + Whether the size was calculated using the values stored in the origin's + index file. If this is false, then the size was recalculated by loading all + of the individual cache backends. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/session/histograms.xml b/tools/metrics/histograms/histograms_xml/session/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..a398c2c558905aab5ea54b36cd3f04ec07ccace4 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/session/histograms.xml @@ -0,0 +1,713 @@ + + + + + + + + + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Sum of this metric yields the total time Chrome was running in the + background. A single session may be represented by multiple values, so that + this histogram is always present in an uploaded log that represents + background activity. + + Android-only. + + + + + rohitrao@chromium.org + marq@chromium.org + + The number of tabs closed by the user during the current session + (launch/foregrounding to backgrounding). + + This histogram is only logged on iOS when the application is backgrounded. + + + + + rohitrao@chromium.org + marq@chromium.org + + The number of tabs created by the user during the current session + (launch/foregrounding to backgrounding). + + This histogram is only logged on iOS when the application is backgrounded. + + + + + rohitrao@chromium.org + marq@chromium.org + + The number of times the user changed the active tab (this can happen when + manually selecting a new tab, when a pre-rendered tab is made active, when + closing the current tab and the next one is selected) during the current + session (launch/foregrounding to backgrounding). + + This histogram is only logged on iOS when the application is backgrounded. + + + + + yiningwang@google.com + chrome-desktop-ui-sea@google.com + + Time spent in focus mode browser. This is recorded when the focus mode + window closes. This metric is only recorded on Win/Mac/Linux/ChromeOS. + + + + + + + asvitkine@chromium.org + chrisha@chromium.org + chrome-analysis-team@google.com + + The length of a session (launch/foregrounding to quitting/backgrounding) in + milliseconds, recorded at the end of the session. See + Session.TotalDurationMax1Day for the same histogram with a higher maximum + value. (The one's maximum is 1 hour.) + + Windows/Mac/Linux: A session ends (i) when the user puts another app in the + foreground, unless audio is playing. (The Chrome windows can still be shown. + What matters is that a different app has focus.) (ii) when Chrome quits. + (iii) when the screensaver turns on (again, unless audio is playing). (iv) + when the user is inactive for five minutes (again, unless audio is playing). + In this case (starting in M-55), that five minutes is not included in the + sesson length. (v) when audio stops playing, if the user has been inactive + for five minutes or Chrome is not in the foreground. Also, until M69, there + was a bug that caused double-counting of some sessions. + + ChromeOS: not implemented. The ChromeOS histogram Platform.DailyUseTime is + somewhat similar. + + Android: Session boundaries are wonky. Thus, only look at total duration for + a client over a day; don't look at individual durations. A session ends (i) + when the Chrome app leaves the foreground. This sounds obvious yet there are + many subtle though common edge cases here. Going to the Android Home screen + via the Home button is an obvious case. Yet, merely pressing the Recents + button, even if the user reselects the Chrome app (i.e., doesn't leave the + app) also ends a session. Another set of cases is the screen time-out + (blanking the screen) or the lock screen. Either will cause Chrome to be + considered to leave the foreground, ending the session. (ii) some in-app + actions. Yes, some in-app events trigger the end of a session. + + Android continued: These in-app actions that trigger the end of a session + can mostly be considered bugs. Cases: (a) switching to viewing Bookmarks, + History, Downloads, or Settings causes the session to end. Note that + switching out of those modes does not cause the end of a session, only + switching in. Oddly, though the interface looks similar, switching to Recent + Tabs does not trigger the end of a session. Nor does going into the tab + switcher view. (b) modal pop-ups. JavaScript dialogs and other things that + take focus away from the Chrome activity can cause this metric to record a + session end prematurely. See: crbug.com/678276. (c) switching Chrome from as + a single app in the foreground into multi-window mode. (d) switching Chrome + from being one of a set of multi-window apps that are displayed to be the + only app displayed. + + iOS: A session starts when Chrome is launched to the foreground and ends + when Chrome leaves the screen. This is generally straightforward. Chrome + leaves the screen when the screen goes blank or shows the lock screen, when + Chrome clicks a link that opens in another app, or when the user switches to + the app switcher. Note that, unlike on desktop, even if Chrome is playing + media in the background, the session is still terminated when Chrome leaves + the screen. + + iOS continued: These are some edge cases to be aware of: (i) OS overlays. + These can appear, for examples, when a link is clicked that could go to a + non-Google app that has not yet been set to default and the OS asks whether + to open the link in the app by default, or when a user has set the OS to + block certain sites or types of sites by default and require authentication + to access them. This authentication prompt is an OS overlay. At the time of + writing this description, we're not sure if displaying an overlay will end + the session. (ii) full-screen media playing. Because media is played through + iOS's technology stack, if the user takes media that's playing within Chrome + and displayed it full-screen, the session ends because no part of Chrome is + on the screen anymore. (iii) multi-window support. Not yet launched as of + M-85. Sessions end and immediately restart when a user switches from a + single-window to a multi-window view and vice versa, and also ends when + resizing the Chrome window. The end is because Chrome is considered no + longer active during the time the OS animates the windows to change their + sizes. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + chrome-analysis-team@google.com + + The amount of active browsing time that was spent not being opted in to sync + but while having a refresh token for a user's account. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin or + sync status changes. These end-points are when the metric is emitted. For + details on how "stopped interacting with the browser" is decided, + see the description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + chrome-analysis-team@google.com + + The amount of active browsing time that was spent not being opted in to sync + and not having a refresh token for a user's account. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin or + sync status changes. These end-points are when the metric is emitted. For + details on how "stopped interacting with the browser" is decided, + see the description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + chrome-analysis-team@google.com + + The total session duration (see Session.TotalDuration) that was spent being + opted in to sync while having a valid refresh token for the account. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin or + sync status changes. These end-points are when the metric is emitted. For + details on how "stopped interacting with the browser" is decided, + see the description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + chrome-analysis-team@google.com + + The total session duration (see Session.TotalDuration) that was spent being + opted in to sync without a having a valid refresh token for the account. + + This can for example be the case if the user signed out of the web, changed + their password, or otherwise invalidated their signin. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin or + sync status changes. These end-points are when the metric is emitted. For + details on how "stopped interacting with the browser" is decided, + see the description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + collinbaker@chromium.org + chrome-desktop-ui-sea@google.com + + Time spent in touch mode in each session (as defined by + DesktopSessionDurationTracker). Samples correspond one-to-one with + Session.TotalDuration samples. + + This histogram should be analyzed with Session.TotalDuration. For example, + the sum of this histogram divided by the sum of Session.TotalDuration is the + total proportion of active browsing time spent in touch mode. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + + The total session duration (see Session.TotalDuration) that was spent with + an account signed into the content area. + + The difference between the With(out)Account measurements and the + Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are + derived from the user's cookies, not their refresh tokens. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin + status changes. These end-points are when the metric is emitted. For details + on how "stopped interacting with the browser" is decided, see the + description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + + + + + + bsazonov@chromium.org + droger@chromium.org + msarda@chromium.org + treib@chromium.org + tschumann@chromium.org + + The total session duration (see Session.TotalDuration) that was spent + without an account signed into the content area. + + The difference between the With(out)Account measurements and the + Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are + derived from the user's cookies, not their refresh tokens. + + This time is measured from when the user starts interacting with the browser + until either they stopped interacting with the browser or their signin + status changes. These end-points are when the metric is emitted. For details + on how "stopped interacting with the browser" is decided, see the + description of Session.TotalDuration. + + Because a duration can end either because the user became inactive or + because their status changed, the distribution of individual durations + measured are unlikely to be helpful. Instead, please compare total + durations. + + This metric is only recorded on Win/Mac/Linux. + + One caveat with this metric is that if the user has multiple profiles open + at the same time, their session activity will be logged from all the + profiles, instead of only from the profile that the user is using at that + moment. + + + + + + + asvitkine@chromium.org + chrisha@chromium.org + chrome-analysis-team@google.com + + The length of a session (launch/foregrounding to quitting/backgrounding) in + milliseconds, recorded at the end of the session. See Session.TotalDuration + for details on how the end of a session is decided. The histogram + Session.TotalDuration records exactly the same values as this histogram, + just with a smaller maximum value. (That one's maximum is 1 hour.) + + This histogram is of special interest to the chrome-analysis-team@. Do not + change its semantics or retire it without talking to them first. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + Number of forward navigation items when navigation was committed/finished. + Recorded when main frame navigation was finished and there is at least one + navigation item. In conjunction with + Session.WebStates.HasForwardItemsAfterNavigation this metric will help to + understand how many navigation items Chrome should restore after relaunch. + + + + + ajuma@chromium.org + eugenebut@chromium.org + gambard@chromium.org + + True if navigation manager has forward navigation items when navigation was + committed/finished. Recorded when main frame navigation was finished. Can be + used to understand how often the users load items in the middle of + back-forward list. In conjunction with + Session.WebStates.ForwardItemsCountAfterNavigation this metric will help to + understand how many navigation items Chrome should restore after relaunch. + + + + + eugenebut@chromium.org + sdefresne@chromium.org + + Recorded when CRWNavigationItemStorage encodes the data, which happens on + page loads, tab changes and app backgrounding. Estimated size, the actual + size can be larger than recorded number. + + + + + justincohen@chromium.org + rohitrao@chromium.org + + The time needed to read iOS session webState data from a file. It's recorded + every time a webState is restored, typically on app startup. + + + + + justincohen@chromium.org + rohitrao@chromium.org + + The size of the file used to persist iOS session history. It's recorded + every time the file is written to storage, which happens on page loads, tab + changes and app backgrounding. + + + + + justincohen@chromium.org + rohitrao@chromium.org + + The time needed to write iOS session webState data to a file. It's recorded + every time the file is written to storage, which happens on page loads, tab + changes and app backgrounding. + + + + + yiyaoliu@chromium.org + How did the user interact with the SessionCrashed Bubble? + + + + chrisha@chromium.org + + The number of tabs involved in a single session restore that were observed + to have historically made use of background communication mechanisms + (favicon and tab title changes, notifications, etc). + + + + + chrisha@chromium.org + + The number of tabs involved in a single session restore that were observed + to have historically made use of background communication mechanisms + (favicon and tab title changes, notifications, etc) and that were actually + loaded. + + + + + + + chrisha@chromium.org + catan-team@chromium.org + + The time from SessionRestore start until a restored tab's first paint. + Recorded when a restored tab stays visible from the beginning of session + restore until its first paint, and no non-restored tab is painted during + that time. See SessionRestore.ForegroundTabFirstPaint4.FinishReason for when + this is not recorded. + + + + + + + chrisha@chromium.org + catan-team@chromium.org + + The reason for which attempt to record + SessionRestore.ForegroundTabFirstPaint4 was deemed complete. Logged once per + session restore. + + + + + chrisha@chromium.org + + The time since a restored tab was last active. This is the cumulative amount + of time that has passed since the tab was last visible. Time accrues while a + browser is active and the tab remains inactive. If the tab is restored and + remains inactive in a subsequent browsing session the time continues to + accrue. Visible tabs report a value of 0 for this. This is recorded at the + moment the tab is restored during a session restore. + + + + + mek@chromium.org + dmurph@chromium.org + + Total size of the HTML5 SessionStorage browser-side cache purged in KB when + memory pressure signal was triggered or cache size hit the limits. + + + + + mek@chromium.org + dmurph@chromium.org + + Total size of the HTML5 SessionStorage databases in KB in the browser-side + cache. Recorded each time a new database is opened in memory. + + + + + mek@chromium.org + dmurph@chromium.org + + The result of an attempt to commit SessionStorage data to the database. + + + + + mek@chromium.org + dmurph@chromium.org + + The result of a failed attempt to open a LevelDB database for + SessionStorage. + + + + + mek@chromium.org + dmurph@chromium.org + + The result of a failed attempt to open a LevelDB database for SessionStorage + on disk. + + + + + mek@chromium.org + dmurph@chromium.org + + The result of a failed attempt to open a LevelDB database for SessionStorage + in memory. + + + + + mek@chromium.org + dmurph@chromium.org + + The result of attempting to delete the SessionStorage database. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason opening a directory for the LevelDB database that backs + LocalStorage failed. + + + + + mek@chromium.org + dmurph@chromium.org + dullweber@chromium.org + + Recorded when the database connection is closed unexpectedly. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason opening the LevelDB database that backs SessionStorage failed. + + + + + + + mek@chromium.org + dmurph@chromium.org + + The result of opening the LevelDB database that backs SessionStorage. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason reading the namespaces metadata of the SessionStorage database + failed. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason reading the next data map id metadata of the SessionStorage + database failed. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason reading the schema version of the SessionStorage database failed. + + + + + + + mek@chromium.org + dmurph@chromium.org + + The result (success, failure, or database recreated) of trying to open the + LevelDB database for sessionStorage. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/settings/histograms.xml b/tools/metrics/histograms/histograms_xml/settings/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..3c364db1dddb826b195c62b3f6482b74e2ec60ee --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/settings/histograms.xml @@ -0,0 +1,549 @@ + + + + + + + + + + gab@chromium.org + + The amount of time it took to run PrefHashFilter::FilterOnLoad on startup. + + + + + gab@chromium.org + + The amount of time it took to run PrefHashFilter::FilterSerializeData on the + UI thread prior to writing the Preferences file to disk. Only logged when + PrefHashFilter::FilterSerializeData actually had work to do. + + + + + mpearson@chromium.org + twellington@chromium.org + + Whether or not the home page user preference is set to the default NTP value + when a profile is loaded. This is only logged if the home button is shown. + + + + + csharp@chromium.org + gab@chromium.org + + Logged on profile load. Indicates whether the hashes dictionary for this + profile is trusted. + + + + + bttk@chromium.org + twellington@chromium.org + wenyufu@chromium.org + + The location type for the homepage if the homepage is enabled. Recorded on + deferred startup iff the homepage is enabled. Android only. + + + + + mpearson@chromium.org + csharp@chromium.org + + Tries to pretend the home page URL is a search URL, and records the search + engine type of that URL by comparing the TLD+1 of the home page URL with + those of the different known search engines. Recorded when a profile is + opened, if a home page URL has been set. Note that at least one profile is + opened on startup. + + + + + twellington@chromium.org + tedchoc@chromium.org + + Whether or not the user has customized their homepage. This is recorded for + all users with a configurable homepage, regardless of whether they have + explicitly disabled the home button in settings. Recorded for Android only + on deferred startup and when the user changes their homepage URL. + + + + + gab@chromium.org + + The size (in kilobytes) of the JSON settings read from disk on startup. + Suffixed with the name of the corresponding JSON file. + + + + + dpapad@chromium.org + dbeam@chromium.org + + The amount of time between the render frame host StartProvisionalLoad event + and the render frame DocumentOnLoadCompleted event for the MD Settings page. + + + + + dpapad@chromium.org + dbeam@chromium.org + + The amount of time between the render frame host StartProvisionalLoad and + DidFinishDocumentLoad events for the MD Settings page. + + + + + mpearson@chromium.org + csharp@chromium.org + + Tries to pretend pinned tab URLs are search URLs, and records the search + engine types of those URLs by comparing the TLD+1s of the URLs with those of + the different known search engines. Recorded when a profile is opened, if + there are pinned tabs. Note that at least one profile is opened on startup. + + + + + rsorokin@chromium.org + jessejames@chromium.org + cros-oac@google.com + + The users progress through the pin unlock setup wizard. Each type + corresponds to the user completeing a different stage of the setup wizard. + + + + + harrisonsean@chromium.org + msramek@chromium.org + sauski@chromium.org + + Which privacy related settings elements a user interacted with. Recorded + every time a user interacts with an element of interest. + + + + + rainhard@chromium.org + msramek@chromium.org + Resulting state of the safety check Chrome cleaner check. + + + + andzaytsev@google.com + msramek@chromium.org + Resulting state of the safety check extensions check. + + + + rainhard@chromium.org + msramek@chromium.org + anaudrey@chromium.org + + Which user actions were taken in safety check. Recorded every time a user + does an interaction in safety check. Value 5 and 6 got added with M86. + + + + + andzaytsev@google.com + msramek@chromium.org + Resulting state of the safety check password check. + + + + andzaytsev@google.com + msramek@chromium.org + Resulting state of the safety check Safe Browsing check. + + + + andzaytsev@google.com + msramek@chromium.org + Resulting state of the safety check updates check. + + + + dschuyler@chromium.org + + The number of characters typed in the chrome://settings page search box. + Intended to determine if we are making the user type too much to find what + they are looking for (the search is incremental). + + + + + dschuyler@chromium.org + + If no matches are found when searching within the chrome://settings page, + record the length of the search text. + + + + + dschuyler@chromium.org + + The number of search page hits within the chrome://settings page. This is + especially important when the count is zero (i.e. we returned no hits for a + given search in settings). A search is considered complete via timeout since + there is no concrete way to define the end of a search (the search is + incremental). + + + + + dschuyler@chromium.org + + If there is no further activity in the search box for 1 second, this records + one tick each time a settings section is shown as a result of searching + withing the chrome://settings page. If multiple matches are found within the + same section, the section match is only recorded once. + + + + + dschuyler@chromium.org + + The number of search subpage hits within the chrome://settings page. This is + different from Settings.SearchPageMatchCount in that it is tracking hits in + subpages rather than top level pages. See also + Settings.SearchPageMatchCount. + + + + + mpearson@chromium.org + twellington@chromium.org + + Whether or not the home button is enabled in user preferences when a profile + is loaded. + + + + + twellington@chromium.org + tedchoc@chromium.org + + If the home button is enabled or disabled. This is only recorded if the + force homepage feature flag is enabled or the home button is partner + provided. Recorded for Android only on deferred startup and when the user + changes their home button enabled setting. + + This histogram is currently being updated to + ShowHomeButtonPreferenceStateManaged and will eventually be removed. + + + + + twellington@chromium.org + tedchoc@chromium.org + + The new state of the show home button preference after it is changed by the + user. Recorded for Android only. + + + + + twellington@chromium.org + tedchoc@chromium.org + + If the home button is enabled or disabled, either by user or by policy. + Recorded for Android only on deferred startup and when the user changes + their home button enabled setting. + + Note: HomeButtonPreferenceStateType#ManagedDisabled is currently not used. + + + + + pmonette@chromium.org + + The user clicked "Make Google Chrome the default browser" on the + settings page. + + + + + mpearson@chromium.org + csharp@chromium.org + + Tries to pretend the startup page URLs are search URLs, and records the + search engine types of those URLs by comparing the TLD+1s of the URLs with + those of the different known search engines. Recorded when a profile is + opened, if startup page URLs have been set. Note that at least one profile + is opened on startup. + + + + + mpearson@chromium.org + ramyan@chromium.org + tiborg@chromium.org + chrome-desktop-ntp@google.com + The startup page settings when a profile is loaded. + + + + dschuyler@chromium.org + + The time between when the chrome://settings page is opened to the first time + a search is done within that page. This is intended to evaluate how long a + user looks for a setting before giving up and searching for it. + + + + + dbeam@chromium.org + dpapad@chromium.org + + The time until the settings Web UI is loaded, rendered, and interactive for + users (as in they can change a setting). Automatically logged each time the + settings page is opened (if not closed before interactive). + + + + + proberge@chromium.org + + The id of a tracked preference whose value has been changed since the last + time Chrome set it. Without a suffix, this histogram stands for preference + validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference whose value has been cleared since the last + time Chrome set it. Without a suffix, this histogram stands for preference + validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference whose last value isn't known. We may be just + starting to track the preference, or local state may have been changed + outside of Chrome. This should only happen once per pref per profile. + Without a suffix, this histogram stands for preference validation using MACs + in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference whose value has not changed since the last + time Chrome set it, but which was last set using a legacy device ID. Each + user should report this at most once per preference id and immediately be + migrated to the latest hashing model. Without a suffix, this histogram + stands for preference validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference which was initialized despite the absence of + a MAC as its value was NULL. Without a suffix, this histogram stands for + preference validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + The id of a tracked preference which was reset by Chrome. + + + + gab@chromium.org + + Whether settings enforcement was cancelled for a machine joined to a domain. + Reported once per session on browser startup (note: this histogram was + disabled for part of M40). + + + + + proberge@chromium.org + + The id of a tracked preference which was initialized despite the absence of + a MAC as the current MACs are trusted, inferring that this is a newly + tracked pref. Without a suffix, this histogram stands for preference + validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference whose value has not changed since the last + time Chrome set it. Without a suffix, this histogram stands for preference + validation using MACs in the JSON pref files. + + + + + proberge@chromium.org + + The id of a tracked preference which Chrome would have reset had the config + allowed it. + + + + + mad@chromium.org + + Counts the number of times the user clicked on the No Thanks button of the + settings reset bubble before clicking on the Reset button in the same Chrome + session. + + + + + alito@chromium.org + + Indicates if an error was detected in the settings reset prompt config data + while initializing the reset prompt configuration. + + + + + alito@chromium.org + + Indicates whether the settings reset prompt dialog was shown to the user. + + + + + alito@chromium.org + + Indicates whether the user accepted the settings reset prompt. + + + + + alito@chromium.org + + Indicates whether the settings reset prompt should be shown to the user + based on the state of the user's settings. + + + + + alito@chromium.org + + Indicates whether the settings reset prompt is enabled for the user's + setting, or the reason for it being disabled. Logged once after startup. + + + + + alito@chromium.org + + Indicates which settings were reset after the user accepted the settings + reset prompt. + + + + + alito@chromium.org + + The time between the settings reset prompt dialog being shown and the user + accepting the prompt. + + + + + alito@chromium.org + + The time between the settings reset prompt dialog being shown and the user + declining the prompt by clicking the cancel button. + + + + + alito@chromium.org + + The time between the settings reset prompt dialog being shown and the user + dismissing the prompt, for example by clicking on the 'x' in the dialog or + pressing the Escape key. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/sharing/histograms.xml b/tools/metrics/histograms/histograms_xml/sharing/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..5a7059b053c39e97b55cd7d9c66938be8f31338e --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/sharing/histograms.xml @@ -0,0 +1,452 @@ + + + + + + + + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + The number of available apps that are about to be shown in a UI for picking + an app to start a phone call with. Desktop only. + + + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + The number of available devices that are about to be shown in a UI for + picking a device to start a phone call on. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Logged when we try to fire a dial intent in click to call. Distinguishes + between if the user has an app that can handle dial intent or not. Android + only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Logged whenever a dialog is shown for the Click to Call feature. Desktop + only. + + + + + knollr@chromium.org + mvanouwerkerk@chromium.org + + Duration of the phone number regex precompilation task. This is recorded + once after startup. Desktop only. + + + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + The index of the app selected by the user for Click to Call. Zero based. + Desktop only. + + + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + The index of the device selected by the user for Click to Call. Zero based. + Desktop only. + + + + + knollr@chromium.org + mvanouwerkerk@chromium.org + + Whether a device identified by its guid is available in the local + DeviceInfoTracker. Logged before sending a message to that guid. + + + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The number of hours since the target device timestamp was last updated. + Logged when a message is sent to the device. Not logged for sending ack + messages. All platforms. + + + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The number of hours since the target device timestamp was last updated. + Logged when a message is sent to the device and the result is known. Not + logged for sending ack messages. All platforms. + + + + + alexchau@chromium.org + peter@chromium.org + + Result of Sharing device registration. Logged after Sharing registration is + attempted. + + + + + alexchau@chromium.org + peter@chromium.org + + Result of Sharing device un-registration. Logged after Sharing + un-registration is attempted. + + + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The comparison of the major version of Chrome on this (the sender) device + and the receiver device. Logged when a message is sent. All platforms. + + + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time from sending a FCM message from the Sharing service until an ack + message is received for it. + + + + + + + mvanouwerkerk@chromium.org + himanshujaju@chromium.org + + The time from receiving a SharingMessage in SharingFCMHandler until an ack + is sent back. Recorded when SendAckMessage callback is run in + SharingMessageHandler. + + + + + mvanouwerkerk@chromium.org + peter@chromium.org + + The type of SharingMessage (aka the PayloadCase). This is logged when a + message is received through FCM by the handler in the Sharing service. All + platforms. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + The time to decode an image for Remote Copy. Desktop only. + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The result of handling a Remote Copy message. Logged once per message, when + the handler for the Remote Copy FCM message is finished handling it. Desktop + only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Result code from loading an image for Remote Copy. Logs net::Error if it's + not net::OK. Logs net::OK if response header is not present. Otherwise, logs + HTTP status code. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + The time to load an image for Remote Copy. Desktop only. + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The size of the image loaded from the image URL specified in a Remote Copy + message received from FCM, after decoding. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The size of the image loaded from the image URL specified in a Remote Copy + message received from FCM, before decoding. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The size of the text in a Remote Copy message received from FCM. Desktop + only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + The time to resize an image for Remote Copy. Desktop only. + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time to detect a clipboard image write for Remote Copy. Logged after + writing the image. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time to write an image to the clipboard for Remote Copy. Logged after + writing the image. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time to detect a clipboard text write for Remote Copy. Logged after + writing the text. Desktop only. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The time to write text to the clipboard for Remote Copy. Logged after + writing the text. Desktop only. + + + + + jeffreycohen@chromium.org + kristipark@chromium.org + src/components/send_tab_to_self/OWNERS + Whether the editor was dismissed during editor recreation. + + + + + + alexchau@chromium.org + knollr@chromium.org + + Result of sending an ack for a SharingMessage by the Sharing service. Logged + in the callback for sending the message to FCM. All platforms. + + + + + + + alexchau@chromium.org + knollr@chromium.org + + Result of sending a SharingMessage by the Sharing service. Logged after the + send message callback is run. Not logged for sending ack messages. All + platforms. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The number of available devices that are about to be shown in a UI for + picking a device to share the clipboard with. On desktop, it gets recorded + when the user right clicks on selected text. On Android, it gest recorded + when the user does long press, share and "Send text to Your + Devices". + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + Logged whenever a dialog is shown for the Shared Clipboard feature. + + + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The retry count for sending a shared clipboard message. The zero value is + for the first attempt to send the message, which is not a retry. Logged when + the result of sending the message is known. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The index of the device selected by the user for Shared Clipboard gets + recorded when the user chooses the destination device for sharing text. Zero + based. + + + + + mvanouwerkerk@chromium.org + knollr@chromium.org + + The size of the selected text in Shared Clipboard gets recorded when the + user shares selected text. + + + + + kmilka@chromium.org + src/components/send_tab_to_self/OWNERS + + Records the index of the third party app selected from the bottom row of the + sharing hub. + + + + + kmilka@chromium.org + src/components/send_tab_to_self/OWNERS + + Records the amount of time taken for the user to select a share target after + initiating a share. + + + + + kmilka@chromium.org + src/components/send_tab_to_self/OWNERS + + Records the amount of time taken for the custom share sheet to open after a + share was initiated. + + + + + himanshujaju@chromium.org + knollr@chromium.org + + Number of ice servers fetched by network traversal API call. Logged after + receiving response of API call. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/signin/histograms.xml b/tools/metrics/histograms/histograms_xml/signin/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..d2ea7fd1533f97f4979862d2972252c20f08625a --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/signin/histograms.xml @@ -0,0 +1,1115 @@ + + + + + + + + + + mlerman@chromium.org + + Tracks user interactions as they sign in through a flow. The suffix of the + histogram indicates what UI widget or application flow triggered the signin + flow. + + + + + bsazonov@chromium.org + aliceywang@chromium.org + + This histogram records the action taken by user after receiving the header + from Gaia in the web sign-in flow. Currently only recorded on Android. + + + + + droger@chromium.org + skym@chromium.org + + There are two separate ways to test for account equality, using the account + id or the email. Historically the email was always used, but going forward + email will be modifiable. Now when we check account equality we use both + approaches and emit this metric to capture if they agreed or not. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Records the state of the account reconcilor when GAIA returns a specific + response. + + + + + + + msarda@chromium.org + sdefresne@chromium.org + + Number of accounts loaded from preferences by the AccountTracker. Invalid + accounts are not counted. + + This is recorded on each profile load. + + + + + msarda@chromium.org + sdefresne@chromium.org + + This histogram records the AccountTracker account ID migration status from + email to GAIA ID after the data is loaded from disk. It is more general than + OAuth2Login.AccountRevoked.MigrationState that only record the event in case + of errors and only on Android. + + This histogram will be used to check whether the migration has completed for + all active installs on a given platform or not (and whether the code can be + removed). + + This is recorded on each profile load. + + + + + bsazonov@chromium.org + + The time it takes to seed accounts before proceeding to the account + confirmation screen. + + + + + bsazonov@chromium.org + aliceywang@chromium.org + + Number of Android accounts on device when entering the First Run Experience + sign-in screen. + + + + + alexilin@chromium.org + bsazonov@chromium.org + + The time it takes to retrieve Gaia ids for all accounts from GoogleAuthUtil. + + + + + alexilin@chromium.org + bsazonov@chromium.org + + The time it takes to retrieve the list of accounts from the system. + + + + + alexilin@chromium.org + bsazonov@chromium.org + + The time it takes to retrieve the list of accounts from the system on the UI + thread. + + + + + bsazonov@chromium.org + + How long the "Waiting for Google Play Services to finish updating" + dialog is shown. + + + + + bsazonov@chromium.org + chrome-signin-team@google.com + + The time UI thread spent waiting for the list of accounts to be populated. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + Records the UI event when user clicks a locked profile on UserManager. + Please note that if the local reauth failed, UserManager might show Gaia + Reauth dialog. + + + + + msarda@chromium.org + droger@chromium.org + + Log the type of GAIA authentication error that occur whenever the error + state changes. + + + + + + + droger@chromium.org + skym@chromium.org + + The relation between the account signed into chrome, and the account(s) in + the cookie jar. This metric is never recorded when not signed into chrome. + + + + + + + droger@chromium.org + skym@chromium.org + The number of signed in accounts in the cookie jar. + + + + jkrcal@chromium.org + droger@chromium.org + + The number of signed in accounts in the cookie jar for users that have a + (possibly unconsented) primary account. Reported at most every 24 hours + (using a persistent timer). Reporting is split based on the type of the + primary account. + + + + + + + droger@chromium.org + skym@chromium.org + The number of signed out accounts in the cookie jar. + + + + + + droger@chromium.org + skym@chromium.org + The amount of time since the cookie jar last changed. + + + + + + droger@chromium.org + skym@chromium.org + The total number of accounts in the cookie jar. + + + + + + droger@chromium.org + msarda@chromium.org + Records Dice responses (signin and signout). + + + + + + droger@chromium.org + msarda@chromium.org + Outcome of the token fetch in Dice signin. + + + + alexilin@chromium.org + droger@chromium.org + + Result of the browser remote consent flow, which is a part of the + chrome.identity.getAuthToken() extension API call. Desktop only. + + + + + + + alexilin@chromium.org + droger@chromium.org + + Result of the chrome.identity.getAuthToken() extension API call. Recorded + right before returning the result to an extension. Desktop only. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + The number profile load events that needs a force-sign-in verification + request. It's recorded when profile is loaded with an authentication token + and force-sign-in policy is enabled. + + + + + zmin@chromium.org + pastarmovj@chromium.org + + Elapsed time of the force-sign-in verfication if it's finished. It includes + total network delay, retry delay and wait time due to no connection. The + verfication will not be recorded if it's not finished before profile is + signed out or removed from memory. + + + + + + + droger@chromium.org + msarda@chromium.org + + The number of requests initiated by the browser to log the user out from + Google web. The Chrome account reconcilor enforces account consistency for + Google accounts between the browser and web. In some cases it must force + logout the user from Google web and then it sends a request to the Gaia + logout endpoint. The expectation is that brower initiated logout is a rare + event and should only occur in the following cases: a) it to be triggered + when the browser fails to exchange an auth code for refresh tokens after a + web sign-in (events which is counted by histogram + Signin.DiceTokenFetchResult), b) when all refresh tokens are invalid (e.g + when they cannot be loaded from disk). + + + + + droger@chromium.org + msarda@chromium.org + + Reconds finished access token requests during Chrome reconcile, both + successful or not, and return the GoogleAuthError state NONE is a success, + other values are failures. + + + + + droger@chromium.org + msarda@chromium.org + + Retry reason of failed access token requests during Chrome reconcile. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the duration of the account info fetch after signin interception. + + + + + droger@chromium.org + alexilin@chromium.org + + Records the outcome of the signin interception heuristic, which runs for + each signin interception. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the duration of the signed-in profile creation after signin + interception. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the duration of the signed-in profile switch after signin + interception. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the duration of session startup time after signin interception. This + includes waiting for the account to be available on the web. + + + + + + + alexilin@chromium.org + droger@chromium.org + + Records the outcome of the enterprise signin interception bubble. Recorded + when the bubble is dismissed. + + + + + + + droger@chromium.org + msarda@chromium.org + + Reason for invalid Gaia credentials. Recorded when Signin.AuthError records + invalid credentials. + + + + + treib@chromium.org + mmoskvitin@google.com + + Records the general type of signin that is occuring in relation to previous + signin and local data. + + + + + fernandex@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Records whether the Gaia cookie is present when a user navigates to a + Google-owned domain that is eligible for Mirror account consistency to track + authentication cookies that have been remove by an external force (e.g. + Apple's ITP). This logging is limited to once every hour due to performance + constraints. + + + + + jebel@chromium.org + fernandex@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Tracks the combination of sign-in method and sync state for signed-in users + on iOS. If the user is signed in, this histogram is updated with the sign-in + method and the sync state each time the application goes to foregrond. + "Client Login" corresponds to users that have signed in via the + legacy client login flow (Chrome iOS M27 and before). "Shared + Authentication" corresponds to user that have signed in via the iOS + Shared Authentication library. "Sync off" corresponds to users + that have sync turned off. "Sync on" corresponds to users that + have sync turned on. + + + + + fernandex@chromium.org + jlebel@chromium.org + msarda@chromium.org + chrome-signin-team@google.com + + Count of the number of SSO accounts present on the device. Note that this is + different to the number of accounts signed in in Chrome. The count is logged + in this histogram each time the application goes to foreground. + + + + + droger@chromium.org + skym@chromium.org + + Current best guess if this device is shared between multiple users. + + + + + + + msarda@chromium.org + droger@chromium.org + + Failure reason of ListAccounts call failure during account reconciliation, + Chrome OS login, or signin internals queries. + + + + + + + msarda@chromium.org + droger@chromium.org + + Retry reason of failed ListAccounts calls (these calls calls are used to + fetch the list of Google accounts present in the Gaia cookies). + + + + + jlebel@chromium.org + msarda@chromium.org + + Counts the number of identities loaded by SSO library using the keychain + API. The metric is recorded every time SSO updates the identity list (either + on the first run, or when the cache is staled). See: + https://crbug.com/897470. + + + + + jlebel@chromium.org + msarda@chromium.org + + Tracks the time it takes to load identities by SSO library using the + keychain API. The metric is recorded every time SSO updates the identity + list (either on the first run, or when the cache is staled). See: + https://crbug.com/897470. + + + + + jlebel@chromium.org + msarda@chromium.org + + Tracks the time it takes to load one identity in average by SSO library + using the keychain API. This value is the total time taken by the keychain + API to finish, divided by the number of identities returned. The metrics is + recorded every time SSO updates the identity list (either on the first run, + or when the cache is staled). See: crbug.com/897470. + + + + + + + droger@chromium.org + msarda@chromium.org + + Action taken for tokens being loaded from the token database, at Chrome + startup. Tokens can be either loaded into Chrome's token service or revoked. + + + + + + + droger@chromium.org + msarda@chromium.org + + Number of accounts in tokens sent to Gaia Multilogin. Recorded when Chrome + does a request to /oauth/multilogin. + + + + + alexilin@chromium.org + droger@chromium.org + + Result of the OAuth2MintToken API call. Recorded after the response is + processed. Desktop only. + + + + + + + msarda@chromium.org + droger@chromium.org + + Reason fetching an OAuth2 Token failed or none in case of success. Available + on all OSes. + + + + + + + msarda@chromium.org + droger@chromium.org + + Reason fetching an OAuth2 Token is being retried. Available on all OSes. + + + + + + + droger@chromium.org + msarda@chromium.org + Response status received from gaia Multilogin. + + + + noms@chromium.org + + Count of the ways users interact with the confirmation dialogs of the new + web based sign in to Chrome flow (accessed via the one click signin). + + + + + noms@chromium.org + Tracks events related to the reauthentication Gaia page. + + + + + + msarda@chromium.org + droger@chromium.org + + How many accounts were added to the cookie jar because they were in the + browser's token service. + + + + + + + msarda@chromium.org + droger@chromium.org + + Records whether all external connections have been successfully checked (a + value of "true") or not ("false") when the reconciler + attempts to perform MergeSession. + + + + + + + msarda@chromium.org + droger@chromium.org + + After execution of the account reconcilor, compares the primary account in + the token service to the primary GAIA account of the cookie jar. + + + + + + + droger@chromium.org + msarda@chromium.org + + Records the execution time of the account reconciler using 100 buckets, up + to 3 minutes. + + + + + + + msarda@chromium.org + droger@chromium.org + + Records the time it took to successfully check all external connections + whenever the reconciler performs a reconciliation. + + + + + + + msarda@chromium.org + droger@chromium.org + + Records the time it took to check only a portion of external connections + whenever the reconciler performs a reconciliation. This means that either a + network error occured while checking some sites or the site did not respond + before the check timeout. + + + + + + + msarda@chromium.org + droger@chromium.org + + How many accounts were removed from the cookie jar because they were not in + the browser's token service. + + + + + droger@chromium.org + msarda@chromium.org + + Reports the status (including error details) of token revocation requests + after they complete. This is recorded once per token, even if the request is + retried multiple times. It will be either a success if the token has been + revoked or the error on the last retry. + + + + + droger@chromium.org + + Tracks the progress of revocation requests for refresh tokens, and can be + used to check how many requests do not complete and why. Recorded for each + refresh token revocation request from the token service. + + + + + droger@chromium.org + msarda@chromium.org + + Reports the status (including error details) of token revocation requests + after they complete. + + + + + + + droger@chromium.org + msarda@chromium.org + + Source for refresh token revocation. This is used to track the sources for + signing out of Google accounts and is required to validate that the browser + is not revoking tokens for large parts of the user population. + + + + + + + droger@chromium.org + msarda@chromium.org + + Source for refresh token updated to invalid tokens. The refresh token is + updated to an permanently invalid token when the user attempts to sign out + of the primary account without turning off sync. This histogram is used to + track the sources for invalidating the token of the primary account and is + required to validate that the browser is not invalidating the token of the + primary account for large parts of the user population. + + + + + + + droger@chromium.org + msarda@chromium.org + + Source for refresh token updated to valid tokens. This is used to track the + sources for adding Google accounts to the browser. + + + + + anastasiian@chromium.org + sinhak@chromium.org + + The result of logging the parent consent for secondary EDU account addition + in child account sessions. + + + + + + + msarda@chromium.org + droger@chromium.org + + This histogram records the success of setting each cookie after Multilogin + response is received and parsed. + + + + + fernandex@chromium.org + jlebel@chromium.org + msarda@chromium.org + + Track the number of times the view that displays the accounts that are + signed is shown. This view only exists on iOS and is shown every time the + application enters forground iff the accounts changed while it was in + background. Only bucket "Shown" is being recorded (this histogram + is a counter). + + This histogram was added following crbug.com/1006717 (stable regression) + where the signed-in accounts view was repeatedly shown for a set of users. + It is used as a counter to monitor that there are no bumps in its timeline. + + + + + + + droger@chromium.org + msarda@chromium.org + tangltom@chromium.org + + Tracks the state of a user's signin-allowed preference. This is recorded at + every startup. + + + + + msarda@chromium.org + bsazonov@chromium.org + droger@chromium.org + chrome-signin-team@google.com + Logs the original access point of each completed sign in. + + + + msarda@chromium.org + bsazonov@chromium.org + droger@chromium.org + chrome-signin-team@google.com + Logs the reason of each completed sign in. + + + + msarda@chromium.org + bsazonov@chromium.org + droger@chromium.org + chrome-signin-team@google.com + + Logs the original access point that displayed the signin or reauth Gaia + page, before the page is displayed. + + + + + skym@chromium.org + + If the user chose to delete their profile or not when signing out of an + unmanaged account. When the user is not given a choice this metric is not + recorded. + + + + + + + msarda@chromium.org + droger@chromium.org + Track how a profile gets signed out. + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Tracks the error code by -[SSOService identitiesWithError:]. See: + https://crbug.com/981082. + + + + + + + jlebel@chromium.org + fernandex@chromium.org + + Tracks the SSO identity cache state before calling -[GCRSSOService + identitiesWithError:] or -[GCRSSOService identitiesForDisplay]. See: + https://crbug.com/897470. + + + + + + + jlebel@chromium.org + fernandex@chromium.org + + Tracks the time it takes to call -[GCRSSOService identitiesWithError:] or + -[GCRSSOService identitiesForDisplay]. See: https://crbug.com/897470. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts the number of cookies returned by -[WKHTTPCookieStore + getAllCookies:]. This histogram is to help to understand how many callbacks + from |getAllCookies:| can be missing. And if the number of cookies is + related in that iOS bug. See: crbug.com/880981. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Tracks the time it takes for -[WKHTTPCookieStore getAllCookies:] to finish + and call its callback. Note that nothing is logged is -[WKHTTPCookieStore + getAllCookies:] fails to calls its callback. This histogram is to help to + understand how many callbacks from |getAllCookies:| can be missing, related + to a bug from iOS. And if the number of cookies is related in that iOS bug. + See: crbug.com/880981. + + + + + jlebel@chromium.org + chrome-signin-team@google.com + + Counts the number of times -[WKHTTPCookieStore getAllCookies:] is called and + the number of times it calls its callback. This histogram is to help to + understand how many callbacks from |getAllCookies:| can be missing, related + to a bug from iOS. And if the number of cookies is related in that iOS bug. + See: crbug.com/880981. + + + + + + + triploblastic@chromium.org + bsazonov@chromium.org + + Records various UI and user action events related to the sync error infobar. + Android only. + + + + + triploblastic@chromium.org + bsazonov@chromium.org + Tracks where FirstSetupComplete bit is set from. + + + + + + msarda@chromium.org + + Counts how many times the SQL statements to get all tokens is valid. + + + + + + + msarda@chromium.org + + Counts the results of loading a refresh token from the token database. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the time from when the user confirms transactional reauth to when + the backround navigation to the Gaia reauth endpoint completes. + + + + + alexilin@chromium.org + droger@chromium.org + + Records the time from when the user triggers transactional reauth to when + the background navigation to Gaia reauth endpoint completes. + + + + + + + alexilin@chromium.org + fhorschig@chromium.org + + Recorded whenever the user interacts with reauthentication to complete a + transaction (like interacting with the account store for passwords) and + whether the reauth challenge was cleared. + + + + + + + alexilin@chromium.org + droger@chromium.org + + Records user actions performed in the reauthentication dialog/tab. + + + + + + + msarda@chromium.org + droger@chromium.org + + Reason of failure to acquiring an ubertoken based on an already-minted + access token. Available on all OSes. + + + + + + + msarda@chromium.org + droger@chromium.org + + Retry reason of failure to acquire an ubertoken based on an already-minted + access token. Available on all OSes. + + + + + triploblastic@google.com + bsazonov@chromium.org + User requested to wipe local device data on signout. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/simple/histograms.xml b/tools/metrics/histograms/histograms_xml/simple/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..2aa6b5c0442842ee2182aaa28b4a0d95b1d3e2d9 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/simple/histograms.xml @@ -0,0 +1,582 @@ + + + + + + + + + + jkarlin@chromium.org + + The size of the cache at the time that the index has finished initializing. + + + + + morlovich@chromium.org + wanderview@chromium.org + + Whether or not the CRC was checked at the moment when the last reference to + a read-only entry stream is closed. + + + + + wanderview@chromium.org + morlovich@chromium.org + + Record the outcome of the simple DiskCache consistency check. The + consistency check is executed every time a simple DiskCache is initialized. + This check includes both inspecting the schema on disk and upgrading the + schema to the latest version if necessary. + + + + + wanderview@chromium.org + morlovich@chromium.org + + Record the final consistency check value after index files have been deleted + from an empty simple DiskCache. This histogram will tell us how often the + index deletion code results in a functioning cache. It will also tell us + what kind of consistency failures cannot be recovered due to index file + deletion. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time from the creation of the simple cache backend until the index has + been loaded from disk. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time from the creation of the simple cache backend until the index fails + to load. + + + + + wanderview@chromium.org + morlovich@chromium.org + + Record if any simple DiskCache index files were deleted from an otherwise + empty cache after the cache failed the initialization consistency check. + This histogram will tell us how often the deletion code is triggering and + modifying the disk. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time to close (write out footers and close the file) the cache entry on + disk. Includes only successful operations. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time to access (open for creation and write initial headers) the cache + entry on disk. Includes only successful operations. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time to remove the cache entry on disk. Includes only individually + doomed entries, not entries bulk-erased during eviction. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time to access (open and read headers from all files) the cache entry on + disk. Includes only successful operations. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time to write a chunk to the cache entry on disk. Includes only + successful operations. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The time, in ms, spent creating a new entry on disk. This measures time from + when the method got removed from SimpleEntryImpl's operation queue till when + the callback is about to be invoked, and includes all Open and Create + operations, despite what the name may suggest. + + + + + wanderview@chromium.org + morlovich@chromium.org + + The difference between EntryTrailerPrefetchSize and EntryTrailerSize in + bytes within a single ReadAndValidateStream0AndMaybe1() method call. If the + prefetch read too many bytes then this will be a positive value. If the + prefetch did not read enough bytes, then this will be a negative value. + + + + + wanderview@chromium.org + morlovich@chromium.org + + The number of bytes prefetched from the end of the entry file in an attempt + read the EOF footer and the stream 0 data in a single file operation. + Ideally this value should match the EntryTrailerSize histogram indicating + the actual trailer size on disk was. + + + + + morlovich@chromium.org + The size of the cache at the beginning of an eviction. + + + + morlovich@chromium.org + The number of entries to be erased in an eviction. + + + + morlovich@chromium.org + + The maximum allowed size of the cache at the beginning of an eviction. + + + + + morlovich@chromium.org + wanderview@chromium.org + The result of an eviction. + + + + morlovich@chromium.org + wanderview@chromium.org + The amount of memory freed in an eviction. + + + + morlovich@chromium.org + wanderview@chromium.org + The size of the cache after running an eviction. + + + + morlovich@chromium.org + wanderview@chromium.org + Time spent completing an eviction. + + + + morlovich@chromium.org + wanderview@chromium.org + Time spent selecting entries for eviction. + + + + morlovich@chromium.org + wanderview@chromium.org + + This even is emitted when SimpleCache is forced to either close some files + due to being over FD limit, or reopen files it had to close due to such + limit earlier. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The size of the header stream of a Simple Cache entry, emitted every time + the headers are written or rewritten. + + + + + morlovich@chromium.org + wanderview@chromium.org + The number of entries in a newly created index file. + + + + morlovich@chromium.org + wanderview@chromium.org + + The state the index file is at when an attempt is made to load from it. + + + + + wanderview@chromium.org + morlovich@chromium.org + The method used to initialize the simple cache index. + + + + jkarlin@chromium.org + + The number of entries in the index at the time that the index has finished + initializing. + + + + + morlovich@chromium.org + wanderview@chromium.org + The number of entries written to the index on a flush. + + + + morlovich@chromium.org + wanderview@chromium.org + + Time (as measured on the worker pool) spent restoring the index file by + iterating directory entries. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The reason an index was written to disk. Recorded every time an index is + saved. + + + + + morlovich@chromium.org + wanderview@chromium.org + + Recorded immediately after loading a fresh index (INDEX_STATE_FRESH or + INDEX_STATE_FRESH_CONCURRENT_UPDATES), the reason the loaded index was + written to disk. + + + + + jkarlin@chromium.org + + The maximum allowed size of the cache at the time that the index has + finished initializing. + + + + + morlovich@chromium.org + wanderview@chromium.org + + At the time that an entry is opened, the state of that entry in the index. + + + + + wanderview@chromium.org + morlovich@chromium.org + + Record the original consistency error produced by a simple DiskCache before + a retry was attempted and succeeded. This histogram will tell us what kind + consistency errors can be recovered from in practice. + + + + + jkarlin@chromium.org + + The fullness (in percent) of the cache at the time that the index has + finished initializing. The percentage is calculated as (cache_size * 100) / + max_cache_size. + + + + + wanderview@chromium.org + morlovich@chromium.org + + Record the outcome of the simple DiskCache consistency check after retrying + initialization on an empty cache directory. The retry may occur after + corrupt index files were deleted from an empty cache. The retry may also + occur if the original failed initialization left an empty directory without + any index files. This histogram will tell us how often the retry succeeds in + recovering caches and also which consistency checks cannot be recovered. + + + + + morlovich@chromium.org + wanderview@chromium.org + + Count of the number of entries recorded in the index, but not actually + present in the cache. Recorded each time a stale index is found and a + directory rescan is required. + + + + + morlovich@chromium.org + wanderview@chromium.org + + Count of the number of entries present in a cache, but not recorded in the + index. Recorded each time a stale index is found and a directory rescan is + required. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The quality of a "stale" index compared to a full directory + rescan. Recorded immediately after every directory scan for stale indexes. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The result, at the synchronous layer, of checking the EOF record of a cache + entry. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The result, at the synchronous layer, of closing a cache entry. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The platform error reported when attempting to create a new cache entry at + the synchronous layer. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The platform error reported when attempting to create a new cache entry at + the synchronous layer. + + + + + wanderview@chromium.org + morlovich@chromium.org + + The kind of prefetching performed, if any, when executing + SimpleSynchronousEntry::ReadAndValidateStream0AndMaybe1(). + + + + + morlovich@chromium.org + wanderview@chromium.org + + The result, at the synchronous layer, reported when attempting to open a new + cache entry. + + + + + morlovich@chromium.org + wanderview@chromium.org + + The result, at the synchronous layer, of writing to a cache entry. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + Events in reqests processing of IP-based SimpleGeolocation. + + + + + + alemate@chromium.org + michaelpg@chromium.org + skylarc@chromium.org + + This boolean histogram counts SimpleGeolocationRequests carrying a nonzero + number of cell towers. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + + This boolean histogram counts SimpleGeolocationRequests carrying nonzero + number of WiFi access points. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + Http response codes in IP-based SimpleGeolocation. + + + + + + alemate@chromium.org + michaelpg@chromium.org + + The time elapsed between the sending of the first API request and the time + the final (failed) response was recorded. Includes all retries. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + + The time elapsed between the sending of the first API request and the time + the final (successfull) response was recorded. Includes all retries. + + + + + + + alemate@chromium.org + michaelpg@chromium.org + Result of SimpleGeolocationRequest. + + + + + + alemate@chromium.org + michaelpg@chromium.org + Number of retries until the final response was recorded. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/smart/histograms.xml b/tools/metrics/histograms/histograms_xml/smart/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..d16bfff8d395813d265bcf59c105d970c004599f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/smart/histograms.xml @@ -0,0 +1,312 @@ + + + + + + + + + + hansberry@chromium.org + better-together-dev@google.com + Records the user's sign in method choice. + + + + hansberry@chromium.org + better-together-dev@google.com + + The state Smart Lock was in when the user chose to use their password to + sign into their device. + + + + + hansberry@chromium.org + better-together-dev@google.com + Records the user's unlock method choice. + + + + hansberry@chromium.org + better-together-dev@google.com + + An enumerated histogram that breaks down what state Smart Lock was in when + the user chose to use their password to unlock their device. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Count of successful and failed attempts to sign in the Chromebook, after the + user selects their profile photo. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Shows why a sign in attempt failed during the authentication phase. Breaks + down the failure bucket of SmartLock.AuthResult.SignIn. + + + + + hansberry@chromium.org + better-together-dev@google.com + + An enumerated histogram that breaks down why the UserController could not + decrypt the account. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Count of successful and failed attempts to unlock the Chromebook, after the + user selects their profile photo. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Shows why an unlock attempt failed during the authentication phase. Breaks + down the failure bucket of SmartLock.AuthResult.Unlock. + + + + + hansberry@chromium.org + better-together-dev@google.com + + A count of the number of eligible SmartLock devices which can be used to + unlock the user's Chromebook. Logged each time the list of eligible devices + is updated. TODO(jhawkins): Log this again once we send this data from + eligible phones. + + + + + hansberry@chromium.org + better-together-dev@google.com + + A count of the number of SmartLock devices which the user has enabled to + unlock the user's Chromebook, i.e., the device connected to in the SmartLock + setup flow. Logged each time the list of eligible devices is updated. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The state of the SmartLock feature for the current user, set at login. The + value is 'enabled' if the user has successfully enabled SmartLock via setup, + disabled if the user has explicitly disabled the feature after it has been + enabled, and unset if the feature is passively disabled, i.e., has never + been enabled by the user. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The resolution of Smart Lock trying to find the host device during the + initial scan window at the signin screen. + + + + + hansberry@chromium.org + better-together-dev@google.com + + The resolution of Smart Lock trying to find the host device during the + initial scan window at the lock screen. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Count of successful and failed attempts to get the 'remote status' of the + host device, i.e., determine if the Chromebook can be signed into. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Shows why a sign in attempt failed during the connection phase. Breaks down + the failure bucket of SmartLock.ConnectionResult. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Count of successful and failed attempts to get the 'remote status' of the + host device, i.e., determine if the Chromebook can be unlocked. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Shows why an unlock attempt failed during the connection phase. Breaks down + the failure bucket of SmartLock.ConnectionResult. + + + + + hansberry@chromium.org + better-together-dev@google.com + + Indicates the feature state of the SmartLock feature. This metric is emitted + to at the creation of the user session (when the user logs in), and when + feature state updates occur. + + + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when Smart Lock successfully establishes a + secure channel connection to the host device, and receives the initial + remote status from it -- this informs if the device can be unlocked on the + first remote status (i.e., if the Smart Lock icon is yellow or green). + + Suffixed by the type of remote status which was the first to be received. + View the base histogram to see results for all remote status types + aggregated together, and suffixed histograms for the results of just that + particular remote status type. + + See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the + remote status from the host. + + + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when the user locks their screen or wakes their + device (either opening a clamshell device or waking up a tablet), and when + the user is first provided a visible indication of Smart Lock's status (the + Smart Lock icon presents as either yellow or green, with a tooltip + explaining the status). + + Suffixed by the type of status which the user is first presented with. View + the base histogram to see results for all status types aggregated together, + and suffixed histograms for the results of just that particular remote + status type. + + See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the + remote status from the host. + + + + + + + hansberry@chromium.org + better-together-dev@google.com + + The duration of time between when Smart Lock begins to try to find the host + device, and receives the initial remote status from it -- this informs if + the device can be unlocked on the first remote status (i.e., if the Smart + Lock icon is yellow or green). + + Suffixed by the type of remote status which was the first to be received. + View the base histogram to see results for all remote status types + aggregated together, and suffixed histograms for the results of just that + particular remote status type. + + See + MultiDevice.SecureChannel.BLE.Performance.StartScanToAuthenticationDuration.Background + and + SmartLock.Performance.AuthenticationToReceiveFirstRemoteStatus.Unlock.Duration + for breakdowns of this metric. + + See SmartLock.GetRemoteStatus.Unlock for the success rate of fetching the + remote status from the host. + + + + + jhawkins@chromium.org + better-together-dev@google.com + + The number of times the user actively enabled or disabled the SmartLock + feature via Settings. + + + + + jhawkins@chromium.org + better-together-dev@google.com + The result of the operation to disable SmartLock. + + + + + diff --git a/tools/metrics/histograms/histograms_xml/software/histograms.xml b/tools/metrics/histograms/histograms_xml/software/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..24e2f4b8f1d45dca5a109e7a1d359e4713111d26 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/software/histograms.xml @@ -0,0 +1,389 @@ + + + + + + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Keeps a tally of IPC related errors between chrome_cleaner and chrome. The + first two bytes of the bucket represent the error category and the two last + bytes represent the actual error code. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time between sending the user's response to the Chrome Cleaner process + and the Cleaner process terminating. This histogram is logged only for + successfully completed runs of the cleaner. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The final status of the Chrome Cleanup Tool run (e.g. succeeded, failed, + reboot required). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + An indication if an attempt to download the Chrome Cleanup Tool succeeded or + the reason why it failed. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The HTTP response or net error code when trying to download the Chrome + Cleanup Tool. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether a reboot happened since the software reporter cleaner tool has + finished execution with a pre-reboot exit code. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates that the user accepted to initiate a reboot to complete a run of + the Chrome Cleanup Tool. This is logged the user starts a reboot from the + cleanup card in the Settings page. We can't track when the reboot is not + initiated, because it can happen at any moment in the future (there is no + prompt blocking the user). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + How long it took to run the software reporter cleaner tool. + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time between launching the Chrome Cleaner process and the cleaner having + scanned the user's machine and Chrome receiving an IPC call with the + results. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates if the Settings page was the active tab once a cleanup finished + with reboot required. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The time between the first attempt to download the Chrome Cleanup tool and a + successful download or the last unsuccessful attempt to download without + retrying. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the user accepted to upload logs from Chrome Cleanup Tool. This is + logged when the user accepts the Chrome prompt to start a cleanup either + from the prompt dialog or from the cleanup card in the Settings page. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the Chrome Cleanup Tool card in the Settings page has been shown. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates where the user started a cleanup from (e.g. from the prompt dialog + or the settings page). + + + + + bdea@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether a configuration error prevented the experimental Software Reporter + from running. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether there was an error reading the registry key containing UwS found by + the Software Removal Tool. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates when the IPC with the Chrome Cleanup Tool process is disconnected + from Chrome. Success is logged when it's disconnected and no longer needed + (the user already responded to the prompt in Chrome or the cleaner process + terminated normally); failures are logged when the IPC is disconnected, but + communication between Chrome and the cleaner process is still required (e.g. + while Chrome is waiting for scanning results or when the cleaner is waiting + for the user's response from Chrome). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + The result of the most recent SRT log upload. + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + If logs uploads are enabled in the Software Reporter or the reason why it is + disabled. Recorded before each run of the Software Reporter. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The result of the most recent Software Reporter logs upload. Written by the + Software Reporter in the registry and sent by Chrome after the reporter + finishes. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Error encountered when reading the software reporter logs upload result from + the registry. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + As SoftwareReporter.MinorVersion, but a double word combination of the other + components of the version of the software reporter. The high word is the + first component when there are more than one, and the low word is either the + second or third one, depending if there are at least 3, or 4 components. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The memory used by the software reporter tool as reported by the tool itself + via the registry. Logged just after the software reporter tool has finished. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The last component of the version of the software reporter that was executed + so we can identify when users are not getting their component updated as + quickly as we expect it. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The reason why the user has not been prompted to run the Chrome Cleanup Tool + (e.g. no unwanted software found, user recently prompted). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of files to be deleted by the Chrome Cleanup Tool. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether an on-demand update of the Software Reporter component was needed + for a user-initiated cleanup. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether an on-demand update of the Software Reporter component succeeded, + when needed for a user-initiated cleanup. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The number of profiles whose settings will be reset once a successful + cleanup completes. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The user response on the modal Chrome Cleanup Tool prompt dialog (e.g. + accepted, cancelled). + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the user has been prompted to run the Chrome Cleanup Tool and which + type of prompt has been shown. + + This is logged once a prompt is presented to the user. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Indicates the type of a reporter sequence run on the user system. Logged + when the sequence is scheduled to start. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + The amount of time it took for the software reporter to run as measured by + chrome. Logged just after the software reporter tool has finished. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Whether the user accepted to upload scanner logs from Chrome Cleanup Tool. + This is logged when the user starts a scan for the Settings page and is only + logged for user-initiated cleanups. + + + + + drubery@chromium.org + chrome-safebrowsing-alerts@google.com + + Registers when a profile is tagged for settings reset before a run of the + Chrome Cleanup Tool. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/stability/histograms.xml b/tools/metrics/histograms/histograms_xml/stability/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9431c26578cfa3a3f1deefa4bbbcf0261bc5ae6d --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/stability/histograms.xml @@ -0,0 +1,467 @@ + + + + + + + + + + boliu@chromium.org + ssid@chromium.org + + Records the reverse rank of a child process when it is killed by android if + applicable. Chrome on Android ranks some child processes and provides hints + to android that it should kill from lowest to highest ranked. The lowest + ranked process has reverse rank 0. This is a measure how good the hints to + android are; if hints were perfect, then all android kills should have + reverse rank 0. + + + + + boliu@chromium.org + ssid@chromium.org + + Getting value for OomKillReverseRank may fail. Recorded when an applicable + child process is killed by android. + + + + + boliu@chromium.org + + Individual enum counts specific conditions of child process terminations. + There are too many individual states to enumerate into a single histogram, + so this effectively does the aggregration that normally happens on the + server side in the client instead. The benefit is this is easily extensible + in the future, and downside is that it does not allow additional server side + analysis. Note a single child process termination may fall into multiple + enums. + + + + + mheikal@chromium.org + smaier@chromium.org + wnwen@chromium.org + + Records the number of non-simulated minidumps processed by Crashpad, split + by process type. This metric is similar to one that could be computed + server-side based on received crash uploads; but the client-side metric also + includes any minidumps that were not successfully uploaded. + + + + + mheikal@chromium.org + smaier@chromium.org + wnwen@chromium.org + + Records the number of simulated minidumps processed by Crashpad, split by + process type. This metric is similar to one that could be computed + server-side based on received crash uploads; but the client-side metric also + includes any minidumps that were not successfully uploaded. + + + + + wnwen@chromium.org + + Counts renderer crashes including OOMs. Android only. Mirrors old stability + proto renderer crashes. + + + + + boliu@chromium.org + ssid@chromium.org + + Record the state of child service bindings left when a child service with + strong binding is OOM killed by Android. Recorded when such a OOM kill is + detected by browser. Note this does not distinguish process type, and is for + example recorded for both GPU and renderer process. + + + + + boliu@chromium.org + ssid@chromium.org + + Record the count of strongly bound child services left when a child service + with strong binding is OOM killed by Android. Recorded when such a OOM kill + is detected by browser. Note this does not distinguish process type, and is + for example count both GPU and renderer process. + + + + + creis@chromium.org + jamescook@chromium.org + + Count of processes killed by chrome/browser because they sent an IPC that + couldn't be properly handled. Categories are the reasons (code locations) + for the kills. + + + + + jam@chromium.org + jamescook@chromium.org + + Count of child processes killed because they sent an IPC that couldn't be + properly handled. Categories are the reasons (code locations) for the kills. + + + + + jamescook@chromium.org + + Count of extension processes killed because they sent an IPC that couldn't + be properly handled. Categories are the reasons (code locations) for the + kills. + + + + + mcnee@chromium.org + + Count of processes killed because they sent a bad IPC that couldn't be + properly handled. Categories are the reasons (code locations) for the kills. + + + + + creis@chromium.org + jamescook@chromium.org + + Count of processes killed because they sent a NaCl IPC that couldn't be + properly handled. Categories are the reasons (code locations) for the kills. + + + + + creis@chromium.org + jamescook@chromium.org + + Count of processes killed because they sent a bad IPC that couldn't be + properly handled. Categories are the reasons (code locations) for the kills. + + + + + + + siggi@chromium.org + chrome-stability-core@google.com + + Records the exit code of the browser process (on Windows) from the previous + launch. On crash, the exit code will indicate the exception code of the + crash. This is emitted in stability data with the first report on a + subsequent launch. Note: Due to https://crbug.com/805754, the enum labels + for RESULT_CODE_* are off by 1 for M56 and earlier. + + + + + alexmos@chromium.org + boliu@chromium.org + lukasza@chromium.org + + Logs the reason that a crashed subframe was shown. Logged at most once per + crash, and only if the subframe was hidden when it crashed and became + visible later. + + + + + alexmos@chromium.org + boliu@chromium.org + + Logs whether or not a tab is marked for reload when a cross-process subframe + crashes. Logged once per subframe process crash. + + + + + alexmos@chromium.org + boliu@chromium.org + + Logs the visibility of a subframe when a subframe process crashes and the + corresponding tab is marked for reload. This indicates whether the crashed + subframe was visible or scrolled out of view at the time of crash. + + + + + alexmos@chromium.org + boliu@chromium.org + lfg@chromium.org + lukasza@chromium.org + + Logged after detecting that a sad subframe is shown (logged at most once per + crash). + + + + + siggi@chromium.org + + Temporary instrumentation to record the Windows browser's exit path. See + http://crbug.com/412384. + + + + + rkaplow@chromium.org + chrome-metrics-team@google.com + + Collects various counters related to stability. The majority of them are + crash types. + + + + + siggi@chromium.org + + Number of times stability data was discarded. This is accumulated since the + last report, even across versions. This is logged during stability metric + recording for the following log sent. + + + + + michaelbai@chromium.org + src/base/metrics/OWNERS + + The number of the unsent files at the time the stability recorded. + + + + + michaelbai@chromium.org + src/base/metrics/OWNERS + + The total number of samples that will be lost if ASSOCIATE_INTERNAL_PROFILE + isn't enabled since the previous stability recorded. This is different than + the previous browser run because one file was just uploaded before the + stability is recorded. + + + + + siggi@chromium.org + + Number of times the initial stability log upload was deferred to the next + startup. This is logged during stability metric recording for the following + log sent. + + + + + siggi@chromium.org + + Number of times a browser crash was detected, where the browser was last + known to be alive in a Windows system session that terminated abnormally. + + + + + siggi@chromium.org + + Number of times the version number stored in prefs did not match the + serialized system profile version number. This is logged during stability + metric recording. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + Number of kilobytes available for "important" data. When an iOS + device is critically low on space, actions generally assumed to succeed can + fail. In extreme cases, this could potentially include writing the + "unclean shutdown" bit to signal a clean shutdown. Logged on + application launch if the last session terminated in an unclean state. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + The last known battery charge before a crash occurred. This will only be + logged for devices which were last known to be in the "unplugged" + state because the intention is to identify devices which may have died + leading to unexpected terminations. Logged on application launch if the last + session terminated in an unclean state. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + The thermal state of the device when a crash occured. Logged on application + launch if the last session terminated in an unclean state. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + Indicates whether or not one of the Stability.iOS.UTE.* metrics could + explain the cause of the UTE which terminated the previous session. Logged + on application launch if the last session terminated in an unclean state. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + The power mode of the device when a crash occurred. Logged on application + launch if the last session terminated in an unclean state. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + Recorded when app starts after Unexplained Termination Event (UTE) or + Explained Termination Event (XTE). Values other than Active indicate that + prefs::kLastSessionExitedCleanly was not properly stored. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + sdefresne@chromium.org + + Recorded when app starts after Unexplained Termination Event (UTE) or + Explained Termination Event (XTE). UTEs/XTEs can be caused by large memory + allocations and this histogram provides information which memory heavy + operation has being performed before UTE/XTE. + + + + + eugenebut@chromium.org + michaeldo@chromium.org + + true if OS was restarted after the previous session. Logged on application + launch if the last session terminated in an unclean state. If this is false + then UTE was not caused by OS restart or shutdown. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + Logged on the session following a crash with the result of a comparison + between the OS version of the session which crashed and the current OS + version. Logged on application launch if the last session terminated in an + unclean state. + + + + + michaeldo@chromium.org + olivierrobin@chromium.org + + The estimated amount of time between when a crash occurred and when the user + relaunched the application. Logged on application launch if the last session + terminated in an unclean state. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + Type of the shutdown. This histogram is recorded at startup and logs a + sample for the previous session. A clean shutdown is one where the app + enters the background before being killed. Other shutdowns are all some sort + of crash. The absence of a crash log indicates that the app was killed by + the OS, normally due to memory pressure. If memory pressure is extremely + high, the app may not have had a chance to response to a memory warning + before being killed. For first launch after upgrade, the crash reports may + be discarded before this histogram is written to so it's not possible to + determine if there's a valid crash log present or not. + + + + + dtapuska@chromium.org + + If the renderer is considered unresponsive from the browser's perspective + before the process is terminated. This metric is being used to figure out + crash reports that have all idle threads and perhaps the process is being + terminated when it shouldn't be. crbug.com/615090. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/startup/histograms.xml b/tools/metrics/histograms/histograms_xml/startup/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9a4c67ff2796d75dc86401355f4ef1739e59389b --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/startup/histograms.xml @@ -0,0 +1,681 @@ + + + + + + + + + + michaeln@chromium.org + + The number of after-startup tasks that were queued prior to startup + completion and deferred until that time. + + + + + michaeln@chromium.org + + Time from the process creation until deferred after-startup tasks began + running. + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records whether or not the cached Feed visibility in the SharedPreferences + is consistent with the Feed visibility user preference on the disk. It's + recorded when overview mode is shown because of Return to Tab Switcher, and + only on cold start. By recording this histogram, the number of mismatches + between the criteria of whether the Feed placeholder of Instant Start + pre-native is shown and the criteria of whether Feed articles after native + initialization are shown is recorded. + + + + + pasko@chromium.org + alexilin@chromium.org + + Android: The time from the activity creation point to the first contentful + paint of the first loaded page. It's not recorded when the first loaded page + is non http(s) page like a chrome error page, a new tab page, a blank page. + It's also not recorded if the application wasn't in the foreground since the + start till the end of event. + + + + + pasko@chromium.org + alexilin@chromium.org + + Android: The time from the activity creation point to the moment the first + navigation is committed, i.e. when renderer gets the first byte of the + document. It's not recorded when the first loaded page is non http(s) page + like a chrome error page, a new tab page, a blank page. It's also not + recorded if the application wasn't in the foreground since the start till + the end of event. + + + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records the time duration from a cold start till the Feeds articles are + first loaded on the StartSurface. This histogram is only recorded when + StartSurface is shown at launch due to "return to tab switcher" + feature. + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records the time duration from a cold start till the Feeds loading + placeholder is shown on the StartSurface. This placeholder is only shown + when the feature flag InstantStart is enabled and StartSurface is shown at + launch due to "return to tab switcher" feature. + + + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records the time duration from a cold start till the Feeds stream is created + on the StartSurface. This histogram is only recorded when StartSurface is + shown at launch due to "return to tab switcher" feature. + + + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records the time duration from a cold start till the first draw completes. + + + + + mthiesse@chromium.org + yfriedman@chromium.org + + Measures the amount of time startup has likely been delayed due to GURL + waiting on the native library to be initialized. + + + + + + + hanxi@chromium.org + spdonghao@chromium.org + wychen@chromium.org + + Records the time duration from a cold start till the title of the single Tab + is shown on the StartSurface. This histogram is only recorded when + StartSurface is shown at launch due to "return to tab switcher" + feature. + + + + + skyostil@chromium.org + + Android: Whether or not creation of a profile lead to the + StartupTabPreloader speculatively created a tab. Recorded when a profile is + created, assuming a StartupTabPreloader has been constructed for intents + with a url and either regular Chrome or a Custom Tab will be loaded. + + + + + skyostil@chromium.org + + Android: Whether or not a tab speculatively created by the + StartupTabPreloader was subsequently adopted by ChromeTabCreator. Recorded + when a tab is loaded, assuming a StartupTabPreloader has been constructed + for intents with a url for either regular Chrome or a Custom Tab will be + loaded. + + + + + yusufo@chromium.org + yfriedman@chromium.org + + Android: The number of thumbnails fetched for the first meaningful paint of + the Grid Tab Switcher. First meaningful paint is defined as having all the + thumbnails shown. This is recorded at most once per activity lifecycle. This + is gated by feature "TabSwitcherOnReturn". + + + + + yusufo@chromium.org + yfriedman@chromium.org + + Android: The elapsed time from the activity creation point to the first + meaningful paint of the Grid Tab Switcher. First meaningful paint is defined + as having all the thumbnails shown. This is recorded at most once per + activity lifecycle. This is gated by feature + "TabSwitcherOnReturn". + + + + + yusufo@chromium.org + yfriedman@chromium.org + + Android: The elapsed time from the activity creation point to the first + meaningful paint of the Grid Tab Switcher. First meaningful paint is defined + as having all the thumbnails shown. This is recorded at most once per + activity lifecycle. This is gated by feature + "TabSwitcherOnReturn". It's only recorded on cold startup. + + + + + yusufo@chromium.org + yfriedman@chromium.org + + Android: The elapsed time from the activity creation point to the first + meaningful paint of the Grid Tab Switcher. First meaningful paint is defined + as having all the thumbnails shown. This is recorded at most once per + activity lifecycle. This is gated by feature + "TabSwitcherOnReturn". It's only recorded on warm startup. + + + + + mark@chromium.org + crashpad-dev@chromium.org + + The amount of time that elapsed during in + crash_report::BlockUntilHandlerStarted(). + + + + + peter@chromium.org + + Records the cause, each time Chrome is brought to the foreground. Currently + only checks if a NotificationUIManager notification was shown in the last 5 + seconds (includes Web Notifications, but not media or Cast). + + + + + robliao@chromium.org + + The amount of time that elapsed during BrowserMainRunnerImpl::Initialize. + + + + + robliao@chromium.org + + The amount of time that elapsed during the first section of + BrowserMainRunnerImpl::Initialize. + + + + + robliao@chromium.org + + The amount of time that elapsed during the second section of + BrowserMainRunnerImpl::Initialize. + + + + + asvitkine@chromium.org + + Time between Startup.BrowserMessageLoopStartTime and + Startup.FirstWebContents.NonEmptyPaint2. Recorded explicitly to allow easy + breakdown of Startup.FirstWebContents.NonEmptyPaint2 when diagnosing issues. + + + + + + + chrisha@chromium.org + fdoray@chromium.org + + The number of hard faults incurred in the browser process from startup to + start of the main thread's message loop, not including first runs of the + browser. + + + + + + + fdoray@chromium.org + gab@chromium.org + + Time from application start to the start of the main thread's message loop. + Not recorded for first run. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + + + fdoray@chromium.org + gab@chromium.org + + Time from application start to the start of the main thread's message loop. + Recorded for a first run of the browser. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + rkaplow@chromium.org + + The amount of time that elapsed during + BrowserProcessImpl::PreMainMessageLoopRun. + + + + + sebmarchand@chromium.org + mblsha@yandex-team.ru + + Time from application start to the time the first Browser window has + finished painting its children. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + sebmarchand@chromium.org + mblsha@yandex-team.ru + + Time from application start to the time the GPU has finished compositing + after first Browser window has finished painting its children. At this point + the Browser interface is visible on screen. Measures how much time does it + take for GPU to actually paint the first time. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + + + fdoray@chromium.org + gab@chromium.org + + Time from application start to the time the browser window initially becomes + visible. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + djean@chromium.org + eugenebut@chromium.org + + The duration of all initializations from process creation time to UI ready. + This includes code loading, static initializers and the execution time + contained in Startup.ColdStartWithExternalURLTime and + Startup.ColdStartWithoutExternalURLTime metrics. iOS specific. + + + + + jif@chromium.org + + The duration of all initializations in a cold start triggered by an external + URL. + + + + + jif@chromium.org + + The duration of all initializations in a cold start not triggered by an + external URL. + + + + + + + fdoray@chromium.org + gab@chromium.org + + How long it takes to load the original profile synchronously on the UI + thread. + + + + + + + fdoray@chromium.org + gab@chromium.org + + [Desktop] The reason for which startup profiling was deemed complete. Logged + once per session on startup. + + + + + + + fdoray@chromium.org + gab@chromium.org + + [Desktop] Measure the elapsed time from application start to the moment when + the navigation is committed (first bytes received) in the first web + contents' main frame. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + + + fdoray@chromium.org + gab@chromium.org + + [Desktop] Measure the elapsed time from application start to the beginning + of navigation in the first web contents' main frame. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + + + etiennep@chromium.org + fdoray@chromium.org + gab@chromium.org + chrome-analysis-team@google.com + + Measure the elapsed time from the application start to the first non empty + paint of the first web contents. Only comprised of cases where the initial + foreground tab gets to complete its rendering task unimpeded (an improvement + over Startup.FirstWebContents.NonEmptyPaint). + + Application start is a time recorded as early as possible in the startup + process. On Android, the application start is the time at which the Java + code starts. On Windows, application start is when chrome.exe:main starts, + before chrome.dll is loaded. On other platforms, it is when + ChromeMainDelegate is constructed. + + + + + hans@chromium.org + + Time between RenderFrameHostImpl::Init and + Startup.FirstWebContents.NonEmptyPaint2. + + + + + + + fdoray@chromium.org + etiennep@chromium.org + gab@chromium.org + + Time from the application start to the C++ ChromeMain() function being + invoked. + + + + + + + fdoray@chromium.org + etiennep@chromium.org + gab@chromium.org + + Time from the process creation to application start, i.e. time recorded as + early as possible in the startup process. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The action requested on the application startup when called from another app + or the OS. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + The calling application (if any). + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + -[AppControllerMac awakeFromNib]. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + -[AppControllerMac didFinishLaunching:]. At that point, the dock icon will + finish its current animation and stop bouncing. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + ChromeBrowserMainPartsMac::PostMainMessageLoopStart. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + ChromeBrowserMainPartsMac::PostProfileInit. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + ChromeBrowserMainPartsMac::PreMainMessageLoopStart. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + ChromeBrowserMainPartsMac::PreProfileInit. + + + + + erikchen@chromium.org + + The amount of time that elapsed between main entry and the invocation of + -[AppControllerMac willFinishLaunching:]. + + + + + rkaplow@chromium.org + + The amount of time that elapsed during + ChromeBrowserMainParts::PreMainMessageLoopRunImpl. + + + + + rkaplow@chromium.org + + The amount of time that elapsed during StartupBrowserCreator::Start(). + + + + + + + chrisha@chromium.org + fdoray@chromium.org + + Indicates whether or not the given startup was warm, cold or unable to be + determined. This is based off observing the number of hard faults that occur + during startup prior to Startup.BrowserMessageLoopStartTime. The threshold + for cold startup was updated Jan 2020, a bump in the metric is expected. + + + + + pbos@chromium.org + robliao@chromium.org + + Time from application start until the first web footer finishes painting. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + pbos@chromium.org + robliao@chromium.org + + Time from application start until the first WebView used to display a web + footer is created. + + April 8, 2020: Changed the reference from process creation to application + start. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of + application start. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/storage/histograms.xml b/tools/metrics/histograms/histograms_xml/storage/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..13a710a4d389789e495743250587889f42476af1 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/storage/histograms.xml @@ -0,0 +1,403 @@ + + + + + + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + This is recorded for every site that the user blacklists when they when they + clear browsing data. It indicates which signals were used to show the given + site to the user that the user then chose to exclude from clearing. + + + + + mek@chromium.org + dmurph@chromium.org + enne@chromium.org + + Recorded when an error occurs in the BlobUrlLoader, which is used to load + blobs from urls in the Renderer. + + + + + mek@chromium.org + dmurph@chromium.org + + If a newly constructed blob is broken. See Storage.Blob.BrokenReason for a + the broken reasons. + + + + + mek@chromium.org + dmurph@chromium.org + + The reason a blob is broken, reported only for broken blobs upon + construction. See Storage.Blob.Broken for the breakdown of blobs broken vs + unbroken. + + + + + mek@chromium.org + + The result of constructing a blob using the BlobRegistry.RegisterFromStream + API. + + + + + mek@chromium.org + dmurph@chromium.org + + Recorded when the old blob storage directories are cleared. This occurs on + storage partition initialization, and is not recorded if there are no + directories to clear. The value indicates if the file operations were a + success. + + + + + mek@chromium.org + dmurph@chromium.org + + Recorded when an error occurs in the FileReaderLoader, which is used to load + blobs in the Renderer. FileReaderUser is mostly used for Javascript's + 'FileReader', but can also be used to read blobs for the IndexedDB + renderer-side implementation. For the read error category, see + Storage.Blob.FileReaderLoader.ReadError for a breakdown of the specific read + error reasons. + + + + + mek@chromium.org + dmurph@chromium.org + + The error code reported by the blob system while trying to read a blob in + the FileReaderLoader. Compare with the + Storage.Blob.IDBRequestLoader.ReadError histogram to eliminate IndexedDB + large-value blobs. + + + + + mek@chromium.org + + The amount of time taken to complete the synchronous + BlobRegistry.GetBlobFromUUID mojo call. + + + + + mek@chromium.org + dmurph@chromium.org + + The error code reported by the blob system while trying to read an IndexedDB + large-value blob in the IDBRequestLoader. These blobs are automatically + created in Blink when a website writes a large value to IndexedDB. + + + + + mek@chromium.org + dmurph@chromium.org + + Counts the number of times we have an invalid refcount operation. An invalid + increment means the blob didn't exist, and an invalid decrement means we + don't have any record of the blob in our host. + + + + + mek@chromium.org + dmurph@chromium.org + + Counts the number of times we have an invalid url registration operation. An + invalid increment means the blob isn't in use by the host yet or the url is + already mapped. An invalid decrement means the url isn't registered. + + + + + mek@chromium.org + dmurph@chromium.org + + Records the calculated max disk space the blob storage system can use. + Recorded on storage partition initialization, and only if the disk is + enabled. + + + + + mek@chromium.org + dmurph@chromium.org + + Recorded when the blob system changes adjustment types on its disk size. The + disk can either be Frozen, Adjusted (near min external available disk + space), or Normal. We record when we transition between these states, which + can happen after any file operations in the blob system (paging data to disk + or saving a new blob directly to disk). + + + + + mek@chromium.org + dmurph@chromium.org + + Size of a page file created for blob data by the blob storage system. + Recorded before we create the file and write the blob items. We page blob + data to files when we get close to our maximum blob memory usage. + + + + + mek@chromium.org + dmurph@chromium.org + + Recorded when we disable paging blobs to file in the blob storage system. + This occurs when we experience a filesystem error during writing blob data + to disk. We write blob data to files when either we have a new blob that's + larger than our memory limit, or we're approaching our in-memory limit for + blob storage. The relevant error is recorded here. + + + + + mek@chromium.org + dmurph@chromium.org + + The amount of time taken to complete the synchronous mojo call + BlobRegistry.Regsiter + + + + + mek@chromium.org + dmurph@chromium.org + + The amount of time taken to complete the synchronous mojo call + BlobURLStore.Register IPC. + + + + + mek@chromium.org + dmurph@chromium.org + + Whether seeking within a file (in order to write a part of a blob) failed in + the renderer. + + + + + mek@chromium.org + dmurph@chromium.org + + Whether writing part of a blob to a file failed in the renderer. + + + + + mek@chromium.org + dmurph@chromium.org + + True if we reuse an item for a blob created from using Blob.slice, recorded + in BlobStorageContext on blob creation. + + + + + ssid@chromium.org + mek@chromium.org + Records the total size of in-memory blobs evicted to disk. + + + + mek@chromium.org + dmurph@chromium.org + + The total in-memory size in KB of finished blobs. Recorded in + BlobStorageContext when the blob is finished being created. This can include + memory that is shared with other blobs or memory from repeated internal + items. + + + + + mek@chromium.org + dmurph@chromium.org + + The total amount of unique memory used to create a blob. Recorded in + BlobStorageContext when the blob is finished being created. This does not + include memory that is shared with other blobs. If multiple of the same blob + item is present, then this number will reflect the size of the single item. + + + + + mek@chromium.org + dmurph@chromium.org + + True if the file size on blob append is unknown (which means the full file), + or false if a specific file length was populated. Recorded in + BlobStorageContext when we are adding a file item to a blob. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + When a user chooses to blacklist one or more sites when they clear browsing + data, this is recorded for every reason each chosen site was marked as + important. It indicates which signals were used to show the given site to + the user that the user then chose to exclude from clearing. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + This records the number of reasons each important site had that the user + chose to blacklist when clearing browsing data. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + When a user chooses to blacklist one or more sites when they clear browsing + data, this is recorded for every reason each unchosen site was marked as + important. It indicates which signals were used to show the given site to + the user, which the user then ignored and did not select to blacklist from + clearing data. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + This records the number of reasons each important site had that the user + chose to NOT blacklist when clearing browsing data. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + Recorded when we generate a list of important sites. This can happen when + the user opens the Clear Browsing Data dialog on Android, views the Storage + tab in Site Settings on Android, or launches 'Manage Storage' from Android + System Settings for Chrome. We record every reason each site was chosen in + this metric. This means that we can report this metric multiple times for a + single site. + + + + + dmurph@chromium.org + chrome-owp-storage@google.com + + This records the number of reasons qualifying a site for being 'important'. + We record this for every site when we generate a list of important sites, + described in "Storage.ImportantSites.GeneratedReason". + + + + + dmurph@chromium.org + pwnall@chromium.org + + The time it takes to generate the list of 'important' sites. This list is + generated when the user enters the 'Clear Browsing Dialog' or the 'Manage + Space' screens for Chrome, both of which are on Android. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the size of a blob used in an IndexedDB add/put operation. Recorded + for every put operation that contains a blob. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records if a blob intended to be used in an IndexedDB add/put operation is a + valid blob. Recorded for every put operation that contains a blob. + + + + + jarrydg@chromium.org + chrome-owp-storage@google.com + + How did the user interact with the StoragePressure Bubble? Ignored means the + user did not click on the positive button before the bubble is closed + (either manually closed or when the browser closes). + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/subresource/histograms.xml b/tools/metrics/histograms/histograms_xml/subresource/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..daf85da012d79c65e2534ca2eaaea7995bdf1366 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/subresource/histograms.xml @@ -0,0 +1,513 @@ + + + + + + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Counts of various UI and user action events related to the + SubresourceFilter. This will be triggered when portions of the UI are shown + or interacted with. + + + + + pkalinnikov@chromium.org + + Records how much thread CPU time it takes to decide whether subresource + filtering should be activated for a main frame or subframe. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + pkalinnikov@chromium.org + + Records how long it takes to decide whether subresource filtering should be + activated for a main frame or subframe. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + engedy@chromium.org + + Whenever a document load is committed in a main frame or subframe, records + whether subresource filtering should be activated for that load. + + + + + engedy@chromium.org + + Whenever a document load is committed in a main frame or subframe and + subresource filtering should be activated, records whether the filtering + rules are available. + + + + + csharrison@chromium.org + + Records the total time a subframe navigation was delayed while calculating + whether it should be disallowed or not. Logged for all navigations that were + allowed. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + csharrison@chromium.org + justinmiron@google.com + + Records the total time a subframe navigation was delayed while calculating + whether it should be disallowed or not. Logged for all navigations with the + disallowed load policy. + + + + + csharrison@chromium.org + justinmiron@google.com + + Records the total time a subframe navigation was delayed while calculating + whether it should be disallowed or not. Logged for all navigations with the + would_disallow load policy. + + + + + pkalinnikov@chromium.org + + The total CPU time it took to parse and index all rules. Does not include + time when the indexing thread was not doing actual work, e.g. waiting for + I/O or being descheduled. Recorded every time the RulesetService kicks off a + ruleset indexing process. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + The number of rules that could be not be successfully indexed and therefore + have been ignored. Recorded every time the RulesetService kicks off a + ruleset indexing process and it reaches the point where rules are getting + indexed. + + + + + ericrobinson@chromium.org + csharrison@chromium.org + + The result of the IndexRulesetMatcher Verify method. Either pass if both the + checksum and verifier succeeded, or a value indicating which combination of + them failed. Note that a zero checksum indicates that the checksum has not + yet been stored during indexing (for rulesets indexed prior to the + checksumming code). + + + + + csharrison@chromium.org + + The total time it took to verify the indexed ruleset in the browser process. + Logged every time verification occurs, which usually occurs when the first + page with activation is navigated to. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + The total time it took to read and index all rules. Includes I/O time for + reading the unindexed rules, but not for writing the indexed ruleset. + Recorded every time the RulesetService kicks off a ruleset indexing process. + + + + + alexmt@chromium.org + jkarlin@chromium.org + + Whenever a document load is committed in the main frame, records whether the + filtering rules are available. This is independent of whether or not + subresource filtering should be activated. + + + + + csharrison@chromium.org + + Records how much thread CPU time it takes to decide whether subresource + filtering should be activated for a main frame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ericrobinson@chromium.org + csharrison@chromium.org + + For pages that match a given subresource_filter activation list, records the + position in the redirect chain of the latest non-NONE list. + + + + + csharrison@chromium.org + + Records how long it takes to decide whether subresource filtering should be + activated for a main frame. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Records the policy decision to activate subresource filtering for a page + load. 'Activated' indicates that subresource filtering was activated. All + other reasons indicate that subresource filtering was not activated. + + + + + csharrison@chromium.org + + The ActivationList or NONE that the main frame navigation matched with. + Recorded at WillProcessResponse time for a main frame navigation. + + + + + csharrison@chromium.org + + Whenever a document load is committed in a main frame, records whether + subresource filtering should be activated for that load. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total number of subresource loads that have been disallowed. + This only differs from `MatchedRules` when filtering is performed in dry-run + mode. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total number of subresource loads that have been evaluated. This + only differs from 'Total' when some of subdocuments is subject to a + deactivating rule with DOCUMENT activation type. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total number of subresource loads that have matched filtering + rules. This only differs from `Disallowed` when filtering is performed in + dry-run mode. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total number of subresource loads that have gone through the + subresource filtering pipeline. + + + + + csharrison@chromium.org + + The navigation delay imposed by the subresource filter on a given navigation + due to Safe Browsing checks. + + + + + pkalinnikov@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total thread CPU time spent on evaluating subresource requests, + aggregated across all frames. + + Note: this histogram is emitted for all clients, both ones which have + high-resolution timer available and those which don't. + + + + + pkalinnikov@chromium.org + + Whenever a page load is finished with subresource filtering activated, + records the total real time spent on evaluating subresource requests, + aggregated across all frames. This includes the time spent on waiting or + being descheduled. + + Note: this histogram is emitted for all clients, both ones which have + high-resolution timer available and those which don't. + + + + + yaoxia@chromium.org + + Records the ruleset verification status at some point in a browsing session. + If AdTagging is disabled, this happens when the user first visits a site + that is failing the Better Ads Standard, and gets ads blocked on that site; + if AdTagging is enabled, this happens immediately on startup. Note that this + is recorded only once per browsing session (the lifetime of the browser + process). + + + + + csharrison@chromium.org + ericrobinson@chromium.org + + The time an individual Safe Browsing URL check took before finishing, + including posting tasks to and from the IO thread. Measured on the UI + thread. + + + + + pkalinnikov@chromium.org + + Whenever a subresource of a document is evaluated against the ruleset, + records the thread CPU time spent on calculating whether it should be + allowed to load. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + pkalinnikov@chromium.org + + Whenever a subresource of a document is evaluated against the ruleset, + records how much time was spent on calculating whether it should be allowed + to load. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + csharrison@chromium.org + jkarlin@chromium.org + + Records the exact error whenever writing a ruleset fails at the step where + the ruleset would be moved from the scratch directory to its final location. + + + + + ericrobinson@chromium.org + csharrison@chromium.org + + Whether indexing a version of the ruleset and writing it to disk succeeded, + or failed at a particular step. Recorded every time the RulesetService kicks + off a ruleset indexing process. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records the duration that the subresource redirect feature was stopped due + to fetch failure. When such a redirected fetch times out or fails with 503 + (loadshed failure), subresource redirect is disabled for subsequent + pageloads for a random duration or duration mentioned in the Retry-After + response header. Recorded for each fetch failure. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The server response code of an attempt to compress an image subresource. The + initial redirect to the compression server will always be logged as a + HTTP_TEMPORARY_REDIRECT, in addition to logging the return code from the + compression server. + + + + + robertogden@chromium.org + tbansal@chromium.org + + Whether or not the request to the compression server succeeded at the + network layer. Records true if there was no error at the network layer, + otherwise false. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Recorded whenever the subresource redirect times out, and leads to a random + bypass of 1-5 minutes. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The bytes of data saved from the SubresourceRedirect. Recorded every time a + SubresourceRedirect returns with a 200 HTTP response code. + + + + + robertogden@chromium.org + tbansal@chromium.org + + The percent of data saved from the SubresourceRedirect. Recorded every time + a SubresourceRedirect returns with a 200 HTTP response code. + + + + + rajendrant@chromium.org + src/components/data_reduction_proxy/OWNERS + + Records the user interaction with the HTTPS Image compression notification + InfoBar. Recorded when the one-time InfoBar is shown. + + + + + rajendrant@chromium.org + mcrouse@chromium.org + + Records whether the subresource redirect was bypassed or not for a pageload. + Recorded once per pageload. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/sync/histograms.xml b/tools/metrics/histograms/histograms_xml/sync/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..0d9a0e6e5edbb7abfdc5b7ff348221a281e01250 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/sync/histograms.xml @@ -0,0 +1,1053 @@ + + + + + + + + + + mastiz@chromium.org + treib@chromium.org + + Tracks sync backend initialization time during initial sync setup. + + + + + mastiz@chromium.org + treib@chromium.org + + Tracks sync backend initialization success rate during initial sync setup. + + + + + mastiz@chromium.org + treib@chromium.org + + Tracks sync backend initialization success rate in cases where sync was + previously initialized. + + + + + mastiz@chromium.org + treib@chromium.org + + Tracks sync backend initialization time in cases where sync was previously + initialized. + + + + + mastiz@chromium.org + treib@chromium.org + + Records whether a GUID was found within BookmarkSpecifics, if an + originator_client_item_id of valid GUID format was used to replace it, or if + the field was left empty. Recorded when processing a remote bookmark update, + except for permanent nodes, which are created server-side and don't have an + originator client item ID. + + + + + mamir@chromium.org + mastiz@chromium.org + + Represents whether the proto field client_tag_hash in locally persisted sync + metadata is present and matches the local bookmark's GUID. It's recorded + after successfully loading the metadata (i.e. must not be corrupt). + + + + + mastiz@chromium.org + rushans@google.com + + Records different types of bookmark entities having the same GUIDs. It's + recorded on each found duplicate when processing remote bookmarks from the + sync server during the initial merge. + + + + + mamir@chromium.org + mastiz@chromium.org + + The reason why the persisted metadata for a bookmark model is considered + corrupted. It either has corrupted data or doesn't match the bookmark model. + It's recorded at start up only if the initial sync has been performed + already. It's recorded after loading the metadata. + + + + + rushans@google.com + mastiz@chromiumg.org + + Number of remote bookmarks which don't have full title in specifics. + Recorded when processing an initial merge. + + + + + rushans@google.com + mastiz@chromiumg.org + + Number of remote bookmarks which don't have full title in specifics. + Recorded when processing a remote bookmark update. + + + + + mastiz@chromium.org + treib@chromium.org + + Records the time between the local model being changed until the commit + response is completed and propagated to the model thread. Note: This is only + recorded with a data type suffix. The base version is never recorded. + + + + + + + rushans@google.com + treib@chromium.org + + Emitted per network Commit() request to the sync server and datatype. + Records the outcome of each commit attempt per data type (success or one of + various error codes). + + + + + treib@chromium.org + + Whether the full Sync feature or only the Sync transport layer is being + configured. Recorded when configuring the data types for any reason: Most + commonly during browser startup, but also after initial setup, after a + reconfiguration by the user, or when switching between full feature mode and + transport mode. + + + + + mastiz@chromium.org + treib@chromium.org + + Breakdown of sync data types being configured at first time signin, restart, + or user-initiated reconfiguration. This is different from Sync.CustomTypes + in that this captures all active devices, not just those that are choosing a + custom sync configuration. + + Note that not all platforms support all data types. As such, comparing + across platforms should only look at the common data types. + + + + + mastiz@chromium.org + treib@chromium.org + Count of model association failures for each type. + + + + victorvianna@google.com + jkrcal@chromium.org + + Time spent configuring data types for the first sync. Recorded when + DataTypeManagerImpl finishes. + + + + + victorvianna@google.com + jkrcal@chromium.org + + Time spent configuring data types for a subsequent (i.e. non-first) sync. + Recorded when DataTypeManagerImpl finishes. + + + + + zea@chromium.org + + Whether the gaia cookie jar was empty. Recorded on every SESSIONS commit + where the gaia cookie jar does not include the signed in user ( + CookieJarMatchOnNavigation == false). + + + + + zea@chromium.org + + Whether the gaia cookie jar included the signed in user (matched) or not. + Recorded on every SESSIONS commit. + + + + + vitaliii@chromium.org + treib@chromium.org + + Key derivation method used for sync custom passphrase when a new custom + passphrase is set. "Not set" will never be reported for this + metric, since we always have an explicit key derivation method when a new + passphrase is set. + + + + + vitaliii@chromium.org + treib@chromium.org + + Key derivation method used for sync custom passphrase on successful + decryption of pending keys, i.e. when a passphrase is requested and the user + types in the correct one. "Not set" will never be reported for + this metric, since we always have an explicit key derivation method on + successful decryption. + + + + + vitaliii@chromium.org + treib@chromium.org + + State of the derivation method used for sync custom passphrase on startup. + Reported only when the passphrase type is CUSTOM_PASSPHRASE. + + + + + vitaliii@chromium.org + treib@chromium.org + + Time taken to derive keys in Nigori using a given key derivation method. + This histogram is always recorded with one of the key derivation method + suffixes. + + + + + mastiz@chromium.org + treib@chromium.org + + Breakdown of sync users whose cryptographer has pending keys. + + + + + mastiz@chromium.org + treib@chromium.org + + Breakdown of sync users whose cryptographer is fully ready for encryption + and decryption (initialized and no pending keys). + + + + + mastiz@chromium.org + treib@chromium.org + + Histogram that keeps track of how users encrypt their sync data. All users + start off with default encryption during initial setup, while a subset of + users go on to encrypt their sync data with a custom passphrase. + + + + + treib@chromium.org + mastiz@chromium.org + + For users who have *not* selected the "Sync Everything" option, + this records all the data types they have selected to sync. Samples are + taken every time the Sync data types are (re)configured, which typically + happens during startup and when the user changes any Sync settings. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Histogram of the run failures for the different sync datatypes. These are + failures that occur after startup while the datatype is syncing. This is one + of the base sync health metrics. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Histogram of the startup failures for the different sync datatypes. These + are failures that occur during startup before the data type is fully loaded. + For USS datatypes, these errors are caused by failures in reading metadata + (or data) from the DB or by another failure in interaction with the model. + For Directory datatypes, startup errors are due to missing top level sync + nodes or model association. This is one of the base sync health metrics. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + The largest number of active and concurrently syncing devices known to any + profile. May be 0 when there are no signed in/syncing profiles open. Logged + with every UMA log. + + + + + rushans@google.com + mastiz@chromium.org + + Counts the number of cases when there are duplicate sync entities while + processing remote update. It is introduced to detect cases when one of those + entities (or both) is a tombstone. Recorded for each duplicate entities + within GetUpdates cycle. + + + + + mastiz@chromium.org + melandory@chromium.org + + Recorded for a subset of users (Finch-controlled) per sync reflection, that + is, server-side updates that represent a local change. The time represents + the E2E time from the local change happening, the corresponding invalidation + being received and the relevant updates being fetched from the sync server. + Note: This is only recorded with a data type suffix. The base version is + never recorded. + + + + + mastiz@chromium.org + treib@chromium.org + A UI event occured. + + + + treib@chromium.org + mastiz@chromium.org + + An approximate state of sync at startup. Logs a few reasons sync definitely + wouldn't be able to start, or that it probably can start. The user having + turned off sync on mobile will be logged as "turned off by user". + A dashboard stop and clear will fall under "turned off and setup not + completed". See the SyncInitialState enum in profile_sync_service.cc + for more information. + + + + + + + melandory@chromium.org + + Histogram tracks the number of invalidations received per sync data type. + + + + + mamir@chromium.org + mastiz@chromium.org + rushans@google.com + + Records different causes for BookmarkSpecifics to be deemed invalid. Issues + are recorded upon verifying validity of specifics received from the server. + + + + + mastiz@chromium.org + treib@chromium.org + + The reason for a failure decrypting the keystore decryptor token. + + + + + pastarmovj@chromium.org + + Tracks the number of times the local sync backend was enabled by the user. + + + + + pastarmovj@chromium.org + + Tracks the size of the local sync backend database file. Recorded every time + the roaming profile file is written by the client. + + + + + pastarmovj@chromium.org + + Tracks the types of requests that caused errors inside of the local server. + + + + + pastarmovj@chromium.org + + Tracks the number of times the Roaming profile cannot be retrieved. + + + + + rushans@google.com + mastiz@chromium.org + + Counts cases when data in sync preferences is invalid. Recorded during sync + startup of the Sync transport layer. It happens soon after a signed-in + profile is opened. + + + + + mamir@chromium.org + mastiz@chromium.org + + Recorded after applying the first sync merge for Bookmarks in case of merge + failure. Merge failure is detected by missing one or more permanent nodes in + the merge result. This metric records which permanent nodes are missing. + It's recorded only for USS infrastrucre. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Recorded once per activation of an ephemeral (in-memory) data type; the + value is the duration of the setup (time from the start of the configuration + of sync until the data type receives all its sync data and the data is ready + for the user). This metric is used for monitoring general health of sync + client-side code. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Recorded once per activation of a persistent (on-disk) data type; the value + is the duration of the setup (time from the start of the configuration of + sync until the data type receives all its sync data and the data is ready + for the user). This metric is used for monitoring general health of sync + client-side code. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Counts the number of entries for each model type. For directory types, the + count is based on the directory contents (excl. the root node), for USS + types, the count is based on metadata entries for the type. Recorded after + sync configuration. This metric is used for monitoring general health of + sync client-side code. + + + + + jkrcal@chromium.org + + Recorded once for every sync entity change (whenever it is commited to the + server or updated from the server). This metric is used for monitoring + general health of sync client-side code. Note: This is only recorded with a + data type suffix. The base version is never recorded. + + + + + + + jkrcal@chromium.org + rushans@google.com + + Recorded whenever ClientTagBasedModelTypeProcessor triggers a data type + failure (recorded for both Start and Run failures). It distinguishes call + sites for triggering such failures. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + Estimated memory usage by sync datatype in kilobytes. Recorded after sync + configuration. This metric is used for monitoring general health of sync + client-side code. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Records whenever an orphan metadata is encountered by the + ClientTagBasedModelTypeProcessor. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + Records the model type when a local change is made and sync optimized it + away because nothing actually changed. + + + + + + + qjw@chromium.org + ortuno@chromium.org + treib@chromium.org + mastiz@chromium.org + + Record the LevelDB Status outcome for ModelTypeStore CommitWriteBatch + operations. + + + + + + + jkrcal@chromium.org + rushans@google.com + + Recorded whenever a remote update for a particular data type gets dropped + for the following reason: + + + + + mastiz@chromium.org + melandory@chromium.org + + Freshness of the sync data per received sync entity update, excluding + reflections. The time represents the clock difference from the model being + modified (usually on another device) until the change is processing by this + instance of the browser. The time is capped at 1 week. Beware of potential + clock skew due to two clients being involved. + + + + + treib@chromium.org + mastiz@chromium.org + The active sync passphrase type at sync startup. + + + + + + mmoskvitin@google.com + mastiz@chromium.org + Sync passphrase type collected at each metrics upload. + + + + tschumann@chromium.org + treib@chromium.org + + Number of times the Sync engine got stopped because of an account state + change, e.g. the user signed out of the web. This should only affect the + sync-transport layer, as the sync feature would go into sync-paused state. + (credentials change). The histogram is emitted by minute of the emit-time to + aid with identifying the source of regular traffic spikes. Recorded before + the sync engine gets stopped. + + + + + tschumann@chromium.org + treib@chromium.org + + Number of times the Sync engine got stopped because of changed credentials. + Today this should not happen (but we have plans to use this path for + sync-paused state). The histogram is emitted by minute of the emit-time to + aid with identifying the source of regular traffic spikes. Recorded before + the sync engine gets stopped. + + + + + tschumann@chromium.org + treib@chromium.org + + Number of times the Sync engine got stopped because of a change in the + managed-sync pref (enterprise configuration). The histogram is emitted by + minute of the emit-time to aid with identifying the source of regular + traffic spikes. Recorded before the sync engine gets stopped. + + + + + tschumann@chromium.org + treib@chromium.org + + Number of times the Sync engine got stopped because of an enterprise policy + or the user not being signed in. The histogram is emitted by minute of the + emit-time to aid with identifying the source of regular traffic spikes. + Recorded before the sync engine gets stopped. + + + + + mastiz@chromium.org + mamir@chromium.org + + Emitted when the model type id in the persisted sync metadata mismatches the + model type id expected by the processor. It's recorded upon loading the + metadata and before trying to connect to sync. It's recorded per data type. + + + + + mastiz@chromium.org + + Number of network requests issued by sync to the sync server, grouped by + content type. + + + + + mastiz@chromium.org + + A sync error code received from the sync server as a result of a + client-initiated request. Note that this excludes network errors (e.g. + client offline) and HTTP errors. + + + + + mastiz@chromium.org + + Time taken for a client-initiated request to be sent over the network and + receive the response from the sync server. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + Emitted per network Commit() request to the sync server and datatype. It + helps estimate how much load each datatype puts on the server. Note that the + sum across buckets does not represent the total number of requests sent to + the server, since multiple datatypes can be grouped in a single request. See + Sync.PostedClientToServerMessage for the total number of requests/messages. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + Emitted per network GetUpdates() request to the sync server and datatype. It + represents how much load each datatype puts on the server. Note that the sum + across buckets does not represent the total number of requests sent to the + server, since multiple datatypes can be grouped in a single request. See + Sync.PostedClientToServerMessage for the total number of requests/messages. + + + + + mastiz@chromium.org + jkrcal@chromium.org + + Emitted per network GetUpdates() request to the sync server, it represents + the reason for sending such GetUpdates() request. + + + + + tschumann@chromium.org + treib@chromium.org + + Counts the number of times a syncable pref got registered using a type that + mismatched the type present in the pref store. In these events, the + persisted value gets removed from the pref store. + + + + + mastiz@chromium.org + rushans@google.com + + Records different issues encountered when processing incremental bookmark + updates from the sync server. + + + + + mastiz@chromium.org + rushans@google.com + + Records different issues encountered when processing remote bookmarks from + the sync server during the initial merge procedure. + + + + + melandory@chromium.org + treib@chromium.org + + The sync datatype of the recieved invalidation with not-fresh version. + + + + + mastiz@chromium.org + treib@chromium.org + + For each Chrome window, records the number of tabs present at the time Sync + associates the SESSIONS datatype. + + + + + rushans@google.com + treib@chromium.org + + Counts the number of commit results while committing sharing message. + + + + + mastiz@chromium.org + treib@chromium.org + The type of event that triggered sync initialization. + + + + mastiz@chromium.org + treib@chromium.org + + Time spent after ProfileSyncService *creation* but before SyncEngine + initialization. + + + + + mastiz@chromium.org + treib@chromium.org + Data type that first requests sync initialization. + + + + treib@chromium.org + mastiz@chromium.org + + Tracks how sync was turned off. Logged every time sync is told to stop + permanently by the user (e.g. it won't come back on by itself). + + + + + victorvianna@google.com + jkrcal@chromium.org + + Records the availability status (local, sync or non-available) for favicons + associated with synced history entries. Recorded when one of the following + is displayed: entries in chrome://history that are known to be present in + remote history data; all entries in chrome://history/syncedTabs; tabs from + other devices in the 3 dots history menu (desktop); tabs from other devices + in the android Recent Tabs UI. + + + + + jkrcal@chromium.org + mastiz@chromium.org + + Records the latency of loading favicons associated with synced history + entries. Recorded when one of the following is displayed: entries in + chrome://history that are known to be present in remote history data; all + entries in chrome://history/syncedTabs; tabs from other devices in the 3 + dots history menu (desktop); tabs from other devices in the android Recent + Tabs UI. + + + + + fernandex@chromium.org + chrome-signin-team@google.com + + Enumeration of error conditions that displays an infobar to the user. iOS + only. + + + + + treib@chromium.org + mastiz@chromium.org + + Boolean histogram for whether the "Sync Everything" option was + selected by the user. Samples are taken every time the Sync data types are + (re)configured, which typically happens during startup and when the user + changes any Sync settings. + + + + + mmoskvitin@google.com + mastiz@chromium.org + + Records whether attempt of adding trusted vault keys was successful (i.e. + whether pending keys state resolved). + + + + + mmoskvitin@google.com + mastiz@chromium.org + + Records whether user action was required to fetch trusted vault keys upon + startup. Recorded only if trusted vault passphrase type is used and at most + once per browser/profile lifetime. + + + + + mmoskvitin@google.com + mastiz@chromium.org + + Records number of trusted vault keys fetched upon fetching completion. + + + + + mmoskvitin@google.com + mastiz@chromium.org + Recorded when fetching trusted vault keys is attempted. + + + + mmoskvitin@google.com + mastiz@chromium.org + + Recorded when user clicks/taps on trusted vault error button. Buckets + represents the UI elements which contain trusted vault error button. + + + + + victorvianna@google.com + treib@chromium.org + + This records the number of sync entities that were still undecrypted by the + time the data type was disabled (typically during browser shutdown). + + + + + mastiz@chromium.org + treib@chromium.org + + Counts of responses (both http code and net error code) for Sync URL + fetches. + + + + + mastiz@chromium.org + treib@chromium.org + + Time spent waiting for a sync cycle to complete the url fetch. + + + + + mastiz@chromium.org + treib@chromium.org + + Whether a url fetch timed out or not. Timing out implies the fetch was + stalled for an unknown reason. + + + + + tzik@chromium.org + + Overridden conflict resolution policy of Sync FileSystem API. Recorded for + each API call to override the policy. + + + + + tzik@chromium.org + The result of opening the Sync FileSystem backend database. + + + + tzik@chromium.org + + The number of cached backing remote file metadata in the Sync FileSystem + database. Recorded at the initialization phase of Sync FileSystem. + + + + + tzik@chromium.org + + The number of Chrome Apps that uses Sync FileSystem with V2 backend. + Recorded at the initialization phase of Sync FileSystem. + + + + + tzik@chromium.org + + The result of the registration of Chrome App to Sync FileSystem. + + + + + peria@chromium.org + tzik@chromium.org + + Time elapsed to register a Chrome App to SyncFilesystem. Recorded for each + registration request by apps. + + + + + tzik@chromium.org + The result of opening the Sync FileSystem tracker database. + + + + tzik@chromium.org + + The number of the directory tree node that maps backing files to local files + in the Sync FileSystem database. Recorded at the initialization phase of + SyncFileSystem. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/tab/histograms.xml b/tools/metrics/histograms/histograms_xml/tab/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..e2aee72511ffcae8e40eb6c677371d0610ee9242 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/tab/histograms.xml @@ -0,0 +1,2141 @@ + + + + + + + + + + dtrainor@chromium.org + yfriedman@chromium.org + + [Android] Age (time since the last display in previous sessions) of a tab + being restored due to the first tab switch after the browser cold start, + recorded upon such restore. When the browser is started from cold, this + metric is not recorded for the foreground, automatically restored tab, so + that the metric tracks only the restores triggered by direct user decision + to switch tabs. + + + + + wnwen@chromium.org + [Android] Count of upload success/failures by crash type. + + + + ppi@chromium.org + + Mobile-specific metric: when a tab that was opened in background (via + "Open link in new tab") is switched to, we record whether the + eagerly loaded tab was still memory resident, or we lost the loaded page due + to memory pressure. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Number of open tabs in each guest window. Recorded once a new tab in a guest + window is opened and adds one to the bucket of number of tabs in that + particular window (it does not count the total number of tabs in all open + guest windows). Please note that this metric double counts the lower + numbers, meaning that if user opens three tabs (without closing any in + between), then buckets 1, 2, and 3 will all be incremented in turn. + + + + + rhalavati@chromium.org + chrome-privacy-core@google.com + + Number of open tabs in each incognito window. Recorded once a new tab is + opened in an incognito window and adds one to the bucket of number of tabs + in that particular window (it does not count the total number of tabs in all + open incognito windows). Please note that this metric double counts the + lower numbers, meaning that if user opens three tabs (without closing any in + between), then buckets 1, 2, and 3 will all be incremented in turn. + + + + + mrefaat@chromium.org + bling-team@google.com + + [iOS] Used on External App launcher Prompt to determine if the user clicked + open or cancel. + + + + + pkl@chromium.org + + [iOS] Used on iOS 9+ iPad to report the usage of Compact or Regular + horizontal size class. This is logged at startup and on each size class + change. + + + + + tbergquist@chromium.org + bsep@chromium.org + + Tracks the different ways users are opening new tabs. Does not apply to + opening existing links or searches in a new tab, only to brand new empty + tabs. Note: Currently the "Regular menu option" includes some + programmatic actions in addition to user actions. + + + + + carlosk@chromium.org + harringtond@chromium.org + + The time for the new tab page to load. Only recorded on Android. Recorded + only once per tab, i.e. excluding back/forward navigations. + + + + + pkl@chromium.org + + [iOS] Used on iOS 9+ iPad to report the usage of Compact or Regular + horizontal size class. Recorded on page load. + + + + + marq@chromium.org + [iOS] The orientation of the device. Recorded on page load. + + + + dtrainor@chromium.org + + [Android] The number of page loads since the last switch to an evicted tab + on Android. This was sampled each time an evicted tab was reloaded. + + + + + dtrainor@chromium.org + yfriedman@chromium.org + + [Android] User-perceived load time for a successful tab restore, measured + from the first time the user sees the tab being restored until the load + completes. + + + + + dfried@chromium.org + collinbaker@chromium.org + Records how a tab preview image was generated. + + + + dfried@chromium.org + collinbaker@chromium.org + + When generating a preview for a background tab, this measures the time + between requesting a video capture and receiving the first usable frame. + + + + + dfried@chromium.org + collinbaker@chromium.org + + When generating a preview, a tab's contents are captured as an uncompressed + image, compressed in the background, then sent to subscribers on the main + thread. This roughly measures the time between the capture completing and + the compressed image being available on the main thread. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + dfried@chromium.org + collinbaker@chromium.org + + When generating a preview for a background tab, this measures the time + between receiving a frame and storing it as the current thumbnail. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + dfried@chromium.org + collinbaker@chromium.org + + On tab switch, the visible content area is captured and stored as a + thumbnail. This measures the time between requesting the capture and storing + it as the current thumbnail. + + + + + dfried@chromium.org + collinbaker@chromium.org + + Measures the total time spent in video capture mode when generating a + preview for a background tab. This is emitted at the end of each capture + session. + + + + + gambard@chromium.org + kkhorimoto@chromium.org + + Record the action executed when the user performs a pull down gesture. This + feature is currently iOS only. + +
+ A pull down gesture is an action completed when the user scrolls past the + edge of the web page and continues scrolling in the same direction revealing + a specific UI on the header with multiple actions icons. The user can then + choose an action by scrolling left or right and lift the finger or cancel by + scrolling back up. This is currently an iOS specific feature. +
+ + + + tedchoc@chromium.org + clank-team@google.com + + [Android] The status of a tab and an application when a renderer crashes. + This is recorded only for Android when a renderer crashes. + + + + + wnwen@chromium.org + + [Android] Breakdown of renderer exit status for renderers that have strong + bindings. An extension of the counts in Tab.RendererExitStatus. Only + recorded on Android. + + + + + wnwen@chromium.org + + [Android] Breakdown of renderer exit status for renderers that do not have + strong bindings. An extension of the counts in Tab.RendererExitStatus. Only + recorded on Android. + + + + + wnwen@chromium.org + + [Android] The status of a renderer when the browser notices that the process + has exited. Only recorded on Android. + + + + + pkl@chromium.org + + [iOS] A count of the number of alive renderers when a renderer termination + occurs. + + + + + pkl@chromium.org + + [iOS] The number of renderers which are either currently alive or recently + terminated at the time of a renderer termination. + + + + + pkl@chromium.org + + [iOS] Records whether a memory warning had recently been received before a + renderer termination. + + + + + dtrainor@chromium.org + marq@chromium.org + + [Android and iOS] When the browser restores a tab, whether the load was + successful. Loads can fail for instance when there is no connectivity. + + + + + dtrainor@chromium.org + marq@chromium.org + [Android and iOS] Load time for a successful tab restore. + + + + dtrainor@chromium.org + + [Android] When the browser restores a tab, whether the user waits for + completion of the load or if the user gives up by switching to another tab + or leaving Chrome. + + + + + ramyan@chromium.org + cyflee@chromium.org + + Records actions taken after one or more screenshots of a page were taken. + This will not be recorded if Chromium is killed before leaving the page. If + several types of action (IPH and Sharing) occur, only the last is recorded. + We think that both IPH and Sharing happening at the same time is rare, so we + do not expect to lose much data this way. + + + + + ramyan@chromium.org + cyflee@chromium.org + + Records the number of screenshots taken of a specific page. It is recorded + when the user navigates away from this page or the tab is destroyed. This + will not be recorded if Chromium is killed before leaving the page. + + + + + eugenebut@chromium.org + olivierrobin@chromium.org + + The state (foreground/background) of a tab when its renderer is terminated. + + + + + marq@chromium.org + + [Android and iOS] The status of a tab collected each time the user switches + to it on mobile. That does not include tabs being created at the time the + user switches to them, such as NTP or tabs opened to handle intents. + + + + + dtrainor@chromium.org + + [Android] Age (in ms) when the tab was switched to foreground. + + + + + csharrison@chromium.org + + The position of the URL in the framebust UI list (desktop only) when it is + clicked. Note that this UI surface is shared with the framebusting + intervention, so elements in the list could come from either features. This + metric will only be logged when a URL from the tab under intervention is + clicked. + + + + + csharrison@chromium.org + + Measures the time from when a tab opens a popup to when it performs a + tab-under (i.e. navigates cross origin, in the background without a user + gesture). + + + + + csharrison@chromium.org + + Measures the total time a tab is visible after it navigates itself + cross-origin in the background, without a user gesture. The tab must have + opened a popup since the last user gesture in the tab. Measured at + WebContents destruction. The total visible time for the tab is the sum of + this metric and Tab.TabUnder.VisibleTimeBefore. + + + + + csharrison@chromium.org + + Measures the total time a tab is visible before it navigates itself + cross-origin in the background, without a user gesture. The tab must have + opened a popup since the last user gesture in the tab. Measured at + WebContents destruction. The total visible time for the tab is the sum of + this metric and Tab.TabUnder.VisibleTime. + + + + + csharrison@chromium.org + + Various actions related to the tab under intervention, logged during main + frame navigation. + + + + + tedchoc@chromium.org + clank-team@google.com + + [Android] The total count of tabs which were kept while Chrome process is in + the foreground. This is recorded only for Android right before Chrome + process goes into the background. + + + + + fdoray@chromium.org + + Time spent by a tab in a given visibility state. Recorded when the + visibility changes and when the tab is closed. + + + + + csharrison@chromium.org + + Measures the total time a tab is visible. Measured at the WebContents layer + so this metric does not attempt to account for things like session restore. + Logged at WebContents destruction. + + + + + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The number of tabs groups that are collapsed in all browsers (counting + app-mode windows) when a load completes. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the number of sessions of a selected tab group + whenever Chrome comes to the foreground, or switch tab in the tab switcher. + This number is accumulated until that group id is outdated, meaning all the + tabs with that group id has been closed. + + + + + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The time a tab group spends in the collapsed state before the group is + either expanded or closed. + + + + + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The time a tab group spends in the expanded state before the group is either + collapsed or closed. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The number of tabs groups with a user-set name or color open in all browsers + (counting app-mode windows) when a load completes. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the number of tab groups whenever Chrome comes to the + foreground. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The number of tabs groups open in all browsers (counting app-mode windows) + when a load completes. + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the number of tab groups that have customized group + name whenever Chrome comes to the foreground. + + + + + corising@chromium.org + chrome-desktop-ui-sea@google.com + + This histogram records the number of tab hover cards seen between the last + active tab change and a tab change by mouse click. + + + + + corising@chromium.org + chrome-desktop-ui-sea@google.com + + This histogram records the time between when a hover card was last hidden to + when it is shown again. Since users can easily hover out of the tab strip we + want to reshow the tab hover card with no delay if we think they + unintentionally exited the tab strip. If the user reenters the tab strip + within X ms we want to reshow the hover card immediately. This histogram + will help to better refine that number. + + + + + chrisha@chromium.org + + The loading state of a tab at the time the user switches to it during a + background tab opening session (the duration of time from when the browser + starts to open background tabs until the time the browser has finished + loading those tabs or otherwise decided to stop loading them). The metric is + only recorded when a tab is switched to from another tab within the same + tabstrip. As a result, the case when switching between different windows is + not included, either between two tabs in different browser windows, or when + switching to a different application and switching back to the browser. The + metric is not recorded when the session overlaps with session restore. + + + + + chrisha@chromium.org + + The max number of background tabs pending or loading when opening background + tabs. This is recorded at the end of the background tab opening session (the + duration of time from when the browser starts to open background tabs until + the time the browser has finished loading those tabs or otherwise decided to + stop loading them). The metric is not recorded when the session overlaps + with session restore. + + + + + chrisha@chromium.org + + The number of background tabs whose loading was triggered by TabManager + automatically when opening background tabs. This is recorded at the end of + the background tab opening session (the duration of time from when the + browser starts to open background tabs until the time the browser has + finished loading those tabs or otherwise decided to stop loading them). The + metric is not recorded when the session overlaps with session restore. + + + + + chrisha@chromium.org + + Whether the tab load is timed out during background tab opening session (the + duration of time from when the browser starts to open background tabs until + the time the browser has finished loading those tabs or otherwise decided to + stop loading them). The metric is not recorded when the session overlaps + with session restore. + + + + + chrisha@chromium.org + + The number of background tabs whose loading was triggered by user action + when opening background tabs. For example, when the user selects a + background tab and brings it to foreground, that tab will start to load + immediately if not already loading. This is recorded at the end of the + background tab opening session (the duration of time from when the browser + starts to open background tabs until the time the browser has finished + loading those tabs or otherwise decided to stop loading them). The metric is + not recorded when the session overlaps with session restore. + + + + + chrisha@chromium.org + + The max number of background tabs paused to load due to memory pressure when + opening background tabs. This is recorded at the end of the background tab + opening session during a background tab opening session (the duration of + time from when the browser starts to open background tabs until the time the + browser has finished loading those tabs or otherwise decided to stop loading + them). The metric is not recorded when the session overlaps with session + restore. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Cumulative number of tabs discarded due to low memory conditions, recorded + once per tab discard event. For example, a user who had 3 tabs discarded + records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the number + of sessions where users experienced N or more tab discard events. + + + + + oysteine@chromium.org + + Recorded for each discarding, indicates whether the discarded tab succeeded + in doing a render process fast shutdown or not. + + + + + oysteine@chromium.org + + Recorded for each discarding, allowing us to know whether the discarded tab + succeeded an unsafe process shutdown (not invoking unload handlers). + + + + + georgesak@chromium.org + + Recorded for each discarding, allowing us to know whether the discarded tab + had a before unload handler or not. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Elapsed time between a tab getting discarded to eventually being reloaded by + the user. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Elapsed time between the time a tab switched from being active to inactive + (that eventually gets discarded) until it gets reloaded. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Cumulative number of discarded tabs that have been reloaded by the user, + recorded once per tab discard event. For example, a user who had 3 tabs + reloaded records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is + the number of sessions where users experienced N or more tab reload events. + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Elapsed time between the last time a discarded tab was reloaded and the time + it gets closed. + + + + + chrisha@chromium.org + + The number of pages compressed per second when opening background tabs. This + is recorded at the end of the background tab opening session as an average + over the entire period (the duration of time from when the browser starts to + open background tabs until the time the browser has finished loading those + tabs or otherwise decided to stop loading them). The metric is not recorded + when the session overlaps with session restore. Only recorded on macOS. + Warning: This metric is a ratio and the session interval differs for each + session. It is hard to tell if it is average rate for each second in the + interval or it has a huge spike. + + + + + chrisha@chromium.org + + The number of pages decompressed per second when opening background tabs. + This is recorded at the end of the background tab opening session as an + average over the entire period (the duration of time from when the browser + starts to open background tabs until the time the browser has finished + loading those tabs or otherwise decided to stop loading them). The metric is + not recorded when the session overlaps with session restore. Only recorded + on macOS. Warning: This metric is a ratio and the session interval differs + for each session. It is hard to tell if it is average rate for each second + in the interval or it has a huge spike. + + + + + chrisha@chromium.org + + The number of swap-ins per second when opening background tabs. This is + recorded at the end of the background tab opening session as an average over + the entire period (the duration of time from when the browser starts to open + background tabs until the time the browser has finished loading those tabs + or otherwise decided to stop loading them). The metric is not recorded when + the session overlaps with session restore. Warning: This metric is a ratio + and the session interval differs for each session. It is hard to tell if it + is average rate for each second in the interval or it has a huge spike. + + + + + chrisha@chromium.org + + The number of swap-outs per second when opening background tabs. This is + recorded at the end of the background tab opening session as an average over + the entire period (the duration of time from when the browser starts to open + background tabs until the time the browser has finished loading those tabs + or otherwise decided to stop loading them). The metric is not recorded when + the session overlaps with session restore. Warning: This metric is a ratio + and the session interval differs for each session. It is hard to tell if it + is average rate for each second in the interval or it has a huge spike. + + + + + chrisha@chromium.org + + The tab load time of a tab that is switched to during a background tab + opening session (the duration of time from when the browser starts to open + background tabs until the time the browser has finished loading those tabs + or otherwise decided to stop loading them). Tab load time is defined as the + time between when the user switches to a backround tab, and the time when + that tab finishes loading in the foreground. If the user switches away + before the tab finishes loading, a metric will not be recorded unless the + user switches back, in which case the tab load time is measured from that + point in time. The metric is only recorded when a tab is switched to from + another tab within the same tabstrip. As a result, the initial forground tab + is not included in this metric since it was not switched to from another + tab. The metric is not recorded when the session overlaps with session + restore. + + + + + chrisha@chromium.org + + The number of pages compressed per second during session restore. Recorded + at the end of session restore as an average over the entire period, defined + as the period of time when session restore is actively loading tabs, which + ends when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. The metric is not recorded when the session overlaps with + background tab opening session. Only recorded on macOS. Warning: This metric + is a ratio and the session interval differs for each session. It is hard to + tell if it is average rate for each second in the interval or it has a huge + spike. + + + + + chrisha@chromium.org + + The number of pages decompressed per second during session restore. Recorded + at the end of session restore as an average over the entire period, defined + as the period of time when session restore is actively loading tabs, which + ends when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. The metric is not recorded when the session overlaps with + background tab opening session. Only recorded on macOS. Warning: This metric + is a ratio and the session interval differs for each session. It is hard to + tell if it is average rate for each second in the interval or it has a huge + spike. + + + + + chrisha@chromium.org + + Elapsed time between the start of the loading and the first contentful paint + of foreground tabs when the browser loads tabs in session restore. + + + + + chrisha@chromium.org + + Elapsed time between the start of the loading and the first meaningful paint + of foreground tabs when the browser loads tabs in session restore. + + + + + chrisha@chromium.org + + Elapsed time between the start of the loading and the first paint of + foreground tabs when the browser loads tabs in session restore. + + + + + chrisha@chromium.org + + The number of swap-ins per second during session restore. Recorded at the + end of session restore as an average over the entire period, defined as the + period of time when session restore is actively loading tabs, which ends + when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. The metric is not recorded when the session overlaps with + background tab opening session. Warning: This metric is a ratio and the + session interval differs for each session. It is hard to tell if it is + average rate for each second in the interval or it has a huge spike. + + + + + chrisha@chromium.org + + The number of swap-outs per second during session restore. Recorded at the + end of session restore as an average over the entire period, defined as the + period of time when session restore is actively loading tabs, which ends + when either all tabs have been loaded and their pages rendered, or tab + loading needs to be deferred in cases where the system is under memory + pressure. The metric is not recorded when the session overlaps with + background tab opening session. Warning: This metric is a ratio and the + session interval differs for each session. It is hard to tell if it is + average rate for each second in the interval or it has a huge spike. + + + + + chrisha@chromium.org + + The tab load time of a tab that is switched to during a session restore. Tab + load time is defined as the time between when the user switches to a + backround tab, and the time when that tab finishes loading in the + foreground. If the user switches away before the tab finishes loading, a + metric will not be recorded unless the user switches back, in which case the + tab load time is measured from that point in time. The metric is only + recorded when a tab is switched to from another tab within the same + tabstrip. As a result, the initial forground tab is not included in this + metric since it was not switched to from another tab. The metric is only + recorded when session restore is actively loading tabs, which ends when + either all tabs have been loaded and their pages rendered, or tab loading + needs to be deferred in cases where the system is under memory pressure. The + metric is not recorded when the session overlaps with background tab opening + session. + + + + + chrisha@chromium.org + lpy@chromium.org + + Measures the time duration from when the tab is backgrounded to when its + favicon is updated. The first-time set of favicon will be ignored; this + metric will only be recorded after 5 minutes from main frame navigation + committed and when the tab is in the background. + + + + + chrisha@chromium.org + lpy@chromium.org + + Measures the time duration from when the tab is backgrounded to when a + non-persistent notification is created. Only recorded when the tab is in the + background. + + + + + chrisha@chromium.org + lpy@chromium.org + + Measures the time duration from when the tab is backgrounded to when its + title is updated. The first-time set of title will be ignored; this metric + will only be recorded after 5 minutes from main frame navigation committed + and when the tab is in the background. + + + + + chrisha@chromium.org + + Whether background tab opening session is overlapped with other types of + session, e.g., session restore. Background tab opening session is the + duration of time from when the browser starts to open background tabs until + the time the browser has finished loading those tabs or otherwise decided to + stop loading them. This metric helps to understand how often background tab + opening has overlap with other sessions. + + + + + chrisha@chromium.org + + Whether session restore is overlapped with other types of session, e.g., + background tab opening. Session restore is the duration from the time when + the browser starts to restore tabs until the time when the browser has + finished loading those tabs or when the browser stops loading tabs due to + memory pressure. This metric helps to understand how often session restore + has overlap with other sessions. + + + + + chrisha@chromium.org + + The loading state of a tab at the time the user switched to it during a + session restore. The metric is only recorded when a tab is switched to from + another tab within the same tabstrip. As a result, there are two cases where + tabs are not included. The first case is when the initial forground tab is + shown, since it was not switched to from another tab. The second case is + when switching between different windows, either between two tabs in + different browser windows, or when switching to a different application and + switching back to the browser. The metric is only recorded when session + restore is actively loading tabs, which ends when either all tabs have been + loaded and their pages rendered, or tab loading needs to be deferred in + cases where the system is under memory pressure. The metric is not recorded + when the session overlaps with background tab opening session. + + + + + michaelpg@chromium.org + charleszhao@chromium.org + + Logged when calculating a tab reactivation score for a background tab. Any + value other than "none" may indicate a bug in the inference code, + a problem with the preprocessor configuration shipped with the model, or a + bug in the code that populates the RankerExample for a tab. + + + + + aebacanu@chromium.org + carlscab@chromium.org + sreejakshetty@chromium.org + + Duration between restoring a tab when "Reopen Closed Tab" button + was clicked or any of Ctrl+Shift+T (on Linux/Windows/Chrome OS) and + Command+Shift+T (on Mac) were pressed and the closing of the same tab. + Recorded when the user manually restores a tab. + + + + + aebacanu@chromium.org + carlscab@chromium.org + sreejakshetty@chromium.org + + Duration between restoring a whole window (multiple tabs) when "Reopen + Closed Window" button was clicked or any of Ctrl+Shift+T (on + Linux/Windows/Chrome OS) and Command+Shift+T (on Mac) were pressed and the + closing of the same window. Recorded when the user manually restores a + window. + + + + + sky@chromium.org + + Error code returned by [moveItemAtPath:toPath:error:] when moving previous + session file to backup file before restoring. 0 in case of success. + + + + + sky@chromium.org + + Error code returned by [removeItemAtPath:error:] when removing previous + session backup file. 0 in case of success. + + + + + sky@chromium.org + + Error code returned by [removeItemAtPath:error:] when removing previous + session file. 0 in case of success. + + + + + marq@chromium.org + + [iOS] The number of tabs open when the app comes out of the background. + + + + + marq@chromium.org + [Android and iOS] The number of tabs open at cold launch. + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The tab index from the beginning of the tab strip when switching into a tab. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The tab index from the end of the tab strip when switching into a tab. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The offset between the tab currently selected tab and the newly selected + tab. + +
+ If the user switches to a tab to the left of their currently selected tab, + we log a positive offset value indicating how many tabs to the left they + moved. If the user switches to a tab to the right of their currently + selected tab, we log a negative offset value. +
+ + + + pkotwicz@chromium.org + + Records the "Tab Creation Rank" for the first background tab which + was switched to the foreground. The "Tab Creation Rank" is + relative to other background tabs which were opened from the same URL via + the context menu. The oldest background tab has a rank of zero. + + + + + pkotwicz@chromium.org + + Records the "Reverse Tab Creation Rank" for the first background + background tab which was switched to the foreground. The "Reverse Tab + Creation Rank" is relative to other background tabs which were opened + from the same URL via the context menu. The newest background tab has a + "Reverse Tab Creation Rank" of zero. + + + + + dtrainor@chromium.org + yusufo@chromium.org + + [Android] Age (time since the last display in previous sessions) of the + foreground tab being restored on the browser cold start. + + + + + mattsimmons@chromium.org + memex-team@google.com + The number of entries/cards shown in the grid tab switcher. +
+ When the user is shown the grid tab switcher, logs the number of entries + (tabs or tab groups) open in the grid tab switcher. +
+ + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The maximum number of tabs that Chrome displays at the same time over the + course of a day. Desktop only. + + NOTE: This metric is asynchronous, the value reported on a given day + represents the previous day's observations (which can be from a different + build). + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The maximum number of tabs per window that Chrome displays over the course + of a day. Desktop Only. + + NOTE: This metric is asynchronous, the value reported on a given day + represents the previous day's observations (which can be from a different + build). + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The maximum number of windows existing at the same time over the course of a + day. Desktop only. + + NOTE: This metric is asynchronous, the value reported on a given day + represents the previous day's observations (which can be from a different + build). + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + The number of tabs total at resume from sleep/hibernate. This is being + logged on all desktop platforms. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + CriticalPersistedTabData stores data pertinent to the running of the app + such as tab id, parent id, web contents. This data is serialized and stored + across restarts. This records if the deserialization succeeds or fails. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + CriticalPersistedTabData stores data pertinent to the running of the app + such as tab id, parent id, web contents. This data is serialized and stored + across restarts. This records if the serialization succeeds or fails. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + FilePersistedTabData storage stores serialized PersistedTabData (metadata + persisted across restarts) in a file. This metric records if a delete was + successful or unsuccessful. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + FilePersistedTabData storage stores serialized PersistedTabData (metadata + persisted across restarts) in a file. This metric records if a delete + operation was found to have the file not existing. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + FilePersistedTabData storage stores serialized PersistedTabData (metadata + persisted across restarts) in a file. This metric records if a restore was + successful or unsuccessful. + + + + + yusufo@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + davidjm@chromium.org + + FilePersistedTabData storage stores serialized PersistedTabData (metadata + persisted across restarts) in a file. This metric records if a save was + successful or unsuccessful. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab crashed with "Aw, Snap!", + recorded once per tab crash event. For example, a user who crashed 3 tabs + will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the + number of sessions where users experienced N or more crash events. The user + may not have actually seen the sad tab page, as it might have been an + inactive tab. Compare to Tabs.SadTab.CrashDisplayed. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab crashed with "Aw, Snap!" and the + user saw the page, recorded once per tab crash event. For example, a user + who crashed 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus + each bin N is the number of sessions where users experienced N or more crash + events. Compare to Tabs.SadTab.CrashCreated. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Counts of events from the style of sad tab which has a feedback button as + its primary action. Currently, events include being displayed (actually + visible in a window), and the actions a user can take on the page. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab was killed with a "He's dead, + Jim!" page, which is usually due to the renderer being killed, recorded + once per tab kill event. For example, a user who loses 3 tabs will record a + count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of + sessions where users experienced N or more kill events. The user may not + have actually seen the sad tab page, as it might have been an inactive tab. + Compare to Tabs.SadTab.KillDisplayed. This can happen due to out of memory, + malformed IPC messages, or a SIGINT/TERM/KILL signal sent by a user. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab was killed with a "He's dead, + Jim!" page due to the kernel out-of-memory killer, recorded once per + tab kill event. For example, a user who loses 3 tabs will record a count in + the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions where + users experienced N or more kill events. The user may not have actually seen + the sad tab page, as it might have been an inactive tab. Compare to + Tabs.SadTab.KillDisplayed. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab was killed with a "He's dead, + Jim!" page and the user saw the page, recorded once per tab kill event. + For example, a user who loses 3 tabs will record a count in the 1 bin, 2 + bin, and 3 bin. Thus each bin N is the number of sessions where users + experienced N or more kill events. Compare to Tabs.SadTab.CrashCreated. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Cumulative number of times a tab was killed with a "He's dead, + Jim!" page due to the kernel out-of-memory killer and the user saw the + page, recorded once per tab kill event. For example, a user who loses 3 tabs + will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the + number of sessions where users experienced N or more kill events. Compare to + Tabs.SadTab.CrashCreated. + + + + + wfh@chromium.org + + Cumulative number of times a tab crashed with "Aw, Snap!", + recorded once per tab oom event. For example, a user who ran out of memory + in 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin + N is the number of sessions where users experienced N or more oom events. + The user may not have actually seen the sad tab page, as it might have been + an inactive tab. Compare to Tabs.SadTab.OomDisplayed. + + + + + wfh@chromium.org + + Cumulative number of times a tab ran out of memory with "Aw, + Snap!" and the user saw the page, recorded once per tab oom event. For + example, a user who ran out of memory in 3 tabs will record a count in the 1 + bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions where users + experienced N or more oom events. Compare to Tabs.SadTab.OomCreated. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + Counts of events from the style of sad tab which has a reload button as its + primary action. Compare to Tabs.SadTab.Feedback.Event. + + + + + sonnyrao@chromium.org + jamescook@chromium.org + + The number of times a tab was reloaded because it was killed (usually by the + kernel OOM killer) and the user clicked on it later, recorded once per + reload event. For example, a user who clicks on 3 discarded tabs will record + a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of + sessions where users experienced N or more reload events. Compare to + Tabs.Discard.DiscardCount. + + + + + davidjm@chromium.org + nyquist@chromium.org + dtrainor@chromium.org + yusufo@chromium.org + + Records load time of a Tab using {SavedTabMethod} storage and whether the + {SavedTabLoadResult} + + + + + + + + + + + + + corising@chromium.org + chrome-desktop-ui-sea@google.com + + This histogram records the number of tabs that are 'scrubbed' by key press + during a given interval of time (i.e. ctrl+tab navigation). For this metric, + a tab is considered 'scrubbed' if it was active for less than or equal to a + given amount of time. + + + + + corising@chromium.org + chrome-desktop-ui-sea@google.com + + This histogram records the number of tabs that are 'scrubbed' by mouse press + during a given interval of time. For this metric, a tab is considered + 'scrubbed' if it was active for less than or equal to a given amount of + time. + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The distance a user multi-finger scrubbed to change tabs. Always positive + (ignores left / right). + + + + + afakhry@chromium.org + tclaiborne@chromium.org + + The duration a user spent doing multi-finger scrubbing to change tabs before + a different tab than the currently active one was actually activated. + + + + + kouhei@chromium.org + tzik@chromium.org + + Recorded once per tab activation. The number of tabs that were activated + while the tab was inactive. + +
+ This metric is to be removed after M46 hits stable. We don't expect this + metric to change over release, so we will remove this once we have the + numbers from stable. +
+ + + + kouhei@chromium.org + tzik@chromium.org + + Number of tabs between the previously active tab and the new active tab. + +
+ This metric is to be removed after M46 hits stable. We don't expect this + metric to change over release, so we will remove this once we have the + numbers from stable. +
+ + + + kouhei@chromium.org + tzik@chromium.org + + The state to which a tab transitioned. Recorded when a tab transitions from + the state in the histogram name to a new state. + +
+ kouhei@ and tzik@ will remove some variation of these once M46 hits stable. +
+ + + + yusufo@chromium.org + davidjm@chromium.org + meiliang@chromium.org + + The user is presented with recommendations on which Tabs they could take the + suggested action. The user has the option to: 1) Remove a Tab from the + recommendation 2) Add a Tab which wasn't in the recommendation to the + recommendation. + + This metric records the sum of the number of times the user does 1) or 2) + and is a measure of how useful the recommendation is. This metric is + recorded after the user accepts a recommendation - potentially with edits by + performing 1) or 2). + + Note: Adding and removing the same Tab, or vice versa, would be counted as + 0. + + + + + dtrainor@chromium.org + yusufo@chromium.org + + [Android] Time between the event that closes a tab and the start of + rendering. + + + + + dtrainor@chromium.org + yusufo@chromium.org + + [Android] Time between the event that exits an app and the start of + rendering. + + + + + dtrainor@chromium.org + yusufo@chromium.org + + [Android] Time between the event that creates a tab and the start of + rendering. + + + + + dtrainor@chromium.org + yusufo@chromium.org + + [Android] Time between the event that selects a tab and the start of + rendering. + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Counts the number of tabs across all windows, reported every 5 minutes. + Desktop only. + + + + + + + markchang@google.com + + The number of tabs open in the active window when a load completes. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The number of tabs in the current active group when a load completes. + Records 0 if the active tab is not in a group. + + + + + mattsimmons@chromium.org + memex-team@google.com + + The number of tabs open when the grid tab switcher is shown. + +
+ When the user is shown the tab switcher, logs the total number of individual + open tabs. Android only. +
+ + + + mattsimmons@chromium.org + memex-team@google.com + + The number of tabs open when the user is returned to the tab switcher on + start. + +
+ When the user is returned to the tab switcher on starting Chrome due to + inactivity, logs the overall number of tabs open. Android only. +
+ + + + mpearson@chromium.org + chrome-desktop-ui-sea@google.com + sbirch@google.com + + The number of tabs open in all browsers (counting app-mode windows) when a + load completes. + +
+ This is basically the average number of tabs over time. + + See also MPArch.RPHCountPerLoad for the number of processes used by these + tabs. +
+ + + + mpearson@chromium.org + chrome-desktop-ui-sea@google.com + + The number of tabs open per window (counting app-mode windows) when a load + completes. + +
+ This value will be recorded multiple times per load if more than one window + is open. +
+ + + + yusufo@chromium.org + + How many tabs a user moved forward or backward in the Android tab switcher. + +
+ Logged by the Android tab switcher when a user switches tabs (other than by + opening a new tab). If the user switches to an earlier tab in the stack, we + log a positive offset value indicating how many tabs back they moved. If the + user switches to a later tab, we log a negative offset value. If the user + stays on the same tab, we log 0. If the user switches to a tab in a + different stack (i.e. they switch from normal to incognito or vice-versa), + we don't log a value. +
+ + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search for and switch to + their desired tabs. The Tab Search UI is shown in a bubble anchored to an + element of the UI in the browser window. + + The bubble is dismissed when it loses focus or the escape key is pressed. + This metric tracks if the UI bubble was dismissed as a result of an action + taken from within the UI (such as switching to an open tab) or dismissed + without direct interaction with the Tab Search UI. + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for their desired tabs and close any currently open tabs. This records the + number of tabs closed from a single instance of the UI (the number of tabs + closed from within Tab Search in the time between when the UI is open and + when it is closed). + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for their desired tabs. It can be opened and closed. This records the number + of tabs there are in the payload Tab Search is sent when it is first opened. + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for their desired tabs. It can be opened and closed. This records the number + of windows there are in the payload Tab Search is sent when it is first + opened. + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search for and switch to + their desired tabs. The Tab Search UI is shown in a bubble anchored to an + element of the UI in the browser window. + + The bubble can be invoked via a number of different means including mouse + click, keyboard navigation, keyboard shortcut or touch gesture. This metric + tracks the kind of action the user took to invoke the Tab Search bubble UI. + + + + + tluk@chromium.org + robliao@chromium.org + + Records the time taken to load the Tab Search WebUI and render (at least) + the initial list of tabs. This is roughly equivalent to 'time to first + meaningful paint' for the Tab Search UI. + + + + + tluk@chromium.org + robliao@chromium.org + + The amount of time between the render frame host StartProvisionalLoad event + and the render frame DocumentOnLoadCompleted event for the Tab Search WebUI + page. + + + + + tluk@chromium.org + robliao@chromium.org + + The amount of time between the render frame host StartProvisionalLoad and + DidFinishDocumentLoad events for the Tab Search WebUI page. + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for and switch to their desired tabs. This records whether the user used Tab + Search to switch to a tab from a filtered search results list or the default + unfiltered list. + + + + + tluk@chromium.org + robliao@chromium.org + + Tab Search is a feature that allows users to better search their browsers + for their desired tabs. It can be opened and closed. This records the amount + of time between when a Tab Search bubble is opened and when it is closed. It + does so by recording the difference in time between when the Tab Search's + bubble is first shown and when the bubble's destructor is called. + + The Tab Search UI is a bubble anchored to an element within a browser window + and is closed if the user switches to a tab, presses the escape key or + performs an action to return focus to the hosting window. The Tab Search UI + bubble will also close if the hosting browser window is closed or crashes. + + Users may leave the bubble open for long periods of time without directly + interacting with the UI which could result in a long tail of displayed + durations. + + + + + sebmarchand@chromium.org + + Counts how often tab stats daily interval events were fired. + + + + + yusufo@chromium.org + wychen@chromium.org + + The average tab group size, average number of tabs in a group, on a cold + start after all tabs are restored. + + + + + yusufo@chromium.org + wychen@chromium.org + + During tab restoration, a tab is considered as a duplicated tab when it has + an identical url with another restored tab. + + This histogram records the number of duplicated tabs on a cold start after + all tabs are restored. The possible range for this number is from 0 to total + number of restored tabs minus 1. In other words, this number is equals to + total number of restored tabs minus the number of unique URLs. + + + + + yusufo@chromium.org + wychen@chromium.org + + During tab restoration, a tab is considered as a duplicated tab when it has + an identical url with another restored tab. + + This histogram records the ratio of duplicated tabs to the total number of + tabs on a cold start after all tabs are restored. This ratio will never + reach 100%, since the highest possible number of duplicated tabs is total + number of restored tabs minus 1. + + + + + + + yusufo@chromium.org + wychen@chromium.org + + The cumulative number of "spokes" from any "hub" page in + every tab. A "hub" is any page that the user navigates away from, + and a "spoke" is a page that's navigated to. The + "spokes" count is incremented and recorded each time the user + navigates back to a "hub" page via navigation back button and then + navigates to a new "spoke". + + + + + + + yusufo@chromium.org + wychen@chromium.org + zea@chromium.org + + This recorded value is the number of currently open tabs that were created + from a given source. This is recorded when entering the tab switcher mode. + + + + + + + yusufo@chromium.org + wychen@chromium.org + zea@chromium.org + + The recorded value is the percentage of the number of currently open tabs + that are created from a given source, relative to the total number of + currently open tabs. This is recorded when entering the tab switcher mode. + + + + + yusufo@chromium.org + wychen@chromium.org + + The number of tab groups on a cold start after all tabs are restored. + + + + + yusufo@chromium.org + wychen@chromium.org + + The tab group density, the ratio of the number of tab groups to the total + number of tabs, on a cold start after all tabs are restored. + + + + + yusufo@chromium.org + wychen@chromium.org + + The number of tabs is belonging to a tab group on a cold start after all + tabs are restored. + + + + + yusufo@chromium.org + wychen@chromium.org + + The ratio of all tabs in tab groups to the total number of tabs on a cold + start after all tabs are restored. + + + + + mattsimmons@chromium.org + memex-team@google.com + + When a tab is revisited and subsequently the omnibox is focused within a + certain threshold of time, this reports the amount of time in seconds that + has passed since the last user engagement with the tab. Currently + Android-only. + + + + + mattsimmons@chromium.org + memex-team@google.com + + When a tab is closed, this reports the amount of time in seconds that has + passed since the last user engagement with the tab. Currently Android-only. + + + + + mattsimmons@chromium.org + memex-team@google.com + + When a tab is revisited, this reports the amount of time in seconds that has + passed since the last user engagement with the tab. Currently Android-only. + + + + + sebmarchand@chromium.org + + The number of tabs that haven't been interacted with, visible or audible + over a given interval time, but which no longer exist at all at the end of + this interval. + + + + + sebmarchand@chromium.org + + The number of tabs that haven't been interacted with, visible or audible or + visible during a given interval of time and still exist at the end of this + interval. + + + + + sebmarchand@chromium.org + + The number of tabs that have been interacted with, visible or audible over a + given interval of time, but which no longer exist at all at the end of this + interval. + + + + + sebmarchand@chromium.org + + The number of tabs that have been interacted with, visible or audible during + a given interval of time, includes tabs that don't exist at the end of this + interval. + + + + + + + sebmarchand@chromium.org + catan-team@chromium.org + + Counts the number of Chrome windows, reported every 5 minutes. Desktop only. + + + + + collinbaker@chromium.org + chrome-desktop-ui-sea@google.com + + Total time spent in each call of TabStrip::PaintChildren(). This comprises + the paint time for all parts of the TabStrip that do not paint to their own + layers. This is recorded at the end of TabStrip::PaintChildren(), when all + child views are finished painting. + + As of writing (May 17, 2019), this always includes the tab backgrounds, + strokes, labels, close buttons. The tab icons and new tab button sometimes + paint to their own layer; in frames where this is so, their times won't be + included here. + + + + + yusufo@chromium.org + wychen@chromium.org + + When conditional tab strip shows, records which kind of intentional + tab-related action triggered it. + + + + + collinbaker@chromium.org + chrome-desktop-ui-sea@google.com + + Time spent painting a tab icon. This includes a page's favicon and loading + animation (when loading). This is recorded at the end of TabIcon::OnPaint(). + + + + + yusufo@chromium.org + wychen@chromium.org + + This histogram records the number of tabs within the group during page load. + + If the loading happens in a tab that does not belong to a group, we log 0. + Else, we log a positive number >= 2. + + + + + connily@chromium.org + cyan@chromium.org + chrome-desktop-ui-sea@google.com + + The amount of time from cursor entering the tabstrip to first click on a tab + to switch. + +
+ This will exclude some kinds of switching (hotkeys, between windows) where + it would be difficult to define a start time. Entering the tabstrip is an + approximation which will vary between users, but should still be useful for + A/B comparison. +
+ + + + yusufo@chromium.org + wychen@chromium.org + + A tab strip session starts when the last time Chrome comes to the foreground + was more than an hour ago. At the beginning of a tab strip session, records + the user status of conditional tab strip feature in the last tab strip + session. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/translate/histograms.xml b/tools/metrics/histograms/histograms_xml/translate/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..9cb0e1763e640a47075c52fdf9ca5290bf50e222 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/translate/histograms.xml @@ -0,0 +1,710 @@ + + + + + + + + + + googleo@chromium.org + chrome-language@google.com + + Time taken for the TranslateAcceptLanguages to decide if a given language is + available as Accept-Languages. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the always translate option was selected in the + translate infobar. + + + + + groby@google.com + chrome-language@google.com + Tracks UI events related to the translate bubble. + + + + sclittle@google.com + megjablon@google.com + chrome-language@google.com + + The time spent capturing plain text from the DOM. Pre sub frame translation + support (this includes before M83), this is reported by + ChromeRenderViewObserver. If sub frame translation is enabled, this is + captured in the browser process and reported by ContentTranslateDriver. + + + + + frechette@chromium.org + chrome-language@google.com + + Language of the input page detected by CLD3. This information is logged on + every page load. + + + + + frechette@chromium.org + chrome-language@google.com + + Percentage of the bytes that are associated with the most popular language + on the input page. Only recorded if the detection returned a + "known" result. + + + + + mcrouse@chromium.org + chrome-language@google.com + + The time to evaluate the CLD3 language detection model for the top language. + This information is logged on every request. + + + + + anthonyvd@chromium.org + chrome-language@google.com + Various user actions performed in the translate infobar. + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the hashcode of the source language when always translate this + language option is clicked in the menu. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the hashcode of the language clicked on the more languages menu. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the hashcode of the source language when never translate this + language option is clicked in the menu. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the hashcode of the language clicked on the menu to indicate the + page is not in the selected language. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the hashcode of the language clicked on the infobar. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + Records the number of times a page is translated, every time the page is + translated. For instance on a page a) translation from A to B, we record + "1" b) from A to B - we record "1" and revert from B to + A - we record "2" c) from A to B - we record "1", then + translation to C - we record "2". d) from A to B - we record + "1", then translation to C - we record "2" and then + revert to A - we record "3". We increment the translation count: + a) every time the target language is changed. b) every time we revert to the + original language (user can only revert to original language and not + intermediate target languages). This essentially means 1 denotes >= 1 + translations, 2 is >=2 translations per page and so on. This will give us + a sense of how often people try out several translates on a page, or flip + back and forth. + + + + + kenjibaheux@google.com + chrome-language@google.com + + A page may provide a Content-Language HTTP header or a META tag. For each + page load, measures whether the Content-Language header exists and is valid. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the "Nope" (don't translate) or the infobar's + X button was clicked in the translate infobar. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the translate infobar was closed by clicking the X + button without the user translating the page. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the translate UI was closed without translating in the + way that the user doesn't deny translating explicityly, like pressing 'Nope' + button. This is counted on both the infobar and the bubble UI. We are + comparing this on infobar to that on bubble by A/B testing and expecting + that the user will click 'Nope' button on bubble less times than infobar. We + won't delete this histogram after the experiment. + + + + + yyushkina@google.com + anthonyvd@google.com + chrome-language@google.com + + The events (shown, saved, cancelled) happening in the Explicit Language Ask + prompt. + + + + + yyushkina@google.com + anthonyvd@google.com + chrome-language@google.com + + The languages that were added to the Accept Languages list from the Explicit + Language Ask prompt. + + + + + yyushkina@google.com + anthonyvd@google.com + chrome-language@google.com + + The languages that were removed from the Accept Languages list from the + Explicit Language Ask prompt. + + + + + megjablon@google.com + chrome-language@google.com + + For Google navigations, the hrefTranslate hint may trigger a translation + automatically. If the hint is present on a Google navigation, record whether + or not automatic translation happened. If automatic translation was already + going to happen, then we use the auto translate target language. Also record + if this caused the target language to be different than the hrefTranslate + target language. + + + + + kenjibaheux@google.com + chrome-language@google.com + + A page may provide a lang attribute in html tag. For each page load, + measures whether the lang attribute exists and is valid. + + + + + anthonyvd@chromium.org + chrome-language@google.com + + The number of times the translate infobar was shown in the old translate UI + on Android. Only true is recorded. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The reason why Chrome decided to perform the next action (e.g., to show + infobar, to translate a page without any prompting, and so on) when Chrome + Translate is ready to translate a page. + + + + + sclittle@chromium.org + megjablon@chromium.org + chrome-language@google.com + + The number of characters of page content used for language detection. + + + + + andrewhayden@chromium.org + chrome-language@google.com + + For each page load, records whether language detection occurs on time or + gets deferred. If deferred language detection later completes, this is also + recorded. This allows measuring the UX impact of using a non-static CLD data + source. + + + + + sclittle@chromium.org + megjablon@chromium.org + chrome-language@google.com + + Records the time from when a navigation finishes to when its page language + is determined. This includes the time to load the frame(s), capturing the + text content of the page, and running language classification on that + content. + + + + + frechette@chromium.org + chrome-language@google.com + + Log everytime the language settings page is shown. This can be either user + visits chrome://settings/languages or user visits the advanced languages + card in chrome://settings. With this stat, we will be able to understand how + well the language model is doing by looking into how the number changes over + time. In additiona to that, we are also interested in how many users ever + visit the languages settings card. + + + + + yyushkina@chromium.org + chrome-language@google.com + + For each page load, measures whether the provided HTML language (i.e. the + page lang attribute if it exists, otherwise the header Content-Language + value) matches the language determined by CLD. Beyond directly matching or + mismatching the HTML language, CLD can complement the HTML language. For + example, suppose the HTML language is 'zh' (general Chinese), a language + code that the Translate server does not support. In this case, CLD can + detect a subcode like '-TW' or '-CN', resulting in language codes 'zh-TW' + and 'zh-CN', which the Translate server supports. This is referred to as + "complementing a language subcode". + + + + + kenjibaheux@google.com + chrome-language@google.com + + Logs the user locale when the Translate feature is disabled by the user. + This is recorded each time a webpage is loaded and prefs for translation is + checked. This allows us to investigate the correlation between the user + locale and the usage rates of the Translate. + + + + + yyushkina@google.com + frechette@chromium.org + chrome-language@google.com + + Whether the 'Translate' app menu entry is shown to the user. Emitted when + the app menu (three dots) is shown and a translation could be performed. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the original language in the translate infobar has been + changed. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the target language in the translate infobar has been + changed. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the never translate option was selected in the translate + infobar. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the never translate site was selected in the translate + infobar. + + + + + kenjibaheux@google.com + chrome-language@google.com + Counts translation target page schemes. + + + + rogerm@google.com + chrome-language@google.com + + Tracks the outcome of attempts to download a Translate Ranker Model. + + + + + rogerm@google.com + chrome-language@google.com + + The date tamp (e.g., 20160916 -> 15 Sept 2016) which denotes the + TranslateRankerModel's version. + + + + + rogerm@google.com + chrome-language@google.com + + Whether the TranslateRanker accepts or denies to show the translation + prompt. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the TranslateRanker to use the translate ranker model to + calculate a score for the translation, in ms. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the Translate Ranker Model Loader to download its model from + the configured URL, in ms. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the Translate Ranker Model Loader to parse its model, in ms. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the Translate Ranker Model Loader to read its model from + local storage (cache), in ms. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the TranslateRanker to decide if a given translation should + be offered or not, in ms. This includes the time taken to extract the + relevant features upon which to base the decision, as well as the time taken + to calculate the result. + + + + + rogerm@google.com + chrome-language@google.com + + Time taken for the Translate Ranker Model Loader to write its model to local + storage, in ms. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the "report this error" of options menu is + selected in the translate infobar. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the show original button was clicked in the translate + infobar. + + + + + kenjibaheux@google.com + chrome-language@google.com + + Chrome Translate shows an error UI (infobar or bubble) when an error happens + on translation and the UI message depends on what kind of error happens. + This metric counts how often each error message is shown. + + + + + kenjibaheux@google.com + chrome-language@google.com + + This metrics is logged whenever a page is loaded. The logged value is + "Mathced" when the CLD-detected language differs from the page + language code , and the two languages are such similar languages. In that + case, Chrome ignore the CLD-determined language and instead uses the page + language code. The page language code is decided by Content-Language and + HTML lang attribute. + + + + + yyushkina@google.com + chrome-language@google.com + + The number of requests sent to the Translate server, grouped by source + language. + + + + + yyushkina@google.com + chrome-language@google.com + + The number of requests sent to the Translate server, grouped by target + language. + + + + + megjablon@google.com + chrome-language@google.com + + Where the target language was determined from. Can be the most recent target + language, from the language model, the UI language, the user's accept + languages, or default to English. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The time from injecting scripts for Chrome Translate to being ready to + perform translation. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The time from injecting scripts for Chrome Translate to the finishing loads + of all depending libraries. + + + + + kenjibaheux@google.com + chrome-language@google.com + The time from starting translation to the completion. + + + + kenjibaheux@google.com + chrome-language@google.com + + The number of times the translate button was clicked in the translate + infobar. + + + + + sclittle@google.com + megjablon@google.com + chrome-language@google.com + + The number of times the translate button was clicked in the translate + infobar for a page that is likely an AMP Cache URL. + + + + + sclittle@google.com + megjablon@google.com + chrome-language@google.com + + The number of frames translated for a translated page (including the main + frame). This is recorded when sub frame translation is enabled. + + + + + sclittle@google.com + megjablon@google.com + chrome-language@google.com + + The error type for a failed sub frame translation (where the main frame was + successfully translated). This is recorded when sub frame translation is + enabled. + + + + + sclittle@google.com + megjablon@google.com + chrome-language@google.com + + The percentage of sub frames that translated successfully for a translated + page (where the main frame was successfully translated). This is recorded + when sub frame translation is enabled. + + + + + kenjibaheux@google.com + chrome-language@google.com + + Logs an undisplayable language included in the language list sent by the + Translate server. The Translate server sends the list each time the user + runs Chrome. This metrics tells us that there is a language which UI should + support but doesn't. + + + + + kenjibaheux@google.com + chrome-language@google.com + + Logs an unsupported source language detected during initiation of the + Translate feature. This is reported when the language detector successfully + detects the language of the webpage, but the language is not supported by + the translation server because it is too minor. This metric allows us to + assess how important the unsupported language is for Google translate. + + + + + kenjibaheux@google.com + chrome-language@google.com + + The time from a page content language being determined to user requesting + Chrome Translate. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/ukm/histograms.xml b/tools/metrics/histograms/histograms_xml/ukm/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..57b9876be81870bbd9e432c16b081292d5ef8517 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/ukm/histograms.xml @@ -0,0 +1,273 @@ + + + + + + + + + + rkaplow@chromium.org + ukm-team@google.com + + The actual interval between log upload start and previous log upload + finished within the same process. A value of 0 indicates there was no + previous upload. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Emitted when UKM Service attempts to build and store a log. Emits true if it + was empty (no sources or entries) which means no log is written, false + otherwise. + + + + + bcwhite@chromium.org + rkaplow@chromium.org + ukm-team@google.com + + Logged in UpdateUkmAllowedForAllProfiles from the UkmConsentStateObserver + which is called when UkmConsentStateObserver starts observing a new profile + and every time a URL-keyed anonymized data collection state changes or a + sync service state changes. This records whether UKM is allowed for all + profiles. + + + + + bcwhite@chromium.org + rkaplow@chromium.org + ukm-team@google.com + + Logged in the UpdateProfileState call from the UkmConsentStateObserver. This + records if the UKM allowed change will trigger a purge of the local UKM + data. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of UKM entries that are dropped. Categorized by the cause of it being + dropped. + + + + + jwd@chromium.org + ukm-team@google.com + + The hashed name of the UKM entry being dropped. The hash is the same hash + sent in the UKM log but truncated to 31 bits with "event_hash & + 0x7fffffff". Recorded when adding an entry and the UKM recorder decides + it should be dropped. + + + + + yrsun@chromium.org + ukm-team@google.com + + The hashed name of the UKM entry being recorded. The hash is the same hash + sent in the UKM log but truncated to 31 bits with "event_hash & + 0x7fffffff". Recorded when an entry is added and accepted by the UKM + recorder. + + + + + rkaplow@chromium.org + ukm-team@google.com + Number of serialized UKM entries when storing a UKM log. + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of serialized UKM entries that are of type PageLoad that have the + metric PaintTiming.NavigationToFirstContentfulPaint. This is recorded every + time a UKM log is stored. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Logged during UkmService initialization whether the init task or the initial + log timer completed first. The expectation is the vast majority of the time, + the init task should complete first. If metrics show otherwise, then it may + indicate there's a bug in the UkmService init sequence and that it should be + investigated. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Size in kilobytes (after compression) of an uploaded UKM log. Recorded after + a successful UKM upload. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Logs whether a log was not uploaded due to cellular log throttling logic. + Android only. + + + + + rkaplow@chromium.org + ukm-team@google.com + + HTTP response codes and network errors encountered by UKM when attempting to + upload logs to the server. + + + + + jwd@chromium.org + rkaplow@chromium.org + ukm-team@google.com + + The client id was migrated from an Int64 pref to a UInt64 pref. Not migrated + is recorded when a valid UInt64 value is loaded from prefs. Migration + started in M75. + + + + + rkaplow@chromium.org + ukm-team@google.com + The status when loading UKM PersistedLogs from Prefs. + + + + rkaplow@chromium.org + ukm-team@google.com + + Recorded when a UKM client state (client_id, session_id) is reset. This + emits the reason the resetting was triggered. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of UKM sources that are dropped. Categorized by the cause of it being + dropped. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of unsent UKM sources that were kept in-memory to be potentially + transmitted in the next log. + + + + + rkaplow@chromium.org + ukm-team@google.com + Number of serialized UKM sources when storing a UKM log. + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of UKM sources that were not sent because they did not match a + navigation source URL. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of UKM sources that were not sent because they had no associated + entries. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Number of bytes in an excessively large log that was discarded while + persisting UKM logs to disk to retry during next chrome run. + + + + + rkaplow@chromium.org + ukm-team@google.com + + Counter for number of UKM unsent logs removed from persistent storage. + + + + + vincb@google.com + ukm-team@google.com + + The status of the retrieval of user demographics from sync that are reported + to UKM. Emitted each time UKM metrics are reported. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/UMA/histograms.xml b/tools/metrics/histograms/histograms_xml/uma/histograms.xml similarity index 98% rename from tools/metrics/histograms/histograms_xml/UMA/histograms.xml rename to tools/metrics/histograms/histograms_xml/uma/histograms.xml index ed0f15b00ee29c24f0692b32bdcc1671b7611e1d..d678c5f30ed84afe1c04b299081917910c101476 100644 --- a/tools/metrics/histograms/histograms_xml/UMA/histograms.xml +++ b/tools/metrics/histograms/histograms_xml/uma/histograms.xml @@ -5,15 +5,12 @@ found in the LICENSE file. --> + + + + + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The network connection type when the attempt begins. Possible values include + "Unknown", "Ethernet", "Wifi", + "Wimax", "Bluetooth", "Cellular", + "Tethered Ethernet", "Tethered Wifi". + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + A more detailed description of the last Payload transfer error when + downloading the payload. + + This is reported when an attempt ends with the "Payload Download + Error" result. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The download source used, possible values include "HTTPS Server", + "HTTP Server" and "HTTP Peer". + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes the update attempt took including the time the device + spent sleeping. + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes the update attempt took excluding the time the device + spent sleeping. + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + A more detailed description of the last internal error. The possible values + correspond to the ErrorCode enumeration in the update_engine source code. + + This is reported when an attempt ends with the InternalError result. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The attempt number which starts at 0 for the initial attempt and keeps + increasing for subsequent attempts. + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of payload mebibytes (1048576 bytes) actually download. + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The payload download speed, in kilobytes per second (1000 bytes/second). + This is calculated as the number of bytes downloaded divided by the duration + of the attempt (excluding time spent sleeping). + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The payload size, in mebibytes (1048576 bytes). + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The payload type, possible values include "Delta" (if Omaha + specified to download a delta payload); and "Full" (if Omaha + specified to download a full payload); and "ForcedFull" (if the + client specified that it would only accept a full payload). + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The result of the update attempt. + + This is reported when an update attempt ends. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes since the last attempt including the time the device + spent sleeping. + + This is reported when an update attempt ends but only if there was a + previous attempt for the same update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes since the last attempt excluding the time the device + spent sleeping. + + This is reported when an update attempt ends but only if there was a + previous attempt for the same update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The status of the certificate check done when downloading a payload over + HTTPS. Note that most downloads are done over HTTP. + + This is reported on every HTTPS connection to the payload download server. + Connection drops on the same payload may report different values. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The status of the certificate check done when querying Omaha for a new + version. + + This is reported on every update check. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + If unable to download a response from Omaha, a more detailed error code is + reported in this metric. + + This is reported on every update check resulting in "Download + error". + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + If there is an update available, this metric will track what the device does + with the information. Possible values include "Applying update", + "Deferring update", "Ignoring update", and "Backing + off". + + This is reported on update checks resulting in "Update available". + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The response from Omaha. Possible values include "No update + available", "Update available", "Download error", + "Response parsing error", and "Reboot pending". + + This is reported on every update check. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + First section of the Chrome OS target version set by device policy and sent + to Omaha if rollback is also allowed. This is a sparse histogram, since the + possible valid values are stable Chrome OS version prefixes (usually one per + milestone). + + Example value: 10323 (meaning M65 stable). + + This is reported on every update check if the TargetVersionPrefix device + policy is set and the value of the RollbackToTargetVersion device policy is + one of the values allowing rollback. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + First section of the Chrome OS target version set by device policy and sent + to Omaha. This is a sparse histogram, since the possible valid values are + stable Chrome OS version prefixes (usually one per milestone). + + Example value: 10323 (meaning M65 stable). + + This is reported on every update check if the TargetVersionPrefix device + policy is set. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes since the last check including the time the device + spent sleeping. + + This is reported on every update check except for the first one. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of minutes since the last check excluding the time the device + spent sleeping. + + This is reported on every update check except for the first one. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The age of the OS in days, defined as the age of the /etc/lsb-release file. + + This is reported on every update check but at most once a day. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + First section of the Chrome OS version to which an enterprise rollback + (rollback initiated by the admin of the device) has failed. This is a sparse + histogram, since the possible valid values are stable Chrome OS version + prefixes (usually one per milestone). + + Example value: 10323 (meaning M65 stable). + + This is reported after a rollback image has failed installing. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + First section of the Chrome OS version to which an enterprise rollback + (rollback initiated by the admin of the device) has succeeded. This is a + sparse histogram, since the possible valid values are stable Chrome OS + version prefixes (usually one per milestone). + + Example value: 10323 (meaning M65 stable). + + This is reported after a rollback image has been successfully installed. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The number of consecutive times a device has failed to boot an update that + successfully applied. + + This is reported every time the firmware fails to boot the slot with the + update and fell back to the slot it originally updated from. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The source used to provision the install-date-days value sent to Omaha with + every request. + + This is reported when OOBE (Out Of Box Experience) completes (M34 or later) + or when upgrading to a version with install-date-days support. + + This metric is specific to Chrome OS. + + + + + poromov@chromium.org + + Whether setting the MaxKernelKeyRollforward value in the TPM succeeded. + + This is reported every time an update check happens. This is a bool value. + + This metric is specific to Chrome OS. + + + + + poromov@chromium.org + + Maximum value the device can roll forward the minimum kernel key version + value in the TPM during the next boot. + + This value is set to infinity (0xfffffffe) for devices which doesn't allow + rollback. + + Otherwise, the value is the kernel key version of the earliest image to + which the device is allowed to roll back. + + This is reported every time an update check happens. This is a sparse value. + + This metric is specific to Chrome OS. + + + + + poromov@chromium.org + + Minimum kernel key version already set in the TPM. This value specifies + which images can be booted up with verified boot. + + This is reported every time an update check happens. This is a sparse value. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + Whether rollback worked. + + This is reported every time there's a rollback request. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of update attempts required to update the device. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of bytes downloaded in mebibytes (1048576 bytes) using all + available sources (e.g. HTTP, HTTPS, HTTP Peer). + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of bytes downloaded in mebibytes (1048576 bytes) using HTTP + from a local peer. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of bytes downloaded in mebibytes (1048576 bytes) using + HTTP. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of bytes downloaded in mebibytes (1048576 bytes) using + HTTPS. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The ratio between bytes downloaded and payload size minus 100. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The various download sources used - this is a combination of the values + "HTTPS Server", "HTTP Server" and "HTTP Peer". + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + The total number of days from when an update is first seen to when an update + is finished downloading (but before rebooting). This metric is recorded on + enterprise-enrolled devices that do not have the + DeviceAutoUpdateTimeRestrictions policy enabled. + + This metric is specific to Chrome OS. + + + + + mpolzer@google.com + managed-platforms@google.com + + The total number of days from when an update is first seen to when an update + is finished downloading (but before rebooting). This metric is recorded on + devices that have the DeviceAutoUpdateTimeRestrictions policy enabled. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The size of the payload, in mebibytes (1048576 bytes). + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The payload type ("Delta", "Full", + "ForcedFull") used. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of reboots during the update. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of minutes from when an update was detected until an update + (possibly another update) was applied. This includes the time waiting for + update checks and time the device spent sleeping. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of minutes from when an update was detected until an update + (possibly another update) was applied. This does not include the time + waiting for update checks and time the device spent sleeping. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of updates that were abandoned since the last successful + update. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The total number of times the URL was switched (from e.g. HTTPS to HTTP) + because of failures. + + This is reported on every successful update. + + This metric is specific to Chrome OS. + + + + + ahassani@chromium.org + chromeos-core-services@google.com + + The duration between when an update has successfully completed and the user + is presented with the "reboot arrow" and when the system has + booted into the new update. + + This is reported every time the device is rebooted after an update has been + applied. + + This metric is specific to Chrome OS. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/v8/histograms.xml b/tools/metrics/histograms/histograms_xml/v8/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..2c3480f746822c054d5c2f65031e6b8d5c961964 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/v8/histograms.xml @@ -0,0 +1,1247 @@ + + + + + + + + + + gdeepti@chromium.org + ecmziegler@chromium.org + + Number of bytes requested in array buffer allocations greater than one + megabyte. + + + + + gdeepti@chromium.org + ecmziegler@chromium.org + Array buffer sizes for which V8 failed to allocate memory. + + + + yangguo@chromium.org + + Reason code data has been rejected when attempting to deserialize. + + + + + yangguo@chromium.org + Cache size to source size ratio when caching compiled code. + + + + delphick@chromium.org + + Time spent collecting source positions to generate stack traces. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yangguo@chromium.org + + Time spent compiling a script that may be subject to caching. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vogelheim@chromium.org + + Time spent deseriailzing code, used by V8 code caching. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yangguo@chromium.org + + Time spent in V8 compiler (full codegen) for eval. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + hablich@chromium.org + + Aggregated time spent compiling functions lazily during a single script + execution. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yangguo@chromium.org + + Time spent in V8 compiler (full codegen) excluding parser. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + The cache behaviour of compiling a V8 script, including whether we produced + or consumed a code cache, whether we hit V8's isolate's cache, and if we + didn't use the code cache, the reason why not. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing/caching). + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + rmcilroy@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) on a background + thread. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script when the 'compilation' is + deserializing it from the code cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing/caching) when the + compilation tried to deserialize it from the code cache, but failed. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing/caching) in the case + where the V8 isolate's compilation cache is hit. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) when the cache is too + cold to use. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) when the script is an + inline script. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) when we do not want + to cache it. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) when the script is + too small to be cached. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in compiling a script (incl. parsing) and serializing it + for the code cache. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Total time spent in finalizing a script that was streaming compiled. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + vogelheim@chromium.org + + Time spent serializing code, used by V8 code caching. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yangguo@chromium.org + + Debugger feature used at least once per isolate, recorded on first use. + + + + + hablich@chromium.org + + The amount of JavaScript errors thrown by V8 per context. It does not count + custom errors and ignores catched errors thrown by V8. This is collected + after the context is detached. + + + + + rmcilroy@chromium.org + + Time spent in JavaScript Execution, including runtime calls, callbacks, and + lazy compilation. + + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + + Time spent in background tasks doing marking in one GC cycle. It is recorded + after each GC. + + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + + Time spent in background tasks doing scavenging in one GC cycle. It is + recorded after each GC. + + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + + Time spent in background tasks doing sweeping in one GC cycle. It is + recorded after each GC. + + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + Time spent in mark-sweep phase of GC. + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in mark-sweep phase of GC in a background isolate. + + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in mark-sweep phase of GC in a foreground isolate. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental latency-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the clearing phase of incremental latency-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the epilogue of incremental latency-optimized Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the evacuation phase of incremental latency-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the finish phase of incremental latency-optimized Mark-Compact + GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the marking phase of incremental latency-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the prologue of incremental latency-optimized Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the sweeping phase of incremental latency-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental latency-optimized + Mark-Compact GC in a background isolate. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental latency-optimized + Mark-Compact GC in a foreground isolate. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental memory-optimized + Mark-Compact GC. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental memory-optimized + Mark-Compact GC in a background isolate. + + + + + ulan@chromium.org + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in the final atomic pause of incremental memory-optimized + Mark-Compact GC in a foreground isolate. + + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + Time spent doing incremental marking steps during GC. + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + Time spent in finalizing incremental marking. + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + Reason an incremental marking was started in V8. + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + Time spent in starting incremental marking. + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + + The total time spent in incremental marking steps in one GC cycle. It is + only recorded if the time is non-zero. + + + + + mlippautz@chromium.org + v8-memory-sheriffs@google.com + + Marking throughput considering all durations of all marking phases on the + main thread and marked bytes within one V8 garbage collection cycle. + Reported once per garbage collection cycle. Only reported for platforms + supporting high resolution clocks and when more than 1MB of live objects + have been found. + + + + + mlippautz@chromium.org + v8-memory-sheriffs@google.com + + Sum of all durations of individual phases within one V8 mark-compact garbage + collection. Reported once per garbage collection. + + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + Reason a mark-compact garbage collection was started in V8. + + + + mlippautz@chromium.org + v8-memory-sheriffs@google.com + + Sum of all durations of all marking phases (incremental and non-incremental) + within one V8 garbage collection cycle. Reported once per garbage collection + at the end. + + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + Time spent in scavenging phase of GC. + + + + mlippautz@chromium.org + v8-memory-sheriffs@google.com + + Wall time spent in the main scavenging phase that copies over all reachable + objects during a V8 scavenge. + + + + + mlippautz@chromium.org + v8-memory-sheriffs@google.com + Time spent in scavenging the roots during a V8 scavenge. + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in scavenging phase of GC in a background isolate. + + + + + ulan@chromium.org + v8-memory-sheriffs@google.com + Reason a scavenge garbage collection was started in V8. + + + + hpayer@chromium.org + v8-memory-sheriffs@google.com + + Time spent in scavenging phase of GC in a foreground isolate. + + + + + oth@chromium.org + Results from snapshot loading. + + + + oth@chromium.org + Results from opening V8 snapshot files. + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Liftoff (V8's baseline compiler for WebAssembly) bails out if it hits the + first unsupported feature in a function. The function is recompiled with + TurboFan then. This histogram records the bailout reason (or success) per + WebAssembly function compilation in Liftoff. + + + + + hpayer@chromium.org + + External memory fragmentation in the code space after each GC in percent. + + + + + hpayer@chromium.org + + External memory fragmentation in the large object space after each GC in + percent. + + + + + hpayer@chromium.org + + External memory fragmentation in the map space after each GC in percent. + + + + + hpayer@chromium.org + + External memory fragmentation in the old space after each GC in percent. + + + + + hpayer@chromium.org + + Total external memory fragmentation after each GC in percent. + + + + + hpayer@chromium.org + + The size of committed memory in the code space after each GC in KB. + + + + + hpayer@chromium.org + + The size of committed memory in the map space after each GC in KB. + + + + + hpayer@chromium.org + + The maximum size of committed memory used by V8 after each GC in KB. + + + + + hpayer@chromium.org + + The total size of committed memory used by V8 after each GC in KB. + + + + + hpayer@chromium.org + + The total size of live memory used by V8 after each GC in KB. + + + + + jgruber@chromium.org + mvstanton@chromium.org + + The number of backtracks performed in a single regexp execution. + + + + + gdeepti@chromium.org + ulan@chromium.org + + Number of megabytes requested in shared array buffer allocations. + + + + + tebbi@chromium.org + mvstanton@chromium.org + + Number of ticks (in 1000s of ticks) from starting optimizing to installing + the code object. Recorded on each regular optimization of a function. + + Similar to V8.TurboFanOptimizeTotalTime, but instead of counting time, we + count a deterministic number of ticks sprinkled throughout the Turbofan + compiler. + + + + + bmeurer@chromium.org + mslekova@chromium.org + + Total time from starting optimizing to installing the code object. Recorded + on each regular, concurrent optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the execution phase of TurboFan optimization. Recorded on each + regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the finalization phase of TurboFan optimization. Recorded on + each regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the execution phase of TurboFan optimization for On Stack + Replacement (OSR). Recorded on each optimization for on-stack replacement of + a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the finalization phase of TurboFan optimization for On Stack + Replacement (OSR). Recorded on each optimization for on-stack replacement of + a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the preparation phase of TurboFan optimization for On Stack + Replacement (OSR). Recorded on each optimization for on-stack replacement of + a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Total time from starting optimizing for On Stack Replacement (OSR) to + installing the code object. Recorded on each optimization for on-stack + replacement of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + bmeurer@chromium.org + mslekova@chromium.org + + Total time from starting optimizing to installing the code object. Recorded + on each regular, non-concurrent optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Time spent in the preparation phase of TurboFan optimization. Recorded on + each regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Total time spent on a background thread during TurboFan optimization. + Recorded on each regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Total time spent on the main thread during TurboFan optimization. Recorded + on each regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + neis@chromium.org + mvstanton@chromium.org + + Total time from starting optimizing to installing the code object. Recorded + on each regular optimization of a function. + + This histogram only records metrics on machines with high-resolution clocks. + + + + + ecmziegler@chromium.org + adamk@chromium.org + ahaas@chromium.org + + The total amount of address space reserved by the backing stores of all live + WebAssembly.Memory backing stores in MiB. Recorded on each memory + reservation. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to compile a WebAssembly function. Recorded on each compilation of a + single function, either synchronous, asynchronous, or lazily. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Peak memory used to compile a WebAssembly function. Recorded for each + TurboFan compilation of a WebAssembly function. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to asynchronously compile a WebAssembly module (using the + 'WebAssembly.compile' API). Recorded on each asynchronous WebAssembly + compilation, but only if a high-resolution clock is available. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to compile a WebAssembly module. Recorded on each synchronous + WebAssembly compilation. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to asynchronously compile a WebAssembly module using streaming + compilation (via the 'WebAssembly.compileStreaming' API). Recorded on each + streaming WebAssembly compilation, but only if a high-resolution clock is + available. Note that compilation speed is often limited by the network + speed, which is also reflected in this metric. + + + + + bbudge@chromium.org + clemensb@chromium.org + adamk@chromium.org + + Time to asynchronously compile or deserialize a WebAssembly module during + streaming compilation (via the 'WebAssembly.compileStreaming' API). Recorded + on each streaming WebAssembly compilation or deserialization from the cache, + but only if a high-resolution clock is available. Note that compilation + speed is often limited by the network speed, which is also reflected in this + metric. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Size of a WebAssembly function in bytes. Recorded on each compilation of a + single function, either synchronous, asynchronous, or lazily. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Function count per WebAssembly module. Recorded for each WebAssembly module + which is decoded for validation, compilation, or deserialization. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to instantiate a WebAssembly module. Recorded on each instantiation of + a WebAssembly module. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + ecmziegler@chromium.org + adamk@chromium.org + ahaas@chromium.org + + Number of 64KiB pages a WebAssembly module declares as its maximum + requirement. Recorded on each instantiation of a WebAssembly module. + + + + + ecmziegler@chromium.org + adamk@chromium.org + ahaas@chromium.org + + The result of attempts to allocate WebAssembly.Memory buffers. Recorded on + each attempt to allocate a WebAssembly.Memory buffer. + + + + + ecmziegler@chromium.org + adamk@chromium.org + ahaas@chromium.org + + Number of 64KiB pages a WebAssembly module declares as its minimum + requirement. Recorded on each instantiation of a WebAssembly module. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The amount of generated code in MiB for one WebAssembly module. Recorded + when baseline compilation finished. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The amount of committed code space in MiB used by individual WebAssembly + modules. Recorded for each live module after each full GC. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The percentage of WebAssembly code freed by garbage collection (ratio of + total freed code to total generated code so far). Recorded for each live + module after each full GC. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The amount of generated code in MiB for one WebAssembly module. Recorded + when top-tier compilation finished. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Number of code GCs triggered per WebAssembly module. Recorded after each + code GC. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + The number of code spaces (i.e. individual reservations) of a WebAssembly + module. Recorded on every code space allocation. + + + + + ecmziegler@chromium.org + adamk@chromium.org + ahaas@chromium.org + + Size of the wire bytes of a WebAssembly module. Recorded for each + WebAssembly module which is decoded for validation, compilation, or + deserialization. + + + + + clemensb@chromium.org + ecmziegler@chromium.org + + Number of WebAssembly native modules live in a Wasm engine (typically per + process). Recorded whenever a new native module is created. + + + + + clemensb@chromium.org + ecmziegler@chromium.org + + Number of WebAssembly native modules live in an isolate. Recorded whenever a + new native module is created. + + + + + ecmziegler@chromium.org + adamk@chromium.org + clemensb@chromium.org + + Time to tier-up a WebAssembly module, i.e. the time between baseline + compilation finishes and top-tier compilation finishes. Recorded whenever an + asynchronously compiled module finishes top-tier compilation, but only if a + high-resolution clock is available. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/variations/histograms.xml b/tools/metrics/histograms/histograms_xml/variations/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..16d796e5d37aa37d7a5c1622367fe74dd2efbf3f --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/variations/histograms.xml @@ -0,0 +1,568 @@ + + + + + + + + + + rmcelrath@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + The time interval between when a WebView-using app's copy of the variations + seed was written to its local app storage and when it was loaded for use. + This is different from Variations.SeedFreshness because it measures + freshness from when the app received its copy of the seed, not when the seed + was originally downloaded. Written every time the browser process + initializes, but not if there was an error reading the seed, or no seed + existed. + + + + + rmcelrath@chromium.org + ntfschr@chromium.org + src/android_webview/OWNERS + + The result of checking if a WebView-using app's copy of the variations seed + is still fresh, or if a new seed should be requested. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The result of verifying if the variations seed is expired, recorded before + trials are created from the seed. Expired seeds are treated as not existing. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The latency of connection to the variations server when fetching an initial + variations seed during Android Chrome first run. This is included in the + Variations.FirstRun.SeedFetchTime measurement. Only considers cases where an + HTTP 200 result was received. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The result of attempting to fetch an initial variations seed during Android + Chrome first run. Records both the HTTP code and various error values in one + enumeration. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The latency of fetching an initial variations seed during Android Chrome + first run. Only considers cases where an HTTP 200 result was received. + + + + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Logs each event related to Android Chrome variations first run prefs to + debug crbug.com/1090968. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The result of attempting to import an initial variations seed during Android + Chrome first run. Logged from VariationsSeedStore::LoadSeed when seed prefs + do not exist. + + + + + caitlinfischer@google.com + src/base/metrics/OWNERS + + The owner of the top-level domain from which certain subframe-initiated HTTP + requests are made. It's logged after determining that (i) the request should + include variations headers, (ii) the request is from a subframe, and (iii) + TrustedParams are not present. It's logged before adding headers. It allows + us to verify whether non-render-thread-initiated requests, if any, lack + TrustedParams. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records number of experiment ids in the X-Client-Data header at the time the + header is constructed. + + + + + asvitkine@chromium.org + jwd@chromium.org + caitlinfischer@google.com + src/base/metrics/OWNERS + + Details about the request context in which an HTTP request is made. Logged + after determining that the request should include variations headers but + before adding the headers. + + + + + asvitkine@chromium.org + jwd@chromium.org + src/base/metrics/OWNERS + + The result of whether to append Variations headers to a request. Logged when + when determining (i) whether the URL to which the request is being sent + should have a variations header and (ii) whether--after a redirect--the + request to which a variations header was added should have the variations + header removed. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records how the country code saved in prefs used for filtering permanent + consistency studies compares to the country code in the variations seed. + This is recorded each time the saved country code is loaded from the pref. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The result of verifying the latest variations seed's signature, recorded + when the seed is loaded from Local State. Not recorded when running in safe + mode. + + + + + pastarmovj@chromium.org + ydago@chromium.org + src/base/metrics/OWNERS + + Records the restrictions on how experiment variations are applied on the + client. This is recorded at start up. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Number of previous requests to the variations server in the same session, + logged each time a new request is attempted to the variations server. For + example, the value of the 0th bucket indicates the number of initial + requests to the server that took place. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Counts the number of times the VariationsService is allowed or not allowed + to make a request due to the ResourceRequestAllowedNotifier. Useful for + debugging cases where variations seeds may not be getting fetched. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Whether or not the VariationsService fell back to Safe Mode, due to either + too many crashes or too many failures to fetch a new seed. Recorded during + Chrome startup, immediately before field trials are created. Only recorded + if either a recent or a safe seed was loaded successfully. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Records whether the safe variations seed was successfully read from local + state on startup. Records a detailed reason on read failure. Only recorded + when attempting to run in safe mode. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + The result of verifying the safe variations seed's signature, recorded when + the seed is loaded from Local State. Only recorded when attempting to run in + safe mode. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Records the result of storing a safe variations seed (and all associated + metadata) to the seed store. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + The result of verifying the safe variations seed's signature, recorded when + the safe seed is stored to Local State. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + The number of consecutive crashes observed by the VariationsService, without + a single intervening successful seed fetch. Recorded during Chrome startup, + when the VariationsService is created. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + The number of consecutive failed attempts to fetch a new seed by the + VariationsService. Recorded during Chrome startup, when the + VariationsService is created. + + + + + jwd@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Counts if a response from the variations server is the first response of the + day or not. This is counted when a new valid seed or a 304 is received. The + date line is computed in UTC and the times being compared are the server + time from the server response and the stored server time from the last + successful request. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + HTTP response codes and network error encountered by VariationsService when + attempting to fetch a variations seed from the server over an HTTPS + connection. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + HTTP response codes and network error encountered by VariationsService when + attempting to fetch a variations seed from the server over an HTTP + connection. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The time interval between when the variations seed was downloaded and when + it was loaded for use. Not recorded for expired seeds, nor when the download + time is unknown (typically, for seeds imported via first run). + + + + + changwan@chromium.org + src/base/metrics/OWNERS + + Records the time spent blocking WebView startup to wait for the variations + seed. This is less than the entire time needed to load the seed, since + startup is only blocked if loading is not complete by the time the seed is + needed. This would ideally have a maximum value equal to the timeout in + VariationsSeedLoader, but there is no actual limit on how late that timeout + could fire. This is logged once per WebView startup, whether or not loading + the seed was successful. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records whether the latest variations seed was successfully read from local + state on startup. Records a detailed reason on read failure. Not recorded + when running in safe mode. + + + + + isherman@chromium.org + asvitkine@chromium.org + src/base/metrics/OWNERS + + Records how long it takes to load and process variations seed. This metric + is recorded only when loading and processing of the seed is successful. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records the result of storing the variations seed that was received from the + server. Also logs the types of data received (gzip, delta, etc). + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records the time taken to perform variations seed simulation. + + Recorded on every variation seed simulation, which follows a fetch. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records the result of variations seed simulation. Logs the number of + experiment groups in the "kill best effort" category that are + expected to change on a restart of the browser with the received seed. + + Recorded on every variation seed simulation, which follows a fetch. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records the result of variations seed simulation. Logs the number of + experiment groups in the "kill critical" category that are + expected to change on a restart of the browser with the received seed. + + Recorded on every variation seed simulation, which follows a fetch. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Records the result of variations seed simulation. Logs the number of + experiment groups in the "normal" category that are expected to + change on a restart of the browser with the received seed. + + Recorded on every variation seed simulation, which follows a fetch. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The size of the variations seed data, which may be a partial (delta) or + compressed (gzip) payload, see Variations.SeedStoreResult. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The result of verifying the variations seed signature, recorded when the + variations seed is stored to Local State after being retrieved from the + server. + + + + + asvitkine@chromium.org + src/base/metrics/OWNERS + + Records the number of UI strings overriden for each study that overrides + strings. Recorded at start up when each study is evaluated. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + The time since the previous attempt to fetch the variations seed within the + same session, with 0 indicating that this is the first attempt. Recorded + when a variations seed fetch is attempted by the VariationsService. + + + + + asvitkine@chromium.org + rkaplow@chromium.org + src/base/metrics/OWNERS + + Log the user channel assigned at browser startup used for evaluating the + variations seeds. + + + + + rmcelrath@chromium.org + src/android_webview/OWNERS + + The result of a WebView seed download. Records both the HTTP code and + various error values in one enumeration. + + + + + rmcelrath@chromium.org + src/android_webview/OWNERS + + The duration of the network request to downloads a new WebView variations + seed from the variations server to the central on-device service. + + + + + rmcelrath@chromium.org + src/android_webview/OWNERS + + The time between the start of two consecutive WebView seed downloads by + WebView's service. This metric will not be written if seeds are never + downloaded. + + + + + rmcelrath@chromium.org + src/android_webview/OWNERS + + The delay between when a WebView seed download was scheduled by the service + with the JobScheduler and when it was executed. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/web_apk/histograms.xml b/tools/metrics/histograms/histograms_xml/web_apk/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..1f9165d450c214aeb196bb005f7f358e6e403fee --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/web_apk/histograms.xml @@ -0,0 +1,301 @@ + + + + + + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the available space that can be used when installing a WebAPK from + Google Play fails. The space recorded is the available space beyond the + system's minimum free space threshold, with a range between -1000 and 1000 + MB. Negative values mean that there is less free space available than the + system's minimum, by the given amount. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the available space that can be used when installing a WebAPK from + Google Play fails after freeing up cache. The space recorded is the + available space beyond the system's minimum free space threshold, with a + range between -1000 and 1000 MB. Negative values mean that there is less + free space available than the system's minimum, by the given amount. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the error code when installing a WebAPK from Google Play fails. See + go/webapk-install-googleplayerrorcode. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records whether installing a WebAPK from Google Play succeeded. If not, + records the reason that the install failed. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + How long it takes to install a WebAPK. The time is measured from the time + that the user initiates the install to the time that the Open button is + shown in the infobar. This metric is only recorded when install succeeds. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or + the add to homescreen menu item. This stat tracks WebAPK installation + events. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the amount of time which has elapsed from the "install infobar + showing" to the "install request being sent to Google Play". + This time includes the time that it takes to request the WebAPK token and + the time that it takes to compute the hashes for the launcher icon and the + badge icon. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the error codes when a WebAPK is launched with network failures. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Recorded each time that a WebAPK is navigated. Records whether the + navigation is within the scope of the WebAPK's Web Manifest. Not recorded + for child tabs - e.g. tabs opened via window.open() + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + When a WebAPK receives a notification, log whether it has permission to + display that notification. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + The length of a WebAPK session (launch/foregrounding to backgrounding) in + milliseconds. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records WebAPK "Shell APK version" when the WebAPK is launched. + The "Shell APK version" is documented in shell_apk_version.gni + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Tracks the time to splash screen visible starting from the launch of the + WebAPK shell (rather than from the launch of Chrome) for new-style WebAPKs. + The WebAPK shell displays the splash screen for new-style WebAPKs. + + This is recorded iff: - This is a cold startup of Chrome. - Chrome has not + been sent to the background since launch. - There was no recents entry for + Chrome (Android replays intents if a recents entry exists), which otherwise + adds noise/long-tail to this histogram. + + + + + mheikal@chromium.org + yfriedman@chromium.org + + Tracks the time to splashscreen hidden starting from the launch of the + WebAPK shell (rather than from the launch of Chrome). The splashscreen is + hidden after the first visually non-empty paint. + + This is recorded iff: - This is a cold startup of Chrome. - Chrome has not + been sent to the background since launch. - There was no recents entry for + Chrome (android replays intents if a recents entry exists), which otherwise + adds noise/long-tail to this histogram. + + + + + mheikal@chromium.org + yfriedman@chromium.org + + Tracks the time to splashscreen visible starting from the launch of the + WebAPK shell (rather than from the launch of Chrome). The splashscreen is + shown during postInflationStartup. + + This is recorded iff: - This is a cold startup of Chrome. - Chrome has not + been sent to the background since launch. - There was no recents entry for + Chrome (android replays intents if a recents entry exists), which otherwise + adds noise/long-tail to this histogram. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + Records that a WebAPK was uninstalled. + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records whether updating a WebAPK from Google Play succeeded. If not, + records the reason that the update failed. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the number of zombie "WebAPK update request" files that + the update process failed to cleanup. Recorded for all WebAPKs whenever a + WebAPK or webapp is launched. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the number of times that a WebAPK update request was queued (i.e. + waiting for the WebAPK to be backgrounded) before being sent to the server. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records the time point when a request to update a WebAPK is sent to the + WebAPK Server. + + + + + hartmanng@chromium.org + + src/chrome/android/java/src/org/chromium/chrome/browser/webapps/OWNERS + + + Records whether Chrome can bind to a WebAPK's "WebAPK service". + Recorded each time that Chrome attempts to bind to a WebAPK service. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/web_audio/histograms.xml b/tools/metrics/histograms/histograms_xml/web_audio/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..6e4ccfece179960b225afa3099ce00beb7a58473 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/web_audio/histograms.xml @@ -0,0 +1,270 @@ + + + + + + + + + + rtoy@chromium.org + hongchan@chromium.org + + The length (in frames) requested by createBuffer(). Recorded for every call + to createBuffer(). Probably many (tens or hundreds) per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The number of channels requested by createBuffer(). Recorded for every call + to createBuffer(). Probably many (tens or hundreds) per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The sample rate (in Hz) requested by createBuffer(). Recorded for every call + to createBuffer(). Probably many (tens or hundreds) per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The ratio of the buffer sample rate from createBuffer() to the context + sample rate. This indicates if the buffer needs to be resampled. Recorded + for every call to createBuffer(). Probably many (tens or hundreds) per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The hardware sample rate (in Hz) used by an AudioContext. Recorded for every + WebAudio AudioContext that is created; probably only one or two per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The maximum number of (hardware) channels available in an AudioContext. + Recorded for every WebAudio AudioContext that is created; probably only one + or two per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The sample rate requested by developer to be used as the sample rate when + constructing an AudioContext with an AudioContextOptions dictionary. This is + recorded for each AudioContext created, probably just one or two per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The ratio of the user-selected sample rate to the hardware sample rate of an + AudioContext. The ratio is represented as a percentage. This is recorded for + each AudioContext created, probably just one or two per page. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The callback buffer size (in audio frames) for WebAudio rendering between + the WebAudio graph and the audio device thread. This can differ from the + value recommended by the audio hardware due to internal constraints in + WebAudio. Recorded for every WebAudio AudioContext that is created. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The buffer size (in audio frames) for WebAudio rendering recommended by the + audio hardware. Recorded for every WebAudio AudioContext that is created. + + + + + mlamouri@google.com + media-dev@chromium.org + rtoy@chromium.org + hongchan@chromium.org + + The autoplay status of an AudioContext when destroyed. This include all + types of frames. In order to know the value only for main frames, the + .CrossOrigin values can be substracted. + + + + + mlamouri@google.com + media-dev@chromium.org + rtoy@chromium.org + hongchan@chromium.org + + The autoplay status of an AudioContext when destroyed in a cross-origin + frame. + + + + + mlamouri@google.com + media-dev@chromium.org + rtoy@chromium.org + hongchan@chromium.org + + Records how an AudioContext was unlocked (if it was). This is recorded when + the AudioContext is destroyed. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The type of the BiquadFilterNode. Recorded each time the type is set. This + recorded once (to lowpass) when a biquad filter is created and also recorded + whenever the filter type changes due to user action or programatically. It + is unlikely the type will change more than once. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The duration in millisec of impulse responses for a ConvolverNode. Recorded + each time the impulse response is set for a ConvolverNode. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The order of the WebAudio IIRFilterNode. The order is one less than the + number of feedback coefficients used in the denominator of the IIRFilter + transfer function. Recorded each time an IIRFilter is constructed. + + + + + rtoy@chromium.org + hongchan@chromium.org + + The number of channels specified for the offline audio context. Recorded for + every offline context created. Probably only a few per page, but could be + potentially much more (thousands). + + + + + rtoy@chromium.org + hongchan@chromium.org + + The length (in frames) specified for the offline audio context. Recorded for + every offline context created. Probably only a few per page, but could be + potentially much more (thousands). + + + + + rtoy@chromium.org + hongchan@chromium.org + + The sample rate (in Hz) specified for the offline audio context. Recorded + for every offline context created. Probably only a few per page, but could + be potentially much more (thousands). + + + + + rtoy@chromium.org + hongchan@chromium.org + + The panning model for the PannerNode. Recorded once with the default value + at creation and once again whenver it is changed. Once changed, it is + unlikely to be changed again. If there are any PannerNodes created at all, + then there is probably one for each source (AudioBufferSourceNode, + OscillatorNode, or other source). + + + + + rtoy@chromium.org + hongchan@chromium.org + + Captures if WebAudio caused glitches or not due to the FIFO underflow. It is + recorded when PushPullFIFO is destroyed. (e.g. navigating away from the + page.) + + + + + rtoy@chromium.org + hongchan@chromium.org + + Percentage of FIFO underflow happened due to the the missed deadline of + WebAudio rendering engine. It is recorded when PushPullFIFO is destroyed. + (e.g. navigating away from the page.) + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/web_core/histograms.xml b/tools/metrics/histograms/histograms_xml/web_core/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..4c443f64ba56d13417e0d68f39245ceb723127a1 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/web_core/histograms.xml @@ -0,0 +1,829 @@ + + + + + + + + + + wychen@chromium.org + gilmanmh@google.com + + The time spent on collecting the statistics of the document in the main + frame. These statistics would be used as features to classify whether the + page is suitable for DOM distiller. + + Warning: This metric may include reports from clients with low-resolution + clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports + will cause this metric to have an abnormal distribution. When considering + revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the + solution. + + + + + yoichio@chromium.org + + Counts the number of times each document.execCommand is executed. This + doesn't count commands not supported by Blink. + + + + + yoichio@chromium.org + + Counts the number of times each Editor::Command::execute is called. This + doesn't count commands not supported by Blink. + + + + + rakina@chromium.org + altimin@chromium.org + + Records the number of find-in-page tasks executed for a find-in-page + request. Emitted when a find-in-page request is finished (it went through + the whole document) or when it got aborted. + + + + + rakina@chromium.org + altimin@chromium.org + + Records how long one find-in-page request (consisting multiple tasks) took + from the request start until the last find-in-page task for the request + finished. Emitted when a find-in-page request is finished (it went through + the whole document) or when it got aborted. + + + + + rakina@chromium.org + altimin@chromium.org + + Records how long one find-in-page task took from invocation start to end. + Emitted when a find-in-page task finished running. + + + + + rakina@chromium.org + altimin@chromium.org + + Records the total task duration of all of the find-in-page tasks for one + find-in-page request. Nothe that this does not include the time spent in + between tasks. Emitted when a find-in-page request is finished (it went + through the whole document) or when it got aborted. + + + + + csharrison@chromium.org + japhet@chromium.org + + The position of the URL in the framebust UI list (desktop only) when it is + clicked. Note that this UI surface is shared with the tab-under + intervention, so elements in the list could come from either features. This + metric will only be logged when a URL from the framebust (3p redirect) + intervention is clicked. + + + + + csharrison@chromium.org + japhet@chromium.org + + The (android only) outcome of a particular framebust infobar. Recorded when + the user either closes the infobar or declines the intervention by clicking + the link. + + + + + yoavweiss@chromium.org + csharrison@chromium.org + + Time in which non-AppCache requests have been delayed after being discovered + by the HTMLPreloadScanner, due to document element not being yet available, + which is required for AppCache support. Recorded per document. + + + + + yoavweiss@chromium.org + csharrison@chromium.org + + Time in which non-AppCache requests have been delayed after being discovered + by the HTMLPreloadScanner, due to document element not being yet available, + which is required for AppCache support. Recorded per document, but applies + only to main frames. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records actions that take place in IndexedDB. These stats are used for + normalization in formulas. See go/chrome-indexeddb-heartbeat + + + + + dmurph@chromium.org + pwnall@chromium.org + + Methods that encountered consistency errors. Such errors probably point to a + bug in our code. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the result of trying to delete an IndexedDB database, per the user + using the IDBFactory::DeleteDatabase API. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the result of the FIRST attempt at opening the backing store for + IndexedDB (i.e. retries are ignored). This is recorded when an API call + needs to open the backing store (if it isn't already opened). API calls that + can open the backing store are: IDBFactory::Open, GetDatabaseNames, + GetDatabaseInfo, and DeleteDatabase. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the time that it takes to open IndexedDB's backing store. This is + only recorded if the backing store was opened successfully on the first + attempt. + + + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Count of the different success and failure modes when opening an IndexedDB + backing store - clean open, successful open with recovery, failed recovery, + etc. Includes all hosts. + + + + + + + dmurph@chromium.org + pwnall@chromium.org + + Count of the different success and failure modes when opening an IndexedDB + backing store - clean open, successful open with recovery, failed recovery, + etc. Only for docs.google.com. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Length of leveldb directories that cause paths to not fit in the filesystem, + either because the individual component is too long or the overall path is + larger than MAX_PATH. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Methods that encountered leveldb errors while trying to read from disk. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Methods that encountered leveldb errors while trying to write to disk. + + + + + cmumford@chromium.org + The reason that a forced-close of a backing store occurred. + + + + dmurph@chromium.org + pwnall@chromium.org + + Number of outstanding transactions (running, blocked) in database when a new + transaction is created. + + + + + cmumford@chromium.org + + Count of the results when attempting to destroy a corrupt Indexed DB backing + store. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Recorded when there is an error during the force close of IndexedDB for an + origin. A force close can be triggered either from DevTools, or when there + is a disk error. Errors during force close are ignored, as the system is + already being torn down. This metric is the only record of these errors + happening. + + + + + cmumford@chromium.org + + The time that it takes to close IndexedDB's LevelDB backing store. + + + + + cmumford@chromium.org + + The time that it takes to open IndexedDB's LevelDB backing store. + + + + + cmumford@chromium.org + + The time that it takes to write data to an IndexedDB's LevelDB backing + store. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Error classes returned by LevelDB when it failed to open a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Errors (base::File::Error) encountered by a single LevelDBEnv method when + opening an IndexedDB instance. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Types of corruption that LevelDB encounters when opening a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + LevelDBEnv methods that generated IO errors when opening a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Error classes returned by LevelDB when it failed to read a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Errors (base::File::Error) encountered by a single LevelDBEnv method when + reading from an IndexedDB instance. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Types of corruption that LevelDB encounters when reading a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + LevelDBEnv methods that generated IO errors when reading a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Error classes returned by LevelDB when it failed to write to a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Errors (base::File::Error) encountered by a single LevelDBEnv method when + writing to an IndexedDB instance. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Types of corruption returned by LevelDB when it failed to write to a + database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + LevelDBEnv methods that generated IO errors when writing to a database. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the full time it takes to open a database that isn't open yet (so + files are loaded from disk, metadata checked, etc). The measurement happens + when a website calls "indexedDB.open", and records the time it + takes from when this method is called to when the onsuccess event (or + onupgradeneeded event, in the case of a database upgrade) is dispatched. See + WebCore.IndexedDB.OpenTime.Warm for the time it takes an already-loaded + database to load. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the full time it takes to open an already-open database. The + measurement happens when a website calls "indexedDB.open", and + records the time it takes from when this method is called to when the + onsuccess event (or onupgradeneeded event, in the case of a database + upgrade) is dispatched. See WebCore.IndexedDB.OpenTime.Cold for the time it + takes to open a database that is not open yet. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The number of blobs being saved in an IndexedDB object store 'put' + operation. Recorded for every 'put' operation. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The total size of the blobs being saved in an IndexedDB object store 'put' + operation. Recorded for every 'put' operation, except when there are no + attached blobs or a blob has an unknown size. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The size of the IndexedDB key used in an IndexedDB object store 'put' + operation. Recorded for every 'put' operation. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The size of the IndexedDB value used in an IndexedDB object store 'put' + operation. Recorded for every 'put' operation. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records if a v2 schema has blob keys in the database, which means the + database is corrupt. These databases will eventually be wiped as corrupt. + Recorded when the IndexedDB backing store for an origin is first opened, + which happens when a IndexedDB database connection is opened or when + database names are fetched. Note: The backing store stays alive for + subsequent connections, and sticks around for a couple seconds after the + last connection is closed. See WebCore.IndexedDB.SchemaV2HasBlobs.Docs for + the Docs-only version. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records if a v2 schema has blob keys in the database, which means the + database is corrupt. These databases will eventually be wiped as corrupt. + Recorded when the IndexedDB backing store for an origin is first opened, + which happens when a IndexedDB database connection is opened or when + database names are fetched. Note: The backing store stays alive for + subsequent connections, and sticks around for a couple seconds after the + last connection is closed. Only for docs.google.com. Note that these samples + will also be recorded in WebCore.IndexedDB.SchemaV2HasBlobs. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the schema version of the IndexedDB database read from disk. + Recorded when the IndexedDB backing store for an origin is first opened, + which happens when a IndexedDB database connection is opened or when + database names are fetched. Note: The backing store stays alive for + subsequent connections, and sticks around for a couple seconds after the + last connection is closed. See WebCore.IndexedDB.SchemaVersion.Docs for the + Docs-only version. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the schema version of the IndexedDB database read from disk. + Recorded when the IndexedDB backing store for an origin is first opened, + which happens when a IndexedDB database connection is opened or when + database names are fetched. Note: The backing store stays alive for + subsequent connections, and sticks around for a couple seconds after the + last connection is closed. Only for docs.google.com. Note that these samples + will also be recorded in WebCore.IndexedDB.SchemaVersion. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the total size of tombstones deleted by the IndexedDB Tombstone + Sweeper. Recorded on the browser side (back end) when the sweeper has + completed scanning and it is in the 'deletion' mode. See + https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the time it takes for the IndexedDB Tombstone Sweeper to commit + tombstone deletions. Recorded on the browser side (back end) when the + sweeper has completed a round of sweeping and, it's in 'deletion' mode, and + it has tombstones to delete. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the time it takes for the IndexedDB Tombstone Sweeper to fully sweep + the indexes. Recorded on the browser side (back end) when the sweeper has + completed sweeping all indexes (so partial sweeps are not recorded) and it + is in 'deletion' mode. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records when an error occurs during deletion of index tombstones by the + IndexedDB Tombstone Sweeper. Recorded on the browser side (back end) when + the sweeper has completed a round of sweeping and, it's in 'deletion' mode, + and it has tombstones to delete. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper + has completed scanning. Records the percentage of the indexes the scanner + fully scanned before it was stopped. To reduce the number of buckets, the + recorded value is the percentage divided by 5. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Records the number of tombstones deleted by the IndexedDB Tombstone Sweeper. + Recorded on the browser side (back end) when the sweeper has completed + scanning and it is in 'deletion' mode. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper + encounters an error while sweeping. See https://goo.gl/coKwA7. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The total temporary size of an IndexedDB ReadOnly Transaction. Since this is + a readonly transaction, the size should only be >0 when the transaction + is removing tombstone index keys. Recorded on transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The time it takes for an IndexedDB ReadOnly Transaction to commit, starting + from when it starts executing tasks (when it is scheduled). Recorded on + transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The total temporary size of an IndexedDB ReadWrite Transaction. This is the + memory that is temporarily stored before writing to disk. Recorded on + transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The time it takes for an IndexedDB ReadWrite Transaction to commit, starting + from when it starts executing tasks (when it is scheduled). Recorded on + transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The total temporary size of an IndexedDB VersionChange Transaction. This is + the memory that is temporarily stored before writing to disk. Version change + transactions happen when creating a database or updating a current database + schema. Recorded on transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + The time it takes for an IndexedDB VersionChange Transaction to commit, + starting from when it starts executing tasks (when it is scheduled). Version + change transactions happen when creating a database or updating a current + database schema. Recorded on transaction commit. + + + + + dmurph@chromium.org + pwnall@chromium.org + + Recorded on the browser side (back end) when an IndexedDB transaction is + aborted, specifically recording the reason for the abort. This can be + triggered by javascript code on the renderer, errors or force closes on the + backend, or by the transaction timeout timer. + + + + + clamy@chromium.org + + The resulting action (e.g. load resource, use resource from in-memory + cache...) upon a resource request. + + + + + clamy@chromium.org + + Whether the resource in the cache is being used by at least one client (live + resource) or not (dead resource) upon a cache hit. + + + + + leszeks@chromium.org + v8-runtime@google.com + Reason for not streaming an async script. + + + + leszeks@chromium.org + v8-runtime@google.com + Whether an async script was streamed or not. + + + + leszeks@chromium.org + v8-runtime@google.com + Reason for not streaming a deferred script. + + + + leszeks@chromium.org + v8-runtime@google.com + Whether a deferred script was streamed or not. + + + + leszeks@chromium.org + v8-runtime@google.com + + Reason for not streaming an other (not async, deferred or parser blocking) + script. + + + + + leszeks@chromium.org + v8-runtime@google.com + + Whether an other (not async, deferred or parser blocking) script was + streamed or not. + + + + + leszeks@chromium.org + v8-runtime@google.com + Reason for not streaming a parsing blocking script. + + + + leszeks@chromium.org + v8-runtime@google.com + Whether a parsing blocking script was streamed or not. + + + + yhirano@chromium.org + ricea@chromium.org + + Count the number of send() method calls on WebSockets for each argument + type. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/web_rtc/histograms.xml b/tools/metrics/histograms/histograms_xml/web_rtc/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..278c14857a34b99c2589d70f446983cb5b87d9d6 --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/web_rtc/histograms.xml @@ -0,0 +1,3300 @@ + + + + + + + + + + grunell@chromium.org + minyue@chromium.org + + The percentage of measurement periods during a capture stream's lifetime + when the echo canceler's filter is considered to have diverged at least + once. A diverged filter could mean that there was echo och ducking + experienced. The measurement period size is fixed and in the order of one + second. The first measurement period is larger, typically 2-3 seconds. + Capture streams with shorter lifetimes (i.e. no data available) are not + recorded here. + + + + + guoweis@chromium.org + + The maximum consecutive discarded bytes caused by not enough buffer + available in WebRTC's socket implementation. This happens when WebRTC + IpcPacketSocket's throttling mechanism kicks in. The maximum bucket is + expanded from previous version to provide more insight when upper layer + feeds a lot of packets. + + + + + guoweis@chromium.org + + The percentage of packets discarded by WebRTC's socket layer due to + EWOULDBLOCKs when WebRTC IpcPacketSocket's throttling mechanism kicks in. + + + + + aleloi@chromium.org + + Logs adaptive digital compression gain that is applied by AgcManagerDirect. + A log call is made once per second. The compression gain is applied to the + microphone signal at the end of the processing chain. + + + + + aleloi@chromium.org + + Logs adaptive digital compression gain that is applied by AgcManagerDirect. + A log call is made every time the gain changes. The compression gain is + applied to the microphone signal at the end of the processing chain. + + + + + aleloi@chromium.org + + Logs adaptive digital compression gain that is applied by + AdaptiveDigitalGainApplier in GainController2. A log call is made once per + second. The compression gain is applied to the microphone signal at the end + of the processing chain. + + + + + aleloi@chromium.org + + This histogram reports the noise level estimation done in GainController2. A + value is reported every second. The unit is inverted dBFS. The scale goes + from 0 (very loud noise) to 100 (very faint noise). + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Identity' region. In this region no attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in + GainController2. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Knee' region. In this region some attenuating gain is applied. + This metric is logged from the Fixed Digital limiter in GainController2. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Limiter' region. In this region some more attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in + GainController2. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Saturation' region. In this region much attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in + GainController2. + + + + + hlundin@chromium.org + + The automatic gain control (AGC) in WebRTC tries to adjust the microphone + gain to maintain a strong audio level, but without clipping (saturation). + The histogram will log a value every time input clipping is detected. The + value is a boolean, with "true" meaning that the gain was in fact + adjusted in response to the detected clipping, and "false" meaning + that adjustment was not allowed due to limiting boundaries in the algorithm. + + + + + hlundin@chromium.org + + The automatic gain control (AGC) in WebRTC tries to adjust the microphone + gain to maintain a strong audio level, but without clipping (saturation). + The histogram will log a new value every time the AGC changes the target + level. + + + + + hlundin@chromium.org + + This histogram reports the average RMS of the signal coming in to WebRTC's + Audio Processing Module, prior to any WebRTC processing. A new value is + reported every 10 seconds, and the average is over the latest interval. The + metric is negated dBFS, meaning that 0 is a full-scale signal, while 127 + corresponds to -127 dBFS (very faint). + + + + + hlundin@chromium.org + + This histogram reports the peak RMS of the signal coming in to WebRTC's + Audio Processing Module, prior to any WebRTC processing. A new value is + reported every 10 seconds, and the peak is the RMS of the strongest 10 ms + block over the latest interval. The metric is negated dBFS, meaning that 0 + is a full-scale signal, while 127 corresponds to -127 dBFS (very faint). + + + + + peah@chromium.org + + This histogram reports the average RMS of the signal in the output of + WebRTC's Audio Processing Module, after all audio WebRTC processing. A new + value is reported every 10 seconds, and the average is over the latest + interval. The metric is negated dBFS, meaning that 0 is a full-scale signal, + while 127 corresponds to -127 dBFS (very faint). + + + + + peah@chromium.org + + This histogram reports the peak RMS of the signal in the output of WebRTC's + Audio Processing Module, after all WebRTC audio processing. A new value is + reported every 10 seconds, and the peak is the RMS of the strongest 10 ms + block over the latest interval. The metric is negated dBFS, meaning that 0 + is a full-scale signal, while 127 corresponds to -127 dBFS (very faint). + + + + + hlundin@chromium.org + ivoc@chromium.org + + Measures the duration of each audio interruption event. An audio + interruption is defined as a loss concealment (a.k.a. expand) event that + lasts more than 150 milliseconds. The metric registers each of these events. + This gives an indication of the length and prevalence of severe network + events, which are likely to be detrimental to the audio quality. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Identity' region. In this region no attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in the Audio + Mixer. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Knee' region. In this region some attenuating gain is applied. + This metric is logged from the Fixed Digital limiter in the Audio Mixer. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Limiter' region. In this region some more attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in the Audio + Mixer. + + + + + aleloi@chromium.org + + The Fixed-Digital part of the AGC protects from saturation by reducing the + level of too loud signals. This metric shows how long the level estimate + stays in the 'Saturation' region. In this region much attenuating gain is + applied. This metric is logged from the Fixed Digital limiter in the Audio + Mixer. + + + + + aleloi@chromium.org + + Reports the sampling rate at which audio mixing is done. Lower rates result + in faster processing, higher rates can give higher quality. + + + + + aleloi@chromium.org + + Reports the number of active incoming streams in the WebRTC audio mixer. An + incoming stream is active if it is not muted. When multiple sterams are + active, adding them can result in saturation and limiting is needed. + + + + + aleloi@chromium.org + + Reports the number of streams in the WebRTC audio mixer. The mixer queries + all streams for audio and preferred sampling rate. The number of streams + affects mixing decisions. Whether to mix in floating points or use a limiter + depends on the number of incoming streams. + + + + + hlundin@chromium.org + + Measures the average waiting time in the buffer for each packet. The waiting + time is the time elapsed from the packet arrives until it is decoded. The + metric is calculated as the average over one minute, and is logged at the + end of each such interval. A well tuned target buffer level should lead to a + low value. + + + + + hlundin@chromium.org + + Measures the duration of each packet loss concealment (a.k.a. expand) event + that is not followed by a merge operation. The outage is measured in + milliseconds, with a range between 0 and 2000 ms. This gives an indication + of how well the jitter buffer's level adaptation is working. If the chosen + target level is too low, this value will increase. + + + + + hlundin@chromium.org + + Counts the number of delayed packet outage events per minute. The range is + between 0 and 100 (corresponds to more 1.6 events per second). See + WebRTC.Audio.DelayedPacketOutageEventMs for the definition of a delayed + packet outage event, and the interpretation of such events. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs a value indicating whether the WebRTC echo canceller + detects that there is active content in the render signal. A new value is + logged every 10 seconds and the logged value is averaged over this period. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the applied render buffer delay used in the WebRTC echo + canceller. A new value is logged every 10 seconds and the logged value + constitutes the current buffer delay at the time when the value is logged. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs a value every time the WebRTC echo canceller has + detected saturation in the capture signal. A new value is logged every 10 + seconds and the logged value indicates whether the capture signal has been + saturated during the last 10 seconds. + + + + + gustaf@chromium.org + peah@chromium.org + + This histogram logs whether clockdrift is detected in the WebRTC echo + canceller. A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the frequency of echo path delay changes that are + detected by the delay estimator in the WebRTC echo canceller. A new value is + logged every 10 seconds and the logged value indicates how frequent delay + changes have been during the last 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the estimated echo path delay in 64 sample blocks as + seen by the delay estimator in the WebRTC echo canceller. A new value is + logged every 10 seconds and the logged value is the estimate of the delay of + the echo path at the time when the value is logged. + + + + + gustaf@chromium.org + peah@chromium.org + + This histogram logs the echo return loss achieved by the WebRTC echo + canceller as described in ITU G.168. When the echo canceller is being used, + one value is logged every 10 seconds per ongoing WebRTC call. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the echo return loss achieved by the WebRTC echo + canceller in the lower 4 kHz. A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the echo return loss achieved by the WebRTC echo + canceller between 4 and 8 kHz. A new value is logged every 10 seconds. + + + + + gustaf@chromium.org + peah@chromium.org + + This histogram logs the echo return loss enhancement achieved by the WebRTC + echo canceller as described in ITU G.168. When the echo canceller is being + used, one value is logged every 10 seconds per ongoing WebRTC call. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the echo return loss enhancement achieved by the WebRTC + echo canceller in the lower 4 kHz. A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the echo return loss enhancement achieved by the WebRTC + echo canceller between 4 and 8 kHz. A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the estimated echo path delay in 64 sample blocks as + seen by the linear filter delay in the WebRTC echo canceller. The value 0 + means that no delay could be estimated from the linear filter, otherwise the + logged delay corresponds to the actual delay + 1. A new value is logged + every 10 seconds and the logged value is the estimate of the filter delay at + the time when the value is logged. + + + + + peah@chromium.org + gustaf@chromium.org + + This histogram logs the observed maximum number of capture API calls in a + row in the unit of frames (10 ms). A new value is logged every 10 seconds. + + + + + peah@chromium.org + gustaf@chromium.org + + This histogram logs the observed maximum number of render API calls in a row + in the unit of frames (10 ms). A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the number of times per minute that the WebRTC echo + canceller detects a shift in the skew between the total number of render and + capture calls. The metric is reported once per minute and the report is done + also for the case of 0 detected skew shifts have been detected. The amount + of skew shifts per minute is capped to 20. The metric is reported separately + for each render process. The metric is only reported for render processes + where the WebRTC echo canceller is active in and there is both audio being + played out and captured simultaneously. The reporting is only done when the + browser is awake. + + + + + peah@chromium.org + gustaf@chromium.org + + This histogram logs the observed minimum number of capture API calls in a + row in the unit of frames (10 ms). A new value is logged every 10 seconds. + + + + + peah@chromium.org + gustaf@chromium.org + + This histogram logs the observed minimum number of render API calls in a row + in the unit of frames (10 ms). A new value is logged every 10 seconds. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs a value every time the WebRTC echo canceller deems that + echo path is possible to model using any of the the echo canceller echo path + models. A new value is logged every 10 seconds and the logged value is the + feasibility assessment at the time when the value is logged. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the assessed reliability of the delay estimates produced + by the delay estimator in the WebRTC echo canceller. A new value is logged + every 10 seconds and the logged value is a meausure based on how often + during that period the delay estimate was reliable. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the frequency of overruns in the render buffer of the + WebRTC echo canceller. A new value is logged every 10 seconds and the logged + value is a meausure that indicates how often overruns occurred. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs the frequency of underruns in the render buffer of the + WebRTC echo canceller. A new value is logged every 10 seconds and the logged + value is a meausure that indicates how often underruns occurred. + + + + + peah@chromium.org + saza@chromium.org + + This histogram logs a value every time the WebRTC echo canceller deems that + the linear filter in the echo canceller is sufficiently well adapted to be + usable. A new value is logged every 10 seconds and the logged value is the + assessment of whether the filter is usable at the time when the value is + logged. + + + + + aleloi@chromium.org + + Histogram of audio codec usage. Every sample corresponds to 5 seconds of + encoding with that codec. + + + + + hlundin@chromium.org + + Measures the expand rate for an incoming WebRTC audio stream. The expand + rate is the fraction of samples that are generated through loss-concealemnt + algorithms instead of being decoded from incoming media packets. The metric + is calculated as the percent over a 10 second internval, and is logged at + the end of each such interval. + + + + + minyue@chromium.org + + Frequency that audio packets hits the capacity of WebRTC jitter buffer. A + larger value indicates that the capacity is not big enough, and/or audio + packets are not processed quickly enough. The metric is recorded every + minute. + + + + + hlundin@chromium.org + + The sound card's buffering delay for the receiving side. Sampled once every + 10 ms when WebRTC audio is playing. + + + + + hlundin@chromium.org + + The jitter buffer delay for the receiving side. Sampled once every 10 ms + when WebRTC audio is playing. + + + + + hlundin@chromium.org + ivoc@chromium.org + + The estimated likelihood percentage of echo as detected by the residual echo + detector. The residual echo detector can be used to detect cases where the + AEC (hardware or software) is not functioning properly. The detector can be + non-causal and operates on larger timescales with more delay than the + regular AEC. + + + + + hlundin@chromium.org + + Measures the audible expand rate for an incoming WebRTC audio stream. The + metric is very similar to WebRTC.Audio.ExpandRate, with the difference that + this metric only reports loss-concealement that generates audible samples. + The metric is calculated as the percent over a 10 second internval, and is + logged at the end of each such interval. + + + + + hlundin@chromium.org + + The target bitrate in kbps that the audio codec should try to produce on + average. Sampled every time the rate is updated. + + + + + hlundin@chromium.org + + The target jitter buffer delay for the receiving side. Sampled once every 10 + ms per WebRTC receive stream when WebRTC audio is playing. + + + + + henrika@chromium.org + webrtc-audio@google.com + Audio input channel layout in WebRTC. + + + + henrika@chromium.org + Audio input sample rate for WebRTC (in Hz). + + + + henrika@chromium.org + webrtc-audio@google.com + + Audio input sample rate for WebRTC (atypical values, in Hz). + + + + + henrika@chromium.org + webrtc-audio@google.com + Audio output sample rate for WebRTC (in Hz). + + + + henrika@chromium.org + webrtc-audio@google.com + + Audio output sample rate for WebRTC (atypical values, in Hz). + + + + + holmer@chromium.org + The bandwidth estimate 2 seconds into a WebRTC call. + + + + holmer@chromium.org + + The number of video packets lost durig the first 2 seconds in a WebRTC call. + + + + + holmer@chromium.org + + The round-trip time as measured 2 seconds into a WebRTC call. + + + + + holmer@chromium.org + + The difference between the bandwidth estimate at 2 seconds and 20 seconds + into a WebRTC call, with a min at 0, which is supposed to capture the how + much the initial bandwidth estimate overshot the actual bandwidth available. + + + + + philipel@chromium.org + + The bitrate that will be probed, triggered by an update to the max + configured bitrate. + + + + + philipel@chromium.org + + The resulting bitrate probed, triggered by an update to the max configured + bitrate. + + + + + philipel@chromium.org + + A successful probing attempt for a given bitrate, triggered by an update to + the max configured bitrate. NOTE! This is not the resulting bitrate from a + probing attempt, see WebRTC.BWE.MidCallProbing.ProbedKbps. + + + + + jonasolsson@chromium.org + crodbro@chromium.org + + The size in bytes of the probe cluster. Counted for each cluster once all + its packets have been sent. + + + + + jonasolsson@chromium.org + crodbro@chromium.org + + The size in packets of the probe cluster. Counted for each cluster once all + its packets have been sent. + + + + + jonasolsson@chromium.org + crodbro@chromium.org + + The time from sending the first to the last packet of the probe cluster. + Counted for each cluster once all its packets have been sent. + + + + + jonasolsson@chromium.org + crodbro@chromium.org + + Counts the amount of probe clusters that timed out. Counted when the prober + is destroyed. + + + + + jonasolsson@chromium.org + crodbro@chromium.org + + Counts the amount of probe clusters that the bitrate prober created. Counted + when the prober is destroyed. + + + + + holmer@chromium.org + + The time it takes the estimated bandwidth to reach 1000 kbps from the first + RTCP packet received. Used to measure the bandwidth ramp-up time. + + + + + holmer@chromium.org + + The time it takes the estimated bandwidth to reach 2000 kbps from the first + RTCP packet received. Used to measure the bandwidth ramp-up time. + + + + + holmer@chromium.org + + The time it takes the estimated bandwidth to reach 500 kbps from the first + RTCP packet received. Used to measure the bandwidth ramp-up time. + + + + + holmer@chromium.org + + The bandwidth estimation used in WebRTC calls. Records whether the BWE is + running on the sender or the receiver and what BWE related RTP header + extensions are in use. + + + + + holmer@chromium.org + + Average audio bitrate received during a call, counted from first packet + received until Call instance is destroyed. Only mesured for calls that are + at least 10 seconds long. + + + + + holmer@chromium.org + + Average total bitrate received during a call (audio + video + RTCP), counted + from first packet received until Call instance is destroyed. Only mesured + for calls that are at least 10 seconds long. + + + + + holmer@chromium.org + + Average estimated send bitrate during a call, counted from first packet sent + until Call instance is destroyed. Only mesured for calls that are at least + 10 seconds long. + + + + + asapersson@chromium.org + + The lifetime of a call. Recorded when a Call instance is destroyed. + + + + + holmer@chromium.org + + Average pacer bitrate during a call, counted from first packet sent until + Call instance is destroyed. Only mesured for calls that are at least 10 + seconds long. + + + + + holmer@chromium.org + + Average RTCP bitrate received during a call, counted from first packet + received until Call instance is destroyed. Only mesured for calls that are + at least 10 seconds long. + + + + + saza@chromium.org + + The amount of time between the arrival of the first and last audio RTP + packets to pass through a Call object. This is logged when the Call object + is destroyed. This is only logged if audio RTP packets are at some point in + time received, and is a way to omit temporary objects that do not send any + actual media. + + + + + saza@chromium.org + + The amount of time between the arrival of the first and last video RTP + packets to pass through a Call object. This is logged when the Call object + is destroyed. This is only logged if video RTP packets are at some point in + time received, and is a way to omit temporary objects that do not send any + actual media. + + + + + holmer@chromium.org + + Average video bitrate received during a call, counted from first packet + received until Call instance is destroyed. Only mesured for calls that are + at least 10 seconds long. + + + + + perkj@chromium.org + + Counters on creation, opening, and a few main attributes of data channels. + + + + + perkj@chromium.org + + The maximum number of retransmissions that are attempted in unreliable mode. + It is set to the value used in the configuration when a RTCDataChannel is + created. + + + + + perkj@chromium.org + + The length of the time window during which transmissions and retransmissions + may occur in unreliable mode. It is set to the value used in the + configuration when a RTCDataChannel is created. + + + + + guidou@chromium.org + marinaciocea@chromium.org + armax@chromium.org + + Counters on creation of DesktopCaptureDevice and the first capture call. + + + + + zhihuang@chromium.org + + Counters on different types of TCP socket error code. Collected when we hit + the error code when writing. + + + + + zhihuang@chromium.org + + Counters on different types of UDP socket error code. Collected when we hit + the error code when writing. + + + + + reillyg@chromium.org + device-dev@chromium.org + + Records whether a user would potentially see a permission prompt for moving + the camera. It is recorded when showing a camera permission prompt + regardless of whether or not the site requested camera movement. + + + + + guoweis@chromium.org + + Counters on various types of NAT observed. This is logged once per session. + + + + + perkj@chromium.org + + Number of data channels created per PeerConnection. Sample added to the + histogram when the PeerConnection is destroyed. Note that this is done + purely on the renderer side, so no sample will be generated when the + renderer process is destroyed (as in the fast shutdown path for the + renderer) before the PeerConnection is destroyed. + + + + + hta@chromium.org + webrtc-dev@chromium.org + + Outcomes of adding ICE candidates to a PeerConnection. Used to check the + theory that failures in candidate addition are ignored by applications. + + + + + qingsi@google.com + jeroendb@google.com + + Counters of various ICE Endpoint types. These values are logged for the + first selected candidate pair of a PeerConnection. + + + + + qingsi@google.com + jeroendb@google.com + + Counters of ICE Connection states. These values are logged when the + PeerConnection gets into that state for the first time or after the ICE + restart. + + + + + zhihuang@chromium.org + + Records the error whenever the Dtls handshake fails. There are only two + types of errors, incompatitable cipher suite and unknown error, for now. + + + + + honghaiz@chromium.org + Records the reasons for ICE re-gathering. + + + + honghaiz@chromium.org + + Records the transport channel states when ICE restart happens. + + + + + qingsi@google.com + jeroendb@google.com + + Counters on IPv4 and IPv6 usage in PeerConnection. These values are logged + once per PeerConnection. + + + + + qingsi@google.com + jeroendb@google.com + + Whether the permission to collect the local IP addresses in WebRTC has been + requested and/or granted. This is collected the first time when networks + updated event is reported or if never reported, during the destruction phase + of a call. + + + + + qingsi@google.com + jeroendb@google.com + + Number of IPv4 network interfaces discovered in a PeerConnection Session. + + + + + qingsi@google.com + jeroendb@google.com + + Number of IPv4 local Candidates gathered in a PeerConnection Session once + the ICE address gathering process reaches the Completed status. To avoid + miscounting, this only includes the first m line's first component. + + + + + qingsi@google.com + jeroendb@google.com + + Number of IPv6 network interfaces discovered in a PeerConnection Session. + + + + + qingsi@google.com + jeroendb@google.com + + Number of IPv6 local Candidates gathered in a PeerConnection Session once + the ICE address gathering process reaches the Completed status. To avoid + miscounting, this only includes the first m line's first component. + + + + + hta@chromium.org + + What key exchange protocol (DTLS or SDES) is used to establish the crypto + keys for a PeerConnection's RTP transport. + + + + + hta@chromium.org + + What key exchange protocol (DTLS or SDES) is used to establish the crypto + keys for a PeerConnection's RTP transport, specified per media type. + + + + + kron@chromium.org + + What setting for the SDP attribute extmap-allow-mixed has been asked for by + the creator of a PeerConnection. This is specified to the constructor + through the dictionary property offerExtmapAllowMixed which can be set to + either true or false. A default value will be used if it's not specified. + + + + + pthatcher@chromium.org + + Whether RTCP-mux is used for the PeerConnection (both the local and remote + description enable RTCP-mux). Recorded after SetLocalDescription and + SetRemoteDescription are called, once per PeerConnection. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of createAnswer(). Using complex SDP without explicitly + specifying the sdpSemantics is considered unsafe in this context because + such usage is sensitive to the rollout of a different default SDP semantic. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of createOffer(). Using complex SDP without explicitly + specifying the sdpSemantics is considered unsafe in this context because + such usage is sensitive to the rollout of a different default SDP semantic. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of setLocalDescription(answer). Using complex SDP + without explicitly specifying the sdpSemantics is considered unsafe in this + context because such usage is sensitive to the rollout of a different + default SDP semantic. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of setLocalDescription(offer). Using complex SDP + without explicitly specifying the sdpSemantics is considered unsafe in this + context because such usage is sensitive to the rollout of a different + default SDP semantic. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of setRemoteDescription(answer). Using complex SDP + without explicitly specifying the sdpSemantics is considered unsafe in this + context because such usage is sensitive to the rollout of a different + default SDP semantic. + + + + + hbos@chromium.org + + The SDP usage category ("safe", "unsafe" or + "unknown") of setRemoteDescription(offer). Using complex SDP + without explicitly specifying the sdpSemantics is considered unsafe in this + context because such usage is sensitive to the rollout of a different + default SDP semantic. + + + + + steveanton@chromium.org + + What SDP format is received in the remote offer. The value "no + tracks" means that no audio or video tracks were received. The value + "simple" means that at most one audio and at most one video track + was received. The value "complex" means that more than one audio + or more than one video track was received, and how this was signaled is + indicated ("Plan B" meaning with a=ssrc lines within the same m= + section and "Unified Plan" meaning with a separate m= section). + + + + + hta@chromium.org + + What SDP semantic (Unified Plan or Plan B) was detected when completing + negotiation of a PeerConnection. This is recorded when accepting an SDP + Answer. The value "mixed" means that the accepted answer included + both types of marker in the SDP. The value "none" will happen when + the answerer sends no media. + + + + + hta@chromium.org + + What SDP semantic (Unified Plan, Plan B or "use default") has been + asked for by the creator of a PeerConnection. + + + + + amithi@chromium.org + + Was simulcast applied to the local description and with which API surface. + + + + + amithi@chromium.org + + Was simulcast applied to the remote description and with which API surface. + + + + + amithi@chromium.org + + Simulcast was disabled because it is not supported by the remote party. This + is a counter that can take on only a single value (1). + + + + + amithi@chromium.org + + Counts the number of send encodings given to PeerConnection::AddTransceiver. + This histogram will be used to understand if and how the API is used. + + + + + + + steveanton@chromium.org + + What error code is reported by libsrtp when failing to unprotect an incoming + SRTCP (secured media control) packet. + + + + + qingsi@google.com + jeroendb@google.com + + Counters on the type of SRTP crypto suites used by WebRTC. This is collected + whenever the transport signals the OnCompleted event. + + + + + + + steveanton@chromium.org + + What error code is reported by libsrtp when failing to unprotect an incoming + SRTP (secured media) packet. + + + + + qingsi@google.com + jeroendb@google.com + + Counters on the type of SSL cipher suites used by WebRTC. This is collected + whenever the transport signals the OnCompleted event. + + + + + eshr@google.com + hbos@chromium.org + + Measures computer thermal state, sampled every 60s when a PeerConnection is + open with a video sender. Most quick toggles between thermal states are thus + not sampled, but thermal states are generally stable so these toggles should + be rare. + + + + + qingsi@google.com + jeroendb@google.com + Time to setup a peer to peer call with PeerConnection. + + + + qingsi@google.com + jeroendb@google.com + + Time to receive the first SignalNetworksChanged from the request to start + updating network in PeerConnection. + + + + + hta@chromium.org + webrtc-dev@chromium.org + + Capsule history of a WebRTC PeerConnection, encoded as a sequence of bits + encapsulated in an integer. Only a few values will be deemed interesting, + but the interesting values may change over time. + + + + + perkj@chromium.org + + Durations of audio tracks received over a PeerConnection. The stopwatch + starts when the track first becomes connected, and ends when it is + disconnected or very soon thereafter. + + + + + perkj@chromium.org + + Durations of video tracks received over a PeerConnection. The stopwatch + starts when the track first becomes connected, and ends when it is + disconnected or very soon thereafter. + + + + + perkj@chromium.org + + Sizes of messages sent over reliable data channels. The size of an + individual message is added to the histogram as a sample immediately when a + message is sent. + + + + + jiayl@chromium.org + Time for capturing one frame in screen capturing. + + + + perkj@chromium.org + + Durations of audio tracks sent over a PeerConnection. The stopwatch starts + when the track first becomes connected, and ends when it is disconnected or + very soon thereafter. + + + + + perkj@chromium.org + + Durations of video tracks sent over a PeerConnection. The stopwatch starts + when the track first becomes connected, and ends when it is disconnected or + very soon thereafter. + + + + + qingsi@google.com + jeroendb@google.com + + For clients using a shared source port per STUN binding request toward the + specified servers, success rate for requests which received a response with + various intervals between requests. Only the first instance of renderers + will conduct the trial and log this result. The STUN binding requests are + grouped into multiple batches and the success rate is calculated for an + individual batch. + + + + + qingsi@google.com + jeroendb@google.com + + For clients using a shared source port per STUN binding request, average RTT + for requests which received a response with various intervals between + requests. Only the first instance of renderers will conduct the trial and + log this result. + + + + + qingsi@google.com + jeroendb@google.com + + For clients using a shared source port per STUN binding request, success + rate for requests which received a response with various intervals between + requests. Only the first instance of renderers will conduct the trial and + log this result. + + + + + qingsi@google.com + jeroendb@google.com + + The maximum of consecutive delayed bytes caused by EWOULDBLOCKs from system. + This happens when system can't send any packet synchronously at that moment. + + + + + qingsi@google.com + jeroendb@google.com + + The percentage of packets delayed due to ERR_IO_PENDING from system in a + WebRTC socket. This happens when system can't send any packet synchronously + at that moment. + + + + + qingsi@google.com + jeroendb@google.com + + The duration that it takes to send out a packet in system layer. This + includes both the queuing time (under the condition when socket returns + EWOULDBLOCK from system) as well as the time system takes to finish the + asynchronous send. For UDP, it's the time from P2PSocketHostUdp::Send to + P2PSocketHostUdp::HandleSendResult. Tcp part is to be implemented. + + + + + perkj@chromium.org + + Sizes of messages sent over unreliable data channels. The size of an + individual message is added to the histogram as a sample immediately when a + message is sent. + + + + + andresp@chromium.org + + The state of a UserMediaRequest when it gets destroyed before having a + result. + + Note: "Explicitly Cancelled" means + MediaStreamImpl::cancelUserMediaRequest was called and not necessarily that + the user cancelled. Those are likely tracked as UserMediaRequest with a + result of permission denied. + + + + + grunell@chromium.org + + Counters for UserMediaRequests results such as failure reasons. The standard + specification error names are in parenthesis. + + + + + + + asapersson@chromium.org + webrtc-video@google.com + + The average number of adaptation changes per minute for a sent video stream. + Recorded when a stream is removed. + + + + + + + holmer@chromium.org + + The average round-trip time of a WebRTC call in milliseconds. Recorded when + a stream is removed. + + + + + + + asapersson@chromium.org + + The absolute value of the sync offset between a rendered video frame and the + latest played audio frame is measured per video frame. The average offset + per received video stream is recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of sent frames that are limited in resolution due to bandwidth + for a sent video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + webrtc-video@google.com + + For frames that are limited in resolution due to bandwidth, the average + number of disabled resolutions is recorded for a sent video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of received bits per second for a received video stream. Recorded + when a stream is removed. The total number of bytes is divided by the time + the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent bits per second for a sent video stream. Recorded when a + stream is removed. The total number of bytes is divided by the time the + video stream exists. + + + + + + + asapersson@chromium.org + + Percentage of frames that are limited in resolution due to CPU for a sent + video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + Average current delay for a received video stream. This is the actual delay + imposed on frames (where the goal is to reach the target delay (see + WebRTC.Video.TargetDelayInMs)). Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The average QP (quantizer value) per frame for a received VP8 video stream. + Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of decoded frames per second for a received video stream. + Recorded when a stream is removed. The total number of frames is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The average decode time per frame for a received video stream. Recorded when + a stream is removed. + + + + + kron@chromium.org + + The decode time per frame for a received video stream. Continously updated + after each frame has been decoded. + + + + + + + asapersson@chromium.org + + Percentage of delayed frames to renderer for a received video stream. + Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The average delay of delayed frames to renderer for a received video stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by a capturer for a sent video stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by an encoder's internal rate limiter for a + sent video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped because encoder queue is full for a sent + video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a + sent video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by a WebRTC on the receive side because they + are incomplete or undecodable. + + + + + + + asapersson@chromium.org + + The average QP (quantizer value) per frame for a sent video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + webrtc-video@google.com + + Configured video codec for a sent video stream. Recorded when a + VideoSendStream is destroyed (for streams whose lifetime is longer than 10 + seconds). + + + + + + + asapersson@chromium.org + + The average encode time per frame for a sent video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + The average end-to-end delay per frame for a received video stream. Recorded + when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The maximum end-to-end delay per frame for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of received FEC bits per second for a received video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent FEC bits per second for a sent video stream. Recorded + when a stream is removed. The total number of bytes is divided by the time + the video stream exists. + + + + + + + asapersson@chromium.org + + The number of received RTCP FIR packets per minute for a sent video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent RTCP FIR packets per minute for a received video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + hbos@chromium.org + + The number of |H264DecoderImpl| events, such as an initialization or + decoding error, that have occurred. At most one Init and one Error is + reported per |H264DecoderImpl| instance. This is to avoid the same event + from being reported multiple times (e.g. if there is an error you might + re-initialize or get a decode error every frame which would otherwise + pollute the data). + + + + + + + hbos@chromium.org + + The number of |H264EncoderImpl| events, such as an initialization or + encoding error, that have occurred. At most one Init and one Error is + reported per |H264EncoderImpl| instance. This is to avoid the same event + from being reported multiple times (e.g. if there is an error you might + re-initialize or get an encode error every frame which would otherwise + pollute the data). + + + + + kron@chromium.org + webrtc-video@google.com + + The number of hardware decoded frames between fallbacks to software decoder + for a received video stream. + + + + + + + asapersson@chromium.org + + The number of incoming frames per second for a sent video stream. Recorded + when a stream is removed. The total number of frames is divided by the time + the video stream exists. + + + + + + + asapersson@chromium.org + + The average input height per frame (for incoming frames to video engine) for + a sent video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The average input width per frame (for incoming frames to video engine) for + a sent video stream. Recorded when a stream is removed. + + + + + ilnik@chromium.org + webrtc-video@google.com + + The 95th percentile of interframe delay for a received video stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average interframe delay for a received video stream. Recorded when a + stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The maximum interframe delay for a received video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + Average jitter buffer delay for a received video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + Permille of frames that are key frames for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + Permille of frames that are key frames for a sent video stream. Recorded + when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average duration of a freeze in video playback. Recorded when a received + stream is removed or content type changes. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average duration of a smooth video playback. Recorded when a received + stream is removed or content type changes. + + + + + + + asapersson@chromium.org + + The number of received media payload bits per second for a received video + stream. Recorded when a stream is removed. The total number of bytes is + divided by the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent media payload bits per second for a sent video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of received RTCP NACK packets per minute for a sent video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent RTCP NACK packets per minute for a received video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + ssilkin@chromium.org + + The number of video freezes per minute for a received video stream. Recorded + when a stream is removed or content type changes. + + + + + + + asapersson@chromium.org + + The number of times a video stream has been paused/resumed during a call. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average number of resolution down-switches per minute for a received + video stream. Recorded when a stream is removed or content type changes. + + + + + + + asapersson@chromium.org + + Average delay (network delay (rtt/2) + jitter delay + decode time + render + delay) for a received video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of received padding bits per second for a received video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent padding bits per second for a sent video stream. Recorded + when a stream is removed. The total number of bytes is divided by the time + the video stream exists. + + + + + + + asapersson@chromium.org + + Percentage of time that the video has been paused for a sent video stream. + Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of received RTCP PLI packets per minute for a sent video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent RTCP PLI packets per minute for a received video stream. + Recorded when a stream is removed. The total number of packets is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + For frames that are downscaled in resolution due to quality, the average + number of downscales is recorded for a sent video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of sent frames that are downscaled in resolution due to quality + for a sent video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of received FEC packets for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + The average received height per frame for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of received packets lost for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + The average received width per frame for a received video stream. Recorded + when a stream is removed. + + + + + + + asapersson@chromium.org + + The lifetime of a video receive stream. Recorded when a VideoReceiveStream + instance is destroyed. + + + + + + + asapersson@chromium.org + + Percentage of recovered media packets from FEC packets for a received video + stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of sent frames to the renderer per second for a received video + stream. Recorded when a stream is removed. The total number of frames is + divided by the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of pixels (sqrt(width*height)) of sent frames to the renderer per + second for a received video stream. Recorded when a stream is removed. The + total number of pixels is divided by the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of retransmitted bits per second for a received video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of retransmitted bits per second for a sent video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The absolute value of the difference between the estimated frequency during + RTP timestamp to NTP time conversion and the actual value (i.e. 90 kHz) is + measured per received video frame. The max offset during 40 second intervals + is stored. The average of these stored offsets per received video stream is + recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The number of received bits over RTX per second for a received video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + asapersson@chromium.org + + The number of sent bits over RTX per second for a sent video stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + sprang@chromium.org + + Percentage of sent frames that are limited in resolution due to bandwidth + for a sent (screen content) video stream. Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + For frames that are limited in resolution due to bandwidth, the average + number of disabled resolutions is recorded for a sent (screen content) video + stream. Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + The number of sent bits per second for a sent screenshare stream. Recorded + when a stream is removed. The total number of bytes is divided by the time + the video stream exists. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average QP (quantizer value) per frame for a received VP8 screenshare + stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by a capturer for a sent screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by an encoder's internal rate limiter for a + sent screenshare stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped because encoder queue is full for a sent + screenshare stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a + sent screenshare stream. Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + The average encode time per frame for a sent (screen content) video stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average end-to-end delay per frame for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The maximum end-to-end delay per frame for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + The number of sent FEC bits per second for a sent screenshare stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + sprang@chromium.org + + The number of received RTCP FIR packets per minute for a sent screenshare + stream. Recorded when a stream is removed. The total number of packets is + divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + Ratio of sent frames to dropped frames at the encoder. The value is reported + when a stream is removed and is calculated as the total number frames sent + divided by the number of dropped frames. + + + + + + + sprang@chromium.org + + Ratio of sent frames to number of re-encoded frames (due to target bitrate + overshoot). The value is reported when a stream is removed and is calculated + as the total number frames sent divided by the number of re-encoded frames. + + + + + + + asapersson@chromium.org + + The number of incoming frames per second for a sent (screen content) video + stream. Recorded when a stream is removed. The total number of frames is + divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + The average input height per frame (for incoming frames to video engine) for + a sent (screen content) video stream. Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + The average input width per frame (for incoming frames to video engine) for + a sent (screen content) video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The 95th percentile of interframe delay for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average interframe delay for a received screenshare stream. Recorded + when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The maximum interframe delay for a received screenshare stream. Recorded + when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Permille of frames that are key frames for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + Permille of frames that are key frames for a sent (screen content) video + stream. Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + Stats for the lower layer (TL0) of a screenshare stream in conference mode. + + + + + + + sprang@chromium.org + + Stats for the higher layer (TL1) of a screenshare stream in conference mode. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average duration of a freeze in screenshare playback. Recorded then a + received stream is removed or content type changes. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average duration of a smooth video playback for screenshare stream. + Recorded when a received stream is removed or content type changes. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The number of received media payload bits per second for a received + screenshare stream. Recorded when a stream is removed. The total number of + bytes is divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + The number of sent media payload bits per second for a sent screenshare + stream. Recorded when a stream is removed. The total number of bytes is + divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + The number of received RTCP NACK packets per minute for a sent screenshare + stream. Recorded when a stream is removed. The total number of packets is + divided by the time the video stream exists. + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average number of resolution down-switches per minute for a receive + screenshare stream. Recorded when a stream is removed or content type + changes. + + + + + + + sprang@chromium.org + + The number of sent padding bits per second for a sent screenshare stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + sprang@chromium.org + + The number of received RTCP PLI packets per minute for a sent screenshare + stream. Recorded when a stream is removed. The total number of packets is + divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + For frames that are downscaled in resolution due to quality, the average + number of downscales is recorded for a sent (screen content) video stream. + Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + Percentage of sent frames that are downscaled in resolution due to quality + for a sent (screen content) video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average received height per frame for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Percentage of received packets lost for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The average received width per frame for a received screenshare stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The lifetime of a screenshare receive stream. Recorded when a + VideoReceiveStream instance is destroyed. + + + + + + + sprang@chromium.org + + The number of retransmitted bits per second for a sent screenshare stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + sprang@chromium.org + + The number of sent bits over RTX per second for a sent screenshare stream. + Recorded when a stream is removed. The total number of bytes is divided by + the time the video stream exists. + + + + + + + sprang@chromium.org + + The average delay (of average delays) of sent packets for a sent (screen + content) video stream. Recorded when a stream is removed. The delay is + measured from a frame is input to video engine until a packet is sent to the + network. For each sent packet, the average delay of all sent packets over + the last second is reported. The average of these reported delays is + recorded. + + + + + + + sprang@chromium.org + + The average delay (of max delays) of sent packets for a sent (screen + content) video stream. Recorded when a stream is removed. The delay is + measured from a frame is input to video engine until a packet is sent to the + network. For each sent packet, the maximum delay of all sent packets over + the last second is reported. The average of these reported delays is + recorded. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + The number of sent frames per second for a sent (screen content) video + stream. Recorded when a stream is removed. The total number of frames is + divided by the time the video stream exists. + + + + + + + sprang@chromium.org + + The average sent height per frame for a sent (screen content) video stream. + Recorded when a stream is removed. + + + + + + + sprang@chromium.org + + Percentage of sent packets lost for a sent screenshare stream. Recorded when + a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Ratio between Screenshare.SentFramesPerSecond and + Screenshare.InputFramesPerSecond in percents. Recorded when a stream is + removed. The total number of sent frames is divided by the total number of + input frames and multiplied by 100. + + + + + + + sprang@chromium.org + + The average sent width per frame for a sent (screen content) video stream. + Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Percentage of time the received screenshare stream playbacks low quality + blocky video. Recorded when a stream is removed or content type changes. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Percentage of time the received screenshare stream playbacks HD resolution. + Recorded when a stream is removed or content type changes. + + + + + + + sprang@chromium.org + + Percentage of unique RTCP NACK requests that are received in response to a + sent screenshare stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + The average send delay of sent packets for a sent video stream. Recorded + when a stream is removed. The delay is measured from a packet is sent to the + transport until leaving the socket. + + + + + + + asapersson@chromium.org + + The average delay (of average delays) of sent packets for a sent video + stream. Recorded when a stream is removed. The delay is measured from a + frame is input to video engine until a packet is sent to the network. For + each sent packet, the average delay of all sent packets over the last second + is reported. The average of these reported delays is recorded. + + + + + + + asapersson@chromium.org + + The average delay (of max delays) of sent packets for a sent video stream. + Recorded when a stream is removed. The delay is measured from a frame is + input to video engine until a packet is sent to the network. For each sent + packet, the maximum delay of all sent packets over the last second is + reported. The average of these reported delays is recorded. + + + + + + + asapersson@chromium.org + + The lifetime of a video send stream. Recorded when a VideoSendStream + instance is destroyed. + + + + + + + asapersson@chromium.org + + The number of sent frames per second for a sent video stream. Recorded when + a stream is removed. The total number of frames is divided by the time the + video stream exists. + + + + + + + asapersson@chromium.org + + The average sent height per frame for a sent video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of sent packets lost for a sent video stream. Recorded when a + stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Ratio between SentFramesPerSecond and InputFramesPerSecond in percents. + Recorded when a stream is removed. The total number of sent frames is + divided by the total number of input frames and multiplied by 100. + + + + + + + asapersson@chromium.org + + The average sent width per frame for a sent video stream. Recorded when a + stream is removed. + + + + + + + asapersson@chromium.org + + Average target delay (jitter delay + decode time + render delay) for a + received video stream. Recorded when a stream is removed. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Percentage of time the receive video stream playbacks low quality blocky + video. Recorded when a stream is removed or content type changes. + + + + + + + ilnik@chromium.org + webrtc-video@google.com + + Percentage of time the receive video stream playbacks HD resolution. + Recorded when a stream is removed or content type changes. + + + + + + + asapersson@chromium.org + + Percentage of unique RTCP NACK requests that are received in response to a + sent video stream. Recorded when a stream is removed. + + + + + + + asapersson@chromium.org + + Percentage of unique RTCP NACK requests that are sent in response to a + received video stream. Recorded when a stream is removed. + + + + + + + perkj@chromium.org + + Counts occurences of if the VP8 software decoder runs out of buffers due to + that they are not returned to the buffer pool. See http://crbug/652923 and + http://crbug/542522. + + + + + guidou@chromium.org + hbos@chromium.org + mcasas@chromium.org + emircan@chromium.org + armax@chromium.org + Counts number of calls to WebRTC APIs from JavaScript. + + + + guidou@chromium.org + armax@chromium.org + + Counts the number of calls to WebRTC APIs from JavaScript once per session. + A session is a crude estimate since its implemented as the lifetime of the + render process that called the WebRTC API. + + + + + jiayl@chromium.org + Time for capturing one frame in window capturing. + + + + eladalon@chromium.org + saeedj@google.com + manj@google.com + dmitriyg@google.com + + The result of calls to the API for the collection and uploading of WebRTC + event logs. + + + + + eladalon@chromium.org + saeedj@google.com + manj@google.com + dmitriyg@google.com + + NetError returned by the SimpleURLLoader object in charge of uploading a + WebRTC event log file. + + + + + eladalon@chromium.org + saeedj@google.com + manj@google.com + dmitriyg@google.com + + Tracks the uploading or discarding of WebRTC event logs that were previously + collected. + + + + + guidou@chromium.org + webrtc-dev@chromium.org + + Counts the number of WebRTC text log events per web application. Suffixed by + event. + + + + + guidou@chromium.org + webrtc-dev@chromium.org + + Network error codes for WebRTC text log upload failures. Recorded when an + upload attempt fails. + + + + + guidou@chromium.org + webrtc-dev@chromium.org + + Counts upload failures for WebRTC text log. Error codes for network errors + are logged in WebRtcTextLogging.UploadFailureNetErrorCode. Recorded when an + upload attempt fails. + + + + + + diff --git a/tools/metrics/histograms/histograms_xml/windows/histograms.xml b/tools/metrics/histograms/histograms_xml/windows/histograms.xml new file mode 100644 index 0000000000000000000000000000000000000000..73b95f574bed925e4ea1f4cb40ac88be3d5ef94c --- /dev/null +++ b/tools/metrics/histograms/histograms_xml/windows/histograms.xml @@ -0,0 +1,297 @@ + + + + + + + + + + forshaw@chromium.org + wfh@chromium.org + + Records if the APPID driver is running which indicates Applocker is enabled + and running. This does not guarantee that Applocker is configured to enforce + any rules. Reported once per browser session, on startup. + + + + + brucedawson@chromium.org + jessemckenna@google.com + + The result of prefetching chrome.dll on Windows, including whether a + fallback to slow prefetch took place, and why if so. + + + + + fdoray@chromium.org + + The amount of CPU time a call to ComputeNativeWindowOcclusionStatus() takes. + + + + + grt@chromium.org + + The Windows error code relating to a failed attempt to operate on a file or + a directory. + + + + + + + wfh@chromium.org + brucedawson@chromium.org + + The Windows version (base::win::Version) as reported by GetVersionEx(). This + is queried shortly after startup. + + + + + brucedawson@chromium.org + gab@chromium.org + + The value of TimeTicks::IsHighResolution(). Reported once per browser + session, on startup. + + + + + stanisc@chromium.org + + Percentage of elapsed time the high resolution timer is activated. The usage + is reported by each of Chrome processes individually (without aggregation) + and logged every 10 minutes. + + + + + rkc@chromium.org + rockot@chromium.org + + Whether Hyper-V is enabled on this machine. Logged shortly after startup. + This metric will only be logged on Windows 10+. + + + + + pmonette@chromium.org + + Whether connection error has happened for the UtilWin service. Every time a + connection is made to the service, a "false" value is reported to + provide a baseline. Every time a mojo connection error happens, a + "true" value is reported, which typically means the utility + process crashed. + + + + + + + markchang@google.com + pmonette@chromium.org + + Indicates whether Chrome is pinned to the Windows taskbar for the current + user. Recorded shortly after startup. + + + + + pmonette@chromium.org + + Indicates whether a connection error occured between the browser and the + shell handler process. This is usually caused by a crash in the utility + process. This is logged every time the pinned state is queried. + + + + + pmonette@chromium.org + chrdavis@microsoft.com + + Indicates whether Chrome is pinned to the Windows taskbar for the current + user. Recorded shortly after startup. This is different from + Windows.IsPinnedToTaskbar in that we do not check if the pin to taskbar verb + is available on the shortcut and only relies on the shortcut existing in the + User Pinned folder. + + + + + + + wfh@chromium.org + brucedawson@chromium.org + + The Windows version (base::win::Version) as reported by VeryQueryValue() on + kernel32.dll. This is queried shortly after startup. + + + + + chrisha@chromium.org + pmonette@chromium.org + + The result of reading the InspectionResultsCache from disk. The cache is + read once at startup when the ModuleInspector needs it. + + + + + chrisha@chromium.org + pmonette@chromium.org + + The result of writing the InspectionResultsCache to disk. This is done every + time the ModuleDatabase becomes idle. + + + + + davidbienvenu@chromium.org + fdoray@chromium.org + + The number of Chrome browser windows in a given visibility state. This is + computed using ComputeNativeWindowOcclusionStatus() and is recorded every 10 + minutes. + + + + + pmonette@chromium.org + + Indicates whether a connection error occured between the browser and the + shell handler process. This is usually caused by a crash in the utility + process. This is logged every time SelectFile() function is called and the + WinOOPSelectFileDialog feature is enabled. + + + + + + + wfh@chromium.org + brucedawson@chromium.org + + The 32-bit hash of the lower-case parent process basename (e.g. + explorer.exe) of the main Chrome executable. Reported once during startup as + part of install verification. + + + + + + + wfh@chromium.org + brucedawson@chromium.org + + A 32-bit value formed from combining the minor and patch level of the + currently running Windows operating system. E.g. "Windows 10 OS Version + 1809 (Build 17763.503)" would be 17763 (0x4563), combined with 503 + (0x1F7) = 0x456301F7. If either minor or patch level exceeds the value that + can fit in a 16-bit unsigned integer, then this histogram will report 0. + Reported once, shortly after browser startup. + + + + + grt@chromium.org + + The state of an item in the filesystem following an operation on it. + + + + + rkc@chromium.org + rockot@chromium.org + + The processor family type. Logged shortly after startup. The value is + specified in the SMBIOS specification, section 7.5.2: + https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf + This metric will only be logged on Windows 10+. + + + + + rkc@chromium.org + rockot@chromium.org + + Whether virtualization has been enabled in the system firmware. Logged + shortly after startup. This metric will only be logged on Windows 10+. + + + + + zturner@chromium.org + Count of browser launches from a Windows tablet pc. + + + + grt@chromium.org + etiennep@chromium.org + + The number of files failed to be deleted in a single directory by the + browser process's tmp file deleter on Windows. These are files that were + left behind on previous runs when third-party software interfered with + Chrome's ability to delete its own temporary files. No value is emitted for + a directory if no delete attempts are made. Otherwise, the fail count will + be zero or more. + + + + + grt@chromium.org + etiennep@chromium.org + + The number of files deleted in a single directory by the browser process's + tmp file deleter on Windows. These are files that were left behind on + previous runs when third-party software interfered with Chrome's ability to + delete its own temporary files. No value is emitted for a directory if no + delete attempts are made. Otherwise, the success count will be zero or more. + + + + + + diff --git a/tools/metrics/histograms/merge_xml.py b/tools/metrics/histograms/merge_xml.py index 697412feb52c0fe29cd8cc645ca0ac58b304c63b..510a7d6f36dad7f99b53c71f4e4c1824572ec940 100755 --- a/tools/metrics/histograms/merge_xml.py +++ b/tools/metrics/histograms/merge_xml.py @@ -128,8 +128,8 @@ def MakeNodeWithChildren(doc, tag, children): """ node = doc.createElement(tag) for child in children: - if child.tagName == 'histograms': - expand_owners.ExpandHistogramsOWNERS(child) + # if child.tagName == 'histograms': + # expand_owners.ExpandHistogramsOWNERS(child) node.appendChild(child) return node